Single Node CDP PVC-Base Cluster
This script automatically sets up a CDP PVC-Base (aka CDP Data Center) Trial cluster on the public cloud on a single VM with the services preconfigured in a template file. It supports both clusters with or without kerberos.
This cluster is meant to be used for demos, experimenting, training, and workshops so it is only one node and does not have TLS enabled.
Instructions
Below are instructions for creating the cluster with or without CDSW service. CDSW requires some extra resources (more powerful instance, and a secondary disk for the docker device).
Provisioning Cluster without CDSW
- Create a Centos 7 VM with at least 8 vCPUs/ 32 GB RAM. Choose the plain vanilla Centos image, not a cloudera-centos image.
- OS disk size: at least 50 GB.
Provisioning Cluster with CDSW
- Create a Centos 7 VM with at least 16 vCPUs/ 64 GB RAM. Choose the plain vanilla Centos image, not a cloudera-centos image.
- OS disk size: at least 100 GB.
- Docker device disk: at least 200GB SSD disk.
- Note: you need a fast disk more than you need a large disk: aim for a disk with 3000 IOPS. This might mean choosing a 1TB disk.
Provisioning Cluster with Trial parcels
Currently, there is no automation process to download parcels for services such as Schema Registry. You need to download the required files from the official Cloudera website on your laptop. Then, sftp the .parcel, .sha and .jar files into the /home/centos or /root directory. The script takes care of placing these files into the correct folders during installation.
For example, you can install Schema Registry once your host looks like the below:
$ ls -l /root/
-rwxr-xr-x. 1 centos centos 148855790 Aug 5 18:41 SCHEMAREGISTRY-0.7.0.1.0.0.0-11-el7.parcel
-rw-r--r--. 1 centos centos 41 Aug 5 18:41 SCHEMAREGISTRY-0.7.0.1.0.0.0-11-el7.parcel.sha
-rwxr-xr-x. 1 centos centos 14525 Aug 5 18:41 SCHEMAREGISTRY-0.7.0.jar
To install Schema Registry, you must use an appropriate template file, like all.json.
Configuration and installation
- If you created the VM on Azure and need to resize the OS disk, here are the instructions.
- add 2 inbound rules to the Security Group:
- to allow your IP only, for all ports.
- to allow the VM's own IP, for all ports.
- ssh into VM and copy this repo.
sudo su -
yum install -y git
git clone https://github.com/fabiog1901/SingleNodeCDPCluster.git
cd SingleNodeCDPCluster
The script setup.sh takes 3 arguments:
- the cloud provider name:
aws,azure,gcp. - the template file.
- OPTIONAL the Docker Device disk mount point.
Example: create cluster without CDSW on AWS using default_template.json
$ ./setup.sh aws templates/base.json
Example: create cluster with CDSW on Azure using cdsw_template.json
$ ./setup.sh azure templates/iot_workshop.json /dev/sdc
Wait until the script finishes, check for any error.
Use
Once the script returns, you can open Cloudera Manager at http://<public-IP>:7180
Wait for about 20-30 mins for CDSW to be ready. You can monitor the status of CDSW by issuing the cdsw status command.
You can use kubectl get pods -n kube-system to check if all the pods that the role Master is suppose to start have really started.
You can also check the CDSW deployment status on CM > CDSW service > Instances > Master role > Processes > stdout.
Docker device
To find out what the docker device mount point is, use lsblk. See below examples:
AWS, using a M5.2xlarge or M5.4xlarge
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:1 0 100G 0 disk
+-nvme0n1p1 259:2 0 100G 0 part /
nvme1n1 259:0 0 1000G 0 disk
$ ./setup.sh aws templates/iot_workshop.json /dev/nvme1n1
Azure Standard D8s v3 or Standard D16s v3
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
sda 8:0 0 30G 0 disk
+-sda1 8:1 0 500M 0 part /boot
+-sda2 8:2 0 29.5G 0 part /
sdb 8:16 0 56G 0 disk
+-sdb1 8:17 0 56G 0 part /mnt/resource
sdc 8:32 0 1000G 0 disk
sr0 11:0 1 628K 0 rom
$ ./setup.sh azure templates/iot_workshop.json /dev/sdc
GCP n1-standard-8 or n1-standard-16
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 100G 0 disk
└─sda1 8:1 0 100G 0 part /
sdb 8:16 0 1000G 0 disk
$ ./setup.sh gcp templates/iot_workshop.json /dev/sdb