-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Mark all kickstart non-RPM content as phase2 [RHELDST-28021]
Kickstart repos don't adhere to the "mutable entry point, immutable everything else" design of other content types, such as yum and file repos. For example, files such as "/EULA", "/images/install.img" may receive in-place updates. As such, the usual categorization between phase1 and phase2 content based on entry points does not fit these repos correctly. From the point of view of exodus-gw, the set of files receiving in-place updates is arbitrary, so we'd better treat them *all* as phase 2 content and try to update them together. RPM files are the only exception, as we still expect that an RPM published to the same path is always the same thing. The effects of categorizing kickstart files as phase2 content include: - on publish, CDN cache will now be flushed for all non-RPM kickstart paths (rather than only the entry points). - on publish, non-RPM kickstart paths will be recorded into PublishedPath table, which allows them to trigger cache flush again when releasever_alias are updated in config. (This is the primary motivation for the change, as this important cache flush currently must be done manually.) - in-place updates to the repos are now more likely to appear as atomic from the customer's point of view. - kickstart publishes may be somewhat slower, as it is necessary to delay more of the publishing work until the user requests the final commit.
- Loading branch information
Showing
3 changed files
with
69 additions
and
7 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
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
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