EMC Enterprise Hybrid Cloud 2.5, Federation Software-Defined Data Center Edition

Transcription

1 Solution Guide EMC Enterprise Hybrid Cloud 2.5, Federation Software-Defined Data Center Edition Public Cloud Solution Guide EMC Solutions Abstract This Solution Guide describes the hybrid nature of the EMC Enterprise Hybrid Cloud solution, which enables IT organizations to deploy an on-premises hybrid cloud while also deploying and migrating resources into public clouds. It introduces the solution s main features and functionality, including the integration with public cloud providers. February 2015

2 Copyright 2015 EMC Corporation. All rights reserved. Published in the USA. Published February 2015 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC 2, EMC, Avamar, Data Domain, RecoverPoint, Syncplicity, ViPR, VMAX, VNX, VPLEX, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. EMC Enterprise Hybrid Cloud 2.5, Federation Software-Defined Data Center Edition Public Cloud Solution Guide Part Number H

3 Contents Contents Chapter 1 Executive Summary 7 Document purpose... 8 Audience... 9 Solution purpose Business challenge Technology solution Chapter 2 EMC Enterprise Hybrid Cloud Solution Overview 13 Introduction EMC Enterprise Hybrid Cloud features and functionality Automation and self-service provisioning Multitenancy and secure separation Workload-optimized storage Elasticity and service assurance Hybrid workloads Operational monitoring and management Metering and chargeback Modular add-on components Chapter 3 Hybrid Cloud Services 21 Overview EMC Enterprise Hybrid Cloud IaaS VMware vcloud Connector VMware vcloud Air Hybrid Cloud services Use case 1: Automated provisioning of public cloud resources Use case 2: Workload migration between private and public clouds Chapter 4 Hybrid Cloud Monitoring 53 Overview Integrated and intelligent Hybrid Cloud monitoring Monitoring across cloud environments vcenter Operations Management Pack for VMware vcloud Air

4 Contents Chapter 5 Conclusion 59 Conclusion Appendix A References 61 References EMC documentation VMware documentation

5 Contents Figures Figure 1. EMC Enterprise Hybrid Cloud key components Figure 2. EMC Enterprise Hybrid Cloud self-service portal Figure 3. EMC ViPR analytics with VMware vcenter Operations Manager Figure 4. IT Business Management Suite overview dashboard for hybrid cloud.. 18 Figure 5. Self-service portal and service catalog overview Figure 6. vcloud Air features Figure 7. vcloud Air Service Catalog Figure 8. vcloud Director API URL Figure 9. Organization or VDC name Figure 10. vcloud Air (vapp vcloud Director) endpoint creation Figure 11. Endpoint Data Collection Figure 12. Edit Fabric Group Figure 13. Reservation information Figure 14. Reservation resources Figure 15. Create New Blueprint Blueprint Information Figure 16. Create New Blueprint Build Information Figure 17. Create New Blueprint Properties Figure 18. Create New Blueprint Actions Figure 19. vapp blueprint creation Build Information Figure 20. vapp blueprint creation Blueprint Information Figure 21. vcloud Connector integration Figure 22. vcloud Connector data flow Figure 23. Workload migration scenarios Figure 24. Deploy vcloud Connector OVF Figure 25. Deploy vcloud Connector Node OVF final summary Figure 26. Deploy vcloud Connector Server OVF Figure 27. Deploy vcloud Connector Server OVF summary Figure 28. vcloud Connector Node/Server Power On Figure 29. Configure vsphere Client registration Figure 30. Register vcloud Air with Node Figure 31. vcloud Air registration Figure 32. EMC Enterprise Hybrid Cloud vsphere Node registration Figure 33. vcloud Air and EMC Enterprise Hybrid Cloud registered Figure 34. Configure vsphere vcloud Connector plugin Figure 35. EMC Enterprise Hybrid Cloud endpoint configuration in vsphere Figure 36. vcloud Connector cloud communication

6 Contents Figure 37. vcloud Connector EMC Enterprise Hybrid Cloud to vcloud Air copy Figure 38. vcloud Air copy verification Figure 39. vcloud Air copy complete Figure 40. vcenter Operations Manager dashboard high-level overview Figure 41. Monitoring across cloud environments Figure 42. vcloud Air Utilization and Performance dashboards Figure 43. Resource topology and resource VM metrics, health, and anomalies Figure 44. Virtual machine resource load heat maps

7 Chapter 1: Executive Summary Chapter 1 Executive Summary This chapter presents the following topics: Document purpose... 8 Audience... 9 Solution purpose Business challenge Technology solution

8 Chapter 1: Executive Summary Document purpose The EMC Federation of companies, EMC, VMware, Pivotal, and RSA, work together to research, develop, and validate leading-edge solutions to deliver superior, integrated solution stacks. This document describes the hybrid nature of the EMC Enterprise Hybrid Cloud solution, which enables IT organizations to quickly deploy an on-premises hybrid cloud with the capability to distribute resources into EMC Powered public cloud service providers, including VMware vcloud Air. The document introduces the main features and functionality of the solution, its architecture and key components, and the validated hardware and software environment. It demonstrates the integration of VMware vcloud Connector with the EMC Enterprise Hybrid Cloud solution for running off-premises workloads. The Public Cloud Solution Guide is a modular add-on to the EMC Enterprise Hybrid Cloud solution and details how EMC Powered public clouds can be integrated into the solution. The EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Reference Architecture and EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide documents describe the reference architecture and the foundation solution upon which all the EMC Enterprise Hybrid Cloud add-on solutions build. Further reading The following documents provide further information about how to implement specific capabilities or enable specific use cases within the EMC Enterprise Hybrid Cloud solution with VMware: EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Data Protection Continuous Availability Solution Guide EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Data Protection Disaster Recovery Solution Guide EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Data Protection Backup Solution Guide EMC Enterprise Hybrid Cloud 2.5, Federation Software-Defined Data Center Edition: Security Management Solution Guide EMC Enterprise Hybrid Cloud 2.5, Federation Software-Defined Data Center Edition: Pivotal CF Platform as a Service Solution Guide EMC Enterprise Hybrid Cloud 2.5, Federation Software-Defined Data Center Edition: Hadoop Applications Solution Guide 8

9 Chapter 1: Executive Summary Audience This document is intended for executives, managers, architects, cloud administrators, and technical administrators of IT environments who want to build a hybrid cloud infrastructure-as-a-service (IaaS) platform with both on- and offpremises capability. Readers should be familiar with VMware vcloud Suite, EMC ViPR, general IaaS-defined datacenter concepts, and how a hybrid cloud infrastructure accommodates these technologies and requirements. 9

10 Chapter 1: Executive Summary Solution purpose Business challenge The EMC Enterprise Hybrid Cloud solution enables EMC customers to build an enterprise-class, scalable, multitenant infrastructure that enables: Complete management of the infrastructure and application service lifecycle On-demand access to and control of network bandwidth, servers, storage, and security Quick deployment of IaaS components to support application provisioning onor off-premises to public clouds, without IT administrator involvement Scalable, flexible IaaS-based services for maximum asset utilization Access to application services from a single platform for both business-critical and next-generation cloud applications This solution provides the reference architecture and the best practice guidance necessary to integrate the key components and functionality of enterprise IaaS into an underlying EMC Enterprise Hybrid Cloud infrastructure. While many organizations have successfully introduced virtualization as a core technology within their data center, the benefits of virtualization have largely been restricted to the IT infrastructure owners. End users and business units within customer organizations have not experienced many of these benefits, such as increased agility, mobility, and control. Transforming from the traditional IT model to an IaaS model involves overcoming the challenges of legacy infrastructure and processes, such as: Inefficiency and inflexibility Slow, reactive responses to customer requests Inadequate visibility of the requested infrastructure cost Limited choice of availability and protection services The difficulty in overcoming these challenges has given rise to public cloud providers who have built technology and business models specifically catering to the requirements of end-user agility and control. Many organizations are under pressure to provide these same service levels within the secure and compliant confines of the on-premises data center. As a result, IT departments need to create cost-effective alternatives to public cloud services, alternatives that do not compromise enterprise features such as data protection, disaster recovery (DR), and guaranteed service levels. 10

11 Chapter 1: Executive Summary Technology solution This EMC Enterprise Hybrid Cloud solution integrates the best of EMC and VMware products and services, and empowers IT organizations to adopt an as-a-service implementation model of compute and storage infrastructure within the data center. Agile, elastic, on-demand, end-to-end IaaS provisioning is crucial to support a comprehensive, dynamic, and fast-growing Hybrid Cloud environment, using private and public resources. The key solution components include: EMC ViPR software-defined storage platform VMware vcloud Suite cloud management and infrastructure EMC and VMware integrated workflows VMware NSX virtual networking technologies VMware vsphere virtualization platform VMware vcloud Connector EMC Powered public cloud, such as vcloud Air 11

12 12 Chapter 1: Executive Summary

13 Chapter 2: EMC Enterprise Hybrid Cloud Solution Overview Chapter 2 EMC Enterprise Hybrid Cloud Solution Overview This chapter presents the following topics: Introduction EMC Enterprise Hybrid Cloud features and functionality

14 Chapter 2: EMC Enterprise Hybrid Cloud Solution Overview Introduction The EMC Enterprise Hybrid Cloud solution enables a well-run hybrid cloud by bringing new functionality not only to IT organizations, but also to developers, end users, and line-of-business owners. Beyond delivering baseline infrastructure as a service (IaaS), built on a software-defined data center (SDDC) architecture, the solution delivers feature-rich capabilities to expand from IaaS to business-enabling IT as a service (ITaaS). Backup as a service (BaaS) and disaster recovery as a service (DRaaS) are now features that users can enable with just a few mouse clicks. End users and developers can quickly access a marketplace of resources for Microsoft, Oracle, SAP, EMC Syncplicity, and Pivotal applications, and can add thirdparty packages as required. All of these applications and resources can be deployed on private cloud or public cloud services (including VMware vcloud Air) from EMC Powered cloud service providers. The EMC Enterprise Hybrid Cloud solution uses the best of EMC and VMware products and services. It takes advantage of the integration between EMC and VMware technologies to provide a strong foundation for enabling IaaS on new and existing infrastructure for the hybrid cloud. Figure 1 shows the key components of the EMC Enterprise Hybrid Cloud solution. For detailed information, refer to EMC Enterprise Hybrid Cloud 2.5.1, Federation Software- Defined Data Center Edition: Foundation Infrastructure Solution Guide. For information on EMC Enterprise Hybrid Cloud modular add-on solutions, which provide functionality such as data protection, continuous availability, and application services, refer to Modular add-on components and to the individual Solution Guides for those add-ons. Figure 1. EMC Enterprise Hybrid Cloud key components 14

15 Chapter 2: EMC Enterprise Hybrid Cloud Solution Overview EMC Enterprise Hybrid Cloud features and functionality The EMC Enterprise Hybrid Cloud solution incorporates the following features and functionality: Automation and self-service provisioning Multitenancy and secure separation Workload-optimized storage Elasticity and service assurance Operational monitoring and management Metering and chargeback Modular add-on components Automation and self-service provisioning The solution provides self-service provisioning of automated cloud services to both users and infrastructure administrators. It uses VMware vcloud Automation Center, integrated with EMC ViPR software-defined storage and VMware NSX, to provide the compute, storage, network, and security virtualization platforms for the SDDC. Cloud users can request and manage their own applications and compute resources within established operational policies. This can reduce IT service delivery times from days or weeks to minutes. Automation and self-service provisioning features include: Self-service portal Provides a cross-cloud storefront that delivers a catalog of custom-defined services for provisioning workloads based on business and IT policies, as shown in Figure 2 Role-based entitlements Ensure that the self-service portal presents only the virtual machine, application, or service blueprints that are appropriate to a user s business role Resource reservations Allocate resources for use by a specific group and ensure that those resources are inaccessible to other groups Service levels Define the amount and types of resources that a particular service receives during initial provisioning or as part of configuration changes Blueprints Contain the build specifications and automation policies that define the process for building or reconfiguring compute resources 15

16 Chapter 2: EMC Enterprise Hybrid Cloud Solution Overview Figure 2. EMC Enterprise Hybrid Cloud self-service portal Multitenancy and secure separation The solution allows the administrator to enforce physical and virtual separation for multitenancy, as strongly as necessary. This separation can encompass network, compute, and storage resources to ensure appropriate security and performance for each tenant. The solution supports secure multitenancy through vcac role-based access control (RBAC), which allows vcac roles to be mapped to Microsoft Active Directory groups. The self-service portal shows only the views, functions, and operations that are appropriate to cloud users, based on their business roles. Workloadoptimized storage Elasticity and service assurance Hybrid workloads The solution lets customers take advantage of the proven benefits of EMC storage in a hybrid cloud environment. Using ViPR storage services, which leverage the capabilities of EMC VNX and EMC VMAX storage systems, the solution provides software-defined, policy-based management of block- and file-based virtual storage. ViPR abstracts the storage configuration and presents it as a single storage control point, enabling cloud administrators to access all heterogeneous storage resources within a data center as if the resources were a single large array. The solution uses vcac and various EMC tools to provide the intelligence and visibility required to ensure service levels in virtual and cloud environments. Infrastructure administrators can add storage, compute, and network resources to their resource pools as needed. Cloud users can select from a range of service levels for compute, storage, and data protection for their applications and can expand the resources of their virtual machines on-demand to achieve the service levels they expect for their application workloads. The EMC Enterprise Hybrid Cloud solution uses the cloud portal self-service catalog to select cloud services. These cloud services run on- or off-premises from within the 16

17 Chapter 2: EMC Enterprise Hybrid Cloud Solution Overview same on-premises self-service portal. Using VMware vcloud Connector it is also possible to migrate workloads to EMC Powered public clouds, including vcloud Air. Operational monitoring and management The solution features automated monitoring and management capabilities that provide IT administrators with a comprehensive view of the cloud environment, enabling smart decision-making for resource provisioning and allocation. These automated capabilities are based on a combination of EMC ViPR Storage Resource Management (SRM), VMware vcenter Log Insight, and VMware vcenter Operations Manager (vc Ops). EMC plugins for ViPR, VNX, VMAX, and EMC Avamar systems are used to provide extensive additional storage details. Cloud administrators can use ViPR SRM to understand and manage the impact that storage has on their applications and to view their storage topologies from application to disk, as shown in Figure 3. Figure 3. EMC ViPR analytics with VMware vcenter Operations Manager Administrators can use capacity analytics and what-if scenarios in vc Ops to identify over-provisioned resources so that they can be right-sized for the most efficient use of virtualized resources. vc Ops also uses management packs to provide additional operational visibility of vcloud Air. For centralized logging, infrastructure components can be configured to forward their logs to vcenter Log Insight, which then aggregates the logs from all sources for analytics and reporting. Metering and chargeback The solution uses VMware IT Business Management Suite (ITBM) to provide cloud administrators with comprehensive metering and cost information across all business groups in the enterprise. ITBM is integrated into the cloud administrator s self-service portal, and presents a dashboard overview of the hybrid cloud infrastructure, as shown in Figure 4. 17

18 Chapter 2: EMC Enterprise Hybrid Cloud Solution Overview Figure 4. IT Business Management Suite overview dashboard for hybrid cloud Modular add-on components The EMC Enterprise Hybrid Cloud solution provides modular add-on components for the following services: Application services This add-on solution uses VMware vcloud Application Director to optimize application deployment and release management through logical application blueprints in vcac. Users can quickly and easily deploy blueprints for applications and databases such as Microsoft Exchange, Microsoft SQL Server, Microsoft SharePoint, Oracle, and SAP. Data protection services EMC Avamar and EMC Data Domain systems provide a backup infrastructure that offers deduplication, compression, and VMware integration. By using VMware vcenter Orchestrator (vco) workflows customized by EMC, administrators can quickly set up multitier data protection policies and enable users to select appropriate policies when they provision their virtual machines. Continuous availability A combination of EMC VPLEX virtual storage and VMware vsphere High Availability (HA) provides the ability to distribute information across multiple data centers over synchronous distances. With virtual storage and virtual servers working together over distance, the infrastructure can transparently provide load balancing, real-time remote data access, and improved application protection. 18

19 Disaster recovery Chapter 2: EMC Enterprise Hybrid Cloud Solution Overview This add-on solution enables cloud administrators to select disaster recovery (DR) protection for their applications and virtual machines when they provision their hybrid cloud environment. ViPR automatically places these systems on storage that is protected remotely by EMC RecoverPoint technology. VMware vcenter Site Recovery Manager automates the recovery of all virtual storage and virtual machines. Platform as a service The EMC Enterprise Hybrid Cloud solution provides an elastic and scalable IaaS foundation for platform as a service (PaaS) and software as a service (SaaS). Pivotal CF provides a highly available platform that enables application owners to easily deliver and manage applications over the application lifecycle. The EMC Enterprise Hybrid Cloud service offerings enable PaaS administrators to provision compute and storage resources on demand to support scalability and growth in their Pivotal CF enterprise environments. Hadoop applications The EMC Enterprise Hybrid Cloud solution provides an elastic and scalable IaaS foundation for Hadoop-based Big Data services. VMware Big Data Extensions and Pivotal Hadoop provide a highly available platform that enables Big Data owners to easily deliver and manage Hadoop clusters. The EMC Enterprise Hybrid Cloud service offerings enable Hadoop Big Data administrators to provision compute and storage resources on demand to support scalability and growth in their VMware Big Data/Pivotal Hadoop environments. 19

20 20 Chapter 2: EMC Enterprise Hybrid Cloud Solution Overview

21 Chapter 3 Hybrid Cloud Services This chapter presents the following topics: Overview EMC Enterprise Hybrid Cloud IaaS VMware vcloud Connector VMware vcloud Air Hybrid Cloud services

22 Overview This chapter identifies and briefly describes the major features and functionality required to support EMC Enterprise Hybrid Cloud with off-premises EMC Powered public clouds. The use cases discussed demonstrate how to run off-premises Hybrid Cloud services from within your on-premises Cloud Service Catalog, and how to migrate Hybrid Cloud services off-premises using an EMC Powered public cloud. EMC Enterprise Hybrid Cloud IaaS The EMC Enterprise Hybrid Cloud IaaS is a solution stack comprised of EMC and VMware components that provide an on-premises private cloud from which services can be consumed from a self-service catalog. The main catalog services provided by VMware vcloud Automation Center also allow services to be selected and consumed from off-premises public clouds. VMware vcac provides a unified self-service portal for delivering infrastructure, applications, data, or Anything as a Service (XaaS). The self-service portal streamlines the ability of cloud users to request services and access to virtual machines both on and off premises. The process is transparent to the cloud user, but securely controlled by the business. Through the self-service portal, vcac provides a highly flexible means for customizing machine configurations while integrating the machine provisioning and management with other enterprise-critical systems. The self-service portal in this hybrid cloud solution presents users with a service catalog of customized and approved services and applications, as summarized in Figure 5. These catalog items are the result of pre-engineered storage and infrastructure services that have been customized to meet the many needs of the business. All service specifications and policies can be preconfigured and approved by higher-level cloud administrators, allowing end users of the cloud to provision, manage, and dispose of their own systems. 22

23 Figure 5. Self-service portal and service catalog overview VMware vcloud Connector VMware vcloud Air VMware vcloud Connector links your internal private cloud with public clouds, so you can manage them as a single hybrid environment and transfer workloads back and forth. VMware provides vcloud Connector as a free application to transfer workloads between connected clouds and to provide a unified view for managing workloads, vapps, and templates across internal data centers, and private and public clouds. The vcloud Connector user interface provides the common portal for cloud administrators to control bi-directional workload migration to EMC Powered clouds, including VMware vcloud Air. VMware vcloud Air is a secure, hybrid cloud service operated by VMware, built on a foundation of vsphere and EMC Powered technologies. The service supports existing workloads and third-party applications as well as new application development, giving IT a common platform to seamlessly extend their data center into the public cloud and remain in control. vcloud Air is available in three infrastructure-as-a-service (IaaS) subscription service types Dedicated Cloud, Virtual Private Cloud, and Disaster Recovery. 23

24 The key benefits of vcloud Air are: Comprehensive suite of vsphere management tools vcloud Air utilizes the same vcloud Suite platform tools such as VMware vsphere, VMware vcloud Automation Center, and vcenter Operations Management Suite. Broad operating system and application support vcloud Air supports thousands of applications and dozens of operating systems that are certified to run vsphere, and can be run in the public cloud without any changes. Reliability and management Applications can be written, deployed, and managed in the public cloud in the same way that they are deployed today on private clouds (such as EMC Enterprise Hybrid Cloud) by utilizing the same vsphere-based platform. Figure 6 summarizes the benefits of vcloud Air. Figure 6. vcloud Air features Hybrid Cloud services The following use cases demonstrate the hybrid nature of the EMC Enterprise Hybrid Cloud solution, and show how an end user can create workloads in a public cloud using the same self-service catalog as within the on-premises private cloud, or migrate a workload off premises into a public cloud. Use case 1: Automated provisioning of public cloud resources The EMC Enterprise Hybrid Cloud can take advantage of vcloud Automation Center s underlying features to present a self-service portal that contains catalog items that are both on and off premises. This use case documents how to create a catalog item with a workload deployed into vcloud Air. 24

25 vcloud Air is a subscription-based service offered by VMware to enable cloud administrators to deploy catalog items off premises for various business reasons such as flexibility and cost. The cloud user selects a vcloud Air-hosted item from the catalog portal in exactly the same way as they select an on-premises item. Figure 7 shows the services that reside both in the EMC Enterprise Hybrid Cloud and off premises on vcloud Air and an EMC Powered cloud provider. Figure 7. vcloud Air Service Catalog A vcloud Air catalog item that is called from the Service Catalog is simply a blueprint or virtual machine that has a different endpoint. An endpoint contains the fundamental object resources that are consumed by a tenant user when provisioning catalog items, either on or off premises. In the case of on-premises workloads, these are inherited from vsphere ESXi hosts in the EMC Enterprise Hybrid Cloud. With offpremises workloads, these are vapp/vcloud Director resources that form part of the vcloud Air subscription or a similar EMC Powered cloud based upon vcloud Director. Endpoints are discussed in more detail in the EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide, Chapter 3 - Solution Architecture and Design. Configuring a vcloud Air endpoint The steps described below provide general guidance on creating a vcloud Air endpoint. Note: The main documentation resource for vcloud Automation Center is located at The vcac Installation and Configuration document provides a great amount of detail on configuring endpoints and blueprints. 1. Ensure that you have the following vcloud Air subscription details and information: 25

26 a. The vcloud Air username and password used to log in to the vcloud Air dashboard, where you see resource snapshots and virtual data centers. These are also called the vcloud Air account credentials, and are entered once in vcac under the Credentials option when creating an endpoint. The same credentials can be used to define multiple vcloud Air endpoints. These details, including the vcloud Air dashboard URL, are supplied to you by VMware as part of the vcloud Air subscription purchase. b. vcloud Direct API URL this is obtained from the specific Virtual Data Center that is shown on the main dashboard under the Virtual Data Centers tab at the bottom of the screen. Click the Virtual Data Center that is to serve as this endpoint if more than one exists. On the right-hand side of the Virtual Data details page (shown in Figure 8), click vcloud Director API URL, then copy the URL to a text file. Figure 8. vcloud Director API URL c. The Virtual Data Center name is obtained from the same screen as the vcloud Director API URL by clicking Edit VDC Name & Description, as shown in Figure 9. It is best to copy this name, as it is case sensitive. 26

27 Figure 9. Organization or VDC name 2. From the vcloud Automation Center administration console, select Infrastructure > Endpoints-Create New Endpoint, then select vapp (vcloud Director). As shown in Figure 10 you populate it with the information collected previously from your vcloud Air account subscription. Click OK when complete. Figure 10. vcloud Air (vapp vcloud Director) endpoint creation This saves your new vcloud Air endpoint to the list of endpoints and starts the initial endpoint discovery process. At this point, the process will discover only the Virtual Data Center so it should only take a few seconds. To gather everything available within the endpoint, you should perform a Data Collection. 3. To run a Data Collection from the list of endpoints as shown in Figure 11, click Data Collection. In the window that opens, click Start. You are then returned to the list of endpoints while the discovery process runs in the background. 27

28 Note: You can view the data status by returning to the Data Collection option for that endpoint and clicking Refresh. When it is finished, you see the status Endpoint Data collection successful. Click Cancel to return to the endpoint list. Figure 11. Endpoint Data Collection 4. With the endpoint created and the Data Collection completed, you must place the resources under vcloud Automation Center control. To do this, the resources must be assigned to an existing fabric group. Navigate to Infrastructure > Groups > Fabric Groups. You can now apply the vcloud Air endpoint to one or more fabric groups. 5. Select the required fabric group and click Edit. As shown in Figure 12, add the vcloud Air virtual data center resources to the selected fabric group by selecting the Compute resources check box associated with vcloud Air. Click OK and you return to the list of fabric groups, where you see the resource has been assigned to the selected group. Figure 12. Edit Fabric Group 6. Assign a portion of the resources to an existing business group. Navigate to Infrastructure > Resources > Reservations. Click New Reservation vapp (vcloud Director). Fill in the reservation information as shown in Figure 13 by selecting the required options and populating the fields. 28

29 Figure 13. Reservation information 7. Click the Reservation tab. Figure 14 shows the storage profiles selected for this reservation policy. Figure 14. Reservation resources 8. Finish by selecting the network path and optionally a network profile. You can find more information on reservation profiles in the VMware vcloud Automation Center User Guide or the EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide. 29

30 Configuring vcloud Air-enabled blueprints The final stage is to create a blueprint that can use the configuration defined in the previous stages to provision to vcloud Air. In this example, we first create the vapp component blueprint that the vapp will be based upon. 1. From the Infrastructure tab, navigate to Blueprints > Blueprints and select Create New Blueprint, then Cloud > vapp Component (vcloud Director). The first step is to name the blueprint component to be used in the blueprint app template as shown in Figure 15. Figure 15. Create New Blueprint Blueprint Information 2. Define the blueprint type and action and then, in the Clone from field, select the vapp Component template from which the clone will be made. This is a template taken from the vcloud endpoint and can be a published public VCD host template available as part of the vcloud Air service. Remember to set the machine resources that this cloned machine will consume examples are shown in Figure

31 Figure 16. Create New Blueprint Build Information 3. Figure 17 and Figure 18 show additional property options that are not required in this example. Review the four tabs and, when satisfied that all relevant options are correct, click OK to save the template. Figure 17. Create New Blueprint Properties 31

32 Figure 18. Create New Blueprint Actions 4. Create the vapp blueprint that uses the vapp component template created previously to deploy the example vapp. From within the same Blueprint section, under Infrastructure create another blueprint but this time use Cloud > vapp (vcloud Director). 5. Select the Build Information tab. Populate the vapp template with the Clone from information. This is the name of the vapp template you are cloning from, which you have already created in vcloud Air as part of your subscription process. This step is shown in Figure 19. Figure 19. vapp blueprint creation Build Information This is paired with the name of the previous vapp Component template you created in the previous step. This vapp template is then deployed to vcloud Air as the endpoint. 32

33 6. The final stage, shown in Figure 20, is to populate the remaining values and name the blueprint. When all the required information is entered, you can publish this information to the Service Catalog so that users can provision this vapp into the vcloud Air public cloud. Figure 20. vapp blueprint creation Blueprint Information For more information, refer to Appendix A which contains links to the VMware documentation for the vcloud Air User Guide and vcloud Automation Center Installation and Configuration document, and IaaS configuration for virtual and cloud platforms. Additional information on using blueprints in the service catalog is available in the EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide. Use case 2: Workload migration between private and public clouds The EMC Enterprise Hybrid Cloud solution uses the vcloud Connector application to move content (including applications, workloads and templates) between private, public, and hybrid clouds. vcloud Connector supports this movement of content between private clouds, including EMC Enterprise Hybrid Cloud, and public or hybrid clouds such as vcloud Air or from EMC Powered service providers. This allows bi-directional movement to public clouds or back into a private cloud. vcloud Connector features: Built-in content compression to improve transfer times Path-optimized multipart transfer to improve data transfer efficiency Checkpoint restarts to simplify transfer between collected clouds vsphere-based unified management interface When used as part of the EMC Enterprise Hybrid Cloud, the vcloud Connector user interface is part of the vsphere user interface and is installed as a vsphere Client 33

34 plugin. Workload movements must therefore be performed by the cloud administrator. The vsphere Client plugin allows the cloud administrator to perform the following functions: Visualize workloads and templates across vsphere and private/public vclouds Migrate workloads and templates between vsphere & vclouds EMC Enterprise Hybrid Cloud (vsphere) vcloud Air (vcloud Director) EMC Enterprise Hybrid Cloud (vsphere) EMC Enterprise Hybrid Cloud (vsphere) vcloud Air (vcloud Director) vcloud Air (vcloud Director) Perform basic power and deployment operations on workloads and templates Access vapp console (VMRC) in vclouds Launch vcloud Director or vcloud Datacenter Service Web UI directly Figure 21 shows the replication of EMC Enterprise Hybrid Cloud private templates into the vcloud Air vapp repository, and the templates into the template catalog. Typical use cases for vcloud Connector-based migrations include: Migrating workloads from vsphere to public vclouds to free up resources Migrating workloads from public vclouds back to EMC Enterprise Hybrid Cloud in the datacenter Migrating workloads between EMC Enterprise Hybrid Clouds Populating private vcloud Director environment with VMs from vsphere Migrate workloads between vclouds (such as vcloud Air or EMC Powered clouds) 34

35 Figure 21. vcloud Connector integration The vcloud Connector copy operation operates as follows: The source Virtual Machine/vApp/template from vsphere/vcloud is exported as an OVF file. It is temporarily stored in vcloud Connector virtual appliance s attached storage /opt/vmware/vccp/staging, with an initial configuration of up to 40 GB. vcloud Connector is considered a hop between the source and target clouds, and can be used in either of two ways: HTTP is used to copy over to the target vsphere or vcloud The OVF is imported directly into vsphere or vcloud If the target is a vcloud, the OVF is stored temporarily in the Transfer Server Storage before it is imported into vcloud. vcloud Connector architecture The following section describes the architecture for data flow within vcloud Connector, which is a single application comprised of the individual components shown in Figure

36 Figure 22. vcloud Connector data flow vcloud Connector server The vcloud Connector server is a virtual appliance that coordinates the activities of vcloud Connector. It controls vcloud Connector nodes and implements the vcloud Connector UI. A vcloud Connector Server is required in a single instance of the EMC Enterprise Hybrid Cloud. vcloud Connector UI The vcloud Connector UI is the user interface created by the vcloud Connector Server. It is registered to and accessed from the main vsphere Client in the EMC Enterprise Hybrid Cloud. The UI registration process is performed during the installation and configuration process covered later in this section. vcloud Connector nodes vcloud Connector nodes are virtual appliances that transfer content from one cloud to another. A vcloud Connector node must be installed in every vsphere or vcloud Director-based cloud that vcloud Connector oversees. In the EMC Enterprise Hybrid Cloud, this would be for every vsphere tenant instance, and is provided as part of vcloud Air and any EMC Powered cloud. On public EMC Powered vcloud Director-based clouds, the service provider installs a vcloud Connector node as a multitenant node for each customer to use. This configuration can also be used by private vcloud Director administrators who control multiple organizations. In vcloud Air, VMware installs a vcloud Connector multitenant node by default as part of the service. 36

37 Figure 23 shows three workload migration scenarios: EMC Enterprise Hybrid Cloud (on-premises) to vcloud Air (off-premises) EMC Enterprise Hybrid Cloud to EMC Enterprise Hybrid Cloud EMC Enterprise Hybrid Cloud to vcloud Air Figure 23. Workload migration scenarios Deploying the vcloud Connector Node OVF The following steps cover deploying the vcloud Connector Node OVF at a high level. For more detail, refer to the links in Appendix A for vcloud Connector documentation. 1. From the vsphere Client, select File > Deploy OVF Template. 2. Enter the location of the vcloud Connector Node OVF package. In this use case the current shipping version of vcloud Connector (2.6.0) was used. The location can be a CD/DVD ROM drive, file, or Internet URL. 3. Figure 24 shows the OVF details, when it has been located and verified as a valid package. 37

38 Figure 24. Deploy vcloud Connector OVF 4. Accept the license agreement, name the vcloud Connector, and specify the vsphere instance in which it is to be deployed. The remaining steps require you to specify the following: the configuration of host or cluster the appropriate resource pool with the node the destination storage for the virtual machine files the storage provisioning (thick or thin) the source and destination networks As part of the network configuration process you must provide the default gateway for the subnet, DNS servers and an IP address for the transit network, complete with netmask. Figure 25 shows the final configuration summary. 38

39 Figure 25. Deploy vcloud Connector Node OVF final summary 5. Click Finish to start the installation process. Deploying vcloud Connector Server The following steps cover deploying the vcloud Connector Server OVF at a high level. For more detailed information, refer to the links in Appendix A for vcloud Connector documentation. 1. From the vsphere Client, select File > Deploy OVF Template. 2. Enter the location of the vcloud Connector Server OVF package. In this use case, the current shipping version of vcloud Connector (version 2.6.0) was used. The location can be a CD/DVD ROM drive, file, or Internet URL. 3. Figure 26 shows the details for the OVF, when it has been located and verified as a valid package. 39

40 Figure 26. Deploy vcloud Connector Server OVF 4. Click Next to accept the license agreement, then name the vcloud Connector and specify the vsphere instance in which it is to be deployed. The remaining steps specify the following: the configuration of host or cluster the appropriate resource pool with the node the destination storage for the virtual machine files the storage provisioning (thick or thin) the source and destination networks As part of the network configuration process you must provide the default gateway for the subnet, DNS servers and an IP address for the transit network, complete with netmask. Figure 27 shows the final configuration summary. 40

41 Figure 27. Deploy vcloud Connector Server OVF summary 5. Click Finish to start the installation process. 6. The final stage is to power on both the vcloud Connector Node and Server virtual machines from within vsphere as shown in Figure 28. Figure 28. vcloud Connector Node/Server Power On 41

42 vcloud Connector Node Configuration The following steps cover configuring the vcloud Connector Node virtual machine at a high level. For more detailed information, refer to the links in Appendix A for vcloud Connector documentation. 1. Add DNS A records to the DNS servers used by the EMC Enterprise Hybrid Cloud vsphere virtual machines. In this example, we add two records that correspond to the vcloud Connector Node and vcloud Connector Server: ppblu-vccnode01.ppblue.emc.lab.local (Node) ppblu-vccsvr01.ppblue.emc.lab.local (Server) 2. To configure the vcloud Connector Node, use a web browser using HTTPS to open the fully qualified domain name (FQDN) of the vcloud Connector Node using port In the previous example, this would be The default credentials are admin (username) and vmware (password). 3. Once logged in, you are prompted to specify the correct time zone for your EMC Enterprise Hybrid Cloud. Depending on the network topology of how the EMC Enterprise Hybrid Cloud environment accesses the Internet, HTPP proxy server settings may be required, so enter these on the next page. You must use the IP address of the proxy server here, as the FQDN will give an error. 4. Specify the Cloud registration details. For EMC Enterprise Hybrid Cloud the type is vsphere and the Cloud URL is the IP address of the vsphere server. You should select Ignore SSL Cert and Use Proxy if proxy settings were entered. 5. Click Update and log out of the website. vcloud Connector Server Configuration The following steps cover configuring the vcloud Connector Server virtual machine at a high level. For more detailed information, refer to the links in Appendix A for vcloud Connector documentation. 1. To configure the vcloud Connector Server, use a web browser using HTTPS to open the fully qualified domain name of the vcloud Connector Node using port In our example using the FQDN from the node example above this would be The default credentials are admin (username) and vmware (password). 2. Once logged in you will be prompted to specify the correct time zone for your EMC Enterprise Hybrid Cloud. Depending on the network topology of how the EMC Enterprise Hybrid Cloud environment access the internet then HTPP Proxy Server settings may be required, enter these on the next page. You must use the IP address of the proxy server here, as the FQDN will give an error. 42

43 3. Configure the vsphere Client Plugin by selecting the Server tab and then vsphere Client Tab, using our examples shown in the installation of the vcloud Connector installation sections above use the following information: vcloud Connector Server URL: Keep default vcenter Server IP/FQDN: ppblu-vc02.ppblue.emc.lab.local (this reference information is shown in Figure 27) vcenter username: PPBLUE\Administrator vcenter password: Remove Overwrite existing registration: Checked Use Proxy: Unchecked Figure 29 shows the vsphere Client Registration screen using this information. Figure 29. Configure vsphere Client registration 4. Configure the server with the vcloud Air subscription details provided by VMware as part of the Cloud Administrator s subscription as shown in Figure

44 Figure 30. Register vcloud Air with Node 5. When you click Register you will see the registration information (if the registration is successful) as shown in Figure 31. Figure 31. vcloud Air registration 44

45 6. Register the node with the EMC Enterprise Hybrid Cloud vsphere details as shown in Figure 32. Figure 32. EMC Enterprise Hybrid Cloud vsphere Node registration Figure 33 shows both the vcloud Air and EMC Enterprise Hybrid Cloud endpoints registered successfully within the vcloud Connector Server. 45

46 Figure 33. vcloud Air and EMC Enterprise Hybrid Cloud registered Migrating a virtual machine from EMC Enterprise Hybrid Cloud to vcloud Air The next stage of the configuration process is to configure the vsphere Thick Client to use the vcloud Connector plugin. 1. The vcloud Connector plugin should appear on the main screen under Solutions and Applications from within the vsphere client. From within the vcloud Connector plugin, click the Clouds option, select Actions > Add, to add the vcloud Air endpoint. Use the same credentials used when configuring the vcc Server Node, the vcloud Air vcloud Director endpoint. Figure 34 shows the same credentials used in the vcloud Connector Server configuration for the vcloud Air account. 46

47 Figure 34. Configure vsphere vcloud Connector plugin 2. Repeat the process for the EMC Enterprise Hybrid Cloud endpoint, again using the same credentials as those used in the vcloud Connector Server configuration. Figure 35 shows the configuration details for the example EMC Enterprise Hybrid Cloud endpoint. 47

48 Figure 35. EMC Enterprise Hybrid Cloud endpoint configuration in vsphere 3. You can verify the command channel between EMC Enterprise Hybrid Cloud vcloud Connector Server to the EMC Enterprise Hybrid Cloud node and vcloud Air node by expanding the browser pane to show the Data Center for each of the newly added clouds, as shown in Figure

49 Figure 36. vcloud Connector cloud communication 4. You can validate the communication by performing a virtual machine copy of a local EMC Enterprise Hybrid Cloud template to vcloud Air. Select a template from within the templates folder on the EHC vsphere instance, as shown in Figure

50 Figure 37. vcloud Connector EMC Enterprise Hybrid Cloud to vcloud Air copy 5. During the copy process, you will be prompted to select features: a. Select the target cloud, in this example vcloud Air Demo Cloud. b. Name the target file. c. Select the catalog item to transfer. d. Select the specified VDC resource from the drop-down list. e. For the Deployment Options screen, click Next as none are required in this example. f. Verify the information you have entered on the final screen, as shown in Figure 38, and click Validate. The copy will then validate. 50

51 Figure 38. vcloud Air copy verification 6. Once validated, you should see the message Validation successful, you can proceed to copy. Once you see this message, click Finish. This then starts the copy process, which has three stages: a. Exporting the virtual machine template as an OVF file b. Transmitting the OVF from the EMC Enterprise Hybrid Cloud vcloud Connector node to the vcloud Air vcloud Connector node c. Importing the OVF as a virtual machine template on vcloud Air 7. After the copy process completes you can expand the destination cloud, in this example vcloud Air Demo Cloud > <VDC name> > EHC Demo, and verify that the newly copied template is in the folder. Note: This can take a few minutes while it is transferring the OVF and importing it into vcloud Air. Figure 39 shows the virtual machine template now present in the vcloud Air VDC template folder. 51

52 Figure 39. vcloud Air copy complete For information on copying other kinds of workloads, please refer to the vcloud Connector and vcloud Air documentation in Appendix A, which contains User Guides and configuration examples. 52

53 Chapter 4: Hybrid Cloud Monitoring Chapter 4 Hybrid Cloud Monitoring This chapter presents the following topic: Overview

54 Chapter 4: Hybrid Cloud Monitoring Overview Infrastructure maintenance and operations teams need the end-to-end visibility and intelligence to make fast, informed operational decisions to proactively guarantee service levels in cloud environments. They need to get promptly to the root cause of performance problems, optimize capacity in real time, and maintain compliance in a dynamic, constantly changing environment. This solution provides the ability to intelligently monitor and manage resources and systems in the hybrid cloud environment using EMC and VMware hybrid cloud environment integration and interoperability. Integrated and intelligent Hybrid Cloud monitoring The VMware vc Ops dashboard provides a comprehensive insight into the environment, as shown in Figure 40. The main dashboard is divided into three logical entities Health, Risk, and Efficiency. These provide high-level information about overall health of all managed resources, potential future issues and risks, and resource efficiency trends, respectively. Figure 40. vcenter Operations Manager dashboard high-level overview The three logical entities in vc Ops are: Health: Calculates health scores based on patented algorithms that dynamically calculate thresholds by observing behavior trends of the cloud environment and gives visibility into the red, yellow, and green status of the virtual machines, datastores, and clusters. You can see where the problems are, what the issues are, and if any trend of abnormal behavior exists in the environment. Risk: Provides insight into the resource consumption to tell you not only when you will run out of capacity but also which resources will run out. Efficiency: Proactively optimizes your environment and reclaims waste. 54

55 Chapter 4: Hybrid Cloud Monitoring Monitoring across cloud environments vcenter Operations Manager with Management Pack for VMware vcloud Air provides comprehensive operational visibility of both EMC Enterprise Hybrid Cloud and vcloud Air resources from a single vcenter Operations Manager console as shown in Figure 41. Figure 41. Monitoring across cloud environments The vcenter Operations Management Pack for VMware vcloud Air extends the capabilities of vcenter Operations Manager to vcloud Air, providing a consistent user experience across cloud environments. The embedded adapter collects metrics, change events, and resource topology details from your vcloud Air environment and displays this information in your on-premises vc Ops dashboard. Extended monitoring capabilities provide the availability to monitor, isolate, and resolve performance bottlenecks across your hybrid cloud environment by utilizing the existing vc Ops instance that you use in the EMC Enterprise Hybrid Cloud environment. vcenter Operations Management Pack for VMware vcloud Air The Management Pack collects metrics from vcloud Air cloud environments, datacenters and virtual machines hosted in the environment. Inventory, metering, and event data is imported into vc Ops and displayed with preconfigured dashboards that show the performance and utilization of consumed CPU, memory, network, and storage resources. The dashboards also present resource details, event alerts, troubleshooting information, and heatmaps. vcloud Air Utilization and Performance dashboards The vcloud Air Utilization and Performance dashboards shown in Figure 42 provide cloud administrators with detailed insight into resource consumption. 55

56 Chapter 4: Hybrid Cloud Monitoring Figure 42. vcloud Air Utilization and Performance dashboards The vcloud Air dashboards provide cloud administrators with highly granular insight into resource consumption at cloud- or data center-level where they can see: CPU reservation usage in MHZ Memory reservation usage in MB Provisioned storage space capacity in MB At virtual machine level, the Performance and Utilization tabs provide more detailed metrics: VM CPU usage VM memory usage Disk commands per second Packets received per second Packets transmitted per second SWAP in rate SWAP out rate vcloud Air troubleshooting The vcloud Air Troubleshooting dashboard provides visual and metric indicators that enable you to research performance and capacity problems across the hybrid cloud 56

57 Chapter 4: Hybrid Cloud Monitoring environment. Cloud resource information is provided hierarchically and cloud administrators can see the topology and relationships between various resources. The Troubleshooting dashboard provides an overview of the performance and condition of the cloud infrastructure and enables easy drill-down to the root cause of problems. When you click on a resource VM in the vcloud Air Relationship widget, the corresponding metrics and health information for that resource are displayed, as shown in Figure 43. Figure 43. Resource topology and resource VM metrics, health, and anomalies vcloud Air heat maps The vcloud Air heat maps dashboard, as shown in Figure 44, provides heat maps of the virtual machines in each cloud and data center, based on various usage metrics. The dashboard provides cloud administrators with an overview of CPU, RAM, disk, and network loads of virtual machines in the environment. When you click a virtual machine in the heat map, a corresponding metric history graph and details are displayed underneath. 57