update version to 4.9.0
diff --git a/source/building_from_source.rst b/source/building_from_source.rst
index 26cbe85..a4303f7 100644
--- a/source/building_from_source.rst
+++ b/source/building_from_source.rst
@@ -92,7 +92,7 @@
 
 .. sourcecode:: bash
 
-   $ gpg --verify apache-cloudstack-4.8.0-src.tar.bz2.asc
+   $ gpg --verify apache-cloudstack-4.9.0-src.tar.bz2.asc
 
 If the signature is valid you will see a line of output that contains
 'Good signature'.
@@ -107,7 +107,7 @@
 
 .. sourcecode:: bash
 
-   $ gpg --print-md MD5 apache-cloudstack-4.8.0-src.tar.bz2 | diff - apache-cloudstack-4.8.0-src.tar.bz2.md5
+   $ gpg --print-md MD5 apache-cloudstack-4.9.0-src.tar.bz2 | diff - apache-cloudstack-4.9.0-src.tar.bz2.md5
 
 If this successfully completes you should see no output. If there is any
 output from them, then there is a difference between the hash you
@@ -123,7 +123,7 @@
 
 .. sourcecode:: bash
 
-   $ gpg --print-md SHA512 apache-cloudstack-4.8.0-src.tar.bz2 | diff - apache-cloudstack-4.8.0-src.tar.bz2.sha
+   $ gpg --print-md SHA512 apache-cloudstack-4.9.0-src.tar.bz2 | diff - apache-cloudstack-4.9.0-src.tar.bz2.sha
 
 If this command successfully completes you should see no output. If
 there is any output from them, then there is a difference between the
@@ -150,7 +150,7 @@
 
 #. MySQLdb (provides Python database API)
 
-#. Tomcat 6 (not 6.0.35)
+#. Tomcat 6 (not 6.0.35) or Tomcat 7
 
 #. genisoimage
 
@@ -165,13 +165,62 @@
 
 .. sourcecode:: bash
 
-   $ tar -jxvf apache-cloudstack-4.8.0-src.tar.bz2
+   $ tar -jxvf apache-cloudstack-4.9.0-src.tar.bz2
 
 You can now move into the directory:
 
 .. sourcecode:: bash
 
-   $ cd ./apache-cloudstack-4.8.0-src
+   $ cd ./apache-cloudstack-4.9.0-src
+
+Install new MySQL connector
+---------------------------
+
+Install Python MySQL connector using the official MySQL packages repository.
+
+
+MySQL connector APT repository
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Install the following package provided by MySQL to enable official repositories:
+
+.. sourcecode:: bash
+
+   wget http://dev.mysql.com/get/mysql-apt-config_0.7.3-1_all.deb
+   sudo dpkg -i mysql-apt-config_0.7.3-1_all.deb
+
+Make sure to activate the repository for MySQL connectors.
+
+.. sourcecode:: bash
+
+   sudo apt-get update
+   sudo apt-get install mysql-connector-python   
+
+
+MySQL connector RPM repository
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Add a new yum repo ``/etc/yum.repos.d/mysql.repo``:
+
+.. sourcecode:: bash
+
+   [mysql-community]
+   name=MySQL Community connectors
+   baseurl=http://repo.mysql.com/yum/mysql-connectors-community/el/$releasever/$basearch/
+   enabled=1
+   gpgcheck=1
+
+Import GPG public key from MySQL:
+
+.. sourcecode:: bash
+
+   rpm --import http://repo.mysql.com/RPM-GPG-KEY-mysql
+
+Install mysql-connector
+
+.. sourcecode:: bash
+
+   yum install mysql-connector-python
 
 
 Building DEB packages
@@ -185,7 +234,7 @@
    $ sudo apt-get update
    $ sudo apt-get install python-software-properties
    $ sudo apt-get update
-   $ sudo apt-get install ant debhelper openjdk-7-jdk tomcat6 libws-commons-util-java genisoimage python-mysqldb libcommons-codec-java libcommons-httpclient-java liblog4j1.2-java maven
+   $ sudo apt-get install ant debhelper openjdk-7-jdk tomcat6 libws-commons-util-java genisoimage libcommons-codec-java libcommons-httpclient-java liblog4j1.2-java maven
 
 While we have defined, and you have presumably already installed the
 bootstrap prerequisites, there are a number of build time prerequisites
@@ -210,13 +259,11 @@
 
 .. sourcecode:: bash
 
-   cloudstack-common-4.8.0.amd64.deb
-   cloudstack-management-4.8.0.amd64.deb
-   cloudstack-agent-4.8.0.amd64.deb
-   cloudstack-usage-4.8.0.amd64.deb
-   cloudstack-awsapi-4.8.0.amd64.deb
-   cloudstack-cli-4.8.0.amd64.deb
-   cloudstack-docs-4.8.0.amd64.deb
+   cloudstack-common-4.9.0.amd64.deb
+   cloudstack-management-4.9.0.amd64.deb
+   cloudstack-agent-4.9.0.amd64.deb
+   cloudstack-usage-4.9.0.amd64.deb
+   cloudstack-cli-4.9.0.amd64.deb
 
 
 Setting up an APT repo
@@ -366,13 +413,11 @@
 
 .. sourcecode:: bash
 
-   cloudstack-agent-4.8.0.el6.x86_64.rpm
-   cloudstack-awsapi-4.8.0.el6.x86_64.rpm
-   cloudstack-cli-4.8.0.el6.x86_64.rpm
-   cloudstack-common-4.8.0.el6.x86_64.rpm
-   cloudstack-docs-4.8.0.el6.x86_64.rpm
-   cloudstack-management-4.8.0.el6.x86_64.rpm
-   cloudstack-usage-4.8.0.el6.x86_64.rpm
+   cloudstack-agent-4.9.0.el6.x86_64.rpm
+   cloudstack-cli-4.9.0.el6.x86_64.rpm
+   cloudstack-common-4.9.0.el6.x86_64.rpm
+   cloudstack-management-4.9.0.el6.x86_64.rpm
+   cloudstack-usage-4.9.0.el6.x86_64.rpm
 
 
 Creating a yum repo
diff --git a/source/conf.py b/source/conf.py
index 40920c0..a6f184c 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -61,9 +61,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = '4.8'
+version = '4.9'
 # The full version, including alpha/beta/rc tags.
-release = '4.8.0'
+release = '4.9.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
diff --git a/source/management-server/_nfs.rst b/source/management-server/_nfs.rst
index 312a946..6a42925 100644
--- a/source/management-server/_nfs.rst
+++ b/source/management-server/_nfs.rst
@@ -101,7 +101,7 @@
 
    .. sourcecode:: bash
 
-      mount -t nfs nfsservername:/nfs/share/secondary /mnt/secondary
+      mount -t nfs nfsservername:/export/secondary /mnt/secondary
 
 
 .. _using-the-management-server-as-the-nfs-server:
diff --git a/source/management-server/_pkg_repo.rst b/source/management-server/_pkg_repo.rst
index f2606bc..d6d8557 100644
--- a/source/management-server/_pkg_repo.rst
+++ b/source/management-server/_pkg_repo.rst
@@ -23,8 +23,8 @@
 
 If you didn't follow the steps to build your own packages from source in
 the sections for `“Building RPMs from Source” 
-<building_from_source.html#building-rpms-from-source>`_ or 
-`“Building DEB packages” <building_from_source.html#building-deb-packages>`_ 
+<../building_from_source.html#building-rpms-from-source>`_ or 
+`“Building DEB packages” <../building_from_source.html#building-deb-packages>`_ 
 you may find pre-built DEB and RPM packages for your convenience linked from 
 the `downloads <http://cloudstack.apache.org/downloads.html>`_ page.
 
@@ -53,7 +53,7 @@
 
    [cloudstack]
    name=cloudstack
-   baseurl=http://cloudstack.apt-get.eu/centos/6/4.8/
+   baseurl=http://cloudstack.apt-get.eu/centos/$releasever/4.9/
    enabled=1
    gpgcheck=0
 
@@ -73,7 +73,7 @@
 
 .. sourcecode:: bash
 
-   deb http://cloudstack.apt-get.eu/ubuntu precise 4.8
+   deb http://cloudstack.apt-get.eu/ubuntu precise 4.9
 
 We now have to add the public key to the trusted keys.
 
diff --git a/source/management-server/_prerequisite.rst b/source/management-server/_prerequisite.rst
index 494bfe0..5bcbf72 100644
--- a/source/management-server/_prerequisite.rst
+++ b/source/management-server/_prerequisite.rst
@@ -72,7 +72,7 @@
 
    .. sourcecode:: bash
 
-      ping www.cloudstack.org
+      ping cloudstack.apache.org
 
 #. Turn on NTP for time synchronization.
 
diff --git a/source/overview/index.rst b/source/overview/index.rst
index 8b0ef53..1305f4a 100644
--- a/source/overview/index.rst
+++ b/source/overview/index.rst
@@ -35,8 +35,8 @@
 
 If you didn't follow the steps to build your own packages from source in
 the sections for `“Building RPMs from Source” 
-<building_from_source.html#building-rpms-from-source>`_ or 
-`“Building DEB packages” <building_from_source.html#building-deb-packages>`_ 
+<../building_from_source.html#building-rpms-from-source>`_ or 
+`“Building DEB packages” <../building_from_source.html#building-deb-packages>`_ 
 you may find pre-built DEB and RPM packages for your convenience linked from 
 the `downloads <http://cloudstack.apache.org/downloads.html>`_ page.
 
diff --git a/source/qig.rst b/source/qig.rst
index 4158c1b..31b52ac 100644
--- a/source/qig.rst
+++ b/source/qig.rst
@@ -34,7 +34,7 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 This runbook will focus on building a CloudStack cloud using KVM on CentOS 
-6.5 with NFS storage on a flat layer-2 network utilizing layer-3 network 
+6.8 with NFS storage on a flat layer-2 network utilizing layer-3 network 
 isolation (aka Security Groups), and doing it all on a single piece of 
 hardware.
 
@@ -53,7 +53,7 @@
 
 #. At least one computer which supports and has enabled hardware virtualization.
 
-#. The `CentOS 6.5 x86_64 minimal install CD 
+#. The `CentOS 6.8 x86_64 minimal install CD 
    <http://mirrors.kernel.org/centos/6/isos/x86_64/>`_
 
 #. A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on 
@@ -71,7 +71,7 @@
 Operating System
 ~~~~~~~~~~~~~~~~
 
-Using the CentOS 6.5 x86_64 minimal install ISO, you'll need to install CentOS 6 
+Using the CentOS 6.8 x86_64 minimal install ISO, you'll need to install CentOS 6 
 on your hardware. The defaults will generally be acceptable for this 
 installation.
 
@@ -256,7 +256,7 @@
 
    [cloudstack]
    name=cloudstack
-   baseurl=http://cloudstack.apt-get.eu/centos/6/4.8/
+   baseurl=http://cloudstack.apt-get.eu/centos/6/4.9/
    enabled=1
    gpgcheck=0
 
@@ -278,8 +278,8 @@
 
 .. sourcecode:: bash
 
-   /secondary *(rw,async,no_root_squash,no_subtree_check)
-   /primary *(rw,async,no_root_squash,no_subtree_check)
+   /export/secondary *(rw,async,no_root_squash,no_subtree_check)
+   /export/primary *(rw,async,no_root_squash,no_subtree_check)
 
 You will note that we specified two directories that don't exist (yet) on the 
 system. We'll go ahead and create those directories and set permissions 
@@ -287,8 +287,8 @@
 
 .. sourcecode:: bash
 
-   # mkdir /primary
-   # mkdir /secondary
+   # mkdir -p /export/primary
+   # mkdir /export/secondary
 
 CentOS 6.x releases use NFSv4 by default. NFSv4 requires that domain setting 
 matches on all clients. In our case, the domain is cloud.priv, so ensure that 
@@ -380,6 +380,33 @@
    # chkconfig mysqld on
 
 
+MySQL connector Installation
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Install Python MySQL connector using the official MySQL packages repository.
+Create the file ``/etc/yum.repos.d/mysql.repo`` with the following content:
+
+.. sourcecode:: bash
+
+   [mysql-connectors-community]
+   name=MySQL Community connectors
+   baseurl=http://repo.mysql.com/yum/mysql-connectors-community/el/$releasever/$basearch/
+   enabled=1
+   gpgcheck=1
+
+Import GPG public key from MySQL:
+
+.. sourcecode:: bash
+
+   rpm --import http://repo.mysql.com/RPM-GPG-KEY-mysql
+
+Install mysql-connector
+
+.. sourcecode:: bash
+
+   yum install mysql-connector-python
+
+
 Installation
 ~~~~~~~~~~~~
 
@@ -425,7 +452,7 @@
 .. sourcecode:: bash
   
    /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt \
-   -m /secondary \
+   -m /export/secondary \
    -u http://cloudstack.apt-get.eu/systemvm/4.6/systemvm64template-4.6.0-kvm.qcow2.bz2 \
    -h kvm -F
 
@@ -489,9 +516,9 @@
 the QEMU VNC configuration. This is done by editing /etc/libvirt/qemu.conf and 
 ensuring the following line is present and uncommented.
 
-..
+::
 
-  vnc_listen=0.0.0.0
+   vnc_listen=0.0.0.0
 
 
 Libvirt Configuration
@@ -575,13 +602,13 @@
 
 #. Name - we will set this to the ever-descriptive 'Zone1' for our cloud.
 
-#. Public DNS 1 - we will set this to '8.8.8.8' for our cloud.
+#. Public DNS 1 - we will set this to ``8.8.8.8`` for our cloud.
 
-#. Public DNS 2 - we will set this to '8.8.4.4' for our cloud.
+#. Public DNS 2 - we will set this to ``8.8.4.4`` for our cloud.
 
-#. Internal DNS1 - we will also set this to '8.8.8.8' for our cloud.
+#. Internal DNS1 - we will also set this to ``8.8.8.8`` for our cloud.
 
-#. Internal DNS2 - we will also set this to '8.8.4.4' for our cloud. 
+#. Internal DNS2 - we will also set this to ``8.8.4.4`` for our cloud. 
 
 .. note:: 
    CloudStack distinguishes between internal and public DNS. Internal DNS is 
@@ -601,19 +628,19 @@
 Now that we've added a Zone, the next step that comes up is a prompt for 
 information regading a pod. Which is looking for several items.
 
-#. Name - We'll use Pod1 for our cloud.
+#. Name - We'll use ``Pod1`` for our cloud.
 
-#. Gateway - We'll use 172.16.10.1 as our gateway
+#. Gateway - We'll use ``172.16.10.1`` as our gateway
 
-#. Netmask - We'll use 255.255.255.0
+#. Netmask - We'll use ``255.255.255.0``
 
-#. Start/end reserved system IPs - we will use 172.16.10.10-172.16.10.20
+#. Start/end reserved system IPs - we will use ``172.16.10.10-172.16.10.20``
 
-#. Guest gateway - We'll use 172.16.10.1
+#. Guest gateway - We'll use ``172.16.10.1``
 
-#. Guest netmask - We'll use 255.255.255.0
+#. Guest netmask - We'll use ``255.255.255.0``
 
-#. Guest start/end IP - We'll use 172.16.10.30-172.16.10.200
+#. Guest start/end IP - We'll use ``172.16.10.30-172.16.10.200``
 
 
 Cluster
@@ -622,17 +649,17 @@
 Now that we've added a Zone, we need only add a few more items for configuring 
 the cluster.
 
-#. Name - We'll use Cluster1
+#. Name - We'll use ``Cluster1``
 
-#. Hypervisor - Choose KVM
+#. Hypervisor - Choose ``KVM``
 
 You should be prompted to add the first host to your cluster at this point. 
 Only a few bits of information are needed.
 
-#. Hostname - we'll use the IP address 172.16.10.2 since we didn't set up a 
+#. Hostname - we'll use the IP address ``172.16.10.2`` since we didn't set up a 
    DNS server.
 
-#. Username - we'll use 'root'
+#. Username - we'll use ``root``
 
 #. Password - enter the operating system password for the root user
 
@@ -644,11 +671,11 @@
 information. Choose NFS as the storage type and then enter the following 
 values in the fields:
 
-#. Name - We'll use 'Primary1'
+#. Name - We'll use ``Primary1``
 
-#. Server - We'll be using the IP address 172.16.10.2
+#. Server - We'll be using the IP address ``172.16.10.2``
 
-#. Path - Well define /primary as the path we are using
+#. Path - Well define ``/export/primary`` as the path we are using
 
 
 Secondary Storage
@@ -657,9 +684,9 @@
 If this is a new zone, you'll be prompted for secondary storage information - 
 populate it as follows:
 
-#. NFS server - We'll use the IP address 172.16.10.2
+#. NFS server - We'll use the IP address ``172.16.10.2``
 
-#. Path - We'll use /secondary
+#. Path - We'll use ``/export/secondary``
 
 Now, click Launch and your cloud should begin setup - it may take several 
 minutes depending on your internet connection speed for setup to finalize.