openstack-ansible/etc/openstack_deploy/env.d/cinder.yml
Matt Thompson 44d3f25de6 Allow cinder-backup to use ceph
This change updates ceph_client and os_cinder roles to allow
cinder-backup to use ceph.  We also create a new group called
'cinder_backup' which allows us to only retreive the cinder backup key
if cinder-backup is actually in use.

To use, you would simply need to set cinder_service_backup_driver to
cinder.backup.drivers.ceph in your user_variables.yml file.

NOTE: You will need to update your
      /etc/openstack_deploy/env.d/cinder.yml in order for this change
      to execute successfully.

Change-Id: Ib94effa40208bbc8de0f78c5487316be007adcf1
Closes-Bug: #1481787
Implements: blueprint ceph-block-devices
DocImpact
2015-09-03 07:37:21 +00:00

80 lines
2.0 KiB
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.
component_skel:
cinder_api:
belongs_to:
- cinder_all
cinder_scheduler:
belongs_to:
- cinder_all
cinder_volume:
belongs_to:
- cinder_all
cinder_backup:
belongs_to:
- cinder_all
container_skel:
cinder_api_container:
belongs_to:
- infra_containers
- storage-infra_containers
contains:
- cinder_api
properties:
service_name: cinder
container_release: trusty
cinder_scheduler_container:
belongs_to:
- infra_containers
- storage-infra_containers
contains:
- cinder_scheduler
properties:
service_name: cinder
container_release: trusty
cinder_volumes_container:
belongs_to:
- storage_containers
contains:
- cinder_volume
- cinder_backup
properties:
# When using lvm as a cinder backend its advised to run cinder-volumes on metal.
# If you are using a different backend you may want to remove "is_metal: true".
# Otherwise if cinder-volumes is already running in containers you may want to
# leave is_metal off, alternatively you will have to migrate your volumes once
# deployed on metal.
is_metal: true
service_name: cinder
container_release: trusty
physical_skel:
storage-infra_containers:
belongs_to:
- all_containers
storage-infra_hosts:
belongs_to:
- hosts
storage_containers:
belongs_to:
- all_containers
storage_hosts:
belongs_to:
- hosts