devel January 2019

devel@lists.centos.org

28 participants
25 discussions

AMI images on AWS
by Rich Bowen 23 Jan '19

23 Jan '19

I asked this on IRC, but posting it here, too, in case someone sees it here and not there. Can someone volunteer to respond to this tweet: https://twitter.com/translatewiki/status/1088137687461183488 "@CentOSProject Can you point me to an active contributor to cloud images in the community? I've searched before, and failed, and the CentOS @awscloud AMIs haven't been updated since May 2018 (i.e. are still on 7.5). https://aws.amazon.com/marketplace/pp/B00O7WM7QW " I have no idea how those are updated, or who provided what's there. I seem to remember asking this before, but I don't think anybody raised their hands. If you know, or if it's you, please document here - https://wiki.centos.org/Cloud/AWS - how one goes about uploading those images, and/or who is responsible for doing so. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 1

Adding to the PPC arch group
by Philip Prindeville 22 Jan '19

22 Jan '19

Hi. I and my development group are interested in doing ppc (ppc32) development for CentOS 7 and getting that running on certain SoC-based platforms. I imagine that there’s some overlap with the 32-bit component on the Power7 work. We have Centos 7.6 x86_64 servers that we can do in-house builds on. We’re mostly looking for collaboration, and maybe a little initial guidance about the pitfalls of setting up a cross build environment, adapting RPM .spec's for additional architectural builds, etc. We have no idea how much work this will be. We’re also interested in supporting newer (4.10 or later) kernels, so we’ll probably contribute to elrepo as well. Any pointers/wisdom welcome. Thanks, -Philip

2 1

what about CentOS7 ppc64 ?
by Fabian Arrotin 22 Jan '19

22 Jan '19

Just wondering the status of CentOS 7 ppc64, as 7.6.1810 was released on December 3rd 2018 for all arches *but* ppc64, and no news since. In the CentOS Infra, I had to maintain ppc64 hosts for both cbs/koji and other nodes, but as recently, someone decided to archive 7.5.1804 to vault, and also that there is no ppc64 anymore on mirrors, one having to deal with ppc64 is now in a position where : - it's impossible to install new ppc64 host - it's impossible to just "yum install" anything either Can we get an official statement from the ppc64 maintainer about this ? Or should we consider that arch dead and unmaintained, and if so, I can remove ppc64 from the centos infra too ... (or maybe we should find a new maintainer, etc ..) Anyway, any official statement would be good at this stage. Cheers, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 1

DevConf.CZ RDO Booth Call For Volunteers and Demos!
by Rain Leander 22 Jan '19

22 Jan '19

Hello one and all! We are gearing up for DevConf.CZ <https://devconf.info/cz>where we'll have our regular booth presence. We'll continue the ManageIQ / RDO demo we started last year and we'd love to see your demos, too! If you've got something you'd like to demo via video OR LIVE because you're not afraid of ANYTHING, please sign up! <https://etherpad.openstack.org/p/devconfCZ-2019-booth> We're also looking for people to spend their precious free time answering questions at the RDO booth. If you're attending, please consider spending one or more of your free moments with us. Questions run the gamut from "What's RDO?" to "I found a bug in Neutron and need help troubleshooting it." Of course, you're not expected to know everything and you can always keep IRC open to access the RDO Community for help! Plus, you get cool stuff! If you show up for three or more shifts, we're going to hook you up with an RDO hoodie. See you soon! -- K Rain Leander OpenStack Community Liaison Open Source and Standards Team https://www.rdoproject.org/ http://community.redhat.com

1 0

CentOS support of s390x architecture
by Vaibhav Kaushik 19 Jan '19

19 Jan '19

Hello everyone, I want to help in building the official centOS support of s390x architecture for Open Mainframe Project. I have familiarity with Linux and working with build systems. The task is to "Bootstrap CentOS on Z" and I need some guidance and reference about where to begin so that I can start learning and contributing. -- Regards, Vaibhav Kaushik (vaibhavk.github.io)

1 0

centos-logos package not updated on git.centos.org
by Maheshwari, Shagun 18 Jan '19

18 Jan '19

Hi, I am using git.centos.org site for source code but don't see the latest commit of centos-logos package on git.centos.org. And, at vault.centos.org centos-logos-70.0.6-3.el7 version is available which is latest, could anyone please check. Version on git.centos.org site: 70.0.6-2 Version on vault.centos.org site: 70.0.6-3 Regards, Shagun

1 0

Vagrant centos/7 v1811.01 breaks nfs at boot
by John-Paul Robinson 17 Jan '19

17 Jan '19

Hi folks, It seems that the latest vagrant box for centos/7 is breaking nfs mounts at boot. My vagrant project has an nfs server and client node. The client has two nfs mount in fstab. https://gitlab.rc.uab.edu/jpr/ohpc_vagrant Using the image from the prior release (1804.02, kernel 3.10.0-862.2.3.el7.x86_64, CentOS Linux release 7.5.1804 (Core) ) the mounts complete successfully. The newest releases (1811.02 and 1809.01) fail to mount the drives at boot. I believe the differences between the older VMs using XFS and volume manager vs direct device and ext4 in the newer images are changing the boot timings of services. The messages.log shows that the network is unavailable at the point which the nfs mounts are tried on the failing nodes. The wait service doesn't appear to work right or wait long enough to allow the network to come up first. It seems that the boot for the direct use of the sda1 and use of ext4 simply initializes too fast. Here's the top of the systemd blame info for the box that succeeds in it's nfs mounts at boot (v1804.02). Note that the boot times are dominated by the network manager wait service: [vagrant@ood ~]$ systemd-analyze blame 2.970s NetworkManager-wait-online.service 1.511s tuned.service 1.272s postfix.service 594ms httpd24-httpd.service 538ms lvm2-monitor.service 474ms opt-ohpc-pub.mount 471ms home.mount 450ms auditd.service 444ms dev-mapper-VolGroup00\x2dLogVol00.device 380ms boot.mount 343ms network.service 216ms munge.service 206ms NetworkManager.service 177ms chronyd.service 157ms polkit.service 149ms sshd.service 148ms systemd-logind.service 134ms slurmd.service 114ms gssproxy.service 112ms lvm2-pvscan@8:3.service 112ms rpc-statd.service 112ms systemd-udev-trigger.service 111ms rsyslog.service 110ms rhel-readonly.service 105ms rhel-dmesg.service 91ms systemd-vconsole-setup.service 84ms systemd-tmpfiles-setup-dev.service 74ms systemd-tmpfiles-clean.service 72ms dev-mapper-VolGroup00\x2dLogVol01.swap 66ms kmod-static-nodes.service 65ms rhel-domainname.service 65ms rpc-statd-notify.service ... Here's the top of systemd blame info for the box that is failing to mount nfs (v1811.02), network manager barely waits: [vagrant@ood ~]$ systemd-analyze blame 1.811s dev-sda1.device 1.737s tuned.service 1.594s postfix.service 785ms httpd24-httpd.service 378ms systemd-vconsole-setup.service 295ms slurmd.service 291ms network.service 286ms home.mount 266ms auditd.service 253ms opt-ohpc-pub.mount 250ms NetworkManager-wait-online.service 208ms systemd-udev-trigger.service 200ms polkit.service 188ms systemd-tmpfiles-setup-dev.service 180ms sshd.service 177ms chronyd.service 175ms rhel-readonly.service 146ms rhel-dmesg.service 145ms munge.service 144ms gssproxy.service 141ms rpcbind.service 139ms swapfile.swap 112ms rhel-domainname.service 102ms systemd-udevd.service 101ms systemd-journald.service 91ms rpc-statd.service 78ms rsyslog.service 70ms var-lib-nfs-rpc_pipefs.mount 69ms systemd-tmpfiles-setup.service 61ms rpc-statd-notify.service 58ms systemd-journal-flush.service 58ms systemd-sysctl.service ... I have the boot svd graphs that tell a similar story on the sequencing of service startup. Is there a way to add delay to the network manager wait or otherwise influence the boot configuration to ensure the NFS drives mount correctly at boot? Thanks, John-Paul

3 4

signing of openvswitch.ko with kernel signing key
by Maheshwari, Shagun 15 Jan '19

15 Jan '19

Hi, Latest CentOS kernel comes with openvswitch-2.0.0 drivers, but for an application, I needed openvswitch-2.9.2. I am trying to get my openvswitch.ko (from openvswitch-kmod-2.9.2-1.el7.centos.x86_64.rpm ) to get signed by the kernel module signing key. To achieve this I included below line to my spec file: mv signing_key.x509.sign.debug signing_key.x509 \ %{modsign_cmd} ~/home/nupur/openvswitch/*.ko %{modsign_cmd} $RPM_BUILD_ROOT/lib/modules/%{KVRA}.debug || exit 1 \ fi \ if [ "%{with_default}" -ne "0" ]; then \ But the build is failing. Please suggest , if it is feasible to achieve this. Or is this the right thing to do to sign third-party module with centos signing key. Regards, Shagun

3 2

moving packages through -candidate to -testing and -release
by Ken Dreyer 15 Jan '19

15 Jan '19

Hi folks, Does anyone have any tooling today that can tag CBS packages as -testing and then tag them as -release? Currently we're tagging packages by hand into -testing and -release, but that makes it really easy to miss builds. I'm looking for something like Bodhi, but something that we can generalize to work with Ceph in CBS. - Ken

2 1

new "mock-ceph-config" git repository
by Ken Dreyer 14 Jan '19

14 Jan '19

Hi Niels, Would you please create a "mock-ceph-config" Git repository at https://github.com/CentOS-Storage-SIG? This will be the dist-git repository location for our mock configs for Ceph. - Ken

2 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2019