Tails

#1 Updated by intrigeri 2015-01-09 16:43:00

• Description updated

#2 Updated by intrigeri 2015-01-09 16:43:47

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

#3 Updated by intrigeri 2015-01-09 16:44:55

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

#4 Updated by intrigeri 2015-05-28 15:13:39

• Target version changed from Sustainability_M1 to Tails_1.7

#5 Updated by intrigeri 2015-05-28 15:14:26

• blocks #8668 added

#6 Updated by intrigeri 2015-08-02 09:55:40

• Due date set to 2016-04-15

#7 Updated by intrigeri 2015-09-28 03:20:35

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

#8 Updated by intrigeri 2015-09-28 03:51:29

• 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 Feature #10284 makes us decide otherwise.

> transport, reading and writing

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

#9 Updated by intrigeri 2015-10-05 11:08:35

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

#10 Updated by intrigeri 2015-10-31 08:18:04

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

#11 Updated by intrigeri 2015-11-02 04:11:25

• Target version changed from Tails_1.8 to 246

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

#12 Updated by sajolida 2015-11-27 04:46:20

• Target version changed from 246 to Tails_2.0

#13 Updated by intrigeri 2015-12-05 16:17:44

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

#14 Updated by intrigeri 2016-02-12 14:31:59

• 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.)

#15 Updated by intrigeri 2016-02-12 14:36:45

• blocked by deleted (#8668)

#16 Updated by intrigeri 2016-02-12 14:37:38

• % 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 2016-02-12 23:35:26

• Assignee deleted (intrigeri)
• % 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_amnesiawebmasters.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 (Feature #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 Anonymous 2016-03-18 23:32:37

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

#19 Updated by Anonymous 2016-03-19 00:02:54

• Assignee deleted ()
• 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_amnesiawebmasters.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 (Feature #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 Anonymous 2016-03-19 00:03:12

• Status changed from In Progress to Resolved

#21 Updated by intrigeri 2016-11-09 10:01:28

• % Done changed from 50 to 100