Spent the better part of a day trying to figure out how to bridge OVN networks with physical networks, only to later find out that "Attach to physical network" has zero effect in a Legacy cluster... which started me down the rabbit hole of "how do I switch the Default cluster to be OVS" Then, I come up with the bright idea that I'm going to create a new OVS cluster and migrate all the hosts there, well in order to do that you might: 1. Put the Host into maintenance 2. Install to UNDEPLOY the hosted engine 3. Remove the host from the cluster 4. Add the host to the new OVS cluster However this has a nasty bug where the required networks won't ever sync I believe because of some QoS settings (even though I haven't set that), so host is not able to reach gluster storage, and this was not one of the 3 replicas, it was just a client So moving on just to test the waters with another angle, I UNDEPLOY on one of the gluster servers, and then and only then after waiting however long it took to install/undeploy, does it tell me that It can't remove this host from the cluster because it holds gluster volumes......... How in the heck can I migrate what I have on Default to use native OVS? Let's say I started fresh (I'm using oVirt Node 4.2.5) since I have that option....I don't ever recall there being an option to select OVS as the hosted-engine switch type, and it of course sets up the Default cluster for you - which is the one I'm having issues with because it's legacy by default. Thanks