Adds dockerfiles for development

Issues:
Fixes #695

Problem:
Dockerfiles did not exist in the repo so there was no convenient way
for existing developers to test and dev the SDK on a known platform

Analysis:
This patch adds dockerfiles so that there is a common dev platform

Tests:
none

Author: caphrim007

devtools/dockerfiles/.dockerignore

@@ -0,0 +1 @@
+*

devtools/dockerfiles/Dockerfile.python2

@@ -0,0 +1,40 @@
+# Dockerfile to build python 2 environment
+#
+# This dockerfile can be used to build the same python2 environment that we
+# use for testing and development. To build the docker container, run the
+# following commands.
+#
+#     cd devtools/dockerfiles
+#     docker build -f Dockerfile.python2 -t python2 .
+#
+# The docker container can then be used as any other docker containter would
+# be used. Connecting to your BIG-IP inside of Vagrant may require that you
+# add a forwarded host in Docker to the Vagrant machine itself.
+#
+# For example,
+#
+#     docker run -it --add-host="localhost:192.168.1.1" \
+#         -v "${HOME}/src/trupp/f5-common-python:/artifacts" python2
+#
+# The 192.x address in this case is the IP address of vboxnet0 interfaces on
+# your host machine (the one that runs docker and vagrant)
+
+FROM python:2
+MAINTAINER @f5networks
+
+RUN mkdir -p /artifacts/coverage
+WORKDIR /artifacts
+
+RUN apt-get update && apt-get -y install vim
+
+RUN pip install hacking==0.10.2 \
+    mock==1.3.0 \
+    pytest==2.9.1 \
+    pytest-cov>=2.2.1 \
+    git+https://github.com/F5Networks/pytest-symbols.git \
+    f5-icontrol-rest==1.0.7 \
+    pyOpenSSL==16.0.0 \
+    python-coveralls==2.7.0 \
+    ordereddict
+
+CMD /bin/bash

devtools/dockerfiles/Dockerfile.python3

@@ -0,0 +1,39 @@
+# Dockerfile to build python 3 environment
+#
+# This dockerfile can be used to build the same python2 environment that we
+# use for testing and development. To build the docker container, run the
+# following commands.
+#
+#     cd devtools/dockerfiles
+#     docker build -f Dockerfile.python2 -t python3 .
+#
+# The docker container can then be used as any other docker containter would
+# be used. Connecting to your BIG-IP inside of Vagrant may require that you
+# add a forwarded host in Docker to the Vagrant machine itself.
+#
+# For example,
+#
+#     docker run -it --add-host="localhost:192.168.1.1" \
+#         -v "${HOME}/src/trupp/f5-common-python:/artifacts" python2
+#
+# The 192.x address in this case is the IP address of vboxnet0 interfaces on
+# your host machine (the one that runs docker and vagrant)
+
+FROM python:3
+MAINTAINER @f5networks
+
+RUN mkdir -p /artifacts/coverage
+WORKDIR /artifacts
+
+RUN apt-get update && apt-get -y install vim
+
+RUN pip install hacking==0.10.2 \
+    mock==1.3.0 \
+    pytest==2.9.1 \
+    pytest-cov>=2.2.1 \
+    git+https://github.com/F5Networks/pytest-symbols.git \
+    f5-icontrol-rest==1.0.7 \
+    pyOpenSSL==16.0.0 \
+    python-coveralls==2.7.0
+
+CMD /bin/bash

devtools/dockerfiles/README.md

@@ -0,0 +1,26 @@
+# Dockerfiles for testing the f5-sdk
+
+This directory contains Dockerfiles that can be used to test the SDK.
+
+## Building
+
+To create the necessary docker images, you can use the following commands for...
+
+Python 2
+
+    docker build -f Dockerfile.python2 -t python2 .
+
+And Python 3
+
+    docker build -f Dockerfile.python2 -t python2 .
+
+## Running
+
+I use these on a Mac and found that they work as expected. Some explanation is
+required
+
+  * `docker run -it -v "${PWD}:/artifacts" --add-host="localhost:192.168.26.66" python2`
+  * `docker run -it -v "${PWD}:/artifacts" --add-host="localhost:192.168.26.66" python3`
+
+The `--add-host` argument lets me communicate with my host machine via that
+IP address, but refer to it as "localhost".