devel May 2019

devel@lists.centos.org

34 participants
24 discussions

[Meeting] RDO meeting (2019-05-08) minutes
by Javier Pena 08 May '19

08 May '19

----- Forwarded Message ----- ============================== #rdo: RDO meeting - 2019-05-08 ============================== Meeting started by jpena at 15:00:31 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_05_08/2019/rdo_m… . Meeting summary --------------- * roll call (jpena, 15:00:36) * request to update to puppet 6 in RDO:- https://trello.com/c/isJkCzYZ (jpena, 15:05:29) * LINK: https://etherpad.openstack.org/p/RDO-Meeting (fultonj, 15:05:45) * puppet 6 will need to wait until centos 8 is available, can do some pre-work in Fedora (jpena, 15:06:43) * ACTION: ykarel to propose pr to update puppet in fedora (amoralej, 15:16:56) * ACTION: amoralej to update puppet in fedora stabilized repo once is built in fedora (amoralej, 15:17:19) * ceph/ansible post-update follow up (jpena, 15:18:33) * ppc64le container uploads (jpena, 15:30:30) * LINK: https://ci.centos.org/job/tripleo-upstream-containers-build-master-ppc64le/… ? (amoralej, 15:32:03) * LINK: https://centos.logs.rdoproject.org/tripleo-upstream-containers-build-master… is the most recent build log, for example (baha, 15:33:03) * LINK: https://trunk.rdoproject.org/centos7-master/deps/latest/ (ykarel, 15:37:52) * ACTION: jpena to check potential alternatives for the RDO registry (jpena, 16:15:44) * chair for the next meeting (jpena, 16:17:17) Meeting ended at 16:18:41 UTC. Action items, by person ----------------------- * amoralej * amoralej to update puppet in fedora stabilized repo once is built in fedora * jpena * jpena to check potential alternatives for the RDO registry * ykarel * ykarel to propose pr to update puppet in fedora People present (lines said) --------------------------- * amoralej (57) * jpena (52) * ykarel (32) * tonyb (19) * fultonj (18) * weshay (18) * mwhahaha (15) * baha (14) * fmount (7) * openstack (7) * Vorrtex (4) * rdogerrit (3) Generated by `MeetBot`_ 0.1.4 _______________________________________________ dev mailing list dev(a)lists.rdoproject.org http://lists.rdoproject.org/mailman/listinfo/dev To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org

1 0

Installing kernel 4.14.34 through kickstart
by Far Had 06 May '19

06 May '19

Hi, Trying to compile and put kernel 4.14.34 into the CentOS 7 (1511 release) DVD with a ks.cfg already configured. This ks DVD has been working fine with the original 3.10 kernel. Here is what I did: I built rpm packages of the 4.14.34 kernel with disabled kernel debugging option. This gave me 3 rpm files: kernel, kernel-header and kernel devel. I replaced them with their equivalents in isolinux/packages directory in the DVD ISO image and made a new ISO file out of it. when booting from this image, automatic installation fails after installing all packages in the post installation at "generating initramfs" phase. The exact error text is: "No such file or directory" (image attached) Regards.

1 0

May SIG reports
by Rich Bowen 01 May '19

01 May '19

In case you have not seen the reminders that I've sent out, we're coming up on the time for the May SIG reports. As documented at https://wiki.centos.org/SpecialInterestGroup we expect reports from SIGs in Group 2: * Alt Arch * Cloud * NFV * Promo * Storage Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

2 1

IRC Meeting Changes
by John R. Dennison 01 May '19

01 May '19

For the past few years the CentOS Project has been holding IRC meetings for our various Special Interest Groups (SIGs) and other projects in the #centos-devel channel on the freenode IRC network. This has, for the most part, worked out fairly well. However, as this is a shared channel, at times things can become a bit hectic and confusing as people occasionally interrupt a meeting in progress. Not only does this break the flow of the meeting but it also injects noise into the logs that the project maintains for historical reference. This policy was also different from most other projects which have a dedicated "meetings" channel to be used for these purposes. In order to address the issue the project has made the decision to transition meetings to the #centos-meeting channel. This is a dedicated channel to be used solely for meetings. We feel this will help alleviate any potential issues with interruptions and other distractions. This channel is managed by the same group of people, our IRC Ops Team, as is #centos-devel and our channel bots are present to help as necessary. An additional bonus of this transition will be that the meeting bot (centbot) responsible for meeting oversight and logging will now be able to set the channel topic to reflect meeting status. This was not previously possible due to policy as we did not want to have the bot op'd unless absolutely necessary in a shared channel. We are planning this transition for June 1st in order to give the stakeholders involved ample time to alert their communities of the change and to ensure we have made the necessary changes on our end to ensure a smooth transition for people who access the logs via the https://www.centos.org/minutes/ interface. Any questions regarding this transition should be addressed either via the centos-devel mailing list or on the #centos-devel IRC channel on freenode. Additionally people can reach out to me personally on IRC (Bahhumbug on freenode) or via email if they have questions or concerns regarding this or other CentOS IRC matters. Thanks and see you in #centos-meeting :) -- The most valuable thing you can make is a mistake - you can't learn anything from being perfect. -- Adam Osborne (1939-2003), American entrepreneur

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel May 2019