Open Stack

So are we talking about using script to eliminate unnecessary new vif types?

Then, a little confusion that why this BP[1] is postponed to L, and
this BP[2] is merged in K.

[1]  https://review.openstack.org/#/c/146914/
[2]  https://review.openstack.org/#/c/148805/

In fact [2] can be replaced by [1] with a customized vouter script, no
need for a totally new vif types introduced by K cycle.

On Thu, Feb 19, 2015 at 3:42 AM, Brent Eagles <beagles at redhat.com> wrote:
> Hi,
>
> On 18/02/2015 1:53 PM, Maxime Leroy wrote:
>> Hi Brent,
>
> <snip/>
>
>> Thanks for your help on this feature. I have just created a channel
>> irc: #vif-plug-script-support to speak about it.
>> I think it will help to synchronize effort on vif_plug_script
>> development. Anyone is welcome on this channel!
>>
>> Cheers,
>> Maxime
>
> Thanks Maxime. I've made some updates to the etherpad.
> (https://etherpad.openstack.org/p/nova_vif_plug_script_spec)
> I'm going to start some proof of concept work these evening. If I get
> anything worth reading, I'll put it up as a WIP/Draft review. Whatever
> state it is in I will be pushing up bits and pieces to github.
>
> https://github.com/beagles/neutron_hacking vif-plug-script
> https://github.com/beagles/nova vif-plug-script
>
> Cheers,
>
> Brent
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>