Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

You do not have to add config data for each hierarchy. If you want to use without any platform configuration then you can set the "platform" facter variable to "default". On Tue, May 10, 2016 at 9:54 AM, Lakmal Warusawithana wrote: > Say platform k8s , we need to have vm_type

Re: [Dev] Developer Studio Server Modification to add Product based Servers

Hello all, We have completed $subject as an improvement for user experience as follows, We have enabled dynamic extension point generation in Developer Studio, we retrieve the Specific display name from the product plugins when they register their servers as given in the following example : *

Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector

Hi Malaka, As an offline chat with Buddhima, if a certain version of automation frame work needs a certain axis2 version, then there should be a release version of automation framework along with that axis2. On Mon, May 9, 2016 at 9:56 AM, Hariprasath Thanarajah wrote: >

Re: [Dev] [DEV][Puppet Modules] Finalizing wso2/puppet-modules 2.0.0 release

Hi, Please find the node port ranges used in puppet modules. We should add this to wiki. Product Port Range Min Port Max Port wso2am 32000 32020 wso2as 32021 32030 wso2bps 32031 32040 wso2brs 32041 32050 wso2cep 32051 32060 wso2das 32061 32070 wso2dss 32071 32080 wso2es 32081 32090 wso2esb 32091

Re: [Dev] [DAS] Starting DAS gives an error when secure vault enabled

HI Inosh, I tried again, it worked. But not sure what was wrong in my configurations. Thanks Amlaka On Tue, May 10, 2016 at 9:44 AM, Inosh Goonewardena wrote: > Hi Amalka, > > Could you please try this again? I checked this and it worked without any > issues. I think this

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

Say platform k8s , we need to have vm_type right? I want to use vm_type docker , but without any platform configuration. How can I do that? On Tue, May 10, 2016 at 9:51 AM, Akila Ravihansa Perera wrote: > Hi Lakmal, > > Hierarchy will be the same (hiera.yaml). You need to

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

Hi Lakmal, Hierarchy will be the same (hiera.yaml). You need to set docker-compose specific configuration in "vm_type/docker-compose.yaml" file. This is for when building the image. Puppet cannot handle run time configuration in container scenario. If there is no platform (Mesos, K8s etc.)

[Dev] Fwd: Why we Keep older versions in the new Releases?

Hi All, In every release of our product we didn't upgrade the dependency versions in the pom file. For example take wso2-synapse and wso2-axis2. The new released version of axis2 according to [1] is v1.6.1-wso2v17 and wso2-synapse is 2.1.7-wso2v3-ALPHA. But in the synapse still the version of

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

Say I want to use in docker-compose (with pure docker). What hiera files (config) I have to use? On Tue, May 10, 2016 at 6:18 AM, Chamila De Alwis wrote: > I agree. Let's keep vm_type for simplicity. > > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache

Re: [Dev] [DAS] Starting DAS gives an error when secure vault enabled

Hi Amalka, Could you please try this again? I checked this and it worked without any issues. I think this might be some configuration issue happen when configuring Secure vault. On Tue, May 10, 2016 at 8:49 AM, Amalka Subasinghe wrote: > Hi, > > Steps to reproduce. > > 1. Get

Re: [Dev] [Docker][Puppet] [MB] Setting 'thriftServerHost' in WSO2 MB broker.xml file

Hi All, I have added the custom extension to wso2mb puppet module through 'system_file_list' method. Like we used file_list to copy files to wso2 carbon home, we can copy files which are added */files/system* to system using *system_file_list *as below: wso2::system_file_list: - file:

[Dev] [DAS] Starting DAS gives an error when secure vault enabled

Hi, Steps to reproduce. 1. Get DAS 3.0.1 vanilla pack. 2. Enable secure vault as follows a. added the following line to the wso2das-3.0.1/repository/conf/security/cipher-tool.properties file

Re: [Dev] [Vote] Developer Studio Kernel RC 2 released !

I have noticed following improvement , those are not blockers but better if we can get it fix in GA from usability point of view -Menu seperators are appearing in Developer studio menu , all the eclipse standard menus has menu separators -Add keyboard shortcut for relevant sub menus -All

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

Hi Osura, On Mon, May 9, 2016 at 11:22 PM, Osura Rathnayake wrote: > Hi mentors, > > When setting up the DB according to [1], should shared REGISTRY_DB and > shared WSO2_USER_DB be resided on a separate server other than the > manager/worker node? if so can I use the same

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

Hi Osura, On Mon, May 9, 2016 at 11:22 PM, Osura Rathnayake wrote: > Hi mentors, > > When setting up the DB according to [1], should shared REGISTRY_DB and > shared WSO2_USER_DB be resided on a separate server other than the > manager/worker node? if so can I use the same

Re: [Dev] [DEV][Puppet Modules] Finalizing wso2/puppet-modules 2.0.0 release

Hi Akila, On Tue, May 10, 2016 at 6:14 AM, Akila Ravihansa Perera wrote: > WARNING: class inherits across module namespaces > WARNING: line has more than 80 characters > I think we can ignore these as they were considered in the decision process. I'll change the release

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

I agree. Let's keep vm_type for simplicity. Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Tue, May 10, 2016 at 6:15 AM, Akila Ravihansa Perera wrote: > Hi Chamila, > > Docker

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

Hi Chamila, Docker is not really a platform if you look at the semantics. If we create another YAML for docker under platform hierarchy then we have to duplicate every platform specific YAML files under product hierarchy. I don't think it's a good option for us. Thanks. On Tue, May 10, 2016 at

Re: [Dev] [DEV][Puppet Modules] Finalizing wso2/puppet-modules 2.0.0 release

Hi Chamila, We had to bring back "vm_type" because it is needed for bare Docker scenario. Please refer to the other thread on wso2-dev list for a detailed explanation. I've also fixed Puppet Lint issues in all modules. There are 2 warnings remaining though, as follows; WARNING: class inherits

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

Hi Akila, Why don't we use Docker as a platform rather than a vm_type? I'm not sure about Rocket, however if there are no considerable data duplication between Docker and a possible Rocket configuration data set, IMO we should keep the hierarchy simple and include Docker as a platform. WDYT?

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

Hi, It seems "vm_type" hierarchy should exist to build Docker images (provisioned via Puppet) and then run on bare Docker. Because when building the images for default platform (which is the option for bare Docker), there should be a separate hierarchy to set the installation_dir parameter to

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

Hi mentors, When setting up the DB according to [1], should shared REGISTRY_DB and shared WSO2_USER_DB be resided on a separate server other than the manager/worker node? if so can I use the same server i used for load balancer for this purpose? [1]

[Dev] [DEV][Puppet Modules] Finalizing wso2/puppet-modules 2.0.0 release

Hi, Let's finalize the wso2/puppet-modules [1] 2.0.0 release. Following are the features and fixes implemented in this release. - Updated Hiera data hierarchy to include deployment platform - Kubernetes based workflow supported, based on wso2/kubernetes-artifacts -

Re: [Dev] [PC] Getting user names from registry log entries

Thanks for the input given.I will look into go for implementing a registry handler in this case. Thanks, Sameera. On Mon, May 9, 2016 at 1:56 PM, Thushara Ranawaka wrote: > Hi Sameera, > > Even though test_user did 868, 869 and 870 activities the registry > delegate the

Re: [Dev] [DS] Adding same child for two different parents in WSO2 permission tree

Note that there are two ways to do the permission mapping in C4. 1) Per-resource - eg: in registry each resources has delete read writes permissions for each role. 2) Per-action - eg: in admin console each role can have permission to add users (but this can't be limited for just one user store)

[Dev] Issue in creating a SaaS App with the Multi-Tenant Carbon Framework

Hi all, I am following the below blog post in order to get an understanding of creating a SaaS App with the Multi-Tenant Carbon Framework. Blog post link : http://wso2.com/library/blog-post/2013/09/creating-a-saas-app-with-the-multi-tenant-carbon-framework-step-1/ According to the blog post,

Re: [Dev] [PC] [ES] Cannot retrieve feature details of searchHistory error after moving to latest store version

Hi, Thanks Denuwanthi. After adding the new element to our process-store-tenant.json issue got resolved. Thanks, Waruna On Fri, May 6, 2016 at 3:30 PM, Denuwanthi De Silva wrote: > Hi Waruna, > > Can you specify the store and registry versions you are using? > We have

Re: [Dev] Running WSO2ESB in Clutered mode

Hi Abhishek, On Mon, May 9, 2016 at 7:14 AM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi All, > > I have been trying to run ESB in clustered setup (one master and one > worker node). Here are the steps I followed: > 1) Have two copies of wso2esb-4.9.0 (esb-master and

[Dev] Failed to add rxt to registry issue in GREG

Hi, I'm trying to setup 2 GREG nodes clustered in Kubernetes using Kubernetes Membership Scheme. The GREG nodes are started using Dsetup. When both GREG nodes are started in different Pods during same time, the following error occurs in one of the nodes but the product starts fine. TID: [-1234]

[Dev] Fwd: Fwd: [IS] Missing requirement in building product-is from source

[Adding dev] -- Forwarded message -- From: Manujith Pallewatte Date: Mon, May 9, 2016 at 5:00 PM Subject: Re: [Dev] Fwd: [IS] Missing requirement in building product-is from source To: Chamila Wijayarathna Hi Malithi, This error in

Re: [Dev] Fwd: [IS] Missing requirement in building product-is from source

Anybody know a way to get out of this error ??? On Mon, May 9, 2016 at 1:59 PM, Malithi Edirisinghe wrote: > Hi, > > Is this being solved. I get the same error [1] when building on OS X > Yosemite. Also seems the same was discussed in [2] as well. > > This was identified as a

Re: [Dev] [C5][BPS] Startup errors with new kernel SNAPSHOT

Can we have a quick resolution to this issue. Regards Nandika On Mon, May 9, 2016 at 11:09 AM, Niranjan Karunanandham wrote: > Hi Sameera, > > I have fixed this for carbon-datasources in PR [1]. > > [1] - https://github.com/wso2/carbon-datasources/pull/14 > > Regards, > Nira

Re: [Dev] [Docker][Puppet] [MB] Setting 'thriftServerHost' in WSO2 MB broker.xml file

Hi All, Thanks for the suggestions !!! As Isuru suggested, the best approach would be to use an extension point to update thriftServerHost with container ip. Will go with this approach. Thanks. On Mon, May 9, 2016 at 2:01 PM, Akila Ravihansa Perera wrote: > Hi Pumudu, > >

Re: [Dev] [DEV][Puppet Modules] Unnecessary lookup for wso2::secure_vault_configs

Hi Chamila, On Mon, May 9, 2016 at 1:50 PM, Chamila De Alwis wrote: > Hi, > > In wso2base/manifests/init.pp [1], we do a Hiera lookup > for wso2::secure_vault_configs, without checking if SecureVault > configurations are needed. IMO we should only do this lookup if the >

Re: [Dev] [Docker][Puppet] [MB] Setting 'thriftServerHost' in WSO2 MB broker.xml file

Hi Pumudu, We can't use "%{::ipaddress}" in kubernetes platform since Puppet is only used to build the Docker images. The ipaddress is assigned when the Kubernetes pods/services are deployed. I think best method would be to use the extension point as explained by Isuru. This should be similar to

Re: [Dev] Fwd: [IS] Missing requirement in building product-is from source

Hi, Is this being solved. I get the same error [1] when building on OS X Yosemite. Also seems the same was discussed in [2] as well. This was identified as a bug in felix plugin at [3]. Upgrading the maven-scr-plugin to version 1.8.0 successfully built the respective component. However, that

Re: [Dev] [PC] Getting user names from registry log entries

Hi Sameera, Even though test_user did 868, 869 and 870 activities the registry delegate the process to wso2.system.user. For example when you creating a soap service using WSDL soap service creation entries are done by wso2.system.user. However you should able to see actions done using test_user

[Dev] [DEV][Puppet Modules] Unnecessary lookup for wso2::secure_vault_configs

Hi, In wso2base/manifests/init.pp [1], we do a Hiera lookup for wso2::secure_vault_configs, without checking if SecureVault configurations are needed. IMO we should only do this lookup if the previous lookup for wso2::enable_secure_vault is true. Otherwise

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

Updated the information given on the "Resend ESB Debug Points" option in [1], to match the current implementation. Thanks everyone! [1] https://docs.wso2.com/display/ESB500/Debugging+Mediation On Mon, May 9, 2016 at 1:24 PM, Dilshani Subasinghe wrote: > Hi Chanaka, > >

Re: [Dev] [Docker][Puppet] [MB] Setting 'thriftServerHost' in WSO2 MB broker.xml file

Hi, AFAIU, Thrift hostname should be changed to IP from puppet modules when configuring hiera data[1]. Following line[2] should added to default.yaml[3] to get the IP when initializing. [1]

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

Hi Chanaka, Added a jira [1] and +1 for fixing it with this release. [1] https://wso2.org/jira/browse/DEVTOOLESB-208 Regards, Dilshani On Mon, May 9, 2016 at 1:00 PM, Nuwan Pallewela wrote: > Hi Chanaka, > > This is not reported as a public JIRA yet. > > Thanks, > Nuwan > >

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

Hi Chanaka, This is not reported as a public JIRA yet. Thanks, Nuwan On Mon, May 9, 2016 at 12:51 PM, Chanaka Fernando wrote: > Is there any public JIRA already created? > > On Mon, May 9, 2016 at 12:46 PM, Isabelle Mauny wrote: > >> +1 - Can we fix this

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

Is there any public JIRA already created? On Mon, May 9, 2016 at 12:46 PM, Isabelle Mauny wrote: > +1 - Can we fix this in 5.0.0 … > __ > > Isabelle Mauny > VP, Product Management; WSO2, Inc.; http://wso2.com/ > > On May 9,

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

+1, IMO that's better since now it's clear how what kubernetes.yaml stands for. Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Mon, May 9, 2016 at 12:21 PM, Akila Ravihansa Perera

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

+1 - Can we fix this in 5.0.0 … __ Isabelle Mauny VP, Product Management; WSO2, Inc.; http://wso2.com/ > On May 9, 2016, at 9:05 AM, Chathurika De Silva wrote: > > Hi ESB Team > > Addition to dilshani' and nuwan's

Re: [Dev] [DS] Adding same child for two different parents in WSO2 permission tree

Hi Megala, >From the dashboard server point of view, we just need to have permission tree as, - Portal - Login - Dashboard - Create - Delete - Settings In this model, the create permission is required for the user to create the dashboard, and similarly for other operations.

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

Hi ESB Team Addition to dilshani' and nuwan's feedback, from user's perspective, when debug points are set and if the artifact is not changed, the need for him to resend debug point information is an additional task. Ideally it's better to give the same feel to a developer who is using this tool

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

Hi Dilshani, Thank you for pointing out this. ESB will forget the registered debug points when synapse configuration changes or server gets restarts. So when one of those happens user need to use the *"Resend ESB Debug Points"* command to re-register the debug-points in the server. But I think

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

Hi Chamila, Agreed. I don't think there would be anymore files in addition to common.yaml here. How about moving this to root level; for eg: "platform/kubernetes.yaml" ? Full Hierarchy will be as follows; :hierarchy: - "node/%{::clientcert}" -

[Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

Hi ESB Team, After restarting debug process, it may not identify previously added debug points. But newly added ESB points will be added to debug process successfully. When we using the option "*Resend ESB Debug Points*", it may send previous debug points too. As Far As I Feel, this is bit of

Re: [Dev] [Docker][Puppet] [MB] Setting 'thriftServerHost' in WSO2 MB broker.xml file

Hi Thanuja, As you have mentioned, the MB needs the IP address instead of the host name to configure the Thrift server. So you will have to correct the thrift server connection details mentioned in "wso2mb-default/10.100.186.164:7611". Thanks, Akalanka. On Mon, May 9, 2016 at 11:31 AM, Isuru

Re: [Dev] [Docker][Puppet] [MB] Setting 'thriftServerHost' in WSO2 MB broker.xml file

Hi Thanuja, There is an extension point [1] in the startup script for Dockerfiles, where is looks for another script with a particular name format to execute before starting the server. You should b able to use that to do a find replace in the broker.xml with the container IP. [1].

Re: [Dev] [Puppet] [Hiera] Introducing a hierarchy for platform specific common configuration

+1 How about wso2/kubernetes.yaml instead of wso2/kubernetes/common.yaml? Will there be a YAML file in addition to the common.yaml? - "wso2/%{::platform}" Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com