devel

devel@lists.centos.org

4 participants
4640 discussions

SIGs: Possibility to drop EOL content at 7.5 release time
by Anssi Johansson 23 Apr '18

23 Apr '18

Hi, this is not really my job, but I don't mind ruffling a few feathers if I need to. RHEL/CentOS 7.5 is probably around the corner. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org. Unless otherwise specified, any SIG content under 7.4 will be copied over to 7,5. I'd imagine that for example openstack-newton could be dropped because it went EOL in 2017-10-25. Is there some other content that could be dropped? If SIGs want to drop something at 7.5 release time, please let hughesjr know. Filing a bug would be one way to do that. Content can be removed either by directory name, or by individual package names. You should also communicate to your users in advance that the EOL packages will disappear, and if necessary, instruct them to migrate to a newer supported version. Having instructions for that procedure published somewhere would be nice. The old content under 7.4.1708, including any EOL content, will be archived to vault.centos.org, and that content will be available in the vault indefinitely. The 7.4.1708 directory on mirror.centos.org will be emptied some time after 7.5 is released. For reference and inspiration, here are some directories from mirror.centos.org, including both up-to-date content and potentially EOL content. SIG chairs should review the list to make sure these directories can be copied over to 7.5.18xx when that time comes. Making the decisions now would save a bit of time at 7.5 release time. cloud/x86_64/openstack-newton cloud/x86_64/openstack-ocata cloud/x86_64/openstack-pike cloud/x86_64/openstack-queens configmanagement/x86_64/yum4 dotnet nfv/x86_64/fdio nfv/x86_64/fdio/vpp nfv/x86_64/fdio/vpp/vpp-1710 opstools/x86_64/fluentd opstools/x86_64/logging opstools/x86_64/perfmon opstools/x86_64/sensu paas/x86_64/openshift-origin paas/x86_64/openshift-origin13 paas/x86_64/openshift-origin14 paas/x86_64/openshift-origin15 paas/x86_64/openshift-origin36 paas/x86_64/openshift-origin37 rt sclo/x86_64/rh/devassist09 sclo/x86_64/rh/devtoolset-3 sclo/x86_64/rh/devtoolset-4 sclo/x86_64/rh/devtoolset-6 sclo/x86_64/rh/devtoolset-7 sclo/x86_64/rh/git19 sclo/x86_64/rh/go-toolset-7 sclo/x86_64/rh/httpd24 sclo/x86_64/rh/llvm-toolset-7 sclo/x86_64/rh/mariadb55 sclo/x86_64/rh/maven30 sclo/x86_64/rh/mongodb24 sclo/x86_64/rh/mysql55 sclo/x86_64/rh/nginx16 sclo/x86_64/rh/nodejs010 sclo/x86_64/rh/passenger40 sclo/x86_64/rh/perl516 sclo/x86_64/rh/php54 sclo/x86_64/rh/php55 sclo/x86_64/rh/postgresql92 sclo/x86_64/rh/python27 sclo/x86_64/rh/python33 sclo/x86_64/rh/python34 sclo/x86_64/rh/rh-eclipse46 sclo/x86_64/rh/rh-git29 sclo/x86_64/rh/rh-java-common sclo/x86_64/rh/rh-mariadb100 sclo/x86_64/rh/rh-mariadb101 sclo/x86_64/rh/rh-mariadb102 sclo/x86_64/rh/rh-maven33 sclo/x86_64/rh/rh-maven35 sclo/x86_64/rh/rh-mongodb26 sclo/x86_64/rh/rh-mongodb30upg sclo/x86_64/rh/rh-mongodb32 sclo/x86_64/rh/rh-mongodb34 sclo/x86_64/rh/rh-mysql56 sclo/x86_64/rh/rh-mysql57 sclo/x86_64/rh/rh-nginx110 sclo/x86_64/rh/rh-nginx112 sclo/x86_64/rh/rh-nginx18 sclo/x86_64/rh/rh-nodejs4 sclo/x86_64/rh/rh-nodejs6 sclo/x86_64/rh/rh-nodejs8 sclo/x86_64/rh/rh-perl520 sclo/x86_64/rh/rh-perl524 sclo/x86_64/rh/rh-php56 sclo/x86_64/rh/rh-php70 sclo/x86_64/rh/rh-php71 sclo/x86_64/rh/rh-postgresql94 sclo/x86_64/rh/rh-postgresql95 sclo/x86_64/rh/rh-postgresql96 sclo/x86_64/rh/rh-python35 sclo/x86_64/rh/rh-python36 sclo/x86_64/rh/rh-redis32 sclo/x86_64/rh/rh-ror42 sclo/x86_64/rh/rh-ror50 sclo/x86_64/rh/rh-ruby23 sclo/x86_64/rh/rh-ruby24 sclo/x86_64/rh/rh-scala210 sclo/x86_64/rh/rh-thermostat16 sclo/x86_64/rh/rh-varnish4 sclo/x86_64/rh/ror40 sclo/x86_64/rh/ror41 sclo/x86_64/rh/ruby193 sclo/x86_64/rh/ruby200 sclo/x86_64/rh/ruby22 sclo/x86_64/rh/rust-toolset-7 sclo/x86_64/rh/thermostat1 sclo/x86_64/rh/v8314 sclo/x86_64/sclo/sclo-git212 sclo/x86_64/sclo/sclo-git25 sclo/x86_64/sclo/sclo-httpd24more sclo/x86_64/sclo/sclo-php54 sclo/x86_64/sclo/sclo-php55 sclo/x86_64/sclo/sclo-php56 sclo/x86_64/sclo/sclo-php70 sclo/x86_64/sclo/sclo-php71 sclo/x86_64/sclo/sclo-python27 sclo/x86_64/sclo/sclo-python34 sclo/x86_64/sclo/sclo-python35 sclo/x86_64/sclo/sclo-ror42 sclo/x86_64/sclo/sclo-subversion19 sclo/x86_64/sclo/vagrant1 storage/x86_64/ceph-hammer storage/x86_64/ceph-jewel storage/x86_64/ceph-luminous storage/x86_64/gluster-3.6 storage/x86_64/gluster-3.7 storage/x86_64/gluster-3.8 storage/x86_64/gluster-3.9 storage/x86_64/gluster-3.10 storage/x86_64/gluster-3.12 storage/x86_64/gluster-3.13 storage/x86_64/gluster-4.0 virt/x86_64/kubernetes19 virt/x86_64/kvm-common virt/x86_64/libvirt-latest virt/x86_64/ovirt-4.1 virt/x86_64/ovirt-4.2 virt/x86_64/xen-46 virt/x86_64/xen-48

9 8

CentOS PaaS SIG meeting (2018-04-18)
by Troy Dawson 18 Apr '18

18 Apr '18

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 18 April 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- automation - Training for new committee members -- How to get packages into repo's -- How to create tags, build targets, and repo's - New time for weekly meeting - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2018/April/centos-devel.2018-04-04-17.00.log…

1 0

Proposal : potential "freeze" for SIG content to be built and/or pushed to mirrors
by Fabian Arrotin 17 Apr '18

17 Apr '18

Hi, As you're all aware, RHEL 7.5 was released yesterday, and at the CentOS side, the massive rebuild started for all arches (x86_64, i386, ppc64, ppc64le, aarch64 and armhfp). We'd like to have your opinion about the following proposal (TBD) : - we freeze the signing process for now, while we have focus on the distro rebuild. - we can also eventually freeze the CBS builders, so that all SIGs are now waiting for 7.5.1804 content to be available in CBS/koji and so rebuild against those pkgs We hope (but can't have any estimate) that for this release, all arches should be in "sync", so normally content should be available faster (in comparison with 7.4.1708 release) to CBS/Koji builders. Of course that's just a discussion, so feel free to comment. For example, we can also think about security issues for rpm packages built through koji that would need to be ASAP available on mirror.centos.org, and that wouldn't need to be built for/against 7.5.1804. Please comment on this. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

3 2

[SIG Process] Point-Release Freeze of SIG Content while CR is Active
by Brian Stinson 17 Apr '18

17 Apr '18

Hi Folks, At the CBS meeting yesterday we discussed a proposal to freeze the Sign and Push-to-mirror processes during the period between when CR is active and a point release. https://lists.centos.org/pipermail/centos-devel/2018-April/016610.html You may recall that we did something similar for 7.1708 We need to Freeze because we make CR content available in CBS for builds, and in CI for testing purposes. But, releasing content built against CR to mirror.centos.org would have had some unintended consequences (e.g. we don't want to require that end-users enable CR to get content from the SIGs). The Point-release Freeze does not affect content moving from the testing tags in CBS to buildlogs.c.o, that will continue to show up as it is built. Do note: since we do want to give testers and developers an opportunity to build and test against an upcoming point-release before it goes GA, content coming from buildlogs.centos.org may require enabling the CR repo. Any new requests for sign+push (adding new tags to mirror.c.o) during Point-release Freeze will be held until the point release goes GA. We approved this as part of the CR checklist during the meeting yesterday, and will include another note about this in the CR release announcement. https://www.centos.org/minutes/2018/April/centos-devel.2018-04-16-14.00.html If there are any questions, please let us know and discuss here on the list. Cheers! -- Brian Stinson

1 0

[ppc64le][rdo][tripleo] Building Power containers for TripleO
by Michael Turek 16 Apr '18

16 Apr '18

Hello all, I brought this up at this last month at an RDO meeting [0] and again this week [1] where we decided this topic might be best suited for centos-devel. The short of it is that we want to start building containers for tripleo in the community. We discussed this at PTG and it seems feasible. Basically the goal is to enable the tripleo job pipeline that builds the containers and uploads them to docker hub set up for ppc64le.[2] From the IRC chat it seems like the first step is to identify the hardware where we could do this. Can anyone shed some light on this? If you need more info, let me know! We're really looking forward to getting this going! Thanks, Mike Turek [0] http://eavesdrop.openstack.org/irclogs/%23rdo/%23rdo.2018-03-14.log.html#t2… [1] http://eavesdrop.openstack.org/irclogs/%23rdo/%23rdo.2018-04-11.log.html#t2… [2] https://review.rdoproject.org/jenkins/job/periodic-tripleo-centos-7-master-… <http://eavesdrop.openstack.org/irclogs/%23rdo/%23rdo.2018-03-14.log.html#t2…> <http://eavesdrop.openstack.org/irclogs/%23rdo/%23rdo.2018-03-14.log.html#t2…>

1 0

Centos 7.5 query
by Thomas F Herbert 16 Apr '18

16 Apr '18

What is the outlook for Centos 7.5? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*

1 0

[NFV SIG] [Cloud SIG] Pushing sources back to Centos from RHEL
by Thomas F Herbert 16 Apr '18

16 Apr '18

Even though I am NFV SIG chair, I am still learning. We have a package, fd.io/vpp that is in the NFV SIG may eventually be part of RHEL. As part of the planning process RHEL RCM is asking for the URL to push packages back to Centos. What URL or mechanism does RHEL use to push sources to Centos? Do they use cbs? Does this happen by way of the CentOS git? Do we need a CentOS git account for NFV SIG? How do you handle this in Cloud SIG? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*

2 2

CentOS Origin packages in testing for 3.7, 3.8 and 3.9
by Troy Dawson 13 Apr '18

13 Apr '18

We have origin packages for 3.7.2, 3.8.0 and 3.9.0. We also have the corresponding openshift-ansible packages. They have been put in our testing repos. DO NOT USE ORIGIN 3.8.0, IT IS FOR UPGRADE PURPOSES ONLY These will not be released until *someone* has tested them. So please, someone, anyone, test them, and let us know. origin 3.9 testing https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ origin-3.9.0-1.el7.git.0.ba7faec openshift-ansible-3.9.0-0.53.0.git.1.af49d87.el7 origin 3.8 testing https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin38/ origin-3.8.0-1.el7.git.0.dd1558c openshift-ansible-3.8.37-1.git.1.151d57f.el7 origin 3.7 testing https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ origin-3.7.2-1.el7.git.0.cd74924 openshift-ansible-3.7.43-1.git.1.ed51ddd.el7 Once again, test and let us know. If you don't know who to send it to, just reply to this email. Thanks Paas Sig Group

3 6

registry.centos.org is down due to maintenance window from the infra side
by Bamacharan Kundu 13 Apr '18

13 Apr '18

Hi All, There is maintenance window going on from the infra side, so registry.centos.org is not available for some time. Impact: users will not be able to pull images from registry.centos.org. Resolution time: will update on resolution We are sorry for the inconvenience caused, will keep you posted. Regards Bamacharan Kundu

1 1

To enquire about the expected arrival of ntp, ntpdate, expat&libxml2 rpms with CVE fix
by Veetil, Vyshnav 12 Apr '18

12 Apr '18

Hi All, Can you please tell me the expected release of these rpms which is having the fix for below CVE's. 1. expat rpm: CVE-2017-9233 2.libxml2: CVE-2015-8035 3. ntp and ntpdate RPM: CVE-2017-6462 CVE-2018-7170 CVE-2018-7170 CVE-2016-4954 CVE-2016-4955 CVE-2016-4956

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel