Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 971
    • Issues 971
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #17412
Closed
Open
Issue created Jan 09, 2020 by intrigeri@intrigeriMaintainer

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

Originally created by @intrigeri on #17412 (Redmine)

That’s the second step of sysadmin#17385 (comment 3031), 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 sysadmin#17385 (closed)
  • Related to #15287 (closed)
Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking