2.0
Table Of Contents
- vCenter Chargeback Manager User’s Guide
- Contents
- About the User's Guide
- Introduction to vCenter Chargeback Manager
- Configuring Administration Settings
- Authenticating and Managing Users, Roles, and Permissions
- Resource Based Authorization in vCenter Chargeback Manager
- Permissions Defined in vCenter Chargeback Manager
- Managing Roles
- Managing Users
- vCenter Chargeback Manager User Authentication
- Managing Chargeback Hierarchies
- Creating a Chargeback Hierarchy
- Managing a Chargeback Hierarchy
- View a Chargeback Hierarchy
- Add a vCenter Chargeback Manager Entity
- Add a vCenter Server Entity
- Rename a Chargeback Hierarchy or a Chargeback Entity
- Delete an Entity from the Hierarchy
- Delete a Chargeback Hierarchy
- Assign Attributes
- Move Entities Within a Hierarchy
- Allocate Computing Resource Units for a Chargeback Entity
- Share Virtual Machine Cost
- Backdate a Chargeback Hierarchy
- View Properties of a vCenter Server Entity
- Managing and Configuring vCenter Chargeback Manager Cost Elements
- Generating Reports
- Monitoring System Health
- Administration Utilities
- Index
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.
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.
Job Interval The interval between consecutive job runs. The values can be:
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.
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
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.
vCenter Chargeback Manager User’s Guide
24 VMware, Inc.