[tor-bugs] #31239 [Internal Services/Tor Sysadmin Team]: automate installs

Tor Bug Tracker & Wiki blackhole at torproject.org
Thu Feb 13 22:21:25 UTC 2020


#31239: automate installs
-------------------------------------------------+-------------------------
 Reporter:  anarcat                              |          Owner:  anarcat
     Type:  enhancement                          |         Status:
                                                 |  assigned
 Priority:  Low                                  |      Milestone:
Component:  Internal Services/Tor Sysadmin Team  |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tpa-roadmap-february                 |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Old description:

> right now, installing machines is mostly a manual, or semi-manual
> process: we install debian, preferably with crypto, and then do stuff on
> top.
>
> some of it is done by hand, some is done in puppet.
>
> we should have a standardized install process that gives us a
> reproducable, identical install across platforms. then Puppet is what
> customizes the machine on top of that.
>
> this ticket aims at documenting what we already have and where we could
> possibly go. this is one of the question we answered "no" on in the "ops
> questionnaire" in #30881. see also the automated upgrade part in #31957.

New description:

 right now, installing machines is mostly a manual, or semi-manual process:
 we install debian, preferably with crypto, and then do stuff on top.

 some of it is done by hand, some is done in puppet.

 we should have a standardized install process that gives us a
 reproducable, identical install across platforms. then Puppet is what
 customizes the machine on top of that.

 this ticket aims at documenting what we already have and where we could
 possibly go. this is one of the question we answered "no" on in the "ops
 questionnaire" in #30881. see also the automated upgrade part in #31957.

 When we started this work, the installer had this many manual steps:

  * new-machine (common trunk): 14 steps
  * new-machine-hetzner-robot: +43 steps (57 total)
  * new-machine-hetzner-cloud: +21 steps (35 total)

--

Comment (by anarcat):

 Document how many steps we had when we drew the diagrams:

 > When we started this work, the installer had this many manual steps:
 >
 > * new-machine (common trunk): 14 steps
 > * new-machine-hetzner-robot: +43 steps (57 total)
 > * new-machine-hetzner-cloud: +21 steps (35 total)

 Now we're at:

  * new-machine (common trunk): 13 steps (3 steps possibly obsolete, 4 more
 being worked on)
  * new-machine-hetzner-robot: +25 steps left (38 total)
  * new-machine-hetzner-cloud: +21 steps (35 total, unchanged, needs to
 merge with setup-storage process)

 i.e. we have eliminated a whopping 19 steps, most of which through the
 setup-storage refactoring.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31239#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list