[
https://issues.apache.org/jira/browse/AMBARI-18049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Thorpe resolved AMBARI-18049.
---------------------------------
Resolution: Won't Fix
Services are now able to specify their own repos. There is no longer a need
for this at the extension level.
> Extensions should support repositories
> --------------------------------------
>
> Key: AMBARI-18049
> URL: https://issues.apache.org/jira/browse/AMBARI-18049
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Tim Thorpe
> Assignee: Tim Thorpe
>
> Extensions generally contain custom services. These custom services are
> usually not included in the stack's repositories. This means that when you
> link an extension version to a stack version and want to install the
> extension's custom services, you first need to add a repositories.
> Extensions should include their own repos/repoinfo.xml. Then ambari can
> handle the new repositories automatically.
> Here are the two possible scenarios:
> A) Install cluster using HDP-2.5
> B) Add extension EXT-1.0
> C) Link EXT-1.0 to HDP-2.5
> D) Install services from EXT-1.0
> 1) Add extension EXT-1.0
> 2) Link EXT-1.0 to HDP-2.5
> 3) Install cluster using HDP-2.5 including services from EXT-1.0
> In the first case during step A, HDP-2.5's repoinfo.xml is used to populate
> the repositories in the repo_version table. During step C, EXT-1.0's
> repoinfo.xml is used to add additional repositories to the repo_version table.
> In the second case during step 3, both HDP-2.5's and EXT-1.0's repoinfo.xml
> files are used to populate the repositories in the repo_version table.
> Unlinking EXT-1.0 from HDP-2.5 would need to remove the extension's
> repositories from the repo_version table. This would use the repo_id because
> the repo_url may have been changed by the user.
> During the linking process (extension version to stack version), there would
> be a check to ensure that the extension does not duplicate any repo_ids or
> repo_urls that exist within the stack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
