1. 26 Jul, 2011 1 commit
  2. 22 Jul, 2011 1 commit
  3. 21 Jul, 2011 2 commits
  4. 20 Jul, 2011 1 commit
    • Michael Hanselmann's avatar
      Implement chained jobs · b95479a5
      Michael Hanselmann authored
      An overview is available in the design document for this change,
      When a job enters the job processor, the current opcode's dependencies
      are evaluated. If a referenced job has not yet reached the desired
      status, the current job is registered as a dependant. The job processor
      will continue to work on other pending tasks. When a job finishes it
      notifies any pending dependants by re-adding them to the workerpool.
      A per-job processor lock is necessary for rare cases where the same job
      can be re-added twice.
      There is no way to view waiting jobs at the moment, but I plan to
      export this information to “gnt-debug locks”.
      A so-called dependency manager takes care of managing waiting jobs and
      keeping track of their status.
      Unittests are included.
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
  5. 14 Jul, 2011 1 commit
  6. 11 Jul, 2011 1 commit
  7. 08 Jul, 2011 1 commit
  8. 05 Jul, 2011 2 commits
  9. 15 Jun, 2011 1 commit
  10. 01 Jun, 2011 1 commit
  11. 31 May, 2011 1 commit
  12. 25 May, 2011 1 commit
    • Michael Hanselmann's avatar
      Fix bug in LUNodeMigrate · f8fa4175
      Michael Hanselmann authored
      Commit aac4511a
       added CheckArguments to LUNodeMigrate with a call to
      _CheckIAllocatorOrNode. When no default iallocator is defined,
      evacuating a node would always fail:
      $ gnt-node migrate node123
      Migrate instance(s) '...'?
      y/[n]/?: y
      Failure: prerequisites not met for this operation:
      No iallocator or node given and no cluster-wide default iallocator
      found; please specify either an iallocator or a node, or set a
      cluster-wide default iallocator
      This patch adds a new parameter to specify a target node. This doesn't
      solve all issues, but will make the most important cases work again in
      the meantime. This opcode will receive more work for node group support.
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
  13. 20 May, 2011 1 commit
  14. 16 May, 2011 2 commits
  15. 12 May, 2011 3 commits
  16. 09 May, 2011 3 commits
  17. 18 Apr, 2011 1 commit
  18. 06 Apr, 2011 2 commits
    • Michael Hanselmann's avatar
      LUInstanceQueryData: Don't acquire locks unless requested · dae661a4
      Michael Hanselmann authored
      Until now LUInstanceQueryData always acquired locks for the instance(s)
      and nodes involved. In combination with long-running operations this
      prevented the use of “gnt-instance info”, even with the “--static”
      option. With this patch, locks are only acquired when explicitely
      requested in the opcode (like all query operations).
      Signed-off-by: default avatarMichael Hanselmann <hansmi@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
    • René Nussbaumer's avatar
      TLMigrateInstance: Merge failover code, allow fallback · d5cafd31
      René Nussbaumer authored
      As the code for failover for checking is almost identical it's an easy
      task to switch it over to the TLMigrateInstance. This allows us to
      fallback to failover if migrate fails prereq check for some reason.
      Please note that everything from LUInstanceFailover.Exec is taken over
      unchanged to TLMigrateInstance._ExecFailover, only with adaption to
      opcode fields and variable referencing, but not in logic. There still
      needs to go some effort into merging the logic with the migration (for
      example DRBD handling). But this should happen in a separate iteration.
      Signed-off-by: default avatarRené Nussbaumer <rn@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
  19. 25 Mar, 2011 1 commit
  20. 15 Mar, 2011 1 commit
  21. 11 Mar, 2011 1 commit
  22. 09 Mar, 2011 2 commits
  23. 08 Mar, 2011 1 commit
  24. 01 Mar, 2011 1 commit
    • Apollon Oikonomopoulos's avatar
      Core shared file storage support · 4b97f902
      Apollon Oikonomopoulos authored
      This patch introduces core file storage support, consisting of the following:
      A configure-time switch for enabling/disabling shared file storage
      support and controlling the shared file storage location:
      --with-shared-file-storage-dir=.  Shared file storage configuration is then
      available as _autoconf.ENABLE_SHARED_FILE_STORAGE and
      _autoconf.SHARED_FILE_STORAGE_DIR and there is a cluster-wide ssconf
      key named "shared_file_storage_dir" for changing the file location.
      A new disk template named "sharedfile" (DT_SHARED_FILE), using
      Auxiliary functions in lib/config.py to handle shared file storage.
      Signed-off-by: default avatarApollon Oikonomopoulos <apollon@noc.grnet.gr>
      [iustin@google.com: small style fixes]
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
  25. 16 Feb, 2011 1 commit
  26. 15 Feb, 2011 2 commits
  27. 04 Feb, 2011 3 commits
  28. 31 Jan, 2011 1 commit