What do they mean by "Spring applications"? That's quite obscure. Do they mean they handle .war J2EE applications? Or they only support Spring libraries?
We can take any .war file that runs on Tomcat, even jruby apps. Not just spring.
VMware launches Node.js, Rails and Spring PaaS
31–40 of 57 posts
Re: VMware launches Node.js, Rails and Spring PaaS
#32Well, to make the license question easier, their invite request form is utterly unusable on Android. I apparently need to 'scroll to the bottom' to submit to a dubiously enforceable license before even being allowed to see their beta, exciting action made anyway imposible by the broken design. Node.js notwithstanding, this tastes from the start like a proper enterprise service.
On the iOS you can scroll textareas and iframes using two fingers. I imagine it should be possible on Android too.
Re: VMware launches Node.js, Rails and Spring PaaS
#33Earlier quoted context omitted.
It doesn't seem like its different people from Heroku. If you've seen Mark Benioff's cloudforce pitch (link below), he mentions that they're partnering with VMWare to launch a PaaS similar to Heroku (which they acquired in December). That said, I think its a bit surprising that VMWare is launching this under their branding - the machinations of large corporations continuously confound me. http://www.salesforce.com/vi…
according to the register: http://www.theregister.co.uk/2011/04/12/vmware_open_sources_... "Cloud Foundry serves as the basis for the VMforce platform cloud VMware is building in tandem with Salesforce.com. Therefore, Chen tells us, developers will be able to readily move applications between VMforce and other Cloud Foundry services" So they are both apparently releasing differently branded versions of the same stack…
None of the code comes from Heroku at all.
Re: VMware launches Node.js, Rails and Spring PaaS
#34I was suprised no virtualisation is included in the solution (or I did not find the parts in the github repos). Seriously, shared-hosting is so 1996 from a security perspective. So for me It will be "just" an "internal cloud" solution and maybe replace capistrano. Still, puppet and chef will do the "physical"/"system" provisioning for my customers and my projects.
As far as I can make out so far it is not designed to be multitenant. Each client gets an instance for their apps which can consist of multiple VMs. Based on interpreting the install guide here https://github.com/cloudfoundry/vcap
It currently supports multi-tenant and single tenant, you choose when you set it up.
Currently the multi-tenancy is based on locked down unix users and permissions and other system hardening, pretty much same approach Heroku uses so you judge whether that's multi-tenant or not. We are looking into lightweight containers like lxc and friends for another implementation of the multi-tenancy.
Re: VMware launches Node.js, Rails and Spring PaaS
#35With support for MySql, MongoDB, and Redis on the DB side :)
Would it be a fair guess that CloudFoundry will support Redis Cluster too when it is released?
That's the idea, I'm taking this in mind while developing redis cluster, for instance a must is the ability to create and manage clusters by using redis-trib in scripts, so that it is possible to have one click provisioning of a Redis cluster of N nodes automatically. You can see that in the unstable branch there is already some initial version of redis-trib I'm developing in this days to allow this kind of things.
Re: VMware launches Node.js, Rails and Spring PaaS
#36Earlier quoted context omitted.
Would it be a fair guess that CloudFoundry will support Redis Cluster too when it is released?
That's the idea, I'm taking this in mind while developing redis cluster, for instance a must is the ability to create and manage clusters by using redis-trib in scripts, so that it is possible to have one click provisioning of a Redis cluster of N nodes automatically. You can see that in the unstable branch there is already some initial version of redis-trib I'm developing in this days to allow this kind of things.
Thanks for the reply - sounds like this will be a really useful combo for operating large Redis deployments.
Re: VMware launches Node.js, Rails and Spring PaaS
#37I was suprised no virtualisation is included in the solution (or I did not find the parts in the github repos). Seriously, shared-hosting is so 1996 from a security perspective. So for me It will be "just" an "internal cloud" solution and maybe replace capistrano. Still, puppet and chef will do the "physical"/"system" provisioning for my customers and my projects.
In web hosting, virtualization is usually excuse for bad design. Personally I'm glad that VMware (virtualization company!) managed to pull this without it.
Re: VMware launches Node.js, Rails and Spring PaaS
#38What do they mean by "Spring applications"? That's quite obscure. Do they mean they handle .war J2EE applications? Or they only support Spring libraries?
We can take any .war file that runs on Tomcat, even jruby apps. Not just spring.
I really think you should make this clear. We're a Java shop, but we use all sorts of frameworks; play, spring, homegrown, but they all build to .war.
This is an interesting product to me, but from the marketing material it's not obvious...
Re: VMware launches Node.js, Rails and Spring PaaS
#39What do they mean by "Spring applications"? That's quite obscure. Do they mean they handle .war J2EE applications? Or they only support Spring libraries?
We can take any .war file that runs on Tomcat, even jruby apps. Not just spring.
Which would mean that Clojure apps would qualify as well - now that might be interesting. We're running our apps on Amazon EC2 right now, managing Redis ourselves.
Re: VMware launches Node.js, Rails and Spring PaaS
#40If you are in the bay area on the 13th the Cloud Foundry team is hosting its first meetup. Come ask the tough questions to engineering: