In this blog, we will cover Opencontrail capability to create virtual networks and show inter-connectivity between machines in the following environments:
- Virtual machines spawned on hypervisors:
- KVM
- ESXi
- Docker Containers and
- Bare Metal Servers.
Compute nodes that are based on a particular hypervisor technology are grouped together as separate Availability Zones (AZ). Thus, compute nodes running ESXi and Docker are two separate AZs, and the ones running KVM is the default AZ.
The bare metal server is physically connected to a standard switch that supports standard industry protocols. The virtual network that includes the bare metal server is instantiated as a standard VRF (Virtual Routing & Forwarding Table) within the switch.
In the topology beow, two virtual networks are created, with one including VMs based on ESXi, KVM and Docker container, and the other including KVM and bare metal server. Each virtual network has been provisioned with a subnet. In the topology below, we should reachability across –
- G1(Docker container), G2(VM on ESXi host), G3 (VM on KVM host)
- G3 (VM on KVM host) and BM1 (Bare Metal Server)
This workflow is also demonstrated in the video below.
[video_lightbox_youtube video_id=”x2n5Q_ycx6o” width=”720″ height=”540″ auto_thumb=”1″]
So, to conclude Opencontrail has seamless integration and orchestration on different hypervisor technologies, Docker containers as well as Bare Metal environments. Having a single orchestration for compute and network certainly simplifies management and monitoring of heterogeneous environments.
