Thank you for providing that info and being so patient with the response.
For a testing/dev cluster to mirror a production cluster, The common practice is to make another cluster(with less nodes) Using a path B install.* This is what I would recommend. You’ll want to make a tweak along the way to install your desired version though.
Establishing your Repo Strategy:
When you get to this part of the install instructions, you’ll be instructed to make a repo file for your CM version. When you click the link for Cent OS6, you’ll be presented with this. I’ve bolded the line you’re going to change.
[cloudera-manager]
# Packages for Cloudera Manager, Version 5, on RedHat or CentOS 6 x86_64
name=Cloudera Manager
baseurl=https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5/ (remove this)
gpgkey =https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera
gpgcheck = 1
After you make the change, it should look like this
[cloudera-manager]
# Packages for Cloudera Manager, Version 5, on RedHat or CentOS 6 x86_64
name=Cloudera Manager
baseurl=https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.7.0/ (add this)
gpgkey =https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera
gpgcheck = 1
This will direct yum to your desired version of Cloudera Manager, which in turn will provide you with the proper options for installing your desired version of CDH during setup.
You can use this method for any version you desire. Simple follow the link in baseurl, navigate to the root directory of the version you want in the archive, and copy that url to the baseurl field. This method has been tested by yours truly. ;)
Other than that, just follow the instructions for the path B install, and you’ll be good to go.
Let me know if this helps, or if you have any questions.
Cheers
* Here’s a link to some cool video guides too <<-------- click that guy
