| layout | bt_about |
|---|---|
| title | Cloudify Roadmap - Features & Bug Fixes |
| category | Roadmap |
Cloudify will allow users to install monitoring agents, such as Diamond or collectd, configure them and collect metrics for all application components. These metrics will be sent to a built-in metrics database (InfluxDB by default), and provide insight about application availability and performance.
The Cloudify GUI will embed Grafana with a pre-configured, yet customizable, monitoring screen to allow users to view and correlate metrics of the same node or compare them across nodes.
Cloudify will allow users to define and push policies for application components to the policy engine.
These policies will process large streams of events and metrics and apply actions to them in real-time. The rules can be based on metrics values as statutes of components and free text fields. The applied actions can be the triggering of a specific workflow or an invocation of a webhook, which means that the user can customize this to trigger any kind of action.
Cloudify 3.1 will have a built-in Docker plugin and matching types, which will allow users to use Docker containers as part of any topology. This provides a full-blown orchestration and automation method for large-scale Docker-based systems.
Cloudify is a TOSCA-inspired project. When we started designing and coding Cloudify, TOSCA’s simple YAML profile was not yet created or approved. We are now taking an active part in the TOSCA TC to finalize the definition of the simple profile.
Alongside this, and as a part of our ongoing commitment to TOSCA, we are aligning our TOSCA-inspired blueprints with the TOSCA simple YAML profile. This transition is going to happen in a few phases, while the main one will happen in 3.1.
Cloudify will support the TOSCA naming convention, and in addition, we are adding support for blueprint inputs, blueprint outputs, and intrinsic functions.
The Cloudify CLI will serve as a lightweight blueprints executor.
The main purpose of this feature is to allow users to easily bootstrap (complex) manager environments, using the same plugins as other applications. This will facilitate the deployment of the management environment with various topologies and different levels of distribution and sizing. So instead of having one monolithic server containing all of the manager’s components, users will be able to divide the server into multiple hosts, as they see fit, using the same blueprints used for describing applications deployed using Cloudify.
This plugin enables easy access to the node’s context from any programming or scripting language as long as it is executed as a sub-process of the plugin.
You can develop your logic for Windows or Linux in any scripting language and gain access to any context list or map using simple client calls. This is done using ZeroMQ.
An officially supported Fabric plugin will be provided which will allow users to remotely execute commands/tasks and remove the agent installation requirement.
A user will be able to provide a set of shell commands hardcoded into the blueprint or, alternatively, a file with tasks. The tasks can then be mapped to the different nodes. This will expose an agentless manner of provisioning applications.
Premade Docker images will replace the current package-based method for deploying a management environment.
This will provide:
- An out-of-the-box cross distribution support while also bridging dependency tree gaps between different user provided images.
- A singleton approach – using only one distribution for the Docker images – will provide a more robust experience.
- Easier, faster upgrades for your management environments.
- A faster bootstrap process.
This will nicely mesh with the Manager Blueprint approach and the Docker and Fabric plugins for a seamless management environment provisioning experience.
Cloudify will provide a basic matrix of agents supporting the default python version on the major distributions.
Alongside those agents, a tool will be provided which will allow users to create agents for their specific distribution with either of the supported python versions.
This plugin allows the user to execute Fabric commands either remotely or locally. Using Fabric is recommended in such as cases as when the user prefers agentless deployment, for example.
Cloudify 3.1 will support the OpenStack Cinder API with Volume type. This will allow users to create and attach external disks to VMs, as well as detach and delete these volumes.
These pages give the user reports on cloud resources consumed across different deployments. The added value of using this versus a Cloud IaaS portal is the application context reported per resource. Cloudify will have such reports for VMs, networks, floating IPs, routers and more.
This view gives a history of workflow executions per deployment and easy access to relevant logs.
Improving the workflow execution trace UX with an event console that has a more CLI-style of tracing.
- Support for Nova networks (Will be released in 3.0.2)
- Support for Proxy (Will be released in 3.0.2) – and will allow users to use Cloudify in an environment where internet access is only available for the agents and manager via proxy.
Join our cloudify-users or cloudify-developers mailing list, and get support from the community.
Subscribe to the Cloudify tag on Stack Overflow, and feel free to ask your questions amongst cloud pros.
Feel free to reach out by email with any question you may have – we’re always happy to help.