-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
Use osp deploy plugin from ci-framework in all integration uni* and VA/DT base in compute component CI jobs to replace install_yamls
-
18
-
L
-
False
-
-
False
-
Not Selected
-
Proposed
-
Proposed
-
In Progress
-
Proposed
-
Proposed
-
25% To Do, 25% In Progress, 50% Done
-
-
Component jobs only deploy via install_yamls and while they do provide the capacity for covering a large portion of feature sets, they still have infra CI and code related limitations that prevent us from being able to test even basic features at times. This coupled with the messaging that install_yamls development should be limited to developer workflow means that we need to be more reliant on adding feature coverage at the integration line. If there has been a change to allow for VA/DT (Devscript) deployment at the component line that could change, but without that support we sometimes are required to add those workflows into integration.
Also, RDO peridoc multnode jobs will be decomissioned, so we should switch multi-cell adoption to the integration pipeline but that also requires ditching install yamls for osp deploy plugin
Acceptance Criteria:
- No uni* integration CI jobs downstream related to the Nova/Compute scenarios are using install yamls
- No coverage lost after decomissioning multinode RDO jobs upstream