deeaitch/ota-reference-design
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

next chapter

Browse Source
This commit is contained in:
deeaitch committed 2026-10-25 08:31:08 -04:00
1 parent 9385583955
commit c98eccc057
21 files changed
+1054 -11
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/06-atomic-updates.md
+5 -1
View File
@@ -58,6 +58,8 @@ If the request returns an error or its result is lost during a restart, the OTA
[Preparation and activation sequence — PlantUML source](../diagrams/plantuml/ab-installation-sequence.puml)
![Preparation and activation sequence](../diagrams/rendered/ab-installation-sequence.png)
There is a gap between steps 6 and 7: boot control may have saved the request while the OTA manager still says “prepared.” After a restart, boot control can start B. The OTA manager must accept that saved boot decision and repair its progress record. It must not overwrite B or reset the trial attempt count.
Two separate records do not form one transaction. Safe ordering and recovery rules handle the states left between them.
@@ -103,6 +105,8 @@ Package scripts, database migrations, and external actions also need their own r
[Installation states and restart decisions — PlantUML source](../diagrams/plantuml/ab-installation-recovery.puml)
![Installation states and restart decisions](../diagrams/rendered/ab-installation-recovery.png)
[ADR-019: Recover Interrupted Updates From Durable State](../adr/ADR-019-recover-interrupted-updates-from-durable-state.md) defines the ownership and recovery rules used here. [ADR-017](../adr/ADR-017-keep-recovery-state-outside-replaceable-software.md) defines where the records must live.
## 6. An Independent Service Update
@@ -151,4 +155,4 @@ Model tests check ordering. Platform tests must also interrupt real writes, rese
Preparation keeps incomplete software out of the boot path. Activation gives a complete version a chance to run. Confirmation still depends on checks after startup.
Next, we will look more closely at rollback: when to return to a previous version, what recovery needs, and when that previous version is no longer a usable choice.
Next, [chapter 07: Rollback and Recovery](07-rollback-and-recovery.md) examines when to return to a previous version, what recovery needs, and when that previous version is no longer a usable choice.