[
https://issues.apache.org/jira/browse/VCL-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976982#comment-13976982
]
ASF subversion and git services commented on VCL-758:
-----------------------------------------------------
Commit 1589196 from [~fapeeler] in branch 'vcl/trunk'
[ https://svn.apache.org/r1589196 ]
VCL-758
Improved functionality for timing variables. Begining steps to allow VCL admins
to set different timing values for selected events related to reservations.
- Moved the following from DataStructure to utils to allow for calls from
non-objects
get_variable, set_variable, is_variable_set, yaml_deserialize, yaml_serialize
> 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
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
