[
https://issues.apache.org/jira/browse/CLOUDSTACK-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760486#comment-15760486
]
ASF GitHub Bot commented on CLOUDSTACK-9683:
--------------------------------------------
GitHub user abhinandanprateek opened a pull request:
https://github.com/apache/cloudstack/pull/1839
CLOUDSTACK-9683: system.vm.default.hypervisor will pin the hypervisor…
… for VR too with this fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shapeblue/cloudstack CLOUDSTACK-9683
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1839.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1839
----
commit ca8a00442c260e0f86079b1cde71cf06291e7fa4
Author: Abhinandan Prateek <[email protected]>
Date: 2016-12-19T07:36:02Z
CLOUDSTACK-9683: system.vm.default.hypervisor will pin the hypervisor for
VR too with this fix
----
> 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)
