Opened 5 weeks ago

Last modified 2 weeks ago

#31659 new defect

new onionoo hosts

Reported by: weasel Owned by: tpa
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: irl, metrics-team Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Right now we have two onionoo backends (that run the java stuff) and also serve users, and two additional frontend-only hosts (that only serve users and ask the backends if they don't have a cached answer). So we have 4 hosts in total, two of which serve a double role.

To make the setup easier to monitor, scale, and maintain we should split these roles. For communications between frontends and backends we'll switch to using ipsec rather than the stunnels.

As a first step, we'll set up a new backend-only host (on Debian 10/buster) and Iain will set up the service there.

Child Tickets

TicketStatusOwnerSummaryComponent
#31952closedmetrics-teamjavax.xml.bind is not longer part of the JREMetrics/Onionoo
#31953needs_informationmetrics-teamIllegalStateException on fresh instancesMetrics/Onionoo

Change History (5)

comment:1 Changed 5 weeks ago by weasel

Onionoo on oo-hetzner-03 and on omeiense use about 40gb (each) of disk space and about 8-9GB of ram.

comment:2 Changed 5 weeks ago by weasel

Cc: irl added

irl, the host onionoo-backend-01.torproject.org should be ready for you.

I suggest you use systemd user services instead of @reboot cronjobs. lingering is already enabled for both roles.

Please let us know when we can proceed.

comment:3 Changed 5 weeks ago by irl

Adding to the Metrics roadmap, but probably for next week's sprint at the earliest.

comment:4 Changed 4 weeks ago by karsten

Cc: metrics-team added

comment:5 Changed 2 weeks ago by weasel

ping

Note: See TracTickets for help on using tickets.