mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
325e72a6f0
The doc explicitly said that BM control plane nodes were supported on OpenStack platform while it's not. QE don't test it either. We do however support BM compute nodes. Related to OCPBUGS-22683.
124 lines
4.6 KiB
Plaintext
124 lines
4.6 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/installing_openstack/installing-openstack-installer-custom.adoc
|
|
// * installing/installing_openstack/installing-openstack-user.adoc
|
|
|
|
ifeval::["{context}" == "installing-openstack-installer-custom"]
|
|
:osp-ipi:
|
|
endif::[]
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="installation-osp-deploying-bare-metal-machines_{context}"]
|
|
= Deploying a cluster with bare metal machines
|
|
|
|
If you want your cluster to use bare metal machines, modify the
|
|
ifdef::osp-ipi[`install-config.yaml`]
|
|
ifndef::osp-ipi[`inventory.yaml`]
|
|
file. Your cluster can have compute machines running on bare metal.
|
|
|
|
[NOTE]
|
|
====
|
|
Be sure that your `install-config.yaml` file reflects whether the {rh-openstack} network that you use for bare metal workers supports floating IP addresses or not.
|
|
====
|
|
|
|
.Prerequisites
|
|
|
|
* The {rh-openstack} link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/bare_metal_provisioning/index[Bare Metal service (Ironic)] is enabled and accessible via the {rh-openstack} Compute API.
|
|
|
|
* Bare metal is available as link:https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/configuring_the_bare_metal_provisioning_service/assembly_configuring-the-bare-metal-provisioning-service-after-deployment#proc_creating-flavors-for-launching-bare-metal-instances_bare-metal-post-deployment[a {rh-openstack} flavor].
|
|
|
|
* If your cluster runs on an {rh-openstack} version that is more than 16.1.6 and less than 16.2.4, bare metal workers do not function due to a link:https://bugzilla.redhat.com/show_bug.cgi?id=2033953[known issue] that causes the metadata service to be unavailable for services on {product-title} nodes.
|
|
|
|
|
|
* The {rh-openstack} network supports both VM and bare metal server attachment.
|
|
|
|
* If you want to deploy the machines on a pre-existing network, a {rh-openstack} subnet is provisioned.
|
|
|
|
* If you want to deploy the machines on an installer-provisioned network, the {rh-openstack} Bare Metal service (Ironic) is able to listen for and interact with Preboot eXecution Environment (PXE) boot machines that run on tenant networks.
|
|
|
|
ifdef::osp-ipi[]
|
|
* You created an `install-config.yaml` file as part of the {product-title} installation process.
|
|
endif::osp-ipi[]
|
|
|
|
ifndef::osp-ipi[]
|
|
* You created an `inventory.yaml` file as part of the {product-title} installation process.
|
|
endif::osp-ipi[]
|
|
|
|
.Procedure
|
|
|
|
ifdef::osp-ipi[]
|
|
. In the `install-config.yaml` file, edit the flavors for machines:
|
|
.. Change the value of `compute.platform.openstack.type` to a bare metal flavor.
|
|
.. If you want to deploy your machines on a pre-existing network, change the value of `platform.openstack.machinesSubnet` to the {rh-openstack} subnet UUID of the network.
|
|
+
|
|
.An example bare metal `install-config.yaml` file
|
|
[source,yaml]
|
|
----
|
|
compute:
|
|
- architecture: amd64
|
|
hyperthreading: Enabled
|
|
name: worker
|
|
platform:
|
|
openstack:
|
|
type: <bare_metal_compute_flavor> <1>
|
|
replicas: 3
|
|
...
|
|
|
|
platform:
|
|
openstack:
|
|
machinesSubnet: <subnet_UUID> <2>
|
|
...
|
|
----
|
|
<1> Change this value to a bare metal flavor to use for compute machines.
|
|
<2> If you want to use a pre-existing network, change this value to the UUID of the {rh-openstack} subnet.
|
|
|
|
|
|
Use the updated `install-config.yaml` file to complete the installation process.
|
|
The compute machines that are created during deployment use the flavor that you
|
|
added to the file.
|
|
endif::osp-ipi[]
|
|
|
|
ifndef::osp-ipi[]
|
|
. In the `inventory.yaml` file, edit the flavors for machines:
|
|
.. Change the value of `os_flavor_worker` to a bare metal flavor.
|
|
+
|
|
.An example bare metal `inventory.yaml` file
|
|
[source,yaml]
|
|
----
|
|
all:
|
|
hosts:
|
|
localhost:
|
|
ansible_connection: local
|
|
ansible_python_interpreter: "{{ansible_playbook_python}}"
|
|
|
|
# User-provided values
|
|
os_subnet_range: '10.0.0.0/16'
|
|
os_flavor_master: 'my-vm-flavor'
|
|
os_flavor_worker: 'my-bare-metal-flavor' <1>
|
|
os_image_rhcos: 'rhcos'
|
|
os_external_network: 'external'
|
|
...
|
|
----
|
|
<1> Change this value to a bare metal flavor to use for compute machines.
|
|
|
|
Use the updated `inventory.yaml` file to complete the installation process.
|
|
Machines that are created during deployment use the flavor that you
|
|
added to the file.
|
|
endif::osp-ipi[]
|
|
|
|
[NOTE]
|
|
====
|
|
The installer may time out while waiting for bare metal machines to boot.
|
|
|
|
If the installer times out, restart and then complete the deployment by using the `wait-for` command of the installer. For example:
|
|
|
|
[source,terminal]
|
|
----
|
|
$ ./openshift-install wait-for install-complete --log-level debug
|
|
----
|
|
====
|
|
|
|
ifeval::["{context}" == "installing-openstack-installer-custom"]
|
|
:!osp-ipi:
|
|
endif::[]
|