Breadcrumbs
Page History
On this page
| Table of Contents | ||
|---|---|---|
|
| Excerpt | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Before installing Teamwork Cloud, ensure that the system requirements described in this chapter are met. Recommended system requirementsSystem requirements are dictated by the intended deployment, taking into account the overall load which the environment will experience, including:
The database (Cassandra) can be located on the same server as Teamwork Cloud or on a separate server. Storage requirements apply only to the node where the database is located. Teamwork Cloud hosting nodes can be virtualized without any issues if the host is not oversubscribed on its resources. Nodes containing both Teamwork Cloud and Cassandra:
Nodes containing only Cassandra:
Nodes containing only Teamwork Cloud:
Storage requirementsMake sure your environment meets the following storage requirements:
For on-premises deployment, Apache Cassandra is designed to run on multiple independent servers. Each Cassandra node should have Directly Attached Storage (DAS) composed of NVMe drives for optimum performance. Traditional network-attached storage solutions that rely on IP-based connections (iSCSI, NFS, or SAN) are not recommended for on-premises deployments, as they introduce additional latencies and anti-patterns. To learn more, see the following topics: For cloud deployment, use storage technologies that have been benchmarked for Cassandra. Modern solid-state/flash arrays with fast interconnects are preferred. Note that Teamwork Cloud is not compatible with managed Cassandra services, such as Amazon Keyspaces. To learn more, see the following topics: Software requirementsTeamwork Cloud supports the following operating systems:
For a fully working environment, you will also need the following:
The following table lists the ports that Teamwork Cloud services use and their descriptions. Port traffic is TCP unless otherwise specified.
| 7001 |
| used if TLS is enabled) | ||
| 7199 | JMX monitoring port of the Cassandra node | |
| 9042 | Native client port for processing database operations | |
| Teamwork Cloud | 2468 | JMX metrics reporting port for monitoring stack |
| 2552 | Teamwork Cloud default remote server port | |
| 3579 | Default Teamwork Cloud port when SSL is not enabled | |
| 8111 | REST API HTTPS port | |
| 10002 | Default port |
| for encrypted TLS client-server communication. | ||
| Web Application Platform | 8443 | Web Application Platform HTTPS port (Authentication, Collaborator…) |
| Zookeeper | 2181 | Zookeeper internal port |
| Info | ||
|---|---|---|
| ||
| When deploying on Amazon EC2, we recommend using the m5-2xlarge, r5-2xlarge, or i3-2xlarge instances. Depending on the workload, you may want to go to the -4xlarge instances, but for most users, the -2xlarge will suffice. The m5 instances meet the minimum system requirements and will be acceptable for small deployments. The r5 instances provide more memory for the same CPU density. The i3 instances should be used when workloads have a higher level of user concurrency due to the significantly improved performance of the ephemeral NVMe storage. |
Storage requirements
Make sure your environment meets the following storage requirements:
Solid State Drives with high IOPS| NVMe |
Data, commit logs, and applications exhibit different access patterns and should reside on separate disks to avoid I/O contention.
| storage |
| . |
For cloud deployment, use storage technologies that have been benchmarked for Cassandra. Modern solid-state/flash arrays with fast interconnects are preferred. Note that Teamwork Cloud is not compatible with managed Cassandra services, such as Amazon Keyspaces. To learn more, see the following topics: