- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
thanks both for your reply.
If i understand what you say, if i have admission control enabled on a cluster, then vrops should be able to detect the parameter and adjust the capacity usage.
But enabling admission control will also block any new start of VM if ressources are not available. So even if we are proactive with vrops, we can be block by admission control.
That's why we didn't enabled this option and we use to manage ressource pool to prioritize which kind of VM we want to prioritize (production vm in mutualized environnement)
With this new upgrade, i'm am unable to do capacity anymore. Before i had some few metrics with some home made configuration to tells me how many VM i deploy or time remaining.
Now, the only way to get an information, it the time remaining. OK... Why not. I can accept. You are the specialist, i'm only a simple user with a small experience.
But, how can you explain me that all my cluster are fine (1 yr remaining) and for some clusters i have CPU contention (7%) and vrops doesn't warm me. My clusters densification is too high and the CPU overcommit too (1:8.5)
I'm thinking about moving to Turbonomic which give me reliable data (in my case, add more host in some clusters which is the right way after some reclamation)