Opened 8 months ago

Closed 5 months ago

#33387 closed task (fixed)

establish tmpfs policy

Reported by: anarcat Owned by: anarcat
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords: tpa-roadmap-may
Cc: Actual Points:
Parent ID: #31239 Points:
Reviewer: Sponsor:

Description

our tmpfs configuration varies wildly across the infrastructure. some hosts have "defaults" (which is 50% of available ram), others have 2GB, 1GB, 4GB, but most have 512m available. The latter is what our current install procedures sets up, and seems rather small for a tmpfs.

I set the latter in the current install scripts, with the following commitlog:

switch to 512m tmpfs

The tmpfs configuration actually varies wildly:

 * 512m: (37) alberti.torproject.org,cache-02.torproject.org,carinatum.torproject.org,chiwui.torproject.org,colchicifolium.torproject.org,crm-ext-01.torproject.org,cupani.torproject.org,eugeni.torproject.org,forrestii.torproject.org,fsn-node-[01-03].torproject.org,gayi.torproject.org,gitlab-01.torproject.org,henryi.torproject.org,hetzner-hel1-02.torproject.org,hetzner-nbg1-02.torproject.org,mandos-01.torproject.org,materculae.torproject.org,meronense.torproject.org,neriniflorum.torproject.org,nevii.torproject.org,omeiense.torproject.org,oo-hetzner-03.torproject.org,palmeri.torproject.org,pauli.torproject.org,perdulce.torproject.org,polyanthum.torproject.org,rouyi.torproject.org,rude.torproject.org,savii.torproject.org,staticiforme.torproject.org,subnotabile.torproject.org,troodi.torproject.org,vineale.torproject.org,web-cymru-01.torproject.org,web-hetzner-01.torproject.org
 * 512m: (1) build-x86-09.torproject.org
 * 512m: (2) build-x86-[05-06].torproject.org
 * 1g: (1) crm-int-01.torproject.org
 * 1g: (1) scw-arm-par-01.torproject.org
 * 2g: (1) build-x86-08.torproject.org
 * 2g: (1) build-x86-07.torproject.org
 * 4g: (5) bungei.torproject.org,kvm[4-5].torproject.org,macrum.torproject.org,unifolium.torproject.org
 * "defaults": (21) bacula-director-01.torproject.org,cache01.torproject.org,cdn-backend-sunet-01.torproject.org,chives.torproject.org,corsicum.torproject.org,gettor-01.torproject.org,gitlab-02.torproject.org,hetzner-hel1-[01,03].torproject.org,hetzner-nbg1-01.torproject.org,loghost01.torproject.org,nutans.torproject.org,onionbalance-01.torproject.org,onionoo-backend-01.torproject.org,onionoo-frontend-01.torproject.org,orestis.torproject.org,static-master-fsn.torproject.org,submit-01.torproject.org,tbb-nightlies-master.torproject.org,web-fsn-[01-02].torproject.org
 * "defaults": (1) build-arm-10.torproject.org

List extracted with:

    cumin '*' 'grep tmpfs /etc/fstab'

Since 512m is the most common one (and especially the one currently in
use by fsn-node-XX), let's adopt it for now, and we can revise later.

Note that the 512m configuration in the robot instructions in the wiki
seem to come from:

e48b7699645dfc137e73d937ca0f1a9c74dbbf3f iterate on new-machine-hetzner-robot.mdwn

... which does not include a rationale for the setting.

The setting is also present in the `tor-install-hetzner` script,
introduced in:

33a552a049c32227fb1599a5437077f45eaa27e6 Add tor-install-hetzner script

... which also doesn't include a rationale.

But it would be nice to find a more uniform policy here.

Child Tickets

Change History (4)

comment:1 Changed 8 months ago by anarcat

Keywords: tpa-roadmap-april added; tpa-roadmap-february removed

comment:2 Changed 5 months ago by anarcat

Keywords: tpa-roadmap-may added; tpa-roadmap-april removed

comment:3 Changed 5 months ago by anarcat

Owner: changed from tpa to anarcat
Status: newassigned

comment:4 Changed 5 months ago by anarcat

Resolution: fixed
Status: assignedclosed

after discussing this briefly with weasel, he suggested we set to the smallest of 2GB or 50% of ram, but that might be hard to implement in the installer. because 2GB might be too big for some hosts, leave this at 512MB for now.

Note: See TracTickets for help on using tickets.