We do support Neutron for vCenter, but – as I mentioned a few months ago – we do not yet have a fully vetted way to deploy the multi-hypervisor use case with both KVM/QEMU and vCenter. This depends on our ability to select multiple networking options and align them to the correct hypervisors.
Per a conversation with Andrian Noga and his team yesterday, they are finishing work on the component registry [1] which will enable the multi-hypervisor, multi-network use case. This work is being completed now. My recommendation remains that we should avoid deprecating nova-network until we have at least tested the basic multi-hypervisor use case with the new functionality. Can we remove nova-network after FF as a High priority bug? [1] https://review.openstack.org/#/c/229306/ *From:* Mike Scherbakov [mailto:mscherba...@mirantis.com] *Sent:* Tuesday, December 01, 2015 1:37 AM *To:* OpenStack Development Mailing List (not for usage questions) < openstack-dev@lists.openstack.org> *Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel? Aleksey, can you clarify it? Why it can't be deployed? According to what I see at our fakeUI install [1], wizard allows to choose nova-network only in case if you choose vcenter. Do we support Neutron for vCenter already? If so - we could safely remove nova-network altogether. [1] http://demo.fuel-infra.org:8000/ On Mon, Nov 30, 2015 at 4:27 AM Aleksey Kasatkin <akasat...@mirantis.com> wrote: This remains unclear. Now, for 8.0, the Environment with Nova-Network can be created but cannot be deployed (and its creation is tested in UI integration tests). AFAIC, we should either remove the ability of creation of environments with Nova-Network in 8.0 or return it back into working state. Aleksey Kasatkin On Fri, Oct 23, 2015 at 3:42 PM, Sheena Gregson <sgreg...@mirantis.com> wrote: 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:sgolovat...@mirantis.com] *Sent:* Friday, October 23, 2015 6:30 AM *To:* OpenStack Development Mailing List (not for usage questions) < openstack-dev@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 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Mike Scherbakov #mihgen
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
