[
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488361#comment-15488361
]
Jayush Luniya edited comment on AMBARI-15538 at 9/13/16 8:42 PM:
-----------------------------------------------------------------
[~Tim Thorpe]
Latest patch submitted by [~bsari] addresses some of your comments (it handles
repos defined for a service definition for an extension correctly as well has
handles stack inheritance correctly).
Lets say that in an extension we have MYSERVICE/1.0 -> HDP-2.4 and
MYSERVICE/2.0 -> HDP-2.5. In that case we will need to add different repos for
MYSERVICE/1.0 and MYSERVICE/2.0 (i.e. we will need to add repos at service
level).
BTW, I don't see a way to add more than one versions of a service in an
extension. I think we need to support that?
was (Author: jluniya):
[~Tim Thorpe]
Latest patch submitted by [~bsari] addresses some of your comments (it handles
repos defined for a service definition for an extension correctly as well has
handles stack inheritance correctly).
Lets say that in an extension we have MYSERVICE/1.0 -> HDP-2.4 and
MYSERVICE/2.0 -> HDP-2.5. In that case we will need to add different repos for
MYSERVICE/1.0 and MYSERVICE/2.0 (i.e. we will need to add repos at service
level). BTW, I don't see a way to add more than one versions of a service in an
extension. I think we need to support that?
> 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
> 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 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)
