1. 13 Oct, 2011 1 commit
  2. 12 Oct, 2011 1 commit
    • Iustin Pop's avatar
      Rename filter and filter_ to qfilter · 2e5c33db
      Iustin Pop authored
      
      
      We currently use 'filter' as the OpCode, QueryRequest and RAPI field
      name for representing a query filter. However, since 'filter' is a
      built-in function, we actually have to use filter_ throughout the code
      in order to not override the built-in function.
      
      This patch simply goes and does a global sed over the code. Due to the
      fact that the RAPI interface already exposed this field, we add
      compatibility code for now which handles both forms.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      2e5c33db
  3. 05 Oct, 2011 2 commits
  4. 30 Sep, 2011 2 commits
  5. 16 Sep, 2011 1 commit
  6. 30 Aug, 2011 1 commit
  7. 25 Aug, 2011 1 commit
  8. 24 Aug, 2011 1 commit
  9. 12 Aug, 2011 6 commits
  10. 11 Aug, 2011 1 commit
  11. 05 Aug, 2011 1 commit
  12. 04 Aug, 2011 1 commit
  13. 03 Aug, 2011 2 commits
  14. 26 Jul, 2011 2 commits
  15. 22 Jul, 2011 1 commit
  16. 21 Jul, 2011 2 commits
  17. 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,
      doc/design-chained-jobs.rst.
      
      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>
      b95479a5
  18. 14 Jul, 2011 1 commit
  19. 11 Jul, 2011 1 commit
  20. 08 Jul, 2011 1 commit
  21. 05 Jul, 2011 2 commits
  22. 15 Jun, 2011 1 commit
  23. 01 Jun, 2011 1 commit
  24. 31 May, 2011 1 commit
  25. 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>
      f8fa4175
  26. 20 May, 2011 1 commit
  27. 16 May, 2011 2 commits
  28. 12 May, 2011 1 commit