Updates for patchset 2 review comments Changed link depth of main Planning index and added some narrative guidance Added planning/openstack as sibling of planning/kubernetes Related additions to abbrevs.txt Added max-workers substitution to accomodate StarlingX/vendor variants Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ibff9af74ab3f2c00958eff0e33c91465f1dab6b4 Signed-off-by: Stone <ronald.stone@windriver.com>
2.4 KiB
Executable File
Shared (VLAN or Multi-Netted) Ethernet Interfaces
The management, , cluster host, and other networks for container workload external connectivity, can share Ethernet or aggregated Ethernet interfaces using tagging or IP Multi-Netting.
The internal management cluster host, and other external networks, can use tagging or IP Multi-Netting, allowing them to share an Ethernet or aggregated Ethernet interface with other networks. If the internal management network is implemented as a -tagged network then it must be on the same physical interface used for booting.
The following arrangements are possible:
For some typical interface scenarios, see : Hardware
Requirements <starlingx-hardware-requirements>
.
Options to share an interface using tagging or Multi-Netting are presented in the Ansible Bootstrap Playbook. To attach an interface to other networks after configuration, you can edit the interface.