VMware vCenter Chargeback Manager - 2.0 User’s Guide
vCenter Chargeback Manager
User’s Guide
vCenter Chargeback Manager 2.0.0
This document supports the version of each product listed and
supports all subsequent versions until the document is replaced
by a new edition. To check for more recent editions of this
document, see http://www.vmware.com/support/pubs.
EN-000716-00
vCenter Chargeback Manager User’s Guide
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
Copyright © 2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual
property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks
and names mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
Contents
About the User's Guide 5
Introduction to vCenter Chargeback Manager 7
1
What Is Chargeback 7
Chargeback Solution for Virtual Environments 7
Overview of vCenter Chargeback Manager 8
Configuring Administration Settings 11
2
Activate the Application 11
Configuring Generic Settings 12
Managing LDAP Servers 15
Managing vCenter Servers 17
Managing Data Collectors 22
Managing the Application License 29
Manage Report View 30
Managing Attributes 31
Manage System Health Thresholds 33
Manage Computing Resources 33
Authenticating and Managing Users, Roles, and Permissions 35
3
Resource Based Authorization in vCenter Chargeback Manager 35
Permissions Defined in vCenter Chargeback Manager 36
Managing Roles 37
Managing Users 44
vCenter Chargeback Manager User Authentication 52
VMware, Inc.
Managing Chargeback Hierarchies 55
4
Creating a Chargeback Hierarchy 55
Managing a Chargeback Hierarchy 58
Managing and Configuring vCenter Chargeback Manager Cost Elements 67
5
vCenter Chargeback Manager Cost-Related Elements 67
Managing Cost Models 73
Managing Fixed Costs 77
Managing Cost Templates 80
Managing Billing Policies 82
Configuring Cost at the Entity Level 85
Physical Infrastructure Costing 87
Configuring a Pricing Matrix for Virtual Machines 91
3
vCenter Chargeback Manager User’s Guide
Generating Reports 95
6
About Reports 95
Generate a Cost Report 98
Generate a Usage Report 100
Generate Cost Comparison Report 101
Generate Showback Report 103
Scheduling Report Generation 105
Managing Reports 111
Managing Archived Reports 115
Managing Automatic Report Scheduler 118
Report Dashboard 120
Monitoring System Health 123
7
vCenter Chargeback Manager Events 124
Administration Utilities 125
8
Database Password Change Utility 125
vCenter Chargeback Manager IP Address Reset Utility 126
Statistics Collection Scripts 127
vCenter Chargeback Manager Database Management Scripts 134
Index 137
4 VMware, Inc.
About the User's Guide
The vCenter Chargeback Manager User's Guide provides information about configuring and using the chargeback
solution for virtual environments that use VMware Infrastructure or VMware vSphere.
Intended Audience
This book is intended for anyone who wants to use vCenter Chargeback Manager. The information in this book
is written for experienced Windows system administrators who are familiar with virtual machine technology
and datacenter operations.
VMware, Inc. 5
vCenter Chargeback Manager User’s Guide
6 VMware, Inc.
Introduction to vCenter Chargeback
Manager 1
vCenter Chargeback Manager is an end-to-end cost reporting solution for virtual environments using vSphere.
vCenter Chargeback Manager can also be used with VMware vCloud Director. Before you install and start
using vCenter Chargeback Manager, an understanding of what is chargeback and about chargeback solutions
for a virtual environment would be helpful.
This chapter includes the following topics:
n
“What Is Chargeback,” on page 7
n
“Chargeback Solution for Virtual Environments,” on page 7
n
“Overview of vCenter Chargeback Manager,” on page 8
What Is Chargeback
Chargeback is a mechanism to account for the operational costs involved in providing and maintaining an
IT infrastructure, including the costs for IT services and applications. Measuring resource utilization and
calculating the corresponding IT operational cost enables you to account for the IT resources utilized and bill
for the services provided.
In a non-virtual environment, a physical server and the associated resources like the applications running on
it can be easily mapped to the department using them, making the billing for such resource utilizations
relatively easy. Also, costs incurred due to maintenance and licensing can be directly associated to a
department, thereby enabling you to calculate the complete IT operational costs.
In a virtual environment, however, the task of calculating the IT operational cost for each department becomes
very difficult. Multiple virtual machines run on a physical server, which might be shared across different
departments or cost centers in an organization. As a result, resource utilization for this server and, therefore,
the cost incurred cannot be directly associated to any single department or cost center. The difficulty in
accounting gets further compounded when applications and services get shifted over time to different servers,
based on the load and available infrastructure resources.
Chargeback Solution for Virtual Environments
In a virtual environment, a chargeback solution requires a flexible metering system that can account for the
utilization of resources shared across the organization.
These measurements can be based on allocation or actual usage of individual servers and resources. In the case
of VMotion, DRS, or HA being enabled, the measurements could be based on the allocation or actual usage of
resource pools.
To support chargeback, the virtual environment and the chargeback solution must provide ways to measure
resource usage and associate the usage with a specific costing model. The chargeback solution must also
support the use of different costing models so as to charge the various departments or cost centers differently.
VMware, Inc.
7
JDBC
vCenter Chargeback
Manager
Load Balancer
vCenter Server
Data Collector
vCenter
Chargeback
Manager
database
vCenter Chargeback
Manager UI
vCenter
Server
database
ESXi
host03
ESXi
host02
ESXi
host01
VIM API
vCenter Chargeback Manager User’s Guide
A chargeback solution for a virtual environment defines a hierarchy with different types of entities such as
departments, divisions, business units, cost centers, physical servers, virtual machines, and so on. For each
entity type, a cost model is defined that determines the rate for each unit of a resource utilized. The chargeback
solution determines the resource usage by using either utilization-based metering or allocation-based metering
of virtual machines. The metered parameters are then associated with the designated entities, and the cost
model defined for that entity along with specific chargeback formulas are used as part of the overall chargeback
solution.
Overview of vCenter Chargeback Manager
Determining the resource utilization and calculating the corresponding cost for a virtual environment that uses
VMware vSphere typically involves VMware professional services’ work or use of partner solutions. These
solutions are built using custom methods for VMware vSphere resource data collection and chargeback cost
calculation for organizations.
vCenter Chargeback Manager is an end-to-end cost reporting solution for virtual environments that use
VMware vSphere. This Web-based application interacts with the vCenter Server Database to retrieve usage
information, calculates the cost by using the defined chargeback formulas, and generates cost and usage
reports. Figure 1-1 shows how vCenter Chargeback Manager interacts with various components of a virtual
environment using VMware vSphere.
Figure 1-1. vCenter Chargeback Manager in a Virtual Environment
vCenter Chargeback Manager runs on an Apache Tomcat server instance. Users interact with vCenter
Chargeback Manager through a load balancer (Apache HTTP Server). vCenter Chargeback Manager connects
to the vCenter Chargeback Manager database that stores application-specific information, such as the defined
chargeback hierarchies, cost models, users, roles, and so on. The application interacts with the vCenter Server
using VIM APIs and with the vCenter Server database through a data collector. The data collector
communicates with the vCenter Server Database using JDBC.
8 VMware, Inc.
Chapter 1 Introduction to vCenter Chargeback Manager
When you install vCenter Chargeback Manager, a load balancer and a data collector is also installed and run
on the same machine. Although the vCenter Chargeback Manager database can also be installed on the same
machine, in a real-world scenario you would install the application and the database on separate machines.
vCenter Chargeback Manager retrieves the virtual infrastructure inventory and the resource usage information
for each virtual machine from the vCenter Server database through the data collector. The data collector
replicates this information in the vCenter Chargeback Manager database. vCenter Chargeback Manager uses
this information from the vCenter Chargeback Manager database along with the cost model and chargeback
cost calculation formulas to generate the cost reports. A single data collector instance can communicate with
multiple vCenter Server instances and vCenter Server databases and replicate the relevant information in a
vCenter Chargeback Manager database.
vCenter Chargeback Manager also lets you create a cluster of vCenter Chargeback Manager instances that
share a single load balancer. Each user request is routed through the load balancer. The load balancer forwards
the request to a vCenter Chargeback Manager instance in the cluster, while ensuring session affinity for an
instance, based on the number of requests currently being serviced by each instance in the cluster. All the
vCenter Chargeback Manager instances in a cluster are connected to the same vCenter Chargeback Manager
database.
If you have a VMWare vCloud Director setup, you can install the vCloud Director Data Collector and configure
it appropriately so that the vCloud Director setup can be integrated with vCenter Chargeback Manager. You
can then generate various reports of the organizations classified under the different categories, such as PayAs-You-Go, Reservation, and Allocation Pool.
VMware, Inc. 9
vCenter Chargeback Manager User’s Guide
10 VMware, Inc.
Configuring Administration Settings 2
As an administrative user, you can perform various administrative tasks, such as configuring the LDAP and
SMTP servers in the application and adding as well as updating vCenter Server information.
To perform these administrative tasks, you must have the Super User or Administrator role. The user account
details provided during the installation has the Super User role defined on it. Log in to the application by using
this administrative user account.
This chapter includes the following topics:
n
“Activate the Application,” on page 11
n
“Configuring Generic Settings,” on page 12
n
“Managing LDAP Servers,” on page 15
n
“Managing vCenter Servers,” on page 17
n
“Managing Data Collectors,” on page 22
n
“Managing the Application License,” on page 29
n
“Manage Report View,” on page 30
n
“Managing Attributes,” on page 31
n
“Manage System Health Thresholds,” on page 33
n
“Manage Computing Resources,” on page 33
Activate the Application
When you log in to vCenter Chargeback Manager for the first time after installation, you are prompted to enter
the license key.
Procedure
1 On the Add License screen, enter the license key.
2 Provide the username and password of the Super User.
3 Click Add.
The details about this license is stored in the application and can be accessed from the License page of the
Settings tab.
VMware, Inc.
11
vCenter Chargeback Manager User’s Guide
Configuring Generic Settings
Before you start using the various features of vCenter Chargeback Manager, you must configure few settings
in the application.
Some of the generic settings can be configured from the Settings tab. You can configure the SMTP server
settings and the log level from the General page of the Settings tab.
The General page of the Settings tab lists all the vCenter Chargeback Manager instances added to the cluster.
In the case of a stand-alone installation, a single URL for the vCenter Chargeback Manager is displayed. You
can remove the vCenter Chargeback Manager instances that are not required or not responding from this page.
Configure the SMTP Server Setting
You must configure the SMTP server setting in vCenter Chargeback Manager to send the generated and
archived reports through email.
You must have the Super User role to perform this task.
Procedure
1 In the Settings tab, click General.
2 Click Add in the Email Setting section.
The Manage Email Server screen is displayed.
3 Provide information about the SMTP server that the application uses to send emails.
Option Description
Server HostName
Server Port
Email Address
Authentication Type
User Name
Password
Maximum Attachment Size(KB)
Static IP address of the SMTP server. If the sever does not have a static IP
address, ensure that you provide the FQDN.
Port number on which the SMTP server is listening for requests.
Email address that the application must use to send emails.
Type of authentication to be used to access the SMTP server. The default is
Anonymous.
User name to be used for authentication, if authentication type is Require
Login.
Password for the user name provided above.
The maximum permissible file size for email attachments. The size specified
is in KB.
4 Click Add.
The email address provided is displayed in the Email Setting section.
Edit the SMTP Server Setting
After configuring the SMTP server setting, you can change it any time, provided you have the required
privileges. For instance, if the SMTP user account password is changed on the SMTP server, you must also
reflect this change in vCenter Chargeback Manager.
You must have the Super User role to perform this task.
Procedure
1 In the Settings tab, click General.
12 VMware, Inc.
2 Click Edit in the Email Setting section.
The Manage Email Server screen is displayed.
3 Modify the required SMTP server settings.
Option Description
Server HostName
Server Port
Email Address
Authentication Type
User Name
Password
Maximum Attachment Size(KB)
Static IP address of the SMTP server. If the sever does not have a static IP
address, ensure that you provide the FQDN.
Port number on which the SMTP server is listening for requests.
Email address that the application must use to send emails.
Type of authentication to be used to access the SMTP server. The default is
Anonymous.
User name to be used for authentication, if authentication type is Require
Login.
Password for the user name provided above.
The maximum permissible file size for email attachments. The size specified
is in KB.
4 Click Edit.
The email address is displayed in the Email Setting section.
Chapter 2 Configuring Administration Settings
Delete the SMTP Server Setting
You can remove an existing SMTP server and add a new one.
You must have the Super User role to perform this task.
Procedure
1 In the Settings tab, clickGeneral.
2 Click Remove in the Email Setting section.
A dialog confirming the action is displayed.
3 Click OK.
Set Log Level
By default, the log level for the application is set at the info level. You can change the log level at any time in
the application as per your requirements.
You must have the Super User role to perform this task.
NOTE In the case of a cluster installation, the changing of log level in one application instance will not be
reflected in the other instances in the cluster immediately. The change will get reflected:
n
If the vCenter Chargeback Manager service is restarted.
n
When the database is polled for changes, which automatically occurs every hour.
Procedure
1 In the Settings tab, clickGeneral.
VMware, Inc. 13
vCenter Chargeback Manager User’s Guide
2 In the Log Setting section, select the required log level from the Select Log level list.
Option Description
trace
debug
info
warn
error
fatal
The trace level is the most informative level providing fine-grained
information about the events.
The debug level provides event information that are most useful to debug
an application.
(default): The info level provides coarse-grained informational messages that
highlight the progress of the application.
The warn level provides information about potentially harmful situations.
The error level designates error events that might still allow the application
to continue running.
The fatal level designates very severe error events that will presumably lead
the application to abort.
3 Click Apply.
Remove a vCenter Chargeback Manager
You must ensure that vCenter Chargeback Manager instances that are unavailable or not required are removed
from the cluster.
In a cluster configuration, the load balancer forwards the requests to a vCenter Chargeback Manager instance
that has a lighter load. However, even if a vCenter Chargeback Manager instance is unavailable and not
responding, the load balancer tries to forward the requests to such an instance. You must, therefore, monitor
the health of the vCenter Chargeback Manager instances and remove those instances from the cluster that are
not responding.
When you remove a vCenter Chargeback Manager from the UI, the corresponding entries for the instance is
removed from the System Health. However, the instance is still in the cluster and the load balancer sends
requests to it. You must manually remove the instance from the load balancer by running the
ModifyLBWorkers.bat file. You must have the Super User role to perform this task.
NOTE Removing a vCenter Chargeback Manager instance does not correspond to uninstalling the instance.
Only the details of the instance is removed from a database table and from the application UI. The instance
exists on the system that it is installed. You can log in to this instance and use it, if the instance functions
correctly.
Procedure
1 In the Settings tab, click General.
A list of vCenter Chargeback Manager instances is displayed under the Chargeback Servers section.
2 Select the vCenter Chargeback Manager that you want to remove.
3 Click Remove.
4 Click OK to confirm the remove operation.
The vCenter Chargeback Manager details are removed from the database and the System Health page.
What to do next
You must run the ModifyLBWorkers.bat file to remove the corresponding vCenter Chargeback Manager entry
from the load balancer. Run the following commands from the command-line prompt:
> cd
Installation_Folder
> ModifyLBWorkers delete
14 VMware, Inc.
\vCenter-CB-Tools\load-balancer\bin\
Server_Instance_Name
<Installation_Folder> is the complete folder path provided during the vCenter Chargeback Manager installation.
The default installation folder is C:\Program Files\VMware\VMware vCenter Chargeback.
Server_Instance_Name is the name that you have provided during the installation.
You must restart the Load Balancer service after running the ModifyLBWorkers.bat file.
Managing LDAP Servers
You can configure one or more LDAP servers in vCenter Chargeback Manager. vCenter Chargeback Manager
supports only Microsoft Windows Server 2003 Active Directory and Microsoft Windows Server 2008 Active
Directory.
You can view and manage the LDAP servers from the LDAP Servers page of the Settings tab. You can also
configure the LDAP server for secure communication using SSL certificates.
Configure the LDAP Server Setting
Configuring the LDAP server setting in the application enables Windows Active Directory users to access the
application using their Windows Active Directory login credentials.
You must have the Super User role or the Administrator role to perform this task.
Procedure
Chapter 2 Configuring Administration Settings
1 In the Settings tab, click LDAP Servers.
2 Click Add.
The Manage LDAP Server screen is displayed.
3 Enter the information related to the LDAP server that you want to configure in the application.
Option Description
Server Name
Server Address
User Name
Password
BaseDN
Port
LDAP Limit
Enable LDAPS
A user-defined name to uniquely identify the LDAP server. You can provide
a full name or a short code to identify the LDAP server.
Static IP address of the LDAP server. If the sever does not have a static IP
address, ensure that you provide the fully-qualified domain name (FQDN).
The LDAP account to authenticate in to the LDAP server. The user name can
be of the formats user_name@domain_name or domain_name\user_name.
Preferably, use the User Principal Name (UPN).
Password for the user name provided.
The distinguished name (DN) of the entity in the LDAP hierarchy from which
groups and users can be added to the application. If not sepcified, vCenter
Chargeback Manager automatically fetches the root base dn and uses this
value.
Port on which the LDAP service is listening. The default port is 389. If you
select the Enable LDAPS option, ensure that you change this to a secure port,
say 636.
The maximum number of Windows Active Directory users or groups to be
fetched and displayed in the Add User Account screen of the application.
Select this option to enable LDAP over SSL.
4 Click Add.
If you have selected Enable LDAPS, then a dialog requesting you to accept the SSL certificate is displayed.
5 Accept the SSL certificate.
If you click Cancel, the LDAP Server setting configuration fails.
VMware, Inc. 15
vCenter Chargeback Manager User’s Guide
On successfully configuring the LDAP server setting, the details of the LDAP server, except the authentication
information, are displayed in the table on the LDAP Servers page.
What to do next
You can now add the Windows Active Directory users and groups to vCenter Chargeback Manager so that
they can access the application using their Windows Active Directory login credentials. To know more about
adding LDAP users and groups to the application, see “Creating Users,” on page 45.
Edit the LDAP Server Setting
After you have configured an LDAP server in the application, you can modify its details any time, provided
you have the required privileges. For instance, if the LDAP user account password is changed on the LDAP
server, you must also reflect this change in vCenter Chargeback Manager.
If the SSL certificate on the LDAP server is changed, you must modify the LDAP server setting in vCenter
Chargeback Manager to obtain the modified SSL certificate. Else, communication with the LDAP server fails.
To perform this task, you must have the Super User role or the Administrator role. If you have the
Administrator role, you can only edit those LDAP server settings that you have configured.
CAUTION Changes to the LDAP server settings might impact the corresponding LDAP users and groups that
are already added to the application. If you change the BaseDN to the DN of an entity that is lower in the LDAP
hierarchy compared to the currently set DN, then LDAP users that exist above the new DN will not be able to
log in to vCenter Chargeback Manager, and the resources created by them in the application, such as
hierarchies, cost model, and reports, might get orphaned and become unusable.
Procedure
1 In the Settings tab, click LDAP Servers.
2 Select the required LDAP server from the table displayed on the page.
3 Click Edit.
The Manage LDAP Server screen is displayed.
4 Modify the required LDAP server setting.
Option Description
Server Name
Server Address
User Name
Password
BaseDN
Port
LDAP Limit
Enable LDAPS
A user-defined name to uniquely identify the LDAP server. You can provide
a full name or a short code to identify the LDAP server.
Static IP address of the LDAP server. If the sever does not have a static IP
address, ensure that you provide the fully-qualified domain name (FQDN).
The LDAP account to authenticate in to the LDAP server. The user name can
be of the formats user_name@domain_name or domain_name\user_name.
Preferably, use the User Principal Name (UPN).
Password for the user name provided.
The distinguished name (DN) of the entity in the LDAP hierarchy from which
groups and users can be added to the application. If not sepcified, vCenter
Chargeback Manager automatically fetches the root base dn and uses this
value.
Port on which the LDAP service is listening. The default port is 389. If you
select the Enable LDAPS option, ensure that you change this to a secure port,
say 636.
The maximum number of Windows Active Directory users or groups to be
fetched and displayed in the Add User Account screen of the application.
Select this option to enable LDAP over SSL.
16 VMware, Inc.
Chapter 2 Configuring Administration Settings
5 Click Save.
If you have selected Enable LDAPS during the modify LDAP Server setting operation or the SSL certificate
on the LDAP server has changed, then a dialog requesting you to accept the SSL certificate is displayed.
6 Accept the SSL certificate.
If you click Cancel, the LDAP Server setting configuration fails.
The table on the LDAP Servers page lists the modified information for the selected LDAP server.
Delete the LDAP Server Setting
Any LDAP server that is no longer in use and configured in the application can be deleted from the application.
To perform this task, you must have the Super User role or the Administrator role. If you have the
Administrator role, you can only delete those LDAP server settings that you have configured.
IMPORTANT If you remove an LDAP server, the corresponding LDAP users and groups will also be deleted
from the application.
Procedure
1 In the Settings tab, clickLDAP Servers.
2 Select the required LDAP server from the table displayed on the page.
3 Click Delete.
A dialog confirming the action is displayed.
4 Click OK.
Information about the LDAP server is deleted from the table displayed on the LDAP Servers page.
Managing vCenter Servers
To determine the utilization of computing resources by the virtual machines and calculate the total costs, you
must first add the vCenter Server instances in your virtual environment to vCenter Chargeback Manager.
You can add more than one vCenter Server to the application. The application also lets you modify the
information about the vCenter Server instances and delete a vCenter Server from the application when it is no
longer required.
Communication with the vCenter Server is secured using a SSL certificate. After you add or modify the vCenter
Server settings in vCenter Chargeback Manager, you can view and install the SSL certificate presented by the
vCenter Server. If you chose not to install the SSL certificate, the vCenter Server is not added to and cannot be
accessed from vCenter Chargeback Manager.
If you change the SSL certificate on the vCenter Server or upgrade the vCenter Server, then you must modify
the vCenter Server information in vCenter Chargeback Manager to import the new SSL certificate.
Add vCenter Server Information
vCenter Chargeback Manager can calculate overall resource utilization and corresponding cost only for
vCenter Servers that are added to the application. You can add one or more vCenter Server instances to vCenter
Chargeback Manager.
You must have the Super User role or the Administrator role to perform this task.
VMware, Inc. 17
vCenter Chargeback Manager User’s Guide
Prerequisites
n
Before you add a vCenter Server, you must ensure that the vCenter Server is accessible over the network.
Also, ensure that vCenter Server and the vCenter Server database have static IP addresses. If not, you must
provide the FQDN for such servers and databases when adding them to vCenter Chargeback Manager.
n
You must ensure that the system time on the vCenter Server, vCenter Chargeback Manager, vCenter Server
database, vCenter Chargeback Manager database, and data collectors are in sync.
n
When adding a vCenter Server to vCenter Chargeback Manager, you must provide a vCenter Server user
name and vCenter Server database user name. Create a clone of the Read-only role in vCenter Server and
include the following permissions in this cloned role:
n
Storage views.View
n
Global.Licenses
n
Extension.Register extension
n
Extension.Unregister extension
n
Extension.Update extension
n
Profile-driven storage.Profile-driven storage view; if you are using vCenter Server 5.0.
n
Global.vCenter Operations User; if you have integrated the vCenter Server with VMware vCenter
Operations.
Create a user in vCenter Server for vCenter Chargeback Manager and assign this cloned role to the user.
Also, create a user in the vCenter Server database for vCenter Chargeback Manager and ensure that the
user has read access on the VPXV_HIST_STAT_DAILY, VPXV_HIST_STAT_WEEKLY, VPXV_HIST_STAT_MONTHLY, and
VPXV_HIST_STAT_YEARLY views.
NOTE Do not provide the user details that vCenter Server uses to connect to the vCenter Server database.
Procedure
1 In the Settings tab, clickvCenter Servers.
A table listing information about the vCenter Server instances added to the application is displayed.
2 Click Add.
The vCenter Server Information screen is displayed.
3 Enter information about the vCenter Server and its corresponding database that has to be added to the
application.
Option Description
vCenter Server Hostname/IP
vCenter Server Display Name
vCenter Server Description
vCenter Server Username
vCenter Server Password
FQDN or IP address of the vCenter Server. The IP address or host name
cannot be edited after the vCenter Server is added to the application.
A display name for the vCenter Server.
A description of the vCenter Server. This is optional.
User name to access the vCenter Server.
Password for the user name entered.
18 VMware, Inc.
Option Description
Database URL
URL to access the vCenter Server database.
For Oracle Database, this URL must have the format:
IP address/host name:TNS listener port
For example:
123.123.123.123:1521
For Microsoft SQL Server, this URL can be in the following formats:
IP address/host name\database instance name
or
IP address/host name
For example:
123.123.123.123\chargeback_db
You can also specify a well formed JDBC URL that starts with 'jdbc' and
contains the database name. If the vCenter Server database is on an Oracle
RAC environment, then you must provide a JDBC URL for the database.
Database Name
Database Type
Authentication Type
Database Username
Database Password
Register As vSphere Client Plug-in
Enable Stats Replication
Name of the vCenter Server database. For example, vim_vcdb, which is the
default name given by vCenter Server. If you are using Oracle Database, then
the database name can be either the service name or SID. If you are providing
the service name, ensure that you prefix the service name with a forward
slash (/). For example:
/
service_name
The database type can be either SQL Server (default) or Oracle.
This option is available only if you have set the Database Type to SQL
Server. You can set the Authentication Type to Credential Based
Authentication or Windows Authentication. Credential Based
Authentication lets you access the database using SQL Server authentication.
If you select Credential Based Authentication, you must provide the
database user name and password to access the database. Windows
Authentication lets you access the database using a Windows user account
that can authenticate in to the SQL Server database. If you select Windows
Authentication, you can provide a domain user name and password to
access the vCenter Server database.
A database user name to access the vCenter Server database. Ensure that this
is not the same user that vCenter Server uses to connect to the vCenter Server
database.
If you have selected Windows Authentication, then provide a domain user
name to access the vCenter Server Database. The domain user name must be
of the form user@domain.com or domain\user. If you do not specify a
domain user name, then vCenter Chargeback Manager uses the details of the
domain user who started the current session of the vCenter Chargeback
Manager service to access the vCenter Server Database.
Password for the database user name or domain user name entered.
Select this option if you would like to register vCenter Chargeback Manager
as a plug-in to vSphere Client. If this option is selected, each time you log in
to this vCenter Server using the vSphere Client, the vCenter Chargeback
Manager plug-in is displayed on the vSphere Client. You can access the
vCenter Chargeback Manager from the vSphere Client as a vCenter Server
user. Ensure that you do not register more than one vCenter Chargeback
Manager instance as a plug-in for a single vCenter Server.
Select this option if you want the resource usage statistics from the vCenter
Server Database to be replicated in the vCenter Chargeback Manager
Database. Statistics starting from three months prior to adding the vCenter
Server are collected. vCenter Chargeback Manager considers the existing
vCenter Server inventory to have existed for the three month period prior to
adding the vCenter Server.
Chapter 2 Configuring Administration Settings
VMware, Inc. 19
vCenter Chargeback Manager User’s Guide
4 Click Add.
A dialog requesting you to add an SSL certificate for secure communication with the vCenter Server is
displayed.
5 Accept the SSL certificate request.
If you click Cancel, the add vCenter Server operation is cancelled.
The vCenter Server is added to the application and included in the table listing the vCenter Server instances.
What to do next
You can log in to the vCenter Server by using a vSphere Client and access the vCenter Chargeback
Manager plug-in if you have selected the Register As vSphere Client Plug-in option. You must, however,
provide the IP address or the DNS name of the vCenter Server during login. If you use localhost during login,
the plug-in might be unavailable.
Edit vCenter Server Information
Changes to the vCenter Server configuration must be manually reflected in the vCenter Chargeback Manager.
For example, if the vCenter Server user account password or the password for the vCenter Server database
user is changed, you must also reflect this change in vCenter Chargeback Manager.
If you change the SSL certificate on the vCenter Server or upgrade the vCenter Server, then you must modify
the vCenter Server information in vCenter Chargeback Manager to import the new SSL certificate. If the new
SSL certificate is not imported on to the vCenter Chargeback Manager machine, then communication with the
vCenter Server fails.
To modify the vCenter Server information in vCenter Chargeback Manager, you must have the Super User
role or the Administrator role. If you have the Administrator role, you can edit only those vCenter Server
settings that you have configured.
NOTE You cannot modify the vCenter Server ID, host name or IP address of the vCenter Server, and the vCenter
Server version number.
Procedure
1 In the Settings tab, clickvCenter Servers.
A table listing information about the vCenter Server instances added to the application is displayed.
2 Select the vCenter Server for which you want to modify the details, and click Edit.
The vCenter Server Information screen is displayed.
3 Modify the required vCenter Server details.
Option Description
vCenter Server Hostname/IP
vCenter Server Display Name
vCenter Server Description
vCenter Server Username
vCenter Server Password
FQDN or IP address of the vCenter Server. The IP address or host name
cannot be edited after the vCenter Server is added to the application.
A display name for the vCenter Server.
A description of the vCenter Server. This is optional.
User name to access the vCenter Server.
Password for the user name entered.
20 VMware, Inc.
Option Description
Database URL
URL to access the vCenter Server database.
For Oracle Database, this URL must have the format:
IP address/host name:TNS listener port
For example:
123.123.123.123:1521
For Microsoft SQL Server, this URL can be in the following formats:
IP address/host name\database instance name
or
IP address/host name
For example:
123.123.123.123\chargeback_db
You can also specify a well formed JDBC URL that starts with 'jdbc' and
contains the database name. If the vCenter Server database is on an Oracle
RAC environment, then you must provide a JDBC URL for the database.
Database Name
Database Type
Authentication Type
Database Username
Database Password
Register As vSphere Client Plug-in
Enable Stats Replication
Name of the vCenter Server database. For example, vim_vcdb, which is the
default name given by vCenter Server. If you are using Oracle Database, then
the database name can be either the service name or SID. If you are providing
the service name, ensure that you prefix the service name with a forward
slash (/). For example:
/
service_name
The database type can be either SQL Server (default) or Oracle.
This option is available only if you have set the Database Type to SQL
Server. You can set the Authentication Type to Credential Based
Authentication or Windows Authentication. Credential Based
Authentication lets you access the database using SQL Server authentication.
If you select Credential Based Authentication, you must provide the
database user name and password to access the database. Windows
Authentication lets you access the database using a Windows user account
that can authenticate in to the SQL Server database. If you select Windows
Authentication, you can provide a domain user name and password to
access the vCenter Server database.
A database user name to access the vCenter Server database. Ensure that this
is not the same user that vCenter Server uses to connect to the vCenter Server
database.
If you have selected Windows Authentication, then provide a domain user
name to access the vCenter Server Database. The domain user name must be
of the form user@domain.com or domain\user. If you do not specify a
domain user name, then vCenter Chargeback Manager uses the details of the
domain user who started the current session of the vCenter Chargeback
Manager service to access the vCenter Server Database.
Password for the database user name or domain user name entered.
Select this option if you would like to register vCenter Chargeback Manager
as a plug-in to vSphere Client. If this option is selected, each time you log in
to this vCenter Server using the vSphere Client, the vCenter Chargeback
Manager plug-in is displayed on the vSphere Client. You can access the
vCenter Chargeback Manager from the vSphere Client as a vCenter Server
user. Ensure that you do not register more than one vCenter Chargeback
Manager instance as a plug-in for a single vCenter Server.
Select this option if you want the resource usage statistics from the vCenter
Server Database to be replicated in the vCenter Chargeback Manager
Database. Statistics starting from three months prior to adding the vCenter
Server are collected. vCenter Chargeback Manager considers the existing
vCenter Server inventory to have existed for the three month period prior to
adding the vCenter Server.
Chapter 2 Configuring Administration Settings
VMware, Inc. 21
vCenter Chargeback Manager User’s Guide
4 Click Save.
If the SSL certificate on the vCenter Server has changed, a dialog requesting you to accept the new SSL
certificate is displayed.
5 Accept the SSL certificate request.
If you click Cancel, the modify vCenter Server operation is cancelled.
The modified information is reflected in the table displayed on the page.
Delete vCenter Server Information
If you no longer want to calculate costs and generate reports for the virtual machines managed by a vCenter
Server, you can remove the vCenter Server from the vCenter Chargeback Manager.
To perform this task, you must have the Super User role or the Administrator role. If you have the
Administrator role, you can delete only those vCenter Server settings that you have configured.
Procedure
1 In the Settings tab, clickvCenter Servers.
A table listing all the vCenter Servers is displayed.
2 Select the vCenter Server that you want to remove and click Delete.
If any of the entities of the vCenter Server are part of a chargeback hierarchy, the Manage linked entities
screen is displayed.
3 (Optional) Click Delete all these entries to remove the entities from the hierarchy permanently.
You can retain the entities by clicking Keep all these entries. If you choose to retain the entities, they will
be temporarily removed from the hierarchy and will appear automatically when you re-add the vCenter
Server at a later stage.
4 If none of the vCenter Server entities are part of any of the chargeback hierarchies, the a dialog box
confirming the delete operation request is displayed. Click OK.
Managing Data Collectors
When you install vCenter Chargeback Manager, you can optionally install a data collector. You can register
more than one data collector with a vCenter Chargeback Manager instance. You can also install the Cloud
Director Data Collector and the vShield Manager Data Collector.
All the data collectors registered with the application can be managed from the Settings tab. You must have
the Super User role to view and manage the data collectors.
n
View Data Collectors on page 23
vCenter Chargeback Manager stores and displays information about each data collector registered with
the application. The data collectors registered with the application and their corresponding details can
be viewed from the Settings tab.
n
Enable Data Collector on page 25
If a data collector registered with the application is disabled, you can enable it from the application.
n
Disable Data Collector on page 25
When a data collector is installed, it is registered with the application and is enabled by default. If you
do not want to use a data collector, you can disable it from the application.
n
Delete Data Collector on page 26
A data collector registered with the application can be removed or deleted.
22 VMware, Inc.
Chapter 2 Configuring Administration Settings
n
Configure VMware Cloud Director Data Collector on page 26
If you have installed the Cloud Director Data Collector, you must configure its properties from the Data
Collectors page of the Settings tab.
n
Configure vShield Manager Data Collector on page 27
If you have installed the vShield Manager Data Collector, you must specify the user name and password
to access the vShield Manager instances. You can set this access information from the Data Collectors
page of the Settings tab.
n
Modify Super User Password for Cloud Data Collectors on page 28
If you change the password of the super user that was used when installing the VMware Cloud Director
Data Collector and vShield Manager Data Collector, you must change the same from the Data Collectors
page to ensure that these data collectors function correctly.
View Data Collectors
vCenter Chargeback Manager stores and displays information about each data collector registered with the
application. The data collectors registered with the application and their corresponding details can be viewed
from the Settings tab.
Procedure
1 Click the Settings tab.
2 Click Data Collectors.
A table listing all the data collectors registered with the application and their corresponding details is displayed.
Registered Data Collectors
The Data Collectors page displays a table listing all the synchronization jobs that each registered data collector
is running for each vCenter Server added to the application. If multiple data collectors are running,
synchronization jobs are equally distributed among them.
The data collector runs two types of synchronization jobs: polling jobs and listening jobs. Polling jobs are jobs
that run periodically at fixed interval of time and poll the vCenter Server database to fetch the changes in the
database. Each time the job run completes, the last synchronization time for the job is updated. Stats
Synchronization and Storage Synchronization are polling jobs.
Listening jobs start once and perform the initial synchronization. These jobs then register a listener with the
vCenter Server database and listen continuously for any update. These jobs run continuously and are not
periodic. They are always in the Running state and never set to Done. These jobs update their status and the
last synchronization time only when an update in the vCenter Server database, for which the job is listening,
is processed successfully.
Table 2-1 lists the information displayed on the Data Collectors page.
Table 2-1. Information About Data Collectors Registered in the Application
Information Type Description
Data Collector ID The ID of the data collector defined in vCenter Chargeback Manager.
Data Collector Heart Beat The time stamp when the data collector was last known to be running. The data collector
updates this information with vCenter Chargeback Manager every 30 seconds. If vCenter
Chargeback Manager does not receive any update from the data collector for more than
150 seconds, then vCenter Chargeback Manager considers the data collector to be down
and reassigns the all jobs to another running data collector, if any.
Data Collector Host Name The name of the machine on which the data collector is running.
Registered Indicates if the data collector is enabled or disabled.
VMware, Inc. 23
vCenter Chargeback Manager User’s Guide
Table 2-1. Information About Data Collectors Registered in the Application (Continued)
Information Type Description
Data Collector Name The name of the data collector provided during the installation.
vCenter Server Name The display name of the vCenter Server added to the application.
Job Type The type of the synchronization job.
Job Interval The interval between consecutive job runs. The values can be:
Last Synchronize Time The time stamp when the synchronization job was last completed.
Job State The status of the synchronization job. The displayed values are:
n
Storage Synchronization: The data collector obtains the storage information for all
the virtual machines managed by the vCenter Server. For vSphere 4.0 and later, the
data collector fetches all the files of a virtual machine and the datastore information
of each file. For vCenter Server 2.5, the data collector fetches all the disks of a virtual
machine and the datastore details of each disk. For vSphere 5.0, the data collector
fetches the storage profiles and groups the datastores under the profiles that they
match.
When calculating the storage utilization, vCenter Chargeback Manager accounts for
thin provisioning and linked clones. The first run of this job might fail if the first run
of the Hosts & Clusters and VMs & Templates Synchronization job takes more than
5 minutes to complete. The VMware VirtualCenter Management Webservices
service must be running on the vCenter Server machine for the storage
synchronization to complete successfully. For vCenter Server 5.0, the VMware
vSphere Profile-Driven Storage service must also be running on the vCenter Server
machine for the storage synchronization to complete successfully.
n
Hosts & Clusters and VMs & Templates Synchronization: The data collector copies
the vCenter Server inventory in to the vCenter Chargeback Manager database. This
synchronization job ensures that the Hosts & Clusters view and VMs & Templates
view of the vCenter Server inventory are synchronized in the vCenter Chargeback
Manager database.
n
Datastore Synchronization: This synchronization job ensures that all information
about the datastore view of the vCenter Server are synchronized in the vCenter
Chargeback Manager database.
n
Network Synchronization: This synchronization job ensures that all information
about the network view of the vCenter Server are synchronized in the vCenter
Chargeback Manager database.
n
Stats Synchronization: If the Enable Stats Replication option is selected for a
vCenter Server added to the application, all the vital performance statistics required
for cost calculation is replicated in the vCenter Chargeback Manager database. This
synchronization job ensures that the statistics information is periodically replicated
in the vCenter Chargeback Manager database with the corresponding information
in the vCenter Server database.
IMPORTANT For vCenter Server 2.5 Update 3, ensure that the stats collection level is
set to 2 or above for the average memory usage counter to be available. If the stats
collection level is set to 1, the cost for actual memory usage cannot be calculated.
n
Global Configuration Synchronization: The data collector fetches global
configuration data of the vCenter Server and stores it in the vCenter Chargeback
Manager database. Currently, this synchronization job fetches the custom attributes
from the vCenter Server.
n
Not periodic: Indicates that the job runs eternally.
n
Positive number: Indicates the repetition interval in minutes. The consecutive job
starts n minutes from the completion of the earlier run of the job, where n denotes
the value you enter in this field.
n
Running: The job is in progress.
n
Waiting: The job is yet to start. It is either waiting to be assigned to a data collector
or waiting for the assigned data collector to start it.
n
Failed: The job has failed. If the job has failed, the job is reassigned to a data collector
after 10 minutes.
n
Done: Refers to jobs that are run at specific intervals and the previous run is
complete.
24 VMware, Inc.
Chapter 2 Configuring Administration Settings
Modify Job Interval
You can control the time interval between two consecutive job runs for jobs that do not run eternally.
Ensure that the job interval time specified is sufficient enough to run the job completely. The data collector
starts a job run only after the earlier job run is completed. If the specified interval is too small, then the job
might not start exactly after the specified minutes post the last synchronization time. The job will start only
after the earlier job run is completed.
Procedure
1 Click Edit in the Job Interval column.
The Change Job Interval screen is displayed.
2 Enter the new job interval.
The specified job interval must be in minutes.
3 Click Save.
The new job interval is displayed in the table.
Enable Data Collector
If a data collector registered with the application is disabled, you can enable it from the application.
Procedure
1 In the Settings tab, clickData Collectors.
A table listing all the data collectors registered with the application is displayed.
2 Select the data collector that you want to enable.
3 Click Enable.
Disable Data Collector
When a data collector is installed, it is registered with the application and is enabled by default. If you do not
want to use a data collector, you can disable it from the application.
IMPORTANT If only a single data collector is running, do not disable it. If disabled, the synchronization jobs
will not run and the data in the vCenter Chargeback Manager database will not be in sync with the data in the
vCenter Server databases.
Procedure
1 In the Settings tab, clickData Collectors.
A table listing all the data collectors registered with the application is displayed.
2 Select the data collector that you want to disable.
3 Click Disable.
The jobs assigned to the selected data collector are unassigned from it and the data collector is disabled.
VMware, Inc. 25
vCenter Chargeback Manager User’s Guide
Delete Data Collector
A data collector registered with the application can be removed or deleted.
IMPORTANT If only a single data collector is running, do not delete it. If deleted, the synchronization jobs will
not run and the data in the vCenter Chargeback Manager database will not be in sync with the data in the
vCenter Server.
Procedure
1 In the Settings tab, clickData Collectors.
A table listing all the data collectors registered with the application is displayed.
2 Select the data collector that you want to delete, and click Delete.
A dialog box confirming you action is displayed.
3 Click OK to confirm deletion.
The data collector is deleted and the synchronization jobs associated with the data collector are assigned to
other registered data collectors, if any.
Configure VMware Cloud Director Data Collector
If you have installed the Cloud Director Data Collector, you must configure its properties from the Data
Collectors page of the Settings tab.
Only users with the Super User role assigned to them can perform this task.
Configuring the Cloud Director Data Collector ensures that vCenter Chargeback Manager related events in
the vCloud Director are processed.
NOTE Only the vCenter Chargeback Manager related events are processed by the Cloud Director Data
Collector. To update the vCloud Director Org hierarchies in vCenter Chargeback Manager, the corresponding
vCenter Server must be added to vCenter Chargeback Manager and the vCenter Chargeback Manager data
collector must be running to synchronize the vCenter Chargeback Manager database with the vCenter Server
database. If the vCenter Chargeback Manager data collector is not installed or is not running, then the changes
will not be processed and the changes in the vCenter Server and the vCloud Director Org hierarchy is not
accounted for in vCenter Chargeback Manager.
Procedure
1 In the Settings tab, click Data Collectors.
2 Select the VMware Cloud Director tab.
3 Select a property and click Edit.
You can edit several properties for VMware Cloud Director Data Collector.
Property Description
VMware Cloud Director database
host
VMware Cloud Director database
type
VMware Cloud Director database
name
26 VMware, Inc.
IP address of the VMware vCloud Director database.
The type of database used to create the VMware vCloud Director database.
The permissible values are SQL_Server and Oracle.
Name of the VMware vCloud Director database.
Property Description
VMware Cloud Director database
port
VMware Cloud Director database
username
VMware Cloud Director database
password
Event processor job interval (in
seconds)
Failed events processor job interval
(in seconds)
Unprocessed VMware Cloud
Director chargeback event lifetime
(in seconds)
VM Instance job interval (in seconds)
VMware Cloud Director apply
overage charge on Allocation Pool
vDC
Port on which the VMware vCloud Director database is listening for request.
If no port details are specified, vCenter Chargeback Manager considers the
default database port.
VMware vCloud Director database user name.
Password for the VMware vCloud Director database user.
VMware Cloud Director Data Collector runs a job that reads and processes
the chargeback events in VMware vCloud Director. This property defines
the time in seconds between two such job runs. If the time between two job
runs is too large, then virtual machines that are created and removed within
this time frame might not be accounted for by vCenter Chargeback Manager
during cost calculation.
VMware Cloud Director Data Collector runs a job to clear failed chargeback
events in VMware vCloud Director. This property defines the time in seconds
between two such job runs.
This property defines the time for which an unprocessed event is retained in
the database. The default value is 10 days. After this lifetime period, events
are removed from the database because they are in an inconsistent state and
cannot be processed. Inconsistency can occur due to the following reasons:
n
Event was generated when it was not necessary.
n
Event fails to get persisted in the VMware vCloud Director database.
VMware Cloud Director Data Collector runs a job to apply the fixed costs
defined in the virtual machine instance price matrix on the virtual machines
in the vDCs (virtual data centers). This property defines the time in seconds
between two such job runs.
Set this flag to true to consider the percentage guarantee value along with
the allocation value for the computing resources. This is global flag and is
applicable for all Org vDCs in the Allocation Pool model. The default value
is false.
The Change Data Collector property screen is displayed.
Chapter 2 Configuring Administration Settings
4 Modify the property value and click Save.
What to do next
After you modify a property value, you must restart the data collector for the change to take effect.
You can test the connection to the vCloud Director database by clicking the Test VMware Cloud Director
database connection link.
Configure vShield Manager Data Collector
If you have installed the vShield Manager Data Collector, you must specify the user name and password to
access the vShield Manager instances. You can set this access information from the Data Collectors page of the
Settings tab.
The vShield Manager Data Collector cannot function if the user name and password for the vShield Manager
instances are not set. After installing the vShield Manager Data Collector, the vShield Manager instances do
not appear immediately in vCenter Chargeback Manager. You can see these instances in the application only
after the VMware Cloud Director Data Collector processes the vShield Manager-related events.
Only users with the Super User role assigned to them can perform this task.
Procedure
1 In the Settings tab, click Data Collectors.
2 Select the vShield Manager tab.
VMware, Inc. 27
vCenter Chargeback Manager User’s Guide
3 Select the property from the vShield Manager common properties section and click Edit.
You can modify the job interval for the external traffic statistics collector job run by the vShield Manager
Data Collector. vShield Manager Data Collector runs a job that collects broadband statistics from vShield
Manager for all the registered networks. The broadband statistics collector job interval defines the time in
seconds between two such job runs.
The Change Data Collector Property screen is displayed.
4 Modify the property value and click Save.
5 Select the required instance from the vShield Manager instances section and click Edit.
The Edit vShield Manager Setting screen is displayed.
6 Modify the property values and click Save.
You can modify the following settings for the selected vShield Manager instance.
Property Description
Host
User name
Password
Confirm password
Host name or IP address of the vShield Manager instance.
User name used to connect to the vShield Manager instance.
Password for the user.
Password for the user.
What to do next
If you modify the External traffic statistics collector job interval property value, you must restart the data
collector for the change to take effect. You need not restart the data collector if you have made modifications
only to the vShield Manager instances.
Modify Super User Password for Cloud Data Collectors
If you change the password of the super user that was used when installing the VMware Cloud Director Data
Collector and vShield Manager Data Collector, you must change the same from the Data Collectors page to
ensure that these data collectors function correctly.
You must have the Super User role to perform this task.
Procedure
1 On the Settings tab, click Data Collectors.
2 Select the VMware Cloud Director tab.
3 Click Change password for 'superuser' for cloud data collectors link.
Here, superuser is the user name used when installing vCenter Chargeback Manager.
The Change Password screen is displayed.
4 Enter the new password for superuser.
5 Confirm the new password.
6 Click Change Password.
What to do next
You must restart the VMware Cloud Director Data Collector after changing the password.
28 VMware, Inc.
Managing the Application License
If you have the Super User role, you can view the details of the current vCenter Chargeback Manager license
by clicking License on the Settings tab.
The following table lists the license information displayed on the License page.
Table 2-2. License Information
License Information Description
License Key The current license key used to access the application.
License Type The type of license used to access the application.
Activated On The date and time when the application was activated using the current license key.
Expiry Date The date on which the existing license will expire.
Count Type vCenter Chargeback Manager provides a CPU-based or VM-based licensing. This entry defines
whether the license in based on the number of CPUs or the number of virtual machines in your
virtual environment that is accounted for using this vCenter Chargeback Manager setup.
Current Count Used This entry indicates the current number of ESXi host CPUs or the virtual machines running on
the ESXi hosts that are accounted for by using your vCenter Chargeback Manager setup.
Maximum Count
Allowed
Is Valid Whether the current license is valid or not.
This entry indicates the maximum number of ESXi host CPUs or the virtual machines running
on the ESXi hosts that can be accounted for by using your vCenter Chargeback Manager setup.
This maximum limit is defined in the license.
Chapter 2 Configuring Administration Settings
Replace the Application License
You must replace an expired license with a valid license. You can also replace an existing valid license with
another valid license.
You must have the Super User role to perform this task.
Procedure
1 In the Settings tab, clickLicense.
A table listing the details of the license added to the application is displayed.
2 Click Replace.
The Replace License screen is displayed.
3 Enter a valid license key and click Replace.
The new license replaces the existing license. The details of the new license is displayed in the table.
Delete the Application License
An existing license can be removed from the application.
You must have the Super User role to perform this task.
IMPORTANT Removing a license will render the application unusable till another valid license is added.
Procedure
1 In the Settings tab, clickLicense.
A table listing the details of the license added to the application is displayed.
VMware, Inc. 29
vCenter Chargeback Manager User’s Guide
2 Select the license and click Delete.
A dialog confirming the action is displayed.
3 Click OK to confirm the deletion.
Manage Report View
vCenter Chargeback Manager provides a report view that is used by all the generated reports. You can
configure the report view to display a specific set of information in each of the generated reports.
Like most reports, the chargeback report has multiple sections, such as Header, Title, Body, and Footer.
The Title section appears only on the first page of the report. The contents in these sections can be modified as
per your requirements. The information to be displayed in the Body section is defined when creating the report.
The Header section is the report header that appears on all pages expect the first. The Footer section is the
report footer that appears on all the pages.
Changes made to the report view is reflected only in the reports generated after the report view is changed.
Existing archived reports are not affected by the changes made to the report view.
You must have the Super User role to perform this task.
Procedure
1 In the Settings tab, click Report View.
2 Select Header.
The Header section of the report view displays four sub-sections.
3 Select a sub-section from the Header section of the report view.
4 Select an option from the Header Settings section to display the required information in the selected sub-
section.
Option Description
Text
Image
Report Name
Report Description
None
The text that you want the report header to contain. For example, the name
of the organization.
An image that you want the header section to display. For instance, the
company logo. Ensure that the image size does not exceed 1MB.
The name of the report entered when generating the report.
A description of the report provided when generating the report.
(default) No information is displayed in this sub-section in the report.
Repeat this step to set the information for each sub-section as required.
5 Click Title.
The Title section of the report template displays nine sub-sections.
6 Select a sub-section from the Title section of the report template.
7 Select an option from the Title Settings section to display the required information in the selected sub-
section.
Option Description
Text
Image
Report Name
30 VMware, Inc.
The text that you want the report header to contain. For example, the name
of the organization.
An image that you want the header section to display. For instance, the
company logo. Ensure that the image size does not exceed 1MB.
The name of the report entered when generating the report.
Loading...