Images changes ahead

Oliver Grawert ogra at
Tue Jan 12 10:33:34 UTC 2016

Am Dienstag, den 12.01.2016, 09:48 +0100 schrieb Michael Vogt:
> On Mon, Jan 11, 2016 at 11:41:06AM -0600, Jamie Strandboge wrote:
> > On 01/11/2016 02:45 AM, Michael Vogt wrote:
> > > The next steps are:
> > > - We stop image imports for 16.04 in the system-image server.
> > >   So no more updates and no new snappy that contains changes
> > >   that would break those systems.
> > 
> > A nice property of the current system is that it automatically pulls in changes
> > to packages from the archive that comprise the image in daily builds, etc. In
> > the new world, will there be a process in place for os snap daily autouploads to
> > the store? Eg, snappy or glibc or systemd in the archive changes-- will that
> > trigger os snap generation and upload to an appropriate channel or will someone
> > have to manually regenerate the os snap for these things?
> For now we get the os and kernel build via cdimage. The import and
> upload to the kernel is manual though.

i think at least the tarball/squashfs import and snap creation should
not be to hard to add directly to the cdimage build process (i'm fine to
implement this, if desired) ... 

perhaps the store could automatically pull from a known good (perhaps
even completely internal (if there are security concerns)) location so
we do not need to manually upload ? 

that way we could have the whole image build process automated again ...


More information about the snappy-devel mailing list