Alex,

You may also want to take a look at OpenShift (https://github.com/openshift).  
Rather than VMs, they separate applications using SELinux controls which leads 
to far greater densities.  This approach has allowed them to support a number 
of unique features (such as SSH access for each account) that are not available 
on other platforms.

Thanks,
-John

On Dec 4, 2012, at 12:05 PM, Alex Heneveld <alex.henev...@cloudsoftcorp.com> 
wrote:

> 
> Hi folks--
> 
> To get the ball rolling here are a few questions on design/features.  And my 
> answers, in order to kick off the argument discussion this needs!  I'll 
> collate and post at #576.
> 
> 
> *(1) Should we try for an AWS or vApp look-alike?  Or build something around 
> Cloudstack concepts?*
> 
> Something new and lightweight based around Cloudstack, taking the best of the 
> others.
> 
> Cloudstack concepts (networking, service offerings) have evolved a lot since 
> EC2 and are more expressive.  If we try to mimic something else too much 
> we'll end up with a poorly fitting shoe.
> 
> A migration tool to take other template types would then be an option.
> 
> 
> *(2) What functionality do people care about most?*
> 
> - ability to launch a set of VM's based on template ID or template key/value 
> details
> - ability to define a scalable cluster of a template
> - ability to attach external (code) policies to that cluster
> - ability to specify that the collection is on a private subnet with only 
> selected VM+ports exposed via a public IP
> 
> 
> *(3) What deployment and management tools/techniques are people using and 
> would like to see supported here?*
> 
> - bash scripts (install and run scripts, with ability to refer to other VMs 
> programmatically in the script)
> - deploy a puppet-master, then bring up other "stem-cell" nodes which connect 
> to the puppet master
> - (David Nalley has already mentioned knife-cloudstack using chef)
> - whirr  ( http://whirr.apache.org )
> - brooklyn ( http://brooklyncentral.github.com ) for clusters and policies, 
> building on the above
> 
> 
> Best,
> Alex
> 

Reply via email to