So is it correcft to then state.. Based on this thread. That if you want to learn OSv4 and evaluate it as platform for running it on-premis as a development and system stack for applications, you are out of luck. Their is no method, documentation, to facilitate that.
Does this mean go back to Openshift 3 for now for that use case?
What is ETA when , when we sell designs to customers with OS4 liceses, they will then be able to start installing on premise?
Ok.. Good news. So we do have method today with OS 4 to deploy on premise.
You noted "AWS is easier" but non of my target customers would / can use that.
I am building out a referance desgin and SOW structure to jump from to do these deployments but need to "eat my own dog food" to learn and make sure I have all the moving parts correct.
As such. you refer to ""documentation exists". I think you meant: https://docs.openshift.com/container-platform/4.1/installing/installing_bare_metal/installing-bare-m... Which is fine... but it states
1) Deployment / boot strap VM must be RHCOS.
2) To deploy RHCOS I noted what appeared to be documentation... and location to get media.. and process. But it fails.
Do you have better documentation or note about where a more detailed guide is, or one that reflects on-site procedures?
I am glad to help document and post my process for the greater community. But having to get over this initial deployment hump.
OpenShift Container Platform (OCP) 4 does indeed require Red Hat Enterprise Linux CoreOS (RHCOS) for a setup, it is documented in the product documentation OCP but I can understand your problem since it can be a bit tricky to get started with.
The reason being is that RHCOS is still a bit sensitive that you have your DNS / DHCP / Load Balancer settings just right when doing an installation.
I'd be willing to try and help you being a sounding board on this if you'd could give me some more details of your setup and where you are currently stuck.
I would like to know:
Have you configured your DNS with the required settings?
Have you configured a load balancer with the required Virtual IPs?
What is your cluster subdomain?
What is your current DHCP settings?
Do you provide a DNS server through DHCP?
Do you provide a subdomain for DNS search options?
What do you envision the FQDN to be for your bootstrap, control planes(masters) workers?
I was looking at your screenshots earlier in this thread and its a bit unclear how far you are getting in the process.
Do you actually succeed downloading the image?
Does it complete the installation and reboot?
If yes, how far do you get when booting? Do you see anything when the machine is booting up?
One of the "features" of RHCOS is that it tends to redirect the console to an actual serial console. Meaning that it can be a bit frustrating to troubleshoot the initial boot if you are not comfortable with working around such issues. You can see the boot options when booting the RHCOS and it is possible to edit them.
Also, I saw that you mentioned that you are looking to build a offering around OCP 4, It is quite common for us from Red Hat Consulting to work with partners and customers when they build offers to ensure that they are correctly setup, just a good thing to consider.
I do suggest though, since OpenShift comes with subscriptions to run it that you open a support case on issues like these. It is important for us to make sure that we can keep on minimizing the occurences of these traits of the installer and user experience. Since as im sure you can vouch for, it can be a bit suboptimal :-)
First of, RHCOS is required, that is not an option to skip, the bootstrap and control plane requires it.
But, for workers it is possible to use RHEL-nodes, but it just doesn't make much sense to mix at that stage, since at that point you've already gone through the pain to setup RHCOS. But sure, there are circumstances where you still want to use RHEL on your workers.
> Yes.. I was using router with its DNS functions but tearing that out as I am not sure it can do all the zone features and SRV records / keys that are needed...
Great, so SRV records are supposedly setup correctly then. Good.
> if you have documentation on details of how they want the VIP defined.. I can follow.
> What is your cluster subdomain? penguinpages.local
Okay, that's good, but most likely not sufficient, since penguinpages.local is probably your TLD in general for your environment. OCP 4 requires a subdomain per cluster you install.
> Do you provide a subdomain for DNS search options? Yes. NTP, bootp server and file is the plan... once I get manual to what is needed
See previous answer, worth noting. RHCOS expects to get the subdomain of the cluster as the search path through DHCP.
> If yes, how far do you get when booting? Do you see anything when the machine is booting up? Screen shot shows. Just sits there at pxe such that it found no target MBR (chain load) or direct path (EFI file target). I did not boot up recovery image and mount file space to see what it plopped out there.
I wouldn't declare an unbootable machine as a succesful installation. I also do not see in any previous screenshot what your boot options for your VM was either.
Also, just noticed the screenshot which you opted to "skip" the ignition config, Which is a large indication to me you havnt been following the documentation:
>What do you envision the FQDN to be for your bootstrap, control planes(masters) workers? boot node will just be osmstr01
Yeah, that isn't a FQDN, so I can just assume you mean osmstr01.penguinpages.local. Again, this wouldn't be a good domain for OCP since it requires its own subdomain to live within.
Also, the first masters cannot be a bootstrap node. Its either a master (Control Plane) or bootstrap, not both. The Bootstrap node will be deleted after initial installation.It is just used to "Bootstrap" the cluster.
I can recommend just using a normal RHEL iso, and boot with that until you get your basic networking and DNS setup correct, It is way easier to verify it using that. At that point, proceed to the RHCOS installation.
As i mentioned before, RHCOS is very picky about the correct setup, you need to be very particular and follow the documentation to a great detail.