Feature #9320

Assistant: Design router for upgrades

Added by sajolida 2015-05-01 09:00:35 . Updated 2015-10-27 09:37:12 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Installation
Target version:
Tails_1.7
Start date:
2015-05-01
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Installation Assistant
Deliverable for:

Description

Files

upgrade-flowchart-20150520.fodg (41603 B) sajolida, 2015-05-20 16:32:38
upgrade-wireframe-20150520.fodg (37081 B) sajolida, 2015-05-20 16:32:42
router-3rd-iteration-upgrade-20150607.fodp (129674 B) sajolida, 2015-06-07 15:27:31
router-upgrade-20150924.fodp (114884 B) sajolida, 2015-09-24 09:14:17
upgrade-flowchart-20150924.fodg (35246 B) sajolida, 2015-09-24 09:14:17

Subtasks

Related issues

Related to Tails - Feature #9319: Assistant: List upgrade scenarios Resolved 2015-05-01

History

#1 Updated by sajolida 2015-05-19 19:23:15

  • Affected tool set to Installation Assistant

#2 Updated by sajolida 2015-05-20 16:32:56

Here is a draft with a flowchart and a wireframe for the first screen.

Please have a look and comment on the general structure. I’ll polish the wireframe, wording, and DVD, VMs, etc. later on once we agree on a basis.

#3 Updated by tchou 2015-05-27 11:11:05

Maybe we could add more details and pictos like in overviews.

For example :

Clone from a friend:
You need a friend with Tails and 15 minutes

- get a trusted up-to-date Tails key

- start a computer with this key

- upgrade your Tails
- it’s done !

Inside Tails :
You need an other USB stick and a lot of time (1 Gb to download in Tails…)

- download the new version of Tails from your current Tails

- install Tails in an other USB stick

- start Tails with this other USB stick

- upgrade
- it’s done !

Outside Tails :
You need an other USB stick

- download the new version of Tails from any computer

- install it in an other USB stick

- start Tails with this USB stick

- upgrade your Tails
- it’s done !

An alternative would be to have a upgrade from ISO path (pro : no need for specific documentation, con: need 2 sticks, but we have other options) :
You need 2 other USB sticks

- download the new version of Tails from any computer

- copy ISO Tails in USB A

- start your current Tails

- install Tails in USB B with ISO from USB A

- start Tails with USB B

- upgrade your Tails
- it’s done !

#4 Updated by tchou 2015-05-27 11:13:38

  • Assignee changed from tchou to sajolida

#5 Updated by sajolida 2015-05-27 15:33:03

  • QA Check changed from Ready for QA to Dev Needed

Thanks for the review, it will be much easier for me to track all this in Redmine.

I probably when too fast on this one and it’s now clear to me that I should include indications of the time and hardware needed like we are doing on the installation router. Still, I don’t want to include the list of steps as I think that this should go in the overview page. Note that this is only the “router” for upgrades, but I consider that we will then have an “overview” for upgrades as we do for installation (the pictos will be roughly the same).

So I’m marking this as Dev Needed again.

#6 Updated by sajolida 2015-05-27 15:40:53

I’ll answer about the alternative technique that you propose for “outside” Tails on Feature #9319 which is more suited.

#7 Updated by sajolida 2015-06-07 15:27:46

Here you go, reusing the work we did for the installation router.

Please review.

#8 Updated by sajolida 2015-06-07 15:28:21

The flowchart is the same.

#9 Updated by tchou 2015-06-10 09:29:01

I had a look to the average global bandwith, and according to Akamai it’s about 4Mbs (http://www.akamai.com/dl/akamai/akamai-soti-q114.pdf?WT.mc_id=soti_Q114) . So I would say half an hour rather than 1 or 2 hours. But, maybe there is some limitations with the mirrors.

Ack for the global mockup.

#10 Updated by tchou 2015-06-10 09:33:17

  • Assignee changed from tchou to sajolida

#11 Updated by sajolida 2015-06-10 11:52:21

  • Assignee changed from sajolida to tchou

Thanks for investigating this!

How did you go from 4Mbs to 30 minutes? Because my calculation still gives me 1 hour based on that number.

Maybe we can advertise 30 to 90 minutes?

Regarding our mirrors, most of them always deliver 1 MB/s and the few slower ones still deliver more than 500 MB/s most of the time.

Do you also feel like investigating the average download bandwidth through Tor to improve our estimates when downloading through Tor. Maybe you can find that information on metrics.torproject.org.

#12 Updated by tchou 2015-06-10 12:44:08

You must be right, I can we a bit confused with MB, Mb, Kbs…

In http://download.stormloader.com/ I used :

- Size of File Download: 971 Megabytes
- Speed of Connection: 4 Mpbs
And the result is Time to download file: 32 minutes

(note : is 0.52 hours half an hour, and not 52 minutes ?)

I compute the average (non-tor) bandwidth for 60% of tor users with https://metrics.torproject.org/userstats-relay-table.html and it’s about 9 Mpbs, more on less our capacity 1 MB (8Mb).

So I would say a bit faster, like 15 to 60 minutes.

#13 Updated by intrigeri 2015-06-10 12:54:17

> Maybe you can find that information on metrics.torproject.org.

IIRC there are stats there for downloading smaller files, but I’m not sure if/how they can be generalized to 1GB files.

#14 Updated by tchou 2015-06-10 13:08:17

According to https://metrics.torproject.org/torperf.html?graph=torperf&start=2015-03-12&end=2015-06-10&source=all&filesize=5mb

I understand that it take from 8 to 17 sec to download a 5 MB file. If we extrapolate (but can we ?) to 971 MB, it’s from 25 to 55 minutes, so 30 to 60 minutes.

If it’s true, it means that it’s more or less the same with and without tor. Kind of strange no ? (or kind of cool).

#15 Updated by tchou 2015-06-10 13:08:51

  • Assignee changed from tchou to sajolida

#16 Updated by intrigeri 2015-06-10 13:46:36

> If it’s true, it means that it’s more or less the same with and without tor. Kind of strange no ? (or kind of cool).

Just my 2cts: this is not surprising to me, and matches my experience in the last 1 year or so. In most situations I am in, Tor is not the limiting factor for bulk HTTP download.

#17 Updated by sajolida 2015-06-11 09:57:31

  • Assignee changed from sajolida to tchou

I freaked out in my hours to minutes convertion: 0.52 hours is 30 minutes and not 52 :) So in the end both our results agree. Let’s put 30-60 minutes for direct download then.

Then what about download through Tor? Do we want to put more time on average. I agree that often Tor is not the limiting factor anymore but it can still be quite slower if you’re out of luck. Shall we say 30-90 minutes over Tor? or 45-90?

#18 Updated by sajolida 2015-06-11 10:03:47

  • related to Feature #9319: Assistant: List upgrade scenarios added

#19 Updated by sajolida 2015-06-11 10:03:57

I research that on metrics.torproject.org and I see: https://metrics.torproject.org/torperf.html?graph=torperf&start=2015-03-13&end=2015-06-11&source=all&filesize=5mb

Downloading a 5 MiB file takes between 7 to 25 seconds over Tor. That’s 30 to 90 minutes for our ISO which is 926 MiB (not MB). So let’s use that.

From this we might then question the fact of proposing the “upgrade outside Tails” scenario. I’ll raise that issue on Feature #9319.

#20 Updated by intrigeri 2015-06-15 03:33:40

  • Status changed from Confirmed to In Progress

#21 Updated by intrigeri 2015-07-01 10:37:33

  • Target version changed from Tails_1.4.1 to Tails_1.5

#22 Updated by tchou 2015-08-06 01:39:27

  • Target version changed from Tails_1.5 to Tails_1.6

#23 Updated by sajolida 2015-08-15 08:18:51

  • Priority changed from Normal to Elevated

Postponed twice, raising priority.

#24 Updated by tchou 2015-09-18 01:28:00

  • Assignee changed from tchou to sajolida

Replied in Feature #9319.

#25 Updated by sajolida 2015-09-18 10:05:02

  • QA Check changed from Ready for QA to Dev Needed

Sure, sorry for having this ticket assigned to you while it was in fact blocked by Feature #9319.

Anyway, we now have:

  • Clone from another Tails
  • Upgrade from Tails (graphical)
  • Upgrade from Tails (command line)
  • Upgrade from outside Tails (minor without detailed instructions)

I should draft a new router for that then.

#26 Updated by sajolida 2015-09-21 10:28:06

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

Postponing and so raising priority.

#27 Updated by sajolida 2015-09-24 09:14:24

Done, please review the LibreOffice attachment.

#28 Updated by sajolida 2015-09-30 09:46:00

  • QA Check changed from Dev Needed to Ready for QA

#29 Updated by tchou 2015-10-27 03:18:28

  • Assignee changed from tchou to sajolida
  • QA Check deleted (Ready for QA)

I’ok with what.

#30 Updated by sajolida 2015-10-27 09:37:12

  • Subject changed from Assistant: Propose router for upgrades to Assistant: Design router for upgrades
  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)

Thanks, so I’m marking this one as resolved (design part) and opening a new ticket for the implementation. That’s Feature #10432.