Epic Goal

• The goal of this epic is to test the storage operators available across architectures of different endianness. Currently, the only supported configuration that could obverse this problem is amd64 and s390x. The objective of this epic is to ensure that a volume created using a storage driver on one of these arches can be used by a node of the other architecture without running into issues accessing the data.
• Specifically, this epic aims to cover the following operators:
  • ocs
  • odf
  • redis
  • postgres
  • ibm spectrum scale
  • volsync-product
• However, upon discussions with the team, scanning for the endianness issue should be focused on ocs and spectrum scale.

Why is this important?

• …

Scenarios
1. …

Acceptance Criteria

• (Enter a list of Acceptance Criteria unique to the Epic)
• …

Dependencies (internal and external)
1. …

Previous Work (Optional):
1. …

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.