On Sun, Aug 21, 2016 at 4:14 PM, Dennis Gilmore <dennis(a)ausil.us> wrote:
On Friday, August 19, 2016 3:31:31 PM CDT Adam Miller wrote:
> On Fri, Aug 19, 2016 at 9:54 AM, Dennis Gilmore <dennis(a)ausil.us> wrote:
> > On Thursday, August 18, 2016 11:35:17 AM CDT Adam Miller wrote:
> >> Hello all,
> >>
> >> This is a proposal for implementing a solution for releng ticket
> >>
> >> #6313[0]
> >>
> >> Currently the compose (pungi) produces an Atomic ostree, installable ISO,
> >> and various cloud images nightly. Those artifacts are then tested via
> >> AutoCloud. I'm proposing that we add a second "new" repo,
every two weeks
> >> we will sync the latest commit from the current repo/ref that has passed
> >> testing in AutoCloud then using the corresponding compose, reproduce the
> >> ISO and various cloud images using the exact same content but pointing to
> >> the new remote ref (which we will call
> >> fedora-atomic/24/x86_64/stable/docker-host) that is only updated every
> >> two-weeks. This would be added to the current two-week atomic release
> >> script instead of impacting pungi or other current processes.
> >
> > The compose currently does not produce a ostree repo so it owuld have to.
> > we could achive what you propose today though by tagging the commit used
> > in the repo with that tag.
>
> Ah ok, I didn't realize the compose wasn't producing an ostree. Is the
> ostree that's used in the Atomic ISO and cloud/VM images produced
> during the compose not from the compose content?
The ostree used is produced by bodhi as part of the updates push cycle. We
just grab and put in whatever is there.
Doesn't that defeat part of the point of the compose? I was under the
impression that the compose was supposed to be able to reproduce all
it's artifacts from the content within the compose itself, is that
incorrect?
-AdamM
>
> Dennis
>> -AdamM
>>
>> > Dennis
>> >
>> >> We then will add documentation for users who want to switch between
>> >> release
>> >> streams via different repos/refs, either nightly updates.
>> >>
>> >> The main concerns are:
>> >> - We would need to manage the versioning of the ref that gets synced
over
>> >>
>> >> ourselves but I think we can just version it as the compose id for
>> >> consistency.
>> >>
>> >> - Need to figure out how to extract the ostree repo/ref commit from
>> >> AutoCloud to ensure we're getting the right thing. This should be
>> >> predictable though since the artifacts are built from an ostree created
>> >> in
>> >> the compose.
>> >>
>> >> [0] -
https://fedorahosted.org/rel-eng/ticket/6313
>> >> _______________________________________________
>> >> rel-eng mailing list
>> >> rel-eng(a)lists.fedoraproject.org
>> >>
https://lists.fedoraproject.org/admin/lists/rel-eng@lists.fedoraproject.o
>> >> rg
>> >
>> > _______________________________________________
>> > rel-eng mailing list
>> > rel-eng(a)lists.fedoraproject.org
>> >
https://lists.fedoraproject.org/admin/lists/rel-eng@lists.fedoraproject.or
>> > g
>>
>> _______________________________________________
>> rel-eng mailing list
>> rel-eng(a)lists.fedoraproject.org
>>
https://lists.fedoraproject.org/admin/lists/rel-eng@lists.fedoraproject.org
>
>
> _______________________________________________
> rel-eng mailing list
> rel-eng(a)lists.fedoraproject.org
>
https://lists.fedoraproject.org/admin/lists/rel-eng@lists.fedoraproject.org
>