Re: [Dev] Storing TimeZone neutral times with Mysql

[Hasitha Aravinda]

Hi Vinod,

I checked MSSQL [1], Postgres [2], DB2 [3], and Oracle [4] documentations
and their max supported time-stamp is . It seems like only MySQL has
this problem.

IMO, we should support time-stamp values beyond 2038, if database supports
it. So shall we add a logic to determine DB type and if DB is MySQL, then
support up to its max time-stamp, if DB is another type, then simple allow
 as Max time-stamp.

Issue in datetime format is, it doesn't support timezone values (Expect for
MSSQL). Since we are considering use-case in different time zones, I think
we have to go with time-stamp.

[1] - https://msdn.microsoft.com/en-us/library/ms187819.aspx
[2] - https://www.postgresql.org/docs/9.2/static/datatype-datetime.html
[3] -
https://www.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/sqlref/src/tpc/db2z_limits.html
[4] - http://www.techonthenet.com/oracle/datatypes.php

Thanks,
Hasitha.

On Wed, Jul 20, 2016 at 11:41 AM, Vinod Kavinda  wrote:

> Hi all,
> I have a requirement that I need to store timestamp values where it will
> be required to retrieve it in different time zones. So in MySql, I used
> timestamp data type where MySQL store  the time in UTC and return in local
> timezone.
>
> The problem is when the time is null, I need to represent 'forever'.
> Thought of setting the max date possible in epoch time (Long.Max) for this.
> But the max possible timestamp value in MySql is year 2038/1/19... [1].
>
> So, is this 2038 is fair enough as the max date? (This will be the max
> date for other DBMS also.)
>
> Should I use DateTime datatype instead and handle the timezone stuff in
> application level?
>
> What is the best practice used here in Wso2?
>
>
> [1] - https://dev.mysql.com/doc/refman/5.5/en/datetime.html
>
> Regards,
> Vinod
> --
> Vinod Kavinda
> Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> 
>
>


-- 
--
Hasitha Aravinda,
Associate Technical Lead,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile : +94 718 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] Too many mysql connections when starting ES instances

[Dilini Gunatilake]

[Adding Mariangela]

Hi,

I think the below points should be documented in the ES doc space to avoid
more issues until a proper solution is in place.

[1] max_connections to configure to mitigate "too many connections" issue.
It is good if we can communicate about delaying each server startups as
well.

[2] the time taken to start the servers due to indexing when there are data
in the database
Normally it takes around 10 mins to settle each server when there are
around 30,000 assets in the db

Reported [1] and [2] to track the issues.

[1] https://wso2.org/jira/browse/STORE-1424
[2] https://wso2.org/jira/browse/DOCUMENTATION-3649

Regards,
Dilini


On Fri, Jul 15, 2016 at 6:28 PM, Udara Liyanage  wrote:

>
>
> On Fri, Jul 15, 2016 at 5:39 AM, Thushara Ranawaka 
> wrote:
>
>> Hi Chanaka,
>>
>> On Fri, Jul 15, 2016 at 2:42 PM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Thushara,
>>>
>>> Increase the mysql active connections to 350. Please note that this is
>>> bounded to server specs.
>>> Now start 2 servers at a time. Wait 10 mins before starting the other 2
>>> WSO2 servers.
>>> Or else you can always start 1 server at a time every 10 mins. Therefore
>>> it will take 30 mins to start all 4 nodes.
>>>
>>> Do you think we can tell something like this in front of a customer?
>>> Normally customers want to start the servers within seconds and they want
>>> to start an entire cluster within minutes (maximum). Please provide a
>>> recommendation which makes sense in a real world. We need a proper way to
>>> handle this.
>>>
>>
>> This recommendation is for ES not for ESB and specially not for customers
>> since we can automate this using config. ES uses governance features
>> therefore ES need to have solr enabled. Therefore please disable[3] solr in
>> all ESB nodes. Further more I understand they will start all the servers
>> straightaway but for ES initial start(database with data) there is a heavy
>> indexing process is happening in the background to have a smooth ride
>> afterward. Since there is 4 nodes either user have to increase database
>> connections from DB side or start servers one by one with a delay. We can
>> automate this using indexingConfiguration[4] in registry.xml. This is just
>> a one time thing, you can change it back to default values after the first
>> startup.
>>
>> [4] - {Different values in each nodes with 10
>> mins different.}
>> 3
>> 
>> 50
>> 
>> 10
>>
>> Thanks,
>> Thushara.
>>
>>
> In a different thought, this kind of work arounds will cause products  to
> hard to be run in a cloud environment where
> you can not guarantee product startup order since containers/vm come
> and go due to various reasons
> Manually changing configurations also not possible in a automated
> deployment environment.
> So it is better if we can have a solid solution.
>
>>
>>
> On Fri, Jul 15, 2016 at 1:25 PM, Thushara Ranawaka 
>>> wrote:
>>>
 Hi Dilini,


 On Thu, Jul 14, 2016 at 2:31 PM, Dilini Gunatilake 
 wrote:

> Hi,
>
> @Thushara,
> Thanks for the info. Any recommended number of max_connections to
> configure considering indexing with a high load etc? Then we can add those
> details in the docs to avoid future issues.
>

 My personal recommendation,
 Increase the mysql active connections to 350. Please note that this is
 bounded to server specs.
 Now start 2 servers at a time. Wait 10 mins before starting the other 2
 WSO2 servers.
 Or else you can always start 1 server at a time every 10 mins.
 Therefore it will take 30 mins to start all 4 nodes.

 Thanks,
 Thushara.


>
> @Sumedha,
> I was able to start all the nodes because the number of connections
> reduces after some time.
>
> As Rajith mentioned, the concern is having that number of connections
> created just for a server startup having less than 25 assets.
>
> Thanks,
> Dilini
>
>
> On Thu, Jul 14, 2016 at 12:53 PM, Rajith Vitharana 
> wrote:
>
>> Hi,
>>
>> On Thu, Jul 14, 2016 at 12:44 PM, Sumedha Rubasinghe <
>> sume...@wso2.com> wrote:
>>
>>> Guys,
>>> Some food for thought.
>>>
>>> 1. A single MySQL Server has a globally defined max_connections
>>> figure (151 as Dilini mentioned)
>>>
>>> So on a clustered setup, when you point to a single MySQL Server
>>> from various WSO2 products, depending on no of keep alive connections
>>> specified, you will at some point will hit too many connections from 
>>> server
>>> side @ some point.
>>>
>> Yeah totally agree, but that much(395) is bit high AFAIU when just
>> starting up a server(without any load in 4 servers, and when it 
>> stabilize,
>> it only consumes less than 20 connections without load)
>>
>> @Thushara, Thanks for the info, will check what you have mentioned.
>>
>> Thanks,

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Imesh Gunaratne]

Hi Akila,

On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera 
wrote:

> Hi Imesh,
>
> I've switched to command based health check for MySQL services. It will
> basically run "mysqladmin -u $MYSQL_USER -p$MYSQL_PASSWORD status". This
> will ensure MySQL service is ready to serve SQL requests.
>

​Wouldn't this make it mandatory to have mysqladmin client installed in the
host machine where the deployment script is run?

Thanks​


>
> Thanks.
>
> On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi,
>>>
>>> Yes, myself and Pubudu also faced this issue, lets fix it properly.
>>>
>>> On Wed, Jul 6, 2016 at 10:57 PM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Akila,

 Yes we faced several issues related to this. Apart from what you have
 mentioned, we encountered mysql app name is not getting resolved. This
 could be the delay in updating Mesos DNS. For these issues we looking into
 following options.

 *Option 1:*
 Use a sleep before deploying a carbon server. Not the best option.

 *Option 2:*
 Depend on the health status results.

 Currently, we do use a health check for mysql apps. Using dcos CLI we
 can check the status of the app whether the app is alive or not. But this
 cannot guarantee the DBs are ready to serve requests and Mesos DNS is
 updated.

>>>
>>
>>> What if we query the Mesos DNS in addition to port checking to see if
>>> its updated? AFAIR what we are seeing is an java.net.UnknownHostException,
>>> related to the DB hostname.
>>>
>>
>> ​May be we can wait for MySQL sockets as we do for Carbon server
>> transports.
>>
>> 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
>>
>>
>
>
> --
> 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] [Mesos artifacts] Deploy script is failing to check database service

[Akila Ravihansa Perera]

Hi Imesh,

mysqladmin client need not be installed on host machine since Mesos will
run this command as a "docker run" command which will be executed inside
the container. MySQL official image contains mysqladmin tool so this is not
a problem.

Thanks.

On Wed, Jul 20, 2016 at 12:46 PM, Imesh Gunaratne  wrote:

> Hi Akila,
>
> On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Imesh,
>>
>> I've switched to command based health check for MySQL services. It will
>> basically run "mysqladmin -u $MYSQL_USER -p$MYSQL_PASSWORD status". This
>> will ensure MySQL service is ready to serve SQL requests.
>>
>
> ​Wouldn't this make it mandatory to have mysqladmin client installed in
> the host machine where the deployment script is run?
>
> Thanks​
>
>
>>
>> Thanks.
>>
>> On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi,

 Yes, myself and Pubudu also faced this issue, lets fix it properly.

 On Wed, Jul 6, 2016 at 10:57 PM, Pubudu Gunatilaka 
 wrote:

> Hi Akila,
>
> Yes we faced several issues related to this. Apart from what you have
> mentioned, we encountered mysql app name is not getting resolved. This
> could be the delay in updating Mesos DNS. For these issues we looking into
> following options.
>
> *Option 1:*
> Use a sleep before deploying a carbon server. Not the best option.
>
> *Option 2:*
> Depend on the health status results.
>
> Currently, we do use a health check for mysql apps. Using dcos CLI we
> can check the status of the app whether the app is alive or not. But this
> cannot guarantee the DBs are ready to serve requests and Mesos DNS is
> updated.
>

>>>
 What if we query the Mesos DNS in addition to port checking to see if
 its updated? AFAIR what we are seeing is an java.net.UnknownHostException,
 related to the DB hostname.

>>>
>>> ​May be we can wait for MySQL sockets as we do for Carbon server
>>> transports.
>>>
>>> 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
>>>
>>>
>>
>>
>> --
>> 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
>
>


-- 
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] WSO2 Developer Studio 4.2.0 RC

[Sohani Weerasinghe]

Hi All,

I have tested the updater tool and found that we need to update the update
and release site URLs with 4.2.0. (Reported at [1]).

[1] https://wso2.org/jira/browse/TOOLS-3436

Thanks,
Sohani

Sohani Weerasinghe
Senior Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine

On Wed, Jul 20, 2016 at 12:15 PM, Jasintha Dasanayake 
wrote:

> HI team
>
> Why we are not proceeding this vote and complete the release ? are there
> any blocking issues ?
>
> Thanks and Regards
> /Jasintha
>
> On Fri, Jul 15, 2016 at 7:44 AM, Awanthika Senarath 
> wrote:
>
>> Hello Devs,
>>
>> We are pleased to announce the WSO2 Developer Studio 4.2.0 RC vote.
>>
>> P2 repository of WSO2 developer Studio Kernle 4.2.0 is available here
>> .
>>  Source
>> and Tag Location to be voted upon is available here
>> 
>> .
>>
>> With this release WSO2 Developer Studio kernel moves into RCP mode
>> further reducing the size.
>>
>> We have also introduced a web base dashboard for Developer Studio to
>> enhance user experience.
>>
>> Also the XULRunner is embedded to maintain unbroken user experience in
>> WSO2 Developer Studio for windows when using web technologies.
>>
>> We have also fixed several bugs
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-441
>> [2] https://wso2.org/jira/browse/TOOLS-3423
>>
>> Please vote as follows.
>>
>>
>>1. [+] Stable - go ahead and release
>>2. [-]  Broken - do not release (please explain why)
>>
>>
>>
>> Awanthika Senarath
>> Senior Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>
>
> --
>
> *Jasintha Dasanayake**Associate Technical Lead*
>
> *WSO2 Inc. | http://wso2.com lean . enterprise .
> middleware*
>
>
> *mobile :- 0711-368-118 <0711-368-118>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC2

[Nirmal Fernando]

-1 We have found a critical issue with data indexing.

On Tue, Jul 19, 2016 at 3:54 AM, Abimaran Kugathasan 
wrote:

> Hi Devs,
>
> *WSO2 API Manager 2.0.0-RC2 Released*
>
> This is the 2nd Release Candidate of the WSO2 API Manager 2.0.0
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> The distribution is available to download at [1]
>
> [1] : *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc2
> *
>
> *WSO2 **API Manager Analytics 2.0.0 RC2** Released*
>
> This is the 2nd Release Candidate of the WSO2 API Manager Analytics 2.0.0
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> The distribution is available to download  [2]
>
> Fixed Issue in [3], known issues [4]
>
> [2] : *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc2
> *
> [3] : https://wso2.org/jira/issues/?filter=13138
> [4] : https://wso2.org/jira/issues/?filter=13139
> 
>
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [GSoC Dockerfiles] Issues with setting up Kubernetes using Vagrant

[Imesh Gunaratne]

Hi Abhishek,

On Wed, Jul 20, 2016 at 9:49 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi Mentors,
>
> I have been working on setting up Kubernetes cluster using vagrant and
> docker using [1]. I ran into multiple issues (coreos download taking hours,
> nfsd not being setup etc), however, those got resolved.
>

​Can you please execute following to ssh into the master node and check the
system log?

vagrant ssh master
journalctl -f​


>
> Now, when I launch the setup using run.sh, I get this error [2]. I tried
> wiping out everything (vagrant destroy -f) and restart the whole process
> again, I get the same issue.
>
> One thing to note is, my host os is Mac and I use VirtualBox for
> development, so essentially I have virtualbox setup inside virtualbox. I
> don't think it should matter, but would like to get other people's opinion
> on this.
>

​This works on OSX.​


>
> While this issue gets resolved, I am planning to complete another
> milestone to add smoke tests for ESB and MB. I feel like, I should complete
> the test workflow for default platform before moving to Kubernetes, since
> the latter involves a lot of new technologies, more moving parts and other
> unknowns. I do plan to address Kubernetes testing, but would like to do
> that once default platform test workflow is complete. Thoughts?
>

​+1

If [1] does not work for you, please try following:
http://kubernetes.io/docs/getting-started-guides/vagrant/

Thanks​


>
> Thanks,
> Abhishek
>
> [1]. https://github.com/imesh/kubernetes-vagrant-setup
> [2].
> master: Waiting for machine to boot. This may take a few minutes...
> master: SSH address: 127.0.0.1:
> master: SSH username: core
> master: SSH auth method: private key
>
> Timed out while waiting for the machine to boot. This means that
> Vagrant was unable to communicate with the guest machine within
> the configured ("config.vm.boot_timeout" value) time period.
>
>
>


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

[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 *
>>
>>
>> Azure has a native monitoring tool which involves collecting and
>> tracking metrics, anal

Re: [Dev] [Mesos-Marathon] Issues in Creating Point to Point TCP Connections in Mesos-Marathon based Deployments

[Isuru Haththotuwa]

Update:
=

Due to the issues we got in setting up the min HA setup, we reverted to
using DAS with spark client mode [1]. After deploying the spark 1.6
application, got the error [2] from the DAS side. The reason was having the
spark master url as spark://:. It should be
mesos://:. But in DAS 3.0.1 we are expecting the spark master
url to start with spark [3]. This needs to be patched. After patching it,
the connection issue from DAS to spark master got resolved. But facing
another issue [4]. Seems we need to have a libmesos.so shared object
library in one of the relevant locations
(/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib). Therefore,
to proceed with this appoach, we might have to have mesos installed in the
machine (in this case, in the Docker image) in which DAS is running.

[1].
https://docs.wso2.com/display/CLUSTER44x/Spark+Deployment+Patterns+-+DAS+3.0.1#SparkDeploymentPatterns-DAS3.0.1-Clientmode

[2].
[2016-07-20 06:39:25,311]  INFO
{org.wso2.carbon.analytics.spark.core.internal.SparkAnalyticsExecutor} -
Starting SPARK CLIENT pointing to an external Spark Cluster
[2016-07-20 06:39:26,073]  INFO {Remoting} -  Starting remoting
[2016-07-20 06:39:26,258]  INFO {Remoting} -  Remoting started; listening
on addresses :[akka.tcp://sparkDriver@172.17.0.2:21543]
[2016-07-20 06:39:26,987]  WARN {akka.remote.ReliableDeliverySupervisor} -
Association with remote system [akka.tcp://sparkMaster@master.mesos:5050]
has failed, address is now gated for [5000] ms. Reason is: [Association
failed with [akka.tcp://sparkMaster@master.mesos:5050]].
[2016-07-20 06:39:46,878]  WARN {akka.remote.ReliableDeliverySupervisor} -
Association with remote system [akka.tcp://sparkMaster@master.mesos:5050]
has failed, address is now gated for [5000] ms. Reason is: [Association
failed with [akka.tcp://sparkMaster@master.mesos:5050]].
[2016-07-20 06:40:06,882]  WARN {akka.remote.ReliableDeliverySupervisor} -
Association with remote system [akka.tcp://sparkMaster@master.mesos:5050]
has failed, address is now gated for [5000] ms. Reason is: [Association
failed with [akka.tcp://sparkMaster@master.mesos:5050]].
[2016-07-20 06:40:26,983] ERROR {akka.actor.OneForOneStrategy} -
java.lang.NullPointerException
at
org.apache.spark.deploy.client.AppClient$ClientActor$$anonfun$receiveWithLogging$1.applyOrElse(AppClient.scala:160)
at
scala.runtime.AbstractPartialFunction$mcVL$sp.apply$mcVL$sp(AbstractPartialFunction.scala:33)
at
scala.runtime.AbstractPartialFunction$mcVL$sp.apply(AbstractPartialFunction.scala:33)
at
scala.runtime.AbstractPartialFunction$mcVL$sp.apply(AbstractPartialFunction.scala:25)
at
org.apache.spark.util.ActorLogReceive$$anon$1.apply(ActorLogReceive.scala:59)
at
org.apache.spark.util.ActorLogReceive$$anon$1.apply(ActorLogReceive.scala:42)
at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:118)
at
org.apache.spark.util.ActorLogReceive$$anon$1.applyOrElse(ActorLogReceive.scala:42)
at akka.actor.Actor$class.aroundReceive(Actor.scala:465)
at
org.apache.spark.deploy.client.AppClient$ClientActor.aroundReceive(AppClient.scala:61)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
at akka.actor.ActorCell.invoke(ActorCell.scala:487)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
at akka.dispatch.Mailbox.run(Mailbox.scala:220)
at
akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at
scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at
scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at
scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
[2016-07-20 06:40:26,999]  WARN {akka.remote.ReliableDeliverySupervisor} -
Association with remote system [akka.tcp://sparkMaster@master.mesos:5050]
has failed, address is now gated for [5000] ms. Reason is: [Association
failed with [akka.tcp://sparkMaster@master.mesos:5050]].
[2016-07-20 06:40:27,306] ERROR
{org.wso2.carbon.analytics.spark.core.internal.AnalyticsComponent} -  Error
initializing analytics executor: Unable to create analytics client. Cannot
call methods on a stopped SparkContext

[3].
https://github.com/wso2/carbon-analytics/blob/v1.0.5/components/analytics-processors/org.wso2.carbon.analytics.spark.core/src/main/java/org/wso2/carbon/analytics/spark/core/internal/SparkAnalyticsExecutor.java#L270

[4].
Failed to load native Mesos library from
/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
[2016-07-20 09:27:16,151] ERROR
{org.wso2.carbon.analytics.spark.core.internal.AnalyticsComponent} -  Error
initializing analytics executor: no mesos in java.library.path
java.lang.UnsatisfiedLinkError: no mesos in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1886)
at java.lang.Runtime.loadLibrary0(Runtime.java:849)
at java.

Re: [Dev] WSO2 Developer Studio 4.2.0 RC

[Sohani Weerasinghe]

Also, I have tested below functionalities

1. Wed Based Dashboard with ESB components
2. The issue with artifact dialog boxes at [1]

these are working fine but due to the issue I reported at [2] my vote is -1

[1] https://wso2.org/jira/browse/DEVTOOLESB-441
[2] https://wso2.org/jira/browse/TOOLS-3436

Thanks,
Sohani



Sohani Weerasinghe
Senior Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine

On Wed, Jul 20, 2016 at 2:26 PM, Sohani Weerasinghe  wrote:

> Hi All,
>
> I have tested the updater tool and found that we need to update the update
> and release site URLs with 4.2.0. (Reported at [1]).
>
> [1] https://wso2.org/jira/browse/TOOLS-3436
>
> Thanks,
> Sohani
>
> Sohani Weerasinghe
> Senior Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, Jul 20, 2016 at 12:15 PM, Jasintha Dasanayake 
> wrote:
>
>> HI team
>>
>> Why we are not proceeding this vote and complete the release ? are there
>> any blocking issues ?
>>
>> Thanks and Regards
>> /Jasintha
>>
>> On Fri, Jul 15, 2016 at 7:44 AM, Awanthika Senarath 
>> wrote:
>>
>>> Hello Devs,
>>>
>>> We are pleased to announce the WSO2 Developer Studio 4.2.0 RC vote.
>>>
>>> P2 repository of WSO2 developer Studio Kernle 4.2.0 is available here
>>> .
>>>  Source
>>> and Tag Location to be voted upon is available here
>>> 
>>> .
>>>
>>> With this release WSO2 Developer Studio kernel moves into RCP mode
>>> further reducing the size.
>>>
>>> We have also introduced a web base dashboard for Developer Studio to
>>> enhance user experience.
>>>
>>> Also the XULRunner is embedded to maintain unbroken user experience in
>>> WSO2 Developer Studio for windows when using web technologies.
>>>
>>> We have also fixed several bugs
>>>
>>> [1] https://wso2.org/jira/browse/DEVTOOLESB-441
>>> [2] https://wso2.org/jira/browse/TOOLS-3423
>>>
>>> Please vote as follows.
>>>
>>>
>>>1. [+] Stable - go ahead and release
>>>2. [-]  Broken - do not release (please explain why)
>>>
>>>
>>>
>>> Awanthika Senarath
>>> Senior Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>
>>
>> --
>>
>> *Jasintha Dasanayake**Associate Technical Lead*
>>
>> *WSO2 Inc. | http://wso2.com lean . enterprise .
>> middleware*
>>
>>
>> *mobile :- 0711-368-118 <0711-368-118>*
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Imesh Gunaratne]

On Wed, Jul 20, 2016 at 1:19 PM, Akila Ravihansa Perera 
wrote:

> Hi Imesh,
>
> mysqladmin client need not be installed on host machine since Mesos will
> run this command as a "docker run" command which will be executed inside
> the container. MySQL official image contains mysqladmin tool so this is not
> a problem.
>

​I thought this was regarding the check we need to make before deploying
the WSO2 server containers to wait until MySQL containers become ready.
​

​Thanks​


> Thanks.
>
> On Wed, Jul 20, 2016 at 12:46 PM, Imesh Gunaratne  wrote:
>
>> Hi Akila,
>>
>> On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Imesh,
>>>
>>> I've switched to command based health check for MySQL services. It will
>>> basically run "mysqladmin -u $MYSQL_USER -p$MYSQL_PASSWORD status". This
>>> will ensure MySQL service is ready to serve SQL requests.
>>>
>>
>> ​Wouldn't this make it mandatory to have mysqladmin client installed in
>> the host machine where the deployment script is run?
>>
>> Thanks​
>>
>>
>>>
>>> Thanks.
>>>
>>> On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne  wrote:
>>>


 On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
 wrote:

> Hi,
>
> Yes, myself and Pubudu also faced this issue, lets fix it properly.
>
> On Wed, Jul 6, 2016 at 10:57 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Akila,
>>
>> Yes we faced several issues related to this. Apart from what you have
>> mentioned, we encountered mysql app name is not getting resolved. This
>> could be the delay in updating Mesos DNS. For these issues we looking 
>> into
>> following options.
>>
>> *Option 1:*
>> Use a sleep before deploying a carbon server. Not the best option.
>>
>> *Option 2:*
>> Depend on the health status results.
>>
>> Currently, we do use a health check for mysql apps. Using dcos CLI we
>> can check the status of the app whether the app is alive or not. But this
>> cannot guarantee the DBs are ready to serve requests and Mesos DNS is
>> updated.
>>
>

> What if we query the Mesos DNS in addition to port checking to see if
> its updated? AFAIR what we are seeing is an java.net.UnknownHostException,
> related to the DB hostname.
>

 ​May be we can wait for MySQL sockets as we do for Carbon server
 transports.

 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


>>>
>>>
>>> --
>>> 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
>>
>>
>
>
> --
> 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] WSO2 Developer Studio 4.2.0 RC

[Kavith Lokuhewage]

Hi All,

Vote has failed due to [1] and we are stopping this vote now.

[1] is already fixed and improved [2] the logic to identify version
automatically to avoid this issue in future.

We will put another RC vote soon.

Thanks,

[1] https://wso2.org/jira/browse/TOOLS-3436
[2]
https://github.com/wso2/developer-studio/commit/0afc63f08cfcc60f7a3b6ddacb846f38119fce03



*Kavith Lokuhewage*
Senior Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +94779145123
Linkedin   Twitter


On Wed, Jul 20, 2016 at 4:37 PM, Sohani Weerasinghe  wrote:

> Also, I have tested below functionalities
>
> 1. Wed Based Dashboard with ESB components
> 2. The issue with artifact dialog boxes at [1]
>
> these are working fine but due to the issue I reported at [2] my vote is -1
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-441
> [2] https://wso2.org/jira/browse/TOOLS-3436
>
> Thanks,
> Sohani
>
>
>
> Sohani Weerasinghe
> Senior Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, Jul 20, 2016 at 2:26 PM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> I have tested the updater tool and found that we need to update the
>> update and release site URLs with 4.2.0. (Reported at [1]).
>>
>> [1] https://wso2.org/jira/browse/TOOLS-3436
>>
>> Thanks,
>> Sohani
>>
>> Sohani Weerasinghe
>> Senior Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Wed, Jul 20, 2016 at 12:15 PM, Jasintha Dasanayake 
>> wrote:
>>
>>> HI team
>>>
>>> Why we are not proceeding this vote and complete the release ? are there
>>> any blocking issues ?
>>>
>>> Thanks and Regards
>>> /Jasintha
>>>
>>> On Fri, Jul 15, 2016 at 7:44 AM, Awanthika Senarath 
>>> wrote:
>>>
 Hello Devs,

 We are pleased to announce the WSO2 Developer Studio 4.2.0 RC vote.

 P2 repository of WSO2 developer Studio Kernle 4.2.0 is available here
 .
  Source
 and Tag Location to be voted upon is available here
 
 .

 With this release WSO2 Developer Studio kernel moves into RCP mode
 further reducing the size.

 We have also introduced a web base dashboard for Developer Studio to
 enhance user experience.

 Also the XULRunner is embedded to maintain unbroken user experience in
 WSO2 Developer Studio for windows when using web technologies.

 We have also fixed several bugs

 [1] https://wso2.org/jira/browse/DEVTOOLESB-441
 [2] https://wso2.org/jira/browse/TOOLS-3423

 Please vote as follows.


1. [+] Stable - go ahead and release
2. [-]  Broken - do not release (please explain why)



 Awanthika Senarath
 Senior Software Engineer, WSO2 Inc.
 Mobile: +94717681791



>>>
>>>
>>> --
>>>
>>> *Jasintha Dasanayake**Associate Technical Lead*
>>>
>>> *WSO2 Inc. | http://wso2.com lean . enterprise .
>>> middleware*
>>>
>>>
>>> *mobile :- 0711-368-118 <0711-368-118>*
>>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Akila Ravihansa Perera]

Hi Imesh,

Sorry for the confusion. In deploy script we are using DCOS CLI to get the
status of the service. We had a Python script earlier to create a TCP
socket to check whether service is active. But that is not a reliable
solution since network might not be reachable from where the deploy script
is being executed and also creating a TCP socket is not equivalent to
creating a HTTP connection and checking the HTTP status code which is
already handled by Mesos. So we offload that work to Mesos and let the
users define any type of health check they think is suitable.

Thanks.

On Wed, Jul 20, 2016 at 4:57 PM, Imesh Gunaratne  wrote:

>
>
> On Wed, Jul 20, 2016 at 1:19 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Imesh,
>>
>> mysqladmin client need not be installed on host machine since Mesos will
>> run this command as a "docker run" command which will be executed inside
>> the container. MySQL official image contains mysqladmin tool so this is not
>> a problem.
>>
>
> ​I thought this was regarding the check we need to make before deploying
> the WSO2 server containers to wait until MySQL containers become ready.
> ​
>
> ​Thanks​
>
>
>> Thanks.
>>
>> On Wed, Jul 20, 2016 at 12:46 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Akila,
>>>
>>> On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 Hi Imesh,

 I've switched to command based health check for MySQL services. It will
 basically run "mysqladmin -u $MYSQL_USER -p$MYSQL_PASSWORD status". This
 will ensure MySQL service is ready to serve SQL requests.

>>>
>>> ​Wouldn't this make it mandatory to have mysqladmin client installed in
>>> the host machine where the deployment script is run?
>>>
>>> Thanks​
>>>
>>>

 Thanks.

 On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne 
 wrote:

>
>
> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi,
>>
>> Yes, myself and Pubudu also faced this issue, lets fix it properly.
>>
>> On Wed, Jul 6, 2016 at 10:57 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Akila,
>>>
>>> Yes we faced several issues related to this. Apart from what you
>>> have mentioned, we encountered mysql app name is not getting resolved. 
>>> This
>>> could be the delay in updating Mesos DNS. For these issues we looking 
>>> into
>>> following options.
>>>
>>> *Option 1:*
>>> Use a sleep before deploying a carbon server. Not the best option.
>>>
>>> *Option 2:*
>>> Depend on the health status results.
>>>
>>> Currently, we do use a health check for mysql apps. Using dcos CLI
>>> we can check the status of the app whether the app is alive or not. But
>>> this cannot guarantee the DBs are ready to serve requests and Mesos DNS 
>>> is
>>> updated.
>>>
>>
>
>> What if we query the Mesos DNS in addition to port checking to see if
>> its updated? AFAIR what we are seeing is an 
>> java.net.UnknownHostException,
>> related to the DB hostname.
>>
>
> ​May be we can wait for MySQL sockets as we do for Carbon server
> transports.
>
> 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
>
>


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


-- 
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] [Mesos artifacts] Deploy script is failing to check database service

[Imesh Gunaratne]

On Wed, Jul 20, 2016 at 5:36 PM, Akila Ravihansa Perera 
wrote:

> Hi Imesh,
>
> Sorry for the confusion. In deploy script we are using DCOS CLI to get the
> status of the service. We had a Python script earlier to create a TCP
> socket to check whether service is active. But that is not a reliable
> solution since network might not be reachable from where the deploy script
> is being executed and also creating a TCP socket is not equivalent to
> creating a HTTP connection and checking the HTTP status code which is
> already handled by Mesos. So we offload that work to Mesos and let the
> users define any type of health check they think is suitable.
>

​Great! Thanks for the explanation Akila!​


>
> Thanks.
>
> On Wed, Jul 20, 2016 at 4:57 PM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Wed, Jul 20, 2016 at 1:19 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Imesh,
>>>
>>> mysqladmin client need not be installed on host machine since Mesos will
>>> run this command as a "docker run" command which will be executed inside
>>> the container. MySQL official image contains mysqladmin tool so this is not
>>> a problem.
>>>
>>
>> ​I thought this was regarding the check we need to make before deploying
>> the WSO2 server containers to wait until MySQL containers become ready.
>> ​
>>
>> ​Thanks​
>>
>>
>>> Thanks.
>>>
>>> On Wed, Jul 20, 2016 at 12:46 PM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Akila,

 On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> Hi Imesh,
>
> I've switched to command based health check for MySQL services. It
> will basically run "mysqladmin -u $MYSQL_USER -p$MYSQL_PASSWORD status".
> This will ensure MySQL service is ready to serve SQL requests.
>

 ​Wouldn't this make it mandatory to have mysqladmin client installed in
 the host machine where the deployment script is run?

 Thanks​


>
> Thanks.
>
> On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne 
> wrote:
>
>>
>>
>> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi,
>>>
>>> Yes, myself and Pubudu also faced this issue, lets fix it properly.
>>>
>>> On Wed, Jul 6, 2016 at 10:57 PM, Pubudu Gunatilaka >> > wrote:
>>>
 Hi Akila,

 Yes we faced several issues related to this. Apart from what you
 have mentioned, we encountered mysql app name is not getting resolved. 
 This
 could be the delay in updating Mesos DNS. For these issues we looking 
 into
 following options.

 *Option 1:*
 Use a sleep before deploying a carbon server. Not the best option.

 *Option 2:*
 Depend on the health status results.

 Currently, we do use a health check for mysql apps. Using dcos CLI
 we can check the status of the app whether the app is alive or not. But
 this cannot guarantee the DBs are ready to serve requests and Mesos 
 DNS is
 updated.

>>>
>>
>>> What if we query the Mesos DNS in addition to port checking to see
>>> if its updated? AFAIR what we are seeing is an
>>> java.net.UnknownHostException, related to the DB hostname.
>>>
>>
>> ​May be we can wait for MySQL sockets as we do for Carbon server
>> transports.
>>
>> 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
>>
>>
>
>
> --
> 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


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

[Dev] [APIM 2.0] Provisioning Out-of-Band OAuth Clients

[Kavitha Subramaniyam]

Hi apim team,

I tried the scenario for provisioning OAuth client in API manger by
following the doc [1], and could not complete the scenario because the
'Provider Key' was not found in API Store.

Steps done: in stand alone pack
- Registered a Oauth application (SP) in apim management console as admin
login
- Set "mapExistingAuthApps" : true at ..store/site/conf/site.json
- Login to Store as admin
- Checked to register above client; but found no Provider Key; Suspects
this could be a document issue..

Appreciate if you can let me know the way how this scenario can be achieved?

[1]
https://docs.wso2.com/display/AM200/Provisioning+Out-of-Band+OAuth+Clients


Thanks,

-- 
Kavitha.S
*Software Engineer -QA*
Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
kavi...@wso2.com 
___
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,

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. Otherwise we would not
>> be able to autoscale a server cluster dynamically.
>> ​
>>
>>
>

Re: [Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Imesh Gunaratne]

On Wed, Jul 20, 2016 at 7:32 PM, Rasanjaya Subasinghe 
wrote:

> Hi all,
>
> Beneath are some behaviors I was noticed during the LW Dev configuration.
>
> 1. Mysql connector needs to copy each and every product.  Anyhow, in cloud
> puppet modules we used to place it in wso2base module.
>
> ​Yes, we need to fix this. @Rasanjaya: Would you mind contributing?
​


> 2. A Pupppetmaster host entry gets deleted in /etc/hosts file once we run
> the puppet in agent nodes. [Added this IP into hiera common.yaml, due to
> resolve the master's IP]
>
> ​@Akila: Any thoughts on this?
​


> 3. Each and every time the config file change [Ex: axis2.xml] product gets
> deleted and start with the fresh configuration.
>

​Agree! It should not start from the beginning for a configuration change.

>
> 4. In clustering, Is there any reason to use the  sub_domain
> [Ex:sub_domain: worker]? In cloud we are not using this anymore.  This used
> to identify the manager, worker separation in previous Stratos and now this
> will treat through the URL and LB [AWS LB or Nginx]. So then we can specify
> this configuration in default.yaml in the relevant product.  No need to
> reiterate again and again.
>
> A good point! Will remove the sub-domain property from Hiera and template
files.

Thanks
​

> Thanks
>
> On Mon, Jul 18, 2016 at 7:35 PM, Imesh Gunaratne  wrote:
>
>> On Mon, Jul 18, 2016 at 5:44 PM, Manula Waidyanatha 
>>  wrote:
>>
>>
>>> What is the reason for checking `@clustering['aws']` in every line in
>>> aws.erb[1] file?
>>> It doesn't do any harm, but there is no point in checking it since
>>> aws.erb file is included to axis2.xml.erb only in the aws clustering
>>> mode.
>>
>>
>> ​Thanks for pointing Manula! It was my mistake!​
>>
>> On Mon, Jul 18, 2016 at 6:05 PM, Lakmal Warusawithana 
>> wrote:
>>
>>> @Imesh, Shall we remove unnecessary if conditions in aws.erb.
>>>
>>> ​Yes Lakmal! I fixed it and pushed changes. Please see the latest
>> template and sample Hiera data config [1], [2]:
>>
>> [1]
>> https://github.com/wso2/puppet-modules/blob/master/modules/wso2base/templates/clustering/aws.erb
>> [2]
>> https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2bps/3.5.1/default/manager.yaml#L36
>>
>> Thanks
>> ​
>>
>>
>>> thanks
>>>
>>> On Mon, Jul 18, 2016 at 2:39 PM, Imesh Gunaratne  wrote:
>>>
 I just added AWS membership scheme template and a sample configuration
 to BPS 3.5.1 [1].
 @Rasanjaya: Would you mind trying this out?

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

 Thanks

 On Mon, Jul 18, 2016 at 2:23 PM, Imesh Gunaratne 
 wrote:

> Hi Devs,
>
> It looks like we have missed $subject:
>
> https://github.com/wso2/puppet-modules/tree/master/modules/wso2base/templates/clustering
>
> https://docs.wso2.com/display/CLUSTER44x/Setting+up+a+Cluster+in+AWS+Mode
>
> 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
>
>


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


>>>
>>>
>>> --
>>> Lakmal Warusawithana
>>> Director - Cloud Architecture; WSO2 Inc.
>>> Mobile : +94714289692
>>> Blog : http://lakmalsview.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
>>
>>
>
>
> --
> --
> Rasanjaya Subasinghe
> Software Engineer, Dev/Ops , WSO2 inc(Sri Lanka)
> +94772250358
> rasanj...@wso2.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

[Dev] Issues with 'Getting Started' (Axis2 services)

[Steve Simmons]

Hi, I'm new to this forum and new to WS02.  I'm trying to set up a proof 
of concept for WS02 and I've started walking through the Tutorial.


Ashamed to say, I've fallen at the first hurdle.  I have WS02 installed, 
the Eclipse Dev environment and the management system installed and 
these all seem to be working as expected.  I'm working through the 
'sending a simple message through ESB' example and I have built the 
SimpleStockQuoteService.  when I run 'axis2Server.bat', I get some 
messages (cut'n'pasted below).  Don't understand the whole text but 
likewise I can't see any obvious issues.  Try connecting to 
localhost:9000\services\  and I get a browser screen saying localhost 
has refused the connection.


Any troubleshooting suggestions very welcome.

Steve


"Starting Sample Axis2 Server ..."
Using AXIS2_HOME: C:\Dev\WS02\wso2esb-4.9.0\samples\axis2Server
Using JAVA_HOME:   C:\Program Files (x86)\Java\jdk1.8.0_92
Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=256m; 
support was removed in 8.0

Usage: java [-options] class [args...]
   (to execute a class)
   or  java [-options] -jar jarfile [args...]
   (to execute a jar file)
where options include:
-d32  use a 32-bit data model if available
-d64  use a 64-bit data model if available
-client   to select the "client" VM
-server   to select the "server" VM
  The default VM is client.

-cp 
-classpath 
  A ; separated list of directories, JAR archives,
  and ZIP archives to search for class files.
-D=
  set a system property
-verbose:[class|gc|jni]
  enable verbose output
-version  print product version and exit
-version:
  Warning: this feature is deprecated and will be removed
  in a future release.
  require the specified version to run
-showversion  print product version and continue
-jre-restrict-search | -no-jre-restrict-search
  Warning: this feature is deprecated and will be removed
  in a future release.
  include/exclude user private JREs in the version search
-? -help  print this help message
-Xprint help on non-standard options
-ea[:...|:]
-enableassertions[:...|:]
  enable assertions with specified granularity
-da[:...|:]
-disableassertions[:...|:]
  disable assertions with specified granularity
-esa | -enablesystemassertions
  enable system assertions
-dsa | -disablesystemassertions
  disable system assertions
-agentlib:[=]
  load native agent library , e.g. -agentlib:hprof
  see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:[=]
  load native agent library by full pathname
-javaagent:[=]
  load Java programming language agent, see 
java.lang.instrument

-splash:
  show splash screen with specified image
See 
http://www.oracle.com/technetwork/java/javase/documentation/index.html 
for more details.

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

Re: [Dev] Issues with 'Getting Started' (Axis2 services)

[Jorge]

Please check this:
http://stackoverflow.com/questions/32866263/axis2server-packed-with-esb-4-9-0-doesnt-start-while-it-works-fine-4-8-0/32878921#32878921

Regards,
 Jorge.

2016-07-20 12:41 GMT-04:00 Steve Simmons :

> Hi, I'm new to this forum and new to WS02.  I'm trying to set up a proof
> of concept for WS02 and I've started walking through the Tutorial.
>
> Ashamed to say, I've fallen at the first hurdle.  I have WS02 installed,
> the Eclipse Dev environment and the management system installed and these
> all seem to be working as expected.  I'm working through the 'sending a
> simple message through ESB' example and I have built the
> SimpleStockQuoteService.  when I run 'axis2Server.bat', I get some messages
> (cut'n'pasted below).  Don't understand the whole text but likewise I can't
> see any obvious issues.  Try connecting to localhost:9000\services\  and I
> get a browser screen saying localhost has refused the connection.
>
> Any troubleshooting suggestions very welcome.
>
> Steve
>
>
> "Starting Sample Axis2 Server ..."
> Using AXIS2_HOME: C:\Dev\WS02\wso2esb-4.9.0\samples\axis2Server
> Using JAVA_HOME:   C:\Program Files (x86)\Java\jdk1.8.0_92
> Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Usage: java [-options] class [args...]
>(to execute a class)
>or  java [-options] -jar jarfile [args...]
>(to execute a jar file)
> where options include:
> -d32  use a 32-bit data model if available
> -d64  use a 64-bit data model if available
> -client   to select the "client" VM
> -server   to select the "server" VM
>   The default VM is client.
>
> -cp 
> -classpath 
>   A ; separated list of directories, JAR archives,
>   and ZIP archives to search for class files.
> -D=
>   set a system property
> -verbose:[class|gc|jni]
>   enable verbose output
> -version  print product version and exit
> -version:
>   Warning: this feature is deprecated and will be removed
>   in a future release.
>   require the specified version to run
> -showversion  print product version and continue
> -jre-restrict-search | -no-jre-restrict-search
>   Warning: this feature is deprecated and will be removed
>   in a future release.
>   include/exclude user private JREs in the version search
> -? -help  print this help message
> -Xprint help on non-standard options
> -ea[:...|:]
> -enableassertions[:...|:]
>   enable assertions with specified granularity
> -da[:...|:]
> -disableassertions[:...|:]
>   disable assertions with specified granularity
> -esa | -enablesystemassertions
>   enable system assertions
> -dsa | -disablesystemassertions
>   disable system assertions
> -agentlib:[=]
>   load native agent library , e.g. -agentlib:hprof
>   see also, -agentlib:jdwp=help and -agentlib:hprof=help
> -agentpath:[=]
>   load native agent library by full pathname
> -javaagent:[=]
>   load Java programming language agent, see
> java.lang.instrument
> -splash:
>   show splash screen with specified image
> See http://www.oracle.com/technetwork/java/javase/documentation/index.html
> for more details.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please vote for WSO2 Developer Studio Kernel 4.2.0 RC2

[Kavith Lokuhewage]

Hello Devs,

Please vote for the second release candidate for WSO2 Developer Studio
Kernel 4.2.0.

P2 repository and RCP products of WSO2 developer Studio kernel 4.2.0 RC2 is
available here

.

Source and Tag Location to be voted upon is available here

.

With the 4.2.0 release, WSO2 Developer Studio kernel also provides an
Eclipse RCP based distribution - further reducing the size.

We have also introduced a web based dashboard for Developer Studio to
enhance user experience.

Also the XULRunner is embedded to maintain an unbroken user experience in
WSO2 Developer Studio on windows platform - when using web technologies.

We have also fixed a few bugs.

 - https://wso2.org/jira/browse/DEVTOOLESB-441
 - https://wso2.org/jira/browse/TOOLS-3423

For the second release candidate, we have identified and fixed a major
blocker for automatic updater in kernel.

- https://wso2.org/jira/browse/TOOLS-3436

Vote will be open for 72 hours or as needed. Please vote as follows.

   1. [+] Stable - go ahead and release
   2. [-]  Broken - do not release (please explain why)


Thanks,

*Kavith Lokuhewage*
Senior Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +94779145123
Linkedin   Twitter

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

[Dev] WSO2 Committers += Rasika Perera

[Geeth Munasinghe]

Hi all,

It is my pleasure to welcome Rasika Perera as WSO2 Committer. He has been a
valuable contributor to EMM/IoT team and to various other projects. In
recognition of his contributions and commitment towards the
responsibilities assigned to him, he has been voted as WSO2 committer.

@Rasika, Welcome aboard and keep up the good work.

Thanks
Geeth

-- 

*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226


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

Re: [Dev] Adding SVN dockerfiles to wso2/dockerfiles

[Akila Ravihansa Perera]

Hi Pubudu,

Why are we using wso2/wso2base:latest as the base image here? We have to
run apt-get update and install subversion anyway right?

IMHO, we need to add artifacts for deploying this on Mesos, Kubernetes etc.
and integrate this with WSO2 DepSync. Shall we work on delivering the
complete package as well?

Thanks.

On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka 
wrote:

> Hi,
>
> At the moment there is no any official docker image for SVN[1]. I have
> created the dockerfile and other relevant artifacts for SVN [2]. This is to
> maintain a separate a docker image for SVN for deployment synchronization.
> For dep sync in container deployments, there is a mail thread with subject
> in [3].
>
> Basically rsync is an option for dep sync. But when it compares to SVN,
> the following are the main advantages.
>
> - Can handle several manager nodes
> - SVN Container can accommodate multiple products
> - We can mount a single volume for SVN server only
>
> Please share your thoughts.
>
> [1] - https://hub.docker.com/
> [2] - https://github.com/wso2/dockerfiles/pull/57
> [3] - [Architecture] Dep sync strategies for Carbon 4 products in
> Kubernetes
>
> Thank you!
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


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

[Dev] [VOTE] WSO2 App Manager 1.2.0 RC3

[Lahiru Cooray]

Hi Devs,

This is the 3rd Release Candidate of the WSO2 App Manager 1.2.0

Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
Refer to github readme for guides.

The distribution is available to download at [1]

[1] :
https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC3/wso2appm-1.2.0.zip

Fixed Issue in [2], known issues [3], tag to be vote upon [4]

[2] : https://wso2.org/jira/issues/?filter=13104
[3] : https://wso2.org/jira/issues/?filter=13148
[4] : https://github.com/wso2/product-app-manager/releases/tag/v1.2.0-RC3

Please vote as follows.
[+] Stable - go ahead and release
[-]  Broken - do not release (please explain why)

Thanks,
App Manager Team

-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [GSoC Dockerfiles] Issues with setting up Kubernetes using Vagrant

[Abhishek Tiwari]

Hi Imesh,

Thanks a lot for the instructions, I will try the setup on OSX itself once
I am done with the smoke tests.

- Abhishek

On Wednesday, July 20, 2016, Imesh Gunaratne  wrote:

> Hi Abhishek,
>
> On Wed, Jul 20, 2016 at 9:49 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com
> > wrote:
>
>> Hi Mentors,
>>
>> I have been working on setting up Kubernetes cluster using vagrant and
>> docker using [1]. I ran into multiple issues (coreos download taking hours,
>> nfsd not being setup etc), however, those got resolved.
>>
>
> ​Can you please execute following to ssh into the master node and check
> the system log?
>
> vagrant ssh master
> journalctl -f​
>
>
>>
>> Now, when I launch the setup using run.sh, I get this error [2]. I tried
>> wiping out everything (vagrant destroy -f) and restart the whole process
>> again, I get the same issue.
>>
>> One thing to note is, my host os is Mac and I use VirtualBox for
>> development, so essentially I have virtualbox setup inside virtualbox. I
>> don't think it should matter, but would like to get other people's opinion
>> on this.
>>
>
> ​This works on OSX.​
>
>
>>
>> While this issue gets resolved, I am planning to complete another
>> milestone to add smoke tests for ESB and MB. I feel like, I should complete
>> the test workflow for default platform before moving to Kubernetes, since
>> the latter involves a lot of new technologies, more moving parts and other
>> unknowns. I do plan to address Kubernetes testing, but would like to do
>> that once default platform test workflow is complete. Thoughts?
>>
>
> ​+1
>
> If [1] does not work for you, please try following:
> http://kubernetes.io/docs/getting-started-guides/vagrant/
>
> Thanks​
>
>
>>
>> Thanks,
>> Abhishek
>>
>> [1]. https://github.com/imesh/kubernetes-vagrant-setup
>> [2].
>> master: Waiting for machine to boot. This may take a few minutes...
>> master: SSH address: 127.0.0.1:
>> master: SSH username: core
>> master: SSH auth method: private key
>>
>> Timed out while waiting for the machine to boot. This means that
>> Vagrant was unable to communicate with the guest machine within
>> the configured ("config.vm.boot_timeout" value) time period.
>>
>>
>>
>
>
> --
> *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] [Puppet Modules] AWS Membership Scheme Configuration Support

[Akila Ravihansa Perera]

Hi,

1. Mysql connector needs to copy each and every product.  Anyhow, in cloud
>> puppet modules we used to place it in wso2base module.
>>
>> ​Yes, we need to fix this. @Rasanjaya: Would you mind contributing?
>

Puppet file bucket integration and AWS S3 integration are in the road map.
We couldn't look into this due to other priorities.


> ​
>
>
>> 2. A Pupppetmaster host entry gets deleted in /etc/hosts file once we run
>> the puppet in agent nodes. [Added this IP into hiera common.yaml, due to
>> resolve the master's IP]
>>
>> ​@Akila: Any thoughts on this?
>

Yes, this was a known issue. I've fixed it in [1]. This won't affect Docker
scenario since we are adding host mappings only in VM scenario. I've used
"host" Puppet resource type [2] so that it won't be platform dependent.
This can be used with Max, Win etc.



> ​
>
>
>> 3. Each and every time the config file change [Ex: axis2.xml] product
>> gets deleted and start with the fresh configuration.
>>
>
> ​Agree! It should not start from the beginning for a configuration change.
>

Yes, this needs to be fixed. I'll follow up on this as well.



>
>> 4. In clustering, Is there any reason to use the  sub_domain
>> [Ex:sub_domain: worker]? In cloud we are not using this anymore.  This used
>> to identify the manager, worker separation in previous Stratos and now this
>> will treat through the URL and LB [AWS LB or Nginx]. So then we can specify
>> this configuration in default.yaml in the relevant product.  No need to
>> reiterate again and again.
>>
>> A good point! Will remove the sub-domain property from Hiera and template
> files.
>

+1 for removing this from template. But are we sure this property is not
used in any scenario?

[1]
https://github.com/wso2/puppet-modules/commit/25821de9d7fd37b351a305fc8777a33bbe49e13e
[2] https://docs.puppet.com/puppet/latest/reference/types/host.html

-- 
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] [Puppet Modules] AWS Membership Scheme Configuration Support

[Imesh Gunaratne]

On Wed, Jul 20, 2016 at 11:12 PM, Akila Ravihansa Perera  wrote:
>
>
>
>>
>>> 4. In clustering, Is there any reason to use the  sub_domain
>>> [Ex:sub_domain: worker]? In cloud we are not using this anymore.  This used
>>> to identify the manager, worker separation in previous Stratos and now this
>>> will treat through the URL and LB [AWS LB or Nginx]. So then we can specify
>>> this configuration in default.yaml in the relevant product.  No need to
>>> reiterate again and again.
>>>
>>> A good point! Will remove the sub-domain property from Hiera and
>> template files.
>>
>
> +1 for removing this from template. But are we sure this property is not
> used in any scenario?
>

​Yes, this was cross checked with Azeez.

Thanks​


>
> [1]
> https://github.com/wso2/puppet-modules/commit/25821de9d7fd37b351a305fc8777a33bbe49e13e
> [2] https://docs.puppet.com/puppet/latest/reference/types/host.html
>
> --
> 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] [ESB] Unable to start ESB 5.0.0 Beta2 on top of IBM JDK

[Rajith Roshan]

Hi Pubudu,

On Wed, Jul 20, 2016 at 11:38 AM, Pubudu Priyashan  wrote:

> Hi Rajith and Ayoma,
>
> *@Rajith:* I have checked this [1] with ESB Beta2 pack and it works with
> both IBM 7 and 8 JDKs once you set the property as you have mentioned. I
> have added this Doc JIRA [2] to include this information in official docs.
> Is there a way that we can automatically pick the JDK whether it's IBM or
> Oracle without setting this particular property? If so, one less step for
> the user. So we may need to look into it if that's possible?
>
ASFAIK this file contains properties that used to enforce csrf guard. I
think changing this to automatically pick the jdk is out of our control. We
need to define it in the properties file.
*@Ayoma* could you please clarify on this.

>
> *@Ayoma:* Just looped you in just in case those two issues might be
> related. As it turns out these aren't.
>
> [1] https://wso2.org/jira/browse/ESBJAVA-4772
> [2] https://wso2.org/jira/browse/DOCUMENTATION-3648
>
> Cheers,
> Pubudu.
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> Linkedin: https://uk.linkedin.com/in/pubududp
> Medium: https://medium.com/@pubududp
>
>
> On Tue, Jul 19, 2016 at 11:16 PM, Ayoma Wijethunga  wrote:
>
>> Hi Pubudu,
>>
>> I hope you were checking with me about "ESBJAVA-4740" [1]. Was
>> "ESBJAVA-4772" mentioned by mistake?  Rajith is correct about
>> "ESBJAVA-4772", although "ESBJAVA-4740" has nothing to do with CSRFGuard.
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-4740
>>
>> Regards,
>> Ayoma
>>
>> On Tue, Jul 19, 2016 at 10:49 PM, Rajith Roshan  wrote:
>>
>>> Hi Pubudu,
>>>
>>> Can you try setting the following property[1] in
>>> "Owasp.CsrfGuard.Carbon.properties" file
>>> (SERVER_HOME/repository/conf/security) which is default set to [2]. We
>>> found same issue with G-Reg and overcame it by setting this property.
>>>
>>> [1] - org.owasp.csrfguard.PRNG.Provider=IBMJCE
>>> [2] - org.owasp.csrfguard.PRNG.Provider=SUN
>>>
>>> Thanks!
>>> Rajith
>>>
>>> On Mon, Jul 18, 2016 at 12:51 PM, Pubudu Priyashan 
>>> wrote:
>>>
 Hi Senduran,

 We are currently facing the issue logged at [1] when starting the ESB
 pack with IBM JDK. Can we please take a look and get this fixed with the
 next release? This blocks us from testing the release on IBM JDK. Do let me
 know if you require any further information. Thanks!

 [1] https://wso2.org/jira/browse/ESBJAVA-4772


 Cheers,
 Pubudu D.P
 Senior Software Engineer - QA Team | WSO2 inc.
 Mobile : +94775464547

 Linkedin: https://uk.linkedin.com/in/pubududp
 Medium: https://medium.com/@pubududp


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


>>>
>>>
>>> --
>>> Rajith Roshan
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ayoma Wijethunga
>> Software Engineer
>> Platform Security Team
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> Mobile : +94 (0) 719428123 <+94+(0)+719428123>
>> Blog : http://www.ayomaonline.com
>> LinkedIn: https://www.linkedin.com/in/ayoma
>>
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Abimaran Kugathasan]

*WSO2 API Manager 2.0.0-RC3 Released*

This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0

Source & binary distribution files of API Manager 2.0.0-RC3 :

 Runtime :
https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
 Analytics :
https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3

Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
Refer to github readme for guides.

Please vote as follows.
[+] Stable - go ahead and release
[-]  Broken - do not release (please explain why)

-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer

Email : abima...@wso2.com
Mobile : +94 773922820


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

Re: [Dev] [Architecture] [VOTE] WSO2 App Manager 1.2.0 RC3

[Lakshani Gamage]

Hi,

Tested following Scenarios

   - Web App/Mobile App life cycle change
   - Web App/ Mobile app update
   - Business Owner functionalities.
   - App documentation. (Publisher and Store)
   - Search in Publisher
   - Sorting and Searching in Store.
   - Tags
   - App invocation in super tenant and tenant domains
   - Anonymous access
   - User comments/rating

Works fine. I didn't encounter any issues.

[+] Stable - go ahead and release

Thanks,

Lakshani.

On Wed, Jul 20, 2016 at 11:09 PM, Lahiru Cooray  wrote:

> Hi Devs,
>
> This is the 3rd Release Candidate of the WSO2 App Manager 1.2.0
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
> Refer to github readme for guides.
>
> The distribution is available to download at [1]
>
> [1] :
> https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC3/wso2appm-1.2.0.zip
>
> Fixed Issue in [2], known issues [3], tag to be vote upon [4]
>
> [2] : https://wso2.org/jira/issues/?filter=13104
> [3] : https://wso2.org/jira/issues/?filter=13148
> [4] : https://github.com/wso2/product-app-manager/releases/tag/v1.2.0-RC3
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> Thanks,
> App Manager Team
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Lakshani Gamage

*Software Engineer, WSO2*

*Mobile : +94 71 5478184 <%2B94%20%280%29%20773%20451194>*
*Blog : http://lakshanigamage.blogspot.com/
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] WSO2 App Manager 1.2.0 RC3

[Lahiru Cooray]

Tested following Scenarios:

   - SSO and SLO
   - App visibility restrictions
   - Resource level role based restriction
   - Favourite apps/page functionality
   - Sorting and searching


+1
Stable - Go ahead and release.


On Wed, Jul 20, 2016 at 11:09 PM, Lahiru Cooray  wrote:

> Hi Devs,
>
> This is the 3rd Release Candidate of the WSO2 App Manager 1.2.0
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
> Refer to github readme for guides.
>
> The distribution is available to download at [1]
>
> [1] :
> https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC3/wso2appm-1.2.0.zip
>
> Fixed Issue in [2], known issues [3], tag to be vote upon [4]
>
> [2] : https://wso2.org/jira/issues/?filter=13104
> [3] : https://wso2.org/jira/issues/?filter=13148
> [4] : https://github.com/wso2/product-app-manager/releases/tag/v1.2.0-RC3
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> Thanks,
> App Manager Team
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>



-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [BPS] Getting meta-data of form elements

[Manuranga Perera]

Can you please point me to the REST API, using which, I can get the form
element information (such as type="string") of a user task.

-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] WSO2 App Manager 1.2.0 RC3

[Dinusha Senanayaka]

Tested with following scenarios and found no issue.

- Throttling
- JWT generation for different apps
- Recent apps loading
- Deleting apps in multiple states

+1
Stable - Go ahead and release.

Regards,
Dinusha.

On Thu, Jul 21, 2016 at 1:01 AM, Lahiru Cooray  wrote:

> Tested following Scenarios:
>
>- SSO and SLO
>- App visibility restrictions
>- Resource level role based restriction
>- Favourite apps/page functionality
>- Sorting and searching
>
>
> +1
> Stable - Go ahead and release.
>
>
> On Wed, Jul 20, 2016 at 11:09 PM, Lahiru Cooray  wrote:
>
>> Hi Devs,
>>
>> This is the 3rd Release Candidate of the WSO2 App Manager 1.2.0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> The distribution is available to download at [1]
>>
>> [1] :
>> https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC3/wso2appm-1.2.0.zip
>>
>> Fixed Issue in [2], known issues [3], tag to be vote upon [4]
>>
>> [2] : https://wso2.org/jira/issues/?filter=13104
>> [3] : https://wso2.org/jira/issues/?filter=13148
>> [4] : https://github.com/wso2/product-app-manager/releases/tag/v1.2.0-RC3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> Thanks,
>> App Manager Team
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>
>
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Akila Ravihansa Perera]

Hi Abimaran,

Shouldn't we include a list of bugs fixed and features added in the release
vote? Ideally this should be a JIRA filter link.

Thanks.

On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan 
wrote:

>
> *WSO2 API Manager 2.0.0-RC3 Released*
>
> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC3 :
>
>  Runtime :
> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>  Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> 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

Re: [Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Abimaran Kugathasan]

It's there in the github release page of both API Manager Runtime and
Analytics,

On Thu, Jul 21, 2016 at 7:12 AM, Akila Ravihansa Perera 
wrote:

> Hi Abimaran,
>
> Shouldn't we include a list of bugs fixed and features added in the
> release vote? Ideally this should be a JIRA filter link.
>
> Thanks.
>
> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan 
> wrote:
>
>>
>> *WSO2 API Manager 2.0.0-RC3 Released*
>>
>> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC3 :
>>
>>  Runtime :
>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>>  Analytics :
>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> 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
>



-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer

Email : abima...@wso2.com
Mobile : +94 773922820


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

Re: [Dev] WSO2 Committers += Rasika Perera

[Geesara Prathap]

Congratulations Rasika!!! :)

On Wed, Jul 20, 2016 at 10:33 PM, SajithAR Ariyarathna 
wrote:

> Hi Maheshika,
>
> Please add RasikaP[1] to UUF team[2] and grant write access to repos.
>
> [1] https://github.com/rasika
> [2] https://github.com/orgs/wso2/teams/uuf
>
> Thanks.
>
> On Wed, Jul 20, 2016 at 10:20 PM, Geeth Munasinghe  wrote:
>
>> Hi all,
>>
>> It is my pleasure to welcome Rasika Perera as WSO2 Committer. He has been
>> a valuable contributor to EMM/IoT team and to various other projects. In
>> recognition of his contributions and commitment towards the
>> responsibilities assigned to him, he has been voted as WSO2 committer.
>>
>> @Rasika, Welcome aboard and keep up the good work.
>>
>> Thanks
>> Geeth
>>
>> --
>>
>> *G. K. S. Munasinghe*
>> *Senior Software Engineer,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: ge...@wso2.com
>> phone:(+94) 777911226
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 Engineering Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to engineering-group+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>



-- 
Geesara Prathap Kulathunga
Software Engineer
WSO2 Inc; http://wso2.com
Mobile : +940772684174
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Nuwan Dias]

Tested Identity Server as Key Manager using IS 5.2.0 Beta2. Tested the
basic scenarios for tenant and super tenant users. No issues found.

[x] - Stable - go ahead and release

Thanks,
NuwanD.


On Thu, Jul 21, 2016 at 7:15 AM, Abimaran Kugathasan 
wrote:

> It's there in the github release page of both API Manager Runtime and
> Analytics,
>
> On Thu, Jul 21, 2016 at 7:12 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Abimaran,
>>
>> Shouldn't we include a list of bugs fixed and features added in the
>> release vote? Ideally this should be a JIRA filter link.
>>
>> Thanks.
>>
>> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan 
>> wrote:
>>
>>>
>>> *WSO2 API Manager 2.0.0-RC3 Released*
>>>
>>> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>>>
>>> Source & binary distribution files of API Manager 2.0.0-RC3 :
>>>
>>>  Runtime :
>>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>>>  Analytics :
>>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> 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
>>
>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS] Getting meta-data of form elements

[Amal Gunatilake]

Hi Manu,

You can get the form data by calling following REST API.

*https://localhost:9444/bpmn/form/form-data/?taskId=${tid}
*


Replace *${tid}* with the task id which you need to retrieve the form-data.
An example usage can be found in [1]. Further reference [2].

[1]
https://github.com/wso2/carbon-business-process/blob/master/components/bpmn/bpmn-explorer-web/src/web/model/taskModel.jag#L134
[2] http://www.activiti.org/userguide/#_get_form_data

Best regards,
Amal.

On Thu, Jul 21, 2016 at 2:01 AM, Manuranga Perera  wrote:

> Can you please point me to the REST API, using which, I can get the form
> element information (such as type="string") of a user task.
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



-- 
*Amal Gunatilake*
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

mobile: (+94) 773561195
blog: amalg-blogs.blogspot.com; twitter: @daag123
linkedIn: https://www.linkedin.com/in/amalgunatilake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How to get the current server-url from a custom Task

[Ayesha Dissanayaka]

Hi,

What is the best way to get the ESB server-url from a custom Task
implementation in ESB?

[1] https://docs.wso2.com/display/ESB480/Writing+Tasks

Thanks!
-Ayesha

-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while starting server as a windows service

[Nadeesha Gamage]

Hi Maduranga,
A prospective customer encountered this issue yesterday and your solution
was able to solve the issue. Thanks for sharing the fix. It would best if
you can blog about this so that its easier to find.

Thank you,
Nadeesha

On Mon, Jun 27, 2016 at 4:03 AM, Maduranga Siriwardena 
wrote:

> Hi all,
>
> While I was trying to start Identity Server with yajws, I could notice an
> encoding error. See the error log bellow.
>
> *Caused by: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber:
> 71; Invalid byte 1 of 1-byte UTF-8 sequence.*
> * at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)*
> * at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)*
> * at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)*
> * at
> org.wso2.carbon.utils.CarbonUtils.replaceSystemVariablesInXml(CarbonUtils.java:1080)*
> * ... 48 more*
>
>
> I could start the server on the same server machine in the normal way,
> without any error. And I could start it as a service in my local machine
> without any error.
>
> I check wso2server.bat file and it had a jvm parameter set related to
> encoding.
>
> *-Dfile.encoding=UTF8*
>
>
> So I added it to wrapper.conf file as bellow and I couldn't notice the
> error any more.
>
> *wrapper.java.additional.26 = -Dfile.encoding=UTF8*
>
>
> May be we need to add this to the default wrapper.conf file or mention
> this in a documentation.
>
> Thanks,
> Maduranga.
>
> --
> Maduranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
> mobile: +94718990591
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nadeesha Gamage
Associate Technical Lead - Solutions Engineering
T : +94 77 394 5706
B : https://nadeesha678.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding SVN dockerfiles to wso2/dockerfiles

[Pubudu Gunatilaka]

Hi Akila,

I used the base image to get rid of running apt-get update again for svn
docker image. Apt-get update takes time and also sometimes it fails as
well.

I have already created Mesos artifacts for svn in [1] and will push those
changes to Mesos artifact repo. Will work on the Kubernetes artifacts.

[1] - https://github.com/pubudu538/mesos-artifacts/tree/master/common/svn

Thank you!

On Wed, Jul 20, 2016 at 10:19 PM, Akila Ravihansa Perera  wrote:

> Hi Pubudu,
>
> Why are we using wso2/wso2base:latest as the base image here? We have to
> run apt-get update and install subversion anyway right?
>
> IMHO, we need to add artifacts for deploying this on Mesos, Kubernetes
> etc. and integrate this with WSO2 DepSync. Shall we work on delivering the
> complete package as well?
>
> Thanks.
>
> On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi,
>>
>> At the moment there is no any official docker image for SVN[1]. I have
>> created the dockerfile and other relevant artifacts for SVN [2]. This is to
>> maintain a separate a docker image for SVN for deployment synchronization.
>> For dep sync in container deployments, there is a mail thread with subject
>> in [3].
>>
>> Basically rsync is an option for dep sync. But when it compares to SVN,
>> the following are the main advantages.
>>
>> - Can handle several manager nodes
>> - SVN Container can accommodate multiple products
>> - We can mount a single volume for SVN server only
>>
>> Please share your thoughts.
>>
>> [1] - https://hub.docker.com/
>> [2] - https://github.com/wso2/dockerfiles/pull/57
>> [3] - [Architecture] Dep sync strategies for Carbon 4 products in
>> Kubernetes
>>
>> Thank you!
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding SVN dockerfiles to wso2/dockerfiles

[Imesh Gunaratne]

On Thu, Jul 21, 2016 at 10:31 AM, Pubudu Gunatilaka 
wrote:

> Hi Akila,
>
> I used the base image to get rid of running apt-get update again for svn
> docker image. Apt-get update takes time and also sometimes it fails as
> well.
>
> I have already created Mesos artifacts for svn in [1] and will push those
> changes to Mesos artifact repo. Will work on the Kubernetes artifacts.
>

​May be we can first focus on Mesos artifacts. Will add this to K8S
artifacts later on. Might be better to track it in JIRA.

Thanks​


>
> [1] - https://github.com/pubudu538/mesos-artifacts/tree/master/common/svn
>
> Thank you!
>
> On Wed, Jul 20, 2016 at 10:19 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Pubudu,
>>
>> Why are we using wso2/wso2base:latest as the base image here? We have to
>> run apt-get update and install subversion anyway right?
>>
>> IMHO, we need to add artifacts for deploying this on Mesos, Kubernetes
>> etc. and integrate this with WSO2 DepSync. Shall we work on delivering the
>> complete package as well?
>>
>> Thanks.
>>
>> On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi,
>>>
>>> At the moment there is no any official docker image for SVN[1]. I have
>>> created the dockerfile and other relevant artifacts for SVN [2]. This is to
>>> maintain a separate a docker image for SVN for deployment synchronization.
>>> For dep sync in container deployments, there is a mail thread with subject
>>> in [3].
>>>
>>> Basically rsync is an option for dep sync. But when it compares to SVN,
>>> the following are the main advantages.
>>>
>>> - Can handle several manager nodes
>>> - SVN Container can accommodate multiple products
>>> - We can mount a single volume for SVN server only
>>>
>>> Please share your thoughts.
>>>
>>> [1] - https://hub.docker.com/
>>> [2] - https://github.com/wso2/dockerfiles/pull/57
>>> [3] - [Architecture] Dep sync strategies for Carbon 4 products in
>>> Kubernetes
>>>
>>> Thank you!
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


-- 
*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] Adding SVN dockerfiles to wso2/dockerfiles

[Akila Ravihansa Perera]

Hi Pubudu,

True, but this image will not be built regularly right? Once we push to
DockerHub users can pull instead of building?

Thanks.

On Thursday, 21 July 2016, Imesh Gunaratne  wrote:

>
>
> On Thu, Jul 21, 2016 at 10:31 AM, Pubudu Gunatilaka  > wrote:
>
>> Hi Akila,
>>
>> I used the base image to get rid of running apt-get update again for svn
>> docker image. Apt-get update takes time and also sometimes it fails as
>> well.
>>
>> I have already created Mesos artifacts for svn in [1] and will push those
>> changes to Mesos artifact repo. Will work on the Kubernetes artifacts.
>>
>
> ​May be we can first focus on Mesos artifacts. Will add this to K8S
> artifacts later on. Might be better to track it in JIRA.
>
> Thanks​
>
>
>>
>> [1] - https://github.com/pubudu538/mesos-artifacts/tree/master/common/svn
>>
>> Thank you!
>>
>> On Wed, Jul 20, 2016 at 10:19 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com >
>> wrote:
>>
>>> Hi Pubudu,
>>>
>>> Why are we using wso2/wso2base:latest as the base image here? We have to
>>> run apt-get update and install subversion anyway right?
>>>
>>> IMHO, we need to add artifacts for deploying this on Mesos, Kubernetes
>>> etc. and integrate this with WSO2 DepSync. Shall we work on delivering the
>>> complete package as well?
>>>
>>> Thanks.
>>>
>>> On Mon, Jul 18, 2016 at 12:40 PM, Pubudu Gunatilaka >> > wrote:
>>>
 Hi,

 At the moment there is no any official docker image for SVN[1]. I have
 created the dockerfile and other relevant artifacts for SVN [2]. This is to
 maintain a separate a docker image for SVN for deployment synchronization.
 For dep sync in container deployments, there is a mail thread with subject
 in [3].

 Basically rsync is an option for dep sync. But when it compares to SVN,
 the following are the main advantages.

 - Can handle several manager nodes
 - SVN Container can accommodate multiple products
 - We can mount a single volume for SVN server only

 Please share your thoughts.

 [1] - https://hub.docker.com/
 [2] - https://github.com/wso2/dockerfiles/pull/57
 [3] - [Architecture] Dep sync strategies for Carbon 4 products in
 Kubernetes

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


>>>
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
> *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] Clarification regarding the validating input using IdentityValidationUtil class

[Chamara Philips]

Hi Farasath,
The white lists (or black lists) should be provided with the keys before
the component is used. It will be not a good idea (from security
perspective) to let a regex to be passed at runtime, for back-end
validation. This is one reason why we shouldn't be satisfied only with
front-end validation.

On Fri, Jul 15, 2016 at 11:03 PM, Farasath Ahamed 
wrote:

> Hi,
>
> I am trying to validate input using the  IdentityValidationUtil[1] class.
> From my current understanding in order to validate an input using the util
> class for a regex, we need to first register it as a pattern in
> IdentityValidationConfig and then use the registered key as below,
>
> String regex = "^[A-Za-z0-9]+$";
> String input = "thisismainput";
>
>
> // add pattern to IdentityValidationConfig
> IdentityValidationUtil.addPattern("my-regex", regex);
> String validInput = 
> IdentityValidationUtil.getValidInputOverWhiteListPatterns(input, "my-regex");
>
>
> When many of the components start using the util class there is a
> possibility of the same key being registered for two different regexes
> resulting in an exception thrown according to [2]. Wouldn't it be better if
> we allow the users to directly provide the regex for validation instead of
> having to register it with a key and use for validation.
>
> So if  you want to use one of the pre-defined regexes you can use the
> relevant key (something like ALPHABETIC_ONLY) defined in class[1]. Or If
> you want to use his own regex you can simply provide it as a whitelist
> pattern.
>
> In the code, we can first check if the provided value is a predefined key,
> if so fetch the regex and validate. If the key is not found then we have
> given the regex directly, so we can use it directly to validate. This
> approach is used it the JavaScript util class we have written[3].
>
> WDYT?
>
>
> [1]
> https://github.com/wso2/carbon-identity-framework/blob/master/components/identity-core/org.wso2.carbon.identity.base/src/main/java/org/wso2/carbon/identity/base/IdentityValidationUtil.java
> [2]
> https://github.com/wso2/carbon-identity-framework/blob/master/components/identity-core/org.wso2.carbon.identity.base/src/main/java/org/wso2/carbon/identity/base/IdentityValidatorConfig.java#L58
> [3]
> https://github.com/wso2/carbon-identity-framework/blob/master/components/identity-core/org.wso2.carbon.identity.core.ui/src/main/resources/web/identity/validation/js/identity-validate.js
>
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
>
>
>
>


-- 
Hareendra Chamara Philips
*Software  Engineer*
Mobile : +94 (0) 767 184161
chama...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Chamalee De Silva]

Tested
 - basic API Flow
- Single Sign On using IS 5.2.0 beta2 for tenant and super tenant.


No issues found.

[x] - Stable -go ahead and release.



On Thu, Jul 21, 2016 at 8:45 AM, Nuwan Dias  wrote:

> Tested Identity Server as Key Manager using IS 5.2.0 Beta2. Tested the
> basic scenarios for tenant and super tenant users. No issues found.
>
> [x] - Stable - go ahead and release
>
> Thanks,
> NuwanD.
>
>
> On Thu, Jul 21, 2016 at 7:15 AM, Abimaran Kugathasan 
> wrote:
>
>> It's there in the github release page of both API Manager Runtime and
>> Analytics,
>>
>> On Thu, Jul 21, 2016 at 7:12 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Abimaran,
>>>
>>> Shouldn't we include a list of bugs fixed and features added in the
>>> release vote? Ideally this should be a JIRA filter link.
>>>
>>> Thanks.
>>>
>>> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan >> > wrote:
>>>

 *WSO2 API Manager 2.0.0-RC3 Released*

 This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0

 Source & binary distribution files of API Manager 2.0.0-RC3 :

  Runtime :
 https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
  Analytics :
 https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3

 Please download, test the product and vote. Vote will be open for 72
 hours or as needed.
 Refer to github readme for guides.

 Please vote as follows.
 [+] Stable - go ahead and release
 [-]  Broken - do not release (please explain why)

 --
 Thanks
 Abimaran Kugathasan
 Senior Software Engineer

 Email : abima...@wso2.com
 Mobile : +94 773922820

 
 
   
 


 ___
 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
>>>
>>
>>
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Chamalee De Silva]

+ Tested Reverse Proxy as well while having Single Sign On using IS 5.2.0
beta2 for tenant and super tenant.


Thanks,
Chamalee

On Thu, Jul 21, 2016 at 11:05 AM, Chamalee De Silva 
wrote:

> Tested
>  - basic API Flow
> - Single Sign On using IS 5.2.0 beta2 for tenant and super tenant.
>
>
> No issues found.
>
> [x] - Stable -go ahead and release.
>
>
>
> On Thu, Jul 21, 2016 at 8:45 AM, Nuwan Dias  wrote:
>
>> Tested Identity Server as Key Manager using IS 5.2.0 Beta2. Tested the
>> basic scenarios for tenant and super tenant users. No issues found.
>>
>> [x] - Stable - go ahead and release
>>
>> Thanks,
>> NuwanD.
>>
>>
>> On Thu, Jul 21, 2016 at 7:15 AM, Abimaran Kugathasan 
>> wrote:
>>
>>> It's there in the github release page of both API Manager Runtime and
>>> Analytics,
>>>
>>> On Thu, Jul 21, 2016 at 7:12 AM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 Hi Abimaran,

 Shouldn't we include a list of bugs fixed and features added in the
 release vote? Ideally this should be a JIRA filter link.

 Thanks.

 On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan <
 abima...@wso2.com> wrote:

>
> *WSO2 API Manager 2.0.0-RC3 Released*
>
> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC3 :
>
>  Runtime :
> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>  Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> 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

>>>
>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. :http://wso2.com/
>
> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
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 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 logs 
 specifying
 the logs location. As you said, logs shouldn't be in .txt extension, I 
 got
 

Re: [Dev] BPS 3.5.1 sends emails with empty bodies

[Sudharma Subasinghe]

Hi,

The issue can be resolved with following fix [1].

[1]
https://github.com/wso2/carbon-business-process/pull/423/commits/17bc321d39079125dbcb0e278107af4cd8cc6d19

Thanks
Sudharma


On Fri, Jul 1, 2016 at 12:43 AM, Amal Gunatilake  wrote:

> Hi Manu,
>
> According to the mail thread [1] discussion, it seems this is a potential
> bug in email task when message body configured in HTML format.
> I have created a jira ticket[2] to track this. Meanwhile as a workaround,
> using the text format body works.
>
> [1] Re: WSO2 BPS - Email Task
> [2] https://wso2.org/jira/browse/BPS-1063
>
> Best regards,
> Amal.
>
> On Thu, Jun 30, 2016 at 9:37 PM, Manuranga Perera  wrote:
>
>> Hi Amal,
>>
>> 1) The doc [1] asks me to copy commons-email:jar:1.3 but the product
>> already comes with 1.4
>>
>> 2) Even if I copy the jars, I still get emails with empty body, only with
>> title. (emails are send with html bodies using )
>>
>> [1] https://docs.wso2.com/display/BPS351/Working+with+the+Email+Task
>>
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>
>
>
> --
> *Amal Gunatilake*
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> mobile: (+94) 773561195
> blog: amalg-blogs.blogspot.com; twitter: @daag123
> linkedIn: https://www.linkedin.com/in/amalgunatilake
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sudharma Subasinghe,
Software Engineer,
WSO2 Inc.
Email: sudhar...@wso2.com 
Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC3

[Abimaran Kugathasan]

P2-Repo can found from here [1]

[1] : https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/p2-repos/rc3/

On Thu, Jul 21, 2016 at 11:11 AM, Chamalee De Silva 
wrote:

> + Tested Reverse Proxy as well while having Single Sign On using IS 5.2.0
> beta2 for tenant and super tenant.
>
>
> Thanks,
> Chamalee
>
> On Thu, Jul 21, 2016 at 11:05 AM, Chamalee De Silva 
> wrote:
>
>> Tested
>>  - basic API Flow
>> - Single Sign On using IS 5.2.0 beta2 for tenant and super tenant.
>>
>>
>> No issues found.
>>
>> [x] - Stable -go ahead and release.
>>
>>
>>
>> On Thu, Jul 21, 2016 at 8:45 AM, Nuwan Dias  wrote:
>>
>>> Tested Identity Server as Key Manager using IS 5.2.0 Beta2. Tested the
>>> basic scenarios for tenant and super tenant users. No issues found.
>>>
>>> [x] - Stable - go ahead and release
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>>
>>> On Thu, Jul 21, 2016 at 7:15 AM, Abimaran Kugathasan 
>>> wrote:
>>>
 It's there in the github release page of both API Manager Runtime and
 Analytics,

 On Thu, Jul 21, 2016 at 7:12 AM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> Hi Abimaran,
>
> Shouldn't we include a list of bugs fixed and features added in the
> release vote? Ideally this should be a JIRA filter link.
>
> Thanks.
>
> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan <
> abima...@wso2.com> wrote:
>
>>
>> *WSO2 API Manager 2.0.0-RC3 Released*
>>
>> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC3 :
>>
>>  Runtime :
>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>>  Analytics :
>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>>   
>>
>>
>> ___
>> 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
>



 --
 Thanks
 Abimaran Kugathasan
 Senior Software Engineer

 Email : abima...@wso2.com
 Mobile : +94 773922820

 
 
   
 


 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Software Architect - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. :http://wso2.com/
>>
>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. :http://wso2.com/
>
> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer

Email : abima...@wso2.com
Mobile : +94 773922820


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