diff --git a/source/reference-manual/ota/production-targets.rst b/source/reference-manual/ota/production-targets.rst index c66b5c153..2b990372c 100644 --- a/source/reference-manual/ota/production-targets.rst +++ b/source/reference-manual/ota/production-targets.rst @@ -35,7 +35,9 @@ Waves allow Factory operators to control an exact time when devices see a new ve Performing a Production OTA --------------------------- -A user should define a process to select CI builds which need to be delivered to production devices. +A customer should define a process to select CI builds which need to be delivered to production devices. +Every user performing production OTAs should generate their personal :ref:`offline TUF targets key ` to sign production Targets. + Let's assume a user selected a CI build version 42 as ready to be run in production. To start the production release process, a user would create a new wave using the below command:: @@ -48,6 +50,7 @@ That TUF targets role only includes a single Target from CI build (in above exam .. note:: We recommend that a user generates :ref:`OSTree static deltas` before rolling out waves to devices. + Static Deltas will optimize your OTA update download. Once created, a new wave can be rolled out to Factory production devices, all at once or in phases. There are several ways how a wave can be rolled out: