<commit_before>Getting Started
===============

This document will show you how to begin using the F5 Ansible modules.
You will create a pool, add two nodes to that pool, and finally assign a
virtual server to serve requests to the nodes in the pool.

First, obtain `Python 2.7`_ and `Ansible`_ if you do not already have them.

You will need to verify that your Ansible version is higher than 2.0
you can do this as such:

    ansible --version

If this is not the case please update your pip version before continuing:

    pip install --upgrade ansible

With this ready, you can create your first playbook. We'll write the remainder
of our Ansible playbooks in a file called ``site.yaml``

Playbook
--------
<commit_msg>added instructions for installing ansible 2.2.0<commit_after>Getting Started
===============

This document will show you how to begin using the F5 Ansible modules.
You will create a pool, add two nodes to that pool, and finally assign a
virtual server to serve requests to the nodes in the pool.

First, obtain `Python 2.7`_ and `Ansible`_ if you do not already have them.

The version of Ansible that is required is at least 2.2.0. At the time of
this writing, that version is still in development. Below, I've included
steps to install Ansible in a virtualenv for you to use until such time
as Ansible 2.2.0 is released

Installing Ansible
------------------

At this time, an unreleased version of Ansible is required to make full
use of these modules; 2.2.0.

Let's install Ansible in a virtualenv to make it possible to use the
modules.

First, make sure `virtualenv` is installed.

    pip install virtualenv

This will make available to you a `virtualenv` command. You can use that
it make a virtual environment for your Ansible installation.

    virtualenv ansible2

In your current working directory, you will find a new directory called
`ansible2`. In this directory resides a copy of Python that is configured
to install any modules inside of that local directory. Via this method,
we can install Python modules without stomping on the system wide ones.

To use this new location, you must `activate` it.

    . ansible2/bin/activate

You should see your prompt change so that the name of the virtualenv is
prefixing the normal prompt. For example.

    (ansible2)SEA-ML-RUPP1:f5 trupp$

Now that our `virtualenv` is active, all future Python commands (such as
`pip`) will install modules into the virtualenv. So let's install the
development copy of ansible.

    pip install git+git://github.com/ansible/ansible.git@devel

You should be able to verify that you are running the new version of
Ansible by using the `--version` argument to the `ansible` command, like
so.

    ansible --version

You should be presented with output that resembles the following

    (test1)SEA-ML-RUPP1:virtualenv trupp$ ansible --version
    ansible 2.2.0
      config file =
      configured module search path = Default w/o overrides

With this ready, you can create your first playbook. We'll write the remainder
of our Ansible playbooks in a file called ``site.yaml``

Playbook
--------

{'fraction_non_alphanumeric': 0.06591639871382636, 'fraction_numerical': 0.009967845659163987, 'mean_word_length': 3.706505295007564, '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': '7195986', 'n_tokens_mistral': 871, 'n_tokens_neox': 815, 'n_words': 472}