| 51 | |
| 52 | == Session Summary == |
| 53 | At the Miscellaneous Developer Topics Session, we heard from Aaron |
| 54 | Helsinger and Tom Mitchell on the status of several efforts, and then |
| 55 | had an open discussion on things that tool developers would like to |
| 56 | see from aggregates and clearinghouses. |
| 57 | |
| 58 | Aaron presented the status of the Aggregate Manager API v3 implementation, with a plea for more progress from aggregate developers, particularly to support Update(). He also presented the status of RSpecs and Omni. |
| 59 | |
| 60 | Tom Mitchell discussed how to integrate tools into the larger GENI infrastructure, particularly through the use of OpenID for Single Sign On. |
| 61 | |
| 62 | Marshall Brinn introduced the question of what support tool developers would |
| 63 | like from aggregates and clearinghouses in order to support GENI |
| 64 | experimenters. We then had an open discussion, where several requests |
| 65 | and suggestions were made. |
| 66 | |
| 67 | In general, tools would like a way to know when something changes in a |
| 68 | slice - the slivers in the slice, expiration times, etc. A callback |
| 69 | function was suggested instead of requiring polling. Alternatively, |
| 70 | GENI could identify the authoritative source(s) of all kinds of |
| 71 | information and ensure those sources have API methods for querying |
| 72 | state. |
| 73 | |
| 74 | Other requests included: |
| 75 | - Common libraries, particularly for handling authentication and authorization in GENI |
| 76 | - Standards among tools, for things like how long to cache state |
| 77 | - Improved documentation |
| 78 | |