EMC ViPR Plug-in for VMware vcenter Orchestrator

Transcription

1 EMC ViPR Plg-in for VMware vcenter Orchestrator Version Installation and Configration Gide

2 Copyright EMC Corporation. All rights reserved. Pblished in USA. Pblished Febrary, 2014 EMC believes the information in this pblication is accrate as of its pblication date. The information is sbject to change withot notice. The information in this pblication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this pblication, and specifically disclaims implied warranties of merchantability or fitness for a particlar prpose. Use, copying, and distribtion of any EMC software described in this pblication reqires an applicable software license. EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other contries. All other trademarks sed herein are the property of their respective owners. For the most p-to-date reglatory docment for yor prodct line, go to EMC Online Spport ( For docmentation on EMC Data Domain prodcts, go to the EMC Data Domain Spport Portal ( EMC Corporation Hopkinton, Massachsetts In North America EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide

3 CONTENTS Tables 5 Chapter 1 EMC ViPR Plg-in for vcenter Orchestrator Overview 7 EMC ViPR for vcenter Orchestrator...8 ViPR plg-in for vco workflows...8 Mlti-client integration...10 Chapter 2 EMC ViPR and vcenter Orchestrator Configration Reqirements 11 EMC ViPR configration reqirements...12 vcenter Orchestrator configration reqirements Chapter 3 EMC ViPR Plg-in Installation and Configration 15 Installing the EMC ViPR plg-in for vcenter Orchestrator Configring EMC ViPR and system settings Verifying the EMC ViPR plg-in installation Generating EMC ViPR workflow docmentation...17 Chapter 4 EMC ViPR Plg-in Integration with Additional VMware Applications 19 EMC ViPR workflow mlti-client integration...20 VMware vcenter Orchestrator REST API integration VMware vsphere, vcenter Server integration VMware vclod Atomation Center Workflow CPU and memory tilization EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide 3

4 CONTENTS 4 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide

5 TABLES Common workflows... 8 Bilding block workflows...9 Basic EMC ViPR workflow...21 Complex EMC ViPR workflow...22 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide 5

6 TABLES 6 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide

7 CHAPTER 1 EMC ViPR Plg-in for vcenter Orchestrator Overview This chapter contains the following topics: EMC ViPR for vcenter Orchestrator...8 Mlti-client integration EMC ViPR Plg-in for vcenter Orchestrator Overview 7

8 EMC ViPR Plg-in for vcenter Orchestrator Overview EMC ViPR for vcenter Orchestrator ViPR plg-in for vco workflows The EMC ViPR plg-in for vcenter Orchestrator (ViPR plg-in for vco) provides an orchestration interface to the EMC ViPR software platform. The EMC ViPR plg-in has prepackaged workflows sed throgh the Orchestrator Client as well as other clients that spport vcenter Orchestrator integration. There are two types of workflows pre-packaged with ViPR. One set of workflows is sed for common ViPR operations, while the other set are the "bilding block" workflows sed for more granlar ViPR operations. Note Workflows for common ViPR operations Yo can access the ViPR worklfows from the VMware vcenter Orchestrator client or web client, Workflows > Library tree. The workflows sed to atomate common ViPR operations sch as provisioning storage for an entire clster. Table 1 Common workflows Workflow Used to - - In Workflow, Library > EMC ViPR > vsphere > Datastore Create EMC ViPR Volme Snapshot for VMFS Datastore Delete Datastore and EMC ViPR Storage Creates a snapshot of a ViPR block volme. Deletes the ViPR storage, if there are no hosts associated, or snapshots associated with the storage. If the storage is associated with hosts, there is an option to delete the storage and the host associations. If the storage has snapshots there is an option to delete the storage and the associated snapshots. Expand a Datastore with EMC ViPR Storage Share VMFS Datastore with Clster Share VMFS Datastore with Mltiple Clsters Expands the ViPR storage and then the datastore. Shares the VMFS datstore and the ViPR storage with the hosts in a clster. Shares a VMFS datastore with more than one clster. In Workflow, Library > EMC ViPR > vsphere > Hosts/clster Delete Raw Disk (RDM) and EMC ViPR Storage Provision NFS Datastore for Clster with EMC ViPR Storage Deletes the Raw Disk, removes the storage from the hosts, then deletes the storage. Creates a ViPR file system, and datastore, and associate them with the clster. 8 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide

9 EMC ViPR Plg-in for vcenter Orchestrator Overview Table 1 Common workflows (contined) Workflow Used to - - Provision Raw Disk (RDM) with Creates a ViPR block storage volme, associates the volme EMC ViPR Storage with the hosts in a clster, and creates a corresponding Raw Disk (RDM) for a virtal machine (VM). Provision VMFS Datastore for Clster with EMC ViPR Storage Creates a ViPR volme, and datastore, and associate them with the clster. Bilding block workflows Bilding block workflows are individal operations sed to constrct the common workflows. The bilding block workflows can also be sed individally, to perform granlar ViPR operations sch as creating a ViPR volme. Table 2 Bilding block workflows Workflow Used to - - In Workflow, Library > EMC ViPR > General Create EMC ViPR File System Create EMC ViPR Volme Create EMC ViPR Volme Snapshot Create Raw Disk (RDM) Delete EMC ViPR File System Creates a file system with ViPR storage. Creates a block volme with ViPR storage. Creates a snapshot of the VMFS datastore. Creates a SCSI controller and Raw Device Mapping (RDM) on the virtal machine (VM). Deletes the ViPR file system, if there are no hosts associated with the file system, and if no snapshots are associated with the file system. If the files system is associated with hosts, there is an option to delete the storage and the host associations. If the file system has snapshots there is an option to delete the storage and the associated snapshots. Delete EMC ViPR Volme Deletes the ViPR block volme, if there are no hosts associated with the volme, and if no snapshots are associated with the volme. If the volme is associated with hosts, there is an option to delete the storage and the host associations. If the volme has snapshots there is an option to delete the storage and the associated snapshots. Delete Raw Disk (RDM) Expand EMC ViPR File System Expand EMC ViPR Volme Deletes a Raw Disk Mapping (RDM) virtal disk on a virtal machine. Expands an ViPR file system. Expands the ViPR block volme to the defined size. ViPR plg-in for vco workflows 9

10 EMC ViPR Plg-in for vcenter Orchestrator Overview Table 2 Bilding block workflows (contined) Workflow Used to - - Export EMC ViPR File System Exports an ViPR file system to a host or host clster. Export EMC ViPR Volme Get EMC ViPR File System Mont Path for Datastore Get EMC ViPR Volme WWN for Datastore Provision for EMC ViPR Volme for Hosts Provision Raw Disk for VM name and UUID Presents a ViPR volme to a host or host clster. Gets the ViPR file system mont path for a given datastore. Gets the ViPR block volme World Wide Name (WWN) for a given datastore. Creates a volme from ViPR storage and presents it to the hosts. This workflow is a non-interactive workflow designed specifically to work with the EMC ViPR Enablement Kit for vcenter Atomation Center. Refer to the EMC ViPR Enablement Kit for vcenter Atomation Center White Paper for complete details. Mlti-client integration The EMC ViPR plg-in for vcenter Orchestrator bilds pon the vcenter Orchestrator integration fnctionality to provide EMC ViPR workflow and resorce management. The mlti-client spport allows access either interactively or programmatically, with maximm flexibility to assemble any soltion appropriate to yor environment. When sed interactively, some workflow vales are poplated with vales corresponding to the context from which they were lanched. For example, if the workflow is exected from a vsphere Web Client within the context of a clster, the host clster vales are entered into the workflow. When sed programmatically, the EMC ViPR plg-in provides the capability to pass new workflow parameters, throgh an external application, as reqired. The fnctionality provided with the EMC ViPR plg-in for vcenter Orchestrator is spported by the following clients when vcenter Orchestrator is integrated with the application. vcenter Orchestrator REST API VMware vsphere, vcenter Server VMware vclod Atomation Center Refer to EMC ViPR Plg-in Integration with Additional VMware Applications on page 20 for client integration details. 10 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide

11 CHAPTER 2 EMC ViPR and vcenter Orchestrator Configration Reqirements This chapter contains the following topics: EMC ViPR configration reqirements...12 vcenter Orchestrator configration reqirements EMC ViPR and vcenter Orchestrator Configration Reqirements 11

12 EMC ViPR and vcenter Orchestrator Configration Reqirements EMC ViPR configration reqirements The EMC ViPR environment mst meet specific configration reqirements to spport the ViPR plg-in for vcenter Orchestrator. Only a ViPR Tenant Administrator or Project Administrator for the Project being configred, can rn the workflows. Note ViPR roles are configred by ViPR Secrity Administrators from the ViPR Administration and Self-service UI (ViPR UI). A ViPR System Administrator mst configre the following, sing the ViPR UI, ViPR API, or ViPR CLI prior to rnning any of the workflows: ViPR virtal assets, sch as virtal storage arrays (virtal arrays), and virtal storage pools (virtal pools) mst have been created. Note Mlti-volme consistency grops are not spported by the EMC ViPR Plg-in for vcenter Orchestrator. The ViPR plg-in does not allow sers to select virtal pools in which mlti-volme consistency is enabled. However, if invoking the workflows programmatically, or throgh an external application, provisioning fails if a virtal pool with mlti-volme consistency enabled is selected. Hosts mst have been to the virtal array, networks. The vcenter server mst be added to ViPR. Each instance of the ViPR plg-in can be sed to manage one instance of ViPR. Yo cannot manage mltiple instances of ViPR with a single instance of the ViPR plg-in for vcenter Orchestrator. vcenter Orchestrator configration reqirements vcenter Orchestrator mst meet specific configration reqirements to spport the EMC ViPR plg-in for vcenter Orchestrator. Note vcenter Orchestrator version 5.1.x. The EMC ViPR plg-in reqires that the VMware vcenter Server plg-in for vcenter Orchestrator version 5.1.x is installed on the same vcenter Orchestrator rnning the EMC ViPR plg-in. The vcenter server on which ViPR storage will be provisioned mst be added to the Orchestrator Configration interface Plg-ins men. Enable the Share a niqe session mode for the vcenter Server plg-in for vcenter Orchestrator before invoking the EMC ViPR workflows. Enable the Share a niqe session mode throgh the vcenter Orchestrator Configration interface, vcenter Server, New vcenter Server Host tab. vcenter Orchestrator sers mst be part of the Orchestrator administrator grop to install and configre plg-ins. 12 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide

13 EMC ViPR and vcenter Orchestrator Configration Reqirements Refer to VMware vcenter Orchestrator docmentation for specific configration steps. vcenter Orchestrator configration reqirements 13

14

15 CHAPTER 3 EMC ViPR Plg-in Installation and Configration This chapter contains the following topics: Installing the EMC ViPR plg-in for vcenter Orchestrator Configring EMC ViPR and system settings Verifying the EMC ViPR plg-in installation Generating EMC ViPR workflow docmentation...17 EMC ViPR Plg-in Installation and Configration 15

16 EMC ViPR Plg-in Installation and Configration Installing the EMC ViPR plg-in for vcenter Orchestrator The EMC ViPR plg-in, EMC-ViPR-vCo-Plgin.dar, is available from EMC Spport Zone. Once downloaded, the plg-in is installed from the Orchestrator Configration interface. Procedre 1. Download the EMC-ViPR-vCo-Plgin.dar file from EMC Spport Zone. 2. Enter the VMware vcenter Orchestrator server host name in a spported browser to access the vcenter Orchestrator Web view. See VMware vcenter Orchestrator docmentation for a list of spported Web browsers. 3. Click thevcenter Orchestrator Orchestrator Configration link. 4. Click Plg-ins, and contine to follow the vcenter Orchestrator steps for installing plg-ins. 5. When prompted, point to the EMC-ViPR-vCo-Plgin.dar file on yor local machine. 6. Once the plg-in is installed, restart the vcenter Orchestrator server host. 7. Restart both the vcenter Orchestrator and the Orchestrator Configration server. Note The vcenter Orchestrator server host mst be restarted before restarting the services. Configring EMC ViPR and system settings Set the EMC ViPR settings and workflow timeot period from the vcenter Orchestrator Configration interface EMC ViPR Configration page. Before yo begin vcenter Orchestrator reqires sers to be part of the vcenter Orchestrator administrator grop to se the Orchestrator Configration interface. The ViPR ser entered in the vcenter Orchestrator Configration settings mst have been assigned a ViPR Tenant Administrator role or a Project Administrator role for the Project being configred. ViPR roles are configred by ViPR Secrity Administrators from the ViPR Administration and Self-service UI (ViPR UI). While working with EMC ViPR workflows interactively, throgh vcenter Orchestrator or vsphere, ViPR configration settings behave as follows: The EMC ViPR hostname/ip address, sername, password, port, and project are not presented in the ViPR workflows, and can only be changed throgh the vcenter Orchestrator Configration interface. The ViPR virtal array is a defalt setting, which may be atomatically or manally set. While execting the workflow, the target virtal array is compted when possible. For example, if the workflow is exected within the context of a vsphere clster, the correct virtal array for the clster is compted by the plg-in, and set in the drop-down men. If the virtal array cannot be compted, the virtal array, defined as the defalt in the vcenter Orchestrator Configration interface is set as the first option in the drop-down men, followed by a list of the other available 16 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide

17 EMC ViPR Plg-in Installation and Configration ViPR virtal arrays. Yo can change the compted or defalt virtal array setting when configring the workflow. When ViPR workflows are invoked programmatically from external applications, the configred settings act as defalts and can be overridden throgh the external program. Procedre 1. Lanch and login to vcenter Orchestrator Configration. 2. Click EMC ViPR Plg-in (1.0.0). 3. Enter the virtal IP address of the EMC ViPR host, and port nmber Note The port nmber mst be Enter the ser credentials and resorces to manage with the EMC ViPR plg-in for vcenter Orchestrator. 5. Click Verify Connection to ensre the connection is valid. 6. Select an EMC ViPR project in which to rn the worklfows. 7. Select the defalt virtal array to se when the virtal array cannot be atomatically compted. 8. Select the amont of time in mintes that each ViPR operation within a workflow can rn before timing ot. 9. Click Apply Changes. Verifying the EMC ViPR plg-in installation To verify that the EMC ViPR plg-in was correctly installed, locate the EMC ViPR folder vcenter Orchestrator > Workflows > vcenter Administrator > Library and review the list of workflows. Procedre 1. Lanch vcenter Orchestrator. 2. Log into the vcenter Orchestrator Clientor Web Operator. 3. Go to Workflows, and expand the vcenter Administrator > Library. 4. Expand the EMC ViPR folder to ensre the EMC ViPR workflow library is installed. The expanded EMC ViPR folder is demonstrated in the EMC ViPR Workflow tree. Generating EMC ViPR workflow docmentation vcenter Orchestrator provides a featre for generating workflow docmentation that describes the workflow inpts in detail. Before yo begin Adobe Reader is reqired to generate and view the workflow docmentation. The generate docmentation featre is only available from the vcenter Orchestrator installable client. Docmentation cannot be generated from the vcenter Orchestrator Web Operator. Verifying the EMC ViPR plg-in installation 17

18 EMC ViPR Plg-in Installation and Configration Procedre 1. From the vcenter Orchestrator Client Workflows tab, expand the vcenter Administrator > Library. 2. Right-click the EMC ViPR folder, and select Generate Docmentation to generate an Adobe PDF docment of all the EMC ViPR workflows and their parameter descriptions. 3. Optionally, expand the EMC ViPR folder, right-click on a specific EMC ViPR workflow, and click Generate Docmentation to generate an Adobe PDF docment of the selected workflow. 18 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide

19 CHAPTER 4 EMC ViPR Plg-in Integration with Additional VMware Applications This chapter contains the following topics: EMC ViPR workflow mlti-client integration...20 VMware vcenter Orchestrator REST API integration VMware vsphere, vcenter Server integration VMware vclod Atomation Center Workflow CPU and memory tilization EMC ViPR Plg-in Integration with Additional VMware Applications 19

20 EMC ViPR Plg-in Integration with Additional VMware Applications EMC ViPR workflow mlti-client integration The EMC ViPR plg-in for vcenter Orchestrator integration fnctionality provides EMC ViPR workflows and resorce management throgh additional VMware clients. VMware integration reqirements and recommendations The VMware environment mst meet the criteria described in the following sections to spport the EMC ViPR plg-in for vcenter Orchestrator. Refer to VMware docmentation for integration procedres and additional details. VMware vcenter Orchestrator REST API integration Access and rn the EMC ViPR plg-in for vco workflows from the vcenter Orchestrator REST API. vcenter Orchestrator REST API integration reqirements vcenter Orchestrator REST API version 5.1 or higher. The defalt EMC ViPR host, ser, project, virtal array, and virtal pool were defined while configring EMC ViPR from the vcenter Orchestrator Configration interface. VMware vsphere, vcenter Server integration Integrate the workflows installed with EMC ViPR plg-in for vcenter Orchestrator with the vcenter Server. Once integrated, invoke and se the workflows throgh the vsphere Web Client. VMware vsphere integration recommendations and reqirements VMware vsphere 5.1 (or higher) VMware vcenter Server vsphere reqires that a Single sign-on (SSO) is configred between vsphere and vcenter Orchestrator. Both the EMC ViPR plg-in for vcenter Orchestrator and the vcenter Server plg-in for vcenter Orchestrator are installed on the same vcenter Orchestrator instance. Enable the Share a niqe session mode for the vcenter Server plg-in for vcenter Orchestrator throgh the vcenter Orchestrator interface, before invoking the ViPR workflows throgh the vcenter Server. One instance of the vsphere vcenter Server can be sed for one ViPR instance. A single vcenter Server instance cannot be sed to manage mltiple instances of ViPR. EMC ViPR workflows can only be invoked from the vsphere Web Client. The workflows cannot be accessed from the locally installed vsphere Client. EMC ViPR workflow settings The EMC ViPR Hostname, Username, Password, and Project are broght in with the workflows and cannot be reconfigred when the workflows are invoked throgh the vsphere Web Client. The EMC ViPR virtal array may be set atomatically or manally. While execting the workflow, the target virtal array is compted based on the context of the workflow when it is invoked. If not compted, the virtal array is atomatically set to the virtal array configred for the workflows in vcenter Orchestrator. The virtal array however, can always be manally overridden when execting the workflows. 20 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide

21 EMC ViPR Plg-in Integration with Additional VMware Applications If manally entering the virtal array, and the virtal pool, the virtal array and virtal pool names are not rendered in vsphere. The virtal array and virtal pool names mst be manally typed into the fields. VMware vclod Atomation Center Invoke and se the ViPR plg-in workflows from vclod Atomation Center vclod Atomation Center integration reqirements and recommendations VMware vclod Atomation Center version 5.1.x. A single instance of vclod Atomation Center can be sed to manage mltiple instances of ViPR for example, the ViPR sername and password can be passed in programmatically, allowing vclod Atomation Center to have mltiple ser mappings. This might be done in a mlti-tenant environment or an enterprise, with self-service portals that may have different configrations for different departments. EMC ViPR workflow settings All the EMC ViPR workflow parameters can be passed programmatically throgh vclod Atomation Center. The ViPR hostname, sername, password, project, and virtal array that are configred for the workflows throgh the vcenter Orchestrator Configration interface are set as defalts, bt can be overridden by the parameters passed when invoked throgh vclod Atomation Center. Workflow CPU and memory tilization EMC testing has demonstrated the following resorce tilization for vcenter Orchestrator when the ViPR plg-in is rnning. Reslts may vary in other environments. EMC testing environment The setp for the EMC testing environment was configred as follows: vcenter Orchestrator VMware vcenter Orchestrator version Gest OS Novell SUSE Linx Enterprise 11 (64-bit) vcpu 2 vcpu, processor type Intel(R) Xeon(R) 2.27 GHz Memory 3072MB Resorce tilization characteristics The statistics measre the tilization of the vcenter Orchestrator Configration server process while execting a ViPR workflow. The two datasets below represent a basic workflow and a complex workflow. The peak CPU tilization occrs at the end of the workflow and is short lived. The memory tilization incldes the overhead of rendering the vcenter Orchestrator Configration client. Table 3 Basic EMC ViPR workflow Resorce Type Average % Peak % CPU 1.48% 2.94% Memory MB 2912 MB VMware vclod Atomation Center 21

22 EMC ViPR Plg-in Integration with Additional VMware Applications Table 4 Complex EMC ViPR workflow Resorce Type Average Peak CPU 1.74% 16.58% Memory MB 3064 MB 22 EMC ViPR Plg-in for VMware vcenter Orchestrator Installation and Configration Gide