Conditional service startup for contrail components
To support upgrades, we need a way to control of services start-up after components deployment. If a flag variable is found in Hiera, manifests do not ensure services to be started. Also, ubuntu-specific tweaks were added to manifests to prevent automation service starts and restarts after package installation or upgrades Change-Id: I13c607078fc2fd4f26a90665a217b1c40288ed04
This commit is contained in:
6
deployment_scripts/puppet/modules/contrail/manifests/analytics.pp
Normal file → Executable file
6
deployment_scripts/puppet/modules/contrail/manifests/analytics.pp
Normal file → Executable file
@@ -27,6 +27,10 @@ class contrail::analytics {
|
||||
|
||||
Exec { path => '/usr/bin:/usr/sbin:/bin:/sbin' }
|
||||
|
||||
tweaks::ubuntu_service_override { 'supervisor-analytics':
|
||||
package_name => 'contrail-analytics',
|
||||
}
|
||||
|
||||
# Packages
|
||||
package { 'redis-server': } ->
|
||||
package { 'contrail-analytics': } ->
|
||||
@@ -81,7 +85,7 @@ class contrail::analytics {
|
||||
}
|
||||
|
||||
service { 'supervisor-analytics':
|
||||
ensure => running,
|
||||
ensure => $contrail::service_ensure,
|
||||
enable => true,
|
||||
require => [Package['contrail-openstack-analytics'],
|
||||
Service['redis-server'],
|
||||
|
||||
Reference in New Issue
Block a user