Network Virtualization has arrived and it’s great. Hardware is getting simpler and networking is moving into the software layer. MidoNet is the bright new star in this space. Our solution completely decouples your cloud tenant networks from your physical network fabric. We are aiming specifically at customers who prefer the benefits of an open ecosystem.
- With Midonet you can build, manage and evolve your physical network separately from your virtual topologies
- Virtual Networks can be created programmatically by the thousands to accommodate workloads
- For the physical layer you can use simple multi-vendor networking hardware that you only need to configure once
- Because your networks are not enmeshed in your hardware, you get centralised management and control
- With centralised management and control, you get greater capability for self-service
- MidoNet brings vastly improved fault tolerance and high availability (any server, any service, any time)
- You get scalability through hierarchy, reduced protocols, optimised traffic, and minimal overhead
The result is greater agility, reduced load on your IT staff, and the ability to respond instantly to changing demands.
Demote the physical network.
MidoNet transforms the physical network from operational backbone to highly available capacity pool. Virtual networks can be created programmatically by the thousands to accommodate workloads. And by decoupling network management from network hardware, MidoNet enables improved self-service capability for even better agility.
MidoNet Key Features
How MidoNet Works
1. In an OpenStack deployment with MidoNet, MidoNet Storage Nodes and MidoNet Border Nodes are added to your cloud infrastructure. The MidoNet Storage Nodes thereby contain all the virtual topology and state information for your entire cloud.
2. The MidoNet Border Nodes enable connectivity to external networks. The MidoNet plugin for OpenStack is then installed.
3. Finally the MidoNet agent is installed on each compute node, completing the installation process.
4. MidoNet automatically creates a Provider Router which connects to the external network
5. When a new tenant is created in the Iaas platform, a Tenant Router is created in the virtual topology.
6. When the tenant creates VM’s and Networks, they are attached to their Tenant Router.
7. Various rules and subnets can be applied to the virtual infrastructure
The following diagram shows an example of inbound traffic from an external network to a VM:
- When a packet from an external network hits a MidoNet Border node and that traffic is destined for VM1, the MidoNet Border node queries the MidoNet Storage cluster and requests the virtual topology and state information for that path.
- The MidoNet Border node then simulates what would happen if the packet actually went through the virtual topology and transforms the packet accordingly.
- A tunnel is created between the MidoNet Border node and the compute host that houses VM1.
- The MidoNet Border node encapsulates the packet and sends it through the newly created tunnel.
- Once the compute host receives the packet, the MidoNet agent decapsulates the packet and delivers it to VM1. All subsequent packets destined from that Border Node to VM1 no longer have to go through the simulation and the packets are delivered at near line-rate speed.
With unparalleled expertise in network virtualization, Midokura can help you build a complete network architecture custom-designed for the needs of your enterprise. Or we can help you deploy Midonet in your existing cloud.
With the flexibility to utilize commodity hardware, many enterprises realize significant upfront cost savings. And with the reduced complexity of the physical network, there’s also the potential for significant reduction in total cost of ownership.
Tight Integration with OpenStack™
MidoNet is tightly integrated with OpenStack™, and provides plugins to handle nearly all of the networking functions found in OpenStack™, in a highly scalable, distributed system. Check out OpenStack™ + MidoNet to find out more.
The following articles contain third party technical deep dives into MidoNet’s architecture and functionality.