enterprise_gateway
enterprise_gateway copied to clipboard
jupyter-server
Do we have R - socketConnection which works on IPV6 please?
Hi @mdsowmya - IPv6 support for our kernel launchers and EG response address is something that will need to come from the community at this time. We neither have the bandwidth or the environment to address this. That said, we would be happy to help guide the effort.
If you're interested in making this contribution, I would be happy to steer you in the proper direction. I would also recommend we merge #877 prior to doing so since it not only changes the response address mechanism but removes the R-specific code for conveying the connection information back to the EG server, utilizing a python implementation instead. This way, both python and R launchers could be addressed with similar logic.
Hi - EG python kernel spawn is done. But need suggestion on R-kernel : https://github.com/IRkernel/IRkernel/issues/674 R-kernel file where the client socketConnection is called is written in R-language which i'm not familiiar with. But when searched online whether there is method that supports IPV6 socketConnection dint find suggestion yet.
the gateway_listener.py is python file & i could make the socketConnection change. But R kernel socketCommunication is not working on IPV6 cluster. Reason/logs : https://github.com/IRkernel/IRkernel/issues/674.
Could you please help
Hi @mdsowmya - thanks for taking a look at this. One of the changes in PR #877 is that the listener socket and the 5 zmq ports are created with python code (rather than R). This was primarily done to deal with the changes for encryption, but I also figured it would make for easier maintainability. I would suggest you look at that branch. The changes are backwards compatible, so you should be able to just rebuild EG and not have to update your kernelspecs until you're ready. We will try to get it reviewed/merged fairly soon.
I'm assuming that if the sockets are created with IPV6, then the R kernel should just work if it's using zmq. However, if we find there are kernel changes necessary, then an issue on the IRKernel repo will be necessary. We only have control over the port creation and the listener socket operation.