EGI-InSPIRE:Sa1 2013-05-07
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Inspire reports menu: | Home • | SA1 weekly Reports • | SA1 Task QR Reports • | NGI QR Reports • | NGI QR User support Reports |
Progress of SA1 issues
Nothing new to report.
Milestones/Deliverables
- D4.8 Annual assessment of infrastructure: completed the first round of external review (all comments received addressed)
- MS425 OLAs: external review in progress
SA1.1 Activity Management
MEETINGS
- FedSM meeting and implementation plan for improvement of EGI.eu core services
- resource allocation framework and kickoff meeting of resource allocation mini project
- first URT meeting: organization and setup of support structures
ACTIVITIES
- assessment of accounting readiness for sites deploying ARC (SGAS and JURA which was reported to have problems with the publishing of accounting records to APEL. In progress
- contribution to VERCE MoU
- assessment of VO availability prototype
- editing of D4.8 to incorporate external reviews
- editing of MS425
- assessment of PY3 metrics in the operations portal (in progress) and collection of PQ4 metrics (in progress)
SA1.2 Security
SA1.3 Staged rollout
SA1.3 Integration
- preparation of EGI/EUDAT/PRACE weekly meeting. Contact with NGI UK and PL for support of MAPPER nano material use case
- contact with BIOMED/VPH for the appointment of two test sites, for testing of data transfer to/from EUDAT
- DRIHM: collection of requirements and discussion of setup of VOMS service
SA1.4 Central tools
- Preparation of QR12
- Deployment of new glue-validator on test instance: https://vcl-1-1.srce.hr/nagios
- Participation in new EMI probes SAM testing
- Providing SAM feedback to FedCloud work group
SA1.5 Accounting
Repository The SSM 2 central repository is in production and we now have our first production client, data is being published using the EMI 3 APEL client from UKI-LT2-QMUL. Chris Walker from QMUL has also produced a report on the process and a new version of the EMI 3 APEL Client has been released today which fixed some bugs found in the initial release. This is EMI 3 Update 3, which we would like to be included in the UMD 3 release if possible.
We have another site who we expect to be publishing in production in the next few days (UA-KNU); they have carried out successful tests and we are just negotiating which month they should start publishing to the new system from.
APEL repositories are ready for a production level usage of SSM2. A site MUST migrate all their accounting clients to UMD-3 (SSM2), there can't be an hybrid situation. CREAM from UMD-2 with APEL from UMD-3 can work. It's theoretically possible also the other way around: CREAM-3 with APEL from UMD-2. This was not tested by APEL (but Enol did some preliminary tests). The manual documenting the transition from EMI-2 APEL to EMI-3 is under preparation. The new APEL clients are now in the UMD repositories, under verification.
Portal
No report received
SA1.6 Helpdesk
- Ticket monitoring
- Preparation of the following GGUS release
- Cleaning up support units after end of EMI project
- Defining new structure of PTs