Hi. Am 19.04.2018 um 10:46 schrieb Fabio Martinelli: > Dear Colleagues > > In few time I've to migrate several corporate applications from a > RedHat6 LXC cluster to a RedHat7 OpenShift Origin 3.7.2 cluster > > here the application Developers are use to write an Ansible playbook > for each app so they've explicitly requested me to prepare a base > CentOS7 container running as non-root and featuring an unprivileged > SSHd daemon in order to run their well tested Ansible playbooks, > furthermore to place the container /home on a dedicated GlusterFS > volume to make it persistent along the time ; last ring of this chain > is the oc port-forward command that's in charge of connecting the > Developers workstation with the unprivileged SSHd daemon just for the > Ansible playbook execution time. > > this is actually working pretty well but the fact that the oc > port-forward command at certain point cuts the connection and the > Ansible run gets obviously affected making the Developer experience > disappointing ; on the other end the SSHd process didn't stop. Does the port-forwarding goes thru a proxy? Is there a amount of time when this happens (= timeout) What's in the events when this happen?
> kindly which settings may I change both on the Origin Masters yaml > files and on the Origin Nodes yaml files in order to prevent this issue ? > > I'm aware that the application Developers should rewrite their works > in terms of Dockerfiles but for the time being they've really no time > to do that. > > > Many thanks, > Fabio Martinelli Best regards Aleks ME2Digital _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
