Browse Source

Add detailed explaination for baremetal network configure

Change-Id: I5521440ef38657107dc3690aaaaa35ea6a7544e7
Wei Hui 2 years ago
parent
commit
bdffdb1a9b
1 changed files with 13 additions and 6 deletions
  1. 13
    6
      userdocs/fuel-install-guide/sysreq/sysreq_ironic_prereq.rst

+ 13
- 6
userdocs/fuel-install-guide/sysreq/sysreq_ironic_prereq.rst View File

@@ -15,12 +15,19 @@ required to succesfully deploy and use the OpenStack Bare Metal service.
15 15
 * Prepare the nodes on which you plan to deploy ``ironic`` by configuring the
16 16
   following:
17 17
 
18
-  * A separate network interface for the *baremetal* network.
19
-
20
-    You must assign a separate network interface or a VLAN for the
21
-    *baremetal* network on the controller node. If you need to configure
22
-    this network interface only on some nodes, such as nodes with ``ironic``
23
-    and ``controller`` roles, use network templates.
18
+  * Prepare the *baremetal* network.
19
+
20
+    In fuel, the *baremetal* network consists of a virtual subnet range and
21
+    a solid subnet range. The virtual subnet range is a part of the OpenStack
22
+    Network service and will be mapped to the Fuel private network. Baremetal
23
+    servers get their IP addresses from this virtual subnet range in the same
24
+    manner as virtual instances. The solid subnet range is similar to the Fuel
25
+    management network and is used for communication between Ironic services
26
+    (ironic-api, ironic-conductor, ...) and agent that run on baremetal servers.
27
+    Therefore, configure the *baremetal* network with care and ensure that the
28
+    baremetal servers PXE boot interface are plugged into this network. If you
29
+    need to configure this network interface only on some nodes, such as nodes
30
+    with ``ironic`` and ``controller`` roles, use network templates.
24 31
 
25 32
   * Access to the IPMI network
26 33
 

Loading…
Cancel
Save