charm-helpers fetch apt_install optimization

Charles Butler charles.butler at
Thu Nov 20 17:33:18 UTC 2014


I think you're touching on some important topics. Tuning and optimizing
charm installation without fetching tons of extra packages around an
install is certainly something I'm very open to experimentation with.

This particular merge makes me suggest we run this through the gauntlet of
testing scenarios - as if we merge this as is it effects the default
expected behavior of the apt_install, with > 200 charms in the store - and
im' going to venture to guess ~ 40% of those are python and charm-helpers
based charms. This means a very expensive test would follow to ensure we
don't break whats in the wild. If you were to refactor this to make that a
parameter on apt_install, and leave the default behavior as is - I would be
more confident in making the merge happen.

All the best,


On Wed, Nov 19, 2014 at 6:27 PM, Jay Wren <jay.wren at> wrote:

> Greetings,
> I wanted to bring attention to a pending MR
> which I feel can help charm-helpers.
> By not installing recommended packages, charms will install packages
> faster, with less unneeded packages.
> This leads to faster deploys and faster experience for new users and an
> overall better feeling about juju.
> On a similar subject, I am asking for feedback from charm-helpers users
> regarding apt related activity. I feel it might make sense use apt_pkg for
> as many operations as possible. Would a merge request of this nature be
> considered or is fork and exec to the more familiar system commands
> preferred?
> Thanks,
> --
> Jay
> --
> Juju mailing list
> Juju at
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Juju mailing list