Difference between revisions of "NetworkServiceDiablo"
| Line 11: | Line 11: | ||
The diagram below describes two things: | The diagram below describes two things: | ||
| − | + | # The software services architecture, and the relationship of the Virtual Network Service and IPAM Service to Nova | |
| − | + | # The logical network architecture elements used to describe a virtual network topology in the Diablo timeframe | |
(diagram goes here) | (diagram goes here) | ||
| Line 25: | Line 25: | ||
The Virtual Networking Service will have the following responsiblities: | The Virtual Networking Service will have the following responsiblities: | ||
| − | # | + | # Provide API for managing L2 network abstraction (“virtual networks”?) |
| + | # Provide authentication, verification, etc | ||
| + | # Provide error handling | ||
| + | # Decompose request (if necessary) | ||
| + | # Dispatch requests to appropriate plug-in(s) | ||
| + | # Resource consumption look-up service | ||
| + | # Plug-in capability directory | ||
Revision as of 06:32, 28 April 2011
Network Service Proposal for Diablo
Overview
This proposal is the result of discussions between several community members that had independently submitted blueprints for networking capabilities in Openstack. Those proposals included:
(List proposals here)
This page describes the resulting target services to be delivered in experiemental form in the Diablo timeframe.
Network Services Model
The diagram below describes two things:
- The software services architecture, and the relationship of the Virtual Network Service and IPAM Service to Nova
- The logical network architecture elements used to describe a virtual network topology in the Diablo timeframe
(diagram goes here)
Nova Refactoring and Responsibilities
It is proposed that Nova networking be refactored in two ways:
- Combine networking capabilities in a more contained model, but do not remove support for existing options
- Add support for the Virtual Network Service to the existing flat (static), flat (DHCP), and VLAN options
Virtual Networking Service
(This project needs a name. "Quantum" was proposed.)
The Virtual Networking Service will have the following responsiblities:
- Provide API for managing L2 network abstraction (“virtual networks”?)
- Provide authentication, verification, etc
- Provide error handling
- Decompose request (if necessary)
- Dispatch requests to appropriate plug-in(s)
- Resource consumption look-up service
- Plug-in capability directory
