[
https://issues.apache.org/jira/browse/CLOUDSTACK-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760703#comment-15760703
]
ASF GitHub Bot commented on CLOUDSTACK-9683:
--------------------------------------------
Github user blueorangutan commented on the issue:
https://github.com/apache/cloudstack/pull/1839
@abhinandanprateek I understand these words: "help", "hello", "thanks",
"package", "test"
Test command usage: test [mgmt os] [hypervisor] [additional tests]
Mgmt OS options: ['centos6', 'centos7', 'ubuntu']
Hypervisor options: ['kvm-centos6', 'kvm-centos7', 'kvm-ubuntu',
'xenserver-65sp1', 'xenserver-62sp1', 'vmware-60u2', 'vmware-55u3',
'vmware-51u1', 'vmware-50u1']
Additional tests: list of comma separated tests with paths relative to the
`test/integration` directory, for example: component/test_acl_listvm.py,
component/test_volumes.py
Note: when additional tests are passed, you need to specify mgmt server os
and hypervisor or use the `matrix` command.
Blessed contributors for kicking Trillian test jobs: ['rhtyd', 'jburwell',
'murali-reddy', 'abhinandanprateek', 'PaulAngus', 'borisstoyanov', 'karuturi']
> system.vm.default.hypervisor Does Not Pin Hypervisor Type of Virtual Routers
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9683
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9683
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.9.0.1
> Reporter: Abhinandan Prateek
> Assignee: Abhinandan Prateek
> Fix For: 4.9.2.0
>
>
> The system.vm.default.hypervisor global setting should pin the type of
> hypervisor on which VRs are created. Therefore, if a user VM is created in a
> VMware cluster with a new isolated network, the associated VR should be
> created on a KVM host. However, the VR is being created on the same
> hypervisor as the user VM instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
