Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

EGI-InSPIRE:SA1 slots for EGI Technical Forum

From EGIWiki
Revision as of 15:45, 15 June 2010 by Tferrari (talk | contribs) (Created page with '===''Grid oversight''=== * 60 min Documentation * 120 min ROD ===''Operations training''=== * 270 min ROD training sessions: 3 slots 90 min each ===''Security''=== TOT 11 h Com…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Grid oversight

  • 60 min Documentation
  • 120 min ROD

Operations training

  • 270 min ROD training sessions: 3 slots 90 min each

===Security=== TOT 11 h Comments: security sessions including training to be split across two contiguous days; Only topic "security vulnerability group" fits in the proposed EGI-EMI security session

  • A coherent security infrastructure (focus on the software output) 90 min
  • SVG (security vulnerability group) 90 min
  • SPG (security policy group) 90 min
  • Security All Hands 90 min
  • EGI CSIRT team face to face meeting 180 min
  • Security Drills, 120 h
    • Results from Security Service Challenge4
    • status of the Security-Drills Tool-set.
    • Invited presentation by one Site which scored best
    • Round table for next Security Drill perhaps end of the year

===Security training=== TOT 3 h

  • 90 min software security group (SSG) training
  • 90 min EGI csirt training

===User support (SA1/SA3/NA3)=== 240 min Comment: check if existing support sessions cover all topics mentioned below

  • 180 min GGUs, SU and ticket workflow implementation, application

middleware support, support from other VCR projects/communities, inter-project support (EMI and other DCIs)

  • 60 min Network support // this is

===OLA Workshop 2 h=== // not in parallel with JRA1 sessions and accounting sessions Discussion in collaboration with JRA1 developers of new types of OLAs to define and monitor

===Operations Management Board=== 2h // avoid parallelism with other SA1 sessions