On 05/08/14 01:53, Matt Bruzek wrote: > On Mon, Aug 4, 2014 at 4:26 AM, John Meinel <[email protected]> wrote: > > >> Creating a template that never gets updated just isn't a great experience, >> and we really need a way to refresh that core snapshot. >> >> John >> =:-> >> > I would like to second John's comment here. We do need a good way for the > user to easily get a new local cloud image if the existing one is getting > old. > > As a developer I know we can delete the lxc cache and Juju bootstrap will > download a new cloud-image, but this is not something we would want a users > to do. >
Indeed. This is being looked at already, see bug https://bugs.launchpad.net/juju-core/+bug/1329154 >> > This proposal looks good and seems to address the concerns I have with the > local update & upgrade. How would this be implemented? Would the > variables pass the appropriate values to cloud-init? > cloud init will just not have the apt commands inserted if the environment is configured not to use them. This is how it is done now for disabling apt-get commands when using lc clone. -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
