Re: Is it possible to return management to Juju after manual provision of a machine?

Hi NAZ, Like Andrew already pointed out, you can issue `juju deploy your-char --to 9` to run your charms. Then on the juju CLI side, use `juju debug-log` to get a running debug log. Whatever the charm error is, you should see it flashing across the screen. Also, hooks and states will be run

Re: Is it possible to return management to Juju after manual provision of a machine?

Hi NAZ, Like Andrew already pointed out, you can issue `juju deploy your-charm --to 9` to run your charms. Then on the juju CLI side, use `juju debug-log` to get a running debug log. Whatever the charm error is, you should see it flashing across the screen. Also, hooks and states will be run

Using Deb Proxy to cache Debs to minimize time starting-up machines and its installation scripts

Hi, I am running juju latest version on local LXD. When deploying services, FOR each new machine, the "cloud init log" of the LXC in question captures some "apt-get install " before starting up the machine and then i see that it's up to the "install" hook to install additional software and con

Re: Using Deb Proxy to cache Debs to minimize time starting-up machines and its installation scripts

Hi Naz, I use squid-deb-proxy to speed up deployments and it works well. If you're using the lxd provider install the proxy on the host machine so that all controllers and models benefit from the packages cached during previous deployments. Ensure that squid-deb-proxy is configured to listen on t