Hi all, I am a new cloudstack user and while reading the related documentation some questions came up.
1. As explained in https://www.shapeblue.com/a-beginners-guide-to-cloudstack-networking/ <https://www.shapeblue.com/a-beginners-guide-to-cloudstack-networking/> the (Logical) Management Network is used for ' communication between the management server(s) and the system VMs. ‘ which is clear. But, in https://www.shapeblue.com/networking-kvm-for-cloudstack-2018-revisit-for-centos7-and-ubuntu-18-04/ <https://www.shapeblue.com/networking-kvm-for-cloudstack-2018-revisit-for-centos7-and-ubuntu-18-04/> it is said that 'CloudStack itself requires internal connectivity from the hypervisor host to system VMs (Virtual Routers, SSVM and CPVM) over the link local 169.254.0.0/16 subnet. This is done over a host-only bridge “cloud0”, which is created by CloudStack when the host is added to a CloudStack zone.’ So my question is, if the link local subnet is used for the communication between the hypervisor host and system vms, then the managent ip range address that is declared during the (advanced) zone creation what is it used for? Is it for the communication between the physical host and system vms?…and if so, what kind of traffic is travelling in this ip range? 2. Is it possible for test purposes to deploy cs with advanced zone with the following addressing scheme? management ip range: 172.16.0.10 - 172.16.0.20, mask: 255.255.255.0, gw 172.16.0.254 (No VLAN) storage ip range: 172.16.0.30 - 172.16.0.40, mask: 255.255.255.0, gw 172.16.0.254 (No VLAN) guest ip range. 172.16.0.50 - 172.16.0.60, mask: 255.255.255.0, gw 172.16.0.254, (VLAN range 1000-1100) pubic ip range 172.16.0.70 - 172.16.0.80, mask: 255.255.255.0, gw 172.16.0.254, (No VLAN) 3. What would be the best solution for the above addressing scheme? a. Use two physical network interfaces NIC0: management + storage, NIC1: guest + public b. Use three physical nics NIC0:management+storage, NIC1:guest, NIC2:public c. other setup
