[CentOS-devel] Official docker images and updates

On Tue, Apr 8, 2014 at 3:40 PM, Jim Perrin <jperrin at centos.org> wrote:

>
>
> On 04/08/2014 02:41 PM, Matthew Miller wrote:
> > On Tue, Apr 08, 2014 at 12:59:18PM -0500, Jim Perrin wrote:
> >> Adam/Matt, could you provide some detail as to the benefits of
> >> appliance-tools, and the capabilities?
> >
> > Wellllllll. We are actively migrating away from appliance tools,
> actually.
> > the two benefits were:
> >
> >  - uses a standard input format we are all familiar with (kickstart)
>
> so that's pretty much the same as what we're doing now then.
>
> >  - integrated into koji for builds (so we get the repeatability and
> >    traceability benefits that brings)
>
>
> and we're not using koji for the core builds.
>
>
> > Now with Koji 1.9, we have an anaconda/imagefactory toolchain, which has
> > these advantages:
> >
> >  - also uses kickstart
> >  - appliance-creator in maintenance mode only, anaconda actively
> developed
> >  - even better koji integration (tarball outputs for docker to take in)
> >
> > But, I think even that is intermediary. There is preliminary work on an
> idea
> > which uses rpm in mock as the build format:
> >
>
> Since el6 will still be current/relevant to us for quite some time,
> would this new method be able to create el6 images as well?
>
>
For what it's worth I figured I'd mention the github comment thread that
kind of
kicked off this topic.

https://github.com/CentOS/sig-cloud-instance-build/pull/4

Also, in the event this ends up going anywhere I've moved forward with
getting
appliance-tools into EPEL6

https://admin.fedoraproject.org/updates/appliance-tools-007.7-2.1.el6

-AdamM




> >  - uses a standard input format we are all familiar with (spec files)
> >  - much lighter weight than anaconda
> >  - in active development
> >  - can handle _layered_ images
> >  - will be integrated with koji (i think also through imagefactory)
> >
> > The nice thing here is that the output format (and fedbus messages)
> should
> > be the same if we make this second transition in the future, so the
> > koji -> docker registry bits can be the same.
> >
>
> --
> Jim Perrin
> The CentOS Project | http://www.centos.org
> twitter: @BitIntegrity | GPG Key: FA09AD77
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel at centos.org
> http://lists.centos.org/mailman/listinfo/centos-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140408/cd743c9a/attachment-0001.html>