A backup tor-agent in initializing state cannot be shown as an alarm

[Vedamurthy Joshi]

R3.0 2711 Ubuntu 14.04 Kilo

In a active-backup tor-agent setup, one of the tor-agents will always be backup. But Contrail UI would continue to show that this tor-agent is non-functional
We should not report this as an alarm at all

Exact alarm raised:
"nodek3-1 , Virtual Router , Process(es) reporting as non-functional"

[Raj Reddy (rajreddy)]

Hi Hari/Praveen,

If the tor-agent is in backup, you should ignore the connection status to the TOR and set it’s status as ‘Functional'

thanks
Raj

[Hari Prasad Killi (haripk)]

Tor-agent doesn't know that it is backup. When OVS connection is established, it knows it is the active. Otherwise, it could either be backup or in standalone mode, with OVS connection not established. contrail-status is the way one checks whether connection to TOR is up or not.

This is the same behavior from earlier releases as well.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17901
Submitter: Ashok Singh (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17903
Submitter: Ashok Singh (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/17901
Committed: http://github.org/Juniper/contrail-controller/commit/c8dbbf1e5866a655ae62494a14cb1f1c0b643ace
Submitter: Zuul
Branch: R3.0

commit c8dbbf1e5866a655ae62494a14cb1f1c0b643ace
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: I8b42afd48abe5800da10d4ca559fd22a1872c48f
Closes-Bug: 1548050

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/17903
Committed: http://github.org/Juniper/contrail-controller/commit/203b52b6e2527f4a8482c8f66987fca07b31d22e
Submitter: Zuul
Branch: master

commit 203b52b6e2527f4a8482c8f66987fca07b31d22e
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.

Closes-Bug: 1548050
(cherry picked from commit c8dbbf1e5866a655ae62494a14cb1f1c0b643ace)

Change-Id: Iee52ea9476f7c7ea58ccbf33bcc82e8124be7514