ActiveBlog

Stackato 2.6 Released
by Brent Smithurst

Brent Smithurst, November 28, 2012

Stackato 2.6 I'm happy to announce that Stackato 2.6 is now available! It was a quick update from the recent Stackato 2.4, but we managed to pack a lot into it. The forum announcement and release notes have all the details. We've been really busy around here (especially since several of our people are out galavanting in attending a conference in Las Vegas), but I wanted to take a few minutes to write a brief post about it.

Why so quick? (Wasn't 2.4 just released a month ago?)

Stackato is developed with an agile mindset. (The lowercase a in agile is quite intentional, as is the absence of the word methodology.) That means we assign items to a release, rank them by priority, and deliver on a set date. If an item isn't ready by the deadline, it's held back for a subsequent release. That's an overly simplistic description, but you get the drift.

The point is that when Stackato 2.4 was released, there were several things that were almost (but not quite) ready. Those things are now done, fully tested, and available for you to use today.

Logyard "2.0" and Cloud Events

The biggest change is a major enhancement to Logyard that we refer to as Logyard 2.0 internally. The major changes include forwarding of application logs, support for Splunk out of the box (joining Loggly and Papertrail), and no single point of failure. These changes also enabled new capabilities in the Management Console's Cloud Events tab: events from all nodes in a cluster are now displayed and events can be forwarded via Logyard drains.

There is also much more to the new Logyard; a detailed blog post dedicated to it will be available tomorrow.

Multiple Stagers

Our enterprise customers are always concerned with high availability, and we've been working on making it possible for each clustered role to be run as a redundant instance for failover and load balancing purposes. Stackato 2.6 adds multiple Stagers to join the multiple Cloud Controllers and multiple Routers from Stackato 2.4.

Migration "2.0"

The Migration feature was introduced in Stackato 2.4. Kind of. It was introduced but just laid the necessary groundwork for the feature to be used in subsequent versions. Stackato 2.6 is the first version that can use this new system to update from Stackato 2.4. For my fellow Mac users, it works kind of like Mac OS X's Migration Assistant, except it works across a cluster. You can now export all data from an entire cluster into a single file with one command, then import that data back into a cluster with another command. You can also import data into a cluster from an existing cluster directly. Live migration. Pretty cool stuff.

Enterprisey changes

The rest of the changes are less headline-worthy, but are nonetheless important for enterprise customers. A couple of little bugs fixed, better Cloud Controller file uploads, further documentation improvements, and the ability to see a history of the administrative commands run across a cluster. Oh, and a couple of changes for a big OEM partner.

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, email, or our Stackato discussion forum.

Subscribe to ActiveState Blogs by Email

Share this post:

Category: announcements, stackato
About the Author: RSS

Brent is ActiveState's Vice President of Product Management & Marketing. He's interested in helping enterprise IT departments and developers work together more effectively. Prior to joining ActiveState, he held leadership positions in software product management, IT, operations, and marketing for organizations in security/computer management, motion picture/television, food services, and hardware retail/online industries. But you already knew that after checking him out on LinkedIn, didn't you?