-
Spike
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
3
-
False
-
-
False
-
-
-
Neutron Sprint 10, Neutron Sprint 11, Neutron Sprint 12, Neutron Sprint 13
-
4
-
Important
Summary:
- In RHOSO we run control plane services on OCP worker nodes and also have option to run OVN Gateway chassis in Pods. The Centralized dataplane traffic goes via these gateway chassis.
- This Spike is to check the impact of OCP updates on such traffics. As it was mentioned in recent discussion that OCP nodes get's rebooted as part updates. So we need to check/confirm on what all cases that happen.
- We can consider updates like OCP 4.16 GA to OCP 4.16.x latest or any mid version or series of updates, as an extension can also check OCP 4.16.x latest to OCP 4.18 upgrade
- The behavior should be checked in Multi node OCP instead of CRC as that's similar to what Customers use.
Goal:
- As part of this activity
- we should understand how OCP updates works in general in the field
- what all our control plane services and dataplane traffic get's impacted as part of the OCP updates and upgrades.
TimeBox:
- 1 weekÂ
Deliverables/Outcomes:
- Jira ticket for the identified issues
- Jira ticket for documentation update based on findings.
- Jir ticket for any CI coverage for such cases, need discussion with Update team to see if there is already in plan.
- is related to
-
RHOSSTRAT-668 Automated testing of OCP updates in a RHOSO environment
-
- In Progress
-
-
OSPRH-11636 Check on how to handle dataplane outage with OVS pods restarts
-
- Closed
-
- relates to
-
RHOSRFE-96 Document Impact of OCP updates on RHOSO Control and Dataplane
-
- Closed
-