1. 13 Nov, 2009 3 commits
  2. 12 Nov, 2009 2 commits
  3. 11 Nov, 2009 5 commits
  4. 10 Nov, 2009 1 commit
  5. 06 Nov, 2009 17 commits
  6. 05 Nov, 2009 6 commits
  7. 04 Nov, 2009 6 commits
    • Iustin Pop's avatar
      Migration: add check for listening target · 50716be0
      Iustin Pop authored
      
      
      This patch adds a check for listening on the remote port in Xen and KVM
      migrations. This will be generating a single “load of migration failed”
      message for KVM, but otherwise not prevent the migration. For Xen (which
      has a dedicated, always listening daemon) this should not create any
      problems.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      50716be0
    • Iustin Pop's avatar
      TLMigrateInstance: add error messagess during Exec · 78212a5d
      Iustin Pop authored
      
      
      Currently the migration of an instance doesn't show any error until the
      end. We add two messages that show better the progress:
      
      node1# gnt-instance migrate -f instance5
      Wed Nov  4 04:04:34 2009 Migrating instance instance5
      Wed Nov  4 04:04:34 2009 * checking disk consistency between source and target
      Wed Nov  4 04:04:35 2009 * switching node node3 to secondary mode
      Wed Nov  4 04:04:35 2009 * changing into standalone mode
      Wed Nov  4 04:04:35 2009 * changing disks into dual-master mode
      Wed Nov  4 04:04:40 2009 * wait until resync is done
      Wed Nov  4 04:04:41 2009 * preparing node3 to accept the instance
      Wed Nov  4 04:04:41 2009 * migrating instance to node3
      Wed Nov  4 04:04:51 2009 Migration failed, aborting
      Wed Nov  4 04:04:51 2009 * switching node node3 to secondary mode
      Wed Nov  4 04:04:51 2009 * changing into standalone mode
      Wed Nov  4 04:04:51 2009 * changing disks into single-master mode
      Wed Nov  4 04:04:57 2009 * wait until resync is done
      Failure: command execution error:
      Could not migrate instance instance5: Failed to migrate instance: Failed
      to migrate instance instance5: …
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      78212a5d
    • Iustin Pop's avatar
      hypervisors: switch to using HV_MIGRATION_PORT · 641ae041
      Iustin Pop authored
      
      
      This changes KVM to use HV_MIGRATION_PORT instead of KVM_MIGRATION_PORT
      and enables passing the port for Xen migrations.
      
      Since KVM_MIGRATION_PORT is not used anymore, we stop exporting it from
      constants.py.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      641ae041
    • Iustin Pop's avatar
      Introduce HV_MIGRATION_PORT hypervisor parameter · 78411c60
      Iustin Pop authored
      
      
      This parameter will replace the direct use of KVM_MIGRATION_PORT and the
      implicit use of the Xen migration port.
      
      While it doesn't make sense to change this at instance level, we don't
      have any other infrastructure for cluster-wide hypervisor parameters, so
      we add it here (and document that it usually shouldn't be changed on a
      per-instance basis).
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      78411c60
    • Iustin Pop's avatar
      hypervisors: change MigrateInstance API · 58d38b02
      Iustin Pop authored
      
      
      Currently the $hypervisor.MigrateInstance takes the instance name. This
      patch changes it to take the instance object, such that other instance
      properties (especially hvparams) are available to it.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      58d38b02
    • Iustin Pop's avatar
      Revert the instance IP conflicts · 9b65e0d4
      Iustin Pop authored
      
      
      Since instances can live in different VLANs from nodes (especially in
      routed mode), based on the 'link' parameter, we shouldn't always
      restrict having duplicate IPs. Thus we only check the node IPs/cluster
      IP for now.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      9b65e0d4