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-9215) Marvin test to check vm deployment in vpc tier if nic type is vmxnet3
Date Thu, 07 Apr 2016 02:42:25 GMT

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

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

Github user swill commented on the pull request:

    https://github.com/apache/cloudstack/pull/1316#issuecomment-206664435
  
    I am not sure how that tests this code though.  I have that same setup, but I don't think
I have the ability to test this configuration.  Am I wrong?


> Marvin test to check vm deployment in vpc tier if nic type is vmxnet3
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9215
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9215
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>            Reporter: Sanjeev N
>            Assignee: Sanjeev N
>
> Marvin test to check vm deployment in vpc tier if nic type is vmxnet3.
> If sytemvm nic type is vmxnet3, debian os takes little more time to discover the nic
after hot plugin compared to nic type E1000. So vm deployment fails.
> Adding new test to validate this functionality with nic type vmxnet3.
> Steps followed in the test:
> 1.Set systemvm.nic.type to Vmxnet3 and restart MS
> 2.Create VPC
> 3.Create Tier
> 4.Deploy one guest vm and make sure no issues in vm deployment
> 5.Reset the nic type to old value



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

Mime
View raw message