Joint School Computing Service (JSCS)

Transcription

1 Joint School Computing Service (JSCS) Requirements and Design Workshops: Scientific Computing School of Biological Science & School of Clinical Medicine

2 Today s Agenda Project background Overview of related services Break out sessions Review of findings Next steps

3 What is the JSCS project? A collaborative project between SBS and SCM. To establish the feasibility of a Joint School Computing Service, which could potentially provide a wider suite of IT Services to both Schools. The project aims to: determine the requirements of the staff across the two Schools design a set of services which would meet those requirements outline the systems and structures which would deliver those services agree a financial and governance model to enable such a service.

4 JSCS Universal Services User Accounts JSCS users will get a JSCS Directory User Account which will enable access to JSCS systems including the network, managed computers and online services. Network Connection All JSCS users will have access to a wired and or wireless network connection

5 JSCS Universal Services Computer Support All staff will can get technical support for one or more nominated computers In addition, several options are available for more specialist support Procurement All staff can contact JSCS for assistance in procuring IT hardware and software Backup Appropriate backup will also be designed into JSCS services.

6 JSCS, UIS and Local IT Services Relationship between UIS and your local IT support via JSCS UIS provides centralised IT services Local IT support provides departmental IT services JSCS recognises that both Schools have common needs and we can improve local IT services, by grouping them together JSCS will not look to replicate an existing UIS service JSCS and UIS services should be broadly complimentary

7 Today s workshop - Scientific Computing Scientific Computing Support HPC/Bioinformatics Local & JSCS procured clusters, large RAM/multi core servers and their operating systems High spec workstations Large RAM, multi core/gpu desktops PC s attached to lab equipment often running specialist software Software and OS support i.e. R, Mattlab, Lasergene, Prism etc. Compilation of packages from source and specialist Linux support File system s and large scale storage used for HPC i.e. lustre, CEPH, OCFS, GPFS. Support beyond standard CIFS/NFS storage

8 HPC Storage File system s and large scale storage used for HPC Usually provided on dedicated hardware in addition to the standard CIFS/NFS storage and support Often optimised for performance with a trade off in resilience i.e. scratch space with no RAID Object storage, CEPH, Open Stack etc. Data is treated as objects with metadata etc

9 Key points from the JSCS interviews We ve identified a large number of PC s attached to lab equipment or run as part of a dedicated facility i.e. Imaging, Mass Spec etc Most SBS and a few SCM departments own and run local clusters. There are also several very large RAM / multi core machines Most clusters and PC s attached to lab kit have a primary non IT user that provides computing advice Some departments already have CEPH, OCFS or Lustre instances Moving large data sets is an issue (fast networking needed)

10 Key points from the JSCS interviews Feedback so far is PC s attached to lab equipment will require a light touch The focus of the service should be support of software and hardware needed for research rather than a prescribed offering

11 Benefits of the JSCS Scientific Support Service Ability to permit resource access and manage accounts via a single user directory Standardisation if / where possible whilst broadening the number of support staff available to users Hardware procurement ideally aligned or co-ordinated with the HPCS Use of JSCS backup, storage and archiving Support of non standard / open source software Funded to a point with cost recovery element

12 Benefits of a Scientific Support Service Closer alignment to the larger UIS HPCS service allowing easier scale out from local to UIS HPCS resources End of life support / migration to JSCS procured and managed equipment Ability to take some or all of the service

13 Break Out Sessions Format for today Break into small groups (one group per topic) Group discussion requirements / identify common ground Each group will write up key points After 15 minutes, rotate round to next topic Present/review feedback

14 Break Out Sessions - Topics Lab equipment PC s attached to equipment run by dedicated facility managers or by a lab member High Performance Computing Users and groups with HPC needs 'Scientific support beyond the service desk Support of scientific users and their computing issues

15 Questions? Q. Are there any gaps we missed? Q. Which requirements are common and which specialised? Q. What do we need to add or refine to make the catalogue complete? Q. Which services might be offered by UIS and which by JSCS?

16 Project Next Steps Project team will review all the feedback from this week s workshops. Check that the information gathered is complete. Review this information against the JSCS prototype proposal. The captured requirements can then be drawn into the design of the proposed JSCS services. Any gaps may require follow-up discussions.

17 Project Next Steps (continued) The project team will then finalise the JSCS proposal and catalogue. Circulate to all in-scope departments for final feedback. This will be considered for approval by SBS and SCM IT Committees, the JSCS Steering Group and the Secretaries of both Schools. If approved, Finance and Governance part of the project will begin in January Regular projects updates will be provided via JSCS mailing list.