Jump to: navigation, search

Difference between revisions of "NeutronStarterBugs"

(Community Projects)
 
(18 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]] -->
Line 5: Line 5:
 
== Code Reviews ==
 
== 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.   
+
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.   
* Quantum Server Reviews: https://review.openstack.org/#/q/status:open+project:openstack/quantum,n,z
+
* Neutron Server Reviews: https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z
* Quantum Client Reviews: https://review.openstack.org/#/q/status:open+project:openstack/python-quantumclient,n,z
+
* Neutron Client Reviews: https://review.openstack.org/#/q/status:open+project:openstack/python-neutronclient,n,z
  
 
== Starter Bugs ==
 
== Starter Bugs ==
  
These are bugs that folks new to Quantum might want to pick off as an introduction: [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&assignee_option=none&field.assignee=  low-hanging-fruit bugs ]
+
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 ]
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.
+
* [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.
  
 
== 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 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 + Horizon Integration''': letting tenants drive Quantum configuration via the Horizon web gui will be important for widespread adoption + use of QuantumArvind is working on the 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. 
+
* '''Auto-associate Floating IPs'''. https://blueprints.launchpad.net/neutron/+spec/auto-associate-floating-ip
* '''API Quotas'''. Service providers need to be able to limit the set of resources a tenant can consume in a flexible way. For example, it might limit each tenant to creating 10 networks by default, with the ability to increase this quota for select tenants who request it. Nova has a framework for Quotas, which we can leverage, ideally using code that is in openstack-common. 
+
* '''DB profiling at scale'''https://blueprints.launchpad.net/neutron/+spec/db-profiling-at-scale
* '''Notifications API'''. Other openstack projects like Nova have a notifications API for external tools to listen to event (e.g., network created/destroyed, floating ip allocated/deallocated).  Quantum should leverage that code (ideally as code from openstack-common) for its own notifications infrastructure.  One example of an external system that would like to consume that information is Ceiliometer (https://launchpad.net/ceilometer)  
+
* '''Make Neutron rootwrap use [[OpenStack]] Common''' https://blueprints.launchpad.net/neutron/+spec/quantum-common-rootwrap
* '''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/).   
+
* '''Load only extensions supported by the current plugin''' https://blueprints.launchpad.net/neutron/+spec/load-plugin-supported-extensions
* '''System/Integration testing'''.  We need system/integration testing that exercises much more functionality than the basic excercise.sh script.  We'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, hua)
+
* '''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).
* '''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.  
+
* '''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.   
 
* '''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.