Convert to ansible-navigator and collection playbooks (#115)

* Remove legacy playbooks
* Update CML definition to use ansible-navigator
* Add AWS base definition for Env and DL only
* Remove obsolete sandbox definitions
* Convert CDE example to ansible-navigator and collection playbooks
* Update base CDP Env and DL example for allowed CIDRs
* Convert CDF example to ansible-navigator and collection playbooks
* Update to use allowed_cidr
* Add Frequently Asked Questions doc
* Add JMESPath Playground example for subnet filters
* Update documentation to use the main FAQ
* Formatting of migration entry
* Add TF example for CDP on AWS
* Create SSH keypair

Signed-off-by: Webster Mudge <wmudge@cloudera.com>
Signed-off-by: Jim Enright <jenright@cloudera.com>
Co-authored-by: Jim Enright <jim.enright.86@gmail.com>

Author: wmudge

FAQ.md

@@ -0,0 +1,116 @@
+# Frequently Asked Questions
+
+## Where did everything go?
+
+The project undertook some serious remodeling, but rest assured, your definitions will still work as they did in the previous version of `cloudera-deploy`.  
+
+Okay, but where did everything go? Well...
+
+1. The `quickstart.sh` migrated to `ansible-navigator`. Both of these applications use a container based on `ansible-runner`, i.e. [`cldr-runner`](https://github.com/cloudera-labs/cldr-runner), to execute the playbooks, yet `ansible-navigator` is configuration-driven and better aligned with how AWX runs Ansible in containers. Also, `ansible-navigator` brings a nifty UI and the ease of use to handle different execution modes.
+  
+    We also migrated `cldr-runner` to use `ansible-builder`, but you can read more about that effort at the [`cldr-runner`](https://github.com/cloudera-labs/cldr-runner) project.
+
+1. The original `cloudera-deploy` playbooks moved into `cloudera.exe`. Starting with Ansible `2.11`, [collections can contain playbooks](https://docs.ansible.com/ansible/latest/collections_guide/collections_using_playbooks.html#using-a-playbook-from-a-collection). We call the playbooks using `import_playbook` like roles.
+
+    PLEASE NOTE, if you are developing your own project playbooks, you must first set up your `cloudera-deploy` variables _before_ calling the playbooks by running the `cloudera.exe.init_deployment` role on `localhost`.
+
+1. The _run-levels_ still remain; you can still use `-t infra` for example. However, the playbooks themselves are more granular and overall set up and tear down processes are now separate playbooks.
+  
+    This change promotes composibility and reusability, and we are going to continue to break apart the functions and operations within `cloudera-deploy` and -- most importantly -- the collections that drive this application. We fully expect that you will want to adapt and create your own "deploy" application, one that caters to _your_ needs and operating parameters. Switching to a more granular, more modular approach is key to this objective.
+
+## How to I add _extra variables_ and tags to `ansible-navigator`?
+
+If you want to run a playbook with a given tag, e.g. `-t infra`, then simply add it as a parameter to the `ansible-navigator` commandline. For example, `ansible-navigator run playbook.yml -t infra`. 
+
+Like tags, so you can pass _extra variables_ to `ansible-navigator` and the underlying Ansible command. For example, `ansible-navigator run playbook.yml -e @some_config.yml -e some_var=yes`.
+
+## How do I tell `ansible-navigator` where to find collections and roles?
+
+By default, `cloudera-deploy` expects to use the collections, roles, and libraries within the _execution environment_ container, that is `cldr-runner`. Make sure you do _not_ have `ANSIBLE_COLLECTIONS_PATH` or `ANSIBLE_ROLES_PATH` set or `ansible-navigator` will pick up these environment variables and pass them to the running container. The underlying `ansible` application, like `ansible-playbook` will then pick up these environment variables and attempt to use them if set! This behavior is great if you want to use host-based collections, e.g. local development, but you need to ensure that you update the `ansible-navigator.yml` configuration file to mount the host collection and/or role directories into the execution environment container.
+
+## `ansible-navigator` hangs when I run my playbook. What is going on?
+
+`ansible-navigator` does not handle user prompts when running in the `curses` UI, so actions in your playbook like:
+
+* Vault passwords
+* SSH passphrases
+* Debugger statements
+
+will not work out-of-the-box. You can enable `ansible-navigator` to run with prompts, but doing so will also disable the UI and instead run its operations using `stdout`.  Try adding:
+
+```bash
+ansible-navigator run --enable-prompts ...
+```
+
+to your execution.
+
+## How can I view a previous `ansible-navigator` run to debug an issue?
+
+Each example is configured to save execution runs in the project's `runs` directory. You can reload a run by using the `replay` command:
+
+```bash
+ansible-navigator replay runs/<playbook name>-<timestamp>.json
+```
+
+Then you can use the UI to review the plays, tasks, and inventory for the previous run!
+
+## How can I enable the playbook debugger?
+
+The [playbook debugger](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_debugger.html) is enabled in `ansible-navigator` by setting the debugger and then enabling prompts. For example,
+
+```bash
+ANSIBLE_ENABLE_TASK_DEBUGGER=True ansible-navigator run --enable-prompts main.yml
+```
+
+## How can I select just a single subnet using `subnet_filter`, say for a CDE definition?
+
+The various `filters`, like `subnet_filter`, `loadbalancer_subnets_filter`, etc., use [JMESPath](https://jmespath.org/) expressions against a list of subnet objects. Using expression like:
+
+```jmespath
+[?contains(subnetName,`pvt`)] | [:1]
+```
+
+will limit the list of subnet objects to those with the term `pvt` and then select the first element of that reduced list.
+
+You can [test sample filters](https://play.jmespath.org/?u=45e4d839-15f9-4569-9490-20a2cbc0cc88) using this example on the JMESPath Playground (link goes to a preloaded playground):
+
+```json
+[
+  {
+    "availabilityZone": "us-east-2c",
+    "cidr": "10.10.64.0/19",
+    "subnetId": "subnet-0123",
+    "subnetName": "sbnt-pub-2"
+  },
+  {
+    "availabilityZone": "us-east-2a",
+    "cidr": "10.10.0.0/19",
+    "subnetId": "subnet-1234",
+    "subnetName": "sbnt-pub-0"
+  },
+  {
+    "availabilityZone": "us-east-2c",
+    "cidr": "10.10.160.0/19",
+    "subnetId": "subnet-2345",
+    "subnetName": "sbnt-pvt-2"
+  },
+  {
+    "availabilityZone": "us-east-2b",
+    "cidr": "10.10.128.0/19",
+    "subnetId": "subnet-3456",
+    "subnetName": "sbnt-pvt-1"
+  },
+  {
+    "availabilityZone": "us-east-2b",
+    "cidr": "10.10.32.0/19",
+    "subnetId": "subnet-4567",
+    "subnetName": "sbnt-pub-1"
+  },
+  {
+    "availabilityZone": "us-east-2a",
+    "cidr": "10.10.96.0/19",
+    "subnetId": "subnet-5678",
+    "subnetName": "sbnt-pvt-0"
+  }
+]
+```

README.md

@@ -0,0 +1,11 @@
+# Cloudera Deploy
+
+## Setting up `ansible-navigator`
+
+`cloudera-deploy` uses `ansible-navigator` to manage and execute the deployment definitions. Setting up `ansible-navigator` is straightforward; create and activate a new `virtualenv` and install the latest `ansible-core` and `ansible-navigator`.
+
+You can name your virtual environment anything you want; by convention, we call it `cdp-navigator`.
+
+```bash
+python -m venv ~/cdp-navigator; source ~/cdp-navigator/bin/activate; pip install ansible-core ansible-navigator
+```