devel

devel@lists.centos.org

5 participants
4621 discussions

SIG-Paas request
by Troy Dawson 04 Feb '16

04 Feb '16

Hi, As a member of the OpenShift project, I am trying to get OpenShift Origin into CentOS. This effort would create CentOS OpenShift Origin rpm's, along with their dependencies. It would also involve creating CentOS OpenShift Origin docker images. It could also involve creating virtual machine and/or cloud images. Virtual machine and cloud images are not part of our original wants and needs, but if someone were to help create them, we wouldn't say no. I am requesting a SIG, named SIG-Paas. If the committee feels that is too broad, then we would like SIG-OpenShift. Thank You Troy Dawson

7 10

Yum missing from Atomic image
by Bent Terp 04 Feb '16

04 Feb '16

Hi, this may be a deliberate choice but I can't really figure out why one would make that decision... [centos@atomic ~]$ sudo yum update sudo: yum: command not found [centos@atomic ~]$ rpm -ql yum | grep bin /usr/bin/yum [centos@atomic ~]$ ls -l /usr/bin/yum ls: cannot access /usr/bin/yum: No such file or directory [centos@atomic ~]$ I used the latest http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-Generic… in an RDO deploy. I don't experience the same issue with the regular image only with the Atomic. regards, Bent

3 3

[altarch?] Naming scheme and lorax parameters for userland + non-distro kernel builds
by Brian Stinson 03 Feb '16

03 Feb '16

Hi All, I'm working on putting some things together for a couple of the Intel boards (Edison, Jaguarboard, etc.) and was wondering if there's a standard way we should be naming things on the install media. For the rpi2, we use 'CentOS Altarch 7 (1511) Userland for armhfp' A lot of the Intel boards out there require a newer or otherwise non-distro kernel so I was considering titling the install media like this: CentOS Altarch 7 (1511) Userland for x86_64 Not sure if the 'Altarch' bit applies because it's the standard x86_64 userland (no rebuilding needed). Cheers! --Brian

3 2

How to create CentOS 7.2 ppc64 image
by Vit Ry 30 Jan '16

30 Jan '16

Hi all. How can I create CentOS 7.2 image for ppc64 arch? Are there any scripts, guides, etc..(is it open source..?)? What is difference between build envs for RH 7.0 and CentOS 7.2 ..? I see, RH uses yaboot as bootloader and so on, when C7.2 - uses grub... --- Regards, Vit Ry.

2 2

Fwd: sig-core-t_functional suite for 7.2.1511
by Thierry Fauck＠linux.vnet.ibm.com 29 Jan '16

29 Jan '16

As talked earlier today, Here are my comments - I understand they are mostly related to the environment it is running into, but it may be interesting to look into it to improve the cases. Regards Thierry (nick - thf ) -------- Forwarded Message -------- Subject: sig-core-t_functional suite for 7.2.1511 Date: Tue, 22 Dec 2015 11:14:29 +0100 From: Thierry Fauck(a)linux.vnet.ibm.com <thierry(a)linux.vnet.ibm.com> To: centos-qa(a)centos.org Hello, While checking the suite for ppc64 and ppc64le, I got the following changes and comment - let me know if you want a diff file. - runtest.sh If script fails and you relaunch it a second time, you may get a failure because tests users are already created - I suggested to remove all test users in runtests.sh to have a clean environment. In t_CheckExitStatus shouldn't we add the test name being run to ease tracing and script debugging like ? [ $1 -eq 0 ] && { t_Log "$0 PASS"; return $PASS; } - Depending on your setting, you may come with LC_ALL setting as utf8 or C and 10-cmp-tests may fails - checking for byte or char would allow both settings to be run. cmp -i 15:16 ${FILE}a ${FILE}b | egrep -q "byte 1, line 1|char 1, line 1"|| ExitFail - tests/p_mtr/mtr_test.sh fails if you are not in the centos.org env as it tries to reach the qa host. As this test is done at start of runtest.sh, in case it is not true, shouldn't you use another hosts found on your local network (an easy bypass is to use like the local DNS server or the gateway ?). - p_shadow-utils/20-chage_tests may fails because of capital letters jan versus Jan - I would suggest to use chage -l testshadow | grep Last | grep -qi "Jan 01, 2013" - tests/p_shim/01_shim_secureboot_signed.sh tests/p_kernel/02_kernel_secureboot_signed.sh are x86_64 dependant - Had to increase -T delay from 2 to 8 in tests/p_squid/squid_test.sh - tests/p_systemd/25-journalctl.sh - for fast processors, you need to had a delay for journalctl to cope with your message - I added a sleep 1 after writting to /dev/kmsg - tests/p_which/which_basic.sh - sounds like wich is now in /bin instead of /usr/bin - /usr/bin/which which | grep -q "/bin/which" would cope with both cases Hope that helps -- Thierry

1 0

Why is systemd user instance support disabled in CentOS 7 / RHEL 7?
by Tadej Janež 28 Jan '16

28 Jan '16

Hi! I'm preparing a backup package for Fedora/EPEL 7 [1] that provides a web server with a systemd unit file for running with the systemd user instance (i.e. 'systemd --user'). As reported in [2], systemd user instance support is disabled in CentOS 7 due to being disabled in the upstream RHEL package. It is the same with the latest systemd for CentOS 7 [3]. Unfortunately, the original Red Hat Bugzilla report [4] is not public so I'm asking here if anyone has more information why this is disabled? Thanks and regards, Tadej [1] https://apps.fedoraproject.org/packages/bup [2] https://bugs.centos.org/view.php?id=8767 [3] https://git.centos.org/blob/rpms! systemd/1ff63606a64d814f37c4956854107e049a684754/SOURCES! 0004-remove-user-.service.patch [4] https://bugzilla.redhat.com/show_bug.cgi?id=1019738

4 5

Questions regarding SCLo rpms
by BC 28 Jan '16

28 Jan '16

What is the meaning of the prepended "rh-" in some of the scl RPM names? At first I thought they were rebuilt from official upstream RHEL rpms, but it appears non "rh-" prepended ones are, too. Which leads me to wondering who is the original upstream for packages in the sclo/x86_64/{sclo,rh} directories? Is the rh directory that which contains RPMs blessed by RH (as in, they provide support for) but which exists to centos users as a rebuild of the official RHEL RPMs as all the base packages generally are? I know that as a centos user, the upstream for the purpose of support and bug submission is never RHEL, so my question re: upstream is more of a point of origin question, I guess. Thank you for your time

2 1

CentOS SCLo SIG sync-up meeting on #centos-devel (2016-01-27)
by Honza Horak 27 Jan '16

27 Jan '16

SCLo SIG meeting will be today at 16:00 UTC (11:00 EST, 17:00 Brno, 11:00 Boston, 0:00+1d Tokyo, 1:00+1d Brisbane) in #centos-devel on Freenode. = Topics = I don't have any specific topics but want to be around and available since there are now couple of more people building in SCLo SIG, so maybe there will be some topic raised by someone else. Honza

3 3

[Cloud SIG] weekly meeting
by Rich Bowen 26 Jan '16

26 Jan '16

The Cloud SIG holds its weekly meeting on Thursdays at 15:00 UTC in #centos-devel on Freenode. It has become evident that this isn't a great time. Turnout is very poor, and many of the folks that want to come, have conflicts almost every week. I was wondering if I could get a show of hands of who would like to be attending that meeting, so that we can get some idea of the distribution of time zones, and see if we can find a better time. Thanks. -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

3 3

[Storage SIG] Ceph build target and tags: +1s required
by François Cami 26 Jan '16

26 Jan '16

Hi, The Ceph project needs build targets and tags for Ceph Hammer in cbs. We would like to use upstream release names (Hammer, Infernalis...) instead of versions ( http://docs.ceph.com/docs/master/releases/ [^] ). Repositories are at: https://github.com/CentOS-Storage-SIG/ceph https://github.com/CentOS-Storage-SIG/ceph-deploy The relevant Hammer git branch is currently sig-storage7-ceph-hammer. So I believe the cbs build target should be: storage7-ceph-hammer-el7 and tags: storage7-ceph-hammer-{candidate,testing,release} Karanbir, Lalatendu, Patrick, Niels, Brian, Lincoln, could you please validate the naming scheme, and then add +1s as requested by Thomas at: https://bugs.centos.org/view.php?id=10244 François

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel