devel July 2016

devel@lists.centos.org

36 participants
37 discussions

Re: [CentOS-devel] [rdo-list] [centos-ci] Artifacts server does not support ranges / resume of downloads?
by Haïkel 18 Aug '16

18 Aug '16

2016-06-28 4:25 GMT+02:00 Gerard Braad <me(a)gbraad.nl>: > Hi all, > > > Usually I download the undercloud images using: > > https://gist.github.com/gbraad/45cbe30415b0dc631f5e8d20beaffebf > > which targets: 'artifacts.ci.centos.org' but now get > > "HTTP server doesn't seem to support byte ranges. Cannot resume." > > I need to resume a download about 10 times on the office connection > (China), so what happened? I have a workaround by storing the files at > another server first in Japan or the west-coast which supports > resuming. > > Although, being able to resume the download of these files is preferable. > > regards, > > > Gerard > Since this part of infrastructure is managed by CentOS Core Team, CC'ing centos-devel list. > > -- > > Gerard Braad | http://gbraad.nl > [ Doing Open Source Matters ] > > _______________________________________________ > rdo-list mailing list > rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com

6 9

Ceph Jewel packaging in CentOS Storage SIG
by Emilien Macchi 16 Aug '16

16 Aug '16

Hi, I'm working on openstack/puppet-ceph module to deploy Ceph Jewel for OpenStack TripleO and Red Hat Director (OpenStack installers). I'm very interested to know when I'll be able to download Jewel packages from SIG on x84_64: buildlogs.centos.org/centos/7/storage/x86_64/ceph-jewel/ currently does not contain Ceph packages. Using ceph.com repositories for us is not optimal as we try to use a maximum of CentOS supported repositories, like we do for OpenStack. Thanks, -- Emilien Macchi

4 10

[Opstools][poll] weekly meeting time
by Matthias Runge 06 Aug '16

06 Aug '16

Hello, to make further progress, we should schedule weekly meetings for the newly founded and approved SIG Opstools The link to the poll is here: http://doodle.com/poll/etgeynq7x3w5t9pr If you're interested in opstools and would like to participate, your feedback is appreciated! Even if you can't make it and we need to change the poll/add times. Best, Matthias

4 4

role based builder capability
by Karanbir Singh 28 Jul '16

28 Jul '16

hi, we've spoken about this in the past a few times, and I've gone ahead to setup the rdobuilder account for building against koji. what this means is that its now possible to have a role based koji account, with some level of limited credentials, that allows a robot like process to build, tag, request-test from koji content. Ofcouse, we need to ensure this bot is unable to tag to release any content, or to promote internally. Anyone else needing this functionality, you will need to get in touch and come through to the CBS meeting to talk through the requirements and justifications. Haikel: this should unblock your work here. Brian: Can we get this included in the SIGGuide content as well, thanks, -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

1 0

How to test CentOS Origin images
by Troy Dawson 28 Jul '16

28 Jul '16

Hi, This email is to get a discussion started. I don't have the answers, so feel free to add to the discussion. The PaaS SIG (through the hard work of Mohammed Ahmed, mzee1000) is now producing OpenShift Origin images. They are currently for origin 1.2. We need some tests so that we can say "These are good images" and then release them. What are some tests that we can run on the images to verify they are good? Troy

4 4

CentOS PaaS SIG meeting (2016-07-27)
by Troy Dawson 27 Jul '16

27 Jul '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 27 July 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing -- images / image building - OpsTools SIG ? - Open Floor

1 0

Testing Vagrant images on ci.centos.org?
by Laurentiu Pancescu 26 Jul '16

26 Jul '16

Currently, the development of the Vagrant images relies on manual testing (I create scratch builds containing my changes and test them locally - due to hardware limitations, this means only testing with VirtualBox on an OS X host). Is it technically possible to automatically test the Vagrant images on ci.centos.org, using e.g. KVM via vagrant-libvirt? Perhaps we could add some sort of trigger on cbs.centos.org to trigger the tests, once a scratch build is successful? Regards, Laurențiu

2 1

/etc/sysconfig/network-scripts/network-functions max limit is 255
by Donatas Abraitis 22 Jul '16

22 Jul '16

Hi folks, what do you think of introducing new variable which could define max value for index iterating over PREFIX/NETMASK pair? Problem: Now it's hardcoded value of 255 in /etc/sysconfig/network-scripts/network-functions: expand_config () { local i=0 val for idx in '' {0..255} ; do ipaddr[$i]=$(eval echo '$'IPADDR$idx) if [ -z "${ipaddr[$i]}" ]; then [ "$idx" ] && [ $idx -ge 2 ] && break continue fi prefix[$i]=$(eval echo '$'PREFIX$idx) netmask[$i]=$(eval echo '$'NETMASK$idx) broadcast[$i]=$(eval echo '$'BROADCAST$idx) arpcheck[$i]=$(eval echo '$'ARPCHECK$idx) We are running plenty of addresses (over 500) under loopback interface and announcing them as /32 for upstream hosts. With IPv6 everything is OK, because it has already native secondary option. I suggest to add additional variable like MAXALIAS to define this '255' inside ifcfg-lo. Any thoughts? Thank you! -- Donatas

1 0

glibc build fails on disk >2TB
by Captain Wiggum 21 Jul '16

21 Jul '16

We are rebuilding the centos 6.8 src.rpm's for both 64-bit (.x86_64.rpm) and also 32-bit-compat (.i686.rpm) When making 32-bit compatible build on a disk >2TB, the build will fail because or large inodes: /home/mlos/WORK/os/PACKAGES/glibc/WORK/BUILD/glibc-2.12-2-gc4ccff1/build-i686-linuxnptl/elf/sln /home/mlos/WORK/os/PACKAGES/glibc/WORK/BUILD/glibc-2.12-2-gc4ccff1/build-i686-linuxnptl/elf/symlink.list /home/mlos/WORK/os/PACKAGES/glibc/WORK/glibc-root/lib/ld-linux.so.2: invalid destination: Value too large for defined data type The solution is to add "-D_FILE_OFFSET_BITS=64" and this has fixed the issue on glibc and all our other i686 RPM builds. However, with the latest update glibc-2.12-1.192.el6.src.rpm we find adding the above flag will cause the following error: In file included from ftello.c:29: ../include/stdio.h:151: warning: asm declaration ignored due to conflict with previous rename ftello.c:66: error: '__EI_ftello' aliased to undefined symbol '__GI_ftello' make[3]: *** [/home/mlos/WORK/os/PACKAGES/glibc/WORK/BUILD/glibc-2.12-2-gc4ccff1/build-i686-linuxnptl/libio/ftello.os] Error 1 Has anyone else hit this issue? Any tips appreciated.

2 2

CentOS PaaS SIG meeting (2016-07-20)
by Troy Dawson 20 Jul '16

20 Jul '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 20 July 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms --- origin 1.2.1 released as a security update --- openshift-ansible-3.2.13 now installable from testing --- This one should have all the changes we need, will be testing to go to release -- Documentation -- Automated testing -- images / image building --- Working on getting Dockerfile.centos7 and .cccp files in origin ---- https://github.com/openshift/origin/pull/9864 - Open Floor

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel July 2016