OCP/Telco Definition of Done
Epic Template descriptions and documentation.

<---

It's not clear yet if OVN-K Interconnect (OVN-IC) will resolve the Local Zone problem, need to run spikes to develop that Epic/feature

--->

Epic Goal

• The MTU customizations enforced in the installer when edge compute pool are present in AWS deployment (introduced in 4.13) must be reviewed with new OVN-K Interconnect feature (available in 4.14)
• Depending of the results> Remove any MTU enforcement and leave OVN-IC resolve the connectivity between zones (for IC each node has it's own zone)

Why is this important?

• The cluster network MTU is lowered 7 times (from 9k to ~1.2k) when installing a cluster with Local Zones subnets. It was created to enable the feature as AWS MTU between the Local Zone and in the region are 1300. AWS Supports "hybrid mode" and the VPC network does not requires to lower the interface MTU as it supports per Path MTU discovery (PMTUD), but SDN (OVN-K, O-SDN) does not support, so services inside the cluster network was impacted.
•  

Scenarios

1. ...

Acceptance Criteria

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

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. AWS Local Zones - Phase II (Full IPI) SPLAT-657 
2. OVN Interconnect work: Part2 (GA) https://issues.redhat.com/browse/SDN-3733
3.  

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>