mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
48 lines
1.7 KiB
Plaintext
48 lines
1.7 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/installing_openstack/installing-openstack-user.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="installation-osp-creating-control-plane_{context}"]
|
|
= Creating the control plane machines on {rh-openstack}
|
|
|
|
Create three control plane machines by using the Ignition config files that you generated. Red Hat provides an Ansible playbook that you run to simplify this process.
|
|
|
|
.Prerequisites
|
|
|
|
* You downloaded the modules in "Downloading playbook dependencies".
|
|
* You downloaded the playbooks in "Downloading the installation playbooks".
|
|
* The infrastructure ID from the installation program's metadata file is set as an environment variable (`$INFRA_ID`).
|
|
* The `inventory.yaml`, `common.yaml`, and `control-plane.yaml` Ansible playbooks are in a common directory.
|
|
* You have the three Ignition files that were created in "Creating control plane Ignition config files".
|
|
|
|
.Procedure
|
|
|
|
. On a command line, change the working directory to the location of the playbooks.
|
|
|
|
. If the control plane Ignition config files are not already in your working directory, copy them into it.
|
|
|
|
. On a command line, run the `control-plane.yaml` playbook:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ ansible-playbook -i inventory.yaml control-plane.yaml
|
|
----
|
|
|
|
. Run the following command to monitor the bootstrapping process:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ openshift-install wait-for bootstrap-complete
|
|
----
|
|
+
|
|
You will see messages that confirm that the control plane machines are running and have joined the cluster:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
INFO API v1.34.2 up
|
|
INFO Waiting up to 30m0s for bootstrapping to complete...
|
|
...
|
|
INFO It is now safe to remove the bootstrap resources
|
|
----
|