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

Daniel P. Berrange berrange at redhat.com
Wed Jul 28 18:10:31 UTC 2010

On Wed, Jul 28, 2010 at 03:22:50PM +0200, Matthias Bolte wrote:
> 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

This all sounds like a good plan to me

|: Red Hat, Engineering, London    -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org        -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

More information about the libvir-list mailing list