-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
tl;dr The current thinking is to add the following snippet in the %post of centos-release and release to all of the arches. This will set a yum var to the correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos' >/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`
Here's the start of a proposal from the SIG perspective
## Requirements:
- - The same noarch binary RPM *must* be distributable to the Extras repo for each architecture
- - The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
- - A yum variable called 'contentdir' will be populated with the toplevel directory for SIGs to use
1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=https://mirror.centos.org/$contentdir/cloud/$basearch/openstack-queens/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we update the SIGGuide and rework centos-release.
Cheers!
- -- Brian Stinson
W dniu 06.03.2018 o 07:11, Brian Stinson pisze:
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
By 'SIG Content' you mean OpenStack?
I do not see storage/ or opstools/ :(
Will keep using https://buildlogs.centos.org/centos/7/ as repository ;(
On 06/03/18 09:18, Marcin Juszkiewicz wrote:
W dniu 06.03.2018 o 07:11, Brian Stinson pisze:
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
By 'SIG Content' you mean OpenStack?
I do not see storage/ or opstools/ :(
Will keep using https://buildlogs.centos.org/centos/7/ as repository ;(
Well, it should be pushed it that was asked, but so far in the file that controls what needs to go where, I only see ovirt, sclo and storage (for gluster, that was added yesterday so it should have appeared today) for aarch64 and ppc64le
If there are more requests to release other content for /altarch/ , it should land there.
Is there other content that was requested to be pushed for /altarch/ and not yet pushed ? if so Brian is doing a review of all opened bug reports on https://bugs.centos.org during the weekly CBS meeting (https://www.centos.org/community/calendar/#Community_Buildsystem_&_Infra...) for that
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mar 06 15:41, Fabian Arrotin wrote:
On 06/03/18 09:18, Marcin Juszkiewicz wrote:
W dniu 06.03.2018 o 07:11, Brian Stinson pisze:
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
By 'SIG Content' you mean OpenStack?
I do not see storage/ or opstools/ :(
Will keep using https://buildlogs.centos.org/centos/7/ as repository ;(
Well, it should be pushed it that was asked, but so far in the file that controls what needs to go where, I only see ovirt, sclo and storage (for gluster, that was added yesterday so it should have appeared today) for aarch64 and ppc64le
If there are more requests to release other content for /altarch/ , it should land there.
Is there other content that was requested to be pushed for /altarch/ and not yet pushed ? if so Brian is doing a review of all opened bug reports on https://bugs.centos.org during the weekly CBS meeting (https://www.centos.org/community/calendar/#Community_Buildsystem_&_Infra...) for that
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Opstools is pending. I have a tag or two to sort out for cbs altarch enablement before we can do the push.
I will do a separate announcement to be sure that everyone creates updated bug reports for content that they're hoping to be released to the /altarch locations. As of right now the mirrors are up to date relative to the requests/bugs we've logged.
- --Brian
W dniu 06.03.2018 o 15:41, Fabian Arrotin pisze:
If there are more requests to release other content for /altarch/ , it should land there.
Is there other content that was requested to be pushed for /altarch/ and not yet pushed ?
1. https://bugs.centos.org/view.php?id=14782 (/storage/ceph-luminous) 2. https://bugs.centos.org/view.php?id=13633 (/opstools)
Brian Stinson kirjoitti 6.3.2018 klo 8.11:
1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=https://mirror.centos.org/$contentdir/cloud/$basearch/openstack-queens/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
Last time I looked, mirror.centos.org did not support https. Other than that, I don't see any immediate problem with this approach.
On 03/06/2018 03:11 AM, Brian Stinson wrote:
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
tl;dr The current thinking is to add the following snippet in the %post of centos-release and release to all of the arches. This will set a yum var to the correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos' >/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`Here's the start of a proposal from the SIG perspective
## Requirements:
The same noarch binary RPM *must* be distributable to the Extras repo for each architecture
The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
- A yum variable called 'contentdir' will be populated with the toplevel directory for SIGs to use
1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=https://mirror.centos.org/$contentdir/cloud/$basearch/openstack-queens/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we update the SIGGuide and rework centos-release.
Cheers!
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi, Brian.
I don't have the whole background of why non-x86_64 architectures are placed at /altarch. Perhaps you or someone else from CentOS can provide some of the details.
Wouldn't it be simpler if a non-x86_64 architecture was just another directory on, for example, /centos/7/<content>/<arch> hierarchy?
This also simplifies packaging.
Cheers Murilo
On 06/03/18 13:21, Murilo Opsfelder Araujo wrote:
On 03/06/2018 03:11 AM, Brian Stinson wrote:
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
tl;dr The current thinking is to add the following snippet in the %post of centos-release and release to all of the arches. This will set a yum var to the correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos' >/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`Here's the start of a proposal from the SIG perspective
## Requirements:
The same noarch binary RPM *must* be distributable to the Extras repo for each architecture
The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
- A yum variable called 'contentdir' will be populated with the toplevel directory for SIGs to use
1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=https://mirror.centos.org/$contentdir/cloud/$basearch/openstack-queens/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we update the SIGGuide and rework centos-release.
Cheers!
Hi, Brian.
I don't have the whole background of why non-x86_64 architectures are placed at /altarch. Perhaps you or someone else from CentOS can provide some of the details.
Wouldn't it be simpler if a non-x86_64 architecture was just another directory on, for example, /centos/7/<content>/<arch> hierarchy?
This also simplifies packaging.
Cheers Murilo
The approach given by Brian isn't rocket science and would permit to cover that /altarch/ vs /centos/ difference for baseurl= , that's also more or less what we use for armhfp , to redirect the kernel repo to correct one, so it's just a one liner snippet in the .spec for the -release noarch pkg :-)
WRT difference in the URI, it was a decision taken by KB and Jim when the first altarch (aarch64) landed on mirror.centos.org, and then we continued with it , as it also added more content/storage, and some external mirrors weren't keen on adding all those arches. That's the reason why they can then do an "opt-in" for those if they want : - https://www.centos.org/download/mirrors/ - https://www.centos.org/download/altarch-mirrors/
Does that answer your question ?
On 03/06/2018 11:34 AM, Fabian Arrotin wrote:
On 06/03/18 13:21, Murilo Opsfelder Araujo wrote:
On 03/06/2018 03:11 AM, Brian Stinson wrote:
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
tl;dr The current thinking is to add the following snippet in the %post of centos-release and release to all of the arches. This will set a yum var to the correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos' >/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`Here's the start of a proposal from the SIG perspective
## Requirements:
The same noarch binary RPM *must* be distributable to the Extras repo for each architecture
The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
- A yum variable called 'contentdir' will be populated with the toplevel directory for SIGs to use
1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=https://mirror.centos.org/$contentdir/cloud/$basearch/openstack-queens/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we update the SIGGuide and rework centos-release.
Cheers!
Hi, Brian.
I don't have the whole background of why non-x86_64 architectures are placed at /altarch. Perhaps you or someone else from CentOS can provide some of the details.
Wouldn't it be simpler if a non-x86_64 architecture was just another directory on, for example, /centos/7/<content>/<arch> hierarchy?
This also simplifies packaging.
Cheers Murilo
The approach given by Brian isn't rocket science and would permit to cover that /altarch/ vs /centos/ difference for baseurl= , that's also more or less what we use for armhfp , to redirect the kernel repo to correct one, so it's just a one liner snippet in the .spec for the -release noarch pkg :-)
WRT difference in the URI, it was a decision taken by KB and Jim when the first altarch (aarch64) landed on mirror.centos.org, and then we continued with it , as it also added more content/storage, and some external mirrors weren't keen on adding all those arches. That's the reason why they can then do an "opt-in" for those if they want :
Does that answer your question ?
Hi, Fabian.
Thanks for the background information.
Cheers Murilo
2018-03-06 7:11 GMT+01:00 Brian Stinson brian@bstinson.com:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
tl;dr The current thinking is to add the following snippet in the %post of centos-release and release to all of the arches. This will set a yum var to the correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos'/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`
Here's the start of a proposal from the SIG perspective
## Requirements:
- The same noarch binary RPM *must* be distributable to the Extras
repo for each architecture
- The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
directory for SIGs to use
- A yum variable called 'contentdir' will be populated with the toplevel
1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=https://mirror.centos.org/$contentdir/cloud/$ basearch/openstack-queens/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we update the SIGGuide and rework centos-release.
+1 on oVirt side. Here's the patch waiting for centos-release to be available with above suggestion: https://gerrit.ovirt.org/#/c/88300/
Cheers!
Brian Stinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJanjEMAAoJEIMGvNKzCweMR6oQAMbsKqvJcfKW1+5yHsbEV33d QAAMwjEcKfZ+v9ypejErbPPh5RhuNCoRFFHUDAn4hBJNo2zb0YC0vKZJF3RIPIkV 9GAOwnnrWIvFJbeZ7sY4POMa/50IJXC3N8CeiW2XonDtf58rXZPsXM9/9JN9xCv7 X39FAIufCYA7rmedta236NMAutiEolyDFKWWJN6kwDzhm4p7BT9UVSyf7sWCBDzx t+TuCo7LZei4iwQWho1YL/9jbm0YP6EEyL3jJ/YT68cE8q9Mqd8qiE0gEMy0Eoof FuGNOLMrFhsvg3jNQr5DkbToDU+VwO3B+YVR29pTrd0Gf8bodmGTH31eCEljlhjg uPlms2cDvkaXlJmjO6XHM0D2cxmlTzBfVG7YrRwlD40JSk1Z3iyPyLkWJ967oyVM 9mmkhv4spNCX4okQlNI737bULwcxILM6ks3oCdO4i4Yk8BbZp/iwrJ9jcxr7U5YT Cvq2SuV5EbcXlxnhmMd/V6+F/VkgKqi0xrltKURlVUk+JzabHTw5zGwcRjnHxUQR nz2YiQ0mdR/pPuGyXl6xOqXl+M6khPBdCk4FHHdrZYw6aijo8FHzR1DYc63m4ibf Pkad1V9Awetuz0YwewgTp3MviRlklQte8jXMV/1Nh0TTp8xIs5e4ISNBwD3EtINL oqQYqpSGC0jkrwXD5fRG =F1Fp -----END PGP SIGNATURE----- _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mar 06 00:11, Brian Stinson wrote:
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
tl;dr The current thinking is to add the following snippet in the %post of centos-release and release to all of the arches. This will set a yum var to the correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos' >/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`Here's the start of a proposal from the SIG perspective
## Requirements:
The same noarch binary RPM *must* be distributable to the Extras repo for each architecture
The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
- A yum variable called 'contentdir' will be populated with the toplevel directory for SIGs to use
1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=http://mirror.centos.org/$contentdir/cloud/$basearch/openstack-queens/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we update the SIGGuide and rework centos-release.
Cheers!
-- Brian Stinson _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
To be clear,
This is a PROPOSAL at this stage, we haven't actually made any changes to centos-release yet. At this point if you're actively doing work relying on the new variable, it will break!
Also thank you to the folks up-thread who pointed out that there was a typo in the repo entry. mirror.centos.org should use http://
- --Brian
2018-03-06 17:40 GMT+01:00 Brian Stinson brian@bstinson.com:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mar 06 00:11, Brian Stinson wrote:
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS 7 on
the
mirrors, we need to come with some requirements and recommendations for
dealing
with the different locations.
tl;dr The current thinking is to add the following snippet in the %post
of
centos-release and release to all of the arches. This will set a yum var
to the
correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos'/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`
Here's the start of a proposal from the SIG perspective
## Requirements:
The same noarch binary RPM *must* be distributable to the Extras repo for each architecture
The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
- A yum variable called 'contentdir' will be populated with the toplevel directory for SIGs to use
1.) Modify baseurls in the SIG repo files to look like the following
(using
openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=http://mirror.centos.org/$contentdir/cloud/$
basearch/openstack-queens/
gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we
update
the SIGGuide and rework centos-release.
Cheers!
-- Brian Stinson _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
To be clear,
This is a PROPOSAL at this stage, we haven't actually made any changes to centos-release yet. At this point if you're actively doing work relying on the new variable, it will break!
Also thank you to the folks up-thread who pointed out that there was a typo in the repo entry. mirror.centos.org should use http://
Any update on the acceptance of the proposal?
- --Brian
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJansRxAAoJEIMGvNKzCweMcm4QAI0RoUT1BVUdU9oUdKSoPyKl qzn/nYOi7c9jsysOsSsHEg3yVWEzDJ/JEIWiTBJ2jtoOSQ3SiXfcieAa+U0d5oIR hNwwx6P6Mh0aCooIxrtC48qAx1Lustv5xrU98LUnpmQGDGfMusY1J7yst4UVc/ZE JI8XW9Zk9jY5GKev2UIVlwAVeqZjQ3A1IsKot11eS2YfV0Q40t2J83eIvyyXRFHG vQ4nV/FaZ3fXvUbjBSlS0xGV3pBcLWvq/bBqkkvXQEBNfjTlcGeIlj8FY/n5Jp6P ErXJSMXrUQG45cnUsqWl6w5VgRtmVmUY+0QHRnl1XQxZYQdzjbMv4/ZALnok0mCZ ceLsFRGhyxJsWcSCH9fNwyEn38arsIfP6FppvjuVvRhMGhfr+RCowrU7dbjSHD/h Oex+mYDLPP5klL/0x4xwMKDO2DgjH1/PGbY5QesIK5Vg+qL8a0/ZOYnO/pXBsIKJ 61yE9PsfdUdDEJb/spTv1cOsxjUqGQRrF4NKA1RdsNntNIS8C1541hozysCfQRQA ce8dDSUxuEb/n8vC1p03fQV29xwXiHxxRiZcbcswiAZfdIbMKqEFcsECDOoutPuY SX0Il5oSYSmb0DKkhXuNpcv+Hce8NXfSNFK33S2t5znyhwJ6/Y6aNNUx8OPYHw3p nwwLUex/cVFeMo59okLU =+bze -----END PGP SIGNATURE----- _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Mar 14, 2018 at 12:03:11PM +0100, Sandro Bonazzola wrote:
2018-03-06 17:40 GMT+01:00 Brian Stinson brian@bstinson.com:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mar 06 00:11, Brian Stinson wrote:
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS 7 on
the
mirrors, we need to come with some requirements and recommendations for
dealing
with the different locations.
tl;dr The current thinking is to add the following snippet in the %post
of
centos-release and release to all of the arches. This will set a yum var
to the
correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos'/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`
Here's the start of a proposal from the SIG perspective
## Requirements:
The same noarch binary RPM *must* be distributable to the Extras repo for each architecture
The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
- A yum variable called 'contentdir' will be populated with the toplevel directory for SIGs to use
1.) Modify baseurls in the SIG repo files to look like the following
(using
openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=http://mirror.centos.org/$contentdir/cloud/$
basearch/openstack-queens/
gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we
update
the SIGGuide and rework centos-release.
Cheers!
-- Brian Stinson _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
To be clear,
This is a PROPOSAL at this stage, we haven't actually made any changes to centos-release yet. At this point if you're actively doing work relying on the new variable, it will break!
Also thank you to the folks up-thread who pointed out that there was a typo in the repo entry. mirror.centos.org should use http://
Any update on the acceptance of the proposal?
This looks good to me. For the Gluster repos in the Storage SIG we'll follow this approach as soon as the packages are synced to the mirror (just filed bug 14631) and a new centos-release with the 'contentdir' variable is available.
Thanks, Niels
2018-03-28 12:53 GMT+02:00 Niels de Vos ndevos@redhat.com:
On Wed, Mar 14, 2018 at 12:03:11PM +0100, Sandro Bonazzola wrote:
2018-03-06 17:40 GMT+01:00 Brian Stinson brian@bstinson.com:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mar 06 00:11, Brian Stinson wrote:
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS
7 on
the
mirrors, we need to come with some requirements and recommendations
for
dealing
with the different locations.
tl;dr The current thinking is to add the following snippet in the
%post
of
centos-release and release to all of the arches. This will set a yum
var
to the
correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos'/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`
Here's the start of a proposal from the SIG perspective
## Requirements:
The same noarch binary RPM *must* be distributable to the Extras repo for each architecture
The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
- A yum variable called 'contentdir' will be populated with the
toplevel
directory for SIGs to use
1.) Modify baseurls in the SIG repo files to look like the following
(using
openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=http://mirror.centos.org/$contentdir/cloud/$
basearch/openstack-queens/
gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we
update
the SIGGuide and rework centos-release.
Cheers!
-- Brian Stinson _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
To be clear,
This is a PROPOSAL at this stage, we haven't actually made any changes to centos-release yet. At this point if you're actively doing work relying on the new variable, it will break!
Also thank you to the folks up-thread who pointed out that there was a typo in the repo entry. mirror.centos.org should use http://
Any update on the acceptance of the proposal?
This looks good to me. For the Gluster repos in the Storage SIG we'll follow this approach as soon as the packages are synced to the mirror (just filed bug 14631) and a new centos-release with the 'contentdir' variable is available.
Thanks, Niels
Brian, any update on the status of the new centos-release rpm?
On Mar 06 00:11, Brian Stinson wrote:
Hi Folks,
Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations.
tl;dr The current thinking is to add the following snippet in the %post of centos-release and release to all of the arches. This will set a yum var to the correct content location when a new system gets installed:
`uname -m | grep -q 'x86_64' && echo 'centos' >/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir`Here's the start of a proposal from the SIG perspective
## Requirements:
- The same noarch binary RPM *must* be distributable to the Extras
repo for each architecture
- The centos-release-<SIG> packages *must* require centos-release
## New Recommendations for creating a centos-release file:
directory for SIGs to use
- A yum variable called 'contentdir' will be populated with the toplevel
1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example):
[centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=https://mirror.centos.org/$contentdir/cloud/$basearch/openstack-queens/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4
## Discussion
I'd like to hear thoughts, additions, and subtractions here before we update the SIGGuide and rework centos-release.
Cheers!
Brian Stinson
Hi All,
Since there were no objections, I think we should start implementing this proposal. I would like see if KB or Johnny have any thoughts before we get started, since they'll be making these changes.
--Brian
-
Anssi Johansson -
Brian Stinson -
Fabian Arrotin -
Marcin Juszkiewicz -
Murilo Opsfelder Araujo -
Niels de Vos -
Sandro Bonazzola