ooni / ooni/devops

Epic: Discontinue, migrate or document legacy hosts

Open
#120 0 comments 0 reactions 4 assignees View on GitHub

@LDiazN is already working on this.

Since Jan 28, 2025.

epic funder/otffoss2025 priority/medium
Dominant language
HCL
Stars
4
Forks
15
Avg merge
1h 50m
Merged PRs (30d)
4

Description

We did a inventory of all of our current infrastructure to plan this area of work.

Highest priority is discontinuing things on eclipsis so that we are able to fall within the new 50 credits/month tier.

Greenhost (ghs)

  • ams-wcth2.ooni.nu (37.218.245.117) -> machine killed
  • ams-wcth3.ooni.nu (37.218.247.47) -> machine killed
  • api-test-geoip (37.218.244.46) 54.10 -> machine killed
  • greenhost-beacon.ooni.org (37.218.243.110) 7.40 -> machine killed
  • explorer-redirector.ooni.nu (37.218.242.29) 24.50 -> machine killed
  • migration of other services tracked in: https://github.com/ooni/devops/issues/121

Hetzner (htz)

  • monitoring.ooni.org 38 -> playbook migration complete. Should eventually migrate jupyter over to notebook.ooni.org. TODO figure out how to monitor nodes in AWS.
  • backend-fsn.ooni.org 116 -> Should be moved to EC2
  • backend-hel.ooni.org 130 -> Is stopped and should be terminated
  • data1.htz-fsn.prod.ooni.nu 122 -> New clickhouse cluster node. Hot primary replicated host. Setup complete.
  • data2.htz-fsn.prod.ooni.nu 129 -> New clickhouse cluster node. Hot secondary replicated host. Keep, but needs to be re-initialized not doing this for now
  • notebook.ooni.org 36 -> New jupyter notebook server. Setup complete.
  • data3.htz-fsn.prod.ooni.nu -> New clickhouse cluster. Cold backup replicated store with slow drives. Setup complete.
AWS
  • Consolidate microservices into bigger ones
  • #337
  • Move secrets manager to parameter store
  • Look into task memory allocations and consider dropping them
  • Monitoring of ECS cluster and EC2 nodes
Digital Ocean
  • wcth-prod[0-2]
  • wcth-dev
  • countly -> running a very out of date version (deprecated)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.