The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Agenda-28-03-2011"
| Line 5: | Line 5: | ||
=== 1. Middleware releases and staged rollout (Mario)=== | === 1. Middleware releases and staged rollout (Mario)=== | ||
====1.1. Update on the status of EMI-1 | ====1.1. Update on the status of EMI-1 release (Cristina)==== | ||
====1.2. Middleware release==== | ====1.2. Middleware release==== | ||
Revision as of 15:45, 23 March 2011
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Detailed agenda: Grid Operations Meeting 28 March 2011
1. Middleware releases and staged rollout (Mario)
1.1. Update on the status of EMI-1 release (Cristina)
1.2. Middleware release
1.3. Staged Rollout
2. Operational Issues
2.1. CREAM deployement model with gLite-CLUSTER
At the Feb 15 OMB meeting the OMB agreed to ask EMI for support of gLite-CLUSTER. This requirement has been subsequently discussed at the TCB, and EMI has positively replied to this request. In particular:
- gLite-CLUSTER will be part of EMI 1.0
- CREAM in EMI will come with glite-CLUSTER
- The CREAM team will support the glite-CLUSTER components in EMI
- CERN will support the glite-CLUSTER component in gLite
The proposal of the CREAM product team is to have a unique deployment model with the gLite-CLUSTER mandatory for every CREAM installation. The motivation of this proposal is to have a single simpler deployment model (with single yaim variables to publish a given GLUE attribute).
Feedback needed on this proposal