Comment 1 for bug 1530414

Hi,

Yes, there are a number of operations for which we used to lack progress information entirely which made this impossible.

Recently, I've implemented the events API and updated most download paths within LXD to expose progress information back to the client (by increment of 10% to avoid flooding them with events), our default client however doesn't yet use this information.

Our focus is currently on a few big and complex features that we want to land before feature freeze (remainder of resource limits and native simplestream support) but I'm hopeful we'll get some time to fix some of those rough edges in the command line client in time for 16.04.