baremetal: Enable ironic on the bootstrap VM #2060
Assignees
Labels
platform/baremetal
IPI bare metal hosts platform
Comments
|
/assign |
|
/label platform/baremetal |
|
cc @russellb please can you add the platform/baremetal label - thanks! |
This was referenced Jul 22, 2019
This was referenced Jul 24, 2019
stbenjam
pushed a commit
to hardys/installer
that referenced
this issue
Jul 29, 2019
For the baremetal platform we require two different bootimages, the QEMU one for the libvirt based bootstrap VM, and the OpenStack one that contains the necessary Ironic config drive support to pass data to ignition. So we rework the Image abstraction by adding a new BootstrapImage type/asset, which returns the same as Image in all cases except for the baremetal platform. This also aligns with the tfvars renamed in openshift#2044 and allows us to pass the rhcos.QEMU image via BootstrapImage to terraform but leaves the OpenStack image URL available for future use to deploy masters via follow-up PRs that implement issue openshift#2060 and also correctly set the worker machineset providerSpec for the baremetal-operator. Related: openshift#2037
hardys
pushed a commit
to hardys/installer
that referenced
this issue
Aug 13, 2019
This adds ironic to the bootstrap VM for the baremetal IPI platform. Related: openshift#2060
|
Closed via #2079 |
jhixson74
pushed a commit
to jhixson74/installer
that referenced
this issue
Dec 6, 2019
This adds ironic to the bootstrap VM for the baremetal IPI platform. Related: openshift#2060
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
openshift-install currently assumes Ironic has been stood up outside of the installer. Terraform will drive that instance of Ironic to provision the masters which works but isn't the desired self-contained integration.
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.
In addition, this instance of Ironic is supposed to be temporary. Once the cluster comes up, the baremetal-operator should be managing Ironic within the cluster so moving the master deployment instance of Ironic to the bootstrap VM solves this problem, because the bootstrap VM will be destroyed when boostrap of the masters is completed.
Copied from openshift-metal3/kni-installer#68
The text was updated successfully, but these errors were encountered: