Tab 2

Deploy Notifications Service on a Separate Node

This topic describes how to deploy ad-notifications as a standalone add-on on a separate node.

Prerequisites

Before deploying ad-notifications, ensure that the following requirements are met:

• You are using Pulse 3.5.0 or later, or Pulse 3.4.3 or later.
• ad-alerts is already deployed.
• ad-notifications is not currently deployed. If it is already deployed, run accelo deploy addons and unselect Notifications to uninstall it.
• The standalone node is configured and ready for deployment.

Deploy ad-notifications as a Standalone Add-on

Follow these steps to deploy ad-notifications as a standalone add-on.

1. Configure ad-notifications

On the standalone node, run the following command to generate ad-notifications.yml if the file does not already exist:

accelo admin makeconfig ad-notifications

$AcceloHome/config/docker/addons

$AcceloHome/config/docker/addons

Open ad-notifications.yml in a text editor and update the required EMAIL_SMTP_* environment variables.

Additionally, update the following fields:

• DB_URI: Set it to the value of the MONGO_URI environment variable. By default, this value is encrypted.
• DIRECTOR_HOST: Set it to the hostname of the node where ad-director is deployed.
• DIRECTOR_PORT: Set it to 19016.
• NATS_SERVER_HOST_LIST: Set it to <Pulse_Node_IP_or_hostname>:19009.

For example:
[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
- NATS_SERVER_HOST_LIST=<existing_value>                | - NATS_SERVER_HOST_LIST=<Pulse_Node_IP_or_hostname>:19009

Save the changes.

2. Update the Cluster Configuration

On the core node, back up the following cluster configuration file:

$AcceloHome/config/acceldata_<cluster_name>.conf

Open the file in a text editor and locate the connections section under the corresponding cluster group.

For example:
# 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, update the following configurations.

Mongo

For all Mongo connections:

• uri: Change its value to the required Alerts database URI.

Elastic

For each applicable Elastic connection:

• host: Change the value from ad-elastic to the hostname of the node where Log Search is deployed.
• port: Change the value from 9200 to 19013.

VM

For readURL, make the following changes:

• Replace ad-vmselect with the hostname of the node where the core services are deployed.
• Replace port 8481 with 19042.

Save the changes.

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

uri = "<existing_value>"                        | uri = "<updated_value>"
uri = "<existing_value>"                        | uri = "<updated_value>"

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/..."  | readURL = "http://plat01.acceldata.dvl:19042/select/..."

3. Push the Configuration

On the core node, run the following command to push the updated configuration:

accelo admin database push-config -a

4. Configure ad-alerts

On the standalone node where ad-alerts is deployed, check whether ad-alerts.yml exists under:

$AcceloHome/config/docker/addons

If ad-alerts.yml does not exist, generate it using:

accelo admin makeconfig ad-alerts

$AcceloHome/config/docker/addons

Open ad-alerts.yml in a text editor and update the following field:

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

For example:
[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

Save the changes.

5. Restart ad-alerts

Run the following command to restart ad-alerts:

accelo restart ad-alerts

6. Configure ad-director

On the node where ad-director is deployed, run the following command to generate ad-director.yml if the file does not already exist:

accelo admin makeconfig ad-director

Open ad-director.yml in a text editor and update the following field:

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

For example:
[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

Save the changes.

7. Restart ad-director

Run the following command to restart ad-director:

accelo restart ad-director

8. Deploy Notifications

On the standalone node where you want to deploy ad-notifications, run:

accelo deploy addons

When prompted, select Notifications to deploy ad-notifications.