Replace -ms-be0 (@fgiunchedi) with smaller (maybe medium) instances? Both XLARGE! (note: these are both using about 5G of 100G space for Swift, though do seem to have quite a bit of activity)
 Replace -logstash2 (@bd808) with a large instance? XLARGE!
 Replace -tin with a large instance? XLARGE! (note: mira is large)
 Replace -mediawiki with small flavours? We have three, all large!
 Replace -fluorine with a custom small/medium flavour with a large disk size? It's large.
 Delete one or two -elastic (@demon, @EBernhardson, @gehel)? There are four of these, all large!
[*] Delete one or two -parsoid (@Catrope, @ssastry, @mobrovac)? There are four of these, all medium.
 Delete -pdf02 (@jeremyb, @cscott)? only -pdf01 seems used according to MW config (medium)
Replacement instance proposed sizes:
| Existing instance | VCPUs | RAM | Disk | Notes |
| deployment-ms-be0 | 8? | 6-16GB? | 20GB | xlarge VCPUs, medium-xlarge RAM, small disk - need to figure out what these servers are up to |
| deployment-logstash2 | 4 | 16GB? | 80GB? | Large with xlarge RAM - could be smaller right now but needs space for spikes in log size and for active queries bursting CPU and RAM |
| deployment-tin | 4 | 4GB | 80GB | Large with half RAM |
| deployment-mediawiki* | 1 | 2GB | 20GB | Small? Need to figure out what 03 requires when in active use by security |
| deployment-fluorine | 1 | 2GB | 80GB | Small with large disk |
[*] What about merging -changeprop (@mobrovac) into -sca0[1-3]?
[*] What about merging -ores-redis (@ladsgroup) into -redis0?
 Delete -conf03 (@ottomata), -conftool (@joe)?
 Delete one or two -kafka (@ottomata)? There are four of these
 @mmodell, are you using phab-beta?