- Apr 20, 2010
-
-
Guido Trotter authored
Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
In order not to complicate to much the _ExecuteKVMRuntime function with nested try/except/finally/else constructs we move the actual runcmd+check call in a separate _RunKVMCmd function. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
If this file exists, for an instance, we release the uid contained inside back to the uid pool, at instance shutdown. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
We can't guarantee to keep the LockedObject around, when ReleaseUid is called (because that might happen, for example, after a ganeti shutdown/restart). So we'll support releasing on just an integer uid. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
uidpool users that get passed a LockedUid by the uidpool need to know which one the uid is. Since it's not nice to make them access a private member, and we shouldn't make "uid" public either, we'll add a getter method. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
Currently putting the cleanup just after the actual shutdown ensures that it never gets called, due to how the retry/shutdown cycle works. So we move those cleanups to their new dedicated place. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
It's a lot easier, when looking at the output, if you can search the parameter you're looking for alphabetically. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
Currently some hypervisors (namely kvm) need to do some cleanup after making sure an instance is stopped. With the moving of the retry cycle in backend those cleanups were never done. In order to solve this we add a new optional hypervisor function, CleanupInstance, which gets called at the end of the shutdown procedure, and which interested hypervisors can implement to be sure not to miss cleanup operations. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
René Nussbaumer authored
Additionally also move to the RunWhileStopped method for the configuration merger. Signed-off-by:
René Nussbaumer <rn@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
When enabling a new hypervisor, we must ensure that we have its parameters in the cluster (global) hvparams dictionary. Furthermore, we add a verify check for this case (this should be better replaced with an auto-fix?). Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Iustin Pop authored
Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Iustin Pop authored
Commit 5fa16422 removed the checks at sed time, but only for %.7. We need to do it for %.8 too. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
René Nussbaumer authored
Signed-off-by:
René Nussbaumer <rn@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Apr 19, 2010
-
-
Luca Bigliardi authored
Fix options description in the documentation for gnt-node powercycle. Signed-off-by:
Luca Bigliardi <shammash@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
Also, fix the string quoting style. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Balazs Lecz <leczb@google.com>
-
Michael Hanselmann authored
*.py[co] were not removed from lib/confd. Removing *.py[co] from all directories listed in $DIRS can't hurt. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
- Apr 16, 2010
-
-
Iustin Pop authored
The primary IP is not used for DRBD disks, only for the job queue and internal commands. As such, it's trivial (with a quiet job queue) to re-ip the node. The patch just relaxes the checks in LUAddNode, and manual testing shows that live instances on that node keep working, and that cluster verify is happy afterwards. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Balazs Lecz authored
Signed-off-by:
Balazs Lecz <leczb@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Apr 15, 2010
-
-
Michael Hanselmann authored
This will be used by the new import/export daemon to split output by its child processes into lines. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Iustin Pop authored
There are a few issues with disabled file storage: - cluster initialization is broken by default, as it uses the 'no' setting which is not a valid path - some other parts of the code require the file storage dir to be a valid path; we workaround by skipping such code paths when it is disabled A side effect is that we abstract the storage type checks into a separate function and add validation in RepairNodeStorage (previously a luxi client which didn't use cli.py and submitted an invalid type would get "storage units of type 'foo' can not be repaired"). Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Iustin Pop authored
This patch updates the docstrings in tools/ (mostly in lvmstrap, which is very very old code-base) and then enabled the tools in this directory for 'make apidoc' too. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Iustin Pop authored
2.1's cfgupgrade doesn't support upgrading from 1.2, only from 2.0. However, it's trivial to forward-port the 2.0 cfgupgrade to work with 2.1, thus providing an upgrade path for 1.2 users directly to 2.1, without the intermediate step of installing 2.0. The new cfgupgrade12 file has just a few trivial changes from 2.0, and skipping the load of the config file. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Iustin Pop authored
This can be used for two purposes: - safety copy of the config file, with just the secrets changed - cleanup of the config file (full randomization), so that (e.g.) users could send a broken config file to the devel-list Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Iustin Pop authored
Commit 43575108 added bootstrap.GenerateclusterCrypto and commit 7506a7f1 changed cfgupgrade to use it. However, this lost the functionality of upgrading in non-default DATA_DIR. To fix this, we enhance bootstrap.GenerateclusterCrypto to accept custom file paths for the three files it modifies. If more files will be needed in the future, we could just pass in modified DATA_DIR, but for now it suffices. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
René Nussbaumer authored
* Be more clear about when POST and PUT should be used * Be more verbose on parameters * Describe allowed parameter values (if not self explaining) Signed-off-by:
René Nussbaumer <rn@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Apr 13, 2010
-
-
Iustin Pop authored
Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
- Apr 12, 2010
-
-
René Nussbaumer authored
Signed-off-by:
René Nussbaumer <rn@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-