Introduction by Jeremy Hess, Cloudify Community Manager
Our goal at Cloudify, aside from building the most awesome cloud orchestration platform, is to be as transparent as possible about what’s happening on the inside. We are, after all, an open source software product. In keeping with that theme, we have decided to bring you detailed info on every single milestone update when it becomes available, straight from one of our awesome core developers.
Enjoy and let us know what you think.
Cloudify – Intelligent Cloud Orchestration Done Better. Download Free. Go
Today we released Cloudify 3.4 M3 for early access download. Our ragtag band of misfits… uh, I mean us awesome developers, are working toward a really ambitious goal for the 3.4 GA release. One of the most important changes is around manager blueprint handling. As we get closer to GA, we will be writing more blog posts on this topic and you will get a small taste here as well. We did, however, want to give you an idea of the critical updates and features that have been added in this latest milestone release. So, here goes:
- Blueprint composition: Blueprints can get quite long. The purpose of the new blueprint composition is to split blueprints into multiple, smaller parts which gives users a clearer view of their blueprint ecosystem. In order to make this happen, we added functionality to import multiple inputs, outputs and node_templates, and to use the CLI to pass multiple input arguments in the form of key value pairs, json strings, file paths, wildcards, and directories.
- Windows Improvements: We created a new plugin for ‘psutil’ which is a monitoring plugin for Windows so users can now add monitoring. We also have AWS Plugin support for Windows which allows you to setup a Windows VM on EC2.
- Team collaboration: We now have a really cool integration setup with tmux that allows multiple users to collaborate simultaneously (like Google Docs) on the same manager terminal using the command
cfy ssh tmux
- Simplified CLI commands: In the CLI, the
cfy installcommand now invokes
deployments create, and
executions start -w installworkflow without the need to enter each command separately. The same applies to the
cfy uninstallcommand which now invokes
executions start -w uninstalland
- CTX module support in Fabric: If you write Python scripts that run with the Fabric plugin, you can now import the ‘ctx’ module using
from cloudify import ctx
- Important breaking change: We are now using only Python scripts (bash is still supported) for bootstrapping the manager. All manager blueprint scripts were migrated from bash to Python, so if a user modifies manager blueprint scripts, it’s now only in Python for easier maintenance and dealing with future changes.
- Error Reporting: We have also made some important changes to clarify the error text in the CLI when using the
I hope this gave you a nice taste of what we are working on and what the bigger picture of Cloudify 3.4 is going to be. Blueprint composition (not the composer) is a big part of that larger vision for Cloudify going forward in an effort to create a more modular system for componentized blueprints with versioning and composition as well as allowing for zero-downtime when making changes to a deployment in production.
We hope you stay tuned to this channel for more about Cloudify and we will be serving up more details in the coming months.