Epic Goal

• Support volumeMode=Block via OADP datamover

• Why is this important? 

1. PV's can be volumeMode=[filesystem, block] we need to support both as it's common across the industry
2. kubevirt defaults to volumeMode=block and virt is a major use case for OADP

• Upstream Design

1. Board: https://github.com/orgs/migtools/projects/5/views/12?pane=issue&itemId=34986611
2. Velero Design: https://github.com/vmware-tanzu/velero/pull/6590
3. Velero Issue: https://github.com/vmware-tanzu/velero/issues/6548
4. WIP implementation: https://github.com/catalogicsoftware/velero_block/pull/1
5. Velero PR: https://github.com/vmware-tanzu/velero/pull/6680

• Downstream Design none yet

Scenarios

1. container app w/ PV in block mode
2. OpenShift-Virt vm's in block mode

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. Velero
2. ODF
3. Openshift-Virt

Open questions::

1. TBD 

Done Checklist

• [ x ] CI - CI is running, tests are automated and merged.

• [ ] Release Enablement <link to Feature Enablement Presentation>

• [ x ] 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 - 1 - Regression tests, All the existing tests should pass
• [ ] QE - Automated tests merged: <link or reference to automated tests>

• [ ] DOC - Downstream documentation merged: <link to meaningful PR>