'\" t
.\"     Title: ocf_heartbeat_ovsmonitor
.\"    Author: ClusterLabs contributors (see the resource agent source for information about individual authors)
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
.\"      Date: 04/13/2023
.\"    Manual: OCF resource agents
.\"    Source: resource-agents 4.12.0-2
.\"  Language: English
.\"
.TH "OCF_HEARTBEAT_OVSMON" "7" "04/13/2023" "resource-agents 4.12.0-2" "OCF resource agents"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
ocf_heartbeat_ovsmonitor \- Monitors ovs bonding bonds
.SH "SYNOPSIS"
.HP \w'\fBovsmonitor\fR\ 'u
\fBovsmonitor\fR [start | stop | status | monitor | meta\-data | validate\-all]
.SH "DESCRIPTION"
.PP
Monitor the vitality of a local ovs bond\&.
.PP
You may set up this RA as a clone resource to monitor the network bonds on different nodes, with the same bond name\&. This is not related to the IP address or the network on which a bond is configured\&. You may use this RA to move resources away from a node, which has a faulty bond or prevent moving resources to such a node\&. This gives you independent control of the resources, without involving cluster intercommunication\&. But it requires your nodes to have more than one network bond\&.
.PP
The resource configuration requires a monitor operation, because the monitor does the main part of the work\&. In addition to the resource configuration, you need to configure some location constraints, based on a CIB attribute value\&. The name of the attribute value is configured in the \*(Aqname\*(Aq option of this RA\&.
.PP
Example constraint configuration using crmsh location loc_connected_node my_resource_grp rule ="rule_loc_connected_node" \-INF: ovsmonitor\-bond\-public eq 0
.PP
Example constraint configuration using pcs\&. Only allow \*(Aqmy_resource\*(Aq to run on nodes where eth0 ethernet device is available\&. pcs constraint location my_resource rule score=\-INFINITY ovsmonitor\-bond\-public ne 1
.PP
The ethmonitor works in 3 different modes to test the bond vitality\&. 1\&. call ovs\-appctl to see if at least one of the bonding\*(Aqs link status is up (if link is down \-> error) 2\&. call ovs\-ofctl and watch the RX counter (if packages come around in a certain time \-> success) 3\&. return error
.SH "SUPPORTED PARAMETERS"
.PP
\fBbond\fR
.RS 4
The name of the network bond which should be monitored (e\&.g\&. bond\-public)\&.
.sp
(unique, required, string, no default)
.RE
.PP
\fBbridge\fR
.RS 4
The name of the ovs bridge that contains the bridge\&.
.sp
(unique, required, string, no default)
.RE
.PP
\fBname\fR
.RS 4
The name of the CIB attribute to set\&. This is the name to be used in the constraints\&. Defaults to "ovsmonitor\-\*(Aqbond_name\*(Aq"\&.
.sp
(unique, optional, string, no default)
.RE
.PP
\fBmultiplier\fR
.RS 4
Multiplier for the value of the CIB attriobute specified in parameter name\&.
.sp
(optional, integer, default
1)
.RE
.PP
\fBrepeat_count\fR
.RS 4
Specify how often the bond will be monitored, before the status is set to failed\&. You need to set the timeout of the monitoring operation to at least repeat_count * repeat_interval
.sp
(optional, integer, default
5)
.RE
.PP
\fBrepeat_interval\fR
.RS 4
Specify how long to wait in seconds between the repeat_counts\&.
.sp
(optional, integer, default
10)
.RE
.PP
\fBpktcnt_timeout\fR
.RS 4
Timeout for the RX packet counter\&. Stop listening for packet counter changes after the given number of seconds\&.
.sp
(optional, integer, default
5)
.RE
.PP
\fBlink_status_only\fR
.RS 4
Only report success based on link status\&. Do not perform RX counter related connectivity tests\&.
.sp
(optional, boolean, default
false)
.RE
.SH "SUPPORTED ACTIONS"
.PP
This resource agent supports the following actions (operations):
.PP
\fBstart\fR
.RS 4
Starts the resource\&. Suggested minimum timeout: 60s\&.
.RE
.PP
\fBstop\fR
.RS 4
Stops the resource\&. Suggested minimum timeout: 20s\&.
.RE
.PP
\fBstatus\fR
.RS 4
Performs a status check\&. Suggested minimum timeout: 60s\&. Suggested interval: 10s\&.
.RE
.PP
\fBmonitor\fR
.RS 4
Performs a detailed status check\&. Suggested minimum timeout: 60s\&. Suggested interval: 10s\&.
.RE
.PP
\fBmeta\-data\fR
.RS 4
Retrieves resource agent metadata (internal use only)\&. Suggested minimum timeout: 5s\&.
.RE
.PP
\fBvalidate\-all\fR
.RS 4
Performs a validation of the resource configuration\&. Suggested minimum timeout: 20s\&.
.RE
.SH "EXAMPLE CRM SHELL"
.PP
The following is an example configuration for a ovsmonitor resource using the
\fBcrm\fR(8)
shell:
.sp
.if n \{\
.RS 4
.\}
.nf
primitive p_ovsmonitor ocf:heartbeat:ovsmonitor \e
  params \e
    bond=\fIstring\fR \e
    bridge=\fIstring\fR \e
  op monitor depth="0" timeout="60s" interval="10s" 
.fi
.if n \{\
.RE
.\}
.SH "EXAMPLE PCS"
.PP
The following is an example configuration for a ovsmonitor resource using
\fBpcs\fR(8)
.sp
.if n \{\
.RS 4
.\}
.nf
pcs resource create p_ovsmonitor ocf:heartbeat:ovsmonitor \e
  bond=\fIstring\fR \e
  bridge=\fIstring\fR \e
  op monitor OCF_CHECK_LEVEL="0" timeout="60s" interval="10s" 
.fi
.if n \{\
.RE
.\}
.SH "SEE ALSO"
.PP
\m[blue]\fB\%http://clusterlabs.org/\fR\m[]
.SH "AUTHOR"
.PP
\fBClusterLabs contributors (see the resource agent source for information about individual authors)\fR