Open Stack

On 04/28/2015 06:25 AM, Rossella Sblendido wrote:
> 
> 
> On 04/28/2015 03:24 AM, Armando M. wrote:
>>     >> UnsupportedVersion error if the version is not bumped in their agent too.
>>     >>
>>     >
>>     > Could the server fall back and keep on using the old version of the API? I
>>     > think that would make for a much nicer experience, especially in face of
>>     > upgrades. Is this not possible? If it is, then the in vs out matter is not
>>     > really an issue and out-of-tree code can reflect the change in API at their
>>     > own pace.
>>
>>     while it's indeed nicer, it's difficult as port_update is
>>     an async call (cast) and does not wait for errors
>>     including UnsupportedVersion.
>>
>>
>> Then, let's figure out how to change it!
> 
> Russell suggested a way to handle it using a version_cap. It doesn't
> seem a trivial change and Russell already mentioned that it adds
> complexity. If we feel that it's necessary I can look into it.

Armando's suggestion is possible if the method is changed from cast() to
call(), but switching from async to sync has a cost, too.

-- 
Russell Bryant