1. 18 Jan, 2011 14 commits
  2. 12 Jan, 2011 1 commit
  3. 07 Jan, 2011 3 commits
  4. 06 Jan, 2011 1 commit
  5. 14 Dec, 2010 1 commit
  6. 01 Nov, 2010 1 commit
  7. 27 Oct, 2010 1 commit
  8. 21 Oct, 2010 1 commit
  9. 20 Oct, 2010 1 commit
  10. 30 Sep, 2010 1 commit
    • Iustin Pop's avatar
      Change behaviour of OpDiagnoseOS w.r.t. 'valid' · d22dfef7
      Iustin Pop authored
      
      
      This patch changes the behaviour of OpDiagnoseOS with regards to the
      'valid' field to be similar to the one for the hidden/blacklisted
      fields: unless this field is requested, invalid OSes are filtered out.
      
      The rationale is that, except for the gnt-os info/diagnose, all other
      users of this opcode are requesting the valid field just to filter out
      invalid OSes, and not for any other use. Thus, changing this behaviour
      makes these callers simpler.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      d22dfef7
  11. 21 Sep, 2010 1 commit
  12. 20 Sep, 2010 1 commit
  13. 23 Aug, 2010 1 commit
  14. 19 Aug, 2010 2 commits
  15. 18 Aug, 2010 1 commit
    • Manuel Franceschini's avatar
      Introduce new IPAddress classes · 8b312c1d
      Manuel Franceschini authored
      
      
      This patch unifies the netutils functions dealing with IP addresses to
      three classes:
      - IPAddress: Common IP address functionality
      - IPv4Address: IPv4 specific functionality
      - IPv6address: IPv6-specific functionality
      
      Furthermore it adds methods to check whether an address is a loopback
      address, replacing the .startswith("127") for IPv4 and adding IPv6
      support.
      
      It also provides the basis for future IPv6 address handling. Methods to
      convert IP strings to their corresponding interger values will allow to
      canonicalize IPv6 addresses.
      Signed-off-by: default avatarManuel Franceschini <livewire@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      8b312c1d
  16. 29 Jul, 2010 1 commit
    • Iustin Pop's avatar
      Change semantics of --force-multi for reinstall · 297ddce9
      Iustin Pop authored
      
      
      Currently, we require both --force and --force-multiple for skipping the
      confirmation on instance reinstalls. After offline conversations, this
      has been deemed to be excessive, and this patch changes the meaning of
      --force-multiple to be a “stronger” force, and not require both.
      
      So, to skip the prompts:
      - single instance reinstallation requires either --force or
        --force-multiple
      - multiple instance reinstallation requires --force-multiple
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      297ddce9
  17. 28 Jul, 2010 2 commits
  18. 23 Jul, 2010 2 commits
  19. 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
  20. 09 Jul, 2010 1 commit
  21. 08 Jul, 2010 1 commit
  22. 06 Jul, 2010 1 commit
    • Iustin Pop's avatar
      gnt-instance: fix GenericManyOps · b4e68848
      Iustin Pop authored
      
      
      Currently, GenericManyOps ignores the actual success or failure results
      from the invididual jobs. We change this to return '0' (i.e. success)
      only when all jobs failed, as many times we have just one job.
      
      Together with the JobExecutor change, this will report failures
      correctly when used with a drained queue and submit only, or when used
      normally and the opcode actually fails.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      b4e68848