devel April 2017

devel@lists.centos.org

26 participants
26 discussions

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

Request for feedback: CentOS-Atomic container
by Karanbir Singh 25 Sep '17

25 Sep '17

hi Alpha2: registry.centos.org/kbsingh/centos-atomic:7-alpha2 The CentOS Atomic Container is a minimal ( 30MB on disk ) image that can be used to host static content, and small footprint content that does not need the entire CentOS Linux Base image. This is also not meant to replace CentOS Linux Base image as the default, we want to make it available as an additional container base for apps that find it useful. The main highlight is that it does not contain yum, but has microdnf. I am looking for feedback, and some wider testing as well as recommendations on howto further reduce size, before we move to release. You can consume this as : docker run -t -i \ registry.centos.org/kbsingh/centos-atomic:7-alpha2 \ /bin/bash regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 4

NFV SIG - update
by Dave Neary 30 May '17

30 May '17

Hi, There has been a recent resurgence of interest in the NFV SIG, and in the interest of keeping the momentum going, I would like to step aside as SIG char, and recommend that Tom Herbert take over. Tom has taken on the packaging and building of VPP and DPDK-accelerated OVS for OPNFV, and has been active in the SIG in recent weeks, and I think he will help add the structure that has been sorely lacking from me in recent months. I'm not sure what the process is for replacing a SIG chair - can someone let us know, please? Thanks, Dave. -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338

4 4

CentOS 7 extras for alternative arches and Koji workflow.
by Thomas Oulevey 18 May '17

18 May '17

Dear All, I'd like to retake a pending issue with -extras on c7 and ask for feedback. I wear two hats : 1/ User, who would like to use altarch-extras packages soon after they are available in c7-extras. 2/ CBS maintainer, who would like to provide his users consistent buildroot across all architecture. Let's start with 1/. The important point here is to be able to rely on altarch-extras and expect it to be in sync with c7-extras in a reasonable time. (days not weeks) As it was always stated c7 (all repositories) cannot and should not be blocked by any alt-arch rebuild and should be independent. However we should at least try to provide these alt-arches packages in a timely manner. A lot of coordination (and motivated contributors) is needed if this effort is not centralized. For 2/ it is very important that we build package with similar buildroots on all arches. As c7-extras is now enabled for everybody, we should be able to have the altarch equivalent in a timely manner. Also all SIGs who are building for all alt-arches will be blocked in case an extras package is needed in the buildroot (we dealt with these issues during 7.2 -> 7.3 cycle and it will come back at next minor release. Additional challenge is the -cr repository which is enabled in CBS by default) However I understand, we need a way not to block official c7 arches for other arches that need fixes. After reviewing the possibilities with different people last year, one way to tackle this issue, would be to have 2 targets in Koji ; 1 including official arches and the other including official arches + alt-arches and allow SIG to bypass alt-arches by changing one target in their config. In this config we could move easily an altarch to an official one and vice versa. Finally, in my opinion, an easy way to have consistent altarch-extras would be to monitor official repository on the mirror.c.o (or buildlogs.c.o) and rebuild automatically extras packages in Koji, which would be picked by a script and so all altarch-extras would be generated directly by Koji itself and the process pretty much automated. The signing process will still be the key to control what is pushed to buildlogs/mirrors. (and close to what we already do) I don't see many disadvantages for this solution but I would like to know if it is possible to move forward and what the community and core contributors think about it. Is altarch-extras important to you ? thank you for your feedback, -- Thomas Oulevey

7 11

[storage] Ceph Jewel 10.2.7 now tagged for -testing
by David Moreau Simard 11 May '17

11 May '17

Hi, Please take note that Ceph Jewel 10.2.7 has been tagged for testing after a successful smoke test of an initial build. It should land on the buildlogs CDN shortly. Ceph Jewel in the stable release repository is currently at 10.2.5 since 10.2.6 had not been built. You can find the release notes for the new versions upstream: - 10.2.6 (March 8th): http://ceph.com/releases/v10-2-6-jewel-released/ - 10.2.7 (April 10th): http://ceph.com/releases/v10-2-7-jewel-released/ The Ceph storage SIG rebuilds straight from upstream source RPMs found here [1]. We version spec file differences on GitHub [2] for information purposes only. You can test this new version with the centos-release-ceph-jewel package, like so: === yum -y install centos-release-ceph-jewel yum-config-manager --enable centos-ceph-jewel-test yum -y install ceph === This will remain in -testing until at least April 24th, after which it will be tagged for release if no problems are reported. Thanks, [1]: http://download.ceph.com/rpm-jewel/ [2]: https://github.com/CentOS-Storage-SIG/ceph David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter]

2 5

We need a newer Vagrant in SCL
by Laurentiu Pancescu 02 May '17

02 May '17

Hello, Our cico test for testing our Vagrant images have support for optionally using vagrant-vbguest. This is now failing with: + scl enable sclo-vagrant1 'vagrant plugin install vagrant-vbguest' Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is: Authentication is required for http://gems.hashicorp.com/. Please supply credentials for this source. You can do this by running: bundle config http://gems.hashicorp.com/ username:password Build step 'Execute shell' marked build as failure I think this is caused by the older version we have in SCL - I can install vagrant-vbguest without any issues on Vagrant 1.9.3 (on OS X). I now reverted the test to not use vagrant-vbguest, but it's still failing because SCL Vagrant doesn't support VirtualBox 5.1.x. Oracle already put a warning on the download page for VirtualBox 5.0.x: "VirtualBox 5.0.x runs out of support, switch to VirtualBox 5.1.x!" https://www.virtualbox.org/wiki/Download_Old_Builds_5_0 We risk becoming unable to automatically test our images with VirtualBox - could we get a Vagrant update in SCL, please? Thanks, Laurentiu

3 4

SIG Proposal - High performance computing (HPC) SIG
by Ondřej Vašík 01 May '17

01 May '17

Hi, I would like to propose start of High performance computing (HPC) SIG. I see it already mentioned on https://wiki.centos.org/SpecialInterestGroup among Future SIGs. Primary reason for the SIG existence will be to improve the state of High performance computing related packages on CentOS and similar distributions, with special focus on stability of builds, CentOS (and similar distribution) related improvements for OpenHPC project and getting new HPC packages packaged for CentOS and/or Fedora. Initial members would be me (ovasik(a)redhat.com, CentOS FAS account: Reset), Adrian Reber (areber(a)redhat.com, CentOS FAS account: areber), Stanislav Kozina (skozina(a)redhat.com, CentOS FAS account: ersin) and Jan Chaloupka (jchaloup(a)fedoraproject.org, CentOS FAS account: jchaloup). Of course, anyone is welcome to join. Thanks in advance for approving/sponsoring the SIG. Regards, Ondrej Vasik

7 9

GA Release: CentOS Community Container Pipeline
by Bamacharan Kundu 28 Apr '17

28 Apr '17

Hi All, We would like to welcome and introduce you all to the CentOS Community Container Pipeline Service[1][4]. This is an effort to make the developer's life simple for containerizing open source projects, where the developer can develop applications on a stack (django, golang, nodejs, redis, rabbitmq, etc.) of his/her choice using CentOS as the base platform. For every open source project building their container images using CentOS Community Container Pipeline, the service ensures that the application is packaged into a container and updated automatically every time changes are pushed to the Git (GitHub, BitBucket, Gitlab, etc.) repository. The resulting container image is scanned for updates, fixes, capabilities, and delivered to registry.centos.org[3]. From there anyone can pull it and run the application. Pipeline service rebuilds and image when an RPM package is updated in the container or base image is updated. For using the service to build the images please raise a PR in container-index [2] All the currently available images at registry.centos.org are updated at Container Pipeline Wiki[3] We're always looking for ideas and improvements for the service. If you're interested in contributing to this repository, here[1] is the source code for the service. For any queries get in touch with us on #centos-devel IRC channel on Freenode or send a mail to centos-devel(a)centos.org. Regards Bama Charan Kundu [1] https://github.com/CentOS/container-pipeline-service [2] https://github.com/centos/container-index [3] https://wiki.centos.org/ContainerPipeline [4] http://www.rtnpro.com/centos-community-container-pipeline/

2 1

The status of our Vagrant images for Hyper-V
by Laurentiu Pancescu 26 Apr '17

26 Apr '17

Hi there, I created the first experimental Vagrant images for Hyper-V on March 14, after the CBS upgrade. They seem to be functional, but they generate a lot of disk I/O during "vagrant up", according to Thomas and Michael. I think we end up with 40GB files as disk images - this is the maximum size of the virtual hard drives we create, but most of that is empty. I compared the contents of our box file to the one from kozo/centos-7, which is produced natively using Packer and Hyper-V: our image contains a real 40GB disk image, while the kozo image only has a 2.1GB image. Image Factory converts the KVM .qcow2 image to a .vhd by calling "qemu-img convert -O vpc <source> <destination>". This produces a 40GB sparse file taking just 1.1GB of space (both with the fixed and dynamic subformats). The problem occurs while packing the sparse image into the .box file: Python's tarfile module only has read-only support for sparse files (a GNU tar extension) - even in Python 3, so the archive ends up with a regular 40GB file. Creating 40GB sparse files seems to be specific to qemu-img: "VBoxManage convertmedium disk box.vmdk box.vhd" produces a 1.1GB regular file (VirtualBox' convert tool doesn't seem to support QCOW2, so I had to first convert the QCOW2 image to VMDK). We should probably either: - call GNU tar from Image Factory to preserve the sparseness of our image files (and hope that Windows handles them properly) - use VBoxManage to convert to .vhd (VirtualBox is not in our repos, but Oracle offers a .rpm for EL7 systems). In the mean time, we will probably release v1703 without Hyper-V support, since CentOS Linux 6.9 was already released. Best regards, Laurențiu [vagrant@localhost ~]$ tar -tvzf c7.box # that's ours drwxr-xr-x root/root 0 2017-03-14 11:23 Virtual Machines/ -rw-r--r-- root/root 39100 2017-03-14 11:23 Virtual Machines/vm.XML -rw-r--r-- root/root 114 2017-03-14 11:23 Vagrantfile drwxr-xr-x root/root 0 2017-03-14 11:22 Virtual Hard Disks/ -rwxr-xr-x root/root 42949672960 2017-03-14 11:23 Virtual Hard Disks/disk.vhd -rw-r--r-- root/root 22 2017-03-14 11:23 metadata.json [vagrant@localhost ~]$ unzip -l hyperv.box # kozo/centos-7 Archive: hyperv.box.zip Length Date Time Name --------- ---------- ----- ---- 36898 02-25-2017 13:05 Virtual Machines/1BF518E8-0055-4ABF-8750-E1D703B23A47.vmcx 61440 02-25-2017 13:05 Virtual Machines/1BF518E8-0055-4ABF-8750-E1D703B23A47.VMRS 64 02-25-2017 12:47 metadata.json 2185232384 02-25-2017 13:05 Virtual Hard Disks/CentOS7.vhdx --------- ------- 2185330786 4 files

4 7

CentOS PaaS SIG meeting (2017-04-26)
by Troy Dawson 26 Apr '17

26 Apr '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 26 April 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing and Automated rpm building -- Images and Image building -- Multi-arch -- separate repo work -- minishift - Open Floor

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel April 2017