Network planning when the PXE-enabled port on the bare metal server and the bare metal compute node belong to different subnets
Network requirements
The cluster and the bare metal compute node are reachable to each other.
The bare metal compute node and the iLO IP address of the bare metal server are reachable to each other.
The IP address of the bare metal compute node's NIC and the DHCP network are reachable to each other.
You must configure DHCP relay on the router so that the DHCP requests from the bare metal server can be forwarded to the bare metal compute node.
Configure DHCP settings for the bare metal compute node, and configure the default route to the DHCP network as the default gateway.
Example
Table-1 Network planning
|
Device |
IP address |
Remarks |
|
System cluster |
VIP: 172.25.17.53/22 |
VLAN: 201 |
|
Bare metal compute node |
eth0: 172.25.50.150/20 DHCP: 10.0.0.151-10.0.0.160/24, with default route 10.0.0.1 |
VLAN: 205 |
|
Bare metal server |
iLO:172.25.18.22/22 |
iLO: 201 Management interface: 301 |
|
Router |
DHCP relay: Specify the address of the bare metal compute node as the DHCP server address on the DHCP relay agent. |
10.0.0.0/24 Gateway: 10.0.0.1 VLAN: 301 Route: VLAN 205 and VLAN 301 can communicate. |
Procedure
|
|
Before performing this task, complete all tasks in "Deploy a bare metal compute node." |
Edit the /etc/ironic-inspector/dnsmasq.conf configuration file to add the default route dhcp-option=3,10.0.0.1.
Execute the following command to restart the openstack-ironic-inspector-dnsmasq.service service:
systemctl restart openstack-ironic-inspector-dnsmasq.service