Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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


  •