Statistics
| Branch: | Tag: | Revision:

root @ 9f9c4543

Name Size
  autotools
  daemons
  devel
  doc
  lib
  man
  qa
  src
  test
  tools
.ghci 21 Bytes
.gitignore 2.6 kB
COPYING 17.6 kB
INSTALL 11.3 kB
Makefile.am 75 kB
NEWS 129.4 kB
README 191 Bytes
UPGRADE 12.4 kB
autogen.sh 283 Bytes
configure.ac 23.4 kB
epydoc.conf.in 444 Bytes
pylintrc 2.9 kB
pylintrc-test 2.9 kB

Latest revisions

# Date Author Comment
9f9c4543 02/21/2014 02:14 pm Klaus Aehlig

Use opportunisticUnion in Arbitrary LockAllocation

Also allow the newly exported function opportunisticLockUnion in the
construction of arbitrary lock allocations.

Signed-off-by: Klaus Aehlig <>
Reviewed-by: Petr Pudlak <>
4b217f68 02/21/2014 02:14 pm Klaus Aehlig

Support opportunistic lock allocation

Add a function to opportunistically allocate as many locks of a given
set as possible. This is equivalent to sequentially try the locks in
increasing lock order after restricting to those locks where the
required owner state is higher than the currently held one....
07eec0fc 02/21/2014 02:14 pm Klaus Aehlig

Generate arbitrary :: LockAllocation according to interface

While we know that freeLocks and intersectLocks are defined in terms
of updateLocks, it is still cleaner to test against the interface: the
module Ganeti.Locking.Allocation exports several functions, and all...
d8216f2d 02/21/2014 02:14 pm Klaus Aehlig

Add a convenience function to restrict locks to a given set

As it is an operation the locking daemon is supposed to provide,
add a function restricting the locks of a user to a given list
and release all other locks.

Signed-off-by: Klaus Aehlig <>...
af8492ff 02/20/2014 11:11 am Michele Tartara

Add precise to build_chroot

Modify the build_chroot script to support Ubuntu Precise as a target
environment.

Signed-off-by: Michele Tartara <>
Reviewed-by: Helga Velroyen <>
956b83d6 02/20/2014 10:12 am Klaus Aehlig

Enforce the order restrictions on group locks

Disallow requests for an exclusive lock, if the owner already
holds a shared (and only shared) lock on a group lock that lock
belongs to.

Signed-off-by: Klaus Aehlig <>
Reviewed-by: Helga Velroyen <>
fe78783d 02/20/2014 10:12 am Klaus Aehlig

Document restrictions on lock implication

As owning a group lock has the same effect as owning a
group of locks, some restrictions have to be added to
to avoid dead locks. Document them.

Signed-off-by: Klaus Aehlig <>
Reviewed-by: Helga Velroyen <>
1ca6b451 02/19/2014 03:45 pm Klaus Aehlig

Efficiently verify consistent lock requests

Most requests for lock updates are consistent and mention
every lock only once. So verify this property efficiently
by comparing lengths. Only if the length do not coincide
go through the actual (quadratic) comparison to find a...
277c969f 02/19/2014 03:45 pm Klaus Aehlig

Add a test verifying that lock-implication is honored

Locks can be included in one another. This inclusion can be violated
in two ways, viz.,
- A holds a lock L and B holds an exclusive lock L belongs to, and
- A holds an exclusive lock and B holds a lock L belongs to....
381889dc 02/19/2014 03:45 pm Klaus Aehlig

Support lock implication in allocation

Make the module abstractly handling lock allocation
honor the additional restrictions caused by lock
implications.

Signed-off-by: Klaus Aehlig <>
Reviewed-by: Petr Pudlak <>

View all revisions | View revisions

Also available in: Atom