[Openstack] [openstack][nova][vmware] why deprecate mapping one nova-compute to multi vcenter cluster?

Guoyong guoyongxhzhf at h3c.com
Thu Aug 11 01:55:17 UTC 2016

The fact is that we can’t map one nova-compute to multi vcenter cluseter since mitaka.

The function is deprecated from liberty  and  the code is removed in mitaka.

From: Vaidyanath Manogaran [mailto:vaidyanath.m at gmail.com]
Sent: Wednesday, August 10, 2016 7:01 PM
To: guoyong 03239 (CCPL)
Cc: openstack at lists.openstack.org
Subject: Re: [Openstack] [openstack][nova][vmware] why deprecate mapping one nova-compute to multi vcenter cluster?

I believe the usecase is to manage multiple vcenter cluster with one nova-compute instance.
And if we restricting this would not make any sense.


On Wed, Aug 10, 2016 at 3:27 PM, Guoyong <guoyongxhzhf at h3c.com<mailto:guoyongxhzhf at h3c.com>> wrote:
Anybody knows reason?
This e-mail and its attachments contain confidential information from H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160811/682cfed8/attachment.html>

More information about the Openstack mailing list