Add ability to set a container base name prefix
In order to facilitate role-based base containers when copy-on-write containers are created, a prefix can now be used to differentiate the base containers. Change-Id: If8094d5bc6a52524128bcaddff2aaf20acf39833
This commit is contained in:
parent
7076c87785
commit
e0ea41b4f8
|
@ -43,8 +43,9 @@ lxc_container_default_bind_mounts:
|
|||
container_directory: "/var/backup"
|
||||
|
||||
# When using a base container to snapshot from for the overlayfs or LVM
|
||||
# copy-on-write backing stored, the base container can be set.
|
||||
lxc_container_base_name: "{{ lxc_container_map.distro }}-{{ lxc_container_map.release }}-{{ lxc_container_map.arch }}"
|
||||
# copy-on-write backing stored, the base container prefix/name can be set.
|
||||
lxc_container_base_name_prefix: ''
|
||||
lxc_container_base_name: "{{ lxc_container_base_name_prefix }}{{ lxc_container_map.distro }}-{{ lxc_container_map.release }}-{{ lxc_container_map.arch }}"
|
||||
|
||||
# Mappings from Ansible reported architecture to distro release architecture
|
||||
lxc_architecture_mapping:
|
||||
|
|
|
@ -0,0 +1,4 @@
|
|||
---
|
||||
features:
|
||||
- When using a copy-on-write backing store, the lxc_container_base_name can
|
||||
now include a prefix defined by ``lxc_container_base_name_prefix``.
|
Loading…
Reference in New Issue