Jump to: navigation, search

Difference between revisions of "NeutronStarterBugs"

(Community Projects)
 
(25 intermediate revisions by 8 users not shown)
Line 1: Line 1:
__NOTOC__
+
 
 
<!-- ## page was renamed from [[QuantumCommunityProjects]] -->
 
<!-- ## page was renamed from [[QuantumCommunityProjects]] -->
 
<!-- ## page was renamed from [[QuantumStarterBugs]] -->
 
<!-- ## page was renamed from [[QuantumStarterBugs]] -->
== Starter Bugs ==
 
  
These are bugs that folks new to Quantum might want to pick off as an introduction:
+
== 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
  
https://bugs.launchpad.net/quantum/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.tag=low-hanging-fruit
+
== Starter Bugs ==
  
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.
+
These are bugs that folks new to Neutron might want to pick off as an introduction:
 +
* [https://bugs.launchpad.net/neutron/+bugs?field.tag=low-hanging-fruit  neutron low-hanging-fruit bugs ]
 +
* [https://bugs.launchpad.net/python-neutronclient/+bugs?field.tag=low-hanging-fruit python-neutronclient low-hanging-fruit bugs ]
 +
<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.
  
== Starter/Community Projects ==
+
== Community Projects ==
  
Note: if you're interested in taking on one of these starter projects, create a blueprint and send email to the netstack 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 Neutron team to help you complete this project.   
  
* '''quantum client improvements''', particularly making it act more like other openstack clients. Quantum client currently doesn't using standard arg parsing, so all args are positional, and there isn't good support for optional argumentsIt also isn't possible to put things like your credentials and tenant-id into environment variables (as is the case with other openstack clients). The output also is not in a standard table format like other clients, which can be confusing, and makes the output harder to parse with scripts. The commands should also use dashes, not underscores. Finally, figuring out how people should be able to extend the CLI to take advantage of extensions is another major area for improvement. ayoung also mentioned the important of specifying the endpoint as a URL, not as a host + port. This matches other clients. (Yong is working on this)
+
* '''Auto-associate Floating IPs'''. https://blueprints.launchpad.net/neutron/+spec/auto-associate-floating-ip
* '''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.  (interested parties: debo, davelaps)
+
* '''DB profiling at scale'''.  https://blueprints.launchpad.net/neutron/+spec/db-profiling-at-scale
* '''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.
+
* '''Make Neutron rootwrap use [[OpenStack]] Common''' https://blueprints.launchpad.net/neutron/+spec/quantum-common-rootwrap
* '''Quantum + Horizon Integration''':  letting tenants drive Quantum configuration via the Horizon web gui will be important for widespread adoption + use of Quantum.  An early version of the Quantum + Horizon integration no longer works with the current Nova + Quantum integration, so we need to redo it (it is currently disabled). We have folks from the Horizon team willing to help, but we need people familiar with Quantum to help them out.  (arvind is working on this, but others can definitely help)
+
* '''Load only extensions supported by the current plugin''' https://blueprints.launchpad.net/neutron/+spec/load-plugin-supported-extensions
 +
* '''Make sure all euca-* commands are proxied correctly to Neutron''' https://blueprints.launchpad.net/neutron/+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 templateOne 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.   
 
* '''Audit existing code coverage''' report and identify additional unit tests that should be written to improve those numbers.   
* '''Improve pylint score''' 
+
* '''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
* '''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
 
* '''Scale Testing'''  We need to be testing Quantum operations at large scale to identify any bottlenecks.  There are three likely divisions for this work.  1) Nova Quantum Integration 2) Quantum API Layer and 3) Plugin Layer.  Each plugin will have to be evaluated for scale independently, but it should be pretty easy to use the [[SamplePlugin]] just to test scale in the first two layers.
 

Latest revision as of 13:02, 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.

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.