Michał Sawicz

@townsend2010 this would work for our custom remote, but for streams-sourced images, every update is a new URL, so that can't be a universal treatment.

@townsend2010 I think we just need to take a step back and identify the valid cache keys for each of the use cases. When we introduce configurable user images, we...

Just to record what we discussed: - every image host (streams or otherwise) needs to be able to declare two refresh cycles: 1) query resolution (e.g. "bionic", "16.04", "http://..." to...

@mlb5000 that's this bit: > You will then need to configure the interface inside the instance, see https://netplan.io/examples/#connecting-multiple-interfaces-with-dhcp for some help.

I would like to see how well we can integrate with `journald` here, ideally giving log lines a category (including the name of the instance), this way we could just...

I wonder if we could also allow another key to increase verbosity, in which case we'd forward `cloud-init.log`'s output to the user.

One thing came to mind: when we introduce such a behaviour, we'll need to also introduce a way for the user to introspect and interrupt the background operations, as a...

Hi @missmah, we have it on our immediate roadmap, milestoned ~end of April.

@imakan you should be able to `multipass shell` inside the instance to see in `/var/log/cloud*` for what's going on. If it just took too long, that's exactly what this issue...

@dmuth when an instance is "Waiting for initialization...", you can already access it via `multipass shell ...` and debug there. Look into `/var/log/cloud-init*log` for problems.