Questions about OSBS

[Tomas Tomecek]

Quoting Adam Miller (2015-07-06 18:27:31)
> On Mon, Jul 6, 2015 at 9:18 AM, Adam Miller
> <maxamillion at fedoraproject.org> wrote:
> > On Fri, Jul 3, 2015 at 2:39 AM, Tomas Tomecek <ttomecek at redhat.com> wrote:
> >> Quoting Adam Miller (2015-07-02 16:46:37)
> >>>   - Main motivation/curiosity is that for the build system we don't
> >>> really need a giant portion of what OpenShift offers and the
> >>> maintenance, administrative overhead and security aspects are of
> >>> concern. (This is mostly an idle curiosity, I'm not advocating for one
> >>> over the other but I wanted to bring it up).
> >>
> >> Chain rebuilds will be nice feature to get from OpenShift. Also, OpenShift has
> >> very sweet web interface [9].
> >>
> >> On the other hand, I totally understand your concerns. Maybe having some
> >> automation on top of atomic-reactor could be more suitable.
> >
> > That's partially what I'm trying to sort out is if automation wrapping
> > atomic-reactor would suffice or if running full fledged OpenShift
> > simply to use it as a build system is really what we want to do. From
> > a systems administration standpoint, OpenShift adds a lot of
> > complexity and is something that a number of members in the Fedora
> > Infrastructure team have never used so there would be a learning curve
> > and I just want to make sure we do our due diligence before requesting
> > the team to take on something this big.
> 
> Sorry to double post but I've been thinking more about this and was
> curious what this might look like if we were to just use some sort of
> automation around atomic-reactor? Would this need to be a whole new
> project or just something that could be held under the atomic-reactor
> umbrella such that it would offer a "stand alone" as well as a "with
> OpenShift" type of functionality? I'm very interested in exploring
> this as an option because the more I think about it, standing up an
> entire PaaS simply for the build tooling seems heavy handed.
> 
> Thank you,
> -AdamM

I guess it could work. But you need some sort of scheduler then. And ideally an
API entry point.

~~
Tomáš Tomeček
Software Engineer
Developer Experience
UTC+2 (CEST)