3c22200109
The LXC container create role has not been updated to use some of our more well throughout patterns and layouts. This change updates the role so that its following our normal role conventions and simplifying task execution. New tags have been added to follow the basic tag pattern found in all other roles. The two tags now supported are lxc-config, and lxc-create. The creation backends have been seperated out into dynamically included files. This will reduce our "skips" which will improve execution time and assist developers in understanding what is happening when a container is created. Stubbs for BTRFS and ZFS container types have been added so future work can continue on those two store options without impacting our normal workflow. All task files have been updated to use the "lxc_" prefix which follows the pattern found in everyone of our roles. Change-Id: I0982a42321cf88f66442b5f766729f17c68e8e4a Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
22 lines
1.2 KiB
YAML
22 lines
1.2 KiB
YAML
---
|
|
features:
|
|
- The tag options when creating an LXC container have been simplified. The two
|
|
tags now supported by the `lxc_container_create` role are
|
|
**lxc-{create,config}**.
|
|
upgrade:
|
|
- The LXC container create option `lxc_container_backing_store` is now defined
|
|
by default and has a value of "dir". Prior to this release the backend store
|
|
option was using several auto-detection methods to try and guess the store
|
|
type based on facts fed into the role and derived from the physical host.
|
|
While the auto-detection methods worked, they created a cumbersome set of
|
|
conditionals and limited our ability to leverage additional container
|
|
stores. Having this option be a default allows deployers to mix and match
|
|
container stores to suit the needs of the deployment. Existing deployments
|
|
should set this option within group or user variables to ensure
|
|
there's no change in the backend store when new container be provisioned.
|
|
other:
|
|
- The LXC container create role will now check for the LXC volume group if
|
|
the option `lxc_container_backing_store` is set to "lvm". If this volume
|
|
group is not found, the role will halt and instruct the deployer to update
|
|
their configuration options and inspect their host setup.
|