Update behaviour of NodeStatus UVE for contrail-tor-agent
Contrail-tor-agent currently publishes status as Non-Functional if it is
not connected to any TOR. Analytics module generates alarms when status
is published as Non-Functional. Since contrail-tor-agent has no way to detect
that is is running in backup mode, it is not possible for contrail-tor-agent to
publish status as Functional only in backup mode when it is not connected to
any TOR.
Fix is to publish connection status of contrail-tor-agent without considering its
connection to TOR.
Reviewed: https:/ /review. opencontrail. org/17901 github. org/Juniper/ contrail- controller/ commit/ c8dbbf1e5866a65 5ae62494a14cb1f 1c0b643ace
Committed: http://
Submitter: Zuul
Branch: R3.0
commit c8dbbf1e5866a65 5ae62494a14cb1f 1c0b643ace
Author: Ashok Singh <email address hidden>
Date: Fri Feb 26 01:38:48 2016 -0800
Update behaviour of NodeStatus UVE for contrail-tor-agent
Contrail-tor-agent currently publishes status as Non-Functional if it is
not connected to any TOR. Analytics module generates alarms when status
is published as Non-Functional. Since contrail-tor-agent has no way to detect
that is is running in backup mode, it is not possible for contrail-tor-agent to
publish status as Functional only in backup mode when it is not connected to
any TOR.
Fix is to publish connection status of contrail-tor-agent without considering its
connection to TOR.
Change-Id: I8b42afd48abe58 00da10d4ca559fd 22a1872c48f
Closes-Bug: 1548050