Apache CloudStack vs. ServiceNow IT Operations Management

Whether our clients are VPS hosting providers or operate private cloud infrastructure for their internal enterprise requirements, CloudStack provides solutions in an easy to implement and operate way that is simple to provide training for. The learning curve for our customesr adopting CloudStack for the management of their cloud infrastructure is shallow, enabling our clients to come up to speed quickly without having to outsource their administrative functions any longer than necessary

We have taken advantage of the single platform for different IT disciplines over the past few years and now we are doing more and more with the integrations. Our teams are looking at the same information which stops the blame game a lot. Their newest AIOps has been a very nice surprise as we've tried another tool for about 2 years and it required us to hire outside consultants to try and build what we needed. So far, ServiceNow found a lot of things we didn't know to look for. It's not perfect in fixing everything, but really has provided a lot of visibility and troubleshooting.

• Low-cost solution
• Open-source
• Engaged community
• Solid documentation
• Is a very reliable tool for orchestration with good usability

Incentivized

• The centralized dashboard allows us to keep track of production incidents as they come in, and allow us to view and sort them based on severity, making sure it's tracked
• The read/edit access and role granting process is straightforward, meaning that only the right people can change /update the statuses of incidents without unintended consequences
• With AI driven classification, it's easy to track outage impacts

Incentivized

• Sometimes you can find undocumented bugs that can compromise the entire infrastructure.
• [If] you don't have an official support channel, you have try to find out the source of the problem by yourself.
• Volume size limitation. Other players allow you to create volumes up to 64TB while ACS allows only 2TB volumes

• Scan network is limited to their discovery tool, which is costly
• Integration to jamf and ubunto tools
• Agents TCO
• integration to password management tools which are critical for successful scans

Incentivized

The University, my first large implementation, had a big issue with 149 small data centers spread on São Paulo State, this data centers costs to university were very high, the consolidation idea in two data centers were awesome, but were worried with the management, so we adopted ACS to management of all 576 physical hosts. Now a days the university is delivering IaaS for all staff, students, teachers and researchers, they are using these resources to delivery services to their clients and have a great results in research area

BMC was our legacy system before deploying ServiceNow. It's time had passed for us as it couldn't really keep up with our move to cloud and the number of services we were using. The cost kept getting higher, especially with all of the customization we had to do. Over the years, just got unwieldy. We still use Splunk for raw data and log analysis, but we upgraded to ServiceNow event management and the Loom system log analytics. We had Loom before ServiceNow bought them, but it's nice it's all on one platform for us. Splunk at times had so much info, we didn't know where to start, but ServiceNow gives us a great starting point.

• Low-cost solution (free and open-source)
• More than 2000 users using it simultaneously
• Stable and reliable
• Up and running since 2012

Incentivized

• With the regular use of ServiceNow IT Operations Management platform, our incident resolution time has gone down by over 90% over the past year
• Our access and role granting process has been streamlined leading to increased developer hours by around ~90 PM
• With the enablement of AIOps driven impact prediction, we expect an improvement of user communication time by over 90%

Incentivized