Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 13 Sep 2016 20:55:20 +0000 (UTC)
From: "Tim Thorpe (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12952943.1458759305000.563831.1473800120532@Atlassian.JIRA>
In-Reply-To: <JIRA.12952943.1458759305000@Atlassian.JIRA>
References: <JIRA.12952943.1458759305000@Atlassian.JIRA> <JIRA.12952943.1458759305494@arcas>
Subject: [jira] [Commented] (AMBARI-15538) Support service-specific repo for
 add-on services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 13 Sep 2016 20:55:22 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-15538?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
488394#comment-15488394 ]=20

Tim Thorpe commented on AMBARI-15538:
-------------------------------------

I will try to look at this tomorrow.  Sorry I've been busy with customer is=
sues today.  [~jluniya] do you mean more than one version of the same servi=
ce in the same extension version?  For example in EXT/1.0 containing 2 diff=
erent MY_SERVICE versions?  If so, this won't be supported until the stack =
is able to do the same thing.  If you mean EXT/1.0/services/MY_SERVICE (ver=
sion 0.1) and EXT/1.1/services/MY_SERVICE (version 0.2) then this is alread=
y supported.

> Support service-specific repo for add-on services
> -------------------------------------------------
>
>                 Key: AMBARI-15538
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15538
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0, 2.2.0, 2.4.0
>            Reporter: Jayush Luniya
>            Assignee: Bal=C3=A1zs Bence S=C3=A1ri
>             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 {{/a=
pi/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo fi=
les 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 model.
> Now the management-pack will provide such repos/ folder in {{mpacks/custo=
m-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
(v6.3.4#6332)