[AMBARI-15538] Support service-specific repo for add-on services

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.0, 2.2.0, 2.4.0
• Fix Version/s: 2.5.0, 2.4.2
• Component/s: ambari-server
• Epic Link: ServiceExtensions
• Assignee: Balázs Bence Sári
• Reporter: Jayush Luniya
• Created: 23/Mar/16 18:55
• Updated: 02/Aug/17 23:14
• Resolved: 21/Sep/16 11:33

Description

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

Issue Links

• blocks: AMBARI-18349 Specify role command order to make Microsoft-R service check run after YARN is started
• duplicates: AMBARI-17285 Custom service repos in repoinfo.xml got overwritten by public VDFs
• duplicates: AMBARI-13456 Allow custom services to specify repositories
• is duplicated by: AMBARI-17285 Custom service repos in repoinfo.xml got overwritten by public VDFs
• relates to: AMBARI-21625 Failed to update custom repos defined via service extension after such a service is installed to cluster
• relates to: AMBARI-18049 Extensions should support repositories
• links to: Link to review request