About Host Networking Configuration
Depending on your Neutron networking configuration, you can either designate one or more hosts as dedicated network nodes, or distribute networking capabilities across all your hosts by using Distributed Virtual Routing.
Regardless of your configuration, all your network nodes and/or hypervisors should have the following networking configuration.
- At least one physical network interface (two interfaces in a bond is recommended)
- Outbound https (port 443) access (to communicate with Platform9 configuration plane).
The following VLAN sub-interfaces on the physical interface or bond.
- VLAN-based virtual machine traffic: The interface routes traffic for the VLAN-based private or tenant networks, as well as provider networks created by using Neutron. Therefore, it must be trunked for all VLAN IDs that you plan to supply to Neutron for tenant or private networking and provider networking.
- Management VLAN: Ensure that the management VLAN allows outbound HTTPS access for the Platform9 host agent to communicate with the controller.
- Tunnelled GRE / VXLAN VLAN (optional): The tunnelled interface routes traffic for the VXLAN or GRE based private /tenant networks created via Neutron. Therefore, it must have IP level connectivity with other hosts through the interface IP.
- External VLAN (optional for hypervisors): This interface is used to route all outbound traffic for all instances that are assigned a floating IP address.
- Storage VLAN (optional): This interface is used for any iSCSI, NFS, or any such storage traffic for instances, or block storage.