Using the Administrator Role in Ambari Web

An Ambari-level Administrator can access the Ambari Admin page using the default, admin/admin credentials. Use the Ambari Admin page to perform the following tasks.

Log In to Ambari as administrator

After installing Ambari, you can log in to Ambari as administrator using the default credentials: username/password = admin/admin

About this task

An Ambari administrator accesses Ambari Server, using a web browser to display the Ambari Admin web page.

Procedure

1. To access the Ambari Admin page, enter the following URL in a web browser: http://[YOUR_AMBARI_SERVER_FQDN]:8080

[YOUR_AMBARI_SERVER_FQDN] is the fully qualified domain name of your Ambari Server host and 8080 is the default HTTP port.

2. Enter your credentials. username/password = admin/admin

Results

The Ambari Admin page displays.

What to do next

If required, change the admin password.

Using the Ambari Admin Pages

Use the Ambari Admin page to create new clusters, register remote clusters, deploy views, and manage users and groups.

When you first log in to Ambari as an administrator, Ambari Admin > Cluster Management > Cluster Information page displays the Launch Install Wizard option. Click Launch Install Wizard to deploy an Ambari-managed, cluster.

Other Ambari Admin options include:

• Dashboard will provide access to Ambari Admin operations options.
• Cluster Information initially provides the option to install a cluster.
• Remote Clusters provides the option to register an existing (remote) cluster with this instance of Ambari server.
• Users provides options for you to create and edit users and group those users.

After you create a cluster, the Dashboard option displays. Use the Dashboard option to operate an Ambari-manged cluster. From Dashboard, you can manage and monitor cluster services, including managing the service life cycle, changing configurations, reviewing alerts, and so on.

After you create a cluster, the Ambari Admin > Cluster Management > Cluster Information page displays the cluster name and blueprint information for the cluster you just created. You can export (download) the Ambari blueprint.

Versions displays current component version information, and the option to register versions stored in specific repositories.

Create a Cluster

After you have successfully installed Ambari, you can create a cluster by using the Ambari cluster install wizard.

Procedure

• In the Ambari Admin page, click LAUNCH INSTALL WIZARD.

What to do next

Complete all steps in the cluster install wizard.

Related Information

Installing, Configuring, and Deploying a Cluster

Changing the Admin Password

Using the Ambari Admin page, you can change the password for the default admin user to create a unique administrator credential for your system.

Procedure

1. In Admin/Users, for a listed Ambari Administrator user, click Actions > Edit.
2. In Users/[USERNAME], click CHANGE PASSWORD.
3. Click Change Password.
4. In Change Password for [USERNAME], type the current password and then your new password, twice.
5. Click OK.

Changing JDK

During your initial Ambari Server Setup, you select the JDK to use or provide a path to a custom JDK already installed on your hosts. After setting up your cluster, you may change the JDK version.

About this task

Acceldata ODP 3.x platforms support both Oracle JDK 8 and Open JDK 8 versions. ODP does not bundle either JDK libraries but certify ODP components using both Oracle and Open JDK libraries.

To change the JDK implementation for an existing cluster:

Procedure

1. On the Ambari Server host, re-run Ambari Server Setup. ambari-server setup
2. At the prompt: change the JDK ?, Enter y.
3. At the prompt: Do you want to change Oracle JDK [y/n] (n)?, Enter y.
4. At the prompt:choose a JDK:, Enter 2 to change the JDK implementation.

Important

If you use a custom JDK, AND if Kerberos is enabled with AES-256 encryption you must also update your JCE security policy files on the Ambari Server and all hosts in the cluster to match the new JDK version. If you are running Kerberos and do not update the JCE to match the JDK, you will have issues starting services.

What to do next

After setup completes, you must restart each component for the new JDK to be used by the Hadoop services. Using the Ambari Web UI, do the following tasks:

1. Restart Ambari Server. ambari-server restart
2. Log in to the Ambari Server and restart all cluster services.

Important

If, after changing the JDK, you experience issues with communication between Ambari Server and Ambari Agents, refer to Java/Python updates and Ambari Agent TLS settings in Acceldata Community Connection for more information.

Additionally if customer certificates were imported into the previous JDK’s cacerts trust store, they need to be re-imported into the new JDK’s >cacerts >trust store.

Renaming a Cluster

After you create a cluster, you can give it a new name.

Procedure

1. On the Ambari Admin page, in Cluster Information > Cluster Name*, enter up to 80 alphanumeric characters to rename your cluster.

Note If you plan to Kerberize the cluster, consider limiting the cluster name (12 characters or less), to accommodate the fact that Kerberos >principals will be appended to the cluster name string and that some identity providers impose a > limit on the total principal name length.

2. Click Save.
3. Confirm.
4. Optional step(s)

a) IF you are running Ranger: Edit each service name to match the new cluster name.

If you do not rename each service to include the new cluster name, Ranger automatically creates a new repository using the new cluster name that contains only the default policies. In this case, to recover your original data, export the customized service policy repository, and then import that repository to overwrite the default policy list generated by Ranger. See Importing and Exporting Resource-based policies for more detailed import and export steps.

b) IF your cluster is Kerberos-enabled: Regenerate keytabs. Note: Regenerating keytabs will incur cluster downtime.

5. Restart Ambari server and the Ambari agents.

After renaming the cluster, alert checks must be re-queued on the agents. Therefore, you must restart Ambari Server and the Ambari Agents for the change to take effect.

6. Adjust any API calls you make to use the new name.

Changing the name of the cluster changes the name of the Ambari REST API resource for the cluster.

Registering a Remote Cluster

Ambari-managed clusters not local to your Ambari server host must be registered as remote clusters with your Ambari Server.

About this task

You might work with clusters that are managed by Ambari but are not local to your Ambari server. These clusters are considered remote with respect to your local Ambari server. They are managed by a remote Ambari server. If you plan to run a standalone server to host views, including accessing clusters managed by a different Ambari server, you can register the cluster managed by the standalone Ambari server as a remote cluster. After you register a remote cluster, use it to configure view instances.

Procedure

1. In Ambari Admin > Remote Clusters, click Register Remote Cluster.
2. In Remote Clusters/Register, enter a name for the remote cluster, the Ambari cluster URL, and a cluster username and associated password.
3. Click Save.

Results

The remote cluster is now available for configuring View instances.