Joint School Computing Service (JSCS)

Transcription

1 Joint School Computing Service (JSCS) Requirements and Design Workshops Data Storage and Sharing School of Biological Science & School of Clinical Medicine

2 Today s Agenda Project background Overview of related services Q&A 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 All staff 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 staff will have access either to a wired and/or wireless network connection (local conditions allowing) which they will access using either their JSCS user account or Raven.

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 service. JSCS recognises that: Both Schools have common needs 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 Data Sharing and Storage Personal and Group Data Storage (Mirrored, Backed up) Large Data Storage (HPCS / Lager Datasets) Archive / Tiered Storage Secure Data Storage / Transfer Remote Access and Cloud

8 Personal and Group Data Storage One user account which provides access to personal and shared storage services. Easier sharing of data between groups and departments

9 Personal and Group Data Storage Automated backup and mirroring of all users data Fast, reliable and expandable storage

10 Large Data Storage A platform that allows large storage of data. Storage that's optimised for high performance computing and larger datasets. High I/O etc.

11 Large Data Storage Access should be provided to all users hardware using all supported protocols e.g. NFS/CIFS/ISCSI etc.

12 Archive / Tiered Storage Long term archive storage of data to satisfy grant or funding body conditions. Expandable storage at a much lower cost while still providing faster access than archive. Lower cost solution for larger data storage.

13 Secure Data Storage / Transfer A single storage platform that allows access to secure information/data Remote secure access to sensitive Research data. Protected using IGT framework and ISO27001 policies and procedures. Shareable, reliable and expandable storage that can be accessed via a JSCS user account.

14 Remote Access and Cloud The creation of a cloud service that uses the JSCS user directory for access. Allows sharing of data between groups and departments internal and external.

15 Remote Access and Cloud Easy to use, accessible from anywhere and automated backup. JSCS cloud can be migrated to the UIS cloud when available.

16 Remote Access Remote Access via SSH, VPN, Citrix. Secure and easy to use from home/work or while traveling.

17 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 30 minutes, rotate round to next topic Present/review feedback

18 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?

19 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.

20 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.