-
Notifications
You must be signed in to change notification settings - Fork 59
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
Support updating from local mirrors #240
Comments
I'm starting to add notes here, so we can more easily collect them into docs. To use a customized/mirrored updates backend, at least all of the following topics have to be covered:
|
Hi, any updates on this? thanks. |
I don't have any updates. Luca may have made some progress on the items he mentioned in #240 (comment). Will let him respond when he gets back. |
Pulp (https://pulpproject.org) supports mirroring repositories locally. Pulp also supports exporting repositories to a physical media and then importing them from that media in a disconnected environment. While Pulp does not currently support OSTree repositories, we would like to add OSTree support in the near future. Please file a story at https://pulp.plan.io/issues/new/ outlining the OSTree repository mirroring use case. Having clear use cases will help us plan and execute this effort. |
Linking #812 which should make it easier to support updating from a local registry |
As of recently, https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md is the successor to #812 One thing I'd note here is that as of rpm-ostree v2021.14 in Fedora, one can use ex-container encapsulate to mirror from the current production ostree repository into a container image, push that to an internal registry, and have a separate process which de-encapsulates for clients to use as an update source. But eventually, the goal of coreos layering is that we just update by default from a container image - and that the container-registries config for mirroring just works for OS updates too. |
For the subcase where the nodes have access to the Internet, but a local mirror is desired to reduce bandwidth, a simple OSTree strategy is:
(I.e. this is 1 and 3 of #240 (comment)) |
Suggest adding some discussion on the effect of different --depth values |
Any update on this ? Best regards. |
Many Fedora CoreOS nodes will update directly from our Cincinnati server and ostree repo, but there are two other use cases we should support:
We'll need tooling and docs for each.
EDIT(lucab): related but slightly different, #261 covers the "manual updates to air-gapped instances" scenario.
The text was updated successfully, but these errors were encountered: