Dmytro Grinenko created AMBARI-21777:
----------------------------------------
Summary: Remove Ambiguous Repository Version When Creating
Clusters via Blueprints
Key: AMBARI-21777
URL: https://issues.apache.org/jira/browse/AMBARI-21777
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
Fix For: 2.6.0
When creating a new cluster via a blueprint, we currently use a combination of
stack and version:
{code}
{
"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"
}
]
}
]
}
{code}
We lookup the repository using a query by stack/version. We could instead also
take a repo ID which removes any ambiguity.
Something like:
{code}
{
"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"
}
]
}
]
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
