cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9707) deployVirtualMachine API should fail if hostid is specified and host doesn't have enough resources
Date Thu, 02 Mar 2017 08:47:45 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891824#comment-15891824
] 

ASF GitHub Bot commented on CLOUDSTACK-9707:
--------------------------------------------

Github user anshul1886 commented on the issue:

    https://github.com/apache/cloudstack/pull/1868
  
    @ustcweizhou, In my opinion we should not do that as that way we are giving them option
of silently deploying VM on some host which he might not be aware of. As after specifying
host he is expecting that VM will be deployed on that host. If he is ok with deploying VM
on different host then he can try deploying VM in next attempt without specifying hostid.


> 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)

Mime
View raw message