This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
community:openstack:process_review [2015/03/27 11:21] Christopher Price |
community:openstack:process_review [2015/03/27 11:30] Christopher Price |
||
---|---|---|---|
Line 11: | Line 11: | ||
* The OPNFV Requirement description document ''repository/requirements/reference_document.rst'' | * The OPNFV Requirement description document ''repository/requirements/reference_document.rst'' | ||
* The OPNFV blueprint proposal document ''repository/design_docs/reference_document.rst'' | * The OPNFV blueprint proposal document ''repository/design_docs/reference_document.rst'' | ||
- | The Requirement document should describe the motivation for the features needed in OPNFV including references to the documented use cases captured by the requirements project and all requirements listed with reference to associated blueprints or upstream development proposals needed. \\ | + | The Requirement document should describe the motivation for the features needed in OPNFV including references to the documented use cases captured by the requirements project and all requirements listed with reference to associated blueprints or upstream development proposals needed. |
- | The blueprint proposal document should start as a proposal from the requirement projects and describe the exact requirement on a particular upstream component in such a way as to describe the implementation of that requirement for that project. This should be an atomic description of the specific requirement and provide needed links to associated requirements and design documents. | + | |
==== OPNFV Requirement to OpenStack Blueprint process ==== | ==== OPNFV Requirement to OpenStack Blueprint process ==== | ||
- | stuff here about lifecycle | + | The blueprint proposal document should start as a proposal from the requirement projects and describe the exact requirement on a particular upstream component in such a way as to describe the implementation of that requirement for that project. This should be an atomic description of the specific requirement and provide needed links to associated requirements and design documents. \\ |
- | links to the templates | + | Once the blueprint has been reviewed and achieves maturity and clarity on what it intends to implement, lists requirements, use cases and intention sufficiently well it should be migrated to the OpenStack specs repository for review, design and development. \\ |
+ | The intention is not to perform development analysis in OPNFV, but to ensure when we engage the OpenStack community we have sufficient clarity in the proposal that a design discussion can occur. | ||
+ | |||
+ | OpenStack blueprint templates: | ||
+ | [[https://github.com/openstack/nova-specs/blob/master/specs/liberty-template.rst|Nova Template]] | ||
+ | [[https://github.com/openstack/ceilometer-specs/blob/master/specs/template.rst|Celiometer Template]] | ||
+ | [[https://github.com/openstack/neutron-specs/blob/master/specs/template.rst|Neutron Template]] | ||
+ | [[https://github.com/openstack/sahara-specs/blob/master/specs/template.rst|Sahara Template]] | ||
==== OPNFV related blueprints ==== | ==== OPNFV related blueprints ==== |