Tarantool Cluster Manager 1.0

Release date: December 26, 2023

Latest release in series: 1.0.4

1.0 is the first public release series of Тarantool Cluster Manager. It was introduced as a part of the Tarantool EE 3.0 release. Below is an overview of key features of TCM 1.0.

TCM works as a standalone application. You can connect any number of Tarantool EE 3.0+ clusters to a single TCM instance and switch between them on the fly.

To connect a cluster to TCM, you need to provide the endpoint URLs and connection parameters of its centralized configuration storage (for example, etcd). To learn more, see tcm_connect_clusters.

The cluster stateboard is a main TCM page that visualizes the information about the selected cluster:

• Cluster topology visualized as a table or a graph
• Tarantool versions running on instances
• Memory statistics
• Errors and warnings that happen on instances

From the stateboard, you can navigate to specific instances to view their details or connect to their interactive consoles.

To learn more, see tcm_cluster_state.

TCM includes a visual editor for cluster configuration. It allows editing cluster configurations as a YAML file in the browser. Once you're done editing the configuration, you can send the changes to the configuration storage in one click or save them locally to continue editing them later.

To learn more, see tcm_configuring_clusters.

TCM features its own role-based access control system. It defines users that can log into TCM and their permissions to perform various actions or access clusters in its web interface.

You can use built-in roles or create new ones with permissions you need. Users' access can be limited to specific clusters and operations on them, for example, editing the configuration or calling stored functions. To learn more, see tcm_access_control.

TCM also supports LDAP authentication.

TCM has a built-in audit logging mechanism. When enabled, it records information about events that occur in TCM and users' actions to dedicated audit log files. You can define events to write to the audit log and adjust logging parameters, such as filename, log rotation, or compression.

To learn more, see tcm_audit_log.