Project

General

Profile

Feature #17412

Drop the need for dedicated temporary storage space for IUKs on rsync.lizard

Added by intrigeri about 1 month ago. Updated 11 days ago.

Status:
Needs Validation
Priority:
Elevated
Assignee:
Category:
Infrastructure
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
doc/17415-fix-IUK-generation-in-release-process
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

That's the second step of #17385#note-2, i.e. make it so temporary data is stored directly in /srv during the release process.

One idea could be to:

  1. give every RM permission to SSH into rsync.lizard as the rsync_tails user, and point $HOME for this user somewhere under /srv
  2. adjust the release process so that all SSH operations done on rsync.lizard are done as the rsync_tails user
  3. drop the /home LV and migrate the corresponding data back to /

Related issues

Related to Tails - Feature #17385: Grow /home on rsync.lizard Resolved
Related to Tails - Feature #15287: Make it possible to reproducibly generate IUKs in CI Resolved 02/05/2018
Blocks Tails - Feature #13242: Core work: Sysadmin (Maintain our already existing services) Confirmed 06/29/2017

Associated revisions

Revision 4eb681c4 (diff)
Added by intrigeri 26 days ago

Release process: drop the need for allocating (duplicated) temporary storage space for IUKs on rsync.lizard (refs: #17412)

Previously, we would copy the IUKs to /home and then move them to /srv/rsync.
Given these 2 directories are on different storage volumes, this means
we had to allocate the corresponding storage space twice.

Let's instead directly copy the IUKs to /srv.

History

#1 Updated by intrigeri about 1 month ago

  • Blocks Feature #13242: Core work: Sysadmin (Maintain our already existing services) added

#2 Updated by intrigeri about 1 month ago

#3 Updated by intrigeri about 1 month ago

  • Related to Feature #15287: Make it possible to reproducibly generate IUKs in CI added

#4 Updated by intrigeri about 1 month ago

  • Priority changed from Normal to Elevated

#5 Updated by intrigeri 26 days ago

  • Status changed from Confirmed to In Progress
  • Feature Branch set to doc/17415-fix-IUK-generation-in-release-process

#6 Updated by intrigeri 26 days ago

  • Status changed from In Progress to Needs Validation
  • Assignee changed from intrigeri to anonym
  • Type of work changed from Sysadmin to Code

In the end I did it differently: instead of a new, dedicated user, I've adjusted our code & release process to use a work directory under /srv.

#7 Updated by anonym 11 days ago

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

Also available in: Atom PDF