On 2020-01-24 07:02:23, Michael Crusoe wrote: > On Fri, Jan 24, 2020, 06:18 Andreas Tille <tille@debian.org> wrote: > > On Thu, Jan 23, 2020 at 08:35:30PM -0500, Noah Meyerhans wrote: > > On Thu, Jan 23, 2020 at 10:15:33PM +0100, Andreas Tille wrote: > > > > Currently the machine has 16GB memory 200GB sdd. From current usage > > > > the minimum requirement is 8GB memory (16 is certainly better since > > > > it is running a UDD clone and teammetrics database) and 80GB sdd. > > > > > > > > Is there anybody who could offer such a machine for long term usage. > > > > Yes, in general this is something we can and should do. We haven't done > > this yet in the new SPI-owned AWS accounts, which are the right ones to > > use here (assuming we decide to use AWS; obviously there are other > > options), so there are some administrative and technical details to work > > out. > > > > How soon do you need this? > > Michael was asking for prolongation but the old contract he was caring > for was ending 24 days ago (without notice to him). :-( > > I've gotten an extension to the end of the month! This month? It's 7 days, I suppose it's enough time to migrate 1 server if it's permissable to have downtime, but I'm not sure how ready we are with hosting this in one of the 'new' accounts. Looks like we have slightly bigger control over AWS then GCP accounts so probably if time is an essence AWS can be a solution. Tho, I'm not sure how the decision making process is working now (if we have one TBH). I'd say in the worst case scenario you could host it on one of the old accounts and then migrate it out to the final one if it's not ready right now. Hopefully you've got this automated :-) -- |_|0|_| | |_|_|0| "Panta rei" | |0|0|0| -------- kuLa -------- | gpg --keyserver pgp.mit.edu --recv-keys 0x686930DD58C338B3 3DF1 A4DF C732 4688 38BC F121 6869 30DD 58C3 38B3
Attachment:
signature.asc
Description: PGP signature