Re: [libvirt] [PATCH] esx: Add vpx:// scheme to allow direct connection to a vCenter

I think you're right, a vpx:// connection that covers a whole vCenter is probably out of libvirt's scope and gives much trouble with stuff like name uniqueness etc. I'm going to restrict a vpx:// connection to a single host for now: vpx://example-vcenter.com/datacenter1/cluster1/hostsystem1 This solves all name uniqueness issues and it allows to resolve remaining no-host-for-vpx-connection-todos in the driver. This way we don't have a feature in 0.8.3 that might need to be restricted in later version. Once we have a single-host-vpx-connection I'd like to investigate if it's feasible to relax the restrictions on a vpx:// in a way that allows to manage a single cluster too. Internally the driver would always manage (Cluster-)ComputeResources then. The URI for such a connection would omit the host part: vpx://example-vcenter.com/datacenter1/cluster1