devel June 2016

devel@lists.centos.org

42 participants
39 discussions

CentOS Atomic SIG meeting
by Jason Brooks 09 Jun '16

09 Jun '16

I'll be traveling during the time of this week's atomic SIG mtg. Unless someone else wants to run the meeting today, we can cancel this one. Jason

2 1

Adding new Imagefactory features to CBS
by Lalatendu Mohanty 09 Jun '16

09 Jun '16

Hi, The current version of Imagefactory [1] running with CentOS build system (CBS) is few versions behind upstream releases of Imagefactory [1] . Imagefactory recently added a new feature to build HyperV variant of Vagrant image and also has capability to build Vagrant box for VMware Fusion. I am confident that bringing these features to CBS will help the community in general. In case you are not aware about Imagefactory [1] , CBS uses it to do Vagrant box builds for CentOS and other projects e.g. Atomic Developer Bundle (ADB) in Atomic SIG. I am wondering how we can facilitate a process to bring upstream features of Imagefactory to CBS. One suggestion from Ian was that we should create a cbs-test setup similar to production CBS setup and use it to build confidence around the new features of Imagefactory and then move the feature to production. If you have better ideas you should speak now :) [1] https://github.com/redhat-imaging/imagefactory Thanks, Lala

3 3

No CentOS Paas SIG today
by Ari LiVigni 08 Jun '16

08 Jun '16

Hello, *No PaaS SIG sync-up meeting this week* Next meeting will be June 15th Time: 1700 UTC - Wedensdays Date: Today Wedensday, 8 June 2016 Where: IRC- Freenode - #centos-devel Last meeting minutes: https://www.centos.org/minutes/2016/may/centos-devel.2016-05-25-17.00.html -- -== @ri ==-

1 0

CBS kernel-debuginfo packages
by Wayne Betts 08 Jun '16

08 Jun '16

I'm not sure if this is an appropriate place for this question - please gently steer me to a better place if you think there is one. I have a machine using a kernel package from the CentOS Community Build System (specifically kernel-3.18.21-16.el6 from http://cbs.centos.org/koji/buildinfo?buildID=4757, but my question applies to other CBS kernel versions as well from what I can tell) The machine is crashing with some regularity on Sunday mornings. Looking at a kdump core dump might help narrow down the cause of the crashes. But the CBS kernel packages don't appear to include kernel-debuginfo packages, and the kernel.spec file appears to me (a non-expert for sure) to have had the necessary pieces removed, so I don't know how to rebuild from the srpm and get the debuginfo packages that way either. If someone could help me find or build the kernel-debuginfo package, it will be appreciated. Thank you,

2 5

New SCL packages for CentOS available for testing
by Honza Horak 06 Jun '16

06 Jun '16

RHSCL 2.2 was released recently [1] and this release includes several new collections: rh-mariadb101 rh-postgresql95 rh-maven33 rh-mongodb30upg rh-mongodb32 rh-python35 rh-nodejs4 rh-ruby23 rh-ror42 SRPMs were taken and rebuilt for CentOS users in cbs.centos.org by SCLo SIG group. The packages are now available in the testing repositories via: sudo yum install centos-release-scl sudo yum-config-manager --enable centos-sclo-rh-testing sudo yum install rh-mariadb101 They will be soon moved to mirrors, but in case there are some issues, let us know. Please, mind, that these packages are not meant to be used on RHEL. On RHEL you can acquire the packages as documented at [1]. [1] https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/… Regards, Honza

1 1

Update on CentOS Community Container Pipeline
by Bamacharan Kundu 06 Jun '16

06 Jun '16

Hi All, Update on recent work done for the CentOS Container Pipeline. - We noticed that some test runs would fail due to content not being available at the right time. We tracked this down to and fixed a race condition that caused container test stages to remove content while it is being used in delivery stage. This also fixed a problem where sometimes the notify email was not being sent out. - removing all artifacts on the builder nodes once the built containers are pushed out (or failed ), without this we were using up a lot of storage for content that would otherwise never be useful. We will try and come up with a smart process to catalog these before removing them ( either via cron or opportunity driven ) - Refresh the build configurations and templates for each build, so that it builds from scratch for each build. This ensures that no previously cached content or state can impact the present build, test and delivery run. - Due to the layers involved with openshift and how we implement the build, reporting cycle we've had issues with the emails that get sent out to the user to notify them of a success / fail state along with some details on what went wrong or where they can download the built images. We've done some work in this area to both improve the content that gets sent out and also to help ensure a better delivery rate ( we believe all the issues causing email delivery failures are now fixed, but we will continue to monitor ) Our immediate next focus is : - be able to demo some of the work we've been doing to the various SIGs in CentOS, to make sure we are doing the best possible work to solve their problems and support them in the best possible manner. - continue to work on closing off the minimal feature set allowing us to release / announce the service for the wider audiences. - develop a comprehensive life-cycle plan to audit and report on existing containers built in the pipeline. Regards Bamacharan -- Bamacharan Kundu IRC Nick- bamachrn

1 0

libmp (gmp) conflicts
by Antonio Trande 03 Jun '16

03 Jun '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, gmp-4.3.1-10.el6 provides these libraries: libgmp.so.3 -> libgmp.so.3.5.0 libgmp.so.3.5.0 libgmpxx.so.4 -> libgmpxx.so.4.1.0 libgmpxx.so.4.1.0 libmp.so.3 -> libmp.so.3.1.14 libmp.so.3.1.14 'libmp.so' from 'gmp' conflicts with same library provided by 'mp' package that I wish to include on Epel6 repositories. Is it reasonable for you splitting off libmp.so from 'gmp' in a sub-package ? - -- - --- Antonio Trande mailto: sagitter 'at' fedoraproject 'dot' org http://fedoraos.wordpress.com/ https://fedoraproject.org/wiki/User:Sagitter GPG Key: 0x6CE6D08A Check on https://keys.fedoraproject.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXT/TwAAoJELbsjn1s5tCKCA8IAKZnI1aKhyYEsrDAAZrOyhcv pu5ZBEBqvBxx16AiSsQtjNTF8ZjUz8Y4Ud2wmfZGp5YQr5KLdjiC/Ji4QTMPPWnQ 5fBK6l3WEK564Myxnr2XkC+JVGcqoVxYxpCbbormBPfbl1cVCoQ1TWYkT+jt9/EK GI0aRO7yucB8nWBt6E09Ge8leIFI9IjJPOgBxVmlIoi3uk9883nodpwQU6BK4/DO icnOJ9+S+uhF3bW097ppR0PblZ/Qr0GUYVG6nkzCZV4/V94AiLOAKghiIbJsjc5T 08VerkLqbfM+QdqeJ1Vqt+JP2DVcB+FP97xFiS5QbjRuVc6biucD49ysAIANyn4= =/CIR -----END PGP SIGNATURE-----

3 3

nfs bug - any info on bugzilla 1324635
by Jagga Soorma 02 Jun '16

02 Jun '16

Hi Guys, Anyone have any information on bugzilla 1324635. This seems like a private bug being tracked by redhat but is major and impacting us. Basically nfs gets impacted with large writes. Thanks!

1 0

[RFC] Operational tools SIG (was logging and monitoring...)
by Matthias Runge 01 Jun '16

01 Jun '16

Hello, I would like to re-iterate my interest in having a SIG in CentOS to provide all kinds of tools for operators providing infrastructure by using CentOS. The scope should be more than just simply packaging applications. Another part should be to provide puppet manifests or ansible playbooks to get things quicker up and running. Ideally, I would start with providing something like * elsasticsearch/fluentd/kibana for centralised logging * collectd/graphite/grafana for performance monitoring * sensu/uchiwa for availability monitoring We have already seen around 10 persons interested in helping, testing, trying out and providing feedback. For communcations etc. I would propose to start small, and to share already existent CentOS channels (email-lists, irc-channel). This decision should be revisited, once amount of SIG related communication becomes annoying in general channels. Questions? Thoughts? Additions? Best, Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

4 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2016