Learn more about these different git repos.
Other Git URLs
ostree has had static deltas for years now; it makes us look less than stellar if people aren't getting them. We do this as part of the FAH release process, but at the moment there is no such thing for FAW which just drops out of pungi. Simplest thing is probably to add it to Ansible for now, literally just ostree --repo=/path/to/repo static-delta generate --if-not-exists fedora/27/x86_64/workstation. (However, the benefits of deltas will be greatly maximized if we batch updates)
ostree --repo=/path/to/repo static-delta generate --if-not-exists fedora/27/x86_64/workstation
@walters we discussed this in the release engineering channel this morning.
A daily delta probably doesn't make sense - what tempo did you have in mind for static deltas?
A daily delta probably doesn't make sense
Yes, This is a whole topic. Basically for FAH we have a clear delineation of releases so that we can know good logical start and end points. With FAW we don't currently have that. Most days there isn't much change in the content in FAW because of batched updates, but it does happen often enough that bodhi users select to go directly to stable rather than batched that it's not reliable.
We could do some smart things like use the fedora/27/x86_64/updates/workstation ref for normal daily composes and then only update fedora/27/x86_64/workstation once there was a security fix OR a batched compose completes. When we update fedora/27/x86_64/workstation we would also generate a static delta.
fedora/27/x86_64/updates/workstation
fedora/27/x86_64/workstation
The above is the only logical way I see to get something useful without making it more complicated.
A daily delta probably doesn't make sense -
But there aren't updates every day for FAW! Remember rpm-ostree (unlike every other image system run by pungi) has built-in change detection. And in practice a lot of things are in the bodhi batches.
There's a ticket somewhere where we did an analysis...it was something like an update roughly every 2-3 days, and with not too much effort could be a lot closer to the weekly batch if we were a bit more aggressive on pushing back against non-batched updates for FAW content in Bodhi.
However, this all blocks on the pungi fix being deployed; from just today's update:
# rpm-ostree status State: idle; auto updates disabled Deployments: ostree://fedora-27:fedora/27/x86_64/workstation Version: 27.79 (2018-02-21 18:21:23) BaseCommit: f790540bd8b3aca3fb3ec4b5afb2598d04b0928e6279ebdd41fe145e4319e5aa GPGSignature: Valid signature by 860E19B0AFA800A1751881A6F55E7430F5282EE4 LayeredPackages: cri-o emacs fuse-sshfs git-evtag gstreamer1-plugin-openh264 keepassx krb5-workstation libvirt-client mozilla-openh264 oci-kvm-hook opensc origin-clients pcsc-lite-ccid powerline strace tmux vagrant-libvirt virt-manager xsel ykclient ykpers LocalPackages: podman-0.2-3.git3d0100b.fc27.x86_64 ● ostree://fedora-27:fedora/27/x86_64/workstation Version: 27.78 (2018-02-20 16:50:04) BaseCommit: 06d0a2129f0c8924aa7d32285bc8ce819def7f68f0498cadab22e8df50260dd8 GPGSignature: Valid signature by 860E19B0AFA800A1751881A6F55E7430F5282EE4 LayeredPackages: cri-o emacs fuse-sshfs git-evtag gstreamer1-plugin-openh264 keepassx krb5-workstation libvirt-client mozilla-openh264 oci-kvm-hook opensc origin-clients pcsc-lite-ccid powerline strace tmux vagrant-libvirt virt-manager xsel ykclient ykpers LocalPackages: podman-0.2-3.git3d0100b.fc27.x86_64 # ostree show --raw f790540bd8b3aca3fb3ec4b5afb2598d04b0928e6279ebdd41fe145e4319e5aa|less ... rpmostree.rpmmd-repos': <[{'id': <'Fedora-27-updates-20180221.0-Everything-20180221180240'>, 'timestamp': <uint64 1519235983>}, {'id': <'https:__kojipkgs.fedoraproject.org_compose_27_latest-Fedora-27_compose_Everything__basearch_os_-20180221180240'>, #
Metadata Update from @mohanboddu: - Issue tagged with: meeting
@mohanboddu plans to bring this up in the Mar 13 releng meeting.
I'd say let's drop this. We've got too much other stuff going on.
Closing it for now and we will look at it later.
Metadata Update from @mohanboddu: - Issue close_status updated to: Get back later - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.