Support virsh console through PVC command #149

New Issue

joshuaboniface · 2021-11-15T11:10:05-05:00

joshuaboniface commented

2021-11-15 11:10:05 -05:00

This was looked at briefly in the past, but I'd like to revisit it again as a QOL feature.

Currently, console logs can be viewed via the PVC API/CLI, but no interaction is possible.

It would be nice if we could interact with the console as well, a la virsh console.

Main difficulties are going to be (a) figuring out how to pass this data via the API, and (b) how to direct it at the right node.

This was looked at briefly in the past, but I'd like to revisit it again as a QOL feature. Currently, console logs can be viewed via the PVC API/CLI, but no interaction is possible. It would be nice if we could interact with the console as well, *a la* `virsh console`. Main difficulties are going to be (a) figuring out how to pass this data via the API, and (b) how to direct it at the right node.

joshuaboniface added the

CLI

API

feature

labels 2021-11-15 11:10:05 -05:00

joshuaboniface self-assigned this 2021-11-15 11:10:05 -05:00

joshuaboniface commented

2022-10-08 00:00:54 -04:00

It looks like there is a python-native implementation of virsh console here:

https://github.com/libvirt/libvirt-python/blob/master/examples/consolecallback.py

And because of how we configure libvirt for live migration, it's possible to connect from the API node to the active node, e.g. hv1$ sudo virsh -c qemu+tcp://10.98.0.2:16509/system console ldap2

The big question would be how to leverage the API for bidirectional support between the CLI and the remote site in a sensible way.

It looks like there is a python-native implementation of virsh console here: https://github.com/libvirt/libvirt-python/blob/master/examples/consolecallback.py And because of how we configure libvirt for live migration, it's possible to connect from the API node to the active node, e.g. `hv1$ sudo virsh -c qemu+tcp://10.98.0.2:16509/system console ldap2` The big question would be how to leverage the API for bidirectional support between the CLI and the remote site in a sensible way.

joshuaboniface commented

2022-10-08 00:13:20 -04:00

From some quick testing, the consolecallback script does not work properly - it prints no output and immediately exits on any input. This is also the only example I can find so far which does not bode well. Will continue to search and experiment.

joshuaboniface commented

2022-11-23 02:12:55 -05:00

Never did find any better solution here. Leaving as a future to-do to dig further into the callback.

joshuaboniface referenced this issue

2023-02-23 22:46:38 -05:00

Revamp/rewrite CLI client and reogranize #162

joshuaboniface added this to the 1.0 milestone 2023-11-17 01:37:16 -05:00

joshuaboniface commented

2023-11-17 01:46:51 -05:00

Investigated several options for this recently, taking inspiration from NoVNC. So far, none have proven particularly impressive but investigation can continue. This is a desired 1.0 feature.