- welcome everyone!
- we have a code of conduct
- thanks to organisers, sponsors, etc
| Adding people on day one, then ongoing maintenance of them when people move | |
| around teams. | |
| What do people do? | |
| Can people deploy on day one? | |
| Some people do deploy on day one others do not | |
| One person, working on a very small team. We just need your github account | |
| to deploy to live. We invested a lot in the initial setup of the dev environment. | |
| - Very small team |
The following is a semi-automated (or semi-manual, if you're a glass-half-empty person) way of generating terraform state mv commands to move existing resources to new paths.
It does not use a Terraform plan file, as this is often not conveniently available (e.g. when using Terraform Cloud).
Tested with Terraform 0.12, 0.13 and 0.14 output.
Note: if you're not using Terraform Cloud, you might want to try some of the proper tooling other people have built, such as https://github.com/mbode/terraform-state-mover.
I have been wondering for a long time why IRC networks have multiple servers. Wouldn't it be simpler just to use a single server?
One of the problems of having multiple servers is that netsplits can occur. Anybody who has been on IRC for a while will have witnessed one. Hundreds of people suddenly ripped out of the chat. This can also screw up channel and user modes, and 'some people' have been known to wait for netsplits in order to takeover channels or enter password protected channels.
So lets compare situation (A) a single IRC server everyone connects to with the current setup people use (B) multiple servers. Let's say you run an IRC network with u = 40,000 users and n = 20 server nodes that people connect to via round robin DNS (meaning that when people resolve the DNS it gives them a random server from the set of 20 to connect to). These are vaguely realistic numbers modelled after libera.chat.
So in (B) you have roughly u/n = 2000 clients connected