On 1 September 2015 at 01:20, Aaron Weitekamp <aweit...@redhat.com> wrote: > I have been confused about what OSBS is. As far as I can tell it's client > tooling[1] that uses OpenShift v3. In other words, is OSBS just a way to > *use* OpenShift? If so, how could we have a roadmap for "using" something? > > So this is a way to pile on Adam's request for some clarification on what > OSBS is.
And how it relates to atomic-reactor. As additional context, one of the topics of discussion that came up during the release engineering session at Flock was the sheer number of services that need a "docker image + git repo -> layered docker image" capability, as well as being able to track the layered images and know which ones need to be recreated when a lower level image is updated. There's at least: * OpenShift (Origin/Online/Enterprise) * Foreman (/Red Hat Satellite) * Atomic Developer Bundle (/RHEL Container Development Kit) * Fedora's build infrastructure (koji, maybe DOPR) * CentOS build infrastructure (including the Community Container Pipeline) * Red Hat's build infrastructure, and presumably that of other Fedora/CentOS derived distros The common components needed across all of them are the build engine itself (which atomic-reactor appears to have covered), and the layer dependency tracking when the input images and source repos are updated. Similar to atomic-reactor, it would be very helpful to be able to consume the latter component as a standalone capability independent of a full OpenShift installation. Regards, Nick. P.S. A potential theme appropriate name for the "update needed" tracking service occurred to me: geiger-counter. Then atomic-reactor + geiger-counter ~= OSBS :) -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
