1. 29 Jan, 2009 1 commit
    • Leigh B. Stoller's avatar
      Add two calls to CM interface; SliverStatus() and SliceStatus() which · 85ea76eb
      Leigh B. Stoller authored
      allow you to find out the status of your sliver. As you can guess, one
      takes a sliver credential and the other takes the slice credential.
      See the test scripts test/slicestatus.py and test/slicestatus.py. Both
      calls return the same thing. In pythonese:
      
      {'status': 'notready',
       'details': {'de9803c2-773e-102b-8eb4-001143e453fe': 'notready'}
      }
      
      The 'status' is a summary of the entire aggregate; if all nodes are
      ISUP then the status is 'ready'
      
      The details is an array of the status of each sliver, indexed by the
      sliver uuid.
      
      Probably need to define a better set of status indicators, but this is
      the one that was bothering me the most.
      85ea76eb
  2. 23 Jan, 2009 1 commit
  3. 03 Dec, 2008 1 commit
  4. 04 Nov, 2008 1 commit
  5. 27 Oct, 2008 1 commit
  6. 16 Oct, 2008 1 commit
  7. 02 Oct, 2008 1 commit
  8. 25 Sep, 2008 1 commit
  9. 18 Sep, 2008 1 commit
  10. 13 Sep, 2008 1 commit
  11. 03 Sep, 2008 1 commit
  12. 14 Aug, 2008 1 commit
  13. 12 Aug, 2008 1 commit
  14. 20 Jun, 2008 1 commit
  15. 17 Jun, 2008 1 commit
  16. 03 Jun, 2008 1 commit
  17. 30 May, 2008 1 commit