openstack-ansible/etc/openstack_deploy/env.d/cinder.yml
Andy McCrae 91bd96b9e1 Move Cinder-volumes to "on metal"
Cinder-volumes is tightly coupled to the storage host and doesn't
gain from the benefits of containerization. This patch moves the default
location for cinder-scheduler into it's own container on the
"storage-infra_hosts", and the default location for cinder-volumes to be
"on metal" in the openstack_environment cinder.yml file.

Added documentation to suggest that you may want to remove "is_metal:
true" from cinder-volumes service when not using lvm.

Change-Id: I1879b1aa6dbe69a5a7e769a43b849441a38feeb8
Closes-Bug: #1433240
2015-06-24 17:33:16 +01:00

76 lines
1.9 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
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
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