[AMBARI-21777] Remove Ambiguous Repository Version When Creating Clusters via Blueprints

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.6.0
• Component/s: ambari-server
• Assignee: Dmytro Grinenko
• Reporter: Dmytro Grinenko
• Created: 22/Aug/17 11:26
• Updated: 28/Aug/17 11:40
• Resolved: 25/Aug/17 16:48

Description

When creating a new cluster via a blueprint, we currently use a combination of stack and version:

{
  "blueprint" : "foo",
  "repository_version": "2.5.0.0-1237",
  "host_groups" :[
    {
      "name" : "host_group_1", 
      "hosts" : [         
        {
          "fqdn" : "c6401.ambari.apache.org"
        },
        {
          "fqdn" : "c6402.ambari.apache.org"
        },
        {
          "fqdn" : "c6403.ambari.apache.org"
        }
      ]
    }
 ]
}

We lookup the repository using a query by stack/version. We could instead also take a repo ID which removes any ambiguity.

Something like:

{
  "blueprint" : "foo",
  "repository_id": 1,
  "host_groups" :[
    {
      "name" : "host_group_1", 
      "hosts" : [         
        {
          "fqdn" : "c6401.ambari.apache.org"
        },
        {
          "fqdn" : "c6402.ambari.apache.org"
        },
        {
          "fqdn" : "c6403.ambari.apache.org"
        }
      ]
    }
 ]
}

Issue Links

• links to: Review Board