Comment 12 for bug 1956846
Revision history for this message
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hello:
This documentation [1] is outdated. We should document how keepalived is configured now.
This is an example of configuration [2]. We don't create an "interface" but an "vrrp_instance" section, named with random ID (in this case, VR_252).
According to the documentation [3], the "state" config knob is the initial state of this instance of the virtual router. Of course, as you comment, keepalived will vote to actually decide which one is the active one.
As commented before, the method initializing the router port [4] is the same for any router, independently of the type (legacy, DVR, HA, DVR-HA). Since Train, the routes written in the router namespace have the protocol defined ("static" by default). That works as the workaround Maximilian commented.
If you want to push a patch to handle this scenario, you are more than welcome. Any help is always accepted in OpenStack.
Regards.
[1]https:/
[2]https:/
[3]https:/
[4]https:/