generated from RedHatQuickCourses/course-starter
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ace7112
commit 2ea084b
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
= Summary | ||
|
||
In this chapter, you learned: | ||
|
||
* No matter how you provision your edge devices, they need access to remote OSTree repositories to fetch system updates. | ||
* Edge commit imagge used for system updates must be created with a reference to an existing OSTree repository and an OSTree branch with at least one commit. | ||
* Devices provisioned using edge installer images are *NOT* configured with an OSTree remote, you must configure it before applying updates. | ||
* RPM-OSTree stages upgrades on the system disk, as a new OSTree commit, and applies then on the next boot. It also keeps the previous OSTree commit so you can rollback from the upgrade. | ||
* Changes to files in `/etc` and `/var` are retained during system updates and rollbacks. | ||
* OSTree static deltas between two OSTree commits make system upgrades faster and more reliable for devices with high latency or low-bandwidth network connections, and most be created manually. | ||
* Everyime you add commits or static deltas to an OSTree repository, you must update its summary file. |