Re: [Architecture] Multiple runtime support for C5 based products

2017-09-07 Thread SajithAR Ariyarathna 
Hi Thusitha,

On Mon, Aug 14, 2017 at 12:08 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Jayanga,
>
> From the beginning of C5, we tried to achieve a clear separation between,
>> User(Custom) space and Server space.
>> IMO, having just a single deployment directory (for both custom and
>> server artifacts) won't help to maintain that separation.
>
> We are having 2 deployment directories.
>
>1. //deployment
>2. /deployment
>
> Is there a priority in these directories?
Thanks.

On Mon, Aug 14, 2017 at 12:14 PM, Niranjan Karunanandham 
wrote:

> Hi Thusitha,
>
> On Mon, Aug 14, 2017 at 12:08 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Jayanga,
>>
>> From the beginning of C5, we tried to achieve a clear separation between,
>>> User(Custom) space and Server space.
>>> IMO, having just a single deployment directory (for both custom and
>>> server artifacts) won't help to maintain that separation.
>>
>> We are having 2 deployment directories.
>>
>>1. //deployment
>>2. /deployment
>>
>> The issue is in existing API we have a method to deploy/upload the given
>> artifact to the deployment directory. This was not an issue previously coz
>> we had only single deployment dir. But since now we have multiple
>> deployment dirs, where should we deploy the artifact?
>>
> When are we using this method, i.e., the use-case? If the artifact is
> within the either the runtime deployment or serverhome deployment
> directory, then based on that the artifact can be deployed in the
> corresponding directory.
>
>
>>
>> Thanks
>> Thusitha
>>
>> On Mon, Aug 14, 2017 at 11:15 AM, Jayanga Dissanayake 
>> wrote:
>>
>>> Hi Thusitha/Nira,
>>>
>>> From the beginning of C5, we tried to achieve a clear separation
>>> between, User(Custom) space and Server space.
>>> IMO, having just a single deployment directory (for both custom and
>>> server artifacts) won't help to maintain that separation.
>>>
>>> WDYT?
>>>
>>> Thanks,
>>> Jayanga.
>>>
>>> *Jayanga Dissanayake*
>>> Associate Technical Lead
>>> WSO2 Inc. - http://wso2.com/
>>> lean . enterprise . middleware
>>> email: jaya...@wso2.com
>>> mobile: +94772207259 <+94%2077%20220%207259>
>>> 
>>>
>>> On Mon, Aug 14, 2017 at 10:53 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi,

 On Fri, Aug 11, 2017 at 11:24 AM, Thusitha Thilina Dayaratne <
 thusit...@wso2.com> wrote:

> Hi All,
>
> In c5 carbon-deployment we have a method to manually deploy artifacts
> where we only provide artifact's path and artifact type. This was no issue
> until 5.2.0-m3 since we only had a single deployment directory.
> public void deploy(String artifactPath, ArtifactType artifactType)[1]
>
> But since we have 2 deployment directories with the new
> runtime architecture. So how should we handle this deployment?
> AFAIU options would be as follows
>
>1. Add a new API(method) to get the relevant deployment dir and
>deploy to that
>2. We have to prioritize a deployment directory (Server or
>runtime) and deploy only to the prioritized one
>3. Deploy to both deployment dirs
>
>
>
 In the new deployment directory, each runtime will have a deployment
 directory and there will be on outside. The runtime deployment will be for
 wso2 artifacts. AFAIU with previous model (C4), the above method is used by
 when a user uploads the artifact from a UI. Therefore IMO the default
 method should deploy the artifact to the deployment directory outside the
 runtime, i.e., /deployment.


> [1] - https://github.com/wso2/carbon-deployment/blob/master/comp
> onents/org.wso2.carbon.deployment.engine/src/main/java/org/w
> so2/carbon/deployment/engine/DeploymentService.java#L43
>
> Thanks
> Thusitha
>
>
> On Fri, Jun 2, 2017 at 10:23 AM, Danesh Kuruppu 
> wrote:
>
>> Hi all,
>>
>> Correction: Proposed directory structure needed to be change as
>> below. instead of having deployment directory per runtime, we will have
>> only deployment directory per server distribution. This deployment
>> directory contains custom deployable artifacts. So ideally there won't be
>> any artifact in default distribution.
>>
>> Though we have packaging all runtimes in one distribution. we are not
>> encouraging to run all runtime from the single pack. So we are going to
>> provide a script to exact runtime from the distribution pack.
>>
>> ServerHome
>>>|_ bin
>>>| |___ runtime1.sh
>>>| |___ runtime2.sh
>>>| |___ start-all.sh (start all the runtimes
>>> except default in separate JVMs)
>>>| |___ default.sh (start required runtimes in a
>>>

Re: [Architecture] Using Kubernetes ConfigMaps for Managing Product Configurations

2017-09-07 Thread Imesh Gunaratne 
On Thu, Sep 7, 2017 at 10:57 AM, Pubudu Gunatilaka  wrote:

>
> On Thu, Sep 7, 2017 at 10:44 AM, Imesh Gunaratne  wrote:
>
>>
>> Are you suggesting to use a single configmap and mount that to a single
>> conf folder in the pod and then copy file by file to relevant folders?
>>
>> As config maps does not support nested folders we have to use multiple
> config maps. Rather than hard coding the folder names in the dockerfile
> [1], using a script we can copy all the files within wso2ei-integrator-conf
> to wso2ei product folder. As I mentioned before, users will be able to add
> any configuration file which resides within the product folder without
> adding that in the dockerfile.
>
> ​I discussed this offline with Pubudu and decided to create separate
folders for each config folder including sub-folders. The plan is to add
all config folders as configmaps and update the Dockerfile to include
commands to copy those if available. As a result users will not need to
re-build Docker images for adding any of the configurations.

Thanks
Imesh
​


> [1] - https://github.com/wso2/kubernetes-ei/blob/master/
> dockerfiles/integrator/Dockerfile#L25
>
> Thank you!
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


-- 
*Imesh Gunaratne*
Associate Director/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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Same feature with different versions in different runtimes

2017-09-07 Thread Niranjan Karunanandham 
Hi Kasun,

Have we created a git issue for the carbon-maven-plugins with regard to not
able to download two versions of the same feature to create a p2-repo?

Regards,
Nira

On 8 Sep 2017 5:13 a.m., "Kasun Siyambalapitiya"  wrote:

> Hi Dilan and all,
>
> Pardon me for the late reply. Yes, I agree with your point due to the fact
> that different feature versions including slight or major differences in
> their implementation has been released as compatible features for WSO2
> Carbon 4.4.x (Wilkes) [1] products,
>
> For example,
>
>
>1. 
> org.wso2.carbon.identity.application.authentication.framework.server_4.5.6.jar
>/ org.wso2.carbon.identity.application.authentication.framewor
>k.server_5.7.5.jar
>2. org.wso2.carbon.directory.service.mgr.server_4.5.6.jar /
>org.wso2.carbon.directory.service.mgr.server_5.7.5.jar
>3. rg.wso2.carbon.forum.server_2.0.0.jar / org.wso2.carbon.forum.server
>_6.1.66.jar
>4. org.wso2.carbon.identity.core.server_4.5.5.jar
>/ org.wso2.carbon.identity.core.server_5.7.5.jar
>5. org.wso2.carbon.identity.core.ui_4.5.5.jar
>/ org.wso2.carbon.identity.core.ui_5.7.5.jar
>
> Since all the jars mentioned above have major implementational changes
> which are not backward compatible (as indicated by the major version no
> change) there is a huge possibility of having a functional inconsistency in
> the system if multiple versions of the same feature are used in different
> runtimes. For example the format of data inserted and queried out from db
> from previous version may differ from the how it is done in the latest
> version leaving to inconsistencies in DB. IMO I think either we should
> restrict to one version of a certain feature or allow up to it's next major
> version. WDYT?
>
>
> [1] http://product-dist.wso2.com/p2/carbon/releases/wilkes/features/
>
> Thanks.
>
> On Fri, Aug 18, 2017 at 8:39 AM, Dilan Udara Ariyaratne 
> wrote:
>
>> Hi Kasun and All,
>>
>> Let me raise a different, but fundamental concern to this issue. Please
>> correct me if I am wrong.
>>
>> It's perfectly valid to have the same feature on different run-times (or
>> profiles) of a product, but if that same feature appears in "different
>> versions",
>> meaning, with slight or major differences of their implementations, at
>> different run-times of the product, wouldn't that open up any possibilities
>> of functional inconsistencies or even failures to the overall system ?
>>
>> Thanks,
>> Dilan.
>>
>> *Dilan U. Ariyaratne*
>> Senior Software Engineer
>> WSO2 Inc. 
>> Mobile: +94766405580 <%2B94766405580>
>> lean . enterprise . middleware
>>
>>
>> On Thu, Aug 17, 2017 at 8:19 PM, Kasun Siyambalapitiya 
>> wrote:
>>
>>> Hi Niranjan,
>>>
>>> When generating the p2-repository using `carbon-maven-plugin version
>>> 3.x` this issue arises due to the fact that it resolves dependencies for
>>> each given feature with the dependencies we defined in the pom itself (note
>>> that the effective pom is used for the resolving). Since maven picks only
>>> one version of a given dependency due the use of `nearest in the dependency
>>> tree` strategy, a p2-repo with multiple versions of the same feature can
>>> not be created by using the current `carbon-maven-plugin version 3.1.3`.
>>>
>>> But in the case of `carbon-maven-plugin version 1.5.x` this is possible
>>> as the dependencies of each feature is defined in a string form as below
>>>
>>> org.apache.axis2.transport:org.apache.axis2.transport.jms.feature:
 ${axis2-transports.wso2.version.1.1.0.wso2v17}
>>>
>>>
>>> and the version `${axis2-transports.wso2.version.1.1.0.wso2v17}` is
>>> replaced with the value of the relevant property we defined in the pom.xml.
>>> Since there are no restrictions like above in defining properties in
>>> pom.xml this works.
>>>
>>> Thanks.
>>>
>>> On Thu, Aug 17, 2017 at 10:39 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Kasun,

 On Thu, Aug 17, 2017 at 10:04 AM, Kasun Siyambalapitiya <
 kasu...@wso2.com> wrote:

> Hi Niranjan,
>
> The build fails before successful generation of the p2-repo by giving
> the following error
>
> [ERROR] Failed to execute goal org.wso2.carbon.maven:carbon-f
>> eature-plugin:3.1.1:generate-repo (p2-repo-generation) on project
>> wso2carbon-kernel: Feature org.wso2.carbon.pax.exam.feature_5.2.0.1
>> not found -> [Help 1]
>
>
>
> Since in the new C5 model the p2-repo containing all the features
> required for all the runtimes of the product, is generated at a single
> specified directory(by default the target directory) multiple version of
> the same feature cannot be generated as maven build will pick only one
> version of the dependency due to the use of "nearest in the dependency
> tree" strategy as shown in above mail. As a result although we can have
> multiple versions at the

Re: [Architecture] [Dev] WSO2 Stream Processor 4.0.0-M11 Released !

2017-09-07 Thread Sriskandarajah Suhothayan 
On Fri, Sep 8, 2017 at 4:55 AM Anusha Jayasundara  wrote:

> Hi All,
>
>
> The WSO2 Analytics team is pleased to announce the release of *WSO2
> Stream Processor Version 4.0.0 Milestone 11*.
>
> WSO2 Smart Analytics let digital business creating real-time, intelligent,
> actionable business insights, and data products which are achieved by WSO2
> Stream Processor's real-time, incremental & intelligent data processing
> capabilities.
>
> WSO2 Stream Processor can:
>
>-
>
>Receive events from various data sources
>-
>
>Process & correlate them in real-time with the sate of the art
>high-performance real-time Siddhi Complex Event Processing Engine that
>works with easy to learn the SQL-Like query language.
>-
>
>Process analysis that spans for longer time duration with its
>incremental processing capability by achieving high performance with low
>infrastructure cost.
>-
>
>Uses Machine Learning and other models to drive intelligent
>insights from the data
>-
>
>Notifications interesting event occurrences as alerts via multiple
>types of transport & let users visualize the results via customizable
>dashboards.
>-
>
>WSO2 SP is released under Apache Software License Version 2.0, one
>of the most business-friendly licenses available today.
>
>
> You can find the product at 
> *https://github.com/wso2/product-sp/releases/download/v4.0.0-M11/wso2sp-4.0.0-M11.zip
> *
> Documentation at *https://docs.wso2.com/display/SP400/Introduction*/
> 
> Source code at *https://github.com/wso2/product-sp
> /*
>
> *WSO2 SP 4.0.0-M11 includes the following*
>
> *New Features*
>
>- Reliable message processing with kafka
>- Non occurrence of event - siddhi pattern
>- Multiple primary-key support for inmemory tables
>- Streaming ML
>   - Hoeffding classifier
>   - K-means clustering
>- Editor improvements
>
> + Static Dashboard

>
>-
>
> *Reporting Issues*
>
> Issues can be reported using the github issue tracker available at
> https://github.com/wso2/product-sp
> 
> *Contact us*
>
> WSO2 Stream Processor developers can be contacted via the mailing lists:
>
> Developer List : d...@wso2.org | Subscribe
>  | M
> 
>
>
> Alternatively, questions can also be raised in the Stackoverflow:
>
> Forum http://stackoverflow.com/questwso2/
> 
>
>
> *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/.  
>
> For more information on WSO2 Smart Analytics and
> Smart Analytics Solutions, visit the WSO2 Smart Analytics Page
> .
>
>
>
> *~ The WSO2 Analytics Team ~*
> --
>
> *Anusha Jayasundara*
> Software Engineer | WSO2
>
> Email : anus...@wso2.com
> Mobile : +94772601160
> Web : http://wso2.com
> Lean.Enterprise.Middleware
> 
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
-- 

*S. Suhothayan*
Associate Director / Architect
*WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Using Kubernetes ConfigMaps for Managing Product Configurations

2017-09-07 Thread Dilan Udara Ariyaratne 
Hi Folks,

As I have experienced so far, using configmaps [1] to do configuration
management of a particular deployment profile is much handy and effective
than
the effort we need to put in doing the same using building per-profile
docker images.

When ever we require a configuration update to be done for a particular
deployment profile, we can easily change the configuration of the specific
file and initiate
a rolling update [2] for that particular deployment as follows. For
example, in the case of wso2/kubernetes-ei [3]

kubectl rolling-update wso2ei-pattern1-integrator-deployment -f
new-integrator-deployment.yaml

No further burden of the need to build docker images again and again
per each change and push them to cluster for a simple configuration
change.

[1] https://kubernetes.io/docs/tasks/configure-pod-container/configmap
[2] 
https://kubernetes.io/docs/tasks/run-application/rolling-update-replication-controller
[3] https://github.com/wso2/kubernetes-ei

Cheers,
Dilan.

*Dilan U. Ariyaratne*
Senior Software Engineer
WSO2 Inc. 
Mobile: +94766405580 <%2B94766405580>
lean . enterprise . middleware


On Thu, Sep 7, 2017 at 10:57 AM, Pubudu Gunatilaka  wrote:

> Hi Imesh,
>
> On Thu, Sep 7, 2017 at 10:44 AM, Imesh Gunaratne  wrote:
>
>> Hi Pubudu,
>>
>> On Thu, Sep 7, 2017 at 12:54 AM, Pubudu Gunatilaka 
>> wrote:
>>
>>>
>>> On Wed, Sep 6, 2017 at 11:06 PM, Imesh Gunaratne  wrote:
>>>

 ​Do we really need to parameterize these? Wouldn't it be better to add
 all required folders?​ May be what we need is the bin, conf and deployment
 folders (including sub folders)?

 Without mentioning all the configuration files in the dockerfile[1], we
>>> can copy all the content of wso2ei-integrator-conf to wso2ei product
>>> folder. In this way, users can dynamically add any configuration file
>>> without changing the base docker image.They only need to add a configmap
>>> and mount that to the wso2ei-integrator-conf folder.
>>>
>>
>> Are you suggesting to use a single configmap and mount that to a single
>> conf folder in the pod and then copy file by file to relevant folders?
>>
>>
> As config maps does not support nested folders we have to use multiple
> config maps. Rather than hard coding the folder names in the dockerfile
> [1], using a script we can copy all the files within wso2ei-integrator-conf
> to wso2ei product folder. As I mentioned before, users will be able to add
> any configuration file which resides within the product folder without
> adding that in the dockerfile.
>
> [1] - https://github.com/wso2/kubernetes-ei/blob/master/dockerfi
> les/integrator/Dockerfile#L25
>
> Thank you!
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5] Collect config-docs in all featues when packaging product distribution

2017-09-07 Thread Dilan Udara Ariyaratne 
Hi Danesh,

With recent discussions on C5 configuration management, If I understood
correctly, deployment.yaml would not be the only option for a user to
manage configurations, but there will also
be options to directly manipulate configurations via environment variables
and system properties.

Shouldn't we be documenting those options as well ?

For example, if our objective is to change port offset,
[1] If we are going with environment variable approach, Which environment
variable we should use ?
[2] If we are going with system property approach, Which system property we
should use ?
[3] If we are going with deployment.yaml approach, Which key we should use ?

Thanks,
Dilan.

*Dilan U. Ariyaratne*
Senior Software Engineer
WSO2 Inc. 
Mobile: +94766405580 <%2B94766405580>
lean . enterprise . middleware


On Thu, Aug 31, 2017 at 1:17 PM, Chamila De Alwis  wrote:

> Hi Danesh,
>
> Thanks for bringing this up! This is a huge improvement and IMO we should
> include the reference YAML file in the product distribution for user
> reference purposes. It's true that hosted documentation would take care of
> most of that story, but there can be situations where the user only has a
> terminal and the product zip file, where a reference text file would come
> in handy.
>
> Just a minor query, what is the purpose of the generated secure-vault.yaml
> file?
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer | WSO2
> Blog: https://medium.com/@chamilad
>
>
>
> On Thu, Aug 31, 2017 at 11:37 AM, Danesh Kuruppu  wrote:
>
>> Hi all,
>>
>> With new global configuration model discussed in mail thread[1], we are
>> generating configuration files(for documentation purposes) automatically at
>> compile time by reading annotations and default values in config bean
>> classes. And those configuration files are packed in features under
>> config-docs directory like below(e.g).
>>
>> ├── features
>>> └── org.wso2.carbon.kernel_5.2.0.SNAPSHOT
>>> *   ├── config-docs*
>>> *   └── wso2.carbon.yaml*
>>> └── plugins
>>> └── org.wso2.carbon.core-5.2.0.SNAPSHOT.jar
>>>
>>
>>
>> Since those configuration files are only for documentation purposes, We
>> are not shipping them with product distribution. Currently those
>> configuration files are inside feature jar files and in order to read
>> relevant configuration file, we need to extract the jar file.
>>
>> In order solve this issue, we thought of collecting configuration docs in
>> all features when packaging product distribution using maven plugin. Maven
>> plugin will go through all features inside p2-repo
>> directory(distribution/target/p2-repo/features directory) and copy
>> configuration docs in each feature to one location like below
>> (distribution/target/config-docs)
>>
>> ├── distribution
>>  ├── target
>>
>>
>> * ├── config-docs ├── secure-vault.yaml
>>└── wso2.carbon.yaml*
>>  └── wso2carbon-kernel-5.2.0-SNAPSHOT.zip
>>
>> So when generating product distribution, we automatically get all
>> configuration files used in the product. This will also help when creating
>> product document.
>>
>> Appreciate your input on this.
>>
>> 1. http://wso2-oxygen-tank.10903.n7.nabble.com/Carbon-C5-Server
>> -Configuration-Model-td144549.html
>>
>> Thanks
>> --
>>
>> *Danesh Kuruppu*
>> Senior Software Engineer | WSO2
>>
>> Email: dan...@wso2.com
>> Mobile: +94 (77) 1690552 <+94%2077%20169%200552>
>> Web: WSO2 Inc 
>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Same feature with different versions in different runtimes

2017-09-07 Thread Kasun Siyambalapitiya 
Hi Dilan and all,

Pardon me for the late reply. Yes, I agree with your point due to the fact
that different feature versions including slight or major differences in
their implementation has been released as compatible features for WSO2
Carbon 4.4.x (Wilkes) [1] products,

For example,


   1. 
org.wso2.carbon.identity.application.authentication.framework.server_4.5.6.jar
   / org.wso2.carbon.identity.application.authentication.
   framework.server_5.7.5.jar
   2. org.wso2.carbon.directory.service.mgr.server_4.5.6.jar
   / org.wso2.carbon.directory.service.mgr.server_5.7.5.jar
   3. rg.wso2.carbon.forum.server_2.0.0.jar / org.wso2.carbon.forum.
   server_6.1.66.jar
   4. org.wso2.carbon.identity.core.server_4.5.5.jar
   / org.wso2.carbon.identity.core.server_5.7.5.jar
   5. org.wso2.carbon.identity.core.ui_4.5.5.jar
   / org.wso2.carbon.identity.core.ui_5.7.5.jar

Since all the jars mentioned above have major implementational changes
which are not backward compatible (as indicated by the major version no
change) there is a huge possibility of having a functional inconsistency in
the system if multiple versions of the same feature are used in different
runtimes. For example the format of data inserted and queried out from db
from previous version may differ from the how it is done in the latest
version leaving to inconsistencies in DB. IMO I think either we should
restrict to one version of a certain feature or allow up to it's next major
version. WDYT?


[1] http://product-dist.wso2.com/p2/carbon/releases/wilkes/features/

Thanks.

On Fri, Aug 18, 2017 at 8:39 AM, Dilan Udara Ariyaratne 
wrote:

> Hi Kasun and All,
>
> Let me raise a different, but fundamental concern to this issue. Please
> correct me if I am wrong.
>
> It's perfectly valid to have the same feature on different run-times (or
> profiles) of a product, but if that same feature appears in "different
> versions",
> meaning, with slight or major differences of their implementations, at
> different run-times of the product, wouldn't that open up any possibilities
> of functional inconsistencies or even failures to the overall system ?
>
> Thanks,
> Dilan.
>
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Thu, Aug 17, 2017 at 8:19 PM, Kasun Siyambalapitiya 
> wrote:
>
>> Hi Niranjan,
>>
>> When generating the p2-repository using `carbon-maven-plugin version 3.x`
>> this issue arises due to the fact that it resolves dependencies for each
>> given feature with the dependencies we defined in the pom itself (note that
>> the effective pom is used for the resolving). Since maven picks only one
>> version of a given dependency due the use of `nearest in the dependency
>> tree` strategy, a p2-repo with multiple versions of the same feature can
>> not be created by using the current `carbon-maven-plugin version 3.1.3`.
>>
>> But in the case of `carbon-maven-plugin version 1.5.x` this is possible
>> as the dependencies of each feature is defined in a string form as below
>>
>> org.apache.axis2.transport:org.apache.axis2.transport.jms.feature:
>>> ${axis2-transports.wso2.version.1.1.0.wso2v17}
>>
>>
>> and the version `${axis2-transports.wso2.version.1.1.0.wso2v17}` is
>> replaced with the value of the relevant property we defined in the pom.xml.
>> Since there are no restrictions like above in defining properties in
>> pom.xml this works.
>>
>> Thanks.
>>
>> On Thu, Aug 17, 2017 at 10:39 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Kasun,
>>>
>>> On Thu, Aug 17, 2017 at 10:04 AM, Kasun Siyambalapitiya <
>>> kasu...@wso2.com> wrote:
>>>
 Hi Niranjan,

 The build fails before successful generation of the p2-repo by giving
 the following error

 [ERROR] Failed to execute goal org.wso2.carbon.maven:carbon-f
> eature-plugin:3.1.1:generate-repo (p2-repo-generation) on project
> wso2carbon-kernel: Feature org.wso2.carbon.pax.exam.feature_5.2.0.1
> not found -> [Help 1]



 Since in the new C5 model the p2-repo containing all the features
 required for all the runtimes of the product, is generated at a single
 specified directory(by default the target directory) multiple version of
 the same feature cannot be generated as maven build will pick only one
 version of the dependency due to the use of "nearest in the dependency
 tree" strategy as shown in above mail. As a result although we can have
 multiple versions at the p2-repo per feature due to the above nature of
 maven, runtimes with different feature versions cannot be created in C5.
 This problem was not there in the previous C4 model as the profiles(runtime
 in C5 wording) were generated at separate locations and their respective
 p2-repos were created at their own locations(where the profile is created)
 [1]

 IMO this issue can

[Architecture] [Dev] WSO2 Stream Processor 4.0.0-M11 Released !

2017-09-07 Thread Anusha Jayasundara 
Hi All,


The WSO2 Analytics team is pleased to announce the release of *WSO2 Stream
Processor Version 4.0.0 Milestone 11*.

WSO2 Smart Analytics let digital business creating real-time, intelligent,
actionable business insights, and data products which are achieved by WSO2
Stream Processor's real-time, incremental & intelligent data processing
capabilities.

WSO2 Stream Processor can:

   -

   Receive events from various data sources
   -

   Process & correlate them in real-time with the sate of the art
   high-performance real-time Siddhi Complex Event Processing Engine that
   works with easy to learn the SQL-Like query language.
   -

   Process analysis that spans for longer time duration with its
   incremental processing capability by achieving high performance with low
   infrastructure cost.
   -

   Uses Machine Learning and other models to drive intelligent insights
   from the data
   -

   Notifications interesting event occurrences as alerts via multiple
   types of transport & let users visualize the results via customizable
   dashboards.
   -

   WSO2 SP is released under Apache Software License Version 2.0, one
   of the most business-friendly licenses available today.


You can find the product at
*https://github.com/wso2/product-sp/releases/download/v4.0.0-M11/wso2sp-4.0.0-M11.zip
*
Documentation at *https://docs.wso2.com/display/SP400/Introduction*/

Source code at *https://github.com/wso2/product-sp
/*

*WSO2 SP 4.0.0-M11 includes the following*

*New Features*

   - Reliable message processing with kafka
   - Non occurrence of event - siddhi pattern
   - Multiple primary-key support for inmemory tables
   - Streaming ML
  - Hoeffding classifier
  - K-means clustering
   - Editor improvements


*Reporting Issues*

Issues can be reported using the github issue tracker available at
https://github.com/wso2/product-sp

*Contact us*

WSO2 Stream Processor developers can be contacted via the mailing lists:

Developer List : d...@wso2.org | Subscribe
 | M



Alternatively, questions can also be raised in the Stackoverflow:

Forum http://stackoverflow.com/questwso2/



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

For more information on WSO2 Smart Analytics and Smart Analytics Solutions,
visit the WSO2 Smart Analytics Page .



*~ The WSO2 Analytics Team ~*
-- 

*Anusha Jayasundara*
Software Engineer | WSO2

Email : anus...@wso2.com
Mobile : +94772601160
Web : http://wso2.com
Lean.Enterprise.Middleware

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

[Architecture] WSO2 Identity Server 5.4.0 Alpha2 Released!

2017-09-07 Thread Hasintha Indrajee 
The WSO2 Identity Server team is pleased to announce the release of WSO2
Identity Server 5.4.0 Alpha2. You can download this distribution from the
following location.

Runtime:   https://github.com/wso2/product-is/releases
/tag/v5.4.0-alpha2

Following list contains all the features, improvements and bug fixes
available with this alpha2 release.
Bugs

   - [IDENTITY-6148 ] - Include
   recommended security filters to the web apps, by default
   - [IDENTITY-6256 ] - XACML
   fine grained permission model is not working after permission refactoring.
   - [IDENTITY-6311 ] - "kid"
   JWT header parameter shouldn't be a hard coded value
   - [IDENTITY-6328 ] - Client
   credentials grant should not return refresh token in response by default
   - [IDENTITY-6340 ] - Issue
   in ask password email template

Tasks

   - [IDENTITY-6339 ] - Remove
   EnableOAuthCache config from identity.xml

Improvements

   - [IDENTITY-4375 ] -
   RelayState can not be set dynamically in SSO agent
   - [IDENTITY-5093 ] - Provide
   a meaningful message for the attempt to execute scim operation while scim
   is not enabled
   - [IDENTITY-5095 ] -
   Repititive logs for SCIM user update
   - [IDENTITY-5487 ] - Better
   to trim the CSV values in Bulk User Import
   - [IDENTITY-5895 ] - Enhance
   default email templates attractive html templates
   - [IDENTITY-5987 ] - JIT
   Provisioned Users Cannot be Associated to Local Accounts Dynamically
   - [IDENTITY-6032 ] - Pass
   HTTP Request Headers to Grant Handlers
   - [IDENTITY-6342 ] -
   Improving the default behavior of ID token validator



*How To Contribute*
Your feedback is most welcome!
Mailing Lists
Join our mailing list and correspond with the developers directly.

   - Developer List: d...@wso2.org | Subscribe  | Mail
   Archive 
   - User Forum: StackOverflow
   

Reporting Issues
We encourage you to report issues, improvements and feature requests
regarding WSO2 Identity Server through public WSO2 Identity Server Runtime
JIRA  and Analytics JIRA



*~ The WSO2 Identity Server Team ~*

-- 
Hasintha Indrajee
WSO2, Inc.
Mobile:+94 771892453
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture