Difference between revisions of "Neutron/nsx-integrated-services"
< Neutron
(Created page with "= Scope = = Use Cases = = Implementation Overview = = Data Model Changes = = Configuration variables = = API = = Plugin Interface = = CLI Requirements = = Horizon Requ...") |
m |
||
| Line 1: | Line 1: | ||
= Scope = | = Scope = | ||
| + | |||
| + | This blueprint is about making the Nicira plugin capable of handling dhcp and metadata proxy services provided directly by the NSX platform. Once the feature is complete, Neutron deployments using NSX no longer require the installation and management of one or more dhcp and metadata proxy agents. Dhcp and metadata proxy services are going to provided by Logical Services Nodes, new components introduced by NSX 4.x. Logical Services Node is introduced to represent a logical entity that provides one or more services (i.e. dhcp) in the logical space (i.e. a logical network). | ||
= Use Cases = | = Use Cases = | ||
| + | |||
| + | * Brown-field OpenStack deployments that use Neutron/NSX as the networking engine: such existing deployments use dhcp and metadata proxy agents to provide dhcp services to tenant VM's and to proxy requests to the Nova metadata servers in certain conditions. Once the feature is complete the following use cases will be implemented: | ||
| + | |||
| + | # A tenant creates a network/subnet with dhcp enabled: the IP address set for a port created on the network is going to be handed out by a dhcp service ran and managed by NSX | ||
| + | # A tenant uplinks a subnet to a router: metadata requests are going to proxied via a metadata proxy service that is ran and managed by NSX | ||
| + | # An admin can migrate existing networks whose dhcp and metadata proxy services are provided by the neutron-dhcp-agent and neutron-metadata-proxy components to their respective entities managed by NSX. | ||
| + | |||
| + | * Green-field OpenStack deployments that use Neutron/NSX as the networking engine: such existing deployments will use NSX Logical Services Nodes to provide dhcp and metadata proxy services and both 1 and 2 as detailed above will be implemented. | ||
= Implementation Overview = | = Implementation Overview = | ||
| + | |||
| + | The following entities have been introduced: | ||
| + | |||
| + | * LsnManager: This class manages LSN (Logical Services Node) entities associated with neutron networks. Every Neutron network has a 1-1 mapping with a LSN node that exists in NSX. A LSN node can provide both dhcp and metadata proxy services. These services are provided by connecting the NSX logical switch representing the neutron network to the LSN node via a patch attachment between a NSX logical switch port and LSN port. Every LSN node can have multiple LSN ports but only one LSN port can be attached to a single NSX logical switch. A LSN port configuration holds the dhcp options to be used to provide dhcp services (allocation pool, IP and MAC mappings, etc). Currently only a single logical switch port can be patch-attached to a LSN port. This means that only single subnet can be created per a single neutron network. This limitation may be lifted in the future. Overall this class takes care of the following: | ||
| + | # CRUD operations of LSN entities in NSX | ||
| + | # CRUD operations of LSN port entities in NSX | ||
| + | # Puggling/Unplugging of Logical Services on/from the neutron network | ||
| + | # DHCP and Metadata configuration for the LSN port | ||
| + | |||
| + | * PersistentLsnManager: this class inherits from LsnManager and adds persistence capabilities to LsnManager, so to offload access to NSX. This class also adds the capability to recover from local datastore loss by pulling the LSN state from NSX on demand. | ||
| + | * MigrationManager: this class manages the migration process for neutron networks created before this feature was avaialable. It validates that a network is eligible for migration and executes it in case it is. | ||
| + | * DhcpMetadataBuilder: this class handles the deallocation of old dhcp and metadata proxy resources for a network being migrated and allocates the needed NSX LSN resources. | ||
| + | * nvp.DhcpAgentNotifyAPI: this class handles lifecycle events for subnets and ports when DHCP and Metadata proxy services are provided by NSX. | ||
| + | * combined.DhcpAgentNotifyAPI: this class handles lifecycle events for subnets and ports for both cases where DHCP and Metadata proxy services are provided by NSX (new networks only) or by the dhcp and metadata proxy agents (existing networks). | ||
= Data Model Changes = | = Data Model Changes = | ||
Revision as of 21:54, 30 October 2013
Contents
Scope
This blueprint is about making the Nicira plugin capable of handling dhcp and metadata proxy services provided directly by the NSX platform. Once the feature is complete, Neutron deployments using NSX no longer require the installation and management of one or more dhcp and metadata proxy agents. Dhcp and metadata proxy services are going to provided by Logical Services Nodes, new components introduced by NSX 4.x. Logical Services Node is introduced to represent a logical entity that provides one or more services (i.e. dhcp) in the logical space (i.e. a logical network).
Use Cases
- Brown-field OpenStack deployments that use Neutron/NSX as the networking engine: such existing deployments use dhcp and metadata proxy agents to provide dhcp services to tenant VM's and to proxy requests to the Nova metadata servers in certain conditions. Once the feature is complete the following use cases will be implemented:
- A tenant creates a network/subnet with dhcp enabled: the IP address set for a port created on the network is going to be handed out by a dhcp service ran and managed by NSX
- A tenant uplinks a subnet to a router: metadata requests are going to proxied via a metadata proxy service that is ran and managed by NSX
- An admin can migrate existing networks whose dhcp and metadata proxy services are provided by the neutron-dhcp-agent and neutron-metadata-proxy components to their respective entities managed by NSX.
- Green-field OpenStack deployments that use Neutron/NSX as the networking engine: such existing deployments will use NSX Logical Services Nodes to provide dhcp and metadata proxy services and both 1 and 2 as detailed above will be implemented.
Implementation Overview
The following entities have been introduced:
- LsnManager: This class manages LSN (Logical Services Node) entities associated with neutron networks. Every Neutron network has a 1-1 mapping with a LSN node that exists in NSX. A LSN node can provide both dhcp and metadata proxy services. These services are provided by connecting the NSX logical switch representing the neutron network to the LSN node via a patch attachment between a NSX logical switch port and LSN port. Every LSN node can have multiple LSN ports but only one LSN port can be attached to a single NSX logical switch. A LSN port configuration holds the dhcp options to be used to provide dhcp services (allocation pool, IP and MAC mappings, etc). Currently only a single logical switch port can be patch-attached to a LSN port. This means that only single subnet can be created per a single neutron network. This limitation may be lifted in the future. Overall this class takes care of the following:
- CRUD operations of LSN entities in NSX
- CRUD operations of LSN port entities in NSX
- Puggling/Unplugging of Logical Services on/from the neutron network
- DHCP and Metadata configuration for the LSN port
- PersistentLsnManager: this class inherits from LsnManager and adds persistence capabilities to LsnManager, so to offload access to NSX. This class also adds the capability to recover from local datastore loss by pulling the LSN state from NSX on demand.
- MigrationManager: this class manages the migration process for neutron networks created before this feature was avaialable. It validates that a network is eligible for migration and executes it in case it is.
- DhcpMetadataBuilder: this class handles the deallocation of old dhcp and metadata proxy resources for a network being migrated and allocates the needed NSX LSN resources.
- nvp.DhcpAgentNotifyAPI: this class handles lifecycle events for subnets and ports when DHCP and Metadata proxy services are provided by NSX.
- combined.DhcpAgentNotifyAPI: this class handles lifecycle events for subnets and ports for both cases where DHCP and Metadata proxy services are provided by NSX (new networks only) or by the dhcp and metadata proxy agents (existing networks).
