
Since Grizzly, nova-compute does not need database access anymore. Currently, only nova-api, nova-scheduler and nova-conductor really need database access. * Keep original nova parameters with backward compatibility * Create nova::db with database parameters * Import nova::db in nova::init for backward compatibility * Import nova::db in nova::{api,conductor,scheduler} * Refactorize unit tests for conductor & scheduler Change-Id: I42b9d2b1efb5856fed6550c25ac3142952690df1 Implements: blueprint move-db-params
37 lines
805 B
Puppet
37 lines
805 B
Puppet
# == Class: nova::schedule
|
|
#
|
|
# Install and manage nova scheduler
|
|
#
|
|
# === Parameters:
|
|
#
|
|
# [*enabled*]
|
|
# (optional) Whether to run the scheduler service
|
|
# Defaults to false
|
|
#
|
|
# [*manage_service*]
|
|
# (optional) Whether to start/stop the service
|
|
# Defaults to true
|
|
#
|
|
# [*ensure_package*]
|
|
# (optional) The state of the scheduler package
|
|
# Defaults to 'present'
|
|
#
|
|
class nova::scheduler(
|
|
$enabled = false,
|
|
$manage_service = true,
|
|
$ensure_package = 'present'
|
|
) {
|
|
|
|
include nova::db
|
|
include nova::params
|
|
|
|
nova::generic_service { 'scheduler':
|
|
enabled => $enabled,
|
|
manage_service => $manage_service,
|
|
package_name => $::nova::params::scheduler_package_name,
|
|
service_name => $::nova::params::scheduler_service_name,
|
|
ensure_package => $ensure_package,
|
|
}
|
|
|
|
}
|