cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelven Yang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-5761) consoleproxy.session.max parameter is not honored in spinning up extra CPVMs
Date Fri, 10 Jan 2014 23:15:50 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kelven Yang resolved CLOUDSTACK-5761.
-------------------------------------

    Resolution: Not A Problem

How many CPVMs will be launched is determined both by consoleproxy.session.max and consoleproxy.capacity.standby.


> consoleproxy.session.max parameter is not honored in spinning up extra CPVMs
> ----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5761
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5761
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller
>    Affects Versions: 4.3.0
>         Environment: Latest build from 4.3branch with commit :
> 95b6a7b96dab1c77e25987d6fe6003b4447281f1
>            Reporter: Sanjeev N
>            Priority: Critical
>              Labels: hyper-V,, hyper-v, hyperv
>             Fix For: 4.3.0
>
>         Attachments: management-server.rar
>
>
> [Hyper-v] consoleproxy.session.max parameter is not honored in spinning up extra CPVMs
> Steps to reproduce:
> ================
> 1.Bring up CS in advanced zone with Hyper-v cluster
> 2.Wait for the system vms to comeup
> 3.Deploy few guest vms
> 4.Open console view sessions for two guest vms
> 5. Set consoleproxy.session.max=2 and restart MS
> 6.Open console view for another vm
> Result:
> ======
> Immediately continuous CPVMs spin up strated one after the other until the resources
were available even though there were only 3 console view sessions opened.
> mysql> select id,name,instance_name,state from vm_instance where name like "v%VM";
> +----+---------+---------------+---------+
> | id | name    | instance_name | state   |
> +----+---------+---------------+---------+
> |  2 | v-2-VM  | v-2-VM        | Running |
> | 13 | v-13-VM | v-13-VM       | Running |
> | 14 | v-14-VM | v-14-VM       | Running |
> | 15 | v-15-VM | v-15-VM       | Running |
> | 16 | v-16-VM | v-16-VM       | Running |
> +----+---------+---------------+---------+
> 5 rows in set (0.00 sec)
> v-2-VM was the initial vm before restarting MS. Immediately after MS restart all the
remaining cpvms spinned up.
> Observations:
> ===========
> I closed all the console view sessions and destroyed all the cpvms except the v-2-VM.
Again CS started creating CPVMs even though there were no console view sessions opened.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message