HP Insight Dynamics 6.3 Release Notes

Suggested action 1

1. Cancel the Create or Add Server request.

2. Modify the template to remove the HA requirement, or

Modify the template to deselect linked clones and add a cluster disk for each virtual machine.

3. Resubmit the Create request, or

For the Add Server request, delete the existing service and recreate it with the updated template.

Take care to migrate data from the existing service to the new service before deleting the

existing service.

Suggested action 2

Upgrade to Microsoft Hyper-V R2, and specify a Cluster Shared Volume (CSV) instead of a cluster

disk in the template.

Console access to provisioned virtual servers from operating systems and browsers

Launching a console to a provisioned virtual server (VM) hosted on VMware ESX 3.5, ESX 4, ESXi

3.5, and ESXi 4 VM hosts is supported using Microsoft Internet Explorer and Mozilla Firefox

browsers running on Windows XP and Windows 2003 operating systems.

Browsing to user interface requires default Systems Insight Manager port

HP Systems Insight Manager is installed with a default port of 50000 in the JBoss container.

Browsing to the Insight Orchestration user interfaces, for example, Designer, depends on this port

value.

Suggested action

Do not modify the Systems Insight Manager default port of 50000 in the JBoss container.

Operations Orchestration Central and Studio are not localized to Japanese

Operations Orchestration Central and Studio are not localized to Japanese in Insight Dynamics

6.3. Operations Orchestration is available only in English, even when it is installed on a Japanese

CMS.

Minor issues

Virtual disk sizes in IO template and vSphere do not match

In 6.3, Insight Orchestration switched to exposing the virtual disk size using the traditional base

2 definitions of size instead of the base 10 definition.

• For virtual storage in 6.3, MB x 1024 = GB

• For virtual storage in previous versions, and for physical storage, MB x 1000 = GB

VMware vSphere uses the base 10 (1000) value. Insight Orchestration made the change to match

Insight Control virtual machine management and logical server management so that storage

resources would be properly allocated.

When creating a new template in 6.3 Insight Orchestration, use the base 2 definitions to calculate

virtual disk size. The disk size displayed in vSphere and Insight Orchestration will not match,

although the virtual disk size is the same.

For example, given the following 6.2 virtual disk size as written in the template:

The converted 6.3 size is 8193 * 1000^2/1024^2 = 7814.

HP Insight Orchestration 21