Both Teamwork Cloud (TWCloud) and Cassandra installations are required. This section contains system requirements for installing TWCloud. The hardware requirements for Cassandra can be found here: https://wiki.apache.org/cassandra/CassandraHardware

Minimum server system requirements: 

  • 8 Processor Cores - i.e. Quad Core Hyper-threaded CPU (such as Intel E3-1230 or faster).
  • 32 GB RAM (Motherboard with an ECC RAM is always preferred on any critical database server).
  • At least 3 separate disks, preferably SSD (NVMe), (OS/Application, Data, and Commit logs). Depending on company backup procedures and infrastructure, an additional disk, equal to the data disk in size, may be required for storing the backup snapshots.
  • Linux (RedHat/CentOS 7), 64 bit or Windows 2012 R2, Windows 2016.

    Although Windows is supported, we recommend using Linux. For more information, please visit https://www.datastax.com/dev/blog/cassandra-and-windows-past-present-and-future.

    Automated deployment scripts must be modified slightly for Centos 6.6 - 6.9 due to different system daemon and firewall configurations.

    Due to Cassandra 3.11's cqlsh dependency on Python 2.7, cqlsh will not be available unless Python 2.7 is installed. Python 2.7 is not available in the standard repositories. As a result of this, we do not recommend deploying on Centos 6.

  • Cassandra 3.11-x
  • Oracle Java (Java Hotspot) 1.8.0_202.
  • A FlexNet License Server.
  • Open ports 2552, 7000, 7001, 7199, 9042, 9160, and 9142 between servers in a cluster, and open port 3579, 8111, 8443, and 8555 (default) to clients, as well as the port number assigned to secure connections between the client software and Teamwork Cloud.
  • Static IP address for each node.

  • TWCloud 19.0 requires Cassandra 3.11-x


Please see the article found at the following link for additional server recommendations for capacity and performance:

http://cassandra.apache.org/doc/latest/operating/hardware.html

Currently, if deploying on Amazon EC2, we recommend m5-2xlarge or r4-2xlarge instances.  Depending on the workloads, you may want to go to the -4xlarge instances, but for the vast majority of users, the -2xlarge will suffice.



Related pages