Difference between revisions of "Neutron/ML2/ALE-Omniswitch"
| Line 1: | Line 1: | ||
= OmniSwitch Plug-in for OpenStack Liberty Installation = | = OmniSwitch Plug-in for OpenStack Liberty Installation = | ||
| − | |||
The OmniSwitch OpenStack Networking Plug-in (OONP) for OpenStack Liberty offers infrastructure services for OpenStack logical networks by coordinating the orchestration of Alcatel-Lucent OmniSwitches as the underlying physical network. When used in conjunction with the OpenVSwitch plug-in, end-to-end multi-tenant network provisioning through OpenStack Networking (Quantum/ Neutron) is achieved. | The OmniSwitch OpenStack Networking Plug-in (OONP) for OpenStack Liberty offers infrastructure services for OpenStack logical networks by coordinating the orchestration of Alcatel-Lucent OmniSwitches as the underlying physical network. When used in conjunction with the OpenVSwitch plug-in, end-to-end multi-tenant network provisioning through OpenStack Networking (Quantum/ Neutron) is achieved. | ||
| Line 10: | Line 9: | ||
==OmniSwitch OpenStack Networking Plug-in Architecture== | ==OmniSwitch OpenStack Networking Plug-in Architecture== | ||
| − | |||
The OpenStack Networking ML2 plug-in provides an extensible architecture that supports a variety of mechanism drivers for configuring physical networks. The architecture provides an environment where multiple independent drivers can be used to configure different network devices from different vendors. Each driver uses its own internal mechanism to communicate with their respective network elements. From the OpenStack Neutron-server perspective a single interface is provided through which the required networking services are provided to the OpenStack cloud applications. This allows OpenStack Network- ing to configure the physical network as well as the virtual switch instances running on the hypervisors. In addition, the OpenStack Networking L3-agent and DHCP-agent are fully supported. | The OpenStack Networking ML2 plug-in provides an extensible architecture that supports a variety of mechanism drivers for configuring physical networks. The architecture provides an environment where multiple independent drivers can be used to configure different network devices from different vendors. Each driver uses its own internal mechanism to communicate with their respective network elements. From the OpenStack Neutron-server perspective a single interface is provided through which the required networking services are provided to the OpenStack cloud applications. This allows OpenStack Network- ing to configure the physical network as well as the virtual switch instances running on the hypervisors. In addition, the OpenStack Networking L3-agent and DHCP-agent are fully supported. | ||
| Line 23: | Line 21: | ||
* OS6860 and OS6860E with AOS 811-R01. | * OS6860 and OS6860E with AOS 811-R01. | ||
| + | |||
[[Image:Basic_topology.png]] | [[Image:Basic_topology.png]] | ||
| Line 28: | Line 27: | ||
In this deployment scenario, the OmniSwitch ML2 Mechanism Driver uses configuration elements from the OpenVSwitch database to ensure configuration consistency and consistent VLAN ID assignment between it and the OVSNeutronPluginV2 plug-in. | In this deployment scenario, the OmniSwitch ML2 Mechanism Driver uses configuration elements from the OpenVSwitch database to ensure configuration consistency and consistent VLAN ID assignment between it and the OVSNeutronPluginV2 plug-in. | ||
| + | |||
==OpenStack Networking API support== | ==OpenStack Networking API support== | ||
OpenStack applications using the northbound Neutron 2.0 APIs can manage logical network resources on the underlying physical network without knowing about the networking devices in the physical network. | OpenStack applications using the northbound Neutron 2.0 APIs can manage logical network resources on the underlying physical network without knowing about the networking devices in the physical network. | ||
The plug-in supports all of the standard Neutron 2.0 APIs (listed below). | The plug-in supports all of the standard Neutron 2.0 APIs (listed below). | ||
| + | |||
| + | {| border="1" cellpadding="2" cellspacing="0" | ||
| + | | '''Network''' | ||
| + | | '''Subnet''' | ||
| + | | '''Port''' | ||
| + | | - | ||
| + | | List Network | ||
| + | | List Subnet | ||
| + | | List Port | ||
| + | | - | ||
| + | | Show Network | ||
| + | | Show Port | ||
| + | | Show Port | ||
| + | | - | ||
| + | | Create Network | ||
| + | | Create Subnet | ||
| + | | Create Port | ||
| + | | - | ||
| + | | Update Network | ||
| + | | Update Subnet | ||
| + | | Update Port | ||
| + | | - | ||
| + | | Delete Network | ||
| + | | Delete Subnet | ||
| + | | Delete Port | ||
| + | | - | ||
| + | |} | ||
Revision as of 08:55, 20 August 2015
OmniSwitch Plug-in for OpenStack Liberty Installation
The OmniSwitch OpenStack Networking Plug-in (OONP) for OpenStack Liberty offers infrastructure services for OpenStack logical networks by coordinating the orchestration of Alcatel-Lucent OmniSwitches as the underlying physical network. When used in conjunction with the OpenVSwitch plug-in, end-to-end multi-tenant network provisioning through OpenStack Networking (Quantum/ Neutron) is achieved.
The plug-in is intended to be installed in existing OpenStack Liberty environments to configure the underly- ing physical network for its cloud networking operations.
- Note. This OONP release for Liberty supports only the base plug-in features such as link aggregation, Virtual Chassis, VPA-based networking, and driver support for Telnet and REST. Advanced features such as UNP, MVRP, SPB, and QoS are not currently supported.
OmniSwitch OpenStack Networking Plug-in Architecture
The OpenStack Networking ML2 plug-in provides an extensible architecture that supports a variety of mechanism drivers for configuring physical networks. The architecture provides an environment where multiple independent drivers can be used to configure different network devices from different vendors. Each driver uses its own internal mechanism to communicate with their respective network elements. From the OpenStack Neutron-server perspective a single interface is provided through which the required networking services are provided to the OpenStack cloud applications. This allows OpenStack Network- ing to configure the physical network as well as the virtual switch instances running on the hypervisors. In addition, the OpenStack Networking L3-agent and DHCP-agent are fully supported.
Release OONP_K_R01_3 of the OONP work with the OVS ML2 driver.
The OmniSwitch ML2 Mechanism Driver supports the following hardware platforms with its respective AOS software releases.
- OS6900 and OS10K with AOS 732-R01 SW release and above
- OS685X and OS9000 with AOS 645-R02 SW release and above
- OS6250 and OS6450 with AOS 664-R01 and above, limited to the features supported on this platform
- OS6860 and OS6860E with AOS 811-R01.
In this deployment scenario, the OmniSwitch ML2 Mechanism Driver uses configuration elements from the OpenVSwitch database to ensure configuration consistency and consistent VLAN ID assignment between it and the OVSNeutronPluginV2 plug-in.
OpenStack Networking API support
OpenStack applications using the northbound Neutron 2.0 APIs can manage logical network resources on the underlying physical network without knowing about the networking devices in the physical network.
The plug-in supports all of the standard Neutron 2.0 APIs (listed below).
| Network | Subnet | Port | - | List Network | List Subnet | List Port | - | Show Network | Show Port | Show Port | - | Create Network | Create Subnet | Create Port | - | Update Network | Update Subnet | Update Port | - | Delete Network | Delete Subnet | Delete Port | - |
