As for the notifier proposed above it is correct that neutron needs to be
changed. This should not be a massive amount of work. Today it works with
nova only pretty much because nova it's the only compute service it
interacts with.
The question brought aboud ping vs operational status is a very go
On 06/10/2016 03:13 PM, Kevin Benton wrote:
Polling should be fine. get_port operations a relatively cheap operation
for Neutron.
Just in principle, I would suggest this polling have a back-off built
into it. Poll once, see the port is not yet "up" - wait a semi-random
short length of time,
miss some critical logs.
> Thanks
> Gary
>
> From: Kevin Benton
> Reply-To: OpenStack List
> Date: Saturday, June 11, 2016 at 1:13 AM
> To: OpenStack List
>
> Subject: Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port
> isActive
>
> Polling
penstack.org>>
Subject: Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port
isActive
Polling should be fine. get_port operations a relatively cheap operation for
Neutron.
Maybe for the future we can have a more pluggable version of the nova callback
notifier we have in Neut
Polling should be fine. get_port operations a relatively cheap operation
for Neutron.
Maybe for the future we can have a more pluggable version of the nova
callback notifier we have in Neutron like Salvatore pointed out.
On Fri, Jun 10, 2016 at 7:49 AM, Mohammad Banikazemi wrote:
> Hi Neil,
>
>
On Fri, Jun 10, 2016 at 5:18 PM, Neil Jerram wrote:
> Yes, that all makes sense - thanks for explaining.
>
> Neil
>
>
> On Fri, Jun 10, 2016 at 3:50 PM Mohammad Banikazemi wrote:
>
>> Hi Neil,
>>
>> Currently, when a docker libnetwork "join" operation in Kuryr is
>> returned, it is not guara
Yes, that all makes sense - thanks for explaining.
Neil
On Fri, Jun 10, 2016 at 3:50 PM Mohammad Banikazemi wrote:
> Hi Neil,
>
> Currently, when a docker libnetwork "join" operation in Kuryr is returned,
> it is not guaranteed that the network connectivity has been established.
> There ar
Hi Neil,
Currently, when a docker libnetwork "join" operation in Kuryr is returned,
it is not guaranteed that the network connectivity has been established.
There are containers that check for network connectivity as the first thing
they do when they come up and under heavy load some notice there
When you write "Neutron has the ability already of sending an event as a
REST call to notify a third party", that third party can be Nova only as of
now and notifying any other party requires changes to Neutron. It seems
that one needs to add a notifier for Kuryr similar to the one that exists
for
