Netcool Network Management integrates the IBM Tivoli Network Manager IP Edition, Tivoli Netcool/OMNIbus and Netcool Configuration Manager products into a unified solution that consolidates the management of networks.
N/A
Salt
Score 6.2 out of 10
N/A
Built on Python, Salt is an event-driven automation tool and framework to deploy, configure, and manage complex IT systems. Salt is used to automate common infrastructure administration tasks and ensure that all the components of infrastructure are operating in a consistent desired state.
This tool was integrated with Control-M, so whenever we receive any job failure, long-running job, job not started yet, etc, we receive an alert against it. This tool is also integrated with Maximo where we receive the incidents as well for it. Alert's color was as per the criticality of the job and that makes it very easy for an associate to act on it to resolve. We have the SLAs for the jobs as per the urgency of the jobs.
SaltStack is a very well architected toolset and framework for reliably managing distributed systems' complexity at varied scale. If the diversity of kind or number of assets is low, or the dependencies are bounded and simple, it might be overkill. Realization that you need SaltStack might come in the form of other tools, scripts, or jobs whose code has become difficult, unreliable, or unmaintainable. Rather than a native from-scratch SaltStack design, be aware that SaltStack can be added on to tools like Docker or Chef and optionally factor those tools out or other tools into the mix.
Targeting is easy and yet extremely granular - I can target machines by name, role, operating system, init system, distro, regex, or any combination of the above.
Abstraction of OS, package manager and package details is far advanced beyond any other CRM I have seen. The ability to set one configuration for a package across multiple distros, and have it apply correctly no matter the distrospecific naming convention or package installation procedure, is amazing.
Abstraction of environments is similarly valuable - I can set a firewall rule to allow ssh from "management", and have that be defined as a specific IP range per dev, test, and prod.
We haven't had to spend a lot of time talking to support, and we've only had one issue, which, when dealing with other vendors is actually not that bad of an experience.
This is one of the essential tools for monitoring. This tool was integrated with Maximo and Control-M in my organization. So whenever any job failed in Control-M, we receive an alert against it in the IBM Netcool/OMNIbus. We receive the alerts in different colors as per the criticality. Black for critical ones(Sev1), red for urgent (Sev2), yellow for major(Sev3), and orange for minor(Sev4). So it makes an easy to operate and act on the alerts as per the severity. This tool is very user-friendly and easy to use. No additional training is required for the tool to operate, just a simple KT is enough.
We moved to SaltStack from Puppet about 3 years ago. Puppet just has too much of a learning curve and we inherited it from an old IT regime. We wanted something we could start fresh with. Our team has never looked back. SaltStack is so much easier for us to use and maintain.
We manage two complex highly available self-healing (all infrastructure and systems) environments using SaltStack. Only one person is needed to run SaltStack. That is a HUGE return on investment.
Building tooling on top of SaltStack has allowed us to share administrative abilities by role - e.g. employee X can deploy software Y. No need to call a sysadmin and etc.
Recovery from problems, or time to stand-up new systems is now counted in minutes (usually under eight) rather than hours. This is a strategic advantage for rolling out new services.
