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/10/28 16:15: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=15615831#comment-15615831 ] 

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

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

VCL-843 - Remove "VM limit"

conf-default.php: removed MAXVMLIMIT

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