As a VIC operation user, I need the ability to update or remove the container datastore, if the vic-machine create --container-store option is implemented. By default, the container VM files are stored in the same datastore as the one used by the image store.
Details:
supported operations:
update the container datastore
remove the container datastore
hot update:
no; need to restart the VCH to make the changes take effect.
input/output data format:
input: --modify --container-store datastore1 or --rm --container-store datastore1
output: N/A
impact on VCH/containerVMs:
VCH: Since we need to move container VM files from the original container datastore to the new datastore, we disallow updating/removing the container datastore if the VCH has running containers.
containerVMs: Running containers have to be stopped by the user before this operation to prevent storage IO when updating the container store.
is upgrade needed:
yes, since the --container-store option is not enabled yet.
Acceptance Criteria:
add the ability to update or remove the container datastore.
even with container store support, we might end up with a simple solution as well. That means no container move, delete or even power off due to container store update.
User Statement:
As a VIC operation user, I need the ability to update or remove the container datastore, if the
vic-machine create --container-store
option is implemented. By default, the container VM files are stored in the same datastore as the one used by the image store.Details:
--modify --container-store datastore1
or--rm --container-store datastore1
--container-store
option is not enabled yet.Acceptance Criteria: