Description of problem:
Part of the Cloud SIG's overall effort to get Fedora on Amazon EC2 involves directing users' VM instances to yum mirrors inside Amazon's S3 storage service. Since the usual IP block-based decisions don't work with EC2 instances, the preferred solution involves passing a "location" parameter to MirrorManager that contains the VM's location so MirrorManager to tell it where to go.
The code to support this exists in both Yum and MirrorManager, so to make it possible for VMs to use this Fedora's yum repo definitions need to be set up to pass MirrorManager this additional information by appending "&location=$location" to Fedora's stock yum repo files.
The whole process is documented in the wiki page for the EC2 mirror proposal. Also relevant are the rel-eng ticket , a recent Cloud SIG discussion on the topic , and a brief FESCo discussion on the topic .
re-assigning to rawhide, pretty much too late for F14, just days away from
change freeze and months past feature freeze. This could get backported to F14
once it has been fleshed out in rawhide.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
The location code in mirrormanager is in the 1.4 branch not yet released or in production for Fedora. I don't think it'll be released before F15 launch. Hopefully soon thereafter though.
reminder that I haven't done this yet for MM 1.3 in production, and 1.4 has been far slower in coming than I would have thought.
The original reason for this request was to reduce the (monetary) cost of running updates on Fedora instances in EC2. Since then Amazon has stopped charging for inbound data, ending the Cloud SIG's push for Fedora-sponsored mirrors inside Amazon.
We have Fedora Infrastructure-managed mirrors in S3 now in several regions, and Amazon now publishes the list of IP address blocks for each region, so we don't really need location=foo anymore. Closing.