Update CDH user doc for CDH 5.5.0

Changes:
* update cdh_imagebuilder.rst about 5.5.0 support
* update cdh_plugin.rst about 5.5.0 support

Change-Id: I2e08d9206bdc402edd554503c170caaf19cdc006
Partial-implements: blueprint cdh-5-5-support

doc/source/userdoc/cdh_imagebuilder.rst

@@ -4,8 +4,8 @@ Building Images for Cloudera Plugin
 ===================================
 
 In this document you will find instructions on how to build Ubuntu and CentOS
-images with Cloudera Express (now only 5.0.0, 5.3.0 and 5.4.0 versions are
-supported).
+images with Cloudera Express (now only 5.0.0, 5.3.0 5.4.0 and 5.5.0 versions
+are supported).
 
 Apache Hadoop. To simplify the task of building such images we use
 `Disk Image Builder <https://github.com/openstack/diskimage-builder>`_.
@@ -39,20 +39,20 @@ To create cloudera images follow these steps:
    specific operating system, you should use the "-i ubuntu|centos" parameter
    to assign the operating system (the cloudera plugin only supports Ubuntu and
    Centos). If you want to create the image only for a specific Cloudera
-   version, you should use the "-v 5.0|5.3|5.4" parameter to assign the
+   version, you should use the "-v 5.0|5.3|5.4|5.5" parameter to assign the
    version. Below is an example to create Cloudera images for both Ubuntu and
-   CentOS with Cloudera Express 5.4.0 version.
+   CentOS with Cloudera Express 5.5.0 version.
 
    .. sourcecode:: console
 
-      tox -e venv -- sahara-image-create -p cloudera -v 5.4
+      tox -e venv -- sahara-image-create -p cloudera -v 5.5
 
    If you want to create only an Ubuntu image, you may use following example
    for that.
 
    .. sourcecode:: console
 
-      tox -e venv -- sahara-image-create -p cloudera -i ubuntu -v 5.4
+      tox -e venv -- sahara-image-create -p cloudera -i ubuntu -v 5.5
 
    NOTE: If you don't want to use default values, you should explicitly set the
    values of your required parameters.

doc/source/userdoc/cdh_plugin.rst

@@ -10,16 +10,19 @@ explicitly enable or disable it in "plugins" line.
 
 You need to build images using :doc:`cdh_imagebuilder` to produce images used
 to provision cluster or you could download prepared images from
-http://sahara-files.mirantis.com/images/upstream/kilo/
-They already have Cloudera Express installed (5.0.0, 5.3.0, or 5.4.0 version).
+http://sahara-files.mirantis.com/images/upstream/
+They already have Cloudera Express installed (5.0.0, 5.3.0, 5.4.0 or 5.5.0
+version).
 
 The cloudera plugin requires an image to be tagged in Sahara Image Registry
-with two tags: 'cdh' and '<cloudera version>' (e.g. '5', '5.3.0' or '5.4.0',
-here '5' stands for '5.0.0').
+with two tags: 'cdh' and '<cloudera version>' (e.g. '5', '5.3.0', '5.4.0'
+or '5.5.0', here '5' stands for '5.0.0').
 
 The default username specified for these images is different for each
 distribution:
 
+for 5.0.0, 5.3.0 and 5.4.0 version:
+
 +--------------+------------+
 | OS           | username   |
 +==============+============+
@@ -28,6 +31,16 @@ distribution:
 | CentOS 6.6   | cloud-user |
 +--------------+------------+
 
+for 5.5.0 version:
+
++--------------+------------+
+| OS           | username   |
++==============+============+
+| Ubuntu 14.04 | ubuntu     |
++--------------+------------+
+| CentOS 6.6   | cloud-user |
++--------------+------------+
+
 Services Supported
 ------------------
 
@@ -47,13 +60,15 @@ and Key-value Store Indexer. 5.4.0 version added KMS service support based on
 High Availability Support
 -------------------------
 
-Currently HDFS NameNode High Availability is supported in Cloudera 5.4.0
-version.  You can refer to :doc:`features` for the detail info.
+Currently HDFS NameNode High Availability is supported beginning with
+Cloudera 5.4.0 version.  You can refer to :doc:`features` for the detail
+info.
 
-YARN ResourceManager High Availability is supported in Cloudera 5.4.0 version.
-This feature adds redundancy in the form of an Active/Standby ResourceManager
-pair to avoid the failure of single RM. Upon failover, the Standby RM become
-Active so that the applications can resume from their last check-pointed state.
+YARN ResourceManager High Availability is supported beginning with Cloudera
+5.4.0 version. This feature adds redundancy in the form of an Active/Standby
+ResourceManager pair to avoid the failure of single RM. Upon failover, the
+Standby RM become Active so that the applications can resume from their last
+check-pointed state.
 
 Cluster Validation
 ------------------
@@ -87,7 +102,7 @@ cloudera plugin versions:
     and at least one hbase regionserver.
   + Cluster can't contain hbase regionserver without at least one hbase maser.
 
-In case of 5.3.0 or 5.4.0 version of Cloudera Plugin there are few extra
+In case of 5.3.0, 5.4.0 or 5.5.0 version of Cloudera Plugin there are few extra
 limitations in the cluster topology:
 
   + Cluster can't contain flume without at least one datanode.