Re: [Dev] Introducing patterns for WSO2 Puppet Modules

[Samuel Gnaniah]

Noted. Let's have a small chat on this if possible Imesh.

Thanks,

*Samuel Gnaniah*
Lead Technical Writer

WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798

On Wed, Sep 7, 2016 at 12:36 AM, Imesh Gunaratne  wrote:

> On Tue, Sep 6, 2016 at 10:09 PM, Pubudu Gunatilaka 
> wrote:
>
>>
>> Patterns will be able to use with hieradata and the following is the
>> hiera hierarchy.
>>
>> ---
>> :hierarchy:
>> - "wso2/%{::product_name}/%{::pattern}/%{::product_profile}"
>> - "wso2/%{::product_name}/%{::pattern}/common"
>> - "wso2/common"
>>
>> ​+1 for the new hierachy.​
>
>>
>>
> Initially, we will ship two basic patterns which are single JVM and fully
>> distributed deployment. Product teams will be able to add more patterns by
>> adding relevant hieradata in later stages. You can refer sample patterns
>> done for WSO2 Application Server [2].
>>
>> Hierarchy is created based on the following facts.
>>
>> 1. Pattern_01 will be always the vanilla pack.
>>
>
> It might be better to make this the single JVM deployment pattern. Calling
> it vanilla configuration might mislead users.
>
> BTW do we need to add a zero before the pattern number? I would prefer to
> avoid that.
> ​
>
>
>> 2. There will be common.yaml file in every pattern except pattern_01 to
>> share common data among the pattern. For an example, common.yaml in
>> pattern_02 will have the values common to worker and manager profiles [3].
>>
>
>
>> 3. Hieradata which is common to all the products will be kept in
>> puppet-base repo [4] and product specific hieradata will be kept in
>> relevant product repo. To run any product with hieradata, you need to merge
>> hieradata in puppet-base and product repo.
>>
>
> I
> ​f we use the term merge, it might mean that we need to merge contents of
> files. Might be better to say that we need to copy hieradata files from
> both puppet-base and product repositories.
>
> @Sam: We are trying to standardize deployment patterns of all products via
> Puppet. It would be great if we can document them in WSO2 Docs.
>
> Thanks
>
> --
> *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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Introducing patterns for WSO2 Puppet Modules

[Imesh Gunaratne]

On Tue, Sep 6, 2016 at 10:09 PM, Pubudu Gunatilaka  wrote:

>
> Patterns will be able to use with hieradata and the following is the hiera
> hierarchy.
>
> ---
> :hierarchy:
> - "wso2/%{::product_name}/%{::pattern}/%{::product_profile}"
> - "wso2/%{::product_name}/%{::pattern}/common"
> - "wso2/common"
>
> ​+1 for the new hierachy.​

>
>
Initially, we will ship two basic patterns which are single JVM and fully
> distributed deployment. Product teams will be able to add more patterns by
> adding relevant hieradata in later stages. You can refer sample patterns
> done for WSO2 Application Server [2].
>
> Hierarchy is created based on the following facts.
>
> 1. Pattern_01 will be always the vanilla pack.
>

It might be better to make this the single JVM deployment pattern. Calling
it vanilla configuration might mislead users.

BTW do we need to add a zero before the pattern number? I would prefer to
avoid that.
​


> 2. There will be common.yaml file in every pattern except pattern_01 to
> share common data among the pattern. For an example, common.yaml in
> pattern_02 will have the values common to worker and manager profiles [3].
>


> 3. Hieradata which is common to all the products will be kept in
> puppet-base repo [4] and product specific hieradata will be kept in
> relevant product repo. To run any product with hieradata, you need to merge
> hieradata in puppet-base and product repo.
>

I
​f we use the term merge, it might mean that we need to merge contents of
files. Might be better to say that we need to copy hieradata files from
both puppet-base and product repositories.

@Sam: We are trying to standardize deployment patterns of all products via
Puppet. It would be great if we can document them in WSO2 Docs.

Thanks

-- 
*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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Introducing patterns for WSO2 Puppet Modules

[Pubudu Gunatilaka]

Hi,

As we are introducing multiple deployment patterns in PaaS artifacts based
on the discussion in [1], we need to introduce patterns for puppet modules
as well. This is mainly because we use puppet provisioning to build docker
images.

Patterns will be able to use with hieradata and the following is the hiera
hierarchy.

---
:hierarchy:
- "wso2/%{::product_name}/%{::pattern}/%{::product_profile}"
- "wso2/%{::product_name}/%{::pattern}/common"
- "wso2/common"


Initially, we will ship two basic patterns which are single JVM and fully
distributed deployment. Product teams will be able to add more patterns by
adding relevant hieradata in later stages. You can refer sample patterns
done for WSO2 Application Server [2].

Hierarchy is created based on the following facts.

1. Pattern_01 will be always the vanilla pack.
2. There will be common.yaml file in every pattern except pattern_01 to
share common data among the pattern. For an example, common.yaml in
pattern_02 will have the values common to worker and manager profiles [3].
3. Hieradata which is common to all the products will be kept in
puppet-base repo [4] and product specific hieradata will be kept in
relevant product repo. To run any product with hieradata, you need to merge
hieradata in puppet-base and product repo.

Please share your thoughts.

[1] -
http://wso2-oxygen-tank.10903.n7.nabble.com/Managing-Multiple-Deployment-Patterns-in-PaaS-Artifacts-td142359.html
[2] -
https://github.com/wso2/puppet-as/tree/master/hieradata/dev/wso2/wso2as
[3] -
https://github.com/wso2/puppet-as/tree/master/hieradata/dev/wso2/wso2as/pattern_02
[4] -
https://github.com/wso2/puppet-base/blob/master/hieradata/dev/wso2/common.yaml

Thank you!
-- 
*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