Difference between revisions of "NeutronStarterBugs"
Jaegerandi (talk | contribs) (→Starter Bugs) |
|||
| Line 12: | Line 12: | ||
These are bugs that folks new to Neutron might want to pick off as an introduction: | These are bugs that folks new to Neutron might want to pick off as an introduction: | ||
| − | * [https://bugs.launchpad.net/ | + | * [https://bugs.launchpad.net/neutron/+bugs?field.tag=low-hanging-fruit neutron low-hanging-fruit bugs ] |
| − | * [https://bugs.launchpad.net/python- | + | * [https://bugs.launchpad.net/python-neutronclient/+bugs?field.tag=low-hanging-fruit python-neutronclient low-hanging-fruit bugs ] |
<BR> | <BR> | ||
If you're new to Neutron, just assign the bug to yourself on launchpad, and feel free to use the bug (or the mailing list) to ask questions about how to fix it. | If you're new to Neutron, just assign the bug to yourself on launchpad, and feel free to use the bug (or the mailing list) to ask questions about how to fix it. | ||
Revision as of 12:58, 16 August 2013
Code Reviews
Before you even start fixing bugs, a good way to familiarize yourself with the Neutron codebase and development practices is to participate in code reviews.
- Neutron Server Reviews: https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z
- Neutron Client Reviews: https://review.openstack.org/#/q/status:open+project:openstack/python-neutronclient,n,z
Starter Bugs
These are bugs that folks new to Neutron might want to pick off as an introduction:
If you're new to Neutron, just assign the bug to yourself on launchpad, and feel free to use the bug (or the mailing list) to ask questions about how to fix it.
Community Projects
Note: if you're interested in taking on one of these community projects, create a blueprint and send email to the openstack dev list with thoughts and to get feedback from the team. In some cases, the blueprint may already exist and be assigned to someone, but they may well be willing to assign it to you or split up the task. Send email will also help you identify the right people on the Neutron team to help you complete this project.
- Auto-associate Floating IPs. https://blueprints.launchpad.net/quantum/+spec/auto-associate-floating-ip
- DB profiling at scale. https://blueprints.launchpad.net/quantum/+spec/db-profiling-at-scale
- Make Neutron rootwrap use OpenStack Common https://blueprints.launchpad.net/quantum/+spec/quantum-common-rootwrap
- Load only extensions supported by the current plugin https://blueprints.launchpad.net/quantum/+spec/load-plugin-supported-extensions
- Make sure all euca-* commands are proxied correctly to Neutron https://blueprints.launchpad.net/quantum/+spec/quantum-v2-euca-compat (has a dependency on https://blueprints.launchpad.net/nova/+spec/nova-quantum-security-group-proxy).
- Integration with Orchestration/PaaS Layers. While some people will interact with Neutron + Nova APIs directly or via Horizon, others will want to use a mechanism that define a complete topology of servers and network connectivity as a single template. One possibility for this is the new OpenStack Heat project (http://wiki.openstack.org/Heat). Heat is an open source implementation of the Amazon Cloudformation APIs (http://aws.amazon.com/cloudformation/).
- Developer documentation. Core openstack projects have develop documentation generated using sphinx and available at <project-name>.openstack.org (e.g., http://keystone.openstack.org/). Neutron currently only has a basic wiki page for developers: http://wiki.openstack.org/NeutronDevelopment . We'll need to improve this significantly.
- Audit existing code coverage report and identify additional unit tests that should be written to improve those numbers.
- Openstack Common Make Neutron leverage the "openstack common" library whenever possible. See QuantumOpenstackCommon for a list of files that would be great candidates. If those files contain code that is not specific to Neutron, consider adding it to Openstack common. See: https://github.com/openstack/openstack-common
