Bug 2037652 - [Doc] NFS StorageProfile resource should be edited with accessModes and volumeMode values before migration
Summary: [Doc] NFS StorageProfile resource should be edited with accessModes and volum...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: Documentation
Version: 2.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.3.0
Assignee: Steve Goodman
QA Contact: Maayan Hadasi
Steve Goodman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-06 09:08 UTC by Maayan Hadasi
Modified: 2022-03-22 15:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-22 15:24:25 UTC
Target Upstream Version:
Embargoed:
sgoodman: needinfo-


Attachments (Terms of Use)

Description Maayan Hadasi 2022-01-06 09:08:17 UTC
Description of problem:
Using MTV 2.3 - the user should update the spec of the StorageProfile resource of a non-provisioner OCP storage class like NFS in order to run a migration using this storageClass

For example:
$ oc get storageprofile nfs -oyaml
...
spec:
  claimPropertySets:
  - accessModes:
    - ReadWriteOnce
    volumeMode: Filesystem


According to Fabien:
"It is a valid choice, and also the safest mode, as all provisioners support it. It won't allow you to live migrate the VM in CNV, but it's fine for MTV."


Additional info:
Please see: https://bugzilla.redhat.com/show_bug.cgi?id=2036479#c4


Version-Release number of selected component (if applicable):
MTV 2.3


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Comment 1 Steve Goodman 2022-02-01 14:19:11 UTC
Ilanit, can you please weigh in on this?

Comment 2 Steve Goodman 2022-02-03 14:05:09 UTC
Please disregard my previous comment.

Comment 3 Steve Goodman 2022-02-22 07:50:38 UTC
User story:

I'm using static provisioning, such as NFS, for MTV migration. In order to enable MTV migration using static provisioning (static storage class), I need to do the following:
Edit the storage profile corresponding to the storage class.

.Procedure

1. Edit the storageprofile corresponding to the the storage class:

$ oc edit storageprofile <name_of_storageclass>

2. Edit the section beginning with `spec:{}` like this:
----
spec:
  claimPropertySets:
  - accessModes:
    - ReadWriteOnce
    volumeMode: Filesystem
----

Open questions:
- Where does the user get this spec from? 
- Here I refer to non-dynamic provisioning as "static provisioning". Is that the correct term?

In the NOTE at the top of 2.2. Storage support and default modes[1], change the "MTV applies the default settings" to "you need to apply the following settings in the storageprofile for your storage class.

[1] https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.2/html-single/installing_and_using_the_migration_toolkit_for_virtualization#about-storage_mtv

Comment 4 Steve Goodman 2022-02-22 15:50:43 UTC
I see that the procedure is already documented in the OpenShift Virtualization documentation under _Customizing the storage profile_[1], so I'll just add a link to that.

[1] https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html-single/virtualization/index#virt-customizing-storage-profile_virt-creating-data-volumes

Comment 7 Steve Goodman 2022-03-10 17:43:16 UTC
Waiting until 2.3 GA to merge.


Note You need to log in before you can comment on or make changes to this bug.