Re: [Libguestfs] Splitting up virt-v2v

On Wed, Nov 25, 2020 at 12:31 PM Richard W.M. Jones <rjones(a)redhat.com&gt; wrote> > Aim (e): > > Better progress bars: nbdcopy should have support for > machine-readable progress bars, once I push the changes. It will > mean no more need to parse debug logs. I don't think this is only about the progress bar, but the entire process. The tool should have an option to generate output for machines, for example GUI showing what the tool is doing. Typically such application needs to get events when changing the state or when progress changes. It can be simple stream of lines: event: Setting up ... event: Converting disk ... event: Copying disk ... progress: 0 progress: 1 ... progress: 100 event: Creating vm ... The program consuming this can change the text on each "event:" line and update the progress bar on each "progress:" line.

This can be enhanced by providing additional info about the process. For example in RHV it will be helpful if we have the transfer id, disk id, and vm id when try to debug failures. Currently we have to use keep debug logs and grep the log to get the values, but it would be more useful if the details were reported by the tool: info: disk_id=xxxyyy transfer_id=yyyzzz If the process failed the tool can report: error: Why it failed... This is something that every tool doing complex/slow stuff needs to implement, like qemu-img convert or dd. Like https://testanything.org/ for watching processes - watch anything protocol?

> Aim (f): > > Better logging: I hope we can log each step separately. > > A custom supervisor program would also be able to tell which > particular step failed (eg. did it fail in conversion? did it fail > copying a disk and which one?) For logging it would be useful to support logging to file, so tools do not have to read the logs and write them to file. This is true for all virt-* tools.