[jira] [Comment Edited] (BIGTOP-1691) Heira site.yaml template needs to have repo uri

["Evans Ye (JIRA)" <ji...@apache.org>]

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

Evans Ye edited comment on BIGTOP-1691 at 2/26/15 3:58 AM:
-----------------------------------------------------------

Hey [~cos]. I renamed the variable name from {{bigtop_yumrepo_uri}} to {{bigtop_repo_uri}} in BIGTOP-1676.
Since we now have yum and apt repo can be auto setup by puppet, the variable name should not specific to yum.

Or, we can take another strategy, that is to have two kind of repo name can be specified:
* bigtop_yumrepo_uri 
* bigtop_aptrepo_uri

Hence we can support mixed OS cluster deployment (for example, centos+debian in one cluster)
But I think this introduce more complexity and that kind of use case is rare. So I took a simple way in BIGTOP-1676.


was (Author: evans_ye):
Hey [~cos]. I renamed the variable name from {{bigtop_yumrepo_uri}} to {{bigtop_repo_uri}} in BIGTOP-1676.
Since we now have yum and apt repo can be auto setup by puppet, the variable name should not specific to yum.

Or, we can take another strategy, that is to have two kind of repo name can be specified:
* bigtop_yumrepo_uri 
* bigtop_aptrepo_uri
Hence we can support mixed OS cluster deployment (for example, centos+debian in one cluster)
But I think this introduce more complexity and that kind of use case is rare. So I took a simple way in BIGTOP-1676.

> Heira site.yaml template needs to have repo uri 
> ------------------------------------------------
>
>                 Key: BIGTOP-1691
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1691
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: deployment
>    Affects Versions: 0.8.0
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>             Fix For: 0.9.0
>
>         Attachments: 0001-BIGTOP-1691.-Heira-site.yaml-template-needs-to-have-.patch
>
>
> It seems that {{bigtop-deploy/puppet/hieradata/site.yaml}} is missing repo uri line without which a package manager won't be able to install cluster packages. I think with  BIGTOP-1676 the same will be true for apt.
> BTW, can we have multiple URLs specified for the repos? A typical use case would be when you have say release repo and a dev.repo with your experimental stuff. Right now the only way around it is by setting a second repo manually.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)