+1 On Mon, Mar 10, 2014 at 10:51 AM, Miguel Angel Ajo <majop...@redhat.com> wrote: > +1 (Voting here to workaround my previous top-posting). > > > On 03/09/2014 01:22 PM, Nir Yechiel wrote: >> >> +1 >> >> I see it as one of the main current gaps and I believe that this is >> something that can promote Neutron as stable and production ready. >> Based on Édouard's comment below, having this enabled in Icehouse as >> experimental makes a lot of sense to me. >> >> ----- Original Message ----- >>> >>> +1 >>> >>> ----- Original Message ----- >>>> >>>> +1 >>>> >>>> On Fri, Mar 7, 2014 at 2:42 AM, Édouard Thuleau <thul...@gmail.com> >>>> wrote: >>>>> >>>>> +1 >>>>> I though it must merge as experimental for IceHouse, to let the >>>>> community >>>>> tries it and stabilizes it during the Juno release. And for the Juno >>>>> release, we will be able to announce it as stable. >>>>> >>>>> Furthermore, the next work, will be to distribute the l3 stuff at the >>>>> edge >>>>> (compute) (called DVR) but this VRRP work will still needed for that >>>>> [1]. >>>>> So if we merge L3 HA VRRP as experimental in I to be stable in J, will >>>>> could >>>>> also propose an experimental DVR solution for J and a stable for K. >>>>> >>>>> [1] >>>>> >>>>> https://docs.google.com/drawings/d/1GGwbLa72n8c2T3SBApKK7uJ6WLTSRa7erTI_3QNj5Bg/edit >>>>> >>>>> Regards, >>>>> Édouard. >>>>> >>>>> >>>>> On Thu, Mar 6, 2014 at 4:27 PM, Sylvain Afchain >>>>> <sylvain.afch...@enovance.com> wrote: >>>>>> >>>>>> >>>>>> Hi all, >>>>>> >>>>>> I would like to request a FFE for the following patches of the L3 HA >>>>>> VRRP >>>>>> BP : >>>>>> >>>>>> https://blueprints.launchpad.net/neutron/+spec/l3-high-availability >>>>>> >>>>>> https://review.openstack.org/#/c/64553/ >>>>>> https://review.openstack.org/#/c/66347/ >>>>>> https://review.openstack.org/#/c/68142/ >>>>>> https://review.openstack.org/#/c/70700/ >>>>>> >>>>>> These should be low risk since HA is not enabled by default. >>>>>> The server side code has been developed as an extension which >>>>>> minimizes >>>>>> risk. >>>>>> The agent side code introduces a bit more changes but only to filter >>>>>> whether to apply the >>>>>> new HA behavior. >>>>>> >>>>>> I think it's a good idea to have this feature in Icehouse, perhaps >>>>>> even >>>>>> marked as experimental, >>>>>> especially considering the demand for HA in real world deployments. >>>>>> >>>>>> Here is a doc to test it : >>>>>> >>>>>> >>>>>> >>>>>> https://docs.google.com/document/d/1P2OnlKAGMeSZTbGENNAKOse6B2TRXJ8keUMVvtUCUSM/edit#heading=h.xjip6aepu7ug >>>>>> >>>>>> -Sylvain >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> OpenStack-dev mailing list >>>>>> OpenStack-dev@lists.openstack.org >>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> OpenStack-dev mailing list >>>>> OpenStack-dev@lists.openstack.org >>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>>> >>>> >>>> _______________________________________________ >>>> OpenStack-dev mailing list >>>> OpenStack-dev@lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>> >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev