openstack
/
fuel-docs
Code Issues Proposed changes

Add detailed explaination for baremetal network configure 

Change-Id: I5521440ef38657107dc3690aaaaa35ea6a7544e7
This commit is contained in:
Wei Hui 2016-10-28 15:39:32 +08:00
parent 3389596f74
commit bdffdb1a9b
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
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.
* Prepare the nodes on which you plan to deploy ``ironic`` by configuring the * Prepare the nodes on which you plan to deploy ``ironic`` by configuring the
following: following:
* A separate network interface for the *baremetal* network. * Prepare the *baremetal* network.
You must assign a separate network interface or a VLAN for the In fuel, the *baremetal* network consists of a virtual subnet range and
*baremetal* network on the controller node. If you need to configure a solid subnet range. The virtual subnet range is a part of the OpenStack
this network interface only on some nodes, such as nodes with ``ironic`` Network service and will be mapped to the Fuel private network. Baremetal
and ``controller`` roles, use network templates. servers get their IP addresses from this virtual subnet range in the same
manner as virtual instances. The solid subnet range is similar to the Fuel
management network and is used for communication between Ironic services
(ironic-api, ironic-conductor, ...) and agent that run on baremetal servers.
Therefore, configure the *baremetal* network with care and ensure that the
baremetal servers PXE boot interface are plugged into this network. If you
need to configure this network interface only on some nodes, such as nodes
with ``ironic`` and ``controller`` roles, use network templates.
* Access to the IPMI network * Access to the IPMI network