bc8e3704db
File location changes to support DS flattend Install TOC Add minitocs and remove duplicate include directive Convert images to figures and add captions Incorporate server prep. steps Add links to post-install steps. Inline overview and HW topics in procs. Patchset 1 review updates. Rework to reuse some StX install content in partner context and some partner install content in StX context. Conditionalize ipv6_note Share aio_duplex_extend Conditionalize Openstack prod name Add HW requirement includes for worker and storage nodes. Link worker and stor reqs to DX, StD and Dedicated install topics. Fix comment notation Correct for duplicate strings in output Updates and additions based on GW review Make ansible_install_time_only note available DS. Move link target from r6 > r7 Temporarily restore alarms to satisfy build Migrate DX flattening to new layout Additional HW requirements to DX, Std and Dedicated tables. Migrate Standard flattening to new layout Roll this-ver forward to r7 Migrate Dedicated Storage flattening to new layout Address review comments. Standardize HW requirement tables Support horizontally conditionalized inline content Address additional review comments Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: I14c8a1e51f6b6ceff69be063a654b4aadb7d3b8c
64 lines
2.0 KiB
ReStructuredText
64 lines
2.0 KiB
ReStructuredText
--------
|
|
Overview
|
|
--------
|
|
|
|
Ironic is an OpenStack project that provisions bare metal machines. For
|
|
information about the Ironic project, see
|
|
`Ironic Documentation <https://docs.openstack.org/ironic>`__.
|
|
|
|
End user applications can be deployed on bare metal servers (instead of
|
|
virtual machines) by configuring OpenStack Ironic and deploying a pool of 1 or
|
|
more bare metal servers.
|
|
|
|
.. note::
|
|
|
|
If you are behind a corporate firewall or proxy, you need to set proxy
|
|
settings. Refer to :ref:`docker_proxy_config` for
|
|
details.
|
|
|
|
.. figure:: /deploy_install_guides/r7_release/figures/starlingx-deployment-options-ironic.png
|
|
:scale: 50%
|
|
:alt: Standard with Ironic deployment configuration
|
|
|
|
*Figure 1: Standard with Ironic deployment configuration*
|
|
|
|
Bare metal servers must be connected to:
|
|
|
|
* IPMI for OpenStack Ironic control
|
|
* ironic-provisioning-net tenant network via their untagged physical interface,
|
|
which supports PXE booting
|
|
|
|
As part of configuring OpenStack Ironic in StarlingX:
|
|
|
|
* An ironic-provisioning-net tenant network must be identified as the boot
|
|
network for bare metal nodes.
|
|
* An additional untagged physical interface must be configured on controller
|
|
nodes and connected to the ironic-provisioning-net tenant network. The
|
|
OpenStack Ironic tftpboot server will PXE boot the bare metal servers over
|
|
this interface.
|
|
|
|
.. note::
|
|
|
|
Bare metal servers are NOT:
|
|
|
|
* Running any OpenStack / StarlingX software; they are running end user
|
|
applications (for example, Glance Images).
|
|
* To be connected to the internal management network.
|
|
|
|
------------
|
|
Installation
|
|
------------
|
|
|
|
StarlingX currently supports only a bare metal installation of Ironic with a
|
|
standard configuration, either:
|
|
|
|
* :doc:`controller_storage_install_kubernetes`
|
|
|
|
* :doc:`dedicated_storage_install_kubernetes`
|
|
|
|
|
|
This guide assumes that you have a standard deployment installed and configured
|
|
with 2x controllers and at least 1x compute-labeled worker node, with the
|
|
StarlingX OpenStack application (|prefix|-openstack) applied.
|
|
|