puppet-heat/manifests/db/sync.pp
ZhongShengping c16009b55b Allow db sync timeouts to be configurable
As Openstack projects continue to have longer database migration
chains, the Puppet default timeout of 300 seconds for an execution
is becoming too short a duration on some hardware, leading to timeouts.
As projects continue to add more migration scripts without pruning
the base, timeouts will continue to become more frequent unless
this time can be expanded.

Change-Id: I9118a6d4e1553ee0715f3fda72d625ccdcdf1b0f
Closes-Bug: #1904962
2020-11-23 09:27:52 +08:00

41 lines
1.0 KiB
Puppet

#
# Class to execute heat dbsync
#
# ==Parameters
#
# [*extra_params*]
# (Optional) String of extra command line parameters to append
# to the heat-manage db_sync command. These will be inserted
# in the command line between 'heat-manage' and 'db_sync'.
# Defaults to '--config-file /etc/heat/heat.conf'
#
# [*db_sync_timeout*]
# (Optional) Timeout for the execution of the db_sync
# Defaults to 300
#
class heat::db::sync(
$extra_params = '--config-file /etc/heat/heat.conf',
$db_sync_timeout = 300,
) {
include heat::deps
exec { 'heat-dbsync':
command => "heat-manage ${extra_params} db_sync",
path => '/usr/bin',
user => 'heat',
refreshonly => true,
try_sleep => 5,
tries => 10,
timeout => $db_sync_timeout,
logoutput => on_failure,
subscribe => [
Anchor['heat::install::end'],
Anchor['heat::config::end'],
Anchor['heat::dbsync::begin']
],
notify => Anchor['heat::dbsync::end'],
tag => 'openstack-db',
}
}