Re: [openstack-dev] [neutron] multiple agents with segment access

2017-11-15 Thread Legacy, Allain
> -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: Tuesday, November 14, 2017 4:19 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [neutron] multiple agents with segment access > > In general, you should

[openstack-dev] [neutron] multiple agents with segment access

2017-11-14 Thread Legacy, Allain
Is it a known limitation that the ML2 plugin and associated drivers do not properly handle cases where there are multiple agents running on the same host? That is, two or more agents that reside on the same host and both report device/interface mappings for physical networks?One such

Re: [openstack-dev] [oslo][concurrency] lockutils lock fairness / starvation

2017-05-15 Thread Legacy, Allain
> -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Monday, May 15, 2017 2:55 PM <...> > > Excerpts from Legacy, Allain's message of 2017-05-15 18:35:58 +: > > import eventlet > > eventlet.monkey_patch > > That's not calling monkey_patch -- there are no

[openstack-dev] [oslo][concurrency] lockutils lock fairness / starvation

2017-05-15 Thread Legacy, Allain
Can someone comment on whether the following scenario has been discussed before or whether this is viewed by the community as a bug? While debugging a couple of different issues our investigation has lead us down the path of needing to look at whether the oslo concurrency lock utilities are