Old python version, requests SSL warnings

[johnarnold]

In StackStorm container, I get warnings from urllib3 when running a module manually. I suspect this will show up in many other places too.

2017-06-28 15:55:36,218 ERROR [-] /opt/stackstorm/st2/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py:318: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/security.html#snimissingwarning.
SNIMissingWarning

2017-06-28 15:55:36,218 ERROR [-] /opt/stackstorm/st2/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py:122: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/security.html#insecureplatformwarning.
InsecurePlatformWarning

I've tried forcing requests[secure] and urllib3[secure] but we really need a newer python version to fix the SNI issue.

root@56b83c8b706d:/# python --version
Python 2.7.6

root@56b83c8b706d:/# python --version
Python 2.7.6

I suggest going to 16.04 for the base image, it's the new LTS...

[LindsayHill]

There are other reasons for not going to 16.04 yet - see #29

[johnarnold]

@LindsayHill fair enough w.r.t. 16.04 / systemd, but that's not a great reason to run old python.

[LindsayHill]

@johnarnold I don't think there's any easy immediate answers. Should we package a newer version of Python with st2?