Thanks for putting this all together, Salvatore.
I just want to comment on this suggestion:
1) Move the allocation logic out of the driver, thus making IPAM an
independent service. The API workers will then communicate with the IPAM
service through a message bus, where IP allocation requests
Excerpts from Salvatore Orlando's message of 2015-02-23 04:07:38 -0800:
Lazy-Stacker summary:
I am doing some work on Neutron IPAM code for IP Allocation, and I need to
found whether it's better to use db locking queries (SELECT ... FOR UPDATE)
or some sort of non-blocking algorithm.
Some
Thanks Clint.
I think you are bringing an interesting and disruptive perspective into
this discussion.
Disruptive because one thing that has not been considered so far in this
thread is that perhaps we don't need at all to leverage multi-master
capabilities for write operations.
More comments
On 25 February 2015 at 13:50, Eugene Nikanorov enikano...@mirantis.com
wrote:
Thanks for putting this all together, Salvatore.
I just want to comment on this suggestion:
1) Move the allocation logic out of the driver, thus making IPAM an
independent service. The API workers will then
jOn Mon, Feb 23, 2015 at 5:07 AM, Salvatore Orlando sorla...@nicira.com wrote:
Lazy-Stacker summary:
I am doing some work on Neutron IPAM code for IP Allocation, and I need to
found whether it's better to use db locking queries (SELECT ... FOR UPDATE)
or some sort of non-blocking algorithm.
On 25 February 2015 at 16:52, Carl Baldwin c...@ecbaldwin.net wrote:
jOn Mon, Feb 23, 2015 at 5:07 AM, Salvatore Orlando sorla...@nicira.com
wrote:
Lazy-Stacker summary:
I am doing some work on Neutron IPAM code for IP Allocation, and I need
to
found whether it's better to use db locking
On 2/25/15, 10:52 AM, Carl Baldwin c...@ecbaldwin.net wrote:
Wondering if Kilo should just focus on creating the interface which
will allow us to create multiple implementations and swap them out
during the Liberty development cycle. Hopefully, this could include
even something like your
On 24 February 2015 at 01:07, Salvatore Orlando sorla...@nicira.com wrote:
Lazy-Stacker summary:
...
In the medium term, there are a few things we might consider for Neutron's
built-in IPAM.
1) Move the allocation logic out of the driver, thus making IPAM an
independent service. The API
Lazy-Stacker summary:
I am doing some work on Neutron IPAM code for IP Allocation, and I need to
found whether it's better to use db locking queries (SELECT ... FOR UPDATE)
or some sort of non-blocking algorithm.
Some measures suggest that for this specific problem db-level locking is
more
