-
Notifications
You must be signed in to change notification settings - Fork 10
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
Added conf option to scope wg hub to right netns #289
Conversation
This change is to add the 'create_hub_in_root_netns' boolean option designed to scope the wireguard hub creation to the root network namespace if set to True. To set, add the option to the site's defaults.
Note! Requires code/container from this PR |
kolla/defaults.yml
Outdated
@@ -257,6 +257,7 @@ neutron_dev_plugins: | |||
|
|||
# minimal config for neutron wireguard agent | |||
neutron_wireguard_hub_endpoint: "{{ kolla_external_vip_address }}" | |||
create_hub_in_root_netns: "{{ create_hub_in_root_netns }}" |
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.
this needs a default:
normally I would say to default it to false
so that just deploying the container won't change behavior.
however, as we're the only ones deploying this, lets set it to true
because it will save some steps.
create_hub_in_root_netns to neutron_wireguard_create_hub_in_root_netns. A boolean to be added to defaults.yaml
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.
In the current version here, the ml2_conf.ini part is fine.
However, under kolla/defaults.yml
, I suggest the following:
neutron_wireguard_create_hub_in_root_netns: True
Done |
This change is to add the 'create_hub_in_root_netns' boolean option designed to scope the wireguard hub creation to the root network namespace if set to True. To set, add the option to the site's defaults.