devel December 2018

devel@lists.centos.org

29 participants
22 discussions

Using mirrorlist in centos-release-* packages
by Anssi Johansson 12 Sep '19

12 Sep '19

Hi, as mentioned in https://lists.centos.org/pipermail/centos-devel/2018-September/016949.html mirrorlist.centos.org has been updated to produce mirror lists for SIG content as well. Some centos-release-* packages have already been modified to use mirrorlist.centos.org instead of mirror.centos.org, but many still point to mirror.centos.org. Most of mirror.centos.org hosts are also used for seeding the 600+ external mirrors we have. By directing some of their download traffic to external mirrors we can offer faster sync speeds for those external mirrors, and for people downloading individual rpms from mirror.centos.org. Second, most of those external mirrors offer faster download speeds to end users than what could be achieved by downloading from mirror.centos.org, so the users will benefit from this change as well. The better geographical coverage does not hurt either. mirror.centos.org nodes are donated servers, and it would be kind to the sponsors to use their bandwidth sparingly. The .repo files should be modified so that the current baseurl line gets commented out and a mirrorlist entry gets added, like this: mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch… #baseurl=http://mirror.centos.org/$contentdir/$releasever/storage/$basearch/gluster-4.1/ Note that mirrorlist.c.o can automatically choose between main and altarch content based on the arch parameter. The repo names are constructed from the repository path by stripping away the architecture and changing any slashes to dashes: sclo/x86_64/rh -> sclo-rh, sclo/x86_64/sclo -> sclo-sclo, paas/x86_64/openshift-origin311 -> paas-openshift-origin311, storage/x86_64/gluster-5 -> storage-gluster-5 etc. You can use 'curl' to check what mirrorlist outputs for your repository. New repos are added to mirrorlist.centos.org automatically once the repository hits mirror.centos.org. That script is currently run every three hours. I guess it could be run more frequently (it's fairly lightweight), but you should give the external mirrors a few hours to sync before announcing your release anyway. You can either submit an update to your current centos-release-* file now, or wait until you need to create a new centos-release-* package for other reasons such as releasing softwarepackage-(version+1) which uses different paths. My recommendation would be to submit an update to your current centos-release-* package, so that you would not need to worry about this when you eventually need to publish a new one for other reasons. We released an updated centos-release package for CentOS AltArch before 7.6.1810 was released for this exact reason, ie. we didn't need to worry about this change at 7.6.1810 release time. Other people (such as bstinson, arrfab and hughesjr) can probably help with creating and publishing an updated centos-release-* package, but the usual tagging procedure to extras will apply. The SIG Guide https://wiki.centos.org/SIGGuide should have all the needed details for this (if not, complain to bstinson). It is highly recommended to actually test your new centos-release-* package from buildlogs before you ask that package to be signed and pushed to extras. The holiday season is fast approaching so (I) don't expect much activity regarding these changes in the following days. I'm hoping that the SIGs would take a look at this in early 2019, though. Thanks to those SIGs who have already made these changes to their centos-release-* packages! If you have questions, feel free to ask either here or on #centos-devel. Thanks for your time!

1 2

Centpkg and the converged git project
by Brian Stinson 22 Feb '19

22 Feb '19

Hi Folks, I've done a bit of work on centpkg, now that we have a testbed at git.stg.centos.org. The goal here is to allow centpkg and fedpkg (Fedora's site) to both understand the different formats. The test version of centpkg described below is the first step in that direction. Basically you can try this out by pulling a container image: `podman pull quay.io/bstinsonmhk/centpkg:develop` Why a container image? - The patches to make this happen involve invasive changes to rpkg, that are still in flight (basically, https://pagure.io/rpkg/pull-request/393) - I wanted to bake in the sources and configs to develop this a little faster as we find problems. What's included, and where to file bugs? - centpkg from: https://bitbucket.org/bstinsonmhk/centpkg/branch/develop - rpkg from: https://pagure.io/fork/bstinson/rpkg/tree/centpkg-inbound - fedpkg from: https://pagure.io/fedpkg/tree/master Here's how I run it for testing CentOS packages (substitute your centos user certificate and a path to RPMs to fit your workstation): `podman run --rm -it -v /home/bstinson/.centos.cert:/home/centpkg-user/.centos.cert:Z -v /home/bstinson/rpms:/home/centpkg-user/rpms:Z quay.io/bstinsonmhk/centpkg:develop` If you're a SIG member, you can push to a sig branch. For example, if I was a mamber of the atomic SIG I could do: # Clone the repo $ centpkg clone -b c7 a2ps # Download the sources from C7 $ centpkg sources # Change to a SIG branch $ git checkout -b c7-sig-atomic-cockpit-preview # Manual push is needed here until we work out a way to register the # new branches $ git push -u origin c7-sig-atomic-cockpit-preview # Upload sources to the SIG branch in the lookaside $ centpkg upload SOURCES/a2ps-4.14.tar.gz SOURCES/i18n-fonts-0.1.tar.gz # CBS does not yet build from SCM, so still need srpms $ centpkg scratch-build --srpm # Try out a fedora branch $ centpkg switch-branch f28 $ centpkg clean # From a Fedora branch this should use your Fedora creds $ centpkg scratch-build # this should work with Fedora's ko What I need help with: - Review the open PRs to rpkg as they come in - Help me find more places where we need to use the new 'Layout' objects (that is where rpkg has paths hard-coded) - Test Fedora workflows, and other commands with centpkg - Help add new commands - to request SIG branches - to translate from one layout to another (ex. bringing a Fedora branch into a CentOS SIG branch) Happy building! --Brian

2 1

[CentOS-docs] Authorization to use CentOS logo in GNOME Boxes
by Ladar Levison 21 Feb '19

21 Feb '19

> Who will prepare the logo? I do not know, we could use a volunteer. > I had to track down SVG logo files for the Robox website. Not sure, is this what you need? https://roboxes.org/res/centos.svg

5 18

collectd-5.8.1 not being published to mirrors
by Sandro Bonazzola 31 Dec '18

31 Dec '18

Hi, collectd-5.8.1-1.el7 has been tagged for release on December 6th: Thu Dec 6 13:15:37 2018: collectd-5.8.1-1.el7 tagged into opstools7-perfmon-common-release by mrunge [still active] but it's not showing up in http://mirror.centos.org/centos/7/opstools/x86_64/perfmon/ Can you please check? -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 1

Storage SIG, where is glusterfs-server?
by Carl T. Miller 24 Dec '18

24 Dec '18

I've spent hours searching for the glusterfs-server package and everywhere I looked said to use packages from the Storage SIG. After installing each of the centos-release-gluster* packages, I still get "No package glusterfs-server available." So...I checked the documentation on the wiki and it says to start by installing glusterfs-server. Is there a reason that there is no package for the server? Are there plans to create one? (Preferably for 4.0, 4.1 and 5.) May I (or would you) update the wiki to reflect the current status of glusterfs on CentOS? Thank you! c

2 2

[Meeting] RDO meeting (2018-12-19) minutes
by Haïkel 19 Dec '18

19 Dec '18

============================== #rdo: RDO meeting - 2018-12-19 ============================== Meeting started by number80 at 15:04:15 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_12_19/2018/rdo_m… . Meeting summary --------------- * roll call (number80, 15:04:28) * Revisit haproxy situation (number80, 15:08:47) * AGREED: use F28 and/or PaaS SIG build of haproxy 1.8 (number80, 15:22:28) * bandini submitted patches for tripleo to support haproxy 1.8 without breaking compat with 1.5 (number80, 15:23:15) * ML migration (number80, 15:32:04) * ping leanderthal about ML migration (number80, 15:35:27) * open floor (number80, 15:35:39) * baha requested reviewers for ppc64le container build job (number80, 15:37:47) * LINK: https://review.rdoproject.org/r/#/c/17741/ (number80, 15:37:55) * ACTION: number80 review it (number80, 15:38:06) * amoralej will chair Jan, 9 meeting (number80, 15:39:04) Meeting ended at 15:40:35 UTC. Action items, by person ----------------------- * number80 * number80 review it People present (lines said) --------------------------- * number80 (47) * dciabrin_ (23) * amoralej (22) * Duck (15) * ykarel (10) * openstack (6) * jpena (5) * baha (3) * bandini (2) * PagliaccisCloud (1) * rdogerrit (1) Generated by `MeetBot`_ 0.1.4

1 0

Fwd: Atomic ISO unavailable
by Eric Lehmann 17 Dec '18

17 Dec '18

Hello Please see below. CentOS mailing list was maybe not the right onw. Thank you. ---------- Forwarded message --------- From: Eric Lehmann <e.lehmann88(a)gmail.com> Date: Fr., 14. Dez. 2018 um 16:04 Uhr Subject: Atomic ISO unavailable To: CentOS mailing list <centos(a)centos.org> Hello The http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-Install… provided in https://wiki.centos.org/SpecialInterestGroup/Atomic/Download is down. Does anybody know if there is a reason for that? Regards

2 2

CentOS Container Pipeline Service OpenShift upgrade to v3.10
by Bamacharan Kundu 14 Dec '18

14 Dec '18

Hi, We are going to upgrade OpenShift cluster for CentOS Container Pipeline service from OpenShift v3.9 to v3.10. For this we will be having downtime for container builds, there will be no downtime for registry.centos.org. Service: registry.centos.org Impact: There will be no downtime for the service and users will able to pull images normally. Service: CentOS Container Pipeline Service Impact: Service will be down, no builds will run Time: 14 Dec 2018, 0430 UTC to 0830 UTC Regards Bamacharan Kundu

1 1

[Meeting] RDO meeting (2018-12-12) minutes
by Haïkel 12 Dec '18

12 Dec '18

============================== #rdo: RDO meeting - 2018-12-12 ============================== Meeting started by number80 at 15:02:11 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_12_12/2018/rdo_m… . Meeting summary --------------- * roll call (number80, 15:02:43) * haproxy 1.8 packaging (number80, 15:04:55) * LINK: https://github.com/mwhahaha/kolla/tree/fedora (mwhahaha, 15:18:19) * AGREED: revisit haproxy 1.8 situation next week (number80, 15:26:48) * What to do with upcoming meetings (number80, 15:28:02) * AGREED: Cancelling december, 26 and January, 2 RDO meeting (number80, 15:29:57) * AGREED: Cancelling december, 26 and January, 2 RDO meetings (number80, 15:30:05) * ACTION: number80 Notify the list about meetings cancelled (number80, 15:32:11) * FOSDEM and DevConf.CZ booths and swag (number80, 15:32:17) * we need volunteers for openstack and RDO booths at FOSDEM/devconf.cz (number80, 15:34:23) * submit ideas for RDO goodies to leanderthal (number80, 15:34:32) * next meeting chair (number80, 15:35:14) * ACTION: number80 to chair next week (number80, 15:36:52) * open floor (number80, 15:36:59) Meeting ended at 16:00:16 UTC. Action items, by person ----------------------- * number80 * number80 Notify the list about meetings cancelled * number80 to chair next week People present (lines said) --------------------------- * number80 (62) * amoralej (56) * mwhahaha (29) * ykarel (23) * dciabrin (17) * rdogerrit (8) * Vorrtex (8) * openstack (7) * Duck (6) * bandini (5) * quiquell (4) * jpena (2) * moguimar (1) Generated by `MeetBot`_ 0.1.4

1 0

CentOS Atomic Host 7.1811 Available for Download
by Jason Brooks 07 Dec '18

07 Dec '18

The CentOS Atomic SIG has released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1811), an operating system designed to run Linux containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. CentOS Atomic Host includes these core component versions: * atomic-1.22.1-26.gitb507039.el7.centos.x86_64 * cloud-init-18.2-1.el7.centos.1.x86_64 * podman-0.11.1.1-3.git594495d.el7.centos.x86_64 * docker-1.13.1-84.git07f3374.el7.centos.x86_64 * etcd-3.2.22-1.el7.x86_64 * flannel-0.7.1-4.el7.x86_64 * kernel-3.10.0-957.1.3.el7.x86_64 * ostree-2018.5-1.el7.x86_64 * rpm-ostree-client-2018.5-2.atomic.el7.x86_64 ## Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download). ## Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: # atomic host upgrade ## Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. ## Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG (http://wiki.centos.org/SpecialInterestGroup/Atomic), based on upstream work from Project Atomic (http://www.projectatomic.io/). If you'd like to work on testing images, help with packaging, documentation -- join us! You'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel (https://lists.projectatomic.io/mailman/listinfo/atomic-devel) mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions. ## Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel (http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the atomic (https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or find us in the #atomic channel on Freenode.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel December 2018