On Tue, Jul 1, 2014 at 9:19 PM, Andrew Wilkins <[email protected]> wrote: > On Wed, Jul 2, 2014 at 3:38 AM, Antonio Rosales > <[email protected]> wrote: >> >> Suggest we make an environments.yaml key value of say "apt-get-update" >> set to a boolean with the default being "true". Existing charms are >> timing out[0] when apt-get update is turned off due to stale apt-get >> metadata. Users then can them make the choice, and we can make >> suggestions in the docs as to what this key value means and how it can >> improve performance especially in the developer scenario when the care >> more about fast iterative deploys. >> >> Thoughts? > > > I'm not suggesting we turn off update, just upgrade. We add repos > (cloud-tools, ppa), so we need to update for juju's dependencies anyway. I > don't think my proposal will affect charms. > >> >> [0] https://bugs.launchpad.net/juju-core/+bug/1336353 \ ^ ^ this bug implies juju is not running update or not running it at the correct time time. This might be because provisioning for a charm is different than provisioning a state-server?
-- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
