Use a better way to manage different versions of CDH

Registered by Ken Chen

Currently we do not have version management for CDH plugin at all. All codes need to support CDH version from 5.0.0 to latest (currently it is 5.3.0). This causes the issue that when new CDH or other key packages are released, we cannot make sure our plugin still work. Further more, we have to base our work on a non-static environment, and could be blocked by issues brought by new packages.
To resolve this issue, we need to support different versions of CDH in a better way (like we did for vanilla and hdp), and keep one or several stable versions of CDH as our support focus. I will write a draft to tell the detail story.

Blueprint information

Status:
Complete
Approver:
Sergey Lukjanov
Priority:
High
Drafter:
Ken Chen
Direction:
Approved
Assignee:
Ken Chen
Definition:
Approved
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon 2015.1.0
Started by
Sergey Lukjanov
Completed by
Sergey Lukjanov

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/cdh-version-management,n,z

Addressed by: https://review.openstack.org/145514
    manage CDH versions in cloudera plugin

Addressed by: https://review.openstack.org/147933
    Separate the codes of CDH5 and CDH5.3.0

Addressed by: https://review.openstack.org/148110
    Add different version builders support for Cloudera plugin

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.