VMware vcenter Lab Manager 4 Evaluator s Guide

Transcription

1 E V A L U A T O R ' S G U I D E Installing, Configuring, and Deploying Lab Manager

2 Contents 1. Getting Started About this Guide Help and Support during the Evaluation What is VMware vcenter Lab Manager? System Requirements Hardware Requirements Software Requirements Software Installations and Configurations VMware vcenter Lab Manager Installation and Configuration Creating Virtual Machine Templates Lab Manager Evaluation Tasks Setting up Organizations and Workspaces Creating Multi-VM Configurations Sharing Configurations With Other Users Moving Configurations Across Workspaces Next Steps VMware Contact Information Providing Feedback Glossary VMware vcenter Lab Manager Evaluation Worksheet

3 1. Getting Started 1.1 About this Guide The purpose of this document is to support a self-guided, hands-on evaluation of VMware vcenter Lab Manager 4. This document is intended to provide IT professionals with the necessary information to install, configure, and deploy VMware vcenter Lab Manager in a VMware vsphere environment. This guide will walk you through some key use cases for VMware vcenter Lab Manager to help you conduct a successful product evaluation. A worksheet provided at the end of this guide will help you track your progress. A glossary of terms is also available to help explain unfamiliar terms. 1.2 Help and Support during the Evaluation This guide is not meant to be a substitute for product documentation. For detailed information regarding installation, configuration, administration, and usage of VMware products, please refer to the online documentation. You may also consult the online Knowledge Base if you have any additional questions. Should you require further assistance, please contact a VMware sales representative or channel partner. Below are some links to online resource, documentation and self-help tools: VMware vsphere and VMware vcenter Server Resources: Product Overview Product Documentation VMware vsphere 4 Documentation (including hardware compatibility guides) White Papers and Technical Papers VMware vsphere Evaluator s Guide VMware vcenter Lab Manager Resources: Product Overview Product Documentation Installation Guide User s Guide VMware vcenter Lab Manager Community Support Knowledge Base 3

4 E valuator s guide 2. What is VMware vcenter Lab Manager? VMware vcenter Lab Manager, part of the VMware vcenter family of management products, provides on-demand access and automated management of the internal cloud for dev/test. Application Owners, Development and Test, Support and Training teams can provision application environments in seconds and manage a library of common system configurations through a self-service portal under IT control. Lab Manager enforces policy-based access control, optimizes utilization of shared infrastructure, and avoids resource conflict in a multi-user environment eliminating repetitive provisioning and ad-hoc management tasks for IT. Designed for enterprise scalability, best-in-class performance, and seamless integration with VMware vsphere, Lab Manager enables higher service levels, faster time to market and simplified IT administration. The key features of VMware vcenter Lab Manager are: Self Service Portal Set up, capture, and re-configure multi-vm system configurations in seconds Virtual Machine Image Library Provide an archive of commonly used system configurations while reducing storage footprints Organizations Optimized resource utilization of shared infrastructure, better control and compliance with IT policy Enterprise Scalability Provides best in class performance and scalability from local to global deployments. VMware vcenter Lab Manager seamlessly integrates with VMware vsphere and VMware vcenter Server 4. Figure 2.1. VMware vcenter Lab Manager System Overview Virtual Machines VM Resource Pool VM V M VM wa re I n VM VM fra str VM uct ure Image Storage Library VMWARE vcenter LAB MANAGER VM Lab Admin VMWARE vcenter Local Team Remote Team 4

5 3. System Requirements 3.1 Hardware Requirements The minimum hardware requirements for a successful evaluation include the following components: One server This is used to install VMware ESX, VMware vcenter Server, and VMware vcenter Lab Manager Server software. Please see the VMware ESX 4 hardware compatibility list for supported server models. One Windows workstation or laptop This is used to manage the ESX server, with the VMware vsphere Client. Please install the VMware vcenter Server and VMware vcenter Lab Manager Server on separate Windows virtual machines. For better scalability, we recommend that you use as many ESX servers and shared storage as you need to support your infrastructure needs. For detailed hardware requirements for ESX Server host(s), refer to the table below: Hardware Requirements for VMware vcenter Lab Manager Evaluation Use Cases Minimum Recommended Hardware Used in this Guide # ESX Server hosts 1 Minimum of 3 ESX Servers for a small lab/ team environment CPU 2 processors of 1500 MHz 2 dual-core processors of 1500 MHz Memory 1GB 16GB 8GB 4 (One server hosting vcenter Server and Lab Manager server. 3 Servers providing resources for Lab Manager) 2 processors of 1500 MHz Disk Space 256GB (SAN/Local) 1 TB (SAN) 512GB (SAN) Network 1 Gigabit NIC 2 Gigabit NIC 1 Gigabit NIC 3.2 Software Requirements For the purpose of this evaluation, you will need the latest versions of the following software: VMware vsphere 4 Evaluation copy VMware vcenter Lab Manager 4 Evaluation copy Please see the VMware Lab Manager product page for the latest compatibility matrices. VMware offers a free 60-day evaluation of VMware vcenter Lab Manager. From the Lab Manager Evaluation page, you will be able to download the necessary licenses and the following binaries: Binary VMware ESX 4 (iso file) VMware vcenter Server 4 (zip file) VMware vcenter Lab Manager executable Usage You can create a boot CD from this iso file and use this CD to boot you server and install ESX 4. The zip file includes an installer for VMware vcenter Server 4. You launch this executable in a Windows Server 2003 host where you wish to install VMware vcenter Lab Manager. 5

6 3.3. Software Installations and Configurations Before you start the evaluation tasks described in this document, you will need to install and configure the software listed in section 3.2. The table uses time estimates based on the hardware used to write this guide. Step Installation and Configuration Details Time Estimate 1. Provision physical servers with the hardware profile described in Step Install ESX software on physical servers, including storage configuration. (See ESX Server 4 Installation Guide for more details) 3. Install VMware vsphere Client1 on a supported Windows machine (e.g. a laptop). 4. Create two virtual machines on an ESX host using the VMware vsphere Client and install Windows Server 2003 on it. 2 Varies 45 minutes per ESX host. For multiple ESX Servers, installations can be done in parallel to save time. 10 minutes 20 minutes including guest OS installation time. OS installations can be done in parallel to save time. Virtual machine configuration: Operating System: Windows Server bit Enterprise Edition (SP1 or higher)/ Standard Edition (SP1 or higher) CPU: 1GHz Memory: 1GB Disk: 40GB Network: 1 NIC card 5. Install VMware vcenter Server on one of the virtual machines created in Step Start the vsphere client and connect to the VMware vcenter Server installed in Step 6. Add the ESX hosts provisioned in Step 2. to the VMware vcenter Server inventory 7. Create a Cluster Lab Manager Cluster. Create four resource pools in Lab Manager Cluster called Project_01, Project_02, Staging and Production and use default settings for all resource pools 3 8. Install and configure VMware vcenter Lab Manager server in the other virtual machine created in Step 4. Please see Section 3.4 for details. Total Estimated Time 15 minutes 10 minutes 10 minutes 15 minutes installation, 15 minutes configuration 2 hours 20 minutes excluding hardware provisioning time 1 Open a Web browser and connect to your ESX host by typing in the hostname or IP address. Click the Download VMware vsphere Client link. Save the installer to your workstation and install the VMware vsphere Client. Launch the client and type in the IP address or hostname of the ESX Server to connect. 2 For instructions on creating virtual machines and installing guest OS, please refer to the vsphere Basic System Administration guide. 3 For instructions on creating Clusters and Resource Pools, please refer to the vsphere Basic System Administration guide. 6

7 3.4. VMware vcenter Lab Manager Installation and Configuration Before installing VMware vcenter Lab Manager on the virtual machine created in step 4 of section 3.3, you need to ensure the following prerequisites are met: Prerequisites Windows Server 2003 services and framework Network Details Install: Internet Information Services (IIS) 6.0.NET framework 2.0 (SP1 or higher) ASP.NET Prepare: Static IP address for NIC card Pool of unused IP addresses Gateway Subnet Mask Primary DNS Server (Optional) Secondary DNS Server To install VMware vcenter Lab Manager, you can simply launch the VMware vcenter Lab Manager Installation executable listed in section 3.2 in a virtual machine. During the installation process, you will be prompted to enter the information of your VMware vcenter Server host. Add the resource pools created in Step 7 of Section 3.3 when configuring Lab Manager for the first time. Create two Physical Networks Engineering Network and IT Operations Network with Static IP addressing mode and pool of IP addresses setup2 After VMware vcenter Lab Manager has been successfully installed, you will be able to evaluate its capabilities as described in the sections below. For detailed installation instructions, please refer to the Lab Manager Installation and Upgrade guide. At the end of the installation, Lab Manager is now configured with the following resources. Resource Resource Pools in VMware vcenter Server Physical Networks in Lab Manager Details Four Resource Pools - Project_01, Project_02, Staging and Production 1 Two physical networks - Engineering Network and IT Operations Network with Static IP addressing mode and pool of IP addresses setup 2 1 Please refer to the VMware vsphere Basic System Administration guide for instruction on setting up Resource Pools. 2 Please refer to the Lab Manager User s Guide for instructions on setting up Physical Networks in Lab Manager. 7

8 3.5 Creating Virtual Machine Templates Templates are basic building blocks in Lab Manager to create multi-tier virtual machine configurations. Templates can be created from scratch in Lab Manager, or imported from VMware vcenter Server or an SMB file server. Step 1: Log in to VMware vcenter Lab Manager 1. Open a browser window 1 and type the address of the VMware vcenter Lab Manager server. You can type in the IP address or the DNS name. 2. Type the administrator credentials to access the VMware vcenter Lab Manager Web interface. Figure 3.5 a. Lab Manager Login screen Step 2: Import existing virtual machines as templates into VMware vcenter Lab Manager You can create virtual machine templates from scratch using Lab Manager. Please see the VMware vcenter Lab Manager User s guide for instructions on how to create templates and install Guest operating systems. 8 1 Please check the Lab Manager User s Guide for a list of supported browsers. Please read the Accessing the Lab Manager Web Console section of the User s Guide to understand the browser settings required to access the Lab Manager console.

9 In this guide, we will import virtual machines from vcenter Server. This step assumes that you have virtual machines available in VMware vcenter Server ready for import. If you need to create virtual machines in vcenter Server, you can do one of the following: Method Create a virtual machine from scratch in vcenter Server Convert an existing physical machine using vcenter Converter Enterprise for VMware vcenter Server Time Estimate 30 minutes including Guest OS installation Varies (Depends on the size of the source machine) To create virtual machine templates in VMware vcenter Lab Manager, do the following: 1. In the left pane, select Global from the Organization drop down menu. 2. In the left pane, click VM Templates. 3. Click the Import VM Template button. 4. Enter the information for the template. a. Select the virtual machine for your template in the vcenter directories. The virtual machine should be powered off and not already under VMware vcenter Lab Manager control. b. Enter a name for the virtual machine template. c. (Optional) Enter a description. d. Click the Next button. Figure 3.5 b. Importing virtual machines from VMware vcenter to use as templates 9

10 e. (Optional) Deselect the Perform customization check box if you do not want Lab Manager to customize the network settings for the virtual machine template or virtual machines based on the virtual machine template. 1 f. Specify the networking information for each NIC in the imported virtual machine template. i. Select Connected to connect the virtual machine template to the network when it is deployed. ii. Choose a default virtual or physical network. iii. Choose a default IP addressing mode. g. Select the Storage and Deployment Leases for this template. h. Select the Destination Datastore. Select Make a copy. i. Click Import. Figure 3.5 c. Selecting Customization, Network, and Storage options when creating template j. Publish the template VM to make it available for use in creating new configurations. i. Mouse over the name of the template you created to reveal the menu options. ii. Click Publish. 10 1To perform customization, please install Windows sysprep files on the VMware vcenter Server. Please see the VMware vsphere Basic System Administration guide for details.

11 Figure 3.5 d. Publishing a template 11

12 4. Lab Manager Evaluation Tasks Lab Manager allows non-it users to create and manage a library of commonly used virtual machine configurations and provision application environments in seconds from a self-service portal while IT remains in administrative control. Lab Manager is ideally suited for groups of users with rapidly changing infrastructure needs such as application development and QA teams, release management, support, and training operations. In the remainder of this document, we describe suggested evaluation tasks to demonstrate the value of Lab Manager. While the evaluation tasks are somewhat generic they can be easily applied to streamline application development and testing processes, staging and pre-production, and improve team collaboration by sharing application environments in state more easily. This section outlines four tasks for VMware vcenter Lab Manager. The tasks are: 1. Setting up organizations and workspaces 2. Creating a multi-vm configuration 3. Sharing configurations with other users 4. Moving configurations across workspaces The table below presents an overview of the tasks and a description of these tasks with their benefits. The time estimates provide an approximation of the expected time that you will spend in each use case. They do not necessarily reflect the exact time needed. Task Description Time Estimate Setting up organizations and workspaces Lab Manager offers policy-based access controls to provide groups of users access to internal resources in a controlled and predictable manner 10 minutes Creating multi-vm configurations Sharing configurations with other users Moving configurations across workspaces Benefit: Simplified user management and the ability to easily separate resources in compliance with IT policy Lab Manager offers the ability to create multi-machine configurations that can be operated on as a single unit Benefit: Develop multi-tiered applications with ease and package them as one unit. Power on, power off, snapshot, suspend configurations in state as a unit Lab Manager lets users share configurations via a shared library or by using LiveLink Benefit: Share gold master library configurations. Reproduce all bugs discovered during testing Lab Manager offers the ability to share configurations with other organizations and move them across workspaces Benefit: Smoothly transition applications from development to staging to production in minutes 10 minutes 10 minutes 10 minutes Total time estimate: 40 minutes 12

13 4.1. Setting up Organizations and Workspaces VMware vcenter Lab Manager allows you to create multiple organizations each with multiple workspaces, which include resources and users. You can use these organizations and workspaces to control which users have access to which resources. Lab Manager has access to the resources of the VMware vcenter Server to which it is connected. A system administrator can assign some or all of these resources to an organization. Users in that organization only have access to their assigned resources. An organization can have dedicated resources or share resources with other organizations. In an organization, an administrator can create workspaces and assign some or all of the organization resources to each workspace. A workspace can have dedicated resources or share resources with other workspaces. These levels of granularity provide the system administrator with substantial control over compute, memory, network, and storage resources. Lab Manager is pre-configured with an organization named Default. A system administrator can change the Default organizations and create additional organizations. We will be creating two new organizations: Engineering and IT Operations. In this task, you will create two organizations: Engineering and IT Operations and assign resources to each of these organizations. You can assign some or all of the resources associated with a Lab Manager installation to an organization. Users in that organization only have access to those resources. An organization can have dedicated resources or share resources with other organizations. In the Engineering organization, you will perform tasks that demonstrate how easy it is to develop applications inside Lab Manager. Once you are done developing the application, you will then proceed to transfer your application to the IT organization for staging and production. Step 1: Create two Organizations Engineering and IT Operations For each organization you create please use the instructions below and the table that follows for the values to enter. 1. In the left pane, click Organizations. 2. Select Global from the Organization drop-down menu. 3. Click Organizations under System in the left pane. 4. Click New Organization. 5. Type in the name. 6. (Optional) Type a description. 7. Select one or more resource pools from Available and move them to Selected. 8. Select one or more fence transport networks from Available and move them to Selected. 9. Select one or more physical networks from Available and move them to Selected. 10. Click OK. Organization Name Resource Pool Names Network Name Engineering Project_01 and Project_02 Engineering Network IT Operations Staging and Production IT Operations Network 13

14 Figure 4.1 a. Selecting the resource pools and Physical Networks for the Engineering organization Lab Manager creates two organizations Engineering and IT Operations and creates a Main workspace for each organization. Click Organizations in the left pane to verify that the Engineering and IT Operations organization are present. 14

15 Figure 4.1 b. Lab Manager with two new organizations Engineering and IT Operations Step 2: Creating Workspaces Every organization includes a Main workspace. The Main workspace is the primary workspace in an organization and contains all the resources and users that are part of the organization. All configurations created in the Main organization are Private by default. The Main workspace can be changed to create Shared configurations by modifying its properties. In a shared workspace, by default, all the users in that workspace can access the configurations. In a private workspace, by default, users can only access their own configurations. System administrators and administrators with rights at the organization level can create additional workspaces. In this task, you will create two additional workspaces each in the Engineering organization and the IT Operations organization. When you create a workspace, you can choose whether you want to share its configurations or keep them private. For each organizational workspace you create please use the instructions below and the table that follows for the values to enter. 1. In the Organization drop-down menu, select the organization in which you want to create a workspace. 2. In the left pane, click Workspaces. 3. Click New Workspace. 4. Type a name. 5. (Optional) Type a description. 6. Determine whether the workspace should be shared or private. 7. Select one or more resource pools from Available and move them to Resource Pools used by this Workspace. 8. Click OK. 15

16 Organization Name Workspace Name Resource Pool Engineering Project_01 (Shared) Project_01 Engineering Project_02 (Shared) Project_02 IT Operations Staging (Shared) Staging IT Operations Production (Private) Production Figure 4.1 c. Creating workspace Project_01 Now that you have created four workspaces, select each Organization from the Organization drop down menu and verify that the workspaces are present. Now you can import virtual machines and create configurations. 16

17 Figure 4.1 d. Engineering Organization with two new workspaces Project_01 and Project_02 Figure 4.1 e. IT Operations Organization with two workspaces Staging and Production 4.2. Creating Multi-VM Configurations VMware vcenter Lab Manager allows you to create multi-vm configurations in seconds using virtual machine templates. Users can share these configurations and act on machines in a configuration as a unit: suspend, snapshot, revert, shutdown, turn on, turn off, suspend, reset, deploy, undeploy, clone, capture to library, and modify properties. In the steps described below, you will use the Engineering organization that you created in Section 4.1 to create and deploy multi-vm configurations. You will then use some of the configuration sharing features in Lab Manager to allow multiple users to effectively collaborate and develop applications. To create a multi-vm configuration you will select the Engineering organization and use the template virtual machines that you created previously. You will combine the templates created to create a multi-machine configuration and deploy it in the engineering resource pools. You will use the Main workspace to create your configurations. The Main workspace contains all of the users and resource pools in the Engineering organization and is Private by default which means configurations are only visible to their owners. 17

18 Step 1: Create multi-vm configuration 1. In the left pane, click Workspaces. 2. Mouse over Main and click Open. 3. Click the New Configuration button. 4. Enter the details of the configuration. a. Enter the name of the configuration. b. (Optional) Enter a description. c. Select the Deployment Lease and Storage Lease for the configuration. d. Select the VM Fencing Policy for the configuration. e. Select the virtual machine template that you wish to add to the configuration. i. Enter a name for the virtual machine in the configuration. ii. VMware vcenter Lab Manager uses linked clones by default for fast deployment and storage savings. If you wish to make a full copy of the VM, select Full Clone. iii. (Optional) Select the Network, IP addressing mode. If you select the manual IP addressing, enter the IP address you will be using with the VM. f. Click Add VM button and repeat Step e for each VM template you wish to add to your configuration. Figure 4.2 a. Creating configuration by adding template virtual machines Step 2: Deploy configurations For every configuration that you wish to deploy in the virtual lab infrastructure do the following: 1. On the left panel, click Workspaces. 2. Mouse over Main and click Open. 3. Mouse over the name of the configuration you created to reveal the menu options. a. Click Deploy. b. Check Fence Virtual Machines. c. Use the defaults for all the other selections and click the OK button. 18

19 Figure 4.2 b. Deploying configuration With network fencing enabled, each configuration is deployed in the infrastructure with a virtual router. Each of these VMs now have an external IP address on the network that is different from the internal IP address in the fence, and the virtual router provides network address translation. This means you can deploy any number of configurations without any modifications on a shared infrastructure and never worry about hostname or IP conflicts. After deploying the configuration, to open the consoles of the virtual machines in the configuration, mouse over the deployed configuration name and click Show Consoles. You can work inside the consoles of all virtual machines in your configuration. You can also perform operations such as suspend, power off, snapshot all virtual machines in your configuration as one unit so the state from all the VMs is saved. For details regarding configurations, please see the section Working with Configurations in the Lab Manager User s Guide. 19

20 Figure 4.2 c: Opening consoles of the deployed configuration The configuration and its virtual machines are now deployed in the Main workspace. Because of the abstraction layer Lab Manager provides, you do not need to know the specific resource pool backing the Main workspace; simply that the virtual machines are deployed and running in his arena of control. 4.3 Sharing Configurations With Other Users Lab Manager provides a shared Library that makes configurations available to other users as the basis for new configurations. Users can clone library configurations to the Workspace and then deploy and/or modify them. This allows users to collaborate with each other and share common configurations to ensure consistent development environments. Administrators can setup the library with blessed Gold Master configurations that all users use for their environments. You will now perform tasks using the Library that demonstrate how easy it is to share configurations with other users in the Lab Manager system. Step 1: Capture running configuration in state to the Library 1. On the left panel, click Workspaces. 2. Mouse over the name of the configuration you created to reveal the menu options. a. Click Capture to Library. b. Enter the name you wish the captured configuration to have in the library. c. (Optional) Enter a description. d. (Optional) Select the Gold Master check box to indicate an important or administrator-approved configuration. e. Select the Storage Lease and click the Capture button. 20

21 Figure 4.3 a. Capturing configuration into Library Step 2: Share the configuration in the Library with other users 1. On the left panel, click Library. 2. Mouse over the name of the configuration you captured to the Library to reveal the menu options. a. Click Sharing. b. Click the Add Users button to select the users with who you want to share your configuration. c. Select Everyone in Organization Engineering and leave defaults for the other options. All users of VMware vcenter Lab Manager can now access this configuration from the Library. d. Click the OK button. e. Verify that Everyone now has Read permissions to your configuration. f. Click the Done button. Figure 4.3 b. Sharing Library copy with all users in the Engineering organization 21

22 You can now proceed to create a LiveLink of the shared library configuration. LiveLink is a feature of VMware vcenter Lab Manager that allows you to capture a running configuration in state and publish a unique URL. Other users use the URL to access the configuration and deploy with a single mouse click. This feature in Lab Manager that allows developers and QA testers in the Engineering organization to collaborate and trouble shoot difficult to reproduce problems. With the LiveLink feature in Lab Manager, QA engineers can freeze a system configuration and capture it in the library. At this point, they will generate the LiveLink and send the LiveLink by to the developers working on the product. When the developers click on the LiveLink in their , it will take them to the Lab Manager system and allow them to deploy into their workspace a linked clone of the library configuration. This ensures that every defect that QA engineers find is now captured in its reproduced state and engineers can deploy these defects into their workspaces while QA engineers can run other tests. You will now perform the task of generating a LiveLink, see how easy and efficient it is to do developement and QA work in Lab Manager. Step 3: Create LiveLink 1. Mouse over the name of the configuration you captured to the Library to reveal the menu options. g. Click LiveLink. h. (Optional) Enter a comment. i. Click the Copy URL button to copy the URL to the windows clipboard. Click OK. j. Send the LiveLink to other users via or capture it in a bug system. The LiveLink is a unique permanent identifier for this configuration in the library. Figure 4.3 c. Creating LiveLink 22

23 Step 4: Deploy LiveLink Lab Manager uses network fencing, a feature that isolates or fences virtual machine configurations on the network. Fencing enables you to work with live instances of the same configuration on the same physical network by providing alternate IP addresses outside the fence and a virtual router for network address translation. To read more about Network fencing, please see the VMware vcenter Lab Manager User s Guide. To deploy the LiveLink: 1. On the top right of your screen, click Logout. 2. In your browser window, paste the URL of the LiveLink that you copied into the windows clipboard. 3. Enter the credentials and click the Login button. 4. Select the Workspace you wish to deploy to from the Workspace drop down list. 5. Click the Deploy button to deploy the configuration in the LiveLink. VMware vcenter Lab Manager deploys the LiveLink into the resource pool with Network Fencing enabled. Network Fencing allows simultaneous deployments of the original configuration (or other configuration in the infrastructure) and the copy created by LiveLink without IP conflict. 6. Mouse over the name of the LiveLink configuration that you deployed in your workspace to reveal the options and Open to show the newly deployed LiveLink details. Figure 4.3 d. LiveLink deployed in fenced mode. Note the IP addresses are different inside the fence and outside the fence 4.4 Moving Configurations Across Workspaces Now that you have developed an application in the Engineering workspace, it is time to move the application into Staging for User Acceptance Testing (UAT) and finally into Production. Lab Manager allows you to easily and efficiently share and move configurations from one workspace to another within organizations and across organizations. In the following set of tasks, you will transition the multi-machine application from the Engineering workspace to the Staging workspace and finally the Production workspace in the IT organization. You will see how easy it is to share configurations across workspaces and you can leverage Lab Manager to roll applications into production. Administrators can share a workspace or library configuration with other users. Sharing a workspace configuration grants access to other users. Sharing a library configuration allows other users to clone their own copy of the configuration to a workspace. 23

24 Step 1: Clone the engineering Library configuration to IT Operations Staging workspace 1. Select Engineering from the Organization drop down menu. 2. In the left pane, click Library. 3. Mouse over your configuration in the library and select Clone to Workspace. 4. Select Staging from the Workspaces drop down menu. 5. Enter a name. 6. (Optional) Enter a description. 7. Click OK. Figure 4.4 a. Cloning configuration to Staging workspace Step 2: Move the configuration to IT Operations Staging workspace to Production workspace. 1. Select IT Operations from the Organization drop down menu. 2. In the left pane, click Workspaces. 3. Click Staging. 4. Mouse over your configuration in the Staging workspace and select Move. 5. Select Production from the Workspaces drop down menu. 6. Enter a name. 7. (Optional) Enter a description. 8. Click OK. 24

25 Figure 4.4 b. Moving configuration from Staging to Production The application is now deployed in production and can be rolled out to users. When the application needs to be updated or patched, you can also use Lab Manager to test production system changes on a production system clone to minimize the risk of downtime due to a failed update. For testing production system patches, you would follow a similar routine as shown above: 1. Create a production system clone. 2. Move the production clone to the Staging workspace. 3. Deploy the production clone in Fenced mode, apply and test your patches. 4. Undeploy the production clone. 5. Move the patched configuration back to the Production workspace. 6. Undeploy the original production system and deploy the new configuration with default settings (not in Fenced mode). Alternatively, you can also apply your tested patches directly to the original production system. 25

26 5. Next Steps As you can see, Lab Manager is an extremely flexible and powerful solution to streamline workflows, improve team collaboration, and automate routine tasks. The examples shown above illustrate some key use cases for this product. As you deploy Lab Manager in your environment, you may discover new ways to make your life easier. Please refer to the Lab Manager User s Guide for more details. We hope you enjoy using VMware vcenter Lab Manager VMware Contact Information For additional information or to purchase VMware vcenter Lab Manager, VMware s global network of solutions providers is ready to assist. If you would like to contact VMware directly, you can reach a sales representative at VMWARE ( outside North America) or sales@vmware.com. When ing, please include the state, country, and company name from which you are inquiring. You can also purchase VMware vcenter Lab Manager 4 online Providing Feedback VMware appreciates your feedback on the material included in this guide, and in particular, would be grateful for any guidance on the following topics: How useful was the information in this guide? What other specific topics would you like to see covered? Overall, how would you rate this guide? Please send your feedback to tmdocfeedback@vmware.com, with VMware vcenter Lab Manager 4 Evaluator s Guide in the subject line. Thank you for your help in making this guide a valuable resource. VMware vcenter Lab Manager 4 Evaluators Guide: Revision

27 6. Glossary Configuration Organizations Workspaces Datastore Fencing (network) Guest operating system IP pool Linked clone Storage lease Deployment lease A group of virtual machines that VMware vcenter Lab Manager controls as a unit. VMware vcenter Lab Manager can replicate these configurations on demand. A group of users and resources in the VMware vcenter Lab Manager system. Organizations can contain multiple workspaces. A workspace is a logical unit in VMware vcenter Lab Manager that contains multiple configurations. Workspaces can be Private or Shared. In private workspaces, only the owners of configurations can see them without explicitly sharing them. In shared workspaces, anyone can see configurations unless their owners explicitly make them private. Configurations can be cloned or moved between workspaces. Virtual representation of combinations of underlying physical storage resources in the datacenter. A Datastore is the storage location (for example, a physical disk, a RAID, or a SAN LUN) for virtual machine files. Lab Manager uses VMFS and NFS datastores for virtual machines and media files. An architecture that isolates or fences virtual machine configurations while allowing full network access. Fencing enables you to work with live instances of identical configurations on the same network simultaneously. An operating system that runs inside a virtual machine. A range of IP addresses set aside for use by VMware vcenter Lab Manager. (n.) A duplicate of a virtual machine that uses the same base disk as the original combined with a chain of delta disks to keep track of the differences between the original and the clone. (v.) To generate a quick copy by creating a delta disk instead of copying an entire virtual hard disk. This operation addresses virtual machine proliferation by using referential provisioning, a process that involves storing new changes but referring back to a chain of delta disks. For each clone, Lab Manager freezes the original delta disk and creates a new one. The amount of time an unused template or configuration exists on a Datastore before VMware vcenter Lab Manager deletes it or marks it for deletion. This affects only unpublished templates. The amount of time after which, VMware vcenter Lab Manager undeploys the configuration or virtual machine template. 27

28 7. VMware vcenter Lab Manager Evaluation Worksheet You can use the worksheet below to organize your evaluation process. Hardware Checklist: Physical server compatible with VMware ESX 4.0 Qty: Storage (Shared/Local) >= 256GB One desktop/laptop running MS Windows (e.g. XP/Windows Server 2003) Software Checklist: Windows Server 2003 Installation CD image VMware ESX 4 Installation DVD image VMware vcenter Server 4 installation zip file VMware vcenter Lab Manager 4 installation file License keys for all software components Installation Checklist: VMware ESX 4 installed on physical server(s) VMware vsphere Client installed on the desktop/laptop running MS Windows Two Virtual machines created on the ESX Server hosts prepared above Windows Server 2003 (W2K3) installed as the guest operating system VMware vcenter Server and database installed on one of the W2K3 virtual machines VMware vcenter Lab Manager installed on the other W2K3 virtual machine Lab Manager configured with resource pools, physical networks and templates After you have successfully checked off the lists above, you can proceed to perform the evaluation of VMware vcenter Lab Manager. For each scenario, you can use the corresponding checklist below to ensure that you are following the proper sequence. Create organizations and workspaces Create two organizations Engineering and IT Operations Create two workspaces within each organization Create multi-vm configurations Create a multi-vm configuration in the Engineering organization using the templates Deploy configuration into the Main workspace Share configurations with other users Capture running configuration in state into the library Share the configuration in the library with other users Publish LiveLink Deploy LiveLink Move configurations across workspaces Clone the engineering library configuration to IT Operations Staging workspace Move the configuration to IT Operations Staging workspace to Production workspace 28

29 VMware, Inc Hillview Ave Palo Alto CA USA Tel Fax Copyright 2009 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMW_09Q2_EG_Lab Manager 4_P29_R1