#907 Deploy a cbs.stg.centos.org public env
Closed: Fixed 2 years ago by arrfab. Opened 2 years ago by arrfab.

Per discussion in infra and releng meeting, and also to publicly be able to test new features/upgrades with community members, we'll deploy a cbs.stg.centos.org koji env
What we need :

  • public https://cbs.stg.centos.org node
  • internal NFS storage (small one)
  • internal proxy (to reflect how real infra is also reaching allowed external repositories)
  • kojid builder attached to kojihub
  • all needed .stg. TLS certs (from accounts.stg.centos.org setup) and public one for frontend

Metadata Update from @arrfab:
- Issue marked as blocking: #696

2 years ago

Metadata Update from @arrfab:
- Issue assigned to arrfab
- Issue tagged with: cbs, centos-build-pipeline, centos-common-infra, high-gain, high-trouble

2 years ago

We have https://cbs.stg.centos.org kojihub/web node online now and with one registered/active kojid builder.
Next steps:

  • tune http proxy for builder[s]
  • setup some external repos (like for cbs)
  • setup some tags (like for cbs)
  • sync users/groups from accounts.stg.centos.org and validate access

Current status : all previous points are done and working

cbs-stg hello
नमस्कार, arrfab!

You are using the hub at https://cbs.stg.centos.org/kojihub/
Authenticated via client certificate /home/arrfab/.centos-stg.cert

cbs-stg list-permissions --mine
Permission name   
------------------
appliance         
build             
build-infra       
image             
livecd            

But to be complete, I'll deploy in parallel a new dedicate small instance for signing (testing purposes) with fake gpg keys (not the real ones) and nothing would be going out

It's all working/validated/tested so closing this ticket and jumping on dependent ones

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Boards 2
CBS Status: Backlog