Hi Matt.

We should use real VMs, which means Xen or KVM (no OpenVZ and no SolusVM). I recommend digitalocean even though they're a bit more expensive :)

On Tue, Sep 2, 2014 at 3:59 PM, Matthew Senate <mattsenate@gmail.com> wrote:

Hey all,

What do ya'll think about setting up a couple of development VPSs from the sudo mesh budget?

I'd like to go for one or two of something like this: 

• http://www.ftpit.com/
  • ~$2 / mo for (either)
    • 2 CPU Core | 512 MB RAM | 30 GB Storage | 1 TB Bandwidth | 1 IPv4 | OpenVZ & SolusVM
    • 2 CPU Core | 512 MB RAM | 20 GB Storage (SSD) | 1 TB Bandwidth | 1 IPv4 | OpenVZ & SolusVM

I'm putting some attention in on the exitnode provisioning (and therefore server provisioning in general).

I was thinking about setting up some in-person machines at sudo room for developer training, development environments, testing before deployment, etc. Marc pointed out that the power consumption of such a machine would probably not be worth it given the low cost of a VPS. However, I still want to streamline the process for facilitating new developers to build a smaller version of peoplesopen.net network, and to provide testing infrastructure to maintain reliability and up-time.

I updated this page on the wiki, please contribute: https://sudoroom.org/wiki/Virtual_Private_Server

// Matt

_______________________________________________
mesh mailing list
mesh@lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh

!DSPAM:5406573189101042447563!

mesh mailing list
mesh@lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh


!DSPAM:5406573189101042447563!