Open Stack

As a reminder: there are no individual networking options that can be used
with both vCenter and KVM/QEMU hypervisors once we deprecate nova-network.



The code for vCenter as a stand-alone deployment may be there, but the code
for the component registry (
https://blueprints.launchpad.net/fuel/+spec/component-registry) is still
not complete.  The component registry is required for a multi-HV
environment, because it provides compatibility information for Networking
and HVs.  In theory, landing this feature will enable us to configure DVS +
vCenter and Neutron with GRE/VxLAN + KVM/QEMU in the same environment.



While Andriy Popyvich has made considerable progress on this story, I
personally feel very strongly against deprecating nova-network until we
have confirmed that we can support *all current use cases* with the
available code base.



Are we willing to lose the multi-HV functionality if something prevents the
component registry work from landing in its entirety before the next
release?



*From:* Sergii Golovatiuk [mailto:sgolovatiuk at mirantis.com]
*Sent:* Friday, October 23, 2015 6:30 AM
*To:* OpenStack Development Mailing List (not for usage questions) <
openstack-dev at lists.openstack.org>
*Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a deployment
option in Fuel?



Hi,



As far as I know neutron code for VCenter is ready. Guys are still testing
it. Keep patience... There will be announce soon.


--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151023/19c4337c/attachment.html>