1 files changed, 90 insertions, 0 deletions
diff --git a/utils/setup.py b/utils/setup.py
new file mode 100644
index 000000000..bc1940636
--- /dev/null
+++ b/utils/setup.py
@@ -0,0 +1,90 @@
+"""A setuptools based setup module.
+
+"""
+
+# Always prefer setuptools over distutils
+from setuptools import setup
+# To use a consistent encoding
+from codecs import open
+from os import path
+
+here = path.abspath(path.dirname(__file__))
+
+setup(
+    name='ooinstall',
+
+    # Versions should comply with PEP440.  For a discussion on single-sourcing
+    # the version across setup.py and the project code, see
+    # https://packaging.python.org/en/latest/single_source_version.html
+    version="3.0.0",
+
+    description="Ansible wrapper for OpenShift Enterprise 3 installation.",
+
+    # The project's main homepage.
+    url="http://github.com/openshift/openshift-extras/tree/enterprise-3.0/oo-install",
+
+    # Author details
+    author="openshift@redhat.com",
+    author_email="OpenShift",
+
+    # Choose your license
+    license="Apache 2.0",
+
+    # See https://pypi.python.org/pypi?%3Aaction=list_classifiers
+    classifiers=[
+        'Development Status :: 4 - Beta',
+        'License :: OSI Approved :: Apache Software License',
+        'Programming Language :: Python :: 2.7',
+        'Topic :: Utilities',
+    ],
+
+    # What does your project relate to?
+    keywords='oo-install setuptools development',
+
+    # You can just specify the packages manually here if your project is
+    # simple. Or you can use find_packages().
+    #packages=find_packages(exclude=['contrib', 'docs', 'tests*']),
+    packages=['ooinstall'],
+    package_dir={'ooinstall': 'src/ooinstall'},
+
+
+    # List run-time dependencies here.  These will be installed by pip when
+    # your project is installed. For an analysis of "install_requires" vs pip's
+    # requirements files see:
+    # https://packaging.python.org/en/latest/requirements.html
+    install_requires=['click', 'PyYAML'],
+
+    # List additional groups of dependencies here (e.g. development
+    # dependencies). You can install these using the following syntax,
+    # for example:
+    # $ pip install -e .[dev,test]
+    #extras_require={
+    #    'dev': ['check-manifest'],
+    #    'test': ['coverage'],
+    #},
+
+    # If there are data files included in your packages that need to be
+    # installed, specify them here.  If using Python 2.6 or less, then these
+    # have to be included in MANIFEST.in as well.
+    package_data={
+        'ooinstall': ['ansible.cfg', 'ansible_plugins/*'],
+    },
+
+    # Although 'package_data' is the preferred approach, in some case you may
+    # need to place data files outside of your packages. See:
+    # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa
+    # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
+    #data_files=[('my_data', ['data/data_file'])],
+    tests_require=['nose'],
+
+    test_suite='nose.collector',
+
+    # To provide executable scripts, use entry points in preference to the
+    # "scripts" keyword. Entry points provide cross-platform support and allow
+    # pip to create the appropriate form of executable for the target platform.
+    entry_points={
+        'console_scripts': [
+            'oo-install=ooinstall.cli_installer:main',
+        ],
+    },
+)