HP Insight Dynamics 6.3 Release Notes

Template containing virtual boot disk shows validation error after upgrade
After upgrading to 6.3, any existing Insight Orchestration templates containing a virtual boot disk
display a validation error for the disk size. The validation error occurs because 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
These templates must be migrated using one of the following two methods:
Suggested action 1
1. From Insight Orchestration Designer, open the invalid template.
2. Right-click the boot disk to open the “Edit Storage Configuration” dialog.
3. Uncheck the “Disk is bootable” checkbox, then check the same checkbox again.
The boot disk size in the template is automatically adjusted to comply with the new virtual disk
conversion factor.
Suggested action 2
If you have a large number of VM templates with validation errors caused by the virtual disk
conversion change:
1. Export the invalid templates using the Insight Orchestration command line interface (CLI). For
more information, see HP BladeSystem Matrix/Matrix Operating Environment 6.3 Integration
Interfaces.
2. Programmatically iterate through each xml file and change the virtual disk size values.
a. Convert the <Size> element values using the following formula:
(6.3 size) = ceiling((6.2 size) * 1000^2/1024^2)
For example, given the following 6.2 virtual disk size as written in the template:
<Size>8193</Size>
<SizeType>MB</SizeType>
The converted 6.3 size is 8193 * 1000^2/1024^2 = 7814.
b. Therefore, change your template to:
<Size>7814</Size>
<SizeType>MB</SizeType>
3. Import the valid templates into Insight Orchestration using the CLI.
Because VSphere uses the base 10 (1000) value instead of the base 2 value (1024), the disk size
displayed in VMware vSphere and Insight Orchestration will not match, although the virtual disk
size is the same.
Delete service request leaves "clean-me" logical servers when used with Integrity servers
if disk is not erased before delete service request
After successfully provisioning a physical Integrity server blade (using Ignite-UX, or through a
secondary CMS in a federated CMS environment), there are manual steps you must perform to
allow the disk to be erased during de-provisioning. Erasing the disk is part of a successful
de-provisioning (delete request) for an Integrity service.
If the disk is not erased, the delete service request may fail and “clean me” logical servers will
remain. In that case, a manual cleanup procedure is required. (See the Suggested action for the
cleanup procedure.)
Before you start a delete service request from Insight Orchestration:
22 Issues and suggested actions