VMware - vCloud Infrastructure extractor

This topic describes how to integrate BMC Helix Continuous Optimization with VMWare vCloud Director to extract vCloud infrastructure data. The ETL imports infrastructure data from VMware vCloud Director.  

In the vCloud Infrastructure ETL, the following entities are fetched by Provider vDCs and Organization vDCs: 

  • For each Provider vDC, related Organization vDCs, Hosts, Resource pools, Datastores and Datastore Clusters are fetched.
  • For each Organization vDC, related Resource pools are fetched.

The VMWare infrastructure hierarchy is refreshed every 6 hours. Removing or adding a new datastore into a datastore cluster can take upto 6 hours to reflect in BMC Helix Continuous Optimization, and during this period, no data is lost. Any change in configuration values (for example, total space of the datastore cluster) will reflect in BMC Helix Continuous Optimization in 1 hour.

Note

To collect data from 9.x and 10.x versions of VMware Cloud Director, use the VMware-Cloud-Director-9-x-10-x-Extractor. This ETL collects vCloud infrastructure and services data from the vCloud Director.

For more information, refer to the following sections:

Integration steps

To integrate BMC Helix Continuous Optimization with the vCloud infrastructure extractor:

  1. Navigate to Administration > ETL & SYSTEM TASKS > ETL tasks.
  2. In the ETL tasks page, click Add > Add ETL under the Last run tab.

  3. In the Add ETL page, set values for the following properties under each expandable tab.

    Note

    Basic properties are displayed by default in the Add ETL page. These are the most common properties that you can set for an ETL, and it is acceptable to leave the default selections for each as is.

    Basic properties

    Note

    To view or configure Advanced properties, click Advanced. You do not need to set or modify these properties unless you want to change the way the ETL works. These properties are for advanced users and scenarios only.

    Advanced properties

  4. Click Save.
    You return to the Last run tab under the ETL tasks page.
  5. Validate the results in simulation mode: In the ETL tasks table under ETL tasks > Last run, locate your ETL (ETL task name), click run_etl.png to run the ETL.
    After you run the ETL, the Last exit column in the ETL tasks table will display one of the following values:
    • OK: The ETL executed without any error in simulation mode.
    • WARNING: The ETL execution returned some warnings in simulation mode. Check the ETL log.
    • ERROR: The ETL execution returned errors and was unsuccessful. Edit the active Run configuration and try again.
  6. Switch the ETL to production mode: To do this, perform the following task:
    1. In the ETL tasks table under ETL tasks > Last run, click the ETL under the Name column.
    2. In the Run configurations table in the ETL details page, click edit_button.gif to edit the active run configuration.
    3. In the Edit run configuration page, navigate to the Run configuration expandable tab and set Execute in simulation mode to No.
    4. Click Save.
  7. Locate the ETL in the ETL tasks table and click run_etl.png to Run it, or schedule an ETL run.
    After you run the ETL, or schedule the ETL for a run, it will extract the data form the source and transfer it to the BMC Helix Continuous Optimization database.

vCloud infrastructure data metrics

The following BMC Helix Continuous Optimization metrics are populated by the VMware - vCloud Director - Cloud infrastructure extractor ETL.

Viewing assistance

To toggle full-screen mode (recommended) for this topic, type f. To hide the navigation tree on the left, type [.

Legend:
C: Configuration metric
T: Time Series metric

Entity

BMC Helix Continuous Optimization metric

Type*

Dataset

Description

vCloud Metric

vCloud











VCLOUD_NAME

C

SYSVMW

Name of the vCloud system

-

CPU_ALLOCATION

T

SYSVIRGLB

Number of Units that have been allocated to all orgvDCs in the vCloud.

-

CPU_TOTAL_MHZ

C

SYSCNF

Total CPU available for vCloud.

-

CPU_UTILMHZ

T

SYSGLB

Sum of CPU used by all child Provider vDCs

-

CPU_UTIL

T

SYSGLB

Percentage (%) utilization, ratio of CPU_UTILMHZ / CPU_TOTAL_MHZ.

-

MEM_ALLOCATION

T

SYSVIRGLB

Number of units that have been allocated to consumers that is all orgvDCs in the vCloud.

-

TOTAL_REAL_MEM

C

SYSCNF

Total memory available for PvDC

-

MEM_USED

T

SYSGLB

Sum of memory used by all child Org vDCs.

-

MEM_UTIL

T

SYSGLB

Percentage (%) utilization, ratio of MEM_USED/TOTAL_REAL_MEM.

-

DSTORE_ALLOCATION

T

SYSVIRGLB

Number of Units that have been allocated to consumers that is all orgvDCs in the vCloud.

-

TOTAL_DSTORE_SIZE

C

SYSVIRDS

Total storage available for vCloud.

-

TOTAL_DSTORE_USED

T

SYSVIRDS

Storage used

-

TOTAL_DSTORE_UTIL

T

SYSVIRDS

Percentage (%) utilization, ratio of TOTAL_DSTORE_USED / TOTAL_DSTORE_SIZE.

-

Provider vDC













VCLOUD_NAME

C

SYSVMW

Name of the vCloud system.

-

PROVIDERVDC_NAME

C

SYSVMW

Name of the Provider vDC.

QueryResultVMWProviderVdcRecordType.name

CPU_ALLOCATION

T

SYSVIRGLB

Number of Units that have been allocated to all orgVDCs under Provider vDC.

QueryResultVMWProviderVdcRecordType.cpuAllocationMhz

CPU_TOTAL_MHZ

C

SYSCNF

Total CPU available for PvDC.

QueryResultVMWProviderVdcRecordType.cpuLimitMhz

CPU_UTILMHZ

T

SYSGLB

Sum of CPU reserved by all child Org vDCs.

QueryResultVMWProviderVdcRecordType.cpuUsedMhz

CPU_UTIL

T

SYSGLB

Percentage (%) utilization, ratio of CPU_UTILMHZ / CPU_TOTAL_MHZ.

QueryResultVMWProviderVdcRecordType.cpuUsedMhz /
QueryResultVMWProviderVdcRecordType.cpuLimitMhz) * 100

MEM_ALLOCATION

T

SYSVIRGLB

Number of Units that have been allocated to all orgVDCs under Provider vDC.

QueryResultVMWProviderVdcRecordType.memoryAllocationMB

TOTAL_REAL_MEM

C

SYSCNF

Total memory available for PvDC.

QueryResultVMWProviderVdcRecordType.memoryLimitMB

MEM_USED

T

SYSGLB

Sum of memory reserved by all child Org vDCs.

QueryResultVMWProviderVdcRecordType.memoryUsedMB

MEM_UTIL

T

SYSGLB

Percentage (%) utilization, ratio of MEM_USED/TOTAL_REAL_MEM.

(QueryResultVMWProviderVdcRecordType.memoryUsedMB/
QueryResultVMWProviderVdcRecordType.memoryLimitMB) * 100

DSTORE_ALLOCATION

T

SYSVIRGLB

Number of units that have been allocated to consumers that is all orgvDCs under Provider vDC.

QueryResultVMWProviderVdcRecordType.storageAllocationMB

TOTAL_DSTORE_SIZE

C

SYSVIRDS

Total storage available for PvDC.

QueryResultVMWProviderVdcRecordType.storageLimitMB

TOTAL_DSTORE_USED

T

SYSVIRDS

Storage Used

QueryResultVMWProviderVdcRecordType.storageUsedMB

TOTAL_DSTORE_UTIL

T

SYSVIRDS

Percentage (%) utilization, ratio of TOTAL_DSTORE_USED / TOTAL_DSTORE_SIZE.

(QueryResultVMWProviderVdcRecordType.storageUsedMB/
QueryResultVMWProviderVdcRecordType.storageLimitMB) * 100

HA_STATUS

C

SYSVMW

Read-only indicator. True if compute capacity is highly available.

VMWProviderVdcType.RootComputeCapacityType.IsHA

VDC_STATUS

C

SYSVMW

Status of vCloud Virtual Datacenter

QueryResultVMWProviderVdcRecordType.isEnabled

Org vDC
















VCLOUD_NAME

C

SYSVMW

Name of the vCloud system

-

PROVIDERVDC_NAME

C

SYSVMW

Name of the Provider vDC

QueryResultVMWProviderVdcRecordType.name

ORGVDC_NAME

C

SYSVMW

Organization vDC Name

QueryResultAdminVdcRecordType .name

CPU_LIMIT_MHZ

C

SYSVIRGLB

Maximum amount of CPU available to the virtual machines running within this organization vDC (taken from the supporting provider vDC).

  • Applicable in case of Allocation Pool.
  • For Pay-As-You-Go this value is always unlimited.

QueryResultAdminVdcRecordType.cpuLimitMhz

CPU_RESERVED_MHZ

C

SYSVIRGLB

Guaranteed Number of Units that have been allocated to org vDC. This is allocation multiplied by the Resource Guaranteed CPU.

QueryResultAdminVdcRecordType.cpuAllocationMhz *
AdminVdcType.ResourceGuaranteedCpu

CPU_UTILMHZ

T

SYSGLB

CPU Used

QueryResultAdminVdcRecordType.cpuUsedMhz

CPU_UTIL

T

SYSGLB

Percentage (%) utilization, ratio of CPU_UTILMHZ / CPU_LIMIT_MHZ

(QueryResultAdminVdcRecordType.cpuUsedMhz/
QueryResultAdminVdcRecordType.cpuLimitMhz) * 100

MEM_LIMIT

C

SYSVIRGLB

Maximum amount of memory available to the virtual machines running within this organization vDC (taken from the supporting provider vDC).

  • Applicable in case of Allocation Pool.
  • For Pay-As-You-Go this value is always unlimited.

QueryResultAdminVdcRecordType.memoryLimitMB

MEM_RESERVED

C

SYSVIRGLB

Guaranteed Number of Units that have been allocated to org vDC. This is allocation multiplied by the Resource Guaranteed memory.

QueryResultAdminVdcRecordType.memoryAllocationMB * AdminVdcType.ResourceGuaranteedMemory

MEM_USED

T

SYSGLB

Memory Used

QueryResultAdminVdcRecordType.memoryUsedMB

MEM_UTIL

T

SYSGLB

Percentage (%) utilization, ratio of MEM_USED/MEM_LIMIT.

(QueryResultAdminVdcRecordType.memoryUsedMB / QueryResultAdminVdcRecordType.memoryLimitMB) * 100

DSTORE_LIMIT

C

SYSVIRDS

The maximum amount of Storage available to the virtual machines running within this organization vDC (taken from the supporting provider vDC).

QueryResultAdminVdcRecordType.storageLimitMB

TOTAL_DSTORE_SIZE

C

SYSVIRDS

Maximum amount of storage available to the virtual machines running within this organization vDC (taken from the supporting provider vDC).

QueryResultAdminVdcRecordType.storageLimitMB

TOTAL_DSTORE_USED

T

SYSVIRDS

Amount of storage used by vAPPs, VMs, templates, media files under this Org vDC.

QueryResultAdminVdcRecordType.storageUsedMB

TOTAL_DSTORE_UTIL

T

SYSVIRDS

Percentage (%) utilization, ratio of TOTAL_DSTORE_USED / TOTAL_DSTORE_SIZE

(QueryResultAdminVdcRecordType.storageUsedMB / QueryResultAdminVdcRecordType.storageLimitMB) * 100

ALLOCATION_MODEL

C

SYSVMW

Allocation model used by this vDC. One of:

  • AllocationVApp : Pay as you go. Resources are committed to a vDC only when vAPPs are created in it.
  • AllocationPool: Only a percentage of the resources you allocate are committed to the organization vDC.

AdminVdcType.AllocationModel

CPU_COMPUTED_LIMIT_OPT

C

SYSVIRGLB

Maximum optimistic amount of CPU the virtual machines running within this organization vDC can avail.

  • Applicable only for Pay-As-You-Go model.
  • Calculated by summing up the CPU used by Org vDC and the capacity free at PvDC level.

-

MEM_COMPUTED_LIMIT_OPT

C

SYSVIRGLB

Maximum optimistic amount of memory the virtual machines running within this organization vDC can avail.

  • Applicable only for Pay-As-You-Go model.
  • Calculated by summing up the memory used by Org vDC and the capacity free at PvDC level.

-

DSTORE_COMPUTED_LIMIT_OPT

C

SYSVIRDS

Maximum optimistic amount of storage the virtual machines running within this organization vDC can avail.

  • Applicable only for Pay-As-You-Go model.
  • Calculated by summing up the storage used by Org vDC and the capacity free at PvDC level.

-

VDC_STATUS

C

SYSVMW

Status of vCloud Virtual Datacenter

QueryResultAdminVdcRecordType.isEnabled

vCloud Aggregation Hierarchy Rule metrics

The following BMC Helix Continuous Optimization metrics are populated by the vCloud Aggregation Hierarchy Rule 

Note

 For vCloud Capacity Visibility, the aggregation hierarchy rule executes automatically from the hierarchy manager task.

Lookup details

 The vCD defines multiple lookup fields for coordinating with other connectors. The following table lists the sequence of field sets for strong lookup and weak lookup.

Related topics

Using-ETL-datasets

Developing-custom-ETLs

Dataset-reference-for-ETL-tasks

Viewing-datasets-and-metrics-by-dataset-and-ETL-module