Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 6 Jul 2017 13:27:01 +0000 (UTC)
From: "Antonenko Alexander (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13082513.1498486097000.184604.1499347621398@Atlassian.JIRA>
In-Reply-To: <JIRA.13082513.1498486097000@Atlassian.JIRA>
References: <JIRA.13082513.1498486097000@Atlassian.JIRA> <JIRA.13082513.1498486097570@jira-lw-us.apache.org>
Subject: [jira] [Updated] (AMBARI-21344) Add Services Using Repository ID
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 06 Jul 2017 13:27:07 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-21344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonenko Alexander updated AMBARI-21344:
-----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Add Services Using Repository ID
> --------------------------------
>
>                 Key: AMBARI-21344
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21344
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 3.0.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-21344.patch
>
>
> Currently, the web client uses the repository version when adding services. Since multiple repositories from different vendors may have identical repository strings, we should switch to using the unique Repo ID instead of the version. Here's an example of the call being made today:
> {code:title=POST http://localhost:8080/api/v1/clusters/c1/services}
> [
>   {
>     "ServiceInfo": {
>       "service_name": "ZOOKEEPER",
>       "desired_repository_version": "2.6.0.0-334"
>     }
>   }
> ]
> {code}
> This should change to the following:
> {code:title=POST http://localhost:8080/api/v1/clusters/c1/services}
> [
>   {
>     "ServiceInfo": {
>       "service_name": "ZOOKEEPER",
>       "desired_repository_version_id": 1
>     }
>   }
> ]
> {code}
> The same change needs to be made for when a service is added to a cluster. However, this case it a bit trickier if there are multiple repositories. Until a more well-defined UX workflow is available, the following should be used for adding services:
> - If there is only a single repository, then use that one
> - If there are more than 1 repository, then choose the most recent repository
> -- It cannot be a {{PATCH}} repository
> -- Its status must be {{CURRENT}}


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)