Restart cinder-volume on controllers to emit notifications

When Ceph is used as a Cinder backend, the cinder-volume process runs on each
controller.

Fixes-bug: #1546555

Change-Id: I077bcebe0b637d001cf66803a24102db9c507c15
This commit is contained in:
Swann Croiset 2016-02-17 15:01:23 +01:00
parent 98441edea0
commit a8f6265c38
1 changed files with 11 additions and 3 deletions

View File

@ -82,17 +82,25 @@ service { [$nova_api_service, $nova_conductor_service, $nova_scheduler_service]:
include cinder::params
$cinder_api_service = $::cinder::params::api_service
$cinder_scheduler_service = $::cinder::params::scheduler_service
$cinder_volume_service = $::cinder::params::volume_service
if $storage_options['volumes_ceph'] {
# In this case, cinder-volume runs on controller node
$cinder_services = [$cinder_api_service, $cinder_scheduler_service, $cinder_volume_service]
} else {
$cinder_services = [$cinder_api_service, $cinder_scheduler_service]
}
cinder_config { 'DEFAULT/notification_topics':
value => $notification_topics,
notify => Service[$cinder_api_service, $cinder_scheduler_service],
notify => Service[$cinder_services],
}
cinder_config { 'DEFAULT/notification_driver':
value => 'messaging',
notify => Service[$cinder_api_service, $cinder_scheduler_service],
notify => Service[$cinder_services],
}
service { [$cinder_api_service, $cinder_scheduler_service]:
service { $cinder_services:
hasstatus => true,
hasrestart => true,
}