Loading...

XML

Word

Printable

Type: Epic
Resolution: Done
Priority: Undefined
Fix Version/s: None
Affects Version/s: None
Component/s: Plumbing
Labels:

Epic Name:
Support for Ansible playbook for offline migration
Activity Type:
Product / Portfolio Work
Hierarchy Progress Bar:

7% To Do, 3% In Progress, 90% Done
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Green
Status Summary:

Hide

[May 08, 2025] Migration playbook updates to meet Ansible collections standards. PR expected to be submitted by mid of next week. Development PR for standardising the approach to be submitted by early next week. ETA to complete this epic to be determined by mid next week. Worst case ETA June 09, 2025.

[April 10, 2025] Ansible validation workflow guide is expected to filled today. Performance degradation bug (OCPBUGS-54575) reported by Perf Team. Awaiting perf report between Manual migration vs Ansible based migration.

[April 03, 2025] Anisble team to get back on the process to publish playbooks to automation hub. Current ETA for docs, automation hub and performance testing should be ready by May 15, 2025.

[March 20, 2025] PR merged, functional testing done and CI in place. Documentation in progress. Performance team flagged a risk on their capacity for this Epic. Decision to be made today.

[March 10, 2025] The current priority for Miheer is to get the PR merged and refine any add-ons later. Doc work for this Epic has also been initiated.

Show
[May 08, 2025] Migration playbook updates to meet Ansible collections standards. PR expected to be submitted by mid of next week. Development PR for standardising the approach to be submitted by early next week. ETA to complete this epic to be determined by mid next week. Worst case ETA June 09, 2025. [April 10, 2025] Ansible validation workflow guide is expected to filled today. Performance degradation bug ( OCPBUGS-54575 ) reported by Perf Team. Awaiting perf report between Manual migration vs Ansible based migration. [April 03, 2025] Anisble team to get back on the process to publish playbooks to automation hub. Current ETA for docs, automation hub and performance testing should be ready by May 15, 2025. [March 20, 2025] PR merged, functional testing done and CI in place. Documentation in progress. Performance team flagged a risk on their capacity for this Epic. Decision to be made today. [March 10, 2025] The current priority for Miheer is to get the PR merged and refine any add-ons later. Doc work for this Epic has also been initiated.
Size:
None

Target Version:

openshift-4.19
Release Blocker:
None

WSJF:
0

Template:

Networking Definition of Planned

Epic Template descriptions and documentation

Epic Goal

Support for Ansible playbook for offline migration

Why is this important?

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

Priority+ is set by engineering
Epic must be Linked to a +Parent Feature
Target version+ must be set
Assignee+ must be set
(Enhancement Proposal is Implementable
(No outstanding questions about major work breakdown
(Are all Stakeholders known? Have they all been notified about this item?
Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement
details and documents.

...

Dependencies (internal and external)

...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

CI - CI is running, tests are automated and merged.
Release Enablement <link to Feature Enablement Presentation>
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Polarion: <link or reference to Polarion>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>

account is impacted by

CORENET-973 Enhancements to pre and post checks of Ansible Playbook for Offline Migration

impacts account

OCPBUGS-49911 machine config can't sync until it is paused

Closed

OCPBUGS-49912 During rollback from OVNKubernetes to OpenShiftSDN, after changing network type in Network.config.openshift.io causing cidr conflict errors