You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2019. It is now read-only.
kni-install currently assumes Ironic has been stood up outside of the installer. Terraform will drive that instance of Ironic to provision the masters.
Instead, we'd like to be able to minimize external pre-requisites and be able to spin up Ironic within the bootstrap VM for provisioning the masters.
Either way, this instance of Ironic is supposed to be temporary. Once the cluster comes up, the baremetal-operator should be managing Ironic within the cluster.
The text was updated successfully, but these errors were encountered:
It occurs to me that we launch the masters and bootstrap concurrently. We'll need a mechanism to have Terraform wait for Ironic to be available on the bootstrap node before trying to create any baremetal resources.
The solution to this seems to be using depends_on, to have each individual Ironic resource wait for something. It can't be used at the module level, but this workaround may work for us.
We'd then use a local-exec provisioner on the bootstrap resource we're waiting for to poll until Ironic API is up.
kni-install currently assumes Ironic has been stood up outside of the installer. Terraform will drive that instance of Ironic to provision the masters.
Instead, we'd like to be able to minimize external pre-requisites and be able to spin up Ironic within the bootstrap VM for provisioning the masters.
Either way, this instance of Ironic is supposed to be temporary. Once the cluster comes up, the baremetal-operator should be managing Ironic within the cluster.
The text was updated successfully, but these errors were encountered: