Epic Goal

Provide metric aggregation and dashboards that report on multiple ACS deployments in a similar manner to Global Hub ACM hub aggregation.

Why is this important?

See linked feature ACM-13694

Working Agreement to add External Components | ACM Program 

                                                                         Template*

This will be entered into an Epic in Jira (replaces Done Criteria) 

(Epic Component - External) 

What is this document?

This document aims to serve the ACM Program, part of the Hybrid Cloud Management organization, as external components are added to the ACM release scope/purview. Additionally this document  provides insight to how the ACM Program operates.

This document sets expectations to assist with external components that wish to onboard with ACM.

This document also serves as a source of information for reference purposes -  including links to important documents, presentations,  calendars, and other information.

Working Agreement

Program Manager

ACM: * Robyn Haignere

Component * Global Hub - ACS Integration

Architecture forum DDR presentation <date> * DDR - ACM Design Decision Document - ACS Security Violations Dashboard - Google Docs

• Review Date: ACM Architecture call – 2024/09/04 09:28 EDT – Recording

Engineering Sponsor

ACM:Joydeep
New Component Engineering lead:jhernand-rh 

OWNER: Eco-Systems, ACS Integration for Global Hub

Release Manager 

ACM:rh-ee-lbainbri 

New Component:GH ACS integration

Product Management  Lead

ACM: * bweidenb@redhat.com 

New Component: * oourfali 

OWNER: Ecosystems

ACM QE Lead 

NOT required for DEVPREVIEW

ACM: * rh-ee-ecai 

New Component: * Plz assign oourfali 

OWNER: ACM / Component

ACM Product Experience Scott Suehle―

• plz assign oourfali 

  ACM Product Support Tiago M. De Rizzo

  ACM Documentation Brandi Swope

NOT required for DEVPREVIEW
ACM: * Brandi Swope Christopher Dawson

New Component: * ???

OWNER: Ecosystems
 
 
 
 
 

Calendar: ACM Calendar - A place to share common ACM events.
Release Calendar: ACM Release Calendar -  Details Y and z stream milestone dates and Train durations. 
Z-stream Schedule: ACM - Z Stream Release Schedule
Release Scrum Meeting:  ACM 2.12 Release SCRUM Weekly meeting held on Mondays at 9AM (US-ET). Purpose of meeting is to discuss current Y stream release in-depth and raise blockers/issues. Ran by Release Manager. 
Program Call Meeting: Program Call Doc - Purpose: Discuss program level updates, process updates, risks and blockers that need cross-program collaboration. Ran by Program Manager. Cadence varies. Bi-weekly after a Y stream release until 5 weeks prior to the Y stream release and cadence will be weekly.
Product Pages: Detailed status, schedule, people list. Updated weekly. 
Program Google Group: Subscribe Here
Playbook: Advanced Cluster Management Playbook Details process, etc - how we work |

Check-list to complete. (If not already complete, a Jira story or task should be created per item)

As a DEVPREVIEW, almost none of this applies

• ✅Architecture Forum & Design Decision Review document approved
• ⚠️Onboarding source code into Stolostron/repo
• ⚠️Build - Konflux
• ⚠️Build - CPaaS?
• ⚠️Installer - Feature flag enabled/disabled
• Meet ACM security code and image scanning
• Playbook
• ❓Disconnected from Internet (installs / works in this mode)

• ❓FIPS readiness
• ❓Infra Node support (install-to)
• ❓Proxy support (OpenShift Global Proxy)

• ❓QE
• ❓Hub Backup / Restore compliance
• ❓Hub Scale / Performance
• ❓Global hub eventing

• ❓Documentation
• ❓Threat Model
• ❓Support Skills transfer
• ❓Must-gather