millions of warnings per day, state DB grows by 4GB/day

Peter Grandi pg at juju.list.sabi.co.UK
Thu Aug 27 11:24:48 UTC 2015


>> That PPA gets mentioned on the mailing list and IRC channel
>> occasionally, plus some "unofficial" pages mention it too,
>> but I'll ask around.

So I asked around and the PPA was looked up because of a bug
with the ULTS version with the syslog configuration going
missing and 1.23 fixed that. We should have followed then update
announcements a bit more...

But I now notice that here (and this page is linked to by the
'juju-core' Lunchpad page):

  https://jujucharms.com/docs/stable/reference-release-notes

the 1.23.x releases are included.

> AIUI our current plan is to use backports to ensure that we
> have a consistent public stable version of Juju across all
> supported releases of Ubuntu, especially 14.04 LTS and the
> upcoming 16.04 LTS.

That's excellent. We occasionally do some local backports for
some packages, and it is good that bits of infrastructure that
are under active development get "official" backports.

> Also, we'll use stronger "beta" signalling for milestones that
> are worth testing for the adventurous, but won't get point
> releases.

What I have found very useful is to keep lists of "major known
issues" (which is a call of judgement) by release, in a compact
form. I keep some of them myself, for example here for various
storage and authentication systems:

  http://www.sabi.co.uk/Notes/linuxFS.html#fsHintsXFS
  http://www.sabi.co.uk/Notes/linuxAuth.html#authHintsKrbMIT

The release notes (including those for Juju in the page
mentioned above) usually are hard to parse and often don't
highlight the big common issues...



More information about the Juju mailing list