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
On 04/04/18 20:20, Anssi Johansson wrote:
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.
Actually, for security purposes, I'd say we should do the opposite - only carry over content from 7.4 that is explicitly requested by the SIGs. That way we do not bring over stuff that has been forgotten about and no-one looks after. This way, only content that is claimed by active SIGs and maintained by them will get brought across and old forgotten, unmaintained content will get removed.
Trevor
On Wed, Apr 04, 2018 at 10:44:18PM +0100, Trevor Hemsley wrote:
Actually, for security purposes, I'd say we should do the opposite - only carry over content from 7.4 that is explicitly requested by the SIGs. That way we do not bring over stuff that has been forgotten about and no-one looks after. This way, only content that is claimed by active SIGs and maintained by them will get brought across and old forgotten, unmaintained content will get removed.
+1
John
On 04/05/2018 02:25 AM, John R. Dennison wrote:
On Wed, Apr 04, 2018 at 10:44:18PM +0100, Trevor Hemsley wrote:
Actually, for security purposes, I'd say we should do the opposite - only carry over content from 7.4 that is explicitly requested by the SIGs. That way we do not bring over stuff that has been forgotten about and no-one looks after. This way, only content that is claimed by active SIGs and maintained by them will get brought across and old forgotten, unmaintained content will get removed.
How do the SIGs go about making this request?
+1
John
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
2018-04-04 21:20 GMT+02:00 Anssi Johansson avij@centosproject.org:
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
Please keep opstools/* in 7.5, needed by oVirt project
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
Please keep sclo/x86_64/rh/rh-postgresql95 in 7.5, needed by oVirt project
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
Please keep storage/x86_64/gluster-3.12, needed by oVirt project
storage/x86_64/gluster-3.13 storage/x86_64/gluster-4.0
Please keep storage/x86_64/gluster-4.0, needed by oVirt project
virt/x86_64/kubernetes19 virt/x86_64/kvm-common
Please keep virt/x86_64/kvm-common, needed by oVirt project
virt/x86_64/libvirt-latest virt/x86_64/ovirt-4.1
virt/x86_64/ovirt-4.1 can be dropped in 7.5 since latest version, 4.1.9, is not compatible with 7.5 content and 4.1 reached EOL.
virt/x86_64/ovirt-4.2
Please keep virt/x86_64/ovirt-4.2, needed by oVirt project
virt/x86_64/xen-46 virt/x86_64/xen-48 _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Apr 04, 2018 at 10:20:34PM +0300, Anssi Johansson wrote:
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.
I'll chime in for the Gluster repositories from the Storage SIG. The Ceph repositories are mostly maintained by others, and I dont know which are actively used.
These repositories still get regulary updates:
storage/x86_64/gluster-3.10 storage/x86_64/gluster-3.12 storage/x86_64/gluster-4.0
These versions are EOL and can be removed:
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.13
With the removal of the repositories, the matching centos-release-gluster36 packages should get dropped from CentOS Extras as well.
Thanks! Niels
On Wed, Apr 4, 2018 at 1:20 PM, Anssi Johansson avij@centosproject.org wrote:
storage/x86_64/ceph-hammer storage/x86_64/ceph-jewel storage/x86_64/ceph-luminous
The first one (ceph-hammer) is EOL.
The latter two (ceph-jewel and ceph-luminous) are maintained.
- Ken
On Wed, Apr 4, 2018 at 8:20 PM, Anssi Johansson avij@centosproject.org wrote:
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.
What do you mean "copied over"? You mean exact RPMs copied over into new repos, or empty repo directory structures?
Re-building packages against the new release seems like a good idea in general, and that will naturally filter out material not being actively maintained by the SIGs.
-George
cloud/x86_64/openstack-newton
This one is EOL for stable release builds, we are keeping it around only in http://trunk.rdoproject.org/centos7-newton/ for upgrade CI purposes.
cloud/x86_64/openstack-ocata cloud/x86_64/openstack-pike cloud/x86_64/openstack-queens
Those stay under upstream and RDO maintenance as per http://releases.openstack.org/
Cheers, Alan
-
Alan Pevec -
Anssi Johansson -
George Dunlap -
John R. Dennison -
Ken Dreyer -
Niels de Vos -
Sandro Bonazzola -
Thomas F Herbert -
Trevor Hemsley