ActiveState announces the immediate release of Stackato 3.0 beta.
Stackato is the application platform for creating a private, secure, flexible Platform as a Service (PaaS) using any language on any stack on any cloud. From the desktop to the datacenter, Stackato makes it easy to develop, deploy, migrate, scale, manage, and monitor applications on any cloud.
To learn more about Stackato 3.0 beta and download the release, go to
Please make sure to download the new client when using the new VMs. You will find the clients available for download from the VM as well.
Make the most of Stackato - check out our sample applications at
Review our updated Stackato documentation at
Changes in this release since Stackato 2.10.6 and client 1.7.2:
==== Stackato 3.0.0 Beta ====
-  Update core components to Cloud Foundry v2 API
-  Update AOK replacement of UAA to new CFv2 API compatibility
-  Update NATS message bus to use gnatsd
- [97026,98612] Replaced Doozer with Redis
- [100386,100732] Update Linux kernel to Raring backport
-  prevent crontab breakage caused by newlines in environment variables
-  New X-Frame header configuration option for router
-  Separate user and admin documentation
- [100352,101383] Use Docker for containerization
-  Improve app startup flapping prevention under high-load
-  New default limit of 50 processes per container. Configurable with kato config under fence max_container_processes
-  Memory consumption during staging is now limited to 1.5 times the application's allocated memory by default. Configurable with kato config under stager app_memory_multiplier
- Add kato node retire to gracefully shut down a DEA, moving its application instances on other available nodes first.
kato admin ... commands removed; use the corresponding stackato admin ... commands or the web console
- [93195,101079,101195] New kato node upgrade command to support node-level upgrades
-  kato process stop fence now correctly stops fence process
-  kato node attach now checks for version compatibility when adding a node to a cluster
-  --no-stop option removed from kato role remove command.
-  kato config no longer supports node-specific config; --node option removed.
-  Extend kato node setup firstuser to require default organization
-  Add Ruby 2.0 runtime and remove Ruby 1.8.7 (EOL)
-  Fixed problem building Nokogiri 1.6 gem. Stager now uses using system libraries (NOKOGIRI_USE_SYSTEM_LIBRARIES=true).
-  ActivePerl 5.14 removed
- Update to ActivePython 188.8.131.52 and ActivePython 184.108.40.206
-  Update PHP to 5.4 for default runtime
-  Support legacy frameworks with built-in buildpack
Management Console updates:
-  New kato log drain status command for showing drain status
-  Move drains from doozer to redis
-  Add "AppGroup" field to app log stream
-  Add "HumanTime" field to systail log stream
-  Add app crashes/exits (eg: OOM killer) to cloud events
-  Add harbor service provision events to cloud events
-  Cloud Events patterns are now configurable (via kato config)
-  New read_limit setting for apptail (default 16MB) to cope with extremely large application log files
-  Application log drain URLs now properly sanitized (v2.10.6 'logdrain-sanitize' patch)
-  Fix a leak in growing TCP connections causing systail to crash (inotify panic), and logyard drains to malfunction.
-  New WARNING log message on drain retries
-  Improve handling of drain state transitions
-  Compile with Go 1.1
- Update look and feel, improve inline loading and responsiveness using websockets
-  New Activity Stream API and timeline
- [94745,94274] New disk activity and disk space graphs
-  New dashboard for router metrics
- [99452,100047] Updated App Store to use new API and YAML format
stackato client updated to 2.0.2:
-  Core services ported to CFv2 API
-  Micro cloud starts with Memcached, Redis, PostrgreSQL, RabbitMQ, and MongoDB roles disabled by default (enable via Managment Console).
-  RabbitMQ updated to 2.8.7
-  RabbitMQ 3.1.3 available (disabled by default). Enable with kato role add rabbit3
-  Increased default filesystem service size to 500MB
-  Make mysql service compatible with Amazon RDS
-  MongoDB client updated to 2.4.1 in application container
-  Full support for CFv2 API, maintained CFv1 compatibility
- Updated command set for CFv2 terminology changes
-  Enforce stricter interpretation of positional options and commands to disambiguate some commands
-  Support array of applications in manifest.yml
-  Support user provided service instances
-  Show status of user drains
-  Removed host subcommand
Release notes: http://docs.stackato.com/3.0/admin/reference/release-notes.html
Enjoy, and let us know if you have any questions or feedback!