VMware

VMware Lifecycle Manager 1.0.1 Release Notes

Note: Lifecycle Manager 1.0.1 (LCM) works with VirtualCenter 2.x and VirtualCenter 2.5 update 2. It is not compatible with VirtualCenter 2.5 and VirtualCenter 2.5 update 1.

VMware Lifecycle Manager 1.0.1| 15 SEPT 2008 | Build 3668

Check frequently for additions and updates to these release notes.


These release notes cover the following topics:

What's New

This section describes the enhancements available in Lifecycle Manager 1.0.1:

Initial Configuration of LCM

LCM Approver and LCM IT Staff can overwrite the existing virtual machine name.

Catalog View

The following filters have been added to simplify the search for existing virtual machines:

  • All
  • All available VMs
  • Rejected
  • Decommissioned
  • Canceled
  • Waiting for approval
  • Waiting for placement
  • Errors

Snapshot

When you click Snapshot, you need to enter a name and description of the snapshot before the confirmation message appears. The name and description of the previous snapshot appears next to the Revert to snapshot link.

Request view

  • The following filters have been added to simplify the search for existing virtual machines:
    • All
    • All request
    • Waiting for approval
    • Waiting for placement
    • Waiting for creation

Approval/Placement view

  • In the Placement view, a new pane called Customization Information has been added. Here, customization information is displayed if the request is waiting for placement or change approval.
  • In the Placement view, a new pane called Infrastructure Elements for Criteria has been added. Here, the criteria that are mapped to each infrastructure element is displayed. This pane provides an overview of the available criteria before you click Setup to complete the placement process.
  • In Validate request, you can validate the successful creation of a virtual machine in VirtualCenter, if there was an error as part of the LCM provisioning process. The request with errors appears under the Placement view where you can complete the validation.
  • In Retry action, you can run a failed provisioning attempt again.

Configuration view

  • The IP address can be added as a meta tag in the body of an email notification.
  • In the Custom elements view, application logos have a size limit. If you insert an image that too big, it is resized.

Administration view

In the workflow that relinks a request, when you click Submit, all virtual machines attached to this request are relinked.

Policy view

  • If you retry archiving and deletion tasks, the workflow knows whether the error occurred in archiving or deletion. For example, if there was a deleting error, the workflow retries only the deletion task.
  • Before you relink a virtual machine, all requests can be checked to determine whether each request is always linked with its virtual machine. For example, if the virtual machine of a request exists in VirtualCenter and if the virtual machine has always the same ID, this virtual machine is not unregistered and reregistered.

Other Changes

  • In the email address check, in the email address field, if you enter username@vmware (without the .com), when you click on Next or Submit, a message tells you that this address is not valid.
  • The memory limit check requires that you enter the memory limit that is a multiple of 4.
  • Mozilla Firefox 3 is experimental in this LCM release.

Top of Page

 

Prior Releases of VMware Lifecycle Manager

To view release notes for the version 1.0 release of Lifecycle Manager, click this link:
Lifecycle Manager 1.0

Top of Page

Linux Installer

VMware Lifecycle Manager 1.0.1 is not officially supported on Linux platforms. However, an installer is provided on an experimental basis for Ubuntu Linux 7.04.

Installing LCM 1.0.1 on Ubuntu Linux

You can install LCM using on Ubuntu Linux 7.04 in one of the following ways:

To install LCM with a graphical environment (X server)

  1. Ensure that the LCM Linux installer .bin file has the correct execution rights:
    chmod +x <binary file>
  2. Execute the binary file by double-clicking on it or running it from the command line.
  3. Follow the instructions from the installation Wizard.

To install LCM on a command line-only system

  1. Make sure the LCM Linux installer .bin file has the correct execution rights:
    chmod +x <binary file>
  2. Enter the following at the command line:
    ./<binary file> -i silent

LCM is installed in /opt/vmo. This is currently the only way to install using the command-line-only installer. If the current working directory does not have enough disk space, you may need to specify a temp directory. To specify a temp directory, use the following command.

export IATEMPDIR=<path>

For example, if your path is /opt/tmp, your path would be as follows.

export IATEMPDIR=/opt/tmp

Top of Page

Known Issues

The following issues have not yet been resolved in LCM:

  • If the connection to LDAP is lost, LCM Webviews do not display elements with authorization elements.
  • When you use Mozilla Firefox 3, the initial view in the Web UI does not display correctly. If you click this view, it displays correctly.
  • In VirtualCenter 2.0, when you use a Windows 32-bit template from the Virtual Machine Library and you configure LCM to provide users with guest virtual machines and fixed IP @, dns, and ActiveDirectory, the guest machines cannot join the domain and the request times out.
  • LCM placement operation works with templates with only one NIC.
  • In the Orchestrator Configurator, if you switch from ActiveDirectory to LDAP, an unrecoverable error occurs.
  • In LCM, on the Login/Credential page, if you enter the domain information and click Submit and click Edit, the login credentials appear. If you log out of LCM and log in with the same user and return to this page, the credentials do not appear.
  • If you install LCM on a box with two IP addresses on two different subnets, LCM only replies on port 8080 to the IP address you selected in the Orchestrator Configurator in the Networking view and not to any other IP address.
  • If the primary LDAP host shuts down, and you try to log in to LCM, a Loading... message appears on the page for about 10 minutes and a blank Web page appears.
  • After you choose Configuration > Edit mail notifications and enter an email address, when you press Tab, an update occurs. After you re-enter the address to confirm the entry, no update occurs. When you re-enter the email address for the next role and press Tab, an update occurs but first email field turns red. After you enter the email address twice and click Next, the check is successful.
  • In Edit custom element, when you create a new custom element and try to edit it, a null string appears in the right pane.
  • After you deploy a new virtual machine and power it on, the CPU and memory counters and the graphs appear but if the appliance is rebooted, they do not reappear.
  • In LCM, in the Catalog view, if you select a virtual machine that is powered off, the Connect and Open console options in the right pane can be clicked. If these buttons are clicked, error messages appear.
  • When you log in to LCM as an IT Admin, and you click the Catalog or Request views, a message about problems with the script on the page appears. You can change the Windows registration table on the machine where Microsoft Internet Explorer is used by doing the following:
    1. Using a Registry Editor such as Regedt32.exe, open this key:
      HKEY_CURRENT_USER\Software\Microsoft\InternetExplorer\Styles
      If the Styles key is not present, create a new key called Styles.
    2. Create a new DWORD value called MaxScriptStatements under this key and set the value to the desired number of script statements.
    3. Set its value as 0xffffffff (Hexadecimal). By default the key does not exist.
    4. Save the registration table and close it.
    5. Restart Internet Explorer.
  • Logging in or logging out of the Orchestrator Configurator can trigger HTTP Error 403 User not in required role message. You need to open Orchestrator Configurator again from the Start menu.
  • The default configuration for Orchestrator is different in the LCM Appliance and Windows installations for https port. By default, the LCM Appliance uses 443, but the Windows installation uses 8081.
  • The Orchestrator Configurator server uses port 3944 for HTTP connections.
  • When you open the LCM installer, the Choose Alias, Link, and Shortcut Folder dialog box has radio buttons in which you can select where you want icons in locations such as the Start menu, the desktop, quickLaunch, and new program group. The dialog box is predefined, so there is no option to define radio button or check boxes.


Top of Page

Resolved Issues

The following issues have been resolved in LCM:

  • When naming virtual machines, use names without apostrophes. The virtual machine will not display for mapping.
  • You can now use SUSE 10.2 with LCM to clone Linux virtual machines.
  • When you edit a template profile and select a new template, the template profile links to the newly selected template.
  • Credential modification for an LCM policy was removed and is not needed to use LCM.
  • A timeout length field has been added to the LDAP view in the Orchestrator Configurator in which you can enter the timeout length (in seconds) for the host. The default timeout is 20 seconds.
  • When you request an extension or customization change for your provisioned virtual machine while it is in the “Available” state, and you click on the request, the Decommission button no longer disappears.
  • You can now delete requests with a control group.
  • During automatic placement, if you request a virtual machine with a size is larger than what is available on the datastore, automatic placement does not complete successfully. IT Staff is notified that this machine needs to be manually placed. Space has to be frozen on the selected datastore, or this machine has to be placed in another location.
  • In the Criteria view, you can only add criteria using alphanumeric characters.
  • You can decommission a virtual machine with the archiving feature disabled.
  • When creating a network subnet, you must enter text in the description field. If this field is left empty, an error occurs.
  • The archiving process now checks the free space in the datastore before archiving.
  • You can now have an IP range and DHCP on the same VirtualCenter network.
  • If you manually change the name of an virtual machine in LCM, the initial name (as created by LCM) appears in the Catalog view. If you select this name, the details about this virtual machine appear on the right pane, including the name of the virtual machine and the changes that were made in VirtualCenter.
  • Virtual machines are now decommissioned on the date and time specified by the user.
  • LDAP does not time out with a large ActiveDirectory (50,000 users). LCM no longer times out with large directory structures.
  • When the configured ActiveDirectory is down, if the host is reachable, the LDAP page in the Orchestrator Configurator successfully loads.
  • After installation, the log level displayed on the configuration is the same as the one configured in the log4j. The log4j.dtd file was copied from the apps directory to the configuration/jetty directory.

Top of Page