Ensure non-overlapping cidrs in subnetpools with galera
This change enables galera support in _lock_subnetpool[1]. It uses an
update to disallow 2 transactions performing concurrent subnet
allocation in the same subnetpool to succeed: the 2 transactions will
conflict because they update the same row so the db (including Galera
multi-writer cluster) will discard the last transaction and
Controller.create[2] will catch and retry the "discarded" allocation.
This change adds the "hash" attribute in "subnetpools" table to enable
previous update.
Reviewed: https:/ /review. openstack. org/187985 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=03b70b10944 9f3b9329834c7aa 88fd26ed71cf26
Committed: https:/
Submitter: Jenkins
Branch: master
commit 03b70b109449f3b 9329834c7aa88fd 26ed71cf26
Author: Cedric Brandily <email address hidden>
Date: Thu May 28 18:35:17 2015 +0200
Ensure non-overlapping cidrs in subnetpools with galera
This change enables galera support in _lock_subnetpoo l[1]. It uses an create[ 2] will catch and retry the "discarded" allocation.
update to disallow 2 transactions performing concurrent subnet
allocation in the same subnetpool to succeed: the 2 transactions will
conflict because they update the same row so the db (including Galera
multi-writer cluster) will discard the last transaction and
Controller.
This change adds the "hash" attribute in "subnetpools" table to enable
previous update.
[1] neutron. ipam.subnet_ alloc.SubnetAll ocator
[2] neutron.api.v2.base
Change-Id: I74f7100a6fd9b7 787be693adffec1 5ec468d0018
Closes-Bug: #1451576