[jira] [Created] (AMBARI-21344) Add Services Using Repository ID

["Antonenko Alexander (JIRA)" <ji...@apache.org>]

Antonenko Alexander created AMBARI-21344:
--------------------------------------------

             Summary: 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
            Priority: Critical
             Fix For: 3.0.0


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)