Jonathan Rosser 440c87a808 Add lxc3 compatibility
lxc3 deprecates many legacy config keys [1].

This change ensures that containers created on systems with lxc3
use the appropriate apparmor config keys. At this point we do not
need to address lxc2->lxc3 upgrades as these would only occur
during a Xenial->Bionic in-place OS upgrade, which is an unsupported
upgrade path.

[1] https://discuss.linuxcontainers.org/t/lxc-2-1-has-been-released/487

Change-Id: I9f30339210827f90818ea6993d90ca68c17fd3b2
2018-08-12 08:16:01 +00:00

31 lines
1.1 KiB
YAML

---
# Copyright 2016, Rackspace US, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# This is the default LXC AppArmor profile
# Groups which need the unbound profile have a specific override
lxc_container_config_list:
- "lxc.{{ lxc_config_key_apparmor }}=lxc-openstack"
# Needed by playbooks/common-tasks/os-lxc-container-setup.yml
lxc_container_log_path: "/var/log/lxc"
## Parameters provided to the wait_for_connection module after a container
## reboot is triggered by the playbook
lxc_container_wait_params:
# Wait 3 seconds before attempting the first connection
delay: 3
# Wait 60 seconds for the container to respond
timeout: 60