TSCG meeting
→
Europe/Paris
Description
Telephone: +33 1 56 78 86 88 (normal Standup number)
Slides from previous meetings.
Attendees:
C. Loomis (CNRS, WP2)
D. O'Callaghan (TCD, WP3)
M-E Bégin (SixSq, WP4)
V. Floros (GRNET, WP5)
H. Muñoz (TID, WP6)
J. Fontan (UCM)
1) Schedule for Fall 2011
A F2F meeting needs to be scheduled for sometime this fall. Cal will send out a doodle to find possible time periods.
The draft sprint schedule was agreed. Everyone should block those dates in their calendar, although they are still subject to change. Known dates that may change are: 1) end date of Sprint 17 (could be 15 or 16) and 2) start date of Sprint 18 (may be a day later to allow a TSCG before).
Releases are currently planned for the ends of Sprints 17 and 19; releases 1.1 and 1.2, respectively.
2) Priorities for Upcoming Sprints
The priority for Sprint 17 is the preparation for the EGI Technical Forum, including the 1.1 release for that event. The planning meeting will work out the details for the preparations of talks, posters, and the booth.
Priorities for each work package:
WP2: Demonstrating working use cases and having a complete tutorial for the TF.
WP3: Preparations of the TF. For the Marketplace, the workflow around image deprecation should be streamlined.
WP4: Ensure clean stable build with the 1.1 release. Desire to make initial contacts for commerial exploitation of StratusLab results.
WP5: Add epic for testing & benchmarks of system. Integration of caching mechanisms in distribution; NFS integration with persistent disk. Continuing shared file system tests.
WP6: Fixing Claudia bugs for release. Looking at authn to see if this can be done for 1.1 release to allow public deployment of Claudia. Afterwards work on scalability.
OpenNebula: Work on converging 3.0 with the StratusLab release. Code will not be brought into StratusLab until after the 1.1 release.
3) Architecture
There was lots of discussion around the diagrams needed for the architecture document. Meb will use that feedback to draft new versions. Further discussion will take place on the mailing list. The document itself will consist of one page per service in addition to the overall diagrams. Meb will distribute the template to be filled in by the service developers.
4) AOB
None.
C. Loomis (CNRS, WP2)
D. O'Callaghan (TCD, WP3)
M-E Bégin (SixSq, WP4)
V. Floros (GRNET, WP5)
H. Muñoz (TID, WP6)
J. Fontan (UCM)
1) Schedule for Fall 2011
A F2F meeting needs to be scheduled for sometime this fall. Cal will send out a doodle to find possible time periods.
The draft sprint schedule was agreed. Everyone should block those dates in their calendar, although they are still subject to change. Known dates that may change are: 1) end date of Sprint 17 (could be 15 or 16) and 2) start date of Sprint 18 (may be a day later to allow a TSCG before).
Releases are currently planned for the ends of Sprints 17 and 19; releases 1.1 and 1.2, respectively.
2) Priorities for Upcoming Sprints
The priority for Sprint 17 is the preparation for the EGI Technical Forum, including the 1.1 release for that event. The planning meeting will work out the details for the preparations of talks, posters, and the booth.
Priorities for each work package:
WP2: Demonstrating working use cases and having a complete tutorial for the TF.
WP3: Preparations of the TF. For the Marketplace, the workflow around image deprecation should be streamlined.
WP4: Ensure clean stable build with the 1.1 release. Desire to make initial contacts for commerial exploitation of StratusLab results.
WP5: Add epic for testing & benchmarks of system. Integration of caching mechanisms in distribution; NFS integration with persistent disk. Continuing shared file system tests.
WP6: Fixing Claudia bugs for release. Looking at authn to see if this can be done for 1.1 release to allow public deployment of Claudia. Afterwards work on scalability.
OpenNebula: Work on converging 3.0 with the StratusLab release. Code will not be brought into StratusLab until after the 1.1 release.
3) Architecture
There was lots of discussion around the diagrams needed for the architecture document. Meb will use that feedback to draft new versions. Further discussion will take place on the mailing list. The document itself will consist of one page per service in addition to the overall diagrams. Meb will distribute the template to be filled in by the service developers.
4) AOB
None.
Il y a un compte-rendu associé à cet événement.
Les afficher.