Difference between revisions of "NaaS-Core"

Revision as of 12:30, 24 March 2011

Launchpad Entry: NovaSpec:network-service
Created: 24 March 2011
Contributors: Ilya Alekseyev, Patrick Ancillotti, Andrey Brindeyev, Erik Carlin, Rick Clark, Dan Mihai Dumitriu, Ram Durairaj, Søren Hansen, Koji Iida, Hisaharu Ishii, Masanori Itoh, Adam Johnson, Youcef Laribi, Romain Lenglet, Brad McConnell, Eldar Nugaev, Salvatore Orlando, John Purrier, Andy Smith, Troy Toman, Dan Wendlandt, Zhixue Wu

Summary

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".

A network created with the core NaaS API can be therefore regarded as a virtual network switch which potentially spans over all the compute nodes in the cloud. NaaS APIs should be decoupled by the actual implementation of the core service, meaning that NaaS does not mandate any specific model for created networks (e.g.: VLANs, IP tunnels).

Goals

Goal 1: allow customers to...

Goal 2: allow customers to...

Goal 3: allow CSPs to ...

Rationale

User stories

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

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.

@@ Line 17: / Line 17: @@
 '''Goal 3''': allow CSPs to ...
-== Release Note ==
-This section should include a paragraph describing the end-user impact of this change.  It is meant to be included in the release notes of the first release in which it is implemented.  (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
-It is mandatory.
 == Rationale ==
@@ Line 28: / Line 23: @@
 == 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 ===
@@ Line 44: / Line 30: @@
 * 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.
 ----
 [[Category:Spec]]