Re: [Dev] IS Analytics - Handling zero values in Login Attempts over Time chart

[Manorama Perera]

Thanks Tharik.

After updating Vizgrammar the chart now looks like below.

[image: Inline image 1]

@Inosh
I've already done the necessary changes for the line charts in session view.

Thanks

On Mon, Jul 25, 2016 at 12:11 PM, Inosh Goonewardena  wrote:

> +1 for figure [2]. We might need to use the same approach for session
> chart (new/terminates count lines) as well. @Manorama, could you please
> check on that too.
>
> On Mon, Jul 25, 2016 at 11:37 AM, Hasintha Indrajee 
> wrote:
>
>>
>>
>> On Mon, Jul 25, 2016 at 11:14 AM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> I prefer the figure [2] which shows 0 values since it gives more
>>> meaningful information to the user..
>>>
>>> +1 for displaying as in figure [2] which is more meaningful.
>>>
>>>
>>> Thanks,
>>> Mohan
>>>
>>>
>>> On Mon, Jul 25, 2016 at 11:08 AM, Manorama Perera 
>>> wrote:
>>>
 Hi all,

 In Authentication dashboard we show login attempts using an area chart.
 The current implementation of this chart doesn't show zero values when
 there are no login attempts corresponding to some points of time within the
 selected period of time.

 For example, as described in [1], consider following scenario where we
 have login events from 10.10 AM to 10.25 AM

 From 10.10 - 10.13 - There are some login attempts
 From 10.14 - 10.17 - *Zero login attempts*
 From 10.18 - 10.25 - Some login attempts

 Currently we are showing the above information in the chart as follows,

 [image: Inline image 1]

 In this chart we are not showing the information about the zero login
 attempts.

 In order to show these information, we have changed the chart as below,

 [image: Inline image 2]

 Now it is showing the zero login attempts. But the chart now is divided
 into two areas.

 What is the better way to draw chart when we have zero login attempts.
 Appreciate any suggestions and opinions on this.

 [1] https://wso2.org/jira/browse/ANLYIS-64

 Thanks
 --
 Manorama Perera
 Software Engineer
 WSO2, Inc.;  http://wso2.com/
 Mobile : +94716436216

>>>
>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Associate Tech Lead,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>>
>> --
>> Hasintha Indrajee
>> WSO2, Inc.
>> Mobile:+94 771892453
>>
>>
>
>
> --
> Thanks & Regards,
>
> Inosh Goonewardena
> Associate Technical Lead- WSO2 Inc.
> Mobile: +94779966317
>



-- 
Manorama Perera
Software Engineer
WSO2, Inc.;  http://wso2.com/
Mobile : +94716436216
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EventPublisherConfigurationException at IS 5.2.0 Snapshot Startup

[Kishanthan Thangarajah]

This seems to be a JDK issue and fixed in later updates as per :
https://bugs.openjdk.java.net/browse/JDK-8059803

We are using a system property to get the OS name which - System.getProperty
("os.name")

On Fri, Jul 22, 2016 at 8:00 AM, Dulanja Liyanage  wrote:

> Also, Kernel Team, I wonder why the correct Windows version cannot be
> identified. Mine is a 10 but identified as 8.1. Could we please check on
> that?
>
> TID: [-1234] [] [2016-07-22 07:36:38,101]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Windows 8.1 6.3, amd64
> TID: [-1234] [] [2016-07-22 07:36:38,105]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> C:\Program Files\Java\jdk1.7.0_80\jre
> TID: [-1234] [] [2016-07-22 07:36:38,108]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.7.0_80
> TID: [-1234] [] [2016-07-22 07:36:38,110]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 24.80-b11,Oracle Corporation
> TID: [-1234] [] [2016-07-22 07:36:38,114]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> D:\packs\WSO2IS~1.0-S\bin\..
> TID: [-1234] [] [2016-07-22 07:36:38,116]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> D:\packs\WSO2IS~1.0-S\bin\..\tmp
> TID: [-1234] [] [2016-07-22 07:36:38,119]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> dulanja, en-US, Asia/Colombo
> TID: [-1234] [] [2016-07-22 07:36:38,233]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  The
> running OS : Windows 8.1 is not a tested Operating System for running WSO2
> Carbon
>
>
> On Fri, Jul 22, 2016 at 7:55 AM, Dulanja Liyanage 
> wrote:
>
>> Hi All,
>>
>> Getting the following error at the server startup:
>>
>> TID: [-1234] [] [2016-07-22 07:37:16,240] ERROR
>>
>> {org.wso2.carbon.event.publisher.core.EventPublisherDeployer}
>>
>> - Error, Event Publisher not deployed and in inactive state, Error while
>> deleting the Event Publisher : Illegal char <:> at index 2:
>> /D:/packs/WSO2IS~1.0-S/bin/../repository/deployment/server/\eventpublishers
>> org.wso2.carbon.event.publisher.core.exception.EventPublisherConfigurationException:
>> Error while deleting the Event Publisher : Illegal char <:> at index 2:
>> /D:/packs/WSO2IS~1.0-S/bin/../repository/deployment/server/\eventpublishers
>> at
>> org.wso2.carbon.event.publisher.core.internal.util.helper.EventPublisherConfigurationFilesystemInvoker.delete(EventPublisherConfigurationFilesystemInvoker.java:131)
>> at
>> org.wso2.carbon.event.publisher.core.EventPublisherDeployer.processDeployment(EventPublisherDeployer.java:177)
>> at
>> org.wso2.carbon.event.publisher.core.EventPublisherDeployer.deploy(EventPublisherDeployer.java:83)
>> at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
>> at
>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>> at
>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>> at
>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:135)
>> at
>> org.wso2.carbon.core.CarbonAxisConfigurator.deployServices(CarbonAxisConfigurator.java:567)
>> at
>> org.wso2.carbon.core.internal.DeploymentServerStartupObserver.completingServerStartup(DeploymentServerStartupObserver.java:51)
>> at
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.notifyBefore(CarbonCoreServiceComponent.java:238)
>> at
>> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:185)
>> at
>> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:288)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> at
>> org.eclipse.osgi

Re: [Dev] IS Analytics - Handling zero values in Login Attempts over Time chart

[Inosh Goonewardena]

+1 for figure [2]. We might need to use the same approach for session chart
(new/terminates count lines) as well. @Manorama, could you please check on
that too.

On Mon, Jul 25, 2016 at 11:37 AM, Hasintha Indrajee 
wrote:

>
>
> On Mon, Jul 25, 2016 at 11:14 AM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> I prefer the figure [2] which shows 0 values since it gives more
>> meaningful information to the user..
>>
>> +1 for displaying as in figure [2] which is more meaningful.
>>
>>
>> Thanks,
>> Mohan
>>
>>
>> On Mon, Jul 25, 2016 at 11:08 AM, Manorama Perera 
>> wrote:
>>
>>> Hi all,
>>>
>>> In Authentication dashboard we show login attempts using an area chart.
>>> The current implementation of this chart doesn't show zero values when
>>> there are no login attempts corresponding to some points of time within the
>>> selected period of time.
>>>
>>> For example, as described in [1], consider following scenario where we
>>> have login events from 10.10 AM to 10.25 AM
>>>
>>> From 10.10 - 10.13 - There are some login attempts
>>> From 10.14 - 10.17 - *Zero login attempts*
>>> From 10.18 - 10.25 - Some login attempts
>>>
>>> Currently we are showing the above information in the chart as follows,
>>>
>>> [image: Inline image 1]
>>>
>>> In this chart we are not showing the information about the zero login
>>> attempts.
>>>
>>> In order to show these information, we have changed the chart as below,
>>>
>>> [image: Inline image 2]
>>>
>>> Now it is showing the zero login attempts. But the chart now is divided
>>> into two areas.
>>>
>>> What is the better way to draw chart when we have zero login attempts.
>>> Appreciate any suggestions and opinions on this.
>>>
>>> [1] https://wso2.org/jira/browse/ANLYIS-64
>>>
>>> Thanks
>>> --
>>> Manorama Perera
>>> Software Engineer
>>> WSO2, Inc.;  http://wso2.com/
>>> Mobile : +94716436216
>>>
>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Associate Tech Lead,*
>> *Data Technologies Team,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: mo...@wso2.com
>> phone:(+94) 771117673
>>
>
>
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453
>
>


-- 
Thanks & Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Asantha Thilina]

Hi Tharindu,

I have cleaned up all the bugs and removed all unnecessary codes and
committed all the changes into my repository[1]

[1] https://github.com/asanthamax/mongodbuserstore

Thanks,
Asantha

On Sat, Jul 23, 2016 at 8:26 AM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> here i added all the commitments to spread sheet[1] and also i updated my
> blog with about java document api[2] and also i added findbug report[3] and
> also i updated my blog with the code quality analysis process i have done[4]
>
> [1]
> https://docs.google.com/spreadsheets/d/1jwSR_qFV-LfOS7ZTZ8CpiFFTYPoudDQF7zQhvblivaE/edit?usp=sharing
> [2]
> http://asanthamax.blogspot.com/2016/07/mongodb-user-store-package-hierarchy.html
> [3]https://googledrive.com/host/0B__ZE1ru1jkXZFdES3BOaHVyZ3M/
> [4]
> http://asanthamax.blogspot.com/2016/07/findbugs-in-mongodbuserstoremanager-in.html
>
> Thanks,
> Asantha
>
> On Fri, Jul 22, 2016 at 8:45 AM, Asantha Thilina  > wrote:
>
>> Hi Tharindu,
>>
>> I have created the API documentation and hosted in my google drive[1] i
>> will be preparing code inspection report as well will share it as soon as
>> well i also added github page also to the userstore script in here[2] as
>> well
>> [1] http://googledrive.com/host/0B__ZE1ru1jkXbDVoSDlveV9yNk0
>> [2] https://asanthamax.github.io/mongodbuserstore/
>>
>> Thanks,
>> Asantha
>>
>> On Tue, Jul 12, 2016 at 11:59 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>> sure we will arrange a hangout on next week and sure i will refer the
>>> link and do the necessary inspect in my code for any security
>>> vulnerabilities and update you sooner
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Tue, Jul 12, 2016 at 9:56 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asantha,

 Thanks for the update. I'm out of the country this week and won't be
 available. Let's have a hangout next week and discuss the final steps of
 the project.

 Along with find bugs, if you haven't enabled findsecuritybugs plugin,
 you can refer [1] and check if any security weaknesses are there in the
 code.

 [1]
 http://tharindue.blogspot.in/2016/06/static-code-analysis-for-java-using.html

 Thanks,
 TharinduE

 On Tue, Jul 12, 2016 at 5:32 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
> I have clean up the code according to find bug plugin and also for
> rollback purposes since it only concern when modifying or adding new user
> or role to user store i have manually added rollback option where if error
> occured all the changes done to db in code segment will be discard from db
> i updated the my repository with recent changes[1] now i preparing the
> documentation and test scripts.
>
> [1] https://github.com/asanthamax/mongodbuserstore
>
> Thanks,
> Asantha
>
> On Mon, Jul 4, 2016 at 2:54 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> thanks for the reply ,sure i will try out that and update the
>> progress as soon as possible
>>
>> Thanks,
>> Asantha
>>
>> On Mon, Jul 4, 2016 at 1:38 AM, Tharindu Edirisinghe <
>> tharin...@wso2.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> While you are adding the roll back transaction capability, also look
>>> into testing a high load and try to generate database level exceptions.
>>> Once thing you can try out is writing a client for performing userstore
>>> manager operations such as add user, add role, login, logout etc. and 
>>> play
>>> it with a high concurrency using Jmeter. Then we should be able to get a
>>> better understanding of transaction management with respective to 
>>> MongoDB.
>>>
>>> Regards,
>>> TharinduE
>>>
>>> On Mon, Jul 4, 2016 at 10:57 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi all,

 i will be trying for implement roll back transactions capability in
 MongoDB to add to MongoDB User Store[2] i found that MongoDB use a 
 concept
 call two phase commit[1] i trying to implement that inside my code but 
 it
 seems to be little complex and i think it may arise performance issue 
 when
 adding high load of dataset at once is there any other better method i 
 can
 achieve this task? any advices would be grateful

 [1]
 https://docs.mongodb.com/manual/tutorial/perform-two-phase-commits/
 [2] https://github.com/asanthamax/mongodbuserstore

 Thanks,
 Asantha

 On Wed, Jun 29, 2016 at 2:55 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> I have finished and added delete functions also to users ,roles
> and user claim deletions to my repo[1

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 the load balancer. We can add auto scale
>> rules, as to when additional VMs should be added and removed, based 
>> on the
>

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 when these VMs 
> getting
> added, it’s a whole new VM.  I’m trying to add custom made VMs which 
> has a
> wso2 prod

Re: [Dev] IS Analytics - Handling zero values in Login Attempts over Time chart

[Hasintha Indrajee]

On Mon, Jul 25, 2016 at 11:14 AM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> I prefer the figure [2] which shows 0 values since it gives more
> meaningful information to the user..
>
> +1 for displaying as in figure [2] which is more meaningful.
>
>
> Thanks,
> Mohan
>
>
> On Mon, Jul 25, 2016 at 11:08 AM, Manorama Perera 
> wrote:
>
>> Hi all,
>>
>> In Authentication dashboard we show login attempts using an area chart.
>> The current implementation of this chart doesn't show zero values when
>> there are no login attempts corresponding to some points of time within the
>> selected period of time.
>>
>> For example, as described in [1], consider following scenario where we
>> have login events from 10.10 AM to 10.25 AM
>>
>> From 10.10 - 10.13 - There are some login attempts
>> From 10.14 - 10.17 - *Zero login attempts*
>> From 10.18 - 10.25 - Some login attempts
>>
>> Currently we are showing the above information in the chart as follows,
>>
>> [image: Inline image 1]
>>
>> In this chart we are not showing the information about the zero login
>> attempts.
>>
>> In order to show these information, we have changed the chart as below,
>>
>> [image: Inline image 2]
>>
>> Now it is showing the zero login attempts. But the chart now is divided
>> into two areas.
>>
>> What is the better way to draw chart when we have zero login attempts.
>> Appreciate any suggestions and opinions on this.
>>
>> [1] https://wso2.org/jira/browse/ANLYIS-64
>>
>> Thanks
>> --
>> Manorama Perera
>> Software Engineer
>> WSO2, Inc.;  http://wso2.com/
>> Mobile : +94716436216
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Associate Tech Lead,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 
Hasintha Indrajee
WSO2, Inc.
Mobile:+94 771892453
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IS Analytics - Handling zero values in Login Attempts over Time chart

[Tharik Kanaka]

Hi All,

I think we should display 0 as in second approach when there are no values.
In vizGrammar i have included an outline for the area chart, so this should
avoid the separation of areas. Please update the js [1].

[1] https://github.com/wso2/VizGrammar/tree/master/dist

Regards,

On Mon, Jul 25, 2016 at 11:14 AM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> I prefer the figure [2] which shows 0 values since it gives more
> meaningful information to the user..
>
> @Prabath/Johann/Hasintha, wdyt ?
>
>
> Thanks,
> Mohan
>
>
> On Mon, Jul 25, 2016 at 11:08 AM, Manorama Perera 
> wrote:
>
>> Hi all,
>>
>> In Authentication dashboard we show login attempts using an area chart.
>> The current implementation of this chart doesn't show zero values when
>> there are no login attempts corresponding to some points of time within the
>> selected period of time.
>>
>> For example, as described in [1], consider following scenario where we
>> have login events from 10.10 AM to 10.25 AM
>>
>> From 10.10 - 10.13 - There are some login attempts
>> From 10.14 - 10.17 - *Zero login attempts*
>> From 10.18 - 10.25 - Some login attempts
>>
>> Currently we are showing the above information in the chart as follows,
>>
>> [image: Inline image 1]
>>
>> In this chart we are not showing the information about the zero login
>> attempts.
>>
>> In order to show these information, we have changed the chart as below,
>>
>> [image: Inline image 2]
>>
>> Now it is showing the zero login attempts. But the chart now is divided
>> into two areas.
>>
>> What is the better way to draw chart when we have zero login attempts.
>> Appreciate any suggestions and opinions on this.
>>
>> [1] https://wso2.org/jira/browse/ANLYIS-64
>>
>> Thanks
>> --
>> Manorama Perera
>> Software Engineer
>> WSO2, Inc.;  http://wso2.com/
>> Mobile : +94716436216
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Associate Tech Lead,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Tharik Kanaka*

WSO2, Inc | lean . enterprise . middleware

Email: tha...@wso2.com | Web: www.wso2.com
___
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,

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
>>> product installation at the VM startup.
>>>

 Note: only a limited horizontal scaling features are s

Re: [Dev] Adding YARN configuration files in anlytics4x distributions

[Mohanadarshan Vivekanandalingam]

Thanks Niranda.. Added them..


On Fri, Jul 22, 2016 at 9:34 PM, Niranda Perera  wrote:

> Hi all,
>
> Since the YARN support for DAS, the following config files were added to
> the spark server feature. [1]
>
> Please add those files in the relevant bin.xml file in the product
> analytic4x distribution to maintain the consistency [2]
>
> Best
>
> [1]
> https://github.com/wso2/carbon-analytics/tree/master/features/analytics-processors/org.wso2.carbon.analytics.spark.server.feature/resources/yarn
> [2]
> https://github.com/wso2/product-das/commit/df328c73ead9ca11b4c3e3c91fbc8c95ea70620b
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>



-- 
*V. Mohanadarshan*
*Associate Tech Lead,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IS Analytics - Handling zero values in Login Attempts over Time chart

[Damith Wickramasinghe]

Hi Mohan,

I prefer the figure [2] which shows 0 values since it gives more meaningful
> information to the user..
>

+1 and also I think x axis should be visible here (with a black line) so
that it does not show the feeling that this not divided . WDYT ?

Regards,
Damith

On Mon, Jul 25, 2016 at 11:14 AM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> I prefer the figure [2] which shows 0 values since it gives more
> meaningful information to the user..
>
> @Prabath/Johann/Hasintha, wdyt ?
>
>
> Thanks,
> Mohan
>
>
> On Mon, Jul 25, 2016 at 11:08 AM, Manorama Perera 
> wrote:
>
>> Hi all,
>>
>> In Authentication dashboard we show login attempts using an area chart.
>> The current implementation of this chart doesn't show zero values when
>> there are no login attempts corresponding to some points of time within the
>> selected period of time.
>>
>> For example, as described in [1], consider following scenario where we
>> have login events from 10.10 AM to 10.25 AM
>>
>> From 10.10 - 10.13 - There are some login attempts
>> From 10.14 - 10.17 - *Zero login attempts*
>> From 10.18 - 10.25 - Some login attempts
>>
>> Currently we are showing the above information in the chart as follows,
>>
>> [image: Inline image 1]
>>
>> In this chart we are not showing the information about the zero login
>> attempts.
>>
>> In order to show these information, we have changed the chart as below,
>>
>> [image: Inline image 2]
>>
>> Now it is showing the zero login attempts. But the chart now is divided
>> into two areas.
>>
>> What is the better way to draw chart when we have zero login attempts.
>> Appreciate any suggestions and opinions on this.
>>
>> [1] https://wso2.org/jira/browse/ANLYIS-64
>>
>> Thanks
>> --
>> Manorama Perera
>> Software Engineer
>> WSO2, Inc.;  http://wso2.com/
>> Mobile : +94716436216
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Associate Tech Lead,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 
Software Engineer
WSO2 Inc.; http://wso2.com

lean.enterprise.middleware

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

Re: [Dev] IS Analytics - Handling zero values in Login Attempts over Time chart

[Mohanadarshan Vivekanandalingam]

I prefer the figure [2] which shows 0 values since it gives more meaningful
information to the user..

@Prabath/Johann/Hasintha, wdyt ?


Thanks,
Mohan


On Mon, Jul 25, 2016 at 11:08 AM, Manorama Perera  wrote:

> Hi all,
>
> In Authentication dashboard we show login attempts using an area chart.
> The current implementation of this chart doesn't show zero values when
> there are no login attempts corresponding to some points of time within the
> selected period of time.
>
> For example, as described in [1], consider following scenario where we
> have login events from 10.10 AM to 10.25 AM
>
> From 10.10 - 10.13 - There are some login attempts
> From 10.14 - 10.17 - *Zero login attempts*
> From 10.18 - 10.25 - Some login attempts
>
> Currently we are showing the above information in the chart as follows,
>
> [image: Inline image 1]
>
> In this chart we are not showing the information about the zero login
> attempts.
>
> In order to show these information, we have changed the chart as below,
>
> [image: Inline image 2]
>
> Now it is showing the zero login attempts. But the chart now is divided
> into two areas.
>
> What is the better way to draw chart when we have zero login attempts.
> Appreciate any suggestions and opinions on this.
>
> [1] https://wso2.org/jira/browse/ANLYIS-64
>
> Thanks
> --
> Manorama Perera
> Software Engineer
> WSO2, Inc.;  http://wso2.com/
> Mobile : +94716436216
>



-- 
*V. Mohanadarshan*
*Associate Tech Lead,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] IS Analytics - Handling zero values in Login Attempts over Time chart

[Manorama Perera]

Hi all,

In Authentication dashboard we show login attempts using an area chart. The
current implementation of this chart doesn't show zero values when there
are no login attempts corresponding to some points of time within the
selected period of time.

For example, as described in [1], consider following scenario where we have
login events from 10.10 AM to 10.25 AM

>From 10.10 - 10.13 - There are some login attempts
>From 10.14 - 10.17 - *Zero login attempts*
>From 10.18 - 10.25 - Some login attempts

Currently we are showing the above information in the chart as follows,

[image: Inline image 1]

In this chart we are not showing the information about the zero login
attempts.

In order to show these information, we have changed the chart as below,

[image: Inline image 2]

Now it is showing the zero login attempts. But the chart now is divided
into two areas.

What is the better way to draw chart when we have zero login attempts.
Appreciate any suggestions and opinions on this.

[1] https://wso2.org/jira/browse/ANLYIS-64

Thanks
-- 
Manorama Perera
Software Engineer
WSO2, Inc.;  http://wso2.com/
Mobile : +94716436216
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Improve startup time in AS 6.0.0

[KasunG Gajasinghe]

On Sun, Jul 24, 2016 at 10:39 AM, Lakshman Udayakantha 
wrote:

> [+dev]
>
> On Sat, Jul 23, 2016 at 8:17 PM, Lakshman Udayakantha 
> wrote:
>
>> I copied all the jars in lib in AS 6.0.0 to a pure tomcat and I could see
>> 40(s) startup time there also. According to the jprofiler also most of the
>> time is going for jar scanning. So I added additional jars in AS than
>> tomcat to the tomcat.util.scan.StandardJarScanFilter.jarsToSkip section in
>> catalina.properties file because we don't want to scan them for
>> configurations. After adding them I could reduce uptime to 2.5 seconds. I
>> think we can go with this in next milestone. WDYT?
>>
>>
+1 Lakshman. We should try to go further down since 2.5sec is also a bit
high compared to Vanilla Tomcat. :-)


> Thanks
>> --
>> Lakshman Udayakantha
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>> Mobile: *0717429601 <0717429601>*
>>
>>
>
>
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0717429601 <0717429601>*
>
>


-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
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,

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 set the path where logs are
>>> located. This feature was under public preview, which might have been 
>>> one
>>> reason 

Re: [Dev] GSOC 2016: Proposal 7

[Kasun Indrasiri]

What's the current state of this project? Shall we do a end to end demo on
what you have done so far?

On Tue, Jun 21, 2016 at 6:24 PM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

> Here are the minutes of the review meeting we had yesterda
> y
>  -Some code refactoring was suggested. Reducing use of static variables
> and static methods was suggested.
>  -As the next milestone adding user configurable esb issue reporting
> suggested. This will change the current implementation to event   base
> implementation.There will be pre defined events for monitoring tool.
>   -E.g Out of memory event
>  Configurable options :Memory threshold
>  Outcomes (heap dumps,thread
> dumps)
>  Frequency of extracting dumps
>
> - Creating a class diagram
>
>
>
> On Wed, Jun 1, 2016 at 10:13 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Hello all,
>>
>> Progress of the tool so far
>>
>> The tool can be deployed in a remote machine to monitor ESB instance. It
>> connects to MBanServer of the targeted machine through RMI. Currently it
>> monitors memory usage, CPU usage and Network traffic of the ESB. Network
>> traffic details are gathered through PassThruHttpSender/receiver mbeans.
>> These metrics values are queried periodically. Period can be defined on a
>> property file under the resources folder inside the working dir. There are
>> three threads running inside the tool.
>>
>> Thread 1: Periodically query memory and operating system mbeans to find
>> out about heap memory usage & cpu load avearge
>>Threshold values for max memory usage and max cpu load
>> average can be set on the property file. So is the period.
>>If memory usage exceeds this max value heap dump will be
>> automatically generated on the remote ESB Home. User can
>>  specify any location. By default it will be created on ESB home. If the
>> average CPU load exceeds the max value the Threaddump will
>> be generated inside the tool. Location to thread dumps to be saved can be
>> specified by the user. Each time a heapdump requested a
>> seperate thread will be created to handle it.
>>
>> Thread 2: Periodically monitors network traffic from
>> PassThruHTTPSender/receiver mbeans. As we discussed earlier network details
>>are persisted to an embedded derby db. Period can be set.
>>
>> Thread 3: This handles persistence services. Period can be set.
>>
>> Name of the heap dumps are created as this "HeapDump "
>> +date.toString().replaceAll(":","")+".bin"
>> Name of the thread dumps are created as this  "ThreadDump"+new
>> Date().toString().replaceAll(":","")+".txt"
>>
>> Let me know if I got it right :)
>>
>>
>> On Mon, May 30, 2016 at 7:30 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Thanks Viraj
>>> On May 30, 2016 7:23 PM, "Viraj Senevirathne"  wrote:
>>>
 
 org.apache.synapse
 synapse-nhttp-transport
 

 On Sun, May 29, 2016 at 9:19 AM, Dinanjana Gunaratne <
 dinanjanagunara...@gmail.com> wrote:

> Hello all,
> I am facing a problem when trying to create a proxy object. I couldn't
> find correct maven dependency to get class
> org.apache.synapse.transport.passthru.jmx.TransportView. Can you
> direct me to the correct dependency.
>
>
> On Sat, May 14, 2016 at 8:46 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Dear all,
>> I have added DynamicReports (which is an implementation based on
>> Jasper reports) as the reporting framework for the Flight recorder. It
>> would be great if I can have wso2 license headers for refactor. Direct me
>> for IntelliJ headers. All changes can be seen here [1]
>> 
>>
>> [1 ]https://github.com/dinanjana/ESBMonitor
>>
>> On Fri, May 6, 2016 at 10:43 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> [1]https://github.com/dinanjana/ESBMonitor
>>>
>>> On Fri, May 6, 2016 at 10:42 PM, Dinanjana Gunaratne <
>>> dinanjanagunara...@gmail.com> wrote:
>>>
 Hello all,
 I have started working on the project. You can have a look on what
 I am doing from this repo [1]. Currently I am implementing heap dump
 creator for this project. Can you explain me how currently heap dump
 analyzing take place with ESB OOM events ? In the current 
 implementation of
 the flight recorder this method creates a .bin file with a snapshot of 
 heap
 memory.

 On Sun, May 1, 2016 at 10:01 PM, Dinanjana Gunaratne <
 dinanjanagunara...@gmail.com> wrote:

> Hello all,
> I have started working on the project. You can have a look on what
> i will be doing on this [1]
>

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC1

[Thanuja Uruththirakodeeswaran]

Hi Akila,

Thanks for pointing this. I have fixed this in commit [1].

Thanks.

[1].
https://github.com/wso2/puppet-modules/commit/71a52d16f3b1d765f911d0ce197f627c36c513a6


On Sat, Jul 23, 2016 at 11:58 AM, Akila Ravihansa Perera  wrote:

> Hi Pubudu,
>
> The pom version in master branch should always be a SNAPSHOT version [1].
>
> [1] https://github.com/wso2/puppet-modules/blob/master/pom.xml#L24
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 10:04 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Devs,
>>
>> This is the first release candidate (RC1) of WSO2 Puppet Modules 2.1.0
>> release. Please download, verify, and vote. Voting will be open for 72
>> hours or as needed.
>>
>> This release fixes following issues:
>>
>> https://wso2.org/jira/browse/PMODULES-16?filter=13155
>>
>> ​Source and binary distribution files:
>>
>> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1
>>
>> The tag to be voted upon:
>>
>> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc1
>>
>> Release verification guide:
>>
>> https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment
>>
>> Refer modules README files for more details.
>>
>> Please vote as follows.
>>
>> [+] Stable - go ahead and release
>>
>> [-]  Broken - do not release (please explain why)
>>
>> Thank you,
>> WSO2 PaaS Team.
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> 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
>
>


-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

mobile: +94 774363167
___
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 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 
>>> any
>>> inconvenience. I will update you with a detailed email today for sure.
>>>
>>> Thanks in advance,
>>>
>>>

[Dev] Importing samples of wso2cep in developer-studio-eclipse

[Aneela Safdar]

Hi,
I am trying to import http sample of wso2cep in eclipse-developer-studio with 
File-->New--->Java--->Java Project From Existing Build File

but it isn't importing the src folder in eclipse. How am I suppose to make this 
import successful? I have used complete installation of wso2 developer studio.

Kindly help.
 Regards, Aneela Safdar___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev