NaaS-Core

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

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.

---