With Cisco Intercloud Fabric Hybrid Cloud, customers have the ability to control this cloud environment through a single pane of glass, moving workloads across and between clouds, all with consistent networking and security policies. Cisco has totally simplified the environment between private and public cloud, which allows customers to choose the right cloud for their business requirements, regardless of underlying technologies like hypervisors. Build highly secure hybrid clouds and extend your existing data center to public clouds as needed, on demand, and with consistent network and security policies. With Cisco Intercloud Fabric Hybrid Cloud, you can do all this and more. Cloud providers can now offer a complete hybrid cloud solution. Differentiate your offering as a premium service and provide a robust set of cloud deployment options. Hybrid clouds gives you the benefits of a private and public cloud, whether you’re using the private cloud or using IT managed provider clouds.
Application admins and network admins surely have already been enlisted to figure out how the workload applications can function in the provider cloud and still interact with the private cloud. What services does the workload need? How does workload security work? How does workload routing work? How does the hybrid cloud environment impact the workload? How many different cloud provider APIs will need to be leafed? These are only a few of the considerations there can be many more. But what if you could put some or all of your workload in the provider cloud and not have to change anything? What if the Layer-2 network could be extended into the provider cloud? Cloud adoption has increased 61% from last year. Yet, 69% of organizations do not have mature cloud strategies in place. According to IDC’s global cloud study, the greater the level of cloud maturity, the better the outcomes. This includes increased revenue and strategic allocation of the IT budget.
Cisco Intercloud Fabric Hybrid Cloud
The Cisco Intercloud Fabric Hybrid Cloud installation documentation and videos go a long way to get you started, however we wanted to provide a bit more information to help you prepare for Cisco Intercloud Fabric installation, configuration and connection to either AWS or Azure or both. First you’ll need an account at the cloud provider; the account needs and capabilities are different for each provider. Standard AWS account, account policy requirements, full Amazon EC2 access policy, full AWS S3 access policy — if you are going to deploy Windows images, full AWS Marketplace — if you are going to deploy Intercloud Cisco Fabric Router, and to deploy the Intercloud Fabric Router in AWS Market place you will need to accept the terms for the image. Cisco Intercloud Fabric Router and Cisco Intercloud Fabric Firewall are not yet deployable in Azure, download the presentation on Cisco’s website for a step by step guide to getting an AWS or Azure account.
The Intercloud Fabric Release Notes detail all the physical and virtual hardware requirements. You will also find the details for which Guest OS versions are supported and any other of the latest caveats related to Intercloud Fabric. Currently Cisco Intercloud Fabric Hybrid Cloud infrastructure runs on vSphere 5.1 (including update 1) and 5.5, an Enterprise Plus license is not needed. The infrastructure is composed of three virtual appliances; Cisco Intercloud Fabric Director (ICFD), Cisco Prime Network Services Controller (PNSC), and Cisco Cloud Virtual Supervisor Module (cVSM). VMware vCenter is required even if you are deploying on a single VMware ESX host. Cisco Intercloud Fabric And Hybrid Cloud needs to connect to a vCenter environment. From a networking perspective you’ll need some IP addresses, management IP address and IP address for the networks that will be extended to the provider cloud. For the ICF Infrastructure the IP requirement is; ICFD-1, PNSC-1, and cVSM-1.
Two virtual machines create the secure tunnel over which layer 2 networking is extended. The ICX/ICS pair (the IcfCloud) can be provisioned as single VM instances at each end of the Layer-2 extension or in an HA mode where there is a primary and secondary VM instance of the ICX in the enterprise cloud and a primary and secondary VM instance of the ICS in the provider cloud. VM instance of the ICX include ICX-1 in standalone mode or 2 in HA mode and ICS-1 in standalone mode or 2 in HA mode. There are two network services that can be deployed in AWS, the Intercloud Fabric Router and the Cisco Intercloud Fabric And Hybrid Cloud Firewall. The Cisco Intercloud Fabric Hybrid Cloud Router is the Cisco CSR1000V and the Intercloud Fabric Firewall is the Cisco Virtual Services Gateway. In the Cisco Intercloud Fabric documentation you will see the acronyms CSR and VSG respectively. As the documentation and messaging for Intercloud Fabric evolves there will be standardization on the ICF router and ICF firewall acronyms. ICF router-2, 1 for management interface, 1 for sub-management interface, ICF firewall-1, Minimal management IP address requirement for AWS deployment is 8, and Minimal management IP address requirement for Azure deployment is 5.
Cisco Intercloud Fabric Hybrid Cloud