Cloudera Docs

Registering clusters

Clusters Register clusters automatically by deploying and starting the CMA Agent on the source cluster, eliminating manual registration workflows within the CMA Master UI.

This workflow is for engineers who register clusters, scan workloads, use collections, and run migration guides.

Cloudera Migration Assistant uses an agent-based auto-discovery model. When the CMA Agent starts on a cluster, the CMA Agent performs the following actions:

  • Connects to the local Cloudera Manager using the configured credentials.

  • Discovers the cluster services, hosts, and metadata.

  • Establishes an outbound gRPC connection to the CMA Master.

  • Registers the cluster with the CMA Master, including discovered metadata.

  • Surfaces the cluster automatically on the Clusters page in the CMA Master UI as a source, ready for scanning.

Figure 1. Cluster registration flow

Sequence diagram: deploy CMA Agent, register with Master, cluster appears in UI

  • The CMA parcel must be distributed and activated on the cluster.

  • CMA Master must be running and reachable from the source cluster network.

  • Cloudera Manager administrator credentials must be available.

  1. In Cloudera Manager on the source cluster, select Add Service and select CMA_AGENT.
  2. Configure the required properties.
    Table 1. CMA Agent configuration properties
    Property Description
    cma_gateway_url URL of the CMA Gateway, for example, https://master-host:8093. Required when the CMA Agent is on a different cluster than the CMA Master. The agent uses this URL to discover the Master host, gRPC port, and Auth Server URI automatically through the discovery endpoint (GET /api/agent/config). When connecting from a different cluster, set the CMA Master service dependency to none in Cloudera Manager.
    cm_username Cloudera Manager administrator user name.
    cm_password Cloudera Manager administrator password.
    cma_user_home Home directory for the cma-agent user, for example, /var/lib/cma-agent.
  3. Set cma_gateway_url when the CMA Agent is on a different cluster than the CMA Master.
  4. Start the CMA Agent service.
  5. Wait for the agent to connect to the CMA Master and finish the registration automatically.

The source cluster is displayed on the Clusters page in the CMA Master UI. Click the cluster name to review details and services.

Scan workloads on the registered source cluster. For instructions, see Scanning clusters.