ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services
Date Tue, 13 Sep 2016 06:56:20 GMT


Hadoop QA commented on AMBARI-15538:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> Support service-specific repo for add-on services
> -------------------------------------------------
>                 Key: AMBARI-15538
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0, 2.2.0, 2.4.0
>            Reporter: Jayush Luniya
>            Assignee: Balázs Bence Sári
>             Fix For: 2.5.0, 2.4.2
>         Attachments: AMBARI-15538-custom-repos-patch3-trunk.diff
> The approach for custom-services to specify their own repo location will be to provide
a {{/repos/repoinfo.xml}} inside the stack-version they will be in. This repo file will be
loaded by Ambari during startup into the {{/api/v1/stacks/HDP/versions/2.4/repository_versions}}
repos. *Service repo files have a restriction that their (repo-name, base-url) locations should
be unique and not conflict*. When conflicts do occur, they will not be loaded into the stacks
> Now the management-pack will provide such repos/ folder in {{mpacks/custom-services/8.0.0/repos}}
which will be linked into the stacks/ folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
-> mpacks/custom-services/8.0.0/repos}}

This message was sent by Atlassian JIRA

View raw message