non-disruptive migration needs to select correct share server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Carlos Eduardo |
Bug Description
Hi,
let's imagine the following scenario:
I have 2 share servers on the same host with the same share subnet (either intentionally setup by user or because the new share server limits created an additional one without end user interaction).
Now I want to non-disruptively migrate a share in one of those share servers within the host from one pool to another.
This is now sometimes throwing an error 'Migration for share <uuid> could not be performed because host-assisted migration is not allowed when share must remain writable, preserve snapshots and/or file metadata or be performed nondisruptively.' in migration_
Both seem valid targets and simply the first one is selected in the choose_
Either this could use the same logic like creating shares from snapshot (parent share server aka migration source share server) or choose_
What do you think?
BR,
Maurice
tags: | added: share-migration |
Changed in manila: | |
milestone: | xena-1 → xena-2 |
Changed in manila: | |
milestone: | yoga-1 → yoga-2 |
tags: | added: bugsquash yoga |
+1
I see, you have at least two compatible share servers in the destination host, but there is a incompatible share server from migration perspective, since NetApp driver doesn't support migrating across share server non-disruptively. share_server_ compatible_ with_share' , usint the metadata dict. In this way we can provide the source share server id and the information about the operation ('operation': 'share_migration') and the driver can choose the correct destination share server.
This can change depending on the share driver, so, the only way is to give the responsability to share drives. One idea is to provide more info in 'choose_