Chapter 6. Installing Red Hat OpenShift 3.11 on IBM PowerVC 119
2. Initialize the Terraf orm working directory:
3. Create an execution plan:
4. Apply the required changes to reach the wanted state:
After this process is completed, the virtual machines are up and running.
cd <PATH> #ocp-aio /ocp-7nodes ocp-3nodes
terraform init
Initializing the backend...
Initializing provider plugins...
The following providers do not have any version constraints in configuration,
so the latest version was installed.
...
Output truncated
...
* provider.null: version = "~> 2.1"
* provider.openstack: version = "~> 1.22"
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
terraform plan
Refreshing Terraform state in-memory prior to plan...
...
Output truncated
...
Plan: 33 to add, 0 to change, 0 to destroy.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
terraform apply
data.openstack_compute_availability_zones_v2.AZ: Refreshing state...
...
Output truncated
...
Plan: 33 to add, 0 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.
  Enter a value: yes
...
Output truncated
...
null_resource.vm4_post_install_config[0] (remote-exec): ---start adding 
user_public_key---
Apply complete! Resources: 33 added, 0 changed, 0 destroyed.