You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/05/02 12:33:12 UTC

[jira] [Commented] (CLOUDSTACK-8894) Dynamic scaling is not restricted when destination offering has changes in the vGPU type

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

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

Github user rhtyd commented on the pull request:

    https://github.com/apache/cloudstack/pull/868#issuecomment-216193049
  
    @anshul1886 please rebase against latest master and push -f, update on status of your PR



> Dynamic scaling is not restricted when destination offering has changes in the vGPU type
> ----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8894
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8894
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>
> Steps:
> 1.Install and configure XenServer 6.5 with vGPU enabled . Enabled dynamic scaliing 
> 2. Deploy VM using K160Q type windows 7 template with PV tools installaed and dynamic scaling enabled 
> 3. Tried dynamic scaling with offering which has K180Q defined.
> Observation: 
> 1. Currently vGPU resource dynamic scaling is not supported. But CloudStack returns success and updating the VM details with new offering details including new vGPU type. 
> 2. But from Xenserver , There is no change with vGPU type and it remains with old vGPU type. This is not correct
> Expected Result:
> Dynamic scaling should be restricted when source/destination offering has vGPU type on a vGPU enabled VM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)