devel February 2016

devel@lists.centos.org

48 participants
48 discussions

[altarch] multiarch docker images
by Manfred Touron 08 Feb '16

08 Feb '16

Hi everyone, I'm working at Scaleway on the multiarch images system, I'm @moul on IRC and talked with @Arrfab and @Evolution (thanks a lot, guys). --- Context: Today, we are using Docker as a build-step to generate our baremetal servers rootfs, what we call, the "Scaleway images". Here is an example of "1 click app" image: - Public Hub: https://hub.scaleway.com/wordpress.html - DevHub (aggregate APIs): http://devhub.scaleway.com/#/images/wordpress:latest - Source (GitHub): https://github.com/scaleway-community/scaleway-wordpress/ - Docker Hub: https://hub.docker.com/r/scaleway/wordpress/ - Build logs: https://travis-ci.org/scaleway/qa/builds/98515979 We are quite happy today with this method and are succesfully running plenty Linux distributions (Ubuntu, openSUSE, Gentoo, Fedora, Debian, Arch Linux and Alpine Linux). Actually we also have a proof-of-concept of CentOS image, but based on an old development CubieTruck snapshot with no public mirrors. Here is how I built this POC image (I wasn't aware of virt-tar-out): https://github.com/armbuild/centos-img/blob/master/buildcontainers.sh --- We will soon release new server models with new architectures, our next priorities are: `arm64` and `x86_64`, but we plan to support more architectures if we feel enough people will need it so the development worth it. I started to work on "multiarch" images (one image per architecture). Here are some images: - https://github.com/multiarch/alpine -> built with `apk-static` in a chroot - https://github.com/multiarch/busybox -> static binaries extracted from latest busybox-static.deb - https://github.com/multiarch/ubuntu-debootstrap -> qemu-debootstrap - https://github.com/multiarch/debian-debootstrap -> same as above - https://github.com/multiarch/ubuntu-core -> based on released rootfs tarballs at https://partner-images.canonical.com/core/wily/current/ All those images also contains an `x86_64` `qemu-${ARCH}-static` so you can run them on an `x86_64` host with `binfmt-support` available. Look at the README.md files for usage and examples. I began to work on the Centos image https://github.com/multiarch/centos, I successfully built the `armhf` and `arm64` images by `virt-tar-out`ing the CubieTruck released image, i.e.: http://mirror.centos.org/altarch/7.2.1511/isos/armhfp/ I also successfully built the `x86_64` and `i386` images using kickstart: livemedia-creator --arch=i386 --make-disk \ --iso=/tmp/boot7-i386.iso \ --ks=$(pwd)/centos-7.ks \ --image-name=centos-7-base-i386 based on https://github.com/CentOS/sig-cloud-instance-build/tree/livemedia_builds/do… For now I failed to build the `ppc64` nor `ppc64le` images, but that's not a priority. I have now an issue, my `armhf` and `x86_64` images are not the same, the ones based on real boards .img.xz embed about 300M of kernel images, dtb, kernel modules, firmware (I don't want them) + a lot more apps that we can find by default in the <200Mb `x86_64` Docker image. I would like to find a solution to build "same" images for all the targets and avoid as much as possible the need of diffing the outputs of `yum list installed`. My favorite solution would be to use kickstart files, which are very cool to put on GitHub. But the non `x86_64` architectures lack of a `boot.iso` file packing `isolinux`. Is it possible to add those `boot.iso` files on the mirror or tell me how to build them ? Do you see alternative ways to build identical images ? -- Manfred Touron - @moul CTO @ scaleway.com

7 16

NO CBS/Infra Meeting 08-Feb-2016
by Brian Stinson 08 Feb '16

08 Feb '16

Hi Folks, I know some of us (myself included) are traveling or recovering from the Dojo -> FOSDEM -> cfgmgmt -> Devconf marathon, so let's cancel this week's meeting. I'll send out a list of open action items here to the list sometime between airplanes tomorrow. Cheers! --Brian

1 0

release process for SIGs
by François Cami 07 Feb '16

07 Feb '16

Hi, I'd like the centos-release-ceph-hammer rpm to be included in the extras (1) repository like the other centos-release-* packages. First things first: some of these centos-release* packages are tagged el7.centos and others el7. Niels told me el7.centos was the right tag and since this matches the build target name (core7-extras-common-el7.centos), el7.centos seems like the right target. Could I get confirmation that I should use el7.centos for centos-release-ceph-*? Then, the main problem is that packages in the extras repository should be built against core7-extras-common-el7.centos but I cannot use that build target (2). Is there an accepted way of doing this? Thanks, François (1) http://mirror.centos.org/centos-7/7.2.1511/extras/x86_64/Packages/ (2) "ActionNotAllowed: tag requires build-core permission" http://cbs.centos.org/koji/taskinfo?taskID=66398

2 1

Code review platform
by Julien Pivotto 06 Feb '16

06 Feb '16

Hi all, For my project of SIG, I would be interested to get some kind of code-review tool. It would be great to be able to review the contributions before they get accepted. Also, we could hook that into cbs and/or public ci. I have no preference regarding the tool, even if several projects I use are using gerrit. Do you think that the CentOS platform could welcome such a tool? We could imagine that we limit its scope at the beginning, then we extend that to any SIG/CentOS project that wants that. -- (o- Julien Pivotto //\ Open-Source Consultant V_/_ Inuits - https://www.inuits.eu

2 1

missing updates for CentOS6
by Jacco Ligthart 05 Feb '16

05 Feb '16

Hi All, I've been busy building updated RH packages for armv5tel (http://www.redsleeve.org/) During that process I often use repodiff to check if there are updates. And I also use repodiff to the CentOS repos. (of you didn't build it it's often also of no use to me :) ) this time around I noticed that CentOS6 was missing a couple of updates. So here a modified output of repodiff. repodiff -o ftp://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/ -n http://vault.centos.org/6.7/os/Source/ -n http://vault.centos.org/6.7/updates/Source/ --downgrade --simple Downgraded Packages: cups-pk-helper: cups-pk-helper-0.0.4-13.el6 -> cups-pk-helper-0.0.4-12.el6 dvd+rw-tools: dvd+rw-tools-7.1-7.el6 -> dvd+rw-tools-7.1-6.el6 environment-modules: environment-modules-3.2.10-3.el6 -> environment-modules-3.2.10-2.el6 findutils: findutils-4.4.2-8.el6 -> findutils-4.4.2-6.el6 freeipmi: freeipmi-1.2.1-7.el6 -> freeipmi-1.2.1-6.el6_5 gedit: gedit-2.28.4-4.el6 -> gedit-2.28.4-3.el6 ibus: ibus-1.3.4-9.el6 -> ibus-1.3.4-8.el6 libcanberra: libcanberra-0.22-3.el6 -> libcanberra-0.22-1.el6.centos libipathverbs: libipathverbs-1.3-3.el6_5 -> libipathverbs-1.3-3.el6 logwatch: logwatch-7.3.6-54.el6 -> logwatch-7.3.6-52.el6 pango: pango-1.28.1-11.el6 -> pango-1.28.1-10.el6 paps: paps-0.6.8-13.el6.3 -> paps-0.6.8-13.el6.2 passwd: passwd-0.77-7.el6 -> passwd-0.77-4.el6_2.2 perl-LDAP: perl-LDAP-0.40-2.el6 -> perl-LDAP-0.40-1.el6 pulseaudio: pulseaudio-0.9.21-24.el6 -> pulseaudio-0.9.21-21.el6 unzip: unzip-6.0-4.el6 -> unzip-6.0-2.el6_6 urw-fonts: urw-fonts-2.4-11.el6 -> urw-fonts-2.4-10.el6 watchdog: watchdog-5.6-5.el6 -> watchdog-5.6-4.el6_6 wget: wget-1.12-8.el6 -> wget-1.12-5.el6_6.1 Jacco

2 3

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2016