[AMBARI-13456] Allow custom services to specify repositories

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.1
• Fix Version/s: 2.5.0, 2.4.2
• Component/s: stacks
• External issue URL: https://issues.cask.co/browse/CDAP-3957
• External issue ID: CDAP-3957
• Assignee: Unassigned
• Reporter: Chris Gianelloni
• Created: 16/Oct/15 15:50
• Updated: 27/Jul/17 00:18
• Resolved: 18/May/17 20:23

Description

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.

Issue Links

• Blocked: AMBARI-21584 Enable Custom Deletion of Service Repositories
• is duplicated by: AMBARI-15538 Support service-specific repo for add-on services