Open a terminal session on your WANdisco Fusion node.

Download the relevant installer from customer.wandisco.com.

Make the downloaded installer file executable, e.g.

# chmod +x live-sentry-installer.<version>.sh Enter

Run the installer using an account with appropriate permissions:

# ./live-sentry-installer.<version>.sh Enter

Verifying archive integrity... All good.
Uncompressing WANdisco Live Sentry.......................................

    ::   ::  ::     #     #   ##    ####  ######   #   #####   #####   #####
   :::: :::: :::    #     #  #  #  ##  ## #     #  #  #     # #     # #     #
  ::::::::::: :::   #  #  # #    # #    # #     #  #  #       #       #     #
 ::::::::::::: :::  # # # # #    # #    # #     #  #   #####  #       #     #
  ::::::::::: :::   # # # # #    # #    # #     #  #        # #       #     #
   :::: :::: :::    ##   ##  #  ## #    # #     #  #  #     # #     # #     #
    ::   ::  ::     #     #   ## # #    # ######   #   #####   #####   #####

You are about to install WANdisco Live Sentry version 2.2.0.0

Do you want to continue with the installation? (Y/n) Y

Full installation of this plugin currently requires that the appropriate
'parcel' files are installed on your Cloudera Manager node.

This installer package includes all the currently supported parcels for this.

If you have not already done so, you should run this installer with the
'extract-parcel' sub-command and follow the instructions it gives. You may
wish to do this on the Cloudera Manager server itself.

Open a terminal session to the location of your parcels repository, it may be your Cloudera Manager server, although the location may have been customized. Ensure that you have suitable permissions for handling files.

Download the installer, as above, and run:

# ./live-sentry-installer.<version>.sh extract-parcel Enter

If you have not extracted this on the Cloudera Manager (CM) node, you should transfer the tarball to that server.

Perform the following steps on the CM node:
 * unpack the parcel tarball package
 * move the parcel and parcel.sha files to the local repository path for CM
 * use the CM UI to discover the location of the Custom Service Descriptors and copy the extracted CSD to this location
 * restart the cloudera-scm-server and cloudera-scm-agent services
 * using the CM parcel interface, ‘Check for New Parcels’ and then distribute and activate the LIVE_SENTRY service

If the parcel installation was successful, and you have not already done so, you should install the final Fusion UI plugin components on the fusion node(s).

For further guidance and clarifications, go to https://docs.wandisco.com/

Unpack the parcel tarball package, for example:

# tar xvzf LIVE_SENTRY-cdh-<version>_<version>.parcel.tar.gz Enter

Change the ownership of the .parcel and .parcel.sha files so that they match the system account that runs Cloudera Manager:

# chown cloudera-scm:cloudera-scm LIVE_SENTRY* Enter

Move the files into the server’s local repository, normally /opt/cloudera/parcel-repo.

On your Cloudera Manager UI, navigate to Settings → Custom Service Descriptors. Find the Local Repository Descriptor Path.

Copy the extracted Custom Service Descriptor file (LIVE_SENTRY-cdhxxx.jar) to the Local Descriptor Repository location.

Restart the cloudera-scm-server and cloudera-scm-agent services.

Open Cloudera Manager and navigate to the Parcels screen by clicking on the Parcel icon.

Click Check for New Parcels.

Figure 2. Check for parcels

The LIVE_SENTRY package is now ready to distribute. Click on the Distribute button to install LIVE_SENTRY from the parcel.

Figure 3. Distribute the parcel

Click on the Activate button to activate LIVE_SENTRY from the parcel.

Figure 4. Activate the parcel

Click Add service

Figure 5. Add Service

Choose LIVE SENTRY and click continue.

Figure 6. Choose Live Sentry

Choose hosts to install the service, at least one host is required. The host for the gateway can also be selected. If gateway is selected, it should be in the same node as where plugin will be installed.

Figure 7. Assign Roles

Configure the service parameters.

You can now see Live Sentry on the Cloudera Manager homepage.

Figure 8. View service on homepage

Open the Cloudera Manager Administration Console and access the Hive service configuration tab.

Select Scope  Hive (Service-Wide).

Locate the Sentry Service and ensure that sentry is enabled.

Locate the Hive Advanced Configuration Snippet (Safety Valve) for the sentry-site.xml property file and add the properties:

Locate the Server Name for Sentry Authorization for the hive.sentry.server property.

Add the same name in all Fusion-enabled zones for this property (i.e. sentry)

Save these changes.

Restart affected services.

Open the Cloudera Manager Administration Console and access the HDFS service configuration tab.

Select Scope  HDFS (Service-Wide).

Locate the Enable Sentry Synchronization property.

Enable Sentry synchronization.

Save these changes.

Restart affected services.

Open the Cloudera Manager Administration Console and access the Impala service configuration tab.

Select Scope  Impala (Service-Wide).

Locate the Sentry Service property and ensure that "sentry" is enabled.

Locate the Impala Service Advanced Configuration Snippet (Safety Valve) for the sentry-site.xml property file and add the properties:

Save these changes.

Restart affected services.

Open the Cloudera Manager Administration Console and access the Solr service configuration tab.

Select Scope  Solr (Service-Wide).

Locate the Sentry Service property and ensure that "sentry" is enabled.

Locate the Solr Service Advanced Configuration Snippet (Safety Valve) for the sentry-site.xml property file and add the properties:

Save these changes.

Restart affected services.

Open the Cloudera Manager Administration Console and access the Hue service configuration tab.

Select Scope  Hue (Service-Wide).

Locate the Sentry Service property and ensure that "sentry" is enabled.

Locate the Hue Service Advanced Configuration Snippet (Safety Valve) for the hue_safety_value.ini property file and add the properties:

[libsentry]
  hostname={wd.sentry.proxy.thrift.host}
  port={wd.sentry.proxy.thrift.port}

Location the Hue Service Advanced Configuration Snippet (Safety Valve) for the sentry-site.xml property file and add the properties:

Save these changes.

Restart affected services.

On the Replication tab, click on All Sentry Rules.

On the Status tab you can see the results of the previous consistency check. Click Check now to trigger a new check.

The results of the consistency check will now be displayed, the bars will turn yellow if the result is inconsistent. A more detailed report can also be downloaded.

Select the zone which you want to be the Source of Truth by clicking on the relevant graph.

Now click Make Consistent.

The zones are now consistent, depending on the option selected. You can run another consistency check to show this if required.