Skip to content
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

Update minimal configuration example with dev mode #229

Conversation

msherman64
Copy link
Contributor

This updates the minimal example to use a loopback API interface, for
consistency across hosts. It also documents the procedure to enable
dev mode for all or specific services.

This updates the minimal example to use a loopback API interface, for
consistency across hosts. It also documents the procedure to enable
dev mode for all or specific services.
@msherman64 msherman64 linked an issue Sep 29, 2022 that may be closed by this pull request
@msherman64 msherman64 marked this pull request as draft October 6, 2022 14:04
Comment on lines +16 to +22
# This example assumes that `lo` has the IP `127.0.0.1/8`
network_interface: "lo"

# Keepalived will manage this IP address, which must be in the same
# subnet as the interface IP above. Haproxy will bind to this IP, and the
# openstack ADMIN and INTERNAL APIs listen here.
kolla_internal_vip_address: "127.0.0.254"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Turns out this breaks keepalived!

Due to the keepalived config: https://github.com/ChameleonCloud/kolla-ansible/blob/19eb03834a543a013ed820a7b370ec99e2825616/ansible/roles/loadbalancer/templates/keepalived/keepalived.conf.j2#L11

It will attempt to use the loopback as the primary vrrp interface, and fail to start. This config is fine for the case where haproxy is disabled, but not otherwise.

A workaround is to create a vlan subinterface, e.g. eth3.1000 to use instead.
The only requirment is that the interface is somehow "valid" for keepalived to watch.

@msherman64 msherman64 closed this Jul 27, 2023
@msherman64 msherman64 deleted the 228-add-defaultsyml-for-minimal-development-configuration branch May 23, 2024 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add defaults.yml for minimal development configuration
1 participant