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

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• Enable GRO for the interfaces and veths on OCP hosts in order to improve UDP throughput.

Why is this important?

• One of the kernel developers estimates that we could see a 2x improvement in UDP throughput with this configuration enabled.

Scenarios

1. Any use case where UDP throughput to or from containers is important should benefit from this.

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. The necessary kernel support will only be available starting in RHEL 8.5. Our CoreOS images will need to be based on 8.5 before we can use this.

Previous Work (Optional):

1. …

Open questions::

1. What is an appropriate default value for the GRO delay parameter?
2. Does the delay parameter need to be user-configurable?

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>