Difference between revisions of "EGI-InSPIRE:SA1.8-QR11"
(→2. Main Achievements)
(→3. Issues and Mitigation)
|Line 82:||Line 82:|
! scope="col" | Mitigation Description
! scope="col" | Mitigation Description
Revision as of 09:18, 15 February 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|
1. Task Meetings
|Date (dd/mm/yyyy)||Url Indico Agenda||Title||Outcome|
2. Main Achievements
Last quarter Documentation task was focused on four areas: EGI wiki, procedures, EGI discussion forum and documentation creation.
EGI operations wiki space has been reorganized and new menus have been introduced to better find needed information. Unnecessary pages were removed or marked as deprecated. For EGI Operations newcomers, site administrators and end-users have been created pagers which gather all existing information useful for their daily work. In addition Documentation task is working on EGI User start guide to provide documentation how to use infrastructure and Regional User Documentation which collects links to end-user documentation provided by NGIs. For EGI Wiki users a wiki guide has been created for better use of this tool.
EGI discussion forum
Documentation task is coordinating and maintaining EGI discussion forum tool. Two new sub forums have been introduced for our community: Site administrator support, NGI administrator support. Both of them are moderated by Grid oversight activity and are supposed to be a place where inexperienced NGIs and site administrators can find support.
During quarter 11 Availability and reliability monthly statistics page was reviewed and split into two pages: PROC04 Quality verification of monthly availability and reliability statistics (procedure) and Availability and reliability monthly statistics (reports). New procedure has been created PROC16 Unsupported software version decommission and introduced on OMB meeting and finely approved. To support Proc16 new escalation process has been created as well: Escalation for operational problem with unsupported MW at site.
Documentation task took part in creation of EGI OLA and EGI service proftolio documents. EGI OLA has been approved by OMB in December.
Within quarter 11 availability reporting was performed as usual on a monthly basis. Publication of results and re-computation requests regarding A/R results were handled by the SLM unit via GGUS.
Catch all services and core grid services
The migration of dteam VO from VOMRS to VOMS has been extensively discussed within quarter 11. The primary issue that withheld the mitigation was related to how the latest available VOMS-Admin interface handles its notification policy. At the end of the quarter it was decided to postpone the migration until EMI-3 VOMS is released. The features needed for dteam VO in specific have been included within the current development roadmap.
EGI Catch all CA
Within quarter 11 the CP/CPS of the EGI Catch all CA has been updated and approved by IGTF.
One new Registration Authority was initialized in South African Astronomical Observatory (SAAO).
Core services for site certification
The site certification infrastructure was timely maintained within quarter 11. In specific, and due to several Ruby on Rails vulnerabilities that were disclosed within security contacts, several patches and upgrades have been performed in order to ensure the infrastructure is not exposed to security threats. An update of the distinct components (Top-BDII, WMS etc) is planned for the upcoming period.
During quarter 11 a new dedicated SAM instance for monitoring of running middleware versions on sites was deployed. Results from this instance are reported on the Operations Dashboard where NGIs can monitor the progress of sites in updating old and not supported software/middleware versions.
3. Issues and Mitigation
|Issue Description||Mitigation Description|
|Migration of dteam VO from VOMRS to VOMS interface. The migration was withholded for the time being as VOMS cannot handle notifications sent to VO admin roles in a similar fashion to VOMRS.||The needs for dteam VO have been discussed with the development team and several issues identified have been included in the current development roadmap towards EMI-3 version of VOMS. Once this is released the migration of dteam VO should follow.|
4. Plans for the next period
Plans for Documentation Task for next quarter is to finalize end-users' and site administrators' wiki space. Middleware wiki space needs requires reorganization, improvements and integration with site administrators' wiki space. RC OLA and RP OLA are planed to be reviewed.