DCOS Command Line Interface

The DCOS Command Line Interface (CLI) is a command line utility supporting several commands to provide an user friendly yet powerful way to manage DCOS installations.

Dependencies

1. git must be installed and on the system path in order to fetch packages from git sources.

Setup

1. Make sure you meet requirements for installing packages

2. Clone git repo for the dcos cli:

   git clone git@github.com:mesosphere/dcos-cli.git

3. Change directory to the repo directory:

   cd dcos-cli

4. Make sure that you have virtualenv installed. If not type:

   sudo pip install virtualenv

5. Create a virtualenv for the dcos cli project:

   make env

Configure Environment and Run

1. source the setup file to add the dcos command line interface to your PATH and create an empty configuration file:

   source env/bin/env-setup

2. Configure Marathon, changing the values below as appropriate for your local installation:

   dcos config marathon.host localhost
   dcos config marathon.port 8080

3. Get started by calling the DCOS CLI help:

   dcos help

Running Tests:

Setup

Tox, our test runner, tests against both Python 2.7 and Python 3.4 environments.

If you're using OS X, be sure to use the officially distributed Python 3.4 installer since the Homebrew version is missing a necessary library.

Running

Tox will run unit and integration tests in both Python environments using a temporarily created virtualenv.

You should ensure DCOS_CONFIG is set and that the config file points to the Marathon instance you want to use for integration tests. If you're happy to use the default test configuration which assumes there is a Marathon instance running on localhost, set DCOS_CONFIG as follows:

export DCOS_CONFIG=$(pwd)/tests/data/Dcos.toml

There are two ways to run tests, you can either use the virtualenv created by make env above:

make test

Or, assuming you have tox installed (via sudo pip install tox):

tox

Other Useful Commands

1. List all of the supported test environments:

   tox --listenvs

2. Run a specific set of tests:

   tox -e <testenv>