Loading...

XML

Word

Printable

Epic Name:
As a cloud operator, I want to validate parts of NodeSet config, before the point of no return (EDPM adoption) - continuation
Story Points:
2
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Parent Link:
OSPRH-813Red Hat OpenStack 18.0 Data Plane Adoption
Epic Status:
To Do
Feature Link:
OSPRH-813 - Red Hat OpenStack 18.0 Data Plane Adoption
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done
Intelligence Requested:
Market:

Add a validation that systemd-container package is installed before starting adoption.

If the package wasn't installed for OSP17, all workloads will be killed during EDPM adoption.

DoD proposal after discussions:

Implement a role in edpm-ansible to perform validation that systemd-container package is installed
Add a validation step that runs the validation role into the Adoption docs and tests (a separate EDPM Deployment with just a single service for the validation). This comes before the point of no return from rollback perspective, last thing before we start adoption of the data plane nodes.

Acceptance criteria:

The epdm-ansible validation role has been properly added.
The validation role has been added in the adoption test-suite CI before EDPM Adoption.
The documented procedure is verified with standalone.

clones

OSPRH-5665 As a cloud operator, I want to validate parts of NodeSet config, before the point of no return (EDPM adoption)