Open Stack

On Mon, Oct 5, 2015 at 10:41 PM, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>> On 05 Oct 2015, at 15:32, Gary Kotton <gkotton at vmware.com> wrote:
>>
>>
>>
>> On 10/5/15, 3:21 AM, "Ihar Hrachyshka" <ihrachys at redhat.com> wrote:
>>
>>>> On 04 Oct 2015, at 19:21, Gary Kotton <gkotton at vmware.com> wrote:
>>>>
>>>> Sorry, it is not a result of the AZ support (humble apologies)
>>>>
>>>> It is a result of https://review.openstack.org/#/c/226362/
>>>
>>> So you use DHCP agent with non-ml2 plugin, and it broke you. Do you think
>>> it¹s ok for you to change the RPC topic to work with Mitaka, or we¹ll
>>> need to handle it more gracefully, f.e. by detecting the reply timeout
>>> and switching back to the old topic?
>>
>> My thinking is that we should fail to use the old topic. But then again, I
>> would expect that the Neutron service would first be upgraded and then the
>> agents. Updating the agents first would be a recipe for disaster.
>
> Yes, controller first, then agents. That’s why there was no fallback mechanism in that patch that broke you, while we looked into backwards compatibility. Though no one considered the case of 3party plugins that may rely on some in-tree agents. We can accommodate for them, if it seems too much effort for them to change the topic name they report on. But note that it would also mean that those plugins don’t utilize the separate threads to handle reports, which can be bad for their scalability.

i made a fix for midonet.  just FYI.
https://review.openstack.org/#/c/230333/

>
> Ihar
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>