VMware vCenter Chargeback Manager 2.0.1 Release Notes
vCenter Chargeback Manager 2.0.1 | 08 March 2012 | Build 643764
Last Document Update: 08 March 2012
What's in the Release Notes
The release notes cover the following topics:
What's New in this Release
The vCenter Chargeback Manager 2.0.1 includes the following fixes:
Upgraded the Apache Tomcat server to version 6.0.35
Apache Tomcat has been updated to version 6.0.35 to address multiple security issues. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2011-3190, CVE-2011-3375, and CVE-2012-0022 to these issues.
vCenter Chargeback Manager fails to validate XML API requests
vCenter Chargeback Manager contains a flaw in its handling of XML API requests. This vulnerability allows an unauthenticated remote attacker to download files from vCenter Chargeback Manager server or conduct a denial-of-service against the server. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-1472 to this issue.
Upgrade fails with database connection error
If you have installed vCenter Chargeback Manager with a custom database port for connecting to the vCenter Chargeback Manager database, then upgrading such an instance fails even if the custom database port details are provided during upgrade. This custom database port issue is fixed and an existing vCenter Chargeback Manager instance can be successfully upgraded to vCenter Chargeback Manager 2.0.1.
Usage of some of the computing resources are reported as zero
The actual usage values for CPU, memory, disk read and write, and network transmitted and received are reported as zero in the usage and cost reports even if these resources have been consumed by the virtual machines during the specified reporting period. This issue occurs only if the report also includes the data for external network transmit and receive for the org vDCs in vCloud Director. In this release of vCenter Chargeback Manager, this issue is fixed and reports can include the actual usage data for these computing resources along with the external network transmit and receive for data the org vDCs.
Enhancements to the vCloud Director Data Collector
The vCloud Director data collector is enhanced in this release. The unprocessed events that have become invalid due to changes in org vDCs in the vCloud Director or changes in the vCenter Server hierarchy are no longer processed by the data collector. The following unprocessed events are removed from the database:
- vApp modify events received after vApp is deleted from the hierarchy.
- Virtual machine create event received after the vApp is deleted from the hierarchy.
- Virtual machine create event received after the virtual machine is deleted from the vCenter Server.
These enhancements have improved the performance of the vCloud Director data collector.
Enhancements to the VM Instance Cost job
Starting with this release, the VM Instance Cost job checks the hierarchy snapshot history to apply fixed costs on the virtual machines. This ensure that any virtual machine that was created and deleted between two consecutive runs of the VM Instance Cost job is also considered by the job and the appropriate fixed cost is applied on such a virtual machine.
Report schedule generates duplicate reports
In earlier releases, a report schedule might generate duplicate reports and send duplicate emails. When the schedule is triggered, the first report generated is correct, but the duplicate report fails and an erroneous report is generated. This results in the user not being able to access the successfully generated report. This issue is fixed in vCenter Chargeback Manager 2.0.1.
This section provides information about the supported operating systems, database management systems, and vCenter Server versions. The vCenter Chargeback Manager User's Guide provides detailed information about the system requirements for installing and running the application.
Supported Operating Systems
- Microsoft Windows Server 2003 with SP2 (32-bit and 64-bit)
- Microsoft Windows Server 2003 R2 (32-bit and 64-bit)
- Microsoft Windows Server 2008 (32-bit and 64-bit)
- Microsoft Windows Server 2008 R2 (64-bit)
You can install and run vCenter Chargeback Manager on any supported localized Windows operating system. However, all the labels and text messages in the installer and application user interface (including the plug-in in the vSphere Client) are displayed in English only. The application supports ASCII, extended ASCII, and non-ASCII characters. However, the characters are rendered correctly only if the client machine uses the appropriate fonts and the Web browser supports all the characters. The installer does not support all characters. Ensure that the information entered in the installer contains only the supported characters as specified in the install and upgrade instructions in this release notes and in the vCenter Chargeback Manager User's Guide.
Supported Database Management Systems
vCenter Chargeback Manager supports the Standard and Enterprise edition of the following database management systems:
- Microsoft SQL Server 2008 (x64) (with Service Pack 2)
- Microsoft SQL Server 2008 (Intel x86) (with Service Pack 2)
- Microsoft SQL Server 2005 (x64) (with Service Pack 2)
- Microsoft SQL Server 2005 (Intel x86)(with Service Pack 2)
vCenter Chargeback Manager supports the Standard and Enterprise edition of the following database management systems:
- Oracle Database 11g Release 2
- Oracle Database 11g Release 1
- Oracle Database 10g Release 2
- Oracle Database 10g Release 1
Supported vCenter Server Versions and vCenter Server Databases
- VirtualCenter Server 2.5 Update 3
- VirtualCenter Server 2.5 Update 4
- VirtualCenter Server 2.5 Update 5
- VirtualCenter Server 2.5 Update 6
- vCenter Server 4.0
- vCenter Server 4.0 Update 1
- vCenter Server 4.0 Update 2
- vCenter Server 4.0 Update 3
- vCenter Server 4.0 Update 4
- vCenter Server 4.1
- vCenter Server 4.1 Update 1
- vCenter Server 4.1 Update 2
- vCenter Server 5.0
- vCenter Server 5.0 Update 1
Note: vCenter Chargeback Manager only supports vCenter Server databases that are created in Microsoft SQL Server or Oracle Database.
Supported Web Browsers and Flash Player Plug-in
- Microsoft Internet Explorer 7.x, and 8.x
- Mozilla Firefox 4.x and 5.x
- Adobe Flash Player for Windows Plug-in version 10.1
- Adobe Flash Player for Linux version 10.1 (Plug-in for Mozilla Firefox running on Linux Platform)
Supported VMware Cloud Director Versions
- VMware Cloud Director 1.5
vCenter Chargeback Manager 2.0.1 does not support any release of VMware Cloud Director prior to VMware Cloud Director 1.5
Supported VMware vCenter Operations Versions
- VMware vCenter Operations 5.0
vCenter Chargeback Manager 2.0.1 does not support VMware vCenter Operations 5.0.1.
Before you install and use the VMware vCenter Chargeback Manager application, you must perform the following tasks:
- Create a vCenter Chargeback Manager database and database user
You must create a database for vCenter Chargeback Manager to store the application-specific data. Ensure that this database is not configured to be case-sensitive. In addition, you must also create a database user having permissions to create and delete schema, as well as read from and write to the database.
- Set a static IP address on the machine
You must set a static IP address on the machine on which you plan to install vCenter Chargeback Manager. You can obtain a static IP address from your network administrator. Preferably, obtain and set static IP addresses on all the servers and databases that the application will communicate with.
- Ensure that MSI installation is enabled
You must ensure that MSI installation is enabled on the machine. If it is not, you must manually install Microsoft Visual C++ 2005 Redistributable Package (x86) before running the vCenter Chargeback Manager installer.
- Check whether the required ports are free
Ensure that the ports that you specify during the installation are free. While installing vCenter Chargeback Manager, you must specify the port numbers for the HTTP port (default 8080), load-balancer port (default 8009), and HTTPS port (default 443).
- Ensure that port exceptions are configured on Windows Firewall
If Windows Firewall is enabled, you must set port exceptions for the HTTP, load-balancer, and HTTPS ports on the Windows Firewall. If these exceptions are not set, the application will not be usable.
- Ensure that system time of all the servers and databases are in sync
You must ensure that the system time of the machines on which you install vCenter Chargeback Manager and vCenter Chargeback Manager database are in sync. If you plan to install a separate data collector on a different machine, then the system time of this machine must be in sync with that of the other machines.
- Ensure that the Windows user has the Log on as a service permission
If you want to use the Windows Authentication option for the vCenter Chargeback Manager database, you must ensure that the Windows user has the Log on as a service permission. If this permission is not set on the user, the installation fails. Also, the installer must be run in the context of this Windows user.
- Ensure that the SQL Server Browser service is running if you are using a Microsoft SQL Server database and using the database instance name and a dynamic database instance port to connect to the vCenter Chargeback Manager database or vCloud Director database.
- Ensure that the vCenter Chargeback Manager database is case-insensitive.
Download the vCenter-CB-2.0.1-643764.zip file, and extract the contents on to the machine on which you want to install vCenter Chargeback Manager. Do not run the installer from a remote machine. To install vCenter Chargeback Manager:
- Run the vCenter-CB.exe file.
The installation wizard is displayed.
- Click Next on the Introduction screen.
- Accept the end-user license agreement, and click Next.
- Provide the path for the installation directory, and click Next.
Ensure that the installation directory path has at least one directory (for example, C:\vCenterChargeback\) and does not point to just a drive (for example, C:\). If the specified installation directory exists, ensure that it is empty. If the specified installation directory does not exist, the installer will create the directory. Also, the directory path must contain only ASCII characters.
- Configure the following vCenter Chargeback Manager database-related information, and click Next:
If the installer successfully connects to the database, the next screen is displayed.
- Database Type: The type of database used to create the vCenter Chargeback Manager database. This can be either SQL SERVER or ORACLE.
- Database URL: The IP address of the system on which the vCenter Chargeback Manager database is installed along with either the port at which the database listener service is running or the vCenter Chargeback Manager database instance name. The database instance name must contain only ASCII characters.
For Oracle Database, the database URL can be in any of the following formats:
For SQL Server, the database URL can be in any of the following formats:
You can also specify a well formed JDBC URL that starts with 'jdbc' and contains the database name.
- <IP Address>
- <Host Name>
- <IP Address>\<Database Instance Name>
- <Host Name>\<Database Instance Name>
- Database Port: (Optional) The port on which the database service is listening for requests. If the port number is not specified, the installer uses the default port. For an Oracle database, you must specify the TNS listener port if you are not using the default port 1521. For an SQL Server database, specify the database instance port if you are using a static port.
- Database Name: Name of the database in which vCenter Chargeback Manager stores the application-specific data. For Oracle Database, ensure that you provide the service name and not the SID.
- SQL Authentication Mode: This option is applicable only for SQL Server database. For an SQL Server database, the authentication type can be either SQL Server Authentication or Windows Authentication.
- Database Username: The name of the database user. The database user must have privileges to create and delete schema, as well as read from and write to the database. If you select Windows Authentication for SQL Authentication Mode, you must provide the Windows user account name. The
user name must be of the form <Domain_Name>\<User_Name>. The user must have the Log on as a service permission.
- Database Password: Password for the user name that you have provided. If you select Windows Authentication for SQL Authentication Mode, you must provide the password for the Windows user
account. Ensure that the Windows user account password does not contain any special characters. The installer might fail if the password contains special characters.
- Enter the load balancer-related information, and click Next:
If the specified port is free, the next screen is displayed.
- IP Address: Static IP address or the FQDN of the machine on which you are installing the load balancer. Do not use localhost instead of the IP address or FQDN.
- Admin Email Address: Email address of the server administrator. Ensure that the email address contains only ASCII characters.
- HTTPS Port: An unused port through which the Apache Server communicates. The load balancer listens on this port for user requests.
- Select Install vCenter Chargeback Server, enter IP address and port details for the vCenter Chargeback Manager, and click Next:
If the specified ports are free, the next screen is displayed.
- IP Address: Static IP address or the FQDN of the machine on which you are installing vCenter Chargeback Manager. Do not use localhost instead of the IP address or FQDN.
- HTTP Port: An unused HTTP port through which vCenter Chargeback Manager communicates.
- Load-Balancer Port: An unused port through which vCenter Chargeback Manager can communicate with the load balancer (Apache Server).
- Server Instance Name: A user-defined name for the vCenter Chargeback Manager instance. This name is used by the load balancer to identify the instance. Ensure that the instance name contains only ASCII characters.
- Enter a user name and password for the administrative account that will be used to manage the vCenter Chargeback Manager application, and click Next.
The password must be less than or equal to 24 characters in length.
Note: If you are using Oracle Database for your vCenter Chargeback Manager database, ensure that the user name for the administrative account contains only ASCII and non-ASCII characters. Extended ASCII characters in the user name is not supported. This restriction is not applicable if you are using Microsoft SQL Server for you vCenter Chargeback Manager database.
- Select the Install Data Collector option and click Next.
You must have at least one instance of the data collector that is running and registered with the application for the database synchronization jobs to run.
- Review the information displayed on the Pre-Installation Summary screen, and click Install.
The installer starts installing the various components and creating the database schema. If the installation is successful, the URL for accessing the vCenter Chargeback Manager application is displayed.
- Note this URL, and click Done.
The installer displays a dialog stating whether you want to generate your own SSL certificate.
- Click Generate my own SSL Certificate.
A command window is displayed.
An SSL certificate is successfully installed.
- Provide a pass phrase for the default key and press Enter.
You are prompted to enter the pass phrase three more times. Provide the same pass phrase and press Enter each time.
- Provide the required certificate information and press Enter.
You are prompted to enter the following information:
- Country Code: A two letter code for the country.
- State or Province Name: Name of the state or province.
- Locality Name: Name of the city or town.
- Organization Name: Name of the organization.
- Organization Unit Name: Name of the department or organization unit.
- Common Name: Your name.
- Email Address: An email address.
- Provide the requested extra attributes for the certificate and press Enter.
You are prompted to enter the following information:
- A challenge password: A user-defined password.
- An optional company name: Company name. This is optional and can be left blank.
- Provide the pass phrase and press Enter.
You are prompted to enter the pass phrase again. Provide the same pass phrase and press Enter.
- Press any key to complete the process and close the window.
For detailed install instruction, refer to the vCenter Chargeback Manager User's Guide.
Upgrading vCenter Chargeback Manager
You can upgrade an existing vCenter Chargeback 1.5 or later setup to vCenter Chargeback Manager 2.0.1. Refer to the vCenter Chargeback Manager Installation and Upgrade Guide for detailed instructions.
The known issues reported in the vCenter Chargeback Manager 2.0 release are applicable to this release too. To know more about the known issues in vCenter Chargeback Manager 2.0, refer to the vCenter Chargeback Manager 2.0 Release Notes.
Generation of Cost Projection and Cost Optimization reports fails with error for entities having more than 50 characters in their name
vCenter Chargeback Manager fails to generate the Cost Projection and Cost Optimization reports in the Report Dashboard and logs an error similar to the following:
Error while retrieving usage information from VC: 188.8.131.52
Entry "T_Win2K3R2_64 (29e3e78a-3d32-402e-8804-ca8a5e08fd70)" on line 37 column 1 is not within the string sizes 0 - 50
This issue occurs if the name of any entity in the vCenter Server inventory contains more than 50 characters. If the inventory of the vCenter Server, which is integrated with vCenter Operations and is added to vCenter Chargeback Manager, contains any entity, such as ESX hosts, virtual machines, resource pools, and so on, with a name exceeding 50 characters in length, then the Report Dashboard in vCenter Chargeback Manager fails to generate the Cost Projection and Cost Optimization reports for all the entities in the vCenter Server entity. Even if the defaulting entity is not included in any hierarchy in vCenter Chargeback Manager, Cost Projection and Cost Optimization report generation fails for all the other entities from the same vCenter Server that are included in a vCenter Chargeback Manager hierarchy.