Create PNDA cluster


With the target platform fully prepared, the PNDA software staged and the YAML configuration completed, the final step is to invoke the PNDA CLI to create the cluster.

Create PNDA

Install CLI dependencies

To use the PNDA command line interface, you will need to install the python, heat and nova clients. To install them on CentOS, run:

sudo yum install -y epel-release
sudo yum install -y python python-pip python-devel

cd cli
sudo pip install -r requirements.txt
sudo pip install jinja2 --upgrade

Keystone authentication

You must authenticate with Keystone before using the OpenStack clients.

The easiest way to accomplish this is to download the credentials file usually named from Horizon for the given user and tenant, then source it in the shell you will use to create PNDA.

. <project>

CLI invocation

The scripts allows to launch a PNDA deployment. It sits in the cli subdirectory.

cd cli
usage: [-h] [-y] [-e PNDA_CLUSTER] [-n DATANODES]
                   [-o OPENTSDB_NODES] [-k KAFKA_NODES] [-z ZK_NODES]
                   [-f {standard}] [-b BRANCH] [-s KEYPAIR]

In particular note that the -s option refers to the name of the key pair created in the OpenStack tenant during the preparation phase.

Make sure you have access to the private key of this key pair otherwise you will not be able to connect to the bastion node and access the cluster.

Important: ensure you are certain what version of PNDA you want to deploy, and specify the correct branch or tag when invoking the CLI using the -b option. In most circumstances you'll want to make sure the branch or tag you specify is identical to the branch or tag you used to build the PNDA mirror, and identical to the version you checked out from the pnda-heat-templates repository. All PNDA releases are designated with a tag such as release/4.0 across all repositories.

./ -e cation -n 3 -o 1 -k 2 -z 3 -f standard -s <existing keypair> -b <branch> create

In the above example we create a standard flavor PNDA named cation. We specify 3 data nodes, 1 opentsdb node, 2 kafka nodes, 3 zookeeper nodes

A small cluster typically takes around 20 minutes to fully provision while a larger cluster can take 40 minutes.


Home Prepare Mirror Build Stage Configure Create

results matching ""

    No results matching ""