Re: Lot of snapshots in AWS Sydney region

2023-07-12 Thread Dusty Mabe
On 7/12/23 19:03, Miroslav Suchý wrote: > Dne 13. 07. 23 v 0:26 Dusty Mabe napsal(a): >> If you say it's an issue then hopefully we can give this some priority and >> get to it soon. >> >> Removing the "old ones" isn't that easy to do. Our production AMIs and >> development AMIs are all mixed

Re: Lot of snapshots in AWS Sydney region

2023-07-12 Thread Miroslav Suchý
Dne 13. 07. 23 v 0:26 Dusty Mabe napsal(a): If you say it's an issue then hopefully we can give this some priority and get to it soon. Removing the "old ones" isn't that easy to do. Our production AMIs and development AMIs are all mixed together so it would be hard to come up with a criteria

Re: Lot of snapshots in AWS Sydney region

2023-07-12 Thread Dusty Mabe
On 7/12/23 16:17, Miroslav Suchý wrote: > Dne 11. 07. 23 v 15:53 Dusty Mabe napsal(a): >> Apologies for not responding sooner. Actually for some reason this is the >> first email I've seen >> in the thread so maybe I need to check my spam filters. Either way, >> apologies. >> >> The reason you

Re: Lot of snapshots in AWS Sydney region

2023-07-12 Thread Miroslav Suchý
Dne 11. 07. 23 v 15:53 Dusty Mabe napsal(a): Apologies for not responding sooner. Actually for some reason this is the first email I've seen in the thread so maybe I need to check my spam filters. Either way, apologies. The reason you are seeing snapshots but no volumes is because these

Re: batcave01 move to rhel9 - 2023-07-13 21UTC

2023-07-12 Thread Stephen Smoogen
On Wed, 12 Jul 2023 at 12:40, Kevin Fenzi wrote: > Hey folks. I keep putting it off, but I need to move it forward, so I am > proposing to move batcave01 to rhel9 tomorrow, starting at 21UTC. > > My plan is roughly: > > reviewed and +1. [I am not sure I will be awake enough to help out at

batcave01 move to rhel9 - 2023-07-13 21UTC

2023-07-12 Thread Kevin Fenzi
Hey folks. I keep putting it off, but I need to move it forward, so I am proposing to move batcave01 to rhel9 tomorrow, starting at 21UTC. My plan is roughly: - sync data from batcave01 to batcave02 - at 21UTC take down services on batcave01 - sync data again - take batcave01 down. - rename