Cisco Cisco Intercloud Fabric for Provider Design Guide
Page 19
Cloud VM Deployment
In current Cisco Intercloud Fabric use cases, four types of cloud VMs must be deployed in public cloud provider
data centers:
data centers:
●
Application VMs—VMs running business customers’ applications.
●
ICF Switch (Infra-ICS)—VMs providing Cisco ICF switched overlay functions.
●
ICF Router (Infra-CSR)—VMs providing routing, NAT, and VPN functions.
●
ICF Firewall (Infra-VSG)—VMs offering firewall and isolation functions.
Some of the infrastructure VMs impose certain deployment requirements, which are summarized in the following
table:
table:
Provider VM
Deployment
Requirements
Cloud VM Types
ICF Router
(Infra-CSR)
ICF Firewall
(Ingra-VSG)
ICF Switch
(Infra-ICS)
Application
VM
O/S Platform
Supported
64-bit Monta Vista
Linux with 2.6.32
Kernel
32-bit NXOS Linux
with 2.6.27 Kernel
64-bit Ubuntu
Linux with 3.10
Kernel
RHEL, CentOS,
Windows 2008 R2
OVF
Customization
Required
N/A
N/A
N/A
The OVF customization required for ICF Router (Infra-CSR) and Infra-VSG enables the cloud orchestrator (in this
case, Cisco ICFPP) to pass a set of OVF configuration parameters to the ICF Router programmatically during VM
instantiation. Depending on the approach that the service provider cloud platform takes to support the OVF
parameter-passing feature, the OVF customization process can be different for different service providers.
case, Cisco ICFPP) to pass a set of OVF configuration parameters to the ICF Router programmatically during VM
instantiation. Depending on the approach that the service provider cloud platform takes to support the OVF
parameter-passing feature, the OVF customization process can be different for different service providers.
Using the CloudStack platform as an example, the OVF parameter-passing requirement in a CloudStack
environment can be achieved by completing the following steps:
environment can be achieved by completing the following steps:
1. Obtain all necessary OVF parameters (such as VM IP address, VM netmask address, gateway IP address,
DNS, domain name, hostname, and so on) from the service provider. Cisco ICFPP uses this information to
create an OVF configuration XML file, named “ovf-env.xml”.
create an OVF configuration XML file, named “ovf-env.xml”.
2. Convert the “ovf-env.xml” file to an ISO image and, using the API registerIso ( ), register the image so that it
can be attached to a specific user.
3. Deploy the targeted VM in a Stopped state (that is, with the startvm parameter set to False) with the API
deployVirtualMachine ( ).
4. Attach the OVF configuration xml file, “ovf-env.xml” to the VM that was deployed with the API attachIso ( ).
5. Start the VM with the API startVirtualMachine ( ); the VM will pick up the parameters passed through the
configuration file.
Public Network Address Assignment
In certain Cisco ICF use cases, cloud VMs might need to communicate with systems on external networks such as
the Internet. These uses cases include the following:
the Internet. These uses cases include the following:
●
An application VM hosting a web server
●
An application VM that must communicate with external web servers
●
An application VM offers VPN services for branch offices
●
An infrastructure VM (such as Infra-ICS) that provides secure network extension for an enterprise.