Ownership Information Storage

In many large businesses with hardware fleets, there may be a variety of
ownership of the underlying hardware for tracking purposes. A good example
of this is in a hybrid service provider scenario where an operator may
directly own a portion of the hardware, may have the hardware on lease,
and may ultimately have customer owned hardware.

We simply cannot model this with existing node fields, since there may
be resource sharing agreements also in place between the owners of the
hardware. And as such, we need some way to store and represent the end
owner of the hardware for tracking and logistical purposes.

While scenarios differ, ultimately there is a need to be able to store
information in a top level fashion about who owns a given piece of hardware.

Information of this sort can be vital when it comes time for tax asset
inventories, or just simple tracking of where the hardware came from.

Providing the ability to search and return the hardware that is known
to be owned by a particular group allows for faster correlation of the
disposition of the hardware for auditing and accounting purposes.

An operator could potentially store this information in extra, however then
they would still need to dump all of the nodes out to obtain a list of nodes
with the specific information that is needed. The operator would begin to
hit limits with the number of responses from the API, and would need to
likely create their own tooling around list processing.