-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OPNET-8: Added a release note for VMware vSphere - Migrate to using unicast keepalived #49549
OPNET-8: Added a release note for VMware vSphere - Migrate to using unicast keepalived #49549
Conversation
ecdfc0c
to
5981a24
Compare
This ended up not being specific to vsphere. Vsphere was the original driver of the change, but since we'd already been running unicast on baremetal for a while we decided to just turn it on for all on-prem platforms to reduce our support matrix, so this applies to vsphere, openstack, and ovirt. |
5981a24
to
00eb3f1
Compare
@cybertron Thank you! Updated. |
@qiowang721 Can you please provide QE review? Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a comment, thanks!
@@ -646,6 +646,11 @@ For clusters that run on {rh-openstack}, the network functions virtualization de | |||
|
|||
These changes are reflected in simplified post-installation and network configuration documentation. | |||
|
|||
[id="ocp-4-11-vsphere-unicast-default"] | |||
==== Installations on Red Hat OpenStack Platform, VMware vSphere, or oVirt now configure keepalived with unicast as the default |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ahardin-rh do we want to use the attribute for OSP here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, updating now
@ahardin-rh, do we need a change management email about this? |
/lgtm |
/lgtm |
@jboxman-rh Yes, as noted above this is going through the change management process. The email is being sent out today. Thanks! |
00eb3f1
to
543ee1c
Compare
New changes are detected. LGTM label has been removed. |
543ee1c
to
07217cc
Compare
Version(s):
4.11 RN only
Addresses:
https://issues.redhat.com/browse/OPNET-8
Link to docs preview:
http://file.rdu.redhat.com/~ahardin/August-2022/4-11-unicast-keepalived/release_notes/ocp-4-11-release-notes.html#ocp-4-11-vsphere-unicast-default
Change management required