Difference between revisions of "EGI-InSPIRE:Plan 2014 SA1.4"
Jump to navigation
Jump to search
Line 21: | Line 21: | ||
===Milestones not accomplished=== <!-- list here milestones that were not completed according to the envisaged schedule, saying why they were not completed, and the new schedule is --> | ===Milestones not accomplished=== <!-- list here milestones that were not completed according to the envisaged schedule, saying why they were not completed, and the new schedule is --> | ||
* MSG: security implementation | |||
** Full security implementation was not achieved. | |||
** APEL SSM2 clients were developed in a way to use authentication. Broker network extension for authorization of APEL clients based on GOCDB data was developed. | |||
** SAM clients are still using unauthenticated connections. | |||
** Full security implementation has to be synchronized with the plans for future SAM developments in PY5 | |||
* Operations portal: Availabilities and reliabilities report system | * Operations portal: Availabilities and reliabilities report system | ||
** A new availabilities/reliabilities reporting system was developed. Release was postponed due to the work on the miniproject "A new approach to Computing A/R Reports". | ** A new availabilities/reliabilities reporting system was developed. Release was postponed due to the work on the miniproject "A new approach to Computing A/R Reports". | ||
** The new system is part of the released planned for the Q1/2014 | |||
* Operations portal: Improvement of sam-MSG-ops portal synchronization | * Operations portal: Improvement of sam-MSG-ops portal synchronization | ||
** Development of better synchronization of Operations Portal with SAM was done, but release was postponed due to the work on the miniproject. | ** Development of better synchronization of Operations Portal with SAM was done, but release was postponed due to the work on the miniproject. | ||
** The new synchronization is part of the released planned for the Q1/2014 | |||
== Plans for 2014 == | == Plans for 2014 == |
Revision as of 19:36, 30 December 2013
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 |
Assessment of progress in 2013
Completed Activities and Milestones
- MSG: Enhance monitoring tools for PROD MSG network
- CERN team implemented detailed monitoring of queues used by known clients.
- Operations portal: Refactoring dashboards
- To increase the efficiency and the maintainability of the different dashboards (security dashboard, VO Dashboard, Operations Dashboard) the code was currently reviewed and improved.
- GOCDB version 5
- GOCDB v5 was released on October 2nd 2013. The new version introduced more non-exclusive scope tags for hosting multiple projects in the same instance. The existing scope PI parameter will support a comma-separated list of scope values rather than exclusive EGI or Local scope values. In addition the new version uses the Doctrine ORM which enables support of RDBMSs other than Oracle.
- SAM: Integration of EMI probes
- SAM Update-22 released on October 28th 2013 contained EMI probes. This release requires full reinstallation of SAM instance because upgrade from gLite UI to EMI-2 is not supported. Several SAM tests were renamed which required special By the end of the year 16 SAM instances were upgraded to Update-22.
- GOCDB: Automatic DNS switching to failover instance
- First version of automatic switching was deployed in December 2013.
Milestones not accomplished
- MSG: security implementation
- Full security implementation was not achieved.
- APEL SSM2 clients were developed in a way to use authentication. Broker network extension for authorization of APEL clients based on GOCDB data was developed.
- SAM clients are still using unauthenticated connections.
- Full security implementation has to be synchronized with the plans for future SAM developments in PY5
- Operations portal: Availabilities and reliabilities report system
- A new availabilities/reliabilities reporting system was developed. Release was postponed due to the work on the miniproject "A new approach to Computing A/R Reports".
- The new system is part of the released planned for the Q1/2014
- Operations portal: Improvement of sam-MSG-ops portal synchronization
- Development of better synchronization of Operations Portal with SAM was done, but release was postponed due to the work on the miniproject.
- The new synchronization is part of the released planned for the Q1/2014