-
Epic
-
Resolution: Done
-
Critical
-
rhos-18.0 Feature Release 1 (Nov 2024)
-
None
-
Implement RHOSO 18+ certification procedure for Networking partners
-
19
-
False
-
-
False
-
Not Selected
-
Proposed
-
No Docs Impact
-
To Do
-
OSPRH-5331 - 3rd party Neutron plugin / ml2 driver support
-
?
-
No impact
-
0% To Do, 0% In Progress, 100% Done
-
Regression Only
-
-
RHOSO 18+ changed the way a cluster is deployed (tripleo -> OCP) and the way tests are executed (direct tempest execution vs test-operator). Both changes significantly affect certification procedures for partners, incl. Networking integration.
This Epic is to implement certification procedure for RHOSO 18+ that would cover both aspects.
The definition of Done here should include:
- a checklist to validate that a cluster provided for certification uses recommended points of integration blessed by Networking DFG;
- a list of test scenarios (tempest, perhaps something else? - need to check what we did before) that must pass for a partner integration to be confirmed as complying;
- documentation updates to relevant guides.
Context:
- There was already a certification program before 18, so it would make sense to adopt the existing approach, if applicable (e.g. the list of tempest scenarios may be directly ported to the new program);
- The checklist doesn't require automation - a cert engineer should be able to follow the instructions though without significant prior knowledge.
Relevant links:
- https://gitlab.cee.redhat.com/certification/rhoso-cert - tools to trigger tests and collect logs (started by Alan B from Storage team - we should check if it needs some work for Networking cases - probably not though)
- https://docs.google.com/document/d/1uU8YZtvzy27NdUGAbKDhXPnRYKGq4qArg1SS6qkuSs8/edit - draft for policy guide
- https://docs.google.com/document/d/1YsQ7bgswUhSYqzjW8qPFCvfD6p59mhLfHsrX5v4tAjo/edit - draft for workflow guide
- OSP17 docs for partners somewhere here: https://docs.redhat.com/en/documentation/red_hat_software_certification/2024
Note: this Epic is not supposed to implement actual integration points in service and OpenStack operators to allow to customize neutron ml2 drivers. This Epic will take care of certification guide / procedure only. See the linked Epic for the actual implementation.
- is blocked by
-
OSPRH-3678 As a partner, I want to be able to integrate Neutron with my custom ML2 driver and SDN back end [Tech preview]
- Resolved
- mentioned on