1. 01 Nov, 2010 1 commit
  2. 28 Oct, 2010 3 commits
  3. 27 Oct, 2010 3 commits
  4. 26 Oct, 2010 1 commit
    • Iustin Pop's avatar
      Rename node.nodegroup to node.group · f936c153
      Iustin Pop authored
      
      
      In the context of a node, its group has (at least today) only one
      meaning, that is the node's node group. As such, we rename
      node.nodegroup to just node.group.
      
      Note: if we want to keep node in there, it should be at least
      node_group, for consistency with the other node attributes.
      
      Similarly, we rename the OpAddNode nodegroup attribute to group.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      f936c153
  5. 20 Sep, 2010 1 commit
  6. 14 Sep, 2010 1 commit
  7. 02 Sep, 2010 1 commit
  8. 25 Aug, 2010 1 commit
  9. 23 Aug, 2010 1 commit
  10. 19 Aug, 2010 3 commits
  11. 18 Aug, 2010 1 commit
  12. 23 Jul, 2010 2 commits
  13. 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
  14. 09 Jul, 2010 1 commit
  15. 08 Jul, 2010 1 commit
  16. 01 Jun, 2010 2 commits
  17. 25 May, 2010 1 commit
  18. 23 Mar, 2010 1 commit
  19. 09 Mar, 2010 1 commit
  20. 08 Mar, 2010 1 commit
  21. 22 Feb, 2010 1 commit
  22. 11 Feb, 2010 2 commits
  23. 04 Jan, 2010 4 commits
  24. 25 Nov, 2009 2 commits
  25. 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
  26. 02 Nov, 2009 2 commits