MirrorManager has no way to do any of the 4 redirects you're asking for today, so it
would have to be a feature enhancement, if done there.
The trick is, you want URLs that, like the mirrorlist?repo=foo&arch=bar, act as an
indirection, meaning, a constant string URL that then points to where said content
actually is (perhaps it's in the staging tree right now, and later it's in the
releases tree). Right? We can do this for yum repositories today, but MM can't do it
for arbitrary files - not impossible, it just isn't implemented today. So by F19, no
chance.
An alternative manual solution would be to deploy apache mod_rewrite lines, such as:
RewriteRule permalink?file=Fedora-x86_64-19-sda.qcow2
mirrorlist?path=pub/alt/stage/19-RC1/Images/x86_64/Fedora-x86_64-19-20130624-sda.qcow2&redirect=1
RewriteRule mirrorlist?file=Fedora-x86_64-19-sda.qcow2
mirrorlist?path=pub/alt/stage/19-RC1/Images/x86_64/Fedora-x86_64-19-20130624-sda.qcow2
RewriteRule permalink?file=Fedora-x86_64-sda.qcow2
mirrorlist?path=pub/alt/stage/19-RC1/Images/x86_64/Fedora-x86_64-19-20130624-sda.qcow2&redirect=1
RewriteRule mirrorlist?file=Fedora-x86_64-sda.qcow2
mirrorlist?path=pub/alt/stage/19-RC1/Images/x86_64/Fedora-x86_64-19-20130624-sda.qcow2
and update them manually as the files change location and version.
If instead done in MM, use of file=<something> here would be new arguments to the
mirrorlist/metalink URLs already existing, and would have to be unique across the whole
file system, so couldn't be used with an arbitrary file (e.g. repomd.xml), only those
with unique names...
--
Matt Domsch
Distinguished Engineer, Technology Strategist
Dell | Office of the CTO
-----Original Message-----
From: infrastructure-bounces(a)lists.fedoraproject.org
[mailto:infrastructure-bounces@lists.fedoraproject.org] On Behalf Of Matthew Miller
Sent: Tuesday, June 25, 2013 10:12 AM
To: infrastructure(a)lists.fedoraproject.org
Subject: mirrormanager support for the cloud image
Um, sorry, this is kind of a last-minute afterthought, so I'm not expecting it for F19
launch or anything crazy. But:
For F19, we're putting cloud images on the mirrors. In the staging tree, the URL is
like this:
https://dl.fedoraproject.org/pub/alt/stage/19-RC1/Images/x86_64/Fedora-x8...
and I presume that the final pattern will be
../19/Images/x86_64/Fedora-x86_64-19-20130624-sda.qcow2
(Or possibly s/Images/Cloud/ -- I had thought that's what we previously agreed but I
need to dig that up.)
Is there a way that we could make permanent URLs for the following:
- per-versionsorted list of URLs to the image on mirrors
- per-version redirect to the closest (or at least randomly chosen) image suitable
for giving to OpenStack Glance directly
- an unversioned URL redirecting to the latest per-version list
- an unversioned URL redirecting to the latest-version redirect
I'm just guessing that mirrormanager is the best place for this. I'm happy with
any other solution....
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
_______________________________________________
infrastructure mailing list
infrastructure(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure