# Revision history [back]

### [kolla-ansible] Dimensions in globals.yml not applied

Hey all. I'm currently testing a deploy using kolla-ansible. All went fine until HOrizon started acting up and taking 10-15 seconds to display. Doing a little research I quickly arrived at the conclusion that it could be related to memory consumption on my control nodes and in fact, neutron-openvswitch-agent container was using up almost all the memory available. Therefore, I attempted to add some restrictions using dimensions and reconfigured services with kolla-ansible -i multinode reconfigure but when inspecting the container I can see that no constraints were applied.

neutron-openvswitch-agent_dimensions:
mem_limit: "3g"
memswap_limit: "4g"
mem_reservation: "2g"


_globals.yml excerpt_

After changing globals.yml, I tried reconfigure, upgrade and even deploy but the containers don't seem to apply the constraints:

# docker container inspect neutron_openvswitch_agent --format='{{json .HostConfig}}' | jq
...
"Memory": 0,
...
"MemoryReservation": 0,
"MemorySwap": 0,
...


Most likely I'm doing something incorrectly here and may have misread how the constraints are supposed to be applied, so any indication in the right direct will be greatly appreciated.

Thanks!

### [kolla-ansible] Dimensions in globals.yml not applied

Hey all. I'm currently testing a deploy using kolla-ansible. All went fine until HOrizon started acting up and taking 10-15 seconds to display. Doing a little research I quickly arrived at the conclusion that it could be related to memory consumption on my control nodes and in fact, neutron-openvswitch-agent container was using up almost all the memory available. Therefore, I attempted to add some restrictions using dimensions and reconfigured services with kolla-ansible -i multinode reconfigure but when inspecting the container I can see that no constraints were applied.

neutron-openvswitch-agent_dimensions:
mem_limit: "3g"
memswap_limit: "4g"
mem_reservation: "2g"


_globals.yml excerpt_

After changing globals.yml, I tried reconfigure, upgrade and even deploy but the containers don't seem to apply the constraints:

# docker container inspect neutron_openvswitch_agent --format='{{json .HostConfig}}' | jq
...
"Memory": 0,
...
"MemoryReservation": 0,
"MemorySwap": 0,
...


Most likely I'm doing something incorrectly here and may have misread how the constraints are supposed to be applied, so any indication in the right direct will be greatly appreciated.

Thanks!