Versions Compared

Old Version 4

changes.mady.by.user Kristina B.

Saved on

compared with

New Version Current

changes.mady.by.user Inga A.

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page

Table of Contents
maxLevel4


Magic Collaboration Studio
Excerpt

Before installing Magic Collaboration StudioTeamwork Cloud, ensure that the system requirements described in this chapter are met.

Note
titleCassandra installation

Magic Collaboration Studio requires Cassandra installation. To learn more about the hardware requirements for Cassandra, see https://cassandra.apache.org/doc/latest/cassandra/operating/hardware.html

Recommended system requirements

Recommended system requirements

System requirements are dictated by the intended deployment, taking into account the overall load which the environment will experience, including:

  • Number of concurrent users
  • Level of activity (commits) per day
  • Overall number and size of the projects stored in Magic Collaboration StudioTeamwork Cloud.

The database (Cassandra) can be located on the same server as Magic Collaboration Studio Teamwork Cloud or on a separate server. Storage requirements apply only to the node where the database is located. Magic Collaboration Studio Teamwork Cloud hosting nodes can be virtualized without any issues if the host is not oversubscribed on its resources.

Nodes containing both Magic Collaboration Studio Teamwork Cloud and Cassandra:

  • 96 -128 GB ECC RAM
  • >=16 processor threads (such as E5-1660)equivalent or better than the Intel Xeon E-2278G, or their AMD counterparts, supporting x86-64 architecture)

  • 1TB NVMe/

    >1TB

    SSD DAS storage

Nodes containing only Cassandra:

  • 48 - 64 GB ECC RAM
  • >=8 processor threads (such as E5-1620)equivalent or better than the Intel Xeon E-2234, or their AMD counterparts, supporting x86-64 architecture)

  • 1TB NVMe/

    >1TB

    SSD DAS storage

Nodes containing only Magic Collaboration StudioTeamwork Cloud:

  • 48 - 64 GB ECC RAM
  • >=8 processor threads (such as E5-1620equivalent or better than the Intel Xeon E-2234, or their AMD counterparts, supporting x86-64 architecture)
  • >250GB storage
SAN Storage
Info
titleMulti-Node Clusters

Recommended minimum sizing stated above applies to each node in a multi-node cluster.

Warning
title

SAN

Storage

should not be used for data or commit log volumes on Cassandra nodes. This will result in severe performance degradation. There is no amount of SAN tuning and OS tuning which could mitigate this.

requirements

Make sure your environment meets the following storage requirements:

  • Solid State Drives with high IOPS 
    NVMe or SSD drives are highly suitable due to their low latency and high throughput. 
  • Separate disk mounts
    Data, commit logs, and applications exhibit different access patterns and should reside on separate disks to avoid I/O contention. 

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 requirements

Teamwork Cloud

Minimal hardware requirements

For adequate Magic Collaboration Studio operation, your hardware should meet the following 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 recommended) and 8 GB RAM dedicated for Magic Collaboration Studio

  • 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 size, may be required to store the backup snapshots.

Software requirements

Magic Collaboration Studio supports the following operating systems:

  • Linux 64-bit RedHat 8, RedHat 9, Oracle Linux 8.

  • Windows 2016 or Windows 2019.
Note

The Linux operating system is highly recommended for Magic Collaboration Studio Teamwork Cloud deployment. Cassandra 4 does not have native Windows support. For more information, please visit https://www.datastax.com/dev/blog/cassandra-and-windows-past-present-and-future.

For a fully working environment, you will also need the following:

  • Cassandra is compatible with OpenJDK 11.0 (tested with Eclipse Temurin™ by ADOPTIUM 11.0.14)
  • Magic Collaboration Studio Teamwork Cloud is compatible with OpenJDK 17.0 (tested with Eclipse Temurin™ by ADOPTIUM 17.0.118)
  • IMPORTANT. To use modeling tools with DSLS licenses, Microsoft Visual C++ Redistributable must be installed (see see Latest supported Visual C++ Redistributable downloads). This applies to Windows OS only.
  • FlexNet or DSLS license server
  • Cassandra 4.0.x, 4.1.x
  • A static IP address for each node.

  • Open ports 1101, 2181, 2552, 7000, 7001, 7199, 9042, and 9142 between servers in a cluster.

  • Open ports 3579, 8111, 8443, and 10002 (default) for clients. The port number 10002 can be changed according to the port assigned to secure connections between the client software and Magic Collaboration StudioTeamwork Cloud.

The following table lists the ports that Magic Collaboration Studio Teamwork Cloud services use and their descriptions:. Port traffic is TCP unless otherwise specified.

https://cassandra.apache.org/doc/latest/cassandra/operating/hardware.html
ServicePortDescription
FlexNet server (lmadmin)1101FLEXnet server port

8090
Default vendor daemon port (web browser management port)
License management web interface HTTP port

27000-27009Internal license server manager port



Cassandra7000Internode cluster communication port (not used if TLS is enabled)

7001Encrypted internode cluster communication port (used if TLS is enabled)

7199JMX monitoring port of the Cassandra node

9042Native client port
used to connect to Cassandra and perform operations (used with 2021x version and later)
for processing database operations



Teamwork Cloud2468JMX metrics reporting port for monitoring stack

2552Teamwork Cloud
9142Native client port when SSL encryption is enabled (used when Cassandra is on a separate server or Cassandra is deployed as a multinode cluster)Magic Collaboration Studio2552
default remote server port

3579Default
Magic Collaboration Studio
Teamwork Cloud port when SSL is not enabled

8111
Magic Collaboration Studio
REST API HTTPS port

10002 Default port when SSL is enabled



Web Application Platform8443Web Application Platform HTTPS port (
Teamwork Cloud Admin
Authentication, Collaborator…)



Zookeeper2181Zookeeper internal port
For additional server capacity and performance recommendations, see 


Info
titleIf deploying on Amazon EC2
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.