Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Pubudu Gunatilaka]

Hi,

We have released puppet-base [1] and puppet-common [2] repos. Now you can
release the product puppet modules against the latest puppet-base module.
Setup guide can be found in [3].

[1] - https://github.com/wso2/puppet-base/releases/tag/v1.0.0
[2] - https://github.com/wso2/puppet-common/releases/tag/v1.0.0
[3] - https://github.com/wso2/puppet-base/wiki

Thank you!

On Tue, Feb 21, 2017 at 11:39 AM, Pubudu Gunatilaka 
wrote:

> Hi Raj,
>
> We haven't considered this aspect. In the latest puppet modules we have
> introduced two ways of applying patches.
>
> 1. You can just copy patches into the patches folder and all the patches
> inside that folder will be copied.
> 2. You can define required patches in a patch list. Once this is defined,
> it will copy only the mentioned patches.
>
> I think you can use option 2 which is the patch list to define the
> relevant patches. But it does not check the checksum of the patch. If you
> need to verify the checksum of the patches, you can write a custom function
> and call this function to copy patches.
>
> Thank you!
>
> On Tue, Feb 21, 2017 at 11:31 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Raj,
>>
>> On Tue, Feb 21, 2017 at 11:23 AM, Rajkumar Rajaratnam > > wrote:
>>
>>> Hi Pubudu,
>>>
>>> Thanks for the response. My question is bit different. We have a
>>> requirement that we want to make sure the official patches released by WSO2
>>> should be applied to the nodes. That means, we should be able to specify
>>> the the checksum of the official patches in hiera or whatever and verify
>>> the checksum of the patches before applying it to the nodes. I think with
>>> the current puppet modules, it's not possible to do, as we copy all patches
>>> found inside /files folder to the nodes. But if we want to have this
>>> feature, then we need to define a resource per patch, I think that's not
>>> scalable or maintainable.
>>>
>> Do we need a resource per patch here? If we have the list of official
>> patches and their checksums, we can write a function in the puppet side to
>> verify and apply AFAIU?
>>
>> However, I do believe that applying only official patches for production
>> environment is the responsibility of the person/team who is maintaining the
>> deployment. And with WUM, we won't have this issue.
>>
>>>
>>> Thanks,
>>> Raj.
>>>
>>> On Tue, Feb 21, 2017 at 12:42 AM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Raj,

 Yes, we do. Basically, when copying files or templates puppet checks
 the checksum by default. We haven't done anything specifically to verify
 checksum in files in our puppet modules.

 Thank you!

 On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam <
 rajkum...@wso2.com> wrote:

> Hi Pubudu,
>
> Do we support verifying checksum when applying patches, in latest
> puppet modules?
>
> Thanks,
> Raj.
>
> On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Devs,
>>
>> We are currently doing final testing for releasing puppet-base [1]
>> and puppet-common [2] repositories. Once these repos are released,
>> puppet-apim, puppet-iot and puppet-is can be released for latest product
>> versions. Please let us know if you have any concerns.
>>
>> [1] - https://github.com/wso2/puppet-base
>> [2] - https://github.com/wso2/puppet-common
>>
>> 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
>>
>>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Senior Software Engineer, WSO2
>
> LinkedIn : https://lk.linkedin.com/in/rajuu
> Mobile : +94777568639 <+94%2077%20756%208639>
>



 --
 *Pubudu Gunatilaka*
 Committer and PMC Member - Apache Stratos
 Software Engineer
 WSO2, Inc.: http://wso2.com
 mobile : +94774078049 <%2B94772207163>


>>>
>>>
>>> --
>>> Rajkumar Rajaratnam
>>> Committer & PMC Member, Apache Stratos
>>> Senior Software Engineer, WSO2
>>>
>>> LinkedIn : https://lk.linkedin.com/in/rajuu
>>> Mobile : +94777568639 <077%20756%208639>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048 <+94%2071%20635%208048>* *
>>
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


-- 
*Pubudu 

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Pubudu Gunatilaka]

Hi Raj,

We haven't considered this aspect. In the latest puppet modules we have
introduced two ways of applying patches.

1. You can just copy patches into the patches folder and all the patches
inside that folder will be copied.
2. You can define required patches in a patch list. Once this is defined,
it will copy only the mentioned patches.

I think you can use option 2 which is the patch list to define the relevant
patches. But it does not check the checksum of the patch. If you need to
verify the checksum of the patches, you can write a custom function and
call this function to copy patches.

Thank you!

On Tue, Feb 21, 2017 at 11:31 AM, Isuru Haththotuwa  wrote:

> Hi Raj,
>
> On Tue, Feb 21, 2017 at 11:23 AM, Rajkumar Rajaratnam 
> wrote:
>
>> Hi Pubudu,
>>
>> Thanks for the response. My question is bit different. We have a
>> requirement that we want to make sure the official patches released by WSO2
>> should be applied to the nodes. That means, we should be able to specify
>> the the checksum of the official patches in hiera or whatever and verify
>> the checksum of the patches before applying it to the nodes. I think with
>> the current puppet modules, it's not possible to do, as we copy all patches
>> found inside /files folder to the nodes. But if we want to have this
>> feature, then we need to define a resource per patch, I think that's not
>> scalable or maintainable.
>>
> Do we need a resource per patch here? If we have the list of official
> patches and their checksums, we can write a function in the puppet side to
> verify and apply AFAIU?
>
> However, I do believe that applying only official patches for production
> environment is the responsibility of the person/team who is maintaining the
> deployment. And with WUM, we won't have this issue.
>
>>
>> Thanks,
>> Raj.
>>
>> On Tue, Feb 21, 2017 at 12:42 AM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Raj,
>>>
>>> Yes, we do. Basically, when copying files or templates puppet checks the
>>> checksum by default. We haven't done anything specifically to verify
>>> checksum in files in our puppet modules.
>>>
>>> Thank you!
>>>
>>> On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam >> > wrote:
>>>
 Hi Pubudu,

 Do we support verifying checksum when applying patches, in latest
 puppet modules?

 Thanks,
 Raj.

 On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
 wrote:

> Hi Devs,
>
> We are currently doing final testing for releasing puppet-base [1] and
> puppet-common [2] repositories. Once these repos are released, 
> puppet-apim,
> puppet-iot and puppet-is can be released for latest product versions.
> Please let us know if you have any concerns.
>
> [1] - https://github.com/wso2/puppet-base
> [2] - https://github.com/wso2/puppet-common
>
> 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
>
>


 --
 Rajkumar Rajaratnam
 Committer & PMC Member, Apache Stratos
 Senior Software Engineer, WSO2

 LinkedIn : https://lk.linkedin.com/in/rajuu
 Mobile : +94777568639 <+94%2077%20756%208639>

>>>
>>>
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Senior Software Engineer, WSO2
>>
>> LinkedIn : https://lk.linkedin.com/in/rajuu
>> Mobile : +94777568639 <077%20756%208639>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048 <+94%2071%20635%208048>* *
>
>
>


-- 
*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

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Isuru Haththotuwa]

Hi Raj,

On Tue, Feb 21, 2017 at 11:23 AM, Rajkumar Rajaratnam 
wrote:

> Hi Pubudu,
>
> Thanks for the response. My question is bit different. We have a
> requirement that we want to make sure the official patches released by WSO2
> should be applied to the nodes. That means, we should be able to specify
> the the checksum of the official patches in hiera or whatever and verify
> the checksum of the patches before applying it to the nodes. I think with
> the current puppet modules, it's not possible to do, as we copy all patches
> found inside /files folder to the nodes. But if we want to have this
> feature, then we need to define a resource per patch, I think that's not
> scalable or maintainable.
>
Do we need a resource per patch here? If we have the list of official
patches and their checksums, we can write a function in the puppet side to
verify and apply AFAIU?

However, I do believe that applying only official patches for production
environment is the responsibility of the person/team who is maintaining the
deployment. And with WUM, we won't have this issue.

>
> Thanks,
> Raj.
>
> On Tue, Feb 21, 2017 at 12:42 AM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Raj,
>>
>> Yes, we do. Basically, when copying files or templates puppet checks the
>> checksum by default. We haven't done anything specifically to verify
>> checksum in files in our puppet modules.
>>
>> Thank you!
>>
>> On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam 
>> wrote:
>>
>>> Hi Pubudu,
>>>
>>> Do we support verifying checksum when applying patches, in latest puppet
>>> modules?
>>>
>>> Thanks,
>>> Raj.
>>>
>>> On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Devs,

 We are currently doing final testing for releasing puppet-base [1] and
 puppet-common [2] repositories. Once these repos are released, puppet-apim,
 puppet-iot and puppet-is can be released for latest product versions.
 Please let us know if you have any concerns.

 [1] - https://github.com/wso2/puppet-base
 [2] - https://github.com/wso2/puppet-common

 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


>>>
>>>
>>> --
>>> Rajkumar Rajaratnam
>>> Committer & PMC Member, Apache Stratos
>>> Senior Software Engineer, WSO2
>>>
>>> LinkedIn : https://lk.linkedin.com/in/rajuu
>>> Mobile : +94777568639 <+94%2077%20756%208639>
>>>
>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Senior Software Engineer, WSO2
>
> LinkedIn : https://lk.linkedin.com/in/rajuu
> Mobile : +94777568639 <077%20756%208639>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Rajkumar Rajaratnam]

Hi Pubudu,

Thanks for the response. My question is bit different. We have a
requirement that we want to make sure the official patches released by WSO2
should be applied to the nodes. That means, we should be able to specify
the the checksum of the official patches in hiera or whatever and verify
the checksum of the patches before applying it to the nodes. I think with
the current puppet modules, it's not possible to do, as we copy all patches
found inside /files folder to the nodes. But if we want to have this
feature, then we need to define a resource per patch, I think that's not
scalable or maintainable.

Thanks,
Raj.

On Tue, Feb 21, 2017 at 12:42 AM, Pubudu Gunatilaka 
wrote:

> Hi Raj,
>
> Yes, we do. Basically, when copying files or templates puppet checks the
> checksum by default. We haven't done anything specifically to verify
> checksum in files in our puppet modules.
>
> Thank you!
>
> On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam 
> wrote:
>
>> Hi Pubudu,
>>
>> Do we support verifying checksum when applying patches, in latest puppet
>> modules?
>>
>> Thanks,
>> Raj.
>>
>> On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> We are currently doing final testing for releasing puppet-base [1] and
>>> puppet-common [2] repositories. Once these repos are released, puppet-apim,
>>> puppet-iot and puppet-is can be released for latest product versions.
>>> Please let us know if you have any concerns.
>>>
>>> [1] - https://github.com/wso2/puppet-base
>>> [2] - https://github.com/wso2/puppet-common
>>>
>>> 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
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Senior Software Engineer, WSO2
>>
>> LinkedIn : https://lk.linkedin.com/in/rajuu
>> Mobile : +94777568639 <+94%2077%20756%208639>
>>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


-- 
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2

LinkedIn : https://lk.linkedin.com/in/rajuu
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Pubudu Gunatilaka]

Hi Raj,

Yes, we do. Basically, when copying files or templates puppet checks the
checksum by default. We haven't done anything specifically to verify
checksum in files in our puppet modules.

Thank you!

On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam 
wrote:

> Hi Pubudu,
>
> Do we support verifying checksum when applying patches, in latest puppet
> modules?
>
> Thanks,
> Raj.
>
> On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Devs,
>>
>> We are currently doing final testing for releasing puppet-base [1] and
>> puppet-common [2] repositories. Once these repos are released, puppet-apim,
>> puppet-iot and puppet-is can be released for latest product versions.
>> Please let us know if you have any concerns.
>>
>> [1] - https://github.com/wso2/puppet-base
>> [2] - https://github.com/wso2/puppet-common
>>
>> 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
>>
>>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Senior Software Engineer, WSO2
>
> LinkedIn : https://lk.linkedin.com/in/rajuu
> Mobile : +94777568639 <+94%2077%20756%208639>
>



-- 
*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

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Rajkumar Rajaratnam]

Hi Pubudu,

Do we support verifying checksum when applying patches, in latest puppet
modules?

Thanks,
Raj.

On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
wrote:

> Hi Devs,
>
> We are currently doing final testing for releasing puppet-base [1] and
> puppet-common [2] repositories. Once these repos are released, puppet-apim,
> puppet-iot and puppet-is can be released for latest product versions.
> Please let us know if you have any concerns.
>
> [1] - https://github.com/wso2/puppet-base
> [2] - https://github.com/wso2/puppet-common
>
> 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
>
>


-- 
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2

LinkedIn : https://lk.linkedin.com/in/rajuu
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Pubudu Gunatilaka]

Hi Devs,

We are currently doing final testing for releasing puppet-base [1] and
puppet-common [2] repositories. Once these repos are released, puppet-apim,
puppet-iot and puppet-is can be released for latest product versions.
Please let us know if you have any concerns.

[1] - https://github.com/wso2/puppet-base
[2] - https://github.com/wso2/puppet-common

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