You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Josh Thompson (JIRA)" <ji...@apache.org> on 2013/11/27 03:44:35 UTC

[jira] [Assigned] (VCL-445) consider having reload reservations ignore image maxusage limit

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

Josh Thompson reassigned VCL-445:
---------------------------------

    Assignee: Josh Thompson

> consider having reload reservations ignore image maxusage limit
> ---------------------------------------------------------------
>
>                 Key: VCL-445
>                 URL: https://issues.apache.org/jira/browse/VCL-445
>             Project: VCL
>          Issue Type: Improvement
>          Components: web gui (frontend)
>            Reporter: Josh Thompson
>            Assignee: Josh Thompson
>
> It may be best to have reload reservations ignore the maxusage limit for an image.  If there are 2 block allocations that are close, but that do not overlap, the max concurrent usage limit for the image can keep the reload reservations from being created for the 2nd block allocation, thus keeping an adequate number of machines from being allocated for the 2nd block allocation.  We'll have to make sure this cannot lead to too many instances of the image actually being used by users.



--
This message was sent by Atlassian JIRA
(v6.1#6144)