ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21777) Remove Ambiguous Repository Version When Creating Clusters via Blueprints
Date Mon, 28 Aug 2017 11:41:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-21777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143677#comment-16143677
] 

Hudson commented on AMBARI-21777:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #71 (See [https://builds.apache.org/job/Ambari-branch-2.6/71/])
AMBARI-21777 Remove Ambiguous Repository Version When Creating Clusters (hapylestat: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=24639dd02bfa8c60e972569515f01fae0679b598])
* (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartOnComponentLevelTest.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterDeployWithStartOnlyTest.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java


> 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
>
>         Attachments: AMBARI-21777-2.6.patch, AMBARI-21777-2.6-UT-FIX.patch, AMBARI-21777.patch
>
>
> 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)

Mime
View raw message