LXC OS Updates

[Matt Bruzek]

On Mon, Aug 4, 2014 at 4:26 AM, John Meinel <john at arbash-meinel.com> 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.


> On Thu, Jul 31, 2014 at 6:34 PM, Katherine Cox-Buday <
> katherine.cox-buday at canonical.com> wrote:
>
>>
>> We'd like to remove the assumption embedded in the code that if we're
>> cloning an LXC container, then we never want to perform OS upgrades.
>> Instead, the logic based on the config variable will take over, and the
>> user can have whatever behavior they desire. Local installations will be
>> snappy, and production installations will be up to date.
>>
>> We feel this empowers both developers and end-users, but wanted to raise
>> this for discussion. Feedback welcome!
>>
>
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?

Thanks,

  - Matt Bruzek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140804/fc4c86d1/attachment.html>