-
Notifications
You must be signed in to change notification settings - Fork 110
Rework additive mirroring policy for Oracle Linux #4732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| :_mod-docs-content-type: CONCEPT | ||
|
|
||
| [id="oracle-linux-content"] | ||
| = Oracle Linux content | ||
|
|
||
| [role="_abstract"] | ||
| You can synchronize content for Oracle Linux to {Project}. | ||
|
|
||
| Oracle adds packages to repositories for Oracle Linux and ULN without removing old versions. | ||
| Content synchronization with the *Content only* mirroring policy might lead to out-of-memory issues on {ProjectServer}. | ||
| You can mitigate this by setting the mirroring policy to *Additive* and the *Retain package versions* to either one or two. | ||
| This means that each time {Project} synchronizes content from Oracle, new packages are added and old packages are removed. | ||
| Note that this does not affect any published content views. | ||
|
|
||
| .Additional resources | ||
| * xref:adding-custom-rpm-repositories-by-using-web-ui[] | ||
| * xref:limiting-growth-of-synchronized-content-by-using-web-ui[] | ||
| * xref:uln-repositories[] | ||
| * xref:oracle-linux-10[] | ||
| * xref:oracle-linux-9[] | ||
| * xref:oracle-linux-8[] |
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this a real issue for concept modules? Until now, I thought this rule only applies to procedures.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. AFAIK it is an issue now for concept modules. I raised jhradilek/asciidoctor-dita-vale#177 to clarify. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| :_mod-docs-content-type: PROCEDURE | ||
|
|
||
| [id="limiting-growth-of-synchronized-content-by-using-cli"] | ||
| = Limiting growth of synchronized content by using Hammer CLI | ||
|
|
||
| [role="_abstract"] | ||
| You can limit the growth of content in the Library lifecycle environment on {ProjectServer} by restraining the number of package versions in synchronized repositories. | ||
|
|
||
| .Procedure | ||
| * Configure your repository to retain a limited number of package versions in {Project}: | ||
| + | ||
| [options="nowrap", subs="+quotes,verbatim,attributes"] | ||
| ---- | ||
| $ hammer repository update \ | ||
| --id _My_Repository_ID_ \ | ||
| --mirroring-policy additive \ | ||
| --retain-package-versions-count _My_Package_Versions_Count_ | ||
| ---- | ||
| + | ||
| ** Set _My_Package_Versions_Count_ to `1` to only keep the latest synchronized package version on {Project}. | ||
| ** Set _My_Package_Versions_Count_ to `2` or higher to keep multiple package versions on {Project}. | ||
|
|
||
| .Additional resources | ||
| * xref:Mirroring_Policies_Overview_{context}[] |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| :_mod-docs-content-type: PROCEDURE | ||
|
|
||
| [id="limiting-growth-of-synchronized-content-by-using-web-ui"] | ||
| = Limiting growth of synchronized content by using {ProjectWebUI} | ||
|
|
||
| [role="_abstract"] | ||
| You can limit the growth of content in the Library lifecycle environment on {ProjectServer} by restraining the number of package versions in synchronized repositories. | ||
|
|
||
| .Procedure | ||
| . In the {ProjectWebUI}, navigate to *Content* > *Products*. | ||
| . Select your product. | ||
| . On the *Repository* tab, select your repository. | ||
| . Set the *Mirroring Policy* to `Additive`. | ||
| . Define the number of retained package versions: | ||
| * Set *Retain package versions* to `1` to only keep the latest synchronized package version on {Project}. | ||
| * Set *Retain package versions* to `2` or higher to keep multiple package versions on {Project}. | ||
|
|
||
| .Additional resources | ||
| * xref:Mirroring_Policies_Overview_{context}[] |
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about moving the core of this to Best practices as a new list item? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not think about this before but I wish to keep it as is: the OOM problem has been specifically reported for Yum content from Oracle for Oracle Linux because Oracle only adds packages to repos instead of replacing them. This means that you might end up with dozens of package versions of large packages, such as
golang-bin.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand that the problem is specific to Oracle Linux, but I'm not entirely happy with adding a new heading for it.