Eco4Cloud Workload Consolidation is a Virtual Infrastructure Optimization Solution designed to improve the economics of virtualized data centers with an intelligent software platform, which increases performances and decreases costs.
Eco4Cloud Workload Consolidation works on top of a virtualization platform, and uses the exposed API to connect to the platform and optimize the workload placement in a virtual farm in order to make it more…
N/A
Nagios Core
Score 7.7 out of 10
N/A
Nagios provides monitoring of all mission-critical infrastructure components. Multiple APIs and community-build add-ons enable integration and monitoring with in-house and third-party applications for optimized scaling.
Eco4Cloud is well suited in VMware farms that have standard VM deployments, especially with small VMs, with nothing blocking vMotion and hardware fully compatible with IPMI 2.0 (minimum). It doesn't work well if many VMs are nodes in a Microsoft cluster because they would be unmovable and therefore their host would never be put in stand-by mode. If every host in the cluster has at least one guest VM that is a node of a Microsoft cluster, no host in the cluster will ever be put in stand-by mode.
Nagios monitoring is well suited for any mission critical application that requires per/second (or minute) monitoring. This would probably include even a shuttle launch. As Nagios was built around Linux, most (85%) plugins are Linux based, therefore its more suitable for a Linux environment.
As Nagios (and dependent components) requires complex configurations & compilations, an experienced Linux engineer would be needed to install all relevant components.
Any company that has hundreds (or thousands) of servers & services to monitor would require a stable monitoring solution like Nagios. I have seen Nagios used in extremely mediocre ways, but the core power lies when its fully configured with all remaining open-source components (i.e. MySQL, Grafana, NRDP etc). Nagios in the hands of an experienced Linux engineer can transform the organizations monitoring by taking preventative measures before a disaster strikes.
It consolidates workloads in VMware clusters using an algorithm that seems to work better than VMware DRS. It keeps headroom for workload peaks and to withstand the number of host failures set for the cluster in vCenter.
If the workload is very variable, Eco4Cloud will not continuously turn a host on and off but it will settle to keep the host running. It sort of "rightsizes" the cluster keeping only the right number of hosts running. This is another main difference when comparing Eco4Cloud with VMware DRS/DPM which strictly follows the workload and sometimes isn't fast enough in turning on the hosts when the workload is ramping-up.
To do a good job Eco4Cloud needs to analyze the hosts and the VMs. Therefore, the troubleshooting component of Eco4Cloud can figure out if there are problems in the configuration of the hosts (e.g. vMotion settings). It can also determine if a VM is stuck and can't vMotion (e.g. using the physical CD-ROM) or if it's oversized or undersized.
Something Eco4Cloud has and others don't is a technology named Smart Ballooning. With Smart Ballooning Eco4Cloud recovers unused RAM from the VMs and gives it back to the host way before the host goes over the 94% RAM threshold. This allows us to reach higher levels of overbooking.
Nagios could use core improvements in HA, though, Nagios itself recommends monitoring itself with just another Nagios installation, which has worked fine for us. Given its stability, and this work-around, a minor need.
Nagios could also use improvements, feature wise, to the web gui. There is a lot in Nagios XI which I felt were almost excluded intentionally from the core project. Given the core functionality, a minor need. We have moved admin facing alerts to appear as though they originate from a different service to make interacting with alerts more practical.
We're currently looking to combine a bunch of our network montioring solutions into a single platform. Running multiple unique solutions for monitoring, data collection, compliance reporting etc has become a lot to manage.
The Nagios UI is in need of a complete overhaul. Nice graphics and trendy fonts are easy on the eyes, but the menu system is dated, the lack of built in graphing support is confusing, and the learning curve for a new user is too steep.
I haven't had to use support very often, but when I have, it has been effective in helping to accomplish our goals. Since Nagios has been very popular for a long time, there is also a very large user base from which to learn from and help you get your questions answered.
We compared the consolidation feature and we obtained exactly the same amount of servers in stand-by. The main difference was that Eco4Cloud turned off the unneeded hosts in 2 days while VMTurbo Operations Manager required one day per host. This behavior is caused by the different algorithms implemented by these two products. Compared to Eco4Cloud, VMware DRS/DPM was very aggressive (we tried it in vSphere 5.0). We haven't tested it with vSphere 6 yet.
Because we get all we required in Nagios [Core] and for npm, we have to do lots of configuration as it is not as easy as Comair to Nagios [Core]. On npm UI, there is lots of data, so we are not able to track exact data for analysis, which is why we use Nagios [Core].
With it being a free tool, there is no cost associated with it, so it's very valuable to an organization to get something that is so great and widely used for free.
You can set up as many alerts as you want without incurring any fees.
