I have been deploying vROps since February this year but have noticed some issues since late August with many new deployments. It is mainly in relation to resources within VM's and Hosts / Clusters. Some clusters will report all information correctly and others can have all hosts missing or only report back on certain hosts and VM's.
I have attached some examples of the issues that I am seeing regularly.
The following example (server names removed) shows that the CPU Recommendation and reclaimable information is missing:
On other clusters or for other customers it may only show one or two hosts in the cluster and misses the others completely.
Another problem I am seeing recently is that it is massively overestimating the CPU resources for hosts and VM's. In the following example a small cluster has 56 cores and it is recommending an upgrade to 149 Cores:
However, if you look at the above the stress zone graph, the requirements are way under anything that is being recommended. I am seeing this on lots of VM's and hosts where the CPU recommendations are massively over what the graphs are showing. When we look in depth on the resource utilisation they do not match the recommendations.
The following is another example:
Previous assessments would have shown a recommendation to 5 or 6 CPU's, suddenly we are seeing an increase of double this up to 10 but the graphs and data don;t add up. I am seeing this problem on most recent deployments.
This also impacts the host rightsizing and massively gives the wrong information:
Suddenly we are going from saving 30% capex to increasing hardware requirements!
Again this has only started since September and the last vROPS version I checked was running 6.0.2.27777062 Build 2777062
I know there is a new version released and have been advised that this "SHOULD" fix this problem but this was all unofficial advice.
Questions:
- Has anyone else experienced this problem and which releases are producing the problem?
- Can anyone confirm that the latest release fixes these problems and is stable?
- Once you apply the update how long do we need to wait to receive consistent data? Will we need to wait 30 days until the old bad data has been replaced with true accurate data or does the update re-analyse the data and fix the reports. Or do we blow vROps away completely and do a fresh installation
I believe that the product is awesome and we have just hit a bit of a hiccup, I just have a lot of customers that I suddenly cannot explain what is going on!
Thoughts and feedback would be appreciated on the above