[
https://issues.apache.org/jira/browse/CLOUDSTACK-9707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891870#comment-15891870
]
ASF GitHub Bot commented on CLOUDSTACK-9707:
--------------------------------------------
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1868
@anshul1886
Considering about backwards compatibility. I would like to add the global
setting, then users will have two options
(1) deploy vm fails if specified host does not have enough capacity. This
is what this PR wants to do.
(2) deploy to other hosts if specified host does not have enough capacity.
In this case, the specified host can be regarded as the perferred host. This is
also what cloudstack works currently.
> deployVirtualMachine API should fail if hostid is specified and host doesn't
> have enough resources
> --------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9707
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9707
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Anshul Gangwar
> Assignee: Anshul Gangwar
>
> While using hostid parameter, vm gets deployed on another if the host
> given is running out of capacity. If host id is specified the deployment
> should happen
> on the given host and it should fail if the host is out of capacity. We are
> retrying
> deployment on the entire zone without the given host id if we fail once. The
> retry,
> which will retry on other hosts, should only be attempted if host id isn't
> given.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
