<commit_before># mini-mesos
Testing infrastructure for Mesos frameworks. 

Build
-----

Let's say hello

    echo "Hello world"

## Overview

The basic idea is to provide simple to use test utilities to setup a Mesos cluster that can be tested against.

The Mesos cluster setup is a docker container running zookeeper with one master and a configurable number of slaves. 
The master and slaves are launched directly inside the container.

The test utilities provide mechanisms to make arbitrary docker images available inside that Mesos cluster container.
This way executors themselves could be launched as docker containers (inside that Mesos cluster container, Docker-in-docker). 

A possible testing scenario could be:
 
 1. In the test setup build an executor image and launch the Mesos cluster container with that executor image being available inside.
 2. Call the scheduler directly from your test and point to zookeeper to detect the master or passing the master URL directly.
 3. The scheduler launches a task (which runs the executor as a docker container) on a suitable slave.
 4. Poll the state of the Mesos cluster to verify that you framework is running
 5. The test utilities take care of stopping and removing the used Mesos cluster container...
<commit_msg>Revert literate plugin changes<commit_after># mini-mesos
Testing infrastructure for Mesos frameworks. 

## Overview

The basic idea is to provide simple to use test utilities to setup a Mesos cluster that can be tested against.

The Mesos cluster setup is a docker container running zookeeper with one master and a configurable number of slaves. 
The master and slaves are launched directly inside the container.

The test utilities provide mechanisms to make arbitrary docker images available inside that Mesos cluster container.
This way executors themselves could be launched as docker containers (inside that Mesos cluster container, Docker-in-docker). 

A possible testing scenario could be:
 
 1. In the test setup build an executor image and launch the Mesos cluster container with that executor image being available inside.
 2. Call the scheduler directly from your test and point to zookeeper to detect the master or passing the master URL directly.
 3. The scheduler launches a task (which runs the executor as a docker container) on a suitable slave.
 4. Poll the state of the Mesos cluster to verify that you framework is running
 5. The test utilities take care of stopping and removing the used Mesos cluster container...

{'fraction_non_alphanumeric': 0.02867383512544803, 'fraction_numerical': 0.00398247710075667, 'mean_word_length': 4.322033898305085, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2575335', 'n_tokens_mistral': 598, 'n_tokens_neox': 550, 'n_words': 386}