Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Currently we set KVM migration capabilities only on the source instance and leave them set even if migration fails. This leads to two problems: - There are a number of features (e.g. postcopy-ram) where the capability needs to be set on both, source and destination instance - If a migration breaks because of a capability mismatch, the capability remains set causing all future migration attempts to fail as well (see Debian bug #969028 ) Fix both issues by setting all capabilities on both sides of the migration and clearing all capabilities on the surviving side when the migration is over.  https://bugs.debian.org/969028 Signed-off-by: Apollon Oikonomopoulos <email@example.com>
Ganeti 3.0 =========== For installation instructions, read the INSTALL and the doc/install.rst files. For a brief introduction, read the ganeti(7) manpage and the other pages it suggests. Please note, that there is no supported upgrade path for users running Ganeti-2.17 (i.e. 2.17.0 beta1). Ganeti-2.17 was never released, so hopefully no one uses it.