Related Manuals for Novell PLATESPIN ORCHESTRATE 2.0.2 - VIRTUAL MACHINE MANAGEMENT GUIDE 10-17-2009
Summary of Contents for Novell PLATESPIN ORCHESTRATE 2.0.2 - VIRTUAL MACHINE MANAGEMENT GUIDE 10-17-2009
- Page 1 AUTHORIZED DOCUMENTATION Virtual Machine Management Guide Novell ® PlateSpin Orchestrate 2.0.2 November 17, 2009 www.novell.com PlateSpin Orchestrate 2.0 Virtual Machine Management Guide...
- Page 2 Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
- Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
- Page 4 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide...
-
Page 5: Table Of Contents
Contents About This Guide 1 Managing Virtual Machine Hosts Configuring Policies for VM Provisioning Adapters ........9 1.1.1 Configuring Policies for Virtual Center . - Page 6 5.2.2 How Autoprep Works ..........45 Known Autoprep Limitations .
-
Page 7: About This Guide
We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html (http:// www.novell.com/documentation/feedback.html) and enter your comments there. - Page 8 For the most recent version of this guide, visit the PlateSpin Orchestrate 2.0 documentation Web site (http://www.novell.com/documentation/ps_orchestrate20/). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark.
-
Page 9: Managing Virtual Machine Hosts
Managing Virtual Machine Hosts ® After installing the PlateSpin Orchestrate Agent on the physical resource, you can discover for the hypervisor technology residing on the resource by editing the appropriate policies and running the Discover VM hosts job. Later on, you can discover and manage VMs residing on the VM hosts. These launch the adapter job to connect to the appropriate hypervisor Web service. - Page 10 NOTE: In the 2.0.2 release of PlateSpin Orchestrate, the VMware Virtual Center Provisioning Adapter supports only VMware Virtual Center 2.x. Virtual Center 1.x is not supported in this release. The JREs that ship with Virtual Center and with the Orchestrate Agent are version 1.5. Version 1.4.2_15 can be downloaded from the Sun* Download Center (https://sdlc4a.sun.com/ECom/ EComActionServlet;jsessionid=88B0E4E7E868F2F6C671427ACC9C0D13).
- Page 11 Policy Name Explanation Additional Details vcenter1x Contains the constraints used You must configure the following facts in the to select the vCenter 1.x Server policy before running any job for the vCenter resources. 1.x servers: webservice_url webservice_user webservice_password Additionally, you can configure the following facts depending upon your requirements: joblet.maxwaittime timeout...
-
Page 12: Configuring Policies For Xen 3.0
NOTE: VM host discovery on the vcenter adapter can fail because VM host discovery with Virtual Center requires JRE 1.4.2 for VCenter 1.x and JRE 1.5 for VCenter 2.x to be installed on the Windows-based Virtual Center host. The JRE that ships with the Orchestrate Agent and with VMware* Virtual Center is v1.5. -
Page 13: Configuring Policies For Hyper-V
Policy Name Explanation Additional Details vmserverDiscovery Contains settings required to discover the Edit the policy only if the VMware VMware Server host machines. It also Server is not installed in the contains the default installation path of the default path. VMware server. -
Page 14: Configuring Policies For Esx
1.1.5 Configuring Policies for ESX Before provisioning and managing the ESX provisioning adapter, you must configure certain policies in the Development Client. The following table provides detailed information about the policies associated with the ESX provisioning adapter that are used to manage the ESX hosts and VMs in the grid. -
Page 15: Discovering Vm Hosts And Repositories
3 To customize the Web service credentials, edit the resoruce.webservice_user.override and resource.webservice_password.override facts. (To edit a fact, click the fact, click the Edit the fact icon, make the necessary changes, then click OK.) 4 To customize the VM credentials for installing the Orchestrate agent, edit the resource.root_user.override and the resource.root_password.override facts. -
Page 16: Discovering Vm Images
1.3 Discovering VM Images To discover the VM images on a specific repository: 1 In the Development Client, click Provision > Discover VM Images. The Discover VM Images dialog box is displayed. 2 In the Provisioning Adapter drop-down list, select the provisioning adapter for which you want to discover the VM images. -
Page 17: Shutting Down Vm Hosts
2 In the Source VM Hosts pane, select the VM hosts to be resynchronized, then click Add. The selected VM hosts are added to the Target VM Hosts pane. 3 Click OK. 1.5 Shutting Down VM Hosts To shut down a single VM host: 1 In the Development Client, right-click the VM host you want to shut down, then click Shutdown. -
Page 18: Restarting Vm Hosts
1.6 Restarting VM Hosts To restart a single VM host: 1 In the Development Client, right-click the VM host you want to start, then click Start. To restart multiple VM hosts: 1 In the Development Client, click Provision > Start VM Hosts. The Start VM Hosts dialog box is displayed. - Page 19 Orchestrate Server Behavior when the VM Host Loses Its Agent Connection Table 1-6 Scenario Failover Behavior Scenario 1: The VM image is: The VMs that had been running on the failed VM host are re-provisioned to other available VM hosts. stored on a non-local repository (for example, the zos repository) If the VM was provisioned from a template, there is...
- Page 20 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide...
-
Page 21: Managing Virtual Machines
Managing Virtual Machines ® Review the following sections for information about the ongoing tasks in PlateSpin Orchestrate VM Management: Section 2.1, “Provisioning a Virtual Machine,” on page 21 Section 2.2, “Managing a Virtual Machine in Runtime,” on page 22 Section 2.3, “Resynchronizing the State of All VMs,” on page 29 Section 2.4, “Resynchronizing the State of All VMs of a Specific VM Host,”... -
Page 22: Managing A Virtual Machine In Runtime
2.2 Managing a Virtual Machine in Runtime There are many ways you can control the VM after it has been deployed. All actions from provisioning to shutting down the VM can be managed directly from the Orchestrate Development Client and through the jobs written and executed by the Orchestrate Server. Review the following sections for ways to manage VMs in runtime: Section 2.2.1, “Using the Right-Click Menu for Provisioning Actions,”... - Page 23 Action Description Migrate vCenter: Migrates the VM from one host machine to another only if both the source and destination host machines have VMotion enabled. VM migrations can be of the following types: A “warm migrate” is the migration of a suspended VM to another host and starting it there with brief resulting downtime (measured in milliseconds).
- Page 24 Action Description Move Disk Images A “move” is the relocation of VM disk images between two storage devices when the VM is in a not running state (including VMs that are suspended with a checkpoint file). This function does not require shared storage;...
-
Page 25: Prerequisites For Performing Provisioning Actions On Esx Vms
Action Description Personalize Allows you to customize the VM. This includes changing elements like the DNS server. The changes are made to a VM that is shut down. IMPORTANT: If you stop or cancel a running Personalize job, the VM is locked and you cannot provision the VM. - Page 26 4 Click Jobs > vmDiskLibDiscovery to view the job execution details on all the resources within the grid. The job execution details are displayed in the Joblet tab. 5 Click the Resources tab to view the resources that have the Virtual Disk Development Kit. For the ESX on Windows, the following facts are automatically configured: resource.vmware.disklib with the value set to true.
-
Page 27: Releasing A Virtual Machine From Usage
2.2.3 Releasing a Virtual Machine from Usage When the demand and load on your data center decreases, the Orchestrate Server analyzes the remaining resources and releases the most appropriate resource. If a VM meets the requirements of the remaining job demands better than a physical machine, the physical machine is released before the VM is released. -
Page 28: Managed Virtual Machine Actions
2.2.5 Managed Virtual Machine Actions You can perform many actions on the VM through the Orchestrate Development Client and the Orchestrate VM Client or you can write jobs to have actions performed on the VMs in your data center. The following table lists the managed VM actions that you can perform or use in a written job. -
Page 29: Resynchronizing The State Of All Vms
2.3 Resynchronizing the State of All VMs To manually verify and ensure that the state of the VMs of all VM hosts displayed in the Orchestrate Development Client is accurate: 1 In the Orchestrate Development Client, click Provision > Resync VM’s State. The Resync VM’s State dialog box is displayed. -
Page 30: Destroying And Deleting A Virtual Machine
2 You can choose to shut down the VMs after the Orchestrate Agent becomes idle or to immediately shut down the VMs. By default, the Wait for Agent to become Idle option is selected. 3 In the Source VMs pane, select the VMs you want to shut down, then click Add. The selected VMs are added to the Target VMs pane. -
Page 31: Managing Vm Repositories
Managing VM Repositories PlateSpin Orchestrate uses the Repository object to represent where VMs are stored. VMs can be stored on local disks, the Orchestrate datagrid, a network attached storage (NAS), a storage area network (SAN), or by using a separate VM technology. Before VMs can be used by PlateSpin Orchestrate, you must create Repository objects and then discover the VM Images within the Repository: Section 3.1, “Deploying a VM to the Local Repository,”... -
Page 32: Deploying A Vm To The Datagrid Repository
3.2 Deploying a VM to the Datagrid Repository By default, a datagrid repository named is automatically created. The datagrid repository represents VMs residing in the PlateSpin Orchestrate datagrid, which is a storage area on the Orchestrate Server. datagrid repository has a location of , which points to an area in the datagrid grid:///vms reserved for VM archival storage. -
Page 33: Virtual Repository
3.5 Virtual Repository A Virtual Repository is where PlateSpin Orchestrate assumes the VM store is handled by the underlying VM technology. For example, the Virtual Repository is used by the Virtual Center adapter because Virtual Center is managing the VM storage. Managing VM Repositories... - Page 34 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide...
-
Page 35: Troubleshooting Provisioning Actions
Troubleshooting Provisioning Actions The following sections provide solution to the problems you might encounter while performing provisioning actions: “The vCenter provisioning adapter for vCenter 1.x does not work properly if the vcenter_client1x policy is not configured with the Java (JRE) 1.4.2 path” on page 35 “After installing the Orchestrate Agent on VM, the VM is not displayed as a resource in the Orchestrate Development Client”... - Page 36 If JRE 1.5 is installed with the Orchestrate Agent, the default location of the JRE on Windows is c:\program files\novell\zos\agent\jre After installing the Orchestrate Agent on VM, the VM is not displayed as a resource in the Orchestrate Development Client Source: The PlateSpin Orchestrate Development Client.
- Page 37 Action: Do the following: 1 Disconnect and remove one of the ESX hosts from the vCenter server. 2 Move or migrate the VMs by using the Orchestrate Development Client. Moving a VM from one ESX host local storage to another ESX host local storage might fail Source: The PlateSpin Orchestrate Development Client.
- Page 38 A VM host cannot provision a VM that has a different file system than the VM host. The currently supported file systems are ext2, ext3, reiserfs, jfs, xfs, vfat, and ntfs. Action: To work around the issue load the VM’s file system Linux module on the VM host, or add this support to the Linux kernel if a custom kernel is being used.
- Page 39 To uncomment a section of code, remove the “<!--” (comment open) tag and the “-->” (comment close) tag. Edit the fact to set xend-domain-lock-path an alternate location on shared storage that is available to all VM hosts. When you make the changes and save the file, the facts become active and the VM locking parameters of each newly-joining VM host are adjusted accordingly.
- Page 40 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide...
-
Page 41: Understanding Autoprep
Understanding Autoprep ® In the PlateSpin Orchestrate Development Client, “Autoprep” refers to the function of preparing unique network settings for Linux VMs on VM hosts so that the VMs can be provisioned by the provisioning adapter without creating network conflicts. As the administrator, you can set “facts” in the PlateSpin Orchestrate Development Client that can later be automatically applied to a VM clone during a Provision or a Clone action from a VM template. -
Page 42: Setting Linux Autoprep Config Facts
The Autoprep Sections of the Info/Groups Page of a VM Template Object Figure 5-1 NOTE: Windows Sysprep Config is not supported in PlateSpin Orchestrate 2.0.2. The fact settings for each of these panels are discussed below. Section 5.1.1, “Setting Linux Autoprep Config Facts,” on page 42 Section 5.1.2, “Setting Autoprep Network Adapter Facts,”... -
Page 43: Setting Autoprep Network Adapter Facts
Linux Domain: The fact name for this setting is resource.provisioner.autoprep.linuxglobal.Domain The string value you enter here becomes the network domain name where the new VM is a member. 5.1.2 Setting Autoprep Network Adapter Facts The PlateSpin Orchestrate Development Client supports creating network settings (facts) for two network interfaces or “adapters”... -
Page 44: Applying Autoprep Facts
resource.provisioner.autoprep.adapters[1].subnetMask The string value you enter here becomes the network subnet mask for the specified adapter. The setting is ignored if the Use DHCP check box is selected. Gateway IP Address: The fact name for this setting is resource.provisioner.autoprep.adapters[0].Gateways resource.provisioner.autoprep.adapters[1].Gateways This is a list of Internet gateways that are available to the network adapter. -
Page 45: Example Autoprep Scenarios
5.2.1 Example Autoprep Scenarios Scenario 1: You want to create 25 dynamic VM instances to test job provisioning. You will never use these instances again, so you will not personalize them. You create a VM template by right-clicking a VM, then you select Create Template. When the VM Template is created in the Explorer Tree, you define its Autoprep facts in the Info/Groups page by entering an asterisk in the MAC Address field, and then you select the Use DHCP check box. -
Page 46: Known Autoprep Limitations
5.3 Known Autoprep Limitations There are some limitations that you need to be aware of when you use Autoprep: Currently, the Gateway IP Address setting under the Autoprep Network Adapter 0 and the Autoprep Network Adapter 1 sections of the Info/Groups tab for a VM object and VM template object is available in a list box. -
Page 47: A Virtual Machine Technologies And Actions
Virtual Machine Technologies and Actions ® The tables in this section contain information about the different PlateSpin Orchestrate VM Management technologies, PlateSpin Orchestrate provisioning adapters, and actions you can perform on and with a VM. This section contains the following: Section A.1, “Virtual Machine Technologies,”... - Page 48 V technology available and enabled. 2 The vcenter provisioning adapter does not support VMware Virtual Center 1.x. The vmserver provisioning adapter does not work with the VMware Server 2.x hypervisor. Novell considers the PlateSpin Orchestrate provisioning technology used in conjunction with VMware Server as “experimental”...
-
Page 49: Xen Hypervisor On Sles 10 Sp2 Or Sles 11 Host
A.2 Xen Hypervisor on SLES 10 SP2 or SLES 11 Host The Xen hypervisor runs on SLES 10 SP2 and SLES 11 host machines with the PlateSpin Orchestrate Xen Provisioning Adapter (xen30). The following table represents the PlateSpin Orchestrate VM actions and whether or not PlateSpin Orchestrate can perform that action on the guest operating system. -
Page 50: Additional Xen Provisioning Adapter Information
A.2.1 Additional Xen Provisioning Adapter Information The following characteristics were added to the Xen Provisioning Adapter, effective with the 2.0.2 release: The VM Builder running on a SLES 11 VM host now supports three additional VM OS types: openSUSE 11 SLED 11 SLES 11 These OS types are not available for build when you use the VM Builder running on a SLES 10... -
Page 51: Additional Vmware Virtual Center Provisioning Adapter Information
PlateSpin Orchestrate SLES 8 SLES 9 SLES 10 RHEL 4 RHEL 5 Other Linux Windows Managed VM Action Resume Create Template Move Disk Image Hot Migrate Warm Migrate Checkpoint Restore Install Orchestrate Agent Make Standalone Check Status Save Config Cancel Action Check Host Assignment Launch Remote Desktop NOTE: Host operating systems are dependent on the VMware Virtual Center support matrix. -
Page 52: Microsoft Hyper-V Hypervisor
If you have installed Vcenter in a location other than those listed as default in the policy file, you can copy one of the three existing values, modify the path to point to their installation listelement location for the process, and then append this new item to the end of the vpxd.exe list. -
Page 53: Vmware Esx Vm Hypervisor (Experimental)
The following table represents the PlateSpin Orchestrate VM actions and whether or not PlateSpin Orchestrate can perform that action on the guest operating system. NOTE: Novell considers the PlateSpin Orchestrate provisioning technology used in conjunction with VMware ESX as “experimental” because it has not yet been fully tested. - Page 54 PlateSpin Orchestrate Managed Windows SLES 9 SLES 10 RHEL 4 RHEL 5 VM Action 2003 Pause Resume Suspend Shutdown Shutdown Agent Restart Move Disk Image Hot Migrate Warm Migrate Resync State Save Config Apply Config Create Template Delete / Destroy Resource Checkpoint Restore Remove Template Dependency...
-
Page 55: B Documentation Updates
Documentation Updates This section contains information about documentation content changes that were made in this PlateSpin Orchestrate Virtual Machine Management Guide after the initial release of PlateSpin Orchestrate 2.0. The changes are listed according to the date they were published. The documentation for this product is provided on the Web in two formats: HTML and PDF. - Page 56 Location Update Section 1.1.1, “Configuring Policies for Added important note to alert users about limitation of one Virtual Center,” on page 9 Virtual Center Server installation per PlateSpin Orchestrate grid. Chapter 4, “Troubleshooting Provisioning Added a new section, “Multiple instances of the same Xen Actions,”...