Difference between revisions of "Naas"
| Line 2: | Line 2: | ||
* '''Launchpad Entry''': [[NovaSpec]]:foo or [[SwiftSpec]]:foo | * '''Launchpad Entry''': [[NovaSpec]]:foo or [[SwiftSpec]]:foo | ||
* '''Created''': | * '''Created''': | ||
| − | * '''Contributors''': | + | * '''Contributors''': |
== Summary == | == Summary == | ||
| + | This is a draft with changes added on top of the NaaS core published few days ago. Changes will be highlighted red text in the beginning and end | ||
| − | The core functionality of Openstack Network-as-a-service (NaaS) is to provide a customer-facing service for creating and managing networks intended as "collection of virtual ports with shared connectivity". | + | The core functionality of Openstack Network-as-a-service (NaaS) is to provide a customer-facing service for creating and managing networks intended as "collection of virtual ports with shared connectivity". |
== Release Note == | == Release Note == | ||
| − | |||
Here is the Word Doc that describes this blueprint [[attachment:paas.doc]] | Here is the Word Doc that describes this blueprint [[attachment:paas.doc]] | ||
== Rationale == | == Rationale == | ||
| − | |||
== User stories == | == User stories == | ||
| − | |||
== Assumptions == | == Assumptions == | ||
| − | |||
== Design == | == Design == | ||
| − | |||
You can have subsections that better describe specific parts of the issue. | You can have subsections that better describe specific parts of the issue. | ||
== Implementation == | == Implementation == | ||
| − | |||
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: | This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: | ||
=== UI Changes === | === UI Changes === | ||
| − | |||
Should cover changes required to the UI, or specific UI that is required to implement this | Should cover changes required to the UI, or specific UI that is required to implement this | ||
=== Code Changes === | === Code Changes === | ||
| − | |||
Code changes should include an overview of what needs to change, and in some cases even the specific details. | Code changes should include an overview of what needs to change, and in some cases even the specific details. | ||
=== Migration === | === Migration === | ||
| + | Include: | ||
| − | |||
* data migration, if any | * data migration, if any | ||
* redirects from old URLs to new ones, if any | * redirects from old URLs to new ones, if any | ||
| Line 42: | Line 35: | ||
== Test/Demo Plan == | == Test/Demo Plan == | ||
| − | |||
This need not be added or completed until the specification is nearing beta. | This need not be added or completed until the specification is nearing beta. | ||
== Unresolved issues == | == Unresolved issues == | ||
| − | |||
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. | This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. | ||
== BoF agenda and discussion == | == BoF agenda and discussion == | ||
| − | |||
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected. | Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected. | ||
---- | ---- | ||
| + | |||
[[Category:Spec]] | [[Category:Spec]] | ||
Revision as of 17:20, 27 April 2011
Summary
This is a draft with changes added on top of the NaaS core published few days ago. Changes will be highlighted red text in the beginning and end
The core functionality of Openstack Network-as-a-service (NaaS) is to provide a customer-facing service for creating and managing networks intended as "collection of virtual ports with shared connectivity".
Release Note
Here is the Word Doc that describes this blueprint attachment:paas.doc
Rationale
User stories
Assumptions
Design
You can have subsections that better describe specific parts of the issue.
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
