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

• In the past, a suggestion to provide Cloud-provider specific profiles was made ( BZ1636205 / BZ1787363 ).  The idea was never implemented mostly due to time/technical difficulties of not being able to discover a Cloud-provider type based on a pure OS-level detection.  In OpenShift, however, we are in a much better position to discover the Cloud-provider, mostly by labels/annotations which are provided during the installation. 

Why is this important?

• Currently, NTO ships AWS-specific tuning for NVMe devices on all platforms.  While this setting does no harm on other Cloud-providers, we need to have the ability to set custom tuning as this one per Cloud-provider.

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. …

Open questions::

1. Implementation, can we use providerId: aws|gce|azure:// from the Node object ?

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>