Hide Forgot
Document URL: https://docs.openshift.com/enterprise/3.2/install_config/routing_from_edge_lb.html#establishing-a-tunnel-using-a-ramp-node Section Number and Name: Establishing a Tunnel Using a Ramp Node: On the ramp node Describe the issue: Enhancement / Amendment required for OSE Documentation (Ramp node) The steps which are described for setting the tunnel on the ramp node (https://docs.openshift.com/enterprise/3.2/install_config/routing_from_edge_lb.html#establishing-a-tunnel-using-a-ramp-node) are incomplete and can lead clients to surprises. Indeed, it is not mentioned anywhere that the sections 3,4 and 5 will not persist a reboot and therefore some manual interventions are required to bring the ramp node back on an operational level. Suggestions for improvement: It will be wise to amend the documentation worth so as to mention it and also provide an example of using interface configuration files (/etc/sysconfig/network-scripts/ifcfg-tunx). As the system boots, it uses these files to determine what interfaces to bring up and how to configure them. Additional information:
PR made for this: https://github.com/openshift/openshift-docs/pull/2846 Brendan, could I please get an ack that this fulfills this BZ? Thanks, much!
We probably want to execute this setup script in entirety to have the ramp node come alive properly after a reboot: https://github.com/ramr/openshift-f5-env-setup/blob/master/setup-ramp-node-sdn
Hi, The doc states to change the /etc/sysconfig/network-scripts/ifcfg-tun<N> file, but then the tunnel is created with "ip". Shouldn't there be an example of what to put in the ifcfg-tun<N> file? Regards,
Brendan I did send you an email about this BZ saying that the PR was incorrect and that I'd be following up with an email to sme list. Maybe I should have put the information in here instead. Rajat and Ram have a script that makes the steps persist. It's going to be written into a KB article. Once it is, we can see what we want to put into the docs. Should be done within the next week.
https://github.com/rajatchopra/f5rampnodekb/blob/master/README.md Is a detailed write-up of how to persist ramp node configuration changes.
With the addition of the KBase article (which I think is OK and I don't think I can add anything to), and the knowledge that this will be fixed by OCP 3.4, I don't think anything needs to be added to the docs. Putting a link into the KBase article will bring up the conversation about putting the procedure into the docs again, so I don't think it's necessary. I'll put this to closed, and close my PR from above. Anyone, feel free to let me know if you disagree.
*** Bug 1409554 has been marked as a duplicate of this bug. ***