community:openstack:process_review
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
community:openstack:process_review [2015/03/27 11:20] Christopher Price |
community:openstack:process_review [2015/04/21 05:24] (current) Tomi Juvonen |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Process Change Proposal/Discussion page ====== | ||
| ====== OPNFV OpenStack community page ====== | ====== OPNFV OpenStack community page ====== | ||
| Line 11: | Line 12: | ||
| * 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 ==== | ||
| - | New table structure: | + | Proposed new table structure: |
| - | ^ OPNFV project ^ OPNFV Requirement ^ Lead Contributor ^ Blueprint ^ OPNFV Status ^ OpenStack Status ^ openstack project ^ | + | ^ OPNFV project ^ OPNFV Requirement ^ Lead Contributor ^ Blueprint ^ OPNFV Status ^ OpenStack Status ^ openstack project ^ |
| | Link to the OPNFV Project | ''repository/requirements/reference_document.rst'' | Lead Contributor | ''repository/design_docs/reference_document.rst'' | Status of the draft | Submitted/Review/Appr os | Target project for the BP | | | Link to the OPNFV Project | ''repository/requirements/reference_document.rst'' | Lead Contributor | ''repository/design_docs/reference_document.rst'' | Status of the draft | Submitted/Review/Appr os | Target project for the BP | | ||
| - | | [[:doctor|Doctor]] | [[https://etherpad.opnfv.org/p/doctor_requirement|Unavailability of physical resource]] | Ryota Mibu | [[https://blueprints.launchpad.net/nova/+spec/update-server-state-immediately|Report host fault to update server state immediately.]] | Under Review | Unsubmitted | Nova | | + | | [[:doctor|Doctor]] | [[https://etherpad.opnfv.org/p/doctor_requirement|Unavailability of physical resource]] | Ryota Mibu | [[https://blueprints.launchpad.net/nova/+spec/mark-host-down|New nova API call to mark nova-compute down.]] | Under Review | Unsubmitted | Nova | |
| | | | | | | | | | | | | | | | | | | ||
| Line 33: | Line 39: | ||
| If you have a blueprint which you would like reviewed, contact Dave Neary <dneary@redhat.com> or email <opnfv-tech-discuss@lists.opnfv.org> to schedule a review on the weekly technical review call. //This process is likely to evolve soon.// | If you have a blueprint which you would like reviewed, contact Dave Neary <dneary@redhat.com> or email <opnfv-tech-discuss@lists.opnfv.org> to schedule a review on the weekly technical review call. //This process is likely to evolve soon.// | ||
| + | |||
| + | Current table structure. | ||
| ^ OpenStack Project ^ Blueprint name ^ OPNFV project driving ^ Lead contributor ^ Status ^ | ^ OpenStack Project ^ Blueprint name ^ OPNFV project driving ^ Lead contributor ^ Status ^ | ||
community/openstack/process_review.1427455249.txt.gz · Last modified: 2015/03/27 11:20 by Christopher Price
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
