[Rdo-list] we have fully automated liberty delorean repo promotion!

[David Moreau Simard]

> This is a great summary. I would like to emphasize the gap here though.
> Delorean is building directly from a more or less random git hash. Where
> as production is built more traditionally using a release tarball with
> some number of cherry-picked patches on top. Thus there is no direct
> relationship between what is in delorean current-passed-ci repo and what
> is the "production" repo. The delta is likely small when the production
> repo gets created at GA, but it is non-zero even then, and just gets
> larger as time goes on.

Right, I forgot about tarballs. How does that work now that there are
no longer dot releases ?

Do each project continuously release tarballs independently of each other ?


David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]


On Wed, Dec 16, 2015 at 2:57 PM, John Trowbridge <trown at redhat.com> wrote:
>
>
> On 12/16/2015 11:50 AM, David Moreau Simard wrote:
>> The stable repositories are stable in the sense that they do not move
>> much and this is typically what you would expect in a production
>> environment.
>> This is the repository we provide through a RPM.
>>
>> As far as stability goes, the flow can be summarized like this:
>> Delorean (current [1]) -> Delorean (current-passed-ci [2]) -> Stable
>> (rpm repository [3])
>> The delorean repositories (both current and current-passed-ci) share
>> the same repository [4] for dependencies.
>>
>> Delorean picks up the source of upstream repositories each time there
>> is a commit and builds a package from it.
>> These packages are untested for the most part other than the very basics.
>>
>> We then periodically pick up the latest delorean repository and make
>> it go through a series of integration tests (CI) where we install and
>> configure OpenStack deployments in a series of ways to try and make
>> sure that all the pieces of the puzzle work fine. If the set of
>> packages passes these tests, they are then promoted to
>> current-passed-ci.
>>
>
> This is a great summary. I would like to emphasize the gap here though.
> Delorean is building directly from a more or less random git hash. Where
> as production is built more traditionally using a release tarball with
> some number of cherry-picked patches on top. Thus there is no direct
> relationship between what is in delorean current-passed-ci repo and what
> is the "production" repo. The delta is likely small when the production
> repo gets created at GA, but it is non-zero even then, and just gets
> larger as time goes on.
>
>> As deemed necessary (important bugs or security patches) or when there
>> is a dot release upstream, we will update the stable repositories -
>> the set of packages that will make it there will be picked up from a
>> hand-picked repository that has gone through CI to be promoted to
>> current-passed-ci.
>>
>> [1]: http://trunk.rdoproject.org/centos7/current/
>> [2]: http://trunk.rdoproject.org/centos7/current-passed-ci/
>> [3]: https://www.rdoproject.org/repos/rdo-release.rpm
>> [4]: http://trunk.rdoproject.org/centos7/delorean-deps.repo
>>
>> David Moreau Simard
>> Senior Software Engineer | Openstack RDO
>>
>> dmsimard = [irc, github, twitter]
>>
>>
>> On Wed, Dec 16, 2015 at 10:18 AM, Pedro Sousa <pgsousa at gmail.com> wrote:
>>> Another dumb question :)
>>>
>>> What's difference between using delorean versus rpm liberty repos in terms
>>> of stability and updates?
>>>
>>> Which one should we use for production?
>>>
>>> Thanks
>>>
>>> On Wed, Dec 16, 2015 at 2:24 PM, John Trowbridge <trown at redhat.com> wrote:
>>>>
>>>>
>>>>
>>>> On 12/16/2015 09:09 AM, Ihar Hrachyshka wrote:
>>>>> John Trowbridge <trown at redhat.com> wrote:
>>>>>
>>>>>> Howdy all,
>>>>>>
>>>>>> Just wanted to make a quick announcement that we now have fully
>>>>>> automated liberty delorean repo promotion including image building and
>>>>>> publishing.
>>>>>>
>>>>>> The multijob can be found here:
>>>>>> https://ci.centos.org/view/rdo/job/rdo-delorean-promote-liberty/
>>>>>>
>>>>>> I would like to add a job for RDO-Manager with network isolation as
>>>>>> well
>>>>>> as one for compute scaling to the import images phase, but overall this
>>>>>> is pretty good coverage.
>>>>>>
>>>>>> Much thanks to weshay for all the jjb help.
>>>>>>
>>>>>> - trown
>>>>>>
>>>>>> _______________________________________________
>>>>>> Rdo-list mailing list
>>>>>> Rdo-list at redhat.com
>>>>>> https://www.redhat.com/mailman/listinfo/rdo-list
>>>>>>
>>>>>> To unsubscribe: rdo-list-unsubscribe at redhat.com
>>>>>
>>>>> Sorry for dumb question, but what’s the link to promoted/validated yum
>>>>> repo?
>>>>>
>>>>
>>>> For liberty the promoted repo is available via:
>>>> http://trunk.rdoproject.org/centos7-liberty/current-passed-ci/
>>>>
>>>>> Ihar
>>>>
>>>> _______________________________________________
>>>> Rdo-list mailing list
>>>> Rdo-list at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/rdo-list
>>>>
>>>> To unsubscribe: rdo-list-unsubscribe at redhat.com
>>>
>>>
>>>
>>> _______________________________________________
>>> Rdo-list mailing list
>>> Rdo-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/rdo-list
>>>
>>> To unsubscribe: rdo-list-unsubscribe at redhat.com