Commit 1e78cf28 authored by Peter Senna Tschudin's avatar Peter Senna Tschudin Committed by Frédéric Dalleau

T5432: Stakeholders feedback on the Software distribution and updates document

This commit addresses stakeholder feedback from T5432.
Signed-off-by: Peter Senna Tschudin's avatarPeter Senna Tschudin <peter.senna@collabora.com>
parent 32b0367d
......@@ -313,7 +313,7 @@ software stack.
### Updates rollback
Software updates should be reversible, and allow to rollback to a previous
working state.
working state. This requirement applies to system software and applications.
### User-driven software distribution
......@@ -330,8 +330,8 @@ across devices* being related to the features *Immutable software stack* and
### Immutable software stack
* Related requirements: *Consistent state across devices*, *Tampering protection*,
*Unwanted changes to the software stack*
* Related requirements: *Consistent state across devices*, *Resilience to user
operation*, *Tampering protection*, *Unwanted changes to the software stack*
One solution to address these requirements is to make the base operating system
and the application domains immutable.
......@@ -362,8 +362,9 @@ bootloader are not guaranteed to rollback gracefully.
* Related requirements: *Conditional software deployment based on business
rules*, *Configurable access rights to user data and system resource*,
*Consistent state across devices*, *Resilience to distribution and update
failures*, *User-driven software deployment*
*Consistent state across devices*, *Independent release and update of
application domains*, *Resilience to distribution and update failures*,
*User-driven software deployment*
These requirements are related to separating the base operating system from
application domains in regards to software distribution, software updates, and
......@@ -376,9 +377,9 @@ how application domains are deployed, updated and executed.
### Deployment management
* Related requirements: *Conditional software deployment based on business
rules*, *Consistent state across devices*, *Protecting the fleet from software
deployment issues*, *Resilience to distribution and update failures*, *Software
inventory*
rules*, *Consistent state across devices*, *Operator-driven software
distribution and updates*, *Protecting the fleet from software deployment
issues*, *Resilience to distribution and update failures*, *Software inventory*
Software distribution is more than a transport layer for packages, it includes
authorization, inventory, and deployment management. The software distribution
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment