Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #32902

Closed (moved)
(moved)
Open
Created Jan 08, 2020 by anarcat@anarcat

document the current install workflow visually

After discussing the problem of automating installs with hiro, it became clear it would be quite useful to better understand the different workflows we currently have in place.

This could be done with a flowchart with the first decision point branching into the various install systems we have (hetzner cloud, hetzner robot, generic baremetal (say at cymru), ganeti).

The diagram should document every step taken by the various processes documented in the new-machine document. the first decision point would branch into the following pages:

  • new-machine-hetzner-cloud
  • new-machine-hetzner-ganeti
  • ganeti new instance

In the first two cases, we should also expand the install scripts from tsa-misc, specifically:

  • tsa-misc/installer/tor-install-hetzner - for hetzner-cloud
  • tsa-misc/installer/tor-install-format-disks - for hetzner-robot
  • tsa-misc/installer/tor-install-luks-setup - for hetzner-robot

We should also cover new-machine-mandos somehow in there.

Bits that should/could be automated should eventually be created as sister tickets here, but for now this should focus on just documenting the actual process in a diagram.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking