You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Currently oneimage command can clone an image to a different image datastore but that image will have a different ID. The migrate command would keep the image ID moved to a different image datastore. In that case there is the following situation that can lead to problems:
A new image datastore is being added and the old one has to be deleted
The images are cloned in the new datastore, the old one is deleted
In this moment
VMs that rely on any image on the old datastore images can't be recreated easily (the image that was used to created them does not exist, they don't know about the clone on the new datastore)
The database reflects that the images on the old datastore are still being in use by those VMs
The command may also have to update:
/VM/TEMPLATE/DISK/{DATASTORE,DATASTORE_ID,IMAGE,IMAGE_ID,SOURCE} on the VMs running that depend on the migrated image
/VMTEMPLATE/TEMPLATE/DISK/{DATASTORE,DATASTORE_ID,SOURCE} on the templates that depend on the migrated image
Description
Currently
oneimage
command can clone an image to a different image datastore but that image will have a different ID. The migrate command would keep the image ID moved to a different image datastore. In that case there is the following situation that can lead to problems:In this moment
The command may also have to update:
/VM/TEMPLATE/DISK/{DATASTORE,DATASTORE_ID,IMAGE,IMAGE_ID,SOURCE}
on the VMs running that depend on the migrated image/VMTEMPLATE/TEMPLATE/DISK/{DATASTORE,DATASTORE_ID,SOURCE}
on the templates that depend on the migrated imageUse case
The use case for the command would be
It should:
IMAGE_ID
andDATASTORE_ID
exist and ifDATASTORE_ID
is an image datastoreIMAGE_ID
toDATASTORE_ID
keeping itsIMAGE_ID
and name (IMAGE
field)/IMAGE/{SOURCE,PATH,DATASTORE,DATASTORE_ID}
of the imageIMAGE_ID
: update the fields/VMTEMPLATE/TEMPLATE/DISK/{DATASTORE,DATASTORE_ID,SOURCE}
IMAGE_ID
: update the fields/VM/TEMPLATE/DISK/{DATASTORE,DATASTORE_ID,SOURCE}
After that, the
/IMAGE/VMS
field of the image should be consistent, and the templates and the vms tooInterface Changes
It may be relevant to have a way to migrate image from the interfaces, but it's out the original scope of the problem
Additional Context
It may be possible that the image source and datastore must be updated somewhere else
Progress Status
The text was updated successfully, but these errors were encountered: