Ravello’s SDN enables access to all the networking constructs available in data-center environments on public cloud. This allows one to mirror their data center setup on AWS or Google cloud. One of these networking constructs is a virtual router.
Ravello creates a virtual router in an ‘application’ when a Gateway is defined for one of the network interfaces associated with a VM in the application. As an example, Netscaler VM’s management interface has a Gateway (10.1.10.1) defined. Due to the presence of Gateway in the configuration, Ravello’s SDN creates a virtual router with a routable path, and connects it to virtual switch (10.1.10.0/24) that NetScaler’s management interface is plugged into.
If I want to connect the external interface on my NetScaler to be routable as well, all that I need to do is define a Gateway IP for that network interface, and Ravello will hook the virtual switch corresponding to this interface to the virtual router as well (see below).
If you are interested in bringing your own Juniper, Cisco (or any other external virtual router) for access to advanced feature-set, or to mirror your data center deployment - that is certainly possible as well. Ravello’s platform allows one to run VMware and KVM appliances ‘as-is’. One can easily import Cisco, Juniper, (or any other external virtual appliance) into their application, define the IP address of the external virtual router appliance to be the default gateway for other VMs in the application, and assign a default gateway to the external virtual router appliance so that it is connected to Ravello’s in-built virtual router. The built-in router in such scenarios simply acts as a forwarding engine.
Interested in exploring deploying external virtual routing appliance? We have published several how-to guides including Juniper, Cisco, Arista Networks, Citrix NetScaler, F5 Big IP, Palo Alto Networks, Fortinet FortGate, Barracuda and PfSense.