Catalog and patch servers

[jdno]

The infra-team operates a handful of physical and virtual servers. These are on various different patch levels, with some running unsupported software versions. We should go through our infrastructure, catalog the machines that we operate and their operating systems, and update the installed software packages.

For machines that run unsupported operating systems, e.g. Ubuntu 18.04, we should plan and perform a manual upgrade to the next supported version.

The list of machines and their OS versions can be used in a following task to ensure all servers run on the same/latest operating system.

[MarcoIeni]

I started working on this.

Things to check

• add other things to check

Patch servers

• playground
• dev desktops
• ...

GCP

Ansible

• check ansible

Azure

• check azure

AWS

For the following accounts, cross-reference what's in aws and terraform (in all regions). Using tag explorer or cost explorer might help.

AWS accounts:

• bors-prod. docs: document bors #123. Used regions:

  • us-east-1
  • us-east-2

• crates-io-prod (region us-east-1). It's basically empty. docs: document crates-io-logs #129

• dev-desktops-prod. Already covered in the docs.

  • should I update the operating systems?

• docs-rs-staging. I'm not documenting this because it's unused.

• rust admin (aka legacy)

  • terragrunt:

    • crates-io-prod docs: document the rest of crates-io infra #130
    • datadog-aws docs: link datadog integrations #131
    • datadog-fastly docs: link datadog integrations #131
    • releases-prod docs: document releases #132
    • rustup-prod docs: document rustup #137

  • terraform:

    • bastion docs: document bastion #139
    • bors docs: document homu #138
    • crater. Also look in gcp to check resources there.
    • crates-io-heroku-metrics docs: document the rest of crates-io infra #130
    • dev-desktops already documented
    • discord-mods-bot docs: document discord mods bot #141
    • dns
    • dns-delegation
    • docs-rs
    • domain-redirects
    • fastly-exporter docs: document fastly-exporter #143
    • monitorbot
    • playground
    • rds-databases
    • releases docs: document releases #132
    • rust-forge
    • rust-log-analyzer
    • rustc-ci
    • rustc-perf
    • shared
    • team-members-access
    • team-members-datadog
    • team-members-fastly
    • team-repo docs: add sync-team to the service catalog #124

• sync-team-prod (us-east-1, us-east-2). I'm not documenting this because it's unused from what JD told me.

Personal notes

Tasks

Ansible configures the things you provision in terraform.

• look at simpleinfra/ansible/playbooks

To remember

I found useful to:

1. download csv from tag explorer
2. use nushell: open resources.csv | group-by Region

Questions

• why does bors-prod uses two regions?
• why aren't crates-io logs present in the crates-io-prod account?
• Why do we have both https://github.com/rust-lang/simpleinfra/tree/master/terragrunt/accounts/sync-team-prod and https://github.com/rust-lang/simpleinfra/tree/master/terraform/team-repo ? Some files are almost the same, e.g. https://github.com/rust-lang/simpleinfra/blob/master/terraform/team-repo/sync-team.tf and https://github.com/rust-lang/simpleinfra/blob/master/terragrunt/modules/sync-team/sync-team.tf