Skip to content
Snippets Groups Projects
  1. Sep 28, 2012
  2. Sep 14, 2012
  3. Sep 11, 2012
  4. Jul 25, 2012
  5. Jul 24, 2012
    • Iustin Pop's avatar
      KVM: only pass boot flag once · 2b846304
      Iustin Pop authored
      
      This addresses issue 230: passing two methods of booting to KVM can,
      depending on the KVM version, confuse it.
      
      Note that commit 4304964a introduced a partial fix for this (but only
      for disks, and keyed on KVM versions). However, it didn't fix cdrom
      booting, which still fails with the same error, so let's fix it more
      generically; we still leave the per-disk check since that is about
      -boot c versus -drive …,boot=on rather than two boot methods.
      
      Patch is based on the one submitted by Vladimir Mencl, many thanks!
      
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      2b846304
  6. Jul 20, 2012
  7. Jul 19, 2012
    • Iustin Pop's avatar
      Add a new gnt-node command list-drbd · 7acbda7b
      Iustin Pop authored
      
      This uses confd to query the DRBD minors, which is very special; no
      other command currently does so.
      
      Since the backend is only implemented in the Haskell version of confd,
      we have checks that 1) confd is enable, and 2) hs confd is also
      enabled. If by mistake people do manage to query Python confd, the
      error message will be clean:
      
        Query gave non-ok status '2': not implemented
      
      So nothing breaks in an "ugly" way.
      
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarAgata Murawska <agatamurawska@google.com>
      7acbda7b
  8. Jul 05, 2012
    • Iustin Pop's avatar
      Add --wait-for-sync in gnt-instance · f30d8165
      Iustin Pop authored
      
      Note that this needs (like for the opcode) a new option, with the
      default reverted (False instead of True).
      
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      f30d8165
    • Iustin Pop's avatar
      hbal: return exit status 0 in case of early exit · 2a2e2610
      Iustin Pop authored
      
      This derives from an internal bug, but the story is consistent across
      both internal and external usage of hbal.
      
      Basically right now, hbal returns exit code 1 if requested to exit
      early, even if all jobs are successful. This is counter-intuitive due
      to two reasons:
      
      - hbal did what it was requested (exit early), so it shouldn't return error
      - there were no job failures, so there's nothing to "cleanup" or
        investigate on the Ganeti cluster, so again it shouldn't return
        error
      
      Therefore the new behaviour is as follows:
      
      - for cases where all jobs were successful, even if terminated early
        via SIGINT or via --limit, we exit with code 0
      - for cases where jobs have failed or there were other errors in
        running hbal, the exit code is 1
      - for cases were hbal is requested an immediate termination (SIGTERM),
        exit code is 2, denoting "unknown whether the Ganeti cluster is
        consistent or not"
      
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      2a2e2610
  9. Jun 29, 2012
  10. Jun 25, 2012
  11. Jun 19, 2012
    • Guido Trotter's avatar
      Allow single-homed <-> multi-homed transitions · 79829d23
      Guido Trotter authored
      
      To change the cluster from single homed to multi homed or vice versa one
      must target the master node first, and pass the --force option. All
      other nodes then will work as long as they are reachable by the master.
      
      Note that this will also prevent a node to be set to single-homed if the
      master is multi-homed, which wasn't disallowed before, and warn if a
      single-homed <-> multi-homed transition happens.
      
      Also note that it's still theoretically possible to flip a cluster
      inadvertently by changing the master node this way, and then doing a
      master failover before fixing the other nodes.
      
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      79829d23
  12. Jun 14, 2012
  13. Jun 12, 2012
  14. May 29, 2012
  15. May 22, 2012
  16. May 16, 2012
  17. May 11, 2012
  18. Apr 26, 2012
  19. Apr 19, 2012
  20. Apr 18, 2012
  21. Mar 30, 2012
  22. Mar 26, 2012
  23. Mar 21, 2012
  24. Mar 19, 2012
  25. Mar 16, 2012
  26. Mar 13, 2012
  27. Feb 29, 2012
Loading