![]() Host failures cluster tolerates – This is perhaps the most complicated policy. The result of an HA event is the only time that this host will have VMs running on it – all other times, it sits there wasting money □ Specify Failover Host – Ugly! Basically you assign a host as the host that will be used in the event of an HA event. If our admission control policies are violated, no more VMs can be powered on inside of our cluster – yikes! There are three types… When an HA event occurs in our cluster, we need to ensure that enough resources are available to successfully failover our infrastructure – Admission control dictates just how many resources we will set aside for this event. I will give a brief description of a few of HA bullet points that are listed within the blueprint and point everyone where we can manage them. This became especially evident after watching the HA section of Jason Nash’s TrainSignal/PluralSight course, as I quickly realized there are a lot of HA advanced settings that I’ve never modified or tested – with that said, here’s the HA post.įirst off I’m not going to go over the basic configuration of HA – honestly, it’s a checkbox right – I think we can all handle that. Although High Availability is something I’ve been configuring for many years now I thought it might be a good idea to go over the whole process again. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |