Deploying the Notifications Component on a Standalone Node

This documentation provides the steps needed to deploy ad-notifications as a standalone add-on.

Prerequisites

Ensure the following criteria are met:

• You are using “Pulse 3.5.0 or higher” or “Pulse 3.4.3 or higher”.
• You have already deployed ad-alerts.
• You have not deployed ad-notifications. If this is already installed, uninstall it using accelo deploy add-ons and unselect Notifications.
• You have already configured the standalone node.

Deploy ad-notifications as a Standalone add-on

Follow the steps listed below to successfully deploy ad-notifications as a standalone add-on.

1. On a standalone node, run the following command to generate ad-notifications.yml if it doesn’t exist. Also, ensure to update the values for the EMAIL_SMTP_* environment variables. If Notifications is already deployed and ad-notifications.yml does exist under $AcceloHome/config/docker/addons on the node where it was previously deployed, copy it over to the same location i.e. $AcceloHome/config/docker/addons on the standalone node.

accelo admin makeconfig ad-notifications

Open the file in a text editor and make changes to the value of the following fields.

• DB_URI: Set it to the value of the environment variable MONGO_URI, which by default, is encrypted.
• DIRECTOR_HOST: Set it to the hostname of the node where the ad-director will be deployed.
• DIRECTOR_PORT: Set it to 19016.

[root@plat03:addons (ad-default)]$ diff -y --suppress-common-lines ad-notifications.yml.orig ad-notifications.yml

    - DB_URI=ZN4v8cuUTXYvdnDJIDp+R8Z+ZsVXXjv8zDOvh8UwQXosC8vf |     - DB_URI=ZN4v8cuUTXYvdnDJIDp+R8Z+ZsVXXjv8zDOvh8UwQXrMzwQK

    - DIRECTOR_HOST=ad-director             |     - DIRECTOR_HOST=plat03.acceldata.dvl

    - DIRECTOR_PORT=8000              |     - DIRECTOR_PORT=19016

2. On the core node, back up $AcceloHome/config/acceldata_<cluster_name>.conf. Open the file in a text editor and navigate to the following section.

# General dependencies are expressed as accessible service url's. Spark, Yarn,

# ATS, Hive Metastore, Spark and Webhdfs urls are required.

# At this point in time, AccelData does not support compression by default.

group {

  name = "odp_zoro"

  displayName = "odp_zoro"

  originalName = "ODP_Zoro"

  distroType = "HWX"

  onprem = true

  active = true

  priority = 1000

  connections = {

    mongo = [

    ........

Under connections, make the following changes:

• mongo:

  • uri: Change its value for all Mongo connections to the value of ALERTS_DB_URI, whose value you have changed in the previous step.

• elastic:

  • host: Change its value from ad-elastic to the host/hosts where Logsearch is deployed.

- port: Change its value to 19013.

• Vm:
  • readURL: In this field, replace the following details:
    • ad-vmselect with a hostname of the node where core services are deployed.
    • 8481 with 19042.

Save your changes. If done correctly, the following changes appear on the screen.

[root@plat01:config (ad-default)]$ diff -y --suppress-common-lines acceldata_odp_zoro.conf.orig acceldata_odp_zoro.conf

        uri = "ZN4v8cuUTXYvdnDJIDp+R8Z+ZsVXXjv8zDOvh8UwQXosC8 |         uri = "ZN4v8cuUTXYvdnDJIDp+R8Z+ZsVXXjv8zDOvh8UwQXrMzw

        uri = "ZN4v8cuUTXYvdnDJIDp+R8Z+ZsVXXjv8zDOvh8UwQXosC8 |         uri = "ZN4v8cuUTXYvdnDJIDp+R8Z+ZsVXXjv8zDOvh8UwQXrMzw

        host = "ad-elastic"             |         host = "plat01.acceldata.dvl"

        port = 9200                           |         port = 19013

        host = "ad-elastic"             |         host = "plat01.acceldata.dvl"

        port = 9200                           |         port = 19013

        host = "ad-elastic"             |         host = "plat01.acceldata.dvl"

        port = 9200                           |         port = 19013

        readURL = "http://ad-vmselect:8481/select/1385609323/ |         readURL = "http://plat01.acceldata.dvl:19042/select/1

3. Run the following command to push the configuration.

accelo admin database push-config -a

4. On the standalone node where ad-alerts is deployed, run the following command to generate ad-alerts.yml if it doesn’t exist.

accelo restart ad-alerts

Open the file in a text editor and make changes to the value of the following fields.

• NOTIFICATIONS_HOST: Set it to the node's hostname where ad-notifications is deployed.

If done correctly, the following changes appear on the screen.

[root@plat03:addons (ad-default)]$ diff -y --suppress-common-lines ad-alerts.yml.original ad-alerts.yml

    - NOTIFICATIONS_HOST=ad-notifications         |     - NOTIFICATIONS_HOST=plat01.acceldata.dvl

Run the following command to restart ad-alerts

Run the following command to restart ad-alerts.

accelo restart ad-alerts

5. On the standalone node where ad-director is deployed, run the following command to generate ad-director.yml if it doesn’t exist.

accelo admin makeconfig ad-director

Open the file in a text editor and make changes to the value of the following fields.

• NOTIFICATIONS_HOST: Set it to the node's hostname where ad-notifications is deployed.

If done correctly, the following details appear on the screen.

[root@plat03:addons (ad-default)]$ diff -y --suppress-common-lines ad-director.yml.original ad-director.yml

    - NOTIFICATIONS_HOST=ad-notifications         |     - NOTIFICATIONS_HOST=plat01.acceldata.dvl

Run the following command to restart the ad-director.

accelo restart ad-director

6. On the standalone node, run the following command and select Notifications.

accelo deploy addons