| 90 | | Document updated to reflect dsicussion of meeting, including rating (H, M, L) of each task for importance, at [http://groups.geni.net/geni/attachment/wiki/ClusterDMtg070209/070209d%20ClusterD_Spiral2_Goals_Roadmap.doc "Cluster D Spiral 2 Roadmap" document] |
| | 90 | After discussion at this meeting, including rating (H, M, L) of each task for importance, see updated [http://groups.geni.net/geni/attachment/wiki/ClusterDMtg070209/070209d%20ClusterD_Spiral2_Goals_Roadmap.doc document] [[BR]] |
| | 91 | [http://groups.geni.net/geni/attachment/wiki/ClusterDMtg070209/cluster-D-review-notes-2July09.txt Notes], particularly concerning: techniques for monitoring; identity management. [[BR]] |
| 95 | | - Experiments: Want to see experiments of end-to-end systems, e.g., matching networks with servers, sensors with clouds, content with buses, radars & buses |
| 96 | | |
| 97 | | - Identity management: DOME plans to plug into some foreign authentication manager. GPO plans to try to go to Shib & InCommon, since it looks like it might take hold broadly. Rough mental model |
| 98 | | is that in the early days, almost anybody can use this. Need ways to say 'these people are out' but probably don't need elaborate policies early on. GPO is interested in knowing whether folks believe moving to Shibboleth is a bad idea. Shib has been most successful for managing user access to a portal, seems good for GENI as far as that goes and that's what ORCA uses it for. What that user is allowed to do is another issue and not currently handled by Shib attributes. Shib is only starting to handle delegated authority, still early days. |
| 99 | | |
| 100 | | - Improved integration. |
| 101 | | |
| 102 | | - Need to improve distribution of keys to containers. Currently manual, ugly, error prone, requires documentation but will work until container reaches 10's. Currently no privacy. Could be added by using HTTPS on transport. |
| 103 | | |
| 104 | | - Measurements |
| 105 | | |
| 106 | | - DOME collects location information on buses but needs a solution on providing it to GENI users. Has also been thinking about longitudinal studies, Brian will send Chip a copy of a paper. |
| 107 | | |
| 108 | | - ERTM will prototype hardware, interface it with BEN, integrate with ORCA. |
| 109 | | |
| 110 | | - Interoperability. Want to avoid CF balkanization. |
| 111 | | |
| 112 | | 4:00 Adjourn |
| | 95 | Submitted by: Harry Mussman, GPO System Engineer[[BR]] |
| | 96 | |
