This github covers setting up a separate DataStax cluster to hold the Opscenter keyspace to for the main DataStax cluster. Two main docker containers are used: DataStax Server and DataStax opscenter.
The DataStax images are well documented at this github location https://github.com/datastax/docker-images/
Upgraded for 6.0
- Prepare Docker environment
- Pull this github into a directory
https://github.com/jphaugla/datastaxOpscDCDocker.git - Follow notes from DataStax Docker github to pull the needed DataStax images. Directions are here: https://github.com/datastax/docker-images/#datastax-platform-overview. Don't get too bogged down here as docker-compose makes all of this automtic.
- Open terminal, then:
docker-compose up -d - Verify DataStax is working for both hosts:
docker exec dse cqlsh dse -u cassandra -p cassandra -e "desc keyspaces";docker exec dseops cqlsh dseops -u cassandra -p cassandra -e "desc keyspaces"- Also note, in the home directory for the github repository directory the docker volumes should be created as subdirectories. To manipulate the dse.yaml file, the local conf subdirectory will be used. The other dse directories are logs, cache and data. The directory that will change is the opscenter-clusters as the opscenter configuration file will be visible here.
This Opscenter storage is documented here:
https://docs.datastax.com/en/latest-opscenter/opsc/configure/opscStoringCollectionDataDifferentCluster_t.html
This tutorial provides specific commands for this environment, so it shouldn't be necessary to refer to the docs, but they're a handy reference if something goes awry.
Open up browser to opscenter and separately add each node to its own cluster to be managed by Opscenter. Note: Each node is assigned to a separate cluster. The dse node is in the "main" cluster and dseops is in OPSCstore. The idea is to have the opscenter cluster for the "main" cluster to be stored in the "OPSCstore" cluster. Use the host names dse and dseops to add the clusters to opscenter. This link describes how to add each of the 1 node clusters: https://docs.datastax.com/en/opscenter/6.1/opsc/online_help/opscAddingCluster_t.html.
- Open up the opscenter UI with localhost:8888
- Click on "Manage existing cluster" and click "Get Started"
- Enter dse into the top box as a node in the cluster, click "Next"
- Click "Install agents manually", click "Close"
- Click "NEW CLUSTER", "Manage existing Cluster" and "Get Started"
- Enter dseops into the top box as a node in the cluster, click "Next"
- Click "Install agents manually", click "Close"
A listing of the opscenter-clusters directory should show the OPSCenter.conf and main.conf files.
When the clusters are added to opscenter, a separate file will be created in the opscenter node for each cluster managed by ospcenter. The following steps will edit the main.conf file in opscenter so the "main" cluster will have its opcenter data stored in the "OPSCstore" cluster. All the seed nodes for "OPSCstore" should be included in the main.diff file. Verify the file main.diff has dseops as the seed_host.
- Get the main.conf file from the opscenter node using docker
docker cp opsc:/opt/opscenter/conf/clusters/main.conf .- append the edited main.diff to the main.conf file
cat main.diff >> main.conf- replace the main.conf file in the image.
docker cp main.conf opsc:/opt/opscenter/conf/clusters- Restart the ospcenter node using docker.
docker restart opscAt this point, DSE is set up with the opscenter storage for the cluster "main" stored in the cluster "OPSCstore". To verify, a new keyspace will be created in the opscenter cluster called "OPSCstore" called "OpsCcenter_Storage_main".
- To get the IP address of the DataStax nodes:
export DSE_IP=$(docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' dse)export DSE_IP2=$(docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' dseops)export OPS_IP=$(docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' opsc)use echo $DSE_IP, echo $DSE_IP2 and echo $OPS_IP to view