[
https://issues.apache.org/jira/browse/JCLOUDS-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376946#comment-15376946
]
Ladislav Thon commented on JCLOUDS-1139:
----------------------------------------
https://github.com/jclouds/jclouds-labs/pull/302
> Azure: suspending a node also deallocates it
> --------------------------------------------
>
> Key: JCLOUDS-1139
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1139
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-labs
> Affects Versions: 1.9.2
> Reporter: Ladislav Thon
> Labels: azurecompute
>
> (Note that this is about the "classic" {{azurecompute}} provider, _not_ about
> {{azurecompute-arm}}.)
> The {{AzureComputeServiceAdapter.suspend}} calls the
> {{VirtualMachineApi.shutdown}} method with a parameter of
> {{StoppedDeallocated}}. Per
> https://msdn.microsoft.com/en-us/library/jj157195, this parameter makes Azure
> release all the resources used by the VM. This causes the suspend operation
> to take a lot of time and any other following resume will also take a lot of
> time.
> I think there should be an option that would cause
> {{AzureComputeServiceAdapter.suspend}} to call the
> {{VirtualMachineApi.shutdown}} method with a parameter of {{Stopped}}. That
> way, suspending and resuming are much faster.
> Tearing down the VM entirely (i.e. {{destroyNode}}) would still always use
> {{StoppedDeallocated}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
