I think it might be a good idea to read through what is available at https://github.com/herlo/paas-sig-ci right now. I've got a PR which Ari is reviewing atm, please add your feedback here also if you like. https://github.com/CentOS-PaaS-SIG/paas-sig-ci/pull/1 Essentially, the work I've done is to get us a nice jenkins job (yes, I did use JJB) that will use a matrix style job to build up any number of instances from duffy, using our linch-pin project ( https://github.com/CentOS-PaaS-SIG/linch-pin). The slick thing is that given an inventory layout, you can generate a powerful static inventory (for now) and use it with further jobs. This current job will be expanded with standard use cases I want to build up for openshift, atomic, and others. I'm excited about this because this folder structure, ansible playbooks, and jenkins job layouts are simple and easy to follow. I will be documenting the process of how to add your own in the next day or two, before I move onto the next cluster to build here. I expect to use it as a model for my documentation. Personally, I don't want to use a wiki page to store this information, and think it could easily be part of the README, along with a docs directory in the pass-sig-ci repository. We could just generate sphinx docs (if we really need them) to show how to use all the of the tools available. I'm wanting the paas-sig-ci and linch-pin projects to grow and get used elsewhere as an elegant and powerful way of managing cloud infrastructure. To that end, I'm planning on writing some blog posts on how to use linch-pin, with both duffy and other cloud infra, as well as a post about how to use the paas-sig-ci repository to do CI for CentOS, specifically. I do see some real value in the code you've written, Colin. It would be a shame to let it disappear. The cciskel tool is very powerful in its own right, but it does fit very specific need. I found that after writing a bit to generate inventories, the caching bit was not something I'd use much, if ever. However, the concept is killer. :) If linch-pin hadn't already been conceived and in play, I'd still be using it today, just without the caching stuff. I'd love to see about moving much of the code (all of the atomic bits for sure) over into the paas-sig-ci repository. What thoughts do you have on this? Cheers, herlo PS - Extra thanks to Colin, Ari, and Samvaran for all of the hard work on this, and helping shape the direction taken with the paas-sig-ci repository. On Tue, Aug 30, 2016 at 1:54 PM, Ari LiVigni <ari at redhat.com> wrote: > +1 > > Clint (Herlo) was going to write up a document for Centos PaaS of the work > that has been done. > > https://github.com/arilivigni/paas-sig-ci > > We are using JJB and Matrix to create and manage jobs. > Blog post - https://metalgeekblog.wordpress.com/2016/08/17/ > jenkins-creating-multijob-matrix-jobs-in-for-simplifying-committed-and-pr- > jobs/ > > We also are using linch-pin as a universal deployer of resources. > > https://github.com/CentOS-PaaS-SIG/linch-pin > > This is work that Clint and SK have done that allows us to get bare metal > and VM resources in many infrastructures to use for CI and testing in > general. > > On Tue, Aug 30, 2016 at 3:42 PM, Colin Walters <walters at verbum.org> wrote: > >> Hey, to recap there are two things I really like about CentOS CI: >> >> 1) The idea that we can more easily share code/ideas/maintenance with >> other users in the ecosystem, from RDO to libguestfs, etc. >> 2) The bare metal provisioning >> >> Relating to #1 though, what I miss right now is a process/model for >> actually sharing more with other users. For example, I find myself >> wanting better code to manipulate artifacts beyond base rsync, >> and I'm curious what others are doing. But how to find their code? >> (Reading through the jenkins job UI configuration is too awful to >> consider, >> I'd hope people are using JJB) >> >> So, how about we start a wiki page with links/descriptions to projects >> which are using CentOS CI? Can someone with the perms start that? >> >> My entry is: >> >> https://github.com/CentOS/sig-atomic-buildscripts/tree/master/centos-ci >> _______________________________________________ >> Ci-users mailing list >> Ci-users at centos.org >> https://lists.centos.org/mailman/listinfo/ci-users >> > > > > -- > -== @ri ==- > > _______________________________________________ > Ci-users mailing list > Ci-users at centos.org > https://lists.centos.org/mailman/listinfo/ci-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/ci-users/attachments/20160830/4954d423/attachment-0002.html>