On Wed, Dec 13, 2017 at 2:30 PM, Michel Peterson wrote:
> Through my work in networking-odl I've found what I believe is an issue
> present in a majority of ML2 drivers. An issue I think needs awareness so
> each project can decide a course of action.
>
> The issue stems from the adopted practice
Don't know why subject wasn't set automatically..
On Tue, Aug 4, 2015 at 3:30 PM, Mike Kolesnik wrote:
>
>
> On Tue, Aug 4, 2015 at 1:02 PM, Ihar Hrachyshka
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Hi all,
>
On Tue, Aug 4, 2015 at 1:02 PM, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi all,
>
> in feature/qos, we use ml2 extension drivers to handle additional
> qos_policy_id field that can be provided thru API:
>
> http://git.openstack.org/cgit/openstack/neutron/tre
- Original Message -
> Yes please.
> This would be a good starting point.
> I also think that the ability of editing it, as well as the value it could be
> set to, should be constrained.
FYI the oVirt project uses this field to identify ports it creates and manages.
So if you're going t
Hi,
I sent a simple patch to check the possibility to add results to callbacks:
https://review.openstack.org/#/c/201127/
This will allow us to decouple the callback logic from the ML2 plugin in the
QoS scenario where we need to update the agents in case the profile_id on a
port/network chang
- Original Message -
> Comments in-line.
>
> - Original Message -
> > On 23 May 2015 at 04:43, Assaf Muller < amul...@redhat.com > wrote:
> >
> >
> >
> > There's no real reason as far as I'm aware, just an implementation
> > decision.
> >
> > This is inaccurate. There is a reas
So their shouldn't have any issue with backward compatibility.
I'm not sure if it's backwards compatible since you're actually changing the
construct of the RPC message so it's a bit unexpected how the old agents will
react.
It's not adding a new key-value, it&
Hi Vivek,
Replies inline.
Regards,
Mike
- Original Message -
> Hi Mike,
>
> Few clarifications inline [Vivek]
>
> -Original Message-----
> From: Mike Kolesnik [mailto:mkole...@redhat.com]
> Sent: Thursday, December 18, 2014 10:58 PM
> To: OpenStack Devel
ther solution.
We have already knowledge of the agents hosting a router so this is
completely doable without waiting for fix for bug 1367391.
Also from my understanding the bug 1367391 is targeted at DVR only, not
at HA router ports.
>
>
> On Thu, Dec 18, 2014 at 6:28 PM, Mike Kolesnik wr
Hi Mathieu,
Thanks for the quick reply, some comments inline..
Regards,
Mike
- Original Message -
> Hi mike,
>
> thanks for working on this bug :
>
> On Thu, Dec 18, 2014 at 1:47 PM, Gary Kotton wrote:
> >
> >
> > On 12/18/14, 2:06 PM, "Mik
Hi Neutron community members.
I wanted to query the community about a proposal of how to fix HA routers not
working with L2Population (bug 1365476[1]).
This bug is important to fix especially if we want to have HA routers and DVR
routers working together.
[1] https://bugs.launchpad.net/neutron/+
Hi,
Currently stable branch Jenkins builds are failing due to the error:
Syncing /opt/stack/new/taskflow/requirements-py3.txt
'wrapt' is not a global requirement but it should be,something went wrong
It's my understanding that this is a side effect from your change in taskflow:
https://revie
Great script!
I have a fork that I made and improved it a bit:
https://gist.github.com/mkolesni/92076378d45c7b5e692b
This fork supports:
1. Button/link is integrated nicely to the gerrit UI (appears in the
comments title, just like the other ones).
2. Auto hide will hide comments by default (can
Hi,
Sorry for late reply, please see replies inline.
I have additional concern that API is something that's user facing so
basically now Nova is exposing some internal synchronization detail to
the outside world.
Does it make sense that the user would now be able to send messages to
this API?
--
Hi,
I came across the implementation of
https://blueprints.launchpad.net/neutron/+spec/nova-event-callback
and have a question about the way it was implemented.
I notice that now Neutron has a dependency on Nova and needs to be configured
to have nova details (API endpoint, user, password, tena
15 matches
Mail list logo