We need to buy a new vm to store swift-proxy on anything with 2 cores or higher will do.
Stalling this as i will change this into a buy a separate vm for swift-proxy. I am currently running swift-proxy on nfs1 to try and reduce cpu on swift1 (and load).
Load and cpu are down.
But i want to make sure mw* will stay up with some fixes i just deployed.
Retroactively approved. This is really my fault as I should be able to just give you a budget, and as long as you stay within it, everything should be fine. I did a budget last year, but no one ever looked at it, so I slacked this year.
Genuinely a good idea rather then continually going back and forth all the time. Since our new year technically starts July 22nd (as three years!) if you want to do that, it’ll seriously be used this time around.