Actions
Feature #32716
open
Missing tasks to allow Openshift provisioning
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
- decision how to download the rootfs (coreos.live.rootfs_url=http://foreman.example.com/pxeboot/rhcos/rhcos-live-rootfs-<%= @host.params['version'] >.x86_64.img) and the metal image into foremans http server (coreos.inst.image_url=http://foreman.example.com/pxeboot/rhcos/rhcos-<= @host.params['version'] %>-x86_64-metal.x86_64.raw.gz) and code for this
- method for provisioning callback, so foreman knows when a node has successfully installed (for now a manual build cancel is needed after the host pxe booted successfully
- generic pxe template for rhcos (i will try to create a pullrequest, but im really lacking free time at the moment, i bought a house which im renovating in my freetime and i have to work 40 hours every week)
- maybe a new foreman template group (e.g openshift install template) which takes an openshift install.yaml as input and is able to run this https://mirror.openshift.com/pub/openshift-v4/clients/ocp/4.7.13/openshift-install-linux.tar.gz binary to produce openshift install files (master,bootstrap,worker.ign) which are then put into the foreman http server
- a positive side effect of this would be we would not need those uncool hostvariables which i used in the pxe template like openshift version and cluster name. the only complicated thing would be to detect/define somehow which host will be a master/worker/boostrap node
- all the same for fedora coreos and openshift origin (its basically exact the same, just fedora instead of redhat coreos and other openshift install binarys)
Updated by
Actions