Working with a major bank to set up a private cloud and used Cloudify implementation as an orchestrator, based on TOSCA blueprints.
Environment was VMWare and OpenStack based instances that was configured using SaltStack.
Working with a major bank to set up a private cloud and used Cloudify implementation as an orchestrator, based on TOSCA blueprints.
Environment was VMWare and OpenStack based instances that was configured using SaltStack.
Product has given us the ability to catch scaling issues early on that many companies hit on with private clouds.
We’ve found application modeling being abstract blueprints fits the need for developers to implement their much needed bi-product from a simple template.
Cloudify provides a good framework that you can build on to provide custom solutions for an organization.
Certainly the UI could use some intensive work, but nevertheless, overall, it’s a complete product with its 3.4 version and much better features are available with 4.0.
No need to change the existing application code base.
Reduced the manual tasks during application release activities.
We have been using this solution for six months.
I did not encounter any issues with deployment.
I did not encounter any issues with stability.
I did encounter any issues with scalability.
I would rate customer support as good.
Technical Support:I would rate technical support as good.
We did not evaluate any other options.
The setup was straightforward.
In-house teams implemented it.
Pricing and licensing are decent.
We did not evaluate other options.
We configured our application using Cloudify in our production environment. We deployed the REST application with Tomcat and configured it with Cloudify auto-scaling and load balancing configuration.
I think about the containers (Docker). We can quickly create a local cloud with Kubernetes, a global deployable format (container), good resource utilization, and open source.
I used the 2.x version and did not use the 3.x version.
Unlike the Docker environment, Cloudify takes time for configuration and its learning curve.
It has enabled us to create the DICE Deployment Service. It also simplified deployment of any other services (monitoring, continuous integration, etc.).
It would be great if it would start supporting Ubuntu 16.04 or newer.
I have used it since spring 2015.
There were some issues with deploying the solution on OpenStack Mitaka. However, we were able to resolve them.
We have not encountered any stability issues. Since version 3.4.0, the solution is stable.
No scalability issues so far.
Very responsive and helpful support through mailing lists and groups.
Initial setup was fairly straightforward though following the documentation.
We have an in-house team.
We also evaluated Brooklyn and Alien4Cloud. None of them offered stable TOSCA blueprint support.