Difference between revisions of "NeutronStarterBugs"
| Line 27: | Line 27: | ||
* '''Load only extensions supported by the current plugin''' https://blueprints.launchpad.net/quantum/+spec/load-plugin-supported-extensions | * '''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 Quantum''' 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). | * '''Make sure all euca-* commands are proxied correctly to Quantum''' 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 Quantum + 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/). | * '''Integration with Orchestration/PaaS Layers'''. While some people will interact with Quantum + 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/). Quantum currently only has a basic wiki page for developers: http://wiki.openstack.org/QuantumDevelopment . We'll need to improve this significantly in Folsom. | * '''Developer documentation'''. Core openstack projects have develop documentation generated using sphinx and available at <project-name>.openstack.org (e.g., http://keystone.openstack.org/). Quantum currently only has a basic wiki page for developers: http://wiki.openstack.org/QuantumDevelopment . We'll need to improve this significantly in Folsom. | ||
* '''Audit existing code coverage''' report and identify additional unit tests that should be written to improve those numbers. | * '''Audit existing code coverage''' report and identify additional unit tests that should be written to improve those numbers. | ||
* '''Openstack Common''' Make Quantum 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 Quantum, consider adding it to Openstack common. See: https://github.com/openstack/openstack-common | * '''Openstack Common''' Make Quantum 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 Quantum, consider adding it to Openstack common. See: https://github.com/openstack/openstack-common | ||
Revision as of 21:30, 23 January 2013
Code Reviews
Before you even start fixing bugs, a good way to familiarize yourself with the Quantum codebase and development practices is to participate in code reviews.
- Quantum Server Reviews: https://review.openstack.org/#/q/status:open+project:openstack/quantum,n,z
- Quantum Client Reviews: https://review.openstack.org/#/q/status:open+project:openstack/python-quantumclient,n,z
Starter Bugs
These are bugs that folks new to Quantum might want to pick off as an introduction:
If you're new to Quantum, 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 Quantum team to help you complete this project.
- Vif Hotplugging. https://blueprints.launchpad.net/nova/+spec/network-adapter-hotplug (this is a Nova change)
- 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 Quantum 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 Quantum 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 Quantum + 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/). Quantum currently only has a basic wiki page for developers: http://wiki.openstack.org/QuantumDevelopment . We'll need to improve this significantly in Folsom.
- Audit existing code coverage report and identify additional unit tests that should be written to improve those numbers.
- Openstack Common Make Quantum 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 Quantum, consider adding it to Openstack common. See: https://github.com/openstack/openstack-common
