Yeah, so possible options:

1. Could make a small seperate nfs volume for this so it can be updated by releng and used in openshift for mirrormanager? yes, we want to be very carefull to never expose the packages out to the world.

2. Could make some kind of volume in openshift and figure out some way to sync data to it?

I suppose here we only need the metadata, so it could be small, but it does update somewhat regularly...

Another option (although perhaps more complex):

1. Openshift has a 's3 compatible' storage built in. We use it now to pull websites to proxies. Perhaps we could set it up so we could push to a volume the contents...

We likely need this very soon due to releng 12275

Related issue: https://pagure.io/releng/issue/12275

I’ve received confirmation that the request has been received by the current maintainers of the publishing process and should be completed in the next couple of days.

Is there a plan on how to proceed when that happens?

@kevin @abompard

I just received confirmation that the binaries are now published and available, and indeed they are.

$ curl -I http://ciscobinary.openh264.org/openh264-2.4.1-2.fc41.x86_64.rpm
HTTP/1.1 200 OK

Is there some temporary workaround that we could do here?

@kevin @abompard

I'd defer to @abompard here. If you want me to make a nfs volume I can...

Yeah, please do that. I think an NFS volume would be easier to share between Openshift and the rest of our infra. Thanks!

ok. I have created a 'openshift_prod_codecs' volume.

It's mounted on /mnt/ on sundries01 right now, and I have copied the existing /srv/web/codecs.fedoraproject.org/ content to it.

I think we should probibly just mount it at /srv/web/codecs.fedoraproject.org, but that will take a freeze break right now, or we could wait until after freeze.

We still need to create a pv in openshift and setup mm to mount it. @abompard can you do that part?

We also need to copy the new content to it (the latest we sent to cisco). @patrikp can you do that part?

Moving forward we also need to setup something to compose these thats not ODCS (since we will be retiring it very soon).

Thanks, I'll deal with the openshift part. It looks like this mount isn't available from staging, am I correct? If so, do we have an equivalent share for staging or should I just ignore it there?

Do you think this change would require a FBR in prod? I'd think so.

I didn't make a staging one... since we never really made staging composes of this. I'd say just ignore on staging...

If we do want to add staging we could, but it would mean we would need to do builds there of it, then composes of the repo, then have some way to test it, which I guess would require asking cisco if they could do another staging repo and send them rpms for it? But that seems like a big lift. ;(

Sure, now that the beta freeze is over I'll just update prod :-)

OK, the Openshift part is done!

ok. I mounted the volume on /srv/web/codecs.fedoraproject.org on sundries01 now.

So, I think now we are set to have @patrikp sync the new repodata to /srv/web/codecs.fedoraproject.org on sundries01 and mm should pick up the new repodata and start serving the new rpms on cisco's side.

Did I miss anything here?

I'm getting a "read-only filesystem" error when trying to sync the repodata.

Could this perhaps be related to the btrfs bug that you mentioned in the weekly releng meeting the other day, @kevin?

Nope. :) It was that I didn't set it to be read-writable. ;(

Should be fixed now, try again?

It works, should be synced now. :thumbsup:

@abompard can you see if mirrormanager updated? I'm getting reports that it's not showing new version in rawhide...

As I replied on https://pagure.io/releng/issue/12275#comment-937076, I don't see a rawhide directory in the codecs space. So the Mirrormanager does not recognize a rawhide repo and does not add it to the database.

OK, it seems that everything works as expected and the releng ticket [1] is now closed.

We have another problem and that is that odcs (used to generate the OpenH264 composes) was recently retired. [2][3]

This ticket is about the process of updating the repos, so I suppose it can be closed and another one should be opened to talk about how to generate the composes in the future?

We already have a request for sending openh264-2.4.1-1.el10_0 to Cisco. [4]

[1] https://pagure.io/releng/issue/12275
[2] https://pagure.io/fedora-infrastructure/issue/12192
[3] https://pagure.io/fedora-infra/ansible/pull-request/2266
[4] https://pagure.io/releng/issue/12385

CC: @kevin @jnsamyak