I *believe* a database dump of the reviewboard site was kept but the site
was taken down as it wasn't being used.
Juju QA folks may be able to shed more light.
On 25 May 2017 at 01:44, roger peppe wrote:
> Despite my plea (quoted below) it seems that our reviewboard
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
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
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
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