The TeamDrive Host Server provides the scalable storage component required for TeamDrive Clients to store their Space data.
This manual will guide you through the installation of your own local hosting service for TeamDrive. This document is intended for administrators who need to install and configure a TeamDrive Hosting Service.
The TeamDrive Host Server installation requires a running TeamDrive Registration Server instance. If you are setting up both components on your own premises, please start with setting up the Registration Server as outlined in the TeamDrive Registration Server installation guides. If you are using a Registration Server instance hosted by some other service provider, make sure you can access it and you have performed an initial setup/configuration already.
To operate a TeamDrive Hosting Service you need a 64-bit system with a minimum of 2 processors (or 1 processor with dual-core or quad-core), a minimum of 2 GB RAM and a redundant storage system (e.g. RAID-5) that is sufficiently large and scalable if required.
The exact sizing depends heavily on the anticipated number of concurrent client connections, the bandwidth required and the amount of space data to be stored. Please contact us via firstname.lastname@example.org for assistance.
We recommend a quad-core processor with 8 GB RAM.
Operating System Requirements¶
We recommend using a recent 64-bit version of Red Hat Enterprise Linux 6 (RHEL 6) or a derivative distribution like CentOS 6, Oracle Linux 6 or Scientific Linux 6 as the operating system platform.
This document is written with this OS environment in mind — the names of packages, configuration files and path names might be different on other Linux distributions. If you have any questions about using other Linux distributions, please contact email@example.com .
You will need at least Apache HTTP Server version 2.2.9 (version 2.4 is currently not supported) which should be configured using the “prefork” MPM (http://httpd.apache.org/docs/2.2/mod/prefork.html). The prefork option is more scalable under load than the worker option and is usually the default configuration on Linux distributions.
The TeamDrive Host Server processes need to open a large number of file
descriptors. Make sure that the values in
ulimit are set sufficiently
high, e.g. by setting “nofile — max number of open files” in file
In addition, the TeamDrive Hosting Service requires the Yvva Runtime Environment version 1.2 or later, and a MySQL Database Server version 5.1 or later (MySQL 5.5 or 5.6 are recommended for performance reasons).
When installing the TeamDrive Hosting Service, we assume that you have basic knowledge of:
VMware: importing and deploying virtual machines, configuring virtual networking and storage (when using a pre-installed Virtual Appliance)
- Linux system administration:
- Adding/configuring software packages
- Editing configurations files
- Starting/stopping services
- Creating user accounts
- Assigning file ownerships and privileges
- Creating and mounting file systems
- Setting up environment variables
Apache web server: installation and configuration, adding and enabling modules, modifying configuration files
MySQL Database: installation and configuration, administration/maintenance, using the MySQL command line client, basic SQL
Basic knowledge of application server technology
Storage Volumes are used to store the TeamDrive Clients’ Space data, so they can grow quite significantly in size. We strongly suggest to place them on a dedicated file system/storage volume or an NFS mount that supports proper file locking (e.g. NFSv4). See Verifying File Locking for a description of how to verify file locking on a Storage Volume.
When using a block device like a local/virtual hard disk or an iSCSI target, we suggest using ext3, ext4 or XFS on top of a logical volume (LVM) as the file system for this storage area. Using LVM provides some additional flexibility for increasing the storage capacity of a single volume dynamically.
It should be ensured that the Space storage volumes that are mounted on the servers are equipped with sufficient security measures against failure and data loss. Strategies could include mirrored drives or some form of RAID at the minimum; even better is a SAN system with upstream NAS heads. Alternatively, block-by-block replication (as provided by many enterprise storage systems) can be implemented.
The bandwidth of the Host Server’s network interface plays a vital role in defining the overall performance and responsiveness of the TeamDrive Service. Clients need to be able to quickly upload new Space data, so it is available for download for all other Clients invited to that Space. Usually, the amount of outgoing traffic (delivering Space data to clients) exceeds the inbound traffic.
The system must have IP connectivity, using a fixed IP address and a resolvable fully qualified domain name. This host name becomes part of the URLs used by the TeamDrive clients to access the TeamDrive Spaces and can not be changed once the service is in operation. The Host Server itself needs to be able to properly resolve host names, too.
If the Host Server is located behind a firewall, please ensure that it is reachable via HTTP (TCP port 80) and HTTPS (TCP port 443) by the TeamDrive Clients.
For the initial registration and the exchange of cryptographic keys, the Host Server must be able to establish HTTP connections (TCP port 80) to the Registration Server. After the registration and activation, no further connections from the Host Server to the Registration Server will be established.
To perform API calls (e.g. to create new Space Depots or to query for existing Spaces for a particular user), the TeamDrive Registration Server must be able to establish outgoing HTTP/HTTPS connections to the TeamDrive Hosting Service.