John Trowbridge <trown(a)redhat.com&gt; wrote: Sorry for dumb question, but what’s the link to promoted/validated yum repo? Ihar

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(a)redhat.com&gt; wrote:

On 12/16/2015 11:22 AM, Ihar Hrachyshka wrote: +1 from me... delorean repos have much more CI running against them right now, so ironically I think they are more stable than the production repos. In terms of updates, they are certainly closer to stable/liberty branch upstream.

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. 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(a)gmail.com&gt; wrote:

2015-12-16 18:10 GMT+01:00 Pedro Sousa <pgsousa(a)gmail.com&gt;: Builds from Delorean are not reproducible, so I recommend not using them for production needs. Nonetheless, you may use Delorean packages for development purpose and for hotfixes. As for that particular issue, as soon as the fix will be merged, it will be rebuilt as a package in Delorean (as upstream gerrit is down, I can't check it) Note that this ticket is filed against RHEL-OSP and not RDO, so without a ticket, it'd have to wait next point-release rebase. Plans are that we automate packages builds from Delorean spec files and have both reproducible builds and more frequent updates. Regards, H.

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(a)redhat.com&gt; 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. >> > > >> 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(a)gmail.com&gt; 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(a)redhat.com&gt; wrote: >>>> >>>> >>>> >>>> On 12/16/2015 09:09 AM, Ihar Hrachyshka wrote: >>>>> John Trowbridge <trown(a)redhat.com&gt; 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(a)redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>>> >>>>>> To unsubscribe: rdo-list-unsubscribe(a)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(a)redhat.com >>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>> >>>> To unsubscribe: rdo-list-unsubscribe(a)redhat.com >>> >>> >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list(a)redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> To unsubscribe: rdo-list-unsubscribe(a)redhat.com