Include bigcouch migration from two pages

1 files changed, 1 insertions, 71 deletions

diff --git a/pages/docs/platform/upgrading/upgrade-0-8.md b/pages/docs/platform/upgrading/upgrade-0-8.md
index 904b240..9d30101 100644
--- a/pages/docs/platform/upgrading/upgrade-0-8.md
+++ b/pages/docs/platform/upgrading/upgrade-0-8.md
@@ -18,77 +18,7 @@ Upgrading to Platform 0.8
 
 ### Step 2: Migrate BigCouch to CouchDB
 
-First migrate your BigCouch nodes to CouchDB.
-
-At the end of this process, you will have just *one* node with `services` property equal to `couchdb`. If you had a BigCouch cluster before, you will be removing all but one of those machines to consolidate them into one CouchDB machine.
-
-1. if you have multiple nodes with the `couchdb` service on them, pick one of them to be your CouchDB server, and remove the service from the others. If these machines were only doing BigCouch before, you can remove the nodes completely with `leap node rm <nodename>` and then you can decommission the servers
-
-1. put the webapp into maintenance mode:
-
-Simply drop a html file to `/srv/leap/webapp/public/system/maintenance.html`. For example:
-
-    workstation$ leap ssh <webapp-node>
-    server# echo "Temporarily down for maintenance. We will be back soon." > /srv/leap/webapp/public/system/maintenance.html
-
-1. turn off daemons that access the database. For example:
-
-    ```
-    workstation$ leap ssh <each soledad-node>
-    server# /etc/init.d/soledad-server stop
-
-    workstation$ leap ssh <mx-node>
-    server# /etc/init.d/postfix stop
-    server# /etc/init.d/leap-mx stop
-
-    workstation$ leap list webapp
-    workstation$ leap ssh <webapp-node>
-    server# /etc/init.d/nickserver stop
-    ```
-
-    Alternately, you can create a temporary firewall rule to block access (run on couchdb server):
-
-    ```
-    server# iptables -A INPUT -p tcp --dport 5984 --jump REJECT
-    ```
-
-1. remove orphaned databases and do a backup of all remaining, active databases. This can take some time and will place several hundred megabytes of data into /var/backups/couchdb. The size and time depends on how many users there are on your system. For example, 15k users took approximately 25 minutes and 308M of space:
-
-    ```
-    workstation$ leap ssh <couchdb-node>
-    server# cd /srv/leap/couchdb/scripts
-    server# ./cleanup-user-dbs
-    server# time ./couchdb_dumpall.sh
-    ```
-
-1. stop bigcouch:
-
-    ```
-    server# /etc/init.d/bigcouch stop
-    server# pkill epmd
-    ```
-
-1. remove bigcouch:
-
-    ```
-    server# apt-get remove bigcouch
-    ```
-1. configure your couch node to use plain couchdb instead of bigcouch, you can do this by editing nodes/<couch-node>.json, look for this section:
-
-  ```
-  "couch": {
-    "mode": "plain"
-  }
-  ```
-
-  change it, so it looks like this instead:
-
-  ```
-  "couch": {
-    "mode": "plain",
-    "pwhash_alg": "pbkdf2"
-  }
-  ```
+<%= render 'common/bigcouch_migration.md' %>
 
 ### Step 3: Upgrade from Debian Wheezy to Jessie