[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: AMBARI-15538-custom-repos-patch-branch-24.diff Patch for 2.4 branch > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: AMBARI-15538-custom-repos-patch6-branch-25.diff Latest 2.5 patch. > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: (was: AMBARI-15538-custom-repos-patch5-branch-25.diff) > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: AMBARI-15538-custom-repos-patch5-branch-25.diff Patch for 2.5 branch > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-15538: --- Priority: Critical (was: Major) > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: (was: AMBARI-15538-custom-repos-patch5-trunk.diff) > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: AMBARI-15538-custom-repos-patch6-trunk.diff Latest patch > 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, > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: (was: AMBARI-15538-custom-repos-patch3-trunk.diff) > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: AMBARI-15538-custom-repos-patch5-trunk.diff Latest version of the patch. > 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, > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Status: Open (was: Patch Available) > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: AMBARI-15538-custom-repos-patch3-trunk.diff Latest patch. > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Status: Patch Available (was: Open) > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Status: Open (was: Patch Available) > 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 > > > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: (was: AMBARI-15538-trunk-v1.patch) > 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 > > > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-15538: --- Fix Version/s: 2.4.2 > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Status: Patch Available (was: In Progress) > 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)
[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Attachment: AMBARI-15538-trunk-v1.patch Patch containing the fix. > 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)
[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- 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}} > 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 > > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Affects Version/s: 2.4.0 > 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 > > 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] [Updated] (AMBARI-15538) Support service-specific repo for add-on services
[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-15538: --- Fix Version/s: 2.5.0 > 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 > > > 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)