Comment 2 for bug 1828444

I agree it shouldn't be done ad-hoc. To do it properly, we should go in the direction of a more REST-y API, where we don't expand all the properties of an object, but rather have refs to related objects.
In this case, for instance, instead of including the VLAN/fabric info in the machine result, we'd have a ref pointing at a VLAN/fabric ID.
At that point it'd be easier to have generic filters that could take a value for any direct attribute of a machine, including VLAN/fabric ID (or pool, zone, domain, ...).
The same would apply to simple attribugtes like the hostname