Bug 1967683

Summary: [OKR7] Shorten the feedback loop between integration "customer 0" DFGS and the "upstream" DFGs.
Product: Red Hat OpenStack Reporter: Artom Lifshitz <alifshit>
Component: openstack-novaAssignee: Artom Lifshitz <alifshit>
Status: CLOSED WONTFIX QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 17.0 (Wallaby)CC: dasmith, eglynn, jhakimra, kchamart, sbauza, sgordon, vromanso
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-23 13:45:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Artom Lifshitz 2021-06-03 15:14:21 UTC 
[This is an OKR 7 tracker RFE. For more information on ORK 7 as it applies to DFG:Compute, see https://docs.google.com/presentation/d/1xaYcX1S0K1kejcxHiAV0QhD7J0q7A1aj_h2UvusUMIs/edit]

Title:

Shorten the feedback loop between integration "customer 0" DFGS and the "upstream" DFGs.

Details:

Two open questions:

1. How do we notify integration DFGs of new features coming down the pipeline?

2. Integration DFGs need to give us a heads up when they're doing things - ex: PerfAndScale giving us a heads that they're running a test.

Comment:

---

AIs:

1. In the upstream -> integration direction: information sharing to other DFGs *before* an upstream cycle (but after planning), similar to how we do after a release to CEE/field. Need to figure out way to target the audience.

2. In the integration -> upstream direction: systematic proactive heads up for large integration tests.
Comment 2 Artom Lifshitz 2022-09-23 13:45:07 UTC 
This went nowhere, closing.