Now that remctl 2.13 has been backported to Hardy, we can use Russ's python-remctl package to implement this.
We should probably shoot to re-establish the remctl connection at the start of every request to make sure that changes caused by RemConfFS are respected.
I think I'd do this by teaching invirt.remctl to always use and hold onto persistent connections, and have a method in that module to clear the cache of connections.
Now that remctl 2.13 has been backported to Hardy, we can use Russ's python-remctl package to implement this.
We should probably shoot to re-establish the remctl connection at the start of every request to make sure that changes caused by RemConfFS are respected.
I think I'd do this by teaching invirt.remctl to always use and hold onto persistent connections, and have a method in that module to clear the cache of connections.