<div dir="ltr">Amos<br>I'm using slicehost for a few projects and I'm extremely satisfied. Response time from Israel is outstanding - for Web and ssh. They setup a new slice in minutes and their customer service is rackspace quality<br>
<br><br>Danny<br>-- <br>Danny Lieberman<br>-------------------------------------------------------------------------------------------------<br><a href="http://www.software.co.il">www.software.co.il</a> - Buggy software is risky software<br>
-------------------------------------------------------------------------------------------------<br><div class="gmail_quote"><br>On Tue, Mar 10, 2009 at 11:29 AM, Amos Shapira <span dir="ltr"><<a href="mailto:amos.shapira@gmail.com">amos.shapira@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2009/3/5 Ira Abramov <<a href="mailto:Lists-Linux-IL@ira.abramov.org">Lists-Linux-IL@ira.abramov.org</a>>:<br>
> I've been waiting for KVM to hit the prime-time for a while, I remember<br>
> Mulix told me a year ago it's "Xen done the right way" and it should be<br>
<br>
I'm waiting for it to - but in the meantime I still need to Get Things<br>
Done so I stick to whatever comes pre-packaged and supported with my<br>
SOE distro - namely Xen (3.0) on CentOS 5.<br>
<br>
I haven't touched Xen before I started using with it for my current<br>
job and don't remember that it was an issue to get on top of it and<br>
start cranking out platforms for our product.<br>
<br>
CentOS 5.4 is scheduled to include KVM so I plan to start playing with<br>
that as soon as it comes out, in parallel to sticking with Xen for<br>
production and generally switch to KVM when I feel comfortable and it<br>
becomes officially supported.<br>
<br>
Right now I got my toolset working around Xen 3.0's limitations and am<br>
generally content with the result. We manage to auto-redeploy complete<br>
environments in about an hour of running scripts. One script execution<br>
per virtual host (7 unique hosts for now, total of 14 on two xen hosts<br>
for HA and scalability, more to come soon).<br>
<br>
("auto-redeploy" means that we rebuild the image from scratch for<br>
every version upgrade (starting at kickstart with a "%post" script<br>
inside an "xm create" with automatically crafted configuration files),<br>
that way we can be sure that what we have in dev, qa, staging is<br>
exactly the same as what we have in production)<br>
<br>
Maybe we should take another look at libvirt if we'll stick to our own<br>
servers instead of moving into the cloud (which we keep looking at).<br>
I'm a Perl guy and get sick from Python's indent-to-enclose but might<br>
have to live with it.<br>
<br>
Speaking of cloud platforms - Amazon is not the only game in town,<br>
there are also:<br>
1. Slicehost<br>
2. GoGrid<br>
3. scalr (<a href="http://code.google.com/p/scalr/" target="_blank">http://code.google.com/p/scalr/</a>) - an open source interface<br>
to AWS turned into a commercial service too.<br>
<br>
These are the ones I can remember off the top of my head right now.<br>
<br>
--Amos<br>
<br>
_______________________________________________<br>
Linux-il mailing list<br>
<a href="mailto:Linux-il@cs.huji.ac.il">Linux-il@cs.huji.ac.il</a><br>
<a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
</blockquote></div><br><br clear="all"><br><br>
</div>