Add support for "Console Output"
|Category:||Drivers - VM|
Some hypervisors (KVM, Xen) support dumping the console output to a file.
The console output includes the boot sequence output.
OpenNebula can easily be extended to make the file available from CLI, Sunstone and Self-service, by using the same functionality that supports the "VM Log" tab.
Changes required would be:
- Add the option for console output to the "new" template form, and translate that into hypervisor specific configuration
- Add a "Console Output" tab to the virtual machine details
- Create a get-console-output CLI action
This will then be used to implement the GetConsoleOutput EC2 action.
#8 Updated by Ricardo Duarte over 7 years ago
Ruben S. Montero wrote:
maybe the console output could be gathered during the monitor phase or boot and attached to the vm template (base64 encoded)
Making it part of the VM template seems like a great idea, as it will simplify getting the console output from all the OpenNebula endpoints/APIs. We just have to keep it truncated to some number of lines, as I assume there is a limitation on how much data you can reasonably put inside the vm template. The raw console.log file can still be kept under the datastore, if the user really needs it.
Gathering it (only) as part of the boot process does not seem to fit tho, because the console output can change during the lifetime of the instance. Doing it during monitoring will also have some problems, because users generally want the data to be available as soon as the instance boots/fails. Can you speed up the first monitoring so that it runs shortly after an instance boots?