VMware vCenter Chargeback 1.5 Release Notes
vCenter Chargeback 1.5 | 08/30/2010 | Build 292472
Last Document Update: 08/30/2010
Check frequently for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
What's New in this Release
vCenter Chargeback 1.5 provides the following new features:
- Hierarchy management tools, filters, and views
This release of vCenter Chargeback allows you to backdate the chargeback hierarchy, view hierarchies in more than one inventory view (Host & Clusters, VM & Templates) per vCenter Server, and highlight vCenter Server entities that have not yet been added to a selected chargeback hierarchy.
- Support for resource allocation on chargeback hierarchical entity
This release of vCenter Chargeback lets you specify allocation units for each computing resource on the entity in a chargeback hierarchy. If a report is generated on the hierarchy using a cost model that has an allocation-based billing policy, vCenter Chargeback accounts for the allocation details set on the entity.
- Auto-Costing for VMware High Availability, VMware Fault Tolerance, and guest operating systems
vCenter Chargeback lets you charge for additional virtual machine configuration parameters. You can now define a set of fixed costs and have vCenter Chargeback automatically assign the appropriate cost based on the guest operating system or level of availability protection (VMware High Availability, VMware Fault Tolerance) configured for the virtual machine.
- Configuring cost at the host and cluster levels
You can now configure costs for the resources at the host and cluster levels. The cost configuration data is then applied to each virtual machine created on the host or cluster.
- Enhanced cost model support
This release adds support for defining one-time costs and overage fees. In addition to hourly rates, you now have the option to define base rates per day, month, and year.
- Support for custom billing policies
This release of vCenter Chargeback lets you create custom billing policies and specify conditions, such as charging based on the power state of virtual machine or billing linked clones.
- New cost analysis dashboard
vCenter Chargeback provides a dashboard that displays cost and usage breakdowns by resource type and business group. The dashboard also lets you identify the N most or least expensive virtual machines and access a list of recent reports.
- Customizable reporting interface
vCenter Chargeback now lets you modify the report view after the report is generated. You can remove rows and columns, and can also rearrange the columns in the generated report.
- Support for generating reports in multiple currencies
This release supports the ability to generate cost summary reports in multiple currency types within a single vCenter Chargeback instance.
- Support for multiple LDAP servers
With this release, you can configure more than one LDAP server in vCenter Chargeback. When logging in to vCenter Chargeback, LDAP users must enter the LDAP code that was provided when configuring the LDAP server.
- Resource-based authorization
Starting with this release, vCenter Chargeback uses resource-based authorization. vCenter Chargeback defines various resource types and authorizes access to a resource based on the role assigned to a user for the resource. A user must have a role assigned to him on the application and for the resources defined in it to enable him to perform any action in the application.
- Full support for vCenter Chargeback APIs
vCenter Chargeback APIs provide an interface to programmatically use the various features of vCenter Chargeback. As an application developer, you can use these APIs to build chargeback applications or integrate vCenter Chargeback with your internal billing systems and compliance policies. This release of vCenter Chargeback adds full support for these APIs.
- Support for VMware Cloud Director
vCenter Chargeback enables the delivery of an integrated pay-as-you-go solution for resource tracking and billing in the cloud. This release of vCenter Chargeback provides two new data collectors: VMware Cloud Director Data Collector and vShield Manager Data Collector. These data collectors integrate vCenter Chargeback with VMware Cloud Director and vShield Manager. This release includes support for the following features:
- Support for VMware Cloud Director resource abstractions and resource management models: Reservation Pool, Allocation Pool, and Pay-As-You-Go.
- Automated creation of chargeback hierarchies mapping to organizations, virtual datacenters, and vApps defined within VMware Cloud Director.
- Metering and charging for allocation and usage of VMware Cloud Director resources, including virtual datacenters, vApps, templates and media file storage.
- Metering and charging for external network bandwidth, network count, and network services, such as DHCP, NAT, and firewall.
- Delivery of targeted multi-tenant chargeback reports.
This section provides information about the supported operating systems, database management systems, and vCenter Server versions. The vCenter Chargeback 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 R2 (32-bit and 64-bit)
You can install and run vCenter Chargeback 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. Also, users must enter only ASCII and extended ASCII characters. The application does not recognize non-ASCII characters.
Supported Database Management Systems
- Microsoft SQL Server 2005 (Standard and Enterprise)
- Microsoft SQL Server 2008 (Standard and Enterprise)
- Microsoft SQL Server 2005 Express
- Oracle Database 10g (Standard and Enterprise)
- Oracle Database 11g (Standard and Enterprise)
Supported vCenter Server Versions
- 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.1
Supported Web Browsers and Flash Player Plug-in
- Microsoft Internet Explorer 7.x, and 8.x
- Mozilla Firefox 3.1 and above
- 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.0
Before you install and use the VMware vCenter Chargeback application, you must perform the following tasks:
- Create a vCenter Chargeback database and database user
You must create a database for vCenter Chargeback to store the application-specific data. 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. 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 installer.
- Check whether the required ports are free
Ensure that the ports that you specify during the installation are free. While installing vCenter Chargeback, 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 and vCenter Chargeback 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 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 database.
- Ensure that the vCenter Chargeback database is case-insensitive.
Download the vCenter-CB-1.5.0-292472.zip file, and extract the contents on to the machine on which you want to install vCenter Chargeback. Do not run the installer from a remote machine. To install vCenter Chargeback:
- 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:\vCenterChargeback10\) 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.
- Configure the following vCenter Chargeback 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 database. This can be either SQL SERVER or ORACLE.
- Database URL: The IP address of the system on which the vCenter Chargeback database is installed along with either the port at which the database listener service is running or the vCenter Chargeback database instance name.
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:
- <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 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.
- Provide the following information for the vCenter Chargeback application, and click Next:
If the specified ports are free, the next screen is displayed.
- IP Address: Static IP address of the machine on which you are installing vCenter Chargeback. Do not use localhost instead of the IP address.
- HTTP Port: An unused HTTP port through which vCenter Chargeback communicates.
- Load-Balancer Port: An unused port through which vCenter Chargeback can communicate with the load balancer (Apache Server).
- Server Instance Name: A user-defined name for the vCenter Chargeback instance. This name is used by the load balancer to identify the instance.
- Provide the following details for installing the load balancer, and click Next:
If the specified port is free, the next screen is displayed.
- IP Address: Static IP address of the machine on which you are installing vCenter Chargeback. Do not use localhost instead of the IP address.
- Admin Email Address: Email address of the server administrator.
- HTTPS Port: An unused port through which the Apache Server communicates. The load balancer listens on this port for user requests.
- Enter a user name and password for the administrative account that will be used to manage the vCenter Chargeback application, and click Next.
The password must be less than or equal to 24 characters in length.
- 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 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 Skip now, I'll generate it later.
For detailed install and upgrade instruction, refer to the vCenter Chargeback User's Guide. Ensure that you perform the pre-upgrade tasks specified in the vCenter Chargeback User's Guide. Also, perform the tasks specified in KB 1026068 and KB 1026796 before you upgrade an existing vCenter Chargeback installation.
This section lists the issues that have been fixed in this release.
Hierarchy Management Issues
- Hierarchy creation fails with the error Hierarchy with name 'X' already exists
In earlier releases of vCenter Chargeback, if you register vCenter Chargeback with a vCenter Server and try to create a hierarchy with the same name as the vCenter Server, vCenter Chargeback displays an error similar to the following:
Hierarchy with name 'X' already exists.
where X is the name of the hierarchy, which is same as the vCenter Server name.
This error occurs because when the application is registered with a vCenter Server, vCenter Chargeback creates a default hierarchy for the vCenter Server with the same name as the vCenter Server name.
Starting with this release, the default hierarchy is not created when vCenter Chargeback is registered as a plug-in with a vCenter Server. Therefore, this error does not occur.
- Sort order of the entities in a hierarchy is different in vCenter Chargeback as compared to that in the vSphere Client
In earlier releases of vCenter Chargeback, the entities at each level in a hierarchy are sorted alphabetically. Therefore, the sort order of the entities in a hierarchy is different in vCenter Chargeback and vSphere Client. In this release, the sort order of entities in vCenter Chargeback and vSphere Client are same.
- Chargeback hierarchy shows vApps as resource pools
In earlier releases of vCenter Chargeback, the icon used to represent vApps in the chargeback hierarchy is same as that used to represent resource pools. This issue is fixed in the current release.
Report Management Issues
Units for Network Received and Transmitted is not displayed in the Chargeback Cost Details section of the report
Depending on the number and type of information selected for display in the Chargeback Cost Details section of a report, the units for the Network Received and Transmitted computing resource might not be displayed in the report. This issue is fixed in this release.
Report displays Disk IO and Network IO in the Chargeback Resource Summary section
In earlier releases of vCenter Chargeback, the Disk Read and Write computing resource is displayed as Disk IO and the Network Received and Transmitted computing resource is displayed as Network IO in the Chargeback Resource Summary section of a report. Starting with this release, the computing resource names appear correctly in the reports.
CPU usage is 100% during report generation
In the earlier release, if five or more reports each having more than 1000 pages are generated simultaneously, the CPU usage of the machine on which vCenter Chargeback is running might reach 100%. The CPU usage reduces after the reports are generated. This performance issue is resolved in the current release of vCenter Chargeback.
Errors displayed when rescheduling an archived report
In earlier releases of vCenter Chargeback, when you reschedule an archived report, vCenter Chargeback might display errors if the archived report was generated by a report schedule that is currently expired. vCenter Chargeback displays the following error:
Invalid at the top level of the document. No data.
If you click OK on the error dialog, the Schedule Report screen is displayed. After you enter the schedule information and click Schedule, vCenter Chargeback displays the following error:
An error has occurred. Please contact system administrator.
The new report schedule is created and can be accessed from the Scheduled Reports page, but contains incorrect information. Starting with this release, you can reschedule archived reports, even if the report schedule that generated it has expired.
User Management Issues
Search for LDAP users returns LDAP users and LDAP groups
In earlier releases of vCenter Chargeback, when you search for users of the type LDAP User on the Permissions page of the Users & Role tab, the displayed search results include the LDAP users as well as the LDAP groups that match the search criteria. If the search criteria is not provided, then all the LDAP users and groups are displayed. This issue is fixed in this release of vCenter Chargeback.
The Number of Chargeback Entities value displayed in the System Health tab is incorrect
In earlier releases of vCenter Chargeback, the Number of Chargeback Entities value reported on the System Health tab of vCenter Chargeback includes the chargeback entities created in the application, the vCenter Server entities added to the application, and also the entities deleted from the application. As a result, there is a mismatch in the reported number of chargeback entities and the actual number of chargeback entities in the application. This issue is rectified in vCenter Chargeback 1.5.
Database URL in the error message is incorrect
In earlier releases, when you are adding a vCenter Server, vCenter Chargeback displays an error similar to the following if it fails to connect to the vCenter Server database:
Unable to connect to the vCenter Database Server:jdbc:sqlserver://220.127.116.111sqlexp_vim;databaseName=vim_vcdb
The error message might not contain the backslash (\) character in the database URL (<IP Address>\<InstanceName>). This issue is fixed in the current release.
Unable to uninstall the vCenter Chargeback plug-in from vSphere Client
In earlier releases of vCenter Chargeback, if you register vCenter Chargeback as a plug-in when adding vCenter Server, you must ensure that the Register As VI Client Plugin option is deselected for all the vCenter Server instances added to vCenter Chargeback before uninstalling vCenter Chargeback. If you uninstall the application without deselecting this option, you cannot remove the plug-in from the vSphere Client. In this release, the vCenter Chargeback uninstaller provides an option to remove the vSphere Client plug-in.
vCenter Chargeback does not automatically connect to the database after a database service restart
In earlier releases, if the vCenter Chargeback database fails and is restarted, then vCenter Chargeback does not automatically connect to the database. Instead, vCenter Chargeback displays an error message similar to Error unknown object. You must restart vCenter Chargeback for the database connection to be established. This issue is fixed in vCenter Chargeback 1.5.
The known issues in this release are listed in this section. Workarounds, if any, are provided in the issue description.
Hierarchy Management Issues
Connection times out when browsing hierarchy
If you are browsing a large vCenter Server or vCenter Chargeback hierarchy in the vCenter Chargeback plug-in, the connection to vCenter Chargeback might time out.
vCenter Chargeback does not show the status of the virtual machines
This release of vCenter Chargeback does not show the status of the virtual machines in the chargeback hierarchy and vCenter Server hierarchy. All the virtual machines in the hierarchies have the same icon and do not indicate whether they are powered on, suspended, or powered off. Also, the vCenter Server hierarchy displays all the virtual machines, including the ones that are suspended or powered off. This, however, does not affect the usage and cost calculation. The usage statistics that are used by vCenter Chargeback to calculate the costs are tracked by vCenter Server and stored in the vCenter Server database.
Changes to a chargeback hierarchy are not reflected in the concurrent user sessions
Hierarchy creation, deletion, and renaming operations performed by a user are not automatically reflected in concurrent user sessions. The concurrent users must log out and then log in again to see these changes. Any other change to the chargeback hierarchy, such as adding or deleting an entity, might not reflect immediately in the concurrent user sessions. After a change is made to the chargeback hierarchy, the hierarchy must be manually refreshed in the concurrent user sessions. Users can refresh the chargeback hierarchy by clicking the refresh button next to the chargeback hierarchy or by loading another chargeback hierarchy and then reloading the chargeback hierarchy. The refresh button appears only if vCenter Chargeback detects changes to the chargeback hierarchy.
Re-added virtual machine does not have the cost information configured on it
If you delete an ESX host from a vCenter Server, all the virtual machines belonging to the ESX host are deleted from the chargeback hierarchy. After re-adding the ESX host to the vCenter Server, you can add the virtual machines on this ESX host back to the respective chargeback hierarchies in vCenter Chargeback. However, any entity-specific cost configuration set on the virtual machines prior to deleting the ESX host from the vCenter Server is lost. You must, therefore, migrate all the virtual machines on an ESX host before removing the ESX host from the vCenter Server.
Changes to the chargeback hierarchy are not reflected immediately
If the changes made to a chargeback hierarchy are not displayed immediately in the Web browser, you must refresh the chargeback hierarchy to view the changes. You can refresh the chargeback hierarchy by selecting another hierarchy and then selecting the required chargeback hierarchy.
Report Management Issues
Report generation schedule fails with an invalid XML error
When generating a reporting schedule, if the recurrence range is shorter in duration than the recurrence pattern, then vCenter Chargeback fails to create the schedule and throws an error similar to the following:
Incoming XML is invalid.
That is, if you create a weekly schedule and the recurrence range has the start date as the current date and end date as five days from the current date, then the schedule creation fails. In this case, the recurrence range is five days, which is less than the recurrence pattern, which is seven days.
Report generation fails with entity not found error
If you backdate a hierarchy after adding a newly created vCenter Server entity to a hierarchy, which contains vCenter Server entities that were synchronized during the first run of the data collector synchronization jobs, then the newly created vCenter Server entity is also backdated by three months. Therefore, when you generate a report on this entity, vCenter Chargeback throws an entity not found error. Also, if you generate a report on any of the parent entities of this entity, the report excludes this entity from the report. vCenter Chargeback does not display or log any message stating the entity was excluded from the report. To ensure that the entity is included in the reports, you must delete the entity from the hierarchy and add it again if you have already backdated the hierarchy.
Information messages stating lack of data for a specific time period is not displayed in the report
If data is unavailable for a part of the reporting period, then vCenter Chargeback considers zero usage for this time period. However, no information message stating the same is included in the report.
Report includes the usage and cost information for secondary virtual machines
If you enable fault tolerance on a virtual machine after the data collector has synchronized the vCenter Chargeback inventory for the first time after installation, the report might include usage and cost information for the secondary virtual machines corresponding to the fault tolerance-enabled virtual machine. However, this cost and usage data included is for a very negligible time frame.
Report created time is modified to upgrade time
After upgrading to vCenter Chargeback 1.5, the create time for the archived reports in vCenter Chargeback is changed to the upgrade time. Although the report content is not changed, a search based on the report create time might provide incorrect results.
Reports for a vCenter Server user might not contain the correct entities
A report scheduled for a vCenter Server user might contain the usage and cost details for entities on which the user does not have permissions. The report might also exclude some entities on which the user has permissions. There is currently no workaround for this issue. However, reports might be generated correctly for the vCenter Server user whose credentials are used to add the vCenter Server to vCenter Chargeback.
Report generation schedule is automatically changed
If vCenter Chargeback stops running and is restarted, all the reports generation schedules that were set to run during the period that the application was not running are immediately started. Also, these report generation schedules are automatically updated to run at this new time. For example, suppose you have created a report generation schedule that generates a daily report at 6:00 PM. If the application stops running at 4:30 PM, and you restart vCenter Chargeback at 9:00 AM the next day, the report that had to be generated at 6:00 PM the previous day is generated at 9:00 AM instead. Also, the corresponding schedule is updated automatically to run at 9:00 AM everyday.
Report generation fails with an error on a vCenter Server entity in a chargeback hierarchy that is not back-dated
In a chargeback hierarchy that is not back-dated, when you try to generate a report on a vCenter Server entity for a time period before the entity was added to the hierarchy, vCenter Chargeback reports the following error:
Error in response format
Report search based on page count returns incorrect results
When you search for reports based on page count by using the Advanced Search option, vCenter Chargeback might not return all the reports that have page count in the specified range. The search results might be incorrect.
The last run time for rescheduled report defaults to N/A
After you reschedule a report, vCenter Chargeback shows the last run time for this scheduled report as N/A instead of the date and time when the report was last generated as per the original schedule.
Additional plug-ins required message displayed when trying to preview Report View
On Mozilla Firefox 3.6.x, an additional plug-ins required message appears when you click Preview on the Report View page of the Settings tab. You can safely close the message. The report preview is displayed on the right pane of the page.
Dashboard report does not check the user's privilege for cost elements
vCenter Chargeback filters the chargeback hierarchical entities included in the dashboard report based on the user's vCenter Chargeback resource authorization details. However, the application does not check for the authorization details on the cost elements for the logged-in user.
Information from the Report View is not included in the exported or emailed report
The information configured in the Report View might not appear in the exported or emailed report after you upgrade to vCenter Chargeback 1.5. Also, the configured data might not be shown when you click Preview on the Report View page of the Settings tab. A workaround for this issue is that, if you have included images in any of the sections of the Report View, then you upload all the images again and save the report view after the upgrade. If you have only text in the Report View sections, just click Save on the Report View page of the Settings tab.
Report does not include cost and usage data for all the child entities
If you delete a virtual machine from a chargeback hierarchy and then upgrade to vCenter Chargeback 1.5, then vCenter Chargeback does not include the entity details in the report, even if the report is generated for time period when the virtual machine existed in the hierarchy.
Inconsistent usage and cost data reported
If you generate a report that considers the actual resource usage for a billing period including the past 24 to 36 hours from the report generation time, the usage data and cost included in the report might be inconsistent. This inconsistency might occur if vCenter Server has not completed the statistics roll-up or the data collector has not synchronized the rolled-up statistics in the vCenter Chargeback database.
Report does not include usage and cost information related to raw devices
If a virtual machine contains a hard disk that uses raw device mapping, then the report does not include the usage and cost information for the raw device. vCenter Chargeback currently does not account for raw device mapping.
User Management Issues
Unable to modify or delete a hierarchy
Although a user has the necessary privileges to update or delete a hierarchy, he is unable to update or delete it. To enable a user to update or delete a hierarchy, the user must be assigned a role with the update and delete privileges for the hierarchy resource type on the hierarchy and the update and delete privileges for the chargeback hierarchical entity resource type on the root node of the hierarchy, which is same as the hierarchy name.
Non-ASCII characters are not displayed correctly in the exported report and the report sent by email
If a report includes non-ASCII characters, they are not displayed correctly if the report is exported to the PDF or CSV format. vCenter Chargeback, however, displays these characters correctly. This issue also occurs when the report is sent through an email. If the report name has non-ASCII characters, the generated report name and emailed report name might differ.
Errors displayed while accessing vCenter Chargeback from a localized version of Windows Server 2003
In this release of vCenter Chargeback, some errors might occur when you access the application from a Web browser on a localized version of Windows Server 2003 operating system. You should access vCenter Chargeback from a Web browser on any operating system other than Windows Server 2003. There are currently no workarounds for this issue.
Virtual Appliance Issues
- Apply Cost Template API fails if the rate factors are not set on the cost template
If the Apply Cost Template API is called for a cost template that does not have any rate factor set, an exception with response XML similar to the following is raised:
<Error majorErrorCode="400" minorErrorCode="3004" message="At least one computing resource must be selected." />
The only workaround is to set the rate factors. This issue, however, does not occur if a cost template without any rate factors is applied from the application user interface.
vCenter Chargeback displays the disconnected hosts and orphaned virtual machines
vCenter Chargeback does not distinguish between connected and disconnected ESX hosts. Therefore, vCenter Chargeback displays the disconnected hosts and orphaned virtual machines and accounts for the same in generated reports. Also, vCenter Chargeback does not display the state of these ESX hosts and virtual machines. If a ESX host is disconnected from a vCenter Server and added to another vCenter Server, and both the vCenter Server instances are added to vCenter Chargeback, then vCenter Chargeback will display a duplicate entry for the ESX host. That is, vCenter Chargeback will display an ESX host entry corresponding to the disconnected host and another corresponding to the host connected to the second vCenter Server. As a result, vCenter Chargeback accounts for the disconnected host CPUs and orphaned virtual machines in vCenter Chargeback licensing.
vCenter Chargeback throws a resource already exists message
If you create a resource with a name that contains the % or _ characters, then vCenter Chargeback might throw an error if it detects another resource with a similar naming pattern. For example, you create a cost model with the name FirstModel. Now, when you try to create a another cost model with the name F%Model, vCenter Chargeback might throw an error stating cost model with the given name already exists. Similarly, let us say you create a hierarchy with the name My1Hierarchy. Now, if you try to create another hierarchy with the name My_Hierarchy, vCenter Chargeback might throw an error.
vCenter Chargeback throws an error when deleting vCenter Server
When you delete a vCenter Server whose entities are added to a hierarchy, vCenter Chargeback shows a dialog box asking whether you want to retain the entities or delete them from vCenter Chargeback. If you choose to delete the entities, then an error message similar to the following is displayed:
vCenter Server 'vcId' or it's 'Hosts & Clusters and VMs & Templates Synchronization' job is not found.
However, the delete operation is successful. This error message is displayed only if the vCenter Server hierarchy is displayed in the Manage Hierarchy tab when the vCenter Server is deleted. You must close all the relevant error dialog boxes displayed to continue normal functioning of vCenter Chargeback.
vCenter Chargeback throws an error when you add a license
When you add a license to vCenter Chargeback, an error is thrown. However, vCenter Chargeback functions correctly without any issue. In Firefox, the error is logged in the error console. In Internet Explorer, the error is shown in the status bar if the Disable script debugging check box is selected under Tools > Internet Options > Advanced. If the check box is not selected, an error dialog is displayed.
User sessions overlap when multiple users are logged in from the same machine
If multiple users are accessing the same vCenter Chargeback instance from a single machine using different instances of the same Web browser, then the user sessions might get overlapped.
Unable to download and install the vCenter Chargeback plug-in from the Plug-ins Manager window of the vSphere Client
This is a vSphere Client issue. Restart the vSphere Client and accept the vCenter Chargeback SSL certificate. This might rectify the issue if the vSphere Client is able to communicate with vCenter Chargeback. If the vSphere Client and vCenter Chargeback are on different network domains, this issue might persist.
VI Client does not render the hierarchy completely or displays error while rendering
If you are using VI Client 2.5 with Internet Explorer 6 on a Windows Server 2003 machine, the VI Client might display some errors, such as Insufficient Memory, when rendering a very large hierarchy (with more than 1000 entities). Also, the hierarchy rendering is very slow. A probable workaround is to access vCenter Chargeback directly from a Web browser instead of using the vCenter Chargeback plug-in on the VI Client.
vCenter Chargeback instance is not recognized as a part of the cluster
If you have a two-instance cluster and the first vCenter Chargeback instance fails due to some reason, all the requests currently being served by the first instance are moved to the second instance. After the first instance is restarted, if the second instance fails, the requests handled by the second instance are not moved to the first instance. That is, the failover does not happen because the second instance does not recognize the first instance as a part of the cluster. A workaround for this issue is to restart all the vCenter Chargeback instances in the cluster. This issue also occurs for clusters with more than two instances. If any of the vCenter Chargeback instances fails and is restarted, that instance starts serving user requests but is not recognized by the cluster until other instances are restarted.
Imported vCenter Server attributes are not deleted when the vCenter Server entity is deleted
While adding a vCenter Server entity to a chargeback hierarchy, you can import the attributes defined on the entity. However, these attributes are not deleted from the vCenter Chargeback application when the corresponding vCenter Server entity is deleted. You can manually delete these attributes from the application if the attributes are no longer required and are not assigned to any other entities across the chargeback hierarchies defined in the application.
Logged-in users do not see newly added computing resources
If you are logged in to vCenter Chargeback and any new computing resource is added to it through an API call, you can see the newly added computing resource only if you log in again to vCenter Chargeback.
vCenter Chargeback ignore the base DN value provided when configuring the LDAP server
In this release, vCenter Chargeback ignores the value entered for base DN when configuring the LDAP server. vCenter Chargeback automatically fetches the root base DN and uses this value to configure the LDAP server.
After upgrade, the samples folder contains old files
When you upgrade from vCenter Chargeback 1.0.1 to vCenter Chargeback 1.5, the installer does not remove or update the samples folder under the installation directory. vCenter Chargeback 1.5 installation does not include any sample files.
The version of the vCenter Chargeback plug-in in vSphere Client is not updated after upgrading to vCenter Chargeback 1.5
After upgrading to vCenter Chargeback 1.5 from vCenter Chargeback 1.0.1, vSphere Client reports the plug-in version as 1.0.1 when you check the version from Plug-ins > Manage Plug-ins. Although the plug-in is upgraded, the plug-in version is reported incorrectly. However, the plug-in version is reported correctly when checked from Tools > About in the plug-in.
VMware Cloud Director Data Collector and vShield Manager Data Collector Issues
Some of the following listed issues are common for both the VMware Cloud Director Data Collector and the vShield Manager Data Collector.
If the VMware Cloud Director database has a large history of chargeback events, the processing of the events might take a long time to complete.
If VMware Cloud Director, vShield Manager instances, vCenter Chargeback instances, and the corresponding databases and data collectors are not in the same timezone, then the data collectors might fail to process the events.
You cannot change the logging level for the data collectors at runtime. Also, the logging levels cannot be changed from the vCenter Chargeback GUI.
vCenter Chargeback accounts for the virtual machines only from the time they are added to the hierarchy in vCenter Chargeback and till they are deleted from vCenter Chargeback by the data collector.
A virtual machine added to the VMware Cloud Director setup is reflected in the corresponding vCenter Chargeback hierarchy only if the lifetime of the virtual machine is greater than the frequency of the event processor job of VMware Cloud Director Data Collector.
vShield Manager reports incorrect external broadband statistics values if the vShield Manager instances are not in the same timezone as VMware Cloud Director, vCenter Chargeback, and the corresponding databases and data collectors.
If chargeback events are not processed because of a failed VMware Cloud Director instance, then the entities in the hierarchy might not be charged correctly and consistently.
vCenter Chargeback charges for the network services and network count even if the deployment of a network fails during service configuration in vShield Manager.
Virtual machines might be incorrectly charged if vApp creation with resolved virtual machines partially fails.
Changes to the vApp name in VMware Cloud Director might not be reflected in vCenter Chargeback.