Re: [Dev] [EI] Data services are not hot deploying

[Gayan Gunarathne]

I guess this happen due to the database connection mentioned in the dbs. It
requires to restart the server.

Thanks,
Gayan

On Thu, Jan 4, 2018 at 7:17 AM, Shazni Nazeer  wrote:

> I have noticed the same. This happens in the data services server 3.5.1
> too. Always requires a restart to take effect.
>
> Is this a bug?
>
> On Tue, Jan 2, 2018 at 1:15 AM, Godwin Shrimal  wrote:
>
>> Hi Devs,
>>
>> We can change proxy services (Deployed using CAR) from UI and its getting
>> hot deploy after changes. But we can't observe same with Data Services. Any
>> reason for this ? Is it the expected behaviour ?
>>
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>> *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> Shazni Nazeer
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>
> Blogs :
>
> https://medium.com/@mshazninazeer
> http://shazninazeer.blogspot.com
>
> 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Supporting registry based parameter values in all Inbound Endpoints

[Gayan Gunarathne]

Are we support to use inbound endpoints with secure vault based parameters
in ESB 5.0.0? If then could you please share some pointers how to use that?

Thanks,
Gayan

On Tue, Jun 28, 2016 at 5:31 PM, Kasun Indrasiri <ka...@wso2.com> wrote:

> The other aspect is the outbound side. For instance, for outbound
> messaging we don't have a way to retries credentials from ESB secure vault?
>
> On Tue, Jun 21, 2016 at 10:20 AM, Kasun Indrasiri <ka...@wso2.com> wrote:
>
>> Hi,
>>
>> $subject is quite important when it comes to developing inbound endpoints
>> and bind them to specific environments (with the use of registry key values
>> paris). Also, at the same time we need to get this integrated to secure
>> vault based parameters which are encrypted.
>>
>> Thanks,
>> Kasun
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [BPS] Substitute API - Change substitute API method

[Gayan Gunarathne]

What is the use case of the BPS change substitution api method in [1] ? Is
it change whole the existing substitute records(I mean old records
+ future records) of the user?

Also what is the different between update substitution record and Change
substitute?Seems we don't have much information in the documentation.

[1]https://docs.wso2.com/display/BPS360/Substitution+REST+APIs

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Error log continuously printing in the carbon log

[Gayan Gunarathne]

Hi Chanaka,

I used this documentation[1]. For the FileURI only changed to the sftps.
Thing is file moving correctly. But continuously see the above log in the
carbon console.

sftp://:@

[1]https://docs.wso2.com/display/ESB500/File+Inbound+Protocol

Thanks,
Gayan

On Sat, Jul 30, 2016 at 12:00 AM, Chanaka Fernando <chana...@wso2.com>
wrote:

> Hi Gayan,
>
> Can you share the configuration you have used?
>
> On Sat, Jul 30, 2016 at 12:52 AM, Gayan Gunarathne <gay...@wso2.com>
> wrote:
>
>> We have used the ESB 5.0.0 beta2 release and configured file inbound
>> endpoint with sftp.
>> File moving happen correctly but found following logs print in the carbon
>> log continuously. Why is that happening?
>>
>> TID: [-1234] [] [2016-07-29 15:11:21,977] ERROR
>> {org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer} -
>>  Unable to close the file system. null
>> {org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer}
>> TID: [-1234] [] [2016-07-29 15:11:21,977] ERROR
>> {org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer} -
>>  java.lang.NullPointerException
>> {org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer}
>>
>> Thanks,
>> Gayan
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> m: +94 773337238
> https://wso2.com <https://wso2.com/signature>
>
>
>
>
>
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Error log continuously printing in the carbon log

[Gayan Gunarathne]

We have used the ESB 5.0.0 beta2 release and configured file inbound
endpoint with sftp.
File moving happen correctly but found following logs print in the carbon
log continuously. Why is that happening?

TID: [-1234] [] [2016-07-29 15:11:21,977] ERROR
{org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer} -
 Unable to close the file system. null
{org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer}
TID: [-1234] [] [2016-07-29 15:11:21,977] ERROR
{org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer} -
 java.lang.NullPointerException
{org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer}

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Gayan Gunarathne]

On Thu, Jul 21, 2016 at 5:05 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:

> Hi Akila,
>
> What you are saying is correct. We will use apt-get install in SVN docker
> image and get rid of base image. And also I will use the image name as
> wso2/svn:1.0.0 as we can push this to docker hub.
>

Why we use 1.0.0 instead of the SVN version? How we manager SVN different
versions?

>
> Thank you!
>
> On Thu, Jul 21, 2016 at 10:59 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> 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 <im...@wso2.com> wrote:
>>
>>>
>>>
>>> On Thu, Jul 21, 2016 at 10:31 AM, Pubudu Gunatilaka <pubu...@wso2.com>
>>> 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 <pubu...@wso2.com>
>>>>> 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
>>
>>
>
>
> --
> *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
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS] BPS processes can't access when start the worker node with -DworkerNode=true

[Gayan Gunarathne]

On Fri, Jul 15, 2016 at 4:40 PM, Hasitha Aravinda <hasi...@wso2.com> wrote:

> For BPS, we are not recommending to use -DworkerNode=true in cluster,
> because when server starts as a worker node, it will disable all the admin
> services. But there are some user services exposed as Admin Services ( i.e
> HumanTask client API, BPMN Admin services etc. ).
>
> It seems like doc is misleading. will correct this doc.
>

Yeah.Then we need to correct the documentation.

>
> Thanks,
> Hasitha.
>
> On Fri, Jul 15, 2016 at 4:32 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
>
>> I won't be able to access the processes in bpmn-explorer of worker node
>> when worker node start with -DworkerNode=true in BPS cluster[1]. It will
>> redirect to the login page.But if I start the worker node
>> without -DworkerNode=true, I can access and start the processes with out a
>> issue.
>>
>> Added a JIRA[2] with steps.
>>
>> [1]
>> https://docs.wso2.com/display/CLUSTER44x/Clustering+Business+Process+Server+3.5.0+and+3.5.1
>> [2]https://wso2.org/jira/browse/BPS-1090
>>
>> Thanks,
>> Gayan
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>
>
>
> --
> --
> Hasitha Aravinda,
> Associate Technical Lead,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +94 718 210 200
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [BPS] BPS processes can't access when start the worker node with -DworkerNode=true

[Gayan Gunarathne]

I won't be able to access the processes in bpmn-explorer of worker node
when worker node start with -DworkerNode=true in BPS cluster[1]. It will
redirect to the login page.But if I start the worker node
without -DworkerNode=true, I can access and start the processes with out a
issue.

Added a JIRA[2] with steps.

[1]
https://docs.wso2.com/display/CLUSTER44x/Clustering+Business+Process+Server+3.5.0+and+3.5.1
[2]https://wso2.org/jira/browse/BPS-1090

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BPS 3.5.1 compatible mysql version

[Gayan Gunarathne]

Thanks. Shall we include those version details in the documentation?
Otherwise it will confuse the end user.

[1]
https://docs.wso2.com/display/CLUSTER44x/Clustering+Business+Process+Server+3.5.0+and+3.5.1#ClusteringBusinessProcessServer3.5.0and3.5.1-Settingupthedatabases
[2]https://docs.wso2.com/display/BPS351/Setting+up+MySQL

Thanks,
Gayan

On Tue, Jul 12, 2016 at 11:34 AM, Hasitha Aravinda <hasi...@wso2.com> wrote:

> Please find my comments inline.
>
> On Tue, Jul 12, 2016 at 11:27 AM, Vinod Kavinda <vi...@wso2.com> wrote:
>
>> Hi Gayan,
>> There are separate scripts for mysql 5.5 for bpmn. Have you tried with
>> those scripts. You need to run following scripts located at
>> /dbscripts/bps/bpmn/create folder.
>>
>> activiti.mysql55.create.engine.sql
>>
>> activiti.mysql55.create.history.sql
>>
>> We have not tested for mysql 5.7 AFAIU.
>>
>>
>> Regards,
>>
>> Vinod
>>
>>
>>
>>
>> On Tue, Jul 12, 2016 at 11:19 AM, Gayan Gunarathne <gay...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Seems BPS 3.5.1 worked only with mysql 5.6. Got the following
>>> incompatibility issues with mysql 5.5 and mysql 5.7.
>>> But in the documentation we didn't mention anything about the mysql
>>> version[1]. If we are support only mysql 5.6, shall we update the
>>> documentation with the compatible mysql version?
>>>
>>> mysql 5.5 - Syntax incompatibility with BPMN_DB
>>>
>>> bps_rdbms  | /usr/local/bin/docker-entrypoint.sh: running
>>> /docker-entrypoint-initdb.d/bpsdb.sql
>>> bps_rdbms  | ERROR 1064 (42000) at line 2052: You have an error in your
>>> SQL syntax; check the manual that corresponds to your MySQL server version
>>> for the right syntax to use near '(3),
>>> bps_rdbms  | primary key (ID_)
>>> bps_rdbms  | ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8_bin' at
>>> line 6
>>> bps_rdbms exited with code 1
>>>
>>
> A
> ​s Vonod mentioned, Activiti has two scripts for MySQL 5.5 and MySQL 5.6. ​
>
>
>>>
>>> mysql 5.7 - Syntax incompatibility  with WSO2_USER_DB
>>>
>>> bps_rdbms  | /usr/local/bin/docker-entrypoint.sh: running
>>> /docker-entrypoint-initdb.d/bpsdb.sql
>>> bps_rdbms  | ERROR 1067 (42000) at line 55: Invalid
>>> ​​
>>> default value for 'REG_CREATED_TIME'
>>> bps_rdbms exited with code 1
>>>
>>
> ​AFAIK, this is a known issue in kernel db scripts. Kernel registry mysql
> script has default timestamp value as 0, which is not supported in MySQL
> 5.7. This is fixed in latest kernel release.
>
> Thanks,
> Hasitha.
> ​
>
>
>>
>>> [1]https://docs.wso2.com/display/BPS351/Setting+up+MySQL
>>>
>>> Thanks,
>>> Gayan
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead, WSO2 Inc. (http://wso2.com)
>>> Committer & PMC Member, Apache Stratos
>>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Vinod Kavinda
>> Software Engineer
>> *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.*
>> Mobile : +94 (0) 712 415544
>> Blog : http://soatechflicks.blogspot.com/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Hasitha Aravinda,
> Associate Technical Lead,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +94 718 210 200
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] BPS 3.5.1 compatible mysql version

[Gayan Gunarathne]

Hi,

Seems BPS 3.5.1 worked only with mysql 5.6. Got the following
incompatibility issues with mysql 5.5 and mysql 5.7.
But in the documentation we didn't mention anything about the mysql
version[1]. If we are support only mysql 5.6, shall we update the
documentation with the compatible mysql version?

mysql 5.5 - Syntax incompatibility with BPMN_DB

bps_rdbms  | /usr/local/bin/docker-entrypoint.sh: running
/docker-entrypoint-initdb.d/bpsdb.sql
bps_rdbms  | ERROR 1064 (42000) at line 2052: You have an error in your SQL
syntax; check the manual that corresponds to your MySQL server version for
the right syntax to use near '(3),
bps_rdbms  | primary key (ID_)
bps_rdbms  | ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8_bin' at line
6
bps_rdbms exited with code 1


mysql 5.7 - Syntax incompatibility  with WSO2_USER_DB

bps_rdbms  | /usr/local/bin/docker-entrypoint.sh: running
/docker-entrypoint-initdb.d/bpsdb.sql
bps_rdbms  | ERROR 1067 (42000) at line 55: Invalid default value for
'REG_CREATED_TIME'
bps_rdbms exited with code 1

[1]https://docs.wso2.com/display/BPS351/Setting+up+MySQL

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Dockerfiles] Improvements to wso2base image

[Gayan Gunarathne]

On Mon, Jul 11, 2016 at 12:52 PM, Imesh Gunaratne <im...@wso2.com> wrote:

> May be we can track these here:
> https://wso2.org/jira/browse/DOCKERFILE
>

Seems this JIRA is not updated. Even 1.0.0, 1.1.0 releases still in the
unreleased category.

Also there are issues in GITHUB also[1]. Which one we are going to track
issues (GITHUB or JIRA) ?

[1]https://github.com/wso2/dockerfiles/issues

>
>
> Thanks
>
> On Mon, Jul 11, 2016 at 12:33 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi,
>>
>> We have also included a feature to enable debug mode for WSO2 servers.
>> This can be enabled by passing "DEBUG" env variable with the port number to
>> listen on for debug connections.
>>
>> You can also pass any system properties to WSO2 servers by adding those
>> to "STARTUP_ARGS" env variable which will be passed when calling the server
>> startup script. Setting DEBUG env variable will simply append ' -debug
>> $DEBUG' to STARTUP_ARGS.
>>
>> DEBUG property was originally added by GayanG. I modified it to support
>> setting any system property in Docker run-time.
>>
>> This is now pushed to DockerHub [1].
>>
>> [1] https://hub.docker.com/r/wso2/wso2base/tags/
>>
>> Thanks.
>>
>> On Mon, Jul 11, 2016 at 11:57 AM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>> Thanks for the update Akila!
>>>
>>> On Mon, Jul 11, 2016 at 11:15 AM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> We have made few improvements in wso2base Dockerfile [1] and init
>>>> script [2].
>>>>
>>>>  - Included 'net-tools' package by default. Commands bundled with this
>>>> package are widely used when troubleshooting network related issues (eg:
>>>> netstat, ifconfig, hostname, route).
>>>>
>>>>  - Introduced "/mnt/wso2-artifacts" folder to copy any kind of artifact
>>>> to CARBON_HOME directory (will be copied recursively and relative to folder
>>>> structure)
>>>>   This can be used as a mount point if a user wants to copy artifacts
>>>> at the Docker run-time.
>>>>
>>>> We will be deprecating the old artifacts folder:
>>>> '/mnt/wso2/carbon-home' to avoid confusion with CARBON_HOME symlink.
>>>>
>>>>
>>>> [1] https://github.com/wso2/dockerfiles/blob/master/wso2base/Dockerfile
>>>> [2]
>>>> https://github.com/wso2/dockerfiles/blob/master/common/scripts/entrypoint.sh
>>>>
>>>> Thanks.
>>>>
>>>> --
>>>> Akila Ravihansa Perera
>>>> WSO2 Inc.;  http://wso2.com/
>>>>
>>>> Blog: http://ravihansa3000.blogspot.com
>>>>
>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Software Architect
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: https://medium.com/@imesh TW: @imesh
>>>
>>>
>>
>>
>> --
>> 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
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How can we keep wait a docker container to start

[Gayan Gunarathne]

Yeah.Currently this is not supported with Docker Compose.So we are using
sleep for this.

But there is a health check feature listed under next version[1][2].May be
with that version we able to use that to determine if a container is
"alive".

[1]https://github.com/docker/docker/issues/21142
[2]https://github.com/docker/compose/issues/374

Thanks,
Gayan

On Mon, Jul 4, 2016 at 8:17 PM, Lakmal Warusawithana <lak...@wso2.com>
wrote:

> Its only work for container start time , not wait for app start time
> inside the container. We have introduced sleep environment variable in our
> products, if we define sleep in compose, our startup script wait sleep time
> before start the server.
>
>
> On Monday, July 4, 2016, Tharindu Dharmarathna <tharin...@wso2.com> wrote:
>
>> Hi All,
>>
>> Is there any way to wait the start of containers which depends on other
>> container get started successfully.
>>
>> I had tried with [1] . But it didn't get worked as well.
>>
>> [1] - https://docs.docker.com/compose/startup-order/
>>
>> --
>>
>> *Tharindu Dharmarathna*Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <%2B94779109091>*
>>
>
>
> --
> Sent from Gmail Mobile
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Pass environment variables in docker run.sh

[Gayan Gunarathne]

Shall we update the run.sh in docker files to pass the environment
variables?As an example sleep,debug that need to be pass as a environment
variable.
docker run -d -e SLEEP=1 --name wso2am wso2am:1.10.0

[1]
https://github.com/wso2/dockerfiles/blob/master/common/scripts/docker-run.sh#L153


Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Error while starting API manager nodes in Docker

[Gayan Gunarathne]

We are getting following when try to starting the store. publisher nodes in
Docker containers by using docker compose.  Also this is happened
intermittently.

store1 | [2016-05-19 12:37:06,845] ERROR - DatabaseUtil Database
Error - Duplicate entry 'http://wso2.org/oidc/claim--1234' for key
'UM_DIALECT_URI'
store1 |
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
Duplicate entry 'http://wso2.org/oidc/claim--1234' for key 'UM_DIALECT_URI'
store1 | at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
store1 | at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
store1 | at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
store1 | at
java.lang.reflect.Constructor.newInstance(Constructor.java:526)
store1 | at com.mysql.jdbc.Util.handleNewInstance(Util.java:377)
store1 | at com.mysql.jdbc.Util.getInstance(Util.java:360)
store1 | at
com.mysql.jdbc.SQLError.createSQLException(SQLError.java:971)
store1 | at
com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3887)
store1 | at
com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3823)
store1 | at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
store1 | at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
store1 | at
com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2530)
store1 | at
com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1907)
store1 | at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2141)
store1 | at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2077)
store1 | at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2062)
store1 | at
org.wso2.carbon.user.core.claim.dao.ClaimDAO.addDialect(ClaimDAO.java:442)
store1 | at
org.wso2.carbon.user.core.claim.dao.ClaimDAO.addClaimMapping(ClaimDAO.java:186)
store1 | at
org.wso2.carbon.user.core.claim.dao.ClaimDAO.addCliamMappings(ClaimDAO.java:140)
store1 | at
org.wso2.carbon.user.core.common.DefaultRealm.populateProfileAndClaimMaps(DefaultRealm.java:438)
store1 | at
org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:105)
store1 | at
org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:262)
store1 | at
org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:99)
store1 | at
org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:112)
store1 | at
org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:68)
store1 | at
org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
store1 | at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)

Any idea why is that happen? Is that happened as we starting the containers
at the same time?

Thanks,
Gayan
-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Dockerfiles] Managing Data Sources & JDBC Driver in Distributed Deployments

[Gayan Gunarathne]

I think we need to consider other Databases (Oracle,PostgreSQL etc) also.

Default[1] set up also we have hard corded to the h2 database. Better if we
support the other set of databases here also.Based on the database we used
we can set the appropriate DB driver with hiera.

[1]
https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2am/1.10.0/kubernetes/default.yaml#L101

Thanks,
Gayan

On Sat, Apr 23, 2016 at 8:25 AM, Imesh Gunaratne <im...@wso2.com> wrote:

> Hi Devs,
>
> How do we manage $subject in Puppet provisioning for Kubernetes?
>
> I can see that in API-M we have defined MySQL connector JAR [1] and data
> sources but not in others. We have also hard coded MySQL host IP [2] in
> API-M profile yaml files.
>
> [1]
> https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2am/1.10.0/kubernetes/api-key-manager.yaml#L36
> [2]
> https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2am/1.10.0/kubernetes/api-key-manager.yaml#L48
>
> Thanks
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.io TW: @imesh
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Handling Kubernetes Specific Configurations in Puppet/Hiera

[Gayan Gunarathne]

On Mon, Apr 11, 2016 at 12:39 PM, Lakmal Warusawithana <lak...@wso2.com>
wrote:

>
>
> On Mon, Apr 11, 2016 at 12:22 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>> Hi Chamila,
>>
>> On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis <chami...@wso2.com>
>> wrote:
>>
>>> Hi Isuru, Imesh,
>>>
>>> IMO we shouldn't have any platform specific restructuring in
>>> wso2/puppet-modules. This should be done at the end user's setup. Another
>>> point is that we have now decoupled wso2/puppet-modules from
>>> wso2/dockerfiles and users are not required to incorporate puppet-modules
>>> in their container setup.
>>>
>>
>> A very good concern! The way I see this is little different. Let's
>> evaluate the options we have:
>>
>>1. Ship generic product/profile Hiera YAML files and let the users
>>configure them according to their platform (VM, AWS, Azure, OpenStack, 
>> K8S,
>>Mesos, OpenShift, CF, etc)
>>2. Ship product/profile/platform Hiera YAML files and let users use
>>them OOB with very few changes.
>>
>> +1 for 2nd option. Yes, it has some duplication on configurations, but
> customer POV, it is very easy to look at single place to do the minimum
> changes. (rather looking for many files in deferent folders to do the
> changes)
>

I am also +1 for the 2nd option. But my concern is we can remove the
duplicates for configuration files by using the defined types with Hiera as
[1].

[1]http://puppetlunch.com/puppet/hiera.html


>
>
>
>
>> Which one would be the best option? IMO 2nd option would provide a much
>> better user experience compared to 1 as it provides platform specific
>> values such as clustering configuration & port mappings OOB. User will only
>> need to provide values such as database hosts, passwords, identity
>> management, etc which are user specific.
>>
>> The whole idea of this effort is to provide a better user experience.
>>
>> Thanks
>>
>>>
>>> IMO Docker images will not be able to run OOB on Kubernetes using
>>> wso2/puppet-modules and wso2/kubernetes-artifacts. There will anyway be
>>> changes related to the Kubernetes Membership Scheme in wso2/puppet-modules
>>> and in wso2/kubernetes-artifacts where environment dependent changes such
>>> as image names, SecureVault passwords, etc. need to be adjusted.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>> On Mon, Apr 11, 2016 at 1:36 AM, Imesh Gunaratne <im...@wso2.com> wrote:
>>>
>>>> Hi Gayan,
>>>>
>>>> On Sun, Apr 10, 2016 at 5:02 PM, Gayan Gunarathne <gay...@wso2.com>
>>>> wrote:
>>>>
>>>>> IMO this will create maintainability issue. We need to maintain all
>>>>> the separate hieradata structure for each scenarios.For the one particular
>>>>> alternation we need to change whole set of files.
>>>>>
>>>>
>>>> In this scenario user experience is much more important than the
>>>> maintainability of few yaml files. If we do not do this, users will not be
>>>> able to use puppet modules OOB until they manually update configuration
>>>> values in above files. The whole idea of this effort is to let users do
>>>> following:
>>>>
>>>>- Setup a K8S cluster
>>>>- Download puppet modules zip file(s).
>>>>- Download docker files
>>>>- Build docker images using puppet for different product profiles
>>>>- Deploy WSO2 product on K8S using K8S artifacts
>>>>
>>>> The above process will allow users to deploy any WSO2 product (with
>>>> mutlitple deployment patterns) on K8S with zero configurations. This will
>>>> be true for any VM based platform or any other container cluster management
>>>> system.
>>>>
>>>>>
>>>>> Why can't we do this by using defined types in Hiera and lookup
>>>>> parameters for a given instance? Based on the identify keys we set
>>>>> for each vm, docker, K8S etc we can select the appropriate data set
>>>>> from Hiera file.
>>>>>
>>>>
>>>> Will you be able to provide a sample?
>>>>
>&g

Re: [Dev] Handling Kubernetes Specific Configurations in Puppet/Hiera

[Gayan Gunarathne]

On Mon, Apr 11, 2016 at 12:39 PM, Lakmal Warusawithana <lak...@wso2.com>
wrote:

>
>
> On Mon, Apr 11, 2016 at 12:22 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>> Hi Chamila,
>>
>> On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis <chami...@wso2.com>
>> wrote:
>>
>>> Hi Isuru, Imesh,
>>>
>>> IMO we shouldn't have any platform specific restructuring in
>>> wso2/puppet-modules. This should be done at the end user's setup. Another
>>> point is that we have now decoupled wso2/puppet-modules from
>>> wso2/dockerfiles and users are not required to incorporate puppet-modules
>>> in their container setup.
>>>
>>
>> A very good concern! The way I see this is little different. Let's
>> evaluate the options we have:
>>
>>1. Ship generic product/profile Hiera YAML files and let the users
>>configure them according to their platform (VM, AWS, Azure, OpenStack, 
>> K8S,
>>Mesos, OpenShift, CF, etc)
>>2. Ship product/profile/platform Hiera YAML files and let users use
>>them OOB with very few changes.
>>
>> +1 for 2nd option. Yes, it has some duplication on configurations, but
> customer POV, it is very easy to look at single place to do the minimum
> changes. (rather looking for many files in deferent folders to do the
> changes)
>
>
>
>
>> Which one would be the best option? IMO 2nd option would provide a much
>> better user experience compared to 1 as it provides platform specific
>> values such as clustering configuration & port mappings OOB. User will only
>> need to provide values such as database hosts, passwords, identity
>> management, etc which are user specific.
>>
>> The whole idea of this effort is to provide a better user experience.
>>
>> Thanks
>>
>>>
>>> IMO Docker images will not be able to run OOB on Kubernetes using
>>> wso2/puppet-modules and wso2/kubernetes-artifacts. There will anyway be
>>> changes related to the Kubernetes Membership Scheme in wso2/puppet-modules
>>> and in wso2/kubernetes-artifacts where environment dependent changes such
>>> as image names, SecureVault passwords, etc. need to be adjusted.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>> On Mon, Apr 11, 2016 at 1:36 AM, Imesh Gunaratne <im...@wso2.com> wrote:
>>>
>>>> Hi Gayan,
>>>>
>>>> On Sun, Apr 10, 2016 at 5:02 PM, Gayan Gunarathne <gay...@wso2.com>
>>>> wrote:
>>>>
>>>>> IMO this will create maintainability issue. We need to maintain all
>>>>> the separate hieradata structure for each scenarios.For the one particular
>>>>> alternation we need to change whole set of files.
>>>>>
>>>>
>>>> In this scenario user experience is much more important than the
>>>> maintainability of few yaml files. If we do not do this, users will not be
>>>> able to use puppet modules OOB until they manually update configuration
>>>> values in above files. The whole idea of this effort is to let users do
>>>> following:
>>>>
>>>>- Setup a K8S cluster
>>>>- Download puppet modules zip file(s).
>>>>- Download docker files
>>>>- Build docker images using puppet for different product profiles
>>>>- Deploy WSO2 product on K8S using K8S artifacts
>>>>
>>>> The above process will allow users to deploy any WSO2 product (with
>>>> mutlitple deployment patterns) on K8S with zero configurations. This will
>>>> be true for any VM based platform or any other container cluster management
>>>> system.
>>>>
>>>
Mainly the target users group of the puppet/hiera files will be system
administrators/Dev Ops. So those guys will be consider the fact the
maintainability of puppet/hiera files. So if this is a maintainability
issue, it will become bad experience for the end user in end of the day.


>
>>>>> Why can't we do this by using defined types in Hiera and lookup
>>>>> parameters for a given instance? Based on the identify keys we set
>>>>> for each vm, docker, K8S etc we can select the appropriate data set
>>>>> from Hiera file.
>>>>>
>>>>
>>>> Will you be able t

Re: [Dev] Handling Kubernetes Specific Configurations in Puppet/Hiera

[Gayan Gunarathne]

IMO this will create maintainability issue. We need to maintain all the
separate hieradata structure for each scenarios.For the one particular
alternation we need to change whole set of files.

Why can't we do this by using defined types in Hiera and lookup parameters
for a given instance? Based on the identify keys we set for each vm,
docker, K8S etc we can select the appropriate data set from Hiera file.

Thanks,
Gayan


On Sat, Apr 9, 2016 at 8:28 AM, Imesh Gunaratne <im...@wso2.com> wrote:

>
> On Fri, Apr 8, 2016 at 7:48 PM, Isuru Haththotuwa <isu...@wso2.com> wrote:
>>
>>
>> hieradata
>> |--- dev
>>|--- wso2
>>| 
>>  |--- 
>>|-- *vm*
>> |--
>> default.yaml
>> |--
>> manager.yaml
>> |--
>> worker.yaml
>>|--* docker*
>> |--
>> default.yaml
>> |--
>> manager.yaml
>> |--
>> worker.yaml
>>|-- *kubernetes*
>>
>> |--
>> default.yaml
>> |--
>> manager.yaml
>> |--
>> worker.yaml
>>
>>
> +1 for the suggestion Isuru, will proceed with this. We can add other
> platforms such as OpenShift, Mesos, Cloud Foundry on the same level.
>
> Thanks
>
>>
>>
>> Thanks
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.io
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.io
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Running WSO2 Products on Cloud Foundry

[Gayan Gunarathne]

On Tue, Feb 9, 2016 at 9:55 AM, Malmee Weerasinghe <mal...@wso2.com> wrote:

> Hi All,
> As an initiative for the $subject I have deployed Cloud Foundry with BOSH
> Lite, have run some sample applications both in BOSH lite and Pivotal Cloud
> Foundry.
>
> BOSH Lite is a pre-built Vagrant box which includes the BOSH Director. BOSH
> Lite is used for developing and testing releases locally.
>
> Cloud Foundry is now owned by Pivotal software and Pivotal Cloud Foundry
> is a commercial implementation.
>
> I have written two blog posts as an introduction to Cloud Foundry [1] and
> Bosh and Bosh Lite in Cloud Foundry [2].
>
> As an approach to the $subject I am deploying tomcat server in Cloud
> Foundry and am expecting to replace the deployment with a WSO2 product
> (docker).
>

How do you going to deploy the server in Cloud foundry? Did you use
Buildpack? Also Did you check with Diego in the case of docker?

>
> Your suggestions on this subject are highly appreciated.
>
> [1]
> http://malmeeweerasinghe.blogspot.com/2016/02/introduction-to-cloud-foundry.html
> <http://malmeeweerasinghe.blogspot.com/2016/02/bosh-and-bosh-lite-in-cloud-foundry.html>
> [2]
> http://malmeeweerasinghe.blogspot.com/2016/02/bosh-and-bosh-lite-in-cloud-foundry.html
>
> Thanks
>
> --
> Malmee Weerasinghe
> WSO2 Intern
> mobile : (+94)* 71 7601905* |   email :   <dehan.vith...@aiesec.net>
> mal...@wso2.com
>
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Running WSO2 Products on Cloud Foundry

[Gayan Gunarathne]

On Tue, Feb 9, 2016 at 12:01 PM, Chamila De Alwis <chami...@wso2.com> wrote:

> Hi Nanduni,
>
> Wouldn't writing a custom buildpack (for each product) [1] allow us to
> deploy a given artifact on CloudFoundry? We'd have to write the detect,
> compile, and release scripts separately.
>
> Is there any difference between that approach and using Docker images?
>

Default that uses Warden for its container management. We can try with
heroka buildpack[1] to run the docker images.

[1] https://blog.docker.com/2013/05/heroku-buildpacks-on-docker/
[2] https://devcenter.heroku.com/articles/docker


> [1] - https://docs.cloudfoundry.org/buildpacks/custom.html
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Mon, Feb 8, 2016 at 9:00 AM, Nanduni Nimalsiri <nand...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> By now, I have managed to deploy applications in Cloud Foundry via,
>> 1. bosh-lite ( a vagrant VM that comes with pre-installed BOSH server or
>> Director)
>> 2. Hosted solutions such as Pivotal web services (pivotal.io)
>>
>> I deployed Tomcat server in Cloud Foundry as well. But I was not able to
>> deploy Docker in Cloud Foundry via Diego. It gives me some errors regarding
>> admin permissions.
>> I found that there are Heroku buildpacks on Docker and they are perfectly
>> compatible with Cloud Foundry too.
>>
>> [1] https://github.com/duglin/cf-docker
>> [1] is another buildpack that supports Docker, but there are several
>> limitations as this buildpack requires that you have a Docker host
>> available for it to access, and you need to also have a Docker container
>> manager app (cf-docker) running that will sync the Cloud Foundry runtime
>> with the Docker containers.
>>
>> My blog in the following link will be useful for any one to get an idea
>> on deploying applications in Cloud Foundry.
>> http://nanduni.blogspot.com/
>>
>> Best regards,
>> Nanduni.
>>
>>
>>
>> *Nanduni Nimalsiri*
>> Software Engineering Intern, WSO2 Inc. (http://wso2.com)
>> email : nand...@wso2.com
>> blog : http://nanduni.blogspot.com/
>> mobile : +94714114256
>>
>>
>> On Sun, Feb 7, 2016 at 11:49 PM, Malmee Weerasinghe <mal...@wso2.com>
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> I have done a background research on Cloud Foundry and the blog under
>>> the following link contains the documentation of the research. I will
>>> include more posts on deploying Cloud Foundry with bosh lite and running
>>> simple applications on it, as I have studied so far.
>>>
>>>
>>> http://malmeeweerasinghe.blogspot.com/2016/02/introduction-to-cloud-foundry.html
>>>
>>> Thanks
>>>
>>> On Fri, Feb 5, 2016 at 10:31 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Shall we summarize the research work we have done so far and our
>>>> approach towards $subject?
>>>>
>>>> I know some of us have already done below, it might be better to
>>>> document this:
>>>>
>>>>- PaaS features of CF
>>>>- Steps for setting up a local environment with Vagrant
>>>>- Running a hello world sample
>>>>- Running a JVM using a standalone framework
>>>>
>>>> Next we might need to check following:
>>>>
>>>> 1. The ability to use Docker on CF
>>>> 2. The process of creating and managing Warden container images
>>>> 3. Find a mechanism to discover the member list of a cluster and
>>>> implement a Carbon membership scheme
>>>> 4. Create standalone frameworks for Carbon products
>>>> 5. Find a way to apply patches and software updates
>>>> 6. Find a way to implement a centralized logging solution
>>>> 7. Check whether there is a way to monitor the health of the containers
>>>> (similar to cAdvisor and Cockpit UI in Kubernetes)
>>>> 8. Create artifacts required for deploying a Carbon server on CF and
>>>> prepare a guideline.
>>>>
>>>> [1]
>>>> https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme
>>>>
>>>>
>>>> Thanks
>>>>
>>>> --
>>>> *Imesh Gunaratne*
>>>> Senior Technical Lead
>>>> WSO2 Inc: http://wso2.com
>>>> T: +94 11 214 5345 M: +94 77 374 2057
>>>> W: http://imesh.io
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>
>>>
>>> --
>>> Malmee Weerasinghe
>>> WSO2 Intern
>>> mobile : (+94)* 71 7601905* |   email :   <dehan.vith...@aiesec.net>
>>> mal...@wso2.com
>>>
>>
>>
>> ___
>> 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
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Private PaaS 4.1.1 Released!

[Gayan Gunarathne]

on components.

Support

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support.

To learn more about WSO2 Private PaaS and WSO2 support offerings please
visit http://wso2.com/cloud/private-paas/


Thanks,

WSO2 Private PaaS Team



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][PPaaS]Puppet Modules - Use of MySQL datasources in the default.yaml

[Gayan Gunarathne]

ld change to point to the H2 database. WDYT?
>>>>>
>>>>> Regards,
>>>>> Chamila de Alwis
>>>>> Committer and PMC Member - Apache Stratos
>>>>> Software Engineer | WSO2 | +94772207163
>>>>> Blog: code.chamiladealwis.com
>>>>>
>>>>>
>>>>>
>>>>> _______
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Rajkumar Rajaratnam
>>>> Committer & PMC Member, Apache Stratos
>>>> Software Engineer, WSO2
>>>>
>>>> Mobile : +94777568639
>>>> Blog : rajkumarr.com
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Sajith Kariyawasam
>>> *Committer and PMC member, Apache Stratos, *
>>> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
>>> *Mobile: 0772269575*
>>>
>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Sajith Kariyawasam
> *Committer and PMC member, Apache Stratos, *
> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
> *Mobile: 0772269575*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC2

[Gayan Gunarathne]

Thank you for testing and verifying WSO2 Private PaaS 4.1.1 RC2.

We are closing this vote and this vote passes with
6(Thanuja,Akila,Raj,IsuruH,Pubudu,Imesh) +1 votes and 0 -1 votes.We will
proceed with the release of WSO2 Private PaaS 4.1.1.


On Thu, Dec 31, 2015 at 7:13 PM, Imesh Gunaratne <im...@wso2.com> wrote:

> +1 for the release! Verified Private PaaS 4.1.1-RC2 with following:
>
> - Verified application deployment & un-deployment on Kubernetes 1.0.6
> - Verified scaling up with high CPU
> - Verified scaling down
> - Verified UI functionality
>
> Thanks
>
> On Mon, Dec 21, 2015 at 7:35 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
>
>>  Hi All,
>>
>> This is the second release candidate of WSO2 Private PaaS 4.1.1.
>>
>> This release fixes the following issues:
>> *https://wso2.org/jira/browse/PAAS-305?filter=12582
>> <https://wso2.org/jira/browse/PAAS-305?filter=12582>*
>>
>> Please download, test and vote. The vote will be open for 72 hours or as
>> needed.
>>
>> *​Source and binary distribution files:*
>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc2/
>>
>> *Maven staging repository:*
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-217/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-private-paas/tree/v4.1.1-rc2
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thanks,
>> The WSO2 Private PaaS Team
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC2

[Gayan Gunarathne]

On Sun, Dec 27, 2015 at 10:00 AM, Akila Ravihansa Perera <raviha...@wso2.com
> wrote:

> Hi Gayan,
>
> Since we have forked Python cartridge agent in PPaaS 4.1.1-RC2, users
> won't be able to use Dockerfile shipped with Stratos to build cartridge
> images.
>
What do you mean by Dockerfile shipped with Stratos?


> Have we documented the steps needed to build cartridge Docker images for
> PPaaS?
>
We are released the Cartridges based on the PPaaS release version.
Currently released cartridges are compatible with PPaaS 4.1.0 release.With
the PPaaS 4.1.1 released our documentation need to be changed in the case
of user using the PPaaS 4.1.1 release

>
> Thanks.
>
> On Fri, Dec 25, 2015 at 12:06 AM, Gayan Gunarathne <gay...@wso2.com>
> wrote:
>
>> IMO if the vote is success we can simply move those binaries to the
>> product distribution without doing any alternation to those binaries.This
>> is the same as the staging repo. If the vote is success we promote the
>> staging repo , if it is fails we drop that staging repo.
>>
>> Thanks,
>> Gayan
>>
>> On Thu, Dec 24, 2015 at 11:47 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>>
>>>
>>> On Thu, Dec 24, 2015 at 10:41 PM, Gayan Gunarathne <gay...@wso2.com>
>>> wrote:
>>>
>>>> Hi Imesh,
>>>>
>>>> What is the ration behind that? I don't see any reason to prefix
>>>> binaries with the release candidate no. As those binaries will be the one
>>>> which move to the product release distribution if the vote is success,
>>>>
>>>> The only concern is once we do multiple release candidates, how would
>>> someone differentiate those if we have the same set of file names?
>>>
>>> Thanks
>>>
>>> Thanks,
>>>> Gayan
>>>>
>>>> On Thu, Dec 24, 2015 at 10:14 PM, Imesh Gunaratne <im...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Gayan,
>>>>>
>>>>> I think all the distributions should get prefixed with rc2, see
>>>>> 4.1.0-rc2:
>>>>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.0-rc2/
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Mon, Dec 21, 2015 at 7:35 PM, Gayan Gunarathne <gay...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>>  Hi All,
>>>>>>
>>>>>> This is the second release candidate of WSO2 Private PaaS 4.1.1.
>>>>>>
>>>>>> This release fixes the following issues:
>>>>>> *https://wso2.org/jira/browse/PAAS-305?filter=12582
>>>>>> <https://wso2.org/jira/browse/PAAS-305?filter=12582>*
>>>>>>
>>>>>> Please download, test and vote. The vote will be open for 72 hours
>>>>>> or as needed.
>>>>>>
>>>>>> *​Source and binary distribution files:*
>>>>>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc2/
>>>>>>
>>>>>> *Maven staging repository:*
>>>>>>
>>>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-217/
>>>>>>
>>>>>> *The tag to be voted upon:*
>>>>>> https://github.com/wso2/product-private-paas/tree/v4.1.1-rc2
>>>>>>
>>>>>>
>>>>>> [ ] Broken - do not release (explain why)
>>>>>> [ ] Stable - go ahead and release
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> The WSO2 Private PaaS Team
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Gayan Gunarathne
>>>>>> Technical Lead, WSO2 Inc. (http://wso2.com)
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Imesh Gunaratne*
>>>>> Senior Technical Lead
>>>>> WSO2 Inc: http://wso2.com
>>>>> T: +94 11 214 5345 M: +94 77 374 2057
>>>>> W: http://imesh.gunaratne.org
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Gayan Gunarathne
>>>> Technical Lead, WSO2 Inc. (http://wso2.com)
>>>> Committer & PMC Member, Apache Stratos
>>>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>> ___
>> 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
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC2

[Gayan Gunarathne]

Hi Imesh,

What is the ration behind that? I don't see any reason to prefix binaries
with the release candidate no. As those binaries will be the one which move
to the product release distribution if the vote is success,

Thanks,
Gayan

On Thu, Dec 24, 2015 at 10:14 PM, Imesh Gunaratne <im...@wso2.com> wrote:

> Hi Gayan,
>
> I think all the distributions should get prefixed with rc2, see 4.1.0-rc2:
> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.0-rc2/
>
> Thanks
>
> On Mon, Dec 21, 2015 at 7:35 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
>
>>  Hi All,
>>
>> This is the second release candidate of WSO2 Private PaaS 4.1.1.
>>
>> This release fixes the following issues:
>> *https://wso2.org/jira/browse/PAAS-305?filter=12582
>> <https://wso2.org/jira/browse/PAAS-305?filter=12582>*
>>
>> Please download, test and vote. The vote will be open for 72 hours or as
>> needed.
>>
>> *​Source and binary distribution files:*
>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc2/
>>
>> *Maven staging repository:*
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-217/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-private-paas/tree/v4.1.1-rc2
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thanks,
>> The WSO2 Private PaaS Team
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC2

[Gayan Gunarathne]

s/ration/rational/

On Thu, Dec 24, 2015 at 10:41 PM, Gayan Gunarathne <gay...@wso2.com> wrote:

> Hi Imesh,
>
> What is the ration behind that? I don't see any reason to prefix binaries
> with the release candidate no. As those binaries will be the one which move
> to the product release distribution if the vote is success,
>
> Thanks,
> Gayan
>
> On Thu, Dec 24, 2015 at 10:14 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>> Hi Gayan,
>>
>> I think all the distributions should get prefixed with rc2, see 4.1.0-rc2:
>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.0-rc2/
>>
>> Thanks
>>
>> On Mon, Dec 21, 2015 at 7:35 PM, Gayan Gunarathne <gay...@wso2.com>
>> wrote:
>>
>>>  Hi All,
>>>
>>> This is the second release candidate of WSO2 Private PaaS 4.1.1.
>>>
>>> This release fixes the following issues:
>>> *https://wso2.org/jira/browse/PAAS-305?filter=12582
>>> <https://wso2.org/jira/browse/PAAS-305?filter=12582>*
>>>
>>> Please download, test and vote. The vote will be open for 72 hours or
>>> as needed.
>>>
>>> *​Source and binary distribution files:*
>>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc2/
>>>
>>> *Maven staging repository:*
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-217/
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/product-private-paas/tree/v4.1.1-rc2
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>>
>>> Thanks,
>>> The WSO2 Private PaaS Team
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead, WSO2 Inc. (http://wso2.com)
>>> Committer & PMC Member, Apache Stratos
>>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead, WSO2 Inc. (http://wso2.com)
> Committer & PMC Member, Apache Stratos
> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>
>
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC2

[Gayan Gunarathne]

IMO if the vote is success we can simply move those binaries to the product
distribution without doing any alternation to those binaries.This is the
same as the staging repo. If the vote is success we promote the staging
repo , if it is fails we drop that staging repo.

Thanks,
Gayan

On Thu, Dec 24, 2015 at 11:47 PM, Imesh Gunaratne <im...@wso2.com> wrote:

>
>
> On Thu, Dec 24, 2015 at 10:41 PM, Gayan Gunarathne <gay...@wso2.com>
> wrote:
>
>> Hi Imesh,
>>
>> What is the ration behind that? I don't see any reason to prefix binaries
>> with the release candidate no. As those binaries will be the one which move
>> to the product release distribution if the vote is success,
>>
>> The only concern is once we do multiple release candidates, how would
> someone differentiate those if we have the same set of file names?
>
> Thanks
>
> Thanks,
>> Gayan
>>
>> On Thu, Dec 24, 2015 at 10:14 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>> Hi Gayan,
>>>
>>> I think all the distributions should get prefixed with rc2, see
>>> 4.1.0-rc2:
>>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.0-rc2/
>>>
>>> Thanks
>>>
>>> On Mon, Dec 21, 2015 at 7:35 PM, Gayan Gunarathne <gay...@wso2.com>
>>> wrote:
>>>
>>>>  Hi All,
>>>>
>>>> This is the second release candidate of WSO2 Private PaaS 4.1.1.
>>>>
>>>> This release fixes the following issues:
>>>> *https://wso2.org/jira/browse/PAAS-305?filter=12582
>>>> <https://wso2.org/jira/browse/PAAS-305?filter=12582>*
>>>>
>>>> Please download, test and vote. The vote will be open for 72 hours or
>>>> as needed.
>>>>
>>>> *​Source and binary distribution files:*
>>>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc2/
>>>>
>>>> *Maven staging repository:*
>>>>
>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-217/
>>>>
>>>> *The tag to be voted upon:*
>>>> https://github.com/wso2/product-private-paas/tree/v4.1.1-rc2
>>>>
>>>>
>>>> [ ] Broken - do not release (explain why)
>>>> [ ] Stable - go ahead and release
>>>>
>>>>
>>>> Thanks,
>>>> The WSO2 Private PaaS Team
>>>>
>>>> --
>>>>
>>>> Gayan Gunarathne
>>>> Technical Lead, WSO2 Inc. (http://wso2.com)
>>>> Committer & PMC Member, Apache Stratos
>>>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>>>
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC2

[Gayan Gunarathne]

 Hi All,

This is the second release candidate of WSO2 Private PaaS 4.1.1.

This release fixes the following issues:
*https://wso2.org/jira/browse/PAAS-305?filter=12582
<https://wso2.org/jira/browse/PAAS-305?filter=12582>*

Please download, test and vote. The vote will be open for 72 hours or as
needed.

*​Source and binary distribution files:*
https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc2/

*Maven staging repository:*

http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-217/

*The tag to be voted upon:*
https://github.com/wso2/product-private-paas/tree/v4.1.1-rc2


[ ] Broken - do not release (explain why)
[ ] Stable - go ahead and release


Thanks,
The WSO2 Private PaaS Team

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Private PaaS Cartridges v4.1.3 released

[Gayan Gunarathne]

Hi All,

The WSO2 Private PaaS community is pleased to announce the release of the
WSO2 Private PaaS Cartridges 4.1.3. This release includes cartridges for
the following WSO2 products.

 - WSO2 API Manager 1.9.1 cartridge
 - WSO2 Enterprise Service Bus 4.8.1 cartridge
 - WSO2 Enterprise Service Bus 4.9.0 cartridge
 - WSO2 Identity Server 5.0.0 cartridge
 - WSO2 Application Server 5.2.1 cartridge
 - WSO2 Application Server 5.3.0 cartridge
 - WSO2 Govenence Registry 5.0.0 cartridge
 - WSO2 Business Process Server 3.5.0 cartridge
 - WSO2 Business Rules Server 2.1.0 cartridge
 - WSO2 Governance Registry 5.0.0 cartridge
 - WSO2 Governance Registry 5.1.0 cartridge
 - WSO2 Data Services Server 3.2.2 cartridge
 - WSO2 Message Broker 3.0.0 cartridge
 - WSO2 Complex Event Processor 4.0.0 cartridge

Following are the newly added cartridges for this release
 - WSO2 Complex Event Processor 4.0.0 cartridge

Please note that above cartridges and Docker files are compatible with WSO2
Private PaaS 4.1.0 or higher releases.

Your feedback is most welcome. The distributions are available at [1]. Any
issues can be reported in [2].


[1]
https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-cartridges-4.1.3/
[2] https://wso2.org/jira/browse/PPC

Thanks,
WSO2 Private PaaS Team

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC1

[Gayan Gunarathne]

This vote has been cancelled due to CEP 3.0.0 artifacts issue and will
start a RC2 release with those fixes.

Thanks,
Gayan

On Fri, Dec 18, 2015 at 11:05 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi All,
>
> Private PaaS distribution pack is missing cep artifacts because in ppaas
> distribution assembly [1] we are referring those artifacts from ppaas cep
> extension which has been removed from ppaas repo. Ideally we should refer
> these cep artifacts in [1] from Stratos [2].
>
> [1].
> https://github.com/wso2/product-private-paas/blob/release-4.1.1/products/ppaas/modules/distribution/src/assembly/bin.xml#L430-L463
>
> [2].
> https://github.com/apache/stratos/tree/stratos-4.1.x/extensions/cep/modules/artifacts/wso2cep-3.0.0
>
> Thanks.
>
> On Wed, Dec 16, 2015 at 11:32 AM, Gayan Gunarathne <gay...@wso2.com>
> wrote:
>
>>  Hi All,
>>
>> This is the first release candidate of WSO2 Private PaaS 4.1.1.
>>
>> This release fixes the following issues:
>> *https://wso2.org/jira/browse/PAAS-305?filter=12582
>> <https://wso2.org/jira/browse/PAAS-305?filter=12582>*
>>
>> Please download, test and vote. The vote will be open for 72 hours or as
>> needed.
>>
>> *​Source and binary distribution files:*
>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc1/
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-181/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-private-paas/tree/v4.1.1-rc1
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thanks,
>> The WSO2 Private PaaS Team
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC1

[Gayan Gunarathne]

 Hi All,

This is the first release candidate of WSO2 Private PaaS 4.1.1.

This release fixes the following issues:
*https://wso2.org/jira/browse/PAAS-305?filter=12582
<https://wso2.org/jira/browse/PAAS-305?filter=12582>*

Please download, test and vote. The vote will be open for 72 hours or as
needed.

*​Source and binary distribution files:*
https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc1/

*Maven staging repository:*
http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-181/

*The tag to be voted upon:*
https://github.com/wso2/product-private-paas/tree/v4.1.1-rc1


[ ] Broken - do not release (explain why)
[ ] Stable - go ahead and release


Thanks,
The WSO2 Private PaaS Team

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] Need to update the Cartridges to support latest Stratos PCA

[Gayan Gunarathne]

On Tue, Dec 15, 2015 at 9:35 AM, Imesh Gunaratne <im...@wso2.com> wrote:

> Hi Gayan,
>
> It looks like this modification in cartridge agent is not backward
> compatible [1]. As a result users will need to upgrade all the existing
> cartridges to their latest versions to work with Private PaaS 4.1.1.
>
> IMO we need to fix first.
>
> [1]
> https://github.com/apache/stratos/commit/9c57c7d803f790078963861e553e5b79290d8f2d
>

Yeah . We need to support MB IP and MB port in the case of that
configurations are there.

>
> Thanks
>
> On Mon, Dec 14, 2015 at 7:38 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
>
>> We found that we need to update the Cartridges to support the Stratos
>> Cartridge Agent 4.1.5.We need to update the startup handlers,sample
>> artifact json to support the ActiveMQ HA with WSO2 Cartridges.
>>
>> We will fix those changes and will do the WSO2 PPaaS Cartridges 4.1.3
>> release.
>>
>> [1]
>> https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.9.0/plugins/wso2esb-490-startup-handler.py#L76
>> [2]
>> https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.9.0/samples/kubernetes-clusters/kubernetes-cluster-1.json#L36
>>
>> Thanks,
>> Gayan
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [PPaaS] Need to update the Cartridges to support latest Stratos PCA

[Gayan Gunarathne]

We found that we need to update the Cartridges to support the Stratos
Cartridge Agent 4.1.5.We need to update the startup handlers,sample
artifact json to support the ActiveMQ HA with WSO2 Cartridges.

We will fix those changes and will do the WSO2 PPaaS Cartridges 4.1.3
release.

[1]
https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.9.0/plugins/wso2esb-490-startup-handler.py#L76
[2]
https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.9.0/samples/kubernetes-clusters/kubernetes-cluster-1.json#L36

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PPaaS Artifact Migration Tool

[Gayan Gunarathne]

Great stuff. This is a really important tool in the case of Private PaaS
migration.

As per the README[1] it mention as "Add the default values to the templates
folder, if needed".I am not clear on that? Are we packing the 4.1.0
artifacts templates with the artifact migration tool? So user need to put
the default values for those artifacts?

[1]
https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/README

Thanks,
Gayan

On Fri, Dec 4, 2015 at 2:51 PM, Nishadi Kirielle <nish...@wso2.com> wrote:

> Hi All,
>
> Currently,we are engaged in developing an artifact migration tool to be
> used to fetch the artifact json files from PPaaS 4.0.0 REST API endpoints
> and convert them to be compatible with PPaaS 4.1.0. [1]
>
> We have implemented the conversions for the following artifacts ;
>- auto scale policy artifacts
>- network partition list artifacts
>- deployment policy artifacts
>- cartridge artifacts
>
> Now we are implementing the conversion of cartridge subscription
> artifacts to application signups and domain mapping subscriptions.
>
> Please raise if there are any concerns regarding this work.
>
> [1]
> https://github.com/nishadi/product-private-paas/tree/master/tools/migration/ppaas-artifact-converter
>
> Thanks
> Nishadi
>
> --
> Nishadi Kirielle
> *Software Engineering Intern*
> Mobile : +94 (0) 714722148
> nish...@wso2.com
>
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Locating the Artifact Converter Tool in WSO2 Product-Private-PaaS Repo

[Gayan Gunarathne]

On Tue, Dec 1, 2015 at 4:46 PM, Imesh Gunaratne <im...@wso2.com> wrote:

> Shall we have something like below:
>
> └── tools
> └── migration
> ├── artifact-converter
> └── subcription-manager
>

I think it is a subscription-converter not subscription-manager.It will
convert the 4.0.0 subscriptions to the 4.1.0. So shall we call it as
subscription-converter?

>
> @Akila: We might need to rename the existing subscription management tool.
>
> Thanks
>
> On Tue, Dec 1, 2015 at 3:37 PM, Malmee Weerasinghe <mal...@wso2.com>
> wrote:
>
>> Hi Akila,
>> We need to locate the Artifact Converter Tool which converts PPaaS 4.0.0
>> artifacts to PPaaS 4.1.0, in Product-Private-PaaS Repo.
>>
>> As Artifact Converter Tool and paas-migration/4.0.0 tool have quite
>> similar functionality, can we create a new folder in 'tools' and move
>> paas-migration/4.0.0 tool to it and locate together with Artifact
>> Converter Tool. Do you have any suggestions?
>>
>> Thank you
>> --
>> Malmee Weerasinghe
>> WSO2 Intern
>> mobile : (+94)* 71 7601905* |   email :   <dehan.vith...@aiesec.net>
>> mal...@wso2.com
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Locating the Artifact Converter Tool in WSO2 Product-Private-PaaS Repo

[Gayan Gunarathne]

On Tue, Dec 1, 2015 at 6:46 PM, Akila Ravihansa Perera <raviha...@wso2.com>
wrote:

> Hi,
>
> +1 for the proposed folder structure.
>
> @Gayan: Currently that tool only exports existing cartridge subscriptions
> and domain mappings. It doesn't do any conversion or migration (although it
> is called migration-tool);
>

In that case, if we put this under tools/migration it will be misleading
for the end user.


> which is why it should be renamed to subscription-manager. I actually
> prefer the name "subscription-exporter". We had to create an external tool
> since regular API didn't have any methods to expose those information. We
> should include those API methods to the regular API in the new PPaaS
> release.
>
> @Malmee: I've restructured the folder structure in [1]. You can create a
> new folder named "artifact-converter" at tools/migration/ to host your
> tool. Please send a PR with those changes.
>
> On a side note; does your tool support converting cartridge subscription
> artifacts to application signups and domain mapping subscriptions?
>
> [1]
> https://github.com/wso2/product-private-paas/tree/master/tools/migration
>
> Thanks.
>
> On Tue, Dec 1, 2015 at 6:23 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>>
>>
>> On Tue, Dec 1, 2015 at 5:23 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
>>
>>>
>>> On Tue, Dec 1, 2015 at 4:46 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>>
>>>> Shall we have something like below:
>>>>
>>>> └── tools
>>>> └── migration
>>>> ├── artifact-converter
>>>> └── subcription-manager
>>>>
>>>
>>> I think it is a subscription-converter not subscription-manager.It will
>>> convert the 4.0.0 subscriptions to the 4.1.0. So shall we call it as
>>> subscription-converter?
>>>
>>
>> AFAIK it does not convert subscriptions, it just export them.
>>
>> Thanks
>>
>>>
>>>> @Akila: We might need to rename the existing subscription management
>>>> tool.
>>>>
>>>> Thanks
>>>>
>>>> On Tue, Dec 1, 2015 at 3:37 PM, Malmee Weerasinghe <mal...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Akila,
>>>>> We need to locate the Artifact Converter Tool which converts PPaaS
>>>>> 4.0.0 artifacts to PPaaS 4.1.0, in Product-Private-PaaS Repo.
>>>>>
>>>>> As Artifact Converter Tool and paas-migration/4.0.0 tool have quite
>>>>> similar functionality, can we create a new folder in 'tools' and move
>>>>> paas-migration/4.0.0 tool to it and locate together with Artifact
>>>>> Converter Tool. Do you have any suggestions?
>>>>>
>>>>> Thank you
>>>>> --
>>>>> Malmee Weerasinghe
>>>>> WSO2 Intern
>>>>> mobile : (+94)* 71 7601905* |   email :   <dehan.vith...@aiesec.net>
>>>>> mal...@wso2.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Imesh Gunaratne*
>>>> Senior Technical Lead
>>>> WSO2 Inc: http://wso2.com
>>>> T: +94 11 214 5345 M: +94 77 374 2057
>>>> W: http://imesh.gunaratne.org
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead, WSO2 Inc. (http://wso2.com)
>>> Committer & PMC Member, Apache Stratos
>>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>>
>>>
>>>
>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> 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
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Private PaaS Cartridges v4.1.2 released

[Gayan Gunarathne]

Hi All,

The WSO2 Private PaaS community is pleased to announce the release of the
WSO2 Private PaaS Cartridges 4.1.2. This release includes cartridges for
the following WSO2 products.

 - WSO2 API Manager 1.9.1 cartridge
 - WSO2 Enterprise Service Bus 4.8.1 cartridge
 - WSO2 Enterprise Service Bus 4.9.0 cartridge
 - WSO2 Identity Server 5.0.0 cartridge
 - WSO2 Application Server 5.2.1 cartridge
 - WSO2 Application Server 5.3.0 cartridge
 - WSO2 Govenence Registry 5.0.0 cartridge
 - WSO2 Business Process Server 3.5.0 cartridge
 - WSO2 Business Rules Server 2.1.0 cartridge
 - WSO2 Governance Registry 5.0.0 cartridge
 - WSO2 Governance Registry 5.1.0 cartridge
 - WSO2 Data Services Server 3.2.2 cartridge
 - WSO2 Message Broker 3.0.0 cartridge


Following are the newly added cartridges for this release
 - WSO2 Enterprise Service Bus 4.9.0 cartridge
 - WSO2 Application Server 5.3.0 cartridge
 - WSO2 Governance Registry  5.1.0 cartridge


Please note that above cartridges and Docker files are compatible with WSO2
Private PaaS 4.1.0 or higher releases.

Your feedback is most welcome. The distributions are available at [1]. Any
issues can be reported in [2].


[1]
https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-cartridges-4.1.2/
[2] https://wso2.org/jira/browse/PPC

Thanks,
WSO2 Private PaaS Team


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] Unable to build Released Docker base image Pack

[Gayan Gunarathne]

Hi Reka,

On Wed, Nov 11, 2015 at 10:28 AM, Reka Thirunavukkarasu <r...@wso2.com>
wrote:

> Hi
>
> Due to the docker base image pack[1] is referred to relative path from the
> product distribution for such as configurator and etc, we can't build and
> get the docker base image.
>


> Can we fix this for 4.1.2 cartridges release? Also, it would be better, if
> the docker image could be built even without phython agent as in
> standalone, python agent is not needed. So, it is an additional step to
> download python agent and locate it in the docker image for a standalone
> docker image user. WDYT?
>
> [1]
> http://product-dist.wso2.com/downloads/private-paas/4.1.0/cartridges/common/wso2ppaas-cartridges-docker-base-image-4.1.1.zip
>

In 4.1.2 , user need to put the configurator in the packages folder. If
user needs to build it from the already build one from the same repo, he
needs to pass additional input parameter -b.[1]

[1]
https://github.com/wso2/private-paas-cartridges/tree/master/common/docker/base-image

Thanks,
Gayan


>
>
> Thanks,
> Reka
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [PPaaS] Docker base image creation scirpt

[Gayan Gunarathne]

The command that we used to retrieve the configurator_version is not
working as we don't have a pom in the base-image.May be we get
the configurator_version from parent pom and but seems that command is not
working when we point to the parent pom.We may not need to read
this configurator_version from the pom?

[1]
https://github.com/wso2/private-paas-cartridges/blob/master/common/docker/base-image/build.sh#L25

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPAAS] Introducing new WSO2 cartridges for PPAAS

[Gayan Gunarathne]

On Mon, Nov 9, 2015 at 10:31 AM, Malaka Silva <mal...@wso2.com> wrote:

> Are we planning to host these on store?
>
> https://store.wso2.com/store/
>

Yes Malaka, We are in the process of hosting the PPaaS cartridges 4.1.1 to
the store. After that we will host this cartridges as well.



>
> On Sun, Nov 8, 2015 at 9:58 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
>
>>
>>
>> On Sun, Nov 8, 2015 at 2:42 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>> Great work team!!
>>>
>>> Please make a new release in cartridges repository:
>>> https://github.com/wso2/private-paas-cartridges/releases
>>>
>>
>> +1. We will do the PPaaS Cartridges 4.1.2 release.
>>
>>>
>>> Thanks
>>>
>>> On Sat, Nov 7, 2015 at 12:58 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> We have introduced following set of new cartridges for WSO2 Private
>>>> PaaS compatible with version 4.1.0 or higher.
>>>>
>>>>  - WSO2 ESB 4.9.0 cartridge
>>>>  - WSO2 AS 5.3.0 cartridge
>>>>  - WSO2 GREG 5.1.0 cartridge
>>>>
>>>> These cartridges support worker manager deployments on EC2, OpenStack
>>>> and Kubernetes. Private PaaS membership scheme can be used for clustering.
>>>>
>>>> Thanks.
>>>>
>>>> --
>>>> Akila Ravihansa Perera
>>>> WSO2 Inc.;  http://wso2.com/
>>>>
>>>> Blog: http://ravihansa3000.blogspot.com
>>>>
>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Private PaaS 4.1.0 EC2 Demo AMI

[Gayan Gunarathne]

Hi Akila,

On Thu, Nov 5, 2015 at 11:44 AM, Akila Ravihansa Perera <raviha...@wso2.com>
wrote:

> Hi Gayan,
>
> Please see my answers inline.
>
> 1. How can user select the products that user need to deploy with the
>> PPaaS?
>>
>
> All cartridges released with Private PaaS cartridges 4.1.1 are added at
> the instance startup. But the applications are not deployed (will be in
> CREATED state). It is up to the user to login to the console and deploy the
> apps as desired.
>

>
>> 2. Are we using embedded CEP for health stats publishing?Can user select
>> to external cep?
>>
>
> It is currently configured in single JVM mode with embedded CEP. Since
> this is only a demo instance, no need to go for an external CEP I think.
>

>
>> 3. AFAIR DAS is running in the same PPaaS instance.How can user enable
>> disable the DAS metering and monitoring stuff?
>>
>
> DAS is running in the same instance with a port offset. It is enabled by
> default. Since this is a demo AMI it is better to showcase all possible
> features we have.
>
>
>>
>> May be we can have the demo image for only one region and if someone
>> needs in the other region he can copy from there.
>>
>
> Yes, but I'm not sure whether AMIs can be directly copied from a region to
> another region.
>

This is possible. We can able to copy the images from one region to
another.

Anyway it  is only a matter of copying those script files and artifacts to
> create a demo AMI.
>
> Thanks.
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Private PaaS 4.1.0 EC2 Demo AMI

[Gayan Gunarathne]

Great Stuff AKila!

I have some questions

1. How can user select the products that user need to deploy with the PPaaS?
2. Are we using embedded CEP for health stats publishing?Can user select to
external cep?
3. AFAIR DAS is running in the same PPaaS instance.How can user enable
disable the DAS metering and monitoring stuff?

May be we can have the demo image for only one region and if someone needs
in the other region he can copy from there.

Thanks,
Gayan

On Wed, Nov 4, 2015 at 8:17 PM, Akila Ravihansa Perera <raviha...@wso2.com>
wrote:

> Hi,
>
> I've created an EC2 AMI preconfigured with WSO2 Private PaaS 4.1.0 and
> WSO2 cartridges. The demo AMI contains init scripts to configure PPaaS,
> ActiveMQ and Nginx load-balancer extension. You need to pass PPaaS specific
> parameters as user data when launching this demo AMI and the init script
> will configure the products, deploy artifacts and cartridges.
> It will also configure WSO2 DAS with PPaaS gadgets which is used to
> provide monitoring and metering related information.
>
>  This will be a very convenient method for users to get started with
> Private PaaS since it reduces most of the configuration related tasks. I've
> written a blog post [1] explaining how to setup WSO2 Private PaaS 4.1.0
> with this demo AMI.
>
> [1]
> http://blog.ravihansa3000.com/2015/11/deploying-wso2-private-paas-410-using.html
>
> Thanks.
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BAM cron job shedule less below one minute

[Gayan Gunarathne]

I think first we need to consider the processing time of the job and
schedule the job accordingly.Otherwise it will make some impact of the end
result also.

Thanks,
Gayan

On Sat, Oct 31, 2015 at 10:44 PM, Sinthuja Ragendran <sinth...@wso2.com>
wrote:

> Hi Udara,
>
> AFAIK there is no such limitation as you cannot configure the cron below 1
> minute, can you please share the doc link where it's stated as such? And
> your cron expression is correct and this will work in BAM, this will
> trigger every 30 seconds as explained in quartz docs.
>
> Thanks,
> Sinthuja.
>
> On Sat, Oct 31, 2015 at 5:01 PM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Hi,
>>
>> As mentioned in docs, smallest time gap a cron job can be is 1 minute.
>> However when I set below as cron expression it seems to run the cron job
>> every 30 second. Is this expected behavior?
>>
>> 0/30 * * * * *
>>
>> However according to quartz docs [1], it supports seconds too.
>>
>> [1]
>> http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/tutorial-lesson-06
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>
>
>
> --
> *Sinthuja Rajendran*
> Associate Technical Lead
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.0 RC2

[Gayan Gunarathne]

Verified the followings.

1. PPaaS installer
2. Application deployment using mock Iaas  and Kubernetes
3. Application un-deployment
4. Products configuration generation using the Configurator.
5. Product clustering using the PPaaS membership scheme

[x] Stable - go ahead and release

Thanks,
Gayan

On Sat, Oct 24, 2015 at 2:33 PM, Akila Ravihansa Perera <raviha...@wso2.com>
wrote:

> Tested samples apps on ec2 and Kubernetes platforms.
>
> [x] Stable - go ahead and release
>
> On Wed, Oct 21, 2015 at 11:00 AM, Gayan Gunarathne <gay...@wso2.com>
> wrote:
>
>> Hi All,
>>
>> Please find the release candidate of the WSO2 PPaaS cartridges related
>> to the WSO2 Private PaaS 4.1.0.
>>
>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-cartridges-4.1.1/
>>
>> Please use these set of Cartridges to test the WSO2 Private PaaS 4.1.0
>> release.
>>
>> Thanks,
>> Gayan
>>
>> On Wed, Oct 21, 2015 at 8:05 AM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the second release candidate of WSO2 Private PaaS 4.1.0.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12467
>>>
>>> Please download, test and vote. The vote will be open for 72 hours or as
>>> needed.
>>>
>>> *​Source and binary distribution files:*
>>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.0-rc2/
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-028/
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/product-private-paas/tree/v4.1.0-rc2
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>>
>>> Thanks,
>>> The WSO2 Private PaaS Team
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>> ___
>> 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
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Configurator does not give priority to env variables

[Gayan Gunarathne]

So what is the usage of the "module.ini"? We can live with only the
environment parameters.

If the module.ini is for the default values, why are we having default
values in the template it self.We are checking whether that value is
defined. If that is not define we are setting the default value.

[1]
https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.8.1/template-module/templates/repository/conf/datasources/master-datasources.xml.template#L8

Thanks,
Gayan

On Sat, Oct 24, 2015 at 10:00 PM, Imesh Gunaratne <im...@wso2.com> wrote:

> Hi Devs,
>
> I noticed $subject if the same variable has been defined in module.ini.
>
> IMO this is not correct. We need to be able to configure any parameter
> using environment variables without touching the module.ini.
>
> Thanks
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Missing links in WSO2 docker hub

[Gayan Gunarathne]

There are some missing github repo links with the WSO2 docker hub pages[1].
Shall we link those to the master branch until  we do the PPaaS Cartridge
release?

[1]https://hub.docker.com/r/wso2/as-5.2.1/

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.0 RC1

[Gayan Gunarathne]

cationAdminStub(authenticationWSUrl);
>>> authenticationAdminStub.login(credentials[0], credentials[1],
>>> LOCALHOST);
>>> var serviceContext =
>>> authenticationAdminStub._getServiceClient().getLastOperationContext()
>>> .getServiceContext();
>>> var sessionCookie =
>>> serviceContext.getProperty(HTTPConstants.COOKIE_STRING);
>>> options.setProperty(HTTPConstants.COOKIE_STRING, sessionCookie);
>>> } else {
>>> var token = session.get(AUTH_TOKEN);
>>> if (token != null) {
>>> options.setProperty(HTTPConstants.COOKIE_STRING, token);
>>> } else {
>>> log.error("user is not authenticated!");
>>> response.status = HTTP_USER_NOT_AUTHENTICATED;
>>> print('{ "status": "Failed", "message": "User is not
>>> authenticated." }');
>>> return;
>>> }
>>> }
>>>
>>> In addition we may need to avoid concatenating table names in SQL
>>> queries.
>>>
>>> [1]
>>> https://github.com/wso2/product-private-paas/tree/v4.1.0-rc1/extensions/das/artifacts/metering-dashboard/jaggery-files
>>> [2]
>>> https://github.com/wso2/product-private-paas/tree/v4.1.0-rc1/extensions/das/artifacts/monitoring-dashboard/jaggery-files
>>> [3]
>>> https://github.com/wso2/carbon-dashboards/blob/master/apps/portal/controllers/apis/analytics.jag#L88
>>>
>>> I think we may need to cancel this vote and do RC2 by fixing these
>>> problems.
>>>
>>> Thanks
>>>
>>> On Tue, Oct 20, 2015 at 5:02 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> This is the first release candidate of WSO2 Private PaaS 4.1.0.
>>>>
>>>> This release fixes the following issues:
>>>> https://wso2.org/jira/issues/?filter=12464
>>>>
>>>> Please download, test and vote. The vote will be open for 72 hours or
>>>> as needed.
>>>>
>>>> *​Source and binary distribution files:*
>>>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.0-rc1
>>>>
>>>> *Maven staging repository:*
>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-027/
>>>>
>>>> *The tag to be voted upon:*
>>>> https://github.com/wso2/product-private-paas/tree/v4.1.0-rc1
>>>>
>>>>
>>>> [ ] Broken - do not release (explain why)
>>>> [ ] Stable - go ahead and release
>>>>
>>>>
>>>> Thanks,
>>>> The WSO2 Private PaaS Team
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.0 RC2

[Gayan Gunarathne]

Hi All,

Please find the release candidate of the WSO2 PPaaS cartridges related to
the WSO2 Private PaaS 4.1.0.

https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-cartridges-4.1.1/

Please use these set of Cartridges to test the WSO2 Private PaaS 4.1.0
release.

Thanks,
Gayan

On Wed, Oct 21, 2015 at 8:05 AM, Imesh Gunaratne <im...@wso2.com> wrote:

> Hi Devs,
>
> This is the second release candidate of WSO2 Private PaaS 4.1.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12467
>
> Please download, test and vote. The vote will be open for 72 hours or as
> needed.
>
> *​Source and binary distribution files:*
> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.0-rc2/
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-028/
>
> *The tag to be voted upon:*
> https://github.com/wso2/product-private-paas/tree/v4.1.0-rc2
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thanks,
> The WSO2 Private PaaS Team
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [PPaaS] PPaaS template modules

[Gayan Gunarathne]

Hi All,

Now we have updated the PPaaS template modules in WSO2 PPaaS cartridge
repo[1]. Those can be used to configure the PPaaS installation.

[1]
https://github.com/wso2/private-paas-cartridges/tree/master/wso2ppaas/4.1.0

Thanks,
Gayan


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppFactory] How to maintain Docker images used in App Factory

[Gayan Gunarathne]

Hi Punnadi,

Can't we use existing WSO2 docker images that we already have? As for your
docker file , it is same as PPaaS. What are the customization we have done
for AppFactory?

My concern is we already have set of docker images in WSO2 docker hub for
WSO2 products[1].So if we have another set of docker images for same
products set, it will be confuse for the end user.

[1]https://hub.docker.com/u/wso2/dashboard/

Thanks,
Gayan


On Wed, Oct 7, 2015 at 9:29 PM, Danushka Fernando <danush...@wso2.com>
wrote:

> I guess in some meeting we discussed to do it right? So +1. We can release
> the image to dockerhub when we release AF.
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> On Wed, Oct 7, 2015 at 8:43 PM, Amalka Subasinghe <ama...@wso2.com> wrote:
>
>> +1
>>
>> On Wed, Oct 7, 2015 at 7:49 PM, Punnadi Gunarathna <punn...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> Shall we have our own space for AppFactory in DockerHub and upload the
>>> WSO2AS image and the other images we have created so far with custom
>>> changes?
>>> I think we will can use the existing Dockerfile [1] in WSO2AS (and for
>>> other image types also) and we just have to change the values passed to the
>>> below command in build.sh to differentiate it as a WSO2AS image with custom
>>> changes made for App Factory deployment.
>>> docker build -t wso2/${wso2_product_type}:${wso2_product_version}
>>>
>>> This way we can release the images in parallel with the product releases
>>> as well.WDYT?
>>>
>>> [1]
>>> https://github.com/punnadih/product-private-paas/blob/master/cartridges/docker/wso2as-5.2.1/Dockerfile
>>> --
>>>
>>> Thanks and Regards,
>>>
>>> Punnadi Gunarathna
>>> Senior Software Engineer,
>>> WSO2, Inc.; http://wso2.com <http://wso2>
>>> Blog: http://hi-my-world.blogspot.com/
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>>
>>> <http://lalajisureshika.blogspot.com/>
>>>
>>
>>
>>
>> --
>> Amalka Subasinghe
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile: +94 77 9401267
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] PPaaS 4.1.0 installer

[Gayan Gunarathne]

Yeah. We need to consider external CEP/DAS.

Installer will ask whether user need to setup CEP/DAS as a separate
service? If user input as it needs to be external service, installer will
configure the CEP/DAS as external services.

Thanks,
Gayan


On Wed, Oct 7, 2015 at 2:26 AM, Lasindu Charith <lasi...@wso2.com> wrote:

> Hi Imesh,
>
> On Mon, Oct 5, 2015 at 11:03 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>> On Tue, Oct 6, 2015 at 12:09 AM, Gayan Gunarathne <gay...@wso2.com>
>>  wrote:
>>>
>>>
>>> PPaaS installer will setup the private paas. Main responsibility of that
>>> installer will be setup the db, ActiveMQ and Private PaaS and start the
>>> Private PaaS server.
>>>
>>
>> We may also need to configure CEP and DAS.
>>
>
> Yes, there should be an option to have CEP/DAS separately. From the
> installer do we only ask to point the external CEP/DAS ip addresses or will
> the installer take care of the configuration of CEP/DAS as well? (similar
> to configuring puppet master)
>
>
>> Thanks
>>
>> On Tue, Oct 6, 2015 at 12:09 AM, Gayan Gunarathne <gay...@wso2.com>
>> wrote:
>>
>>>
>>> Hi All,
>>>
>>> We are planing to have two installers with the PPaaS 4.1.0. Our idea
>>> behind that is to make the PPaaS setup and the cartridge deployment to be
>>> loosely coupled.
>>>
>>> +1
>
>> PPaaS installer will setup the private paas. Main responsibility of that
>>> installer will be setup the db, ActiveMQ and Private PaaS and start the
>>> Private PaaS server.
>>>
>>
> I think this is for PPaaS running in a single instance. Since we may not
> recommend to use installer in production, we need not to support
> distributed deployment of PPaaS in the installer. But as Imesh has
> mentioned, we would need to support CEP/DAS running externally.
>
>
>>
>>> PPaaS cartridges installer will be to deploy the Private PaaS
>>> cartridges.Main responsibility of this will be deploy the cartridges.Mainly
>>> It will carry out the following tasks,
>>>
>>> - Obtain the user input on deployment product and environment
>>> - If it is vm,
>>>   set up the puppet master ,set up the packs , template module and
>>> plugins to right location
>>> - If it is kubenetes cluster,
>>>pull the docker images for nodes/or build the docker image
>>> locally and transfer to the Kubernetes cluster nodes based on the user input
>>> - Execute configurator to configure the samples
>>> - Update the deployment artifacts based on the user inputs and
>>> initialized the deployment process through Rest API.
>>>
>>> We will maintain and release those two installers separately.
>>>
>>> Please share your thoughts and suggestions on this.
>>>
>>> Thanks,
>>> Gayan
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead, WSO2 Inc. (http://wso2.com)
>>> Committer & PMC Member, Apache Stratos
>>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>>
>>>
>>>
>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> Thanks,
> --
> *Lasindu Charith*
> Software Engineer, WSO2 Inc.
> Committer & PMC Member, Apache Stratos
> Mobile: +94714427192 | Web: blog.lasindu.com
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [PPaaS] PPaaS 4.1.0 installer

[Gayan Gunarathne]

Hi All,

We are planing to have two installers with the PPaaS 4.1.0. Our idea behind
that is to make the PPaaS setup and the cartridge deployment to be loosely
coupled.

PPaaS installer will setup the private paas. Main responsibility of that
installer will be setup the db, ActiveMQ and Private PaaS and start the
Private PaaS server.

PPaaS cartridges installer will be to deploy the Private PaaS
cartridges.Main responsibility of this will be deploy the cartridges.Mainly
It will carry out the following tasks,

- Obtain the user input on deployment product and environment
- If it is vm,
  set up the puppet master ,set up the packs , template module and
plugins to right location
- If it is kubenetes cluster,
   pull the docker images for nodes/or build the docker image locally
and transfer to the Kubernetes cluster nodes based on the user input
- Execute configurator to configure the samples
- Update the deployment artifacts based on the user inputs and initialized
the deployment process through Rest API.

We will maintain and release those two installers separately.

Please share your thoughts and suggestions on this.

Thanks,
Gayan






-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

[Gayan Gunarathne]

On Thu, Oct 1, 2015 at 6:06 PM, Reka Thirunavukkarasu <r...@wso2.com> wrote:

> Hi
>
> Shall we maintain an installer as well(specially for VM cartridges) in
> this repository to quickly create specific cartridges in puppet? What this
> installer could do is,
>
> User has to provide the packs and set of values for the environment
> variables.
>
> - Install puppet master
> - Locate the relevant cartridges puppet modules
> - Place the packs, template modules and plugins to right location
> - Export all the user given environment variables
> - Execute configurator to configure the samples
>
> WDYT?
>

Good thought reka. As our offline chat , we can plan to have two installers
for ppaas and ppaas cartridges.We can have the ppaas installer to set up
the ppaas related stuff while ppaas cartridge installer to set up the
cartridge specific installations.

>
> Thanks,
> Reka
>
> On Thu, Oct 1, 2015 at 2:01 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
>
>> Hi Akila,
>>
>> Common folder has all the common stuff related to the cartridges.So if
>> someone can navigate to the common folder and get the stuff shared among
>> the cartridges.
>>
>> I think it is meaningful to have those common stuff at a one place, then
>> someone new to this repository also have a feeling those stuff will be
>> common for all the cartridges.Common PCA plugins and utils also we can have
>> inside the common folder
>>
>> Thanks,
>> Gayan
>>
>> On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Gayan,
>>>
>>> Wouldn't it be easier to navigate if we move those common folders to
>>> root folder?
>>>
>>> We can create a common folder under /plugins/ folder to keep common PCA
>>> plugins and util files.
>>>
>>> Just a thought...wdyt?
>>>
>>> Thanks.
>>>
>>> On Thu, Oct 1, 2015 at 10:29 AM, Gayan Gunarathne <gay...@wso2.com>
>>> wrote:
>>>
>>>> Adding to the Dev list
>>>>
>>>>
>>>> On Thu, Oct 1, 2015 at 7:05 AM, Imesh Gunaratne <im...@wso2.com> wrote:
>>>>
>>>>> Shall we move this discussion to Dev?
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, Sep 30, 2015 at 11:02 PM, Gayan Gunarathne <gay...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> As puppet,init-scripts,base image are common for all the
>>>>>> cartridges,shall we group them under common?
>>>>>> Also what about the configurator?I can see two options
>>>>>> One option will be move the configurator to the private-paas
>>>>>> repository and release it with the private paas.Other option will be we 
>>>>>> can
>>>>>> do the separate release for the configurator.Seems it is better to have a
>>>>>> separate release for the configurator. WDYT?
>>>>>>
>>>>>> Thanks,
>>>>>> Gayan
>>>>>>
>>>>>> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne <gay...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
>>>>>>> raviha...@wso2.com> wrote:
>>>>>>>
>>>>>>>> +1 for having a simple folder structure. I think we can move the
>>>>>>>> contents in /common/ folder to root folder. One can easily identify the
>>>>>>>> important files available and easy to navigate as well.
>>>>>>>>
>>>>>>>> What should be the Maven groupId for this repo? How about
>>>>>>>> "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ?
>>>>>>>>
>>>>>>> We can use org.wso2.ppaas.cartridges as groupId
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Gayan
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>> On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne <im...@wso2.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>  I would like to reduce the complexity of the folder structure and
>>>>>>>>> make it much simple. Shall we

Re: [Dev] Private PaaS 4.1.0 Beta Release Preparation

[Gayan Gunarathne]

Great. Thanks Dinithi!

As we moved the cartridge related stuff to the new repository, now we need
to do sample testing on openstack/ec2 and kubernetes.

Thanks,
Gayan


On Thu, Oct 1, 2015 at 6:01 PM, Dinithi De Silva <dinit...@wso2.com> wrote:

> Hi,
>
> I have now moved the samples to the relevant folder with the product name
> in private-paas-cartridges repository and done some modifications to the
> paths in the deploy script according to the changes in the folder structure.
> Please use these samples when testing Private PaaS.
>
> Thanks.
>
> On Thu, Oct 1, 2015 at 12:26 PM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I have completed the clean up plugin for all the WSO2 cartridges which
>> enables to shutdown the server gracefully. I will add the changes to the
>> new cartridge repository once the structuring is completed in the repo. I
>> will start working on setting up Private Paas for google cloud engine.
>>
>> Thank you!
>>
>> On Thu, Oct 1, 2015 at 10:30 AM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> I think we are now few steps away from doing $subject. Apache Stratos
>>> 4.1.3 was released few days back. The idea is to release Private PaaS
>>> 4.1.0-Beta with Stratos 4.1.3.
>>>
>>> We now have a separate git repository for cartridges. Once we move ESB,
>>> API-M, IS and AS cartridges there and update JIRA I think we can go ahead
>>> with $subject. Please update this thread with what you are currently
>>> working on.
>>>
>>> Thanks
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774079049 <%2B94772207163>
>>
>>
>> _______
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinithi De Silva*
> Associate Software Engineer, WSO2 Inc.
> m:+94716667655 | e:dinit...@wso2.com | w: www.wso2.com
> | a: #20, Palm Grove, Colombo 03
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] Moving cartridges to a new Git repository

[Gayan Gunarathne]

Hi Imesh,

I think we need to refine the structure of the ppaas-cartridges
repository.We can have a separate folder for each cartridges.Then we can
release the each cartridge separately.We can have the samples for each
product itself.

Thanks,
Gayan







On Wed, Sep 30, 2015 at 6:01 PM, Imesh Gunaratne <im...@wso2.com> wrote:

> Hi Gayan,
>
> Great work on moving the cartridges to the new repository. Shall we bring
> them to the root folder. IMO since the git repository name contains the
> word "cartridges" may be we do not need a folder called "cartridges"
> inside. WDYT?
>
> Thanks
>
> On Tue, Sep 29, 2015 at 3:27 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>> Cartridges git repository is now available:
>> https://github.com/wso2/private-paas-cartridges
>>
>> On Tue, Sep 29, 2015 at 3:26 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>> On Tue, Sep 29, 2015 at 1:36 PM, Sajith Kariyawasam <saj...@wso2.com>
>>>  wrote:
>>>
>>>>
>>>> Will there be separate cartridge releases thereafter?
>>>>
>>>
>>> Yes we can do separate releases for cartridges afterwards. That was the
>>> idea.
>>>
>>>>
>>>>  How do we handle cartridge compatibility with Private PaaS version?
>>>>
>>>
>>> A very good question! May we for each cartridge we can mention the
>>> Private PaaS version its compatible with.
>>>
>>> On Tue, Sep 29, 2015 at 1:36 PM, Sajith Kariyawasam <saj...@wso2.com>
>>> wrote:
>>>
>>>> Hi Imesh,
>>>>
>>>> Will there be separate cartridge releases thereafter? How do we handle
>>>> cartridge compatibility with Private PaaS version?
>>>> For eg, Cartridge A version 1.0 may be compatible with PPaaS 4.1.0. If
>>>> Cartridge A is improved it may not compatible with PPaaS 4.1.0, so need to
>>>> version it to version 2.0
>>>>  That way, I think we need to do cartridge releases (tags)
>>>> for each Private PaaS release, and need to track the compatibility. Am I
>>>> right?
>>>>
>>>> On Tue, Sep 29, 2015 at 12:31 PM, Imesh Gunaratne <im...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> Currently we have all the cartridges in the Private PaaS product
>>>>> repository. As a result whenever we introduce a new cartridge we need to 
>>>>> do
>>>>> a Private PaaS release.
>>>>>
>>>>> After a discussion with Shankar and the team we thought of introducing
>>>>> a new Git repository for cartridges. Please share your thoughts on this.
>>>>>
>>>>> Thanks
>>>>>
>>>>> --
>>>>> *Imesh Gunaratne*
>>>>> Senior Technical Lead
>>>>> WSO2 Inc: http://wso2.com
>>>>> T: +94 11 214 5345 M: +94 77 374 2057
>>>>> W: http://imesh.gunaratne.org
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Sajith Kariyawasam
>>>> *Committer and PMC member, Apache Stratos, *
>>>> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
>>>> *Mobile: 0772269575*
>>>>
>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

[Gayan Gunarathne]

Adding to the Dev list

On Thu, Oct 1, 2015 at 7:05 AM, Imesh Gunaratne <im...@wso2.com> wrote:

> Shall we move this discussion to Dev?
>
> Thanks
>
> On Wed, Sep 30, 2015 at 11:02 PM, Gayan Gunarathne <gay...@wso2.com>
> wrote:
>
>> As puppet,init-scripts,base image are common for all the cartridges,shall
>> we group them under common?
>> Also what about the configurator?I can see two options
>> One option will be move the configurator to the private-paas repository
>> and release it with the private paas.Other option will be we can do the
>> separate release for the configurator.Seems it is better to have a separate
>> release for the configurator. WDYT?
>>
>> Thanks,
>> Gayan
>>
>> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne <gay...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
>>>> +1 for having a simple folder structure. I think we can move the
>>>> contents in /common/ folder to root folder. One can easily identify the
>>>> important files available and easy to navigate as well.
>>>>
>>>> What should be the Maven groupId for this repo? How about
>>>> "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ?
>>>>
>>> We can use org.wso2.ppaas.cartridges as groupId
>>>
>>> Thanks,
>>> Gayan
>>>
>>>
>>>>
>>>
>>>> On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne <im...@wso2.com>
>>>> wrote:
>>>>
>>>>>  I would like to reduce the complexity of the folder structure and
>>>>> make it much simple. Shall we have some thing like below:
>>>>>
>>>>> private-paas-cartridges/
>>>>> |--/common/
>>>>>|--/configurator/
>>>>>|--/puppet/
>>>>>   |--/wso2-installer/
>>>>>|--/scripts/
>>>>>   |---/ec2/init.sh
>>>>>   |---/openstack/init.sh
>>>>>
>>>>> |--/wso2esb/4.9.0/
>>>>>|-/template-module/
>>>>>        |-/cartridge-agent-plugins/
>>>>>|-/application/
>>>>>|-/docker/
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, Sep 30, 2015 at 9:13 PM, Imesh Gunaratne <im...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> May be we can have this discussion in Dev, I cannot see any reason to
>>>>>> take this private.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Wed, Sep 30, 2015 at 6:26 PM, Gayan Gunarathne <gay...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Adding Engineering group
>>>>>>>
>>>>>>>
>>>>>>> -- Forwarded message --
>>>>>>> From: Gayan Gunarathne <gay...@wso2.com>
>>>>>>> Date: Wed, Sep 30, 2015 at 6:26 PM
>>>>>>> Subject: [PPaaS] private-paas-cartridges repository structure
>>>>>>> To: Imesh Gunaratne <im...@wso2.com>, Reka Thirunavukkarasu <
>>>>>>> r...@wso2.com>, Udara Liyanage <ud...@wso2.com>, Lahiru Sandaruwan <
>>>>>>> lahi...@wso2.com>, Rajkumar Rajaratnam <rajkum...@wso2.com>, Sajith
>>>>>>> Kariyawasam <saj...@wso2.com>, Isuru Haththotuwa <isu...@wso2.com>,
>>>>>>> Lasindu Charith <lasi...@wso2.com>, Akila Ravihansa Perera <
>>>>>>> raviha...@wso2.com>, Chamila De Alwis <chami...@wso2.com>, Vishanth
>>>>>>> Balasubramaniam <vishan...@wso2.com>, Dinithi De Silva <
>>>>>>> dinit...@wso2.com>, Anuruddha Liyanarachchi <anurudd...@wso2.com>,
>>>>>>> Pubudu Gunatilaka <pubu...@wso2.com>, Thanuja Uruththirakodeeswaran
>>>>>>> <thanu...@wso2.com>
>>>>>>>
>>>>>>>
>>>>>>> Hi All,
>>>>>

Re: [Dev] [PPaaS] IS 5.0.0 EC2 artifacts

[Gayan Gunarathne]

Great. Thanks Dinithi

On Wed, Sep 23, 2015 at 12:43 PM, Dinithi De Silva <dinit...@wso2.com>
wrote:

> Hi Gayan,
>
> I have now added the missing deployment scripts [1].
>
> [1] -
> https://github.com/wso2/product-private-paas/commit/8586ebbddf89dbc8f621f38bc709dbce922ee42a
>
> Thanks.
>
> On Wed, Sep 23, 2015 at 12:39 PM, Gayan Gunarathne <gay...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Seems we are missing the IS 5.0.0 artifact related to the EC2 deployment
>> in PPaaS git repo[1]
>>
>> [1]
>> https://github.com/wso2/product-private-paas/tree/master/samples/applications/wso2is-500/scripts
>>
>> Thanks,
>> Gayan
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinithi De Silva*
> Associate Software Engineer, WSO2 Inc.
> m:+94716667655 | e:dinit...@wso2.com | w: www.wso2.com
> | a: #20, Palm Grove, Colombo 03
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [PPaaS] IS 5.0.0 EC2 artifacts

[Gayan Gunarathne]

Hi,

Seems we are missing the IS 5.0.0 artifact related to the EC2 deployment in
PPaaS git repo[1]

[1]
https://github.com/wso2/product-private-paas/tree/master/samples/applications/wso2is-500/scripts

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Carbon Common Puppet Module

[Gayan Gunarathne]

That puppet modules contains the products based on the WSO2 carbon. I think
it is OK to name as wso2carbon or wso2servers. If we use the ppaas_deployer
, it may reflect the meaning that all the deploying artifacts are within
that folder.

Thanks,
Gayan

On Tue, Sep 22, 2015 at 3:31 PM, Akila Ravihansa Perera <raviha...@wso2.com>
wrote:

> Hi Imesh,
>
> Since this module is not really being used by other modules rather it is
> the only Puppet module that exists for PPaaS; shall we give it a generic
> name? wso2carbon could be confusing with our Carbon product.
>
> For eg: ppaas_deployer
>
> wdyt?
>
> Thanks.
>
> On Tue, Sep 22, 2015 at 3:15 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>> Hi Anuruddha,
>>
>> IMO it would be better to call $subject wso2carbon instead of wso2servers:
>>
>> https://github.com/wso2/product-private-paas/tree/master/cartridges/vm/puppet/modules/wso2servers
>>
>> Thanks
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> 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
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Carbon Common Puppet Module

[Gayan Gunarathne]

On Tue, Sep 22, 2015 at 3:52 PM, Akila Ravihansa Perera <raviha...@wso2.com>
wrote:

> Hi Gayan,
>
> I don't see the relevance to name a Puppet module wso2carbon because all
> products are based on Carbon. All I'm saying is this could be confusing to
> an end user since we have a separate product called wso2carbon. I was only
> giving a suggestion, we can rename it to something like "wso2_installer".
> Does it make more sense?
>

+1. It makes more sense.


> Thanks.
>
> On Tue, Sep 22, 2015 at 3:42 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
>
>> That puppet modules contains the products based on the WSO2 carbon. I
>> think it is OK to name as wso2carbon or wso2servers. If we use the
>> ppaas_deployer , it may reflect the meaning that all the deploying
>> artifacts are within that folder.
>>
>> Thanks,
>> Gayan
>>
>> On Tue, Sep 22, 2015 at 3:31 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Imesh,
>>>
>>> Since this module is not really being used by other modules rather it is
>>> the only Puppet module that exists for PPaaS; shall we give it a generic
>>> name? wso2carbon could be confusing with our Carbon product.
>>>
>>> For eg: ppaas_deployer
>>>
>>> wdyt?
>>>
>>> Thanks.
>>>
>>> On Tue, Sep 22, 2015 at 3:15 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>>
>>>> Hi Anuruddha,
>>>>
>>>> IMO it would be better to call $subject wso2carbon instead of
>>>> wso2servers:
>>>>
>>>> https://github.com/wso2/product-private-paas/tree/master/cartridges/vm/puppet/modules/wso2servers
>>>>
>>>> Thanks
>>>>
>>>> --
>>>> *Imesh Gunaratne*
>>>> Senior Technical Lead
>>>> WSO2 Inc: http://wso2.com
>>>> T: +94 11 214 5345 M: +94 77 374 2057
>>>> W: http://imesh.gunaratne.org
>>>> 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
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPAAS] Error when deploying the available samples

[Gayan Gunarathne]

This is now fixed in Stratos 4.1.x branch and that fix will be available in
PPaaS alpha release.

Thanks,
Gayan



On Thu, Sep 17, 2015 at 3:58 PM, Gayan Gunarathne <gay...@wso2.com> wrote:

> Getting the following exception when deploying the ESB 4.8.1 on Kubernetes
> cluster with Stratos 4.1.x branch. Seems this is due to the length of the
> application name that we are using with the samples. We may need to
> validate the application name and update the samples appropriately.
>
> javax.ws.rs.WebApplicationException: HTTP 422 Service
> "wso2esb-481-application-service-1" is invalid: metadata.name: invalid
> value 'wso2esb-481-application-service-1': must be a DNS 952 label (at most
> 24 characters, matching regex [a-z]([-a-z0-9]*[a-z0-9])?): e.g. "my-name"
> at
> io.fabric8.kubernetes.api.ExceptionResponseMapper.fromResponse(ExceptionResponseMapper.java:40)
> at
> io.fabric8.kubernetes.api.ExceptionResponseMapper.fromResponse(ExceptionResponseMapper.java:31)
> at
> org.apache.cxf.jaxrs.client.ClientProxyImpl.checkResponse(ClientProxyImpl.java:302)
> at
> org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(ClientProxyImpl.java:725)
> at
> org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(ClientProxyImpl.java:683)
> at
> org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(ClientProxyImpl.java:224)
> at com.sun.proxy.$Proxy84.createService(Unknown Source)
> at
> io.fabric8.kubernetes.api.KubernetesClient.createService(KubernetesClient.java:440)
> at
> io.fabric8.kubernetes.api.KubernetesClient.createService(KubernetesClient.java:430)
> at
> org.apache.stratos.kubernetes.client.KubernetesApiClient.createService(KubernetesApiClient.java:217)
> at
> org.apache.stratos.cloud.controller.iaases.kubernetes.KubernetesIaas.createKubernetesServices(KubernetesIaas.java:533)
> at
> org.apache.stratos.cloud.controller.iaases.kubernetes.KubernetesIaas.startContainer(KubernetesIaas.java:221)
> at
> org.apache.stratos.cloud.controller.iaases.kubernetes.KubernetesIaas.startInstance(KubernetesIaas.java:125)
> at
> org.apache.stratos.cloud.controller.services.impl.InstanceCreator.startInstance(InstanceCreator.java:109)
> at
> org.apache.stratos.cloud.controller.services.impl.InstanceCreator.run(InstanceCreator.java:68)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
>
> Thanks,
> Gayan
> --
>
> Gayan Gunarathne
> Technical Lead, WSO2 Inc. (http://wso2.com)
> Committer & PMC Member, Apache Stratos
> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>
>
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [PPAAS] Error when deploying the available samples

[Gayan Gunarathne]

Getting the following exception when deploying the ESB 4.8.1 on Kubernetes
cluster with Stratos 4.1.x branch. Seems this is due to the length of the
application name that we are using with the samples. We may need to
validate the application name and update the samples appropriately.

javax.ws.rs.WebApplicationException: HTTP 422 Service
"wso2esb-481-application-service-1" is invalid: metadata.name: invalid
value 'wso2esb-481-application-service-1': must be a DNS 952 label (at most
24 characters, matching regex [a-z]([-a-z0-9]*[a-z0-9])?): e.g. "my-name"
at
io.fabric8.kubernetes.api.ExceptionResponseMapper.fromResponse(ExceptionResponseMapper.java:40)
at
io.fabric8.kubernetes.api.ExceptionResponseMapper.fromResponse(ExceptionResponseMapper.java:31)
at
org.apache.cxf.jaxrs.client.ClientProxyImpl.checkResponse(ClientProxyImpl.java:302)
at
org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(ClientProxyImpl.java:725)
at
org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(ClientProxyImpl.java:683)
at
org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(ClientProxyImpl.java:224)
at com.sun.proxy.$Proxy84.createService(Unknown Source)
at
io.fabric8.kubernetes.api.KubernetesClient.createService(KubernetesClient.java:440)
at
io.fabric8.kubernetes.api.KubernetesClient.createService(KubernetesClient.java:430)
at
org.apache.stratos.kubernetes.client.KubernetesApiClient.createService(KubernetesApiClient.java:217)
at
org.apache.stratos.cloud.controller.iaases.kubernetes.KubernetesIaas.createKubernetesServices(KubernetesIaas.java:533)
at
org.apache.stratos.cloud.controller.iaases.kubernetes.KubernetesIaas.startContainer(KubernetesIaas.java:221)
at
org.apache.stratos.cloud.controller.iaases.kubernetes.KubernetesIaas.startInstance(KubernetesIaas.java:125)
at
org.apache.stratos.cloud.controller.services.impl.InstanceCreator.startInstance(InstanceCreator.java:109)
at
org.apache.stratos.cloud.controller.services.impl.InstanceCreator.run(InstanceCreator.java:68)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

Thanks,
Gayan
-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

[Gayan Gunarathne]

Hi,

On Mon, Sep 7, 2015 at 10:38 AM, Reka Thirunavukkarasu <r...@wso2.com>
wrote:

> Hi
>
> When we include python in  PCA and configurator, won't it get installed by
> both the modules where i might give errors as it is already installed by
> the other module. Otherwise, we will need to add a check for whether the
> relevant library exists already or not.
>
Yeah. We need to check whether  those are already exist or not.

>
> In order to overcome this, what if we define a module for python with all
> the relevant libraries and then include it as we need when defining node
> classes for relevant module. Eg:
>
> Class['stratos_base'] -> Class['java'] -> Class['*python*'] ->
> Class['configurator']-> Class['python_agent'] -> Class['wso2am']
>

+1. I think this is the way for long run.

>
> WDYT?
>
> Thanks,
> Reka
>
>
> On Sun, Sep 6, 2015 at 11:50 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>> On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> IMO we can define 'python-dev', 'python-pip' libraries in stratos base
>>> since they are required by configurator which is a mandatory module.
>>>
>>
>> Why do we use "python-dev" instead of "python"?
>>
>> It would be better to include them in the Configurator and PCA modules
>> specifically. I do not see any reason to include them in the base module.
>>
>> On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> IMO we can define 'python-dev', 'python-pip' libraries in stratos base
>>> since they are required by configurator which is a mandatory module.
>>> Therefore,
>>> In configurator module we can inlcude jinja2;
>>> In PCA module we can include PCA related python dependencies 
>>> *(**paho,psutil,gittle,pexpect,yapsy
>>> etc.);*
>>>
>>> WDYT ?
>>>
>>>
>>> On Sun, Sep 6, 2015 at 11:02 AM, Gayan Gunarathne <gay...@wso2.com>
>>> wrote:
>>>
>>>> It is ok to redefined the python-pip module in configurator module
>>>> since currently it is used in PCA and configurator only.
>>>>
>>>> But this might be a issue with other python libraries as well if that
>>>> commonly used among the python modules.Also if there is several python
>>>> modules exists we need to redefined the libraries everywhere.IMO we may
>>>> need to include separate module for python and that module we can include
>>>> the common libraries for python.
>>>>
>>>> Thanks,
>>>> Gayan
>>>>
>>>> On Sun, Sep 6, 2015 at 9:25 AM, Akila Ravihansa Perera <
>>>> raviha...@wso2.com> wrote:
>>>>
>>>>> Hi Raj,
>>>>>
>>>>> Yes, I meant python-pip should not be removed from PCA module but
>>>>> should be installed for configurator as well.
>>>>>
>>>>> I think it should be redefined for configurator module since
>>>>> python-pip is not a compulsory package. We can use Java agent without it.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Sun, Sep 6, 2015 at 6:17 AM, Rajkumar Rajaratnam <
>>>>> rajkum...@wso2.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Sep 6, 2015 at 7:45 AM, Akila Ravihansa Perera <
>>>>>> raviha...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Raj,
>>>>>>>
>>>>>>> I think we should not remove python-pip from PCA module since those
>>>>>>> dependencies should be installed for PCA to function.
>>>>>>>
>>>>>>
>>>>>> ​In the very similar way, python-pip should be installed for
>>>>>> configurator to function as well :). So if I am using java agent instead 
>>>>>> of
>>>>>> python agent, how would configurator work without python-pip? IMO, we can
>>>>>> either move python-pip to stratos_base or use [1] to redfine python-pip
>>>>>> package in configurator if it is not already defined anywhere else.
>>>>>>
>>>>>> [1]
>>>>>> http://stackoverflow.com/questions/15266347/puppet-test-if-a-package-already-defined
>>>>>>
>>>>>> 

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

[Gayan Gunarathne]

It is ok to redefined the python-pip module in configurator module since
currently it is used in PCA and configurator only.

But this might be a issue with other python libraries as well if that
commonly used among the python modules.Also if there is several python
modules exists we need to redefined the libraries everywhere.IMO we may
need to include separate module for python and that module we can include
the common libraries for python.

Thanks,
Gayan

On Sun, Sep 6, 2015 at 9:25 AM, Akila Ravihansa Perera <raviha...@wso2.com>
wrote:

> Hi Raj,
>
> Yes, I meant python-pip should not be removed from PCA module but should
> be installed for configurator as well.
>
> I think it should be redefined for configurator module since python-pip is
> not a compulsory package. We can use Java agent without it.
>
> Thanks.
>
> On Sun, Sep 6, 2015 at 6:17 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>>
>>
>> On Sun, Sep 6, 2015 at 7:45 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Raj,
>>>
>>> I think we should not remove python-pip from PCA module since those
>>> dependencies should be installed for PCA to function.
>>>
>>
>> ​In the very similar way, python-pip should be installed for configurator
>> to function as well :). So if I am using java agent instead of python
>> agent, how would configurator work without python-pip? IMO, we can either
>> move python-pip to stratos_base or use [1] to redfine python-pip package in
>> configurator if it is not already defined anywhere else.
>>
>> [1]
>> http://stackoverflow.com/questions/15266347/puppet-test-if-a-package-already-defined
>>
>> Thanks,
>> Raj.
>>
>>>
>>> @Anuruddha: I still see that jinja2 is packed from PCA module [1]. Shall
>>> we move this to configurator module?
>>>
>>> [1]
>>> https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/python_agent/manifests/initialize.pp#L57
>>>
>>> Thanks.
>>>
>>> On Sat, Sep 5, 2015 at 3:21 PM, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
>>>> Hi Raj,
>>>>
>>>> Thanks for pointing this out. I have now added the jinja2 dependency to
>>>> configurator module and removed from PCA. [1]
>>>>
>>>> [1]
>>>> https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/configurator/manifests/init.pp#L32
>>>>
>>>> On Sat, Sep 5, 2015 at 3:14 PM, Rajkumar Rajaratnam <rajkum...@wso2.com
>>>> > wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I think python-pip & jinja2 should be installed by configurator
>>>>> puppet module, not by python agent.
>>>>>
>>>>> I am using vagrant, puppet and configurator to setup my development
>>>>> environment, but I am not using python agent. Since $subject is not done, 
>>>>> I
>>>>> had to modify configurator puppet module.
>>>>>
>>>>> It would be better if we do the $subject.
>>>>>
>>>>> Thanks,
>>>>> Raj.
>>>>>
>>>>> --
>>>>> Rajkumar Rajaratnam
>>>>> Committer & PMC Member, Apache Stratos
>>>>> Software Engineer, WSO2
>>>>>
>>>>> Mobile : +94777568639
>>>>> Blog : rajkumarr.com
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Thanks and Regards,*
>>>> Anuruddha Lanka Liyanarachchi
>>>> Software Engineer - WSO2
>>>> Mobile : +94 (0) 712762611
>>>> Tel  : +94 112 145 345
>>>> a <thili...@wso2.com>nurudd...@wso2.com
>>>>
>>>> ___
>>>> 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
>>>
>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> 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
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Syntax Error in ESB 4.8.1 build.sh File

[Gayan Gunarathne]

Yeah. We can add the validation to check whether all necessary files are
available before continue with the docker image build process.

Also when we building the template module we can just copy the template
binary to the package folder as template module is part of the PPasS. That
will be more easier for the user.For the other binaries I think it is
better to provide the download URL in the read me file.

Thanks,
Gayan


On Tue, Aug 25, 2015 at 9:39 AM, Lasindu Charith lasi...@wso2.com wrote:

 Sure will do.

 On Tue, Aug 25, 2015 at 9:31 AM, Imesh Gunaratne im...@wso2.com wrote:

 Thanks for the response Lasindu!! IMO it would be better if we can add
 few validations in the build.sh file to check whether necessary files are
 there before building the docker image.

 On Tue, Aug 25, 2015 at 7:50 AM, Lasindu Charith lasi...@wso2.com
 wrote:



 On Tue, Aug 25, 2015 at 6:36 AM, Lasindu Charith lasi...@wso2.com
 wrote:

 Hi Imesh/Pubudu,

 Please find my comments inline.

 On Tue, Aug 25, 2015 at 12:31 AM, Pubudu Gunatilaka pubu...@wso2.com
 wrote:

 Hi,

 build.sh file fails when there are no plugins in the {product/plugins}
 folder. We need to change the scripts as well.

 pushd ${wso2_product_plugin_path}
 cp * ${script_path}/plugins
 popd

 The above 'cp * command will not fail if there are no files inside '
 wso2_product_plugin_path'. But however it will fail if there's no '
 wso2_product_plugin_path'or'script_path}/plugins'which I guess is not
 possible.


 My-bad. It will say *cp: cannot stat ‘*’: No such file or directory*
 which I think is ok since it acts as a warning. Building the docker image
 requires these plugins (that's the reason to include them in buil.sh) and
 shouldn't it log an error if the required files are not available?

 I don't think we should hide the errors by changing it to 'cp * 
 ${script_path}/plugins 2/dev/null'


 I could see the same syntax errors in the other docker images as well.
 Will do the needful.

 Thank you!

 On Mon, Aug 24, 2015 at 11:47 PM, Imesh Gunaratne im...@wso2.com
 wrote:

 One other problem I noticed with this build.sh file is that it does
 not copy the plugin files to plugins folder when executed with clean.

 On Mon, Aug 24, 2015 at 11:41 PM, Imesh Gunaratne im...@wso2.com
 wrote:

 Hi,

 I found the following issue in ESB 4.8.1 build.sh file and fixed:

 echo ---
 -   echo Building ${wso2_product_type^^} - ${wso2_product_version}
 template module
 +   echo Building ${wso2_product_type} - ${wso2_product_version}
 template module
 echo ---


 https://github.com/wso2/product-private-paas/commit/f2f763e7612eeae1a1e211b1fd97a970b5c369f1

 This in-fact will change the 'wso2_product_type' to uppercase.
 However it will not work with bash versions below v4.0.
 So it's ok to remove them for now.



 This will be a syntax error in mac since the default bash version is
 v3.x.x.



 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware




 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware


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




 --

 *Pubudu Gunatilaka*
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean.enterprise.middleware
 mobile:  +94 77 4078049



 Thanks,
 --
 *Lasindu Charith*
 Software Engineer, WSO2 Inc.
 Committer  PMC Member, Apache Stratos
 Mobile: +94714427192 | Web: blog.lasindu.com




 --
 *Lasindu Charith*
 Software Engineer, WSO2 Inc.
 Committer  PMC Member, Apache Stratos
 Mobile: +94714427192 | Web: blog.lasindu.com




 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware




 --
 *Lasindu Charith*
 Software Engineer, WSO2 Inc.
 Committer  PMC Member, Apache Stratos
 Mobile: +94714427192 | Web: blog.lasindu.com

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




-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer  PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 %2B94%20766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exception in cartridge agent : ValueError: invalid literal for int() with base 10: '9763

[Gayan Gunarathne]

Yeah. Seems that fix override when merging the changes.

Now that is fixed in the master branch.

Thanks,
Gayan

On Wed, Aug 12, 2015 at 11:04 PM, Imesh Gunaratne im...@wso2.com wrote:

 Hi Punnadi,

 Looks like the fix I did for this issue has been removed in the following
 commit:

 https://github.com/apache/stratos/commit/c0455c9ac666484b24ccd948c44742e0d18e9d4f#diff-a50b759b3c52867f8df7fae4ed433faa

 @Gayan: Was this removed accidentally when we were merging the LVS load
 balancer modification?

 Thanks

 On Wed, Aug 12, 2015 at 6:59 PM, Punnadi Gunarathna punn...@wso2.com
 wrote:

 Hi,

 I get below exception in CA log. I have noticed that this has been fixed
 in Stratos 4.1.0 RC2 [1]. In latest codebase [2] I can see the fix is not
 available (Check line no 267).
 Exception in thread Thread-1:
 Traceback (most recent call last):
   File /usr/lib/python2.7/threading.py, line 552, in __bootstrap_inner
 self.run()
   File agent.py, line 100, in run
 publisher.publish_instance_activated_event(Config.health_stat_plugin)
   File /opt/apache-stratos-python-cartridge-agent-4.1.1/publisher.py,
 line 80, in publish_instance_activated_event
 int(Config.read_property(port.check.timeout, critical=False)))
   File
 /opt/apache-stratos-python-cartridge-agent-4.1.1/modules/util/cartridgeagentutils.py,
 line 80, in wait_until_ports_active
 active = check_ports_active(ip_address, ports)
   File
 /opt/apache-stratos-python-cartridge-agent-4.1.1/modules/util/cartridgeagentutils.py,
 line 109, in check_ports_active
 s.connect((ip_address, int(port)))
 ValueError: invalid literal for int() with base 10: '9763


 [1]
 https://github.com/apache/stratos/commit/819f96e57c998841a9a687c3c728d145e9f9e6ee
 [2]
 https://github.com/apache/stratos/blame/master/components/org.apache.stratos.python.cartridge.agent/src/main/python/cartridge.agent/cartridge.agent/config.py


 Please advice.

 --
 Thanks and Regards,

 Punnadi Gunarathna
 Senior Software Engineer,
 WSO2, Inc.; http://wso2.com http://wso2
 Blog: http://hi-my-world.blogspot.com/
 Tel : 94 11 214 5345
 Fax :94 11 2145300



 http://lalajisureshika.blogspot.com/




 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware




-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer  PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 %2B94%20766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PPaaS configurator doesn't pick all the payload parameters

[Gayan Gunarathne]

 Stratos,
 Senior Software Engineer,
 WSO2 Inc., http://wso2.com
 lean.enterprise.middleware

 phone: +94773325954
 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
 linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146




 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 a thili...@wso2.comnurudd...@wso2.com




 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware


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




-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer  PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Python Cartridge Agent fails with gaierror: [Errno -2] Name or service not known

[Gayan Gunarathne]

Seems python agent try to connect to the different socket rather than
message broker running. It seems python agent not reading the message
broker configurations correctly. Can you please check whether it reads the
message broker configuration correctly?

Thanks,
Gayan

On Wed, Apr 29, 2015 at 1:15 PM, Anuruddha Liyanarachchi 
anurudd...@wso2.com wrote:

 Hi Sajith,

 Yes. I am able to telnet to the mb ip and mb port

 On Wed, Apr 29, 2015 at 12:57 PM, Sajith Kariyawasam saj...@wso2.com
 wrote:

 were u able to telnet to mb,ip and mb.port from inside openstack node?

 On Wed, Apr 29, 2015 at 12:01 PM, Anuruddha Liyanarachchi 
 anurudd...@wso2.com wrote:

 Hi,

 I am trying to run python cartridge agent in openstack with Stratos.
 Agent is not able to connect to MB and fails with following error. I
 have attached agent.screen.log and agent.conf here. I can telnet to ip
 address and port in the agent.conf.

 Any idea why this is happening ?

 *2015-04-29 06:12:58,251:INFO:Cartridge agent topology receiver thread
 started*
 *Exception in thread Thread-8:*
 *Traceback (most recent call last):*
 *  File /usr/lib/python2.7/threading.py, line 551, in
 __bootstrap_inner*
 *self.run()*
 *  File
 /mnt/apache-stratos-python-cartridge-agent-4.1.0-SNAPSHOT/modules/subscriber/eventsubscriber.py,
 line 46, in run*
 *self.__mb_client = mqtt.Client()*
 *  File /usr/local/lib/python2.7/dist-packages/paho/mqtt/client.py,
 line 410, in __init__*
 *self._sockpairR, self._sockpairW = _socketpair_compat()*
 *  File /usr/local/lib/python2.7/dist-packages/paho/mqtt/client.py,
 line 255, in _socketpair_compat*
 *listensock.bind((localhost, 0))*
 *  File /usr/lib/python2.7/socket.py, line 224, in meth*
 *return getattr(self._sock,name)(*args)*
 *gaierror: [Errno -2] Name or service not known*

 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 a thili...@wso2.comnurudd...@wso2.com

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





 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 a thili...@wso2.comnurudd...@wso2.com

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




-- 

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Python Cartridge Agent fails with gaierror: [Errno -2] Name or service not known

[Gayan Gunarathne]

Great. Then previous base cartridge not create properly.

Thanks,
Gayan



On Wed, Apr 29, 2015 at 6:10 PM, Anuruddha Liyanarachchi 
anurudd...@wso2.com wrote:

 Hi Gayan,

 Thanks for the reply.
 The issue was with the base image used to create cartridges. I used a new
 base image at it worked as expected.

 On Wed, Apr 29, 2015 at 6:03 PM, Gayan Gunarathne gay...@wso2.com wrote:


 Seems python agent try to connect to the different socket rather than
 message broker running. It seems python agent not reading the message
 broker configurations correctly. Can you please check whether it reads the
 message broker configuration correctly?

 Thanks,
 Gayan

 On Wed, Apr 29, 2015 at 1:15 PM, Anuruddha Liyanarachchi 
 anurudd...@wso2.com wrote:

 Hi Sajith,

 Yes. I am able to telnet to the mb ip and mb port

 On Wed, Apr 29, 2015 at 12:57 PM, Sajith Kariyawasam saj...@wso2.com
 wrote:

 were u able to telnet to mb,ip and mb.port from inside openstack node?

 On Wed, Apr 29, 2015 at 12:01 PM, Anuruddha Liyanarachchi 
 anurudd...@wso2.com wrote:

 Hi,

 I am trying to run python cartridge agent in openstack with Stratos.
 Agent is not able to connect to MB and fails with following error. I
 have attached agent.screen.log and agent.conf here. I can telnet to ip
 address and port in the agent.conf.

 Any idea why this is happening ?

 *2015-04-29 06:12:58,251:INFO:Cartridge agent topology receiver thread
 started*
 *Exception in thread Thread-8:*
 *Traceback (most recent call last):*
 *  File /usr/lib/python2.7/threading.py, line 551, in
 __bootstrap_inner*
 *self.run()*
 *  File
 /mnt/apache-stratos-python-cartridge-agent-4.1.0-SNAPSHOT/modules/subscriber/eventsubscriber.py,
 line 46, in run*
 *self.__mb_client = mqtt.Client()*
 *  File /usr/local/lib/python2.7/dist-packages/paho/mqtt/client.py,
 line 410, in __init__*
 *self._sockpairR, self._sockpairW = _socketpair_compat()*
 *  File /usr/local/lib/python2.7/dist-packages/paho/mqtt/client.py,
 line 255, in _socketpair_compat*
 *listensock.bind((localhost, 0))*
 *  File /usr/lib/python2.7/socket.py, line 224, in meth*
 *return getattr(self._sock,name)(*args)*
 *gaierror: [Errno -2] Name or service not known*

 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 a thili...@wso2.comnurudd...@wso2.com

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





 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 a thili...@wso2.comnurudd...@wso2.com

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




 --

 Gayan Gunarathne
 Technical Lead
 WSO2 Inc. (http://wso2.com)
 email  : gay...@wso2.com  | mobile : +94 766819985





 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 a thili...@wso2.comnurudd...@wso2.com




-- 

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Duplicate payload parameters

[Gayan Gunarathne]

IMO exportMetadataKeys will be more sense as it is used to keep track of
the keys related with the meta data service.I think we can remove the
exportingProperties if that has the same usage.

Thanks,
Gayan

On Tue, Feb 24, 2015 at 2:02 PM, Udara Liyanage ud...@wso2.com wrote:

 Hi Gayan,

 Seems exportMetadataKeys and importMetadataKeys parameters were added while 
 there exist another parameter exportingProperties which exist for the same 
 reason of exportMetadataKeys. Please refer to the mail thread [Grouping] 
 Metadata service metaInfoAlias property where early property is added. If 
 so, shall I remove early exportingProperties.

 private String[] *exportingProperties*;
 private String[] exportMetadataKeys;
 private String[] importMetadataKeys;


 Udara Liyanage
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware

 web: http://udaraliyanage.wordpress.com
 phone: +94 71 443 6897




-- 

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Integrating Python modules to the Maven build process

[Gayan Gunarathne]

Hi Chamila

Did you check with maven assembly plugin[1]? I guess we are already used
this plugin in the project itself.

http://maven.apache.org/plugins/maven-assembly-plugin/

Thanks,
Gayan

On Mon, Nov 10, 2014 at 1:02 PM, Chamila De Alwis chami...@wso2.com wrote:

 Update:

 I used the maven-antrun-plugin to zip the folder contents, as it was far
 simpler than the exec plugin.

 build
 plugins
 plugin
 artifactId*maven-antrun-plugin*/artifactId
 executions
 execution
 phasepackage/phase
 goals
 goalrun/goal
 /goals
 configuration
 target


 *zip
 destfile=${project.build.directory}/artifact-name-${project.version}.zip
 basedir=parentdir/contentdir/*
 /target
 /configuration
 /execution
 /executions
 /plugin
 /plugins
 /build



 Regards,
 Chamila de Alwis
 Software Engineer | WSO2 | +94772207163
 Blog: code.chamiladealwis.com



 On Fri, Nov 7, 2014 at 12:10 PM, Chamila De Alwis chami...@wso2.com
 wrote:

 Hi,

 I have a python module that should be integrated in to the rest of the
 Java code in a project with Maven. The production code folder in this
 module should be zipped up and moved to the target folder when maven
 install is run.

 The only option I've found so far is to map actions in Python's
 setuptools to Maven through exec-maven-plugin[1]. However my requirement
 seems simpler than writing a setup.py file.

 Are there any other methods to approach this?


 [1] - http://shiningpanda.com/python-java-unified-build-process-14.html


 Regards,
 Chamila de Alwis
 Software Engineer | WSO2 | +94772207163
 Blog: code.chamiladealwis.com




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




-- 

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Lasindu Charith

[Gayan Gunarathne]

/




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




-- 

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Rajkumar Rajaratnam

[Gayan Gunarathne]

Congratulations Rajkumar!!

On Tue, Oct 21, 2014 at 9:45 AM, Roshan Deniyage rosh...@wso2.com wrote:

 Congratulation Rajkumar!


 Roshan Deniyage
 Associate Technical Lead
 WSO2, Inc: http://wso2.com

 Mobile:  +94 777636406
 Twitter:  *https://twitter.com/roshku https://twitter.com/roshku*
 LinkedIn :  https://www.linkedin.com/in/roshandeniyage


 On Tue, Oct 21, 2014 at 9:41 AM, Godwin Amila Shrimal god...@wso2.com
 wrote:

 Congratulation Rajkumar ...!

 On Tue, Oct 21, 2014 at 9:38 AM, Roshan Wijesena ros...@wso2.com wrote:

 Congratulation!!

 On Tue, Oct 21, 2014 at 9:33 AM, Prasanna Dangalla prasa...@wso2.com
 wrote:

 Congratulations Rajkumar...

 On Tue, Oct 21, 2014 at 9:28 AM, Thilini Shanika thili...@wso2.com
 wrote:

 Congratulations Rajkumar !!!

 On Tue, Oct 21, 2014 at 9:27 AM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Congratulations Raj !

 *Dakshika Jayathilaka*
 Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Tue, Oct 21, 2014 at 9:26 AM, Sameera Jayaratna samee...@wso2.com
  wrote:

 Congratz Rajkumar!!!

 On Tue, Oct 21, 2014 at 9:23 AM, Suhan Dharmasuriya suh...@wso2.com
  wrote:

 Congrats Rajkumar!!!

 On Tue, Oct 21, 2014 at 9:22 AM, Shiroshica Kulatilake 
 sh...@wso2.com wrote:

 Congrats !!

 On Tue, Oct 21, 2014 at 9:19 AM, Kasun De Silva kas...@wso2.com
 wrote:

 Congrats Rajkumar !!!

 *Kasun de Silva*
 Software Engineer | *WSO2 Inc.*; http://wso2.com
 lean.enterprise.middleware

 email   : kas...@wso2.com
 mobile : +94 77 794 4260


 On Tue, Oct 21, 2014 at 9:07 AM, Lakmal Warusawithana 
 lak...@wso2.com wrote:

 Hi all,

 It's my pleasure to announce Raj as a WSO2 Committer. Raj has
 done great contributions to Apache Stratos and WSO2 Private PaaS 
 products.
 And in recognition of his contribution he has been voted as a WSO2 
 commiter.

 Raj, welcome aboard and keep up the good work!.

 --
 Lakmal Warusawithana
 Vice President, Apache Stratos
 Director - Cloud Architecture; WSO2 Inc.
 Mobile : +94714289692
 Blog : http://lakmalsview.blogspot.com/


 ___
 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




 --
 Shiroshica Kulatilake

 Architect,
 WSO2, Inc. http://wso2.com/
 Phone: +94 776523867

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




 --
 Suhan Dharmasuriya
 Software Engineer - Test Automation

 *WSO2, Inc. *

 lean . enterprise . middleware
 Tel: +94 112 145345
 Mob: +94 779 869138
 Blog: http://suhan-opensource.blogspot.com/

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




 --



 *Thanks  Regards,Sameera Jayaratna Software Engineer; **WSO2 Inc. *

 *lean . enterprise . middleware |  http://wso2.com http://wso2.com
 *

 ___
 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




 --
 Thilini Shanika
 Software Engineer
 WSO2, Inc.; http://wso2.com
 20, Palmgrove Avenue, Colombo 3

 E-mail: tgtshan...@gmail.com


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




 --
 Prasanna Dangalla
 Software Engineer, WSO2, Inc.; http://wso2.com/
 lean.enterprise.middleware

 cell: +94 777 55 80 30 | +94 718 11 27 51
 twitter: @prasa77

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




 --
 Roshan Wijesena.
 Senior Software Engineer-WSO2 Inc.
 Mobile: *+94752126789*
 Email: ros...@wso2.com
 *WSO2, Inc. :** wso2.com http://wso2.com/*
 lean.enterprise.middleware.

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




 --
 *Godwin Amila Shrimal*
 Senior Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: *+94772264165*
 linkedin: *http://lnkd.in/KUum6D http://lnkd.in/KUum6D*
 twitter: https://twitter.com/godwinamila

 ___
 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




-- 

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: How do we restart the Private PAAS

[Gayan Gunarathne]

Hi Udara,

Yeah this is the requirement.

As Manula said this can be happen due to PP host machine crashed.

Thanks,
Gayan

On Tue, Oct 7, 2014 at 10:40 AM, Udara Liyanage ud...@wso2.com wrote:


 -- Forwarded message --
 From: Udara Liyanage ud...@wso2.com
 Date: Tue, Oct 7, 2014 at 10:37 AM
 Subject: Re: How do we restart the Private PAAS
 To: Reka Thirunavukkarasu r...@wso2.com
 Cc: Manula Chathurika Thantriwatte manu...@wso2.com, Gayan Gunarathne 
 gay...@wso2.com, WSO2 Developers' List dev@wso2.org, Nirmal Fernando 
 nir...@wso2.com, Akila Ravihansa Perera raviha...@wso2.com, Dinesh
 Bandara dine...@wso2.com, Imesh Gunaratne im...@wso2.com, Isuru
 Haththotuwa isu...@wso2.com, Lasindu Charith lasi...@wso2.com, Lahiru
 Sandaruwan lahi...@wso2.com, Lakmal Warusawithana lak...@wso2.com,
 Rajkumar Rajaratnam rajkum...@wso2.com, Isuru Perera isu...@wso2.com,
 Sajith Kariyawasam saj...@wso2.com, Shiroshica Kulatilake 
 sh...@wso2.com, Chamila De Alwis chami...@wso2.com


 Hi Gayan,

 I think I have misunderstood your requirement when I replied last time.
 I think you are referring to a state where
  you boot up PP
  instances are spawned
  Now you stop the vm which PP is running?
 I am correct?

 My first concern is why someone stop the PP instance  in a production
 environment?



 On Tue, Oct 7, 2014 at 10:29 AM, Reka Thirunavukkarasu r...@wso2.com
 wrote:

 Hi

 If ips are getting changed, can we follow one of these approaches?

 1. We unsubscribe and undeploy the cartridges before stopping. May be we
 can create a script to do that. Later, when they start again we can ask the
 user to start with -t and configure the relevant services again. In this
 case, user will loose any configured cartridges with apps. But he can
 subscribe again with the same git URL. Assumption is that the user kept all
 the apps modification in the Git. Also, user has to wait a bit to get the
 system up and running after the restart, since all the cartridge has to be
 spun again.

 2. Another case is to use MB and send the changed ips to cartridge
 instances using instance-notifier topic and restart cartridge agent. We
 need to make sure the cluster monitor shouldn't spin any new instances
 while the cartridge agent is restarting.

 Are these still feasible solution? If not, is there any other way of
 handling this?

 Thanks,
 Reka

 On Tue, Oct 7, 2014 at 10:13 AM, Manula Chathurika Thantriwatte 
 manu...@wso2.com wrote:

 Hi Gayan,

 AFAIK these options only valid for restart Stratos scenario. If we stop
 the EC2 instance and start it again, the public and private IPs of that EC2
 instance got changed. Then the spin up cartridge instances didn't aware of
 this new IPs of Stratos.

 Thanks !


 On Tue, Oct 7, 2014 at 9:59 AM, Gayan Gunarathne gay...@wso2.com
 wrote:

 Adding dev list

 Use case of this is EC2 instance stop and start again.In this case what
 is our recommendation procedure for user to follow start the private PASS
 again?

 AFAIK there are two options in the boot.sh. (-s and -t)

 -s for silent mode
 -t for configure services only mode

  Are we recommend user to use one of those options and start the
 private pass again? AFAIU -t option will be fitted in to this type of
 scenario.

 Thanks,
 Gayan



 On Mon, Oct 6, 2014 at 7:10 PM, Udara Liyanage ud...@wso2.com wrote:

 Hi,

 If the instances are getting restarted, that means instances are not
 getting activated. Look for puppet logs and agent log for the issue.

 If you want to terminate the instances and clean the system.
 First un deploy services. Then instances will be terminated. After
 that execute clean.sh if you want to clean the system.

 @gayan you can use wso2 dev list for this kind of e-mails right ?

 On Mon, Oct 6, 2014 at 6:57 PM, Gayan Gunarathne gay...@wso2.com
 wrote:

 Hi All,

 What is our recommended method to restart the Private PASS? This need
 to be done when the EC2 instance is getting restarted.

 I have used the boot.sh -t option.  But still I need to run the
 clean.sh.Is n't ?

 There is a JIRA related to this.[1]

 [1] https://wso2.org/jira/browse/PAAS-139


 Thanks,
 Gayan




 --

 Udara Liyanage
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware

 web: http://udaraliyanage.wordpress.com
 phone: +94 71 443 6897




 --


 Gayan Gunarathne
 Technical Lead
 WSO2 Inc. (http://wso2.com)
 email  : gay...@wso2.com  | mobile : +94 766819985





 --
 Regards,
 Manula Chathurika Thantriwatte
 Software Engineer
 WSO2 Inc. : http://wso2.com
 lean . enterprise . middleware

 email : manu...@wso2.com / man...@apache.org
 phone : +94 772492511
 blog : http://manulachathurika.blogspot.com/






 --
 Reka Thirunavukkarasu
 Senior Software Engineer,
 WSO2, Inc.:http://wso2.com,
 Mobile: +94776442007





 --

 Udara Liyanage
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware

 web: http://udaraliyanage.wordpress.com
 phone: +94 71 443 6897

Re: [Dev] WSO2 Committers += Akila Ravihansa Perera

[Gayan Gunarathne]

 Congrats Akila!!!


On Thu, Sep 4, 2014 at 2:11 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:

 Congratulations Akila !!


 On Thu, Sep 4, 2014 at 2:03 PM, Lasindu Charith lasi...@wso2.com wrote:

 Congrats Akila...!!!


 On Thu, Sep 4, 2014 at 1:51 PM, Praneesha Chandrasiri pranee...@wso2.com
  wrote:

 Congrats Akila!


 On Thu, Sep 4, 2014 at 1:49 PM, Manula Chathurika Thantriwatte 
 manu...@wso2.com wrote:

 Congratulations !!!


 On Thu, Sep 4, 2014 at 1:28 PM, Kasun Dissanayake kas...@wso2.com
 wrote:

 Congratulations Akila and keep up the good work !

 Cheers


 On Thu, Sep 4, 2014 at 1:19 PM, Lakmal Warusawithana lak...@wso2.com
 wrote:

 Hi all,

 It's my pleasure to announce Akila as a WSO2 Committer. Akila has
 done great contributions to Apache Stratos and WSO2 Private PaaS 
 products.
 And in recognition of his contribution he has been voted as a WSO2 
 commiter.

 Akila, welcome aboard and keep up the good work!.

 --
 Lakmal Warusawithana
 Vice President, Apache Stratos
 Director - Cloud Architecture; WSO2 Inc.
 Mobile : +94714289692
 Blog : http://lakmalsview.blogspot.com/


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




 --
 Kasun Dissanayake
 Software Engineer
 WSO2 Inc.
 Lean | Enterprise | Middleware
 Tel - +94 77 086 2860
 Skype - kasun.dissanayake4
 LinkedIn - lk.linkedin.com/in/kasundis/

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




 --
 Regards,
 Manula Chathurika Thantriwatte
 Software Engineer
 WSO2 Inc. : http://wso2.com
 lean . enterprise . middleware

 email : manu...@wso2.com / man...@apache.org
 phone : +94 772492511
 blog : http://manulachathurika.blogspot.com/




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




 --
 Thanks  Best Regards,
 *Praneesha Chandrasiri*
 *Technical Writer*
 *WSO2 Inc. *
 *Mobile: +(94) 718156888 %2B%2894%29%20718156888*
 *E-mail: pranee...@wso2.com pranee...@wso2.com*


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




 --
 *Lasindu Charith*
 Software Engineer, WSO2 Inc.
 Mobile: +94714427192
 Web: blog.lasindu.com

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




 --

 Thanks  Best Regards,

 Tharindu Edirisinghe
 Software Engineer

 *WSO2 Inc*
 *email   : tharin...@wso2.com tharin...@wso2.com *
 *mobile : +94 775 181586*
 *www: :http://wso2.com http://wso2.com/ *
 lean . enterprise . middleware



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




-- 
Best Regards,

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Connector uploading error in ESB!

[Gayan Gunarathne]

Seems like some of the dependencies refer in the connector are missing.
Please check whether you have include all the dependencies to the lib
folder of the connector zip file.

Thanks,
Gayan


On Fri, Jun 20, 2014 at 9:44 AM, Asanki Fernando iasankiferna...@gmail.com
wrote:

 Hi All,

 I'm writing an ESB connector to foursquare, and most of the times when I
 try to upload the connector to the ESB, it gives me the following error. I
 checked all the possible syntax errors that could be made. Is this coz of a
 syntax error? Please let me know a way to solve this.

 [2014-06-20 09:38:00,431] ERROR - LibraryArtifactDeployer Artifact
 representing the filename
 /home/ian/Documents/Software/ESB2/wso2esb-4.8.1/repository/deployment/server/synapse-libs/foursquare.zip
 is not deployed on Synapse
 [2014-06-20 09:38:00,431]  INFO - DeploymentEngine
 org.apache.axis2.deployment.DeploymentException: Artifact representing the
 filename
 /home/ian/Documents/Software/ESB2/wso2esb-4.8.1/repository/deployment/server/synapse-libs/foursquare.zip
 is not deployed on Synapse
 [2014-06-20 09:38:00,598] ERROR - LibDeployerUtils artifact.xml is
 invalid. Error occurred while resolving Synapse Library :
 {org.wso2.carbon.connectors}foursquare
 [2014-06-20 09:38:00,598]  WARN - LibDeployerUtils Could not build lib
 artifact for path :
 /home/ian/Documents/Software/ESB2/wso2esb-4.8.1/tmp/libs/1403237280432foursquare.zip/fourSq_venues
 Synapse Library :{org.wso2.carbon.connectors}foursquare. Continue searching
 for other lib artifacts
 [2014-06-20 09:38:00,605] ERROR - LibraryArtifactDeployer Deployment of
 synapse artifact failed for synapse libray at :
 /home/ian/Documents/Software/ESB2/wso2esb-4.8.1/repository/deployment/server/synapse-libs/foursquare.zip
 : Error when resolving Dependencies for lib :
 {org.wso2.carbon.connectors}foursquare
 org.apache.synapse.deployers.SynapseArtifactDeploymentException: Error
 when resolving Dependencies for lib : {org.wso2.carbon.connectors}foursquare
 at
 org.apache.synapse.libraries.util.LibDeployerUtils.searchAndResolveDependencies(LibDeployerUtils.java:244)
  at
 org.apache.synapse.libraries.util.LibDeployerUtils.createSynapseLibrary(LibDeployerUtils.java:80)
 at
 org.apache.synapse.deployers.LibraryArtifactDeployer.deploy(LibraryArtifactDeployer.java:60)
  at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
  at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
  at
 org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
 at
 org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
  at
 org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
  at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
 at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
  at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
  at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
 at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
  at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
  at java.lang.Thread.run(Thread.java:744)


 Thank you.
 Best Regards,
 Asanki Fernando.



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




-- 
Best Regards,

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 766819985
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AS] Create a new carbon WebappClassLoader instance in a servlet using reflexion

[Gayan Gunarathne]

Hi Chamil,

In generally, this exception can be occurred with the following reasons.

   1. When JVM tries to load a class at runtime and if that class is not
found in classpath

   2. Classloader can see multiple versions of the same class or different
dependency paths end in different versions of the same class.

Please check if any of the scenario exist with this given class.


Best Regards,

Gayan





On Mon, Apr 28, 2014 at 5:38 PM, Chamil Jeewantha cha...@wso2.com wrote:

 Hi All,

 In my servlet I want to create another WebappClassLoader instance as
 follows.

 public class LoaderServlet extends HttpServlet {

 public void init(ServletConfig config) throws ServletException {

 ClassLoader catalinaCl = config.getClass().getClassLoader();
 Class? webappClClass =
 catalinaCl.loadClass(org.wso2.carbon.webapp.mgt.loader.WebappClassLoader);
  ClassLoader childCl = (ClassLoader)
 webappClClass.getConstructor(ClassLoader.class).newInstance(catalinaCl);
 }
 }

 The above code gives ClassNotFoundException

 java.lang.ClassNotFoundException:
 org.wso2.carbon.webapp.mgt.loader.WebappClassLoader
 at
 org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)

 Please help.

 Regards,
 Chamil

 --
 K.D. Chamil Jeewantha
 Associate Technical Lead
 WSO2, Inc.;  http://wso2.com
 Mobile: +94716813892


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




-- 

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 784713028
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev