PR for the code in https://pagure.io/releng/pull-request/6872

I'm not aware of a way to make a PR for the repos; I think a releng admin will need to do this:

cd https://kojipkgs.fedoraproject.org/atomic/  (wherever that is on a filesystem)
mv 25 repo
ln -s repo 25
for rel in 26 rawhide; do
  ostree --repo=repo pull-local ${rel}
  mv ${rel}{,.orig}
  ln -s repo ${rel}
done
ostree --repo=repo summary -u

we identified quite a few work items that need to accompany some work like this. See https://pagure.io/atomic-wg/issue/231#comment-432157.

It's better to not rush this change to a unified repo setup IMHO. Could we possibly have static deltas from 25 to 26 by "importing" the last f25 two week release commit into the f26 repo and generating the static delta from that?

I don't understand the blockers for doing a repo unification. That script above should work, and leaves compat symlinks for existing clients.

Did you have specific concerns?

OK, I did find another potential issue: https://pagure.io/pungi-fedora/pull-request/267

Basically none of those bullet items linked in that comment have been done. I'd like to be successful with this switch and not foobar it. I believe we are going to achieve a lot of our goals that we have wanted over the past few months soon after fedora 26 release. My main goal right now is to make sure we get fedora 26 out smoothly and hopefully without bugs and I want to minimize changes so that we can achieve that goal. I'm sorry if I'm being a bit conservative. Please trust me and I'll make sure this (or equivalent) happens for the next release (or maybe in the middle of the f26 cycle if we're confident we have covered all angles).

But yes, we can import the 25 commit into the 26 repo and generate a delta that way. That's literally just:

ostree --repo=26 pull-local 25 fedora-atomic/25/x86_64/docker-host

We've gone so many releases now without doing a unified repo though and it's just getting crazy.

• work to make a unified repo

That's what my script does.

• verify the backup strategy for the repos we serve is sufficient

I renamed the existing repos to .orig - someone could easily rsync them elsewhere too or whatever.

• need to set up tooling for pruning the ostree repo

This can come after; it's not like we've pruned the 23/24 repos either yet. But that part is https://pagure.io/pungi-fedora/pull-request/267

• sym link needs to be updated when new NUMBER release is first released

Not relevant for this.

• ostree creation process needs to point to new unified repo

The compat symlinks should keep things working.

• 2wk script needs to be updated to update unified repo

That's what my PR does.

Pinged @dustymabe in IRC to update the status here.

we generate static deltas now for the last release of N-1 to the first few releases of N. this can be closed.

@dustymabe thanks for the update - much appreciated.

Closing per above note.