Cloud Manager 2.5.1 Patch 4 Release Notes
Cloud Manager 2.5 Support Pack 1 Patch Update 4 (2.5.1 Patch 4) resolves several issues for Cloud Manager 2.5.1. This patch is cumulative. It includes hotfixes and patches that have been provided since the Cloud Manager 2.5.1 release.
The documentation for this product is available in HTML and PDF formats at the Cloud Manager 2.5 Documentation website.
11.0 Supplemental Documentation
This section provides documentation and procedures for new features and tools provided in patches for Cloud Manager 2.5.1.
11.1 Using SQL Scripts to Fix Workloads in a State of Disk Inconsistency
Cloud Manager Application Server 2.5.1 Patch 3 and Patch 4 provide SQL scripts to help you locate VMs that have inconsistent disks and to correct the disk information stored in the database for each VM by swapping the disk information reported for its non-zero-size CDROM and its no-size hard disk.
|
SQL Script |
Description |
|---|---|
|
query_01_find_bad_cdroms_with_size.sql |
Run the script to get a list of disk IDs for CDROMs that currently have a non-zero disk size. Results are output to the text file you specify in the query, such as D:\results.txt. |
|
query_02_find_list_of_disks_for_the_wl_that_a_disk_is_in.sql |
You set the disk ID of a CDROM with a non-zero disk size as the value for the disk_data_id parameter in the script. Run the script to get a list of information about other disks on the CDROM’s parent VM. |
|
query_03_find_list_of_disks_for_the_wl_template_that_a_disk_is_in.sql |
You set the disk ID of a CDROM with a non-zero disk size as the value for the disk_data_id parameter in the script. Run the script to get a list of information about other disks on the workload template that was used to create the CDROM’s parent VM. |
|
sr411_fix_swapped_disk_cdrom_with_size_with_disk_with_no_size.sql |
Fixes values for one current problem VM at a time. You set the disk ID of a CDROM with a non-zero disk size as the value for the temp_disk_data_id parameter in the script. Run the script to swap the disk information of the CDROM and a hard disk with no size on the CDROM’s parent VM. |
|
sr411_fix_swapped_disks_cdrom_with_size_with_disk_with_no_size.sql |
Fixes values for all current problem VMs in a single run. After you output a list of disk IDs for CDROMs with non-zero sizes in a results.txt file, run the script to swap the disk information for the CDROM and the hard disk with no size on each CDROM’s parent VM, where each disk entry in the file is processed in turn. |
To fix all VMs that currently have swapped information for their CDROMs and hard disks:
-
Run the following SQL query to identify the CDROMs in the database that have a non-zero disk size and return their disk IDs to a file named results.txt.
query_01_find_bad_cdroms_with_size.sql
For example, if you extracted the scripts in the D:\sr411\sqlscripts\ directory, enter
psql -U postgres -o D:\results.txt tietodb < D:\sr411\sqlscripts\query_01_find_bad_cdroms_with_size.sql
-
Run the following SQL script to fix the CDROM and hard disk that have been swapped on the parent VM of each disk ID entry in the results.txt file.
sr411_fix_swapped_disks_cdrom_with_size_with_disk_with_no_size.sql
For example, enter
psql -U postgres tietodb < D:\sr411\sqlscripts\sr411_fix_swapped_disks_cdrom_with_size_with_disk_with_no_size.sql
To fix a single VM that currently has swapped information for its CDROM and hard disk:
-
Run the following SQL query to identify the CDROMs in the database that have a non-zero disk size and return their disk IDs to a file named results.txt.
query_01_find_bad_cdroms_with_size.sql
For example, if you extracted the scripts in the D:\sr411\sqlscripts\ directory, enter
psql -U postgres -o D:\results.txt tietodb < D:\sr411\sqlscripts\query_01_find_bad_cdroms_with_size.sql
-
For each disk ID entry in the results.txt file:
-
Open the following SQL script in a text editor, then set the disk ID as the value for the temp_disk_data_id parameter.
sr411_fix_swapped_disk_cdrom_with_size_with_disk_with_no_size.sql
-
Run the script to fix the CDROM and hard disk that have been swapped on the parent VM of the specified disk ID.
For example, enter
psql -U postgres tietodb < D:\sr411\sqlscripts\sr411_fix_swapped_disk_cdrom_with_size_with_disk_with_no_size.sql
-
Repeat Step 2.a and Step 2.b for each disk ID entry in turn.
If you are using the single-VM-at-a-time process only to verify the outcome, remove the disk IDs for the corrected CDROMs from the results.txt file, then run the script for fixing all entries in a single run. See Step 2 in the fix-all procedure.
-
11.2 Configuring Maximum Number of VMs for a Business Service
Cloud Manager 2.5.1 Patch 2 provides a new option that enables you to configure a global setting for the number of workloads you can assign to a Business Service.
You can limit the number of VMs allowed to be configured for a Business Service by setting a global system setting in the System Configuration dialog. The default value is 1000. This value is intentionally set to a high value to allow any practical number of VMs to be added to a Business Service.
Setting a limit is optional. You can specify a smaller value to enforce consistent maximum values and to improve performance in your environment. Specify a value based on your operational needs and performance characteristics of your deployment.
To specify a maximum number of VMs for a Business Service:
-
In the System Configuration dialog, select .
-
Under Business Service Dialog, specify the maximum number of workloads to allow users to configure for each Business Service.
-
Click to apply the setting.