-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
-
False
-
-
100% To Do, 0% In Progress, 0% Done
-
0
-
0
Feature Overview (aka. Goal Summary)
Allow Datacenter customers to leverage existing SAN infrastructure with OCP Virt with dynamic provisioning and live migration.
Goals (aka. expected user outcomes)
As Data Center OCP admin, I can add my existing expensive SAN infrastructure to OCP nodes to host VM workloads, so that I can better migration VMs from vSphere to OCP Virt.
The goal of Dev Preview release is to to provide MVP functions with limited docs, to get early feedback from customers.
Requirements (aka. Acceptance Criteria):
A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.
General:
- Allow Datacenter customers to leverage existing SAN infrastructure with OCP Virt
- Support multiple VMs (virtual disks) out of a single LUN with dynamic provisioning for end-user self service with high level of isolation
- Support live migration of VMs (--> RWX)
MVP Scope:
- 1 LUN per VG
- many VMs per VG
- VM can have multiple PV, but they must all be on the same VG (== StorageClass)
- No multi-path
- LiveMigration of a single VM from one node to another (RWX)
- Snapshots/Cloning/ReSizing (CSI conformity >=V1.5)
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | both |
Classic (standalone cluster) | yes |
Hosted control planes | yes (using LVMs as storage for etcd), no special needs |
Multi node, Compact (three node), or Single node (SNO), or all | all |
Connected / Restricted Network | yes |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | x86 and Arm |
Operator compatibility | yes |
Backport needed (list applicable versions) | no |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | no |
Other (please specify) |
Questions to Answer (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
- HW for CI testing - AWS? ReUse from RHV team?
Out of Scope
- Full fledge CI, DevPreview has minimum CI testing
- multi-path SAN (–> TechPreview scope)
- Thin pool only
- other subprovisoner backends then SAN-LUN (NFS, etc)
Background
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
<your text here>
Customer Considerations
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.
<your text here>
Documentation Considerations
- Docs needs to be added to the [existing LVMS docs |http://example.com] which might need a refactoring to allow for the two different backend types (LVM and SAN).
- Constraints and Limitations / OutOfScope needs to be clearly documented
Interoperability Considerations
Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.
- OCP Virt
- Hosted Control Plane
- links to