Update check_vmware_hs2ds2vms plugin to support excluding VMware Mobility Platform host & associated datastore

[atc0005]

Overview

Whenever our VMware admins perform work to update the associated VMware Hybrid Cloud Extensions (HCX) resources service checks using the check_vmware_hs2ds2vms plugin are triggered.

This is because the service account we're using to run the plugin sees the associated datastore (ma-ds-* where * is a 36 character alphanumeric string with dashes) for the mobility agents (shown as VMware Mobility Platform model hosts) and object to the lack of a Location attribute.

I don't know if they're able to assign a Location attribute, but the workaround thus far has been for our VMware admins to remove access to the mobility agent host entries and the associated datastore.

Ideally (from the perspective of this plugin), we could provide a flag to ignore specific model hosts (or find a better attribute to key off of) along with datastores which consider the host its parent. Then whenever VMware Hybrid Cloud Extensions (HCX) resources are updated in the future those host/datastore objects will be ignored and the service check(s) will continue to function as before, evaluating based solely on Location attribute values.

References

• Add "origin" or "parent" annotation for Resources resource pool when multiple pools of the same name are present #1148
• https://www.softwaredefinedblog.com/first-look-at-hcx-network-extension-ha-feature/
• https://www.softwaredefinedblog.com/hcx/hcx-mobility-agent-aka-dummy-host/

[atc0005]

Snippet of what the vSphere web UI shows for the mobility agent host entry:

[atc0005]

Looking at the Managed Object Browser UI:

• Data Object Type: HostHardwareSummary
• Parent Managed Object ID: host-XYZ (host MoRef)
• Property Path: summary.hardware

Properties:

• cpuModel
  • "VMware Virtual Processor"
• model
  • `VMware Mobility Platform"
• vendor
  • "VMware"

Any of those values may be enough to use for exclusion purposes.