2013 12 03

• Who: Matteo, Antons, Ole, Ashley, AndreM, Shantenu

• Agenda:

  • open TODOs
    • TODO OW: fix demo-2
    • TODO OW: reply to Mark/AndreM on API
    • DONE AM: look at scheduler re-enabling...
    • DONE AM: send mongodb / callback link to Ole again
  • updates from Ashley, Antons
  • THE DEMO.v2 / v3 -- coding progress in general
    • status v2
    • status / plans v3 * from last call: * notifications are not yet taken care of * everything else should be relatively straight forward (tm), as extension to existing functionality * is that still valid?
      • 2 agents on india, sierra
      • 10 bulks of 10 CUs each
      • schedule CUs
      • notifications for pilot, CU state changes
      • integrated performance measurement and reporting

• Notes:

  • no changes on current state
  • separate out API discussion from development, stick to agree API for time being
  • working dir problem...
    • needs to be explicitly settable
    • MT: env var support while setting would be useful
    • MS: not sure if WD has actually a useful meaning
    • AM: infrastructure specific solution, user needs at least inspection on what happens
    • MT: may need MW support to access data - that's life. Other systems may allow direct access
    • SJ: user experience needs to be stable
    • MS: Matteo's problem is to get data out, not to set the PWD
    • AM: inspection seems the Least Common Denominator
    • MT: setting is still difficult
    • AM: there is no single point of information, so there is no simple (or even complicated) solution
    • --> this is very difficult, we don't see a good solution right now
    • MT: should not discourage us from finding a satisfactory solution, even if a pragmatic one is ok at the moment.