Services Setup with DataStax Mission Control Runtime Installer
DataStax Mission Control is currently in Public Preview. DataStax Mission Control is not intended for production use, has not been certified for production workloads, and might contain bugs and other functional issues. There is no guarantee that DataStax Mission Control will ever become generally available. DataStax Mission Control is provided on an “AS IS” basis, without warranty or indemnity of any kind.
If you are interested in trying out DataStax Mission Control please join the Public Preview.
DataStax Mission Control must be installed on dedicated Virtual Machines (VM) or a bare-metal servers that are running in
Use DataStax Mission Control Runtime Installer to first create and configure Kubernetes where you are installing DataStax Mission Control. With the prerequisite infrastructure and services in place, install DataStax Mission Control and its components.
The cluster created by DataStax Mission Control Runtime Installer is composed of one or more
Control Plane nodes and several worker nodes.
When performing migrations from OpsCenter, the
Control Plane servers replace the servers running OpsCenter and its metrics cluster, and worker nodes are to be installed on each node running DSE. The following diagram shows how the original servers from the DSE cluster running OpsCenter overlay (map) onto the DataStax Mission Control topology.
This diagram illustrates an existing server running Opscenter along with a single datacenter (dc) DSE deployment. The DataStax Mission Control Runtime Installer creates and configures a Kubernetes cluster on the DSE and OpsCenter hosts. The resulting
Control Plane runs a mixture of operator and DSE resources, making it necessary to map specific DSE instances to certain worker nodes. When the migration is complete, Kubernetes is running on all hosts with DSE nodes. These hosts run on the same hardware prior to and following migration. The data is maintained by the hosts with migration to the container-based processes happening in-place. DataStax Mission Control manages all aspects of the migration with its advanced automation.
kubectlCLI tool, v1.22 or later.
Dedicated server hardware or VMs on which to run the
A downloaded DataStax Mission Control license file.
Installation of DataStax Mission Control requires a license file containing installer coordinates and update streams. Generate a community edition license file at the DataStax Mission Control Public Preview Portal. If you need a replacement license file or a non-community edition please contact your account team.
This procedure details three distinct steps.
Workerruntimes on every DSE node.
Installing DataStax Mission Control on the runtime.
curl -sSL https://kurl.sh/mission-control-public-preview | sudo bash
curlcommand establishes a Transport Layer Security (TLS) connection and an online Public Preview copy of DataStax Mission Control.
The command returns a URL and a password that you use to access the KOTS installation interface. This dashboard manages the DataStax Mission Control installation.
The output also issues a command line to run on all of the DSE worker nodes.
kubeconfigfile to your
$HOME/.kube/configdirectory. This simplifies running
mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chmod 755 -R /home/ubuntu/.kube
Run the following command to verify that the
kubectlcommand works and that the
Control Planeis in
$ kubectl get nodes NAME STATUS ROLES AGE VERSION ip-172-31-28-116 Ready control-plane,master 13m v1.24.8
Run the following command on the
curl -L https://k8s.kurl.sh/latest/tasks.sh | sudo bash -s taint_primaries
This taints the
Control Planeto prevent any DSE nodes from accidentally scheduling on this hardware.
Copy the command line issued from the Install
Control Planeon a DSE server output.
Example with variables:
curl -fsSL https://kurl.sh/version/<version-number>/<version-label>/join.sh | sudo bash -s kubernetes-master-address=<IP-address>:<port> kubeadm-token=<token-number> kubeadm-token-ca-hash=<token-ca-hash-number> kubernetes-version=1.24.9 docker-registry-ip=<IP-address> primary-host=<IP-address>
Append the following to that copied command on any worker node that runs DataStax Mission Control
Run the appropriate version of the command on all DSE worker nodes.
This installs the required packages, starts the processes, and joins the nodes to the DataStax Mission Control cluster running in
Run the copied version of the command without the appended
labels=parameter on all DSE nodes.
The command can run concurrently on all the worker nodes without risking any conflict.
Each node should display the following message upon successful completion:
Control Planeserver, run the following command to check if all the worker nodes have joined:
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION ip-172-31-2-195 Ready <none> 8m14s v1.24.8 ip-172-31-28-116 Ready control-plane,master 30m v1.24.8 ip-172-31-31-212 Ready <none> 8m53s v1.24.8 ip-172-31-37-223 Ready <none> 8m55s v1.24.8
All worker nodes now appear in the result and eventually reach the
Readystate. Contact your account team if any nodes fail to reach the
Proceed to the installation of DataStax Mission Control.
Open a browser and go to the
KOTSURL provided by the Control Plane installation output. The following screen should appear:
Follow the instructions on the screen, and then click Continue to Setup. On the next screen, click Advanced, and then click Proceed to work toward accessing the Admin Console UI.
The next screen allows you to upload a certificate for
httpsand avoid going through the warning screens. It is not mandatory to do so and you can click Skip and Continue to proceed with the DataStax Mission Control deployment.
A Log-in screen appears. Enter the password provided in the Control Plane installation output.
On the next screen, upload your downloaded customer license file.
An ensuing window tracks the installation progress.
On the next screen, leave the Control Plane box checked when installing in a single datacenter cluster or when installing the first datacenter. Click Continue.
Kubernetes packages are installed on every DSE worker node. When this task completes, a screen appears with a green badge indicating the Currently deployed version:
Control Planenode and run the following command:
kubectl get pods -n mission-control
NAME READY STATUS RESTARTS AGE XXX-operator-controller-manager-74b9654d87-55k8t 1/1 Running 0 2m28s XXX-operator-65c8f6d9c8-hc7ss 1/1 Running 0 2m28s XXX-manager-59dc98998d-gs25p 1/1 Running 0 2m28s
All deployed DataStax Mission Control pods are displayed. This sample result indicates that three pods are in a
Runningstate. These pods contain the DataStax Mission Control operators.
DataStax Mission Control is now ready to use for DSE cluster installation or migration. See Adding a DSE cluster