<p dir="ltr">What are the chances of someone doing a talk on integrating cloud and local services? March is open.</p>
<div class="gmail_quote">On Jan 8, 2016 11:20 PM, "Jeremy T. Bouse" <<a href="mailto:jeremy.bouse@undergrid.net">jeremy.bouse@undergrid.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On 1/8/2016 7:34 PM, Justin Caratzas wrote:<br>
> On 1/8/16 7:23 PM, Jeremy T. Bouse wrote:<br>
>> On 1/8/2016 5:39 PM, James Sumners wrote:<br>
>>> On Fri, Jan 8, 2016 at 1:13 PM, chip <<a href="mailto:chip.gwyn@gmail.com">chip.gwyn@gmail.com</a><br>
>>> <mailto:<a href="mailto:chip.gwyn@gmail.com">chip.gwyn@gmail.com</a>>> wrote:<br>
>>><br>
>>> Take a look at Vultr.com, can do it there. They have hosting in<br>
>>> Atlanta too. They're basically the economy choopa stuff.<br>
>>><br>
>>><br>
>>> That's looking rather nice. $5/mo for 1TB of transfer and plenty of<br>
>>> resources for my needs.<br>
>> Not that I have any horse in the race or anything, but as a cloud<br>
>> service consumer here's a few of my observations...<br>
>><br>
>> First off, I have/currently use LInode, AWS and DigitalOcean... Mainly<br>
>> for one simple reason, all 3 providers have good support with SaltStack<br>
>> so I don't actually have to log into their UI to do anything to manage<br>
>> my servers from cradle to grave.<br>
>><br>
>> I will say I did look at Vultr and they do have some nice features and<br>
>> it does appear that Apache libcloud [1] does have support for Vultr<br>
>> which would make a SaltStack salt-cloud driver realistically possible<br>
>> though doesn't currently exist. I was really floored by their benchmark<br>
>> comparisons [2] and how much it was apples and oranges. I loved how they<br>
>> compare a 768MB/1CPU Vultr system for $5/month against a 3.75GB/2CPU AWS<br>
>> C3.Large that will run you around $78/month on-demand or between<br>
>> $29-54/month depending on reserved instance pricing or their 2GB/2CPU<br>
>> Vultr system for $20/month against the 3.75GB/1CPU AWS M3.Large with run<br>
>> costs abount $99/month on-demand and<br>
>> $39-71/month reserved instance. Comparing against an AWS T2 instance<br>
>> (nano 512MB/1CPU or micro 1GB/1CPU) would have seemed like better<br>
>> candidate for comparison against the 768MB Vultr and runs closer<br>
>> ($5/month t2.nano or $10/month t2.micro on-demand or $2-4/month t2.nano<br>
>> or $6-7/month t2.micro reserved instance). Likewise a t2.small or<br>
>> t2.medium would have been better comparisons for the 2GB Vultr. It<br>
>> looked like they went out of their way to pick the most expensive option<br>
>> to compare so their numbers looked better. I found a blog [3] that<br>
>> seemed to give a better comparison in fact.<br>
> Slight disagreement, I believe the t2.* are terrible machines to<br>
> benchmark, given the cpu bursting budget. m3/4.mediums would have been<br>
> the better comparison, the Cs are a bit nuts w/ pricing.<br>
Yes, the t2 instances are burstable but they are better than the older<br>
generate t1 instances. If you're comparing cost however the t2 would be<br>
a better comparison as the specs are closer as is the cost. When you're<br>
comparing a $5 instance to a $78 instance your "Performance per dollar"<br>
is obviously not going to be comparable. The C3 instances are more CPU<br>
optimized instances, the M3 and M4 are more general purpose with<br>
balanced CPU & memory with the M3 being SSD-based instances which is<br>
really the only comparison against DO or Vultr with the minimum in the<br>
series being the m3.medium which has 1 CPU and 3.75GB RAM and 4GB SSD.<br>
> How do you like libcloud? I've been meaning to check it out.<br>
I haven't worked with it directly myself. Many of the salt-cloud<br>
provider drivers are written utilizing it as it provides a quick method<br>
to do so. There are still many drivers that have libcloud support<br>
available but still don't utilize it. In most of the cases the drivers<br>
were written prior to libcloud support and hasn't been any real need to<br>
re-write them yet. I'm currently working with another cloud provider<br>
that doesn't have libcloud support so we're having to do a lot more of<br>
the work going off API documentation from the provider as the only API<br>
library we've been able to find for it is not fully up to the task.<br>
>> Otherwise the pricing between DO and Vultr doesn't appear to really be<br>
>> all that difference comparing plans either. That said I may have to<br>
>> check out Vultr and see if I can't get the salt-cloud driver working.<br>
>> Cost being low enough I wouldn't mind throwing some money at it to get<br>
>> another cloud provider option made available to me. I like having the<br>
>> ability to launch and deploy my hosts to any SaltStack supported cloud<br>
>> provider for a DR/BC perspective and keeps me from being locked into any<br>
>> one provider. Then again I'm not worried about uploading custom ISO<br>
>> images and if I were I'd simply build and deploy those to AWS where I<br>
>> could easily make my own AMI offline and knowing how to work AWS to be<br>
>> cost comparative wouldn't bother me.<br>
>><br>
>> 1. <a href="http://libcloud.readthedocs.org/en/latest/compute/drivers/vultr.html" rel="noreferrer" target="_blank">http://libcloud.readthedocs.org/en/latest/compute/drivers/vultr.html</a><br>
>> 2. <a href="https://www.vultr.com/benchmarks/" rel="noreferrer" target="_blank">https://www.vultr.com/benchmarks/</a><br>
>> 3. <a href="http://blog.due.io/2014/linode-digitalocean-and-vultr-comparison/" rel="noreferrer" target="_blank">http://blog.due.io/2014/linode-digitalocean-and-vultr-comparison/</a><br>
<br>
<br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div>