Hi, To add more to what Anuruddha said, we are planning to create a separate GitHub repo called "puppet-common" to host Vagrantfile, site.pp and shell scripts to deploy WSO2 products using Puppet. Anything related to Puppet based deployment automation but does not belong to a particular Puppet module will go in here.
Thanks. On Fri, Sep 2, 2016 at 10:13 AM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi, > > We have decided to use hybrid approach of option2 and option3 as below. > > Common hieradata are added to puppet base repository > [1] with .pmtignore file. > Default platform hieradata are added to product specific > puppet repositories [2] with .pmtignore file . > Platform specific hieradata data are added to product platform artifacts > repositories [3][4]. > > > > [1] https://github.com/wso2/puppet-base > [2] https://github.com/wso2/puppet-as > [3] https://github.com/wso2/mesos-artifacts-as > [4] https://github.com/wso2/kubernetes-artifacts-as > > > On Fri, Sep 2, 2016 at 6:19 AM, Isuru Haththotuwa <isu...@wso2.com> wrote: > >> Hi Anurudhdha, >> >> Are we not keeping default platform hieradata in the puppet module repo >> itself? >> >> On Fri, Aug 26, 2016 at 9:44 AM, Akila Ravihansa Perera < >> raviha...@wso2.com> wrote: >> >>> Hi, >>> >>> There is one catch with option 2; we need to track which Hiera >>> distribution (in platform specific artifacts repo) goes with which Puppet >>> release. This won't be a big issue but just wanted point out. >>> >>> Thanks. >>> >>> On Fri, Aug 26, 2016 at 9:05 AM, Rasanjaya Subasinghe < >>> rasanj...@wso2.com> wrote: >>> >>>> Hi all, >>>> >>>> The option 2 would be good for do the MC deployment. And other >>>> users can be used default profile with released puppet forge module. >>>> >>>> Thanks >>>> >>>> >>>> On Thursday, August 25, 2016, Anuruddha Liyanarachchi < >>>> anurudd...@wso2.com> wrote: >>>> >>>>> Hi Devs, >>>>> >>>>> We are in the process of restructuring and splitting the puppet >>>>> modules per product. As per the initial discussions, we have created >>>>> separate repositories per product puppet module and one common repository >>>>> for puppet base module. >>>>> >>>>> In order to publish puppet modules to puppet forge, we have decoupled >>>>> hieradata from puppet modules using profiles. Now the puppet modules are >>>>> capable of running without hieradata for the default profile. >>>>> >>>>> However, it is easier to do deployment using hieradata. The intention >>>>> of this mail is to discuss and finalize hieradata location. >>>>> >>>>> Appreciate your feedback on selecting an available option. >>>>> >>>>> Following are the available options: >>>>> >>>>> *1. Use one repository to keep all product hieradata.* >>>>> Pros: >>>>> - Easy to manage since all the hieradata are in one place. >>>>> - No data duplication >>>>> >>>>> Cons: >>>>> - Releasing hieradata with a product is not possible. >>>>> - Difficult to track changes. >>>>> >>>>> >>>>> *2. Keep hieradata with platform specific artifact repositories. >>>>> (kubernetes, mesos )* >>>>> Pros: >>>>> - Hieradata can be released with a product. >>>>> >>>>> Cons: >>>>> - Possible data duplication. >>>>> - Hieradata is a part of puppet and it is not related to mesos or >>>>> kubernetes >>>>> - Have to create repositories to store default hieradata. >>>>> >>>>> >>>>> *3. Create separate repositories per product to store hieradata. * >>>>> Pros: >>>>> - Product level hieradata separation. >>>>> - Easier to release and track changes. >>>>> >>>>> Cons: >>>>> - No of repositories are high. >>>>> - User experience will be not good as users will have to clone from >>>>> multiple locations. >>>>> >>>>> >>>>> >>>>> *4. Keep hieradata in the product puppet module repos with >>>>> .pmtignore file. *Pros: >>>>> - Minimum changes required. >>>>> - Can be released with product puppet modules. >>>>> >>>>> Cons: >>>>> - Most of the puppet repos don't contain hieradata >>>>> - Puppet recommends keeping hieradata separately from modules. >>>>> >>>>> >>>>> >>>>> -- >>>>> *Thanks and Regards,* >>>>> Anuruddha Lanka Liyanarachchi >>>>> Software Engineer - WSO2 >>>>> Mobile : +94 (0) 712762611 >>>>> Tel : +94 112 145 345 >>>>> anurudd...@wso2.com >>>>> >>>> >>>> >>>> -- >>>> ------------------------------------- >>>> Rasanjaya Subasinghe >>>> Software Engineer, Dev/Ops, WSO2 Inc. >>>> +94772250358 >>>> rasanj...@wso2.com >>>> >>>> >>> >>> >>> -- >>> Akila Ravihansa Perera >>> WSO2 Inc.; http://wso2.com/ >>> >>> Blog: http://ravihansa3000.blogspot.com >>> >> >> >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048* <http://wso2.com/>* >> >> >> > > > -- > *Thanks and Regards,* > Anuruddha Lanka Liyanarachchi > Software Engineer - WSO2 > Mobile : +94 (0) 712762611 > Tel : +94 112 145 345 > a <thili...@wso2.com>nurudd...@wso2.com > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
