Im trying to deploy 6 nodes with 512G ram and 24TB disk each Im envisioning 2-3 AIO DUPLEX Controller and 4 WORKER/STORAGE SO i deployed a single AIO duplex node, works fine, then had issues with pxe booting other nodes from it, due to switch configuration, without having to reinvent the switch topology to accomodate the pxe 169.254.202.1 pxe network, im reading below where it states PXE Boot Network VERSION You can set up a PXE boot network for booting all nodes to allow a non-standard management network configuration. The internal management network is used for PXE booting of new hosts and the PXE boot network is not required. However there are scenarios where the internal management network cannot be used for PXE booting of new hosts. For example, if the internal management network needs to be on a VLAN-tagged network for deployment reasons, or if it must support IPv6, you must configure the optional untagged PXE boot network for PXE booting of new hosts using IPv4. According to: https://docs.starlingx.io/deploy_install_guides/r6_release/bare_metal/config... Okay so it seems i need to go this route, and pxe boot all nodes, however.. reading the configure a pxe boot server doc, it states "You can optionally set up a PXE Boot Server to support controller-0 initialization." so this tells me that it can only be used for pxe booting controller-0 ???? https://docs.starlingx.io/deploy_install_guides/r6_release/bare_metal/config... so questions: 1) can i boot multiple aio duplex from a pxe boot server 2) once controller-0 is up, how does controller-1 connect to it. 3) which then i have to inquire how does discovery work for controller-1 on controller-0 4) in your opinions, which are welcome, how should i be deploying 6 nodes with this much memery and storage per node, to use 3 as controllers, and all 6 as compute/storage nodes?