Testing Out Vultr
-
So after the crash and burn of our lab cloud computing service provider, we at NTG are taking some time to put in the effort to test out some other providers. Today we are testing out Vultr. Vultr targets low cost, high global diversity and provides Windows. Vultr provides a $5 credit to people signing up for a new account so that you can test our their platform. This is enough to experiment with several products over a few days or run their smallest VM for an entire month or their next smallest for about eighteen days.
The available operating system selection on Vultr is very good with CentOS, Ubuntu, FreeBSD, CoreOS, Debian and Windows all available. The only major OS that I feel is missing in OpenSuse.
Rather than talk about Vultr, about which I do not have too much to say as we are just testing them out now, I figured that a series of screenshots would answer most questions that people might have about them.
Building our first instance was effectively instantaneous. It took no time whatsoever. As soon as I look at the web page, it was already ready and waiting for me.
Vultr runs on KVM.
-
First system is built. CentOS 7 ready for testing.
-
-
-
-
-
-
-
-
-
-
Nice, easy to use console too. So well suited for SMBs and VPS usage.
-
Well, they look professional.
-
After the first install, I did a yum update and the system was already totally patched on initial install. Woot. Small, but a nice touch.
-
Thanks for posting screenies.
-
The use of SSH Keys is very nice too and very much required for normal cloud usage. Without it, access would be a problem. With the integrated keys, you build an instance and can access it, without a password, instantly from your normal SSH client. I've gotten used to this with the enterprise clouds and it is a feature I do not like to be without. Very glad to see that here.
-
-
The support custom ISOs as well, which is a nice feature.
-
I like that we have IPv6 too. And Reverse DNS management too.
-
Some post install details:
# free -m total used free shared buff/cache available Mem: 993 81 376 12 535 763 Swap: 0 0 0
By default, no swap space is installed. Not an uncommon way to go. Only 81MB used after install process and a few packages installed (sysstat, htop, fail2ban, etc.) So this is memory usage after SAR is running.
EPEL is installed on initial install and does not need to be added.