You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Chris Gianelloni (JIRA)" <ji...@apache.org> on 2017/05/18 20:24:04 UTC

[jira] [Resolved] (AMBARI-13456) Allow custom services to specify repositories

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

Chris Gianelloni resolved AMBARI-13456.
---------------------------------------
       Resolution: Duplicate
    Fix Version/s: 2.4.2
                   2.5.0

This was fixed in AMBARI-15538 and is available with Ambari 2.4.2+ and 2.5.0+

> Allow custom services to specify repositories
> ---------------------------------------------
>
>                 Key: AMBARI-13456
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13456
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.0.1
>            Reporter: Chris Gianelloni
>             Fix For: 2.5.0, 2.4.2
>
>
> When creating a custom service for inclusion into Ambari, there is no way to specify any custom repositories. There should be a way to set a definition for the repository and have it show up on the repository pages, allowing an Administrator to override it. Currently, to use a custom repository, one must modify a file in the custom service definition to point to another repository.
> For example, a custom service may use public APT/YUM repositories for fetching packages. This is done by copying an appropriate configuration file from the service definition to the cluster hosts via Ambari Agent, and packages are fetched from the official public repositories. Many Ambari users would like to point this to their internal mirrors, just like they do with HDP. This is currently not possible without modifying the repository.xml at the stack level.
> As a workaround, I am looking at having an option defined as configuration that is used in a template, but Ambari should really support this use case natively, without the service author being required to create their own implementations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)