Matt Thompson d60f55f0d6 Use fixed templates for glance configuration
This change moves away from the template generation to using fixed
template files.  This allows us to conditionally write blocks of
configurations, which I have done for the swift_store options.

This work is largely ripped from @cloudnull's cdc branch.  Note that
there are a few minor configuration changes introduced here by
(from @cloudnull's branch), such as worker count in glance-api.conf.
2014-09-09 15:17:03 +01:00

33 lines
1012 B
YAML

---
# Copyright 2014, 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.
- name: Drop Glance Config(s)
template:
src: "{{ item }}"
dest: "/etc/glance/{{ item }}"
owner: "{{ system_user }}"
group: "{{ system_group }}"
with_items:
- glance-api-paste.ini
- glance-api.conf
- glance-cache.conf
- glance-registry-paste.ini
- glance-registry.conf
- glance-scrubber.conf
- policy.json
- schema-image.json
- schema.json
notify: Restart os service