#4149 Need a way to point EC2 instances to specific mirrors
Closed: Fixed None Opened 10 years ago by gholms.

To get Fedora working well on Amazon's EC2 cloud computing service ![1] the Cloud SIG is working on creating yum mirrors inside Amazon's network. Doing so provides a number of benefits:
* Faster updates for users
* People with hundreds of Fedora instances don't overload other public mirrors
* No data transfer costs for users or those who fund the EC2 mirrors (traffic within a given cloud region is free)

Unfortunately, data transfers are only free if they stay within a given region. This, combined with the fact that EC2's IP addresses freely roam between regions, makes normal IP-based direction via !MirrorManager impossible. We therefore need another way of directing clients toward the mirrors that reside within their own regions.

Our list of proposed solutions to this are posted in the "Client Access" portion of my overall proposal for EC2 mirror infrastructure ![2]. Could you folks (a) offer any feedback, or (b) choose which solution would be best? I apologize if this is more of a FESCo question; I can take it to them if that would be better.

![1] https://fedoraproject.org/wiki/Features/EC2

![2] https://fedoraproject.org/wiki/User:Gholms/EC2_Mirror_Proposal#Client_Access


I'm pretty OK with the proposal that involves a tag to add to MM urls to indicate the area of amazon that saves money.

Replying to [comment:1 jkeating]:

I'm pretty OK with the proposal that involves a tag to add to MM urls to indicate the area of amazon that saves money.

Which one? 2 (fedora-release + init script), or 3 (yum plugin)?

Given that I suggested the yum plugin, that's the one I would like to see :)

Appending a variable which can be nothing or which can be populated as an /etc/yum/vars variable would mean not having to maintain a standalone plugin forever for a single purpose of appending to urls.

and it would also mean that we wouldn't have to guess if any yum-using tool was properly setting up their plugins.

Replying to [comment:4 skvidal]:

Appending a variable which can be nothing or which can be populated as an /etc/yum/vars variable would mean not having to maintain a standalone plugin forever for a single purpose of appending to urls.

and it would also mean that we wouldn't have to guess if any yum-using tool was properly setting up their plugins.

That seems like a good reason to not use the plugin. I'm easily convinced :)

If solution 2 is accepted I need to file blocker bugs against fedora-release and generic-release. Setting Milestone to reflect that...

Now that F14 is out, we can work on the fedora-release stuff for F15. Where do we stand here?

Replying to [comment:8 jkeating]:

Now that F14 is out, we can work on the fedora-release stuff for F15. Where do we stand here?

The fedora-release bug ([https://bugzilla.redhat.com/show_bug.cgi?id=643185 #643185]) is open, assigned to you. The generic-release bug ([https://bugzilla.redhat.com/show_bug.cgi?id=643186 #643186]) made it into F14. AFAIK the necessary !MirrorManager changes are done but not yet rolled out, though that doesn't block this particular part of the effort.

I think we have this handled now

Login to comment on this ticket.

Metadata