Purpose (The Why): The Service Delivery team should be engaged from the outset and informed of the approval of any new services. ** Once the service has been approved and kick off has been facilitated, It is important to proactively liaise with the SRE team to complete formal onboarding. This process can take some time and connecting with SRE from the outset will reduce the risk of issues or delays at a later phase. The onboarding includes tasks such as defining Standard Operating Procedures (SOPs) and ensuring adherence to cloud native development best practices. The entry point for this involves raising a JIRA in the Service Delivery Jira Project space. The requester should also inform the program manager for the service that a JIRA has been created. The program manager can then actively work with the Service Delivery program manager to ensure that the request is scheduled.  

If I don't complete this task, what is the risk

SRE onboarding is NOT required to be completed by Service Preview. However, it is recommended that this task starts early as the end to end process for SRE Onboarding can take time. Once executive approval and initial budget has been confirmed, the next step is to present to SAG. Following on from this the SRE Onboarding process can commence. It is important to bear in mind that SRE will have a backlog of items and as such, it is important to engage early to ensure that expectations are set with regard to timelines. You should ensure to include representatives from SRE in the program kick off

Activity

• Step 1: Create a SRE Onboarding Jira epic following instructions here: https://source.redhat.com/groups/public/sre-services/onboarding
  • Note above page is still a WIP - this is the direct link to creating the Epic & onboarding questionnaire: https://gitlab.cee.redhat.com/app-sre/contract/-/blob/master/content/service/jira_templates/service_onboarding.md#tenant-onboarding-epic
• Step 2: The onboarding will be reviewed and dispatched to the appropriate SRE team.
  • Once approved you will be able to start your self service onboarding. This involves completing an onboarding questionnaire as referenced in the above guide.
• Step 3: Follow the SRES Partnership Agreement guidance to understand SRES requirements and support for different type of releases (Service Preview to General Availability): https://source.redhat.com/groups/public/sre-services/sre_services_wiki/sres_partnership_agreement 

Responsible: Engineering, SRE

Consulted: Product Management, Program Management

Prerequisite/ Input:

• SAG Approval
• Executive Approval
• Initial Budget
• Create SRE Jira epic (project=SDE) and fill out SRE questionnaire 

Deliverable/ Competition criteria: Completion of SRE Onboarding questionnaire and associated acceptance criteria including cloud native requirement for SRE readiness:

• Your application MUST be prepared for compute node failure.
• Your application MUST be prepared for storage node failure.
• Your application’s staging environment MUST be identical to prod.
• Seamless application upgrades, OSD upgrades not impacting, OpenShift Dedicated (OSD) upgrades MUST NOT be service impacting to your component running on OSD.,
• Your application MUST be resilient during its own upgrade process and not experience any downtime.
• Applications MUST support rollback or rapid roll-forward.

Expected duration/ effort: weeks to months

Exception Process: This is a mandatory step that cannot get an exception.  You should discuss with SRE the minimum requirements as you move through the stages of service onboarding

How to get Help: Managed Services CoP GChat

Before you Close

• Before you close this JIRA, please confirm that SRE Onboarding has been completed
• Please ensure that sign off from SRE is documented here or provide links to related JIRAs or documentation confirming this
• This task is mandatory and must be completed where SRE are running the service (post Service Preview)
• Please reach out to roms-leaders@redhat.com with any questions