Cluster configuration

Now we are ready to create and configure our first cluster with Jumbo!

Cluster creation and Jumbo context

First, lets enter the Jumbo shell and create our cluster:

[user@computer:~]$ jumboJumbo v0.4.1
jumbo > create myclusterCreating mycluster...
Cluster "mycluster" created (domain name = "mycluster.local").
jumbo (mycluster) >

After creating a cluster, the Jumbo context is set to this cluster. You can see the name of the cluster loaded (jumbo (mycluster) >). Use exit to reset the context, and then use to set the context to an existing cluster:

jumbo (mycluster) > exitjumbo > use anotherclusterLoading anothercluster...
Cluster "anothercluster" loaded.
jumbo (anothercluster) > 

If you are in a hurry, use templates

When creating a cluster, you can reference a template. The cluster will then be configured in one second:

jumbo > create mycluster --template small-fullCreating mycluster...
Cluster "mycluster" created (domain name = "mycluster.local").
jumbo (mycluster) > listnodes+----------+--------------------+-------------+----------+------+
|   Name   |       Types        |      IP     | RAM (MB) | CPUs |
+----------+--------------------+-------------+----------+------+
|  edge01  |        edge        | 10.10.10.10 |   1024   |  1   |
| master01 | master, sidemaster | 10.10.10.11 |   3072   |  1   |
| worker01 |       worker       | 10.10.10.21 |   4096   |  2   |
+----------+--------------------+-------------+----------+------+

If this is your first time using Jumbo, we recommend following this tutorial to learn everything you need to know, but you can jump straight to Cluster provisioning from here.
See the list of available templates on the Github repo (templates/docs).

Virtual machine creation

Now that we have created our cluster, lets add 3 virtual machines to it:

jumbo (mycluster) > addnode master --types master --ip 10.10.10.11 --ram 2048Machine "master" added to cluster "mycluster".
jumbo (mycluster) > addnode smaster -t sidemaster -t edgeIP: 10.10.10.12
RAM (MB): 3072
Machine "smaster" added to cluster "mycluster".
jumbo (mycluster) > addnode worker -t worker --cpus 2IP: 10.10.10.13
RAM (MB): 3072
Machine "worker" added to cluster "mycluster".

We now have all the nodes needed to deploy a functional Hadoop cluster. Use listnodes to see details about the nodes of the cluster:

jumbo (mycluster) > listnodes+---------+------------------+-------------+----------+------+
|   Name  |      Types       |      IP     | RAM (MB) | CPUs |
+---------+------------------+-------------+----------+------+
|  master |      master      | 10.10.10.11 |   2048   |  1   |
| smaster | sidemaster, edge | 10.10.10.12 |   3072   |  1   |
|  worker |      worker      | 10.10.10.13 |   3072   |  2   |
+---------+------------------+-------------+----------+------+

Service installation

A service can have dependencies to other services. A dependency is satisfied if the required service is installed and if the minimum required number for each component is installed. If the requirements to install a service are not met, Jumbo will tell you what services or components you have to install:

jumbo (mycluster) > addservice AMBARIThe requirements to add the service "AMBARI" are not met!
These services are missing:
 - ANSIBLE,
 - POSTGRESQL
jumbo (mycluster) > addservice ANSIBLEService "ANSIBLE" and related clients added to cluster "mycluster".
1 type of component auto-installed. Use "listcomponents -a" for details.

You can let Jumbo install all the dependencies with the tag --recursive:

jumbo (mycluster) > addservice AMBARI --recursiveThe service AMBARI and its dependencies will be installed. Dependencies:
Services:
 - POSTGRESQL

Do you want to continue? [y/N]: y
Service "AMBARI" and related clients added to cluster "mycluster".
Auto-installed the dependencies:
Services:
 - POSTGRESQL
2 type of component auto-installed. Use "listcomponents -a" for details.

When installing a service, all its components are auto-installed on the best fitting hosts by default. You can avoid the auto-installation with the flag --no-auto.

Note that the service's clients will always be installed on all hosts (even with --no-auto) and on nodes created after the service installation. However you can use rmcomponent to delete them individually afterward.

A list of all the services supported by Jumbo is available here.

Component installation

If you choose to not auto-install the components with the flag --no-auto, you have to manually add components with addcomponent on the machines of your choice. Use the command checkservice to see what components are missing for the service to be complete:

jumbo (mycluster) > checkservice HDFSThe service "HDFS" misses:
 - 1 DATANODE
jumbo (mycluster) > addcomponent DATANODE -m workerComponent "DATANODE" added to machine "mycluster/worker".

Installation of all Hadoop services and components

We have to reproduce the same procedure of installation for the following services and components:

Remove items

Use the commands rmnode, rmservice, or rmcomponent to remove items.

See what have been installed

Jumbo has list commands to describe the cluster state:

• listclusters to list all the clusters and the services installed on each of them;
• listnodes to list the VMs and their configurations;
• listservices to list the status of each service installed on a cluster (complete or not);
• listcomponents to list the components installed on a machine.