Initial commit for sparkml serving container

Author: orchidmajumder

CHANGELOG.md

@@ -0,0 +1,4 @@
+2.2
+===
+
+Initial release of sagemaker-sparkml-serving-container, supporting Spark major version 2.2.

CONTRIBUTING.md

@@ -11,13 +11,13 @@ information to effectively respond to your bug report or contribution.
 
 We welcome you to use the GitHub issue tracker to report bugs or suggest features.
 
-When filing an issue, please check [existing open](https://github.com/aws/sagemaker-spark-serving-container/issues), or [recently closed](https://github.com/aws/sagemaker-spark-serving-container/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already 
+When filing an issue, please check [existing open](https://github.com/aws/sagemaker-python-sdk/issues), or [recently closed](https://github.com/aws/sagemaker-python-sdk/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already 
 reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
 
 * A reproducible test case or series of steps
 * The version of our code being used
 * Any modifications you've made relevant to the bug
-* Anything unusual about your environment or deployment
+* A description of your environment or deployment
 
 
 ## Contributing via Pull Requests
@@ -31,19 +31,17 @@ To send us a pull request, please:
 
 1. Fork the repository.
 2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
-3. Ensure local tests pass.
-4. Commit to your fork using clear commit messages.
-5. Send us a pull request, answering any default questions in the pull request interface.
-6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+3. Include unit tests when you contribute new features or make bug fixes, as they help to a) prove that your code works correctly, and b) guard against future breaking changes to lower the maintenance cost.
+4. Ensure local tests pass.
+5. Update the [changelog](https://github.com/aws/sagemaker-python-sdk/blob/master/CHANGELOG.rst) with a description of your changes for any code contribution.
+6. Commit to your fork using [clear and imperative commit messages](https://chris.beams.io/posts/git-commit/).
+7. Send us a pull request, answering any default questions in the pull request interface.
+8. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
 
 GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and 
 [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
 
-## Finding contributions to work on
-Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws/sagemaker-spark-serving-container/labels/help%20wanted) issues is a great place to start. 
-
-
 ## Code of Conduct
 This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 
 For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
@@ -56,6 +54,6 @@ If you discover a potential security issue in this project we ask that you notif
 
 ## Licensing
 
-See the [LICENSE](https://github.com/aws/sagemaker-spark-serving-container/blob/master/LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+See the [LICENSE](https://github.com/aws/sagemaker-python-sdk/blob/master/LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
 
-We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.
+We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.

Dockerfile

@@ -0,0 +1,16 @@
+FROM openjdk:8
+
+LABEL com.amazonaws.sagemaker.capabilities.accept-bind-to-port=true
+
+RUN apt-get update && apt-get -y install apt-utils net-tools apt-transport-https wget curl nginx git maven
+
+COPY / /sagemaker-sparkml-model-server
+WORKDIR /sagemaker-sparkml-model-server
+
+RUN mvn clean package
+
+RUN cp ./target/sparkml-serving-2.2.jar /usr/local/lib/sparkml-serving-2.2.jar
+RUN cp ./serve.sh /usr/local/bin/serve.sh
+
+RUN chmod a+x /usr/local/bin/serve.sh
+ENTRYPOINT ["/usr/local/bin/serve.sh"]