openstack/fuel-docs
Code Issues Proposed changes

[Restructuring] Boot the Fuel Slave nodes

Browse Source 
Adds the rewritten Boot the Fuel Slave nodes section to
the Installation Guide.

Change-Id: Ie4aca82835146ad0a7b1fa2e8b7e32c296f22022
This commit is contained in:
OlgaGusarenko
2015-11-11 17:30:57 +02:00
parent 1af548009f
commit 7d44a0cf27
1 changed files with 64 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
pages/draft/fuel-install-guide/boot_slave_nodes.rst Normal file
View File

@@ -0,0 +1,64 @@
.. _install_boot_nodes:
Boot the Fuel Slave nodes
~~~~~~~~~~~~~~~~~~~~~~~~~
Before you boot the Fuel Slave nodes, verify that you have completed
the following tasks:
#. `Install and boot the Fuel Master node <install_install_fuel_master_node>`.
#. If you plan using RAID arrays, configure you RAID-attached devices first.
#. Configure the network:
* If you use bare-metal servers, verify that the Fuel Slave nodes are
physically connected to the same network as the Fuel Master node.
* If you use virtual servers, verify that the Fuel Slave nodes
are bridged to the same network as the Fuel Master node.
The Fuel Master node and the Fuel Slave nodes must be in
the same L2 network segment.
**To boot the Fuel Slave nodes:**
#. Power on a Fuel Slave node.
#. Boot the Fuel Slave node through PXE using one of the following options:
* Modify the boot order in BIOS to PXE boot.
* Press the appropriate key to initiate a PXE boot.
.. warning::
If the Fuel Slave node has several network interfaces, enable
the PXE boot on the interface that is on the same network
as Admin (PXE) network on the Fuel Master node.
#. Repeat the procedure for all the Fuel Slave nodes you will use for your
OpenStack environment.
Boot workflow of a Fuel Slave node
----------------------------------
The boot workflow of a Fuel Slave node does not require any user interaction.
For general understanding of the processes that take place in the system when
the Fuel Slave node is booting, get acquainted with the boot procedure:
#. The Fuel Slave node sends out a DHCP discovery request and gets the response
from the Fuel Master node that runs the DHCP server.
#. On receiving the response, the Fuel Slave node fetches the PXELINUX
bootloader and the bootstrap image from the Fuel Master node's TFTP
server, and boots into it.
#. On loading the image, the Fuel Slave node reports readiness and
configuration to the Fuel Master node.
The number of discovered Fuel Slave nodes appears in the Fuel web UI.
When all nodes boot, you can create an OpenStack environment.
.. seealso::
- `create-env-ug`