You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jayush Luniya (JIRA)" <ji...@apache.org> on 2016/09/15 20:30:21 UTC
[jira] [Reopened] (AMBARI-15538) Support service-specific repo for
add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jayush Luniya reopened AMBARI-15538:
------------------------------------
Please commit this to branch-2.4 too so that it is in 2.4.2 release.
> 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ázs Bence Sári
> Priority: Critical
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch6-branch-25.diff, AMBARI-15538-custom-repos-patch6-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 model.
> 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
(v6.3.4#6332)