Juju 1.23 has some known issues with Lease operations. All of those have
been fixed in the 1.24.4 (5?) release. It is good practice to take a backup
before upgrading, and if you want we can try to help sort out the specific
growth to make sure it gets cleaned out after the upgrade. (Even just
+1.
We should definitely have package docs for every package,
explaining what it's for, how it is intended to be used and explaining
any overarching concepts.
There's no particular need for it to be in a separate doc.go file
though.
On 26 August 2015 at 14:11, Frank Mueller
[ ... lots of notification logging of notification timeouts,
Juju state DB growing large ... ]
Juju 1.23 has some known issues with Lease operations. All of
those have been fixed in the 1.24.4 (5?) release. It is good
practice to take a backup before upgrading,
Ahh interesting thanks. I was
Hi,
I would like to share an idea with you.
As our codebase gets larger and larger the chance of touching areas you've
never worked before gets larger too. So you often need some time to get
behind the concepts here. So for example many testing packages we have
follow different ideas. Some only
Looking at a MAAS+Juju collection of 12 hosts, with 3 Juju
state nodes. The collection runs OpenStack and Ceph,
apparently still working. It was mostly installed in May, 3
months ago, on ULTS 14 with package versions:
ii juju-core 1.23.2-0ubuntu amd64 Juju is devops distilled -
On 27 August 2015 at 03:55, John Meinel j...@arbash-meinel.com wrote:
Juju 1.23 has some known issues with Lease operations. All of those have
been fixed in the 1.24.4 (5?) release. It is good practice to take a backup
before upgrading, and if you want we can try to help sort out the specific
Hi All, when using 'juju bootstrap --constraints' the constraint is used
for bootstrap, but the constraint is also set on the environment for future
machines.
Is it helpful to set the additional environment constraint?
So far I've frequently seen the bootstrap constraint used to choose which
