[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-20 Thread Sandor Magyari (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15506470#comment-15506470
 ] 

Sandor Magyari commented on AMBARI-15538:
-

Committed to branch-2.4

> 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.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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-15 Thread Jayush Luniya (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15494453#comment-15494453
 ] 

Jayush Luniya commented on AMBARI-15538:


Ok. But at some stage we will add support multiple service versions in a stack 
(ex: Spark 1.6 and Spark 2.0 in HDP-2.x). We can add the option of a repo at 
extension/mpack level, it can go as a separate improvement. 

> 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-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-15 Thread Jayush Luniya (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15494441#comment-15494441
 ] 

Jayush Luniya commented on AMBARI-15538:


Yes reopened so its not missed. cc: [~bsari]

> 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-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-15 Thread Lav Jain (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15494027#comment-15494027
 ] 

Lav Jain commented on AMBARI-15538:
---

[~jluniya] I do not see this JIRA being committed to 2.4.2 yet (only committed 
to 2.5 and trunk) .

> 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-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-15 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493661#comment-15493661
 ] 

Hudson commented on AMBARI-15538:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #39 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/39/])
AMBARI-15538. Support service-specific repo for add-on services (Balazs 
(smagyari: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7961cd114566d035ee844098865195667d1cb4f5])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* (add) 
ambari-server/src/test/resources/org/apache/ambari/server/stack/UpdateActiveRepoVersionOnStartupTest_initialRepos.json
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/RepositoryInfo.java
* (add) ambari-server/src/main/java/org/apache/ambari/server/stack/RepoUtil.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/stack/UpdateActiveRepoVersionOnStartup.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java
* (add) ambari-server/src/test/resources/common-services/ADDON/1.0/metainfo.xml
* (add) 
contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R/8.0.0/configuration/microsoft-r-env.xml
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/StackServiceDirectory.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/stack/StackModuleTest.java
* (edit) ambari-server/src/main/resources/version_definition.xsd
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/stack/RepoUtilTest.java
* (add) 
ambari-server/src/test/resources/common-services/ADDON/1.0/configuration/addon-env.xml
* (edit) 
contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R/8.0.0/package/scripts/microsoft_r.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/StackDirectory.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelper.java
* (add) 
ambari-server/src/test/resources/stacks_with_common_services/HDP/0.2/services/ADDON/repos/repoinfo.xml
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerCommonServicesTest.java
* (add) 
ambari-server/src/test/resources/stacks_with_common_services/HDP/0.2/services/ADDON/metainfo.xml
* (add) 
contrib/management-packs/microsoft-r_mpack/src/main/resources/custom-services/MICROSOFT_R/8.0.0/repos/repoinfo.xml
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/stack/UpdateActiveRepoVersionOnStartupTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java


> 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-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-15 Thread Sandor Magyari (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493300#comment-15493300
 ] 

Sandor Magyari commented on AMBARI-15538:
-

Committed to branch-2.5.

> 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-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-15 Thread Tim Thorpe (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493178#comment-15493178
 ] 

Tim Thorpe commented on AMBARI-15538:
-

I don't understand in the description where it says:

"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"

There was no change made to the mpacks generation.  So the repos dir would need 
to exist under the service in the mpack and the link would be from the 
HDP/2.3/services/SERVICE_NAME to the SERVICE_NAME dir wherever it exists under 
the mpack.  There wouldn't be a separate link directly to the repos dir.

> 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-patch5-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-14 Thread Matt (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491501#comment-15491501
 ] 

Matt commented on AMBARI-15538:
---

Just tested the patch. Confirming that it works for HAWQ use case!

> 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-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-14 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490866#comment-15490866
 ] 

Hudson commented on AMBARI-15538:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5669 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5669/])
AMBARI-15538. Support service-specific repo for add-on services. (Balazs 
(stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0e4515c42ba950ee73bd6511b43cc8eec7481348])
* (add) 
ambari-server/src/test/resources/org/apache/ambari/server/stack/UpdateActiveRepoVersionOnStartupTest_initialRepos.json
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/StackDirectory.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/RepositoryVersionHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java
* (add) ambari-server/src/test/resources/common-services/ADDON/1.0/metainfo.xml
* (edit) ambari-server/src/main/resources/version_definition.xsd
* (edit) 
contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R/8.0.0/package/scripts/microsoft_r.py
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/stack/UpdateActiveRepoVersionOnStartup.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/RepositoryInfo.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/StackServiceDirectory.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/stack/StackModuleTest.java
* (add) 
contrib/management-packs/microsoft-r_mpack/src/main/resources/common-services/MICROSOFT_R/8.0.0/configuration/microsoft-r-env.xml
* (add) 
ambari-server/src/test/resources/common-services/ADDON/1.0/configuration/addon-env.xml
* (add) 
ambari-server/src/test/resources/stacks_with_common_services/HDP/0.2/services/ADDON/repos/repoinfo.xml
* (add) 
contrib/management-packs/microsoft-r_mpack/src/main/resources/custom-services/MICROSOFT_R/8.0.0/repos/repoinfo.xml
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/stack/UpdateActiveRepoVersionOnStartupTest.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/stack/RepoUtilTest.java
* (add) ambari-server/src/main/java/org/apache/ambari/server/stack/RepoUtil.java
* (add) 
ambari-server/src/test/resources/stacks_with_common_services/HDP/0.2/services/ADDON/metainfo.xml
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerCommonServicesTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java


> 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
> Fix For: 2.5.0, 2.4.2
>
> Attachments: 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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-14 Thread Tim Thorpe (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490425#comment-15490425
 ] 

Tim Thorpe commented on AMBARI-15538:
-

[~jluniya] An extension version is linked to a stack version as a whole not in 
part.  So it doesn't make sense for a single extension version to contain two 
versions of the same service which are intended to be included with different 
stack versions.

> 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
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch5-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-13 Thread Tim Thorpe (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488394#comment-15488394
 ] 

Tim Thorpe commented on AMBARI-15538:
-

I will try to look at this tomorrow.  Sorry I've been busy with customer issues 
today.  [~jluniya] do you mean more than one version of the same service in the 
same extension version?  For example in EXT/1.0 containing 2 different 
MY_SERVICE versions?  If so, this won't be supported until the stack is able to 
do the same thing.  If you mean EXT/1.0/services/MY_SERVICE (version 0.1) and 
EXT/1.1/services/MY_SERVICE (version 0.2) then this is already supported.

> 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
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch3-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-13 Thread Jayush Luniya (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488361#comment-15488361
 ] 

Jayush Luniya commented on AMBARI-15538:


[~Tim Thorpe]
Latest patch submitted by [~bsari] addresses some of your comments (it handles 
repos defined for a service definition for an extension correctly as well has 
handles stack inheritance correctly). 

Lets say that in an extension we have MYSERVICE/1.0 -> HDP-2.4 and 
MYSERVICE/2.0  -> HDP-2.5. In that case we will need to add different repos for 
MYSERVICE/1.0 and MYSERVICE/2.0 (i.e. we will need to add repos at service 
level). BTW, I don't see a way to add more than one versions of a service in an 
extension. I think we need to support that? 

> 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
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch3-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-12 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486481#comment-15486481
 ] 

Hadoop QA commented on AMBARI-15538:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12828105/AMBARI-15538-custom-repos-patch3-trunk.diff
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8642//console

This message is automatically generated.

> 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
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch3-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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-09-08 Thread Tim Thorpe (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475155#comment-15475155
 ] 

Tim Thorpe commented on AMBARI-15538:
-

Will the repos folder be linked to all services?  I guess this is to reduce 
duplication?  Is this going to be specific to custom services?  What about 
extensions?  Would I need to include the repos directory under all services in 
the extension or I just include EXT/1.0/repos/repoinfo.xml and it would 
automatically get associated with all services in that extension?

Couldn't the repos just be included directly under the service folder?  Could I 
have mpacks/custom-services/8.0.0/SERVICEA/repos/repoinfo.xml

If so will there be anything to prevent an mpack from doing both?  Such that if 
a service has its own repos folder that it would be an error to either have one 
at the custom services level or potentially it just wouldn't link the other one.

Will services under the stack be allowed to specify their own repos?  Either 
those directly in any of the HDP stack versions, or in an mpack?



> 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
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-trunk-v1.patch
>
>
> 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)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

2016-08-19 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428413#comment-15428413
 ] 

Hadoop QA commented on AMBARI-15538:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12824560/AMBARI-15538-trunk-v1.patch
  against trunk revision .

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8468//console

This message is automatically generated.

> 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
> Fix For: 2.5.0
>
> Attachments: AMBARI-15538-trunk-v1.patch
>
>
> 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)