All the projects on Communishift will be deleted every Fedora Linux release (6 months). If you need more than 6 months for your project, please open a ticket https://docs.fedoraproject.org/en-US/infra/communishift/#_removal_of_the_projects
Please don't delete my communishift-fedora-review-service project. I am using it for a production deployment of the Fedora Review Service.
communishift-fedora-review-service
If you wish the project to be migrated to a different OpenShift instance, please let me know which one. But until it is done, please exempt my project from the Communishift periodic removal.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: communishift, medium-gain, medium-trouble, ops
If your service is production ready and it's used by community, we can host it in Fedora OpenShift instance. Communishift is more for proof of concepts and testing.
@kevin What do you think?
Yeah, I would think we could roll it into staging -> production... it seems like it's a useful service.
Thank you guys. So can I simply start creating my own "openshift-apps" playbook and its respective role as described here https://docs.fedoraproject.org/en-US/infra/developer_guide/openshift/ or do you need to grant me some permissions or ack the project somehow?
@frostyx Yes, you can start working on the role. We just need to create a project for you on our OpenShift cluster.
@kevin I can't find any documentation for onboarding a new tenant for OpenShift, just found one for Communishift. I assume it will be similar.
The openshift-apps playbook is responsible for creating the OpenShift project (by using the openshift/project role) and assigning permission. No action on the OpenShift cluster is required beforehand.
openshift/project
I thought we did have a guide... it's quite different from communishift because everything has to be in ansible (at least in prod, stg is more open).
Login to comment on this ticket.