Comment 1 for bug 1557918

Revision history for this message
Eric Snow (ericsnowcurrently) wrote :

tl;dr good luck :)

FWIW, we ran into a similar situation with resources, tracking download progress of resources from the controller to the units. We considered using the status machinery as you've described because it would mostly re-use the existing framework. However, we opted to not go that route for exactly the reason you've described. Solving the problem of status-history spam was too heavy a lift for us given our schedule. (Ultimately we moved resource download progress over to "juju list-resources", but that's beside the point.) Instead we are tracking the download progress (of resources) separately, which is manageable since we can keep it all server-side.

All that said, I imagine it's a different story for LXD images (unless we are caching them on the controller like we do for resources).

Also note that if you are doing this client-side (e.g. in the uniter) then you are producing an API call for each of those status messages, right?