Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vCenter Server Inventory Hierarchy #1

Closed
rlankfo opened this issue Feb 23, 2022 · 0 comments · Fixed by #10
Closed

vCenter Server Inventory Hierarchy #1

rlankfo opened this issue Feb 23, 2022 · 0 comments · Fixed by #10
Milestone

Comments

@rlankfo
Copy link
Member

rlankfo commented Feb 23, 2022

The inventory of a vSphere cluster is organized via a resource hierarchy. Access to objects and their properties/methods are based on their location in the inventory. When starting a session, vSphere creates a ServiceInstance with one root folder, one Datacenter and four folders that hold different types of inventory objects. Starting with the ServiceInstance associated with a session (the root object of the inventory), the entire inventory hierarchy can be traversed.

During initialization of the exporter, this inventory tree should be populated in memory and then kept in sync with the server on an interval. The resources discovered during inventory traversal will be used to collect metrics from the performance managers.

The following objects should be discovered while traversing the inventory:

  • ClusterComputeResource
  • Datacenter
  • Datastore
  • HostSystem
  • ResourcePool
  • VirtualMachine

Note: Parent/children references should be stored so the resource hierarchy can be reflected in labels.

@rlankfo rlankfo added this to the alpha milestone Feb 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant