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 2014/03/06 21:08:43 UTC
[jira] [Updated] (VCL-752) block allocated nodes count toward max
concurrent usage of image even for users in that block allocation
[ https://issues.apache.org/jira/browse/VCL-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Thompson updated VCL-752:
------------------------------
Attachment: maxconcurrent_block_allocation-2.3.2.patch
put patch in somewhere such as /root/vcl_patches
go to /var/www/html/vcl/.ht-inc:
cd /var/www/html/vcl/.ht-inc
create a backup copy of utils.php:
cp utils.php /root/vcl_patches/utils.php-pre-maxconcurrent-patch
apply patch:
patch < /root/vcl_patches/maxconcurrent_block_allocation-2.3.2.patch
> block allocated nodes count toward max concurrent usage of image even for users in that block allocation
> --------------------------------------------------------------------------------------------------------
>
> Key: VCL-752
> URL: https://issues.apache.org/jira/browse/VCL-752
> Project: VCL
> Issue Type: Bug
> Components: web gui (frontend)
> Reporter: Josh Thompson
> Fix For: 2.4
>
> Attachments: maxconcurrent_block_allocation-2.3.2.patch
>
>
> When an image has a max concurrent usage set and there is a block allocation for that image, the number of nodes in the block allocation count toward the max concurrent usage even without having a reservation for them. Example - image has concurrent usage of 6; block allocation for for image with 6 as the number of seats; no one, including the members of the block allocation, can make a reservation for the image. The fix is to ignore block allocations that the user is a member of when counting up the block allocated nodes for the image.
--
This message was sent by Atlassian JIRA
(v6.2#6252)