1. 14 May, 2010 1 commit
  2. 20 Apr, 2010 1 commit
  3. 19 Apr, 2010 1 commit
  4. 16 Apr, 2010 1 commit
  5. 12 Apr, 2010 1 commit
  6. 08 Apr, 2010 2 commits
  7. 31 Mar, 2010 1 commit
  8. 17 Mar, 2010 3 commits
  9. 15 Mar, 2010 3 commits
  10. 12 Mar, 2010 1 commit
  11. 10 Mar, 2010 3 commits
  12. 09 Mar, 2010 2 commits
  13. 22 Feb, 2010 1 commit
  14. 11 Feb, 2010 2 commits
  15. 10 Feb, 2010 1 commit
  16. 09 Feb, 2010 1 commit
    • Iustin Pop's avatar
      Add an early release lock/storage for disk replace · 7ea7bcf6
      Iustin Pop authored
      
      
      This patch adds an early_release parameter in the OpReplaceDisks and
      OpEvacuateNode opcodes, allowing earlier release of storage and more
      importantly of internal Ganeti locks.
      
      The behaviour of the early release is that any locks and storage on all
      secondary nodes are released early. This is valid for change secondary
      (where we remove the storage on the old secondary, and release the locks
      on the old and new secondary) and replace on secondary (where we remove
      the old storage and release the lock on the secondary node.
      
      Using this, on a three node setup:
      
      - instance1 on nodes A:B
      - instance2 on nodes C:B
      
      It is possible to run in parallel a replace-disks -s (on secondary) for
      instances 1 and 2.
      
      Replace on primary will remove the storage, but not the locks, as we use
      the primary node later in the LU to check consistency.
      
      It is debatable whether to also remove the locks on the primary node,
      and thus making replace-disks keep zero locks during the sync. While
      this would allow greatly enhanced parallelism, let's first see how
      removal of secondary locks works.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      7ea7bcf6
  17. 01 Feb, 2010 1 commit
  18. 27 Jan, 2010 1 commit
  19. 22 Jan, 2010 1 commit
  20. 16 Dec, 2009 1 commit
  21. 10 Dec, 2009 1 commit
  22. 25 Nov, 2009 1 commit
  23. 16 Nov, 2009 1 commit
  24. 06 Nov, 2009 2 commits
  25. 04 Nov, 2009 1 commit
  26. 02 Nov, 2009 2 commits
    • Iustin Pop's avatar
      Some improvements to gnt-node repair-storage · 7e9c6a78
      Iustin Pop authored
      
      
      Currently the repair storage has two issues:
      
      - down instances are aborting the operation, even though they should be
        ignored (it's not technically possible to know their disk status
        unless we would activate their disks)
      - if the VG is so broken that disks cannot be activated via gnt-instance
        activate-disks or gnt-instance startup, it's not possible to repair
        the VG at all
      
      The patch makes the opcode skip down instances and also introduces an
      ``--ignore-consistency`` flag for forcing the execution of the LU.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      7e9c6a78
    • Iustin Pop's avatar
      Unify the query fields for the storage framework · 620a85fd
      Iustin Pop authored
      
      
      This patch unifies the query fields in the storage framework for all
      types. Note that the information is still computed on-demand, so if e.g.
      the used disk space is not requested for the ‘file’ type, it won't be
      computed on nodes.
      
      Summary of changes:
      - improve the LVM storage type to support multiple lvm fields in the
        LIST_FIELDS declaration and constant (not-computed via lvm commands)
        fields
      - rename utils.GetFilesystemFreeSpace to utils.GetFilesystemStats
        returning tuple of (total, free)
      - add used and free as valid fields for lvm-vg (use being computed as
        vg_size-vg_free)
      - make allocatable accepted for all types (ones which are always
        allocatable always return True)
      - add a new list field ‘type’ that gives the current selected type; not
        much useful today (except for understanding what the default output
        is) but in the future might help if we want to list multiple types
      - add type, size and allocatable to the default output field list
      - update the man page with details on how, for file storage, size ≠ used
        + free for non-mountpoint cases
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      620a85fd
  27. 28 Oct, 2009 2 commits
    • Iustin Pop's avatar
      Documentation updates · c71a1a3d
      Iustin Pop authored
      
      
      Our admin guide was very very trivial. This patch updates it to contain
      advice on when to use which commands, removes the instance
      administration part from the installation guide (moved to the admin
      guide), and adds a walkthrough document that should be useable as a
      starting point for new admins.
      
      The patch also adds emacs variables to the documents, and rewraps some
      which were not already at 72 chars.
      
      The doc updates also show backwards-compatible commands for Ganeti 2.0,
      as we don't have a good up-to-date 2.0 document and people might refer
      to this set of documentation even when running that.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      c71a1a3d
    • Iustin Pop's avatar
      Rename the node storage commands · 9b94905f
      Iustin Pop authored
      
      
      To reduce confusion, the following gnt-node commands are renamed:
      
      - physical-volumes → list-storage
      - modify-volume → modify-storage
      - repair-volume → repair-storage
      
      The NEWS file is update accordingly and it also gets emacs local
      variables.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      9b94905f
  28. 22 Oct, 2009 1 commit