Application owners feel challenged when they move their multi-VM, multi-tier environment from data-center to AWS & Google cloud. The networking changes -- you cannot keep the same IP addresses, netmask, networking interconnect on public cloud as you have in your data center. Ravello’s software defined networking (SDN) overlay gives you the ability to mirror your data-center network on AWS & Google cloud without making changes. This article goes over how to mirror the static IPs that you have in your data center on top of Ravello’s platform to be able to run your application on AWS & Google cloud.
Here’s a quick video showing you how to set up your Static IPs for interfaces on Ravello.
As an example, I will walk you through how to mirror the Static IPs that I have in my Data Center onto Ravello’s platform.
I have the following load-balancer network setup in my data-center that I want to mirror on Ravello.
Ravello allows you to set up the network properties for each of the VMs - including static IPs. Navigate to the VM → Network Tab to be able to change the network settings.
Scroll to the network interface for the VM that you want to associate a Static IP with, and click on the ‘Static’ radio button for IP configuration.
Next, you will be presented with fields to enter the Static IP, Netmask, Gateway and DNS server for this interface.
Ravello’s SDN automatically creates a virtual switch based on the IP address and netmask of the interfaces, and adds the interfaces that are part of the same subnet to the same virtual switch. As an example, look at the following:
The webserver-1 is configured with an IP address of 188.8.131.52/24 and webserver-2 10.168.0.3/24. This prompts Ravello’s SDN to create two virtual switches 184.108.40.206/24 and 10.168.0.0/24 (highlighted in red above).
To put both webserver-1 and webserver-2 onto the same switch, all that you need to do is give webserver-1 and webserver-2 an IP address that are a part of the same subnet and have the same netmask, and Ravello’s SDN will put both the network interfaces corresponding to webserver-1 and webserver-2 onto the same virtual switch. For example, if we change the IP address of webserver-2 to 220.127.116.11/24, Ravello will put both of them on the same virtual switch 18.104.22.168/24 (highlighted in red below).
Next, if we want to put both the web-servers onto the same virtual switch as NetScaler load balancer, we will assign webserver-1, webserver-2 and NetScaler’s internal interface IP addresses & netmask that are on the same subnet. Changing IP for webserver-1 to 192.168.0.2/24, webserver-2 to 192.168.0.3/24 and NetScaler’s internal interface to 192.168.0.1/24 leads to new virtual switch 192.168.0.0/24 on Ravello that joins these three interfaces (see below).
With these changes, the network on Ravello mirrors my network in data center.
Here is how Ravello’s SDN behaves behind the scenes
Using the constructs listed above, I can configure static IPs for my application and run it on AWS or Google cloud using Ravello.