4.3.2015
Holger Angenent
> 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
> Content
Setup
User Management Working with sciebo Monitoring
User Adaptation and Feedback Problems
> 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)
•
> 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 6 800 GB SSD (RAID
10) per site
•
•• Loadbalancers: 2 Linux machines per site (LVS with keepalive)
•
> 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)
•
> Naming Scheme
•
•• UserID are composed as username@institution
•
•• Individual addresses for each institution (e.g.
rwth-aachen.sciebo.de) Pro:
•
•• Migration of institutions between sites possible •
•• Users do not need to know their corresponding site
Con:
•
•• 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
•
> User Management
•
•• Users register at www.sciebo.de 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
> Sharing
•
•• Displayname is composed of common name and sciebo-uid:
Mustermann, Max (maxid@uni-muenster.de)
•
•• Autocompletion deactivated
•
•• sciebo-uid is used for sharing •
•• If entered completely, name is shown
Pro:
•
•• Privacy •
•• Better control of shares
Con:
•
> Support concept
•
•• First level support by each institution •
•• Second level support by sciebo team
•
•• Third level support by ownCloud
•
•• On www.sciebo.de there is documentation and FAQ (work in
> 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 •
> 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
> To Do
•
•• Project boxes •
•• Increase quota for employees
•
•• Self-service tools (increase quota, delete account,...) •
•• Status reports for users •
•• Learnweb Integration
•
•• Addressbook
•
