Cisco Cisco Intercloud Fabric for Provider White Paper

Page 11 of 13

Application Deployment Across Hybrid Cloud

Application-Tier Deployment

Data and authentication servers (the MySQL back end) are configured to stay in the private data center, and

therefore the intercloud fabric extender trunk is configured to carry VLAN 101 only. The front-end Apache and PHP

server will be deployed in both the private and public clouds; hence, VLAN 101 is configured to be extended to the

public cloud. Because traffic will enter only through the private data center, the solution requires just a Layer 2

extension of VLAN 101 to the public cloud (Figure 6).

In this configuration, front-end servers deployed in the cloud will access the MySQL database server using the

Cisco Intercloud Fabric link. These cloud virtual machines will have their default gateway set to the router on the

enterprise data center, hence enabling routing between all the virtual machines. To load balance customer traffic

onto multiple front-end servers, a load balancer can also be deployed.

Note: For test purposes, a load balancer installation can be avoided by accessing the front-end server URLs
directly.

Figure 6. Application Deployment Across Hybrid Cloud

Creating a Virtual Machine Template in the Cloud

The intercloud fabric director gives customers several ways to deploy a virtual machine in the cloud. One of the

most common methods is to create a virtual machine template and then upload this template to the public cloud.

When the template resides in the public cloud, deploying a new virtual machine directly in the public cloud helps

customers avoid uploading large amounts of data from their private data center to the cloud. When the template is

uploaded using the director, the director performs the appropriate conversion to the cloud virtual machine format

and exposes the new template as a catalog item available in director GUI, as shown in Figure 7.