1. 23 Jul, 2010 2 commits
  2. 16 Jul, 2010 1 commit
    • Iustin Pop's avatar
      Add a migration type global hypervisor parameter · e71b9ef4
      Iustin Pop authored
      
      
      Since migration live/non-live is more stable (e.g.) for Xen-PVM versus
      Xen-HVM, we introduce a new parameter for what mode we should use by
      default (if not overridden by the user, in the opcode).
      
      The meaning of the opcode 'live' field changes from boolean to either
      None (use the hypervisor default), or one of the allowed migration
      string constants. The live parameter of the TLMigrateInstance is still a
      boolean, computed from the opcode field (which is no longer passed to
      the TL).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      e71b9ef4
  3. 09 Jul, 2010 1 commit
  4. 08 Jul, 2010 1 commit
  5. 01 Jun, 2010 2 commits
  6. 25 May, 2010 1 commit
  7. 23 Mar, 2010 1 commit
  8. 09 Mar, 2010 1 commit
  9. 08 Mar, 2010 1 commit
  10. 22 Feb, 2010 1 commit
  11. 11 Feb, 2010 2 commits
  12. 04 Jan, 2010 4 commits
  13. 25 Nov, 2009 2 commits
  14. 04 Nov, 2009 1 commit
    • Iustin Pop's avatar
      Introduce a wrapper for hostname resolving · 104f4ca1
      Iustin Pop authored
      
      
      Currently a few of the LU's CheckPrereq use utils.HostInfo which raises
      a resolver error in case of failure. This is an exception from the
      standard that CheckPrereq should raise an OpPrereqError if the error is
      in the 'pre' phase (so that it can be retried).
      
      This patch adds a new error code (resolver_error) and a wrapper over
      utils.HostInfo that just converts the ResolverError into
      OpPrereqError(…, errors.ECODE_RESOLVER). It then uses this wrapper in
      cmdlib, bootstrap and some scripts.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      104f4ca1
  15. 02 Nov, 2009 3 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
      Convert the rest of the OpPrereqError users · debac808
      Iustin Pop authored
      
      
      This finishes the conversion of OpPrereqError creation to two-argument
      style. Any leftovers as one-argument are not breaking anything, just
      losing information about the errors.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      debac808
    • 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
  16. 28 Oct, 2009 2 commits
  17. 26 Oct, 2009 2 commits
  18. 09 Oct, 2009 1 commit
  19. 24 Sep, 2009 1 commit
  20. 18 Sep, 2009 10 commits