Jump to: navigation, search

Difference between revisions of "NeutronStarterBugs"

Line 19: Line 19:
 
== Community Projects ==
 
== 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.  Send email will also help you identify the right people on the Quantum team to help you complete this project.   
+
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.   
  
* '''Tempest for System/Integration testing'''.   We need system/integration testing that exercises much more functionality than the basic excercise.sh scriptWe'd also like to explore integration with Tempest and working with the openstack CI team to make sure that both unit tests and system/integration testing is a gate to Quantum commits in Folsom. 
+
* '''Proxy Nova Security Groups to Quantum'''. https://blueprints.launchpad.net/nova/+spec/nova-quantum-security-group-proxy (this is a Nova change)
* '''Quantum + Horizon Integration for Advanced Features''': letting tenants drive Quantum configuration via the Horizon web gui will be important for widespread adoption + use of QuantumThere is already a base integration of Horizon and Quantum, but we will need a lot more help to get advanced Quantum features (e.g., security groups, L3, port-status, admin-state, port-statistics) expose.
+
* '''Vif Hotplugging'''.  https://blueprints.launchpad.net/nova/+spec/network-adapter-hotplug  (this is a Nova change)
* '''String Localization''': Compared to Nova we haven't paid much attention to string localization. If this is important to you, updating the codebase for this would be a great way to get up to speed on Quantum.
+
* '''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  (related to nova security group proxy blueprint above).  
 
* '''Ceiliometer Integration'''.  Use Quantum Notification mechanism (in development) to integrate with Ceiliometer (https://launchpad.net/ceilometer)  
 
* '''Ceiliometer Integration'''.  Use Quantum Notification mechanism (in development) to integrate with Ceiliometer (https://launchpad.net/ceilometer)  
 
* '''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/).   

Revision as of 20:46, 21 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.

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.