Open Stack

On Sun, Jun 28, 2015 at 1:16 PM, Duncan Thomas <duncan.thomas at gmail.com>
wrote:

> We need mutual exclusion for several operations. Whether that is done by
> entity queues, locks, state based locking at the api later, or something
> else, we need mutual exclusion.
>
> Our current api does not lend itself to looser consistency, and I struggle
> to come up with a sane api that does - nobody doing an operation on a
> volume  wants it to happen maybe, at some time...
>
What about deletes?  They can happen later on, which can help in these
situations I think.

-- 
*Avishay Traeger*
*Storage R&D*

Mobile: +972 54 447 1475
E-mail: avishay at stratoscale.com



Web <http://www.stratoscale.com/> | Blog <http://www.stratoscale.com/blog/>
 | Twitter <https://twitter.com/Stratoscale> | Google+
<https://plus.google.com/u/1/b/108421603458396133912/108421603458396133912/posts>
 | Linkedin <https://www.linkedin.com/company/stratoscale>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150629/5b87d922/attachment.html>