Provision to assign disk offering(s) for volumes(s) when migrate VM with volumes
- Langage dominant
- Java
- Étoiles
- 3.1k
- Forks
- 1.4k
- Merge moyen
- 6 j 19 h
- PR mergées (30 j)
- 32
Description
### problem
Currently, Migrate VM with volume(s) bypasses the service and disk offerings of the volumes, as the target pools for migration are specified and volumes can be moved between shared to local and local to shared pools without any offering change. The subsequent operations on these volumes were impacted due to disk offering and pool type mismatch.
There should be provision to admin/operation, to assign disk offering(s) for volumes(s) with proper checks, when migrate VM with volumes (mainly when change in pool type - shared to local, local to shared). Similar provision was already there for Migrate volume, and it prompts to change the disk offering.
### versions
ACS 4.20.x , KVM Hypervisor, NFS / Local Storage.
### The steps to reproduce the bug
1. Deploy a VM with ROOT and DATA volumes on Local storage.
2. Migrate VM with volumes to NFS (Shared) storage - the Disk Offerings still point to Local storage offering.
### What to do about it?
Allow operator to assign disk offering(s) for volumes(s) when migrate VM with volumes, or auto assign the suitable offering.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par comparer le flux Migrate volume existant, qui demande un disk offering, avec le flux Migrate VM with volumes décrit dans l’issue. Reproduisez la migration du stockage local vers NFS et vérifiez que le comportement une fois terminé permet soit d’attribuer des disk offerings appropriés avec des contrôles, soit de les attribuer automatiquement sans incompatibilité de type de pool.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- backend, cloud, infrastructure
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 38/100