On Tue, Jul 17, 2018 at 11:17 PM, Wesley Hayutin <whayutin@redhat.com> wrote:On Tue, Jul 17, 2018 at 4:57 PM Paul Belanger <pabelanger@redhat.com> wrote:On Tue, Jul 17, 2018 at 06:16:04PM +0200, Alfredo Moralejo Alonso wrote:
> On Tue, Jul 17, 2018 at 5:38 PM, Alan Pevec <apevec@redhat.com> wrote:
>
> > > I think having the two separated images is the only way we can ensure we
> > are not polluting the image in the initial phase with packages newer that
> > in the stabilized repo.
> >
> > This should be a small list, are any of those actually included in the
> > base image?
> >
>
> Yes, the list is small but we can't be sure if it will change at some
> point, and analysing if we are having one of those cases on each change is
> too error prone, IMO.
>
>
> > Alternatively, which jobs use "normal" f28 images, could we switch
> > them to use "stabilized" f28 ?
> >
>
> fedora-stable has the required packages to run and build python3 packages.
> Currently it's missing some requirements for the jobs running on fedora 28
> image although it's something we could work on.
>
>
> >
> > Alan
> >
>
> Maybe I'm underestimating the cost of maintaining two different images for
> fedora, but my understanding is that the resources the extra image uses and
> the effort to maintain is workable. Please, correct me if i'm wrong.
I wouldn't say minimal, but there is a cost. With fedora-29 around the corner,
it does mean we have 2 iamges to update now, over one. How long does this image
need to live for? When can we get to a point of just using the default fedora
image?
- PaulHey guys,Slight tangent, but wondering how far out we are from the CI team having to get involved here? Is there any planning required at this point?AFAIK, before getting CI involved to create a job to build container we need to get patches merged in kolla to build containers for fedora/python3. I'm not sure if there is a ETA for it. Adding Martin to CC, he may have some estimation for it.
--Thanks_______________________________________________
dev mailing list
dev@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsubscribe@lists.rdoproject.org
_______________________________________________
dev mailing list
dev@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsubscribe@lists.rdoproject.org