DevHeads.net

Postings by Thomas Oulevey

Status of Ansible within CentOS 7 and SIGs

Hello Folks,

Starting with CentOS 7.5, ansible package will no be available in CentOS
-extras anymore as Red Hat decided to ship Ansible on a separate channel.

Looking at ansible package in CBS [1] I see that Troy, Fabian, Sandro
and Alan are rebuilding it.
Can we get better at that task ?

My proposal would to initiate a rebuild of the new Ansible
channel[2](within the Config Management SIG) and follow a better release
cycle.

What do you think ?

debuginfo.centos.org status

Hello folks,

I have few remarks about <a href="http://debuginfo.centos.org" title="http://debuginfo.centos.org">http://debuginfo.centos.org</a> as an user.

Lately our debug tools are depending on few debuginfo packages so we
depend on them in our production environment.

The debuginfo server is structured as following :
.
├── 7
│ ├── i386
│ │ └── repodata
│ └── x86_64
│ └── repodata
└── centos
├── 6
│ └── sclo
└── 7
├── cloud
├── sclo
├── storage
└── virt

1/ It seems that the experimental kernel debuginfo are copied in the
same directory as the os/updates/extras which confuse a bit users
(/7/x86_64

CentOS 7 extras for alternative arches and Koji workflow.

Dear All,

I'd like to retake a pending issue with -extras on c7 and ask for feedback.

I wear two hats :
1/ User, who would like to use altarch-extras packages soon after they
are available in c7-extras.
2/ CBS maintainer, who would like to provide his users consistent
buildroot across all architecture.

Let's start with 1/. The important point here is to be able to rely on
altarch-extras and expect it to be in sync with c7-extras in a
reasonable time.

2017-01-31 cbs.centos.org infrastructure upgrade.

Dear All,

Please note that next Tuesday cbs.centos.org intervention will be
postponed due to some issue with the upgrade process I didn't catch
earlier with alternative arch builders.

We will announce a new time slot as soon as possible.

2017-01-31 cbs.centos.org infrastructure upgrade.

Dear All,

Please note that next week on Tuesday cbs.centos.org will be upgraded to
support newer features and allow us to improve our vagrant images type
coverage.

What does that mean for you ?

Next Tuesday, we'll upgrade koji and imagefactory to latest version.
The change is scheduled to be implemented on Tuesday January 31st, 8:00
am UTC time
You can convert to local time with $(date -d '2017-01-31 8:00 UTC')

What will be the impact ?

Koji build service will be down for an hour.
It will not be possible to build new packages or images.
Please note that temporary repositories served on

cbs.centos.org is building against CR repository

Dear All,

Since this morning, 08:30 UTC, all koji buildroot for CentOS 7 have the
CR repository enabled.

Few notes :

- For multi-arch SIGs, until arch specific CR is populated your
buildroot will be different on a per arch basis but will NOT fail. We
are looking into a better way to handle this.

- The plan is to leave this repository enabled by default for the
lifetime of a SIG target as it will be empty until we need it again.

- Please report any issue you may find on <a href="http://bugs.centos.org" title="http://bugs.centos.org">http://bugs.centos.org</a>.

thanks,

cbs.centos.org upgrade on 2016-08-24

Hello Folks,

Please note that intervention scheduled on Monday August the 22nd has
been postponed to Wednesday August 24th.

cbs.centos.org will be upgraded to support newer features.

What does that mean for you ?

We will upgrade Imagefactory to latest version.
The change is scheduled to be implemented on Wednesday August 24th 7:00
am UTC time
You can convert to local time with $(date -d '2016-08-24 7:00 UTC')

What will be the impact ?

During the update it will not be possible to build packages or images.
Please note that temporary repositories served on cbs.centos.org will be
available (

cbs.centos.org upgrade on 2016-08-22

Hello Folks,

Please note that next week on Monday cbs.centos.org will be upgraded to
support newer features.

What does that mean for you ?

Next Monday, we will upgrade imagefactory to latest version.
The change is scheduled to be implemented on Monday August 22nd 7:00 am
UTC time
You can convert to local time with $(date -d '2016-08-22 7:00 UTC')

What will be the impact ?

During the update it will not be possible to build packages or images.
Please note that temporary repositories served on cbs.centos.org will be
available (Mostly used for CI).

Please let us know before Thursday August 1

Adding an alternative architecture to your SIG.

Hi Folks,

We are able to build packages for new arches we need to propose a
workflow to support a new architecture in a SIG project.

Two use cases :

A/ It's an official architecture.
-> Sources *must* build for all enable architecture. SIGs are
responsible to fix issues for all arches.
-> We provide a script that will rebuild existing arch specific packages
(scratch build + merge scratch build) if needed.

cbs.centos.org infrastructure upgrade.

Dear All,

Please note that cbs.centos.org has been upgraded successfully.

Please let us know through bugs.centos.org if you find any
issues/regressions.

cbs.centos.org infrastructure upgrade.

Dear All,

Please note that next week on Monday cbs.centos.org will be upgraded to
support newer features and allow us to put in place aarch64 and future
alt arch builders.

What does that mean for you ?

Next Monday, we'll upgrade koji and mock to latest version.
The change is scheduled to be implemented on Monday April 11th, 7:00 am
UTC time
You can convert to local time with $(date -d '2016-04-11 7:00 UTC')

What will be the impact ?

Koji build service will be down for an hour.
It will not be possible to build new packages or images.
Please note that temporary repositories served on cbs.ce

Koji and aarch64 update

Hash: SHA256

Dear All,

Following FOSDEM discussion, I owe an update on the koji development
for aarch64.

Thanks to Fabian, at this we have a builder configured and we are able
to build on specific targets for aarch64. I tested few glusterfs
builds to ensure all operations are working well and no issue was found.

At this time we will support only new builds, it won't be possible to
rebuild an old NVR. A future koji update may help us with this
requirement.

livecd-tools in Extras

Hello,

For CentOS 7 I rely, at work for our minimal pxe image, on the
livecd-tools that are provided by Fabian:

<a href="http://people.centos.org/arrfab/CentOS7/LiveMedia/RPMS/" title="http://people.centos.org/arrfab/CentOS7/LiveMedia/RPMS/">http://people.centos.org/arrfab/CentOS7/LiveMedia/RPMS/</a>

I would like to know if there is a plan to maybe ship these RPMs in
centos Extras (<a href="http://mirror.centos.org/centos/7/extras/" title="http://mirror.centos.org/centos/7/extras/">http://mirror.centos.org/centos/7/extras/</a>) ?

Is there strong opinions against this idea ? What do you think ? Is it
useful to more people ?

thanks for the feedback,

Koji workflow / git branches

Hi Folks,

Few questions/points about the Koji git workflow.

* We have different way to build RPMs in Koji

1/ From source rpm ; you can build any source RPM you submit to the
system.
e.g:
koji build storage7-el7 myNVR.src.rpm

2/ From git ; you send koji an URL + #commit
e.g:
koji build storage7-el7
"git+https://git.centos.org/git/rpms/tzdata.git?#e24d98"
(For that I need to patch kojid so it supports git.c.o schema i.e not
having a .spec file directly at / in git)

The proposal is to have both solutions supported but :
- - Building from src.rpm will be only trigger by git.c.o and will
requ

Koji targets for the SIGs

Hello Folks,

As discussed in the past on this mailing list for the Centos build
service we need to define different koji targets for the SIGs.

Community build system

Hi All,

The initial idea is to configure Koji and make it available to the
community.

Thanks to Karanbir/Fabian we already got the hardware and installation
is on going.

But first, we would like to ask for feedback:

1/ PKI setup, a proposal:
- - koji-web use a certificate signed by an external CA (and obviously
trusted)
- - the rest of the koji architecture (hub and kojid) will use a
self-signed CA that we'll use to also generate other certs.