This page is maintained by OPNFV and OpenStack community members. Rather than establish a project for OpenStack the OPNFV community has agreed to work on establishing focus community groups where we will describe community engagement practices, identify community leaders, manage our contributions toward those communities and generally get ourselves organised well enough to be a benefit, rather than a burden, to our source communities.
This list of the primary OpenStack and OPNFV projects, with links to the wikis and Project Technical Leaders, is designed to facilitate collaboration. Please follow the blueprint process below to request features in OpenStack.
To facilitate the work of developers submitting blueprints to OpenStack, we have instituted a process for requirements projects which consists of the following:
repository/requirements/reference_document.rst- this document should describe the goal at a high level for OPNFV consumers
The table below is a summary of the currently in-flight blueprints for OpenStack Mitaka. Regularly updated.
Blueprint status can be "Work in progress" (blueprint being actively edited), "Under review" (blueprint is final and submitted for review), "Approved" (approved for inclusion, development work not yet started), "In development", "Completed" (work accepted upstream), "Rejected" (not approved for inclusion), "Deferred" (to be submitted for next release).
If you have a blueprint which you would like reviewed, email firstname.lastname@example.org to schedule a review on the weekly technical review call.
|OpenStack Project||Blueprint name||Blueprint URL||OPNFV project driving||Lead contributor||Developer||Status|
|Ceilometer||Add independent alarm report mechanism||https://blueprints.launchpad.net/ceilometer/+spec/add-independent-alarm-mechanism||HA for OPNFV||Zhang Shaoman||Abandoned (Liberty) in favour of Monasca approach|
|Event Alarm Evaluator||https://blueprints.launchpad.net/ceilometer/+spec/event-alarm-evaluator||Doctor||Ryota Mibu||Ryota Mibu||Completed (Liberty)|
|Nova||New nova API call to mark nova-compute down||https://blueprints.launchpad.net/nova/+spec/mark-host-down||Doctor||Tomi Juvonen||Roman Dobosz||Completed (Liberty)|
|Support forcing service down||https://blueprints.launchpad.net/python-novaclient/+spec/support-force-down-service||Doctor||Tomi Juvonen||Carlos Goncalves||Completed (Liberty)|
|Get valid server state||https://blueprints.launchpad.net/nova/+spec/get-valid-server-state||Doctor||Tomi Juvonen||Tomi Juvonen||Completed (Mitaka)|
|Get servers filtered by host status||https://blueprints.launchpad.net/nova/+spec/servers-by-host-status||Doctor||Tomi Juvonen||Tomi Juvonen||In review (Newton)|
|Add notification for service status change||https://blueprints.launchpad.net/nova/+spec/service-status-notification||Doctor||Balazs Gibizer||Balazs Gibizer||Completed (Mitaka)|
|(VNF_Geo_site_redundancy)Expose quiesce unquiesce api||https://blueprints.launchpad.net/nova/+spec/expose-quiesce-unquiesce-api||Multisite||Chaoyi Huang||Zhenyu Zheng||In development (Mitaka)|
|Congress||Event-Driven Policy Engine||Copper||Bryan Sullivan||roadmap (post-R1)|
|Data Source Extensions||Copper||Bryan Sullivan||roadmap (post-R1)|
|Keystone||(multisite identity service management)Can't specify identity endpoint for token validation among several keystone servers in keystonemiddleware||https://bugs.launchpad.net/keystone/+bug/1488347||Multisite, HA for OPNFV||Chaoyi Huang / Hans Feldt||Completed (Liberty) (Bug # 1405717)|
|OpenStack Hierarchical Administrative Framework||https://blueprints.launchpad.net/keystone/+spec/hierarchical-administrative-boundary||ONOSFW||Prakash Ramchandran||Stalled|
|Cinder||Add pagination query support for cinder snapshots/backup in a large scale system||https://blueprints.launchpad.net/cinder/+spec/snapshots-and-bakcup-support-pagination-query||Multisite||Chi Zhang||Completed (Liberty)|
|Using Change-Since Filter for Resource Query based on a specified time period for better sync in a large scale system||https://blueprints.launchpad.net/cinder/+spec/resource-change-since-filter||Multisite||Zhiyuan Cai||Stalled|
|(VNF_Geo_site_redundancy)Get replicated volume ref for DR||https://blueprints.launchpad.net/cinder/+spec/get-replica-volume-ref-for-dr||Multisite||Wang Hao||Work In Progress|
|new cinder API call to mark cinder-volume down||https://blueprints.launchpad.net/cinder/+spec/mark-services-down||Doctor||Wenjuan Dong||Work In Progress|
|Support forcing service down (CLI)||https://blueprints.launchpad.net/python-cinderclient/+spec/mark-service-down-cli||Doctor||Wenjuan Dong||Work In Progress|
|Heat-Translator||Implement new Networking feature in TOSCA||https://blueprints.launchpad.net/heat-translator/+spec/tosca-networking||Parser||Simeon Monov||Completed (Liberty)|
|Neutron||OpenStack Service Chaining Framework||https://blueprints.launchpad.net/neutron/+spec/openstack-service-chain-framework||VNFFG||Cathy Zhang||Superseded (networking-sfc and/or Tacker)|
|Allow admin to mark agents down||https://bugs.launchpad.net/neutron/+bug/1513144||Doctor||Carlos Goncalves||Carlos Goncalves||Stalled (Incomplete)|
|(VNF High Availability across VIM)ml2 cross backends extension spec||https://bugs.launchpad.net/neutron/+bug/1486882||Multisite||Shi Hanzhang||Shi Hanzhang||Work In Progress|
Relevant process pages:
A good blueprint has the following characteristics:
This provides the material for an informed, useful discussion upstream of the feature and whether the proposed approach is the best way to accomplish the high level goal.
It is possible to get code into OpenStack without going through the Blueprint process by submitting a patch for review directly, but it does not make it easier to get the code accepted.
Blueprints should be discussed and reviewed online in advance of Tokyo, and advocated for the design summit working sessions, to ensure they are included in scope for Mitaka. Blueprints proposed after the Tokyo Summit are not eliminated, but will have a hard time being approved for Mitaka.
As a general rule of thumb, the earlier in the cycle you engage with the project teams, the more time you have for features and fixes to land in the release. Make sure that code starts coming in as soon as the spec is approved, as there are cases where time is spent on specs and then code shows up too late to be reviewed in time anyway.
Some additional links on successfully shepherding blueprints through review:
From the Project Team Guide:
Key dates for Mitaka, with emphasis on Nova; consolidated cross-project schedule. All projects follow the Mitaka release schedule except Nova and Cinder, which are listed under Project-specific events.
With Liberty, OpenStack has implemented a Core and "Big Tent" project architecture. This enables a common definition of what constiutes "OpenStack" for interoperability, as well as opens the door to more projects.
After the first OPNFV Summit in November 2015, it became clear there would be tremendous value in a consistent means to present OPNFV blueprints and patches to the OpenStack projects. It's important to send your blueprints to email@example.com, for adding to the table above. From there,