- Get Stackato
- Why a Private PaaS?
- Features & Benefits
- Stackato by Language
- Compare Editions
- Stackato & Cloud Foundry
- Developer Tools
Brent Smithurst, December 20, 2012
This release is a bit unusual because the version number indicates bugfixes only, and yet we managed to slip some new features and capabilities in as well. As I said in my last blog post, Stackato is developed with an agile mindset. So, since we had some new stuff ready, we decided to release it now.
Support for Java 7 is both new and also not so new in Stackato. It has been available for a while via a buildpack. However, The Cloud Foundry Core project requires it to be built-in in order to get a check mark. Although our customers (mostly large enterprises) primarily use Java 6, there is certainly interest in Java 7 now as well. So, we built it in to make it a little easier for everyone.
A blog post dedicated to Java 7 will be available shortly.
Much like Java 7, Node.js 0.8 has been available in Stackato via a buildpack for quite some time. Again, the Cloud Foundry Core project requires it to be built-in to get a check mark. Plus, it wasn't always obvious to our users that buildpacks were even available in Stackato. So, we built it in.
Something You May Never See
One of our customers recently had a strange issue with Stackato that was troublesome to diagnose. It turned out that he had some duplicate, rogue, nodes attached to his cluster. This wasn't really Stackato's fault -- he had been doing some pretty heavy duty experimenting immediately prior. However, Stackato didn't identify this anomaly. We thought we could do better, so we did -- the web console will now identify rogue nodes and allow you to kill them with a single click. (You'll probably never see this feature unless you're a creative experimenter who identifies with his self description: "I can break anything, it's a gift I was born with".)
HP Cloud Services Block Storage Compatibility
Our friends at HP recently moved their HP Block Storage product from private beta to public beta. This provides Stackato services nodes with the persistent storage that they require when running on HP Cloud Services. The reasons for this should be obvious; if your application needs to store data, then that data needs to be on a persistent, rather than ephemeral, node.
Stackato worked with their block storage, until they made a change and then suddenly it didn't. It turns out their change exposed a Linux kernel bug that had already been patched. So, we applied the patch and can now claim to have HP Cloud Services Block Storage Compatibilty. Pretty cool, eh?
The rest of the changes are less headline-worthy, but are nonetheless important for enterprise customers. A couple of little bugs fixed, better theming capability, and some router2g improvements round out the list.
Once again, I encourage you to let us know what you'd like to see added to Stackato. What problems are you having that Stackato isn't currently solving? How can we make your life easier? Please let me know -- on Twitter, brents+feedback [at] activestate [dot] com (subject: Stackato%20feedback) (email), or our Stackato discussion forum.