1. 25 Jan, 2010 1 commit
    • Iustin Pop's avatar
      Add a crude disable for DRBD barriers · 89b70f39
      Iustin Pop authored
      
      
      Ideally we want to/will have per-device DRBD controls of disk/metadata
      flushes. In the meantime, we want at least a disable of the barrier
      functionality for cases where one has battery-backed caches.
      
      Background: DRBD has four mechanism of handling ordered disk-writes.
      From the drbdsetup man-page, these are: barrier, flush, drain and none.
      DRBD prior to 8.2 only has drain and none. This patch makes all 8.x
      versions of DRBD disable all methods, and revert to none, in case one
      fully trusts batteries (either UPS for the whole system or battery for
      NVRAM).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      89b70f39
  2. 22 Jan, 2010 2 commits
  3. 20 Jan, 2010 1 commit
  4. 15 Jan, 2010 1 commit
  5. 14 Jan, 2010 2 commits
  6. 13 Jan, 2010 11 commits
  7. 11 Jan, 2010 1 commit
  8. 05 Jan, 2010 2 commits
    • Iustin Pop's avatar
      Introduce a Luxi call for GetTags · 7699c3af
      Iustin Pop authored
      
      
      This changes from submitting jobs to get the tags (in cli scripts) to
      queries, which (since the tags query is a cheap one) should be much
      faster.
      
      The tags queries are already done without locks (in the generic query
      paths for instances/nodes/cluster), so this shouldn't break tags query
      via gnt-* list-tags.
      
      On a small cluster, the runtime of gnt-cluster/gnt-instance list tags
      more than halves; on a big cluster (with many MCs) I expect it to be
      more than 5 times faster. The speed of the tags get is not the main
      gain, it is eliminating a job when a simple query is enough.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      7699c3af
    • Iustin Pop's avatar
      LURenameCluster: run post hook on all nodes · 47a72f18
      Iustin Pop authored
      
      
      Since the cluster name might be used for various purposes on nodes, we
      should let all nodes "know" about a cluster rename by running the post
      hook on all nodes. This will make cluster rename slightly
      slower/costlier, but it is not/shouldn't be an operation that is run
      very often.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarOlivier Tharan <olive@google.com>
      47a72f18
  9. 04 Jan, 2010 19 commits