#352 Create project for Cloud SIG in the CI openshift cluster
Closed: Fixed 2 years ago by siddharthvipul1. Opened 2 years ago by amoralej.

As the recommendation is to move out of ci.centos.org, Cloud SIG wants to move to the new openshift cluster apps.ci.centos.org.

IIUC console is published in https://console-openshift-console.apps.ocp.ci.centos.org

Is autorization for projects based on CAS groups?

Also, let me know if there is any doc that has been useful for others about how to move jobs to the new jenkins on openshift.


@amoralej I'll let @siddharthvipul1 answer all your questions , and there is even a template for how to ask for namespace, but yes, authentication is using your accounts.centos.org credentials (or accounts.fedoraproject.org, now all the same and merged)

From the template

=== CentOS CI - OCP4 migration

  • Do you have a namespace in OpenShift 3.6 Cluster? No
  • Do you need duffy bare-metal/vms checkout capability? Yes
Project_name: cloudsig-ci (any naming convention I need to respect?)
Project_admins:
 - amoralej@redhat.com
 - apevec@redhat.com
 - jcapitao@redhat.com
 - jpena@redhat.com
 - ykarel@redhat.com

Metadata Update from @siddharthvipul1:
- Issue assigned to siddharthvipul1
- Issue tagged with: centos-ci-infra, low-gain, low-trouble

2 years ago

IIUC console is published in https://console-openshift-console.apps.ocp.ci.centos.org

Correct, when you login (after I have created the namespace in a few minutes, you will see your project there)

Is autorization for projects based on CAS groups?

No (at least not yet, we have plans to look into it), the way we do this is keeping users (that you provided in the following comments) in a yaml file (private repository) and use ansible + openshift template to create group and role bind to projects.. so if you want to add a user, you can open a ticket and I usually do these in a few hours (if I am around).

Also, let me know if there is any doc that has been useful for others about how to move jobs to the new jenkins on openshift.

https://centosci.github.io/ocp4-docs/
This should have some content that will help you migrate. If you have any confusion, do tag me to the text/email or comment

  • [x] create namespace for cloudsig-ci
  • [x] generate ssh keys and enter in duffy db + fetch api key
  • [x] create jenkins instance
  • [x] create pv to bind to jenkins
  • [x] update timeout variable in deployment config

@amoralej hey, so if you login to https://console-openshift-console.apps.ocp.ci.centos.org/dashboards , you should be able to see the project and jenkins instance url (as you would be able to see in routes) is: https://jenkins-cloudsig-ci.apps.ocp.ci.centos.org/

I have access to both openshift console and jenkins console.

Thanks for your help!

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

2 years ago

I just realized there was a typo in the users list, the right mail for apevec is:

apevec@gmail.com

@siddharthvipul1 may you update the users list or do you want me to create a new ticket?

@siddharthvipul1 I don't have access, my CAS/FAS email is apevec@gmail.com

FTR Siddhart added me, I can access jenkins-cloudsig-ci now!

Login to comment on this ticket.

Metadata
Boards 1
CentOS CI Infra Status: Backlog