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 2012/05/09 18:21:51 UTC

[jira] [Updated] (VCL-568) refresh current reservations page 15 minutes after a reservation becomes available

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

Aaron Peeler updated VCL-568:
-----------------------------

    Fix Version/s:     (was: 2.3)
                   2.4
    
> refresh current reservations page 15 minutes after a reservation becomes available
> ----------------------------------------------------------------------------------
>
>                 Key: VCL-568
>                 URL: https://issues.apache.org/jira/browse/VCL-568
>             Project: VCL
>          Issue Type: Improvement
>          Components: vcld (backend), web gui (frontend)
>            Reporter: Josh Thompson
>            Assignee: Josh Thompson
>             Fix For: 2.4
>
>
> It would be useful to refresh the current reservations page shortly after a timeout could have occurred so that users will see if the reservation timed out.
> We'll key off events in computerloadlog. 
> Two entries will be created in the variable table - acknowledgetimeout and connecttimeout that will have values that are the timeout period in seconds.  One entry will be added to computerloadstate - connecttimeout.
> When vcld inserts the 'reserved' computerloadstate into computerloadlog, both vcld and the frontend will key off of that timestamp and variable.acknowledgetimeout to know when the reservation will timeout if the user does not click the Connect button.  
> When the user clicks the Connect button, the frontend will insert an entry into computerloadlog for connecttimeout.  Both vcld and the frontend will key off of that timestamp and variable.connecttimeout to know when the reservation will timeout if the user never connects.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira