Bug #11056

Wait for most mirrors to implement new virtual hostname

Added by Anonymous 2016-02-04 12:19:44 . Updated 2016-06-26 11:14:37 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2016-02-04
Due date:
% Done:

100%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:
269

Description

..and remove the ones who did not from the pool.


Subtasks


Related issues

Blocked by Tails - Bug #11055: Ask all mirror operators to implement new virtual hostname Resolved 2016-02-04

History

#1 Updated by intrigeri 2016-03-04 12:49:48

  • Status changed from New to Confirmed

#2 Updated by intrigeri 2016-03-04 12:54:50

  • Category set to Infrastructure

#3 Updated by intrigeri 2016-03-04 18:30:02

  • blocked by Bug #11055: Ask all mirror operators to implement new virtual hostname added

#4 Updated by intrigeri 2016-04-25 13:00:21

  • Target version changed from Tails_2.3 to Tails_2.4

Bug #11055 is done, so there you go. I’ll handle the fallout of my email to mirror operators when it comes to 1. allocating unique hostnames; 2. taking note of their answers; 3. adjusting the doc as needed. So basically what you need to do is to check in our mirrors.mdwn if they all provided a unique URL prefix (last column in the list of mirrors), ping them again in a week and again until we have enough updated mirrors to do the switch to the new setup.

#5 Updated by intrigeri 2016-04-28 12:08:09

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 30

So, all active mirrors but 5 now have a unique URI, 5 of our spare mirrors also have a unique URI, and on top of that we have another mirror that we can enable only once we’ve switched to the new setup. In short, if we switched to the new setup right now, we would have one more mirror than previously. Which means that this ticket is not really blocking anything anymore, and we can go ahead :) I’ll reflect that in Redmine-speak right now.

Still, please ping the remaining mirrors at least once or twice in a week or two, because our goal (and success metrics!) here is to have more mirrors in the end.

#6 Updated by intrigeri 2016-05-10 06:12:30

  • Assignee set to intrigeri

Given I handled the rest of the communication process, maybe it makes sense that I lead it to its end. If you prefer doing it yourself, just take it back :)

#7 Updated by intrigeri 2016-05-10 06:12:42

  • Priority changed from Normal to High

#8 Updated by Anonymous 2016-05-13 03:28:40

I think it makes sense to let you do the remaining bits of work indeed. If you don’t want to, please give the ticket back to me :)

#9 Updated by intrigeri 2016-05-16 11:46:18

  • % Done changed from 30 to 80

Sent one last ping to the remaining 4 (2 active + 2 spare) mirrors that still haven’t adjusted to the new setup. Then I’ll give up, because mirror operators being unresponsive is a problem in itself.

#10 Updated by intrigeri 2016-05-23 12:38:18

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 80 to 100

Done.

#11 Updated by BitingBird 2016-06-26 11:14:37

  • Priority changed from High to Normal