Alert.png 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.

Agenda-28-03-2011

From EGIWiki
Revision as of 12:53, 25 March 2011 by David (talk | contribs)
Jump to navigation Jump to search
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:

  1. gLite-CLUSTER will be part of EMI 1.0
  2. CREAM in EMI will come with glite-CLUSTER
  3. The CREAM team will support the glite-CLUSTER components in EMI
  4. 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

2.2 DPM in glite 3.1 (Mario)

The only EA doing the test of DPM 1.8.0 in gLite 3.1, has successfully deployed the voms-api with the memory leak fixed. Waiting for the staged rollout report, and a proposal will be to release this version with the advisory to install aposteriori the fixed voms-api packages.

2.3 Bring ARC, Unicore and globus to this meeting (Mario)

For ARC some people (sites) are already represented, we would like that they also report about issues they have, and about interoperability in the infrastructure.

For UNICORE and Globus, NGI's should invite their sites to the meeting, and make themselves known, and what they expect to be integrated into the infrastructure, or what sites (NGI's) expect to deploy these MW stacks.

2.4 Publishing the MW version in the information system (Mario)

Recent discussion within EMI with participation of EGI TSA1.3, about how and what should be published in the information system with respect to the MW stack, version , service and service version.

The discussion has been concentrated in the GLUE2 schema, but there may be also some resolution for GLUE1.3

EMI will decide the technical implementation, on our side the following proposal will be presented to EMI. The proposal will be to use the GLUE2Entity = Endpoint

GLUE2 Attribute Comment