1. 20 May, 2011 3 commits
  2. 09 Mar, 2011 2 commits
  3. 01 Mar, 2011 2 commits
  4. 24 Feb, 2011 2 commits
  5. 26 Jan, 2011 3 commits
    • Iustin Pop's avatar
      Verify disks: increase parallelism and other fixes · 397693d3
      Iustin Pop authored
      The recent work on multi-VG support has converted LUClusterVerifyDisks
      into doing serialised calls to each node, as each node can have
      different VGs. This is suboptimal, especially for big clusters, where
      this LU is executed by the watcher very often.
      This patch changes the logic based on the observation that querying a
      node for its VGs and then requesting a LV list for those VGs is
      equivalent to simply asking for all LVs, without specifying the VG
      name(s). So backend.py needs changes to accept an empty VG list, and
      the LU itself partially reverts to the previous version.
      Additionally, we do two other fixes to this LU:
      - small improvement in getting the instance list from the config
      - MapLVsByNode works for all disk types, hence no need to restrict to
        the DRBD template, especially as today we can "recreate" disks for
        plain volumes too (the warning message in gnt-cluster is updated
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
    • Iustin Pop's avatar
      gnt-cluster verify-disks: fix VG name · fd78c5ce
      Iustin Pop authored
      Recent multi-VG work already exports the missing LV names as vg/lv,
      not simply lv. So the query and addition of the VG name in gnt-cluster
      verify-disks is redundant, and even wrong for non-default-VG
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
    • Iustin Pop's avatar
      Show hidden/blacklisted OSes in cluster info · afc3c260
      Iustin Pop authored
      Since we can blacklist/hide non-existing OSes (for preseeding), we
      cannot query easily the OSes themselves for this status. Hence we
      export the entire lists in cluster info (which should be cheaper than
      gnt-os diagnose).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
  6. 18 Jan, 2011 10 commits
  7. 13 Jan, 2011 1 commit
  8. 12 Jan, 2011 1 commit
    • Guido Trotter's avatar
      Remove --master-netdev default value · 25be0c75
      Guido Trotter authored
      Since the --master-netdev option is now used both at cluster init and at
      cluster modify time, it cannot have a default value of DEFAULT_BRIDGE
      (xen-br0) anymore. As such at cluster init we make the initialization
      explicit if another value hasn't been passed. This fixes gnt-cluster
      modify changing the master_netdev to xen-br0 if called without that
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
  9. 13 Dec, 2010 1 commit
  10. 01 Dec, 2010 1 commit
  11. 29 Nov, 2010 2 commits
  12. 27 Oct, 2010 1 commit
  13. 26 Oct, 2010 1 commit
  14. 19 Oct, 2010 1 commit
  15. 05 Oct, 2010 1 commit
  16. 20 Sep, 2010 1 commit
  17. 19 Aug, 2010 4 commits
  18. 29 Jul, 2010 1 commit
  19. 28 Jul, 2010 2 commits