DevHeads.net

Postings by Ken Dreyer

where should we build nsible-2.4.1 in CBS?

Hi folks,

The latest ceph-ansible version requires ansible-2.4.1.0 now, due to
some regressions in ansible-2.4.0.0.

It looks like the "ansible" package in CBS has been built in several
different build targets recently.

Is there a standard place where we can build the "ansible" package
going forward, and then cross-tag that build into all the places that
need it?

- Ken

automating paas auth to CBS

Hi Clint,

Recently I was looking into automatically building some ceph packages in
CBS, and I was curious how you're doing automatic CBS builds with the paas user.

I'm guessing you've generated the paas CentOS FAS x509 cert with
centos-cert, and then you upload that .centos.cert file into some
Jenkins instance? Is that ci.centos.org or something else?

I see mention of the account creation @
<a href="https://bugs.centos.org/view.php?id=11465" title="https://bugs.centos.org/view.php?id=11465">https://bugs.centos.org/view.php?id=11465</a>, but there's no mention of
how long-lived this FAS x509 cert is.

where is the centos-packager source?

Is there a Git repository with the source code for the centos-packager package?

I'm interested in adding a feature to centos-cert to allow downloading
the CAs without re-generating a user cert (basically splitting up
download_cert() in /usr/bin/centos-cert.)

This would make it easier to run cbs in Jenkins with ephemeral cloud
slaves, without having to hardcode the
<a href="https://accounts.centos.org/ca/ca-cert.pem" title="https://accounts.centos.org/ca/ca-cert.pem">https://accounts.centos.org/ca/ca-cert.pem</a> URL in the job's code.

It also looks like the centos-packager.spec's License field says
"GPLv2+", whereas the COPYING file is the GPLv3, so it would be good
to make these align.

- Ken

Building Debian packages on ci.centos.org?

Hi folks,

I'm thinking about how we can migrate some of the jobs on
jenkins.ceph.com to ci.centos.org.

One of the barriers to entry for Ceph is that our jenkins.ceph.com
jobs output both RPMs and DEBs for every branch, and keeping parity
between the two formats is important.

If we "brought our own" Jenkins slaves for building .deb packages,
could we use the ci.centos.org infrastructure?

- Ken

Storage SIG introduction: Ken Dreyer

Hi folks,

My name is Ken Dreyer, and I work on the Ceph Engineering team @ RH.
We're working on a new GUI for Ceph and Gluster management,
<a href="https://github.com/Tendrl" title="https://github.com/Tendrl">https://github.com/Tendrl</a>

There are a couple of groups across the Ceph and Gluster communities
that are working on Tendrl and its dependencies, so the CentOS Storage
SIG community would be an ideal place to make all the pieces fit
together.

I'd like to help with packaging the Ceph-related dependencies in the
CentOS Storage SIG, and getting them built in CBS, etc.

I've set up my account at
<a href="https://accounts.centos.org/user/view/ktdreyer" title="https://accounts.centos.org/user/view/ktdreyer">https://accounts.centos.org/user/view/ktdreyer</a> and requested the