I think we can provide this. Some questions:

Would space under https://dl.fedoraproject.org/pub/alt/ be ok?

What would you want it called? okd-crc?

Who would be uploading content to this place? A human? Several humans?

How often would they change?

Is any backup/retention needed?

Would like @dustymabe, @vrutkovs, @lorbus, @ngompa to render their opinions as well.

1. Space under "https://dl.fedoraproject.org/pub/alt/" is probably fine for our purposes.
2. okd-crc seems like an appropriate name for the folder.
3. A few humans would be doing the uploads initially. I would be responsible for the immediate future. Eventually we want to leverage CI.
4. We would upload a new release on the release cadence of OKD4. So, every two-three weeks.
5. Probably only need to keep one previous revision just incase we blow something up in a release.

1. No preference on exact URL, alt seems fine
2. +1, okd-crc sounds good
3. Few humans (Charro, me, Christian for a start). Eventually CI would do that
4. Usual cadence is two weeks
5. Hopefully we'll upload the artifact to Github as well, but backing up current + previous versions should be sufficient

I have no opinion. Thanks for working on this

So, the alt space should work fine for now... if you do move to a CI upload/using tokens, I think a better fit at that point would be a s3 bucket.

If it's ok to switch this down the road when/if that happens, I can make the alt space now.
I need the fas account name of everyone who will be uploading there in order to add them to the right group.

Thanks!

That works for us.

@vrutkovs, @lorbus, and @cgruver are the users that need access.

ok. I have added you 3 to our hosted-content group. Note that YOU are responsible to make sure you don't upload non free content or non distributable items, etc.

You will all want to make sure you have a ssh key in your fas account.

You can then ssh to secondary.fedoraproject.org and go to /srv/alt/okd-crc/ and sync your content to there.

Let us know if you run into any problems with it...

I added my public SSH key to my FAS account.

ssh cgruver@secondary.fedoraproject.org is timing out. Does it take a while for the key to sync?

I've run a sync, can you try again now?

I am unclear on how to execute the rsync. @Kevin indicated that ssh protocol would work, but secondary.fedoraproject.org is not listening on port 22. It looks like it just has rsyncd listening on 873.

Nmap scan report for secondary.fedoraproject.org (38.145.60.22)
Host is up (0.022s latency).
Other addresses for secondary.fedoraproject.org (not scanned): 38.145.60.24 38.145.60.23
rDNS record for 38.145.60.22: dl-iad01.fedoraproject.org
Not shown: 997 filtered ports
PORT    STATE SERVICE
80/tcp  open  http
443/tcp open  https
873/tcp open  rsync

Oops. Sorry about that, it's 'secondary01.fedoraproject.org' for ssh. secondary.fedoraproject.org just aliases to our proxies.

Try secondary01.fedoraproject.org

Thanks! That works.