Hi,
We've seen the altarch (i386) for 7 being available at http://mirror.centos.org/altarch/
Could this be made available on rsync mirrors too ?:
rsync eu-msync.centos.org::CentOS
seems to be missing it ...
Thanks
Jarek
PS: .. the location of that is little bit confusing ... seems that all other SIGs products are to be found under releasenumber/signame/ ... why altarch is available in completely separate tree ? ....
Hi Jarek,
On 14/10/15 07:05, Jarek Polok wrote:
PS: .. the location of that is little bit confusing ... seems that all other SIGs products are to be found under releasenumber/signame/ ... why altarch is available in completely separate tree ? ....
Within a couple of months, we are going to have quite a bit of content under altarch as the armv7 / power( many of them)/ aarch64 / i386 tree's expand. We didnt think every rsync mirror would want to host those extra 100+GB given that we don't expect a huge user-base in the early months. Its likely ( and we hope ) the user-base expands, but we didnt want all hundreds of mirrors to suddenly inherit a huge payload.
The plan is to open rsync for these targets as wide as possible, to allow anyone wanting to opt into these to grab it from us. In the mean time we still need to workout how mirrorlist.centos.org is going to handle these, and how other SIGs are able to consume and extend this content.
Hi Karanbir !
On 10/14/2015 10:28 AM, Karanbir Singh wrote:
Hi Jarek,
On 14/10/15 07:05, Jarek Polok wrote:
PS: .. the location of that is little bit confusing ... seems that all other SIGs products are to be found under releasenumber/signame/ ... why altarch is available in completely separate tree ? ....
Within a couple of months, we are going to have quite a bit of content under altarch as the armv7 / power( many of them)/ aarch64 / i386 tree's expand. We didnt think every rsync mirror would want to host those extra 100+GB given that we don't expect a huge user-base in the early months. Its likely ( and we hope ) the user-base expands, but we didnt want all hundreds of mirrors to suddenly inherit a huge payload.
I understand this concern but since all official mirror owners are on this mailing list perhaps it would be sufficient to inform everybody about it few weeks/months in advance ? (and update howto at https://wiki.centos.org/HowTos/CreatePublicMirrors accordingly..)
(also: isn't RH going to release 7.X for aarch64 in the future ? .. in that case would CentOS 7 for aarch64 be in same place as x86_64 or in altarch ?)
The plan is to open rsync for these targets as wide as possible, to allow anyone wanting to opt into these to grab it from us. In the mean time we still need to workout how mirrorlist.centos.org is going to handle these, and how other SIGs are able to consume and extend this content.
Ok, so for now the only way to mirror the i686 altarch tree is to get it over http at: http://mirror.centos.org/altarch/ ?
(we are using these 32bit packages in our internal build system, so far we mirror from buildlogs.centos.org .. which is not very practical ..)
Thanks !
Jarek __ ------------------------------------------------------- _ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ _ http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ ______________________________________+41_75_411_9487 _
On 14/10/15 12:47, Jarek Polok wrote:
I understand this concern but since all official mirror owners are on this mailing list perhaps it would be sufficient to inform everybody about it few weeks/months in advance ? (and update howto at https://wiki.centos.org/HowTos/CreatePublicMirrors accordingly..)
right, I appreciate that - however, the goto release for aarch64 happened very quickly, we had literally 2 days to workout the entire process and so took the safest option that gives us the most expandability down the road.
(also: isn't RH going to release 7.X for aarch64 in the future ? .. in that case would CentOS 7 for aarch64 be in same place as x86_64 or in altarch ?)
if they do, when they do, then if we have a clear downstream build, that would end up in /centos/ space, till then ( and maybe beyond ) we would keep the altarch/ space going for this.
There is an ongoing conversation about what makes a SIG content be CentOS Linux branded and what makes it CentOS AltArch Branded, and hopefully in the coming months we can get a tangible plan in place to facilitate migration. This is also why I've tried to stay away from the idea of a secondary arch or a primary arch. Every build should be able to flourish on its own merits, we just need to communicate to the user base what that implies.
The plan is to open rsync for these targets as wide as possible, to allow anyone wanting to opt into these to grab it from us. In the mean time we still need to workout how mirrorlist.centos.org is going to handle these, and how other SIGs are able to consume and extend this content.
Ok, so for now the only way to mirror the i686 altarch tree is to get it over http at: http://mirror.centos.org/altarch/ ?
(we are using these 32bit packages in our internal build system, so far we mirror from buildlogs.centos.org .. which is not very practical ..)
we should have these on rsync in the coming days. Likely tomorrow.
On Wed, October 14, 2015 11:39 am, Karanbir Singh wrote:
On 14/10/15 12:47, Jarek Polok wrote:
I understand this concern but since all official mirror owners are on this mailing list perhaps it would be sufficient to inform everybody about it few weeks/months in advance ? (and update howto at https://wiki.centos.org/HowTos/CreatePublicMirrors accordingly..)
right, I appreciate that - however, the goto release for aarch64 happened very quickly, we had literally 2 days to workout the entire process and so took the safest option that gives us the most expandability down the road.
(also: isn't RH going to release 7.X for aarch64 in the future ? .. in that case would CentOS 7 for aarch64 be in same place as x86_64 or in altarch ?)
if they do, when they do, then if we have a clear downstream build, that would end up in /centos/ space, till then ( and maybe beyond ) we would keep the altarch/ space going for this.
And IMHO this is the wisest decision to keep anything that is not from upstream in a separate tree.
Valeri
There is an ongoing conversation about what makes a SIG content be CentOS Linux branded and what makes it CentOS AltArch Branded, and hopefully in the coming months we can get a tangible plan in place to facilitate migration. This is also why I've tried to stay away from the idea of a secondary arch or a primary arch. Every build should be able to flourish on its own merits, we just need to communicate to the user base what that implies.
The plan is to open rsync for these targets as wide as possible, to allow anyone wanting to opt into these to grab it from us. In the mean time we still need to workout how mirrorlist.centos.org is going to handle these, and how other SIGs are able to consume and extend this content.
Ok, so for now the only way to mirror the i686 altarch tree is to get it over http at: http://mirror.centos.org/altarch/ ?
(we are using these 32bit packages in our internal build system, so far we mirror from buildlogs.centos.org .. which is not very practical ..)
we should have these on rsync in the coming days. Likely tomorrow.
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 14/10/15 19:36, Valeri Galtsev wrote:
On Wed, October 14, 2015 11:39 am, Karanbir Singh wrote:
On 14/10/15 12:47, Jarek Polok wrote:
I understand this concern but since all official mirror owners are on this mailing list perhaps it would be sufficient to inform everybody about it few weeks/months in advance ? (and update howto at https://wiki.centos.org/HowTos/CreatePublicMirrors accordingly..)
right, I appreciate that - however, the goto release for aarch64 happened very quickly, we had literally 2 days to workout the entire process and so took the safest option that gives us the most expandability down the road.
(also: isn't RH going to release 7.X for aarch64 in the future ? .. in that case would CentOS 7 for aarch64 be in same place as x86_64 or in altarch ?)
if they do, when they do, then if we have a clear downstream build, that would end up in /centos/ space, till then ( and maybe beyond ) we would keep the altarch/ space going for this.
And IMHO this is the wisest decision to keep anything that is not from upstream in a separate tree.
Valeri
Well, as KB said, there is a need to define clearly what AltArch is. For example, it makes sense to say that armv7hl is AltArch as there is no upstream for it. It's interesting for ppc64/pp64le that is actually being built by Community, but with a real upstream version.
Anyway, such discussion would need to happen on the centos-devel list, and not the centos-mirror one.
Cheers, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 14/10/15 12:47, Jarek Polok wrote:
Ok, so for now the only way to mirror the i686 altarch tree is to get it over http at: http://mirror.centos.org/altarch/ ?
see if this works for you msync.centos.org::altarch - we dont have a clear policy for the mirrorlist and tracking side of things, that will still take a few days/weeks to resolve, but it should not have any user facing impact as we have enough capacity in mirror.centos.org to handle the yum and install operations for these altarch distro's.
regards,
On 10/15/2015 03:06 PM, Karanbir Singh wrote:
On 14/10/15 12:47, Jarek Polok wrote:
Ok, so for now the only way to mirror the i686 altarch tree is to get it over http at: http://mirror.centos.org/altarch/ ?
see if this works for you msync.centos.org::altarch
Yes it does, Thanks !
Jarek
- we ont have a
clear policy for the mirrorlist and tracking side of things, that will still take a few days/weeks to resolve, but it should not have any user facing impact as we have enough capacity in mirror.centos.org to handle the yum and install operations for these altarch distro's.
regards,
-
Fabian Arrotin -
Jarek Polok -
Karanbir Singh -
Valeri Galtsev