[
https://issues.apache.org/jira/browse/CLOUDSTACK-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769012#comment-15769012
]
ASF subversion and git services commented on CLOUDSTACK-9683:
-------------------------------------------------------------
Commit 743dd4249cc813fbd30a130bb10fb17158ae92f5 in cloudstack's branch
refs/heads/master from [~rohit.ya...@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=743dd42 ]
Merge pull request #1839 from shapeblue/CLOUDSTACK-9683
CLOUDSTACK-9683: system.vm.default.hypervisor will pin the hypervisor for VR
too with this fix
* pr/1839:
CLOUDSTACK-9683: system.vm.default.hypervisor will pin the hypervisor for VR
too with this fix
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
> 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)
