Initial Login

To configure your Fuzzball cluster for use, you must first log in. This section will guide you through the process of creating a Fuzzball context and an admin context that you can use to authenticate to your cluster.

For simplicity, you should carry out these steps on the server node hosting Fuzzball orchestrate. You can follow a similar procedure to add contexts and access your Fuzzball cluster from other machines later.

Start by installing the Fuzzball CLI on your server node with the following commands:

# DEPOT_USER="" # populate with your username for CIQ Depot

# ACCESS_KEY="" # populate with the Depot key obtained from the CIQ sales/support team

# VERSION="3.0.9" # change to the proper version of Fuzzball as necessary

# dnf install -y https://depot.ciq.com/public/files/depot-client/depot/depot.x86_64.rpm

# depot register --user "${DEPOT_USER}" --token "${ACCESS_KEY}"

# depot enable fuzzball

# dnf install -y fuzzball-cli-${VERSION}-1

The minimal Fuzzball configuration used in this deployment guide causes Fuzzball to be hosted with a self-signed certificate. Since self-signed certificates are not trusted by default, you have to add Fuzzball’s root certificate to your system’s trust store to avoid validation errors with the commands shown below.

# kubectl get secret -n cert-manager root-ca-cert -o "jsonpath={.data['ca\.crt']}" | base64 --decode \
    >/etc/pki/ca-trust/source/anchors/fb_ca.crt

# update-ca-trust

The procedure to accept this self-signed certificate should be repeated on other systems that will access the Fuzzball cluster and differs depending on the operating system.

Now download and run the following script on your server node to view information about logging into your cluster:

# wget https://ciq-marketplace-assets.s3.us-east-1.amazonaws.com/public/fuzzball/scripts/deployment-info-wait.sh

# chmod +x deployment-info-wait.sh

# ./deployment-info-wait.sh

-------------------CLUSTER INFORMATION--------------------

Keycloak URL:     https://auth.10.1.96.99.nip.io/auth/realms/62c4aca0-7b38-4972-9300-7d17472a0fcc
Fuzzball API URL: https://api.10.1.96.99.nip.io
Fuzzball UI URL:  https://ui.10.1.96.99.nip.io
Fuzzball Admin UI URL: https://ui-admin.10.1.96.99.nip.io

Fuzzball admin account:
- username: user@domain.com
- password: fbpassword

Fuzzball cluster admin account:
- username: fuzzball-admin
- password: adminpassword

Keycloak admin account:
- username: keycloak
- password: keycloakpassword

To connect to Fuzzball:

$ fuzzball context create default api.10.1.96.99.nip.io https://auth.10.1.96.99.nip.io/auth/realms/62c4aca0-7b38-4972-9300-7d17472a0fcc fuzzball-cli
$ fuzzball context use default
$ fuzzball context login --direct

You will need to log in to the admin context to set the provisioner configuration. And you will need to log in to the regular Fuzzball context to check the configuration is working as expected and to manage entities.

Use the information displayed by the script to create a Fuzzball context and an admin context and to log into both. Using the example values above, the commands will look like the following. (Use the values that were returned to you by the deployment-info-wait.sh script instead of the example values demonstrated here.)

Note the single quotes around the passwords in the code block below. The default passwords set up by the Fuzzball CRD often have special characters that require single quotes.

# fuzzball context create default api.10.1.96.99.nip.io https://auth.10.1.96.99.nip.io/auth/realms/62c4aca0-7b38-4972-9300-7d17472a0fcc fuzzball-cli

# fuzzball admin context create admin api.10.1.96.149.nip.io

# fuzzball context login --direct -u user@domain.com -p 'fbpassword'

# fuzzball admin context login -u fuzzball-admin -p 'adminpassword'

The username and password for fuzzball context login --direct can also be provided more securely via the FUZZBALL_USER and FUZZBALL_PASSWORD environment variables. Now that you are logged into your Fuzzball cluster, you can proceed to creating an initial basic provisioner configuration.