Hi Chris, The main components like controller, Load Balancer, Host Machine of Tropos are similar in function to Clound Foundry corresponding components (Cloud Controller, Routers, Droplet Execution Agent(DEA)). In addition CF has two main components called Services and Health Monitor.
The applications are run in Droplet Execution Engines(DEE) which is monitored by DEA. These DEE's could be Linux Containers. CF provide a service gateway that is controlled by Controller to provide service access to applications running in DEE's. These services could be databases, Message systems or any other service useful to the applications. Tropos is more to the Iaas layer while Could Foundry deals mainly with Paas layer. Howerver CF is designed to deployed with existing Cloud Iaas layers. A nice slide presentation by the CF main architect is here [1] Following are some of the features that Cloud Foundry provide - Controller is policy free. It provide plug-in points for policy engines. Currently Tropos Controller include policies on selecting Adaptor, autoscaling etc in built. - CF services gateway provides plug-in points for new services. - CF aPaas can be deployed in different Iaas. In fact Rightscale [2] runs CF on it's Iaas layer. - CF can be deployed as a public aPaas or a private aPaas or a mix of both. - in CF new Applications can be bundled and make ready for new DEE deployments through controller. This is in our Roadmap. Thanks, Damitha [1] http://www.slideshare.net/derekcollison/design-of-cloud-foundry [2] http://blog.rightscale.com/2011/04/12/launch-vmwares-cloudfoundry-paas-using-rightscale/ On Tue, May 1, 2012 at 9:53 PM, Chris Haddad <[email protected]> wrote: > How does Tropos compare/contrast with VMWare's Cloud Foundry project? > > /Chris > > On Apr 25, 2012, at 11:46 AM, Afkham Azeez wrote: > > Today we were able to see an end to end demo where the autoscaler talked > to the Tropos controller, and the controller spawned LXC instances! Tropos > is the name we've been using for this 'thing' we are doing with > LXC+autoscaler+LB+agents :) If there is a better name, please come up with > suggestions :) > > Some stuff were done manually to get the end to end flow working, but the > team got it working. Good job folks! > > Damitha et. al., please schedule another demo for all interested parties > next week. It would be ideal if the manual steps are fixed to be done > automatically with scripts etc. > > Thanks > Azeez > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org/>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > > -- __________________________________________________________________ Damitha Kumarage Technical Leader; WSO2 Inc. Oxygenating the Web Service Platform http://www.wso2.com/ blog: http://damithakumarage.wordpress.com/ __________________________________________________________________
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
