|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "2019-10-22 Infrastructure Team Meeting" |
| 4 | +author: Pietro Albini |
| 5 | +team: the infrastructure team <https://www.rust-lang.org/governance/teams/operations#infra> |
| 6 | +--- |
| 7 | + |
| 8 | +Meeting run by pietroalbini. Mintues written by pietroalbini. |
| 9 | +Attending: aidanhs, alexcrichton, kennytm, Mark-Simulacrum, pietroalbini, |
| 10 | +shepmaster |
| 11 | +[Start of the conversation][discord] |
| 12 | + |
| 13 | +[discord]: https://discordapp.com/channels/442252698964721669/443148319431065610/636247640794857472 |
| 14 | + |
| 15 | +## News from the team |
| 16 | + |
| 17 | +- All the AWS resources related to the bastion are now managed with Terraform. |
| 18 | + The documentation on [how to add whitelisted IPs][bastion-whitelist] has |
| 19 | + also been updated. |
| 20 | +- Crater agents are now deployed with Ansible, and the related AWS resources |
| 21 | + are now managed with Terraform. Agents are configured to check for updates |
| 22 | + every 5 minutes. |
| 23 | +- There was an outage of docs.rs on Sunday night, the postmortem is going to be |
| 24 | + published soon on the "Inside Rust" blog and work on the action items from it |
| 25 | + is ongoing. |
| 26 | + |
| 27 | +[bastion-whitelist]: https://github.com/rust-lang/infra-team/blob/master/docs/hosts/bastion.md#updating-the-whitelisted-ips |
| 28 | + |
| 29 | +## Putting a CDN in front of the CI S3 buckets (pietroalbini) |
| 30 | + |
| 31 | +After an audit of our bandwidth usage for the `rust-lang-ci-sccache2` and |
| 32 | +`rust-lang-ci-mirrors` S3 buckets we discovered CI is pulling respectively 8.3 |
| 33 | +TB and 1.4 TB from them each month. Egress from S3 is pricey (0.09$/GB), while |
| 34 | +for us egress from CloudFront is way cheaper (0.04$/month, as across all of our |
| 35 | +distributions we transfer out more than 150 TB each month). Putting CloudFront |
| 36 | +in front of them is going to save us an estimate of 485$/month. |
| 37 | + |
| 38 | +Thankfully all the data in those buckets is immutable (mirrors are versioned |
| 39 | +and all caches are addressed by hash), so there are not going to be any |
| 40 | +problems due to cache invalidation. Sccache doesn’t support querying a CDN yet |
| 41 | +but aidanhs is going to write some pointers and pietroalbini is going to do the |
| 42 | +implementation work. The caches CDN is also going to query a new |
| 43 | +`rust-lang-ci-caches` bucket, to avoid the old naming scheme. |
| 44 | + |
| 45 | +pietroalbini already setup |
| 46 | +[ci-mirrors.rust-lang.org](https://ci-mirrors.rust-lang.org), and is going to |
| 47 | +do the implementation work to both create a CDN distribution for caches and |
| 48 | +switch the CI to query the CDN. |
| 49 | + |
| 50 | +## Moving infra documentation to the forge (pietroalbini) |
| 51 | + |
| 52 | +There is an effort in the project to centralize all the internal documentation |
| 53 | +[on the forge](https://forge.rust-lang.org). pietroalbini proposed to move all |
| 54 | +the infra team documentation to it. Everyone agreed, as we find value in having |
| 55 | +everything reachable in a single place. aidanhs pointed out that meeting |
| 56 | +minutes should not be migrated on the forge. |
| 57 | + |
| 58 | +## Next meeting time |
| 59 | + |
| 60 | +Europe will switch DST next week, so the next meeting will be at -1 hours for |
| 61 | +europeans and at the same time for everyone else on the team. |
0 commit comments