for OKD purposes we are looking to make a build of CentOS Stream CoreOS and would like to get space available for downloads and to make AMI images available in all regions.
Metadata Update from @arrfab: - Issue tagged with: centos-build-pipeline, feature-request, high-gain, medium-trouble
Metadata Update from @arrfab: - Issue assigned to arrfab
@ausil : as a follow-up of the discussion we had last week at CentOS Connect, let's just come with a plan of multiple artifacts list (like .iso , .qcow2 and others) and where they should land. From that list we'd be able to adapt releng process to push these where needed
Metadata Update from @arrfab: - Issue untagged with: medium-trouble - Issue tagged with: high-trouble
Metadata Update from @arrfab: - Issue priority set to: Waiting on External (was: Needs Review) - Issue tagged with: blocked
status update : there were multiple discussions (but unfortunately not in this ticket) and while https://cloud.centos.org/centos/scos/ is now ready to serve content (underlying infra was modified and moved to AWS Cloudfront), we are now just waiting for Stream CoreOS team to start pushing content . Blocked for now
status update : last week I worked with someone from coreos team and they can manually push artifacts, as shown on https://cloud.centos.org/centos/scos/9/prod/streams/ Just need one last info from them and then updating git/ansible and then close ticket
discussed with stakeholders (outside of this ticket) and they confirmed it's all working so closing at centos infra side
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.