XML

Word

Printable

Epic Name:
binding-plugins-ga
Story Points:
77
Acceptance Criteria:
Hide

The binding plugin mechanism GA'd downstream

The binding plugin mechanism available upstream in a way we feel comfortable marking as GA downstream

KCS article clearly describing what interfaces can be used to build a supportable binding plugin

No downstream docs

No QE

No UXD
Show
The binding plugin mechanism GA'd downstream The binding plugin mechanism available upstream in a way we feel comfortable marking as GA downstream KCS article clearly describing what interfaces can be used to build a supportable binding plugin No downstream docs No QE No UXD
Current Status:
Green
Epic Status:
To Do
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done
Ready-Ready:

dev-ready, doc-ready, po-ready, qe-ready, ux-ready
Status Summary:

Hide

Should be ok...

Show
Should be ok...
Target Version:

CNV v4.19.0

Goal

Graduate the binding plugin mechanism, so we can ship solutions based on binding plugins to our customers.

User Stories

As a Red Hat partner, I want to use a well defined and stable interface to build network solutions for my customers.
As Red Hat, we want to ship bindings based on the plugin mechanism without having to risk that upstream changes will break our solutions.

<List of things not included in this epic, to alleviate any doubt raised during the grooming process.>

blocks

CNV-45524 OVN: Graduating user-defined primary networks in Virtualization

1.	upstream roadmap issue	New	Unassigned
2.	upstream design	New	Unassigned
3.	upstream documentation	New	Unassigned
4.	upgrade consideration	New	Unassigned
5.	CEE/PX summary presentation	New	Unassigned
6.	test plans in polarion	New	Unassigned
7.	automated tests	New	Unassigned
8.	downstream documentation merged	New	Unassigned