<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 1/8/2016 5:39 PM, James Sumners wrote:<br>
<blockquote
cite="mid:CAAt=rgCSEGMtOOpONv6MVz=sBEWFze2h-Yr8qw2j_9XE+EyaAg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jan 8, 2016 at 1:13 PM, chip
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:chip.gwyn@gmail.com" target="_blank">chip.gwyn@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Take a
look at Vultr.com, can do it there. They have hosting in
Atlanta too. They're basically the economy choopa stuff.
</blockquote>
</div>
<br>
That's looking rather nice. $5/mo for 1TB of transfer and
plenty of resources for my needs.<br>
</div>
</div>
</blockquote>
Not that I have any horse in the race or anything, but as a cloud
service consumer here's a few of my observations...<br>
<br>
First off, I have/currently use LInode, AWS and DigitalOcean...
Mainly for one simple reason, all 3 providers have good support with
SaltStack so I don't actually have to log into their UI to do
anything to manage my servers from cradle to grave.<br>
<br>
I will say I did look at Vultr and they do have some nice features
and it does appear that Apache libcloud [1] does have support for
Vultr which would make a SaltStack salt-cloud driver realistically
possible though doesn't currently exist. I was really floored by
their benchmark comparisons [2] and how much it was apples and
oranges. I loved how they compare a 768MB/1CPU Vultr system for
$5/month against a 3.75GB/2CPU AWS C3.Large that will run you around
$78/month on-demand or between $29-54/month depending on reserved
instance pricing or their 2GB/2CPU Vultr system for $20/month
against the 3.75GB/1CPU AWS M3.Large with run costs abount $99/month
on-demand and <br>
$39-71/month reserved instance. Comparing against an AWS T2 instance
(nano 512MB/1CPU or micro 1GB/1CPU) would have seemed like better
candidate for comparison against the 768MB Vultr and runs closer
($5/month t2.nano or $10/month t2.micro on-demand or $2-4/month
t2.nano or $6-7/month t2.micro reserved instance). Likewise a
t2.small or t2.medium would have been better comparisons for the 2GB
Vultr. It looked like they went out of their way to pick the most
expensive option to compare so their numbers looked better. I found
a blog [3] that seemed to give a better comparison in fact.<br>
<br>
Otherwise the pricing between DO and Vultr doesn't appear to really
be all that difference comparing plans either. That said I may have
to check out Vultr and see if I can't get the salt-cloud driver
working. Cost being low enough I wouldn't mind throwing some money
at it to get another cloud provider option made available to me. I
like having the ability to launch and deploy my hosts to any
SaltStack supported cloud provider for a DR/BC perspective and keeps
me from being locked into any one provider. Then again I'm not
worried about uploading custom ISO images and if I were I'd simply
build and deploy those to AWS where I could easily make my own AMI
offline and knowing how to work AWS to be cost comparative wouldn't
bother me.<br>
<br>
1.
<a class="moz-txt-link-freetext" href="http://libcloud.readthedocs.org/en/latest/compute/drivers/vultr.html">http://libcloud.readthedocs.org/en/latest/compute/drivers/vultr.html</a><br>
2. <a class="moz-txt-link-freetext" href="https://www.vultr.com/benchmarks/">https://www.vultr.com/benchmarks/</a><br>
3. <a class="moz-txt-link-freetext" href="http://blog.due.io/2014/linode-digitalocean-and-vultr-comparison/">http://blog.due.io/2014/linode-digitalocean-and-vultr-comparison/</a><br>
</body>
</html>