- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for that write up vLarus. Very helpful.
Yes, I ALWAYS question why someone wants dedicated resources, and to date, I have never had to provide it. We've never had hosts with resource issues, so there has never been a reason to grant these guaranteed resources to vm's. However, this customer wants to buy their own host to put it in our cluster, which we've agreed to as long as they realize that if their host experiences down time, we will only bring back up their environment at a reduced capacity on other hosts in the interim. They were fine with that. (FYI, No DRS, NO HA in this cluster)
So, one would think that I don't need to use either of those things, core sharing or affinity, if the users have their own host, but I was hoping to utilize this host somewhat too, since I know they won't use all of the resources despite what they think. (current environment metrics tell the truth) That's why I was trying to understand these options.
What do you think would be the best setting to enable to ensure their vm's always get host resources they need, even if it comes at the cost of other vm's suffering? It sounds like no matter what solution I choose, I could introduce temporary problems on to other hosts in my cluster during any downtime for their host, but I just want to ensure their vm's always get the resources they need on their host, and any other vm I decide to put there do not if there was ever contention.