When deploying a new host on a Vmware CR, the selection of the datastore/datastore cluster and the network should filter out the irrelevant objects for the chosen cluster.

When you have more then one cluster on your vmware datacenter and many different dvPortGroup and datastores, the actual form is really confusing. It can happen that one can try to deploy a new vm on a datastore or on a network that isn't available for that specify cluster.

I can see that list_datastore[1] and list_network[2] methods in the fog-vsphere library support a filtering option...so it should not be too difficult to implement what i'm asking.

[1] http://www.rubydoc.info/github/fog/fog/Fog/Compute/Vsphere/Real#list_datastores-instance_method
[2] http://www.rubydoc.info/github/fog/fog/Fog/Compute/Vsphere/Real#list_networks-instance_method