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-9683) system.vm.default.hypervisor Does Not Pin Hypervisor Type of Virtual Routers
Date Mon, 19 Dec 2016 09:43:58 GMT

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

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

Github user abhinandanprateek commented on the issue:

    https://github.com/apache/cloudstack/pull/1839
  
    @blueorangutan help


> 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)

Mime
View raw message