ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Thorpe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services
Date Thu, 08 Sep 2016 22:01:20 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475155#comment-15475155
] 

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

Will the repos folder be linked to all services?  I guess this is to reduce duplication? 
Is this going to be specific to custom services?  What about extensions?  Would I need to
include the repos directory under all services in the extension or I just include EXT/1.0/repos/repoinfo.xml
and it would automatically get associated with all services in that extension?

Couldn't the repos just be included directly under the service folder?  Could I have mpacks/custom-services/8.0.0/SERVICEA/repos/repoinfo.xml

If so will there be anything to prevent an mpack from doing both?  Such that if a service
has its own repos folder that it would be an error to either have one at the custom services
level or potentially it just wouldn't link the other one.

Will services under the stack be allowed to specify their own repos?  Either those directly
in any of the HDP stack versions, or in an mpack?



> 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-trunk-v1.patch
>
>
> 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)

Mime
View raw message