Now I'm blaming myself - had a closer look at the code - it's NOT a
message via the Bus, but some nova external events interface that I was
not aware of.
Sorry for all the confusion
--
-
Andreas
IRC: andreas_s
On Mi, 2016-06-08 at 08:09 +0200, Andreas Scheuring wrote:
> > This handshake
> This handshake between Neutron and Nova does not happen over RPC
Sorry, Armando, you're absolutely right. What I meant to say is, that
this communication goes via the Message Bus instead of an ReST API.
Thanks for correcting!
--
-
Andreas
IRC: andreas_s
On Mo, 2016-06-06 at 20:17
On Mon, Jun 6, 2016 at 7:18 PM, Ihar Hrachyshka wrote:
>
> > On 06 Jun 2016, at 16:44, Sean M. Collins wrote:
> >
> > I agree, it would be convenient to have something similar to what Nova
> > has:
> >
> >
>
On Mon, Jun 6, 2016 at 2:03 PM, Armando M. wrote:
>
>
> On 6 June 2016 at 10:06, Oleg Bondarev wrote:
>
>> Hi,
>>
>> There are cases where it would be useful to know the version of Neutron
>> (or any other project) from API, like during upgrades or in
Ihar Hrachyshka wrote:
>
> > On 06 Jun 2016, at 16:44, Sean M. Collins wrote:
> >
> > I agree, it would be convenient to have something similar to what Nova
> > has:
> >
> > https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/versions.py#L59-L60
> >
>
On 6 June 2016 at 17:05, Andreas Scheuring
wrote:
> Is there a chance to get rid of this vif-plugged event at all? E.g. by
> transitioning it to an ReST API interface? As far as I know this is the
> only RPC interface between neutron and nova.
>
This handshake
> On 06 Jun 2016, at 16:44, Sean M. Collins wrote:
>
> I agree, it would be convenient to have something similar to what Nova
> has:
>
> https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/versions.py#L59-L60
>
> We should put some resources behind
The ovs agent reports if it uses hybrid plug or not since [1]. At least
the hybrid plug is part of the agent state - haven't tested if it's
visible via the API. Might that be helpful?
[1]https://review.openstack.org/#/c/311814/
--
-
Andreas
IRC: andreas_s (formerly scheuran)
On Mo,
Is there a chance to get rid of this vif-plugged event at all? E.g. by
transitioning it to an ReST API interface? As far as I know this is the
only RPC interface between neutron and nova.
--
-
Andreas
IRC: andreas_s (formerly scheuran)
On Mo, 2016-06-06 at 20:25 +0900, Akihiro Motoki
I agree, it would be convenient to have something similar to what Nova
has:
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/versions.py#L59-L60
We should put some resources behind implementing micro versioning and we
could end up with something similar.
It would also be
Hi,
If I understand correctly, what you need is to expose the neutron
behavior through API or something. In this particular case, neutron
need to send a vif-plugged event when neutron detects some event in
the data plane (VIF plugging in OVS or some virtual switch). Thus I
think the question can
On 6 June 2016 at 10:06, Oleg Bondarev wrote:
> Hi,
>
> There are cases where it would be useful to know the version of Neutron
> (or any other project) from API, like during upgrades or in cross-project
> communication cases.
> For example in
Hi,
There are cases where it would be useful to know the version of Neutron (or
any other project) from API, like during upgrades or in cross-project
communication cases.
For example in https://review.openstack.org/#/c/246910/ Nova needs to know
if Neutron sends vif-plugged event during live
13 matches
Mail list logo