Ensure the components are isolated from the system
This creates a specific slice which all OpenStack services will operate from. By creating an independent slice these components will be governed away from the system slice allowing us to better optimise resource consumption. See the following for more information on slices: * https://www.freedesktop.org/software/systemd/man/systemd.slice.html See for following for more information on resource controls: * https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html Tools like ``systemd-cgtop`` and ``systemd-cgls`` will now give us insight into specific processes, process groups, and resouce consumption in ways that we've not had access to before. To enable some of this reporting the accounting options have been added to the [Service] section of the unit file. Change-Id: Idac3056145b92adcd0b5b328296c59b71bf28441 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
parent
4f487eda06
commit
bdc17256d2
|
@ -85,14 +85,19 @@ cloudkitty_cloudkitty_conf_overrides: {}
|
|||
cloudkitty_policy_overrides: {}
|
||||
cloudkitty_api_paste_ini_overrides: {}
|
||||
|
||||
cloudkitty_api_init_overrides: {}
|
||||
cloudkitty_processor_init_overrides: {}
|
||||
|
||||
## Service Name-Group Mapping
|
||||
cloudkitty_services:
|
||||
cloudkitty-api:
|
||||
group: cloudkitty_api
|
||||
service_name: cloudkitty-api
|
||||
init_config_overrides: "{{ cloudkitty_api_init_overrides }}"
|
||||
cloudkitty-processor:
|
||||
group: cloudkitty_api
|
||||
service_name: cloudkitty-processor
|
||||
init_config_overrides: "{{ cloudkitty_processor_init_overrides }}"
|
||||
|
||||
cloudkitty_pip_packages:
|
||||
- cloudkitty
|
||||
|
|
|
@ -0,0 +1,10 @@
|
|||
---
|
||||
features:
|
||||
- New variables have been added to allow a deployer to customize
|
||||
a cloudkitty systemd unit file to their liking.
|
||||
- The task dropping the cloudkitty systemd unit files now uses the
|
||||
``config_template`` action plugin allowing deployers access to
|
||||
customize the unit files as they see fit without having to
|
||||
load extra options into the defaults and polute the generic
|
||||
systemd unit file with jinja2 variables and conditionals.
|
||||
|
|
@ -44,12 +44,14 @@
|
|||
when: inventory_hostname in groups[item.value.group]
|
||||
|
||||
- name: Place the systemd init script
|
||||
template:
|
||||
config_template:
|
||||
src: "cloudkitty-systemd-init.j2"
|
||||
dest: "/etc/systemd/system/{{ item.value.service_name }}.service"
|
||||
mode: "0644"
|
||||
owner: "root"
|
||||
group: "root"
|
||||
config_overrides: "{{ item.value.init_config_overrides }}"
|
||||
config_type: "ini"
|
||||
with_dict: "{{ cloudkitty_services }}"
|
||||
when: inventory_hostname in groups[item.value.group]
|
||||
notify:
|
||||
|
|
|
@ -21,5 +21,14 @@ TimeoutSec=300
|
|||
Restart=on-failure
|
||||
RestartSec=150
|
||||
|
||||
# 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=cloudkitty.slice
|
||||
CPUAccounting=true
|
||||
BlockIOAccounting=true
|
||||
MemoryAccounting=false
|
||||
TasksAccounting=true
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
|
|
Loading…
Reference in New Issue