You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Minutes

Only specific points raised and queries are minuted - see slides for what is presented.

Session 1: Planning Reports

Task 1 - Campus and Fed

Campus IdP Challenges - non technical, process and business challenges.

  • Experience from FaaS - the trust relationship between the campus and GÉANT is a gap.
  • Scope - IdP or IDM?
  • Link to eduroam-as-a-Service.
  • Sustainability
  • What do established federations benefit from this?

SIRTFI Challenges

  • Coordination with several bodies - AARC, GÉANT, REFEDS.
  • How to get high coverage without 'mandatory' which results in expulsion from eduGAIN.

Task 2 - Research & SP

e-Science Support

  • Use existing OTRS/ticketing system and escalation concepts
  • REFEDs also able to feed it in
  • Think about scaling the support depending on user types.
  • eduroam used scripts to direct queries too

Assurance

  • Needs some refining on workplan decisions
  • Lots of options, not clear info
  • VO PaaS requires some assurance info - good location for the tool as a context provider.
  • Suggest working on improving federation documentation in this field.
  • Who implements the tool? AARC or GÉANT? (We have budget and dev)

Additional work items

  • Various check tools nearly all have connections with other tasks
  • wiki.edugain.org - should this move to new wiki system?
  • TODO - reusing information from the wiki to be real support docs for different target users

Task 3 - TrustTech

User centric ID

  • Question - is there a link between user centric ID and Campus IdP - should small countries jump straight to user-centric if they don't have a footprint? M18 should trigger a decision?

MFA

  • MFA service in VO context? (Surfnet model)
  • Who 'triggers' the requirement? SP, IdP, User?
  • Beware vendor lock-in.

Mobile

  • Gap - mobile phone usability for IdP dialog windows
  • ECP?

Cross sector

  • Link with VO PaaS
  • SaToSa aspects are only once VOPaaS is complete with it's development of it

Task 4 - eduroam

  • Links with campus IdP
  • Silver bullet - how monolithic should the components be?
  • Security of information, trust.
  • Mobile expertise cross-usable in T3?

Session 2: Business Development

  • Support NRENs deploying stuff
  • FaaS - registry as a service. Can we go beyond it?
  • New users are outside Europe
  • Cost model?
  • Priority - 
    • Get our house in order - focus on improving the performance of eduGAIN - R&S etc.
    • Work with Partner relations on NREN engagement - e.g. 'only two of your IdPs support xxx, what can we do to help and International on outside Europe
    • Focus on business models (inc. outside geant costs)
      • eduGAIN/FaaS -> USPs are Hosted registry & signing 
      • eduroam IdP as a Service
      • InAcademia
      • VO PaaS
  • On international, keep us informed of what happens on that scale
  • Portfolio for organization sync'd with project portfolio
  • We need a CRM!

KPIs - need to be real, useful and we may need to develop tools to capture them. Go beyond the EC contract.

Session 3: Monitoring

  • Discussion on where should tools be hosted
    •  technical.eduGAIN for eduGAIN stuff
    • MET and fedlab stay separately in their scopes
    • REFEDs already has an info page on existing tools, linking to those
    • How do we promote this?
  • Do we need official GEANT training on the checking and monitoring tools that are available?
    • Train federations
    • Get it included in the AARC training!!!
    • Then get the AARC training to the IdPs.
  • Blog posts/features
  • http://jusp.mimas.ac.uk/ - agreements for sharing of accounting stats with SPs

Session 4: Operations

  • Would like to do usability testing but do not have enough skilled people currently.
  • Dev teams would like to do validation early as possible
  • Give input on what people are actually doing to define process.
  • How to handle dependent code not developed in house
  • Allow 2 months to transition a new service
  • How to apply agile dev to the split ops model?
  • Very important to document current ways of working before considering any change
  • Budget your support load in the CBA
  • Provide info on default security and DP considerations for pilot and production.
  • Use the ops docs as a sanity checklist during development - link to CBA too. Influence design with ops concepts early
  • Provide OLA/SLA targets.

Session 5: Breakouts

  • Need more outreach 
  • Assurance profile for MFA
  • Gamification of Science support - quadrant of R&S, CoCo, SIRTFI, MFA
  • Outreach - IAMonline - develop campus contacts

-----------------------

  • Distinguish between full services and incremental improvements in handover
  • SA should provide design guidelines & templates or technical.edugain.org - started work (Robert Latta)
  • Need to understand the role of e-science support - is it L2 or consultancy?
  • Start organizing support behind the scenes before service is scoped.
  • How to handle the 'ad hoc' support which goes to various mailing lists?

---------------------

  • letsradsec needs access to the ops data - raw db access.
  • self-service diagnostic needs ops data and more frequent checks for realtime diagnostics
  • need to benchmark the performance implications of on demand tests against the production system
  • need a spec and reporting format for probes data. f-ticks as it stands isn't quite suitable, and it isn't easily extensible to this case. JSON is of interest but TCP is an issue.

Action items



  • No labels