Enables us to maximize the available capacity of the environment that workloads are using
What is our primary use case?
We evaluated Calm primarily as an automation platform because that's what it is. I work for a service provider and we represent a lot of customers. Our journey with Calm started because we wanted to decentralize our platform of services to customers, because agility is one of the biggest concerns. As a service provider, we have very rigid practices because we follow ITIL processes. If we're managing a customer's environment, we need to have controls. The unfortunate reality of controls is that they add rigidity, and that works in contrast to the agility of cloud where customers want to be able… more »
Pros and Cons
"We use Calm's one-click self-service feature and it's really transforming the team's efficiency. The teams are used to being reactive, which is typical of what you find in IT organizations and service providers. Customers run into problems and teams react. What we're trying to do is reduce that slope and be more proactive in approach. The one-click ability is enabling us to take some of those activities and put them into operation, versus people manually responding."
"While there are multiple clouds supported, we want less friction around the ease of delivery. We want the ability to integrate other clouds, unify the accounts."
What other advice do I have?
My advice would be patience. It's very exciting and sometimes you want to jump in with both feet and go really fast. It's not that I'm against that, but my take is that it's such a capable platform that you should take on things that you can achieve and then achieve them. Take on activities that you can succeed with and show that incremental progress. Sometimes you want to take on too much and go big-bang. As enticing as that is, take on pieces of Calm and succeed with them, and let the platform evolve. Don't try to wholesale adopt it too fast. If you're more traditional in nature and you're…