- play_arrow Overview
- play_arrow Zero-Touch-Provisioning
- play_arrow Fabric Configuration
- Image Management
- Onboard Brownfield Devices
- Onboard Greenfield Devices
- Device Import
- Create Virtual Network
- Create Logical Routers
- Create Network Policy
- Create Network IPAM
- Reconfigure Roles
- Managing Custom Roles
- View Node Profile Information
- Monitoring Fabric Jobs
- Terminating Ongoing Fabric Jobs
- Adding a Leaf or Spine Device to an Existing Fabric Using ZTP
- Grouping Fabric Devices and Roles Using Device Functional Groups
- Creating Layer 3 PNF Service Chains for Inter-LR Traffic
- Creating VNF Service Chains for Inter-LR Traffic
- Retaining the AS Path Attribute in a Service Chain
- Assisted Replication of Broadcast, Unknown Unicast, and Multicast Traffic
- Running Generic Device Operations Commands In Contrail Command
- Adding DHCP Server Information for Virtual Networks and Logical Routers
- Return Material Authorization
- Approaches to Enable External Connectivity for Overlay Networks
- Contrail Networking Supported Hardware Platforms and Associated Roles And Node Profiles
- play_arrow Managing Data Center Devices
- Data Center Interconnect
- Logical Router Interconnect
- Configuring Data Center Gateway
- Virtual Port Groups
- Configuring Virtual Port Groups
- Using Static, eBGP, PIM, and OSPF Protocols to Connect to Third-Party Network Devices
- Configuring Storm Control on Interfaces
- Creating Port Profiles, Storm Control Profiles, sFlow Profiles, or Telemetry Profiles by Cloning
- Configuring EVPN VXLAN Fabric with Multitenant Networking Services
- Edge-Routed Bridging for QFX Series Switches
- Activating Maintenance Mode on Data Center Devices
- Viewing the Network Topology
- Viewing Hardware Inventory of Data Center Devices
- Viewing Configuration of Devices Deployed in Contrail Fabric
- Detecting and Managing Manual CLI Configuration Changes
- Certificate Lifecycle Management Using Red Hat Identity Management
- Collapsed Spine Architecture
- Support for Superspine Role
- play_arrow High Availability in Contrail Networking
- play_arrow Integrating VMware with Contrail Networking Fabric
- play_arrow Extending Contrail Networking to Bare Metal Servers
- Bare Metal Server Management
- How Bare Metal Server Management Works
- LAG and Multihoming Support
- Adding Bare Metal Server to Inventory
- Launching a Bare Metal Server
- Onboarding and Discovery of Bare Metal Servers
- Launching and Deleting a Greenfield Bare Metal Server
- Destination Network Address Translation for Bare Metal Servers
- Troubleshooting Bare Metal Servers
Understanding OpenStack-Contrail Networking Fabric Integration
Contrail Networking Release 2011 supports integrating OpenStack with Contrail Networking Fabric. A Modular Layer 2 (ML2) Neutron plug-in is deployed for this integration. With this integration, you can manage underlay networks for OpenStack compute nodes.
Modular Layer 2 (ML2) Neutron Plug-in
Starting in Contrail Networking Release 2011, the ML2 Neutron plug-in is used to integrate OpenStack with Contrail Networking Fabric. Neutron is an OpenStack project that manages networking between interface devices. The ML2 plug-in enables OpenStack to use various layer 2 networking technologies that are found in complex real-world data centers.
In order to facilitate multi-vendor solutions, Neutron offers the following plug-ins:
Monolithic Plug-in
Modular Layer 2 (ML2) Plug-in
The Monolithic plug-in is no longer supported and is removed from OpenStack. With this release, the only supported plug-in is ML2. For more information on the plug-in, see ML2 Plug-in.
With Contrail Networking Release 2011, the ML2 plug-in is used with Contrail Command UI to facilitate multi-vendor solutions. ML2 plug-in works with Open vSwitch, Linux Bridge, and HyperV layer 2 agents. The ML2 plug-in simplifies adding support for layer 2 networking technologies. This plug-in requires less initial effort to deploy than what would be required to add a new monolithic plug-in.
The ML2 framework offers the following drivers:
| Type Drivers | Describes the type of underlying technology that is deployed. |
| Mechanism Drivers | Facilitates the multi-vendor solutions built upon the technology specified by type driver. |
Benefits of ML2 Plug-in
The following are the benefits of ML2 plug-in:
Helps in integrating OpenStack with Contrail Networking Fabric.
Used with Contrail Command to facilitate multi-vendor solutions.
Simplifies adding support for layer 2 networking technologies.
Design Overview
This section describes the topology.
Figure 2 depicts the OpenStack Controller, Contrail Networking Controller and the fabric. The Neutron Rest API, ML2 plug-in for layer 2 networking technologies, L3 router plug-in, and the mechanism drivers rests within the Neutron server. The ML2 plug-in mechanism driver (Tungsten Fabric ML2 Driver) and the Tungsten Fabric L3 driver connects the server to the Config API. The connection between the Config API and the fabric is established through the device manager.
| ML2 Neutron Plug-in | This plug-in is also called the ML2 plug-in. The ML2 Neutron plug-in is used to integrate OpenStack with Contrail Networking Fabric. This plug-in enables OpenStack to use various layer 2 networking technologies that are found in complex real-world data centers. For more information, see Modular Layer 2 (ML2) Neutron Plug-in. |
| Tungsten Fabric Mechanism Driver | This driver is also called the Tungsten Fabric ML2 Driver or ML2 Driver. This driver is located in the OpenStack repository. The driver communicates with the Contrail Controller and manages Juniper devices. This driver is triggered by the ML2 plug-in in response to networking events such as creating a virtual network or modifying a port, that is handled by Neutron. |
| Tungsten Fabric Router Service Plug-in | This is also called the L3 Router Plug-in. The Tungsten Fabric Router Service Plug-in supports routing functionality on fabric. This plug-in also supports vendor-specific routing functionality. This plug-in pushes the ERB or CRB routing configuration on leaf or spine devices respectively. |
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.