This document describes the system requirements for GNOS. It is not intended to serve as an installation guide or administrator's manual.
GNOS is the server-side software which will manage the storage where your organization's files will reside. Your end users will use a separate product, GeneTorrent, to upload, search for, and download files.
System requirements and installation instructions for GeneTorrent can be found here.
GNOS is comprised of four different components:
- GNOS Manager - allows you to monitor the health of GNOS and configure the other GNOS components.
- GT Tracker - coordinates file uploads and downloads.
- GT Exec - exposes public APIs and scheduling services.
- GT Server - receives upload and download requests.
These components can be installed on a single machine (virtual or physical) running CentOS 6.4 with the following characteristics.
|Minimum Cores||Memory (RAM)||Storage|
|4||8 GB||40 GB|
Note that this configuration would be suitable for a GNOS deployment with a small number of end users. For larger deployments, you would likely separate the four GNOS components across multiple machines, and could scale up the number of GT Servers to support a larger user base.
GNOS utilizes a standard POSIX interface to the back-end storage service, and is compatible with NFS, GlusterFS, and similar file system services.
The storage system should provide a minimum of 100 MB per second of read/write performance per server (see above).
- Public network access to the internet.
- 1 GB per second of bandwidth per GT server (see above).
- 7 real or public IP addresses.
- Hostnames and DNS entries are required for the compute servers where the GT Exec and GT Tracker components reside. The GT Exec hostname will become the site URL for your organization’s repository (e.g., acmeinc.annailabs.com)
For the components listed below, the firewall must allow inbound traffic to these ports.
|GNOS Manager||22, 80*|
|GT Server||6881 - 6899|
*Port 80 is needed for administrators to view GNOS performance monitoring graphs; it should only be exposed to trusted IPs.
Public Key Certificate
GNOS requires a public key certificate to ensure the authenticity of the party requesting data. Your organization must provide the SSL certificate which the GT Exec component will use.
A public key certificate is a digitally signed document that serves to validate the sender’s authorization and name. The document consists of a specially formatted block of data that contains the name of the certificate holder (which will contain the system name for the GNOS repository) and the holder’s public key, as well as the digital signature of a certification authority for authentication. The certification authority attests that the sender’s name is the one associated with the public key in the document.
The GNOS repository generates a certificate-signing request. The requestor will return a signed certificate and a chain certificate that is signed by the trusted provider.