Project

General

Profile

Feature #11335

Bug #7161: Support more than 24 HTTP mirrors

Feature #8635: Make each mirror provide a unique virtualhost name

Set up the process and tools to allocate unique *.dl.amnesia.boum.org hostnames

Added by intrigeri over 3 years ago. Updated over 3 years ago.

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

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
Affected tool:

Description

It would be nice to be able to actually allocate such unique hostnames, once after #11055 is done mirror operators start asking us :)

Associated revisions

Revision e4a36e44 (diff)
Added by anonym over 3 years ago

Don't explicitly depend on openjdk-7-jre.

... or any JRE for that matter. Sikuli will pull in a suitable one, so
depending on one ourselves is only risking causing trouble (like the
current situation in Sid, see #11335).

Will-fix: #11335

History

#1 Updated by intrigeri over 3 years ago

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to sajolida
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

Done on the server side, pushed scripts and doc => sajolida, I'm sending you a private email with details about what you should review :)

#2 Updated by intrigeri over 3 years ago

FYI, I have some additional local changes that I would like to test before pushing. I don't think it should block your review, but here's a spoiler: in add-mirror-subdomain, in the next_free_mirror_id function, we'll check what the last.dl.amnesia.boum.org CNAME record points to; and when creating a new NNN.dl.a.b.o host name, we'll make that CNAME point to the newly created host name. It feels like a more robust way to track what's the highest allocated mirror ID than the previous loop, and contrary to the previous implementation, it doesn't rely on the fact that there is no hole in the range of the NNN.dl.a.b.o we've allocated (which should be more robust against mistakes in the pool management).

#3 Updated by sajolida over 3 years ago

  • Assignee changed from sajolida to intrigeri
  • QA Check changed from Ready for QA to Dev Needed

Reviewed, and I'm fine! I also prefer the last.dl.amnesia.boum.org trick that the current version. So I'm reassigning to you to push this.

#4 Updated by intrigeri over 3 years ago

  • Assignee changed from intrigeri to sajolida
  • % Done changed from 50 to 60
  • QA Check changed from Dev Needed to Ready for QA

Perfect timing, I just finished this and pushed (check-mirrors & mirrors repositories), so please review the last version. If you want to test the new script, I can clean behind you.

#5 Updated by sajolida over 3 years ago

  • Assignee changed from sajolida to intrigeri
  • Target version changed from Tails_2.3 to Tails_2.4
  • QA Check changed from Ready for QA to Pass

I don't want to test it just for the sake of testing it. I reviewed the code as far as my scripting skills go and it looks good.

Also, on a slighly related topic, we should decide what to do with the information currently in mirrors.mdwn. I guess we should at least update the list to include the new subdomains. But maybe this will be handled when communicating with mirror operators.

#6 Updated by intrigeri over 3 years ago

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

sajolida wrote:

I don't want to test it just for the sake of testing it. I reviewed the code as far as my scripting skills go and it looks good.

OK, resolved then!

Also, on a slighly related topic, we should decide what to do with the information currently in mirrors.mdwn.

Right. This is now tracked by #11384.

I guess we should at least update the list to include the new subdomains.

Sure. I've been doing it continuously until now, and I intend to go on until we switch production to the new setup.

But maybe this will be handled when communicating with mirror operators.

Not sure what you mean here, please clarify (either here or on #11384 or elsewhere, as you think is best).

#7 Updated by sajolida over 3 years ago

But maybe this will be handled when communicating with mirror operators.

Not sure what you mean here, please clarify (either here or on #11384 or elsewhere, as you think is best).

You already started doing this in "Please update your Tails mirror
configuration" so my concern is irrelevant now.

#8 Updated by BitingBird over 3 years ago

  • Priority changed from Elevated to Normal

Also available in: Atom PDF