Junaid, You might try writing that data to a filesystem that's outside VCL and just gets mounted by the VCL VMs, along the lines of creating a "thaw space" when using the lab-locking software DeepFreeze:
https://tracermedia.atlassian.net/browse/MCHLEM-307 If your VCL VMs are on your LAN in such a way that they can get to a fileserver where LabStats knows to write its data, it could be a workaround for the more complicated task of changing VCL's reclaim behavior. Regards, Mike On Thu, Apr 24, 2014 at 5:49 PM, Junaid Ali <[email protected]> wrote: > Hello, > > When a user’s reservation ends, the VM’s are reloaded immediately with the > next image. This includes hard powering off of the VM and any running user > session is lost. We use Labstats to track application usage and user login > times, that depends on a graceful logoff and shutdown of applications to > record usage data. This hard powering off of the VM causes much of the > LabStats data to be lost. Is there a way to hookup processes (e.g. > unreserve) that run at the end of the reservation, maybe like an opposite > of reserve() routine. Would there be enough interest in having this > functionality in the core software, so we don’t diverge from the community? > > FYI, we are using VCL 2.2 and plan on an upgrade to 2.3.2 this summer. > > Any thoughts? > > > > Junaid Ali > > >
