docs: Note how we use Terraform/Ansible as an example

docs/source/prod-node-setup-mgmt/overview.md

@@ -7,7 +7,11 @@ Deploying and managing a production BigchainDB node is much more involved than w
 * Production nodes need monitoring
 * Production nodes need maintenance, e.g. software upgrades, scaling
 
-Thankfully, there are tools to help! We use:
+Thankfully, there are tools that can help (e.g. provisioning tools and configuration management tools). You can use whatever tools you prefer.
+
+As an example, we provide documentation and code showing how to use Terraform and Ansible (together).
 
 * [Terraform](https://www.terraform.io/) to provision infrastructure such as AWS instances, storage and security groups
 * [Ansible](https://www.ansible.com/) to manage the software installed on that infrastructure (configuration management)
+
+You can use those as-described or as a reference for setting up your preferred tools. If you notice something that could be done better, let us know (e.g. by creating an issue on GitHub).

ntools/one-m/ansible/one-m-node.yml

@@ -0,0 +1,9 @@
+---
+# This playbook deploys a BigchainDB node in one machine (one-m).
+
+- name: deploy all software and configure it
+  hosts: all
+  remote_user: root
+
+  roles:
+    - common

ntools/one-m/ansible/roles/common/handlers/main.yml

@@ -0,0 +1,10 @@
+---
+# This file should be in roles - common - handlers
+# Handler to handle common notifications. Handlers are called by other plays.
+# See http://docs.ansible.com/playbooks_intro.html for more information about handlers.
+
+- name: restart ntp
+  service: name=ntpd state=restarted
+
+- name: restart iptables
+  service: name=iptables state=restarted