On Jan 27, 2013, at 3:51 AM, Andy Burnett <[email protected]> wrote:
>> I built CloudFoundry so that you uploaded a .st file (in my ESUG example it >> was 'aida.st') that was used to build the image. The server executed the .st >> file and saved the resulting image (it could load .mcz files directly or >> execute a Metacello script). Whenever your application was needed, a copy of >> the saved image was used. >> >> James Foster > > James, can I check a few assumptions - I want to make sure I am not > putting words in VMWare's mouth, or missing an opportunity. Janko has done a good job of summarizing the current situation. > 1. Is it the case that CloudFoundry.com has no current plans to offer > gemstone as a hosted option? I am not aware of any such plans, and at the present time I think it would be unlikely. (Note that we are completely different teams in different locations in different parts of a large organization. My knowledge of and interaction with the Cloud Foundry team is essentially the same as that of anyone else who forked their code on GitHub.) As Janko noted, cloudfoundry.com is still in beta and the commercial arrangements are not yet formalized. I believe that Cloud Foundry will be part of the VMware/EMC spin-off (as will GemStone), so there is a bit more uncertainty than usual. > 2. Your work on getting Aida to run was targeted at the > cloudfoundry.org, And therefore it would require someone to set up a > separate hosting operation - using the cloudfoundry code - in order > for us to use your work? Yes. As Janko noted there are others doing the same thing. > If 1 and 2 are true, is there anyway that we can use the .com side in > pursuit of this PhaaS objective? I assume not, but I would hate to > miss the simple fix :-) Speaking as an observer of business operations (not as a VMware employee), I suspect that the best way would be to demonstrate commercial feasibility. James Foster > Cheers > Andy
