3143d86b69
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>
1.7 KiB
Executable File
Internal Management Network Overview
The internal management network must be implemented as a single, dedicated, Layer 2 broadcast domain for the exclusive use of each cluster. Sharing of this network by more than one cluster is not supported.
Note
This network is not used with Simplex systems.
During the software installation process, several network services such as , , and , are expected to run over the internal management network. These services are used to bring up the different hosts to an operational state. It is therefore mandatory that this network be operational and available in advance, to ensure a successful installation.
On each host, the internal management network can be implemented using a 1 Gb or 10 Gb Ethernet port. Requirements for this port are that:
- It must be capable of -booting.
- It can be used by the motherboard as a primary boot device.
Note
If required, the internal management network can be configured as a -tagged network. In this case, a separate IPv4 boot network must be implemented as the untagged network on the same physical interface. This configuration must also be used if the management network must support IPv6.
Internal Management Network Planning
<internal-management-network-planning>
Multicast Subnets for the Management Network
<multicast-subnets-for-the-management-network>