Installation requirements

Hardware requirements - Single-host installation

This section outlines hardware requirements for installing TeamForge Orchestrate on a single server. The single-host installation places all three TeamForge Orchestrate components (App server, MQ server, and DB server) on a single operating system. This configuration is designed for trials and moderate load, while the multi-host option outlined below is provided as a first step toward scaling your TeamForge Orchestrate instance.

Prepare for installation by setting up:

One empty host running Redhat EL or CentOS, release 6.3+ or 7.x
User credentials with sudo privileges on the host

Note: TeamForge Orchestrate must be installed on an empty host, it cannot be installed on the same OS hosting TeamForge itself.

The following are minimum resource specification requirements:

Host	CPU	RAM	Storage	Description
App/DB/MQ server	Quad-core 2.5 GHz	8 GB	74 GB	Single host, all components

Hardware requirements - Multi-host installation

For high load instances or when scalability is critical, install TeamForge Orchestrate components on separate servers or virtual machines.

Multi-host installation originates on a single server and installs core components and the TeamForge Orchestrate application on that first server (the App server). Then, the installer remotely installs the database components on a second server (the DB server) and the message queue on a third server (the MQ server).

Prepare for a multi-host installation by setting up:

Three empty hosts running Redhat EL or CentOS, release 6.3+ or 7.x
User credentials with sudo privileges on all three hosts
ssh routes from the App server host to the other two hosts

Note: TeamForge Orchestrate must be installed on an empty host, it cannot be installed on the same OS hosting TeamForge itself.

The following are minimum resource specification requirements:

Host	CPU	RAM	Storage	Bandwidth	Description
App server	Quad-core 2.4 GHz	4 GB	16 GB	1 Gbps to DB server	Application server, initiates installation process
DB server	Dual-core 2.4 GHz	4 GB	50 GB	1 Gbps to App server	MongoDB database server
MQ server	Dual-core 2.4 GHz	4 GB	16 GB	N/A	AMQP Message queue server

Software requirements and components

Proper TeamForge version:
- Orchestrate 1.4 - TeamForge 8.0
- Orchestrate 1.2/1.3 - TeamForge 7.2
- Orchestrate 1.1 - TeamForge 7.1
- Orchestrate 1.0 - TeamForge 7.0
SSH and SFTP clients are required, i.e. openssh-client. To test for this dependency, on the target server issue the command: sftp localhost
createrepo package is required by the disconnected mode installation. To test for this dependency, on the target server issue the command: createrepo --version
Orchestrate has a number of other open source software dependencies, all of which are installed as part of the installation process. During the installation process you may choose to use pre-existing MongoDB or RabbitMQ services instead of installing them, so long as version requirements are satisfied. Aside from that exception, the following software components and their dependencies will be installed:

Product	Version	Home Page	Documentation	Host
Nginx	1.5.1	http://nginx.org	http://nginx.org/en/docs/	App server
Phusion Passenger	4.0.5	https://www.phusionpassenger.com	https://www.phusionpassenger.com/support	App server
Redis	2.6.13	http://www.redis.io	http://redis.io/documentation	App server
MongoDB	2.4.3	http://www.mongodb.org	http://docs.mongodb.org/manual	DB server
RabbitMQ	3.1.0	http://www.rabbitmq.com	http://www.rabbitmq.com/documentation.html	MQ server

Ports used by TeamForge Orchestrate components

Be aware of the following port requirements to avoid conflicts during installation:

Port	Component	Host
80	Nginx HTTP	App server
443	Nginx HTTPS SSL	App server
6379	Redis	App server
27017	MongoDB	DB server
28017	MongoDB HTTP console	DB server
5672	RabbitMQ	MQ server
15672	RabbitMQ management console	MQ server

Firewall/Routing requirements

The following use cases detail TeamForge Orchestrate's firewall/routing requirements. End-user web access requires HTTP(S) access to the App server. TeamForge Orchestrate adapters supply data using the MQ layer and therefore need access to the MQ server (default port 5672). There are also private access requirements between the various installed components as detailed below.

Port	From	To	Description
80 / 443	End-users	App server	End-user HTTP(S) access
80 / 443	App server	TeamForge server	App communication with TeamForge server
80 / 443	TeamForge server	App server	TeamForge communication with App server
5672	TeamForge Orchestrate Adapters	MQ server	Message communication between Adapters and MQ server
5672	App server	MQ server	App communication with MQ server
5672	TeamForge server	MQ server	TeamForge communication with MQ server
15672	App server	MQ server	App administration of MQ server
27017	App server	DB server	App server communication with DB server
22	App server	MQ server	App ssh to MQ server, installation only
22	App server	DB server	App ssh to DB server, installation only

The App server also needs access to the Redis service, but since it is installed on the App server by default, it is not included in the table above.