> + VirtualMachine vm = api.getVirtualMachineApi(group).get(id);
> + String location = vm.location();
> + final VMImage ref = new VMImage(CUSTOM_IMAGE_PREFIX + group,
> CUSTOM_IMAGE_PREFIX + storageAccountName, disks[0], disks[1], location);
> +
> + return userExecutor.submit(new Callable<Image>() {
> + @Override
> + public Image call() throws Exception {
> + return imageReferenceToImage.apply(ref);
> + }
> + });
> +
> + }
> +
> + @Override
> + public boolean deleteImage(String id) {
> + return false;
Hmm... if we do custom image from existing VM, it generalizes the existing VM
and we cannot run it anymore. Also it uses the storage of that VM to create
image there. Potentially we can do multiple custom images of that same VM there
but it does not make any sense as all images are similar. That makes it
possible to destroy whole original VM with all related custom images. That is
actually only reasonable way to do this. If we want to destroy only created
image and leave that "useless" VM there, we need to use Blob storage API (like
we need in list images).
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/291/files/8a39037237f5cccc7d100bc58a9a82bdb89924b1#r68012829
