Move nspawn to unmaintained state

Update docs so that they mention about nspawn removal. Also drop nspawn
from example configurations as much as we can.

Change-Id: I45dc64ef785cc4a61d09af5ca9e5181dff066400

doc/source/reference/inventory/configure-inventory.rst

@@ -221,12 +221,11 @@ To omit a component from a deployment, you can use one of several options:
 Deploying using a different container technology
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. note::
+.. warning::
 
    While nspawn is an available containerization technology it should be
-   considered experemental at this time. Even though this subsystem is not yet
+   considered unmaintained and it's support will be removed in the upcoming
-   recommended for production, it is stable enough to introduce to the community
+   release.
-   and something we'd like feedback on as we improve it over the next cycle.
 
 OpenStack-Ansible presently supports two different container technologies, LXC
 and nspawn. These two container technologies can be used separately or together

etc/openstack_deploy/openstack_user_config.yml.example

@@ -321,7 +321,8 @@
 # List of target hosts on which to deploy shared infrastructure services
 # and define the container_tech for a specific infra node. If this setting
 # is omitted the inventory generation system will default to "lxc". Accpetable
-# options are "lxc" and "nspawn".
+# options are "lxc" and "nspawn". Please note, that nspawn is unmaintained
+# and will be removed in the upcoming release
 #
 #   Level: <value> (required, string)
 #   Hostname of a target host.

etc/openstack_deploy/openstack_user_config.yml.multibond.example

@@ -94,14 +94,8 @@ global_overrides:
 shared-infra_hosts:
   infra1:
     ip: 172.29.236.11
-    container_vars:
-      # Optional | Example setting the container_tech for a target host.
-      container_tech: lxc
   infra2:
     ip: 172.29.236.12
-    container_vars:
-      # Optional | Example setting the container_tech for a target host.
-      container_tech: nspawn
   infra3:
     ip: 172.29.236.13
 

etc/openstack_deploy/openstack_user_config.yml.prod.example

@@ -79,14 +79,8 @@ global_overrides:
 shared-infra_hosts:
   infra1:
     ip: 172.29.236.11
-    container_vars:
-      # Optional | Example setting the container_tech for a target host.
-      container_tech: lxc
   infra2:
     ip: 172.29.236.12
-    container_vars:
-      # Optional | Example setting the container_tech for a target host.
-      container_tech: nspawn
   infra3:
     ip: 172.29.236.13
 

etc/openstack_deploy/openstack_user_config.yml.provnet-group.example

@@ -132,14 +132,8 @@ global_overrides:
 shared-infra_hosts:
   infra1:
     ip: 172.29.236.11
-    container_vars:
-      # Optional | Example setting the container_tech for a target host.
-      container_tech: lxc
   infra2:
     ip: 172.29.236.12
-    container_vars:
-      # Optional | Example setting the container_tech for a target host.
-      container_tech: nspawn
   infra3:
     ip: 172.29.236.13
 

etc/openstack_deploy/openstack_user_config.yml.singlebond.example

@@ -94,14 +94,8 @@ global_overrides:
 shared-infra_hosts:
   infra1:
     ip: 172.29.236.11
-    container_vars:
-      # Optional | Example setting the container_tech for a target host.
-      container_tech: lxc
   infra2:
     ip: 172.29.236.12
-    container_vars:
-      # Optional | Example setting the container_tech for a target host.
-      container_tech: nspawn
   infra3:
     ip: 172.29.236.13