Closed DP-B21 closed 2 months ago
Thank you, yes. I see there are broadly two ways forward:
1) Try to deploy the terraform to the systems project as is and see how openstack complains, then adjust the quota in response to that. 2) Inspect the terraform files to see what it's going to require and adjust the project quota based on that expectation.
(Or probably a combination of both)
Thank you.
Fork created - https://github.com/DP-B21/terraform-aufn-fork/tree/fork
pushed the new changed files with changes to Providers.tf, credentiatls.auto.tfvars and vars.tf to accommodate the Openstack Systems project and to indicate what fields need to be changed by anyone trying to use this terraform env
Terraform script seems to work once the file provisioning at the end is commented out. it seems like i get a timeout on the remote-exec
provisioner - my theory is that the VMs are not fully booted before terraform tries to run the final bash scripts:
╷
│ Error: remote-exec provisioner error
│
│ with null_resource.lab[0],
│ on openstack-device.tf line 180, in resource "null_resource" "lab":
│ 180: provisioner "remote-exec" {
│
│ timeout - last error: dial tcp 10.65.0.27:22: i/o timeout
╵
the reason for the error above is due to the SSH credentials not being correct, thus not allowing my local machine to scp
and execute any of the "file" provision blocks. I will investigate
Openstack setup has been completed alongside with access to the Horizon GUI with working vm as proof of concept
I was given the task to build a cluster by forking the tf script below:
https://github.com/stackhpc/terraform-aufn/blob/smslab/yoga/openstack-device.tf
It is expected that I will change the quotas for the Systems project on the Somerville Openstack