Technical Note:

Using VMware

vCenter

Chargeback Manager

with
VMware vCloud

Director

T E CH NI C AL WHI T E PAP E R
T E C H NI C AL WH I T E PAP E R / 2
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Table of Contents
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
vCenter Chargeback Manager Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
vCenter Chargeback Manager Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Data Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
vCenter Chargeback Manager Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
vCenter Chargeback Manager API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Data Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Hierarchy Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Allocation Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Allocation Unit Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Cost Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Billing Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Base Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Fixed Costs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
VM Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
vApp Lifecycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Congure Costs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Report Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Cost Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Calculating Resource Costs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Calculating Fixed Costs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Calculating VM Instance Costs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Integration with External Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Key Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Appendix A: Conguration Maximums. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Appendix B: Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
T E C H NI C AL WH I T E PAP E R / 3
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Introduction
VMwarevCloudDirectormakesbroaddeploymentofcloudspossiblebyenablingself-serviceaccessto
infrastructureresources.Itprovidestheinterface,automationandmanagementfeaturesetthatenables
enterprisesandserviceproviderstosupplyVMwarevSphereresourcesasaWeb-basedservice.Withthe
adventofmassivecloudenvironments,keepingtrackofdynamiccloudresourcesbecomesanincreasingly
importanttask.
VMwarevCenterChargebackManagerprovidesthemeteringcapabilitytomeasure,analyze,andreporton
utilizationandcostsassociatedwithVMware-basedcloudinfrastructures.Itoferstheabilitytocongureand
associatevariouscostmodelswithvCloudDirectorentities.ThecosttransparencyenabledbyvCenter
ChargebackManagerallowscloudproviderstovalidateandadjustnancialmodelsbasedonresource
consumption.
ThispaperhasbeenwrittentoexplaintheintegrationofvCloudDirectorandvCenterChargebackManager.
ShareddeploymentdesignconsiderationsforvCenterChargebackManagerarealsocovered.Theintended
audienceisvirtualizationpersonnelwhohaveastrongunderstandingofvSphereandvCloudDirectorconcepts
andterminology.
T E C H NI C AL WH I T E PAP E R / 4
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Overview
TheprocessforinstallingandconguringvCenterChargebackManagerisasfollows:
1. Install vCenter Chargeback Manager along with the vCenter Chargeback Manager, VMware vCloud Director,
and VMware vShield Manager data collectors. Refer to the vCenter Chargeback Manager Installation and
Upgrade Guide for detailed installation instructions.
2. Validate vCenter Chargeback Manager data collector settings. Change vShield Manager login credentials
accordingly.
3. Add all vCenter Servers attached to the VMware vCloud Director instance. Refer to the vCenter Chargeback
Manager Users Guide for detailed instructions.
4. Validate synchronization of inventories between vCloud Director and vCenter Chargeback Manager.
5. Based on approved service denition, create and congure cost models, xed costs or virtual machine
instance.
6. Congure costs for specic vCenter Chargeback Manager entities.
7. Schedule reports manually or leverage automatic scheduler.
8. Create users and associate the appropriate roles and access.
9. (optional) Integrate vCenter Chargeback Manager with external systems.
Thistechnicalnoteprovidesadditionaldetailsandbestpracticesforeachstepintheprocess.
Architecture
vCenterChargebackManagercomponentsinclude:
vCenterChargebackManagerserver
vCenterChargebackManagerdatabase
vCenterChargebackManagerdatacollectors
vCenterChargebackManagerwebinterface
vCenterChargebackManagerAPI
ThedatacollectorsgatherandsenddatatothevCenterChargebackManagerdatabase.ThevCenter
ChargebackManagerWebinterfacehandlescostmodeling,usermanagement,andreportgeneration.
Integrationwithothermanagementproducts,suchasVMwarevCenterOrchestratorandVMwarevCenter
OperationsManager,isavailablethroughtheappropriateplug-in/adaptor.
T E C H NI C AL WH I T E PAP E R / 5
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
CBM DB
JDBC
HTTP(S)
CB Plug-in
HTTP(S) VC APIs/JDBC
vSphere
Client
Data
Collectors
CBM Application/
Web UI
Multi VC Deployment
VC2
VC1
vCenter Chargeback
Server
Stores Org Hierarchy
Stores Cost/Rate Plan
Global CB Conguration
VC DB Statistics
Conguration
Reporting
Rest API
vCenter Orchestrator
vCenter Operations
ITBM
Figure 1.VMwarevCenterChargebackManagerComponents
vCenter Chargeback Manager Server
ThevCenterChargebackManagerserverrunsthewebinterface,loadbalancer,anddatacollectorservices.This
servercanbevirtualorphysicalandhasthefollowingrecommendedspecications:
2.0GHzorfasterIntelorAMDx86processor
4GBormoreofRAM
3GBdiskstorage
1GbEthernet(1GbE)adaptor
RefertothevCenterChargebackManagerInstallationandUpgradeGuideformoredetails.
vCenterChargebackManagerserverscanbeclusteredtogethertoprovideimprovedperformanceand
availabilityforthewebinterface.AclustercongurationleveragestheApacheloadbalancer,whichisbundled
withthevCenterChargebackManagersoftware.Thebuilt-inloadbalancercanbeinstalledonanyvCenter
ChargebackManagerserverinstance,butcannotbereplacedbyathird-partyloadbalancer.Allinstancesina
clustermustrunthesameversionofvCenterChargebackManager.
T E C H NI C AL WH I T E PAP E R / 6
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Chargeback
database
Session 1
1
2
3
Load Balancer
Chargeback
Server 3
Chargeback
Server 1
Chargeback
Server 2
Session 2
Session 3
Figure 2.UserRequestRoutingwithClustering
Loadbalancingisactive/active.Eachuserrequest,whetheritcomesfromthewebinterfaceorAPI,routes
throughtheloadbalancer.TheloadbalancerforwardstherequesttoavCenterChargebackManagerinstancein
thecluster,basedonthenumberofrequestscurrentlyservicedbyeachinstanceinthecluster.Stickysessions
areenabled,sosessionsalwayssticktoonevCenterChargebackManagerserver.Iftherearemultiplesessions,
theloadbalancerusesthenumberofrequeststofndthebestworker.WithmultiplevCenterChargeback
Managerservers,thereportprocessingloadisbalancedbytheinternalQuartzScheduler.
LosingthevCenterChargebackManagerserverthatcontainstheloadbalancerremovesaccesstotheWeb
interface.PointuserstotheIPaddressesoftheremainingvCenterChargebackManagerserversuntilthefrst
serverisrestored.
vCenter Chargeback Manager Database
ThevCenterChargebackManagerdatabasestoresorganizationhierarchies,cost/rateplansandglobalvCenter
ChargebackManagerconfgurationdata.Currently,MicrosoftSQLExpress,MicrosoftSQLServerandOracle
aresupported.
SQLscriptsareavailablethatenableadministratorstomanageandretrieveusagedatafromthevCenter
ChargebackManagerdatabase.RefertothevCenterChargebackManagerUsersGuideformoredetails.
Data Collectors
vCenterChargebackManagerusesdatacollectorstopullinformationfromvarioussources.Eachdatacollector
runsonitsownschedule,sopollingintervalsareuniquetoeachandaremodifable.
vCenter Chargeback Manager data collectorConnectstovCenterServerstopullvCenterinformation.Add
connectionstoallvCenterServersattachedtothevCloudinstance.VMwarevSpherevAppvirtualmachines
arenotdisplayedinthevCloudhierarchiesuntiltheirrespectivevCenterServersareregisteredwithvCenter
ChargebackManager.
T E C H NI C AL WH I T E PAP E R / 7
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
vCloud Director data collector ConnectstothevCloudDirectordatabaseandmonitorsallvCenterCharge-
backManagerrelatedevents.ThevCloudDirectordatacollectorpopulatesthevCenterChargebackManager
databasewithvCloudhierarchies,vCloudentitiesandallocationunitinformation.
vShield Manager data collector ConnectstovCloud-associatedvShieldManagerstocollectstatisticsfor
networksincludedinvCloudhierarchies.
Chargeback
Manager
database
JDBC
JDBC
JDBC
JDBC
JDBC
JDBC
JDBC
1:1
many: 1
many: 1
SOAP
REST
REST
REST
Chargeback
Manager
Server
vCloud
Director
database
vShield
Manager
vCenter
database
vCloud data
collector
Chargeback
data collector
VSM data
collector
vCenter
Server
Figure 3.VMwarevCenterChargebackManagerDataCollectors
InstalladditionalvCloudandvShieldManagerdatacollectorsonseparateserversforincreasedavailability.
Datacollectorinstancesupdatetheirheartbeatevery480seconds.Ifinstance1failsupdatingitsheartbeat,
instance2takesovereventprocessingafter1,200seconds(active/passive).Thevaluesarenotusermodifable.
Bydefault,thevCloudDirectordatacollectorprocesseschargeableeventsinthevCloudDirectordatabase
everyfveminutes.Thiscanbereducedtothirtyseconds,orincreased,dependingonthefrequencyof
operationsinvCloudDirector.Chargeableeventsthatfailtogetprocessedareretainedinatemporarystorefor
uptotendays(defaultsetting)andarereprocessedwhenthesystemisavailableagain.
AvCenterChargebackManagerenvironmentcanhavemultiplevCloudDirectordatacollectors,butitcan
connecttoonlyonevCloudDirectordatabase.WithoutvCloudDirector,vCenterChargebackManagercannot
connecttovShieldManager.ThereisadependencybetweenthevCloudDirectordatacollectorandthevShield
Managerdatacollector.ThevCloudDirectordatacollectorpopulatesthenetworkIDsandcorresponding
MOREFIDs,whicharethenconsumedbythevShieldManagerdatacollector.
ThevShieldManagerdatacollectorcarriestheexternaltrafcinformationforprivateroutedorganization
networks,routedvAppnetworks,andfencedvAppnetworks.IfaroutedorfencedvAppnetworkisconnected
toaprivateroutedorganizationnetwork,theexternaltrafcinformationofthecorrespondingvirtualmachineis
recordedatthevAppnetworklevelandtheorganizationnetworklevel.
vShieldManagersareautomaticallydiscoveredbythevCloudDirectordatacollector.Afterinstallation,make
suretosettheappropriateusernameandpasswordforallvShieldManagersinthevCenterChargebackManager
Webinterface.Ifthepasswordisnotsetproperly,noexternalnetworkstatisticswillbegathered.
OnthevCloudDirectorsystemsettingspage,thereisauser-congurableeldthatdenesthenumberofdays
tokeepvCenterChargebackManagereventhistorywithinthevCloudDirectordatabase.Bydefault,thisissetto
365days.Afterthat,thereisadailyjobthatrunsinthevCloudDirectordatabaseonceevery24hours,cleaning
upjobsolderthan365days.
T E C H NI C AL WH I T E PAP E R / 8
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
NOTE: To avoid errors in event processing and data collection, ensure that all vCloud componentsincluding
vSphere environment, vCloud Director, vShield Manager, and vCenter Chargeback Managerare pointed to the
same network time source.
vCenter Chargeback Manager Web Interface
AccesstothevCenterChargebackManagerWebinterfacerequiresasupportedbrowserandAdobeFlash
Player.vCenterChargebackManagerprovidesautilitytogenerateself-signedSSLcertifcates.
vCenter Chargeback Manager API
ThevCenterChargebackManagerAPIisbasedonrepresentationalstatetransfer(REST)andprovidesa
programminginterfaceforvCenterChargebackManagerfunctionality.Thisincludeshierarchymanagement,
costconguration,andcostreporting.AllactionsintheWebinterfacecanbeperformedthroughthe
vCenterChargebackManagerRESTAPI.FormoreontheAPI,refertothevCenterChargebackManager
ProgrammingGuide.
vCenterChargebackManagerAPIsaredividedintothefollowingcategories:
Administration
Costmanagement
Hierarchymanagement
Reportmanagement
Usermanagement
Eventmanagement
Search
ThevCenterChargebackManagerSDKforJavaprovidespackagescontainingclassesandmethodsthat
encapsulatetheinterfaces,objectsandoperationssupportedbythevCenterChargebackManagerAPI.Java
developerscanusetheSDKtoquicklybuildapplicationsthatintegratewiththevCenterChargebackManager
platform.TheSDKusestheJAXBframeworktocreateclassesforresourcesdenedinthevCenterChargeback
ManagerAPIXMLschemas.
T E C H NI C AL WH I T E PAP E R / 9
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Data Flow
vCenterChargebackManagergathersdatafromvarioussourcesthroughdatacollectors.Theowofdatafora
vCloudDirectorwithvCenterChargebackManagerdeploymentisdepictedinFigure4:
vCloud
Director UI
vCloud API
vCloud
cell
REST
REST
REST
JDBC
CBM
Server
CBM
DB
Billing
System
vCenter
DB
vShield
Manager
vCD
DB
vCenter
Server
Chargeback
data
collector
vCloud
data
collector
VMS data
collector
1 2 3
4
Figure 4. VMwarevCenterChargebackManagerDataFlow
1. vCloud entities are created within vCloud Director through the vCloud Director API or vCloud Director Web
console. These entities persist in the vCloud Director database.
2. The vCloud Director data collector connects to the vCloud Director database to process chargeback-
specifc events. External network trafc counters are pulled from vShield Manager by the VSM data
collector.
3. The vCloud Director and vShield Manager data collectors make vCenter Chargeback Manager API calls to
perform chargeback-related functions. If changes must be made to data collector settings, the settings are
updated directly in the vCenter Chargeback Manager database.
4. Optionally, the vCenter Chargeback Manager REST APIs can be leveraged to pull XML reports from vCenter
Chargeback Manager. The XML reports are parsed and passed to the external billing system.
Hierarchy Management
AchargebackhierarchyisautomaticallycreatedinvCenterChargebackManagerwhenanorganizationis
createdinvCloudDirector.EachimportedorganizationappearsasavCenterChargebackManagerhierarchy
andincludesalltheorganizationvirtualdatacenters(vDCs),themediaandtemplateles,vApps,virtual
machinesandnetworks.
Allorganizationhierarchieshavefourfolders:AllocationPool,Networks,PayAsYouGoandReservationPool.
OrganizationvDCsareassignedtofoldersbasedontheallocationmodelcongured.TheNetworksfolder
consistsofallthenetworksdenedintheorganization.
EachorganizationvDChastwofolders:MediaandTemplateFilesandvApps.TheMediaandTemplateFiles
folderconsistsofmedialesandtemplatelesassociatedwiththeorganizationvDC.ThevAppfolderincludes
allthevAppscreatedintheorganizationvDC.EachvAppconsistsofthecorrespondingvirtualmachinesanda
NetworkfoldercontainingtheorganizationnetworksusedbythevApp.
Bydefault,thepollingintervalbetweenvCloudDirectorandvCenterChargebackManagerisveminutes.Thisis
auser-congurablesettingthatcannotgobelowthirtyseconds.Thereisnooptiontorefreshorresynchronize
withvCloudDirector.
T E C H NI C AL WH I T E PAP E R / 1 0
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
BackdatefunctionalityisnotcurrentlyavailableforvCloudhierarchies;itcanbeappliedagainstonly
vCenterhierarchies.
Customattributescanbedenedagainstanyobjectwithinthehierarchy.Bydefault,thesystemcreates
anattributecalledvCloudEntityID,whichisanidentiferthatprovidesauniquemappingtothecorresponding
vCloudDirectorentity.Thissystem-denedattributeindicatestheobjecttypeandIDasstoredinthe
vCloudDirectordatabase(e.g.,vCloudOrgEntity-123456789,vCloudvDCEntity-123456789,
vCloudVMEntity-123456789).
IfavApp,network,orcatalogleisdeletedusingvCloudDirector,itisautomaticallyremovedfromvCenter
ChargebackManager.IfanorganizationororganizationvDCisdeletedusingvCloudDirector,itremainsin
vCenterChargebackManagerwithDELETED_pre-pendedandatimestamppost-pendedtothename.
Costdataassociatedwiththatorganization/chargebackhierarchyisnotautomaticallydeleted.Thesehierarchies
persistuntildeletedfromthevCenterChargebackManagerUI.
NOTE: If an object or hierarchy is deleted using vCenter Chargeback Manager but still exists in vCloud Director,
this is an irreversible operation. There is no method for selectively resynchronizing the hierarchy structure
between the two products. vCloud hierarchies deleted from vCenter Chargeback Manager are not recreated
by the vCloud Director data collector. Exercise caution when deleting hierarchy objects within vCenter
Chargeback Manager.
Allocation Units
vCenterChargebackManagertracksresourceallocationsforallvCloudentitiesineachhierarchy.ThevCloud
DirectordatacollectorsetsallocationunitvaluesinvCenterChargebackManager.Whentheallocationschange
invCloudDirector,theallocationunitsareupdatedaccordingly.
NOTE: For vCloud entities such as vDCs and vApps, vCenter Chargeback Manager solely tracks allocation. Usage
or reservation data from vCenter Server is not correlated. vCenter Chargeback Manager gets usage and
reservation data for the virtual machines pulled from vCenter Server.
AllocationPoolvDCshaveallocationunitsassignedattheorganizationvDClevel.AllocationunitvaluesforCPU
andmemoryarebasedontheoverageagscongured.ModifytheVMware vCloud Director apply overage
charge on Allocation Pool vDCattributeonthevCloudDirectordatacollectortoenableordisableoverage
charging.
Ifsettofalse(default),allocationunit=conguredlimitinvCloudDirector.
Ifsettotrue,allocationunit=conguredlimitinvCloudDirector*percentageofresourcesguaranteed.
Thisenablesoveragecharging.
Forexample:
vCloudDirectormemoryallocation=10GB,guarantee=50percent
globaloverageag=true
allocationunit:10GB*50percent=5GB
ItispossibletooverridetheglobalsettingbyassigningtheEntityLevelOverageFlag attributeonanindividual
entity.OverageagsareapplicableonlytonewlycreatedAllocationPoolvDCs.Theallocationunitsofexisting
AllocationPoolvDCsarenotchanged.
ReservationPoolvDCshaveallocationunitsassignedattheorganizationvDClevel,withtheallocationunitequal
totheconfguredlimitinvCloudDirector.Forthisallocationmodel,theCPUandmemoryreservationsarefully
reserved(settothelimit)andthecustomershouldbebilledaccordingly.
PayAsYouGovDCshaveallocationunitsassignedatthevirtualmachinelevel.Parententitiesdonothave
allocationunitsassigned.vCPUcount,totalmemoryandtotalstoragemetricsaretracked.Ifvirtualmachinedetails
donotappear,ensurethataconnectiontothevCenterServerhostingthecloudworkloadshasbeenestablished.
T E C H NI C AL WH I T E PAP E R / 1 1
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
StorageallocationunitsforvCloudentitiesaresetasthick,regardlessofprovisioning.Ifthebillingpolicyuses
theusageattributeforstorage,itispossibletochargeforthin-provisioneddisksasthick-provisioneddisks.
Toviewallocationunits,gotoManage Hierarchy,selectthehierarchy,right-clicktheobjectandselect
Set allocation units.ClickShowtoviewhistoricalallocationunits.
NOTE: Do not set any allocation units on vCloud objects, because this is done automatically by the vCloud
Director data collector. If allocation units are modied in the vCenter Chargeback Manager Web interface, they
persist until overridden by a vCloud Director chargeback event.
TheallocationunitstrackedforvCloudobjectsarelistedinTable1.
OBJECT PAY AS YOU GO ALLOCATI ON
POOL
RESERVATI ON
POOL
OrganizationVirtual
Datacenter(vDC)
None CPU
Memory
Storage
CPU
Memory
Storage
vApp None None None
VirtualMachine vCPU
Memory
Storage
vCPU
Memory
Storage
vCPU
Memory
Storage
Template Storage Storage Storage
MediaFile Storage Storage Storage
Network DHCP
NAT
Firewall
EnabledIPSecVPN
TunnelCount
CountofNetworks
DHCP
NAT
Firewall
EnabledIPSecVPN
TunnelCount
CountofNetworks
DHCP
NAT
Firewall
EnabledIPSecVPN
TunnelCount
CountofNetworks
Table 1.VMwarevCloudObjectAllocationUnits
ExternalnetworkRx/TxistrackedbyvShieldManagerdatacollectorbypollingvShieldManager,notvCenter
Server.ThedatacollectorgathersinformationforExternal Network Routed Connection for Org and Routed or
Fence Deploy of vApp Network.ExternalnetworkRx/TxiscollectedonlybythevShieldManagerdata
collector.NetworkRx/TxiscollectedbythevCenterChargebackManagerdatacollector.Therefore,useexternal
networkRx/TxratherthannetworkRx/TxforvCloud-specicnetworkentities.
ThevShieldManagerdatacollectorcompilesinformationonexternalnetworkRx/Txandnoothercounters.
NetworkservicecounterssuchasNAT,DHCP,Firewall,andEnabledIPSecVPNTunnelCountaregatheredby
thevCloudDirectordatacollector.Thenetworkservicesarechargedbasedontheservicebeingenabledor
disabledforaparticularnetwork(disabled=0orenabled=1forthiscounter).Forexample,ifyouset$1/day
forDHCP,thechargedependsonwhetherDHCPisenabledordisabledforthatdeployednetwork
(1or0respectively).
T E C H NI C AL WH I T E PAP E R / 1 2
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
The(NA)metricunitforNAT,DHCPandFirewallresourcesindicatesthatthevShieldManagerdatacollector
tracksthecountofvShieldEdgeswiththosespecifcservicesenabled.
CountofnetworksissetintheallocationunitsontheNetworksfolder.Eachchangetonumberofnetworksis
trackedbyvCenterChargebackManager.
Figure 5.CountofNetworks
Allocation Unit Examples
AllocationPoolexample
OrganizationvDCcreatedusingtheAllocationPoolmodel
CPU=10GHz,20percentreserved
Memory=20GB,20percentreserved
Storage=100GB,thinprovisioned
Globaloveragefag=false
Allocation units:CPU=10.0GHz,Memory=20.0GB,Storage=100.0GB
Figure 6.VMwarevCloudDirectorAllocationPoolvDCConguration

T E C H NI C AL WH I T E PAP E R / 1 3
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Figure 7. VMwarevCenterChargebackManagerAllocationUnits
ReservationPoolexample
OrganizationvDCcreatedusingtheReservationPoolmodel
CPU=10GHz,Memory=20GB,Storage=100GB
Allocation units: CPU=10.0GHz,Memory=20.0GB,Storage=100.0GB
PayAsYouGoexample
OrganizationvDCcreatedusingPayAsYouGomodel
vAppdeployedinPAYGvDC
vCPUcount=2,Memory=4GB,Storage=40GB
Allocation units: vCPU=2.0,Memory=4.0GB,Storage=40.0GB
AlthoughtheAllocationPoolandReservationPoolexamplesdiferastothepercentageofguaranteed
resources,thetwovDCsaresizedidenticallytotheenduserandvCenterChargebackManager.Without
overageenabled,theallocationunitsforthetwovDCsarethesame.
AlthoughactualCPUGHzallocationisnotprovidedforPAYGentities,itispossibletocalculatethisvalueby
multiplyingthevCPUcountbythevCPUspeedsetonthePAYGorganizationvDC.Forinstance,ifthevCPU
speedissetto1vCPU=1GHz,thevCPUcountalwaysequatestotheCPUallocation(vCPUCountvalue=
CPUGHz)foreachvirtualmachine.
AftervCenterChargebackManagerhasallocationunitspopulatedforvCloudentities,costcalculationscanbe
performedthroughtheuseofcostmodels,billingpoliciesandxedcosts.
T E C H NI C AL WH I T E PAP E R / 1 4
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Cost Models
Costmodelsareusedtoassociatebaserates,billingpoliciesandxedcostswithchargeableentities.
vCenterChargebackManagercomeswiththefollowingdefaultcostmodelsforvCloudDirectorentities.These
vCD-speciccostmodelsaremappedtotheappropriatebillingpolicyandhavenobaseratesdened.
vCloudDirectoractualusagecostmodel
vCloudDirectorAllocationPoolcostmodel
vCloudDirectorNetworkscostmodel
vCloudDirectoroverageAllocationPoolcostmodel
vCloudDirectorPayAsYouGoxed-basedchargingcostmodel
vCloudDirectorPayAsYouGoresourcebasedchargingcostmodel
vCloudDirectorReservationPoolcostmodel
UsethedefaultvCloudDirectorcostmodelsordefnenew,customcostmodels.DonotusethedefaultvCenter
ChargebackManagercostmodel,whichhaspreexistingbaseratesdened.
UsethePayAsYouGoxed-basedchargingcostmodelifyouintendtochargeaat,xedfeepervirtual
machine;usethePayAsYouGoresource-basedchargingcostmodelifyouintendtochargebasedonthe
amountofvCPU,memoryandstorageallocatedtothevApp.
ConsiderthefollowingoptionsforapplyingcoststovCloudentities:
Defnestandardunitsofconsumption(small,medium,large,x-large).Createcostmodelsforeachallocation
type.DenexedcostsforeachunitofconsumptionandapplythemtotheappropriatevCloudvDCentities.
Createacostmodelforeachallocationtypeandsetbaserates.ApplythecostmodeltothevCloudentity
regardlessofallocationsize.Thisassumesthatthewantedchargescaleslinearlywithchangesinallocation
units.Forexample,a2GHz,4GBvirtualmachineisdoublethecostofa1GHz,2GBvirtualmachine.
Determinepricingforrangeofoferingsandcreatevirtualmachinematrices.
EachcostmodelcontainsatabforOther Costs,whichincludedenablexedcostsforguestoperatingsystems
andvServicessuchasVMwarevSphereHighAvailability(VMwareHA),VMwarevSphereFaultTolerance
(VMwareFT)andvirtualmachinecreationanddeletioncosts.
Billing Policies
BillingpolicyexpressionsdenehowvCenterChargebackManagerassociatesacosttoaparticularmetered
resource.Theattributesavailablefortheresourcedependontheresourcetype.Forexample,memoryhasthe
followingassignableattributes:
AllocationCustomallocationunitvaluesetinvCenterChargebackManager
SizeConfguredsizeoftheresource
UsageUsageoftheresource
ReservationReservationsetfortheresource
Figure6depictsagraphoftheattributesformemoryovertime.Typically,onlyusageshowsvarianceunlessthe
usermodiesthesize,allocationorreservationoftheresource.
T E C H NI C AL WH I T E PAP E R / 1 5
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Figure 8. MemoryAttributesExample
Therefore,thebillingpolicyindicatestovCenterChargebackManagerwhichattributetouseforeachmetered
resourcewhencalculatingcostsforreportgeneration.WithvCloudentities,theallocationunitvalueissetbythe
vCloudDirectordatacollectorandmapstothelimitspeciedinvCloudDirector.
NOTE: Fixed costs are not included by default in any of the above billing policies, with the exception of Pay As
You Go xed charging. Inclusion of xed costs can be enabled for any of the above policies by selecting
Add/Include Fixed Cost in the Edit Billing Policy wizard.
Figure 9.IncludingFixedCostsinBillingPolicy
Youcanapply95th-percentilebillingtoexternal network transferrateandexternal network receiverateby
addingtheresourceandselectingBurstable Utilizationastheattribute.vCenterChargebackManagerperforms
thecalculationondailydatarecordedfromvShieldManager.
vCenterChargebackManagercomeswiththefollowingdefaultvCloudDirectorbillingpolicies:
vCloudDirectorbillingpolicyactualusage
vCloudDirectorbillingpolicyAllocationPool
vCloudDirectorbillingpolicyNetworks
vCloudDirectorbillingpolicyOverageAllocationPool
vCloudDirectorbillingpolicyPayAsYouGoxed-basedcharging
vCloudDirectorbillingpolicyPayAsYouGoresource-basedcharging
vCloudDirectorbillingpolicyReservationPool
T E C H NI C AL WH I T E PAP E R / 1 6
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
OtherdefaultbillingpoliciesarespecifctovCenterServeronly(e.g.,fxedcostandCPUreservation).Usethe
defaultvCloudDirectorbillingpoliciesordenenewbillingpolicies.
Table2presentstheexpressionsusedtoconstructthedefaultvCloudbillingpolicies.
BI LLI NG POLI CY RESOURCE EXPRESSI ON
ActualUsagePool Countofnetworks
EnabledIPsecVPNtunnelcount
NATservice
DHCPservice
Firewallservice
Allotherresources
Allocation
Allocation
Allocation
Allocation
Allocation
Usage
AllocationPool Externalnetworktransfer
Externalnetworkreceive
Allotherresources
Usage
Usage
Allocation
Networks Externalnetworktransfer
Externalnetworkreceive
Allotherresources
Usage
Usage
Allocation
OverageAllocationPool CPU
Memory
Externalnetworktransfer
Externalnetworkreceive
Allotherresources
Usage
Usage
Usage
Usage
Allocation
PayAsYouGo
Fixed-Based
Fixedcost
Externalnetworktransfer
Externalnetworkreceive
Allotherresources
Include
Usage
Usage
Allocation
PayAsYouGo
Resource-Based
vCPU
Memory
Externalnetworktransfer
Externalnetworkreceive
Allotherresources
If(vmpoweron){
allocation
}
if(vmpoweron){
allocation
}
usage
usage
allocation
ReservationPool Externalnetworktransfer
Externalnetworkreceive
Allotherresources
Usage
Usage
Allocation
Table 2.VMwarevCloudBillingPolicyExpressions
Base Rates
Baseratesarethosechargedtometeredcomputingresourcesoveraspecictimeinterval.Workwiththe
appropriatestakeholderstodenebaseratesandxedcosts.Intheabsenceofconcretecosts,useapproximate
valuestoprovideanestimation.
vCenterChargebackManagerincludesabuilt-inbaseratecalculatortohelpcomputebaseratesforCPU,
memoryandstorage.RefertothevCenterChargebackManagerUsersGuidefordetailedinstructions.
T E C H NI C AL WH I T E PAP E R / 1 7
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Fixed Costs
FixedcostsarecostsdefnedforanyresourcesnotdirectlymeteredbyvCenterChargebackManager.For
example,aprovidermightwanttoinjectcostsfordatacenterspace,power,cooling,one-timesetupfee,
andphysicalloadbalancersintothecustomerscostreport.
vCenterChargebackManagercanconsidervirtualmachinestatewhenapplyingxedcoststoentities
containingvirtualmachines.Bydefault,xedcostsareprorated.Itispossibletodisableprorationifwanted.
Afterdeningxedcosts,applythexedcoststhroughtheCongure Costtab.
VM Instance
VMInstanceenablesthecreationofamatrixoffxedcoststhatapplytoahardbundleofvCPU(count)and
memory(MB).VMInstancematricesarelinkedwithacostmodelandconsistofthehierarchyselectioncriteria,
axed-costtableandadefaultxedcost.Selectioncriteriacanbebasedonname-patternmatchingorcustom-
attributematching.VMInstanceusesasteppingfunction,wherethevirtualmachinechargestepsuptothenext
instancesize.Costsareappliedonlyforthedurationwhenavirtualmachineispoweredonandisnotprorated.
VMInstancecostingisspecictoPayAsYouGovDCs.
Figure 10.VMInstanceMatrix
Multiplecostmatricescanbecreatedforacostmodelandorderedbyselectioncriteriapriority.Inthiscase,the
criteriamustbeuniqueforeachmatrix.
SeetheConfguringaPricingMatrixforVirtualMachinessectioninthevCenterChargebackManagerUsers
Guideforadditionaldetails.
T E C H NI C AL WH I T E PAP E R / 1 8
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
vApp Lifecycle
PayAsYouGoserviceoferingsmonitortheconsumptionofvSphereresourcesduringthelifecycleofavApp.
WhenvAppsareinstantiatedorcomposed,vCloudDirectorinstructsvCenterServertobeginacloneorcreate
operation.StorageresourcesareconsumedduringthisprocessandareuseduntilthevAppisdeleted.Table3
illustrateshowvApporvirtualmachineoperationscorrelatetotheusageofCPU,memory,networkand
storageresources.
vAPP UI VM UI VCLOUD DI RECTOR API CPU MEMORY NETWORK STORAGE
Add/New Instantiate/Compose

Start
Deploy
PowerOn PowerOn
Reset Reset Reset
Suspend Suspend(vApp)
Suspend Suspend(virtualmachine)
ShutDown
Reboot

Stop
PowerOf PowerOf
Undeploy
Delete Delete Delete
Table 3. VMwarevSpherevAppResourceUsageLifecycle
Congure Costs
CostscanbeindividuallyconguredonvDCs,vApps,virtualmachines,media,templatelesandnetworks
withinanorganization.Fixedcostsandratefactorscanbesetforeachcomputingresourceforaselectedcost
model.Thisenablesdiferentiationofcostingbetweenhierarchieswhileusingthesamecostmodel.For
example,youcandeneaxedcostfortheoperatingsystematthevirtualmachinelevelandaxedcostfor
networkmaintenanceatthenetworklevel.
Billingcanbeenabledordisabledatanylevelwithinthehierarchy.vCenterChargebackManagerdoesnot
accountforanentityonwhichbillingisdisabledwhenareportisgeneratedonanyofitsparentlevels.Thecost
congurationonanentitycanvaryfordiferenttimeperiods.vCenterChargebackManagercanapplyaspecic
costcongurationthatisapplicableforacertaintimeinterval.

T E C H NI C AL WH I T E PAP E R / 1 9
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Report Generation
Automaticreportschedulerscanbeusedtogeneratereportsondemandforhierarchiesandentitiesthatmatch
thespeciedcriteria.ThisisespeciallyusefulfortheonboardingofneworganizationsintovCloudenvironments.
SeetheManagingAutomaticReportSchedulersectioninthevCenterChargebackManagerUsersGuidefor
additionaldetails.
Duringreportgeneration,deselectresourcesfromcomputationresources,reportsummary,anddetailsthatare
notusedforcostcalculation.Thisimprovesreportgenerationtimeandproducesacleanerreport.Usage
processingisignoredifthecostmodelcontainsnodenedbaserates.
Figure 11.PayAsYouGoResourceBased
Figure 12.AllocationPoolandReservationPool
Togenerateasinglereportagainstanorganizationthatusesmultiplecostmodels,useCtrl-Shifttomultiselect
theentitiestobeincludedinthereport.IntheCreate Reportwizard,selectUse diferent cost models for
entities andchoosetheappropriatecostmodelsinthedrop-downmenus.InFigure13,fvediferentvCloud
entitiesareselectedandmappedtotheappropriatecostmodelforreportgeneration.
T E C H NI C AL WH I T E PAP E R / 2 0
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Figure 13. MultipleCostModelsinaReport
Dashboardfunctionalityiscurrentlylimitedtoonecostmodelandmightnotyieldaccurateresultsfor
organizationswithmultiplevDCtypesandcostmodels.
Cost Calculation
ThisexampleconsistsofanorganizationvDC(CPU=10GHz,Memory=20GB,Storage=100GB)containinga
vAppwithtwovirtualmachines(vCPU=1,Memory=4GB,Storage=50GB).VM2ispoweredofat10:40a.m.
andasecondvCPUisadded.VM2issubsequentlypoweredonat11:30a.m.
Thereportintervalistwohours,from10:30a.m.to12:30p.m.
Figure 14.VMwarevCloudEntityStateTimeline
Costcalculationcomponentsincludereportintervallength,baserates,xedcostsandbillingpolicychosen.
T E C H NI C AL WH I T E PAP E R / 2 1
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Calculating Resource Costs
Base-ratecalculationincludes:timeinterval*ratecost*usedunits*ratefactor.
PerformingthiscalculationontheorganizationvDCforCPU(allocation),withabaserateof$0.1USDGHz/hour
andnoratefactor:2hours*$0.02USDGHz/hour*10GHz*1.0=$0.4USD.
Doingthesameformemory(allocation)withabaserateof$0.5USDGB/hourandnoratefactoryieldsthe
followingresult:2hours*$0.05USDGB/hour*20GB*1.0=$2USD.
Ifthebillingpolicyissettochargebasedonusageinsteadofallocation,theusedunitsistheusagevalueforthe
resourcethatisobtainedfromvCenterServer.
Atthevirtualmachinelevel,thebillingpolicydictateswhethercostsareappliedfortheentirereportdurationor
foronlythedurationwhenavirtualmachineispoweredon.
Calculating Fixed Costs
Fixed-costcalculationconsiders:timeinterval*xedcost/durationoftheresource.
Applyingaweeklyproratedfxedcostof$125USDtotheorganizationvDCandgeneratingthereportwillresult
inthefollowing:2hours*$125USD/168hoursinaweek=$1.49USD.
Calculating VM Instance Costs
Thesecondvirtualmachineispoweredofduringthemiddleofthereportinginterval.Thetimeintervalforthis
virtualmachineisapproximately70minutes.IfusingVMInstancetoapplycosts,thefxedcostsarenotprorated
andareappliedonlyforthedurationwhenavirtualmachineispoweredon.Thechangeinvirtualmachinesize
willtriggeraseparatelineiteminthereport,reectingthecongurationchangeandthenewxedcostapplied.
Thetwototalsareaddedtogetherforthenalcost.
User Management
vCenterChargebackManagerdoesnotextract,consumeorsyncwithvCloudDirectoruserlogins,rolesor
permissions.AfterinitialinstallationofvCenterChargebackManager,anadministratoruseriscreatedinit,and
allthevCloudDirectorobjectsbelongtothisuser.Onlytheadministrator/supervisorusercangrantpermissions.
Therearenoper-organizationusers,andnovCloudDirectoruserinformationispassedontovCenter
ChargebackManager.
Exampleusecase:GrantvCloudDirectororganizationadministratorstheabilitytoviewandruncostreportsfor
theirorganizations.
Creatingusers
CreatelocalusersinvCenterChargebackManagerthatmaptothosecreatedinvCloudDirector.
ImportLDAPusersintovCenterChargebackManagerthatmaptothosecreatedinvCloudDirector.
vCenterChargebackManagersupportsMicrosoftActiveDirectorybutdoesnotsupportOpenLDAP.
ImportLDAPgroupsintovCenterChargebackManagerthatmaptothosecreatedinvCloudDirector.
Assigningrolestousers
AssigningaroleonvCenterChargebackManager,otherthanthesupervisoruserrole,denesonlytheactions
thattheusercanperformintheapplication.Thisdoesnotimplicitlygiveaccesstotheresourcescreatedinthe
application.Toaccessaresource,theusereithermusthavecreateditorexplicitlybeassignedaroleforit.
T E C H NI C AL WH I T E PAP E R / 2 2
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Assigningrolestousers(e.g.,organizationadministrator)foraresource(e.g.,organization)
ThehierarchymanagerroleisassignedtovCenterServer,sotheusercanviewthevCenterServer.Tomakean
existinghierarchyvisibletotheuser,assignthehierarchymanagerroletothehierarchy.
AssigningthehierarchymanagerroleinvCenterChargebackManagerenablesausertocreatehierarchies.
Assigningarole(otherthanthesupervisoruserrole)denestheactionsthattheusercanperformonthe
applicationbutdoesnotprovideaccesstotheexistingresources.Toaccesstheexistingresources,applyroles
toeachresourceexplicitly.
Availability
WhathappensifaccessislosttocomponentsinthevCloudenvironment?
vCenterServerscenarios
IfavCloud-associatedvCenterServerisremovedfromvCloudDirector(throughtheUIandnotsomefailure)
butispresentinvCenterChargebackManager,thevCenterServerisnotusedbyvCloudDirectordata
collectoranymoreinvCenterChargebackManager.Ifthereareanyunprocessedeventsfromtheremoved
vCenterServer,theyarenotprocessed.
IfavCloud-associatedvCenterServerexperiencesafailureandbecomesinaccessible,correspondingvirtual
machinesarenotaddedinvCenterChargebackManageruntilthevCenterServerhasbeenrecovered.Keeptrack
ofthecongurablepropertyUnprocessed VMware vCloud Director chargeback event lifetime (in seconds).
IfvCenterServerisrecoveredaftertheabove-speciedvalue,someeventsareushedoutbeforethey
areprocessed.VirtualmachinesfromtheinaccessiblevCenterServermightnotbeaddedtovCenter
ChargebackManager.
IfthevCloud-associatedvCenterServersarenotadded,orifthosevCenterServersgodown,thiscan
causeissueswithPayAsYouGoallocationmodelreporting.Theabsenceofvirtualmachinedataresultsin
inaccuratereports.
vCloudDirectorscenarios
IfthevCloudDirectordatabasegoesdown,thevClouddatacollectorinstalledwithvCenterChargeback
Managertriestoreconnect.Theretryinterval/count(stopsretryingafteracertainnumberofattempts)
iscongurable.
IfanerroroccurswhilethevCloudDirectordatacollectorisreadingtheeventsfromthevCloudDirector
database,thecurrentjobcyclefailsimmediatelyandthevCloudDirectordatacollectortriestoreadtheevents
inthenextscheduledcycle.
vCenterChargebackManagerscenarios
IfthevCenterChargebackManagerservergoesdownwhilethevCloudDirectordatacollectorisprocessing
theevents,alltheeventsinthecurrentcyclearereprocessedinthenextcycle.
IfthevCenterChargebackManagerdatabasegoesdownwhilethevCloudDirectordatacollectorisprocessing
theevents,thewholecycleisrepeatedagain.
T E C H NI C AL WH I T E PAP E R / 2 3
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Integration with External Systems
IntegrationbetweenvCenterChargebackManagerandexternalsystemsrequirestheuseofthevCenter
ChargebackManagerAPI.DataisexportedinXMLformatthroughanAPIcallandthenformattedtomeetthe
inputrequirementsofthebillingsystem.Table4liststheprimarytaskfowswhenintegratingvCenter
ChargebackManagerwithabillingsystem.Taskfowsthatrequireintegrationefortarehighlightedingrey.
TASK NAME DESCRI PTI ON RESULT API s USED
InitialSetup CongurethevCenterChargebackManager
serverandthevCloudDirectorconnection
informationinsidetheinternalbillingsystem.
Allthecomponents
areabletotalkto
eachother.
None
CreateaNewUser
Account
Thecustomersubmitsarequestforanew
accountfromtheself-serviceportal.
Theself-serviceportalcreatesavCloud
organizationanduserinsidethe
organization.
Theself-serviceportalprovisionsthe
infrastructureasaservice(IaaS)inside
vCloudDirector.
Theself-serviceportalpassesarequestto
thebillingsystem,whichcreatesabilling
account.
Thebillingsystemupdatesamappingofthe
billingaccounttotheorganization.
Thecustomercan
logintothevCloud
accountandusethe
provisionedservice.
vCloud
administratorAPIs
BillingsystemAPIs
CreateaNew
Hierarchyin
vCenterChargeback
Manager
ThevCloudDirectordatacollectorperforms
thistaskautomatically.
ThevCloud
organizationandthe
servicesprovisioned
arereectedinside
vCenterChargeback
Manager.
N/A
ScheduleaCost
Report
Acostreportforthenewlycreatedhierarchy
isscheduledwithafrequencythatmatches
thecustomersbillingcycle.
Areportscheduleis
createdinside
vCenterChargeback
Manager.
Automated
vCenter
Chargeback
Managerreport
managementAPIs
ExportReportin
XML
ThebillingsystemsearchesthevCenter
ChargebackManagerreportarchiveand
exportstheappropriatereportsinXML
format.
Costreportsare
nowavailableinthe
billingsystem.
vCenter
Chargeback
Managersearch
API
vCenter
Chargeback
Managerreport
managementAPI
Generate
Invoice
Thebillingsystemgeneratestheinvoicefor
eachcustomeronthebillinganniversary.
Customersreceive
invoices.
N/A
PaymentProcessing Thebillingsystemhandlespaymentsagainst
invoices.
Paymentsare
processed.
N/A
Table 4.IntegrationTaskFlows
T E C H NI C AL WH I T E PAP E R / 2 4
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Summary
Meteringisacorecomponentofacloudserviceofering.Providerscangovernandshapeend-userbehavior
throughpricingschemesforinfrastructureresourcesconsumed.Collecteddatacanbeusedtopluginto
advancedanalyticsenginessuchasITBMforcostoptimizationandplanning.vCenterChargebackManager
providesthemeteringandcostcalculationcapabilitiesforvCloudenvironments.
Key Points
vCenterChargebackManagerserverscanbeclusteredtogetherforhigheravailability.
Multipledatacollectorscanbeinstalledforactive/passiveredundancy.
OnevCenterChargebackManagerinstancecanmanageonevCloudDirectordatabase.
Defnestandardunitsofconsumptionandallocationmodels.
Simplifyserviceoferingswherepossible.
Determinepricingthroughfnancialanalysis.
MappricingschemethroughvCenterChargebackManager/vCloudcostmodels.
Meteringenablesdiferentiationofserviceoferingsthroughcostmodels.
Authors
BenLin
CatherineFan
AmrainderSingh
References
I TEM URL
VMwarevCenterChargeback
Manager
http://www.vmware.com/products/vcenter-chargeback/
VMwarevCenterChargeback
Managerdocumentation
http://www.vmware.com/support/pubs/vcbm_pubs.html
VMwarevCenterChargeback
ManagerAPI
http://communities.vmware.com/community/developer/forums/chargeback
VMwarevCenterChargeback
ManagerJavaSDK
http://communities.vmware.com/community/vmtn/developer/forums/
cbmsdkjava
VMwarevCenterChargeback
ManagerconnectorforITBMsuite
https://www.vmware.com/support/vcbm/doc/cbm_itbm_connector.pdf
VMwarevCenterChargeback
Managercommunities
http://communities.vmware.com/community/vmtn/mgmt/chargeback
VMwarevCloudDirectorAPI http://vmware.com/go/vcloudapi
VMwarevCloudDirector http://www.vmware.com/products/vcloud-director/
Table 5.VMwarevCenterChargebackManagerReferences
T E C H NI C AL WH I T E PAP E R / 2 5
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Appendix A: Conguration Maximums
CONSTRAI NT LI MI T
VMwarevCenterServersinavCenterChargebackManagersystem 10
VMwarevCenterServersperdatacollector 5
Virtualmachinesperdatacollector 15,000
Virtualmachines/entitiesinavCenterChargebackManagersystem 35,000
Virtualmachines/entitiesperhierarchy 1,000
HierarchiesinavCenterChargebackManagersystem 5,000
Concurrentreports(approximately3,000pages)
pervCenterChargebackManagersystem
5
Concurrentreports(approximately10pages)
pervCenterChargebackManagersystem
150
Table 6. VMwarevCenterChargebackManagerCongurationMaximums
T E C H NI C AL WH I T E PAP E R / 2 6
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Appendix B: Port Requirements
DESCRI PTI ON PORT(S) PROTOCOL
VMwarevCenterChargebackManagerWebinterfaceto
VMwarevCenterChargebackManagerserver
8,080 TCP
VMwarevCenterChargebackManagerWebinterfaceto
VMwarevCenterChargebackManagerserver
443 TCP
VMwarevCenterChargebackManagerserver(loadbalancer)to
VMwarevCenterChargebackManagerserver
8,009 TCP
VMwarevCenterChargebackManagerserverto
VMwarevCenterChargebackManagerdatabase(JDBC)
Varies* TCP
Datacollector(all)to
VMwarevCenterChargebackManagerdatabase(JDBC)
Varies* UDP
VMwarevCenterChargebackManagerdatacollectorto
VMwarevCenterServerdatabase(JDBC)
Varies* TCP
VMwarevCloudDirectordatacollectorto
VMwarevCloudDirectordatabase(JDBC)
1,521 TCP
VMwarevCenterChargebackManagerdatacollectorto
VMwarevCenterServer
443 TCP
VMwarevShielddatacollectortoVMwarevShieldManager 443 TCP
VMwarevCenterChargebackManagerservertoLDAPserver 389 TCP,UDP
VMwarevCenterChargebackManagerservertoSMTPserver 25 TCP
*Depends on databaseOracle: 1,521 ports; SQL server: 1,433 ports.
Table 7. VMwarevCenterChargebackManagerPortRequirements
VMware, Inc.3401HillviewAvenuePaloAltoCA94304USATel877-486-9273Fax650-427-5001www.vmware.com
Copyright2012VMware,Inc.Allrightsreserved.ThisproductisprotectedbyU.S.andinternationalcopyrightandintellectualpropertylaws.VMwareproductsarecoveredbyoneormorepatentslisted
athttp://www.vmware.com/go/patents.VMwareisaregisteredtrademarkortrademarkofVMware,Inc.intheUnitedStatesand/orotherjurisdictions.Allothermarksandnamesmentionedhereinmaybe
trademarksoftheirrespectivecompanies.ItemNo:VMW-WP-vCNTR-CHRGBK-MNGT-vCLD-USLET-101-WEB