Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
| Sent: Friday, March 7, 2014 8:53:26 AM
| Subject: [openstack-dev] [nova][vmware] Locking: A can of worms
|
| We need locking in the VMware driver. There are 2 questions:
|
| 1. How much locking do we need?
| 2. Do we need
We need locking in the VMware driver. There are 2 questions:
1. How much locking do we need?
2. Do we need single-node or multi-node locking?
I believe these are quite separate issues, so I'm going to try not to
confuse them. I'm going to deal with the first question first.
In reviewing the
(not for usage questions)
openstack-dev@lists.openstack.org
Subject: [openstack-dev] [nova][vmware] Locking: A can of worms
We need locking in the VMware driver. There are 2 questions:
1. How much locking do we need?
2. Do we need single-node or multi-node locking?
I believe these are quite separate issues
On Fri, Mar 7, 2014 at 11:53 AM, Matthew Booth mbo...@redhat.com wrote:
We need locking in the VMware driver. There are 2 questions:
1. How much locking do we need?
2. Do we need single-node or multi-node locking?
I believe these are quite separate issues, so I'm going to try not to
On Fri, Mar 7, 2014 at 12:55 PM, Doug Hellmann
doug.hellm...@dreamhost.com wrote:
http://git.openstack.org/cgit/stackforge/tooz
This is good stuff. The only solution I could come up with for image
cache management was to have yet another service that you would set up
to manage the shared image
@lists.openstack.org
| Sent: Friday, March 7, 2014 8:53:26 AM
| Subject: [openstack-dev] [nova][vmware] Locking: A can of worms
|
| We need locking in the VMware driver. There are 2 questions:
|
| 1. How much locking do we need?
| 2. Do we need single-node or multi-node locking?
|
| I believe
