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-07-11-2011"
| Line 35: | Line 35: | ||
* UNICORE cli | * UNICORE cli | ||
* SAGA SD API/CLI | * SAGA SD API/CLI | ||
* ''EMI Registry client'' - design not final, yet | * ''EMI Registry client'' - ''design not final, yet'' | ||
The questions ''could'' be: | The questions ''could'' be: | ||
* Which of the clients above are used in the activities | * Which of the clients above are used in the activities of your NGI? | ||
** Both operational activities, and user support | |||
* Which features are important in a info system client? | |||
* Which features should the EMIR client include, to be useful? | |||
** The added value would be to discover resources from different middleware stacks | |||
** EMIR will not contain VO information about the services, should the client provide the resource-VO match, like lcg-info*? | |||
== 3. AOB == | == 3. AOB == | ||
Revision as of 12:20, 4 November 2011
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Detailed agenda: Grid Operations Meeting 24 October 2011 14h00 Amsterdam time
| EVO direct link | Pwd: gridops |
| EVO details | Indico page |
1. Middleware releases and staged rollout
1.1 EMI-1 release status
1.2 Staged Rollout (Mario)
1.2.1 gLite 3.2
1.2.2 UMD1
2. Operational Issues
2.1 Usage of the information system clients
The EMI Registry is the common service discovery system designed during this year by EMI, scheduled to be implemented by EMI-2 and adopted by all EMI products by EMI-3. EMI Registry Twiki page.
Consolidation is the EMI task that aims to reduce the maintenance costs of the software, for example by reducing the number of components and duplicates. EMI has not yet planned a consolidation strategy for the information system clients. EMI explicitly asked for feedback about the usage of the current info-sys clients. They would like to harmonize this area, and they want to choose the direction to go based on the EGI and user communities feedback.
The clients are:
- lcg-info*
- ARC lib
- UNICORE cli
- SAGA SD API/CLI
- EMI Registry client - design not final, yet
The questions could be:
- Which of the clients above are used in the activities of your NGI?
- Both operational activities, and user support
- Which features are important in a info system client?
- Which features should the EMIR client include, to be useful?
- The added value would be to discover resources from different middleware stacks
- EMIR will not contain VO information about the services, should the client provide the resource-VO match, like lcg-info*?
3. AOB
3.1 Next meetings
21 November 2011 h 14:00