Difference between revisions of "EGI-InSPIRE:Sa1 2013-05-28"

From EGIWiki
Jump to: navigation, search
(SA1.1 Activity Management)
(SA1.3 Integration)
Line 54: Line 54:
 
* attending ENVRI meeting (collaboration with EISCAT-3D)
 
* attending ENVRI meeting (collaboration with EISCAT-3D)
 
* work on cloud resources integration and certification
 
* work on cloud resources integration and certification
 +
* setup of DRIHM collaboration with the involvement of NGIs
  
 
=SA1.4 Central tools=  
 
=SA1.4 Central tools=  

Revision as of 18:44, 28 May 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


Progress of SA1 issues

PQ11: NGI operations sustainability: Various NGIs expressed interest in sharing operational services (as providers and/or consumers). A new survey with a detailed service portfolio will be produced to help NGIs in sharing operational effort in preparation to tthe end of EGI-inSPIRE in April 2014.

Milestones/Deliverables

  • MS425 Operational Level Agreements: completed first external review cycle, one request of clarification to one reviewer submitted, documented expected to by finalized on 28-05-2013
  • MS431 DMSU: first draft circulated

SA1.1 Activity Management

MEETINGS

  • UMD Release Team meeting: contribution and preparation of the agenda
  • OMB monthly meeting: preparation of contributions and of agenda
  • SAM Update 22 meeting: preparation of action plan for the deployment in production of this new major release when staged rollout will be successfully passed
  • participation to the ENVRI WP3 meeting

ACTIVITIES

  • organization of the DRIHM collaboration (user contacts, testbed and infrastructure providers)
  • review of SA1 metrics and strategic metrics and targets (D1.13), review of the document provided
  • review of all SA1 metrics (metrics portal, consistency with QR reports) and values in the metrics portal, submission of various bug fix requests, review of metrics portal project metrics
  • review of web site structure, provisioning of NGI operations contacts
  • definition of SHA-2 monitoring work plan
  • assessment of progress of EMI-1 campaign
  • council document on resource application and allocation
  • provisioning of content (SA1 plans) for the technical roadmap
  • approval of changes to the service operations security policy
  • definition of new EMI-1 StoRM support calendar with PT
  • handling of operations tickets and VO service tickets in GGUS
  • update of UMD membership list

SA1.2 Security

  • Handling the critical vulnerability CVE-2013-2094 (EGI-ADV-20130514). Tickets have been submitted to perceived vulnerable sites. We are currently ironing out some monitoring issues to reliably identify any remaining vulnerable sites
  • Monitoring changes made to monitor CVE-2013-2094
  • work on Emergency-Suspension Mini Project
  • Attended ENISA Securty Workshop Bucharest
  • Attended TF-CSIRT Meeting Bucharest
  • SVG: Three new vulnerabilities reported
  • Modified the Compromised certificate /emergency suspension document to address comments
  • Attended EGI OMB meeting

SA1.3 Staged rollout

SA1.3 Integration

  • attending ENVRI meeting (collaboration with EISCAT-3D)
  • work on cloud resources integration and certification
  • setup of DRIHM collaboration with the involvement of NGIs

SA1.4 Central tools

  • Analyzing the status of UserDN Publishing probe
  • Discussions related to SAM Update-22 transitions
  • Proposed adding OPS-MONITOR tests to Operations tests (https://ggus.eu/ws/ticket_info.php?ticket=94374)
  • OMB presentations related to OPS-MONITOR and SAM Upgrade
  • Modifying StoRM tests at midmon.egi.eu to return OK

SA1.5 Accounting

Repository

Portal

SA1.6 Helpdesk

  • Ticket monitoring
  • Preparation of the next GGUS release
  • Testing of new features on GGUS test instance

SA1.7 Support

  • followup of new sites with new EMI-1 alarms for software retirement
  • follow up of RPI, sites to be suspended, top BDII A/R, Unknowns
  • handling topics of the SAM nagios WG.
  • participation in a status update meeting of the SAM team.
  • handling requests to review SE probes
  • investigation status changes of sites
  • setting up database to track top bdii availability, availability/reliability,unknowns of sites, certification status changes and the rod performance index over time.

Software Support

Network Support

SA1.8 Availability and core services

Documentation

  • final work on MS425 based on internal review results and comments

Meetings