1 # Example: managing cinder controller services with pacemaker
3 # By setting enabled to false, these services will not be started at boot. By setting
4 # manage_service to false, puppet will not kill these services on every run. This
5 # allows the Pacemaker resource manager to dynamically determine on which node each
8 # The puppet commands below would ideally be applied to at least three nodes.
10 # Note that cinder-api is associated with the virtual IP address as
11 # it is called from external services. The remaining services connect to the
12 # database and/or message broker independently.
14 # Example pacemaker resource configuration commands (configured once per cluster):
16 # sudo pcs resource create cinder_vip ocf:heartbeat:IPaddr2 params ip=192.0.2.3 \
17 # cidr_netmask=24 op monitor interval=10s
19 # sudo pcs resource create cinder_api_service lsb:openstack-cinder-api
20 # sudo pcs resource create cinder_scheduler_service lsb:openstack-cinder-scheduler
22 # sudo pcs constraint colocation add cinder_api_service with cinder_vip
25 database_connection => 'mysql://cinder:secret_block_password@openstack-controller.example.com/cinder',
28 class { 'cinder::api':
29 keystone_password => 'CINDER_PW',
30 keystone_user => 'cinder',
32 manage_service => false,
35 class { 'cinder::scheduler':
36 scheduler_driver => 'cinder.scheduler.simple.SimpleScheduler',
38 manage_service => false,