Is TOR based vxlan really a common interest to most of the people, and
should a BP be taken care now with its designed use case of 3rd TOR backend
integration?


On Fri, Sep 5, 2014 at 10:54 PM, Robert Kukura <kuk...@noironetworks.com>
wrote:

> Kyle,
>
> Please consider an FFE for https://blueprints.launchpad.
> net/neutron/+spec/ml2-hierarchical-port-binding. This was discussed
> extensively at Wednesday's ML2 meeting, where the consensus was that it
> would be valuable to get this into Juno if possible. The patches have had
> core reviews from Armando, Akihiro, and yourself. Updates to the three
> patches addressing the remaining review issues will be posted today, along
> with an update to the spec to bring it in line with the implementation.
>
> -Bob
>
>
> On 9/3/14, 8:17 AM, Kyle Mestery wrote:
>
>> Given how deep the merge queue is (146 currently), we've effectively
>> reached feature freeze in Neutron now (likely other projects as well).
>> So this morning I'm going to go through and remove BPs from Juno which
>> did not make the merge window. I'll also be putting temporary -2s in
>> the patches to ensure they don't slip in as well. I'm looking at FFEs
>> for the high priority items which are close but didn't quite make it:
>>
>> https://blueprints.launchpad.net/neutron/+spec/l3-high-availability
>> https://blueprints.launchpad.net/neutron/+spec/add-ipset-to-security
>> https://blueprints.launchpad.net/neutron/+spec/security-
>> group-rules-for-devices-rpc-call-refactor
>>
>> Thanks,
>> Kyle
>>
>> _______________________________________________
>> 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

Reply via email to