anchor.diff:  
   *Note: For local development, you don't need to run all containers, just the ones listed below.*
   
  -For the containers to link up properly, they must be run in a certain order.
  -
  -.*Recommended run order*:
  +For the containers to link up properly, they must be run in a certain order. 
  +
  +
  +*Important:* The oso-zaio container must undergo cleanup and configuration before _oso-zagg-web_ and _oso-host-monitoring_ are run.
  +Complete everything in the *Setting up the ZAIO* section before running any of the other containers. 
  +
  +.*Run order*:
   . oso-zaio
  +. _Setup ZAIO_
   . oso-zagg-web
   . oso-host-monitoring
   
  
positive.code: 
  For the containers to build properly, they must be built in a certain order.
  
  .*Recommended build order*:
  . oso-ops-base
  . oso-zaio
  . oso-zagg-web
  
negative.code: 
  *Note: the container will stay in the foreground (on purpose). This allows you to see the container startup messages and allows you to exit the container by pressing ctrl-c*
  
  == Setting up the ZAIO
  The ZAIO is a completely default installation of zabbix. It has the default templates, items and triggers loaded. The reason it's completely default is that the ZAIO is used by multiple teams, for multiple projects. Therefore, having a default install makes sense.
  
  The ZAIO is also a completely ephemeral. Meaning that when the ZAIO container is stopped and then re-started, it is back to being a completely default installation of zabbix. This is great for development.
  
  This makes the ZAIO a great resource for local development.
  
  === Setting up the openshift-tools Ansible Zabbix Modules
  In order to setup the openshift-tools Ansible Zabbix modules, you need to either install the Zabbix Ansible Module package, or setup the python path to point to the openshift_tools python module.
  
  For development purposes, it's almost always preferable to set the python path, as then you're guaranteed to have the latest code.
  
  .Steps to configure the Ansible Zabbix Modules:
  . Change into the openshift-tools git repo
  [source]
  ----
  > cd openshift-tools/ansible/playbooks/adhoc/zabbix_setup
  ----
  . Set the python path to see our openshift_tools python package, as well as the system's site-packages
  [source]
  ----
  > export PYTHONPATH=$(pwd)/../../../..:$(ls /usr/lib/python2*/site-packages/ -d)
  ----
  
  
  === Cleaning out the ZAIO
  For our monitoring development, we really don't need the vast majority of the default templates.
  
  To clean them out, run the `oo-clean-zaio.yml` playbook.
  
  .Example of running the oo-clean-zaio.yml playbook:
  ----
  > ./oo-clean-zaio.yml
  ----
  
  === Setup the Monitoring templates, items and triggers in the ZAIO
  After cleaning out the default templates, items and triggers from the ZAIO, it is necessary to setup the ZAIO with our latest monitoring templates, items and triggers.
  
  To do this, run the `oo-config-zaio.yml` playbook.
  
  *Note: this playbook is idempotent and can be run multiple times without any new changes being made.*
  
  .Example of running the oo-config-zaio.yml playbook:
  ----
  > ./oo-config-zaio.yml
  ----
  
  == Logging into the ZAIO
  Once the containers are up and running, you can log into the Zaio http://localhost/zabbix[here].
  
  The username is `Admin`.
  The password is `zabbix`.
  
  == Container Features
  
  