-
Notifications
You must be signed in to change notification settings - Fork 17
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
(rpm-)ostree pkg: prepare for jigdo #13
Comments
Thanks @cgwalters for the early warning. This is really cool work BTW, and it's awesome that it simplifies the server side so much! In cockpit we need to support both the traditional and jigdo ostree for a while, so I figure we need some dynamic API tests. Is there already some early Atomic image available which uses jigdo, or some COPR or jigdo-ostree.rpm that can be installed into an existing Atomic image, to play around with this? Even though the D-Bus API might not be final yet, it would already allow us to get more familiar with the new concepts and look-and-feel. Will the switch to ostree-jigdo be possible on upgrades to existing Atomics? I figure the current ostree remote+refspec might be sitting in /etc and are not part of the ostree itself; can the upgrade process somehow adjust them? I figure once this goes life, we don't want to keep the old ostree repos around for a long time? |
Moving this over to cockpit-ostree, which got split out a while ago. @cgwalters, did that go anywhere? There are some questions in the previous comment. Thanks! |
Not yet; will update the rojig issue with instructions once I am able to work on it more. |
We are in the process of a fundamental rework to rpm-ostree to add rojig mode ♲📦.
Since the current
ostree.js
pkg does things like parse refspecs, it's going to have to learn about this. We're still debating the design on the DBus side though.It'd actually be very useful to think about how this looks and feels on the Cockpit side. Note this also strongly intersects with our push for automatic updates 🆕⌚️.
One thing I want to specifically highlight is this subthread.
Basically the analogies we're currently building are:
For example, after jigdo there's no separate
fedora/27/x86_64/atomic-host
andfedora/27/x86_64/updates-testing/atomic-host
. A bit like traditional, you'drpm-ostree rebase --repo=updates-testing
which would be short for going fromfedora:fedora-atomic-host
tofedora-updates-testing:fedora-atomic-host
.The text was updated successfully, but these errors were encountered: