openstack/fuel-docs
Code Issues Proposed changes

Improve wording around PXE booting nodes

Browse Source 
This commit includes some minor changes in
wording regarding PXE booting, specificically
reminding the reader to consider which network
the node will PXE boot from.

Change-Id: I198ca2e73ded7551ac1e62ba58bf52e41612a073
Closes-Bug: 1382259
This commit is contained in:
Christopher Aedo
2014-10-27 12:28:08 +01:00
committed by Meg McRoberts
parent 3501f89185
commit 289583df6d
1 changed files with 23 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
pages/user-guide/initialize-fuel/0600-boot-nodes.rst
View File

@@ -4,15 +4,18 @@
Boot the node servers
=====================
After the Fuel Master Node is installed and booted,
power on all slave nodes that you are going to use for the OpenStack environment.
First, ensure that servers are physically installed
in the same network as the Master node or,
if you are using virtual servers,
are bridged to it so they are in the same L2 network segment.
Then you can boot each node (other than the Fuel master) in PXE boot mode
by either modifying the BIOS boot order
or using F12 (or another key your server uses) to enable PXE booting.
After the Fuel Master Node is installed and booted, power on
all target nodes that you are going to use for the OpenStack
environment. First, ensure that servers are physically
connected to the same network as the Master node or, if you
are using virtual servers, are bridged to it so they are in
the same L2 network segment. Then you can boot each node
(other than the Fuel master) via PXE by either modifying the
BIOS boot order or pressing the appropriate key to initiate
a PXE boot. If your nodes have several network interfaces,
be sure to enable PXE-boot on the interface that is on the
same network you configured for PXE booting on the Fuel
Master Node.
#. Each node sends out DHCP discovery requests and gets the response from
the Fuel Master node that runs the DHCP server.
@@ -24,16 +27,17 @@ or using F12 (or another key your server uses) to enable PXE booting.
it reports the node's readiness and configuration to the Fuel Master.
This can take a few minutes.
Follow the instructions in :ref:`boot-fuel-master-ug`
to log into the Fuel UI if you have not already done so.
You will see notifications in the user interface about the discovered nodes.
Find the count of "Discovered nodes"
in the upper right area of the Fuel Web UI;
this value is incremented as each new node is ready.
When the count of "Discovered nodes"
becomes equal to the amount of the servers you have booted in the network,
you can create an OpenStack environment,
add nodes into it, and start configuration.
Follow the instructions in :ref:`boot-fuel-master-ug` to log
into the Fuel UI if you have not already done so. You will
see notifications in the user interface about the discovered
nodes. Find the count of "Discovered nodes" in the upper
right area of the Fuel Web UI; this value is incremented as
each new node is ready. When the count of "Discovered
nodes" becomes equal to the amount of the servers you have
booted in the network,
you can :ref:`create an OpenStack environment<create-env-ug>`,
:ref:`add nodes<add-nodes-ug>` into it,
and start :ref:`configuration<configure-env-ug>`.
Networking configuration is the most complicated part,
so please read :ref:`net-topology-plan`