Use DSE OpsCenter Lifecycle Manager (LCM) to provision and deploy a DataStax Enterprise (DSE) cluster
When you use DSE OpsCenter Lifecycle Manager (LCM) to install a DataStax Enterprise (DSE) cluster, you must install OpsCenter on a dedicated server, and then use LCM to configure and install DSE on the nodes in the DSE cluster.
For demonstration purposes, this guide installs one cluster with the following characteristics:
-
Two datacenters.
-
Three nodes per datacenter.
-
One datacenter,
dc1, is dedicated to transactional workloads, and the other datacenter,dc2, is dedicated to Analytics workloads. -
Both datacenters support DSE Graph workloads.
-
Internode and client encryption are enabled on all nodes in the cluster.
-
Internal authentication and authorization are enabled.
Modify this guide as needed to fit your cluster topology and requirements.
Prepare for cluster deployment
-
Plan your cluster topology and workloads.
The topology of your clusters is important. You need to know the following:
-
The number of clusters you need.
-
The number of datacenters per cluster.
-
The number of nodes per datacenter.
-
-
Prepare infrastructure based on your cluster topology, including machines for DSE and a separate machine for OpsCenter, if you haven’t already installed OpsCenter.
All machines must be running a supported platform.
-
Get authentication credentials (username and password, or an SSH key) for each machine where you will install DSE.
You can use the same credentials for one or more machines.
-
Make sure all DSE nodes are accessible from the OpsCenter machine.
For example, if you have a firewall, make sure the firewall allows access to the DSE nodes from the OpsCenter machine.
-
Make sure the DSE nodes have access to download DSE software files from IBM Fix Central using one of the following methods:
-
Download over the public internet.
-
Download through a proxy.
-
Download from an internal mirror repository owned and managed by your organization.
-
Access LCM
-
Install and start OpsCenter, if you haven’t done so already:
-
Connect to OpsCenter in a web browser at
http://opscenter-host:8888/.For more information, see Access OpsCenter LCM.
-
In the OpsCenter UI, select Create a new cluster, and then click Get Started.
LCM opens in a separate window.
-
Optional: Create custom data directories if you aren’t using the default directories.
Add credentials, configuration profiles, and repositories
-
In LCM, click SSH Credentials, then click Add Credential, and then enter the credentials for the nodes in your cluster:
-
Give each user or key a descriptive, human-readable name so you can keep track of the users and keys used in your cluster.
-
For password authentication, add each node’s user credentials in Login User and Login Password, and then click Save.
-
For a private key, enter the username in Login User, select Private Key, enter the key, and then click Save.
For more information, see Add SSH credentials.
-
-
Click Config Profiles, click Add Config Profile.
Configuration profiles define the required DSE configuration on the cluster. If your cluster configuration isn’t uniform at all levels, you can create multiple configuration profiles to apply to the cluster, datacenter, and node levels. Similarly, you can create different profiles for different environment or use cases, such as development, test, and production profiles.
-
Enter a name for the configuration profile, such as
dse68. -
Select the DSE version, such as
dse v6.8.0. -
In Config Profiles, select cassandra.yaml in the left pane under Apache Cassandra, and then configure the encryption settings:
-
Under server_encryption_options, set internode_encryption to
all. -
Set the keystore_password and truststore_password to new values.
-
Under client_encryption_options select
enabled. -
Set the keystore_password and truststore_password to new values.
-
-
In Config Profiles, select dse.yaml, and then configure the authentication and authorization settings:
-
In the DSE Authenticator Options section, under authentication_options, select enabled.
-
In the DSE Authorizer Options section, under authorization_options, select enabled.
-
-
Click Save to create the configuration profile.
-
Click Repositories, and then click Add Repository to add your DSE software repository.
LCM uses this repository to install and update DSE on the nodes in your cluster. For more information, see Add a repository.
-
Enter a name for the repository, such as
dse. -
If you are using an internal mirror repository, click Access Private Repo, and then enter the repository URL and URL key.
-
Enter the repository credentials in Username and Password.
-
Click Save.
-
Define the cluster topology
To define the cluster topology in LCM, you must add the cluster, add datacenters to the cluster, and then add nodes to each datacenter.
-
Click Clusters, and then click Add a Cluster.
-
Enter a name for the cluster.
-
If all machines in the cluster use the same credentials (password or key), select the name of the credentials you configured earlier in SSH Credentials.
-
For Config Profile, select the name of your configuration profile.
-
When you are prompted to enter passwords, enter
cassandrain Old Password, and then enter the desired new password for thecassandrauser on your cluster’s nodes. If this is a new installation, the Old Password is alwayscassandra. If DSE is already installed on this cluster, the Old Password might not becassandraif you changed thecassandrauser’s password. -
For Repository, select the name of your DSE repository.
-
Click Save.
-
-
Click your new cluster’s name, and then click the Add icon by Datacenters to add a datacenter to the cluster.
-
Configure a datacenter for transactional workloads and support for DSE Graph.
For example purposes, this guide segregates transactional and analytics workloads on different datacenters. Your cluster topology depends on your actual use cases and database workloads.
Transactional workloads are standard Cassandra database workloads. The other workload options are for DSE advanced workloads, including DSE Search, Analytics, and Graph. The workloads enabled in a datacenter determine the capabilities of the DSE nodes in that datacenter.
-
Enter a name for the datacenter.
-
If you use different SSH credentials for each datacenter, select the name of the SSH credentials to use for this datacenter.
-
For Workload, select the workloads that can run on this datacenter. For this example, use the default Cassandra option, which is for transactional workloads.
-
Select DSE Graph to enable graph support on the nodes in this datacenter.
-
Click Save.
-
-
Add a second datacenter that supports DSE Analytics and Graph:
-
Enter a name for the datacenter.
-
If you use different SSH credentials for each datacenter, select the name of the SSH credentials to use for this datacenter.
-
For Workload, select Spark to enable DSE Analytics workloads.
-
To disallow transactional workloads, make sure Cassandra isn’t selected.
-
Select DSE Graph.
-
Click Save.
-
-
Add nodes to the datacenters.
-
Click the name of the first datacenter, then click the Add icon next to Nodes.
-
Enter a name for the node, such as
dse-transactional-1. -
For SSH IP Address, enter the node’s IP address.
-
If you use different SSH credentials for each node, select the name of the SSH credentials to use for this node.
-
To override the default IP address, which is the SSH IP Address, enter an IP Address in Native Transport (RPC) Address.
-
Click Save.
-
Continue adding nodes until you have configured all nodes in all datacenters in this cluster. This example requires six nodes because there are two datacenters with three nodes each.
-
Run the installation job
After adding all nodes, run the installation job to install DSE on the nodes:
-
Under Clusters, click your cluster’s name.
-
Click the More menu next to the cluster’s name.
-
Click Install to open the Run Installation Job dialog, and then queue the installation job for LCM.

-
Click View Job Summary to track the progress of the installation.
To return to the main OpsCenter interface, click OpsCenter Monitoring.