Per discussion with @bstinson , and to validate the migration for #285 , we'll need a minimal working koji setup working on top of CentOS 8-stream.
Requirements:
Metadata Update from @arrfab: - Issue tagged with: centos-common-infra, centos-stream, high-gain, low-trouble
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @siddharthvipul1: - Issue untagged with: centos-common-infra, centos-stream
Metadata Update from @arrfab: - Issue tagged with: centos-common-infra, centos-stream
storage/nfs was configured virtual machines deployed TLS certificates all created (both internal IPA STG CA and external for letsencrypt) kojihub was deployed and publicly visible (through haproxy) here : https://koji-mbox.stg.centos.org/koji/
Next step : adding one builder (should be easy) but something different for mbs as we don't have any properly defined role for this
mbs
koji list-hosts Hostname Enb Rdy Load/Cap Arches Last Update x86-01.mbox.stg.centos.org Y Y 0.0/2.0 x86_64,i686 2021-07-07 13:01:52
We now have one builder ready to be used and attached to hub .. for mbs I'll wait for @bstinson to be available and we can take it from there. Marking as groomed for now
groomed
Metadata Update from @arrfab: - Issue tagged with: groomed
@bstinson : when do you think that we can schedule time to close that request ? once done and validated, we can proceed with #285
Metadata Update from @arrfab: - Assignee reset
Metadata Update from @arrfab: - Issue priority set to: Waiting on External (was: Needs Review)
[backlog refinement] : bugs triaging so we can close this one as parent ticket #285 will be worked on differently and we don't need stg koji setup anymore
Metadata Update from @arrfab: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.