A AlexLup Well-Known Member Mar 19, 2018 218 16 58 43 Jan 10, 2019 #41 Yes that the KB I was referring too, but bear in mind that the NUC wont be able to take VMs on its CPU if it cant see the cluster.
Yes that the KB I was referring too, but bear in mind that the NUC wont be able to take VMs on its CPU if it cant see the cluster.
P ProxCH New Member Jan 5, 2019 29 0 1 25 Jan 11, 2019 #42 AlexLup said: Yes that the KB I was referring too, but bear in mind that the NUC wont be able to take VMs on its CPU if it cant see the cluster. Click to expand... I'm not sure to follow you; why NUC cannot see the cluster ? For me, the NUC is fully integrated to the cluster now, do I miss something ? So in my case, I have this in the corosync config : totem { cluster_name: HomeLab config_version: 3 interface { bindnetaddr: 192.168.7.20 ringnumber: 0 } ip_version: ipv4 secauth: on version: 2 } Do I have to do modify anything ? This is the default entry I have...
AlexLup said: Yes that the KB I was referring too, but bear in mind that the NUC wont be able to take VMs on its CPU if it cant see the cluster. Click to expand... I'm not sure to follow you; why NUC cannot see the cluster ? For me, the NUC is fully integrated to the cluster now, do I miss something ? So in my case, I have this in the corosync config : totem { cluster_name: HomeLab config_version: 3 interface { bindnetaddr: 192.168.7.20 ringnumber: 0 } ip_version: ipv4 secauth: on version: 2 } Do I have to do modify anything ? This is the default entry I have...
