Hi Anuruddha,

Great work Anuruddha!

I think we need to include the platform as well. If we consider the big
picture, ideally any user should be able to use this script and create a
puppet home for building docker images for Kubernetes, Mesos, or any other
platforms. As we have separate repos for platform hieradata,  we need to
copy those hieradata to the puppet home repo.

Thank you!


On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne <im...@wso2.com> wrote:

>
>
> On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi Imesh,
>>
>> I have now added the ability to configure multiple products using comma
>> separated product list.
>> Also included '-p all' option which configures all the products.
>>
>> Ex: ./setup.sh -p as
>> Ex: ./setup.sh -p as,esb,bps
>> Ex: ./setup.sh -p all
>>
>
> Great!
> ​Nice to hear that!
>
>>
>> On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>> Great work Anuruddha! The bash script works well!
>>>
>>> Shall we add the ability to install multiple product modules in one go?
>>> Maybe we can use a comma separated product list with -p.
>>>
>>> Thanks
>>>
>>> On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> We have  created separate GitHub repos for Puppet modules so that the
>>>> Puppet module can be shipped as part of a product release.
>>>>
>>>> Since modules are distributed we have introduced a script to generate
>>>> PUPPET_HOME. The script will work as following.
>>>>
>>>>  1. Check puppet_home folder exists.
>>>>
>>>>  2. Create folder structure required for puppet_home.
>>>>     ├── hiera.yaml
>>>>     ├── hieradata
>>>>     ├── manifests
>>>>     └── modules
>>>>
>>>> 3.  Create a symlink to manifest/site.pp file.
>>>>
>>>> 4. Clone wso2base puppet module into  <PUPPET_HOME>/modules directory.
>>>>
>>>> 5. Create a symlink to wso2base common.yaml hiera-file.
>>>>
>>>>> <PUPPET_HOME>/modules/wso2base/hieradata/wso2/common.yaml ->
>>>>> <PUPPET_HOME>/hieradata/dev/wso2/
>>>>
>>>>
>>>> 6. Clone wso2<product> puppet module into  <PUPPET_HOME>/modules
>>>> directory.
>>>>
>>>> 7. Create a symlink to wso2<product> hiera-files.
>>>>
>>>>>   <PUPPET_HOME>/wso2<product>/hieradata/dev/wso2/wso2<product> ->
>>>>> ../hieradata/dev/wso2/
>>>>
>>>>
>>>> Once the setup.sh completes, users can copy product pack and jdk
>>>> distribution for relevant folders and run vagrant setup against
>>>> above-created puppet home.
>>>>
>>>> We are planning to automate the copying of product pack, jdk
>>>> distribution and starting vagrant setup as well.
>>>>
>>>> Setup.sh can be found at [1]. Please share your suggestions towards
>>>> this approach.
>>>>
>>>> [1] https://github.com/wso2/puppet-common/blob/master/setup.sh
>>>>
>>>> --
>>>> *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
>>>>
>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Software Architect
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: https://medium.com/@imesh TW: @imesh
>>> lean. enterprise. middleware
>>>
>>>
>>
>>
>> --
>> *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
>>
>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to