apache / apache/cloudstack

Provision to assign disk offering(s) for volumes(s) when migrate VM with volumes

Abierto
#11,739 1 comentario 0 reacciones 0 asignados Ver en GitHub
status:needs-functional-definition type:improvement
Lenguaje dominante
Java
Estrellas
3.1k
Forks
1.4k
Merge medio
6 d 19 h
PR fusionados (30 d)
32

Descripción

### 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.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza comparando el flujo existente de Migrate volume, que solicita un disk offering, con el flujo de Migrate VM with volumes descrito en el issue. Reproduce la migración desde el almacenamiento local a NFS y verifica que el comportamiento final permita asignar disk offerings adecuados con comprobaciones o que los asigne automáticamente sin una discrepancia en el tipo de pool.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
java
Área
backend, cloud, infrastructure
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
38/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.