[openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

Mike Bayer wrote: > Well let me reiterate the idea, which is that: > > 1. we add features to oslo.db so that the use of a custom stored > function is not a big deal > > 2. we add features to oslo.db that are based on using triggers, special > constraints, or Gist indexes, so that the use of a

Re: [openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

On 07/21/2016 02:43 PM, Carl Baldwin wrote: None of these operations are expected to be very contentious and performance hasn't really been a concern yet. If it were a big concern, I'd be very interested in the GiST index solution because, as I understand it, detecting overlap without that

Re: [openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

I think the one use case you missed is the bug for which it was being developed to fix: https://review.openstack.org/#/c/314054/ Currently we check for overlapping subnets on the same network in a lookup before creating the subnet, so two requests can race and get overlapping subnets committed to

Re: [openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

On Tue, Jul 19, 2016 at 7:40 AM, Mike Bayer wrote: > Oslo.db devs : > > We've developed a system by which CIDR math, such as that of detecting > region overlaps, can be performed on a MySQL database within queries [1] > [2]. This feature makes use of a custom stored function

Re: [openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

On Tue, Jul 19 2016, Mike Bayer wrote: Hi Mike, > We've developed a system by which CIDR math, such as that of detecting region > overlaps, can be performed on a MySQL database within queries [1] [2]. This > feature makes use of a custom stored function I helped to produce which > provides

Re: [openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

Mike, On Tue, Jul 19, 2016 at 7:40 AM, Mike Bayer wrote: > Note that I use the term "function" and not "procedure" to stress that this > is not a "stored procedure" in the traditional sense of performing complex > business logic and persistence operations - this CIDR function

[openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

Oslo.db devs : We've developed a system by which CIDR math, such as that of detecting region overlaps, can be performed on a MySQL database within queries [1] [2]. This feature makes use of a custom stored function I helped to produce which provides functionality similar to that which