I am working on the November newsletter (See
https://wiki.centos.org/Newsletter for past issues) and would like
content from you. Relevant topics include:
* What interesting things you're working on, in or on CentOS
* SIG reports (these have already been requested, but if you have
something interesting to report, that would be of interest)
* Releases (either of SIG projects, or something else that you're
working on)
* Tutorials/Howtos
* Upcoming events that you would like to promote
* Recent events that you attended and want to tell us about
Please either contact me directly, or (better yet) post to the
centos-promo mailing list (copied here) with your ideas, your articles,
or suggestions of who I should be approaching. Thanks!
--
Rich Bowen - rbowen(a)redhat.com
@CentOSProject // @rbowen
859 351 9166
FOSDEM will be February 1st and 2nd in Brussels, Belgium.
It would be great to have representation from each of our SIGs at
FOSDEM. There are dozens of devrooms this year -
https://fosdem.org/2020/news/2019-10-01-accepted-developer-rooms/ - and
many of them have some direct relevance to you. Note that each devroom
handles its own call for presentations separately, which is a bit of a
hassle. So have a look at the list and see the track(s) where your
content would be most relevant. Please keep me informed once you know
that your talk(s) have been accepted.
We are also running the annual CentOS Dojo on the Friday before the main
FOSDEM event (January 31). The details are at
https://wiki.centos.org/Events/Dojo/Brussels2020 and we need (roughly)
14 presentations. I would love to have representation from our various
SIGs there. The audience tends to be those most passionate about CentOS,
and they're looking for fairly deep technical content about what you're
working on, both *in* and *on* CentOS. If you want help with an idea, or
with your abstract, please let me know.
--
Rich Bowen - rbowen(a)redhat.com
@CentOSProject // @rbowen
859 351 9166
Hi Folks,
>> We are going to announce soon a plan to upgrade cbs.centos.org and
>> associated builders to be able to build standard C8 RPM packages,
>> without interfering too much with SIGs ongoing work.
>
> is this plan discussed on Mondays CBS meetings?
> I don't see it logged in https://www.centos.org/minutes/2019/September/
We didn't manage to have a meeting on Monday.
>> To conclude, we will send an update beginning of next week with more
>> information, a schedule and a list of points that need to be sorted out
>> with the community.
I'll try to give a summary of my investigation. I'll decouple two
problems : the koji upgrade and having a working CentOS 8
target/buildroot in cbs.centos.org with CentOS 7 builders.
1/ koji upgrade
The first step is to upgrade our version of koji to match the version
mbox uses. At the same time we move away from puppet to ansible (thanks
Arrfab for all the work! [1] & [2]) and upgrade the base operating
system from CentOS 6 to CentOS 7.
At the same time the builders (where mock runs) need to run specific
version of certain tools for C8 buildroots :
distribution-gpg-keys.noarch 1.21-1.el7
kernel.x86_64 4.19.34-300.el7
mock.noarch 1.3.4-1.el7_build.rhel8
python-perf.x86_64 4.19.34-300.el7
python2-distro.noarch 1.0.3-1.el7.rhel8
* Status: Update works and db schema can be easily upgraded. We have few
more test to validate that the previous mentioned RPM updates don't
break anything for C6 & C7 targets.
Next step is to announce a downtime and execute the upgrade plan.
2/ CentOS 8 buildroot
When 1/ is done we can create an C8 buildroot without enabling the
Appstream repo.
Due to the nature of Appstream, and how koji uses mergerepo
(--koji)/updaterepo/mock, more work is needed to get a working buildroot.
I don't fully understand the underlying issue so comments are very
welcome to enlighten us !
One of the solution found by Fedora team is to split Appstream per
repository and enable only the one needed in a specific buildroot [3].
We are evaluating the tools. And see if we can use koji external-repo or
tag inheritance to achieve it (which is mbox solution [4])
However for a community build service, we don't know exactly what people
will build and what Appstream packages will be needed in each buildroot
(we have 290 targets at this time for C7). So we still need time and new
ideas :-)
* Status: Investigating possible solutions.
--
Thomas Oulevey
[1] : https://github.com/CentOS/ansible-role-kojihub
[2] : https://github.com/CentOS/ansible-role-kojid
[3] : https://github.com/fedora-modularity/GrobiSplitter
[4] : https://koji.mbox.centos.org/koji/taginfo?tagID=3
Dear All,
As previously announced [1], an intervention on cbs.centos.org will
start in few minutes at 2019-10-28 7:00 UTC.
--
Thomas on behalf of the infrastructure team.
[1]:
* What does that mean for you ?
Next Monday, we'll upgrade koji and tools to 1.16 version. At the
same time the koji hub server will be moved from CentOS 6 to CentOS 7.
The change is scheduled to be implemented on Monday October 28th, 7:00
am UTC time
You can convert to local time with $(date -d '2019-10-28 7:00 UTC')
* What will be the impact ?
Koji build service will be down for 4 hours.
It will not be possible to build new packages or images.
Please note that temporary repositories served on cbs.centos.org will be
also affected ; they are mostly used for CI.
Please let us know before Friday October 25th if it could impact
dramatically your work/releases schedule.
If the article isn't posting correctly, please feel free to visit it
directly at
https://blogs.rdoproject.org/2019/10/cycle-trailing-projects-and-rdos-lates…
---
The RDO community is pleased to announce the general availability of the
RDO build for OpenStack Train for RPM-based distributions, CentOS Linux and
Red Hat Enterprise Linux. RDO is suitable for building private, public, and
hybrid clouds. Train is the 20th release from the OpenStack project, which
is the work of more than 1115 contributors
<https://www.stackalytics.com/?metric=commits> from around the world.
The release is already available on the CentOS mirror network at
http://mirror.centos.org/centos/7/cloud/x86_64/openstack-train/.
BUT!
*This is not the official announcement you’re looking for.*
We’re doing something a little different this cycle – we’re waiting for
some of the “cycle-trailing”
<https://releases.openstack.org/reference/release_models.html#cycle-trailing>
projects that we’re particularly keen about, like TripleO
<https://docs.openstack.org/tripleo-docs/latest/developer/release.html> and
Kolla
<https://docs.openstack.org/kolla/latest/contributor/release-management.html>,
to finish their push BEFORE we make the official announcement.
Photo by Denis Chick on Unsplash
Deployment and lifecycle-management tools generally want to follow the
release cycle, but because they rely on the other projects being completed,
they may not always publish their final release at the same time as those
projects. To that effect, they may choose the cycle-trailing release model
<https://docs.openstack.org/project-team-guide/release-management.html#trail…>
.
Cycle-trailing projects are given an extra three months after the final
release date to request publication of their release. They may otherwise
use intermediary releases or development milestones.
While we’re super hopeful that these cycle trailing projects will be
uploaded to the CentOS mirror before OpenInfrastructure Summit Shanghai
<https://www.openstack.org/summit/shanghai-2019>, we’re going to do the
official announcement just before the Summit with or without the packages.
We’ve got a lot of people to thank!
Do you like that we’re waiting a bit for our cycle trailing projects or
would you prefer the official announcement as soon as the main projects are
available? Let us know in the comments and we may adjust the process for
future releases!
In the meantime, keep an eye here or on the mailing lists
<https://lists.rdoproject.org/mailman/listinfo> for the official
announcement COMING SOON!
--
K Rain Leander
OpenStack Community Liaison
Open Source Program Office
https://www.rdoproject.org/http://community.redhat.com