| 14 | | A meeting of the project teams associated with the ProtoGENI cluster. This meeting is primarily targeted to developers of aggregates, tools and other software that integrate with the ProtoGENI control framework. |
| | 14 | A meeting of the project teams associated with the ProtoGENI cluster. This meeting is primarily targeted to developers of aggregates, tools and other software that integrate with the ProtoGENI control framework. The meeting will be run as an informal discussion. Topics of conversation will include: |
| | 15 | |
| | 16 | |
| | 17 | * Services for cross-aggregate slices - currently, each aggregate sets |
| | 18 | up IP addresses, routes, hosts files, etc. for the slivers in that |
| | 19 | aggregate. However, it doesn't include slivers that live on other |
| | 20 | aggregates. This means, for example, that users must set up |
| | 21 | cross-aggregate routes themselves. I think it's time we considered |
| | 22 | running things like routing daemons, nameservers, etc. to make |
| | 23 | cross-aggregate slices work together better. Obviously, these sorts of |
| | 24 | multi-domain problems have been dealt with in the Internet, giving us |
| | 25 | things like OSPF, BGP, and the DNS. But what form should this take in |
| | 26 | ProtoGENI? Which services should we provide, and which (hopefully |
| | 27 | existing, not new) tools should we use to provide them? |
| | 28 | |
| | 29 | * Certificate format update |
| | 30 | |
| | 31 | * Other topics that have come up at the GEC - I'm sure that many of the |
| | 32 | software-track sessions will raise issues that we need to decide how to |
| | 33 | handle in our control framework. We'll use some of our cluster meeting |
| | 34 | time to talk about these. |
