Hi Vishanth,

On Wed, Nov 23, 2016 at 12:59 AM, Vishanth Balasubramaniam <
[email protected]> wrote:

> Hi Imesh,
>
> I have now added the custom logic in setup.sh in puppet-common for
> initializing IoT.
>

​Great! I tested it and works fine!​


>
> I believe the setup script needs some improvements where I noticed that it
> still takes platform as an argument which is not being used.
>

​We have added platform parameter on purpose. The reason of having it is,
once the platform is given the setup.sh will fetch relevant Hieradata files
from the product platform repository (example: kubernetes-apim) and copy
them to the puppet home. Otherwise users will need to do that manually.

@Prasanna, Harsha, Jagath: We have now completed CEP, DAS and IoT puppet
modules and planning to release puppet-common and puppet-base. Would you
mind verifying ESB, API-M and IS puppet modules before that?

Thanks​


>
> Regards,
> Vishanth
>
> On Tue, Nov 22, 2016 at 3:23 PM, Imesh Gunaratne <[email protected]> wrote:
>
>> Adding others who are working on product puppet modules.
>>
>> I updated puppet-common and puppet-base repositories: [1], [2] as needed.
>> Vishanth is now working on adding custom logic to setup.sh in puppet-common
>> for initializing IoT product profiles. Once he is done we should be able to
>> release [1] and [2].
>>
>> [1] https://github.com/wso2/puppet-common/commits/master
>> [2] https://github.com/wso2/puppet-base/commits/master
>>
>> Thanks
>>
>> On Mon, Nov 21, 2016 at 5:33 PM, Imesh Gunaratne <[email protected]> wrote:
>>
>>> Hi Sajith,
>>>
>>> Thanks for your contributions on preparing DAS and CEP puppet modules. I
>>> will update puppet-common and puppet-base and let you know once they are
>>> ready to be released.
>>>
>>> We would need to publish product puppet modules (including wso2base) to
>>> Puppet Forge [5].
>>>
>>> [5] https://docs.puppet.com/puppet/latest/reference/modules_
>>> publishing.html
>>>
>>> Thanks
>>>
>>> On Mon, Nov 21, 2016 at 3:26 PM, Sajith Perera <[email protected]> wrote:
>>>
>>>> Hi All,
>>>>
>>>> We are planning to do a release on Puppet modules related to Complex
>>>> Event Processor 4.0.0 and Data Analytics Server 3.0.1.
>>>> Current puppet module for DAS 3.0.1 and CEP 4.0.0 supports following
>>>> deployment patterns.
>>>>
>>>> Pattern-1: Standalone server with default profile.
>>>> Pattern-2: Clustered environment (minimum HA)
>>>>
>>>> Also we are required to release puppet-common[2] 1.0.0 prior to these
>>>> releases.
>>>> I have tested the deployment scenarios via Puppet using VM and Docker
>>>> build as explained in [4].
>>>>
>>>> [1] https://github.com/wso2/puppet-cep
>>>> [2] https://github.com/wso2/puppet-das
>>>> <https://github.com/wso2/puppet-base>
>>>> [3] https://github.com/wso2/puppet-common
>>>> [4] https://github.com/wso2/puppet-base/wiki/Setting-up-the-Deve
>>>> lopment-Environment
>>>>
>>>> Thanks,
>>>> SajithD
>>>>
>>>> --
>>>> <http://wso2.com/signature>
>>>> Sajith Dimal
>>>> Software Engineer
>>>> Email : [email protected]
>>>> Mobile : +94783101496
>>>> WSO2 Inc. | http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>
>>>
>>>
>>> --
>>> *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
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>



-- 
*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
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to