Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/oracle-quickstart/oci-datastax

Terraform module to deploy DataStax Enterprise (DSE) on Oracle Cloud Infrastructure (OCI)
https://github.com/oracle-quickstart/oci-datastax

cassandra cloud datastax datastax-enterprise dse nosql oci oracle partner-led terraform

Last synced: 29 days ago
JSON representation

Terraform module to deploy DataStax Enterprise (DSE) on Oracle Cloud Infrastructure (OCI)

Awesome Lists containing this project

README 

        
# oci-datastax

These are Terraform modules that deploy [DataStax Enterprise (DSE)](https://www.datastax.com/products/datastax-enterprise) on [Oracle Cloud Infrastructure (OCI)](https://cloud.oracle.com/en_US/cloud-infrastructure).  They are developed jointly by Oracle and DataStax.



## Resource Manager Deployment



This Quick Start uses [OCI Resource Manager](https://docs.cloud.oracle.com/iaas/Content/ResourceManager/Concepts/resourcemanager.htm) to make deployment easy, sign up for an [OCI account](https://cloud.oracle.com/en_US/tryit) if you don't have one, and just click the button below:



[![Deploy to Oracle Cloud](https://oci-resourcemanager-plugin.plugins.oci.oraclecloud.com/latest/deploy-to-oracle-cloud.svg)](https://cloud.oracle.com/resourcemanager/stacks/create?region=home&zipUrl=https://github.com/oracle-quickstart/oci-datastax/archive/master.zip)



After logging into the console you'll walk through the selection of variables for

the deployment. You'll then select `Terraform Actions -> Apply` on the stack created, and be able

to see the progress of resource creation in the logs in the console. Once that's

complete follow the instructions in the [Login to DataStax Lifecycle Manager ](#login-to-datastax-lifecycle-manager)

section below. Note, these templates generate an ssh key pair on the fly for

LCM -> node connections. The private key is in the terraform state file, therefore

treat it as a secret.



Note, if you fork this repo you'll need to change the link for the button to point at your repo.



## Local Development



If you prefer to develop locally, ie by running the `terraform` command

you'll need to do some pre deploy setup. That's all detailed [here](https://github.com/oracle/oci-quickstart-prerequisites).



Now, you'll want a local copy of this repo.  You can make that with the commands:



    git clone https://github.com/oracle-quickstart/oci-datastax.git

    cd oci-datastax

    ls



![](./images/01%20-%20git%20clone.png)



You need to rename `provider.tf.cli -> provider.tf`. This is because

authentication works slightly differently in ORM vs the CLI.



We now need to initialize the directory with the module in it.  This makes the module aware of the OCI provider.  You can do this by running:



    terraform init



This gives the following output:



![](./images/02%20-%20terraform%20init.png)



## Deploy

Now for the main attraction.  Let's make sure the plan looks good:



    terraform plan



That gives:



![](./images/03%20-%20terraform%20plan.png)



If that's good, we can go ahead and apply the deploy:



    terraform apply



You'll need to enter a password shared by the `cassandra` user and OpsCenter `admin` user,

and then `yes` when prompted.  The apply should take about five minutes to run.  

Once complete, you'll see something like this:



![](./images/04%20-%20terraform%20apply.png)



When the apply is complete, the infrastructure will be deployed, but cloud-init scripts will still be running.  Those will wrap up asynchronously.  OpsCenter and Lifecycle Manager (LCM) will probably be up five minutes after you run apply.  The cluster might take another ten minutes to build after that.  Now is a good time to get a coffee.



## Login to DataStax Lifecycle Manager

When the `terraform apply` completed, it printed out the URLs for OpsCenter and LCM.  Let's check out LCM first.  Open a browser to the URL from the output.  



![](./images/05%20-%20warning.png)



The username is `admin` and the password is whatever you specified in [variables.tf](simple/variables.tf).



![](./images/06%20-%20login.png)



In this case, the job isn't done yet.  If we drill down on clusters we can see that the nodes have been added but LCM hasn't yet SSH'd into them to install DSE.



![](./images/07%20-%20cluster.png)



Similarly, if we check out the job, we see it hasn't run yet.



![](./images/08%20-%20job.png)



Checking back a few minutes later, we see the job is complete!



![](./images/09%20-%20job%20done.png)



## Login to DataStax OpsCenter

Now that the LCM job is all done, let's take a look at OpsCenter.  Open up a browser to that URL.  It was printed as output when `terraform apply` completed.



![](./images/10%20-%20opscenter.png)



If everything ran ok, you should see a ring with the number of nodes you specified in [variables.tf](simple/variables.tf).



## View the Cluster in the Console

You can also login to the web console [here](https://console.us-phoenix-1.oraclecloud.com/a/compute/instances) to view the IaaS that is running the cluster.



![](./images/11%20-%20console.png)



## SSH to a Node

These machines are using Ubuntu 16.  The default login is ubuntu.  You can SSH into the machine with a command like this:



    ssh -i ~/.ssh/oci ubuntu@



You can debug deployments by investigating the cloud-init log file `/var/log/cloud-init-output.log`.



If you want to get started interacting with the database you can run `cqlsh` with the default user `cassandra` and whatever password you chose when prompted.  For instance:



    cqlsh -u cassandra -p 



This gives:



![](./images/12%20-%20cqlsh.png)



## Destroy the Deployment

When you no longer need the DSE cluster, you can run this to delete the deployment:



    terraform destroy



You'll need to enter `yes` when prompted.  Once complete, you'll see something like this:



![](./images/13%20-%20terraform%20destroy.png)