<commit_before>Preparation: paasta_tools and yelpsoa-configs
=========================================================

paasta_tools reads configuration about services from several YAML
files in `soa-configs <soa_configs.html>`_:

Each object inside of these YAML files is called an "instance" of a PaaSTA
service. It describes a unique way to run the service, with a unique command,
cpu and ram requirements, etc.

Duplication can be reduced by using YAML `anchors and merges<https://gist.github.com/bowsersenior/979804>`_.
PaaSTA will **not** attempt to run any definition prefixed with ``_``,
so you are free to use them for YAML templates.

Example::

    _template: &template
        env:
            foo: bar

    main:
        <<: *template
        cpus: 1.0
        mem: 1000
        command: busybox httpd

    worker:
        <<: *template
        cpus: 0.1
        mem: 100
        command: python -m worker


``Common Settings``
-------------------

All configuration files that define something to launch on a PaaSTA Cluster can
specify the following options:

  * ``cpus``: Number of CPUs an instance needs. Defaults to .25. CPUs in Mesos
    are "shares" and represent a minimal amount of a CPU to share with a task
    relative to the other tasks on a host.  A task can burst to use any<commit_msg>Fix small docs typo<commit_after>Preparation: paasta_tools and yelpsoa-configs
=========================================================

paasta_tools reads configuration about services from several YAML
files in `soa-configs <soa_configs.html>`_:

Each object inside of these YAML files is called an "instance" of a PaaSTA
service. It describes a unique way to run the service, with a unique command,
cpu and ram requirements, etc.

Duplication can be reduced by using YAML `anchors and merges <https://gist.github.com/bowsersenior/979804>`_.
PaaSTA will **not** attempt to run any definition prefixed with ``_``,
so you are free to use them for YAML templates.

Example::

    _template: &template
        env:
            foo: bar

    main:
        <<: *template
        cpus: 1.0
        mem: 1000
        command: busybox httpd

    worker:
        <<: *template
        cpus: 0.1
        mem: 100
        command: python -m worker


``Common Settings``
-------------------

All configuration files that define something to launch on a PaaSTA Cluster can
specify the following options:

  * ``cpus``: Number of CPUs an instance needs. Defaults to .25. CPUs in Mesos
    are "shares" and represent a minimal amount of a CPU to share with a task
    relative to the other tasks on a host.  A task can burst to use any
{'fraction_non_alphanumeric': 0.1206831119544592, 'fraction_numerical': 0.014421252371916509, 'mean_word_length': 2.987897125567322, 'pattern_counts': {'":': 0, '<': 15, '<?xml version=': 0, '>': 7, 'https://': 2, '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': '6589514', 'n_tokens_mistral': 788, 'n_tokens_neox': 716, 'n_words': 335}