An Architectural Summary Document includes the service introduction, architectural diagram, feature roadmap, dependencies with other Red Hat products and technologies etc. Having SAG review and approval of the architectural design (ideally during the design phase) is required to continue onboarding a new cloud service.

Template/Example: See existing cloud services Architecture Documents here as reference.

Service Architecture Group (SAG)

SAG Source Space: https://source.redhat.com/groups/public/sag 

SAG is a group of lead engineers (distinguished engineers, technical leads, product owners, architects etc), collectively, this group possesses the knowledge of Red Hat business strategy and technical vision for cloud services. SAG is an advisory board and also provides a converging function, it helps ensure our efforts best align with our strategy by identifying risks, conflicts, and duplicates early on. 

To schedule SAG review and obtain SAG acks, send your architectural document to service-architecture@redhat.com (expect replies within 1 week) to attend one SAG meeting (an 1-hour session, scheduled every Monday/Thursday), your engineering lead/architect or product owner is expected to present the architectural summary, then SAG provides recommendations or approval during/after the session.

Template/Example: Clone the SAG Review Template, or use your architecture summary document to prepare and present.

Who

• Responsible: Engineering (engineering lead or architect)
• Accountable: Product Manager

SAG Contacts

• Get Help: SAG Office Hours is a monthly meeting where anyone can explore premature ideas with SAG, or ask technical questions before or after the SAG reviews.

• SAG Mail list: service-architecture@redhat.com
• SAG Slack channel: https://app.slack.com/client/T027F3GAJ/C03TFQJGP4Y
• SAG Individual Contacts: Jessica Forrester <jforrest@redhat.com>, Paul Bergene <pbergene@redhat.com>, Emmanuel Bernard <ebernard@redhat.com>, Christopher Duryee <cduryee@redhat.com>