You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Aaron Peeler (JIRA)" <ji...@apache.org> on 2014/08/28 16:58:08 UTC
[jira] [Updated] (VCL-758) VCL timings - make various timings to be
variables and edited by admin
[ https://issues.apache.org/jira/browse/VCL-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Peeler updated VCL-758:
-----------------------------
Description:
Allow VCL admins edit some of the timing values via the front-end.
Possible variables to allow edits are:
acknowledge timeout = time limit to wait on user to hit connect button
connect timeout = wait for user to connect for normal reservations
ignore_connections_gte = skip checks for durations gte X (24hrs is hardcoded in code)
general_inuse_check = how often to check on normal reservations
server_inuse_check = how often to check on server reservations
cluster_inuse_check = how often to check on cluster reservations
Some of these can easily be setup based on an affiliation, but others we may want to limit as a global setting such as general_inuse_check.
Need a page on the web portal for admins to set the values.
List of times for variable table and their default times being set in backend:
acknowledgetimeout => '900',
connecttimeout => '900',
wait_for_reconnect => '900',
general_inuse_check => '300',
server_inuse_check => '900',
cluster_inuse_check => '900',
general_end_notice_first => '600',
general_end_notice_second => '300',
ignore_connections_gte => '1440'
was:
Allow VCL admins edit some of the timing values via the front-end.
Possible variables to allow edits are:
acknowledge timeout = time limit to wait on user to hit connect button
connect timeout = wait for user to connect for normal reservations
ignore connections gte = skip checks for durations gte X (24hrs is hardcoded in code)
general_inuse_check = how often to check on normal reservations
server_inuse_check = how often to check on server reservations
cluster_inuse_check = how often to check on cluster reservations
Some of these can easily be setup based on an affiliation, but others we may want to limit as a global setting such as general_inuse_check.
Need a page on the web portal for admins to set the values.
> VCL timings - make various timings to be variables and edited by admin
> -----------------------------------------------------------------------
>
> Key: VCL-758
> URL: https://issues.apache.org/jira/browse/VCL-758
> Project: VCL
> Issue Type: Improvement
> Components: database, vcld (backend), web gui (frontend)
> Reporter: Aaron Peeler
> Priority: Minor
> Fix For: 2.3.3, 2.4
>
>
> Allow VCL admins edit some of the timing values via the front-end.
> Possible variables to allow edits are:
> acknowledge timeout = time limit to wait on user to hit connect button
> connect timeout = wait for user to connect for normal reservations
> ignore_connections_gte = skip checks for durations gte X (24hrs is hardcoded in code)
> general_inuse_check = how often to check on normal reservations
> server_inuse_check = how often to check on server reservations
> cluster_inuse_check = how often to check on cluster reservations
> Some of these can easily be setup based on an affiliation, but others we may want to limit as a global setting such as general_inuse_check.
> Need a page on the web portal for admins to set the values.
> List of times for variable table and their default times being set in backend:
> acknowledgetimeout => '900',
> connecttimeout => '900',
> wait_for_reconnect => '900',
> general_inuse_check => '300',
> server_inuse_check => '900',
> cluster_inuse_check => '900',
> general_end_notice_first => '600',
> general_end_notice_second => '300',
> ignore_connections_gte => '1440'
--
This message was sent by Atlassian JIRA
(v6.2#6252)