Open Stack

hi,

On Mon, Jul 24, 2017 at 8:49 AM, Kevin Benton <kevin at benton.pub> wrote:
> If I understand the main issue with using regular callbacks, it's mainly
> just that the flavor assignment itself is in a callback, right?

yes.

>
> If so, couldn't we solve the problem by just moving flavor assignment to an
> explicit call before emitting the callbacks? Or would that still result in
> other ordering issues?

it would solve the problem for CREATE.
for UPDATE and DELETE, i'm not sure.
UPDATE can change the flavor but it's supposed to be a special case
only for dvr/ha, right?
AFTER_DELETE might be tricky as we probably need to provide flavor
info to subscribers.

>
> On Thu, Jul 13, 2017 at 3:01 AM, Takashi Yamamoto <yamamoto at midokura.com>
> wrote:
>>
>> hi,
>>
>> today i managed to play with l3 flavors.
>> i wrote a crude patch to implement midonet flavor. [1]
>>
>> [1] https://review.openstack.org/#/c/483174/
>>
>> a good news is it's somehow working.
>>
>> a bad news is it has a lot of issues, as you can see in TODO comments
>> in the patch.
>> given these issues, now i tend to think it's cleaner to introduce
>> ml2-like precommit/postcommit driver api (or its equivalent via
>> callbacks) rather than using these existing notifications.
>>
>> how do you think?
>
>