Yeah, we definitely need to fix this for Grizzly.  I think the hang up on
the review is a question over whether the allocation of a specific IP
address also requires a change to lock the DB.

Bob, I think that's a good question regarding VLAN allocation.  My guess is
that this would also be impacted.

It seems like current developer of the patch is non-responsive, as they
haven't replied to comments from Feb 19th, so probably best if we have a
core team member take over the change-set.

Dan

On Mon, Mar 4, 2013 at 6:53 AM, Robert Kukura <[email protected]> wrote:

> On 03/04/2013 04:01 AM, Gary Kotton wrote:
> > Hi,
> > I personally am in favor of moving this one forward.
>
> Do we need similar DB locking in the linuxbridge, openvswitch, and
> hyperv plugins for the transactions that allocate VLAN tags and tunnel
> IDs from pools?
>
> -Bob
>
> > Thanks
> > Gary
> >
> > On 03/04/2013 10:28 AM, Salvatore Orlando wrote:
> >> Hi,
> >>
> >> The code review for this bug
> >> (https://bugs.launchpad.net/quantum/+bug/1110807 -
> >> https://review.openstack.org/#/c/21424/4) has seen no activity in the
> >> last week.
> >> The bug is marked as high, and is also marked for backporting.
> >> The patch works for me, but I still see a couple of -1s on the review.
> >> I wonder if we should approve this patch as it is, or defer everything
> >> to havana (Isaku created a blueprint for addressing race conditions)
> >>
> >> Salvatore
> >>
> >
> >
>
>
> --
> Mailing list: https://launchpad.net/~quantum-core
> Post to     : [email protected]
> Unsubscribe : https://launchpad.net/~quantum-core
> More help   : https://help.launchpad.net/ListHelp
>



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
Mailing list: https://launchpad.net/~quantum-core
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~quantum-core
More help   : https://help.launchpad.net/ListHelp

Reply via email to