GN42_SA2_JRA3 kick off_201612071234.pptx

WorldTrade3 6 views 8 slides May 01, 2024
Slide 1
Slide 1 of 8
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8

About This Presentation

Transition project


Slide Content

Marina Adomeit JRA3 kick off SA2 in GN4 -2 12 -13 July, Zürich SA2 Activity leader

SA2 Find us on wiki : https :// wiki.geant.org/display/timops

T1- Service Transition and software management Service Transition : According to the defined transition process Performs s ervice validation and testing : Software validation: code quality testing and build process Security testing: penetration testing and secure code testing S ystem testing: d ocumentation a ssessment , u ser s upport r eview , d atabase d esign r eview Regular and on-demand s oftware security and quality audits and penetration testing Software Management: Organise training for software developers - S4D, SCT Software management services for software development and release teams across GÉANT services - started survey among developers

T2- T & I operations - organisation T2 is organised in a horizontal way, having: Service operations teams, for each servie operated in T2, consisting of: Service Manager: (Miro -eduroam, Tomasz – eduGAIN, Nebojša – FaaS, Reimer - eduPKI ) DevOps team Steering group management: (Miro- eduroam, Brook- eduGAIN) L2 support teams ? Core team, consisting of: Security team Technical team Reporting: Deliverable report for each 10M of operations period Operational KPIs in the SA2 quaterly management reports Uptake KPIs provided to JRA3 on request

T2- T & I operations - streamlining Service operatons will need to be consistent and minimum baseline fullfiled: Defined draft of service operations baseline, that got translated into: Template for service documentation Checklist for adhering to operations baseline , when service is transitioned into operations Checklist for adhering to operations baseline, yearly check Milestone for M13 for production services to be inline with service operations For new services comming to SA2, we are working to arrange the resources needed for operations. Currently T2 core team is drafting a list of requirements for operational enviroment : VMs, monitoring, availability, backups, logs, resource inventory, configuration management, CRM, helpdesk, something else !?

Propose improvements within individual services and a dvance shared and common processes and information across services. Help in consolidating and streamlining processes and workflows. Provide CSI (ITIL: Continual Service Improvement) related guidelines and BPs. Make the key process flows and operational service related procedures more transparent – data, documentation, metrics, promotion, user relationship. Further elaborate SDP , add service related measurements, KPIs and metrics Contribute to better overlaying of fabrics of GEANT, NRENs and services. 6 T 4 - Production Optimisation

Enhancements to current services eduGAIN: Changes to constitution Consultancy support Service provider easier registration Identity assurance support Monitoring GEANT training on using different test/monitor/diagnostic tools e duroam: letsRadsec Self service support (end users and admins) CAT and adding a probe New services coming our way: VOPaaS inAcademia Moonshot e duroam as a service IdP as a service (SAML) 7 Collaboration with JRA3 Enhancements needs to be well planned including the implementation in the operations Services needs to be documented before start of transition Plan aprox 2 months for service transition

8
Tags