summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLaurent Bonnans <laurent.bonnans@here.com>2019-03-12 11:29:04 +0100
committerPatrick Vacek <patrickvacek@gmail.com>2019-04-29 09:26:36 +0200
commitb8ada64b350335185cff6f4b42d6be990c7f725d (patch)
treeaee0a06d370c298ce2587d534f0802e9ab9a3e31
parent07a1bd757035d31a10af4e2703e624f9a96bb881 (diff)
downloadmeta-updater-b8ada64b350335185cff6f4b42d6be990c7f725d.tar.gz
Document aktualizr-resource-control
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
-rw-r--r--README.adoc14
1 files changed, 14 insertions, 0 deletions
diff --git a/README.adoc b/README.adoc
index 434c04c..01159a0 100644
--- a/README.adoc
+++ b/README.adoc
@@ -91,6 +91,7 @@ Your images will also need network connectivity to be able to reach an actual OT
91* `SOTA_CLIENT_FEATURES` - extensions to aktualizr. The only valid options are `hsm` (to build with HSM support) and `secondary-network` (to set up a simulated 'in-vehicle' network with support for a primary node with a DHCP server and a secondary node with a DHCP client). 91* `SOTA_CLIENT_FEATURES` - extensions to aktualizr. The only valid options are `hsm` (to build with HSM support) and `secondary-network` (to set up a simulated 'in-vehicle' network with support for a primary node with a DHCP server and a secondary node with a DHCP client).
92* `SOTA_SECONDARY_CONFIG_DIR` - a directory containing JSON configuration files for virtual secondaries on the host. These will be installed into `/etc/sota/ecus` on the device and automatically provided to aktualizr. 92* `SOTA_SECONDARY_CONFIG_DIR` - a directory containing JSON configuration files for virtual secondaries on the host. These will be installed into `/etc/sota/ecus` on the device and automatically provided to aktualizr.
93* `SOTA_HARDWARE_ID` - a custom hardware ID that will be written to the aktualizr config. Defaults to MACHINE if not set. 93* `SOTA_HARDWARE_ID` - a custom hardware ID that will be written to the aktualizr config. Defaults to MACHINE if not set.
94* `RESOURCE_xxx_pn-aktualizr` - controls maximum resource usage of the aktualizr service, when `aktualizr-resource-control` is installed on the image. See <<aktualizr service resource control>> for details.
94 95
95== Usage 96== Usage
96 97
@@ -156,6 +157,19 @@ Second, you can write recipes to install additional config files with customized
156 157
157To use these recipes, you will need to add them to your image with a line such as `IMAGE_INSTALL_append = " aktualizr-log-debug "` in your `local.conf`. 158To use these recipes, you will need to add them to your image with a line such as `IMAGE_INSTALL_append = " aktualizr-log-debug "` in your `local.conf`.
158 159
160=== aktualizr service resource control
161
162With systemd based images, it is possible to set resource policies for the aktualizr service. The main use case is to provide a safeguard against resource exhaustion during an unforeseen failure scenario.
163
164To enable it, install `aktualizr-resource-control` on the target image and optionally override the default resource limits set in link:recipes-sota/aktualizr/aktualizr_git.bb[aktualizr_git.bb], from your `local.conf`.
165
166For example:
167
168....
169IMAGE_INSTALL_append += " aktualizr-resource-control "
170RESOURCE_CPU_WEIGHT_pn-aktualizr = "50"
171....
172
159== Development configuration 173== Development configuration
160 174
161There are a few settings that can be controlled in `local.conf` to simplify the development process: 175There are a few settings that can be controlled in `local.conf` to simplify the development process: