From 8de5d35d2dab751ea9cf72057b6ab8522aadd7fd Mon Sep 17 00:00:00 2001 From: Mohammed Naser Date: Fri, 1 Feb 2019 13:02:26 -0500 Subject: [PATCH] nspawn: add container_network config We do not have a container_network configuration included which means that the mv-container went up with no IP address. This patch resolves this by bringing it up with the IP address which is supposed to be the internal virtual IP. Change-Id: I36c56a46fe37a0423552f99f221855118e328766 --- etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 b/etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 index c54377a8b1..18d0e190e5 100644 --- a/etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 +++ b/etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 @@ -104,6 +104,11 @@ aio_block: &aio_info_block # be used and should already have an IP address assigned # to it. container_extra_networks: + container_network: + bridge: "{{ ansible_default_ipv4['alias'] }}" + interface: mv-container + address: 172.29.236.100 + netmask: 255.255.252.0 flat_network: bridge: "{{ ansible_default_ipv4['alias'] }}" interface: mv-flat