Add a keystone-cinder-api constraint

Make sure the keystone service starts before the cinder-api one.

Change-Id: I21549c066afcf051e52fc4bba4fae2f34ad2ba4b
This commit is contained in:
Yanis Guenane 2015-05-27 15:39:22 +02:00
parent 2c73a7b6ac
commit 1012fe2195
1 changed files with 10 additions and 0 deletions

View File

@ -700,12 +700,22 @@ if hiera('step') >= 4 {
# Cinder
pacemaker::resource::service { $::cinder::params::api_service :
clone_params => "interleave=true",
require => Pacemaker::Resource::Service[$::keystone::params::service_name],
}
pacemaker::resource::service { $::cinder::params::scheduler_service :
clone_params => "interleave=true",
}
pacemaker::resource::service { $::cinder::params::volume_service : }
pacemaker::constraint::base { 'keystone-then-cinder-api-constraint':
constraint_type => 'order',
first_resource => "${::keystone::params::service_name}-clone",
second_resource => "${::cinder::params::api_service}-clone",
first_action => 'start',
second_action => 'start',
require => [Pacemaker::Resource::Service[$::cinder::params::api_service],
Pacemaker::Resource::Service[$::keystone::params::service_name]],
}
pacemaker::constraint::base { 'cinder-api-then-cinder-scheduler-constraint':
constraint_type => "order",
first_resource => "${::cinder::params::api_service}-clone",