Details
Critical Description
It has been announced, that RHOS-01 cloud [1] is going to act as a secondary production cloud in RDU2 that can host your workload in parallel with RHOS-D.
Every user of RHOS-D will have access to their projects both in RHOS-01 and RHOS-D.
Quota in RHOS-01 will be the same as we currently have in RHOS-D effectively meaning that our quota doubles for the duration of the Transition Period.
Action items:
1. Obtain business application ID within the Transition Period [2], [3]: DONE
SNOW Ticket: https://redhat.service-now.com/surl.do?n=RITM1087390
Application ID: CRW-001
2. Get an access to RHOS-01 cloud:
SNOW Ticket: https://redhat.service-now.com/surl.do?n=RITM1106650
3. Move all Jenkins nodes to RHOS-01 cloud, leaving QE OCP nodes on RHOS-D.
4. Make sure our preference for quota split is recorded at [4]: split between RHOS-D and RHOS-01 (equally 50% and 50%).
5. Make sure we split our workflows between the two clouds before the end of the Transition Period (middle of February 2022).
!!! Failure to do so and being over half of our quota usage will result in inability to spin any instances on the cloud where we are over half of our quota after the Transition Period ends (middle of February 2022). !!!
Update from PnT RHOS team:
We have reminded you that the Application ID has become a mandatory step for every existing or new project requested to be open in RHOS-01.
The compliance with this requirement remains essential and needs to be followed.
Unfortunately, the requirement to add Application ID into the process came at the very last moment and the current ServiceNow workflow is not ready to accomplish this requirement automatically.
We are in the discussion about how to implement this new requirement with Infrastructure Architect, Platforms Tech Lead and ServiceNow Group Tech Lead. The solution needs to be incorporated into the current process and it will take some time to complete this.
Work to do by D&O jenkins team: team needs to implement HA for openstack cloud plugin to be able to switch between rhos-d and rhos-01:
- there is a custom script for that, some info in the related MR (it is not integrated to jenkins): https://gitlab.cee.redhat.com/ocs/ocs4-jenkins/-/tree/master/scripts/python/psi_rhos_selector
- CCITJEN-1250 openstack-cloud: permit disabling cloud
- CCITJEN-75 openstack-cloud: Ensure next clouds are tried when one starts failing or run out of quota
[1] https://dashboard.rhos-01.prod.psi.rdu2.redhat.com
[2] https://gitlab.cee.redhat.com/psi/psi-osp/-/blob/master/docs/FAQs.md#302
[3] https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0007368
[4] https://docs.google.com/forms/d/1D7CyKdvQJJdwiWR9qRmmyienFd9jYZ-uqwLsj87YoEc/edit
