openstack-ansible-os_cinder/templates/cinder-systemd-init.j2
Jesse Pretorius b620dc00e9 Replace var approach with config_template approach
Instead of having specific variables do adjust the init
behaviour, the more generalised approach of hard setting
sensible defaults in the template and allowing the use
of config_template to override those is being used.

Change-Id: Id74d06cdfa2cf1e4a6270566d67083a50d82f6ac
2017-04-26 13:08:09 +00:00

35 lines
1001 B
Django/Jinja

# {{ ansible_managed }}
[Unit]
Description=cinder openstack service
After=syslog.target
After=network.target
[Service]
Type=simple
User={{ cinder_system_user_name }}
Group={{ cinder_system_group_name }}
{% if program_override is defined %}
ExecStart={{ program_override }} {{ program_config_options|default('') }} --log-file=/var/log/cinder/{{ item.value.service_name }}.log
{% else %}
ExecStart={{ cinder_bin }}/{{ item.value.service_name }} {{ program_config_options|default('') }} --log-file=/var/log/cinder/{{ item.value.service_name }}.log
{% endif %}
# Give a reasonable amount of time for the server to start up/shut down
TimeoutSec=120
Restart=on-failure
RestartSec=2
# This creates a specific slice which all services will operate from
# The accounting options give us the ability to see resource usage through
# the `systemd-cgtop` command.
Slice=cinder.slice
CPUAccounting=true
BlockIOAccounting=true
MemoryAccounting=false
TasksAccounting=true
[Install]
WantedBy=multi-user.target