Accessing a cluster
The following section describes how to access the various services in the cluster.
Cloudbreak user accounts
The following table describes what credentials to use to access Cloudbreak and Cloudbreak-managed clusters:
|Cloudbreak||Web UI, CLI||Access with the username and password provided when launching Cloudbreak on the cloud provider.|
|Cloudbreak||SSH to VM||Access as the "cloudbreak" user with the SSH key provided when launching Cloudbreak on the cloud provider.|
|Cluster||SSH to VMs||Access as the "cloudbreak" user with the SSH key provided during cluster creation.|
|Cluster||Ambari web UI||Access with the credentials provided in the “Cluster User” parameter during cluster creation.|
|Cluster||Web UIs for specific cluster services||Access with the credentials provided in the “Cluster User” parameter during cluster creation.|
Finding cluster information in the web UI
Once your cluster is up and running, click on the tile representing your cluster in the Cloudbreak UI to access information related the cluster and access cluster actions.
The information presented includes:
- Access cluster actions such as resize and sync by clicking on ACTIONS.
- Access Ambari web UI by clicking on the link in the CLUSTER INFORMATION section.
- View public IP addresses for all cluster instances in the HARDWARE section. Click on the links to view the instances in the cloud console.
- The SSH user that you must use when accessing cluster VMs is "cloudbreak".
The summary bar includes the following information about your cluster:
|Cluster Name||The name that you selected for your cluster is displayed at the top of the page. Below it is the name of the cluster blueprint.|
|Time Remaining||If you enabled lifetime management for your cluster, the clock next to the cluster name indicates the amount of time that your cluster will run before it gets terminated. Note that the time remaining counter does not stop when you stop the cluster.|
|Cloud Provider||The logo of the cloud provider on which the cluster is running.|
|Credential||The name of the credential used to create the cluster.|
|Status||Current status. When a cluster is healthy, the status is Running.|
|Nodes||The current number of cluster nodes, including the master node.|
|Uptime||The amount of time (HH:MM) that the cluster has been in the running state since it was started. Each time you stop and restart the cluster, the running time is reset to 0.|
|Created||The date when the cluster was created. The date format is Mon DD, YYYY. For example: Oct 27, 2017.|
The following information is available on the cluster details page:
|Cluster User||The name of the cluster user that you created when creating the cluster.|
|SSH Username||The SSH user which you must use when accessing cluster VMs via SSH. The SSH user is always "cloudbreak".|
|Ambari URL||Link to the Ambari web UI.|
|Region||The region in which the cluster is running in the cloud provider infrastructure.|
|Availability Zone||The availability zone within the region in which the cluster is running.|
|Blueprint||The name of the blueprint selected under "Cluster Type" to create this cluster.|
|Created With||The version of Cloudbreak used to create this cluster.|
|Ambari Version||The Ambari version which this cluster is currently running.|
|HDP/HDF Version||The HDP or HDF version which this cluster is currently running.|
|Authentication Source||If you are using an external authentication source (LDAP/AD) for your cluster, you can see it here. Refer to Using an external authentication source.|
Below this, you will see additional tabs that you can click on in order to see their content:
|Hardware||This section includes information about your cluster instances: instance names, instance IDs, instance types, their status, fully qualified domain names (FQDNs), and private and public IPs.|
|Cloud storage||If you configured any cloud storage options, you will see them listed here.|
|Tags||This section lists keys and values of the user-defined tags, in the same order as you added them.|
|Gateway||This section is available when gateway is configured for a cluster. It includes the gateway URL to Ambari and the URLs for the service UIs.|
|Recipes||This section includes recipe-related information. For each recipe, you can see the host group on which a recipe was executed, recipe name, and recipe type. Refer to Using custom scripts (recipes).|
|External databases||If you are using an external database for your cluster, you can see it here. Refer to using an external database.|
|Repository details||This section includes Ambari and HDP/HDF repository information, as you provided it in the "Base Images" section when creating a cluster.|
|Image details||This section includes information about the base image that was used for the Cloudbreak instance.|
|Network||This section includes information about the names of the network and subnet in which the cluster is running and the links to related cloud provider console.|
|Security||This section is only available if you have enabled Kerberos security. It provides you with the details of your Kerberos configuration.|
|Autoscaling||This section includes configuration options related to autoscaling. Refer to Configuring autoscaling.|
The Event History section shows you events logged for the cluster, with the most recent event at the top. For example, after your cluster has been created, the following messages will be written to the log:
Ambari cluster built; Ambari ip:188.8.131.52 10/26/2017, 9:41:58 AM Building Ambari cluster; Ambari ip:184.108.40.206 10/26/2017, 9:30:20 AM Starting Ambari cluster services 10/26/2017, 9:27:12 AM Setting up infrastructure metadata 10/26/2017, 9:27:11 AM Bootstrapping infrastructure cluster 10/26/2017, 9:26:38 AM Infrastructure successfully provisioned 10/26/2017, 9:26:37 AM Billing started, Infrastructure successfully provisioned 10/26/2017, 9:26:37 AM Infrastructure metadata collection finished 10/26/2017, 9:25:39 AM Infrastructure creation took 194 seconds 10/26/2017, 9:25:37 AM Creating infrastructure 10/26/2017, 9:22:22 AM Setting up HDP image 10/26/2017, 9:22:21 AM
Accessing cluster via SSH
If you plan to access the cluster via the command line clients, SSH into the master node instance in the cluster.
- In order to use SSH, you must generate an SSH key pair or use an existing SSH key pair.
- You can find the cluster instance public IP addresses on the cluster details page.
- When accessing instances via SSH use the
On Mac OS, you can use the following syntax to SSH to the VM:
ssh -i "privatekey.pem" cloudbreak@publicIPFor example:
ssh -i "dominika-kp.pem" firstname.lastname@example.org
On Windows, you can SSH using an SSH client such as PuTTY.
You can access Ambari web UI by clicking on the links provided in the Cluster Information > Ambari URL.
From the cluster dashboard, click on the tile representing your cluster to navigate to cluster details.
Find the Ambari URL in the Cluster Information section. This URL is available once the Ambari cluster creation process has completed.
Click on the Ambari URL link.
The first time you access the server, your browser will attempt to confirm that the SSL Certificate is valid. Since Cloudbreak automatically generates a self-signed certificate, your browser will warn you about an Untrusted Connection and ask you to confirm a Security Exception. Depending on your browser, perform the steps below to proceed.
Browser Steps Firefox Click Advanced > Click Add Exception... > Click Confirm Security Exception Safari Click Continue Chrome Click Advanced > Click Proceed...
View cluster blueprints
Cloudbreak includes a useful option to view blueprints of a future cluster (from the create cluster wizard) or an existing cluster (from cluster details):
To view a cluster blueprint from the create cluster wizard, on the last page of the wizard, select Show blueprint.
To view a cluster blueprint for an existing cluster, navigate to cluster details, and from the ACTIONS menu, select Show blueprint.