sciebo die Campuscloud für NRW The Academic NRW Cloud Storage Service

Transcription

1 sciebo die Campuscloud für NRW The Academic NRW Cloud Storage Service Holger Angenent Röntgenstr. 7-13, Münster

2 2 > What is sciebo sciebo is the brand name, short for science box Sync and share service for universities and universities of applied sciences in North Rhine Westphalia Up to 500,000 users in NRW (if all 30 universities and applied universities participate) It is organized as a consortium of all participants with the University of Münster as the head

3 3 > Content Setup User Management Working with sciebo Monitoring User Adaptation and Feedback Problems What's next

4 4 > Scenario and Software Started in February 2015 with 12 institutions 30 GB/user with the possibility to increase the quota for the employees up to 500 GB (planned) Project boxes for groups (500 GB - 2 TB) owncloud 7 Enterprise RedHat 6, later RedHat 7 (when GPFS support is available) Galera cluster with MariaDB

5 5 > Hardware Storage: 5 PB at three sites (3 PB in Muenster, 1 PB in Essen and 1 PB in Bonn) Filesystem: GPFS with declustered RAID and triple parity Application servers: 16 IBM NeXtScale nx360 M4 (16 cores) for owncloud per site Database: 4 IBM System x3650 M4 with GB SSD (RAID 10) per site Loadbalancers: 2 Linux machines per site (LVS with keepalive) Management: 1 server per site

6 Setup User Management Working with sciebo Monitoring User Adaptation and Feedback Problems What's next 6

7 7 > Three Sites One owncloud installation per institution No replication of user data between the sites Sharing between institutions via the server to server sharing (owncloud 7) owncloud has improved this mechanism in version 8

8 8 Pro: Con: > Naming Scheme UserID are composed as Individual addresses for each institution (e.g. rwth-aachen.sciebo.de) Migration of institutions between sites possible Users do not need to know their corresponding site owncloud wants us to deliver a single servername for the mobile client Possible solution: Identication of the servername in the clients via the unique userid A lookup server directs the user to the right location

9 9 > User Management Users register at via DFN-AAI for the service An account is created in a central LDAP server A separate password is set The LDAP is replicated to every owncloud application server After six months, the user will be asked to reregister After 12 months, the account will be locked After 15 months, the account will be deleted One is able to access the service at least six months after leaving university.

10 10 Pro: Con: > Sharing Displayname is composed of common name and sciebo-uid: Mustermann, Max Autocompletion deactivated sciebo-uid is used for sharing If entered completely, name is shown Privacy Better control of shares One has to know the sciebo-uid of the receiver

11 11 > WebGUI

12 12 > Desktop Sync Client

13 13 > Mobile Client

14 14 > Ganglia

15 15 > Nagios

16 16 > Registered users

17 17 > Actual users

18 18 > Support concept First level support by each institution Second level support by sciebo team Third level support by owncloud On there is documentation and FAQ (work in progress...)

19 19 > User feedback Many happy users Users from other sites asking for joining sciebo First sites asking to join sciebo Demand for owncloud-extensions like calendar and editor Some security issues High demand for project boxes and quota adjustment

20 20 > Problems At day one out-time of site Bonn: Session data were written to a slow lesystem Special WebDAV-Clients seem to disturb owncloud Besides from that, only single machines have failed without impact for the users

21 21 > To Do Project boxes Increase quota for employees Self-service tools (increase quota, delete account,...) Status reports for users Learnweb Integration Addressbook Evaluate calendar and editor

22 22 > Thank you for your attention!

23