ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Balázs Bence Sári (JIRA) <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
Date Mon, 03 Oct 2016 11:55:20 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Balázs Bence Sári updated AMBARI-15538:
---------------------------------------
    Attachment: AMBARI-15538-custom-repos-patch-branch-24-part2.diff

> 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-patch-branch-24-part2.diff, AMBARI-15538-custom-repos-patch-branch-24.diff,
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)

Mime
View raw message