Stackato is built on top Cloud Foundry (plus other open source packages), so we're excited about Cloud Foundry v2 and are watching it closely as it evolves. In this post I'm going to quickly run through how I got up and running with Cloud Foundry v2. These notes are based on my colleague's instructions, who is in the process of giving Cloud Foundry v2's tires a good kicking.
In a recent whirlwind trip to Japan, I met with Cloud Foundry users in Tokyo and Osaka. There is deep investment in Cloud Foundry in Japan. For example, NTT Communications providing a Cloud Foundry-based PaaS through its "Cloud N" service.
It's great when you deploy an app and it just works. I recently worked on a proposal for a Stackato prospect who asked about a number of PHP application frameworks (basically "Will the following PHP frameworks run on Stackato"). Though I couldn't think of any reason they wouldn't work, I thought it would be prudent to test them before marking them "supported".
Arch Linux ARM (ALARM) is a distribution of Linux for ARM computers. Since ARM architecture is found in microprocessors and semiconductors made by a wide range of manufacturers, including Apple, Broadcom and Texas Instruments, chances are that at least one of your devices has an ARM-based processor.
Let's say you're running a private cloud application platform like Stackato or Cloud Foundry. Let's further say that you're running this Platform-as-a-Service (PaaS) inside your enterprise IT organization. This all sounds pretty reasonable, right? Enterprises are exactly the kind of customers who want private PaaS. What kind of features do enterprises expect from a PaaS?
With Stackato Private Platform as a Service (PaaS), enterprise IT enjoys rapid application deployment, scalable administration, and greater control while developers can code in the language that’s right for them. But how does Stackato actually work?