Containerized imcsdk support for CIMC 3.0 using Docker

[vhosakot]

The new CIMC version 3.0 needs:

• TLS 1.2
• Python2 version >= 2.7.9 or Python3 version >= 3.2
• OpenSSL version >= 1.0.1

https://github.com/CiscoUcs/imcsdk/blob/master/docs/imcsdk_ug.rst#getting-started

RHEL ships with Python 2.7.5 as the system Python version:

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.2 (Maipo)

# python -V
Python 2.7.5

CentOS also ships with Python 2.7.5 as the system Python version:

# cat /etc/centos-release
CentOS Linux release 7.3.1611 (Core)

# python -V
Python 2.7.5

Upgrading system Python in RHEL and CentOS from Python 2.7.5 to Python >= 2.7.9 breaks a lot of packages like pip, yum, ansible, OpenStack packages, etc.

Upgrading system OpenSSL to version >= 1.0.1 may break VPN client and SSL. Apple MacOS sierra ships with OpenSSL 0.9.8 and will not even allow the user to upgrade OpenSSL.

Production/staging/ops testbeds may not even allow us to upgrade system Python and system OpenSSL as it may break other packages/features.

Hence, the best approach is to containerize imcsdk using Docker with all the required dependencies/packages needed to programmatically interact with CIMC 3.0.

This pull request adds Containerized imcsdk support for CIMC 3.0 using Docker.

The Docker container has the following packages needed for CIMC 3.0:

• Python 2.7.13 (Python >= 2.7.9 is needed for CIMC 3.0)
• pip with Python 2.7.13
• OpenSSL 1.0.1
• Cisco's Python imcsdk library (https://github.com/CiscoUcs/imcsdk)
• DMTF's Python RedFish library (python-redfish-library in https://github.com/DMTF/python-redfish-library)
• epel-release and latest Ansible (if the user wants to automate anything with CIMC 3.0)
• Python requests library needed to interact with RedFish URIs /redfish/v1/*

The README file has all the instructions to use this Docker container with CIMC 3.0.

[iawells]

Is your argument that we will need to ship this or that we should use this environment for dev while we work something out? Shipping this would be a can of worms.

You probably shouldn't be using pip at all.

[vhosakot]

@iawells Thanks for your comments. Yes, I think users/customers using CIMC 3.0 need to use this Docker container if they do not want to upgrade their Python to >= 2.7.9 and OpenSSL to 1.0.1.

Maintaining/versioning/shipping this Dockerfile should be very easy.

What is wrong with pip to install a stable upstream package? If pip causes problems, we can use yum or install from source as well using wget, curl, tar, setup.py, make, etc.

[vhosakot]

@vvb @waghswapnil @ragupta-git FYI.

[vvb]

LGTM. Thanks for the changes.

[vhosakot]

@vvb Thanks a lot for merging this! :) Please let me know if there are any questions using the Docker container with CIMC 3.0 and I'd love to help with it.