GitLab

* stable-2.11
  Remove user-initiated shutdown design from drafts
  Improve startup/shutdown in the admin guide
  Improve user down documentation
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

.. as it has been already implemented in 2.11.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Helga Velroyen <helgav@google.com>

Instance creation supports opportunistic locking. So,
also export it on the command line. There is no reason
to have this feature RAPI only.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Cherry-picked from e845c100.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Petr Pudlak <pudlak@google.com>

Fixes issue 877.
Signed-off-by: Jose A. Lopes <jabolopes@google.com>
Reviewed-by: Petr Pudlak <pudlak@google.com>

... namely, the 'user-shutdown' cluster parameter.
Signed-off-by: Jose A. Lopes <jabolopes@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

Change the way MultiMap is an instance of Arbitrary to
be a random term of the exported functions. In this way,
we really obtain a sample of all values of type MultiMap
that are definable outside the module. In particular, we
verify that all invariants of the implementation are preserved
over all exported functions. This renders the extensionality
test meaningful.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Petr Pudlak <pudlak@google.com>

With the recent changes, opportunistic locking should not
require retries any more on clusters that have enough capacity.
So it is fair to add the --opportunistic-locking option the
parallel instance creation tests. In this way, we
- verify that the absence of the need to retry is indeed true and
- get a realistic performance measurement for truly parallel
  instance creation.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Cherry-picked from 37d6f7f5.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Explicitly state, that parallelism enhancing options are to be used
in parallel performance tests, if it is best practice to use them on
the respective versions. A prerequisite for those options is that
using them does not require, even under heavy load but assuming enough
capacity in the cluster, any jobs to be retried.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Cherry-picked from a305cb96.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Change lock allocation in mcpu to honor the required minimum
of locks to allocate in opportunistic lock allocation.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Cherry-picked from f3f1fc57.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

In opportunistic locking, we always ask for as many locks
as possible to later chose what fits best. However, we
may also ask for a minimum as otherwise it cannot work
for principle reasons. For DRBD, this minimum should
be two, rather than the default one.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Cherry-picked from ed94242f.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

LUs may decide to acquire locks in an opportunistic way. In this
case, also allow them to specify the number of locks the which to
acquire at least.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Cherry-picked from 24ef93b3.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

...so that jobs can wait till they get a number of locks
that might work at least in principle.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Cherry-picked from 280f37bc.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

...allowing to request at least a certain number of
the requests to succeed and otherwise not touch the
locking state.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Cherry-picked from 96245004.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

* stable-2.11
  Fix format of NEWS file
  Bump revision to 2.11.3
  Prepare NEWS file for 2.11.3 release

* stable-2.10
  Make gnt-cluster upgrade honor backup-dir
  Add a new --with-backup-dir configure option
  Fix BlockdevSnapshot in case of non lvm-based disk
  Fix RAPI in case split query mechanism is used
  Allow disk hot-remove even with chroot or SM
  Remove superflous loop in instance queries

Conflicts:
	NEWS: takke all additions
	configure.ac: ignore revision bump
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

* stable-2.10
  Make gnt-cluster upgrade honor backup-dir
  Add a new --with-backup-dir configure option
  Fix BlockdevSnapshot in case of non lvm-based disk
  Fix RAPI in case split query mechanism is used
  Allow disk hot-remove even with chroot or SM
  Remove superflous loop in instance queries

Conflicts:
	lib/cmdlib/instance_query.py: take version from 2.11
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

Make gnt-cluster upgrade honor the --with-backup-dir configure option.
In this way, at configure time, it can be decided in which directory
the configuration backup tar balls are put.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

During Ganeti version upgrades, Ganeti creates a backup of
the full configuration directory. Add a new configure option
to decide in which directory the backup tar ball is to be put.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

In case of non lvm-based disk (i.e. drbd, plain disk template)
snapshot is currently not supported. The RPC will fail reporting the
disk's logical_id (and not unique_id since only BlockDev has one)
and its dev_type.
Signed-off-by: Dimitris Aragiorgis <dimara@grnet.gr>
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

Let RAPI raise HttpNotFound() in case the item requested is not
found, if luxid serves the query (split query mechanism).
Signed-off-by: Dimitris Aragiorgis <dimara@grnet.gr>
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

Up until now, in case the KVM hypervisor used chroot or pool/user
security model, disk hot-remove was not allowed. This should not be
the case since only during hot-add there are permission constrains.

Fix that.
Signed-off-by: Dimitris Aragiorgis <dimara@grnet.gr>
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

This patch fixes a piece of convoluted code in the
implementation of instance queries. There was an
unecessarily nested loop, which in case of ongoing
migrations, could throw a key error. This fixes
issue 875.
Signed-off-by: Helga Velroyen <helgav@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

Signed-off-by: Helga Velroyen <helgav@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

Signed-off-by: Helga Velroyen <helgav@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

Add all changes since the last release.
Signed-off-by: Helga Velroyen <helgav@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

* stable-2.11
  (no changes)

* stable-2.10
  (no changes)

* stable-2.9
  Push return out of genericResult
  Make htools tolerate missing "spfree" on luxi
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Petr Pudlak <pudlak@google.com>

...that was accidentally removed in e8127e66.
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

* stable-2.10
  (no changes)

* stable-2.9
  Push return out of genericResult
  Make htools tolerate missing "spfree" on luxi
Signed-off-by: Klaus Aehlig <aehlig@google.com>
Reviewed-by: Hrvoje Ribicic <riba@google.com>

In particular, test serialization of IPv4Reservation, which is used
on the Python part as well.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

We verify that 'readJSON . showJSON == Ok' and that maps are equal iff
keys map to the same values.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

It generates random pairs of keys/values and constructs a map from them.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

.. so that tests that require these calls still work.

Also use the mocked configuration for some tests that require
functions related to IP reservations.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

Also remove unnecessary constants.

Furthermore remove configuration synchronization locks that aren't
needed any more.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

This corresponds to the currents IP reservation methods in ConfigWriter.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

In particular, allow the modifying function to fail with an error, which
will then be reported in the WConfd monad, and use logging.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

For complex pure functions that update an IORef it's convenient to be
able to log error messages. This function makes it possible by
accumulating error messages from the pure function, threading them
through atomicModifyIORef and logging them afterwards at once.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

.. and corresponding helper functions.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

.. that follow the original Python implementation.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

In particular, for reserving a value given the set of reserved ones,
looking up networks by a UUID and for creating stateful computations.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

.. as it's not useful anywhere outside.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>

Before many of them threw just GenericError.
Signed-off-by: Petr Pudlak <pudlak@google.com>
Reviewed-by: Klaus Aehlig <aehlig@google.com>