Purpose (The Why): An architectural summary is required for continue onboarding a new cloud service. The service team is required to present an architectural summary at Service Architecture Group (a.k.a. "Distinguished Filter", SAG). The 1 hour SAG review session ensures that the SAG has upfront visibility of the services and can identify any issues or gaps at an early stage across Red Hat portfolio. The information provided at this stage will also be applicable to the SRE Onboarding process.

Do This: Use the Architecture Summary Template to prepare your SAG review or cover the information in your Architecture Summary document. Reach out the SAAG service-architecture@redhat.com to schedule the review session, a SAG sponsor might be assigned to you to guide you through the process and further action items.

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

This is a required task. You MUST complete an architectural summary and present to SAG in order to proceed with your service and secure SRE commitment to onboarding

Responsible: Engineering (engineering lead or architect)

SAG Contacts: Paul Bergene <pbergene@redhat.com>, Emmanuel Bernard <ebernard@redhat.com>, Christopher Duryee <cduryee@redhat.com>

Prerequisite/ Input: Executive Approval confirmed

Deliverable/ Competition criteria: <Service> Architecture Summary presented, and approval obtained from SAG. 

Expected duration/ effort: hours to days to weeks (maximum 2 weeks)

Examples / Best Practices: https://drive.google.com/drive/u/0/folders/1iyTbbGE8ol2cae0701xnOJJFucKaEXVz 

Exception Process: ** This is a mandatory step that cannot get an exception. You MUST receive approval from SAG to proceed. 

Before you Close

• Please link to SAG Jira ticket with the outcome

How to get help:

• Reach out to roms-leaders@redhat.com with any questions
• Managed Services CoP GChat (general)
• mas-architecture@redhat.com