I would like to ask for publicly accessible (via https) storage space, that can be used to share unofficial builds of FCOS prior regular infra will be setup for non-intel architectures(ppc64le, s390x, aarch64). I expect ~30G(4~2.53) of space will be used/needed. At maximum 50-60G. I think that something like AWS S3 or extended home quota will be good fit. CC'ing @dustymabe @cverna
# When do you need this to be done by? (YYYY/MM/DD) Sooner better :).
Where is the data going to be built and how do you envision it needing to be uploaded and available for? Some locations are better solutions than others depending on what is needed.
Metadata Update from @smooge: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: aws
I would like to use community HW/VMs at universities(current plan, but if there will be other resources in Fedora infra I would be happy to used them, only thing that is really necessary is ability to run VM on the host) that I have access to do the builds and upload via ssh/sftp/https. Builds will be equivalent to the regular developer/local builds, but published so people that can't do builds, from various reason, can test and provide feedback, so really more a scratch space. I would hope that it won't be needed for more than ~6 months, until we have built infra for the arches(most notably openshift clusters), but all the technical stuff needs to be further discussed and as I'm not that well versed on the Fedora/CentOS infra side. I would much appreciate any help and pointers.
To note I would like to store just ~3 last successful builds or alike, but I'm open to suggestions of best practice there.
ok. I setup a fedora people group space for this.
login to fedorapeople.org and look in /project/fcos-images/
Those will appear on the web in: https://fedorapeople.org/groups/fcos-images/
There's no quota there, but please try and keep space to 30GB or so.
If for some reason that doesn't work for you, just re-open this and we can go with another solution.
Enjoy!
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks @kevin! @jcajka were you able to get this to work?
Login to comment on this ticket.