1.1 Configuring Policies for VM Provisioning Adapters

This section contains information on the policies required to manage the Provisioning adapters. Provisioning adapters are programs that provision (start, stop, snapshot, migrate, or pause) a VM. They run just like regular jobs on the PlateSpin Orchestrate Server.

1.1.1 Configuring Policies for Virtual Center

Before provisioning and managing the Virtual Center provisioning adapter, you must configure certain policies in the Development Client. However, before configuring the policies for the Virtual Center, make sure that the following prerequisites are met:

  • Make sure that the Orchestrate Agent for Windows* is installed and started on the Windows host running Virtual Center.

    IMPORTANT:The PlateSpin Orchestrate Server supports only one VMware Virtual Center server per grid.

  • Make sure that J2RE with version 1.4.2 for VCenter 1.x or version 1.5 for VCenter 2.x is installed on the Windows system running Virtual Center.

    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.

  • Make sure that the keystore is created on the server where Virtual Center is installed.

    If the keystore is not created, do the following on the server where Virtual Center is installed to generate it

    1. Find the rui.crt certificate.

      On Windows, the default location is: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\rui.crt.

    2. Create a VCenter_Certs directory at the top level by entering mkdir C:\VCenter_Certs\.

    3. Copy rui.crt to C:\VCenter_Certs\.

    4. Run keytool.

      The default location is C:\Program Files\VMware\VMware VirtualCenter 2.0\jre\bin\keytool.exe.

    5. Enter:

      cd C:\VCenter_Certs

      [path]keytool -import -keystore keystore -file rui.crt

    6. Enter a password when prompted.

The following table provides detailed information about the policies associated with the Virtual Center provisioning adapter that are used to manage the Virtual Center hosts and the VMs in the grid. The policy settings are applied to all the Virtual Center VMs in the grid.

Table 1-1 Virtual Machine Management Policies for Virtual Center

Policy Name

Explanation

Additional Details

vcenter

Contains the constraints used to select the vCenter Server resources.

Do not edit the policy.

vcenter1x

Contains the constraints used to select the vCenter 1.x Server resources.

You must configure the following facts in the policy before running any job for the vCenter 1.x servers:

  • webservice_url

  • webservice_user

  • webservice_password

Additionally, you can configure the following facts depending upon your requirements:

  • joblet.maxwaittime

  • timeout

  • debug

vcenter2x

Contains the constraints used to select the vCenter 2.x Server resources

You must configure the following facts in the policy before running any job for the vCenter 2.x servers:

  • webservice_url

  • webservice_user

  • webservice_password

Additionally, you can configure the following facts depending upon your requirements:

  • joblet.maxwaittime

  • timeout

  • debug

vcenter_client1x

Contains the settings used to run only the vCenter job on the associated vCenter resource.

You must configure the following facts in the policy before running any job for the vCenter 1.x servers:

  • java1.4.2

  • vcenter.truststore

  • joblets.slots

vcenter_client2x

Contains the settings used to run only the vCenter job on the associated vCenter resource.

You must configure the following facts in the policy before running any job for the vCenter 1.x servers:

  • java1.5.0

  • vcenter.truststore

  • joblets.slots

vcenterDiscovery

Contains the settings required to discover the vCenter Server host machines. It also contains the default installation path of the vCenter server.

Do not edit the policy.

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.

1.1.2 Configuring Policies for Xen 3.0

Before provisioning and managing the Xen* 3.0 Server provisioning adapter, you must configure certain policies in the Development Client. The following table provides detailed information about the policies associated with the Xen 3.0 Server provisioning adapter that are used to manage the Xen 3.0 Server hosts and VMs in the grid. The policy settings are applied to all the VMs in the grid.

Table 1-2 Virtual Machine Management Policies for Xen 3.0 Server

Policy Name

Explanation

Additional Details

xen30

Contains the policy settings for the Xen 3.0 Server Provisioning Adapter.

By default, the optimal values are configured for the job and joblets in the policy.

xenDiscovery

Contains the settings required to discover the Xen 3.0 Server host machines. It also contains the default installation path of the Xen server.

If the Xen Server is not installed in the default path, edit this policy to provide the correct information.

xenPA

Contains the constraints used to check whether the Xen 3.0 Server host is registered to the Orchestrate Server, and the host is up and running.

Do not edit the policy.

1.1.3 Configuring Policies for VMware Server

Before provisioning and managing the VMware Server provisioning adapter, you must configure certain policies in the Development Client. The following table provides detailed information about the policies associated with the VMware Server provisioning adapter that are used to manage the VMware Server hosts and VMs in the grid. The policy settings are applied to all the VMware Server VMs in the grid.

Table 1-3 Virtual Machine Management Policies for VMware Server

Policy Name

Explanation

Additional Details

vmserver

Contains the policy settings for the VMware Server provisioning adapter.

By default, the optimal values are configured for the job and joblets in the policy.

vmserverPA

Contains the constraints used to check whether the VMware Server host is registered to the Orchestrate Server, and whether the host is up and running.

Do not edit the policy.

vmserverDiscovery

Contains settings required to discover the VMware Server host machines. It also contains the default installation path of the VMware server.

Edit the policy only if the VMware Server is not installed in the default path.

1.1.4 Configuring Policies for Hyper-V

Before provisioning and managing the Hyper-V provisioning adapter, you must configure certain policies in the Development Client. The following table provides detailed information about the policies associated with the Hyper-V provisioning adapter that are used to manage the Hyper-V hosts and VMs in the grid. The policy settings are applied to all the Hyper-V VMs in the grid.

Table 1-4 Virtual Machine Management Policies for Hyper-V

Policy Name

Explanation

Additional Details

hyperv

Contains the policy settings for the Hyper-V provisioning adapter

By default, the optimal values are configured for the job and joblets in the policy.

hypervDiscovery

Contains the settings required to discover the Hyper-V host.

Do not edit the policy.

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. The policy settings are applied to all the ESX VMs in the grid.

Table 1-5 Virtual Machine Management Policies for ESX

Policy Name

Explanation

Additional Details

esx

Contains the policy settings for the ESX provisioning adapter.

You must configure the following facts in the policy before running any job for the ESX VM hosts:

  • webservice_user

  • webservice_password

  • root_user

  • root_password

Additionally, you can configure the following facts depending upon your requirements:

  • joblet.maxwaittime

  • timeout

  • debug

esxPA

Contains the constraints used to check whether the ESX host is registered to the Orchestrate Server, and whether the host is up and running.

Do not edit the policy.

esxServerDiscovery

Contains the settings required to discover the ESX host.

Do not edit the policy.

esxvmPrep

Contains the settings required to perform the Install Agent action and the Personalize Provisioning action.

Do not edit the policy.

esxVncServerConfig

Contains the settings required to perform the Launch Remote Desktop Provisioning action.

Do not edit the policy.

You can customize the facts for a specific ESX VM. This overrides the policy settings configured in the ESX policy of the ESX host on which the VM is hosted.

To customize the facts for an ESX VM, do the following in the Development Client:

  1. Click Resources > Physical.

  2. Click the ESX machine whose policy settings you want to edit.

    The Constraints/Facts tab is displayed by default.

  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.

    This overrides the default values configured in the ESX policy for all the ESX machines at the grid level.