Importing a cluster topology

Import the topology of a DataStax Enterprise cluster that already exists and is being monitored in OpsCenter into Lifecycle Manager so you can start centrally managing installations and configurations.

Import the topology of a DataStax Enterprise (DSE) cluster that already exists in OpsCenter and is being monitored in OpsCenter into Lifecycle Manager (LCM) so you can start centrally managing configurations. LCM imports the cluster topology and automatically builds the topology model in the Clusters workspace. If a cluster is not connected to OpsCenter, the cluster is not displayed in LCM and is not available for import.

Important: LCM imports cluster topologies only. Configuration profiles are not imported, and must be recreated manually after importing the topology.

Note: Lifecycle Manager does not currently support managing DSE Multi-Instance nodes (also referred to as dense nodes).

Additionally, LCM currently only supports importing DSE clusters installed from Debian (.deb) or RedHat (.rpm) packages.

Prerequisites

Add SSH credentials.
Ensure all nodes in the cluster you want to import use the same SSH credentials. If some nodes require different credentials, see manually importing a cluster topology.
Only the GossipingPropertyFileSnitch is supported for managing or importing DataStax Enterprise clusters in Lifecycle Manager. See Migrating from the PropertyFileSnitch to the GossipingPropertyFileSnitch.
Lifecycle Manager currently does not support configuring nodes by network interface (listen_interface or rpc_interface/native_transport_interface). If a cluster is configured with those options, the import will fail. Reconfigure the nodes by listen_address and native_transport_address rather than the corresponding interface options before importing the cluster.
Datacenters must consist of a homogeneous node workload type. Mixed-load datacenters cannot be imported into Lifecycle Manager.
If Transparent Data Encryption is enabled, it must be disabled prior to importing the cluster into LCM. See Encrypting configuration file properties.

Procedure

Click Clusters from the Lifecycle Manager navigation menu.
Clusters that are not being managed by LCM are indicated with a red plus sign in the Clusters pane.
In the Clusters pane, select the cluster to manage.
The Automatic Cluster Import dialog appears.
Select the SSH credentials defined for the cluster.
Read the warning messages. Follow the instructions that are applicable to your environment:
1. If nodes do not use the same SSH credentials, you must follow the instructions to manually import the cluster topology.
Select acknowledgement of the warnings.
Click Submit.
The import cluster job begins processing. Follow the progress in the Jobs workspace. If unsuccessful, a dialog provides a link to review the job details.

What's next

Create the necessary configuration profiles and associate them with the cluster, datacenter, or nodes in the Clusters workspace.
Add a repository and associate it with the cluster in the Clusters workspace for running future install jobs.