fd9cda8df9
This change adds an nspawn container driver which will enable deployers to run clouds with systemd-nspawn instead of LXC. This adds "nspawn" to as an option to the `container_tech` variable. To support this change, The inventory generation tools have been updated to allow for a new group named `nspawn_hosts`. All of the container connectivity and setup are stored within the integrated repo under the new templates directory. The addition of "nspawn" container driver enables the ability for deployers to change, or mix container technologies within a single deployment without needing to change our well defined network topology or storage layout. Depends-On: I13d05ba8bcfe785257a9cf98dbdb6024ec937816 Change-Id: I41cfec63c423cd56a91c25dabae9aa1031c27e03 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
17 lines
978 B
YAML
17 lines
978 B
YAML
---
|
|
features:
|
|
- Deployers can now set the ``container_tech`` to **nspawn** when deploying
|
|
OSA within containers. When making the decision to deploy container types
|
|
the deployer only needs to define the desired ``container_tech`` and
|
|
continue the deployment as normal.
|
|
- The addition of the ``container_tech`` option and the inclusion of
|
|
**nspawn** support deployers now have the availability to define a desired
|
|
containerization strategy globally or on specific hosts.
|
|
- When using the **nspawn** driver containers will connect to the system
|
|
bridges using a MACVLAN, more on this type of network setup can be seen
|
|
`here <https://www.systutorials.com/docs/linux/man/8-ip-link/>`_.
|
|
- When using the **nspawn** driver container networking is managed by
|
|
systemd-networkd both on the host and within the container. This gives us a
|
|
single interface to manage regardless of distro and allows systemd to
|
|
efficiently manage the resources.
|