Closed jwflory closed 6 years ago
Let's address this at the eboard meeting tomorrow.
@jflory7 I am blocked on this because I don't have access to Titan so I have no clue what's on there, nor how much space they take up
Here is what I see in Proxmox
@Serubin From this list that @axk4545 dug out, we can exclude 105 and 301.
I am reassigning this to you, and we can work out billing to see if we can fit it into this semester for some of 2018.
I'm closing this ticket as complete. We know we don't want to back up 105 and 301. We need to process payments for backups this week if we will fit it into the budget for this semester. If we cannot get an EAF form process started, we won't be able to pay for the backups until next semester.
@Serubin asked RITlug to help support the costs of backups on Titan, the primary hosted server for RITlug. We want to complete this payment by the end of this semester to effectively use the remainder of our budget.
@axk4545 and @ct-martin need to pass @Serubin a list of VMs to not back up in the backup scheme. Some especially large VMs are easily reproduced with Ansible and do not contain persistent data.
Once this is done, @Serubin can work closer with us on expensing the backups and ideally paying for a long-term option with the remainder of our club budget. I chose critical priority because this is timeboxed to this semester – our budget may expire by May and we are awarded a new budget from RIT Clubs Office in the fall 2018 semester otherwise.