Is there any specific reason for which you removed
havana-backport-potential tag?
Mark had added this tag so that this could be back ported into havana - as
this was accidentally missed from Havana release.
regards..
-Sukhdev
On Tue, Oct 22, 2013 at 5:21 PM, Aaron Rosen <email address hidden> wrote:
> ** Tags removed: havana-backport-potential
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1215097
>
> Title:
> Arista ML2 driver integration with port-binding BP
>
> Status in OpenStack Neutron (virtual network service):
> Fix Committed
>
> Bug description:
> This bug is to track the integration of the port-binding BP with
> Arista ML2 Mechanism Driver.
>
> It appears that Arista Driver will merge before port binding merges.
> Therefore, it was decided in the ML2 working group meeting that we
> open this bug to track this integration.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/neutron/+bug/1215097/+subscriptions
>
Hi Aaron,
Is there any specific reason for which you removed backport- potential tag?
havana-
Mark had added this tag so that this could be back ported into havana - as
this was accidentally missed from Havana release.
regards..
-Sukhdev
On Tue, Oct 22, 2013 at 5:21 PM, Aaron Rosen <email address hidden> wrote:
> ** Tags removed: havana- backport- potential /bugs.launchpad .net/bugs/ 1215097 /bugs.launchpad .net/neutron/ +bug/1215097/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Arista ML2 driver integration with port-binding BP
>
> Status in OpenStack Neutron (virtual network service):
> Fix Committed
>
> Bug description:
> This bug is to track the integration of the port-binding BP with
> Arista ML2 Mechanism Driver.
>
> It appears that Arista Driver will merge before port binding merges.
> Therefore, it was decided in the ML2 working group meeting that we
> open this bug to track this integration.
>
> To manage notifications about this bug go to:
> https:/
>