Page Comparison

...

Table accounting_event_vm

Field name	Field type	Description
idVMAccountingEvent	BIGINT	ID event unique
idVM	INTEGER	ID of virtual machine owning the resource
idEnterprise	INTEGER	ID of enterprise resource owner
idVirtualDataCenter	INTEGER	ID of virtual datacenter facility owner
idVirtualApp	INTEGER	ID virtual app resource owner
cpu	INTEGER	'cores' units
ram	INTEGER	Memory, in megabytes (MB)
hd	BIGINT	Local storage, in bytes (B)
startTime	TIMESTAMP	When a resource was created
stopTime	TIMESTAMP	When a resources was destroyed
consolidated	TINYINT	Flag for processed or not
costCode	TINYINT	Cost code assigned for pricing purposes
hypervisorType	VARCHAR	The type of hypervisor hosting the virtual machine
idDataCenter	INTEGER	ID of datacenter
VirtualMachine-haHosted	INTEGER	Deprecated - Flag for hosted on HA-enabled PM or not (haEnabled)
antiAffinity	INTEGER	For VMs in an anti-affinity layer
idHardwareProfile	INTEGER	ID of hardware profile

...

This table stores details of reserved physical servers - one row for each reserved server.

...

Field name	Field type	Description
idPMAccountingEvent	BIGINT	Unique column identifier for the accounting event
idPhysicalMachine	INT	ID of the physical machine, as defined in the kinton.physicalmachine table. NOTE: Use the kinton_accounting ABQ_PM_ID_TO_NAME(id) function to obtain the machine name associated with the ID
idEnterprise	INT	ID of the ENTERPRISE, as defined in the kinton.enterprise table. NOTE: Use the kinton_accounting ABQ_ENT_ID_TO_NAME(id) function to obtain the machine name associated with the ID
cpu	INT	The number of physical CPUs in the machine
ram	INT	The physical machine’s RAM (in MB)
startTime	TIMESTAMP	The time at which the machine reservation started
stopTime	TIMESTAMP	The time at which the reservation finished.   This value is NULL if the reservation is still active
idDataCenter	INT	ID of the physical datacenter, as defined in the kinton.datacenter table. NOTE: Use the kinton_accounting ABQ_DC_ID_TO_NAME(id) function to obtain the datacenter name associated with the ID
consolidated	TINYINT	Indicates whether this row has been consoliated with other rows.   Currently this value is always 0
version_c	INT	Software controlled data version

 

Table accounting_event_repository

This table contains details of the repository usage. There is one row for each VM Template and Instance stored in the repository. Persistent VM templates are not included in this table, because they are stored as external volumes and charged separately.

 

Field name	Field type	Description
idRepoAccountingEvent	BIGINT	Unique column identifier for the accounting event
idImage	INT	ID of the repository image, as defined in the kinton.virtualimage table. NOTE: Use the kinton_accounting ABQ_IMG_ID_TO_NAME(id) function to obtain the image name associated with the ID
idEnterprise	INT	ID of the ENTERPRISE, as defined in the kinton.enterprise table. NOTE: Use the kinton_accounting ABQ_ENT_ID_TO_NAME(id) function to obtain the machine name associated with the ID
idImageTypeName	INT	The ID of the image type name in the generic accounting name table, use the kinton_accounting ABQ_OBJECT_ID_TO_NAME (id)  function to retrieve the actual type name.   Names are one of: INSTANCE, TEMPLATE, INSTANCE-CONVERSION, TEMPLATE-CONVERSION
idImageFormatName	INT	The ID of the image format name in the generic accounting name table, use the kinton_accounting ABQ_OBJECT_ID_TO_NAME (id)  function to retrieve the actual format name.   Names are: VMDK_FLAT, RAW, etc. see the wiki API reference for further details
imageSize	BIGINT	Physical size of the repository image, in bytes
idRepository	INT	The ID of the image repository as defined in the kinton.repository table
idRepositoryName	INT	Deprecated - The ID of the repository name in the generic accounting name table, use the kinton_accounting ABQ_OBJECT_ID_TO_NAME (id)  function to retrieve the actual repository name. THIS FIELD WAS DEPRECATED IN ABIQUO 3.4
startTime	TIMESTAMP	The time at which the image was created in the repository
stopTime	TIMESTAMP	The time at which the image was deleted from the repository.  This value is NULL if the image still exists.
idDataCenter	INT	ID of the physical datacenter, as defined in the kinton.datacenter table. NOTE: Use the kinton_accounting ABQ_DC_ID_TO_NAME(id) function to obtain the datacenter name associated with the ID.
consolidated	TINYINT	Indicates whether this row has been consoliated with other rows.   Currently this value is always 0.
version_c	INT	Software controlled data version.

List of accounting event tables

The accounting event tables include the following.

• backup
• ds_storage
• firewall
• ips
• loadbalancer
• pm
• protect
• repository
• storage
• vlan
• vm
• vm_off
• vm_on

...

Every hour, the status of each resource implemented in the system is recorded, which can generate a large number of rows. Abiquo recommends that the table is periodically purged of resource information which is no longer required.

...

• Cores
• RAM
• Local storage

• Cost codes (if the VM template has a cost code)

  NoteGrouped  Grouped virtual machine components and virtual machines are accounted per group, not per individual virtual machine.
  

  
  

2. Virtual appliance

• Groups of virtual machines
  
  • Cores
  • RAM
  • Local storage

  • Cost codes (if the VM template has a cost code)

    NoteGrouped  Grouped virtual appliances are accounted per group, not per individual virtual appliance.
    

    
    

3. Virtual datacenter

• Groups of virtual machines
• Groups of virtual appliances
  
  • Cores
  • RAM
  • Local storage
  • VLANS
  • Public IPs

  • External storage

    NoteVirtual  Virtual Datacenter accounting is the total of the resources reserved and/or consumed by the Virtual Machines, Virtual Appliances, and users of a Virtual Datacenter.
    

    
    

4. Enterprise
An Enterprise has no managed resources that do not belong to a Virtual Datacenter, so there is no accounting per Enterprise. However, the Enterprise associated with each resource is recorded for aggregating resources at Enterprise level, and this information can be retrieved through the database views. 

Legacy accounting views

For accounting and billing, Abiquo has previously implemented database views (in both the kinton and kinton_accounting schemas) to help you access the resource usage information correctly. However, the use of these views is no longer recommended for scalability and performance reasons. Instead, use the equivalent queries described above.

...

• ACCOUNTING_CONFIG_VW  - Returns the current accounting configuration as a single row

...