Project

General

Profile

Feature #8637

Bug #7161: Support more than 24 HTTP mirrors

Design how to convey the mirror pool's configuration to the dispatcher script

Added by intrigeri over 4 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
Start date:
01/09/2015
Due date:
04/15/2016
% Done:

100%

Feature Branch:
Type of work:
Research
Starter:
Affected tool:

Description

Data model, data format, transport, reading and writing, taking into account how to integrate this all into how our website is hosted.


Related issues

Blocks Tails - Feature #8638: Implement how to convey the mirror pool's configuration to the dispatcher script Resolved 01/09/2015 04/15/2016
Blocks Tails - Feature #8639: Write a mirror pool dispatcher script Resolved 01/09/2015 04/15/2016
Blocked by Tails - Feature #10294: Define format for per-mirror hostname Resolved 09/28/2015

History

#1 Updated by intrigeri over 4 years ago

  • Description updated (diff)

#2 Updated by intrigeri over 4 years ago

  • Blocks Feature #8638: Implement how to convey the mirror pool's configuration to the dispatcher script added

#3 Updated by intrigeri over 4 years ago

  • Blocks Feature #8639: Write a mirror pool dispatcher script added

#4 Updated by intrigeri about 4 years ago

  • Target version changed from Sustainability_M1 to Tails_1.7

#6 Updated by intrigeri almost 4 years ago

  • Due date set to 04/15/2016

#7 Updated by intrigeri over 3 years ago

  • Blocked by Feature #10294: Define format for per-mirror hostname added

#8 Updated by intrigeri over 3 years ago

  • Blueprint set to https://tails.boum.org/blueprint/HTTP_mirror_pool/

Data model,

To be done.

data format,

This will be JSON, to avoid the need for third-party YAML parsers, unless #10284 makes us decide otherwise.

transport, reading and writing

We'll be using an ikiwiki overlay stored in Git.

#9 Updated by intrigeri over 3 years ago

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

#10 Updated by intrigeri over 3 years ago

  • Target version changed from Tails_1.7 to Tails_1.8

#11 Updated by intrigeri over 3 years ago

  • Target version changed from Tails_1.8 to 246

I'll focus on #5926 instead, during the 1.8 cycle.

#12 Updated by sajolida over 3 years ago

  • Target version changed from 246 to Tails_2.0

#13 Updated by intrigeri over 3 years ago

  • Target version changed from Tails_2.0 to Tails_2.2

#14 Updated by intrigeri over 3 years ago

  • Subject changed from Design how to convey the mirror pool's configuration to the server-side dispatcher script to Design how to convey the mirror pool's configuration to the dispatcher script

(The dispatcher will be client-side.)

#16 Updated by intrigeri over 3 years ago

  • % Done changed from 10 to 30

I think the only bit left to do here is to model how data will be stored in the JSON configuration.

#17 Updated by intrigeri over 3 years ago

  • Assignee changed from intrigeri to u
  • % Done changed from 30 to 50
  • QA Check set to Ready for QA

Pushed a free-form description to the blueprint, and a formal JSON schema + validation script + example config file to a dedicated repo (https://git-tails.immerda.ch/mirror-pool/). Also updated, on the blueprint, how exactly I think this will be integrated on our website. Had root@b.o set it up so boum_org_amnesia@webmasters.boum.org:mirror-pool.git is now an underlay for our website, meaning that it's content is already available online, e.g. https://tails.boum.org/example-mirrors.json.

I think this is all that this ticket was about, plus a little bit for the next step (#8638).

Please review all this. In particular, it's the first time I deal with JSON and JSON schemas, so I've quite possibly made newbie mistakes.

#18 Updated by u over 3 years ago

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

#19 Updated by u over 3 years ago

  • Assignee deleted (u)
  • QA Check changed from Ready for QA to Pass

intrigeri wrote:

Pushed a free-form description to the blueprint, and a formal JSON schema + validation script + example config file to a dedicated repo (https://git-tails.immerda.ch/mirror-pool/). Also updated, on the blueprint, how exactly I think this will be integrated on our website. Had root@b.o set it up so boum_org_amnesia@webmasters.boum.org:mirror-pool.git is now an underlay for our website, meaning that it's content is already available online, e.g. https://tails.boum.org/example-mirrors.json.

Great job! :)

I think this is all that this ticket was about, plus a little bit for the next step (#8638).

Please review all this. In particular, it's the first time I deal with JSON and JSON schemas, so I've quite possibly made newbie mistakes.

I can't find any mistake nor missing information, sorry! ;]

validated schema and data using https://json-schema-validator.herokuapp.com/
and had no errors.

#20 Updated by u over 3 years ago

  • Status changed from In Progress to Resolved

#21 Updated by intrigeri over 2 years ago

  • % Done changed from 50 to 100

Also available in: Atom PDF