Website should use persistent remctl connections
Bug #307533 reported by
Evan Broder
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Invirt Project |
New
|
Medium
|
Unassigned | ||
Bug Description
Currently each remctl from the website requires a new connection and handshake to the remctl server. These are slow, typically taking on the order of 0.5-1 seconds to do the initial handshake.
We should take advantage of some bindings to the C API to use persistent connections instead of shelling out to the remctl command. Notably, the new 2.13 release of remctl includes Python bindings. We should possibly backport those and use them.
Revision history for this message
| Evan Broder (broder) wrote | #1 |
| Changed in invirt: | |
| importance: | Undecided → Medium |
To post a comment you must log in.
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.