Placing cinder-volume into a nspawn-container renders inventory with network problems

[Marcus Klein]

I tried to place cinder-volume into a nspawn container as volumes should only be stored in Ceph. Therefore I created the following configuration

env.d/cinder.yml

container_skel:
  cinder_volumes_container:
    properties:
      is_metal: false

This results in a problem in the rendered inventory:
            "controller1": {
                "ansible_host": "10.0.0.1",
                "component": "haproxy",
                "container_address": "10.0.0.1",
                "container_name": "controller1",
                "container_networks": {
                    "container_address": {
                        "address": "10.0.0.1",
                        "bridge": "br-mgmt",
                        "interface": "eth1",
                        "netmask": "255.255.255.0",
                        "type": "veth"
                    }
                },
                "container_tech": "nspawn",
                "container_types": "controller1-host_containers",
                "is_metal": true,
                "physical_host": "controller1",
                "physical_host_group": "haproxy_hosts",
                "properties": {
                    "is_metal": true
                }
            },
            "controller1_cinder_volumes_container-b635c1f0": {
                "ansible_host": "10.0.0.171",
                "component": "cinder_volume",
                "container_address": "10.0.0.171",
                "container_name": "controller1_cinder_volumes_container-b635c1f0",
                "container_networks": {
                    "container_address": {
                        "address": "10.0.0.171",
                        "bridge": "br-mgmt",
                        "interface": "eth1",
                        "netmask": "255.255.255.0",
                        "type": "veth"
                    },
                    "storage_address": {
                        "address": "10.0.1.19",
                        "bridge": "br-storage",
                        "interface": "eth2",
                        "netmask": "255.255.255.0",
                        "type": "veth"
                    }
                },
                "container_tech": "nspawn",
                "physical_host": "controller1",
                "physical_host_group": "storage_hosts",
                "properties": {
                    "is_metal": false
                }
            },

The physical host controller1 is lacking the storage network connection in the inventory although the target machine has br-storage up and running. Maybe this is due to the nspawn container technology. I will try the rendering again with lxc container technology and see if I have there the same problem.

When deploying now the container for cinder-volume the deployment fails because the container will not have the storage network configured.

[Jonathan Rosser (jrosser)]

nspawn is no longer supported in openstack-ansible, so this is wontfix.