Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Wed, Aug 24, 2016 at 12:10 AM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I submitted my final evaluation with this link [1]. It contains all the
> information including what's done, what's yet to be done, repos and the
> blogspot.
>

​Great! Thanks Osura! We will go through everything.

Thanks​


>
> [1] https://github.com/osuran/GSoC-16-final-submission/blob/
> master/README.md
>
> Thanks
>
> On Tue, Aug 23, 2016 at 5:11 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Tue, Aug 23, 2016 at 2:48 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Issue #6 was fixed.
>>>
>> great! thanks.
>>
>>>
>>> Thanks,
>>>
>>> On Tue, Aug 23, 2016 at 10:27 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 I'm fixing issue #6 and  almost done. I will fix other issues soon
 after finishing #6.

 Thanks,

 On Tue, Aug 23, 2016 at 7:50 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Several issues reported against the membership scheme is still in open
> state [1]. Other than issue 6, all others are straightforward to fix.
> Please fix those asap.
>
> [1]. https://github.com/osuran/azure-membership-scheme/issues
>
> On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> current status: I'm trying to implement the deploy.sh by trying to
>> invoke puppet to install product configuration at the startup of a puppet
>> installed VM. But still couldn't come up with a presentable outcome.
>>
>> Thanks,
>>
>> On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Thank you
>>>
>>>
>>> On Thursday, August 18, 2016, Imesh Gunaratne 
>>> wrote:
>>>


 On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Imesh,
>
> Yes now I understand that creating VM images for each product
> profile will not going to work out.
>
> Can you please give me a step by step guideline on what I should
> do to achieve this?
>

 ​Please refer [1] and [2].

 [1] https://github.com/wso2/puppet-modules
 [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
 mentation​


 ​Thanks​

 .
>  Thank you,
>
> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
> wrote:
>
>>
>>
>> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne > > wrote:
>>>
>>>
>>> ​There are many spelling mistakes on this file [2], please
>>> review it again.
>>>
>>
>> ​Correction: s/on this file/in this file/g
>>
>> Thanks
>> ​
>>
>>
>>> Overall I see very less attention to detail in this repository
>>> and the membership scheme implementation.
>>>
>>>
 There I mentioned the things that should be kept in mind while
 configuring wso2 AS and did not go in to detail on hot to 
 configure as it
 can be found in the wso2 documentation. Would that be okay?

>>>
>>> ​I don't think this is helpful. Without having detailed steps
>>> users might not be able to do a complete deployment.
>>>
>>> Few questions:
>>>
>>>- How do you create a distributed deployment​
>>>
>>>​of AS ​or any other product (say for an example WSO2 API-M)
>>>with this approach? As I explained earlier creating a VM image 
>>> per product
>>>profile is an unnecessary overhead (time consumption, disk space 
>>> needed,
>>>maintenance, etc).
>>>
>>>- ​What would be the approach of applying​
>>> a patch or do
>>>​ing​
>>>a configuration change in a such deployment?
>>>
>>> ​IMO it is really important to understand the concepts well and
>>> solve problems with the most efficient manner. Otherwise the 
>>> outcome of
>>> this project might not be usable.
>>>
>>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>>
>>> Thanks
>>>
>>>
 user do not need to change anything in template.json, so should
 I explain the parameters in that too?

 in the paramters.json, except for the vm_image parameter, all
 of the parameters are just for the naming of the elements that you 
 find in
 a VM, for an example, the name of 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

I submitted my final evaluation with this link [1]. It contains all the
information including what's done, what's yet to be done, repos and the
blogspot.

[1] https://github.com/osuran/GSoC-16-final-submission/blob/master/README.md

Thanks

On Tue, Aug 23, 2016 at 5:11 PM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> On Tue, Aug 23, 2016 at 2:48 PM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Issue #6 was fixed.
>>
> great! thanks.
>
>>
>> Thanks,
>>
>> On Tue, Aug 23, 2016 at 10:27 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> I'm fixing issue #6 and  almost done. I will fix other issues soon after
>>> finishing #6.
>>>
>>> Thanks,
>>>
>>> On Tue, Aug 23, 2016 at 7:50 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Several issues reported against the membership scheme is still in open
 state [1]. Other than issue 6, all others are straightforward to fix.
 Please fix those asap.

 [1]. https://github.com/osuran/azure-membership-scheme/issues

 On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> current status: I'm trying to implement the deploy.sh by trying to
> invoke puppet to install product configuration at the startup of a puppet
> installed VM. But still couldn't come up with a presentable outcome.
>
> Thanks,
>
> On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake  > wrote:
>
>> Thank you
>>
>>
>> On Thursday, August 18, 2016, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Imesh,

 Yes now I understand that creating VM images for each product
 profile will not going to work out.

 Can you please give me a step by step guideline on what I should do
 to achieve this?

>>>
>>> ​Please refer [1] and [2].
>>>
>>> [1] https://github.com/wso2/puppet-modules
>>> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
>>> mentation​
>>>
>>>
>>> ​Thanks​
>>>
>>> .
  Thank you,

 On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
 wrote:

>
>
> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne 
> wrote:
>>
>>
>> ​There are many spelling mistakes on this file [2], please review
>> it again.
>>
>
> ​Correction: s/on this file/in this file/g
>
> Thanks
> ​
>
>
>> Overall I see very less attention to detail in this repository
>> and the membership scheme implementation.
>>
>>
>>> There I mentioned the things that should be kept in mind while
>>> configuring wso2 AS and did not go in to detail on hot to configure 
>>> as it
>>> can be found in the wso2 documentation. Would that be okay?
>>>
>>
>> ​I don't think this is helpful. Without having detailed steps
>> users might not be able to do a complete deployment.
>>
>> Few questions:
>>
>>- How do you create a distributed deployment​
>>
>>​of AS ​or any other product (say for an example WSO2 API-M)
>>with this approach? As I explained earlier creating a VM image 
>> per product
>>profile is an unnecessary overhead (time consumption, disk space 
>> needed,
>>maintenance, etc).
>>
>>- ​What would be the approach of applying​
>> a patch or do
>>​ing​
>>a configuration change in a such deployment?
>>
>> ​IMO it is really important to understand the concepts well and
>> solve problems with the most efficient manner. Otherwise the outcome 
>> of
>> this project might not be usable.
>>
>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>
>> Thanks
>>
>>
>>> user do not need to change anything in template.json, so should
>>> I explain the parameters in that too?
>>>
>>> in the paramters.json, except for the vm_image parameter, all of
>>> the parameters are just for the naming of the elements that you 
>>> find in a
>>> VM, for an example, the name of the network interface. Therefore I 
>>> have
>>> given instructions on how to set the vm_image parameter.
>>>
>>> current progress: The script which was generated by Azure does
>>> not have the capability to add a custom VM image. I modified it so 
>>> that now
>>> it 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

On Tue, Aug 23, 2016 at 2:48 PM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Issue #6 was fixed.
>
great! thanks.

>
> Thanks,
>
> On Tue, Aug 23, 2016 at 10:27 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> I'm fixing issue #6 and  almost done. I will fix other issues soon after
>> finishing #6.
>>
>> Thanks,
>>
>> On Tue, Aug 23, 2016 at 7:50 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Several issues reported against the membership scheme is still in open
>>> state [1]. Other than issue 6, all others are straightforward to fix.
>>> Please fix those asap.
>>>
>>> [1]. https://github.com/osuran/azure-membership-scheme/issues
>>>
>>> On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 current status: I'm trying to implement the deploy.sh by trying to
 invoke puppet to install product configuration at the startup of a puppet
 installed VM. But still couldn't come up with a presentable outcome.

 Thanks,

 On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake 
 wrote:

> Thank you
>
>
> On Thursday, August 18, 2016, Imesh Gunaratne  wrote:
>
>>
>>
>> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Imesh,
>>>
>>> Yes now I understand that creating VM images for each product
>>> profile will not going to work out.
>>>
>>> Can you please give me a step by step guideline on what I should do
>>> to achieve this?
>>>
>>
>> ​Please refer [1] and [2].
>>
>> [1] https://github.com/wso2/puppet-modules
>> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
>> mentation​
>>
>>
>> ​Thanks​
>>
>> .
>>>  Thank you,
>>>
>>> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
>>> wrote:
>>>


 On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne 
 wrote:
>
>
> ​There are many spelling mistakes on this file [2], please review
> it again.
>

 ​Correction: s/on this file/in this file/g

 Thanks
 ​


> Overall I see very less attention to detail in this repository and
> the membership scheme implementation.
>
>
>> There I mentioned the things that should be kept in mind while
>> configuring wso2 AS and did not go in to detail on hot to configure 
>> as it
>> can be found in the wso2 documentation. Would that be okay?
>>
>
> ​I don't think this is helpful. Without having detailed steps
> users might not be able to do a complete deployment.
>
> Few questions:
>
>- How do you create a distributed deployment​
>
>​of AS ​or any other product (say for an example WSO2 API-M)
>with this approach? As I explained earlier creating a VM image per 
> product
>profile is an unnecessary overhead (time consumption, disk space 
> needed,
>maintenance, etc).
>
>- ​What would be the approach of applying​
> a patch or do
>​ing​
>a configuration change in a such deployment?
>
> ​IMO it is really important to understand the concepts well and
> solve problems with the most efficient manner. Otherwise the outcome 
> of
> this project might not be usable.
>
> [2] https://github.com/osuran/azure-artifacts/issues/2
>
> Thanks
>
>
>> user do not need to change anything in template.json, so should I
>> explain the parameters in that too?
>>
>> in the paramters.json, except for the vm_image parameter, all of
>> the parameters are just for the naming of the elements that you find 
>> in a
>> VM, for an example, the name of the network interface. Therefore I 
>> have
>> given instructions on how to set the vm_image parameter.
>>
>> current progress: The script which was generated by Azure does
>> not have the capability to add a custom VM image. I modified it so 
>> that now
>> it has that capability. Normally when you login to azure from CLI, 
>> it needs
>> web interaction to authenticate. I modified deploy.sh in a way that 
>> it
>> authenticates the user without web interaction, this will be useful 
>> if we
>> run deploy.sh in a minimal version of linux.
>>
>> currently I'm working on adding deployment patterns to deploy.sh
>> and undeploy.sh
>>
>>
>> [1] 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Issue #6 was fixed.

Thanks,

On Tue, Aug 23, 2016 at 10:27 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> I'm fixing issue #6 and  almost done. I will fix other issues soon after
> finishing #6.
>
> Thanks,
>
> On Tue, Aug 23, 2016 at 7:50 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Several issues reported against the membership scheme is still in open
>> state [1]. Other than issue 6, all others are straightforward to fix.
>> Please fix those asap.
>>
>> [1]. https://github.com/osuran/azure-membership-scheme/issues
>>
>> On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> current status: I'm trying to implement the deploy.sh by trying to
>>> invoke puppet to install product configuration at the startup of a puppet
>>> installed VM. But still couldn't come up with a presentable outcome.
>>>
>>> Thanks,
>>>
>>> On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake 
>>> wrote:
>>>
 Thank you


 On Thursday, August 18, 2016, Imesh Gunaratne  wrote:

>
>
> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh,
>>
>> Yes now I understand that creating VM images for each product profile
>> will not going to work out.
>>
>> Can you please give me a step by step guideline on what I should do
>> to achieve this?
>>
>
> ​Please refer [1] and [2].
>
> [1] https://github.com/wso2/puppet-modules
> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
> mentation​
>
>
> ​Thanks​
>
> .
>>  Thank you,
>>
>> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
>> wrote:
>>
>>>
>>>
>>> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne 
>>> wrote:


 ​There are many spelling mistakes on this file [2], please review
 it again.

>>>
>>> ​Correction: s/on this file/in this file/g
>>>
>>> Thanks
>>> ​
>>>
>>>
 Overall I see very less attention to detail in this repository and
 the membership scheme implementation.


> There I mentioned the things that should be kept in mind while
> configuring wso2 AS and did not go in to detail on hot to configure 
> as it
> can be found in the wso2 documentation. Would that be okay?
>

 ​I don't think this is helpful. Without having detailed steps users
 might not be able to do a complete deployment.

 Few questions:

- How do you create a distributed deployment​

​of AS ​or any other product (say for an example WSO2 API-M)
with this approach? As I explained earlier creating a VM image per 
 product
profile is an unnecessary overhead (time consumption, disk space 
 needed,
maintenance, etc).

- ​What would be the approach of applying​
 a patch or do
​ing​
a configuration change in a such deployment?

 ​IMO it is really important to understand the concepts well and
 solve problems with the most efficient manner. Otherwise the outcome of
 this project might not be usable.

 [2] https://github.com/osuran/azure-artifacts/issues/2

 Thanks


> user do not need to change anything in template.json, so should I
> explain the parameters in that too?
>
> in the paramters.json, except for the vm_image parameter, all of
> the parameters are just for the naming of the elements that you find 
> in a
> VM, for an example, the name of the network interface. Therefore I 
> have
> given instructions on how to set the vm_image parameter.
>
> current progress: The script which was generated by Azure does not
> have the capability to add a custom VM image. I modified it so that 
> now it
> has that capability. Normally when you login to azure from CLI, it 
> needs
> web interaction to authenticate. I modified deploy.sh in a way that it
> authenticates the user without web interaction, this will be useful 
> if we
> run deploy.sh in a minimal version of linux.
>
> currently I'm working on adding deployment patterns to deploy.sh
> and undeploy.sh
>
>
> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>
> thank you,
>
> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa <
> isu...@wso2.com> wrote:
>
>> Hi Osura,
>>
>> Can you please send an update on the 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

I'm fixing issue #6 and  almost done. I will fix other issues soon after
finishing #6.

Thanks,

On Tue, Aug 23, 2016 at 7:50 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> Several issues reported against the membership scheme is still in open
> state [1]. Other than issue 6, all others are straightforward to fix.
> Please fix those asap.
>
> [1]. https://github.com/osuran/azure-membership-scheme/issues
>
> On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> current status: I'm trying to implement the deploy.sh by trying to invoke
>> puppet to install product configuration at the startup of a puppet
>> installed VM. But still couldn't come up with a presentable outcome.
>>
>> Thanks,
>>
>> On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake 
>> wrote:
>>
>>> Thank you
>>>
>>>
>>> On Thursday, August 18, 2016, Imesh Gunaratne  wrote:
>>>


 On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake 
 wrote:

> Hi Imesh,
>
> Yes now I understand that creating VM images for each product profile
> will not going to work out.
>
> Can you please give me a step by step guideline on what I should do to
> achieve this?
>

 ​Please refer [1] and [2].

 [1] https://github.com/wso2/puppet-modules
 [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
 mentation​


 ​Thanks​

 .
>  Thank you,
>
> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
> wrote:
>
>>
>>
>> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne 
>> wrote:
>>>
>>>
>>> ​There are many spelling mistakes on this file [2], please review it
>>> again.
>>>
>>
>> ​Correction: s/on this file/in this file/g
>>
>> Thanks
>> ​
>>
>>
>>> Overall I see very less attention to detail in this repository and
>>> the membership scheme implementation.
>>>
>>>
 There I mentioned the things that should be kept in mind while
 configuring wso2 AS and did not go in to detail on hot to configure as 
 it
 can be found in the wso2 documentation. Would that be okay?

>>>
>>> ​I don't think this is helpful. Without having detailed steps users
>>> might not be able to do a complete deployment.
>>>
>>> Few questions:
>>>
>>>- How do you create a distributed deployment​
>>>
>>>​of AS ​or any other product (say for an example WSO2 API-M)
>>>with this approach? As I explained earlier creating a VM image per 
>>> product
>>>profile is an unnecessary overhead (time consumption, disk space 
>>> needed,
>>>maintenance, etc).
>>>
>>>- ​What would be the approach of applying​
>>> a patch or do
>>>​ing​
>>>a configuration change in a such deployment?
>>>
>>> ​IMO it is really important to understand the concepts well and
>>> solve problems with the most efficient manner. Otherwise the outcome of
>>> this project might not be usable.
>>>
>>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>>
>>> Thanks
>>>
>>>
 user do not need to change anything in template.json, so should I
 explain the parameters in that too?

 in the paramters.json, except for the vm_image parameter, all of
 the parameters are just for the naming of the elements that you find 
 in a
 VM, for an example, the name of the network interface. Therefore I have
 given instructions on how to set the vm_image parameter.

 current progress: The script which was generated by Azure does not
 have the capability to add a custom VM image. I modified it so that 
 now it
 has that capability. Normally when you login to azure from CLI, it 
 needs
 web interaction to authenticate. I modified deploy.sh in a way that it
 authenticates the user without web interaction, this will be useful if 
 we
 run deploy.sh in a minimal version of linux.

 currently I'm working on adding deployment patterns to deploy.sh
 and undeploy.sh


 [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as

 thank you,

 On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa <
 isu...@wso2.com> wrote:

> Hi Osura,
>
> Can you please send an update on the current status?
>
> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa <
> isu...@wso2.com> wrote:
>
>> Hi Osura,
>>
>> Few comments regarding the README:
>>
>>1. Need to mention how to configure the VM with the product

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

Several issues reported against the membership scheme is still in open
state [1]. Other than issue 6, all others are straightforward to fix.
Please fix those asap.

[1]. https://github.com/osuran/azure-membership-scheme/issues

On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> current status: I'm trying to implement the deploy.sh by trying to invoke
> puppet to install product configuration at the startup of a puppet
> installed VM. But still couldn't come up with a presentable outcome.
>
> Thanks,
>
> On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake 
> wrote:
>
>> Thank you
>>
>>
>> On Thursday, August 18, 2016, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Imesh,

 Yes now I understand that creating VM images for each product profile
 will not going to work out.

 Can you please give me a step by step guideline on what I should do to
 achieve this?

>>>
>>> ​Please refer [1] and [2].
>>>
>>> [1] https://github.com/wso2/puppet-modules
>>> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
>>> mentation​
>>>
>>>
>>> ​Thanks​
>>>
>>> .
  Thank you,

 On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
 wrote:

>
>
> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne 
> wrote:
>>
>>
>> ​There are many spelling mistakes on this file [2], please review it
>> again.
>>
>
> ​Correction: s/on this file/in this file/g
>
> Thanks
> ​
>
>
>> Overall I see very less attention to detail in this repository and
>> the membership scheme implementation.
>>
>>
>>> There I mentioned the things that should be kept in mind while
>>> configuring wso2 AS and did not go in to detail on hot to configure as 
>>> it
>>> can be found in the wso2 documentation. Would that be okay?
>>>
>>
>> ​I don't think this is helpful. Without having detailed steps users
>> might not be able to do a complete deployment.
>>
>> Few questions:
>>
>>- How do you create a distributed deployment​
>>
>>​of AS ​or any other product (say for an example WSO2 API-M) with
>>this approach? As I explained earlier creating a VM image per product
>>profile is an unnecessary overhead (time consumption, disk space 
>> needed,
>>maintenance, etc).
>>
>>- ​What would be the approach of applying​
>> a patch or do
>>​ing​
>>a configuration change in a such deployment?
>>
>> ​IMO it is really important to understand the concepts well and solve
>> problems with the most efficient manner. Otherwise the outcome of this
>> project might not be usable.
>>
>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>
>> Thanks
>>
>>
>>> user do not need to change anything in template.json, so should I
>>> explain the parameters in that too?
>>>
>>> in the paramters.json, except for the vm_image parameter, all of the
>>> parameters are just for the naming of the elements that you find in a 
>>> VM,
>>> for an example, the name of the network interface. Therefore I have 
>>> given
>>> instructions on how to set the vm_image parameter.
>>>
>>> current progress: The script which was generated by Azure does not
>>> have the capability to add a custom VM image. I modified it so that now 
>>> it
>>> has that capability. Normally when you login to azure from CLI, it needs
>>> web interaction to authenticate. I modified deploy.sh in a way that it
>>> authenticates the user without web interaction, this will be useful if 
>>> we
>>> run deploy.sh in a minimal version of linux.
>>>
>>> currently I'm working on adding deployment patterns to deploy.sh and
>>> undeploy.sh
>>>
>>>
>>> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>>>
>>> thank you,
>>>
>>> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa >> > wrote:
>>>
 Hi Osura,

 Can you please send an update on the current status?

 On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa <
 isu...@wso2.com> wrote:

> Hi Osura,
>
> Few comments regarding the README:
>
>1. Need to mention how to configure the VM with the product
>pack and JDK for Azure
>2. There are lot of parameters in the template and parameters
>json files; please explain what a user needs to change there.
>3. The deploy script should be able to handle both standalone
>and distributed deployment pattern for the product. Refer to K8s 
> 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

current status: I'm trying to implement the deploy.sh by trying to invoke
puppet to install product configuration at the startup of a puppet
installed VM. But still couldn't come up with a presentable outcome.

Thanks,

On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake 
wrote:

> Thank you
>
>
> On Thursday, August 18, 2016, Imesh Gunaratne  wrote:
>
>>
>>
>> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> Yes now I understand that creating VM images for each product profile
>>> will not going to work out.
>>>
>>> Can you please give me a step by step guideline on what I should do to
>>> achieve this?
>>>
>>
>> ​Please refer [1] and [2].
>>
>> [1] https://github.com/wso2/puppet-modules
>> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Documentation
>> ​
>>
>>
>> ​Thanks​
>>
>> .
>>>  Thank you,
>>>
>>> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
>>> wrote:
>>>


 On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne 
 wrote:
>
>
> ​There are many spelling mistakes on this file [2], please review it
> again.
>

 ​Correction: s/on this file/in this file/g

 Thanks
 ​


> Overall I see very less attention to detail in this repository and the
> membership scheme implementation.
>
>
>> There I mentioned the things that should be kept in mind while
>> configuring wso2 AS and did not go in to detail on hot to configure as it
>> can be found in the wso2 documentation. Would that be okay?
>>
>
> ​I don't think this is helpful. Without having detailed steps users
> might not be able to do a complete deployment.
>
> Few questions:
>
>- How do you create a distributed deployment​
>
>​of AS ​or any other product (say for an example WSO2 API-M) with
>this approach? As I explained earlier creating a VM image per product
>profile is an unnecessary overhead (time consumption, disk space 
> needed,
>maintenance, etc).
>
>- ​What would be the approach of applying​
> a patch or do
>​ing​
>a configuration change in a such deployment?
>
> ​IMO it is really important to understand the concepts well and solve
> problems with the most efficient manner. Otherwise the outcome of this
> project might not be usable.
>
> [2] https://github.com/osuran/azure-artifacts/issues/2
>
> Thanks
>
>
>> user do not need to change anything in template.json, so should I
>> explain the parameters in that too?
>>
>> in the paramters.json, except for the vm_image parameter, all of the
>> parameters are just for the naming of the elements that you find in a VM,
>> for an example, the name of the network interface. Therefore I have given
>> instructions on how to set the vm_image parameter.
>>
>> current progress: The script which was generated by Azure does not
>> have the capability to add a custom VM image. I modified it so that now 
>> it
>> has that capability. Normally when you login to azure from CLI, it needs
>> web interaction to authenticate. I modified deploy.sh in a way that it
>> authenticates the user without web interaction, this will be useful if we
>> run deploy.sh in a minimal version of linux.
>>
>> currently I'm working on adding deployment patterns to deploy.sh and
>> undeploy.sh
>>
>>
>> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>>
>> thank you,
>>
>> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Can you please send an update on the current status?
>>>
>>> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa >> > wrote:
>>>
 Hi Osura,

 Few comments regarding the README:

1. Need to mention how to configure the VM with the product
pack and JDK for Azure
2. There are lot of parameters in the template and parameters
json files; please explain what a user needs to change there.
3. The deploy script should be able to handle both standalone
and distributed deployment pattern for the product. Refer to K8s 
 repository
as a reference [1]
4. Highlights the commands that a user needs to issue clearly

 Please note a user should be able to deploy a WSO2 product in Azure
 by following the README. If we provide abstract and incomplete
 instructions, user experience will not be good.

 On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Imesh  /Isuru,
>
> Please 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Thank you

On Thursday, August 18, 2016, Imesh Gunaratne  wrote:

>
>
> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake  > wrote:
>
>> Hi Imesh,
>>
>> Yes now I understand that creating VM images for each product profile
>> will not going to work out.
>>
>> Can you please give me a step by step guideline on what I should do to
>> achieve this?
>>
>
> ​Please refer [1] and [2].
>
> [1] https://github.com/wso2/puppet-modules
> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Documentation​
>
>
> ​Thanks​
>
> .
>>  Thank you,
>>
>> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne > > wrote:
>>
>>>
>>>
>>> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne >> > wrote:


 ​There are many spelling mistakes on this file [2], please review it
 again.

>>>
>>> ​Correction: s/on this file/in this file/g
>>>
>>> Thanks
>>> ​
>>>
>>>
 Overall I see very less attention to detail in this repository and the
 membership scheme implementation.


> There I mentioned the things that should be kept in mind while
> configuring wso2 AS and did not go in to detail on hot to configure as it
> can be found in the wso2 documentation. Would that be okay?
>

 ​I don't think this is helpful. Without having detailed steps users
 might not be able to do a complete deployment.

 Few questions:

- How do you create a distributed deployment​

​of AS ​or any other product (say for an example WSO2 API-M) with
this approach? As I explained earlier creating a VM image per product
profile is an unnecessary overhead (time consumption, disk space needed,
maintenance, etc).

- ​What would be the approach of applying​
 a patch or do
​ing​
a configuration change in a such deployment?

 ​IMO it is really important to understand the concepts well and solve
 problems with the most efficient manner. Otherwise the outcome of this
 project might not be usable.

 [2] https://github.com/osuran/azure-artifacts/issues/2

 Thanks


> user do not need to change anything in template.json, so should I
> explain the parameters in that too?
>
> in the paramters.json, except for the vm_image parameter, all of the
> parameters are just for the naming of the elements that you find in a VM,
> for an example, the name of the network interface. Therefore I have given
> instructions on how to set the vm_image parameter.
>
> current progress: The script which was generated by Azure does not
> have the capability to add a custom VM image. I modified it so that now it
> has that capability. Normally when you login to azure from CLI, it needs
> web interaction to authenticate. I modified deploy.sh in a way that it
> authenticates the user without web interaction, this will be useful if we
> run deploy.sh in a minimal version of linux.
>
> currently I'm working on adding deployment patterns to deploy.sh and
> undeploy.sh
>
>
> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>
> thank you,
>
> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa  > wrote:
>
>> Hi Osura,
>>
>> Can you please send an update on the current status?
>>
>> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa > > wrote:
>>
>>> Hi Osura,
>>>
>>> Few comments regarding the README:
>>>
>>>1. Need to mention how to configure the VM with the product pack
>>>and JDK for Azure
>>>2. There are lot of parameters in the template and parameters
>>>json files; please explain what a user needs to change there.
>>>3. The deploy script should be able to handle both standalone
>>>and distributed deployment pattern for the product. Refer to K8s 
>>> repository
>>>as a reference [1]
>>>4. Highlights the commands that a user needs to issue clearly
>>>
>>> Please note a user should be able to deploy a WSO2 product in Azure
>>> by following the README. If we provide abstract and incomplete
>>> instructions, user experience will not be good.
>>>
>>> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake <
>>> osura...@gmail.com
>>> > wrote:
>>>
 Hi Imesh  /Isuru,

 Please accept my apologies for the delayed response.

 There is a MySQL instance in the Azure marketplace, we can
 straightaway deploy that. It's a 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake 
wrote:

> Hi Imesh,
>
> Yes now I understand that creating VM images for each product profile will
> not going to work out.
>
> Can you please give me a step by step guideline on what I should do to
> achieve this?
>

​Please refer [1] and [2].

[1] https://github.com/wso2/puppet-modules
[2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Documentation​


​Thanks​

.
>  Thank you,
>
> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne  wrote:
>>>
>>>
>>> ​There are many spelling mistakes on this file [2], please review it
>>> again.
>>>
>>
>> ​Correction: s/on this file/in this file/g
>>
>> Thanks
>> ​
>>
>>
>>> Overall I see very less attention to detail in this repository and the
>>> membership scheme implementation.
>>>
>>>
 There I mentioned the things that should be kept in mind while
 configuring wso2 AS and did not go in to detail on hot to configure as it
 can be found in the wso2 documentation. Would that be okay?

>>>
>>> ​I don't think this is helpful. Without having detailed steps users
>>> might not be able to do a complete deployment.
>>>
>>> Few questions:
>>>
>>>- How do you create a distributed deployment​
>>>
>>>​of AS ​or any other product (say for an example WSO2 API-M) with
>>>this approach? As I explained earlier creating a VM image per product
>>>profile is an unnecessary overhead (time consumption, disk space needed,
>>>maintenance, etc).
>>>
>>>- ​What would be the approach of applying​
>>> a patch or do
>>>​ing​
>>>a configuration change in a such deployment?
>>>
>>> ​IMO it is really important to understand the concepts well and solve
>>> problems with the most efficient manner. Otherwise the outcome of this
>>> project might not be usable.
>>>
>>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>>
>>> Thanks
>>>
>>>
 user do not need to change anything in template.json, so should I
 explain the parameters in that too?

 in the paramters.json, except for the vm_image parameter, all of the
 parameters are just for the naming of the elements that you find in a VM,
 for an example, the name of the network interface. Therefore I have given
 instructions on how to set the vm_image parameter.

 current progress: The script which was generated by Azure does not have
 the capability to add a custom VM image. I modified it so that now it has
 that capability. Normally when you login to azure from CLI, it needs web
 interaction to authenticate. I modified deploy.sh in a way that it
 authenticates the user without web interaction, this will be useful if we
 run deploy.sh in a minimal version of linux.

 currently I'm working on adding deployment patterns to deploy.sh and
 undeploy.sh


 [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as

 thank you,

 On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Can you please send an update on the current status?
>
> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Few comments regarding the README:
>>
>>1. Need to mention how to configure the VM with the product pack
>>and JDK for Azure
>>2. There are lot of parameters in the template and parameters
>>json files; please explain what a user needs to change there.
>>3. The deploy script should be able to handle both standalone and
>>distributed deployment pattern for the product. Refer to K8s 
>> repository as
>>a reference [1]
>>4. Highlights the commands that a user needs to issue clearly
>>
>> Please note a user should be able to deploy a WSO2 product in Azure
>> by following the README. If we provide abstract and incomplete
>> instructions, user experience will not be good.
>>
>> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake > > wrote:
>>
>>> Hi Imesh  /Isuru,
>>>
>>> Please accept my apologies for the delayed response.
>>>
>>> There is a MySQL instance in the Azure marketplace, we can
>>> straightaway deploy that. It's a Ubuntu 16.04.1 LTS with MySQL 
>>> installed. I
>>> think it's better to use it as there won't be licensing issues with it.
>>>
>>> Please find the updated readme file in [1] which includes steps on
>>> how to deploy WSO2 AS in Azure.
>>>
>>
>>> About the undeploy.sh, should it remove the VM entirely or just the
>>> WSO2 AS instance?
>>>
>> Ideally we should be able to re-use the VM, so IMHO removing only the
>> instance is ok.
>>
>> [1]. 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

Yes now I understand that creating VM images for each product profile will
not going to work out.

Can you please give me a step by step guideline on what I should do to
achieve this?
.
 Thank you,

On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne  wrote:

>
>
> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne  wrote:
>>
>>
>> ​There are many spelling mistakes on this file [2], please review it
>> again.
>>
>
> ​Correction: s/on this file/in this file/g
>
> Thanks
> ​
>
>
>> Overall I see very less attention to detail in this repository and the
>> membership scheme implementation.
>>
>>
>>> There I mentioned the things that should be kept in mind while
>>> configuring wso2 AS and did not go in to detail on hot to configure as it
>>> can be found in the wso2 documentation. Would that be okay?
>>>
>>
>> ​I don't think this is helpful. Without having detailed steps users might
>> not be able to do a complete deployment.
>>
>> Few questions:
>>
>>- How do you create a distributed deployment​
>>
>>​of AS ​or any other product (say for an example WSO2 API-M) with
>>this approach? As I explained earlier creating a VM image per product
>>profile is an unnecessary overhead (time consumption, disk space needed,
>>maintenance, etc).
>>
>>- ​What would be the approach of applying​
>> a patch or do
>>​ing​
>>a configuration change in a such deployment?
>>
>> ​IMO it is really important to understand the concepts well and solve
>> problems with the most efficient manner. Otherwise the outcome of this
>> project might not be usable.
>>
>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>
>> Thanks
>>
>>
>>> user do not need to change anything in template.json, so should I
>>> explain the parameters in that too?
>>>
>>> in the paramters.json, except for the vm_image parameter, all of the
>>> parameters are just for the naming of the elements that you find in a VM,
>>> for an example, the name of the network interface. Therefore I have given
>>> instructions on how to set the vm_image parameter.
>>>
>>> current progress: The script which was generated by Azure does not have
>>> the capability to add a custom VM image. I modified it so that now it has
>>> that capability. Normally when you login to azure from CLI, it needs web
>>> interaction to authenticate. I modified deploy.sh in a way that it
>>> authenticates the user without web interaction, this will be useful if we
>>> run deploy.sh in a minimal version of linux.
>>>
>>> currently I'm working on adding deployment patterns to deploy.sh and
>>> undeploy.sh
>>>
>>>
>>> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>>>
>>> thank you,
>>>
>>> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Can you please send an update on the current status?

 On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Few comments regarding the README:
>
>1. Need to mention how to configure the VM with the product pack
>and JDK for Azure
>2. There are lot of parameters in the template and parameters json
>files; please explain what a user needs to change there.
>3. The deploy script should be able to handle both standalone and
>distributed deployment pattern for the product. Refer to K8s 
> repository as
>a reference [1]
>4. Highlights the commands that a user needs to issue clearly
>
> Please note a user should be able to deploy a WSO2 product in Azure by
> following the README. If we provide abstract and incomplete instructions,
> user experience will not be good.
>
> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh  /Isuru,
>>
>> Please accept my apologies for the delayed response.
>>
>> There is a MySQL instance in the Azure marketplace, we can
>> straightaway deploy that. It's a Ubuntu 16.04.1 LTS with MySQL 
>> installed. I
>> think it's better to use it as there won't be licensing issues with it.
>>
>> Please find the updated readme file in [1] which includes steps on
>> how to deploy WSO2 AS in Azure.
>>
>
>> About the undeploy.sh, should it remove the VM entirely or just the
>> WSO2 AS instance?
>>
> Ideally we should be able to re-use the VM, so IMHO removing only the
> instance is ok.
>
> [1]. https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as
>
>>
>> [1] https://github.com/osuran/azure-artifacts
>>
>> Thank you,
>>
>> On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> I see that you have updated the repo [1] with a deploy script for
>>> wso2as. Additionally we would need an undeploy script as well. What 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne  wrote:
>
>
> ​There are many spelling mistakes on this file [2], please review it
> again.
>

​Correction: s/on this file/in this file/g

Thanks
​


> Overall I see very less attention to detail in this repository and the
> membership scheme implementation.
>
>
>> There I mentioned the things that should be kept in mind while
>> configuring wso2 AS and did not go in to detail on hot to configure as it
>> can be found in the wso2 documentation. Would that be okay?
>>
>
> ​I don't think this is helpful. Without having detailed steps users might
> not be able to do a complete deployment.
>
> Few questions:
>
>- How do you create a distributed deployment​
>
>​of AS ​or any other product (say for an example WSO2 API-M) with this
>approach? As I explained earlier creating a VM image per product profile is
>an unnecessary overhead (time consumption, disk space needed, maintenance,
>etc).
>
>- ​What would be the approach of applying​
> a patch or do
>​ing​
>a configuration change in a such deployment?
>
> ​IMO it is really important to understand the concepts well and solve
> problems with the most efficient manner. Otherwise the outcome of this
> project might not be usable.
>
> [2] https://github.com/osuran/azure-artifacts/issues/2
>
> Thanks
>
>
>> user do not need to change anything in template.json, so should I explain
>> the parameters in that too?
>>
>> in the paramters.json, except for the vm_image parameter, all of the
>> parameters are just for the naming of the elements that you find in a VM,
>> for an example, the name of the network interface. Therefore I have given
>> instructions on how to set the vm_image parameter.
>>
>> current progress: The script which was generated by Azure does not have
>> the capability to add a custom VM image. I modified it so that now it has
>> that capability. Normally when you login to azure from CLI, it needs web
>> interaction to authenticate. I modified deploy.sh in a way that it
>> authenticates the user without web interaction, this will be useful if we
>> run deploy.sh in a minimal version of linux.
>>
>> currently I'm working on adding deployment patterns to deploy.sh and
>> undeploy.sh
>>
>>
>> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>>
>> thank you,
>>
>> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Can you please send an update on the current status?
>>>
>>> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Few comments regarding the README:

1. Need to mention how to configure the VM with the product pack
and JDK for Azure
2. There are lot of parameters in the template and parameters json
files; please explain what a user needs to change there.
3. The deploy script should be able to handle both standalone and
distributed deployment pattern for the product. Refer to K8s repository 
 as
a reference [1]
4. Highlights the commands that a user needs to issue clearly

 Please note a user should be able to deploy a WSO2 product in Azure by
 following the README. If we provide abstract and incomplete instructions,
 user experience will not be good.

 On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake 
 wrote:

> Hi Imesh  /Isuru,
>
> Please accept my apologies for the delayed response.
>
> There is a MySQL instance in the Azure marketplace, we can
> straightaway deploy that. It's a Ubuntu 16.04.1 LTS with MySQL installed. 
> I
> think it's better to use it as there won't be licensing issues with it.
>
> Please find the updated readme file in [1] which includes steps on how
> to deploy WSO2 AS in Azure.
>

> About the undeploy.sh, should it remove the VM entirely or just the
> WSO2 AS instance?
>
 Ideally we should be able to re-use the VM, so IMHO removing only the
 instance is ok.

 [1]. https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as

>
> [1] https://github.com/osuran/azure-artifacts
>
> Thank you,
>
> On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> I see that you have updated the repo [1] with a deploy script for
>> wso2as. Additionally we would need an undeploy script as well. What are 
>> the
>> steps that I need to follow to deploy WSO2 AS on Azure? Can you please
>> provide me a documentation link?
>>
>> [1]. https://github.com/osuran/azure-artifacts
>>
>> On Thu, Aug 11, 2016 at 10:22 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Can you give an update on the latest status? I checked the github
>>> repositories under 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

Hi Osura,

On Tue, Aug 16, 2016 at 11:32 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> I have updated the readme file [1], please have a look.
>

​There are many spelling mistakes on this file [2], please review it again.
Overall I see very less attention to detail in this repository and the
membership scheme implementation.


> There I mentioned the things that should be kept in mind while configuring
> wso2 AS and did not go in to detail on hot to configure as it can be found
> in the wso2 documentation. Would that be okay?
>

​I don't think this is helpful. Without having detailed steps users might
not be able to do a complete deployment.

Few questions:

   - How do you create a distributed deployment​

   ​of AS ​or any other product (say for an example WSO2 API-M) with this
   approach? As I explained earlier creating a VM image per product profile is
   an unnecessary overhead (time consumption, disk space needed, maintenance,
   etc).

   - ​What would be the approach of applying​
a patch or do
   ​ing​
   a configuration change in a such deployment?

​IMO it is really important to understand the concepts well and solve
problems with the most efficient manner. Otherwise the outcome of this
project might not be usable.

[2] https://github.com/osuran/azure-artifacts/issues/2

Thanks


> user do not need to change anything in template.json, so should I explain
> the parameters in that too?
>
> in the paramters.json, except for the vm_image parameter, all of the
> parameters are just for the naming of the elements that you find in a VM,
> for an example, the name of the network interface. Therefore I have given
> instructions on how to set the vm_image parameter.
>
> current progress: The script which was generated by Azure does not have
> the capability to add a custom VM image. I modified it so that now it has
> that capability. Normally when you login to azure from CLI, it needs web
> interaction to authenticate. I modified deploy.sh in a way that it
> authenticates the user without web interaction, this will be useful if we
> run deploy.sh in a minimal version of linux.
>
> currently I'm working on adding deployment patterns to deploy.sh and
> undeploy.sh
>
>
> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>
> thank you,
>
> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you please send an update on the current status?
>>
>> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Few comments regarding the README:
>>>
>>>1. Need to mention how to configure the VM with the product pack and
>>>JDK for Azure
>>>2. There are lot of parameters in the template and parameters json
>>>files; please explain what a user needs to change there.
>>>3. The deploy script should be able to handle both standalone and
>>>distributed deployment pattern for the product. Refer to K8s repository 
>>> as
>>>a reference [1]
>>>4. Highlights the commands that a user needs to issue clearly
>>>
>>> Please note a user should be able to deploy a WSO2 product in Azure by
>>> following the README. If we provide abstract and incomplete instructions,
>>> user experience will not be good.
>>>
>>> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Imesh  /Isuru,

 Please accept my apologies for the delayed response.

 There is a MySQL instance in the Azure marketplace, we can straightaway
 deploy that. It's a Ubuntu 16.04.1 LTS with MySQL installed. I think it's
 better to use it as there won't be licensing issues with it.

 Please find the updated readme file in [1] which includes steps on how
 to deploy WSO2 AS in Azure.

>>>
 About the undeploy.sh, should it remove the VM entirely or just the
 WSO2 AS instance?

>>> Ideally we should be able to re-use the VM, so IMHO removing only the
>>> instance is ok.
>>>
>>> [1]. https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as
>>>

 [1] https://github.com/osuran/azure-artifacts

 Thank you,

 On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> I see that you have updated the repo [1] with a deploy script for
> wso2as. Additionally we would need an undeploy script as well. What are 
> the
> steps that I need to follow to deploy WSO2 AS on Azure? Can you please
> provide me a documentation link?
>
> [1]. https://github.com/osuran/azure-artifacts
>
> On Thu, Aug 11, 2016 at 10:22 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you give an update on the latest status? I checked the github
>> repositories under your account, but still can find only the membership
>> scheme and a couple of templates. Did you add the scripts to
>> 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

HI Osura,

For trying out purposes, can you provide the links for the VMs you created?

On Tue, Aug 16, 2016 at 11:32 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> I have updated the readme file [1], please have a look.
>
> There I mentioned the things that should be kept in mind while configuring
> wso2 AS and did not go in to detail on hot to configure as it can be found
> in the wso2 documentation. Would that be okay?
>
> user do not need to change anything in template.json, so should I explain
> the parameters in that too?
>
> in the paramters.json, except for the vm_image parameter, all of the
> parameters are just for the naming of the elements that you find in a VM,
> for an example, the name of the network interface. Therefore I have given
> instructions on how to set the vm_image parameter.
>
> current progress: The script which was generated by Azure does not have
> the capability to add a custom VM image. I modified it so that now it has
> that capability. Normally when you login to azure from CLI, it needs web
> interaction to authenticate. I modified deploy.sh in a way that it
> authenticates the user without web interaction, this will be useful if we
> run deploy.sh in a minimal version of linux.
>
> currently I'm working on adding deployment patterns to deploy.sh and
> undeploy.sh
>
>
> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>
> thank you,
>
> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you please send an update on the current status?
>>
>> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Few comments regarding the README:
>>>
>>>1. Need to mention how to configure the VM with the product pack and
>>>JDK for Azure
>>>2. There are lot of parameters in the template and parameters json
>>>files; please explain what a user needs to change there.
>>>3. The deploy script should be able to handle both standalone and
>>>distributed deployment pattern for the product. Refer to K8s repository 
>>> as
>>>a reference [1]
>>>4. Highlights the commands that a user needs to issue clearly
>>>
>>> Please note a user should be able to deploy a WSO2 product in Azure by
>>> following the README. If we provide abstract and incomplete instructions,
>>> user experience will not be good.
>>>
>>> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Imesh  /Isuru,

 Please accept my apologies for the delayed response.

 There is a MySQL instance in the Azure marketplace, we can straightaway
 deploy that. It's a Ubuntu 16.04.1 LTS with MySQL installed. I think it's
 better to use it as there won't be licensing issues with it.

 Please find the updated readme file in [1] which includes steps on how
 to deploy WSO2 AS in Azure.

>>>
 About the undeploy.sh, should it remove the VM entirely or just the
 WSO2 AS instance?

>>> Ideally we should be able to re-use the VM, so IMHO removing only the
>>> instance is ok.
>>>
>>> [1]. https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as
>>>

 [1] https://github.com/osuran/azure-artifacts

 Thank you,

 On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> I see that you have updated the repo [1] with a deploy script for
> wso2as. Additionally we would need an undeploy script as well. What are 
> the
> steps that I need to follow to deploy WSO2 AS on Azure? Can you please
> provide me a documentation link?
>
> [1]. https://github.com/osuran/azure-artifacts
>
> On Thu, Aug 11, 2016 at 10:22 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you give an update on the latest status? I checked the github
>> repositories under your account, but still can find only the membership
>> scheme and a couple of templates. Did you add the scripts to
>> deploy/undeploy the products? As we saw, its just a matter of copy 
>> pasting
>> from the Azure management portal since the deployment script is auto
>> generated.
>>
>> On Fri, Aug 5, 2016 at 10:56 AM, Imesh Gunaratne 
>> wrote:
>>
>>> On Fri, Aug 5, 2016 at 9:07 AM, Osura Rathnayake >> > wrote:
>>>
 Hi Mentors,

 This is the progress so far.

 I have created a template, using which you can deploy 3 VMs,
 manager node, worker node and a DB. This template can be used in any 
 azure
 subscription, you only have to do a template deployment using that
 template. You have to pass the relevant VM images at the time of 
 deployment
 so for that I have created 5 VM images,

1. WSO2 AS as manager

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

I have updated the readme file [1], please have a look.

There I mentioned the things that should be kept in mind while configuring
wso2 AS and did not go in to detail on hot to configure as it can be found
in the wso2 documentation. Would that be okay?

user do not need to change anything in template.json, so should I explain
the parameters in that too?

in the paramters.json, except for the vm_image parameter, all of the
parameters are just for the naming of the elements that you find in a VM,
for an example, the name of the network interface. Therefore I have given
instructions on how to set the vm_image parameter.

current progress: The script which was generated by Azure does not have the
capability to add a custom VM image. I modified it so that now it has that
capability. Normally when you login to azure from CLI, it needs web
interaction to authenticate. I modified deploy.sh in a way that it
authenticates the user without web interaction, this will be useful if we
run deploy.sh in a minimal version of linux.

currently I'm working on adding deployment patterns to deploy.sh and
undeploy.sh


[1] https://github.com/osuran/azure-artifacts/tree/master/wso2as

thank you,

On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> Can you please send an update on the current status?
>
> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Few comments regarding the README:
>>
>>1. Need to mention how to configure the VM with the product pack and
>>JDK for Azure
>>2. There are lot of parameters in the template and parameters json
>>files; please explain what a user needs to change there.
>>3. The deploy script should be able to handle both standalone and
>>distributed deployment pattern for the product. Refer to K8s repository as
>>a reference [1]
>>4. Highlights the commands that a user needs to issue clearly
>>
>> Please note a user should be able to deploy a WSO2 product in Azure by
>> following the README. If we provide abstract and incomplete instructions,
>> user experience will not be good.
>>
>> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Imesh  /Isuru,
>>>
>>> Please accept my apologies for the delayed response.
>>>
>>> There is a MySQL instance in the Azure marketplace, we can straightaway
>>> deploy that. It's a Ubuntu 16.04.1 LTS with MySQL installed. I think it's
>>> better to use it as there won't be licensing issues with it.
>>>
>>> Please find the updated readme file in [1] which includes steps on how
>>> to deploy WSO2 AS in Azure.
>>>
>>
>>> About the undeploy.sh, should it remove the VM entirely or just the WSO2
>>> AS instance?
>>>
>> Ideally we should be able to re-use the VM, so IMHO removing only the
>> instance is ok.
>>
>> [1]. https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as
>>
>>>
>>> [1] https://github.com/osuran/azure-artifacts
>>>
>>> Thank you,
>>>
>>> On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 I see that you have updated the repo [1] with a deploy script for
 wso2as. Additionally we would need an undeploy script as well. What are the
 steps that I need to follow to deploy WSO2 AS on Azure? Can you please
 provide me a documentation link?

 [1]. https://github.com/osuran/azure-artifacts

 On Thu, Aug 11, 2016 at 10:22 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Can you give an update on the latest status? I checked the github
> repositories under your account, but still can find only the membership
> scheme and a couple of templates. Did you add the scripts to
> deploy/undeploy the products? As we saw, its just a matter of copy pasting
> from the Azure management portal since the deployment script is auto
> generated.
>
> On Fri, Aug 5, 2016 at 10:56 AM, Imesh Gunaratne 
> wrote:
>
>> On Fri, Aug 5, 2016 at 9:07 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> This is the progress so far.
>>>
>>> I have created a template, using which you can deploy 3 VMs, manager
>>> node, worker node and a DB. This template can be used in any azure
>>> subscription, you only have to do a template deployment using that
>>> template. You have to pass the relevant VM images at the time of 
>>> deployment
>>> so for that I have created 5 VM images,
>>>
>>>1. WSO2 AS as manager
>>>2. WSO2 AS as worker
>>>3. WSO2 ESB as manager
>>>4. WSO2 ESB as worker
>>>5. DB
>>>
>>> ​Are you running a database server on a VM? On Azure it would be
>> better to use their database service for creating databases otherwise
>> managing databases on VMs would be difficult.
>>
>> These VM images are 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

Can you please send an update on the current status?

On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> Few comments regarding the README:
>
>1. Need to mention how to configure the VM with the product pack and
>JDK for Azure
>2. There are lot of parameters in the template and parameters json
>files; please explain what a user needs to change there.
>3. The deploy script should be able to handle both standalone and
>distributed deployment pattern for the product. Refer to K8s repository as
>a reference [1]
>4. Highlights the commands that a user needs to issue clearly
>
> Please note a user should be able to deploy a WSO2 product in Azure by
> following the README. If we provide abstract and incomplete instructions,
> user experience will not be good.
>
> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh  /Isuru,
>>
>> Please accept my apologies for the delayed response.
>>
>> There is a MySQL instance in the Azure marketplace, we can straightaway
>> deploy that. It's a Ubuntu 16.04.1 LTS with MySQL installed. I think it's
>> better to use it as there won't be licensing issues with it.
>>
>> Please find the updated readme file in [1] which includes steps on how to
>> deploy WSO2 AS in Azure.
>>
>
>> About the undeploy.sh, should it remove the VM entirely or just the WSO2
>> AS instance?
>>
> Ideally we should be able to re-use the VM, so IMHO removing only the
> instance is ok.
>
> [1]. https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as
>
>>
>> [1] https://github.com/osuran/azure-artifacts
>>
>> Thank you,
>>
>> On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> I see that you have updated the repo [1] with a deploy script for
>>> wso2as. Additionally we would need an undeploy script as well. What are the
>>> steps that I need to follow to deploy WSO2 AS on Azure? Can you please
>>> provide me a documentation link?
>>>
>>> [1]. https://github.com/osuran/azure-artifacts
>>>
>>> On Thu, Aug 11, 2016 at 10:22 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Can you give an update on the latest status? I checked the github
 repositories under your account, but still can find only the membership
 scheme and a couple of templates. Did you add the scripts to
 deploy/undeploy the products? As we saw, its just a matter of copy pasting
 from the Azure management portal since the deployment script is auto
 generated.

 On Fri, Aug 5, 2016 at 10:56 AM, Imesh Gunaratne 
 wrote:

> On Fri, Aug 5, 2016 at 9:07 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> This is the progress so far.
>>
>> I have created a template, using which you can deploy 3 VMs, manager
>> node, worker node and a DB. This template can be used in any azure
>> subscription, you only have to do a template deployment using that
>> template. You have to pass the relevant VM images at the time of 
>> deployment
>> so for that I have created 5 VM images,
>>
>>1. WSO2 AS as manager
>>2. WSO2 AS as worker
>>3. WSO2 ESB as manager
>>4. WSO2 ESB as worker
>>5. DB
>>
>> ​Are you running a database server on a VM? On Azure it would be
> better to use their database service for creating databases otherwise
> managing databases on VMs would be difficult.
>
> These VM images are in my azure storage account so that prior to the
>> deployment, they have to be copied to the storage account of the 
>> customer.
>> Each VM image is approx 30 GB in size. Once you copied the images, you 
>> can
>> start the deployment using the template.
>> ​
>>
>
> ​Ideally we should have a configuration management system in place to
> manage this. It's an overhead to work with multiple VM images.
> ​
> ​
>
> 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
>
>
>


 --
 Thanks and Regards,

 Isuru H.
 +94 716 358 048* *



>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* *
>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>> Osura Rathnayake
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
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] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

Few comments regarding the README:

   1. Need to mention how to configure the VM with the product pack and JDK
   for Azure
   2. There are lot of parameters in the template and parameters json
   files; please explain what a user needs to change there.
   3. The deploy script should be able to handle both standalone and
   distributed deployment pattern for the product. Refer to K8s repository as
   a reference [1]
   4. Highlights the commands that a user needs to issue clearly

Please note a user should be able to deploy a WSO2 product in Azure by
following the README. If we provide abstract and incomplete instructions,
user experience will not be good.

On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake 
wrote:

> Hi Imesh  /Isuru,
>
> Please accept my apologies for the delayed response.
>
> There is a MySQL instance in the Azure marketplace, we can straightaway
> deploy that. It's a Ubuntu 16.04.1 LTS with MySQL installed. I think it's
> better to use it as there won't be licensing issues with it.
>
> Please find the updated readme file in [1] which includes steps on how to
> deploy WSO2 AS in Azure.
>

> About the undeploy.sh, should it remove the VM entirely or just the WSO2
> AS instance?
>
Ideally we should be able to re-use the VM, so IMHO removing only the
instance is ok.

[1]. https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as

>
> [1] https://github.com/osuran/azure-artifacts
>
> Thank you,
>
> On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> I see that you have updated the repo [1] with a deploy script for wso2as.
>> Additionally we would need an undeploy script as well. What are the steps
>> that I need to follow to deploy WSO2 AS on Azure? Can you please provide me
>> a documentation link?
>>
>> [1]. https://github.com/osuran/azure-artifacts
>>
>> On Thu, Aug 11, 2016 at 10:22 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Can you give an update on the latest status? I checked the github
>>> repositories under your account, but still can find only the membership
>>> scheme and a couple of templates. Did you add the scripts to
>>> deploy/undeploy the products? As we saw, its just a matter of copy pasting
>>> from the Azure management portal since the deployment script is auto
>>> generated.
>>>
>>> On Fri, Aug 5, 2016 at 10:56 AM, Imesh Gunaratne  wrote:
>>>
 On Fri, Aug 5, 2016 at 9:07 AM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> This is the progress so far.
>
> I have created a template, using which you can deploy 3 VMs, manager
> node, worker node and a DB. This template can be used in any azure
> subscription, you only have to do a template deployment using that
> template. You have to pass the relevant VM images at the time of 
> deployment
> so for that I have created 5 VM images,
>
>1. WSO2 AS as manager
>2. WSO2 AS as worker
>3. WSO2 ESB as manager
>4. WSO2 ESB as worker
>5. DB
>
> ​Are you running a database server on a VM? On Azure it would be
 better to use their database service for creating databases otherwise
 managing databases on VMs would be difficult.

 These VM images are in my azure storage account so that prior to the
> deployment, they have to be copied to the storage account of the customer.
> Each VM image is approx 30 GB in size. Once you copied the images, you can
> start the deployment using the template.
> ​
>

 ​Ideally we should have a configuration management system in place to
 manage this. It's an overhead to work with multiple VM images.
 ​
 ​

 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



>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* *
>>>
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> Regards,
> Osura Rathnayake
>



-- 
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] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh  /Isuru,

Please accept my apologies for the delayed response.

There is a MySQL instance in the Azure marketplace, we can straightaway
deploy that. It's a Ubuntu 16.04.1 LTS with MySQL installed. I think it's
better to use it as there won't be licensing issues with it.

Please find the updated readme file in [1] which includes steps on how to
deploy WSO2 AS in Azure.

About the undeploy.sh, should it remove the VM entirely or just the WSO2 AS
instance?

[1] https://github.com/osuran/azure-artifacts

Thank you,

On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> I see that you have updated the repo [1] with a deploy script for wso2as.
> Additionally we would need an undeploy script as well. What are the steps
> that I need to follow to deploy WSO2 AS on Azure? Can you please provide me
> a documentation link?
>
> [1]. https://github.com/osuran/azure-artifacts
>
> On Thu, Aug 11, 2016 at 10:22 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you give an update on the latest status? I checked the github
>> repositories under your account, but still can find only the membership
>> scheme and a couple of templates. Did you add the scripts to
>> deploy/undeploy the products? As we saw, its just a matter of copy pasting
>> from the Azure management portal since the deployment script is auto
>> generated.
>>
>> On Fri, Aug 5, 2016 at 10:56 AM, Imesh Gunaratne  wrote:
>>
>>> On Fri, Aug 5, 2016 at 9:07 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 This is the progress so far.

 I have created a template, using which you can deploy 3 VMs, manager
 node, worker node and a DB. This template can be used in any azure
 subscription, you only have to do a template deployment using that
 template. You have to pass the relevant VM images at the time of deployment
 so for that I have created 5 VM images,

1. WSO2 AS as manager
2. WSO2 AS as worker
3. WSO2 ESB as manager
4. WSO2 ESB as worker
5. DB

 ​Are you running a database server on a VM? On Azure it would be better
>>> to use their database service for creating databases otherwise managing
>>> databases on VMs would be difficult.
>>>
>>> These VM images are in my azure storage account so that prior to the
 deployment, they have to be copied to the storage account of the customer.
 Each VM image is approx 30 GB in size. Once you copied the images, you can
 start the deployment using the template.
 ​

>>>
>>> ​Ideally we should have a configuration management system in place to
>>> manage this. It's an overhead to work with multiple VM images.
>>> ​
>>> ​
>>>
>>> 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
>>>
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
Regards,
Osura Rathnayake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

I see that you have updated the repo [1] with a deploy script for wso2as.
Additionally we would need an undeploy script as well. What are the steps
that I need to follow to deploy WSO2 AS on Azure? Can you please provide me
a documentation link?

[1]. https://github.com/osuran/azure-artifacts

On Thu, Aug 11, 2016 at 10:22 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> Can you give an update on the latest status? I checked the github
> repositories under your account, but still can find only the membership
> scheme and a couple of templates. Did you add the scripts to
> deploy/undeploy the products? As we saw, its just a matter of copy pasting
> from the Azure management portal since the deployment script is auto
> generated.
>
> On Fri, Aug 5, 2016 at 10:56 AM, Imesh Gunaratne  wrote:
>
>> On Fri, Aug 5, 2016 at 9:07 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> This is the progress so far.
>>>
>>> I have created a template, using which you can deploy 3 VMs, manager
>>> node, worker node and a DB. This template can be used in any azure
>>> subscription, you only have to do a template deployment using that
>>> template. You have to pass the relevant VM images at the time of deployment
>>> so for that I have created 5 VM images,
>>>
>>>1. WSO2 AS as manager
>>>2. WSO2 AS as worker
>>>3. WSO2 ESB as manager
>>>4. WSO2 ESB as worker
>>>5. DB
>>>
>>> ​Are you running a database server on a VM? On Azure it would be better
>> to use their database service for creating databases otherwise managing
>> databases on VMs would be difficult.
>>
>> These VM images are in my azure storage account so that prior to the
>>> deployment, they have to be copied to the storage account of the customer.
>>> Each VM image is approx 30 GB in size. Once you copied the images, you can
>>> start the deployment using the template.
>>> ​
>>>
>>
>> ​Ideally we should have a configuration management system in place to
>> manage this. It's an overhead to work with multiple VM images.
>> ​
>> ​
>>
>> 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
>>
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
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] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

Can you give an update on the latest status? I checked the github
repositories under your account, but still can find only the membership
scheme and a couple of templates. Did you add the scripts to
deploy/undeploy the products? As we saw, its just a matter of copy pasting
from the Azure management portal since the deployment script is auto
generated.

On Fri, Aug 5, 2016 at 10:56 AM, Imesh Gunaratne  wrote:

> On Fri, Aug 5, 2016 at 9:07 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> This is the progress so far.
>>
>> I have created a template, using which you can deploy 3 VMs, manager
>> node, worker node and a DB. This template can be used in any azure
>> subscription, you only have to do a template deployment using that
>> template. You have to pass the relevant VM images at the time of deployment
>> so for that I have created 5 VM images,
>>
>>1. WSO2 AS as manager
>>2. WSO2 AS as worker
>>3. WSO2 ESB as manager
>>4. WSO2 ESB as worker
>>5. DB
>>
>> ​Are you running a database server on a VM? On Azure it would be better
> to use their database service for creating databases otherwise managing
> databases on VMs would be difficult.
>
> These VM images are in my azure storage account so that prior to the
>> deployment, they have to be copied to the storage account of the customer.
>> Each VM image is approx 30 GB in size. Once you copied the images, you can
>> start the deployment using the template.
>> ​
>>
>
> ​Ideally we should have a configuration management system in place to
> manage this. It's an overhead to work with multiple VM images.
> ​
> ​
>
> 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
>
>
>


-- 
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] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Fri, Aug 5, 2016 at 9:07 AM, Osura Rathnayake > wrote:

> Hi Mentors,
>
> This is the progress so far.
>
> I have created a template, using which you can deploy 3 VMs, manager node,
> worker node and a DB. This template can be used in any azure subscription,
> you only have to do a template deployment using that template. You have to
> pass the relevant VM images at the time of deployment so for that I have
> created 5 VM images,
>
>1. WSO2 AS as manager
>2. WSO2 AS as worker
>3. WSO2 ESB as manager
>4. WSO2 ESB as worker
>5. DB
>
> ​Are you running a database server on a VM? On Azure it would be better to
use their database service for creating databases otherwise managing
databases on VMs would be difficult.

These VM images are in my azure storage account so that prior to the
> deployment, they have to be copied to the storage account of the customer.
> Each VM image is approx 30 GB in size. Once you copied the images, you can
> start the deployment using the template.
> ​
>

​Ideally we should have a configuration management system in place to
manage this. It's an overhead to work with multiple VM images.
​
​

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] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

This is the progress so far.

I have created a template, using which you can deploy 3 VMs, manager node,
worker node and a DB. This template can be used in any azure subscription,
you only have to do a template deployment using that template. You have to
pass the relevant VM images at the time of deployment so for that I have
created 5 VM images,

   1. WSO2 AS as manager
   2. WSO2 AS as worker
   3. WSO2 ESB as manager
   4. WSO2 ESB as worker
   5. DB

These VM images are in my azure storage account so that prior to the
deployment, they have to be copied to the storage account of the customer.
Each VM image is approx 30 GB in size. Once you copied the images, you can
start the deployment using the template.

I think it'd better if you have a look at these VM images to check if they
are up to the standard.

Thanks,

On Wed, Aug 3, 2016 at 7:58 PM, Osura Rathnayake  wrote:

> Hi Imesh,
>
> Thank you for highlighting the issues. I'm right on solving them.
>
> You can find the artifacts here [1]. Using the template.json, you can
> deploy a manager node, worker node and the DB VMs and other related
> resources such as network interfaces and network security groups. also you
> can pass the VM image for each of them. For an example If you pass a WSO2
> AS manager VM image to the the manager VM in the template, you can deploy
> that manager VM with WSO2 AS. you can do the same for worker node VM and DB
> VM. Next task is to create VM images for each product as manager and
> worker. I will soon update the readme file for each of them as well.
>
> [1] https://github.com/osuran/azure-artifacts
>
> thank you,
>
> On Wed, Aug 3, 2016 at 11:44 AM, Imesh Gunaratne  wrote:
>
>> Hi Osura,
>>
>> I have reported some issues in your git repository, please have a look:
>> https://github.com/osuran/azure-membership-scheme/issues
>>
>> Where can we find the artifacts that you have created for deploying WSO2
>> AS on Azure?
>>
>> Thanks
>>
>> On Wed, Aug 3, 2016 at 10:30 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you for the corrections. I will update you with the findings.
>>>
>>> On Wed, Aug 3, 2016 at 10:17 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Thanks for the notes.

 On Wed, Aug 3, 2016 at 10:09 AM, Osura Rathnayake 
 wrote:

> Hi All,
>
> following are the meeting minutes of the hangout we had on 2nd of
> August, 2016.
>
> We discussed about how to automate the deployment process and came to
> the conclusion to use Azure Automation Script feature where you can
> generate a script to automate the deployment of a particular resource.
> Output of this can be in Azure Template( JSON), CLI, PowerShell, .NET or
> Ruby.
> next task : 1) As the initial step, come up with templates and CLI
> scripts for deployments of WSO2 AS, AM and ESB where there are a manager
> node and two worker with hardcoded credentials and then use puppet. 2)
> Research on the flow of automated deployment considering the dependencies.
>
> I was instructed to implement a method to get metering information
> incurred on WSO2 products.
>
 Correction: we need to check if Azure side supports the level of
 metering that is required. As per the information we have up to now, Azure
 has some billing information for the usage, in which we cannot drill down
 and get fine grained information.

>
> I was instructed to do the documentation on each automated deployment
> template, in Github in markdown format.
>
 From the R'n D point of view, lets prioritize the following:

1. automating the distributed deployment for few products (AS and
APIM, etc.)
2. Check the possibility of using WSO2 Puppet modules to create the
VM.


> Thank you,
>
> On Mon, Aug 1, 2016 at 12:44 PM, Imesh Gunaratne 
> wrote:
>
>> Hi Osura,
>>
>> It's good to see the blog posts!
>> IMO it would be better if you can start writing documentation in
>> parallel to blog posts, may be using Markdown format in Github.
>>
>> Thanks
>>
>> On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Hi Isuru,
>>>
>>> I'm researching about automation in Azure. Shall we please have the
>>> hangout on Monday?
>>> BTW I will be able to complete the documentation on centralized
>>> logging, monitoring, auto scaling and load balancing by this weekend 
>>> and I
>>> will update my blog with the progress. Your feedback is much 
>>> appreciated.
>>>
>>> Thank you,
>>>
>>> On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 On Wed, Jul 27, 2016 at 9:17 AM, Osura 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

Thank you for highlighting the issues. I'm right on solving them.

You can find the artifacts here [1]. Using the template.json, you can
deploy a manager node, worker node and the DB VMs and other related
resources such as network interfaces and network security groups. also you
can pass the VM image for each of them. For an example If you pass a WSO2
AS manager VM image to the the manager VM in the template, you can deploy
that manager VM with WSO2 AS. you can do the same for worker node VM and DB
VM. Next task is to create VM images for each product as manager and
worker. I will soon update the readme file for each of them as well.

[1] https://github.com/osuran/azure-artifacts

thank you,

On Wed, Aug 3, 2016 at 11:44 AM, Imesh Gunaratne  wrote:

> Hi Osura,
>
> I have reported some issues in your git repository, please have a look:
> https://github.com/osuran/azure-membership-scheme/issues
>
> Where can we find the artifacts that you have created for deploying WSO2
> AS on Azure?
>
> Thanks
>
> On Wed, Aug 3, 2016 at 10:30 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you for the corrections. I will update you with the findings.
>>
>> On Wed, Aug 3, 2016 at 10:17 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Thanks for the notes.
>>>
>>> On Wed, Aug 3, 2016 at 10:09 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi All,

 following are the meeting minutes of the hangout we had on 2nd of
 August, 2016.

 We discussed about how to automate the deployment process and came to
 the conclusion to use Azure Automation Script feature where you can
 generate a script to automate the deployment of a particular resource.
 Output of this can be in Azure Template( JSON), CLI, PowerShell, .NET or
 Ruby.
 next task : 1) As the initial step, come up with templates and CLI
 scripts for deployments of WSO2 AS, AM and ESB where there are a manager
 node and two worker with hardcoded credentials and then use puppet. 2)
 Research on the flow of automated deployment considering the dependencies.

 I was instructed to implement a method to get metering information
 incurred on WSO2 products.

>>> Correction: we need to check if Azure side supports the level of
>>> metering that is required. As per the information we have up to now, Azure
>>> has some billing information for the usage, in which we cannot drill down
>>> and get fine grained information.
>>>

 I was instructed to do the documentation on each automated deployment
 template, in Github in markdown format.

>>> From the R'n D point of view, lets prioritize the following:
>>>
>>>1. automating the distributed deployment for few products (AS and
>>>APIM, etc.)
>>>2. Check the possibility of using WSO2 Puppet modules to create the
>>>VM.
>>>
>>>
 Thank you,

 On Mon, Aug 1, 2016 at 12:44 PM, Imesh Gunaratne 
 wrote:

> Hi Osura,
>
> It's good to see the blog posts!
> IMO it would be better if you can start writing documentation in
> parallel to blog posts, may be using Markdown format in Github.
>
> Thanks
>
> On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake  > wrote:
>
>> Hi Isuru,
>>
>> I'm researching about automation in Azure. Shall we please have the
>> hangout on Monday?
>> BTW I will be able to complete the documentation on centralized
>> logging, monitoring, auto scaling and load balancing by this weekend and 
>> I
>> will update my blog with the progress. Your feedback is much appreciated.
>>
>> Thank you,
>>
>> On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi All,

 Following are the meeting notes of the hangout we had on 25th of
 July, 2016.

 *Centralized logging*

 Azure Log Analytics provides centralized logging which facilitates
 the users to get logs from a given location in a VM, to a centralized
 location so that they can analyse and query those logs as they need.
 *next task - Documentation in terms of a blog post or webinar

 *Auto scaling*

 Auto scaling is achieved through scale sets in Azure. Scale set is
 a set of VMs and auto scaling rules that defines auto scale metrics &
 actions and the specification of the VMs.

 *Limitations - Azure portal doesn't support addition of auto scale
 rules, it only allows to add a simple scale set with a given number of
 instances. Whereas azure CLI, Powershell and REST API supports full
 functionality.

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

Hi Osura,

I have reported some issues in your git repository, please have a look:
https://github.com/osuran/azure-membership-scheme/issues

Where can we find the artifacts that you have created for deploying WSO2 AS
on Azure?

Thanks

On Wed, Aug 3, 2016 at 10:30 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Thank you for the corrections. I will update you with the findings.
>
> On Wed, Aug 3, 2016 at 10:17 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Thanks for the notes.
>>
>> On Wed, Aug 3, 2016 at 10:09 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi All,
>>>
>>> following are the meeting minutes of the hangout we had on 2nd of
>>> August, 2016.
>>>
>>> We discussed about how to automate the deployment process and came to
>>> the conclusion to use Azure Automation Script feature where you can
>>> generate a script to automate the deployment of a particular resource.
>>> Output of this can be in Azure Template( JSON), CLI, PowerShell, .NET or
>>> Ruby.
>>> next task : 1) As the initial step, come up with templates and CLI
>>> scripts for deployments of WSO2 AS, AM and ESB where there are a manager
>>> node and two worker with hardcoded credentials and then use puppet. 2)
>>> Research on the flow of automated deployment considering the dependencies.
>>>
>>> I was instructed to implement a method to get metering information
>>> incurred on WSO2 products.
>>>
>> Correction: we need to check if Azure side supports the level of metering
>> that is required. As per the information we have up to now, Azure has some
>> billing information for the usage, in which we cannot drill down and get
>> fine grained information.
>>
>>>
>>> I was instructed to do the documentation on each automated deployment
>>> template, in Github in markdown format.
>>>
>> From the R'n D point of view, lets prioritize the following:
>>
>>1. automating the distributed deployment for few products (AS and
>>APIM, etc.)
>>2. Check the possibility of using WSO2 Puppet modules to create the
>>VM.
>>
>>
>>> Thank you,
>>>
>>> On Mon, Aug 1, 2016 at 12:44 PM, Imesh Gunaratne  wrote:
>>>
 Hi Osura,

 It's good to see the blog posts!
 IMO it would be better if you can start writing documentation in
 parallel to blog posts, may be using Markdown format in Github.

 Thanks

 On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> I'm researching about automation in Azure. Shall we please have the
> hangout on Monday?
> BTW I will be able to complete the documentation on centralized
> logging, monitoring, auto scaling and load balancing by this weekend and I
> will update my blog with the progress. Your feedback is much appreciated.
>
> Thank you,
>
> On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake > > wrote:
>>
>>> Hi All,
>>>
>>> Following are the meeting notes of the hangout we had on 25th of
>>> July, 2016.
>>>
>>> *Centralized logging*
>>>
>>> Azure Log Analytics provides centralized logging which facilitates
>>> the users to get logs from a given location in a VM, to a centralized
>>> location so that they can analyse and query those logs as they need.
>>> *next task - Documentation in terms of a blog post or webinar
>>>
>>> *Auto scaling*
>>>
>>> Auto scaling is achieved through scale sets in Azure. Scale set is a
>>> set of VMs and auto scaling rules that defines auto scale metrics & 
>>> actions
>>> and the specification of the VMs.
>>>
>>> *Limitations - Azure portal doesn't support addition of auto scale
>>> rules, it only allows to add a simple scale set with a given number of
>>> instances. Whereas azure CLI, Powershell and REST API supports full
>>> functionality.
>>>
>>> I have added the template to the github repo which I used to create
>>> the auto scale settings which includes the ability to add a custom VM 
>>> image
>>> and auto scale rules. When you deploy from this template you should give
>>> the URI of the VM image. you can edit auto scale rules using CLI, Power
>>> shell or REST API. Azure Resource Explorer
>>>  can be used if you choose REST API to
>>> modify.
>>>
>>> *next tasks - 1) Have to figure out a way to pass application and
>>> user data such as usernames and passwords of database, to the VM image
>>> through the template. 2) Documentaion
>>>
>>>
>>> *Load balancing*
>>>
>>> Following are some key terms you need to know.
>>>
>>> · Backend pool: This is a pool of virtual machines that
>>> share the traffic
>>>
>>> · Probe: The 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Thank you for the corrections. I will update you with the findings.

On Wed, Aug 3, 2016 at 10:17 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> Thanks for the notes.
>
> On Wed, Aug 3, 2016 at 10:09 AM, Osura Rathnayake 
> wrote:
>
>> Hi All,
>>
>> following are the meeting minutes of the hangout we had on 2nd of August,
>> 2016.
>>
>> We discussed about how to automate the deployment process and came to the
>> conclusion to use Azure Automation Script feature where you can generate a
>> script to automate the deployment of a particular resource. Output of this
>> can be in Azure Template( JSON), CLI, PowerShell, .NET or Ruby.
>> next task : 1) As the initial step, come up with templates and CLI
>> scripts for deployments of WSO2 AS, AM and ESB where there are a manager
>> node and two worker with hardcoded credentials and then use puppet. 2)
>> Research on the flow of automated deployment considering the dependencies.
>>
>> I was instructed to implement a method to get metering information
>> incurred on WSO2 products.
>>
> Correction: we need to check if Azure side supports the level of metering
> that is required. As per the information we have up to now, Azure has some
> billing information for the usage, in which we cannot drill down and get
> fine grained information.
>
>>
>> I was instructed to do the documentation on each automated deployment
>> template, in Github in markdown format.
>>
> From the R'n D point of view, lets prioritize the following:
>
>1. automating the distributed deployment for few products (AS and
>APIM, etc.)
>2. Check the possibility of using WSO2 Puppet modules to create the VM.
>
>
>> Thank you,
>>
>> On Mon, Aug 1, 2016 at 12:44 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Osura,
>>>
>>> It's good to see the blog posts!
>>> IMO it would be better if you can start writing documentation in
>>> parallel to blog posts, may be using Markdown format in Github.
>>>
>>> Thanks
>>>
>>> On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 I'm researching about automation in Azure. Shall we please have the
 hangout on Monday?
 BTW I will be able to complete the documentation on centralized
 logging, monitoring, auto scaling and load balancing by this weekend and I
 will update my blog with the progress. Your feedback is much appreciated.

 Thank you,

 On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
> wrote:
>
>> Hi All,
>>
>> Following are the meeting notes of the hangout we had on 25th of
>> July, 2016.
>>
>> *Centralized logging*
>>
>> Azure Log Analytics provides centralized logging which facilitates
>> the users to get logs from a given location in a VM, to a centralized
>> location so that they can analyse and query those logs as they need.
>> *next task - Documentation in terms of a blog post or webinar
>>
>> *Auto scaling*
>>
>> Auto scaling is achieved through scale sets in Azure. Scale set is a
>> set of VMs and auto scaling rules that defines auto scale metrics & 
>> actions
>> and the specification of the VMs.
>>
>> *Limitations - Azure portal doesn't support addition of auto scale
>> rules, it only allows to add a simple scale set with a given number of
>> instances. Whereas azure CLI, Powershell and REST API supports full
>> functionality.
>>
>> I have added the template to the github repo which I used to create
>> the auto scale settings which includes the ability to add a custom VM 
>> image
>> and auto scale rules. When you deploy from this template you should give
>> the URI of the VM image. you can edit auto scale rules using CLI, Power
>> shell or REST API. Azure Resource Explorer
>>  can be used if you choose REST API to
>> modify.
>>
>> *next tasks - 1) Have to figure out a way to pass application and
>> user data such as usernames and passwords of database, to the VM image
>> through the template. 2) Documentaion
>>
>>
>> *Load balancing*
>>
>> Following are some key terms you need to know.
>>
>> · Backend pool: This is a pool of virtual machines that
>> share the traffic
>>
>> · Probe: The load balancer can probe the health of the
>> various server instances. When a probe fails to respond, the load 
>> balancer
>> stops sending new connections to the unhealthy instances. Existing
>> connections are not impacted.
>>
>> · Availability set: when you have a set of virtual machines
>> for the same purpose, azure recommends to add them to an availability 
>> set.
>>
>> We can add load balancing 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

Thanks for the notes.

On Wed, Aug 3, 2016 at 10:09 AM, Osura Rathnayake 
wrote:

> Hi All,
>
> following are the meeting minutes of the hangout we had on 2nd of August,
> 2016.
>
> We discussed about how to automate the deployment process and came to the
> conclusion to use Azure Automation Script feature where you can generate a
> script to automate the deployment of a particular resource. Output of this
> can be in Azure Template( JSON), CLI, PowerShell, .NET or Ruby.
> next task : 1) As the initial step, come up with templates and CLI scripts
> for deployments of WSO2 AS, AM and ESB where there are a manager node and
> two worker with hardcoded credentials and then use puppet. 2) Research on
> the flow of automated deployment considering the dependencies.
>
> I was instructed to implement a method to get metering information
> incurred on WSO2 products.
>
Correction: we need to check if Azure side supports the level of metering
that is required. As per the information we have up to now, Azure has some
billing information for the usage, in which we cannot drill down and get
fine grained information.

>
> I was instructed to do the documentation on each automated deployment
> template, in Github in markdown format.
>
>From the R'n D point of view, lets prioritize the following:

   1. automating the distributed deployment for few products (AS and APIM,
   etc.)
   2. Check the possibility of using WSO2 Puppet modules to create the VM.


> Thank you,
>
> On Mon, Aug 1, 2016 at 12:44 PM, Imesh Gunaratne  wrote:
>
>> Hi Osura,
>>
>> It's good to see the blog posts!
>> IMO it would be better if you can start writing documentation in parallel
>> to blog posts, may be using Markdown format in Github.
>>
>> Thanks
>>
>> On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> I'm researching about automation in Azure. Shall we please have the
>>> hangout on Monday?
>>> BTW I will be able to complete the documentation on centralized logging,
>>> monitoring, auto scaling and load balancing by this weekend and I will
>>> update my blog with the progress. Your feedback is much appreciated.
>>>
>>> Thank you,
>>>
>>> On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
 wrote:

> Hi All,
>
> Following are the meeting notes of the hangout we had on 25th of July,
> 2016.
>
> *Centralized logging*
>
> Azure Log Analytics provides centralized logging which facilitates the
> users to get logs from a given location in a VM, to a centralized location
> so that they can analyse and query those logs as they need.
> *next task - Documentation in terms of a blog post or webinar
>
> *Auto scaling*
>
> Auto scaling is achieved through scale sets in Azure. Scale set is a
> set of VMs and auto scaling rules that defines auto scale metrics & 
> actions
> and the specification of the VMs.
>
> *Limitations - Azure portal doesn't support addition of auto scale
> rules, it only allows to add a simple scale set with a given number of
> instances. Whereas azure CLI, Powershell and REST API supports full
> functionality.
>
> I have added the template to the github repo which I used to create
> the auto scale settings which includes the ability to add a custom VM 
> image
> and auto scale rules. When you deploy from this template you should give
> the URI of the VM image. you can edit auto scale rules using CLI, Power
> shell or REST API. Azure Resource Explorer
>  can be used if you choose REST API to
> modify.
>
> *next tasks - 1) Have to figure out a way to pass application and user
> data such as usernames and passwords of database, to the VM image through
> the template. 2) Documentaion
>
>
> *Load balancing*
>
> Following are some key terms you need to know.
>
> · Backend pool: This is a pool of virtual machines that share
> the traffic
>
> · Probe: The load balancer can probe the health of the
> various server instances. When a probe fails to respond, the load balancer
> stops sending new connections to the unhealthy instances. Existing
> connections are not impacted.
>
> · Availability set: when you have a set of virtual machines
> for the same purpose, azure recommends to add them to an availability set.
>
> We can add load balancing rules such that requests coming from a given
> URL  are shared among the VMs in backend pool. if we configure the load
> balancer with auto scaling, VMs in the scale set can be added to the
> backend pool so if the auto scale rules are met, it can scale in or out.
>
> *next tasks - 1)  

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi All,

following are the meeting minutes of the hangout we had on 2nd of August,
2016.

We discussed about how to automate the deployment process and came to the
conclusion to use Azure Automation Script feature where you can generate a
script to automate the deployment of a particular resource. Output of this
can be in Azure Template( JSON), CLI, PowerShell, .NET or Ruby.
next task : 1) As the initial step, come up with templates and CLI scripts
for deployments of WSO2 AS, AM and ESB where there are a manager node and
two worker with hardcoded credentials and then use puppet. 2) Research on
the flow of automated deployment considering the dependencies.

I was instructed to implement a method to get metering information incurred
on WSO2 products.

I was instructed to do the documentation on each automated deployment
template, in Github in markdown format.

Thank you,

On Mon, Aug 1, 2016 at 12:44 PM, Imesh Gunaratne  wrote:

> Hi Osura,
>
> It's good to see the blog posts!
> IMO it would be better if you can start writing documentation in parallel
> to blog posts, may be using Markdown format in Github.
>
> Thanks
>
> On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> I'm researching about automation in Azure. Shall we please have the
>> hangout on Monday?
>> BTW I will be able to complete the documentation on centralized logging,
>> monitoring, auto scaling and load balancing by this weekend and I will
>> update my blog with the progress. Your feedback is much appreciated.
>>
>> Thank you,
>>
>> On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi All,

 Following are the meeting notes of the hangout we had on 25th of July,
 2016.

 *Centralized logging*

 Azure Log Analytics provides centralized logging which facilitates the
 users to get logs from a given location in a VM, to a centralized location
 so that they can analyse and query those logs as they need.
 *next task - Documentation in terms of a blog post or webinar

 *Auto scaling*

 Auto scaling is achieved through scale sets in Azure. Scale set is a
 set of VMs and auto scaling rules that defines auto scale metrics & actions
 and the specification of the VMs.

 *Limitations - Azure portal doesn't support addition of auto scale
 rules, it only allows to add a simple scale set with a given number of
 instances. Whereas azure CLI, Powershell and REST API supports full
 functionality.

 I have added the template to the github repo which I used to create the
 auto scale settings which includes the ability to add a custom VM image and
 auto scale rules. When you deploy from this template you should give the
 URI of the VM image. you can edit auto scale rules using CLI, Power shell
 or REST API. Azure Resource Explorer  can
 be used if you choose REST API to modify.

 *next tasks - 1) Have to figure out a way to pass application and user
 data such as usernames and passwords of database, to the VM image through
 the template. 2) Documentaion


 *Load balancing*

 Following are some key terms you need to know.

 · Backend pool: This is a pool of virtual machines that share
 the traffic

 · Probe: The load balancer can probe the health of the various
 server instances. When a probe fails to respond, the load balancer stops
 sending new connections to the unhealthy instances. Existing connections
 are not impacted.

 · Availability set: when you have a set of virtual machines
 for the same purpose, azure recommends to add them to an availability set.

 We can add load balancing rules such that requests coming from a given
 URL  are shared among the VMs in backend pool. if we configure the load
 balancer with auto scaling, VMs in the scale set can be added to the
 backend pool so if the auto scale rules are met, it can scale in or out.

 *next tasks - 1)  research more about Probe and service health
 checking. 2)  documentation 3) How to automate the whole deployment
 process.

>>> Thanks for the notes.
>>>
>>> From the next steps you have mentioned here, deployment automation part
>>> is very vital for the project completion. Basically we would need to use
>>> either the CLI or the Rest API and create a few of scripts to do a complete
>>> deployment on Azure. We can have a hangout today/Monday to discuss the
>>> progress on the next tasks and the automation aspects.
>>>

 [1] https://github.com/osuran/Azure-templates

 Thank you,


 On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

Hi Osura,

It's good to see the blog posts!
IMO it would be better if you can start writing documentation in parallel
to blog posts, may be using Markdown format in Github.

Thanks

On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> I'm researching about automation in Azure. Shall we please have the
> hangout on Monday?
> BTW I will be able to complete the documentation on centralized logging,
> monitoring, auto scaling and load balancing by this weekend and I will
> update my blog with the progress. Your feedback is much appreciated.
>
> Thank you,
>
> On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi All,
>>>
>>> Following are the meeting notes of the hangout we had on 25th of July,
>>> 2016.
>>>
>>> *Centralized logging*
>>>
>>> Azure Log Analytics provides centralized logging which facilitates the
>>> users to get logs from a given location in a VM, to a centralized location
>>> so that they can analyse and query those logs as they need.
>>> *next task - Documentation in terms of a blog post or webinar
>>>
>>> *Auto scaling*
>>>
>>> Auto scaling is achieved through scale sets in Azure. Scale set is a set
>>> of VMs and auto scaling rules that defines auto scale metrics & actions and
>>> the specification of the VMs.
>>>
>>> *Limitations - Azure portal doesn't support addition of auto scale
>>> rules, it only allows to add a simple scale set with a given number of
>>> instances. Whereas azure CLI, Powershell and REST API supports full
>>> functionality.
>>>
>>> I have added the template to the github repo which I used to create the
>>> auto scale settings which includes the ability to add a custom VM image and
>>> auto scale rules. When you deploy from this template you should give the
>>> URI of the VM image. you can edit auto scale rules using CLI, Power shell
>>> or REST API. Azure Resource Explorer  can
>>> be used if you choose REST API to modify.
>>>
>>> *next tasks - 1) Have to figure out a way to pass application and user
>>> data such as usernames and passwords of database, to the VM image through
>>> the template. 2) Documentaion
>>>
>>>
>>> *Load balancing*
>>>
>>> Following are some key terms you need to know.
>>>
>>> · Backend pool: This is a pool of virtual machines that share
>>> the traffic
>>>
>>> · Probe: The load balancer can probe the health of the various
>>> server instances. When a probe fails to respond, the load balancer stops
>>> sending new connections to the unhealthy instances. Existing connections
>>> are not impacted.
>>>
>>> · Availability set: when you have a set of virtual machines for
>>> the same purpose, azure recommends to add them to an availability set.
>>>
>>> We can add load balancing rules such that requests coming from a given
>>> URL  are shared among the VMs in backend pool. if we configure the load
>>> balancer with auto scaling, VMs in the scale set can be added to the
>>> backend pool so if the auto scale rules are met, it can scale in or out.
>>>
>>> *next tasks - 1)  research more about Probe and service health checking.
>>> 2)  documentation 3) How to automate the whole deployment process.
>>>
>> Thanks for the notes.
>>
>> From the next steps you have mentioned here, deployment automation part
>> is very vital for the project completion. Basically we would need to use
>> either the CLI or the Rest API and create a few of scripts to do a complete
>> deployment on Azure. We can have a hangout today/Monday to discuss the
>> progress on the next tasks and the automation aspects.
>>
>>>
>>> [1] https://github.com/osuran/Azure-templates
>>>
>>> Thank you,
>>>
>>>
>>> On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Thank you. That will solve the issue.

 On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> If you need any customizations/configurations done at the VM startup,
> you can use /etc/rc.local script to do it. Also, if you define the
> JAVA_HOME in a system wide bashrc file at /etc/bash.bashrc it won't get
> deleted when the user home is removed.
>
>
> On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake  > wrote:
>
>> Hi Imesh,
>>
>> You can only capture a generalized VM image, so when it's being
>> generalized, all of the data in '/home' is erased. Since .bashrc is also 
>> in
>> '/home/', it's also erased. Only the data that are 
>> not
>> in '/home' is preserved.
>>
>> Okay I will try out these steps.
>>
>> Thanks,
>>
>> On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Sun, Jul 24, 2016 at 6:30 PM, 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

I'm researching about automation in Azure. Shall we please have the hangout
on Monday?
BTW I will be able to complete the documentation on centralized logging,
monitoring, auto scaling and load balancing by this weekend and I will
update my blog with the progress. Your feedback is much appreciated.

Thank you,

On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
> wrote:
>
>> Hi All,
>>
>> Following are the meeting notes of the hangout we had on 25th of July,
>> 2016.
>>
>> *Centralized logging*
>>
>> Azure Log Analytics provides centralized logging which facilitates the
>> users to get logs from a given location in a VM, to a centralized location
>> so that they can analyse and query those logs as they need.
>> *next task - Documentation in terms of a blog post or webinar
>>
>> *Auto scaling*
>>
>> Auto scaling is achieved through scale sets in Azure. Scale set is a set
>> of VMs and auto scaling rules that defines auto scale metrics & actions and
>> the specification of the VMs.
>>
>> *Limitations - Azure portal doesn't support addition of auto scale rules,
>> it only allows to add a simple scale set with a given number of instances.
>> Whereas azure CLI, Powershell and REST API supports full functionality.
>>
>> I have added the template to the github repo which I used to create the
>> auto scale settings which includes the ability to add a custom VM image and
>> auto scale rules. When you deploy from this template you should give the
>> URI of the VM image. you can edit auto scale rules using CLI, Power shell
>> or REST API. Azure Resource Explorer  can be
>> used if you choose REST API to modify.
>>
>> *next tasks - 1) Have to figure out a way to pass application and user
>> data such as usernames and passwords of database, to the VM image through
>> the template. 2) Documentaion
>>
>>
>> *Load balancing*
>>
>> Following are some key terms you need to know.
>>
>> · Backend pool: This is a pool of virtual machines that share
>> the traffic
>>
>> · Probe: The load balancer can probe the health of the various
>> server instances. When a probe fails to respond, the load balancer stops
>> sending new connections to the unhealthy instances. Existing connections
>> are not impacted.
>>
>> · Availability set: when you have a set of virtual machines for
>> the same purpose, azure recommends to add them to an availability set.
>>
>> We can add load balancing rules such that requests coming from a given
>> URL  are shared among the VMs in backend pool. if we configure the load
>> balancer with auto scaling, VMs in the scale set can be added to the
>> backend pool so if the auto scale rules are met, it can scale in or out.
>>
>> *next tasks - 1)  research more about Probe and service health checking.
>> 2)  documentation 3) How to automate the whole deployment process.
>>
> Thanks for the notes.
>
> From the next steps you have mentioned here, deployment automation part is
> very vital for the project completion. Basically we would need to use
> either the CLI or the Rest API and create a few of scripts to do a complete
> deployment on Azure. We can have a hangout today/Monday to discuss the
> progress on the next tasks and the automation aspects.
>
>>
>> [1] https://github.com/osuran/Azure-templates
>>
>> Thank you,
>>
>>
>> On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you. That will solve the issue.
>>>
>>> On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 If you need any customizations/configurations done at the VM startup,
 you can use /etc/rc.local script to do it. Also, if you define the
 JAVA_HOME in a system wide bashrc file at /etc/bash.bashrc it won't get
 deleted when the user home is removed.


 On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake 
 wrote:

> Hi Imesh,
>
> You can only capture a generalized VM image, so when it's being
> generalized, all of the data in '/home' is erased. Since .bashrc is also 
> in
> '/home/', it's also erased. Only the data that are 
> not
> in '/home' is preserved.
>
> Okay I will try out these steps.
>
> Thanks,
>
> On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne 
> wrote:
>
>> Hi Osura,
>>
>> On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Mentors,
>>>
>>> I could successfully configure auto scaling with a VM which has a
>>> WSO2 application server installed in it. When capturing a VM, it first 
>>> get
>>> deallocated and then generalized.
>>>
>>
>> ​I'm sorry I did not get this. Can you please elaborate this further?
>> ​
>>

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
wrote:

> Hi All,
>
> Following are the meeting notes of the hangout we had on 25th of July,
> 2016.
>
> *Centralized logging*
>
> Azure Log Analytics provides centralized logging which facilitates the
> users to get logs from a given location in a VM, to a centralized location
> so that they can analyse and query those logs as they need.
> *next task - Documentation in terms of a blog post or webinar
>
> *Auto scaling*
>
> Auto scaling is achieved through scale sets in Azure. Scale set is a set
> of VMs and auto scaling rules that defines auto scale metrics & actions and
> the specification of the VMs.
>
> *Limitations - Azure portal doesn't support addition of auto scale rules,
> it only allows to add a simple scale set with a given number of instances.
> Whereas azure CLI, Powershell and REST API supports full functionality.
>
> I have added the template to the github repo which I used to create the
> auto scale settings which includes the ability to add a custom VM image and
> auto scale rules. When you deploy from this template you should give the
> URI of the VM image. you can edit auto scale rules using CLI, Power shell
> or REST API. Azure Resource Explorer  can be
> used if you choose REST API to modify.
>
> *next tasks - 1) Have to figure out a way to pass application and user
> data such as usernames and passwords of database, to the VM image through
> the template. 2) Documentaion
>
>
> *Load balancing*
>
> Following are some key terms you need to know.
>
> · Backend pool: This is a pool of virtual machines that share the
> traffic
>
> · Probe: The load balancer can probe the health of the various
> server instances. When a probe fails to respond, the load balancer stops
> sending new connections to the unhealthy instances. Existing connections
> are not impacted.
>
> · Availability set: when you have a set of virtual machines for
> the same purpose, azure recommends to add them to an availability set.
>
> We can add load balancing rules such that requests coming from a given URL
>  are shared among the VMs in backend pool. if we configure the load
> balancer with auto scaling, VMs in the scale set can be added to the
> backend pool so if the auto scale rules are met, it can scale in or out.
>
> *next tasks - 1)  research more about Probe and service health checking.
> 2)  documentation 3) How to automate the whole deployment process.
>
Thanks for the notes.

>From the next steps you have mentioned here, deployment automation part is
very vital for the project completion. Basically we would need to use
either the CLI or the Rest API and create a few of scripts to do a complete
deployment on Azure. We can have a hangout today/Monday to discuss the
progress on the next tasks and the automation aspects.

>
> [1] https://github.com/osuran/Azure-templates
>
> Thank you,
>
>
> On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you. That will solve the issue.
>>
>> On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> If you need any customizations/configurations done at the VM startup,
>>> you can use /etc/rc.local script to do it. Also, if you define the
>>> JAVA_HOME in a system wide bashrc file at /etc/bash.bashrc it won't get
>>> deleted when the user home is removed.
>>>
>>>
>>> On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Imesh,

 You can only capture a generalized VM image, so when it's being
 generalized, all of the data in '/home' is erased. Since .bashrc is also in
 '/home/', it's also erased. Only the data that are not
 in '/home' is preserved.

 Okay I will try out these steps.

 Thanks,

 On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne 
 wrote:

> Hi Osura,
>
> On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I could successfully configure auto scaling with a VM which has a
>> WSO2 application server installed in it. When capturing a VM, it first 
>> get
>> deallocated and then generalized.
>>
>
> ​I'm sorry I did not get this. Can you please elaborate this further?
> ​
>
>
>> So the Java home set in .bashrc is gone in the captured image of the
>> VM. So I had to reset the Java home and also I had to manually start the
>> server after the startup of the VM.
>>
>
> ​​I think you are trying to create a VM image from a running VM
> instance and try to reuse that. Can you please try following:
>
>
>1. Create a VM instance from Ubuntu 14.04 VM image
>2. Extract JDK 1.7 (JAVA_HOME) and the WSO2 server distribution
>(CARBON_HOME) to /opt/ directory.
>

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi All,

Please read my blog if you have some free time [1] and your suggestions and
comments are most welcome. I have updated it with posts on Azure Membership
Scheme, Centralized logging in Azure and monitoring in Azure.

[1] http://osuran.blogspot.com/

Thank you,

On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
wrote:

> Hi All,
>
> Following are the meeting notes of the hangout we had on 25th of July,
> 2016.
>
> *Centralized logging*
>
> Azure Log Analytics provides centralized logging which facilitates the
> users to get logs from a given location in a VM, to a centralized location
> so that they can analyse and query those logs as they need.
> *next task - Documentation in terms of a blog post or webinar
>
> *Auto scaling*
>
> Auto scaling is achieved through scale sets in Azure. Scale set is a set
> of VMs and auto scaling rules that defines auto scale metrics & actions and
> the specification of the VMs.
>
> *Limitations - Azure portal doesn't support addition of auto scale rules,
> it only allows to add a simple scale set with a given number of instances.
> Whereas azure CLI, Powershell and REST API supports full functionality.
>
> I have added the template to the github repo which I used to create the
> auto scale settings which includes the ability to add a custom VM image and
> auto scale rules. When you deploy from this template you should give the
> URI of the VM image. you can edit auto scale rules using CLI, Power shell
> or REST API. Azure Resource Explorer  can be
> used if you choose REST API to modify.
>
> *next tasks - 1) Have to figure out a way to pass application and user
> data such as usernames and passwords of database, to the VM image through
> the template. 2) Documentaion
>
>
> *Load balancing*
>
> Following are some key terms you need to know.
>
> · Backend pool: This is a pool of virtual machines that share the
> traffic
>
> · Probe: The load balancer can probe the health of the various
> server instances. When a probe fails to respond, the load balancer stops
> sending new connections to the unhealthy instances. Existing connections
> are not impacted.
>
> · Availability set: when you have a set of virtual machines for
> the same purpose, azure recommends to add them to an availability set.
>
> We can add load balancing rules such that requests coming from a given URL
>  are shared among the VMs in backend pool. if we configure the load
> balancer with auto scaling, VMs in the scale set can be added to the
> backend pool so if the auto scale rules are met, it can scale in or out.
>
> *next tasks - 1)  research more about Probe and service health checking.
> 2)  documentation 3) How to automate the whole deployment process.
>
> [1] https://github.com/osuran/Azure-templates
>
> Thank you,
>
>
> On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you. That will solve the issue.
>>
>> On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> If you need any customizations/configurations done at the VM startup,
>>> you can use /etc/rc.local script to do it. Also, if you define the
>>> JAVA_HOME in a system wide bashrc file at /etc/bash.bashrc it won't get
>>> deleted when the user home is removed.
>>>
>>>
>>> On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Imesh,

 You can only capture a generalized VM image, so when it's being
 generalized, all of the data in '/home' is erased. Since .bashrc is also in
 '/home/', it's also erased. Only the data that are not
 in '/home' is preserved.

 Okay I will try out these steps.

 Thanks,

 On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne 
 wrote:

> Hi Osura,
>
> On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I could successfully configure auto scaling with a VM which has a
>> WSO2 application server installed in it. When capturing a VM, it first 
>> get
>> deallocated and then generalized.
>>
>
> ​I'm sorry I did not get this. Can you please elaborate this further?
> ​
>
>
>> So the Java home set in .bashrc is gone in the captured image of the
>> VM. So I had to reset the Java home and also I had to manually start the
>> server after the startup of the VM.
>>
>
> ​​I think you are trying to create a VM image from a running VM
> instance and try to reuse that. Can you please try following:
>
>
>1. Create a VM instance from Ubuntu 14.04 VM image
>2. Extract JDK 1.7 (JAVA_HOME) and the WSO2 server distribution
>(CARBON_HOME) to /opt/ directory.
>3. Write a brash script (init.sh) to start the WSO2 server by
>invoking CARBON_HOME/bin/wso2server.sh
>   

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi All,

Following are the meeting notes of the hangout we had on 25th of July, 2016.

*Centralized logging*

Azure Log Analytics provides centralized logging which facilitates the
users to get logs from a given location in a VM, to a centralized location
so that they can analyse and query those logs as they need.
*next task - Documentation in terms of a blog post or webinar

*Auto scaling*

Auto scaling is achieved through scale sets in Azure. Scale set is a set of
VMs and auto scaling rules that defines auto scale metrics & actions and
the specification of the VMs.

*Limitations - Azure portal doesn't support addition of auto scale rules,
it only allows to add a simple scale set with a given number of instances.
Whereas azure CLI, Powershell and REST API supports full functionality.

I have added the template to the github repo which I used to create the
auto scale settings which includes the ability to add a custom VM image and
auto scale rules. When you deploy from this template you should give the
URI of the VM image. you can edit auto scale rules using CLI, Power shell
or REST API. Azure Resource Explorer  can be
used if you choose REST API to modify.

*next tasks - 1) Have to figure out a way to pass application and user data
such as usernames and passwords of database, to the VM image through the
template. 2) Documentaion


*Load balancing*

Following are some key terms you need to know.

· Backend pool: This is a pool of virtual machines that share the
traffic

· Probe: The load balancer can probe the health of the various
server instances. When a probe fails to respond, the load balancer stops
sending new connections to the unhealthy instances. Existing connections
are not impacted.

· Availability set: when you have a set of virtual machines for the
same purpose, azure recommends to add them to an availability set.

We can add load balancing rules such that requests coming from a given URL
 are shared among the VMs in backend pool. if we configure the load
balancer with auto scaling, VMs in the scale set can be added to the
backend pool so if the auto scale rules are met, it can scale in or out.

*next tasks - 1)  research more about Probe and service health checking. 2)
 documentation 3) How to automate the whole deployment process.

[1] https://github.com/osuran/Azure-templates

Thank you,


On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Thank you. That will solve the issue.
>
> On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> If you need any customizations/configurations done at the VM startup, you
>> can use /etc/rc.local script to do it. Also, if you define the JAVA_HOME in
>> a system wide bashrc file at /etc/bash.bashrc it won't get deleted when the
>> user home is removed.
>>
>>
>> On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> You can only capture a generalized VM image, so when it's being
>>> generalized, all of the data in '/home' is erased. Since .bashrc is also in
>>> '/home/', it's also erased. Only the data that are not
>>> in '/home' is preserved.
>>>
>>> Okay I will try out these steps.
>>>
>>> Thanks,
>>>
>>> On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Osura,

 On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> I could successfully configure auto scaling with a VM which has a WSO2
> application server installed in it. When capturing a VM, it first get
> deallocated and then generalized.
>

 ​I'm sorry I did not get this. Can you please elaborate this further?
 ​


> So the Java home set in .bashrc is gone in the captured image of the
> VM. So I had to reset the Java home and also I had to manually start the
> server after the startup of the VM.
>

 ​​I think you are trying to create a VM image from a running VM
 instance and try to reuse that. Can you please try following:


1. Create a VM instance from Ubuntu 14.04 VM image
2. Extract JDK 1.7 (JAVA_HOME) and the WSO2 server distribution
(CARBON_HOME) to /opt/ directory.
3. Write a brash script (init.sh) to start the WSO2 server by
invoking CARBON_HOME/bin/wso2server.sh
4. Update /etc/rc.local to invoke the above bash script; init.sh
5. Create a VM image of this VM instance.

 Thanks

 Is there any method developed in WSO2 to overcome this situation?
>
> thanks,
>
> On Thu, Jul 21, 2016 at 5:10 PM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> That time is fine by me.
>>
>> thanks,
>>
>> On Thu, Jul 21, 2016 at 3:44 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Thank you. That will solve the issue.

On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> If you need any customizations/configurations done at the VM startup, you
> can use /etc/rc.local script to do it. Also, if you define the JAVA_HOME in
> a system wide bashrc file at /etc/bash.bashrc it won't get deleted when the
> user home is removed.
>
>
> On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh,
>>
>> You can only capture a generalized VM image, so when it's being
>> generalized, all of the data in '/home' is erased. Since .bashrc is also in
>> '/home/', it's also erased. Only the data that are not
>> in '/home' is preserved.
>>
>> Okay I will try out these steps.
>>
>> Thanks,
>>
>> On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne  wrote:
>>
>>> Hi Osura,
>>>
>>> On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 I could successfully configure auto scaling with a VM which has a WSO2
 application server installed in it. When capturing a VM, it first get
 deallocated and then generalized.

>>>
>>> ​I'm sorry I did not get this. Can you please elaborate this further?
>>> ​
>>>
>>>
 So the Java home set in .bashrc is gone in the captured image of the
 VM. So I had to reset the Java home and also I had to manually start the
 server after the startup of the VM.

>>>
>>> ​​I think you are trying to create a VM image from a running VM instance
>>> and try to reuse that. Can you please try following:
>>>
>>>
>>>1. Create a VM instance from Ubuntu 14.04 VM image
>>>2. Extract JDK 1.7 (JAVA_HOME) and the WSO2 server distribution
>>>(CARBON_HOME) to /opt/ directory.
>>>3. Write a brash script (init.sh) to start the WSO2 server by
>>>invoking CARBON_HOME/bin/wso2server.sh
>>>4. Update /etc/rc.local to invoke the above bash script; init.sh
>>>5. Create a VM image of this VM instance.
>>>
>>> Thanks
>>>
>>> Is there any method developed in WSO2 to overcome this situation?

 thanks,

 On Thu, Jul 21, 2016 at 5:10 PM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> That time is fine by me.
>
> thanks,
>
> On Thu, Jul 21, 2016 at 3:44 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Hi Mentors,
>>>
>>> I will try using Puppet.
>>> It wasn't a problem with log path/pattern, in fact I used the same
>>> log path that I used last time. I believe it was a bug from Azure side,
>>> please check the attached screenshots.
>>> Shall we please have the meeting on Friday?
>>>
>> +1. How about 2.00 - 3.0.0 PM on Friday?
>>
>>>
>>> thank you,
>>>
>>> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Shall we have a hangout on Thursday/ Friday to discuss and
 demonstrate the current progress of the project? Please let us know 
 your
 preference.

 On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne 
 wrote:

> Hi Osura,
>
> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake <
> osura...@gmail.com> wrote:
>
>> Hi Mentors,
>>
>> This is the progress so far.
>>
>> *Auto scaling*
>>
>>
>> Azure supports two paradigms of auto scaling, vertical and
>> horizontal. Vertical scaling, also known as scale up and scale down, 
>> means
>> increasing or decreasing virtual machine (VM) sizes in response to a
>> workload. As I explained in one of my previous emails, vertical auto
>> scaling is achieved through monitoring rules. We can set it to 
>> trigger an
>> alarm when certain conditions are met and also as the action we can 
>> set up
>> a runbook to scale up or down. I could successfully get VMs to scale 
>> up and
>> down using this feature.
>>
>
> ​We would use horizontal scaling in most scenarios.​
>
>
>>
>> Horizontal scaling, also referred to as scale out and scale in,
>> where the number of VMs is altered depending on the workload. 
>> Horizontal
>> scaling is achieved through virtual machine scale sets (VMSS). One
>> important thing about VMSS is that the VMs included should be of the 
>> same
>> size and have the same OS image. All the VMs in the scale set are 
>> added to
>> the load balancer, as a backend pool. Backend pool is a pool of VMs 
>> which
>> share the traffic coming via 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

If you need any customizations/configurations done at the VM startup, you
can use /etc/rc.local script to do it. Also, if you define the JAVA_HOME in
a system wide bashrc file at /etc/bash.bashrc it won't get deleted when the
user home is removed.

On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake 
wrote:

> Hi Imesh,
>
> You can only capture a generalized VM image, so when it's being
> generalized, all of the data in '/home' is erased. Since .bashrc is also in
> '/home/', it's also erased. Only the data that are not
> in '/home' is preserved.
>
> Okay I will try out these steps.
>
> Thanks,
>
> On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne  wrote:
>
>> Hi Osura,
>>
>> On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> I could successfully configure auto scaling with a VM which has a WSO2
>>> application server installed in it. When capturing a VM, it first get
>>> deallocated and then generalized.
>>>
>>
>> ​I'm sorry I did not get this. Can you please elaborate this further?
>> ​
>>
>>
>>> So the Java home set in .bashrc is gone in the captured image of the VM.
>>> So I had to reset the Java home and also I had to manually start the server
>>> after the startup of the VM.
>>>
>>
>> ​​I think you are trying to create a VM image from a running VM instance
>> and try to reuse that. Can you please try following:
>>
>>
>>1. Create a VM instance from Ubuntu 14.04 VM image
>>2. Extract JDK 1.7 (JAVA_HOME) and the WSO2 server distribution
>>(CARBON_HOME) to /opt/ directory.
>>3. Write a brash script (init.sh) to start the WSO2 server by
>>invoking CARBON_HOME/bin/wso2server.sh
>>4. Update /etc/rc.local to invoke the above bash script; init.sh
>>5. Create a VM image of this VM instance.
>>
>> Thanks
>>
>> Is there any method developed in WSO2 to overcome this situation?
>>>
>>> thanks,
>>>
>>> On Thu, Jul 21, 2016 at 5:10 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 That time is fine by me.

 thanks,

 On Thu, Jul 21, 2016 at 3:44 PM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake  > wrote:
>
>> Hi Mentors,
>>
>> I will try using Puppet.
>> It wasn't a problem with log path/pattern, in fact I used the same
>> log path that I used last time. I believe it was a bug from Azure side,
>> please check the attached screenshots.
>> Shall we please have the meeting on Friday?
>>
> +1. How about 2.00 - 3.0.0 PM on Friday?
>
>>
>> thank you,
>>
>> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Shall we have a hangout on Thursday/ Friday to discuss and
>>> demonstrate the current progress of the project? Please let us know your
>>> preference.
>>>
>>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Osura,

 On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Mentors,
>
> This is the progress so far.
>
> *Auto scaling*
>
>
> Azure supports two paradigms of auto scaling, vertical and
> horizontal. Vertical scaling, also known as scale up and scale down, 
> means
> increasing or decreasing virtual machine (VM) sizes in response to a
> workload. As I explained in one of my previous emails, vertical auto
> scaling is achieved through monitoring rules. We can set it to 
> trigger an
> alarm when certain conditions are met and also as the action we can 
> set up
> a runbook to scale up or down. I could successfully get VMs to scale 
> up and
> down using this feature.
>

 ​We would use horizontal scaling in most scenarios.​


>
> Horizontal scaling, also referred to as scale out and scale in,
> where the number of VMs is altered depending on the workload. 
> Horizontal
> scaling is achieved through virtual machine scale sets (VMSS). One
> important thing about VMSS is that the VMs included should be of the 
> same
> size and have the same OS image. All the VMs in the scale set are 
> added to
> the load balancer, as a backend pool. Backend pool is a pool of VMs 
> which
> share the traffic coming via the load balancer. We can add auto scale
> rules, as to when additional VMs should be added and removed, based 
> on the
> conditions. I could test some auto scale rules and observed VMs 
> getting
> added to the backend pool. But one problem is that 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

You can only capture a generalized VM image, so when it's being
generalized, all of the data in '/home' is erased. Since .bashrc is also in
'/home/', it's also erased. Only the data that are not
in '/home' is preserved.

Okay I will try out these steps.

Thanks,

On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne  wrote:

> Hi Osura,
>
> On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I could successfully configure auto scaling with a VM which has a WSO2
>> application server installed in it. When capturing a VM, it first get
>> deallocated and then generalized.
>>
>
> ​I'm sorry I did not get this. Can you please elaborate this further?
> ​
>
>
>> So the Java home set in .bashrc is gone in the captured image of the VM.
>> So I had to reset the Java home and also I had to manually start the server
>> after the startup of the VM.
>>
>
> ​​I think you are trying to create a VM image from a running VM instance
> and try to reuse that. Can you please try following:
>
>
>1. Create a VM instance from Ubuntu 14.04 VM image
>2. Extract JDK 1.7 (JAVA_HOME) and the WSO2 server distribution
>(CARBON_HOME) to /opt/ directory.
>3. Write a brash script (init.sh) to start the WSO2 server by invoking
>CARBON_HOME/bin/wso2server.sh
>4. Update /etc/rc.local to invoke the above bash script; init.sh
>5. Create a VM image of this VM instance.
>
> Thanks
>
> Is there any method developed in WSO2 to overcome this situation?
>>
>> thanks,
>>
>> On Thu, Jul 21, 2016 at 5:10 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> That time is fine by me.
>>>
>>> thanks,
>>>
>>> On Thu, Jul 21, 2016 at 3:44 PM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> I will try using Puppet.
> It wasn't a problem with log path/pattern, in fact I used the same log
> path that I used last time. I believe it was a bug from Azure side, please
> check the attached screenshots.
> Shall we please have the meeting on Friday?
>
 +1. How about 2.00 - 3.0.0 PM on Friday?

>
> thank you,
>
> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Shall we have a hangout on Thursday/ Friday to discuss and
>> demonstrate the current progress of the project? Please let us know your
>> preference.
>>
>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Mentors,

 This is the progress so far.

 *Auto scaling*


 Azure supports two paradigms of auto scaling, vertical and
 horizontal. Vertical scaling, also known as scale up and scale down, 
 means
 increasing or decreasing virtual machine (VM) sizes in response to a
 workload. As I explained in one of my previous emails, vertical auto
 scaling is achieved through monitoring rules. We can set it to trigger 
 an
 alarm when certain conditions are met and also as the action we can 
 set up
 a runbook to scale up or down. I could successfully get VMs to scale 
 up and
 down using this feature.

>>>
>>> ​We would use horizontal scaling in most scenarios.​
>>>
>>>

 Horizontal scaling, also referred to as scale out and scale in,
 where the number of VMs is altered depending on the workload. 
 Horizontal
 scaling is achieved through virtual machine scale sets (VMSS). One
 important thing about VMSS is that the VMs included should be of the 
 same
 size and have the same OS image. All the VMs in the scale set are 
 added to
 the load balancer, as a backend pool. Backend pool is a pool of VMs 
 which
 share the traffic coming via the load balancer. We can add auto scale
 rules, as to when additional VMs should be added and removed, based on 
 the
 conditions. I could test some auto scale rules and observed VMs getting
 added to the backend pool. But one problem is that when these VMs 
 getting
 added, it’s a whole new VM.  I’m trying to add custom made VMs which 
 has a
 wso2 product installed and configured.

>>>
>>> ​Yes we would need a VM image with required WSO2 product and
>>> pre-requisites to test this. At WSO2 we use Puppet​
>>>
>>> ​for automating the installation process [1]. With Puppet we can use
>>> one base VM image and start a VM for any WSO2 product. Puppet does the 
>>> WSO2

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

Hi Osura,

On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I could successfully configure auto scaling with a VM which has a WSO2
> application server installed in it. When capturing a VM, it first get
> deallocated and then generalized.
>

​I'm sorry I did not get this. Can you please elaborate this further?
​


> So the Java home set in .bashrc is gone in the captured image of the VM.
> So I had to reset the Java home and also I had to manually start the server
> after the startup of the VM.
>

​​I think you are trying to create a VM image from a running VM instance
and try to reuse that. Can you please try following:


   1. Create a VM instance from Ubuntu 14.04 VM image
   2. Extract JDK 1.7 (JAVA_HOME) and the WSO2 server distribution
   (CARBON_HOME) to /opt/ directory.
   3. Write a brash script (init.sh) to start the WSO2 server by invoking
   CARBON_HOME/bin/wso2server.sh
   4. Update /etc/rc.local to invoke the above bash script; init.sh
   5. Create a VM image of this VM instance.

Thanks

Is there any method developed in WSO2 to overcome this situation?
>
> thanks,
>
> On Thu, Jul 21, 2016 at 5:10 PM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> That time is fine by me.
>>
>> thanks,
>>
>> On Thu, Jul 21, 2016 at 3:44 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 I will try using Puppet.
 It wasn't a problem with log path/pattern, in fact I used the same log
 path that I used last time. I believe it was a bug from Azure side, please
 check the attached screenshots.
 Shall we please have the meeting on Friday?

>>> +1. How about 2.00 - 3.0.0 PM on Friday?
>>>

 thank you,

 On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
> the current progress of the project? Please let us know your preference.
>
> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne 
> wrote:
>
>> Hi Osura,
>>
>> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Mentors,
>>>
>>> This is the progress so far.
>>>
>>> *Auto scaling*
>>>
>>>
>>> Azure supports two paradigms of auto scaling, vertical and
>>> horizontal. Vertical scaling, also known as scale up and scale down, 
>>> means
>>> increasing or decreasing virtual machine (VM) sizes in response to a
>>> workload. As I explained in one of my previous emails, vertical auto
>>> scaling is achieved through monitoring rules. We can set it to trigger 
>>> an
>>> alarm when certain conditions are met and also as the action we can set 
>>> up
>>> a runbook to scale up or down. I could successfully get VMs to scale up 
>>> and
>>> down using this feature.
>>>
>>
>> ​We would use horizontal scaling in most scenarios.​
>>
>>
>>>
>>> Horizontal scaling, also referred to as scale out and scale in,
>>> where the number of VMs is altered depending on the workload. Horizontal
>>> scaling is achieved through virtual machine scale sets (VMSS). One
>>> important thing about VMSS is that the VMs included should be of the 
>>> same
>>> size and have the same OS image. All the VMs in the scale set are added 
>>> to
>>> the load balancer, as a backend pool. Backend pool is a pool of VMs 
>>> which
>>> share the traffic coming via the load balancer. We can add auto scale
>>> rules, as to when additional VMs should be added and removed, based on 
>>> the
>>> conditions. I could test some auto scale rules and observed VMs getting
>>> added to the backend pool. But one problem is that when these VMs 
>>> getting
>>> added, it’s a whole new VM.  I’m trying to add custom made VMs which 
>>> has a
>>> wso2 product installed and configured.
>>>
>>
>> ​Yes we would need a VM image with required WSO2 product and
>> pre-requisites to test this. At WSO2 we use Puppet​
>>
>> ​for automating the installation process [1]. With Puppet we can use
>> one base VM image and start a VM for any WSO2 product. Puppet does the 
>> WSO2
>> product installation at the VM startup.
>>
>>>
>>> Note: only a limited horizontal scaling features are supported in
>>> the azure portal yet so I’m using REST API to create and manage auto
>>> scaling features.
>>>
>>>
>>> *Centralized logging*
>>>
>>>
>>> I was able to get log to Log Analytics using custom logs. I have
>>> collected logs generated from 2 wso2 application servers. You only have 
>>> to
>>> add respective VMs to the Log analytics and 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

I could successfully configure auto scaling with a VM which has a WSO2
application server installed in it. When capturing a VM, it first get
deallocated and then generalized. So the Java home set in .bashrc is gone
in the captured image of the VM. So I had to reset the Java home and also I
had to manually start the server after the startup of the VM. Is there any
method developed in WSO2 to overcome this situation?

thanks,

On Thu, Jul 21, 2016 at 5:10 PM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> That time is fine by me.
>
> thanks,
>
> On Thu, Jul 21, 2016 at 3:44 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> I will try using Puppet.
>>> It wasn't a problem with log path/pattern, in fact I used the same log
>>> path that I used last time. I believe it was a bug from Azure side, please
>>> check the attached screenshots.
>>> Shall we please have the meeting on Friday?
>>>
>> +1. How about 2.00 - 3.0.0 PM on Friday?
>>
>>>
>>> thank you,
>>>
>>> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
 the current progress of the project? Please let us know your preference.

 On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne 
 wrote:

> Hi Osura,
>
> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> This is the progress so far.
>>
>> *Auto scaling*
>>
>>
>> Azure supports two paradigms of auto scaling, vertical and
>> horizontal. Vertical scaling, also known as scale up and scale down, 
>> means
>> increasing or decreasing virtual machine (VM) sizes in response to a
>> workload. As I explained in one of my previous emails, vertical auto
>> scaling is achieved through monitoring rules. We can set it to trigger an
>> alarm when certain conditions are met and also as the action we can set 
>> up
>> a runbook to scale up or down. I could successfully get VMs to scale up 
>> and
>> down using this feature.
>>
>
> ​We would use horizontal scaling in most scenarios.​
>
>
>>
>> Horizontal scaling, also referred to as scale out and scale in, where
>> the number of VMs is altered depending on the workload. Horizontal 
>> scaling
>> is achieved through virtual machine scale sets (VMSS). One important 
>> thing
>> about VMSS is that the VMs included should be of the same size and have 
>> the
>> same OS image. All the VMs in the scale set are added to the load 
>> balancer,
>> as a backend pool. Backend pool is a pool of VMs which share the traffic
>> coming via the load balancer. We can add auto scale rules, as to when
>> additional VMs should be added and removed, based on the conditions. I
>> could test some auto scale rules and observed VMs getting added to the
>> backend pool. But one problem is that when these VMs getting added, it’s 
>> a
>> whole new VM.  I’m trying to add custom made VMs which has a wso2 product
>> installed and configured.
>>
>
> ​Yes we would need a VM image with required WSO2 product and
> pre-requisites to test this. At WSO2 we use Puppet​
>
> ​for automating the installation process [1]. With Puppet we can use
> one base VM image and start a VM for any WSO2 product. Puppet does the 
> WSO2
> product installation at the VM startup.
>
>>
>> Note: only a limited horizontal scaling features are supported in the
>> azure portal yet so I’m using REST API to create and manage auto scaling
>> features.
>>
>>
>> *Centralized logging*
>>
>>
>> I was able to get log to Log Analytics using custom logs. I have
>> collected logs generated from 2 wso2 application servers. You only have 
>> to
>> add respective VMs to the Log analytics and set the path where logs are
>> located. This feature was under public preview, which might have been one
>> reason why it didn’t work last time when I tried.
>>
>
> ​Was the issue with the log file path/pattern?​ Did it work once you
> remove that?
>
> [1]
> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
>
> ​Thanks​
>
>>
>> Thanks,
>>
>> On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake > > wrote:
>>
>>> Hi Isuru,
>>>
>>> Please accept my apologies I have messed up names in my last email.
>>> I'm not going to be available today due to an unavoidable circumstance 
>>> so
>>> can we please have the meeting on Wednesday? Extremely sorry if it made 
>>> 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

That time is fine by me.

thanks,

On Thu, Jul 21, 2016 at 3:44 PM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I will try using Puppet.
>> It wasn't a problem with log path/pattern, in fact I used the same log
>> path that I used last time. I believe it was a bug from Azure side, please
>> check the attached screenshots.
>> Shall we please have the meeting on Friday?
>>
> +1. How about 2.00 - 3.0.0 PM on Friday?
>
>>
>> thank you,
>>
>> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
>>> the current progress of the project? Please let us know your preference.
>>>
>>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:
>>>
 Hi Osura,

 On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> This is the progress so far.
>
> *Auto scaling*
>
>
> Azure supports two paradigms of auto scaling, vertical and horizontal.
> Vertical scaling, also known as scale up and scale down, means increasing
> or decreasing virtual machine (VM) sizes in response to a workload. As I
> explained in one of my previous emails, vertical auto scaling is achieved
> through monitoring rules. We can set it to trigger an alarm when certain
> conditions are met and also as the action we can set up a runbook to scale
> up or down. I could successfully get VMs to scale up and down using this
> feature.
>

 ​We would use horizontal scaling in most scenarios.​


>
> Horizontal scaling, also referred to as scale out and scale in, where
> the number of VMs is altered depending on the workload. Horizontal scaling
> is achieved through virtual machine scale sets (VMSS). One important thing
> about VMSS is that the VMs included should be of the same size and have 
> the
> same OS image. All the VMs in the scale set are added to the load 
> balancer,
> as a backend pool. Backend pool is a pool of VMs which share the traffic
> coming via the load balancer. We can add auto scale rules, as to when
> additional VMs should be added and removed, based on the conditions. I
> could test some auto scale rules and observed VMs getting added to the
> backend pool. But one problem is that when these VMs getting added, it’s a
> whole new VM.  I’m trying to add custom made VMs which has a wso2 product
> installed and configured.
>

 ​Yes we would need a VM image with required WSO2 product and
 pre-requisites to test this. At WSO2 we use Puppet​

 ​for automating the installation process [1]. With Puppet we can use
 one base VM image and start a VM for any WSO2 product. Puppet does the WSO2
 product installation at the VM startup.

>
> Note: only a limited horizontal scaling features are supported in the
> azure portal yet so I’m using REST API to create and manage auto scaling
> features.
>
>
> *Centralized logging*
>
>
> I was able to get log to Log Analytics using custom logs. I have
> collected logs generated from 2 wso2 application servers. You only have to
> add respective VMs to the Log analytics and set the path where logs are
> located. This feature was under public preview, which might have been one
> reason why it didn’t work last time when I tried.
>

 ​Was the issue with the log file path/pattern?​ Did it work once you
 remove that?

 [1]
 https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment

 ​Thanks​

>
> Thanks,
>
> On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Please accept my apologies I have messed up names in my last email.
>> I'm not going to be available today due to an unavoidable circumstance so
>> can we please have the meeting on Wednesday? Extremely sorry if it made 
>> any
>> inconvenience. I will update you with a detailed email today for sure.
>>
>> Thanks in advance,
>>
>> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Can you send a detailed updated on the current status? Shall we have
>>> a meeting on Monday to review the progress.
>>>
>>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Imesh,

 About dynamically adding members to the load balancer, I will cross
 check it with auto-scaling. I couldn't look into that from 
 auto-scaling end
 since I couldn't test it yet.

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

Okay sure.

thanks,

On Thu, Jul 21, 2016 at 2:14 PM, Imesh Gunaratne  wrote:

>
>
> On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I will try using Puppet.
>>
>
> I think its okay to create a VM image with a specific product,
> configurations and prerequisites. We can utilize that time for adding more
> value to Azure related features.
> ​
>
>
>> It wasn't a problem with log path/pattern, in fact I used the same log
>> path that I used last time. I believe it was a bug from Azure side, please
>> check the attached screenshots.
>> Shall we please have the meeting on Friday?
>>
>> ​Right, got it!
> ​
>
>
>> thank you,
>>
>> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
>>> the current progress of the project? Please let us know your preference.
>>>
>>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:
>>>
 Hi Osura,

 On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> This is the progress so far.
>
> *Auto scaling*
>
>
> Azure supports two paradigms of auto scaling, vertical and horizontal.
> Vertical scaling, also known as scale up and scale down, means increasing
> or decreasing virtual machine (VM) sizes in response to a workload. As I
> explained in one of my previous emails, vertical auto scaling is achieved
> through monitoring rules. We can set it to trigger an alarm when certain
> conditions are met and also as the action we can set up a runbook to scale
> up or down. I could successfully get VMs to scale up and down using this
> feature.
>

 ​We would use horizontal scaling in most scenarios.​


>
> Horizontal scaling, also referred to as scale out and scale in, where
> the number of VMs is altered depending on the workload. Horizontal scaling
> is achieved through virtual machine scale sets (VMSS). One important thing
> about VMSS is that the VMs included should be of the same size and have 
> the
> same OS image. All the VMs in the scale set are added to the load 
> balancer,
> as a backend pool. Backend pool is a pool of VMs which share the traffic
> coming via the load balancer. We can add auto scale rules, as to when
> additional VMs should be added and removed, based on the conditions. I
> could test some auto scale rules and observed VMs getting added to the
> backend pool. But one problem is that when these VMs getting added, it’s a
> whole new VM.  I’m trying to add custom made VMs which has a wso2 product
> installed and configured.
>

 ​Yes we would need a VM image with required WSO2 product and
 pre-requisites to test this. At WSO2 we use Puppet​

 ​for automating the installation process [1]. With Puppet we can use
 one base VM image and start a VM for any WSO2 product. Puppet does the WSO2
 product installation at the VM startup.

>
> Note: only a limited horizontal scaling features are supported in the
> azure portal yet so I’m using REST API to create and manage auto scaling
> features.
>
>
> *Centralized logging*
>
>
> I was able to get log to Log Analytics using custom logs. I have
> collected logs generated from 2 wso2 application servers. You only have to
> add respective VMs to the Log analytics and set the path where logs are
> located. This feature was under public preview, which might have been one
> reason why it didn’t work last time when I tried.
>

 ​Was the issue with the log file path/pattern?​ Did it work once you
 remove that?

 [1]
 https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment

 ​Thanks​

>
> Thanks,
>
> On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Please accept my apologies I have messed up names in my last email.
>> I'm not going to be available today due to an unavoidable circumstance so
>> can we please have the meeting on Wednesday? Extremely sorry if it made 
>> any
>> inconvenience. I will update you with a detailed email today for sure.
>>
>> Thanks in advance,
>>
>> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Can you send a detailed updated on the current status? Shall we have
>>> a meeting on Monday to review the progress.
>>>
>>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Imesh,

 About dynamically adding members to the load balancer, I will 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I will try using Puppet.
> It wasn't a problem with log path/pattern, in fact I used the same log
> path that I used last time. I believe it was a bug from Azure side, please
> check the attached screenshots.
> Shall we please have the meeting on Friday?
>
+1. How about 2.00 - 3.0.0 PM on Friday?

>
> thank you,
>
> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
>> the current progress of the project? Please let us know your preference.
>>
>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Osura,
>>>
>>> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 This is the progress so far.

 *Auto scaling*


 Azure supports two paradigms of auto scaling, vertical and horizontal.
 Vertical scaling, also known as scale up and scale down, means increasing
 or decreasing virtual machine (VM) sizes in response to a workload. As I
 explained in one of my previous emails, vertical auto scaling is achieved
 through monitoring rules. We can set it to trigger an alarm when certain
 conditions are met and also as the action we can set up a runbook to scale
 up or down. I could successfully get VMs to scale up and down using this
 feature.

>>>
>>> ​We would use horizontal scaling in most scenarios.​
>>>
>>>

 Horizontal scaling, also referred to as scale out and scale in, where
 the number of VMs is altered depending on the workload. Horizontal scaling
 is achieved through virtual machine scale sets (VMSS). One important thing
 about VMSS is that the VMs included should be of the same size and have the
 same OS image. All the VMs in the scale set are added to the load balancer,
 as a backend pool. Backend pool is a pool of VMs which share the traffic
 coming via the load balancer. We can add auto scale rules, as to when
 additional VMs should be added and removed, based on the conditions. I
 could test some auto scale rules and observed VMs getting added to the
 backend pool. But one problem is that when these VMs getting added, it’s a
 whole new VM.  I’m trying to add custom made VMs which has a wso2 product
 installed and configured.

>>>
>>> ​Yes we would need a VM image with required WSO2 product and
>>> pre-requisites to test this. At WSO2 we use Puppet​
>>>
>>> ​for automating the installation process [1]. With Puppet we can use one
>>> base VM image and start a VM for any WSO2 product. Puppet does the WSO2
>>> product installation at the VM startup.
>>>

 Note: only a limited horizontal scaling features are supported in the
 azure portal yet so I’m using REST API to create and manage auto scaling
 features.


 *Centralized logging*


 I was able to get log to Log Analytics using custom logs. I have
 collected logs generated from 2 wso2 application servers. You only have to
 add respective VMs to the Log analytics and set the path where logs are
 located. This feature was under public preview, which might have been one
 reason why it didn’t work last time when I tried.

>>>
>>> ​Was the issue with the log file path/pattern?​ Did it work once you
>>> remove that?
>>>
>>> [1]
>>> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
>>>
>>> ​Thanks​
>>>

 Thanks,

 On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> Please accept my apologies I have messed up names in my last email.
> I'm not going to be available today due to an unavoidable circumstance so
> can we please have the meeting on Wednesday? Extremely sorry if it made 
> any
> inconvenience. I will update you with a detailed email today for sure.
>
> Thanks in advance,
>
> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you send a detailed updated on the current status? Shall we have
>> a meeting on Monday to review the progress.
>>
>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Imesh,
>>>
>>> About dynamically adding members to the load balancer, I will cross
>>> check it with auto-scaling. I couldn't look into that from auto-scaling 
>>> end
>>> since I couldn't test it yet.
>>>
>>> about monitoring, yes we can do a POC on that.
>>>
>>> thanks,
>>>
>>> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne 
>>> wrote:
>>>
 On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake <
 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Thu, Jul 21, 2016 at 11:15 AM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I will try using Puppet.
>

I think its okay to create a VM image with a specific product,
configurations and prerequisites. We can utilize that time for adding more
value to Azure related features.
​


> It wasn't a problem with log path/pattern, in fact I used the same log
> path that I used last time. I believe it was a bug from Azure side, please
> check the attached screenshots.
> Shall we please have the meeting on Friday?
>
> ​Right, got it!
​


> thank you,
>
> On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate
>> the current progress of the project? Please let us know your preference.
>>
>> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Osura,
>>>
>>> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 This is the progress so far.

 *Auto scaling*


 Azure supports two paradigms of auto scaling, vertical and horizontal.
 Vertical scaling, also known as scale up and scale down, means increasing
 or decreasing virtual machine (VM) sizes in response to a workload. As I
 explained in one of my previous emails, vertical auto scaling is achieved
 through monitoring rules. We can set it to trigger an alarm when certain
 conditions are met and also as the action we can set up a runbook to scale
 up or down. I could successfully get VMs to scale up and down using this
 feature.

>>>
>>> ​We would use horizontal scaling in most scenarios.​
>>>
>>>

 Horizontal scaling, also referred to as scale out and scale in, where
 the number of VMs is altered depending on the workload. Horizontal scaling
 is achieved through virtual machine scale sets (VMSS). One important thing
 about VMSS is that the VMs included should be of the same size and have the
 same OS image. All the VMs in the scale set are added to the load balancer,
 as a backend pool. Backend pool is a pool of VMs which share the traffic
 coming via the load balancer. We can add auto scale rules, as to when
 additional VMs should be added and removed, based on the conditions. I
 could test some auto scale rules and observed VMs getting added to the
 backend pool. But one problem is that when these VMs getting added, it’s a
 whole new VM.  I’m trying to add custom made VMs which has a wso2 product
 installed and configured.

>>>
>>> ​Yes we would need a VM image with required WSO2 product and
>>> pre-requisites to test this. At WSO2 we use Puppet​
>>>
>>> ​for automating the installation process [1]. With Puppet we can use one
>>> base VM image and start a VM for any WSO2 product. Puppet does the WSO2
>>> product installation at the VM startup.
>>>

 Note: only a limited horizontal scaling features are supported in the
 azure portal yet so I’m using REST API to create and manage auto scaling
 features.


 *Centralized logging*


 I was able to get log to Log Analytics using custom logs. I have
 collected logs generated from 2 wso2 application servers. You only have to
 add respective VMs to the Log analytics and set the path where logs are
 located. This feature was under public preview, which might have been one
 reason why it didn’t work last time when I tried.

>>>
>>> ​Was the issue with the log file path/pattern?​ Did it work once you
>>> remove that?
>>>
>>> [1]
>>> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
>>>
>>> ​Thanks​
>>>

 Thanks,

 On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> Please accept my apologies I have messed up names in my last email.
> I'm not going to be available today due to an unavoidable circumstance so
> can we please have the meeting on Wednesday? Extremely sorry if it made 
> any
> inconvenience. I will update you with a detailed email today for sure.
>
> Thanks in advance,
>
> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you send a detailed updated on the current status? Shall we have
>> a meeting on Monday to review the progress.
>>
>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Imesh,
>>>
>>> About dynamically adding members to the load balancer, I will cross
>>> check it with auto-scaling. I couldn't look into that from auto-scaling 
>>> end
>>> since I couldn't test it yet.
>>>
>>> about monitoring, yes we can do a POC on that.
>>>
>>> thanks,
>>>
>>> On Tue, Jul 12, 2016 at 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

I will try using Puppet.
It wasn't a problem with log path/pattern, in fact I used the same log path
that I used last time. I believe it was a bug from Azure side, please check
the attached screenshots.
Shall we please have the meeting on Friday?

thank you,

On Wed, Jul 20, 2016 at 6:50 PM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> Shall we have a hangout on Thursday/ Friday to discuss and demonstrate the
> current progress of the project? Please let us know your preference.
>
> On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:
>
>> Hi Osura,
>>
>> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> This is the progress so far.
>>>
>>> *Auto scaling*
>>>
>>>
>>> Azure supports two paradigms of auto scaling, vertical and horizontal.
>>> Vertical scaling, also known as scale up and scale down, means increasing
>>> or decreasing virtual machine (VM) sizes in response to a workload. As I
>>> explained in one of my previous emails, vertical auto scaling is achieved
>>> through monitoring rules. We can set it to trigger an alarm when certain
>>> conditions are met and also as the action we can set up a runbook to scale
>>> up or down. I could successfully get VMs to scale up and down using this
>>> feature.
>>>
>>
>> ​We would use horizontal scaling in most scenarios.​
>>
>>
>>>
>>> Horizontal scaling, also referred to as scale out and scale in, where
>>> the number of VMs is altered depending on the workload. Horizontal scaling
>>> is achieved through virtual machine scale sets (VMSS). One important thing
>>> about VMSS is that the VMs included should be of the same size and have the
>>> same OS image. All the VMs in the scale set are added to the load balancer,
>>> as a backend pool. Backend pool is a pool of VMs which share the traffic
>>> coming via the load balancer. We can add auto scale rules, as to when
>>> additional VMs should be added and removed, based on the conditions. I
>>> could test some auto scale rules and observed VMs getting added to the
>>> backend pool. But one problem is that when these VMs getting added, it’s a
>>> whole new VM.  I’m trying to add custom made VMs which has a wso2 product
>>> installed and configured.
>>>
>>
>> ​Yes we would need a VM image with required WSO2 product and
>> pre-requisites to test this. At WSO2 we use Puppet​
>>
>> ​for automating the installation process [1]. With Puppet we can use one
>> base VM image and start a VM for any WSO2 product. Puppet does the WSO2
>> product installation at the VM startup.
>>
>>>
>>> Note: only a limited horizontal scaling features are supported in the
>>> azure portal yet so I’m using REST API to create and manage auto scaling
>>> features.
>>>
>>>
>>> *Centralized logging*
>>>
>>>
>>> I was able to get log to Log Analytics using custom logs. I have
>>> collected logs generated from 2 wso2 application servers. You only have to
>>> add respective VMs to the Log analytics and set the path where logs are
>>> located. This feature was under public preview, which might have been one
>>> reason why it didn’t work last time when I tried.
>>>
>>
>> ​Was the issue with the log file path/pattern?​ Did it work once you
>> remove that?
>>
>> [1]
>> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
>>
>> ​Thanks​
>>
>>>
>>> Thanks,
>>>
>>> On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Please accept my apologies I have messed up names in my last email. I'm
 not going to be available today due to an unavoidable circumstance so can
 we please have the meeting on Wednesday? Extremely sorry if it made any
 inconvenience. I will update you with a detailed email today for sure.

 Thanks in advance,

 On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Can you send a detailed updated on the current status? Shall we have a
> meeting on Monday to review the progress.
>
> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh,
>>
>> About dynamically adding members to the load balancer, I will cross
>> check it with auto-scaling. I couldn't look into that from auto-scaling 
>> end
>> since I couldn't test it yet.
>>
>> about monitoring, yes we can do a POC on that.
>>
>> thanks,
>>
>> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne 
>> wrote:
>>
>>> On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Imesh,

 About centralized logging, I'm trying to get logs to the Log
 Analytics using few methods supported in azure. We can either parse 
 logs in
 to syslogs and send to the Log Analytics or create custom 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

Shall we have a hangout on Thursday/ Friday to discuss and demonstrate the
current progress of the project? Please let us know your preference.

On Wed, Jul 20, 2016 at 3:35 PM, Imesh Gunaratne  wrote:

> Hi Osura,
>
> On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> This is the progress so far.
>>
>> *Auto scaling*
>>
>>
>> Azure supports two paradigms of auto scaling, vertical and horizontal.
>> Vertical scaling, also known as scale up and scale down, means increasing
>> or decreasing virtual machine (VM) sizes in response to a workload. As I
>> explained in one of my previous emails, vertical auto scaling is achieved
>> through monitoring rules. We can set it to trigger an alarm when certain
>> conditions are met and also as the action we can set up a runbook to scale
>> up or down. I could successfully get VMs to scale up and down using this
>> feature.
>>
>
> ​We would use horizontal scaling in most scenarios.​
>
>
>>
>> Horizontal scaling, also referred to as scale out and scale in, where the
>> number of VMs is altered depending on the workload. Horizontal scaling is
>> achieved through virtual machine scale sets (VMSS). One important thing
>> about VMSS is that the VMs included should be of the same size and have the
>> same OS image. All the VMs in the scale set are added to the load balancer,
>> as a backend pool. Backend pool is a pool of VMs which share the traffic
>> coming via the load balancer. We can add auto scale rules, as to when
>> additional VMs should be added and removed, based on the conditions. I
>> could test some auto scale rules and observed VMs getting added to the
>> backend pool. But one problem is that when these VMs getting added, it’s a
>> whole new VM.  I’m trying to add custom made VMs which has a wso2 product
>> installed and configured.
>>
>
> ​Yes we would need a VM image with required WSO2 product and
> pre-requisites to test this. At WSO2 we use Puppet​
>
> ​for automating the installation process [1]. With Puppet we can use one
> base VM image and start a VM for any WSO2 product. Puppet does the WSO2
> product installation at the VM startup.
>
>>
>> Note: only a limited horizontal scaling features are supported in the
>> azure portal yet so I’m using REST API to create and manage auto scaling
>> features.
>>
>>
>> *Centralized logging*
>>
>>
>> I was able to get log to Log Analytics using custom logs. I have
>> collected logs generated from 2 wso2 application servers. You only have to
>> add respective VMs to the Log analytics and set the path where logs are
>> located. This feature was under public preview, which might have been one
>> reason why it didn’t work last time when I tried.
>>
>
> ​Was the issue with the log file path/pattern?​ Did it work once you
> remove that?
>
> [1]
> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
>
> ​Thanks​
>
>>
>> Thanks,
>>
>> On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Please accept my apologies I have messed up names in my last email. I'm
>>> not going to be available today due to an unavoidable circumstance so can
>>> we please have the meeting on Wednesday? Extremely sorry if it made any
>>> inconvenience. I will update you with a detailed email today for sure.
>>>
>>> Thanks in advance,
>>>
>>> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Can you send a detailed updated on the current status? Shall we have a
 meeting on Monday to review the progress.

 On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake 
 wrote:

> Hi Imesh,
>
> About dynamically adding members to the load balancer, I will cross
> check it with auto-scaling. I couldn't look into that from auto-scaling 
> end
> since I couldn't test it yet.
>
> about monitoring, yes we can do a POC on that.
>
> thanks,
>
> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne 
> wrote:
>
>> On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Hi Imesh,
>>>
>>> About centralized logging, I'm trying to get logs to the Log
>>> Analytics using few methods supported in azure. We can either parse 
>>> logs in
>>> to syslogs and send to the Log Analytics or create custom logs 
>>> specifying
>>> the logs location. As you said, logs shouldn't be in .txt extension, I 
>>> got
>>> it clarified from a azure blog. Will update you soon after I could 
>>> resolve
>>> it.
>>>
>>> ​Right, thanks for the update!​
>>
>>
>>> No you can't dynamically add VMs to the load balancer. Backend pool,
>>> where all the VMs reside, should be predefined.
>>>
>>
>> ​Technically that capability should be there. 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

Hi Osura,

On Mon, Jul 18, 2016 at 4:20 PM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> This is the progress so far.
>
> *Auto scaling*
>
>
> Azure supports two paradigms of auto scaling, vertical and horizontal.
> Vertical scaling, also known as scale up and scale down, means increasing
> or decreasing virtual machine (VM) sizes in response to a workload. As I
> explained in one of my previous emails, vertical auto scaling is achieved
> through monitoring rules. We can set it to trigger an alarm when certain
> conditions are met and also as the action we can set up a runbook to scale
> up or down. I could successfully get VMs to scale up and down using this
> feature.
>

​We would use horizontal scaling in most scenarios.​


>
> Horizontal scaling, also referred to as scale out and scale in, where the
> number of VMs is altered depending on the workload. Horizontal scaling is
> achieved through virtual machine scale sets (VMSS). One important thing
> about VMSS is that the VMs included should be of the same size and have the
> same OS image. All the VMs in the scale set are added to the load balancer,
> as a backend pool. Backend pool is a pool of VMs which share the traffic
> coming via the load balancer. We can add auto scale rules, as to when
> additional VMs should be added and removed, based on the conditions. I
> could test some auto scale rules and observed VMs getting added to the
> backend pool. But one problem is that when these VMs getting added, it’s a
> whole new VM.  I’m trying to add custom made VMs which has a wso2 product
> installed and configured.
>

​Yes we would need a VM image with required WSO2 product and pre-requisites
to test this. At WSO2 we use Puppet​

​for automating the installation process [1]. With Puppet we can use one
base VM image and start a VM for any WSO2 product. Puppet does the WSO2
product installation at the VM startup.

>
> Note: only a limited horizontal scaling features are supported in the
> azure portal yet so I’m using REST API to create and manage auto scaling
> features.
>
>
> *Centralized logging*
>
>
> I was able to get log to Log Analytics using custom logs. I have collected
> logs generated from 2 wso2 application servers. You only have to add
> respective VMs to the Log analytics and set the path where logs are
> located. This feature was under public preview, which might have been one
> reason why it didn’t work last time when I tried.
>

​Was the issue with the log file path/pattern?​ Did it work once you remove
that?

[1]
https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment

​Thanks​

>
> Thanks,
>
> On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Please accept my apologies I have messed up names in my last email. I'm
>> not going to be available today due to an unavoidable circumstance so can
>> we please have the meeting on Wednesday? Extremely sorry if it made any
>> inconvenience. I will update you with a detailed email today for sure.
>>
>> Thanks in advance,
>>
>> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Can you send a detailed updated on the current status? Shall we have a
>>> meeting on Monday to review the progress.
>>>
>>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Imesh,

 About dynamically adding members to the load balancer, I will cross
 check it with auto-scaling. I couldn't look into that from auto-scaling end
 since I couldn't test it yet.

 about monitoring, yes we can do a POC on that.

 thanks,

 On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne 
 wrote:

> On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake  > wrote:
>
>> Hi Imesh,
>>
>> About centralized logging, I'm trying to get logs to the Log
>> Analytics using few methods supported in azure. We can either parse logs 
>> in
>> to syslogs and send to the Log Analytics or create custom logs specifying
>> the logs location. As you said, logs shouldn't be in .txt extension, I 
>> got
>> it clarified from a azure blog. Will update you soon after I could 
>> resolve
>> it.
>>
>> ​Right, thanks for the update!​
>
>
>> No you can't dynamically add VMs to the load balancer. Backend pool,
>> where all the VMs reside, should be predefined.
>>
>
> ​Technically that capability should be there. Otherwise we would not
> be able to autoscale a server cluster dynamically.
> ​
>
>
>> you can auto-scale using scale sets(I'm still researching about it),
>> that's the equivalent of AWS auto scaling group . also you can scale up 
>> or
>> down a VM if it exceeds a certain parameter like CPU usage, using
>> monitoring rules.
>>
>> *Monitoring *

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

This is the progress so far.

*Auto scaling*


Azure supports two paradigms of auto scaling, vertical and horizontal.
Vertical scaling, also known as scale up and scale down, means increasing
or decreasing virtual machine (VM) sizes in response to a workload. As I
explained in one of my previous emails, vertical auto scaling is achieved
through monitoring rules. We can set it to trigger an alarm when certain
conditions are met and also as the action we can set up a runbook to scale
up or down. I could successfully get VMs to scale up and down using this
feature.


Horizontal scaling, also referred to as scale out and scale in, where the
number of VMs is altered depending on the workload. Horizontal scaling is
achieved through virtual machine scale sets (VMSS). One important thing
about VMSS is that the VMs included should be of the same size and have the
same OS image. All the VMs in the scale set are added to the load balancer,
as a backend pool. Backend pool is a pool of VMs which share the traffic
coming via the load balancer. We can add auto scale rules, as to when
additional VMs should be added and removed, based on the conditions. I
could test some auto scale rules and observed VMs getting added to the
backend pool. But one problem is that when these VMs getting added, it’s a
whole new VM.  I’m trying to add custom made VMs which has a wso2 product
installed and configured.


Note: only a limited horizontal scaling features are supported in the azure
portal yet so I’m using REST API to create and manage auto scaling features.


*Centralized logging*


I was able to get log to Log Analytics using custom logs. I have collected
logs generated from 2 wso2 application servers. You only have to add
respective VMs to the Log analytics and set the path where logs are
located. This feature was under public preview, which might have been one
reason why it didn’t work last time when I tried.


Thanks,

On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Please accept my apologies I have messed up names in my last email. I'm
> not going to be available today due to an unavoidable circumstance so can
> we please have the meeting on Wednesday? Extremely sorry if it made any
> inconvenience. I will update you with a detailed email today for sure.
>
> Thanks in advance,
>
> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you send a detailed updated on the current status? Shall we have a
>> meeting on Monday to review the progress.
>>
>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> About dynamically adding members to the load balancer, I will cross
>>> check it with auto-scaling. I couldn't look into that from auto-scaling end
>>> since I couldn't test it yet.
>>>
>>> about monitoring, yes we can do a POC on that.
>>>
>>> thanks,
>>>
>>> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne 
>>> wrote:
>>>
 On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake 
 wrote:

> Hi Imesh,
>
> About centralized logging, I'm trying to get logs to the Log Analytics
> using few methods supported in azure. We can either parse logs in to
> syslogs and send to the Log Analytics or create custom logs specifying the
> logs location. As you said, logs shouldn't be in .txt extension, I got it
> clarified from a azure blog. Will update you soon after I could resolve 
> it.
>
> ​Right, thanks for the update!​


> No you can't dynamically add VMs to the load balancer. Backend pool,
> where all the VMs reside, should be predefined.
>

 ​Technically that capability should be there. Otherwise we would not be
 able to autoscale a server cluster dynamically.
 ​


> you can auto-scale using scale sets(I'm still researching about it),
> that's the equivalent of AWS auto scaling group . also you can scale up or
> down a VM if it exceeds a certain parameter like CPU usage, using
> monitoring rules.
>
> *Monitoring *
>
>
> Azure has a native monitoring tool which involves collecting and
> tracking metrics, analyzing log files, defining custom metrics and logging
> generated by specific applications or workloads running in Virtual
> Machines. Azure represents monitored data in a graphical manner using
> charts. Monitoring also facilitates triggering alarms when certain
> conditions are met and also it can be configured to take actions on the 
> met
> conditions. Monitoring is done by the Diagnostic Extension and it has
> following capabilities.
>
> · Collects and uploads the system performance information
> from the Linux VM to the user's storage table, including diagnostic and
> syslog information.
>
> · Enables users to customize the data metrics 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Please accept my apologies I have messed up names in my last email. I'm not
going to be available today due to an unavoidable circumstance so can we
please have the meeting on Wednesday? Extremely sorry if it made any
inconvenience. I will update you with a detailed email today for sure.

Thanks in advance,

On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> Can you send a detailed updated on the current status? Shall we have a
> meeting on Monday to review the progress.
>
> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh,
>>
>> About dynamically adding members to the load balancer, I will cross check
>> it with auto-scaling. I couldn't look into that from auto-scaling end since
>> I couldn't test it yet.
>>
>> about monitoring, yes we can do a POC on that.
>>
>> thanks,
>>
>> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne  wrote:
>>
>>> On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Imesh,

 About centralized logging, I'm trying to get logs to the Log Analytics
 using few methods supported in azure. We can either parse logs in to
 syslogs and send to the Log Analytics or create custom logs specifying the
 logs location. As you said, logs shouldn't be in .txt extension, I got it
 clarified from a azure blog. Will update you soon after I could resolve it.

 ​Right, thanks for the update!​
>>>
>>>
 No you can't dynamically add VMs to the load balancer. Backend pool,
 where all the VMs reside, should be predefined.

>>>
>>> ​Technically that capability should be there. Otherwise we would not be
>>> able to autoscale a server cluster dynamically.
>>> ​
>>>
>>>
 you can auto-scale using scale sets(I'm still researching about it),
 that's the equivalent of AWS auto scaling group . also you can scale up or
 down a VM if it exceeds a certain parameter like CPU usage, using
 monitoring rules.

 *Monitoring *


 Azure has a native monitoring tool which involves collecting and
 tracking metrics, analyzing log files, defining custom metrics and logging
 generated by specific applications or workloads running in Virtual
 Machines. Azure represents monitored data in a graphical manner using
 charts. Monitoring also facilitates triggering alarms when certain
 conditions are met and also it can be configured to take actions on the met
 conditions. Monitoring is done by the Diagnostic Extension and it has
 following capabilities.

 · Collects and uploads the system performance information from
 the Linux VM to the user's storage table, including diagnostic and syslog
 information.

 · Enables users to customize the data metrics that will be
 collected and uploaded.

 · Enables users to upload specified log files to a designated
 storage table.

 Note: Azure storage tables are a non-relational, key-value-pair,
 storage system suitable for storing massive amounts of unstructured data.


 We can add monitor rules so that when an alert triggers it notifies the
 admins via email. Furthermore we can set to take automated actions. Azure
 automate actions by running runbooks. A runbook is a set of tasks that
 perform some automated process in Azure Automation. We can create our own
 runbooks as well. Available runbooks include,

 · Restart VM

 · Stop VM

 · Remove VM

 · Scale up VM

 · Scale down VM

 When scaling up it sets the virtual machine to the next larger size
 within the size group and when scaling down it sets the virtual machine to
 the next smaller size within the size group.

 More about runbooks and automation [1]

>>>
>>> ​Sounds good, will us be able to do a POC on this?​
>>>
>>>

 *Auto scaling *


 Auto-scaling is the process of dynamically allocating the resources
 required by an application to match performance requirements. Virtual
 machine scale sets are an Azure Compute resource you can use to deploy and
 manage a set of identical VMs. With all VMs configured the same, VM scale
 sets are designed to support true auto-scale  no pre-provisioning of VMs is
 required – and as such makes it easier to build large-scale services
 targeting big compute, big data, and containerized workloads [2].


 Note: I couldn’t practically do this as my azure free account lets me
 have only 4 cores and I have used all of them on my current deployment. I’m
 getting a new azure account from one of my friends in a day so hopefully I
 will do this on it and update you.

>>>
>>> ​Great! Thanks!​
>>>
>>>

 [1]
 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Sun, Jul 17, 2016 at 8:46 AM, Osura Rathnayake 
wrote:

> Hi Imesh,
>
>  I think it was Isuru who asked this :-)​



> Sure we shall have a meeting on Monday to review the progress. I will send
> a detailed update on the current status by tonight. Sorry for the delay.
>

​+1

>
> Thanks,
>
> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you send a detailed updated on the current status? Shall we have a
>> meeting on Monday to review the progress.
>>
>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> About dynamically adding members to the load balancer, I will cross
>>> check it with auto-scaling. I couldn't look into that from auto-scaling end
>>> since I couldn't test it yet.
>>>
>>> about monitoring, yes we can do a POC on that.
>>>
>>> thanks,
>>>
>>> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne 
>>> wrote:
>>>
 On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake 
 wrote:

> Hi Imesh,
>
> About centralized logging, I'm trying to get logs to the Log Analytics
> using few methods supported in azure. We can either parse logs in to
> syslogs and send to the Log Analytics or create custom logs specifying the
> logs location. As you said, logs shouldn't be in .txt extension, I got it
> clarified from a azure blog. Will update you soon after I could resolve 
> it.
>
> ​Right, thanks for the update!​


> No you can't dynamically add VMs to the load balancer. Backend pool,
> where all the VMs reside, should be predefined.
>

 ​Technically that capability should be there. Otherwise we would not be
 able to autoscale a server cluster dynamically.
 ​


> you can auto-scale using scale sets(I'm still researching about it),
> that's the equivalent of AWS auto scaling group . also you can scale up or
> down a VM if it exceeds a certain parameter like CPU usage, using
> monitoring rules.
>
> *Monitoring *
>
>
> Azure has a native monitoring tool which involves collecting and
> tracking metrics, analyzing log files, defining custom metrics and logging
> generated by specific applications or workloads running in Virtual
> Machines. Azure represents monitored data in a graphical manner using
> charts. Monitoring also facilitates triggering alarms when certain
> conditions are met and also it can be configured to take actions on the 
> met
> conditions. Monitoring is done by the Diagnostic Extension and it has
> following capabilities.
>
> · Collects and uploads the system performance information
> from the Linux VM to the user's storage table, including diagnostic and
> syslog information.
>
> · Enables users to customize the data metrics that will be
> collected and uploaded.
>
> · Enables users to upload specified log files to a designated
> storage table.
>
> Note: Azure storage tables are a non-relational, key-value-pair,
> storage system suitable for storing massive amounts of unstructured data.
>
>
> We can add monitor rules so that when an alert triggers it notifies
> the admins via email. Furthermore we can set to take automated actions.
> Azure automate actions by running runbooks. A runbook is a set of tasks
> that perform some automated process in Azure Automation. We can create our
> own runbooks as well. Available runbooks include,
>
> · Restart VM
>
> · Stop VM
>
> · Remove VM
>
> · Scale up VM
>
> · Scale down VM
>
> When scaling up it sets the virtual machine to the next larger size
> within the size group and when scaling down it sets the virtual machine to
> the next smaller size within the size group.
>
> More about runbooks and automation [1]
>

 ​Sounds good, will us be able to do a POC on this?​


>
> *Auto scaling *
>
>
> Auto-scaling is the process of dynamically allocating the resources
> required by an application to match performance requirements. Virtual
> machine scale sets are an Azure Compute resource you can use to deploy and
> manage a set of identical VMs. With all VMs configured the same, VM scale
> sets are designed to support true auto-scale  no pre-provisioning of VMs 
> is
> required – and as such makes it easier to build large-scale services
> targeting big compute, big data, and containerized workloads [2].
>
>
> Note: I couldn’t practically do this as my azure free account lets me
> have only 4 cores and I have used all of them on my current deployment. 
> I’m
> getting a new azure account from one of my friends in a day so hopefully I
> will do 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

Sure we shall have a meeting on Monday to review the progress. I will send
a detailed update on the current status by tonight. Sorry for the delay.

Thanks,

On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> Can you send a detailed updated on the current status? Shall we have a
> meeting on Monday to review the progress.
>
> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh,
>>
>> About dynamically adding members to the load balancer, I will cross check
>> it with auto-scaling. I couldn't look into that from auto-scaling end since
>> I couldn't test it yet.
>>
>> about monitoring, yes we can do a POC on that.
>>
>> thanks,
>>
>> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne  wrote:
>>
>>> On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Imesh,

 About centralized logging, I'm trying to get logs to the Log Analytics
 using few methods supported in azure. We can either parse logs in to
 syslogs and send to the Log Analytics or create custom logs specifying the
 logs location. As you said, logs shouldn't be in .txt extension, I got it
 clarified from a azure blog. Will update you soon after I could resolve it.

 ​Right, thanks for the update!​
>>>
>>>
 No you can't dynamically add VMs to the load balancer. Backend pool,
 where all the VMs reside, should be predefined.

>>>
>>> ​Technically that capability should be there. Otherwise we would not be
>>> able to autoscale a server cluster dynamically.
>>> ​
>>>
>>>
 you can auto-scale using scale sets(I'm still researching about it),
 that's the equivalent of AWS auto scaling group . also you can scale up or
 down a VM if it exceeds a certain parameter like CPU usage, using
 monitoring rules.

 *Monitoring *


 Azure has a native monitoring tool which involves collecting and
 tracking metrics, analyzing log files, defining custom metrics and logging
 generated by specific applications or workloads running in Virtual
 Machines. Azure represents monitored data in a graphical manner using
 charts. Monitoring also facilitates triggering alarms when certain
 conditions are met and also it can be configured to take actions on the met
 conditions. Monitoring is done by the Diagnostic Extension and it has
 following capabilities.

 · Collects and uploads the system performance information from
 the Linux VM to the user's storage table, including diagnostic and syslog
 information.

 · Enables users to customize the data metrics that will be
 collected and uploaded.

 · Enables users to upload specified log files to a designated
 storage table.

 Note: Azure storage tables are a non-relational, key-value-pair,
 storage system suitable for storing massive amounts of unstructured data.


 We can add monitor rules so that when an alert triggers it notifies the
 admins via email. Furthermore we can set to take automated actions. Azure
 automate actions by running runbooks. A runbook is a set of tasks that
 perform some automated process in Azure Automation. We can create our own
 runbooks as well. Available runbooks include,

 · Restart VM

 · Stop VM

 · Remove VM

 · Scale up VM

 · Scale down VM

 When scaling up it sets the virtual machine to the next larger size
 within the size group and when scaling down it sets the virtual machine to
 the next smaller size within the size group.

 More about runbooks and automation [1]

>>>
>>> ​Sounds good, will us be able to do a POC on this?​
>>>
>>>

 *Auto scaling *


 Auto-scaling is the process of dynamically allocating the resources
 required by an application to match performance requirements. Virtual
 machine scale sets are an Azure Compute resource you can use to deploy and
 manage a set of identical VMs. With all VMs configured the same, VM scale
 sets are designed to support true auto-scale  no pre-provisioning of VMs is
 required – and as such makes it easier to build large-scale services
 targeting big compute, big data, and containerized workloads [2].


 Note: I couldn’t practically do this as my azure free account lets me
 have only 4 cores and I have used all of them on my current deployment. I’m
 getting a new azure account from one of my friends in a day so hopefully I
 will do this on it and update you.

>>>
>>> ​Great! Thanks!​
>>>
>>>

 [1]
 https://azure.microsoft.com/en-us/documentation/articles/automation-intro/

 [2]
 https://azure.microsoft.com/en-us/documentation/articles/virtual-machine-scale-sets-overview/


 thanks,

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

Can you send a detailed updated on the current status? Shall we have a
meeting on Monday to review the progress.

On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake 
wrote:

> Hi Imesh,
>
> About dynamically adding members to the load balancer, I will cross check
> it with auto-scaling. I couldn't look into that from auto-scaling end since
> I couldn't test it yet.
>
> about monitoring, yes we can do a POC on that.
>
> thanks,
>
> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne  wrote:
>
>> On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> About centralized logging, I'm trying to get logs to the Log Analytics
>>> using few methods supported in azure. We can either parse logs in to
>>> syslogs and send to the Log Analytics or create custom logs specifying the
>>> logs location. As you said, logs shouldn't be in .txt extension, I got it
>>> clarified from a azure blog. Will update you soon after I could resolve it.
>>>
>>> ​Right, thanks for the update!​
>>
>>
>>> No you can't dynamically add VMs to the load balancer. Backend pool,
>>> where all the VMs reside, should be predefined.
>>>
>>
>> ​Technically that capability should be there. Otherwise we would not be
>> able to autoscale a server cluster dynamically.
>> ​
>>
>>
>>> you can auto-scale using scale sets(I'm still researching about it),
>>> that's the equivalent of AWS auto scaling group . also you can scale up or
>>> down a VM if it exceeds a certain parameter like CPU usage, using
>>> monitoring rules.
>>>
>>> *Monitoring *
>>>
>>>
>>> Azure has a native monitoring tool which involves collecting and
>>> tracking metrics, analyzing log files, defining custom metrics and logging
>>> generated by specific applications or workloads running in Virtual
>>> Machines. Azure represents monitored data in a graphical manner using
>>> charts. Monitoring also facilitates triggering alarms when certain
>>> conditions are met and also it can be configured to take actions on the met
>>> conditions. Monitoring is done by the Diagnostic Extension and it has
>>> following capabilities.
>>>
>>> · Collects and uploads the system performance information from
>>> the Linux VM to the user's storage table, including diagnostic and syslog
>>> information.
>>>
>>> · Enables users to customize the data metrics that will be
>>> collected and uploaded.
>>>
>>> · Enables users to upload specified log files to a designated
>>> storage table.
>>>
>>> Note: Azure storage tables are a non-relational, key-value-pair, storage
>>> system suitable for storing massive amounts of unstructured data.
>>>
>>>
>>> We can add monitor rules so that when an alert triggers it notifies the
>>> admins via email. Furthermore we can set to take automated actions. Azure
>>> automate actions by running runbooks. A runbook is a set of tasks that
>>> perform some automated process in Azure Automation. We can create our own
>>> runbooks as well. Available runbooks include,
>>>
>>> · Restart VM
>>>
>>> · Stop VM
>>>
>>> · Remove VM
>>>
>>> · Scale up VM
>>>
>>> · Scale down VM
>>>
>>> When scaling up it sets the virtual machine to the next larger size
>>> within the size group and when scaling down it sets the virtual machine to
>>> the next smaller size within the size group.
>>>
>>> More about runbooks and automation [1]
>>>
>>
>> ​Sounds good, will us be able to do a POC on this?​
>>
>>
>>>
>>> *Auto scaling *
>>>
>>>
>>> Auto-scaling is the process of dynamically allocating the resources
>>> required by an application to match performance requirements. Virtual
>>> machine scale sets are an Azure Compute resource you can use to deploy and
>>> manage a set of identical VMs. With all VMs configured the same, VM scale
>>> sets are designed to support true auto-scale  no pre-provisioning of VMs is
>>> required – and as such makes it easier to build large-scale services
>>> targeting big compute, big data, and containerized workloads [2].
>>>
>>>
>>> Note: I couldn’t practically do this as my azure free account lets me
>>> have only 4 cores and I have used all of them on my current deployment. I’m
>>> getting a new azure account from one of my friends in a day so hopefully I
>>> will do this on it and update you.
>>>
>>
>> ​Great! Thanks!​
>>
>>
>>>
>>> [1]
>>> https://azure.microsoft.com/en-us/documentation/articles/automation-intro/
>>>
>>> [2]
>>> https://azure.microsoft.com/en-us/documentation/articles/virtual-machine-scale-sets-overview/
>>>
>>>
>>> thanks,
>>>
>>>
>>> On Mon, Jul 11, 2016 at 9:54 AM, Imesh Gunaratne  wrote:
>>>
 On Thu, Jul 7, 2016 at 7:11 PM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
>
> In addition to refining the membership scheme code, I looked into
> following features of Azure.
> ​
>
 ​Good findings Osura, please find few questions 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

About dynamically adding members to the load balancer, I will cross check
it with auto-scaling. I couldn't look into that from auto-scaling end since
I couldn't test it yet.

about monitoring, yes we can do a POC on that.

thanks,

On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne  wrote:

> On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh,
>>
>> About centralized logging, I'm trying to get logs to the Log Analytics
>> using few methods supported in azure. We can either parse logs in to
>> syslogs and send to the Log Analytics or create custom logs specifying the
>> logs location. As you said, logs shouldn't be in .txt extension, I got it
>> clarified from a azure blog. Will update you soon after I could resolve it.
>>
>> ​Right, thanks for the update!​
>
>
>> No you can't dynamically add VMs to the load balancer. Backend pool,
>> where all the VMs reside, should be predefined.
>>
>
> ​Technically that capability should be there. Otherwise we would not be
> able to autoscale a server cluster dynamically.
> ​
>
>
>> you can auto-scale using scale sets(I'm still researching about it),
>> that's the equivalent of AWS auto scaling group . also you can scale up or
>> down a VM if it exceeds a certain parameter like CPU usage, using
>> monitoring rules.
>>
>> *Monitoring *
>>
>>
>> Azure has a native monitoring tool which involves collecting and tracking
>> metrics, analyzing log files, defining custom metrics and logging generated
>> by specific applications or workloads running in Virtual Machines. Azure
>> represents monitored data in a graphical manner using charts. Monitoring
>> also facilitates triggering alarms when certain conditions are met and also
>> it can be configured to take actions on the met conditions. Monitoring is
>> done by the Diagnostic Extension and it has following capabilities.
>>
>> · Collects and uploads the system performance information from
>> the Linux VM to the user's storage table, including diagnostic and syslog
>> information.
>>
>> · Enables users to customize the data metrics that will be
>> collected and uploaded.
>>
>> · Enables users to upload specified log files to a designated
>> storage table.
>>
>> Note: Azure storage tables are a non-relational, key-value-pair, storage
>> system suitable for storing massive amounts of unstructured data.
>>
>>
>> We can add monitor rules so that when an alert triggers it notifies the
>> admins via email. Furthermore we can set to take automated actions. Azure
>> automate actions by running runbooks. A runbook is a set of tasks that
>> perform some automated process in Azure Automation. We can create our own
>> runbooks as well. Available runbooks include,
>>
>> · Restart VM
>>
>> · Stop VM
>>
>> · Remove VM
>>
>> · Scale up VM
>>
>> · Scale down VM
>>
>> When scaling up it sets the virtual machine to the next larger size
>> within the size group and when scaling down it sets the virtual machine to
>> the next smaller size within the size group.
>>
>> More about runbooks and automation [1]
>>
>
> ​Sounds good, will us be able to do a POC on this?​
>
>
>>
>> *Auto scaling *
>>
>>
>> Auto-scaling is the process of dynamically allocating the resources
>> required by an application to match performance requirements. Virtual
>> machine scale sets are an Azure Compute resource you can use to deploy and
>> manage a set of identical VMs. With all VMs configured the same, VM scale
>> sets are designed to support true auto-scale  no pre-provisioning of VMs is
>> required – and as such makes it easier to build large-scale services
>> targeting big compute, big data, and containerized workloads [2].
>>
>>
>> Note: I couldn’t practically do this as my azure free account lets me
>> have only 4 cores and I have used all of them on my current deployment. I’m
>> getting a new azure account from one of my friends in a day so hopefully I
>> will do this on it and update you.
>>
>
> ​Great! Thanks!​
>
>
>>
>> [1]
>> https://azure.microsoft.com/en-us/documentation/articles/automation-intro/
>>
>> [2]
>> https://azure.microsoft.com/en-us/documentation/articles/virtual-machine-scale-sets-overview/
>>
>>
>> thanks,
>>
>>
>> On Mon, Jul 11, 2016 at 9:54 AM, Imesh Gunaratne  wrote:
>>
>>> On Thu, Jul 7, 2016 at 7:11 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,


 In addition to refining the membership scheme code, I looked into
 following features of Azure.
 ​

>>> ​Good findings Osura, please find few questions inline:​
>>>
>>>
 ​

 *Azure dynamic load balancing*


 Azure has a native load balancer which is very easy to configure. It’s
 a layer 4 (TCP, UDP) load balancer which helps to spread traffic among
 healthy virtual machines. Following are some key terms you need to know.
 ​

>>> ​Can members be dynamically 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake 
wrote:

> Hi Imesh,
>
> About centralized logging, I'm trying to get logs to the Log Analytics
> using few methods supported in azure. We can either parse logs in to
> syslogs and send to the Log Analytics or create custom logs specifying the
> logs location. As you said, logs shouldn't be in .txt extension, I got it
> clarified from a azure blog. Will update you soon after I could resolve it.
>
> ​Right, thanks for the update!​


> No you can't dynamically add VMs to the load balancer. Backend pool, where
> all the VMs reside, should be predefined.
>

​Technically that capability should be there. Otherwise we would not be
able to autoscale a server cluster dynamically.
​


> you can auto-scale using scale sets(I'm still researching about it),
> that's the equivalent of AWS auto scaling group . also you can scale up or
> down a VM if it exceeds a certain parameter like CPU usage, using
> monitoring rules.
>
> *Monitoring *
>
>
> Azure has a native monitoring tool which involves collecting and tracking
> metrics, analyzing log files, defining custom metrics and logging generated
> by specific applications or workloads running in Virtual Machines. Azure
> represents monitored data in a graphical manner using charts. Monitoring
> also facilitates triggering alarms when certain conditions are met and also
> it can be configured to take actions on the met conditions. Monitoring is
> done by the Diagnostic Extension and it has following capabilities.
>
> · Collects and uploads the system performance information from
> the Linux VM to the user's storage table, including diagnostic and syslog
> information.
>
> · Enables users to customize the data metrics that will be
> collected and uploaded.
>
> · Enables users to upload specified log files to a designated
> storage table.
>
> Note: Azure storage tables are a non-relational, key-value-pair, storage
> system suitable for storing massive amounts of unstructured data.
>
>
> We can add monitor rules so that when an alert triggers it notifies the
> admins via email. Furthermore we can set to take automated actions. Azure
> automate actions by running runbooks. A runbook is a set of tasks that
> perform some automated process in Azure Automation. We can create our own
> runbooks as well. Available runbooks include,
>
> · Restart VM
>
> · Stop VM
>
> · Remove VM
>
> · Scale up VM
>
> · Scale down VM
>
> When scaling up it sets the virtual machine to the next larger size within
> the size group and when scaling down it sets the virtual machine to the
> next smaller size within the size group.
>
> More about runbooks and automation [1]
>

​Sounds good, will us be able to do a POC on this?​


>
> *Auto scaling *
>
>
> Auto-scaling is the process of dynamically allocating the resources
> required by an application to match performance requirements. Virtual
> machine scale sets are an Azure Compute resource you can use to deploy and
> manage a set of identical VMs. With all VMs configured the same, VM scale
> sets are designed to support true auto-scale  no pre-provisioning of VMs is
> required – and as such makes it easier to build large-scale services
> targeting big compute, big data, and containerized workloads [2].
>
>
> Note: I couldn’t practically do this as my azure free account lets me have
> only 4 cores and I have used all of them on my current deployment. I’m
> getting a new azure account from one of my friends in a day so hopefully I
> will do this on it and update you.
>

​Great! Thanks!​


>
> [1]
> https://azure.microsoft.com/en-us/documentation/articles/automation-intro/
>
> [2]
> https://azure.microsoft.com/en-us/documentation/articles/virtual-machine-scale-sets-overview/
>
>
> thanks,
>
>
> On Mon, Jul 11, 2016 at 9:54 AM, Imesh Gunaratne  wrote:
>
>> On Thu, Jul 7, 2016 at 7:11 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>>
>>> In addition to refining the membership scheme code, I looked into
>>> following features of Azure.
>>> ​
>>>
>> ​Good findings Osura, please find few questions inline:​
>>
>>
>>> ​
>>>
>>> *Azure dynamic load balancing*
>>>
>>>
>>> Azure has a native load balancer which is very easy to configure. It’s a
>>> layer 4 (TCP, UDP) load balancer which helps to spread traffic among
>>> healthy virtual machines. Following are some key terms you need to know.
>>> ​
>>>
>> ​Can members be dynamically added and removed to/from a load balancer? To
>> check this we may need to explore how autoscaling works. On AWS this is
>> handled with autoscaling groups [3]
>>
>>>
>>> *Capturing Virtual Machine Images as templates*
>>>
>>>
>>> Azure provides the feature of generalizing and capturing virtual
>>> machines so that they can be used as templates. This is very useful and
>>> time saving when the production environment has many instances of the same
>>> kind of 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

About centralized logging, I'm trying to get logs to the Log Analytics
using few methods supported in azure. We can either parse logs in to
syslogs and send to the Log Analytics or create custom logs specifying the
logs location. As you said, logs shouldn't be in .txt extension, I got it
clarified from a azure blog. Will update you soon after I could resolve it.

No you can't dynamically add VMs to the load balancer. Backend pool, where
all the VMs reside, should be predefined. you can auto-scale using scale
sets(I'm still researching about it), that's the equivalent of AWS auto
scaling group . also you can scale up or down a VM if it exceeds a certain
parameter like CPU usage, using monitoring rules.

*Monitoring *


Azure has a native monitoring tool which involves collecting and tracking
metrics, analyzing log files, defining custom metrics and logging generated
by specific applications or workloads running in Virtual Machines. Azure
represents monitored data in a graphical manner using charts. Monitoring
also facilitates triggering alarms when certain conditions are met and also
it can be configured to take actions on the met conditions. Monitoring is
done by the Diagnostic Extension and it has following capabilities.

· Collects and uploads the system performance information from the
Linux VM to the user's storage table, including diagnostic and syslog
information.

· Enables users to customize the data metrics that will be
collected and uploaded.

· Enables users to upload specified log files to a designated
storage table.

Note: Azure storage tables are a non-relational, key-value-pair, storage
system suitable for storing massive amounts of unstructured data.


We can add monitor rules so that when an alert triggers it notifies the
admins via email. Furthermore we can set to take automated actions. Azure
automate actions by running runbooks. A runbook is a set of tasks that
perform some automated process in Azure Automation. We can create our own
runbooks as well. Available runbooks include,

· Restart VM

· Stop VM

· Remove VM

· Scale up VM

· Scale down VM

When scaling up it sets the virtual machine to the next larger size within
the size group and when scaling down it sets the virtual machine to the
next smaller size within the size group.

More about runbooks and automation [1]


*Auto scaling *


Auto-scaling is the process of dynamically allocating the resources
required by an application to match performance requirements. Virtual
machine scale sets are an Azure Compute resource you can use to deploy and
manage a set of identical VMs. With all VMs configured the same, VM scale
sets are designed to support true auto-scale  no pre-provisioning of VMs is
required – and as such makes it easier to build large-scale services
targeting big compute, big data, and containerized workloads [2].


Note: I couldn’t practically do this as my azure free account lets me have
only 4 cores and I have used all of them on my current deployment. I’m
getting a new azure account from one of my friends in a day so hopefully I
will do this on it and update you.


[1]
https://azure.microsoft.com/en-us/documentation/articles/automation-intro/

[2]
https://azure.microsoft.com/en-us/documentation/articles/virtual-machine-scale-sets-overview/


thanks,


On Mon, Jul 11, 2016 at 9:54 AM, Imesh Gunaratne  wrote:

> On Thu, Jul 7, 2016 at 7:11 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>>
>> In addition to refining the membership scheme code, I looked into
>> following features of Azure.
>> ​
>>
> ​Good findings Osura, please find few questions inline:​
>
>
>> ​
>>
>> *Azure dynamic load balancing*
>>
>>
>> Azure has a native load balancer which is very easy to configure. It’s a
>> layer 4 (TCP, UDP) load balancer which helps to spread traffic among
>> healthy virtual machines. Following are some key terms you need to know.
>> ​
>>
> ​Can members be dynamically added and removed to/from a load balancer? To
> check this we may need to explore how autoscaling works. On AWS this is
> handled with autoscaling groups [3]
>
>>
>> *Capturing Virtual Machine Images as templates*
>>
>>
>> Azure provides the feature of generalizing and capturing virtual machines
>> so that they can be used as templates. This is very useful and time saving
>> when the production environment has many instances of the same kind of
>> virtual machine. When the virtual machine is being generalized all the data
>> in user directories are erased so better to have wso2 product directory not
>> in "/home/*". More about this can be found here [2].
>>
>> Once the virtual machine is captured, it is stored in the storage account
>> that is associated with the virtual machine. You can either download this
>> or use directly by referring to the URI when you want to make other virtual
>> machines with this template. What would be awesome is if we 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Thu, Jul 7, 2016 at 7:11 PM, Osura Rathnayake  wrote:

> Hi Mentors,
>
>
> In addition to refining the membership scheme code, I looked into
> following features of Azure.
> ​
>
​Good findings Osura, please find few questions inline:​


> ​
>
> *Azure dynamic load balancing*
>
>
> Azure has a native load balancer which is very easy to configure. It’s a
> layer 4 (TCP, UDP) load balancer which helps to spread traffic among
> healthy virtual machines. Following are some key terms you need to know.
> ​
>
​Can members be dynamically added and removed to/from a load balancer? To
check this we may need to explore how autoscaling works. On AWS this is
handled with autoscaling groups [3]

>
> *Capturing Virtual Machine Images as templates*
>
>
> Azure provides the feature of generalizing and capturing virtual machines
> so that they can be used as templates. This is very useful and time saving
> when the production environment has many instances of the same kind of
> virtual machine. When the virtual machine is being generalized all the data
> in user directories are erased so better to have wso2 product directory not
> in "/home/*". More about this can be found here [2].
>
> Once the virtual machine is captured, it is stored in the storage account
> that is associated with the virtual machine. You can either download this
> or use directly by referring to the URI when you want to make other virtual
> machines with this template. What would be awesome is if we can fully
> configure the virtual machine with a given product and make it available to
> users.
>
>
>
​Yes, this is mandatory. Otherwise we would not be able to autoscale a
server cluster.

​​I'm sorry I may have missed, how did it go with centralized logging?

[3]
http://docs.aws.amazon.com/autoscaling/latest/userguide/AutoScalingGroup.html

​Thanks​


> [1]
> https://azure.microsoft.com/en-us/documentation/articles/load-balancer-overview/
>
> [2]
> https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-capture-image/
>
>
> Thanks,
>
> On Wed, Jul 6, 2016 at 12:18 PM, Osura Rathnayake 
> wrote:
>
>> Hi Akila,
>>
>> Please refer to the screenshots that I have attached. When I updated
>> localMemberPort to 4200, I can see it being reflected in logs when members
>> are joining. So should I still make modifications in the code?
>>
>> .gitignore was added.
>>
>> okay I will write test cases in testNG and update
>>
>> thanks,
>>
>> On Wed, Jul 6, 2016 at 9:06 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> On Tue, Jul 5, 2016 at 11:38 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Akila,

 Please check the modified code. It now takes the value which is
 specified as localMemberPort in axis2.xml.

>>>
>>> I still don't see any change to the logic of how member address is
>>> calculated. Can you double check?
>>>
>>> Please make sure "target/**" directories are ignored from .gitignore.
>>> These shouldn't be in the repo [1]. You might also need to ignore any IDE
>>> specific files. Have a look at .gitignore in Kubernetes artifacts [2].
>>>
>>> I see that you have committed some test cases based on JUnit. Please
>>> note that as a platform we are moving to testng framework so better to use
>>> that.
>>> @Imesh, Isuru: Please correct me if I'm wrong.
>>>
>>> Shall we get a repo created under wso2-incubator for this?
>>>
>>> [1] https://github.com/osuran/azure-membership-scheme/tree/master/target
>>> [2] https://github.com/wso2/kubernetes-artifacts/blob/master/.gitignore
>>>
>>> Thanks.
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>
>>
>>
>> --
>> Regards,
>> Osura Rathnayake
>>
>
>
>
> --
> Regards,
> Osura Rathnayake
>



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

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,


In addition to refining the membership scheme code, I looked into following
features of Azure.


*Azure dynamic load balancing*


Azure has a native load balancer which is very easy to configure. It’s a
layer 4 (TCP, UDP) load balancer which helps to spread traffic among
healthy virtual machines. Following are some key terms you need to know.

· Backend pool: This is a pool of virtual machines that is
configured to share the traffic among

· Probe: The load balancer can probe the health of the various
server instances. When a probe fails to respond, the load balancer stops
sending new connections to the unhealthy instances. Existing connections
are not impacted.

· Availability set: when you have a set of virtual machines for the
same purpose, azure recommends to add them to an availability set.

You can configure it to:

· Load balance incoming Internet traffic to virtual machines,
called internet-facing load balancing

· Load balance traffic between virtual machines in a virtual
network, between virtual machines in cloud services, or between on-premises
computers and virtual machines in a cross-premises virtual network, called
internal load balancing

· Forward external traffic to a specific virtual machine

A diagram showing the assembly of elements is attached.


Before creating the load balancer, you have to create backend pool and
probes. One important thing about creating the backend pool is that only
the virtual machines that are included in an availability set is permitted
to add to the backend pool. And very importantly, a virtual machine can be
added to an availability set only at the time of its creation.

Once you created the load balancer, you can add load balancing rules where
you can define ports and virtual machines that cater requests. furthermore
you can define a different port for the users to access and map that to the
actual port in the virtual machine which increases security. Also you can
define whether requests are TCP or UDP based.


more about the load balancer its advantages can be found here [1]


*Capturing Virtual Machine Images as templates*


Azure provides the feature of generalizing and capturing virtual machines
so that they can be used as templates. This is very useful and time saving
when the production environment has many instances of the same kind of
virtual machine. When the virtual machine is being generalized all the data
in user directories are erased so better to have wso2 product directory not
in "/home/*". More about this can be found here [2].

Once the virtual machine is captured, it is stored in the storage account
that is associated with the virtual machine. You can either download this
or use directly by referring to the URI when you want to make other virtual
machines with this template. What would be awesome is if we can fully
configure the virtual machine with a given product and make it available to
users.




[1]
https://azure.microsoft.com/en-us/documentation/articles/load-balancer-overview/

[2]
https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-capture-image/


Thanks,

On Wed, Jul 6, 2016 at 12:18 PM, Osura Rathnayake 
wrote:

> Hi Akila,
>
> Please refer to the screenshots that I have attached. When I updated
> localMemberPort to 4200, I can see it being reflected in logs when members
> are joining. So should I still make modifications in the code?
>
> .gitignore was added.
>
> okay I will write test cases in testNG and update
>
> thanks,
>
> On Wed, Jul 6, 2016 at 9:06 AM, Akila Ravihansa Perera  > wrote:
>
>> Hi,
>>
>> On Tue, Jul 5, 2016 at 11:38 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Akila,
>>>
>>> Please check the modified code. It now takes the value which is
>>> specified as localMemberPort in axis2.xml.
>>>
>>
>> I still don't see any change to the logic of how member address is
>> calculated. Can you double check?
>>
>> Please make sure "target/**" directories are ignored from .gitignore.
>> These shouldn't be in the repo [1]. You might also need to ignore any IDE
>> specific files. Have a look at .gitignore in Kubernetes artifacts [2].
>>
>> I see that you have committed some test cases based on JUnit. Please note
>> that as a platform we are moving to testng framework so better to use that.
>> @Imesh, Isuru: Please correct me if I'm wrong.
>>
>> Shall we get a repo created under wso2-incubator for this?
>>
>> [1] https://github.com/osuran/azure-membership-scheme/tree/master/target
>> [2] https://github.com/wso2/kubernetes-artifacts/blob/master/.gitignore
>>
>> Thanks.
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> Regards,
> Osura Rathnayake
>



-- 
Regards,
Osura Rathnayake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Akila,

Please refer to the screenshots that I have attached. When I updated
localMemberPort to 4200, I can see it being reflected in logs when members
are joining. So should I still make modifications in the code?

.gitignore was added.

okay I will write test cases in testNG and update

thanks,

On Wed, Jul 6, 2016 at 9:06 AM, Akila Ravihansa Perera 
wrote:

> Hi,
>
> On Tue, Jul 5, 2016 at 11:38 AM, Osura Rathnayake 
> wrote:
>
>> Hi Akila,
>>
>> Please check the modified code. It now takes the value which is specified
>> as localMemberPort in axis2.xml.
>>
>
> I still don't see any change to the logic of how member address is
> calculated. Can you double check?
>
> Please make sure "target/**" directories are ignored from .gitignore.
> These shouldn't be in the repo [1]. You might also need to ignore any IDE
> specific files. Have a look at .gitignore in Kubernetes artifacts [2].
>
> I see that you have committed some test cases based on JUnit. Please note
> that as a platform we are moving to testng framework so better to use that.
> @Imesh, Isuru: Please correct me if I'm wrong.
>
> Shall we get a repo created under wso2-incubator for this?
>
> [1] https://github.com/osuran/azure-membership-scheme/tree/master/target
> [2] https://github.com/wso2/kubernetes-artifacts/blob/master/.gitignore
>
> Thanks.
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
Regards,
Osura Rathnayake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Wed, Jul 6, 2016 at 9:06 AM, Akila Ravihansa Perera 
wrote:
>
>
> I see that you have committed some test cases based on JUnit. Please note
> that as a platform we are moving to testng framework so better to use that.
> @Imesh, Isuru: Please correct me if I'm wrong.
>

​Yes, WSO2 integration test framework (a sample can be found here [3])
would be suitable for implementing integration tests (tests that need a
running server instance). However if it just unit tests we can simply use
JUnit.

Shall we get a repo created under wso2-incubator for this?
>

​That's a good question. May be we can move to incubator at the end of the
project?

[3]
https://github.com/wso2/product-esb/blob/master/modules/integration/tests-integration/tests-mediator-1/src/test/java/org/wso2/carbon/esb/mediator/test/call/CallMediatorAPIWithNamedSeqCase.java

Thanks​


>
> [1] https://github.com/osuran/azure-membership-scheme/tree/master/target
> [2] https://github.com/wso2/kubernetes-artifacts/blob/master/.gitignore
>
> Thanks.
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi,

On Tue, Jul 5, 2016 at 11:38 AM, Osura Rathnayake 
wrote:

> Hi Akila,
>
> Please check the modified code. It now takes the value which is specified
> as localMemberPort in axis2.xml.
>

I still don't see any change to the logic of how member address is
calculated. Can you double check?

Please make sure "target/**" directories are ignored from .gitignore. These
shouldn't be in the repo [1]. You might also need to ignore any IDE
specific files. Have a look at .gitignore in Kubernetes artifacts [2].

I see that you have committed some test cases based on JUnit. Please note
that as a platform we are moving to testng framework so better to use that.
@Imesh, Isuru: Please correct me if I'm wrong.

Shall we get a repo created under wso2-incubator for this?

[1] https://github.com/osuran/azure-membership-scheme/tree/master/target
[2] https://github.com/wso2/kubernetes-artifacts/blob/master/.gitignore

Thanks.
-- 
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

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

On Tue, Jul 5, 2016 at 11:33 AM, Akila Ravihansa Perera 
wrote:

> Hi Osura,
>
> As Isuru mentioned you need to be clear about tenantId since it might
> conflict with Carbon tenantId. As suggested, please rename it to something
> like AZURE_TENANT_ID or something like that.
>
> Regarding localMemberPort in axis2.xml, the value of this parameter should
> be same in all nodes by convention therefore no need read localMemberPort
> parameter value in each member's axis2.xml. When adding members to
> Hazelcast config context you need to take the value of this parameter.
> Because we cannot guarantee that it will be 4000 in every deployment. There
> are some special cases in which we need to change this. Have a look at [1]
> to see how this is handled in Mesos membership scheme.
>
Great! +1 for this approach of considering the Hz port same for a cluster.

>
> [1]
> https://github.com/wso2/mesos-artifacts/blob/master/common/mesos-membership-scheme/src/main/java/org/wso2/carbon/clustering/mesos/MesosMembershipScheme.java#L247
>
> Thanks.
>



-- 
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] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Akila,

Please check the modified code. It now takes the value which is specified
as localMemberPort in axis2.xml.

Thanks,

On Tuesday, July 5, 2016, Akila Ravihansa Perera  wrote:

> Hi Osura,
>
> As Isuru mentioned you need to be clear about tenantId since it might
> conflict with Carbon tenantId. As suggested, please rename it to something
> like AZURE_TENANT_ID or something like that.
>
> Regarding localMemberPort in axis2.xml, the value of this parameter should
> be same in all nodes by convention therefore no need read localMemberPort
> parameter value in each member's axis2.xml. When adding members to
> Hazelcast config context you need to take the value of this parameter.
> Because we cannot guarantee that it will be 4000 in every deployment. There
> are some special cases in which we need to change this. Have a look at [1]
> to see how this is handled in Mesos membership scheme.
>
> [1]
> https://github.com/wso2/mesos-artifacts/blob/master/common/mesos-membership-scheme/src/main/java/org/wso2/carbon/clustering/mesos/MesosMembershipScheme.java#L247
>
> Thanks.
>


-- 
Regards,
Osura Rathnayake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi Osura,

As Isuru mentioned you need to be clear about tenantId since it might
conflict with Carbon tenantId. As suggested, please rename it to something
like AZURE_TENANT_ID or something like that.

Regarding localMemberPort in axis2.xml, the value of this parameter should
be same in all nodes by convention therefore no need read localMemberPort
parameter value in each member's axis2.xml. When adding members to
Hazelcast config context you need to take the value of this parameter.
Because we cannot guarantee that it will be 4000 in every deployment. There
are some special cases in which we need to change this. Have a look at [1]
to see how this is handled in Mesos membership scheme.

[1]
https://github.com/wso2/mesos-artifacts/blob/master/common/mesos-membership-scheme/src/main/java/org/wso2/carbon/clustering/mesos/MesosMembershipScheme.java#L247

Thanks.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

On Tue, Jul 5, 2016 at 9:49 AM, Osura Rathnayake  wrote:

> Hi Akila,
>
> Please find more about tenantId here [1].
>
Seems the tenantId you are referring to a detail specific to Azure. Please
confirm. Since there is a tenancy concept in Carbon as well, shall we
re-name the variable and constant to something more meaningful (ex.: azure
TenantId for the variable name)?

>
> Regarding the last point, what I do is, I collect all the ip addresses and
> update the hazelcast config. in that case how can i get localMemberPort for
> each member since localMemberPOrt is defined in each member's axis2.xml.
> Also I observed that when the same localMemberPort is assigned to all the
> members, cluster discovery works fine but when different ports are assigned
> it doesn't work.
>
There should be a way to get this information (clustering port of members)
from the API, as we do for the IP addresses currently. If not, IMHO we can
keep the current implementation (where it assumes clustering port is 4000)
and document it clearly.

>
> Yes I'm still implementing the test cases and will update soon.
>
> [1]
> https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/
>
>
> thanks,
>
> On Mon, Jul 4, 2016 at 9:41 PM, Akila Ravihansa Perera  > wrote:
>
>> Hi Osura,
>>
>> I'm still not clear on tenantId. Perhaps you can explain in detail during
>> the code review meeting. Regarding the last point, yes it should be
>> localMemberPort. Sorry, it was a typo.
>>
>> One more thing, I noticed that test cases are empty [1]. Are you still
>> working on implementing those?
>>
>> [1]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/test/java/org/wso2/carbon/clustering/azure/AppTest.java
>>
>> Thanks.
>>
>
>
>
> --
> Regards,
> Osura Rathnayake
>



-- 
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] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi Osura,

I'm still not clear on tenantId. Perhaps you can explain in detail during
the code review meeting. Regarding the last point, yes it should be
localMemberPort. Sorry, it was a typo.

One more thing, I noticed that test cases are empty [1]. Are you still
working on implementing those?

[1]
https://github.com/osuran/azure-membership-scheme/blob/master/src/test/java/org/wso2/carbon/clustering/azure/AppTest.java

Thanks.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Akila,

Thank you for the feedback.
tenantId is used because it is needed in the url which is used to
authenticate. WIthout the tenantId the url would be incomplete.
I have fixed [1] all the issues you have mentioned in the previous email
except for the Netflix Feign standard and I'm looking into it. About the
last point, is it localMemberHostPort or localMemberPort ?

[1] https://github.com/osuran/azure-membership-scheme

thanks,

On Thu, Jun 30, 2016 at 11:22 AM, Akila Ravihansa Perera  wrote:

> Hi Osura,
>
> Good progress :)
>
> Netflix Feign [1] is a highly customizable and easy to use REST API client
> framework. The GitHub page itself contains many samples. We have written
> Mesos membership scheme [2] using that which you can use as a reference
> guideline. Please refactor your code to use this client. Let me know if you
> run into any issues.
>
> I noticed few more issues in the code;
>  - No need to define a variable and assign a const [3]. You can directly
> use the const.
>  - Why do you need to append tenantId to authorization endpoint? Just
> asking to clarify why tenantId is needed here.
>
> - You can move common operations to common method. In [4], instead of
> checking for empty values and in [5] reading from System.env. Move all that
> to getParameterValue method. This will reduce the amount of code you have
> to write.
>
>  - You don't have to log and throw [6]. This will only clutter the log
> file.
>
>  - You don't need a for loop here [7]. Simply use a for-each iterator.
>
>  - Don't put ":" in front of the placeholder [8]
>
>  - Don't put spaces around square brackets [9]
>
>  - You need to separate variables by commas [10]
>
>  - Use proper case for log msg labels [11]. Should be "VM-IP" or simply
> "IP Address" is enough. This should contain both IP and local port. Read
> below for more info on local port.
>
> * This is very important *
>  - Use localMemberHostPort defined in axis2.xml when adding the member IPs
> in [12]. This is the port that all WSO2 server instances are listening on
> for Hazelcast connections. By default it is 4000 that's why it works now.
> But for some reason if someone changes it, then this code will break.
>
> [1] https://github.com/Netflix/feign
> [2]
> https://github.com/wso2/mesos-artifacts/tree/master/common/mesos-membership-scheme
> [3]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L101
> [4]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L113
> [5]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L110
> [6]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L182
> [7]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L200
> [8]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L263
> [9]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L282
> [10]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L171
> [11]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L177
> [12]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L176
>
> Thanks.
>
>


-- 
Regards,
Osura Rathnayake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

For the Log analytics, we can directly feed the logs if they are in .txt
format. [1]

[1]
https://azure.microsoft.com/en-us/documentation/articles/log-analytics-data-sources-custom-logs/

thanks,

On Thu, Jun 30, 2016 at 2:36 PM, Imesh Gunaratne  wrote:

> Hi Osura,
>
> On Thu, Jun 30, 2016 at 12:10 PM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Is there a way to configure application server to get logs in .txt format
>> instead of .log format?
>>
>
> ​
> C
> ​an you please explain the reason for this requirement?
>
> Thanks​
>
>
>> thanks,
>>
>> On Thu, Jun 30, 2016 at 10:24 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> If it supports syslog as an input source, you can use the syslog
>>> appender [1].
>>>
>>> [1].
>>> http://wso2.com/library/knowledge-base/2012/04/setup-syslog-wso2-carbon-products/
>>>
>>>
>>> On Thu, Jun 30, 2016 at 10:22 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 thank you for the link. yes we can use Log Analytics to collect and
 analyse data. following are the types of data that can be collected from a
 linux machine.

- Performance metrics
- Syslog events
- Alerts from Nagios and Zabbix
- Docker container performance metrics, inventory and logs

 I'm looking into how we can collect wso2 Application server logs
 thanks,



 On Wed, Jun 29, 2016 at 8:08 PM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> On Wed, Jun 29, 2016 at 7:47 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I'm trying to implement the log4j appender to facilitate centralized
>> logging. In that case where should be the central location to collect 
>> logs?
>>
> Since the aim is to run WSO2 products on Azure, the ideal case is to
> use a log aggregation/management solution provided by Azure, if any. Can
> you do a quick research on this and check? Found [1] from a simple google
> search.
>
> [1].
> https://azure.microsoft.com/en-us/documentation/articles/log-analytics-overview/
>
>>
>> thanks
>>
>> On Tue, Jun 28, 2016 at 11:19 AM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Hi Akila,
>>>
>>> Thank you for the feedback and please accept my apologies for the
>>> delayed response.
>>> I updated the code according to the guidelines you have provided on
>>> coding standards and pushed it to the repository [1].
>>> tenantId is used here [2].
>>> I'm not familiar with Netflix Feign standard on HTTP requests. Can
>>> you please explain it briefly or mention a link to a tutorial?
>>>
>>> [1] https://github.com/osuran/azure-membership-scheme
>>> [2]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L168
>>>
>>> Thanks,
>>>
>>> On Fri, Jun 24, 2016 at 10:49 PM, Imesh Gunaratne 
>>> wrote:
>>>


 On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> Hi Osura,
>
> I still see some issues in the code.
>
> 1. Make sure to use consts when appropriate [1]
> 2. Where do you use tenantId [2] ?
> 3. Use the actual parameter key in the error message [3] instead
> of hard coding it
> 4. You need to adhere to max line len of 120 chars. I see this
> standard being violated in couple of places [4]. Use IDE formatting 
> tool to
> fix this
> 5. Do not keep empty spaces [5]. This is bad code styling
>
> @Imesh: Osura has used Apache HTTP client to send HTTP requests
> [6]. Shall we make Netflix Feign the standard for this?
>

 ​+1 Yes, definitely.

 Thanks​


>
> [1]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
> [2]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
> [3]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
> [4]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
> [5]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
> [6]
> 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

Hi Osura,

On Thu, Jun 30, 2016 at 12:10 PM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Is there a way to configure application server to get logs in .txt format
> instead of .log format?
>

​
C
​an you please explain the reason for this requirement?

Thanks​


> thanks,
>
> On Thu, Jun 30, 2016 at 10:24 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> If it supports syslog as an input source, you can use the syslog appender
>> [1].
>>
>> [1].
>> http://wso2.com/library/knowledge-base/2012/04/setup-syslog-wso2-carbon-products/
>>
>>
>> On Thu, Jun 30, 2016 at 10:22 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> thank you for the link. yes we can use Log Analytics to collect and
>>> analyse data. following are the types of data that can be collected from a
>>> linux machine.
>>>
>>>- Performance metrics
>>>- Syslog events
>>>- Alerts from Nagios and Zabbix
>>>- Docker container performance metrics, inventory and logs
>>>
>>> I'm looking into how we can collect wso2 Application server logs
>>> thanks,
>>>
>>>
>>>
>>> On Wed, Jun 29, 2016 at 8:08 PM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 On Wed, Jun 29, 2016 at 7:47 PM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> I'm trying to implement the log4j appender to facilitate centralized
> logging. In that case where should be the central location to collect 
> logs?
>
 Since the aim is to run WSO2 products on Azure, the ideal case is to
 use a log aggregation/management solution provided by Azure, if any. Can
 you do a quick research on this and check? Found [1] from a simple google
 search.

 [1].
 https://azure.microsoft.com/en-us/documentation/articles/log-analytics-overview/

>
> thanks
>
> On Tue, Jun 28, 2016 at 11:19 AM, Osura Rathnayake  > wrote:
>
>> Hi Akila,
>>
>> Thank you for the feedback and please accept my apologies for the
>> delayed response.
>> I updated the code according to the guidelines you have provided on
>> coding standards and pushed it to the repository [1].
>> tenantId is used here [2].
>> I'm not familiar with Netflix Feign standard on HTTP requests. Can
>> you please explain it briefly or mention a link to a tutorial?
>>
>> [1] https://github.com/osuran/azure-membership-scheme
>> [2]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L168
>>
>> Thanks,
>>
>> On Fri, Jun 24, 2016 at 10:49 PM, Imesh Gunaratne 
>> wrote:
>>
>>>
>>>
>>> On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 Hi Osura,

 I still see some issues in the code.

 1. Make sure to use consts when appropriate [1]
 2. Where do you use tenantId [2] ?
 3. Use the actual parameter key in the error message [3] instead of
 hard coding it
 4. You need to adhere to max line len of 120 chars. I see this
 standard being violated in couple of places [4]. Use IDE formatting 
 tool to
 fix this
 5. Do not keep empty spaces [5]. This is bad code styling

 @Imesh: Osura has used Apache HTTP client to send HTTP requests
 [6]. Shall we make Netflix Feign the standard for this?

>>>
>>> ​+1 Yes, definitely.
>>>
>>> Thanks​
>>>
>>>

 [1]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
 [2]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
 [3]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
 [4]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
 [5]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
 [6]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234

 Thanks.

 On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne 
 wrote:

>
>
> On Fri, Jun 24, 2016 at 11:00 AM,  wrote:
>
>> Hi Imesh,
>>
>> Yes I completed the evaluation.
>>
> ​Great! 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Is there a way to configure application server to get logs in .txt format
instead of .log format?

thanks,

On Thu, Jun 30, 2016 at 10:24 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> If it supports syslog as an input source, you can use the syslog appender
> [1].
>
> [1].
> http://wso2.com/library/knowledge-base/2012/04/setup-syslog-wso2-carbon-products/
>
>
> On Thu, Jun 30, 2016 at 10:22 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> thank you for the link. yes we can use Log Analytics to collect and
>> analyse data. following are the types of data that can be collected from a
>> linux machine.
>>
>>- Performance metrics
>>- Syslog events
>>- Alerts from Nagios and Zabbix
>>- Docker container performance metrics, inventory and logs
>>
>> I'm looking into how we can collect wso2 Application server logs
>> thanks,
>>
>>
>>
>> On Wed, Jun 29, 2016 at 8:08 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Wed, Jun 29, 2016 at 7:47 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 I'm trying to implement the log4j appender to facilitate centralized
 logging. In that case where should be the central location to collect logs?

>>> Since the aim is to run WSO2 products on Azure, the ideal case is to use
>>> a log aggregation/management solution provided by Azure, if any. Can you do
>>> a quick research on this and check? Found [1] from a simple google search.
>>>
>>> [1].
>>> https://azure.microsoft.com/en-us/documentation/articles/log-analytics-overview/
>>>

 thanks

 On Tue, Jun 28, 2016 at 11:19 AM, Osura Rathnayake 
 wrote:

> Hi Akila,
>
> Thank you for the feedback and please accept my apologies for the
> delayed response.
> I updated the code according to the guidelines you have provided on
> coding standards and pushed it to the repository [1].
> tenantId is used here [2].
> I'm not familiar with Netflix Feign standard on HTTP requests. Can you
> please explain it briefly or mention a link to a tutorial?
>
> [1] https://github.com/osuran/azure-membership-scheme
> [2]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L168
>
> Thanks,
>
> On Fri, Jun 24, 2016 at 10:49 PM, Imesh Gunaratne 
> wrote:
>
>>
>>
>> On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Osura,
>>>
>>> I still see some issues in the code.
>>>
>>> 1. Make sure to use consts when appropriate [1]
>>> 2. Where do you use tenantId [2] ?
>>> 3. Use the actual parameter key in the error message [3] instead of
>>> hard coding it
>>> 4. You need to adhere to max line len of 120 chars. I see this
>>> standard being violated in couple of places [4]. Use IDE formatting 
>>> tool to
>>> fix this
>>> 5. Do not keep empty spaces [5]. This is bad code styling
>>>
>>> @Imesh: Osura has used Apache HTTP client to send HTTP requests [6].
>>> Shall we make Netflix Feign the standard for this?
>>>
>>
>> ​+1 Yes, definitely.
>>
>> Thanks​
>>
>>
>>>
>>> [1]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
>>> [2]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
>>> [3]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
>>> [4]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
>>> [5]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
>>> [6]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234
>>>
>>> Thanks.
>>>
>>> On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne 
>>> wrote:
>>>


 On Fri, Jun 24, 2016 at 11:00 AM,  wrote:

> Hi Imesh,
>
> Yes I completed the evaluation.
>
 ​Great! Thanks!​

> Thanks,
>
> Get Outlook for Android 
>
>
>
> On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" <
> im...@wso2.com> wrote:
>
> Hi Osura,
>>
>> Were you able to submit the midterm 

Re: [Dev] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi Osura,

Good progress :)

Netflix Feign [1] is a highly customizable and easy to use REST API client
framework. The GitHub page itself contains many samples. We have written
Mesos membership scheme [2] using that which you can use as a reference
guideline. Please refactor your code to use this client. Let me know if you
run into any issues.

I noticed few more issues in the code;
 - No need to define a variable and assign a const [3]. You can directly
use the const.
 - Why do you need to append tenantId to authorization endpoint? Just
asking to clarify why tenantId is needed here.

- You can move common operations to common method. In [4], instead of
checking for empty values and in [5] reading from System.env. Move all that
to getParameterValue method. This will reduce the amount of code you have
to write.

 - You don't have to log and throw [6]. This will only clutter the log file.

 - You don't need a for loop here [7]. Simply use a for-each iterator.

 - Don't put ":" in front of the placeholder [8]

 - Don't put spaces around square brackets [9]

 - You need to separate variables by commas [10]

 - Use proper case for log msg labels [11]. Should be "VM-IP" or simply "IP
Address" is enough. This should contain both IP and local port. Read below
for more info on local port.

* This is very important *
 - Use localMemberHostPort defined in axis2.xml when adding the member IPs
in [12]. This is the port that all WSO2 server instances are listening on
for Hazelcast connections. By default it is 4000 that's why it works now.
But for some reason if someone changes it, then this code will break.

[1] https://github.com/Netflix/feign
[2]
https://github.com/wso2/mesos-artifacts/tree/master/common/mesos-membership-scheme
[3]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L101
[4]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L113
[5]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L110
[6]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L182
[7]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L200
[8]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L263
[9]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L282
[10]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L171
[11]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L177
[12]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L176

Thanks.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

If it supports syslog as an input source, you can use the syslog appender
[1].

[1].
http://wso2.com/library/knowledge-base/2012/04/setup-syslog-wso2-carbon-products/

On Thu, Jun 30, 2016 at 10:22 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> thank you for the link. yes we can use Log Analytics to collect and
> analyse data. following are the types of data that can be collected from a
> linux machine.
>
>- Performance metrics
>- Syslog events
>- Alerts from Nagios and Zabbix
>- Docker container performance metrics, inventory and logs
>
> I'm looking into how we can collect wso2 Application server logs
> thanks,
>
>
>
> On Wed, Jun 29, 2016 at 8:08 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Wed, Jun 29, 2016 at 7:47 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> I'm trying to implement the log4j appender to facilitate centralized
>>> logging. In that case where should be the central location to collect logs?
>>>
>> Since the aim is to run WSO2 products on Azure, the ideal case is to use
>> a log aggregation/management solution provided by Azure, if any. Can you do
>> a quick research on this and check? Found [1] from a simple google search.
>>
>> [1].
>> https://azure.microsoft.com/en-us/documentation/articles/log-analytics-overview/
>>
>>>
>>> thanks
>>>
>>> On Tue, Jun 28, 2016 at 11:19 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Akila,

 Thank you for the feedback and please accept my apologies for the
 delayed response.
 I updated the code according to the guidelines you have provided on
 coding standards and pushed it to the repository [1].
 tenantId is used here [2].
 I'm not familiar with Netflix Feign standard on HTTP requests. Can you
 please explain it briefly or mention a link to a tutorial?

 [1] https://github.com/osuran/azure-membership-scheme
 [2]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L168

 Thanks,

 On Fri, Jun 24, 2016 at 10:49 PM, Imesh Gunaratne 
 wrote:

>
>
> On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Osura,
>>
>> I still see some issues in the code.
>>
>> 1. Make sure to use consts when appropriate [1]
>> 2. Where do you use tenantId [2] ?
>> 3. Use the actual parameter key in the error message [3] instead of
>> hard coding it
>> 4. You need to adhere to max line len of 120 chars. I see this
>> standard being violated in couple of places [4]. Use IDE formatting tool 
>> to
>> fix this
>> 5. Do not keep empty spaces [5]. This is bad code styling
>>
>> @Imesh: Osura has used Apache HTTP client to send HTTP requests [6].
>> Shall we make Netflix Feign the standard for this?
>>
>
> ​+1 Yes, definitely.
>
> Thanks​
>
>
>>
>> [1]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
>> [2]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
>> [3]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
>> [4]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
>> [5]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
>> [6]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234
>>
>> Thanks.
>>
>> On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne 
>> wrote:
>>
>>>
>>>
>>> On Fri, Jun 24, 2016 at 11:00 AM,  wrote:
>>>
 Hi Imesh,

 Yes I completed the evaluation.

>>> ​Great! Thanks!​
>>>
 Thanks,

 Get Outlook for Android 



 On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" <
 im...@wso2.com> wrote:

 Hi Osura,
>
> Were you able to submit the midterm evaluation? Might be better to
> do it soon.
>
> Thanks
> ​Imesh​
>
>
>>>
>>>
>>> --
>>> *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 . 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

thank you for the link. yes we can use Log Analytics to collect and analyse
data. following are the types of data that can be collected from a linux
machine.

   - Performance metrics
   - Syslog events
   - Alerts from Nagios and Zabbix
   - Docker container performance metrics, inventory and logs

I'm looking into how we can collect wso2 Application server logs
thanks,



On Wed, Jun 29, 2016 at 8:08 PM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> On Wed, Jun 29, 2016 at 7:47 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I'm trying to implement the log4j appender to facilitate centralized
>> logging. In that case where should be the central location to collect logs?
>>
> Since the aim is to run WSO2 products on Azure, the ideal case is to use a
> log aggregation/management solution provided by Azure, if any. Can you do a
> quick research on this and check? Found [1] from a simple google search.
>
> [1].
> https://azure.microsoft.com/en-us/documentation/articles/log-analytics-overview/
>
>>
>> thanks
>>
>> On Tue, Jun 28, 2016 at 11:19 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Akila,
>>>
>>> Thank you for the feedback and please accept my apologies for the
>>> delayed response.
>>> I updated the code according to the guidelines you have provided on
>>> coding standards and pushed it to the repository [1].
>>> tenantId is used here [2].
>>> I'm not familiar with Netflix Feign standard on HTTP requests. Can you
>>> please explain it briefly or mention a link to a tutorial?
>>>
>>> [1] https://github.com/osuran/azure-membership-scheme
>>> [2]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L168
>>>
>>> Thanks,
>>>
>>> On Fri, Jun 24, 2016 at 10:49 PM, Imesh Gunaratne 
>>> wrote:
>>>


 On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> Hi Osura,
>
> I still see some issues in the code.
>
> 1. Make sure to use consts when appropriate [1]
> 2. Where do you use tenantId [2] ?
> 3. Use the actual parameter key in the error message [3] instead of
> hard coding it
> 4. You need to adhere to max line len of 120 chars. I see this
> standard being violated in couple of places [4]. Use IDE formatting tool 
> to
> fix this
> 5. Do not keep empty spaces [5]. This is bad code styling
>
> @Imesh: Osura has used Apache HTTP client to send HTTP requests [6].
> Shall we make Netflix Feign the standard for this?
>

 ​+1 Yes, definitely.

 Thanks​


>
> [1]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
> [2]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
> [3]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
> [4]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
> [5]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
> [6]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234
>
> Thanks.
>
> On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne 
> wrote:
>
>>
>>
>> On Fri, Jun 24, 2016 at 11:00 AM,  wrote:
>>
>>> Hi Imesh,
>>>
>>> Yes I completed the evaluation.
>>>
>> ​Great! Thanks!​
>>
>>> Thanks,
>>>
>>> Get Outlook for Android 
>>>
>>>
>>>
>>> On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" <
>>> im...@wso2.com> wrote:
>>>
>>> Hi Osura,

 Were you able to submit the midterm evaluation? Might be better to
 do it soon.

 Thanks
 ​Imesh​


>>
>>
>> --
>> *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
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.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


>>>
>>>

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

On Wed, Jun 29, 2016 at 7:47 PM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I'm trying to implement the log4j appender to facilitate centralized
> logging. In that case where should be the central location to collect logs?
>
Since the aim is to run WSO2 products on Azure, the ideal case is to use a
log aggregation/management solution provided by Azure, if any. Can you do a
quick research on this and check? Found [1] from a simple google search.

[1].
https://azure.microsoft.com/en-us/documentation/articles/log-analytics-overview/

>
> thanks
>
> On Tue, Jun 28, 2016 at 11:19 AM, Osura Rathnayake 
> wrote:
>
>> Hi Akila,
>>
>> Thank you for the feedback and please accept my apologies for the delayed
>> response.
>> I updated the code according to the guidelines you have provided on
>> coding standards and pushed it to the repository [1].
>> tenantId is used here [2].
>> I'm not familiar with Netflix Feign standard on HTTP requests. Can you
>> please explain it briefly or mention a link to a tutorial?
>>
>> [1] https://github.com/osuran/azure-membership-scheme
>> [2]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L168
>>
>> Thanks,
>>
>> On Fri, Jun 24, 2016 at 10:49 PM, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 Hi Osura,

 I still see some issues in the code.

 1. Make sure to use consts when appropriate [1]
 2. Where do you use tenantId [2] ?
 3. Use the actual parameter key in the error message [3] instead of
 hard coding it
 4. You need to adhere to max line len of 120 chars. I see this standard
 being violated in couple of places [4]. Use IDE formatting tool to fix this
 5. Do not keep empty spaces [5]. This is bad code styling

 @Imesh: Osura has used Apache HTTP client to send HTTP requests [6].
 Shall we make Netflix Feign the standard for this?

>>>
>>> ​+1 Yes, definitely.
>>>
>>> Thanks​
>>>
>>>

 [1]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
 [2]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
 [3]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
 [4]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
 [5]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
 [6]
 https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234

 Thanks.

 On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne 
 wrote:

>
>
> On Fri, Jun 24, 2016 at 11:00 AM,  wrote:
>
>> Hi Imesh,
>>
>> Yes I completed the evaluation.
>>
> ​Great! Thanks!​
>
>> Thanks,
>>
>> Get Outlook for Android 
>>
>>
>>
>> On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" <
>> im...@wso2.com> wrote:
>>
>> Hi Osura,
>>>
>>> Were you able to submit the midterm evaluation? Might be better to
>>> do it soon.
>>>
>>> Thanks
>>> ​Imesh​
>>>
>>>
>
>
> --
> *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
>
>


 --
 Akila Ravihansa Perera
 WSO2 Inc.;  http://wso2.com/

 Blog: http://ravihansa3000.blogspot.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
>>>
>>>
>>
>>
>> --
>> Regards,
>> Osura Rathnayake
>>
>
>
>
> --
> Regards,
> Osura Rathnayake
>



-- 
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] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

I'm trying to implement the log4j appender to facilitate centralized
logging. In that case where should be the central location to collect logs?

thanks

On Tue, Jun 28, 2016 at 11:19 AM, Osura Rathnayake 
wrote:

> Hi Akila,
>
> Thank you for the feedback and please accept my apologies for the delayed
> response.
> I updated the code according to the guidelines you have provided on coding
> standards and pushed it to the repository [1].
> tenantId is used here [2].
> I'm not familiar with Netflix Feign standard on HTTP requests. Can you
> please explain it briefly or mention a link to a tutorial?
>
> [1] https://github.com/osuran/azure-membership-scheme
> [2]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L168
>
> Thanks,
>
> On Fri, Jun 24, 2016 at 10:49 PM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Osura,
>>>
>>> I still see some issues in the code.
>>>
>>> 1. Make sure to use consts when appropriate [1]
>>> 2. Where do you use tenantId [2] ?
>>> 3. Use the actual parameter key in the error message [3] instead of hard
>>> coding it
>>> 4. You need to adhere to max line len of 120 chars. I see this standard
>>> being violated in couple of places [4]. Use IDE formatting tool to fix this
>>> 5. Do not keep empty spaces [5]. This is bad code styling
>>>
>>> @Imesh: Osura has used Apache HTTP client to send HTTP requests [6].
>>> Shall we make Netflix Feign the standard for this?
>>>
>>
>> ​+1 Yes, definitely.
>>
>> Thanks​
>>
>>
>>>
>>> [1]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
>>> [2]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
>>> [3]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
>>> [4]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
>>> [5]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
>>> [6]
>>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234
>>>
>>> Thanks.
>>>
>>> On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne 
>>> wrote:
>>>


 On Fri, Jun 24, 2016 at 11:00 AM,  wrote:

> Hi Imesh,
>
> Yes I completed the evaluation.
>
 ​Great! Thanks!​

> Thanks,
>
> Get Outlook for Android 
>
>
>
> On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" <
> im...@wso2.com> wrote:
>
> Hi Osura,
>>
>> Were you able to submit the midterm evaluation? Might be better to do
>> it soon.
>>
>> Thanks
>> ​Imesh​
>>
>>


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


>>>
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.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
>>
>>
>
>
> --
> Regards,
> Osura Rathnayake
>



-- 
Regards,
Osura Rathnayake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Akila,

Thank you for the feedback and please accept my apologies for the delayed
response.
I updated the code according to the guidelines you have provided on coding
standards and pushed it to the repository [1].
tenantId is used here [2].
I'm not familiar with Netflix Feign standard on HTTP requests. Can you
please explain it briefly or mention a link to a tutorial?

[1] https://github.com/osuran/azure-membership-scheme
[2]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L168

Thanks,

On Fri, Jun 24, 2016 at 10:49 PM, Imesh Gunaratne  wrote:

>
>
> On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Osura,
>>
>> I still see some issues in the code.
>>
>> 1. Make sure to use consts when appropriate [1]
>> 2. Where do you use tenantId [2] ?
>> 3. Use the actual parameter key in the error message [3] instead of hard
>> coding it
>> 4. You need to adhere to max line len of 120 chars. I see this standard
>> being violated in couple of places [4]. Use IDE formatting tool to fix this
>> 5. Do not keep empty spaces [5]. This is bad code styling
>>
>> @Imesh: Osura has used Apache HTTP client to send HTTP requests [6].
>> Shall we make Netflix Feign the standard for this?
>>
>
> ​+1 Yes, definitely.
>
> Thanks​
>
>
>>
>> [1]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
>> [2]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
>> [3]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
>> [4]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
>> [5]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
>> [6]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234
>>
>> Thanks.
>>
>> On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Fri, Jun 24, 2016 at 11:00 AM,  wrote:
>>>
 Hi Imesh,

 Yes I completed the evaluation.

>>> ​Great! Thanks!​
>>>
 Thanks,

 Get Outlook for Android 



 On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" <
 im...@wso2.com> wrote:

 Hi Osura,
>
> Were you able to submit the midterm evaluation? Might be better to do
> it soon.
>
> Thanks
> ​Imesh​
>
>
>>>
>>>
>>> --
>>> *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
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.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
>
>


-- 
Regards,
Osura Rathnayake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Fri, Jun 24, 2016 at 10:43 PM, Akila Ravihansa Perera  wrote:

> Hi Osura,
>
> I still see some issues in the code.
>
> 1. Make sure to use consts when appropriate [1]
> 2. Where do you use tenantId [2] ?
> 3. Use the actual parameter key in the error message [3] instead of hard
> coding it
> 4. You need to adhere to max line len of 120 chars. I see this standard
> being violated in couple of places [4]. Use IDE formatting tool to fix this
> 5. Do not keep empty spaces [5]. This is bad code styling
>
> @Imesh: Osura has used Apache HTTP client to send HTTP requests [6]. Shall
> we make Netflix Feign the standard for this?
>

​+1 Yes, definitely.

Thanks​


>
> [1]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
> [2]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
> [3]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
> [4]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
> [5]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
> [6]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234
>
> Thanks.
>
> On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Fri, Jun 24, 2016 at 11:00 AM,  wrote:
>>
>>> Hi Imesh,
>>>
>>> Yes I completed the evaluation.
>>>
>> ​Great! Thanks!​
>>
>>> Thanks,
>>>
>>> Get Outlook for Android 
>>>
>>>
>>>
>>> On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" <
>>> im...@wso2.com> wrote:
>>>
>>> Hi Osura,

 Were you able to submit the midterm evaluation? Might be better to do
 it soon.

 Thanks
 ​Imesh​


>>
>>
>> --
>> *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
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi Osura,

I still see some issues in the code.

1. Make sure to use consts when appropriate [1]
2. Where do you use tenantId [2] ?
3. Use the actual parameter key in the error message [3] instead of hard
coding it
4. You need to adhere to max line len of 120 chars. I see this standard
being violated in couple of places [4]. Use IDE formatting tool to fix this
5. Do not keep empty spaces [5]. This is bad code styling

@Imesh: Osura has used Apache HTTP client to send HTTP requests [6]. Shall
we make Netflix Feign the standard for this?

[1]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L117
[2]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L107
[3]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L148
[4]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L181
[5]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L94
[6]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L234

Thanks.

On Fri, Jun 24, 2016 at 11:05 AM, Imesh Gunaratne  wrote:

>
>
> On Fri, Jun 24, 2016 at 11:00 AM,  wrote:
>
>> Hi Imesh,
>>
>> Yes I completed the evaluation.
>>
> ​Great! Thanks!​
>
>> Thanks,
>>
>> Get Outlook for Android 
>>
>>
>>
>> On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" > > wrote:
>>
>> Hi Osura,
>>>
>>> Were you able to submit the midterm evaluation? Might be better to do it
>>> soon.
>>>
>>> Thanks
>>> ​Imesh​
>>>
>>>
>
>
> --
> *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
>
>


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

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Fri, Jun 24, 2016 at 11:00 AM,  wrote:

> Hi Imesh,
>
> Yes I completed the evaluation.
>
​Great! Thanks!​

> Thanks,
>
> Get Outlook for Android 
>
>
>
> On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne" 
> wrote:
>
> Hi Osura,
>>
>> Were you able to submit the midterm evaluation? Might be better to do it
>> soon.
>>
>> Thanks
>> ​Imesh​
>>
>>


-- 
*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] [GSOC 16] Initial Project Progress

[osuranew]

Hi Imesh, 


Yes I completed the evaluation. 


Thanks, 


Get Outlook for Android






On Fri, Jun 24, 2016 at 10:08 AM +0530, "Imesh Gunaratne"  
wrote:










Hi Osura,

Were you able to submit the midterm evaluation? Might be better to do it soon.

Thanks​Imesh​







___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

Hi Osura,

Were you able to submit the midterm evaluation? Might be better to do it
soon.

Thanks
​Imesh​
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Akila,

Thank you for the feedback.
I fixed all the bugs you had specified in your previous email and pushed to
the repository [1].

[1] https://github.com/osuran/azure-membership-scheme

On Thu, Jun 23, 2016 at 2:52 PM, Akila Ravihansa Perera 
wrote:

> Hi Osura,
>
> The code base still needs to be cleaned up.
>
> 1. Unnecessary class in [1]
> 2. Package structure should be refactored from
> *com.osura.membershipscheme* to *org.wso2.carbon.clustering.azure*
> 3. Put proper JavaDoc comments for classes and methods. [2]
> 4. Do not keep commented code [3]
> 5. Use String.format when logging parameters [4]
> 6. Do not print the stack trace to console [5]
> 7. Thread pool should be initialized separately as a one time task [6]
> 8. Keep default values as separate consts and use them if no value is
> specified [7]
> 9. Put the WSO2 license header in every file
> 10. Write unit tests to verify the functionality
> 11. validateAuthority flag should be configurable [8]
>
> [1]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/App.java
> [2]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/AzureMembershipScheme.java#L44
> [3]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/AzureMembershipScheme.java#L67
> [4]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/AzureMembershipScheme.java#L293
> [5]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/authentication/Authentication.java#L38
> [6]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/authentication/Authentication.java#L25
> [7]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/Constants.java#L13
> [8]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/authentication/Authentication.java#L27
>
> Please make sure you complete the above tasks before arranging a code
> review.
>
> Thanks.
>
> On Thu, Jun 23, 2016 at 12:15 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> Please arrange a hangout for the code review of membership scheme at any
>> time which is convenient for you.
>>
>> thanks,
>>
>> On Wed, Jun 22, 2016 at 3:21 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> I have handled the exceptions and pushed the changes to my repository
>>> [1]. Please have a look
>>>
>>>
>>>
>>> [1] https://github.com/osuran/azure-membership-scheme
>>>
>>> thanks,
>>>
>>> On Wed, Jun 22, 2016 at 11:42 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Thank you very much for the feedback.
 I updated the snapshot dependency with a released version. Also I made
 it use Jackson to parse the API responses using bean classes. And I
 properly formatted the code as well. Exceptions handling is still on the
 way.
 Sure will have a code review this week.


 On Tue, Jun 21, 2016 at 10:18 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> I went through the code at [1] briefly. Some general comments:
>
>- The code is not properly formatted
>- The code has a SNAPSHOT dependency for org.wso2.carbon.utils. If
>you do not have a specific reason to do so, its better to use a 
> released
>version.
>- To parse the responses from the rest API, you are directly
>manipulating JSON objects. Have a look at the Kubernetes Membership 
> Scheme.
>Its using Jackson to parse the API responses using bean classes. This 
> would
>be much easier than directly interacting with JSON structures. Or 
> else, you
>can use Netflix Feign as a REST API client [2], in which the amount of 
> code
>you have to write is very less.
>- System.exit(1) is used in few places to handle error scenarios,
>which is wrong. Please use a proper Exception for the purpose
>
> Noted that you have updated the README file, which is great. Lets have
> a code review this week to go through the functional aspects at a more 
> fine
> grained level.
>
> [1]. https://github.com/osuran/azure-membership-scheme.git
>
> [2]. https://github.com/Netflix/feign
>
> On Thu, Jun 16, 2016 at 11:23 AM, Osura Rathnayake  > wrote:
>
>> Hi Isuru,
>>
>> That's great, will do the demo at 3 o'clock in the evening today.
>> thanks
>>
>> On Thu, Jun 16, 2016 at 11:21 AM, Isuru Haththotuwa 
>> wrote:
>>
>>>
>>>
>>> On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake 

Re: [Dev] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi Osura,

The code base still needs to be cleaned up.

1. Unnecessary class in [1]
2. Package structure should be refactored from *com.osura.membershipscheme*
to *org.wso2.carbon.clustering.azure*
3. Put proper JavaDoc comments for classes and methods. [2]
4. Do not keep commented code [3]
5. Use String.format when logging parameters [4]
6. Do not print the stack trace to console [5]
7. Thread pool should be initialized separately as a one time task [6]
8. Keep default values as separate consts and use them if no value is
specified [7]
9. Put the WSO2 license header in every file
10. Write unit tests to verify the functionality
11. validateAuthority flag should be configurable [8]

[1]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/App.java
[2]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/AzureMembershipScheme.java#L44
[3]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/AzureMembershipScheme.java#L67
[4]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/AzureMembershipScheme.java#L293
[5]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/authentication/Authentication.java#L38
[6]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/authentication/Authentication.java#L25
[7]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/Constants.java#L13
[8]
https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/com/osura/membershipscheme/azure/authentication/Authentication.java#L27

Please make sure you complete the above tasks before arranging a code
review.

Thanks.

On Thu, Jun 23, 2016 at 12:15 PM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> Please arrange a hangout for the code review of membership scheme at any
> time which is convenient for you.
>
> thanks,
>
> On Wed, Jun 22, 2016 at 3:21 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I have handled the exceptions and pushed the changes to my repository
>> [1]. Please have a look
>>
>>
>>
>> [1] https://github.com/osuran/azure-membership-scheme
>>
>> thanks,
>>
>> On Wed, Jun 22, 2016 at 11:42 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you very much for the feedback.
>>> I updated the snapshot dependency with a released version. Also I made
>>> it use Jackson to parse the API responses using bean classes. And I
>>> properly formatted the code as well. Exceptions handling is still on the
>>> way.
>>> Sure will have a code review this week.
>>>
>>>
>>> On Tue, Jun 21, 2016 at 10:18 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 I went through the code at [1] briefly. Some general comments:

- The code is not properly formatted
- The code has a SNAPSHOT dependency for org.wso2.carbon.utils. If
you do not have a specific reason to do so, its better to use a released
version.
- To parse the responses from the rest API, you are directly
manipulating JSON objects. Have a look at the Kubernetes Membership 
 Scheme.
Its using Jackson to parse the API responses using bean classes. This 
 would
be much easier than directly interacting with JSON structures. Or else, 
 you
can use Netflix Feign as a REST API client [2], in which the amount of 
 code
you have to write is very less.
- System.exit(1) is used in few places to handle error scenarios,
which is wrong. Please use a proper Exception for the purpose

 Noted that you have updated the README file, which is great. Lets have
 a code review this week to go through the functional aspects at a more fine
 grained level.

 [1]. https://github.com/osuran/azure-membership-scheme.git

 [2]. https://github.com/Netflix/feign

 On Thu, Jun 16, 2016 at 11:23 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> That's great, will do the demo at 3 o'clock in the evening today.
> thanks
>
> On Thu, Jun 16, 2016 at 11:21 AM, Isuru Haththotuwa 
> wrote:
>
>>
>>
>> On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Hi Mentors,
>>>
>>> Thank you for the update.
>>> Yes I can demonstrate it anytime today.
>>>
>> Great! Shall we have a hangout at 3.00 PM? The main purpose would be
>> to demonstrate the membership scheme functionality with a carbon cluster
>> deployed in Azure.
>>
>>>
>>>
>>> thanks
>>>
>>> On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

Please arrange a hangout for the code review of membership scheme at any
time which is convenient for you.

thanks,

On Wed, Jun 22, 2016 at 3:21 PM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I have handled the exceptions and pushed the changes to my repository [1].
> Please have a look
>
>
>
> [1] https://github.com/osuran/azure-membership-scheme
>
> thanks,
>
> On Wed, Jun 22, 2016 at 11:42 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you very much for the feedback.
>> I updated the snapshot dependency with a released version. Also I made it
>> use Jackson to parse the API responses using bean classes. And I
>> properly formatted the code as well. Exceptions handling is still on the
>> way.
>> Sure will have a code review this week.
>>
>>
>> On Tue, Jun 21, 2016 at 10:18 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> I went through the code at [1] briefly. Some general comments:
>>>
>>>- The code is not properly formatted
>>>- The code has a SNAPSHOT dependency for org.wso2.carbon.utils. If
>>>you do not have a specific reason to do so, its better to use a released
>>>version.
>>>- To parse the responses from the rest API, you are directly
>>>manipulating JSON objects. Have a look at the Kubernetes Membership 
>>> Scheme.
>>>Its using Jackson to parse the API responses using bean classes. This 
>>> would
>>>be much easier than directly interacting with JSON structures. Or else, 
>>> you
>>>can use Netflix Feign as a REST API client [2], in which the amount of 
>>> code
>>>you have to write is very less.
>>>- System.exit(1) is used in few places to handle error scenarios,
>>>which is wrong. Please use a proper Exception for the purpose
>>>
>>> Noted that you have updated the README file, which is great. Lets have a
>>> code review this week to go through the functional aspects at a more fine
>>> grained level.
>>>
>>> [1]. https://github.com/osuran/azure-membership-scheme.git
>>>
>>> [2]. https://github.com/Netflix/feign
>>>
>>> On Thu, Jun 16, 2016 at 11:23 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 That's great, will do the demo at 3 o'clock in the evening today.
 thanks

 On Thu, Jun 16, 2016 at 11:21 AM, Isuru Haththotuwa 
 wrote:

>
>
> On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake  > wrote:
>
>> Hi Mentors,
>>
>> Thank you for the update.
>> Yes I can demonstrate it anytime today.
>>
> Great! Shall we have a hangout at 3.00 PM? The main purpose would be
> to demonstrate the membership scheme functionality with a carbon cluster
> deployed in Azure.
>
>>
>>
>> thanks
>>
>> On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Would you be able to demonstrate the functionality of the membership
>>> scheme today?
>>>
>>> Also, please keep an eye on the timeline for the project [1], as the
>>> midterm evaluations will be starting on 20th.
>>>
>>> [1]. https://developers.google.com/open-source/gsoc/timeline
>>>
>>> On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne 
>>> wrote:
>>>


 On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Mentors,
>
> As we discussed at the very beginning, next in line is to see how
> each of the following can be setup on Azure using native features:
>
>- Auto healing
>- Autoscaling
>- Dynamic load balancing
>- Centralized logging
>- Monitoring
>- Metering
>
> For auto healing, we can implement it in both VM level and
> application level. In VM level, we can poll for VM statuses and check 
> if a
> given VM is down or not. And then we can up them if they have gone 
> down,
> using api calls. for application level of course we will have to run a
> shell script to determine the status of a given application and will 
> have
> to up it accordingly. I'm looking forward to hear from you regarding 
> this.
>

 ​No, auto healing and autoscaling should be handled by Azure. We
 might not need to write code to handle that.

 Thanks​


>
> thanks,
>
> On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake <
> osura...@gmail.com> wrote:
>
>> Hi Isuru,
>>
>> Can you please tell me when you would be free to have a hangout
>> to do a code review and discuss next project goals?
>>
>> Thanks,
>>
>> On Saturday, June 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

I have handled the exceptions and pushed the changes to my repository [1].
Please have a look



[1] https://github.com/osuran/azure-membership-scheme

thanks,

On Wed, Jun 22, 2016 at 11:42 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Thank you very much for the feedback.
> I updated the snapshot dependency with a released version. Also I made it
> use Jackson to parse the API responses using bean classes. And I properly
> formatted the code as well. Exceptions handling is still on the way.
> Sure will have a code review this week.
>
>
> On Tue, Jun 21, 2016 at 10:18 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> I went through the code at [1] briefly. Some general comments:
>>
>>- The code is not properly formatted
>>- The code has a SNAPSHOT dependency for org.wso2.carbon.utils. If
>>you do not have a specific reason to do so, its better to use a released
>>version.
>>- To parse the responses from the rest API, you are directly
>>manipulating JSON objects. Have a look at the Kubernetes Membership 
>> Scheme.
>>Its using Jackson to parse the API responses using bean classes. This 
>> would
>>be much easier than directly interacting with JSON structures. Or else, 
>> you
>>can use Netflix Feign as a REST API client [2], in which the amount of 
>> code
>>you have to write is very less.
>>- System.exit(1) is used in few places to handle error scenarios,
>>which is wrong. Please use a proper Exception for the purpose
>>
>> Noted that you have updated the README file, which is great. Lets have a
>> code review this week to go through the functional aspects at a more fine
>> grained level.
>>
>> [1]. https://github.com/osuran/azure-membership-scheme.git
>>
>> [2]. https://github.com/Netflix/feign
>>
>> On Thu, Jun 16, 2016 at 11:23 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> That's great, will do the demo at 3 o'clock in the evening today.
>>> thanks
>>>
>>> On Thu, Jun 16, 2016 at 11:21 AM, Isuru Haththotuwa 
>>> wrote:
>>>


 On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> Thank you for the update.
> Yes I can demonstrate it anytime today.
>
 Great! Shall we have a hangout at 3.00 PM? The main purpose would be to
 demonstrate the membership scheme functionality with a carbon cluster
 deployed in Azure.

>
>
> thanks
>
> On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Would you be able to demonstrate the functionality of the membership
>> scheme today?
>>
>> Also, please keep an eye on the timeline for the project [1], as the
>> midterm evaluations will be starting on 20th.
>>
>> [1]. https://developers.google.com/open-source/gsoc/timeline
>>
>> On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne 
>> wrote:
>>
>>>
>>>
>>> On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Mentors,

 As we discussed at the very beginning, next in line is to see how
 each of the following can be setup on Azure using native features:

- Auto healing
- Autoscaling
- Dynamic load balancing
- Centralized logging
- Monitoring
- Metering

 For auto healing, we can implement it in both VM level and
 application level. In VM level, we can poll for VM statuses and check 
 if a
 given VM is down or not. And then we can up them if they have gone 
 down,
 using api calls. for application level of course we will have to run a
 shell script to determine the status of a given application and will 
 have
 to up it accordingly. I'm looking forward to hear from you regarding 
 this.

>>>
>>> ​No, auto healing and autoscaling should be handled by Azure. We
>>> might not need to write code to handle that.
>>>
>>> Thanks​
>>>
>>>

 thanks,

 On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Isuru,
>
> Can you please tell me when you would be free to have a hangout to
> do a code review and discuss next project goals?
>
> Thanks,
>
> On Saturday, June 11, 2016, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you very much.
>> Yes there was a misconfiguration in registry mounts and now it
>> works properly.
>> Okay will have a code review next week.
>>
>>
>> On Fri, Jun 10, 2016 at 9:45 AM, Isuru 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Thank you very much for the feedback.
I updated the snapshot dependency with a released version. Also I made it
use Jackson to parse the API responses using bean classes. And I properly
formatted the code as well. Exceptions handling is still on the way.
Sure will have a code review this week.


On Tue, Jun 21, 2016 at 10:18 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> I went through the code at [1] briefly. Some general comments:
>
>- The code is not properly formatted
>- The code has a SNAPSHOT dependency for org.wso2.carbon.utils. If you
>do not have a specific reason to do so, its better to use a released
>version.
>- To parse the responses from the rest API, you are directly
>manipulating JSON objects. Have a look at the Kubernetes Membership Scheme.
>Its using Jackson to parse the API responses using bean classes. This would
>be much easier than directly interacting with JSON structures. Or else, you
>can use Netflix Feign as a REST API client [2], in which the amount of code
>you have to write is very less.
>- System.exit(1) is used in few places to handle error scenarios,
>which is wrong. Please use a proper Exception for the purpose
>
> Noted that you have updated the README file, which is great. Lets have a
> code review this week to go through the functional aspects at a more fine
> grained level.
>
> [1]. https://github.com/osuran/azure-membership-scheme.git
>
> [2]. https://github.com/Netflix/feign
>
> On Thu, Jun 16, 2016 at 11:23 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> That's great, will do the demo at 3 o'clock in the evening today.
>> thanks
>>
>> On Thu, Jun 16, 2016 at 11:21 AM, Isuru Haththotuwa 
>> wrote:
>>
>>>
>>>
>>> On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 Thank you for the update.
 Yes I can demonstrate it anytime today.

>>> Great! Shall we have a hangout at 3.00 PM? The main purpose would be to
>>> demonstrate the membership scheme functionality with a carbon cluster
>>> deployed in Azure.
>>>


 thanks

 On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Would you be able to demonstrate the functionality of the membership
> scheme today?
>
> Also, please keep an eye on the timeline for the project [1], as the
> midterm evaluations will be starting on 20th.
>
> [1]. https://developers.google.com/open-source/gsoc/timeline
>
> On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne 
> wrote:
>
>>
>>
>> On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Mentors,
>>>
>>> As we discussed at the very beginning, next in line is to see how
>>> each of the following can be setup on Azure using native features:
>>>
>>>- Auto healing
>>>- Autoscaling
>>>- Dynamic load balancing
>>>- Centralized logging
>>>- Monitoring
>>>- Metering
>>>
>>> For auto healing, we can implement it in both VM level and
>>> application level. In VM level, we can poll for VM statuses and check 
>>> if a
>>> given VM is down or not. And then we can up them if they have gone down,
>>> using api calls. for application level of course we will have to run a
>>> shell script to determine the status of a given application and will 
>>> have
>>> to up it accordingly. I'm looking forward to hear from you regarding 
>>> this.
>>>
>>
>> ​No, auto healing and autoscaling should be handled by Azure. We
>> might not need to write code to handle that.
>>
>> Thanks​
>>
>>
>>>
>>> thanks,
>>>
>>> On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Isuru,

 Can you please tell me when you would be free to have a hangout to
 do a code review and discuss next project goals?

 Thanks,

 On Saturday, June 11, 2016, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> Thank you very much.
> Yes there was a misconfiguration in registry mounts and now it
> works properly.
> Okay will have a code review next week.
>
>
> On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa <
> isu...@wso2.com> wrote:
>
>> Hi Osura,
>>
>> This is great progress! This shows that a clustered deployment of
>> WSO2 products on Azure is possible with this membership scheme.
>>
>> About the error, what is says is that a particular resource that
>> the first node is expecting to find in the config registry is not 
>> found.

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

I went through the code at [1] briefly. Some general comments:

   - The code is not properly formatted
   - The code has a SNAPSHOT dependency for org.wso2.carbon.utils. If you
   do not have a specific reason to do so, its better to use a released
   version.
   - To parse the responses from the rest API, you are directly
   manipulating JSON objects. Have a look at the Kubernetes Membership Scheme.
   Its using Jackson to parse the API responses using bean classes. This would
   be much easier than directly interacting with JSON structures. Or else, you
   can use Netflix Feign as a REST API client [2], in which the amount of code
   you have to write is very less.
   - System.exit(1) is used in few places to handle error scenarios, which
   is wrong. Please use a proper Exception for the purpose

Noted that you have updated the README file, which is great. Lets have a
code review this week to go through the functional aspects at a more fine
grained level.

[1]. https://github.com/osuran/azure-membership-scheme.git

[2]. https://github.com/Netflix/feign

On Thu, Jun 16, 2016 at 11:23 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> That's great, will do the demo at 3 o'clock in the evening today.
> thanks
>
> On Thu, Jun 16, 2016 at 11:21 AM, Isuru Haththotuwa 
> wrote:
>
>>
>>
>> On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> Thank you for the update.
>>> Yes I can demonstrate it anytime today.
>>>
>> Great! Shall we have a hangout at 3.00 PM? The main purpose would be to
>> demonstrate the membership scheme functionality with a carbon cluster
>> deployed in Azure.
>>
>>>
>>>
>>> thanks
>>>
>>> On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Would you be able to demonstrate the functionality of the membership
 scheme today?

 Also, please keep an eye on the timeline for the project [1], as the
 midterm evaluations will be starting on 20th.

 [1]. https://developers.google.com/open-source/gsoc/timeline

 On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne 
 wrote:

>
>
> On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> As we discussed at the very beginning, next in line is to see how
>> each of the following can be setup on Azure using native features:
>>
>>- Auto healing
>>- Autoscaling
>>- Dynamic load balancing
>>- Centralized logging
>>- Monitoring
>>- Metering
>>
>> For auto healing, we can implement it in both VM level and
>> application level. In VM level, we can poll for VM statuses and check if 
>> a
>> given VM is down or not. And then we can up them if they have gone down,
>> using api calls. for application level of course we will have to run a
>> shell script to determine the status of a given application and will have
>> to up it accordingly. I'm looking forward to hear from you regarding 
>> this.
>>
>
> ​No, auto healing and autoscaling should be handled by Azure. We might
> not need to write code to handle that.
>
> Thanks​
>
>
>>
>> thanks,
>>
>> On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Hi Isuru,
>>>
>>> Can you please tell me when you would be free to have a hangout to
>>> do a code review and discuss next project goals?
>>>
>>> Thanks,
>>>
>>> On Saturday, June 11, 2016, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Thank you very much.
 Yes there was a misconfiguration in registry mounts and now it
 works properly.
 Okay will have a code review next week.


 On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> This is great progress! This shows that a clustered deployment of
> WSO2 products on Azure is possible with this membership scheme.
>
> About the error, what is says is that a particular resource that
> the first node is expecting to find in the config registry is not 
> found.
> This can be due to a mis-configured registry mounts. Did you mount the
> config and governance registries? If not please do so by referring 
> [1].
>
> Lets schedule a code review early next week for the membership
> scheme.
>
> [1].
> https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database
>
> On Fri, Jun 10, 2016 at 12:42 AM, Osura Rathnayake <
> osura...@gmail.com> wrote:
>
>> Hi Mentors,
>>
>> I have two application 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

That's great, will do the demo at 3 o'clock in the evening today.
thanks

On Thu, Jun 16, 2016 at 11:21 AM, Isuru Haththotuwa  wrote:

>
>
> On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> Thank you for the update.
>> Yes I can demonstrate it anytime today.
>>
> Great! Shall we have a hangout at 3.00 PM? The main purpose would be to
> demonstrate the membership scheme functionality with a carbon cluster
> deployed in Azure.
>
>>
>>
>> thanks
>>
>> On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Would you be able to demonstrate the functionality of the membership
>>> scheme today?
>>>
>>> Also, please keep an eye on the timeline for the project [1], as the
>>> midterm evaluations will be starting on 20th.
>>>
>>> [1]. https://developers.google.com/open-source/gsoc/timeline
>>>
>>> On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne  wrote:
>>>


 On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> As we discussed at the very beginning, next in line is to see how
> each of the following can be setup on Azure using native features:
>
>- Auto healing
>- Autoscaling
>- Dynamic load balancing
>- Centralized logging
>- Monitoring
>- Metering
>
> For auto healing, we can implement it in both VM level and application
> level. In VM level, we can poll for VM statuses and check if a given VM is
> down or not. And then we can up them if they have gone down, using api
> calls. for application level of course we will have to run a shell script
> to determine the status of a given application and will have to up it
> accordingly. I'm looking forward to hear from you regarding this.
>

 ​No, auto healing and autoscaling should be handled by Azure. We might
 not need to write code to handle that.

 Thanks​


>
> thanks,
>
> On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake  > wrote:
>
>> Hi Isuru,
>>
>> Can you please tell me when you would be free to have a hangout to do
>> a code review and discuss next project goals?
>>
>> Thanks,
>>
>> On Saturday, June 11, 2016, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you very much.
>>> Yes there was a misconfiguration in registry mounts and now it works
>>> properly.
>>> Okay will have a code review next week.
>>>
>>>
>>> On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 This is great progress! This shows that a clustered deployment of
 WSO2 products on Azure is possible with this membership scheme.

 About the error, what is says is that a particular resource that
 the first node is expecting to find in the config registry is not 
 found.
 This can be due to a mis-configured registry mounts. Did you mount the
 config and governance registries? If not please do so by referring [1].

 Lets schedule a code review early next week for the membership
 scheme.

 [1].
 https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database

 On Fri, Jun 10, 2016 at 12:42 AM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Mentors,
>
> I have two application servers (AS) running on azure and I'm
> testing the azure membership scheme on them. When I run the first AS I
> could see member added and member joined log messages. And when I run 
> the
> second AS, I could see member added log messages and then I get an 
> error
> saying carbon initialization failed (screenshot attached as error6). 
> Also
> when I stopped the second AS I could see member left log message on 
> the
> first AS( screenshot attached as Capture1).
>
> Afterwards I stopped both of them and started the second AS first
> and it ran without errors but the other AS( previous case I started 
> this AS
> first) showed up the same error which I got earlier. I'm getting this 
> error
> always from the secondly started AS. Please share with me if you have 
> any
> idea why I'm getting this.
>
> Thanks,
>
> On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake <
> osura...@gmail.com> wrote:
>
>> Hi all,
>>
>> This is the summary of the matters that we discussed during
>> hangout we had on 6th of June, 2016.
>>
>> We had a productive discussion on how to pass 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> Thank you for the update.
> Yes I can demonstrate it anytime today.
>
Great! Shall we have a hangout at 3.00 PM? The main purpose would be to
demonstrate the membership scheme functionality with a carbon cluster
deployed in Azure.

>
>
> thanks
>
> On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Would you be able to demonstrate the functionality of the membership
>> scheme today?
>>
>> Also, please keep an eye on the timeline for the project [1], as the
>> midterm evaluations will be starting on 20th.
>>
>> [1]. https://developers.google.com/open-source/gsoc/timeline
>>
>> On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 As we discussed at the very beginning, next in line is to see how each
 of the following can be setup on Azure using native features:

- Auto healing
- Autoscaling
- Dynamic load balancing
- Centralized logging
- Monitoring
- Metering

 For auto healing, we can implement it in both VM level and application
 level. In VM level, we can poll for VM statuses and check if a given VM is
 down or not. And then we can up them if they have gone down, using api
 calls. for application level of course we will have to run a shell script
 to determine the status of a given application and will have to up it
 accordingly. I'm looking forward to hear from you regarding this.

>>>
>>> ​No, auto healing and autoscaling should be handled by Azure. We might
>>> not need to write code to handle that.
>>>
>>> Thanks​
>>>
>>>

 thanks,

 On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> Can you please tell me when you would be free to have a hangout to do
> a code review and discuss next project goals?
>
> Thanks,
>
> On Saturday, June 11, 2016, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you very much.
>> Yes there was a misconfiguration in registry mounts and now it works
>> properly.
>> Okay will have a code review next week.
>>
>>
>> On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> This is great progress! This shows that a clustered deployment of
>>> WSO2 products on Azure is possible with this membership scheme.
>>>
>>> About the error, what is says is that a particular resource that the
>>> first node is expecting to find in the config registry is not found. 
>>> This
>>> can be due to a mis-configured registry mounts. Did you mount the config
>>> and governance registries? If not please do so by referring [1].
>>>
>>> Lets schedule a code review early next week for the membership
>>> scheme.
>>>
>>> [1].
>>> https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database
>>>
>>> On Fri, Jun 10, 2016 at 12:42 AM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Mentors,

 I have two application servers (AS) running on azure and I'm
 testing the azure membership scheme on them. When I run the first AS I
 could see member added and member joined log messages. And when I run 
 the
 second AS, I could see member added log messages and then I get an 
 error
 saying carbon initialization failed (screenshot attached as error6). 
 Also
 when I stopped the second AS I could see member left log message on the
 first AS( screenshot attached as Capture1).

 Afterwards I stopped both of them and started the second AS first
 and it ran without errors but the other AS( previous case I started 
 this AS
 first) showed up the same error which I got earlier. I'm getting this 
 error
 always from the secondly started AS. Please share with me if you have 
 any
 idea why I'm getting this.

 Thanks,

 On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi all,
>
> This is the summary of the matters that we discussed during
> hangout we had on 6th of June, 2016.
>
> We had a productive discussion on how to pass the azure specific
> parameters to the Azure membership scheme and how we should test the 
> Azure
> membership scheme
>
> Current progress : Getting a list of IP addresses of members in
> the cluster and updating the hazelcast configuration are done but 
> certain

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

Thank you for the update.
Yes I can demonstrate it anytime today.


thanks

On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> Would you be able to demonstrate the functionality of the membership
> scheme today?
>
> Also, please keep an eye on the timeline for the project [1], as the
> midterm evaluations will be starting on 20th.
>
> [1]. https://developers.google.com/open-source/gsoc/timeline
>
> On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> As we discussed at the very beginning, next in line is to see how each
>>> of the following can be setup on Azure using native features:
>>>
>>>- Auto healing
>>>- Autoscaling
>>>- Dynamic load balancing
>>>- Centralized logging
>>>- Monitoring
>>>- Metering
>>>
>>> For auto healing, we can implement it in both VM level and application
>>> level. In VM level, we can poll for VM statuses and check if a given VM is
>>> down or not. And then we can up them if they have gone down, using api
>>> calls. for application level of course we will have to run a shell script
>>> to determine the status of a given application and will have to up it
>>> accordingly. I'm looking forward to hear from you regarding this.
>>>
>>
>> ​No, auto healing and autoscaling should be handled by Azure. We might
>> not need to write code to handle that.
>>
>> Thanks​
>>
>>
>>>
>>> thanks,
>>>
>>> On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Can you please tell me when you would be free to have a hangout to do a
 code review and discuss next project goals?

 Thanks,

 On Saturday, June 11, 2016, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> Thank you very much.
> Yes there was a misconfiguration in registry mounts and now it works
> properly.
> Okay will have a code review next week.
>
>
> On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> This is great progress! This shows that a clustered deployment of
>> WSO2 products on Azure is possible with this membership scheme.
>>
>> About the error, what is says is that a particular resource that the
>> first node is expecting to find in the config registry is not found. This
>> can be due to a mis-configured registry mounts. Did you mount the config
>> and governance registries? If not please do so by referring [1].
>>
>> Lets schedule a code review early next week for the membership scheme.
>>
>> [1]. https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database
>>
>> On Fri, Jun 10, 2016 at 12:42 AM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Hi Mentors,
>>>
>>> I have two application servers (AS) running on azure and I'm testing
>>> the azure membership scheme on them. When I run the first AS I could see
>>> member added and member joined log messages. And when I run the second 
>>> AS,
>>> I could see member added log messages and then I get an error saying 
>>> carbon
>>> initialization failed (screenshot attached as error6). Also when I 
>>> stopped
>>> the second AS I could see member left log message on the first AS(
>>> screenshot attached as Capture1).
>>>
>>> Afterwards I stopped both of them and started the second AS first
>>> and it ran without errors but the other AS( previous case I started 
>>> this AS
>>> first) showed up the same error which I got earlier. I'm getting this 
>>> error
>>> always from the secondly started AS. Please share with me if you have 
>>> any
>>> idea why I'm getting this.
>>>
>>> Thanks,
>>>
>>> On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake >> > wrote:
>>>
 Hi all,

 This is the summary of the matters that we discussed during hangout
 we had on 6th of June, 2016.

 We had a productive discussion on how to pass the azure specific
 parameters to the Azure membership scheme and how we should test the 
 Azure
 membership scheme

 Current progress : Getting a list of IP addresses of members in the
 cluster and updating the hazelcast configuration are done but certain 
 azure
 specific parameters are hard coded in the program.

 As in kubernetes membership scheme, we agreed upon sending those
 parameters as either environment variables or system properties. So the
 next immediate goal is to get those parameters that way. As of how to 
 test
 the azure membership scheme, [1] was shared get a more clear idea on 
 the

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

Would you be able to demonstrate the functionality of the membership scheme
today?

Also, please keep an eye on the timeline for the project [1], as the
midterm evaluations will be starting on 20th.

[1]. https://developers.google.com/open-source/gsoc/timeline

On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne  wrote:

>
>
> On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> As we discussed at the very beginning, next in line is to see how each
>> of the following can be setup on Azure using native features:
>>
>>- Auto healing
>>- Autoscaling
>>- Dynamic load balancing
>>- Centralized logging
>>- Monitoring
>>- Metering
>>
>> For auto healing, we can implement it in both VM level and application
>> level. In VM level, we can poll for VM statuses and check if a given VM is
>> down or not. And then we can up them if they have gone down, using api
>> calls. for application level of course we will have to run a shell script
>> to determine the status of a given application and will have to up it
>> accordingly. I'm looking forward to hear from you regarding this.
>>
>
> ​No, auto healing and autoscaling should be handled by Azure. We might not
> need to write code to handle that.
>
> Thanks​
>
>
>>
>> thanks,
>>
>> On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Can you please tell me when you would be free to have a hangout to do a
>>> code review and discuss next project goals?
>>>
>>> Thanks,
>>>
>>> On Saturday, June 11, 2016, Osura Rathnayake  wrote:
>>>
 Hi Isuru,

 Thank you very much.
 Yes there was a misconfiguration in registry mounts and now it works
 properly.
 Okay will have a code review next week.


 On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> This is great progress! This shows that a clustered deployment of WSO2
> products on Azure is possible with this membership scheme.
>
> About the error, what is says is that a particular resource that the
> first node is expecting to find in the config registry is not found. This
> can be due to a mis-configured registry mounts. Did you mount the config
> and governance registries? If not please do so by referring [1].
>
> Lets schedule a code review early next week for the membership scheme.
>
> [1]. https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database
>
> On Fri, Jun 10, 2016 at 12:42 AM, Osura Rathnayake  > wrote:
>
>> Hi Mentors,
>>
>> I have two application servers (AS) running on azure and I'm testing
>> the azure membership scheme on them. When I run the first AS I could see
>> member added and member joined log messages. And when I run the second 
>> AS,
>> I could see member added log messages and then I get an error saying 
>> carbon
>> initialization failed (screenshot attached as error6). Also when I 
>> stopped
>> the second AS I could see member left log message on the first AS(
>> screenshot attached as Capture1).
>>
>> Afterwards I stopped both of them and started the second AS first and
>> it ran without errors but the other AS( previous case I started this AS
>> first) showed up the same error which I got earlier. I'm getting this 
>> error
>> always from the secondly started AS. Please share with me if you have any
>> idea why I'm getting this.
>>
>> Thanks,
>>
>> On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi all,
>>>
>>> This is the summary of the matters that we discussed during hangout
>>> we had on 6th of June, 2016.
>>>
>>> We had a productive discussion on how to pass the azure specific
>>> parameters to the Azure membership scheme and how we should test the 
>>> Azure
>>> membership scheme
>>>
>>> Current progress : Getting a list of IP addresses of members in the
>>> cluster and updating the hazelcast configuration are done but certain 
>>> azure
>>> specific parameters are hard coded in the program.
>>>
>>> As in kubernetes membership scheme, we agreed upon sending those
>>> parameters as either environment variables or system properties. So the
>>> next immediate goal is to get those parameters that way. As of how to 
>>> test
>>> the azure membership scheme, [1] was shared get a more clear idea on the
>>> subject.
>>>
>>>
>>> [1]
>>> https://docs.wso2.com/display/KA100/Kubernetes+Membership+Scheme+for+WSO2+Carbon
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> On Mon, Jun 6, 2016 at 1:21 PM, Osura Rathnayake >> > wrote:
>>>
 Hi Isuru,

 Thank you 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> As we discussed at the very beginning, next in line is to see how each of
> the following can be setup on Azure using native features:
>
>- Auto healing
>- Autoscaling
>- Dynamic load balancing
>- Centralized logging
>- Monitoring
>- Metering
>
> For auto healing, we can implement it in both VM level and application
> level. In VM level, we can poll for VM statuses and check if a given VM is
> down or not. And then we can up them if they have gone down, using api
> calls. for application level of course we will have to run a shell script
> to determine the status of a given application and will have to up it
> accordingly. I'm looking forward to hear from you regarding this.
>

​No, auto healing and autoscaling should be handled by Azure. We might not
need to write code to handle that.

Thanks​


>
> thanks,
>
> On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Can you please tell me when you would be free to have a hangout to do a
>> code review and discuss next project goals?
>>
>> Thanks,
>>
>> On Saturday, June 11, 2016, Osura Rathnayake  wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you very much.
>>> Yes there was a misconfiguration in registry mounts and now it works
>>> properly.
>>> Okay will have a code review next week.
>>>
>>>
>>> On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 This is great progress! This shows that a clustered deployment of WSO2
 products on Azure is possible with this membership scheme.

 About the error, what is says is that a particular resource that the
 first node is expecting to find in the config registry is not found. This
 can be due to a mis-configured registry mounts. Did you mount the config
 and governance registries? If not please do so by referring [1].

 Lets schedule a code review early next week for the membership scheme.

 [1]. https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database

 On Fri, Jun 10, 2016 at 12:42 AM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> I have two application servers (AS) running on azure and I'm testing
> the azure membership scheme on them. When I run the first AS I could see
> member added and member joined log messages. And when I run the second AS,
> I could see member added log messages and then I get an error saying 
> carbon
> initialization failed (screenshot attached as error6). Also when I stopped
> the second AS I could see member left log message on the first AS(
> screenshot attached as Capture1).
>
> Afterwards I stopped both of them and started the second AS first and
> it ran without errors but the other AS( previous case I started this AS
> first) showed up the same error which I got earlier. I'm getting this 
> error
> always from the secondly started AS. Please share with me if you have any
> idea why I'm getting this.
>
> Thanks,
>
> On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake 
> wrote:
>
>> Hi all,
>>
>> This is the summary of the matters that we discussed during hangout
>> we had on 6th of June, 2016.
>>
>> We had a productive discussion on how to pass the azure specific
>> parameters to the Azure membership scheme and how we should test the 
>> Azure
>> membership scheme
>>
>> Current progress : Getting a list of IP addresses of members in the
>> cluster and updating the hazelcast configuration are done but certain 
>> azure
>> specific parameters are hard coded in the program.
>>
>> As in kubernetes membership scheme, we agreed upon sending those
>> parameters as either environment variables or system properties. So the
>> next immediate goal is to get those parameters that way. As of how to 
>> test
>> the azure membership scheme, [1] was shared get a more clear idea on the
>> subject.
>>
>>
>> [1]
>> https://docs.wso2.com/display/KA100/Kubernetes+Membership+Scheme+for+WSO2+Carbon
>>
>>
>> Thanks,
>>
>>
>>
>> On Mon, Jun 6, 2016 at 1:21 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you very much. Okay will have a hangout today at 3.00 pm.
>>>
>>> thanks,
>>>
>>> On Mon, Jun 6, 2016 at 10:37 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 You need to test the membership scheme following the same method
 that we use for the Kuberntes Membership scheme. Please refer the 
 README
 [1]. The only difference is that you will be deploying in Azure.

 Please note the parameters that are 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

As we discussed at the very beginning, next in line is to see how each of
the following can be setup on Azure using native features:

   - Auto healing
   - Autoscaling
   - Dynamic load balancing
   - Centralized logging
   - Monitoring
   - Metering

For auto healing, we can implement it in both VM level and application
level. In VM level, we can poll for VM statuses and check if a given VM is
down or not. And then we can up them if they have gone down, using api
calls. for application level of course we will have to run a shell script
to determine the status of a given application and will have to up it
accordingly. I'm looking forward to hear from you regarding this.

thanks,

On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Can you please tell me when you would be free to have a hangout to do a
> code review and discuss next project goals?
>
> Thanks,
>
> On Saturday, June 11, 2016, Osura Rathnayake  wrote:
>
>> Hi Isuru,
>>
>> Thank you very much.
>> Yes there was a misconfiguration in registry mounts and now it works
>> properly.
>> Okay will have a code review next week.
>>
>>
>> On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> This is great progress! This shows that a clustered deployment of WSO2
>>> products on Azure is possible with this membership scheme.
>>>
>>> About the error, what is says is that a particular resource that the
>>> first node is expecting to find in the config registry is not found. This
>>> can be due to a mis-configured registry mounts. Did you mount the config
>>> and governance registries? If not please do so by referring [1].
>>>
>>> Lets schedule a code review early next week for the membership scheme.
>>>
>>> [1]. https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database
>>>
>>> On Fri, Jun 10, 2016 at 12:42 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 I have two application servers (AS) running on azure and I'm testing
 the azure membership scheme on them. When I run the first AS I could see
 member added and member joined log messages. And when I run the second AS,
 I could see member added log messages and then I get an error saying carbon
 initialization failed (screenshot attached as error6). Also when I stopped
 the second AS I could see member left log message on the first AS(
 screenshot attached as Capture1).

 Afterwards I stopped both of them and started the second AS first and
 it ran without errors but the other AS( previous case I started this AS
 first) showed up the same error which I got earlier. I'm getting this error
 always from the secondly started AS. Please share with me if you have any
 idea why I'm getting this.

 Thanks,

 On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake 
 wrote:

> Hi all,
>
> This is the summary of the matters that we discussed during hangout we
> had on 6th of June, 2016.
>
> We had a productive discussion on how to pass the azure specific
> parameters to the Azure membership scheme and how we should test the Azure
> membership scheme
>
> Current progress : Getting a list of IP addresses of members in the
> cluster and updating the hazelcast configuration are done but certain 
> azure
> specific parameters are hard coded in the program.
>
> As in kubernetes membership scheme, we agreed upon sending those
> parameters as either environment variables or system properties. So the
> next immediate goal is to get those parameters that way. As of how to test
> the azure membership scheme, [1] was shared get a more clear idea on the
> subject.
>
>
> [1]
> https://docs.wso2.com/display/KA100/Kubernetes+Membership+Scheme+for+WSO2+Carbon
>
>
> Thanks,
>
>
>
> On Mon, Jun 6, 2016 at 1:21 PM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you very much. Okay will have a hangout today at 3.00 pm.
>>
>> thanks,
>>
>> On Mon, Jun 6, 2016 at 10:37 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> You need to test the membership scheme following the same method
>>> that we use for the Kuberntes Membership scheme. Please refer the README
>>> [1]. The only difference is that you will be deploying in Azure.
>>>
>>> Please note the parameters that are added to the axis2.xml:
>>>
>>> membershipSchemeClassName, membershipScheme, KUBERNETES_MASTER,
>>> KUBERNETES_SERVICES, etc.
>>>
>>> membershipSchemeClassName is the fully qualified classname for the
>>> relevant Membership Scheme class that you have written. Carbon will try 
>>> to
>>> load that class using the class name.
>>> membershipScheme should 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Thank you very much.
Yes there was a misconfiguration in registry mounts and now it works
properly.
Okay will have a code review next week.


On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> This is great progress! This shows that a clustered deployment of WSO2
> products on Azure is possible with this membership scheme.
>
> About the error, what is says is that a particular resource that the first
> node is expecting to find in the config registry is not found. This can be
> due to a mis-configured registry mounts. Did you mount the config and
> governance registries? If not please do so by referring [1].
>
> Lets schedule a code review early next week for the membership scheme.
>
> [1]. https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database
>
> On Fri, Jun 10, 2016 at 12:42 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I have two application servers (AS) running on azure and I'm testing the
>> azure membership scheme on them. When I run the first AS I could see member
>> added and member joined log messages. And when I run the second AS, I could
>> see member added log messages and then I get an error saying carbon
>> initialization failed (screenshot attached as error6). Also when I stopped
>> the second AS I could see member left log message on the first AS(
>> screenshot attached as Capture1).
>>
>> Afterwards I stopped both of them and started the second AS first and it
>> ran without errors but the other AS( previous case I started this AS first)
>> showed up the same error which I got earlier. I'm getting this error always
>> from the secondly started AS. Please share with me if you have any idea why
>> I'm getting this.
>>
>> Thanks,
>>
>> On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi all,
>>>
>>> This is the summary of the matters that we discussed during hangout we
>>> had on 6th of June, 2016.
>>>
>>> We had a productive discussion on how to pass the azure specific
>>> parameters to the Azure membership scheme and how we should test the Azure
>>> membership scheme
>>>
>>> Current progress : Getting a list of IP addresses of members in the
>>> cluster and updating the hazelcast configuration are done but certain azure
>>> specific parameters are hard coded in the program.
>>>
>>> As in kubernetes membership scheme, we agreed upon sending those
>>> parameters as either environment variables or system properties. So the
>>> next immediate goal is to get those parameters that way. As of how to test
>>> the azure membership scheme, [1] was shared get a more clear idea on the
>>> subject.
>>>
>>>
>>> [1]
>>> https://docs.wso2.com/display/KA100/Kubernetes+Membership+Scheme+for+WSO2+Carbon
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> On Mon, Jun 6, 2016 at 1:21 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Thank you very much. Okay will have a hangout today at 3.00 pm.

 thanks,

 On Mon, Jun 6, 2016 at 10:37 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> You need to test the membership scheme following the same method that
> we use for the Kuberntes Membership scheme. Please refer the README [1].
> The only difference is that you will be deploying in Azure.
>
> Please note the parameters that are added to the axis2.xml:
>
> membershipSchemeClassName, membershipScheme, KUBERNETES_MASTER,
> KUBERNETES_SERVICES, etc.
>
> membershipSchemeClassName is the fully qualified classname for the
> relevant Membership Scheme class that you have written. Carbon will try to
> load that class using the class name.
> membershipScheme should be 'azure' or any other suitable name
> KUBERNETES_MASTER and KUBERNETES_SERVICES are the API endpoint and the
> Kubernetes Service Name(s) to be considered in the cluster. You need to
> change these parameters according to your case, reflecting the Azure
> deployment (using Azure API endpoint and the Network Security Group as you
> mentioned in a previous reply, etc.).
>
> Lets have a hangout today at 3.00 PM if you are free at that time to
> discuss more.
>
> [1].
> https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme
>
> On Fri, Jun 3, 2016 at 11:18 PM, Osura Rathnayake 
> wrote:
>
>> Hi mentors,
>>
>> please find the updated membership scheme here [1].
>> Can you please tell me how to test the membership scheme? Also how
>> can I get the parameters that are passed into the constructor of the
>> membership class? Also where is the membership class invoked.
>>
>> [1]https://github.com/osuran/azure-membership-scheme
>>
>> Thanks,
>>
>>
>>
>>
>> On Thu, Jun 2, 2016 at 10:38 AM, Imesh Gunaratne 
>> wrote:
>>
>>>

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

This is great progress! This shows that a clustered deployment of WSO2
products on Azure is possible with this membership scheme.

About the error, what is says is that a particular resource that the first
node is expecting to find in the config registry is not found. This can be
due to a mis-configured registry mounts. Did you mount the config and
governance registries? If not please do so by referring [1].

Lets schedule a code review early next week for the membership scheme.

[1]. https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database

On Fri, Jun 10, 2016 at 12:42 AM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I have two application servers (AS) running on azure and I'm testing the
> azure membership scheme on them. When I run the first AS I could see member
> added and member joined log messages. And when I run the second AS, I could
> see member added log messages and then I get an error saying carbon
> initialization failed (screenshot attached as error6). Also when I stopped
> the second AS I could see member left log message on the first AS(
> screenshot attached as Capture1).
>
> Afterwards I stopped both of them and started the second AS first and it
> ran without errors but the other AS( previous case I started this AS first)
> showed up the same error which I got earlier. I'm getting this error always
> from the secondly started AS. Please share with me if you have any idea why
> I'm getting this.
>
> Thanks,
>
> On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake 
> wrote:
>
>> Hi all,
>>
>> This is the summary of the matters that we discussed during hangout we
>> had on 6th of June, 2016.
>>
>> We had a productive discussion on how to pass the azure specific
>> parameters to the Azure membership scheme and how we should test the Azure
>> membership scheme
>>
>> Current progress : Getting a list of IP addresses of members in the
>> cluster and updating the hazelcast configuration are done but certain azure
>> specific parameters are hard coded in the program.
>>
>> As in kubernetes membership scheme, we agreed upon sending those
>> parameters as either environment variables or system properties. So the
>> next immediate goal is to get those parameters that way. As of how to test
>> the azure membership scheme, [1] was shared get a more clear idea on the
>> subject.
>>
>>
>> [1]
>> https://docs.wso2.com/display/KA100/Kubernetes+Membership+Scheme+for+WSO2+Carbon
>>
>>
>> Thanks,
>>
>>
>>
>> On Mon, Jun 6, 2016 at 1:21 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you very much. Okay will have a hangout today at 3.00 pm.
>>>
>>> thanks,
>>>
>>> On Mon, Jun 6, 2016 at 10:37 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 You need to test the membership scheme following the same method that
 we use for the Kuberntes Membership scheme. Please refer the README [1].
 The only difference is that you will be deploying in Azure.

 Please note the parameters that are added to the axis2.xml:

 membershipSchemeClassName, membershipScheme, KUBERNETES_MASTER,
 KUBERNETES_SERVICES, etc.

 membershipSchemeClassName is the fully qualified classname for the
 relevant Membership Scheme class that you have written. Carbon will try to
 load that class using the class name.
 membershipScheme should be 'azure' or any other suitable name
 KUBERNETES_MASTER and KUBERNETES_SERVICES are the API endpoint and the
 Kubernetes Service Name(s) to be considered in the cluster. You need to
 change these parameters according to your case, reflecting the Azure
 deployment (using Azure API endpoint and the Network Security Group as you
 mentioned in a previous reply, etc.).

 Lets have a hangout today at 3.00 PM if you are free at that time to
 discuss more.

 [1].
 https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme

 On Fri, Jun 3, 2016 at 11:18 PM, Osura Rathnayake 
 wrote:

> Hi mentors,
>
> please find the updated membership scheme here [1].
> Can you please tell me how to test the membership scheme? Also how can
> I get the parameters that are passed into the constructor of the 
> membership
> class? Also where is the membership class invoked.
>
> [1]https://github.com/osuran/azure-membership-scheme
>
> Thanks,
>
>
>
>
> On Thu, Jun 2, 2016 at 10:38 AM, Imesh Gunaratne 
> wrote:
>
>>
>>
>> On Thu, Jun 2, 2016 at 10:33 AM, Osura Rathnayake > > wrote:
>>
>>> Hi mentors,
>>>
>>> When developing the membership scheme, from where can I get
>>> the HazelcastMembershipScheme interface? I Googled but couldn't find an
>>> appropriate jar file or anything. the one that netbeans suggests also

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Akila,

Thank you it worked.


On Thu, Jun 9, 2016 at 6:51 PM, Akila Ravihansa Perera 
wrote:

> Hi Osura,
>
> Please make sure that you have kernel patch0012 applied in
> repository/components/patches for Carbon 4.2.0 based products. You can
> refer to Carbon release matrix [1] to get a list of products that are based
> on Carbon 4.2.0.
>
> For Carbon 4.4.1 based products you need kernel patch0005.
>
> [1] http://wso2.com/products/carbon/release-matrix/
>
> Thanks.
>
>
> On Thursday, 9 June 2016, Osura Rathnayake  wrote:
>
>> Hi Mentors,
>>
>> When i was testing the azure membership scheme, the error in the attached
>> screenshot occurred. I added the jar file of azure membership scheme in 
>> "repository/components/lib"
>> and updated the axis2.xml with following parameters. Can you please point
>> out any possible mistakes I have done?
>>
>> > class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
>> enable="true">
>>   > name="membershipSchemeClassName">com.osura.membershipscheme.AzureMembershipScheme
>>   Azure
>>
>>   > name="credential">uduq558Ble9TlucvGECEFDvRqGv6q0WsFvFWYWOTaRs=
>>   > name="tenantId">7a94c74f-5ab1-46c2-a98c-df7df7c5f41e
>>   > name="clientId">ce86678c-8520-431c-9c9f-0bdf733e4133
>>   > name="subscriptionId">0820043e-501c-43ff-ab1d-a96258a301de
>>
>> 
>>
>> thanks
>>
>> On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi all,
>>>
>>> This is the summary of the matters that we discussed during hangout we
>>> had on 6th of June, 2016.
>>>
>>> We had a productive discussion on how to pass the azure specific
>>> parameters to the Azure membership scheme and how we should test the Azure
>>> membership scheme
>>>
>>> Current progress : Getting a list of IP addresses of members in the
>>> cluster and updating the hazelcast configuration are done but certain azure
>>> specific parameters are hard coded in the program.
>>>
>>> As in kubernetes membership scheme, we agreed upon sending those
>>> parameters as either environment variables or system properties. So the
>>> next immediate goal is to get those parameters that way. As of how to test
>>> the azure membership scheme, [1] was shared get a more clear idea on the
>>> subject.
>>>
>>>
>>> [1]
>>> https://docs.wso2.com/display/KA100/Kubernetes+Membership+Scheme+for+WSO2+Carbon
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> On Mon, Jun 6, 2016 at 1:21 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Thank you very much. Okay will have a hangout today at 3.00 pm.

 thanks,

 On Mon, Jun 6, 2016 at 10:37 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> You need to test the membership scheme following the same method that
> we use for the Kuberntes Membership scheme. Please refer the README [1].
> The only difference is that you will be deploying in Azure.
>
> Please note the parameters that are added to the axis2.xml:
>
> membershipSchemeClassName, membershipScheme, KUBERNETES_MASTER,
> KUBERNETES_SERVICES, etc.
>
> membershipSchemeClassName is the fully qualified classname for the
> relevant Membership Scheme class that you have written. Carbon will try to
> load that class using the class name.
> membershipScheme should be 'azure' or any other suitable name
> KUBERNETES_MASTER and KUBERNETES_SERVICES are the API endpoint and the
> Kubernetes Service Name(s) to be considered in the cluster. You need to
> change these parameters according to your case, reflecting the Azure
> deployment (using Azure API endpoint and the Network Security Group as you
> mentioned in a previous reply, etc.).
>
> Lets have a hangout today at 3.00 PM if you are free at that time to
> discuss more.
>
> [1].
> https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme
>
> On Fri, Jun 3, 2016 at 11:18 PM, Osura Rathnayake 
> wrote:
>
>> Hi mentors,
>>
>> please find the updated membership scheme here [1].
>> Can you please tell me how to test the membership scheme? Also how
>> can I get the parameters that are passed into the constructor of the
>> membership class? Also where is the membership class invoked.
>>
>> [1]https://github.com/osuran/azure-membership-scheme
>>
>> Thanks,
>>
>>
>>
>>
>> On Thu, Jun 2, 2016 at 10:38 AM, Imesh Gunaratne 
>> wrote:
>>
>>>
>>>
>>> On Thu, Jun 2, 2016 at 10:33 AM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi mentors,

 When developing the membership scheme, from where can I get
 the HazelcastMembershipScheme interface? I Googled but couldn't find an
 appropriate jar file or anything. the one that netbeans suggests also
 cannot be 

Re: [Dev] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi Osura,

Please make sure that you have kernel patch0012 applied in
repository/components/patches for Carbon 4.2.0 based products. You can
refer to Carbon release matrix [1] to get a list of products that are based
on Carbon 4.2.0.

For Carbon 4.4.1 based products you need kernel patch0005.

[1] http://wso2.com/products/carbon/release-matrix/

Thanks.

On Thursday, 9 June 2016, Osura Rathnayake  wrote:

> Hi Mentors,
>
> When i was testing the azure membership scheme, the error in the attached
> screenshot occurred. I added the jar file of azure membership scheme in 
> "repository/components/lib"
> and updated the axis2.xml with following parameters. Can you please point
> out any possible mistakes I have done?
>
>  class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
> enable="true">
>name="membershipSchemeClassName">com.osura.membershipscheme.AzureMembershipScheme
>   Azure
>
>name="credential">uduq558Ble9TlucvGECEFDvRqGv6q0WsFvFWYWOTaRs=
>name="tenantId">7a94c74f-5ab1-46c2-a98c-df7df7c5f41e
>name="clientId">ce86678c-8520-431c-9c9f-0bdf733e4133
>name="subscriptionId">0820043e-501c-43ff-ab1d-a96258a301de
>
> 
>
> thanks
>
> On Mon, Jun 6, 2016 at 4:16 PM, Osura Rathnayake  > wrote:
>
>> Hi all,
>>
>> This is the summary of the matters that we discussed during hangout we
>> had on 6th of June, 2016.
>>
>> We had a productive discussion on how to pass the azure specific
>> parameters to the Azure membership scheme and how we should test the Azure
>> membership scheme
>>
>> Current progress : Getting a list of IP addresses of members in the
>> cluster and updating the hazelcast configuration are done but certain azure
>> specific parameters are hard coded in the program.
>>
>> As in kubernetes membership scheme, we agreed upon sending those
>> parameters as either environment variables or system properties. So the
>> next immediate goal is to get those parameters that way. As of how to test
>> the azure membership scheme, [1] was shared get a more clear idea on the
>> subject.
>>
>>
>> [1]
>> https://docs.wso2.com/display/KA100/Kubernetes+Membership+Scheme+for+WSO2+Carbon
>>
>>
>> Thanks,
>>
>>
>>
>> On Mon, Jun 6, 2016 at 1:21 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you very much. Okay will have a hangout today at 3.00 pm.
>>>
>>> thanks,
>>>
>>> On Mon, Jun 6, 2016 at 10:37 AM, Isuru Haththotuwa >> > wrote:
>>>
 Hi Osura,

 You need to test the membership scheme following the same method that
 we use for the Kuberntes Membership scheme. Please refer the README [1].
 The only difference is that you will be deploying in Azure.

 Please note the parameters that are added to the axis2.xml:

 membershipSchemeClassName, membershipScheme, KUBERNETES_MASTER,
 KUBERNETES_SERVICES, etc.

 membershipSchemeClassName is the fully qualified classname for the
 relevant Membership Scheme class that you have written. Carbon will try to
 load that class using the class name.
 membershipScheme should be 'azure' or any other suitable name
 KUBERNETES_MASTER and KUBERNETES_SERVICES are the API endpoint and the
 Kubernetes Service Name(s) to be considered in the cluster. You need to
 change these parameters according to your case, reflecting the Azure
 deployment (using Azure API endpoint and the Network Security Group as you
 mentioned in a previous reply, etc.).

 Lets have a hangout today at 3.00 PM if you are free at that time to
 discuss more.

 [1].
 https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme

 On Fri, Jun 3, 2016 at 11:18 PM, Osura Rathnayake > wrote:

> Hi mentors,
>
> please find the updated membership scheme here [1].
> Can you please tell me how to test the membership scheme? Also how can
> I get the parameters that are passed into the constructor of the 
> membership
> class? Also where is the membership class invoked.
>
> [1]https://github.com/osuran/azure-membership-scheme
>
> Thanks,
>
>
>
>
> On Thu, Jun 2, 2016 at 10:38 AM, Imesh Gunaratne  > wrote:
>
>>
>>
>> On Thu, Jun 2, 2016 at 10:33 AM, Osura Rathnayake > > wrote:
>>
>>> Hi mentors,
>>>
>>> When developing the membership scheme, from where can I get
>>> the HazelcastMembershipScheme interface? I Googled but couldn't find an
>>> appropriate jar file or anything. the one that 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi all,

This is the summary of the matters that we discussed during hangout we had
on 6th of June, 2016.

We had a productive discussion on how to pass the azure specific parameters
to the Azure membership scheme and how we should test the Azure membership
scheme

Current progress : Getting a list of IP addresses of members in the cluster
and updating the hazelcast configuration are done but certain azure
specific parameters are hard coded in the program.

As in kubernetes membership scheme, we agreed upon sending those parameters
as either environment variables or system properties. So the next immediate
goal is to get those parameters that way. As of how to test the azure
membership scheme, [1] was shared get a more clear idea on the subject.


[1]
https://docs.wso2.com/display/KA100/Kubernetes+Membership+Scheme+for+WSO2+Carbon


Thanks,



On Mon, Jun 6, 2016 at 1:21 PM, Osura Rathnayake  wrote:

> Hi Isuru,
>
> Thank you very much. Okay will have a hangout today at 3.00 pm.
>
> thanks,
>
> On Mon, Jun 6, 2016 at 10:37 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> You need to test the membership scheme following the same method that we
>> use for the Kuberntes Membership scheme. Please refer the README [1]. The
>> only difference is that you will be deploying in Azure.
>>
>> Please note the parameters that are added to the axis2.xml:
>>
>> membershipSchemeClassName, membershipScheme, KUBERNETES_MASTER,
>> KUBERNETES_SERVICES, etc.
>>
>> membershipSchemeClassName is the fully qualified classname for the
>> relevant Membership Scheme class that you have written. Carbon will try to
>> load that class using the class name.
>> membershipScheme should be 'azure' or any other suitable name
>> KUBERNETES_MASTER and KUBERNETES_SERVICES are the API endpoint and the
>> Kubernetes Service Name(s) to be considered in the cluster. You need to
>> change these parameters according to your case, reflecting the Azure
>> deployment (using Azure API endpoint and the Network Security Group as you
>> mentioned in a previous reply, etc.).
>>
>> Lets have a hangout today at 3.00 PM if you are free at that time to
>> discuss more.
>>
>> [1].
>> https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme
>>
>> On Fri, Jun 3, 2016 at 11:18 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi mentors,
>>>
>>> please find the updated membership scheme here [1].
>>> Can you please tell me how to test the membership scheme? Also how can I
>>> get the parameters that are passed into the constructor of the membership
>>> class? Also where is the membership class invoked.
>>>
>>> [1]https://github.com/osuran/azure-membership-scheme
>>>
>>> Thanks,
>>>
>>>
>>>
>>>
>>> On Thu, Jun 2, 2016 at 10:38 AM, Imesh Gunaratne  wrote:
>>>


 On Thu, Jun 2, 2016 at 10:33 AM, Osura Rathnayake 
 wrote:

> Hi mentors,
>
> When developing the membership scheme, from where can I get
> the HazelcastMembershipScheme interface? I Googled but couldn't find an
> appropriate jar file or anything. the one that netbeans suggests also
> cannot be downloaded.
>


 https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastMembershipScheme.java


 ​Will implement this for Carbon 4.4.x.

 Thanks​


> Thanks,
>
> On Mon, May 30, 2016 at 1:49 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you
>> I have updated my Git repository with this sample code, please find
>> it here [1].
>>
>> [1] https://github.com/osuran/azure-membership-scheme
>>
>> Thanks
>>
>> On Sun, May 29, 2016 at 8:41 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Sun, May 29, 2016 at 12:32 AM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Isuru,

 Please find the attached project zip. From line 108 to 148 I hard
 coded because I was getting errors with StringTokenizer and I didn't 
 want
 to focus much on that.
 Okay I'm right on writing the actual membership scheme.

>>> Thanks. Will have a look.
>>>
>>> It would be better if you can commit this to a github repository. By
>>> doing that, your sample is available for anyone to use/refer. Make sure 
>>> to
>>> remove any sensitive information (passwords, etc.) before doing so.
>>>

 thanks

 On Sat, May 28, 2016 at 10:19 PM, Isuru Haththotuwa <
 isu...@wso2.com> wrote:

> Hi Osura,
>
> These are great findings!
>
> Can you please share the sample code that you wrote?
>
> The next step would be to start writing 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Thank you very much. Okay will have a hangout today at 3.00 pm.

thanks,

On Mon, Jun 6, 2016 at 10:37 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> You need to test the membership scheme following the same method that we
> use for the Kuberntes Membership scheme. Please refer the README [1]. The
> only difference is that you will be deploying in Azure.
>
> Please note the parameters that are added to the axis2.xml:
>
> membershipSchemeClassName, membershipScheme, KUBERNETES_MASTER,
> KUBERNETES_SERVICES, etc.
>
> membershipSchemeClassName is the fully qualified classname for the
> relevant Membership Scheme class that you have written. Carbon will try to
> load that class using the class name.
> membershipScheme should be 'azure' or any other suitable name
> KUBERNETES_MASTER and KUBERNETES_SERVICES are the API endpoint and the
> Kubernetes Service Name(s) to be considered in the cluster. You need to
> change these parameters according to your case, reflecting the Azure
> deployment (using Azure API endpoint and the Network Security Group as you
> mentioned in a previous reply, etc.).
>
> Lets have a hangout today at 3.00 PM if you are free at that time to
> discuss more.
>
> [1].
> https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme
>
> On Fri, Jun 3, 2016 at 11:18 PM, Osura Rathnayake 
> wrote:
>
>> Hi mentors,
>>
>> please find the updated membership scheme here [1].
>> Can you please tell me how to test the membership scheme? Also how can I
>> get the parameters that are passed into the constructor of the membership
>> class? Also where is the membership class invoked.
>>
>> [1]https://github.com/osuran/azure-membership-scheme
>>
>> Thanks,
>>
>>
>>
>>
>> On Thu, Jun 2, 2016 at 10:38 AM, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Thu, Jun 2, 2016 at 10:33 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi mentors,

 When developing the membership scheme, from where can I get
 the HazelcastMembershipScheme interface? I Googled but couldn't find an
 appropriate jar file or anything. the one that netbeans suggests also
 cannot be downloaded.

>>>
>>>
>>> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastMembershipScheme.java
>>>
>>>
>>> ​Will implement this for Carbon 4.4.x.
>>>
>>> Thanks​
>>>
>>>
 Thanks,

 On Mon, May 30, 2016 at 1:49 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> Thank you
> I have updated my Git repository with this sample code, please find it
> here [1].
>
> [1] https://github.com/osuran/azure-membership-scheme
>
> Thanks
>
> On Sun, May 29, 2016 at 8:41 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Sun, May 29, 2016 at 12:32 AM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Hi Isuru,
>>>
>>> Please find the attached project zip. From line 108 to 148 I hard
>>> coded because I was getting errors with StringTokenizer and I didn't 
>>> want
>>> to focus much on that.
>>> Okay I'm right on writing the actual membership scheme.
>>>
>> Thanks. Will have a look.
>>
>> It would be better if you can commit this to a github repository. By
>> doing that, your sample is available for anyone to use/refer. Make sure 
>> to
>> remove any sensitive information (passwords, etc.) before doing so.
>>
>>>
>>> thanks
>>>
>>> On Sat, May 28, 2016 at 10:19 PM, Isuru Haththotuwa >> > wrote:
>>>
 Hi Osura,

 These are great findings!

 Can you please share the sample code that you wrote?

 The next step would be to start writing the actual membership
 scheme. Please refer the Kubernetes Membership scheme as a reference.


 On Sat, May 28, 2016 at 9:06 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi All,
>
>
>
> This is the summary of everything that I have done so far.
>
>
>
> Pre requisite: VMs which has WSO2 Application Server running
> should have been added to a particular network security group (NSG). 
> In my
> case it’s ASNSG
>
>
>
> First the java app should be authenticated. Then it query for the
> information on ASNSG. Response of that API call includes names of all 
> the
> network interfaces that are existed in ASNSG. Then each and every 
> network
> interface is queried using their names to get private IP addresses of 
> each
> of them. As the final outcome we get a list of IP addresses of VMs 
> which
> has 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

You need to test the membership scheme following the same method that we
use for the Kuberntes Membership scheme. Please refer the README [1]. The
only difference is that you will be deploying in Azure.

Please note the parameters that are added to the axis2.xml:

membershipSchemeClassName, membershipScheme, KUBERNETES_MASTER,
KUBERNETES_SERVICES, etc.

membershipSchemeClassName is the fully qualified classname for the relevant
Membership Scheme class that you have written. Carbon will try to load that
class using the class name.
membershipScheme should be 'azure' or any other suitable name
KUBERNETES_MASTER and KUBERNETES_SERVICES are the API endpoint and the
Kubernetes Service Name(s) to be considered in the cluster. You need to
change these parameters according to your case, reflecting the Azure
deployment (using Azure API endpoint and the Network Security Group as you
mentioned in a previous reply, etc.).

Lets have a hangout today at 3.00 PM if you are free at that time to
discuss more.

[1].
https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme

On Fri, Jun 3, 2016 at 11:18 PM, Osura Rathnayake 
wrote:

> Hi mentors,
>
> please find the updated membership scheme here [1].
> Can you please tell me how to test the membership scheme? Also how can I
> get the parameters that are passed into the constructor of the membership
> class? Also where is the membership class invoked.
>
> [1]https://github.com/osuran/azure-membership-scheme
>
> Thanks,
>
>
>
>
> On Thu, Jun 2, 2016 at 10:38 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Thu, Jun 2, 2016 at 10:33 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi mentors,
>>>
>>> When developing the membership scheme, from where can I get
>>> the HazelcastMembershipScheme interface? I Googled but couldn't find an
>>> appropriate jar file or anything. the one that netbeans suggests also
>>> cannot be downloaded.
>>>
>>
>>
>> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastMembershipScheme.java
>>
>>
>> ​Will implement this for Carbon 4.4.x.
>>
>> Thanks​
>>
>>
>>> Thanks,
>>>
>>> On Mon, May 30, 2016 at 1:49 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Thank you
 I have updated my Git repository with this sample code, please find it
 here [1].

 [1] https://github.com/osuran/azure-membership-scheme

 Thanks

 On Sun, May 29, 2016 at 8:41 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> On Sun, May 29, 2016 at 12:32 AM, Osura Rathnayake  > wrote:
>
>> Hi Isuru,
>>
>> Please find the attached project zip. From line 108 to 148 I hard
>> coded because I was getting errors with StringTokenizer and I didn't want
>> to focus much on that.
>> Okay I'm right on writing the actual membership scheme.
>>
> Thanks. Will have a look.
>
> It would be better if you can commit this to a github repository. By
> doing that, your sample is available for anyone to use/refer. Make sure to
> remove any sensitive information (passwords, etc.) before doing so.
>
>>
>> thanks
>>
>> On Sat, May 28, 2016 at 10:19 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> These are great findings!
>>>
>>> Can you please share the sample code that you wrote?
>>>
>>> The next step would be to start writing the actual membership
>>> scheme. Please refer the Kubernetes Membership scheme as a reference.
>>>
>>>
>>> On Sat, May 28, 2016 at 9:06 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi All,



 This is the summary of everything that I have done so far.



 Pre requisite: VMs which has WSO2 Application Server running should
 have been added to a particular network security group (NSG). In my 
 case
 it’s ASNSG



 First the java app should be authenticated. Then it query for the
 information on ASNSG. Response of that API call includes names of all 
 the
 network interfaces that are existed in ASNSG. Then each and every 
 network
 interface is queried using their names to get private IP addresses of 
 each
 of them. As the final outcome we get a list of IP addresses of VMs 
 which
 has WSO2 Application Server running.



 *Authentication*

 In order to work with Azure Resource Manager (ARM) REST API, first
 of all our app has to be authenticated. ARM provides two methods for 
 this
 purpose,



 1) Authenticate using service 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi mentors,

please find the updated membership scheme here [1].
Can you please tell me how to test the membership scheme? Also how can I
get the parameters that are passed into the constructor of the membership
class? Also where is the membership class invoked.

[1]https://github.com/osuran/azure-membership-scheme

Thanks,




On Thu, Jun 2, 2016 at 10:38 AM, Imesh Gunaratne  wrote:

>
>
> On Thu, Jun 2, 2016 at 10:33 AM, Osura Rathnayake 
> wrote:
>
>> Hi mentors,
>>
>> When developing the membership scheme, from where can I get
>> the HazelcastMembershipScheme interface? I Googled but couldn't find an
>> appropriate jar file or anything. the one that netbeans suggests also
>> cannot be downloaded.
>>
>
>
> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastMembershipScheme.java
>
>
> ​Will implement this for Carbon 4.4.x.
>
> Thanks​
>
>
>> Thanks,
>>
>> On Mon, May 30, 2016 at 1:49 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you
>>> I have updated my Git repository with this sample code, please find it
>>> here [1].
>>>
>>> [1] https://github.com/osuran/azure-membership-scheme
>>>
>>> Thanks
>>>
>>> On Sun, May 29, 2016 at 8:41 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 On Sun, May 29, 2016 at 12:32 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> Please find the attached project zip. From line 108 to 148 I hard
> coded because I was getting errors with StringTokenizer and I didn't want
> to focus much on that.
> Okay I'm right on writing the actual membership scheme.
>
 Thanks. Will have a look.

 It would be better if you can commit this to a github repository. By
 doing that, your sample is available for anyone to use/refer. Make sure to
 remove any sensitive information (passwords, etc.) before doing so.

>
> thanks
>
> On Sat, May 28, 2016 at 10:19 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> These are great findings!
>>
>> Can you please share the sample code that you wrote?
>>
>> The next step would be to start writing the actual membership scheme.
>> Please refer the Kubernetes Membership scheme as a reference.
>>
>>
>> On Sat, May 28, 2016 at 9:06 PM, Osura Rathnayake > > wrote:
>>
>>> Hi All,
>>>
>>>
>>>
>>> This is the summary of everything that I have done so far.
>>>
>>>
>>>
>>> Pre requisite: VMs which has WSO2 Application Server running should
>>> have been added to a particular network security group (NSG). In my case
>>> it’s ASNSG
>>>
>>>
>>>
>>> First the java app should be authenticated. Then it query for the
>>> information on ASNSG. Response of that API call includes names of all 
>>> the
>>> network interfaces that are existed in ASNSG. Then each and every 
>>> network
>>> interface is queried using their names to get private IP addresses of 
>>> each
>>> of them. As the final outcome we get a list of IP addresses of VMs which
>>> has WSO2 Application Server running.
>>>
>>>
>>>
>>> *Authentication*
>>>
>>> In order to work with Azure Resource Manager (ARM) REST API, first
>>> of all our app has to be authenticated. ARM provides two methods for 
>>> this
>>> purpose,
>>>
>>>
>>>
>>> 1) Authenticate using service principal
>>>
>>> 2) Authenticate using organizational account.
>>>
>>>
>>>
>>> I have used the first method that is authenticating using a service
>>> principal.  A Service Principal is an instance of an application that is
>>> within your Active Directory that is allowed access to one or more
>>> resources or an entire resource group. How to set up a service 
>>> principal is
>>> well described here [1]. Once you successfully set up a service 
>>> principal,
>>> you will have the following information in hand.
>>>
>>>
>>>
>>> 1)  Client ID
>>>
>>> 2)  Client secret
>>>
>>> 3)  Tenant ID
>>>
>>> Above parameters and Azure subscription ID are used in the java app
>>> for authentication purpose. I have used Active Directory Authentication
>>> Library (ADAL) [2] for authentication. Once the authentication is
>>> successful, an authentication token will be issued and it will be used 
>>> in
>>> the rest of the program as to make calls to API.
>>>
>>>
>>>
>>> *Getting information on ASNSG*
>>>
>>> For this purpose, [3] API reference is used. As the response we get
>>> a JSON string which includes names of NICs which are available in ASNSG.
>>>
>>>
>>>
>>> *Getting private IP 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Thu, Jun 2, 2016 at 10:33 AM, Osura Rathnayake 
wrote:

> Hi mentors,
>
> When developing the membership scheme, from where can I get
> the HazelcastMembershipScheme interface? I Googled but couldn't find an
> appropriate jar file or anything. the one that netbeans suggests also
> cannot be downloaded.
>

https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/clustering/hazelcast/HazelcastMembershipScheme.java


​Will implement this for Carbon 4.4.x.

Thanks​


> Thanks,
>
> On Mon, May 30, 2016 at 1:49 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you
>> I have updated my Git repository with this sample code, please find it
>> here [1].
>>
>> [1] https://github.com/osuran/azure-membership-scheme
>>
>> Thanks
>>
>> On Sun, May 29, 2016 at 8:41 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Sun, May 29, 2016 at 12:32 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Please find the attached project zip. From line 108 to 148 I hard coded
 because I was getting errors with StringTokenizer and I didn't want to
 focus much on that.
 Okay I'm right on writing the actual membership scheme.

>>> Thanks. Will have a look.
>>>
>>> It would be better if you can commit this to a github repository. By
>>> doing that, your sample is available for anyone to use/refer. Make sure to
>>> remove any sensitive information (passwords, etc.) before doing so.
>>>

 thanks

 On Sat, May 28, 2016 at 10:19 PM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> These are great findings!
>
> Can you please share the sample code that you wrote?
>
> The next step would be to start writing the actual membership scheme.
> Please refer the Kubernetes Membership scheme as a reference.
>
>
> On Sat, May 28, 2016 at 9:06 PM, Osura Rathnayake 
> wrote:
>
>> Hi All,
>>
>>
>>
>> This is the summary of everything that I have done so far.
>>
>>
>>
>> Pre requisite: VMs which has WSO2 Application Server running should
>> have been added to a particular network security group (NSG). In my case
>> it’s ASNSG
>>
>>
>>
>> First the java app should be authenticated. Then it query for the
>> information on ASNSG. Response of that API call includes names of all the
>> network interfaces that are existed in ASNSG. Then each and every network
>> interface is queried using their names to get private IP addresses of 
>> each
>> of them. As the final outcome we get a list of IP addresses of VMs which
>> has WSO2 Application Server running.
>>
>>
>>
>> *Authentication*
>>
>> In order to work with Azure Resource Manager (ARM) REST API, first of
>> all our app has to be authenticated. ARM provides two methods for this
>> purpose,
>>
>>
>>
>> 1) Authenticate using service principal
>>
>> 2) Authenticate using organizational account.
>>
>>
>>
>> I have used the first method that is authenticating using a service
>> principal.  A Service Principal is an instance of an application that is
>> within your Active Directory that is allowed access to one or more
>> resources or an entire resource group. How to set up a service principal 
>> is
>> well described here [1]. Once you successfully set up a service 
>> principal,
>> you will have the following information in hand.
>>
>>
>>
>> 1)  Client ID
>>
>> 2)  Client secret
>>
>> 3)  Tenant ID
>>
>> Above parameters and Azure subscription ID are used in the java app
>> for authentication purpose. I have used Active Directory Authentication
>> Library (ADAL) [2] for authentication. Once the authentication is
>> successful, an authentication token will be issued and it will be used in
>> the rest of the program as to make calls to API.
>>
>>
>>
>> *Getting information on ASNSG*
>>
>> For this purpose, [3] API reference is used. As the response we get a
>> JSON string which includes names of NICs which are available in ASNSG.
>>
>>
>>
>> *Getting private IP address of each NIC*
>>
>> With the NIC names we received from previous API call, we can use
>> this [4] API reference to get the private IP address of each NIC. And 
>> then
>> with that information we can list out the IP addresses of all the VMs 
>> which
>> has WSO2 Application Server running.
>>
>>
>>
>> [1]
>> https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/
>>
>> [2] https://github.com/AzureAD/azure-activedirectory-library-for-java
>>
>> [3] 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi mentors,

When developing the membership scheme, from where can I get
the HazelcastMembershipScheme interface? I Googled but couldn't find an
appropriate jar file or anything. the one that netbeans suggests also
cannot be downloaded.

Thanks,

On Mon, May 30, 2016 at 1:49 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Thank you
> I have updated my Git repository with this sample code, please find it
> here [1].
>
> [1] https://github.com/osuran/azure-membership-scheme
>
> Thanks
>
> On Sun, May 29, 2016 at 8:41 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Sun, May 29, 2016 at 12:32 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Please find the attached project zip. From line 108 to 148 I hard coded
>>> because I was getting errors with StringTokenizer and I didn't want to
>>> focus much on that.
>>> Okay I'm right on writing the actual membership scheme.
>>>
>> Thanks. Will have a look.
>>
>> It would be better if you can commit this to a github repository. By
>> doing that, your sample is available for anyone to use/refer. Make sure to
>> remove any sensitive information (passwords, etc.) before doing so.
>>
>>>
>>> thanks
>>>
>>> On Sat, May 28, 2016 at 10:19 PM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 These are great findings!

 Can you please share the sample code that you wrote?

 The next step would be to start writing the actual membership scheme.
 Please refer the Kubernetes Membership scheme as a reference.


 On Sat, May 28, 2016 at 9:06 PM, Osura Rathnayake 
 wrote:

> Hi All,
>
>
>
> This is the summary of everything that I have done so far.
>
>
>
> Pre requisite: VMs which has WSO2 Application Server running should
> have been added to a particular network security group (NSG). In my case
> it’s ASNSG
>
>
>
> First the java app should be authenticated. Then it query for the
> information on ASNSG. Response of that API call includes names of all the
> network interfaces that are existed in ASNSG. Then each and every network
> interface is queried using their names to get private IP addresses of each
> of them. As the final outcome we get a list of IP addresses of VMs which
> has WSO2 Application Server running.
>
>
>
> *Authentication*
>
> In order to work with Azure Resource Manager (ARM) REST API, first of
> all our app has to be authenticated. ARM provides two methods for this
> purpose,
>
>
>
> 1) Authenticate using service principal
>
> 2) Authenticate using organizational account.
>
>
>
> I have used the first method that is authenticating using a service
> principal.  A Service Principal is an instance of an application that is
> within your Active Directory that is allowed access to one or more
> resources or an entire resource group. How to set up a service principal 
> is
> well described here [1]. Once you successfully set up a service principal,
> you will have the following information in hand.
>
>
>
> 1)  Client ID
>
> 2)  Client secret
>
> 3)  Tenant ID
>
> Above parameters and Azure subscription ID are used in the java app
> for authentication purpose. I have used Active Directory Authentication
> Library (ADAL) [2] for authentication. Once the authentication is
> successful, an authentication token will be issued and it will be used in
> the rest of the program as to make calls to API.
>
>
>
> *Getting information on ASNSG*
>
> For this purpose, [3] API reference is used. As the response we get a
> JSON string which includes names of NICs which are available in ASNSG.
>
>
>
> *Getting private IP address of each NIC*
>
> With the NIC names we received from previous API call, we can use this
> [4] API reference to get the private IP address of each NIC. And then with
> that information we can list out the IP addresses of all the VMs which has
> WSO2 Application Server running.
>
>
>
> [1]
> https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/
>
> [2] https://github.com/AzureAD/azure-activedirectory-library-for-java
>
> [3] https://msdn.microsoft.com/en-us/library/azure/mt163654.aspx
>
> [4] https://msdn.microsoft.com/en-us/library/azure/mt163611.aspx
>
>
>
> Thanks
>
>
>
> *From:* Imesh Gunaratne [mailto:im...@wso2.com]
> *Sent:* Saturday, May 28, 2016 8:53 AM
> *To:* Osura Rathnayake
> *Cc:* Isuru Haththotuwa; WSO2 Developers' List
> *Subject:* Re: [GSOC 16] Initial Project Progress
>
>
>
>
>
>
>
> On Sat, May 28, 2016 at 12:42 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Thank you
I have updated my Git repository with this sample code, please find it here
[1].

[1] https://github.com/osuran/azure-membership-scheme

Thanks

On Sun, May 29, 2016 at 8:41 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> On Sun, May 29, 2016 at 12:32 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Please find the attached project zip. From line 108 to 148 I hard coded
>> because I was getting errors with StringTokenizer and I didn't want to
>> focus much on that.
>> Okay I'm right on writing the actual membership scheme.
>>
> Thanks. Will have a look.
>
> It would be better if you can commit this to a github repository. By doing
> that, your sample is available for anyone to use/refer. Make sure to remove
> any sensitive information (passwords, etc.) before doing so.
>
>>
>> thanks
>>
>> On Sat, May 28, 2016 at 10:19 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> These are great findings!
>>>
>>> Can you please share the sample code that you wrote?
>>>
>>> The next step would be to start writing the actual membership scheme.
>>> Please refer the Kubernetes Membership scheme as a reference.
>>>
>>>
>>> On Sat, May 28, 2016 at 9:06 PM, Osura Rathnayake 
>>> wrote:
>>>
 Hi All,



 This is the summary of everything that I have done so far.



 Pre requisite: VMs which has WSO2 Application Server running should
 have been added to a particular network security group (NSG). In my case
 it’s ASNSG



 First the java app should be authenticated. Then it query for the
 information on ASNSG. Response of that API call includes names of all the
 network interfaces that are existed in ASNSG. Then each and every network
 interface is queried using their names to get private IP addresses of each
 of them. As the final outcome we get a list of IP addresses of VMs which
 has WSO2 Application Server running.



 *Authentication*

 In order to work with Azure Resource Manager (ARM) REST API, first of
 all our app has to be authenticated. ARM provides two methods for this
 purpose,



 1) Authenticate using service principal

 2) Authenticate using organizational account.



 I have used the first method that is authenticating using a service
 principal.  A Service Principal is an instance of an application that is
 within your Active Directory that is allowed access to one or more
 resources or an entire resource group. How to set up a service principal is
 well described here [1]. Once you successfully set up a service principal,
 you will have the following information in hand.



 1)  Client ID

 2)  Client secret

 3)  Tenant ID

 Above parameters and Azure subscription ID are used in the java app for
 authentication purpose. I have used Active Directory Authentication Library
 (ADAL) [2] for authentication. Once the authentication is successful, an
 authentication token will be issued and it will be used in the rest of the
 program as to make calls to API.



 *Getting information on ASNSG*

 For this purpose, [3] API reference is used. As the response we get a
 JSON string which includes names of NICs which are available in ASNSG.



 *Getting private IP address of each NIC*

 With the NIC names we received from previous API call, we can use this
 [4] API reference to get the private IP address of each NIC. And then with
 that information we can list out the IP addresses of all the VMs which has
 WSO2 Application Server running.



 [1]
 https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/

 [2] https://github.com/AzureAD/azure-activedirectory-library-for-java

 [3] https://msdn.microsoft.com/en-us/library/azure/mt163654.aspx

 [4] https://msdn.microsoft.com/en-us/library/azure/mt163611.aspx



 Thanks



 *From:* Imesh Gunaratne [mailto:im...@wso2.com]
 *Sent:* Saturday, May 28, 2016 8:53 AM
 *To:* Osura Rathnayake
 *Cc:* Isuru Haththotuwa; WSO2 Developers' List
 *Subject:* Re: [GSOC 16] Initial Project Progress







 On Sat, May 28, 2016 at 12:42 AM, Osura Rathnayake 
 wrote:

 Hi mentors,



 Sorry for the late reply. ARM portal doesn't have certain features like
 Active Directory but it doesn't matter because they can be implemented
 using classic portal and they work hand in hand. So all the features in
 classic plus the new features in ARM can be used if we choose ARM model.
 Therefore I think it's fruitful if we stick to ARM model, and the other
 important thing 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

On Sun, May 29, 2016 at 12:32 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Please find the attached project zip. From line 108 to 148 I hard coded
> because I was getting errors with StringTokenizer and I didn't want to
> focus much on that.
> Okay I'm right on writing the actual membership scheme.
>
Thanks. Will have a look.

It would be better if you can commit this to a github repository. By doing
that, your sample is available for anyone to use/refer. Make sure to remove
any sensitive information (passwords, etc.) before doing so.

>
> thanks
>
> On Sat, May 28, 2016 at 10:19 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> These are great findings!
>>
>> Can you please share the sample code that you wrote?
>>
>> The next step would be to start writing the actual membership scheme.
>> Please refer the Kubernetes Membership scheme as a reference.
>>
>>
>> On Sat, May 28, 2016 at 9:06 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi All,
>>>
>>>
>>>
>>> This is the summary of everything that I have done so far.
>>>
>>>
>>>
>>> Pre requisite: VMs which has WSO2 Application Server running should have
>>> been added to a particular network security group (NSG). In my case it’s
>>> ASNSG
>>>
>>>
>>>
>>> First the java app should be authenticated. Then it query for the
>>> information on ASNSG. Response of that API call includes names of all the
>>> network interfaces that are existed in ASNSG. Then each and every network
>>> interface is queried using their names to get private IP addresses of each
>>> of them. As the final outcome we get a list of IP addresses of VMs which
>>> has WSO2 Application Server running.
>>>
>>>
>>>
>>> *Authentication*
>>>
>>> In order to work with Azure Resource Manager (ARM) REST API, first of
>>> all our app has to be authenticated. ARM provides two methods for this
>>> purpose,
>>>
>>>
>>>
>>> 1) Authenticate using service principal
>>>
>>> 2) Authenticate using organizational account.
>>>
>>>
>>>
>>> I have used the first method that is authenticating using a service
>>> principal.  A Service Principal is an instance of an application that is
>>> within your Active Directory that is allowed access to one or more
>>> resources or an entire resource group. How to set up a service principal is
>>> well described here [1]. Once you successfully set up a service principal,
>>> you will have the following information in hand.
>>>
>>>
>>>
>>> 1)  Client ID
>>>
>>> 2)  Client secret
>>>
>>> 3)  Tenant ID
>>>
>>> Above parameters and Azure subscription ID are used in the java app for
>>> authentication purpose. I have used Active Directory Authentication Library
>>> (ADAL) [2] for authentication. Once the authentication is successful, an
>>> authentication token will be issued and it will be used in the rest of the
>>> program as to make calls to API.
>>>
>>>
>>>
>>> *Getting information on ASNSG*
>>>
>>> For this purpose, [3] API reference is used. As the response we get a
>>> JSON string which includes names of NICs which are available in ASNSG.
>>>
>>>
>>>
>>> *Getting private IP address of each NIC*
>>>
>>> With the NIC names we received from previous API call, we can use this
>>> [4] API reference to get the private IP address of each NIC. And then with
>>> that information we can list out the IP addresses of all the VMs which has
>>> WSO2 Application Server running.
>>>
>>>
>>>
>>> [1]
>>> https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/
>>>
>>> [2] https://github.com/AzureAD/azure-activedirectory-library-for-java
>>>
>>> [3] https://msdn.microsoft.com/en-us/library/azure/mt163654.aspx
>>>
>>> [4] https://msdn.microsoft.com/en-us/library/azure/mt163611.aspx
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> *From:* Imesh Gunaratne [mailto:im...@wso2.com]
>>> *Sent:* Saturday, May 28, 2016 8:53 AM
>>> *To:* Osura Rathnayake
>>> *Cc:* Isuru Haththotuwa; WSO2 Developers' List
>>> *Subject:* Re: [GSOC 16] Initial Project Progress
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, May 28, 2016 at 12:42 AM, Osura Rathnayake 
>>> wrote:
>>>
>>> Hi mentors,
>>>
>>>
>>>
>>> Sorry for the late reply. ARM portal doesn't have certain features like
>>> Active Directory but it doesn't matter because they can be implemented
>>> using classic portal and they work hand in hand. So all the features in
>>> classic plus the new features in ARM can be used if we choose ARM model.
>>> Therefore I think it's fruitful if we stick to ARM model, and the other
>>> important thing is sooner or later Microsoft will develop the ARM fully so
>>> eventually classic model will be obsolete(I think).
>>>
>>>
>>>
>>> +1 We may need to go ahead with what they provide at the moment.
>>>
>>>
>>>
>>> As we discussed in our last hangout, using a main program I could list
>>> out the IP addresses of the VMs where Application Servers are installed.
>>> Please arrange another hangout so that