diff options
| author |   Tomi Juvonen <tomi.juvonen@nokia.com> | 2020-10-13 16:37:57 +0300 |
|---|---|---|
| committer | Tomi Juvonen <tomi.juvonen@nokia.com> | 2020-10-13 16:48:12 +0300 |
| commit | 72a1f8c92f1692f1ea8dcb5bc706ec9939c30e0a (patch) | |
| tree | e851c88b40b16d6c8d791b746b8c78728fff0c4f /docs/development/manuals/monitors.rst | |
| parent | 6ff11513a0d3728c79033af623c79dd6df7c621e (diff) | |
Documents up-to-dateHEADopnfv-10.0.0stable/jermamaster
According to document guidelines
Release notes
ETSI FEAT03 support and other minor enhancements
JIRA: DOCTOR-143
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
Change-Id: Iefa74004dfada376d1ab05c0149029a26f822275
Diffstat (limited to 'docs/development/manuals/monitors.rst')
| -rw-r--r-- | docs/development/manuals/monitors.rst | 37 |
1 files changed, 0 insertions, 37 deletions
diff --git a/docs/development/manuals/monitors.rst b/docs/development/manuals/monitors.rst deleted file mode 100644 index eeb5e226..00000000 --- a/docs/development/manuals/monitors.rst +++ /dev/null @@ -1,37 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -Monitor Types and Limitations -============================= - -Currently there are two monitor types supported: sample and collectd - -Sample Monitor --------------- - -Sample monitor type pings the compute host from the control host and calculates the -notification time after the ping timeout. -Also if inspector type is sample, the compute node needs to communicate with the control -node on port 12345. This port needs to be opened for incomming traffic on control node. - -Collectd Monitor ----------------- - -Collectd monitor type uses collectd daemon running ovs_events plugin. Collectd runs on -compute to send instant notification to the control node. The notification time is -calculated by using the difference of time at which compute node sends notification to -control node and the time at which consumer is notified. The time on control and compute -node has to be synchronized for this reason. For further details on setting up collectd -on the compute node, use the following link: -:doc:`<barometer:release/userguide/feature.userguide>` - - -Collectd monitors an interface managed by OVS. If the interface is not be assigned -an IP, the user has to provide the name of interface to be monitored. The command to -launch the doctor test in that case is: -MONITOR_TYPE=collectd INSPECTOR_TYPE=sample INTERFACE_NAME=example_iface ./run.sh - -If the interface name or IP is not provided, the collectd monitor type will monitor the -default management interface. This may result in the failure of doctor run.sh test case. -The test case sets the monitored interface down and if the inspector (sample or congress) -is running on the same subnet, collectd monitor will not be able to communicate with it. |