Dom Processor¶
Overview¶
The Dom Processor microservice handles the inventory add/update/delete for devices discovered using discovery service. The service is invoked from discovery service's /inventory endpoint.
Prerequisites¶
-
A microservices cluster must be setup. Refer to Microservice Cluster Setup.
-
Apache Pulsar must be installed. Refer to Apache Pulsar microservice.
-
The following core microservices must be installed as per the requirement -
- Discovery Service microservice
Setup¶
su - assure1
export NAMESPACE=a1-zone1-pri
export WEBFQDN=<Primary Presentation Web FQDN>
a1helm install dom-processor assure1/dom-processor -n $NAMESPACE --set global.imageRegistry=$WEBFQDN
Default Configuration¶
| Name | Value | Possible Values | Notes |
|---|---|---|---|
| LOG_LEVEL | INFO | FATAL, ERROR, WARN, INFO, DEBUG | Logging level used by application. |
| PULSAR_DOM_PROCESSOR_OVERRIDE | "" | persistent://assure1/discovery/dom-processor-zoneX | Overrides the value of pulsar topic from which dom processor requests to be received (same as where discovery service sends the request). Example- dom-processor-zone1 |
| PULSAR_DOM_FEEDBACK_OVERRIDE | "" | persistent://assure1/discovery/dom-feedback-zoneX | Overrides the value of pulsar topic on which dom processor errors to be sent. Example- dom-feedback-zone1 |
| DB_CONNECTION_TIMEOUT | 60 | Integer | Time value in seconds for db connection timeout |
| DB_FAILOVER_CONNECTION_TIMEOUT | 10 | Integer | Time value in seconds for failover db connection timeout |
| DB_HEALTH_CHECK_DELAY | 30 | Integer | Time value in seconds to verify the db connectivity |
| DB_FAILOVER_ENABLED | "true" | true, false | contains the boolean to control db failover |
| REDUNDANCY_POLL_PERIOD | 5 | Integer | How often the secondary service checks to see if the primary is online, in seconds. |
| REDUNDANCY_FAILOVER_THRESHOLD | 4 | Integer | The number of failed polls before the secondary becomes the active application. |
| REDUNDANCY_FALLBACK_THRESHOLD | 1 | Integer | The number of successful polls before the secondary goes back to sleep. |
Configurations can be changed by passing the values to the a1helm install prefixed with the configData parent key.
Example of setting the log level to DEBUG¶
a1helm install ... --set configData.LOG_LEVEL=DEBUG
Example of enabling redundancy¶
Redundancy will not be enabled by default. To enable this functionality, pass the following to the install command:
a1helm install ... --set redundancy.enabled=true