IUS CDN

[carlwgeorge]

Summary

The IUS project will be migrating from our existing mirror network to utilizing Rackspace CDN.

Current State

Currently the IUS repositories are published to https://dl.iuscommunity.org. We have a network of community mirrors that replicate this content. The ius-release package points users to https://mirrors.iuscommunity.org/mirrorlist, which provides a geographically sorted list of mirrors based on the GeoIP information of the requesting IP.

Future State

https://repo.ius.io has been configured using Rackspace CDN. New packages will be published here going forward. Existing packages on https://dl.iuscommunity.org will continue to be updated until the transition is complete. This will be accomplished by updating the ius-release package to point to https://repo.ius.io instead of https://mirrors.iuscommunity.org/mirrorlist. Users of the ius-release package should not have to take any action other than upgrading ius-release. If you have customized the repo files from this package, you will need to merge in the rpmnew files just like any other package update.

FAQ

Can I start using the CDN now?

Sure! If you are already subscribed to IUS, you can update the ius-release package from the testing repo just update ius-release. Make sure to clear the yum cache afterwards.

yum update ius-release
yum clean all

On a system that isn't subscribed to IUS yet, new ius-release packages can be downloaded at these links:

• https://repo.ius.io/ius-release-el6.rpm
• https://repo.ius.io/ius-release-el7.rpm

You can also download the repo config and GPG key individually from https://repo.ius.io.

What if I still want to mirror IUS for my own needs?

We realize that many members of our mirror network still would like to mirror our content for their own needs, commonly referred to as a "private" mirror. This will still be an option even after https://dl.iuscommunity.org is taken offline in the future. We will be reaching out to existing mirror contacts with the new rsync information. If anyone new wants to mirror IUS for their own needs reach out to [email protected].

Why don't I see separate packages for RHEL and CentOS?

In the past IUS built separate packages for RHEL and CentOS due to possible long delays between a RHEL release and CentOS catching up. Now that Red Hat sponsors CentOS that only takes a few weeks at most. It's just not worth the effort of the duplicate builds anymore. In the future, if a library change happens in RHEL that causes a built package to be compatible with the new RHEL but not the yet-to-catch-up CentOS, IUS can keep that package in ius-testing until CentOS catches up. This is the approach that EPEL normally takes.

[devicenull]

Why are you switching away from third party mirrors?

[carlwgeorge]

@devicenull Managing a mirror network takes much more effort than using a CDN. On top of that, CDN solves the distribution problem much better. There are more endpoints around the globe, and no work is needed from the IUS team as the CDN service adds and removes nodes. Anyone that still wants to mirror IUS can, but the official ius-release package is going to point to the CDN.

[jjlin]

@carlwgeorge For people who run "private" mirrors, could you just post the rsync info publicly?

[carlwgeorge]

@jjlin The domain for the rsync is the same as the https origin for the CDN. I'd like to avoid users bypassing the CDN. If you need the rsync info just email [email protected] and I'll be happy to share it with you.

[carlwgeorge]

I've created a new ius-release package that points to the CDN. It can be downloaded at the following links for those that want to start using it.

• https://repo.ius.io/ius-release-el6.rpm
• https://repo.ius.io/ius-release-el7.rpm

I have not published this package into the stable repo yet.

[kustodian]

What about the CentOS packages? I only see EL. Old repository URL has separate repositories for CentOS and RHEL.

[carlwgeorge]

@kustodian Yes, in the past IUS built separately for RHEL and CentOS. To my knowledge we were the only third party repository doing this. Even EPEL only builds against RHEL. In the past there were concerns with long delays between a RHEL release and CentOS catching up, but now that Red Hat sponsors CentOS that only takes a few weeks at most. It's just not worth the effort of the duplicate builds anymore.

In the future, if a library change happens in RHEL that causes a built package to be compatible with the new RHEL but not the yet-to-catch-up CentOS, IUS can keep that package in ius-testing until CentOS catches up. This is the approach that EPEL normally takes.

[kustodian]

Cool. That means that we can safely switch to the new repo URL. Thanks.

[kustodian]

Is the new repo up-to-date? Because once I changed the URL yum is telling me that the repo data is older from what we already have:

ius                                                                                                                                                                                  | 1.3 kB  00:00:00     
Not using downloaded ius/repomd.xml because it is older than what we have:
  Current   : Wed May  1 10:58:04 2019
  Downloaded: Mon Apr 22 18:45:24 2019

[carlwgeorge]

Yes, it's up to date. That was just a side effect of the timing of migrating the content. The old system regenerated the repodata every night, even if the content was the same, and that ran a few more times after I seeded the new repo with the old content. A yum clean all would resolve this for you. I went ahead and regenerated the repodata for good measure as well.

[kustodian]

Thanks for the explanation.

[carlwgeorge]

@ScoobyDone Yes, the website is getting overhauled and the update will include refreshed information for getting started.

[khambrecht]

All of the previous i686 packages are available on the CDN in the archive repository. With they ius-release package installed they can be accessed by adding the --enablerepo ius-archive flag to yum. We keep all our old builds in the archive, so it shouldn't be necessary to mirror them yourself unless you really want to.

looks like the i686 package are gone. Any chance to get them back?

[carlwgeorge]

@khambrecht See this comment about i686 packages. The previously built i686 packages are still available from the old URL: https://dl.iuscommunity.org/pub/ius/

[khambrecht]

@carlwgeorge thanks

iirc, the i686 packages have been available via https://repo.ius.io/archive/6/i686/ also. At least a couple of weeks ago.

But I'll switch over to https://dl.iuscommunity.org/pub/ius/ then.

[carlwgeorge]

The legacy mirrorlist API will be turned off 2020-01-08.

[BBQigniter]

this info, that iuscommunity.org-repo is being "turned off" and that https://dl.iuscommunity.org/pub/ius/stable/ will not be updated soon, would be super great somehwere in the ius-faq (with mentioning "iuscommunity.org") or so. i couldn't find any info on ius.io in the FAQ or in About - just that there was/will be some change.

because me and my colleagues now wondered why we do not get the latest php72u-common 7.2.24 packages on our internal mirror and with some googleing i found this github issue with the explanation :)

[carlwgeorge]

@BBQigniter The website sources are linked in the website footer. If you'd like to add an FAQ item or update an existing one, please send a pull request.

[dpeterson1128]

I appreciate the info. Same as @BBQigniter I am needing the php72u-common 7.2.24 package but it is not on the old mirror (https://dl.iuscommunity.org/pub/ius/stable/). Is there a new rysnc target I can point to for https://repo.ius.io/?

This is the rsync target I was previously using that no longer works: rsync://dl.iuscommunity.org/ius/stable/CentOS/7/x86_64/

[carlwgeorge]

@dpeterson1128 Assuming you're the same David that emailed me, I've replied to the email with instructions.

[carlwgeorge]

As promised in #14 (comment), I have turned off the mirrorlist service. If your system wasn't able to update ius-release from the repos before now, you should take the following steps.

1. yum erase ius-release
2. rm /etc/yum.repos.d/ius*.repo*
3. follow the instructions on https://ius.io/setup

[mty22]

@carlwgeorge Congrats on moving to Rackspace CDN. :)

Just a question, did you plan on reaching out to existing mirror admins to advise?

I have been the maintainer for ius.mirror.digitalpacific.com.au for almost 5 years now and I only happened to stumble on this thread by chance as I noticed our IUS mirror was out of sync as I was migrating all mirrors to newer hardware.

Just as a note, we still see a lot of traffic from existing IUS users who are yet to update their repo files. It may be worth updating your rsync end point, more specifically rsync://dl.iuscommunity.org/ius/ to just be a 301 to new newer CDN? (lets us maintainers recover resources).

[carlwgeorge]

@mty22 I sent you (and all the other mirror contacts we had on file) an email the same day I opened this issue (2019-04-30).

Anyone syncing from rsync://dl.iuscommunity.org/ius/ is getting the latest content set. That hostname will eventually go away. If you'd like to continue to mirror IUS for your own needs reach out to [email protected] for the new hostname.

[carlwgeorge]

This issue is closed, but seems to be a magnet for unrelated problems. To avoid continuing sending notification to users that subscribed for the CDN changes, I'm going to lock this issue. Please follow the instructions in our FAQ for future problems.