You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/06/02 21:14:59 UTC

[jira] [Commented] (VCL-843) Remove "VM limit"

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

ASF subversion and git services commented on VCL-843:
-----------------------------------------------------

Commit 1746635 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1746635 ]

VCL-843 - Remove "VM limit"

vm.php:
-modified editVMInfo: removed row related to VM limit; added a line below the list of assigned VMs that shows how many VMs are currently assigned
-modified vmhostdata: removed vmlimit from returned data
-modified getVMHostData: removed vmlimit from returned data
-removed updateVMlimit
-modified AJvmToHost: removed section that checks if the host has too many assigned VMs

vm.js:
-modified VMHostDataCB: removed line that set vmlimit; added line that sets assignedcnt to the number of currently assigned VMs
-removed updateVMlimit
-removed updateVMlimitCB
-modified vmToHost: removed section that checks for exceeding vmlimit
-modified vmToHostCB: removed section that checks for error code of vmlimit; added line that sets assignedcnt to the number of currently assigned VMs
-modified vmFromHostCB: added line that sets assignedcnt to the number of currently assigned VMs

> Remove "VM limit"
> -----------------
>
>                 Key: VCL-843
>                 URL: https://issues.apache.org/jira/browse/VCL-843
>             Project: VCL
>          Issue Type: Improvement
>          Components: database, web gui (frontend)
>            Reporter: Andy Kurth
>            Priority: Minor
>             Fix For: 2.5
>
>
> In addition to not being very useful, the _*Virtual Hosts* > *VM limit*_ setting can cause problems if vCenter or high capacity VM hosts are used.  The column is defined as an unsigned tinyint so the maximum value is 255.  The web code won't let you enter anything above 100 by default, configurable in _conf.php_.  Situations where you'd want more than 100 or possibly 255 VMs assigned to a host are becoming more and more common.
> Rather than reworking things by altering the column definition, I propose removing it altogether.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)