debian_hypervisor: synchronize team0_x port state with OVS #666
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Yoann Congal <[email protected]>
On hypervisor shutdown, OVS is stopped a long time before the team0_x ports are shutdown as well. In the meantime: * The switching done by OVS is stopped * The corosync totem stops circulating and nodes are disconnected from the pacemake cluster which leads to resources being stopped. * After a while, RTSP detects this and change ports configuration to avoid the shutdown node and corosync/pacemaker start back with the left nodes. To avoid this, use systemd services to shutdown team0_x ports as soon as OVS is stopped to signal RTSP to change the configuration "instantly" and thus, avoid the corosync totem timeout. Signed-off-by: Yoann Congal <[email protected]>
Signed-off-by: Yoann Congal <[email protected]>
ycongal-smile
force-pushed
the
yco/rtsp_ovs_fix
branch
from
641dde1 to
0216411
Compare
Signed-off-by: Florent CARLI <[email protected]>
insatomcat
added a commit
to seapath/cukinia-tests
that referenced
this pull request
Dec 16, 2024
Usefull to deal with RSTP/Corosync working together (seapath/ansible#666) Signed-off-by: Florent CARLI <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On hypervisor shutdown, OVS is stopped a long time before the team0_x
ports are shutdown as well.
In the meantime:
the pacemake cluster which leads to resources being stopped.
avoid the shutdown node and corosync/pacemaker start back with the
left nodes.
To avoid this, use systemd services to shutdown team0_x ports as soon as
OVS is stopped to signal RTSP to change the configuration "instantly"
and thus, avoid the corosync totem timeout.
This PR also include preliminary work and a unrelated readme fix
TODO: