Skip to content

BZ1851320 - Updated metadata file extension #29988

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
codyhoag merged 1 commit into from
Mar 3, 2021
Merged

BZ1851320 - Updated metadata file extension #29988

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions modules/installation-osp-creating-bootstrap-machine.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Create a bootstrap machine and give it the network access it needs to run on {rh
* You downloaded the modules in "Downloading playbook dependencies."
* You downloaded the playbooks in "Downloading the installation playbooks."
* The `inventory.yaml`, `common.yaml`, and `bootstrap.yaml` Ansible playbooks are in a common directory.
* The `metadata.yaml` file that the installation program created is in the same directory as the Ansible playbooks.
* The `metadata.json` file that the installation program created is in the same directory as the Ansible playbooks.

.Procedure

Expand All @@ -29,4 +29,4 @@ $ ansible-playbook -i inventory.yaml bootstrap.yaml
[source,terminal]
----
$ openstack console log show "$INFRA_ID-bootstrap"
----
----
4 changes: 2 additions & 2 deletions modules/installation-osp-creating-compute-machines.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ After standing up the control plane, create compute machines. Red Hat provides a
* You downloaded the modules in "Downloading playbook dependencies."
* You downloaded the playbooks in "Downloading the installation playbooks."
* The `inventory.yaml`, `common.yaml`, and `compute-nodes.yaml` Ansible playbooks are in a common directory.
* The `metadata.yaml` file that the installation program created is in the same directory as the Ansible playbooks.
* The `metadata.json` file that the installation program created is in the same directory as the Ansible playbooks.
* The control plane is active.

.Procedure
Expand All @@ -28,4 +28,4 @@ $ ansible-playbook -i inventory.yaml compute-nodes.yaml

.Next steps

* Approve the certificate signing requests for the machines.
* Approve the certificate signing requests for the machines.