ansible 2.2.2.0 has an [issue]() that causes problems for kargo:

```
(env) kargo ᐅ env/bin/ansible-playbook upgrade-cluster.yml 
ERROR! Unexpected Exception: 'Host' object has no attribute 'remove_group'
```

Pinning ansible to 2.2.1.0 resolved this for me.

Refactor etcd role

Fix markdown of heading in README

- Run docker run from script rather than directly from systemd target
- Refactoring styling/templates

Signed-off-by: Sergii Golovatiuk <sgolovatiuk@mirantis.com>

Update roadmap.md

replace non-breakable space with regular space

Add missing defaults

Fixes for AWS Terraform Deployment

Non-brekable space is 0xc2 0xa0 byte sequence in UTF-8.

To find one:

    $ git grep -I -P '\xc2\xa0'

To replace with regular space:

    $ git grep -l -I -P '\xc2\xa0' | xargs sed -i 's/\xc2\xa0/ /g'

This commit doesn't include changes that will overlap with commit f1c59a91.

Use checksum of dnsmasq config to trigger updates of dnsmasq

Change wait for dnsmasq to skip if there are no kube-nodes in play

Allows config changes made by Ansible to restart dnsmasq deployment

Add KVM hypervisor playbook to contrib

Disable download_run_once and download_localhost for most CI scenarios

Optional Ansible playbook for preparing a host for running Kargo.
This includes creation of a user account, some basic packages,
and sysctl values required to allow CNI networking on a libvirt network.

Also changed unnecessary delay to a max timeout (now defaulting to 1s sleep
between tries)

Also rename play_hosts to ansible_play_hosts

This adds time to deployment, so we should only test it sparingly during
daily master.

Backup etcd

Bump CoreOS stable to latest version

Make reset check on idempotency check optional

Add helm deployment

etcd is crucial part of kubernetes cluster. Ansible restarts etcd on
reconfiguration. Backup helps operator to restore cluster manually in
case of any issues.

Signed-off-by: Sergii Golovatiuk <sgolovatiuk@mirantis.com>

1298.6.0 fixes some sporadic network issues. It also includes docker
1.12.6 which includes several stability fixes for kubernetes.

Signed-off-by: Sergii Golovatiuk <sgolovatiuk@mirantis.com>

By default we do not test reset.yml now.

AWS Terraform for Kargo

limit jinja2 version to <2.9

Ansible 2.2.1 requires jinja2<2.9, see <https://github.com/ansible/ansible/blob/v2.2.1.0-1/setup.py#L25>,
but without explicit limiting upper jinja2 version here pip ignores
Ansible requirements and installs latest available jinja2
(pip is not very smart here), which is incompatible with with
Ansible 2.2.1.
With incompatible jinja2 version "ansible-vault create" (and probably other parts)
fails with:
  ERROR! Unexpected Exception: The 'jinja2<2.9' distribution was not found 
  and is required by ansible
This upper limit should be removed in 2.2.2 release, see:
<https://github.com/ansible/ansible/commit/978311bf3f91dae5806ab72b665b0937adce38ad>

Fix weave on RHEL deployment

Retry yum/apt/rpm download commands

remove obsolete script

Currently Kubernetes version can be selected using "kube_version" variable.

fix jinja package name

Jinja 2.* releases are published under `Jinja2` name.

Condense resolvconf sources before starting loop