Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1
Technical White Paper on
Physical Bare-Metal Server
Issue V1.0
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei
and the customer. All or part of the products, services and features described in this document may not
be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all
statements, information, and recommendations in this document are provided "AS IS" without
warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://enterprise.huawei.com
Overview
This document describes the FusionSphere physical bare-metal server technology.
Intended Audience
This document is intended for Huawei marketing and sales engineers, as well as FusionSphere
distributors in their market development projects.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Contents
1.1 Background
In OpenStack scenario, pure virtualization cannot fully meet users' requirements. Physical
servers are demanded in scenarios that require high performance or need to use physical
hardware or interfaces.
Physical bare-metal servers provide a new mode of using physical servers, which allows you
to:
Use OpenStack VM interfaces to provision physical bare-metal servers.
Use OpenStack Nova interfaces to create a bare-metal server image with specified
specifications, and query, modify, start, stop, and restart a physical bare-metal server.
Attach a Cinder-created volume to a physical bare-metal server using the interfaces for
attaching a volume to a VM.
Create a virtual port on a physical bare-metal server to connect Neutron VLAN or
VXLAN networks for communicating with VMs.
server image to the glance image server. When provisioning the physical bare-metal server,
Ironic-conductor downloads the physical bare-metal server image from the glance image
server and automatically registers the image as physical bare-metal server's OS.
The physical bare-metal server management function also supports the change of a bare-metal
server's boot option to preboot execution environment (PXE). After you power on the server,
the system loads a miniOS and then executes the installation scripts to download the needed
basic OS to the server and decompress the OS in a disk partition on the server. After
decompressing the OS, the system informs Ironic-conductor to change the physical bare-metal
server's boot option to local boot. The new boot takes effect after the physical bare-metal
server is restarted.
Life Cycle Management
To make multiple physical bare-metal servers available for life cycle management, register
them in the Ironic database to form a physical bare-metal server resource pool. Then you can
use Nova interfaces to create, delete, query, modify, start, or stop a server in the pool. The
server image and specifications can be specified during creation, and Nova scheduler is
responsible for scheduling and filtering the required servers.
Automatic Storage Attaching
After a physical bare-metal server starts, the management agent built in the physical
bare-metal server can automatically attach a volume to or detach a volume from the server.
Connection to a Virtual Network
The built-in OVS and management agent in a physical bare-metal server can query, discover,
and configure the virtual networks that the bare-metal server can connect to, and can connect
the bare-metal server to the VLAN and VXLAN created by Neutron.
1. The importance of Ironic in OpenStack is similar to Nova compute driver. Ironic consists
of Nova compute driver (Ironic driver), Ironic-api, Ironic-conductor, and Ironic-agent
processes.
2. When provisioning physical bare-metal servers, Nova sends the requests to the supported
Nova compute node by the specified AZ or host group.
3. Nova compute (Ironic driver) performs the required operations, such as downloading the
bare-metal server image, attaching a volume to the server, and creating ports on it. Nova
compute (Ironic driver) invokes the Ironic-api process to power on or off a physical
bare-metal server or to change the server's boot mode.
4. After receiving an operation request, Ironic-api invokes the Ironic-conductor interface to
carry out the required operation using IPMI, for example, power on or off a server,
restart a server, change the server's boot mode, and install an OS for the server in PXE
mode.
5. Ironic-conductor invokes the CPS interfaces to install an OS on a physical bare-metal
server. After the OS is installed, the built-in management agent and OVS in the server
run to issue and configure storage and network settings for the server.
3.1 Preparations
Before provisioning physical bare-metal servers, perform the following operations:
Configure an IPMI network plane for OpenStack control nodes to ensure that the control
nodes are connected to the BMC plane of the to-be managed physical bare-metal server
and that the control nodes are allowed to control the server's power status and boot mode
using IPMI.
Change the boot mode of all physical bare-metal servers to once PXE, and then power on
the servers to make CPS automatically discover them. This process is the same as the
common server installation process.
Select a VM's qcow2 image and convert the image to a physical bare-metal server image
using an image-making tool in the Linux environment.
Import the physical bare-metal server image to Glance and register it as a physical
bare-metal server image.
On Service Center (SC), select the registered physical bare-metal server image and use
the specified physical bare-metal server flavor to create physical bare-metal servers by
invoking Nova interfaces. During the creation process, you can specify the network the
physical bare-metal servers are to be connected.
Ironic-conductor downloads the physical bare-metal server image, registers it in the
software repository, and changes the bare-metal server boot mode to PXE. After
restarting the physical bare-metal servers, Ironic-conductor PXE-installs the OS
specified in the image for the bare-metal servers.
Ironic-conductor regularly queries the image installation progress. After the image is
installed, Ironic-conductor restarts the physical bare-metal servers and changes the
physical bare-metal servers' deployment status on Ironic, and then notifies Nova that the
image installation is complete.
After the physical bare-metal servers are restarted, their built-in management agents run
to obtain network configurations and create virtual network devices for the bare-metal
servers to automatically connect to VLAN or VXLAN.