The baremetal role does not properly extend/override the docker systemd unit file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Wishlist
|
Chason Chan |
Bug Description
The proper documented way of extending/
https:/
Right now we pretty much hardcode the docker daemon options without leaving room for additional end-user customization: https:/
An example use case of being more flexible in customization is this particular Docker issue: https:/
TL;DR: there can be a mismatch of MTU configuration between the host and the container -- say the host has a MTU of 1400, Docker defaults to 1500 anyway and this causes certain network transactions to fail.
Docker has a way to customize the MTU through the systemd unit file, as such:
ExecStart=
But I have no way to "hook" into that with the current way things work.
The way I would probably see this is when we set up the defaults file, here:
https:/
First, drop that in /etc/default/docker for Ubuntu or /etc/sysconfig/
So in the defaults template here: https:/
Instead of doing: DOCKER_OPTS=""
I would do: DOCKER_OPTS="{{ custom_docker_opts }}".
This would allow someone to pass an extra variable:
kolla-ansible <...> -e "custom_
description: | updated |
Changed in kolla-ansible: | |
milestone: | pike-2 → pike-3 |
Changed in kolla-ansible: | |
milestone: | pike-3 → pike-rc1 |
Changed in kolla-ansible: | |
milestone: | pike-rc1 → pike-rc2 |
milestone: | pike-rc2 → queens-1 |
Changed in kolla-ansible: | |
milestone: | queens-2 → queens-3 |
Changed in kolla-ansible: | |
milestone: | queens-3 → queens-rc1 |
Changed in kolla-ansible: | |
milestone: | queens-rc1 → rocky-1 |
Changed in kolla-ansible: | |
milestone: | rocky-2 → rocky-3 |
Changed in kolla-ansible: | |
assignee: | nobody → Chason Chan (chen-xing) |
Changed in kolla-ansible: | |
importance: | Low → Wishlist |
@David Moreau Simard mind to push patch?