+++ This bug was initially created as a clone of Bug #643185 +++
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.
generic-release-14-1 has been submitted as an update for Fedora 14.
generic-release-14-1 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update generic-release'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/generic-release-14-1
generic-release-14-1 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.