#8354 access to openshift docsbuilding
Closed: Will Not/Can Not fix 4 years ago by jibecfed. Opened 4 years ago by jibecfed.

Hello,

can you please allow me to see the content of docsbuilding?
URL is: https://os.stg.fedoraproject.org/console/project/docsbuilding/browse/pods

As a maintainer of the localization of our docs, I need to see if an error occurred to eventually fix it myself or ping appropriate community member.

If not an issue, I think every Fedora user should have read access.

ping @asamalik


As discussed with @asamalik, @jibecfed I ll add you to the appowner that will give you permission to login in OpenShift and cancel/trigger builds.

Metadata Update from @cverna:
- Issue assigned to cverna

4 years ago

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

4 years ago

I have access to this: https://os.stg.fedoraproject.org/console/project/docsbuilding/browse/builds
but I don't know how to add a build or restart an existing build
I would have expect to see a button, or maybe I just don't have the apropriate authorizations?

I receive this error message: Could not load config maps. Reason: configmaps is forbidden: User "jibecfed" cannot list configmaps in the namespace "docsbuilding": no RBAC policy matched

the openshift documentation is a little bit confusing for my level of technical knowledge, I don't understand where is the documentation for a classical user : https://docs.openshift.com/container-platform/3.11/welcome/index.html

any advice on where to start is welcome <3

I tried to deploy a new image: Cannot create deployment config "internationalization". deploymentconfigs is forbidden: User "jibecfed" cannot create deploymentconfigs in the namespace "docsbuilding": no RBAC policy matched

Metadata Update from @jibecfed:
- Issue status updated to: Open (was: Closed)

4 years ago

So, all of our applications in staging or production openshifts are managed via ansible.

Adding you as an application owner does give you some rights to the application, but they are all read-only. If you want to make changes you MUST commit them to ansible and run the ansible playbook.

Here's the docsbuild config: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/openshift-apps/docsbuilding
Here's the docsbuild playbook: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playbooks/openshift-apps/docsbuilding.yml

Perhaps it would be good to try and schedule some time next week to meet up on irc and go over things or help you get done whatever it is you are wanting to do. :)

Thanks for your answer.

I understood OpenShift is meant to allow the the community for autonomy to host some services.
OpenShift itself already is a complex tool to me, and indeed this additional layer of Ansible indeed prevents my own usage as you guessed it.

Am I mistaken if I think OpenShift should be easier to use? What can we do to lower the barrier?
I basically don't have much to do, it's more or less a cron task.

No rush, but where could we discuss this and how to discuss it without adding an additional stress on the infrastructure team?
Please note most of links from this page leads to 404: https://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/openshift.html

About my goal regarding doc's automation, I already sent an email to misc with explanations as we met at FOSDEM. Let me know how we should proceed with OpenShift requests, I have no idea

Metadata Update from @jibecfed:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

4 years ago

Thanks for your answer.
I understood OpenShift is meant to allow the the community for autonomy to host some services.

You are thinking of the communishift cluster. Yes, that one is run differently. There we just provide the platform and it's all up to the user(s) to manage their applications.
I'm happy to give you access there if you like.

OpenShift itself already is a complex tool to me, and indeed this additional layer of Ansible indeed prevents my own usage as you guessed it.
Am I mistaken if I think OpenShift should be easier to use? What can we do to lower the barrier?

Well, for our prod/stg clusters we want a high barrier, because these are the things we monitor and support and would try and bring up if they ever go down.

I basically don't have much to do, it's more or less a cron task.
No rush, but where could we discuss this and how to discuss it without adding an additional stress on the infrastructure team?
Please note most of links from this page leads to 404: https://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/openshift.html
About my goal regarding doc's automation, I already sent an email to misc with explanations as we met at FOSDEM. Let me know how we should proceed with OpenShift requests, I have no idea

Well, we can discuss on the infrastructure list, or if you can find a time we could discuss on irc?

Would love to figure out a way to help you out. Perhaps communishift is a better fit for what you are trying to do.

I understood the openshift was community handled and was not creating any request for it here because of that... Let's make it open for everyone to read and contribute: https://pagure.io/fedora-infrastructure/issue/8691

Login to comment on this ticket.

Metadata