Morning Everyone,
I was looking deeper into the High Availability States and I thought at first I misunderstood the directions but the options are for Start, Stop, Ignore, Disabled. Start forces a startup, stop forces shutdown , ignore allows for manual start and stop but no more resource relocation, and disabled shuts the vm off and no resource relocation. The problem I have with this it there's no option to allow start and stop options with resource relocation if the node fails. I was hoping I could build the VMs then set permissions to individuals so that they can manage the VM/Container on their own. This will require their ability to start/stop when they choose and provide an option to transfer the VM/Container if something happens to the node.
Does anyone have an option here? Maybe it's not in the GUI but I can set it via CLI? The only option I would have is set a bunch to ignore but if a server crashes then I have to set em all to start on another server.
Second Question, I am looking at the max relocate and max restart options. Currently if a node goes down it takes about 2 minutes for VM's to spin up on another server. That's not bad but I'm wondering if there's a delay due to these max restart and max relocate options. There's going to be some sensitive VMs that I plan on constantly replicating. In the 2 minutes I'm not sure if it's the cluster all agreeing to wait 2 minutes to see if the node completes a reboot and see if the VMs come back up or it takes that long for the VM to spin up on another server, I have a feeling it's the former. Either way I want to cut down that time and let the system know that after 10 seconds if there's no response to just spin the VMs up on other nodes.
I was looking deeper into the High Availability States and I thought at first I misunderstood the directions but the options are for Start, Stop, Ignore, Disabled. Start forces a startup, stop forces shutdown , ignore allows for manual start and stop but no more resource relocation, and disabled shuts the vm off and no resource relocation. The problem I have with this it there's no option to allow start and stop options with resource relocation if the node fails. I was hoping I could build the VMs then set permissions to individuals so that they can manage the VM/Container on their own. This will require their ability to start/stop when they choose and provide an option to transfer the VM/Container if something happens to the node.
Does anyone have an option here? Maybe it's not in the GUI but I can set it via CLI? The only option I would have is set a bunch to ignore but if a server crashes then I have to set em all to start on another server.
Second Question, I am looking at the max relocate and max restart options. Currently if a node goes down it takes about 2 minutes for VM's to spin up on another server. That's not bad but I'm wondering if there's a delay due to these max restart and max relocate options. There's going to be some sensitive VMs that I plan on constantly replicating. In the 2 minutes I'm not sure if it's the cluster all agreeing to wait 2 minutes to see if the node completes a reboot and see if the VMs come back up or it takes that long for the VM to spin up on another server, I have a feeling it's the former. Either way I want to cut down that time and let the system know that after 10 seconds if there's no response to just spin the VMs up on other nodes.