docs: fixed broken links to prod-node-depl-tplt section

docs/source/prod-node-depl-tplt/index.rst

@@ -0,0 +1,12 @@
+Production Node Deployment Template
+===================================
+
+.. toctree::
+   :maxdepth: 1
+
+   overview
+   install-terraform
+   install-ansible
+   prov-one-m-aws
+   prov-one-m-azure
+   start-one-m-node

docs/source/prod-node-depl-tplt/install-ansible.md

@@ -0,0 +1,11 @@
+# Install Ansible
+
+The Ansible documentation has [installation instructions](https://docs.ansible.com/ansible/intro_installation.html). Note the control machine requirements: at the time of writing, Ansible required Python 2.6 or 2.7. (Support for Python 3 [is a goal of Ansible 2.2](https://github.com/ansible/ansible/issues/15976#issuecomment-221264089).)
+
+For example, you could create a special Python 2.x virtualenv named `ansenv` and then install Ansible in it:
+```text
+cd repos/bigchaindb/ntools
+virtualenv -p /usr/local/lib/python2.7.11/bin/python ansenv
+source ansenv/bin/activate
+pip install ansible
+```

docs/source/prod-node-depl-tplt/install-terraform.md

@@ -0,0 +1,30 @@
+# Install Terraform
+
+The [Terraform documentation has installation instructions](https://www.terraform.io/intro/getting-started/install.html) for all common operating systems.
+
+If you don't want to run Terraform on your local machine, you can install it on a cloud machine under your control (e.g. on AWS).
+
+Note: Hashicorp has an enterprise version of Terraform called "Terraform Enterprise." You can license it by itself or get it as part of Atlas. If you decide to license Terraform Enterprise or Atlas, be sure to install it on your own hosting (i.e. "on premise"), not on the hosting provided by Hashicorp. The reason is that BigchainDB clusters are supposed to be decentralized. If everyone used Hashicorp's hosted Atlas, then that would be a point of centralization.
+
+
+## Ubuntu Installation Tips
+
+If you want to install Terraform on Ubuntu, first [download the .zip file](https://www.terraform.io/downloads.html). Then install it in `/opt`:
+```text
+sudo mkdir -p /opt/terraform
+sudo unzip path/to/zip-file.zip -d /opt/terraform
+```
+
+Why install it in `/opt`? See [the answers at Ask Ubuntu](https://askubuntu.com/questions/1148/what-is-the-best-place-to-install-user-apps).
+
+Next, add `/opt/terraform` to your path. If you use bash for your shell, then you could add this line to `~/.bashrc`:
+```text
+export PATH="/opt/terraform:$PATH"
+```
+
+After doing that, relaunch your shell or force it to read `~/.bashrc` again, e.g. by doing `source ~/.bashrc`. You can verify that terraform is installed and in your path by doing:
+```text
+terraform --version
+```
+
+It should say the current version of Terraform.

docs/source/prod-node-depl-tplt/overview.md

@@ -0,0 +1,17 @@
+# Overview
+
+Deploying and managing a production BigchainDB node is much more involved than working with a dev/test node:
+
+* There are more components in a production node; see [the page about node components](../nodes/node-components.html)
+* Production nodes need more security
+* Production nodes need monitoring
+* Production nodes need maintenance, e.g. software upgrades, scaling
+
+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). We use:
+
+* [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).

docs/source/prod-node-depl-tplt/prov-one-m-aws.md

@@ -0,0 +1,50 @@
+# Provision a One-Machine Node on AWS
+
+This page describes how to provision the resources needed for a one-machine BigchainDB node on AWS using Terraform.
+
+## Get Set
+
+First, do the [basic AWS setup steps outlined in the Appendices](../appendices/aws-setup.html).
+
+Then go to the `.../bigchaindb/ntools/one-m/aws/` directory and open the file `variables.tf`. Most of the variables have sensible default values, but you can change them if you like. In particular, you may want to change `aws_region`. (Terraform looks in `~/.aws/credentials` to get your AWS credentials, so you don't have to enter those anywhere.)
+
+The `ssh_key_name` has no default value, so Terraform will prompt you every time it needs it.
+
+To see what Terraform will do, run:
+```text
+terraform plan
+```
+
+It should ask you the value of `ssh_key_name`. 
+
+It figured out the plan by reading all the `.tf` Terraform files in the directory.
+
+If you don't want to be asked for the `ssh_key_name`, you can change the default value of `ssh_key_name` (in the file `variables.tf`) or [you can set an environmen variable](https://www.terraform.io/docs/configuration/variables.html) named `TF_VAR_ssh_key_name`.
+
+
+## Provision
+
+To provision all the resources specified in the plan, do the following. **Note: This will provision actual resources on AWS, and those cost money. Be sure to shut down the resources you don't want to keep running later, otherwise the cost will keep growing.**
+```text
+terraform apply
+```
+
+Terraform will report its progress as it provisions all the resources. Once it's done, you can go to the Amazon EC2 web console and see the instance, its security group, its elastic IP, and its attached storage volumes (one for the root directory and one for RethinkDB storage).
+
+At this point, there is no software installed on the instance except for Ubuntu 14.04 and whatever else came with the Amazon Machine Image (AMI) specified in the configuration. The next step is to use Ansible to install and configure all the necessary software.
+
+
+## (Optional) "Destroy"
+
+If you want to shut down all the resources just provisioned, you must first disable termination protection on the instance:
+
+1. Go to the EC2 console and select the instance you just launched. It should be named `BigchainDB_node`.
+2. Click **Actions** > **Instance Settings** > **Change Termination Protection** > **Yes, Disable**
+3. Back in your terminal, do `terraform destroy`
+
+Terraform should "destroy" (i.e. terminate or delete) all the AWS resources you provisioned above.
+
+## See Also
+
+* The [Terraform Documentation](https://www.terraform.io/docs/)
+* The [Terraform Documentation for the AWS "Provider"](https://www.terraform.io/docs/providers/aws/index.html)

docs/source/prod-node-depl-tplt/prov-one-m-azure.md

@@ -0,0 +1,3 @@
+# Provision a One-Machine Node on Azure
+
+This is just a placeholder so you can see the future structure of these docs.

docs/source/prod-node-depl-tplt/start-one-m-node.md

@@ -0,0 +1,45 @@
+# Start a One-Machine Node
+
+In this step, we will install, configure and run all the software necessary to run BigchainDB, all on one machine.
+
+
+## Create an Ansible Inventory File
+
+An Ansible "inventory" file is a file which lists all the hosts (machines) you want to manage using Ansible. (Ansible will communicate with them via SSH.) Right now, we only want to manage one host.
+
+First, determine the public IP address of the host (i.e. something like `192.0.2.128`).
+
+Then create a one-line text file named `hosts` by doing this:
+```text
+# cd to the directory .../bigchaindb/ntools/one-m/ansible
+echo "192.0.2.128" > hosts
+```
+
+but replace `192.0.2.128` with the IP address of the host.
+
+
+## Run the Ansible Playbook
+
+The next step is to run the Ansible playbook `one-m-node.yml`:
+```text
+# cd to the directory .../bigchaindb/ntools/one-m/ansible
+ansible-playbook -i hosts --private-key ~/.ssh/<key-name> one-m-node.yml
+```
+
+where `<key-name>` should be replaced by the name of the SSH private key you created earlier (for SSHing to the host machine at your cloud hosting provider).
+
+What did you just do? Running that playbook ensures all the software necessary for a one-machine BigchainDB node is installed, configured, and running properly. You can run that playbook on a regular schedule to ensure that the system stays properly configured. If something is okay, it does nothing; it only takes action when something is not as-desired.
+
+Note: At the time of writing, the playbook only installs, configures and runs an NTP daemon, but more is coming soon.
+
+
+## Optional: Create an Ansible Config File
+
+The above command (`ansible-playbook -i ...`) is fairly long. You can omit the optional arguments if you put their values in an [Ansible configuration file](https://docs.ansible.com/ansible/intro_configuration.html) (config file) instead. There are many places where you can put a config file, but to make one specifically for the "one-m" case, you should put it in `.../bigchaindb/ntools/one-m/ansible/`. In that directory, create a file named `ansible.cfg` with the following contents:
+```text
+[defaults]
+private_key_file = $HOME/.ssh/<key-name>
+inventory = hosts
+```
+
+where, as before, `<key-name>` must be replaced.