Re: [Dev] DAS minimum HA deployment in one node?

[Samuel Gnaniah]

I thought we recommend two nodes for minimum deployment in production
environments. Normally we document the minimum recommended deployment
pattern for production. Should we be documenting the configurations for 1
node as well?

*Samuel Gnaniah*
Lead Technical Writer

WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798

On Tue, Apr 12, 2016 at 10:45 AM, Nirmal Fernando  wrote:

> Great! Can we have this in docs please?
>
> On Tue, Apr 12, 2016 at 10:42 AM, Niranda Perera  wrote:
>
>> Yes, since both the nodes are in the same file system, there is no need
>> for a symbolic link
>>
>> best
>>
>> On Tue, Apr 12, 2016 at 10:34 AM, Gihan Anuruddha  wrote:
>>
>>> Normally what we are doing is stating one node path in both
>>> configuration files. Basically, this symbolic link is used to load some
>>> classes to runtime. Since both node are identical this won't be an issue
>>> IMO.
>>>
>>> Regards,
>>> Gihan
>>>
>>> On Tue, Apr 12, 2016 at 10:30 AM, Nirmal Fernando 
>>> wrote:
>>>
 Hi All,

 Is it possible to setup DAS minimum HA deployment in one node? AFAIS
 the requirement to create a symbolic link makes it impossible?

 --

 Thanks & regards,
 Nirmal

 Team Lead - WSO2 Machine Learner
 Associate Technical Lead - Data Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/



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


>>>
>>>
>>> --
>>> W.G. Gihan Anuruddha
>>> Senior Software Engineer | WSO2, Inc.
>>> M: +94772272595
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Niranda Perera*
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-71-554-8430
>> Twitter: @n1r44 
>> https://pythagoreanscript.wordpress.com/
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Common configuration for publishing events from carbon servers to DAS/CEP

[Niranjan Karunanandham]

Hi Malith,

On Fri, Mar 18, 2016 at 11:42 AM, Malith Dhanushka  wrote:

>
>
> On Fri, Mar 18, 2016 at 11:38 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> This new change is only for OSGi based servers in the platform right? Are
>> there any changes for standalone data publishing API's used with non-OSGi
>> servers in the platform or is it still the same as before? We have AS 6.0.0
>> which is based on pure tomcat and currently we are using the minimum
>> required data publishing libs and the standalone data publishing API's to
>> publish HTTP stats to DAS.
>>
>
> Yes this new change is only for OSGi based servers and no change in
> standalone data publishing API's.
>
>
>> On Mon, Mar 14, 2016 at 4:51 PM, Malith Dhanushka 
>> wrote:
>>
>>> Hi all,
>>>
>>> Please follow the steps bellow when publishing events from carbon
>>> servers to DAS/CEP. Here we keep the DAS/CEP server location in
>>> CARBON_HOME/repository/deployment/server/eventpublishers directory and this
>>> is common across platform.
>>>
>>> - Install the Event Publisher Aggregate feature from p2_repo [1]
>>>
>>> - Install Registry Core feature if not installed
>>>
>>> - Create event stream and deploy that to
>>> CARBON_HOME/repository/deployment/server/eventstreams
>>>
>>> - Create publishers for the created stream and deploy that to
>>>  CARBON_HOME/repository/deployment/server/eventpublishers
>>> Following is a sample configuration,
>>>
>>> 
>>> >> xmlns="http://wso2.org/carbon/eventpublisher;>
>>>   
>>>   
>>>   
>>> admin
>>> thrift
>>> non-blocking
>>> 0
>>> tcp://localhost:7611
>>> X
>>>   
>>> 
>>>
>>> - Publish events to the created stream using
>>> org.wso2.carbon.event.stream.core.EventStreamService OSGI service.
>>> Following is a sample code snippet.
>>>
>>> Event event = new Event();
>>> event.setTimeStamp(System.currentTimeMillis());
>>> event.setStreamId("streamTest:1.0.0");
>>> event.setPayloadData(new Object[]{data});
>>> eventStreamService.publish(event);
>>>
>>> Please note that Event Publisher Aggregate feature is not yet included
>>> in carbon feature repo. It will be available with the immediate analytics
>>> feature release.
>>>
>> Usually features are added to the p2-repo (carbon-feature-repository
repo) when products are released. The product team has to send a PR of all
the features they are using in the product (from the p2-profile-gen pom).
Therefore this feature should come from the PR from the products which are
using this feature when the product is released.


>
>>> [1]
>>> https://github.com/wso2/carbon-analytics-common/tree/master/features/event-publisher/org.wso2.carbon.event.publisher.aggregate.feature
>>>
>>> Thanks,
>>> Malith
>>> --
>>> Malith Dhanushka
>>> Senior Software Engineer - Data Technologies
>>> *WSO2, Inc. : wso2.com *
>>> *Mobile*  : +94 716 506 693
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Associate Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> *
>> Twitter - *http://twitter.com/kishanthan *
>>
>
>
>
> --
> Malith Dhanushka
> Senior Software Engineer - Data Technologies
> *WSO2, Inc. : wso2.com *
> *Mobile*  : +94 716 506 693
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>

Regards,
Nira

-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] DAS minimum HA deployment in one node?

[Nirmal Fernando]

Great! Can we have this in docs please?

On Tue, Apr 12, 2016 at 10:42 AM, Niranda Perera  wrote:

> Yes, since both the nodes are in the same file system, there is no need
> for a symbolic link
>
> best
>
> On Tue, Apr 12, 2016 at 10:34 AM, Gihan Anuruddha  wrote:
>
>> Normally what we are doing is stating one node path in both configuration
>> files. Basically, this symbolic link is used to load some classes to
>> runtime. Since both node are identical this won't be an issue IMO.
>>
>> Regards,
>> Gihan
>>
>> On Tue, Apr 12, 2016 at 10:30 AM, Nirmal Fernando 
>> wrote:
>>
>>> Hi All,
>>>
>>> Is it possible to setup DAS minimum HA deployment in one node? AFAIS the
>>> requirement to create a symbolic link makes it impossible?
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> W.G. Gihan Anuruddha
>> Senior Software Engineer | WSO2, Inc.
>> M: +94772272595
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>



-- 

Thanks & regards,
Nirmal

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

Re: [Dev] DAS minimum HA deployment in one node?

[Niranda Perera]

Yes, since both the nodes are in the same file system, there is no need for
a symbolic link

best

On Tue, Apr 12, 2016 at 10:34 AM, Gihan Anuruddha  wrote:

> Normally what we are doing is stating one node path in both configuration
> files. Basically, this symbolic link is used to load some classes to
> runtime. Since both node are identical this won't be an issue IMO.
>
> Regards,
> Gihan
>
> On Tue, Apr 12, 2016 at 10:30 AM, Nirmal Fernando  wrote:
>
>> Hi All,
>>
>> Is it possible to setup DAS minimum HA deployment in one node? AFAIS the
>> requirement to create a symbolic link makes it impossible?
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> W.G. Gihan Anuruddha
> Senior Software Engineer | WSO2, Inc.
> M: +94772272595
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] DAS minimum HA deployment in one node?

[Gihan Anuruddha]

Normally what we are doing is stating one node path in both configuration
files. Basically, this symbolic link is used to load some classes to
runtime. Since both node are identical this won't be an issue IMO.

Regards,
Gihan

On Tue, Apr 12, 2016 at 10:30 AM, Nirmal Fernando  wrote:

> Hi All,
>
> Is it possible to setup DAS minimum HA deployment in one node? AFAIS the
> requirement to create a symbolic link makes it impossible?
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
W.G. Gihan Anuruddha
Senior Software Engineer | WSO2, Inc.
M: +94772272595
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] DAS minimum HA deployment in one node?

[Nirmal Fernando]

Hi All,

Is it possible to setup DAS minimum HA deployment in one node? AFAIS the
requirement to create a symbolic link makes it impossible?

-- 

Thanks & regards,
Nirmal

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

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Pushpalanka Jayawardhana]

On Tue, Apr 12, 2016 at 6:58 AM, Johann Nallathamby  wrote:

> @Pushpalanka: Isn't the repo versions (all the repos, now that we have 46
> IINM maintained by IS team) going to be 5.10.0 since we have backward
> compatible API additions ?
>
Yes my mistake.. Next release version will be *5.1.0.*

>
> On Mon, Apr 11, 2016 at 3:40 AM, Pushpalanka Jayawardhana 
> wrote:
>
>>
>>
>> On Mon, Apr 11, 2016 at 1:53 PM, Dinusha Senanayaka 
>> wrote:
>>
>>> Hi IS Team,
>>>
>>> Do you have release date for identity-5.0.9 ? This fix is critical for
>>> App manager release.
>>>
>> We are working on to release the beta pack tomorrow.  Identity-5.0.9
>> release will be done with the RC pack, which will be by 25th in best case.
>>
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> On Mon, Apr 4, 2016 at 10:34 AM, Rushmin Fernando 
>>> wrote:
>>>
 Thanks Pulasthi !

 App Manager WIP code can be found in [1] and [2]

 Thanks
 Rushmin

 [1] -
 https://github.com/wso2/carbon-appmgt/tree/feature/kernel-4.4.5-upgrade

 [2]  -
 https://github.com/wso2/product-app-manager/tree/feature/kernel-4.4.5-upgrade

 On Fri, Apr 1, 2016 at 4:52 PM, Pulasthi Mahawithana <
 pulast...@wso2.com> wrote:

> Yes, we no longer use the wso2/carbon-identity repo for development.
> We use the repos in 'wso2-extensions'. However the group ids, artifact ids
> and versions follow the same from carbon-identity.
>
> On Fri, Apr 1, 2016 at 3:56 PM, Rushmin Fernando 
> wrote:
>
>> Thanks Supun !
>>
>> So is [1] obsolete now since the connector code resides in
>> 'wso2-extensions' account now ?
>>
>>
>> Thanks
>> Rushmin
>>
>> [1] -
>> https://github.com/wso2/carbon-identity/blob/master/features/provisioning/org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature
>>
>> On Fri, Apr 1, 2016 at 3:47 PM, Pulasthi Mahawithana <
>> pulast...@wso2.com> wrote:
>>
>>> Hi Rushmin,
>>>
>>> This issue was due to that component being moved from carbon-commons
>>> to analytic commons. Isura fixed that issue with [1] and [2]. Can you
>>> please try now?
>>>
>>> [1]
>>> https://github.com/wso2-extensions/identity-extension-parent/pull/6
>>> [2]
>>> https://github.com/wso2-extensions/identity-outbound-provisioning-salesforce/pull/6
>>>
>>> On Fri, Apr 1, 2016 at 12:21 PM, Rushmin Fernando 
>>> wrote:
>>>

 Hi Devs,

 We are in the process of upgrading the Carbon Kernel version to
 4.4.5

 During this upgrade we found out that
 "org.wso2.carbon.identity.provisioning.connector.salesforce.server" 
 feature
 is dependenct on a non-existing feature version of
 "org.wso2.carbon.databridge.commons.server"

 I opened a Jira to track this. [1]

 Had a chat with Pulasthi and this will be fixed with IS 5.2.0
 release which will happen in the next week.

 Until this is fixed, I'm proceeding with the identity
 5.0.9-SNAPSHOT having the issue fixed locally.

 Thanks
 Rushmin

 [1] - https://wso2.org/jira/browse/IDENTITY-4465

 --
 *Rushmin Fernando*
 *Technical Lead*

 WSO2 Inc.  - Lean . Enterprise . Middleware

 email : rush...@wso2.com
 mobile : +94772310855



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


>>>
>>>
>>> --
>>> *Pulasthi Mahawithana*
>>> Software Engineer
>>> WSO2 Inc., http://wso2.com/
>>> Mobile: +94-71-5179022
>>> Blog: http://blog.pulasthi.org
>>>
>>
>>
>>
>> --
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> email : rush...@wso2.com
>> mobile : +94772310855
>>
>>
>>
>
>
> --
> *Pulasthi Mahawithana*
> Software Engineer
> WSO2 Inc., http://wso2.com/
> Mobile: +94-71-5179022
> Blog: http://blog.pulasthi.org
>



 --
 *Rushmin Fernando*
 *Technical Lead*

 WSO2 Inc.  - Lean . Enterprise . Middleware

 email : rush...@wso2.com
 mobile : +94772310855



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


>>>
>>>
>>> --
>>> Dinusha Dilrukshi
>>> Associate Technical Lead
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94725255071
>>> Blog: http://dinushasblog.blogspot.com/

Re: [Dev] [App Cloud] Search By Tag feature in App Cloud

[Danushka Fernando]

I just checked the EC2 behavior. Since we have similar concept I would vote
for that.
Which is tag::
If we want to search the instances have that tag with particular key only
it would be like
tag:

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Tue, Apr 12, 2016 at 8:27 AM, Nishadi Kirielle  wrote:

> Hi All,
> Currently, I'm focusing on implementing the functionality to search
> applications by the provided tag in application listing index page. In
> implementing that functionality I'm planning to use the same search box
> used to search applications by their name to be used but the search phrase
> will begin with the 'tag' keyword. For example;
>  'tag:tomcat'
>
> Really appreciate your suggestions in proceeding with this.
>
> Thanks
> --
> *Nishadi Kirielle*
> *Software Engineering Intern*
> Mobile : +94 (0) 714722148
> Blog : http://nishadikirielle.blogspot.com/
> nish...@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

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

[Chamila De Alwis]

Hi Thanuja,

+1, although I'm again concerned with the structural complexity. However
when weighed against other options available (having the YAML files in the
same folder, enabling deep merge [1], etc) this is the best option as I
see.

`kubernetes/default.yaml` for WSO2 AM 1.10.0 would look something like the
following. This would get duplicated for each product version which is a
bit complex than needed and is unnecessary duplication IMO.

[image: Inline image 1]

[1] - [Dev] [Hiera] Deeper hash merge instead of Native hash merge?


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com



On Mon, Apr 11, 2016 at 4:15 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

>
>
> On Mon, Apr 11, 2016 at 2:06 PM, Chamila De Alwis 
> wrote:
>
>> Hi Pubudu,
>>
>> That's a good idea, however, we can't exactly map `environment` with the
>> `platform` concept. How about using a new level on top of the profile
>> specific level mapping to `platform`?
>>
>> :hierarchy:
>> - "node/%{::clientcert}"
>> *-
>> "wso2/%{::product_name}/%{::product_version}/%{::product_profile}-%{::platform}"*
>> - "wso2/%{::product_name}/%{::product_version}/%{::product_profile}"
>> - "wso2/%{::product_name}/%{::product_version}/default"
>> - "osfamily/%{::osfamily}"
>> - "vm_type/%{::vm_type}"
>> - wso2/common
>> - common
>>
>
> +1 for introducing a new level in hierarchy to lookup for platform
> specific data on top of profile specific data per product.
>
>>
>> This will allow us to extract the platform specific data only to one
>> layer up. An example would be,
>>
>> puppet-modules/hieradata/dev/wso2/wso2am/1.10.0/default-kubernetes.yaml
>>
>
> It would be better to have spearate folders for platform specific yaml
> files inside each product versions like below with changing the above hiera
> level to: *-
> "wso2/%{::product_name}/%{::product_version}/%{::product_profile}/%{::platform}"*
>
> hieradata/dev/wso2/wso2as/
>
> └── 5.3.0
>
> ├── default.yaml
>
> ├── <*platform*>
>
> │   ├── default.yaml
>
> │   ├── manager.yaml
>
> │   └── worker.yaml
>
> ├── kubernetes
>
> │   ├── default.yaml
>
> │   ├── manager.yaml
>
> │   └── worker.yaml
>
> ├── manager.yaml
>
> └── worker.yaml
>
>
> With the above structure, configs common to all platform will be there in
> the products' root level hierafiles. Only the platform specific configs
> related to a particular profile will be there in /.yaml
> (ex: proxy_ports).
>
>
>
>> WDYT?
>>
>>
>> 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 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Without duplicating files and adding new files, I would rather prefer to
>>> use the following hierarchy. For each and every different environment we
>>> can have product profiles and include the environment specific values. For
>>> Kubernetes, we can include the clustering section only in manager.yaml file
>>> which resides under environment Kubernetes. And the rest of the other
>>> configurations can be included in the generic file folder, i.e "
>>> wso2/%{::product_name}/%{::product_version}/%{::product_profile}".
>>>
>>>
>>> :hierarchy:
>>> - "node/%{::clientcert}" - - "
>>> wso2/%{::product_name}/%{::product_version}/%{::environment}
>>> /%{::product_profile}"
>>> - "wso2/%{::product_name}/%{::product_version}/%{::product_profile}"
>>> - "wso2/%{::product_name}/%{::product_version}/default"
>>> - "osfamily/%{::osfamily}"
>>> - "vm_type/%{::vm_type}"
>>> - wso2/common
>>> - common
>>>
>>>
>>> Thank you!
>>>
>>> On Mon, Apr 11, 2016 at 1:07 PM, Isuru Haththotuwa 
>>> wrote:
>>>


 On Mon, Apr 11, 2016 at 12:47 PM, Gayan Gunarathne 
 wrote:

>
>
> 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 
>> wrote:
>>
>>> Hi Chamila,
>>>
>>> On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis >> > 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 

[Dev] [App Cloud] Search By Tag feature in App Cloud

[Nishadi Kirielle]

Hi All,
Currently, I'm focusing on implementing the functionality to search
applications by the provided tag in application listing index page. In
implementing that functionality I'm planning to use the same search box
used to search applications by their name to be used but the search phrase
will begin with the 'tag' keyword. For example;
 'tag:tomcat'

Really appreciate your suggestions in proceeding with this.

Thanks
-- 
*Nishadi Kirielle*
*Software Engineering Intern*
Mobile : +94 (0) 714722148
Blog : http://nishadikirielle.blogspot.com/
nish...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Configuring load balancing in app cloud with HA Proxy

[Nishadi Kirielle]

Hi,
The limitation is there with the service load balancer. If we are going
with that approach we need to patch kubernetes service load balancer code
to annotate the services with port definitions. The current approach taken
is to create two services for https and http.
We can use the node ports as well. Already the host ports are available in
AWS load balancer.

Regards
Nishadi

On Thu, Apr 7, 2016 at 10:14 PM, Imesh Gunaratne  wrote:

>
>
> On Wed, Mar 16, 2016 at 10:49 AM, Nishadi Kirielle 
> wrote:
>>
>>
>> In the current deployment, we have tested a service with a single port
>> exposed. This is because the service identifies whether this is exposed to
>> http or https through the service annotation which is common to all exposed
>> ports in the service. If we are going with that approach, in order to
>> support http traffic and https traffic, we need several services. Thus,
>> currently I'm attempting to deploy a service with several exposed ports.
>>
>
> AFAIU this is not a restriction enforced by K8S services rather a
> limitation in the service load balancer (the way it uses service
> annotations) [3]. K8S services allow to define any number of annotations
> with any key/value pair. We can change the service load balancer to use an
> annotation per port to handle this.
>
>>
>> In addition, another concern is how the HAProxy load balancer itself is
>> exposed to external traffic. Currently it is done through host ports. If we
>> use node ports for this, it will expose the particular port in all the
>> nodes. But the use of host port will only expose the particular port in the
>> specified node.
>>
>
> Why do we use host ports instead of node ports? I believe traffic get
> delegated to HAProxy via an AWS load balancer. If so what would happen if
> the above host becomes unavailable?
>
> [3]
> https://github.com/nishadi/contrib/blob/master/service-loadbalancer/service_loadbalancer.go#L468
>
> Thanks
>
>
>>
>> Appreciate your feedback on the approach taken.
>>
>> Thanks
>>
>> [1].
>> https://github.com/nishadi/contrib/commit/f169044546dc8a84a359d889bb186aef83d9c422
>> [2].
>> https://github.com/nishadi/contrib/blob/master/service-loadbalancer/rc.yaml#L52
>>
>> On Mon, Mar 14, 2016 at 10:39 AM, Nishadi Kirielle 
>> wrote:
>>
>>> Hi all,
>>> +1 for going with SSL pass through approach. Once the testing with
>>> staging is done, I will focus on this approach.
>>>
>>> Thanks
>>>
>>> On Mon, Mar 14, 2016 at 10:29 AM, Manjula Rathnayake 
>>> wrote:
>>>
 Hi Imesh,

 On Mon, Mar 14, 2016 at 10:20 AM, Imesh Gunaratne 
 wrote:

> Hi Manjula,
>
> On Mon, Mar 14, 2016 at 10:06 AM, Manjula Rathnayake <
> manju...@wso2.com> wrote:
>
>> Hi Imesh,
>>
>> On Mon, Mar 14, 2016 at 9:56 AM, Imesh Gunaratne 
>> wrote:
>>
>>>
>>> On Sun, Mar 13, 2016 at 11:36 PM, Nishadi Kirielle >> > wrote:
>>>
 Hi all,
 Currently I'm working on configuring HAProxy load balancing support
 for app cloud.
 In checking the session affinity functionality in kuberenetes, I
 have verified the load balancing of http traffic with HAProxy. It 
 could be
 done using kubernetes contribution repo, 'service loadbalancer' [1].

 In order to check the load balancing with https traffic the taken
 approach is SSL termination.In the scenario of app cloud, kubernetes
 cluster is not directly exposed and the load balancer exists within the
 cluster. Thus the communication between the application servers and the
 load balancer happens internally. Although SSL termination ends the 
 secure
 connection at the load balancer, due to the above mentioned reasons, 
 SSL
 termination seems to be a better solution. The reason for the use of 
 SSL
 termination over SSL pass through is because of the complexity of 
 handling
 a separate SSL certificate for each server behind the load balancer in 
 the
 case of SSL pass through.

 -1 for this approach, IMO this has a major security risk.
>>>
>>> Let me explain the problem. If we offload SSL at the service load
>>> balancer, all traffic beyond the load balancer will use HTTP and the
>>> message content will be visible to anyone on network inside K8S. Which
>>> means someone can simply start a container in K8S and trace all HTTP
>>> traffic going through.
>>>
>>
>
>> Below is from HA Proxy documentation[1]. AFAIU, HA Proxy to backend
>> server communication happens with HTTPS enabled but not validating the
>> server certificate.
>>
>
>
>> verify
>> 
>> [none|required]
>>
>> This 

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Johann Nallathamby]

@Pushpalanka: Isn't the repo versions (all the repos, now that we have 46
IINM maintained by IS team) going to be 5.10.0 since we have backward
compatible API additions ?

On Mon, Apr 11, 2016 at 3:40 AM, Pushpalanka Jayawardhana 
wrote:

>
>
> On Mon, Apr 11, 2016 at 1:53 PM, Dinusha Senanayaka 
> wrote:
>
>> Hi IS Team,
>>
>> Do you have release date for identity-5.0.9 ? This fix is critical for
>> App manager release.
>>
> We are working on to release the beta pack tomorrow.  Identity-5.0.9
> release will be done with the RC pack, which will be by 25th in best case.
>
>>
>> Regards,
>> Dinusha.
>>
>> On Mon, Apr 4, 2016 at 10:34 AM, Rushmin Fernando 
>> wrote:
>>
>>> Thanks Pulasthi !
>>>
>>> App Manager WIP code can be found in [1] and [2]
>>>
>>> Thanks
>>> Rushmin
>>>
>>> [1] -
>>> https://github.com/wso2/carbon-appmgt/tree/feature/kernel-4.4.5-upgrade
>>>
>>> [2]  -
>>> https://github.com/wso2/product-app-manager/tree/feature/kernel-4.4.5-upgrade
>>>
>>> On Fri, Apr 1, 2016 at 4:52 PM, Pulasthi Mahawithana >> > wrote:
>>>
 Yes, we no longer use the wso2/carbon-identity repo for development. We
 use the repos in 'wso2-extensions'. However the group ids, artifact ids and
 versions follow the same from carbon-identity.

 On Fri, Apr 1, 2016 at 3:56 PM, Rushmin Fernando 
 wrote:

> Thanks Supun !
>
> So is [1] obsolete now since the connector code resides in
> 'wso2-extensions' account now ?
>
>
> Thanks
> Rushmin
>
> [1] -
> https://github.com/wso2/carbon-identity/blob/master/features/provisioning/org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature
>
> On Fri, Apr 1, 2016 at 3:47 PM, Pulasthi Mahawithana <
> pulast...@wso2.com> wrote:
>
>> Hi Rushmin,
>>
>> This issue was due to that component being moved from carbon-commons
>> to analytic commons. Isura fixed that issue with [1] and [2]. Can you
>> please try now?
>>
>> [1]
>> https://github.com/wso2-extensions/identity-extension-parent/pull/6
>> [2]
>> https://github.com/wso2-extensions/identity-outbound-provisioning-salesforce/pull/6
>>
>> On Fri, Apr 1, 2016 at 12:21 PM, Rushmin Fernando 
>> wrote:
>>
>>>
>>> Hi Devs,
>>>
>>> We are in the process of upgrading the Carbon Kernel version to 4.4.5
>>>
>>> During this upgrade we found out that
>>> "org.wso2.carbon.identity.provisioning.connector.salesforce.server" 
>>> feature
>>> is dependenct on a non-existing feature version of
>>> "org.wso2.carbon.databridge.commons.server"
>>>
>>> I opened a Jira to track this. [1]
>>>
>>> Had a chat with Pulasthi and this will be fixed with IS 5.2.0
>>> release which will happen in the next week.
>>>
>>> Until this is fixed, I'm proceeding with the identity 5.0.9-SNAPSHOT
>>> having the issue fixed locally.
>>>
>>> Thanks
>>> Rushmin
>>>
>>> [1] - https://wso2.org/jira/browse/IDENTITY-4465
>>>
>>> --
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> email : rush...@wso2.com
>>> mobile : +94772310855
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pulasthi Mahawithana*
>> Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022
>> Blog: http://blog.pulasthi.org
>>
>
>
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>


 --
 *Pulasthi Mahawithana*
 Software Engineer
 WSO2 Inc., http://wso2.com/
 Mobile: +94-71-5179022
 Blog: http://blog.pulasthi.org

>>>
>>>
>>>
>>> --
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> email : rush...@wso2.com
>>> mobile : +94772310855
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Associate Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> Pushpalanka.
> --
> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
> Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
> Mobile: +94779716248
> Blog: pushpalankajaya.blogspot.com/ | LinkedIn:
> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*

Re: [Dev] [GREG-5.2.0] Writing extension to replicate more artifact metadata in Store

[Praneesha Chandrasiri]

Noted. Created a doc JIRA in [1] to track this.

Thanks Ayesha!


[1] https://wso2.org/jira/browse/DOCUMENTATION-3216

On Mon, Apr 11, 2016 at 8:12 PM, Chalitha Waldeniyage 
wrote:

> Very Useful.
>
> On Mon, Apr 11, 2016 at 8:05 PM, Ayesha Dissanayaka 
> wrote:
>
>> Hi,
>>
>> I have written this blog-post
>> [1]
>> on how to extend  WSO2GREG-5.2.0 - using Store extensions to replicate more
>> artifact metadata in Store other than the default fields.
>>
>> @Praneesha: Please, include content in GREG-5.2.0 docs as relevant.
>>
>> [1]
>> http://asadistechspace.blogspot.com/2016/04/wso2greg-520-writing-extension-to.html#.Vwu0Dl4hv7A
>>
>> Thanks!
>> -Ayesha
>>
>>
>> --
>> *Ayesha Dissanayaka*
>> Software Engineer,
>> WSO2, Inc : http://wso2.com
>> 
>> 20, Palmgrove Avenue, Colombo 3
>> E-Mail: aye...@wso2.com 
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Documentation Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to documentation+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
>
> --
> *Chalitha Maheshwari*
> Software Engineer-QA,
> WSO2 Inc.
>
> *E-mail:* chali...@wso2.com
> *Mobile: *+94710 411 112
>



-- 
Thanks & Best Regards,
*Praneesha Chandrasiri*
*Technical Writer*
*WSO2 Inc. *
*Mobile: +(94) 718156888*
*E-mail: pranee...@wso2.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[Geesara Prathap]

Hi Zhou,

Seems like you are on the right track now!

Regards,
Geesara

On Mon, Apr 11, 2016 at 7:08 PM, 云展智创  wrote:

> Geesara,
>
> Thank you very much! I can pass the building process of the new device
> types.
>
> －－
> Zhanwen Zhou (Jason)
>
> 在 2016年4月11日，下午4:14，Geesara Prathap  写道：
>
> Hi Zhou,
>
> Is that right to select 4 in below step?  You should select 2
>
> What’s the difference between 2 and 4 archetype selection? In maven
> archetype plugin groupId renamed from m3 to m4. In M3 it was named as
> cdmf.devicetype. But m4 onwards it named as org.wso2.cdmf.devicetype.
> Please follow the instruction in README[1]
> .
> It says everything you need to follow.
>
> 1.
> https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
>
> Thanks,
> Geesara
>
> On Mon, Apr 11, 2016 at 1:31 PM, 云展智创  wrote:
>
>> Hi Shabir/Geesara,
>>
>> Is that right to select 4 in below step? What’s the difference between 2
>> and 4 archetype selection?
>>
>> $ mvn archetype:generate -DarchetypeCatalog=local
>> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>> MaxPermSize=1024m; support was removed in 8.0
>> [INFO] Scanning for projects...
>> [INFO]
>>
>> [INFO]
>> 
>> [INFO] Building Maven Stub Project (No POM) 1
>> [INFO]
>> 
>> [INFO]
>> [INFO] >>> maven-archetype-plugin:2.4:generate (default-cli) >
>> generate-sources @ standalone-pom >>>
>> [INFO]
>> [INFO] <<< maven-archetype-plugin:2.4:generate (default-cli) <
>> generate-sources @ standalone-pom <<<
>> [INFO]
>> [INFO] --- maven-archetype-plugin:2.4:generate (default-cli) @
>> standalone-pom ---
>> [INFO] Generating project in Interactive mode
>> [INFO] No archetype defined. Using maven-archetype-quickstart
>> (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
>> Choose archetype:
>> 1: local -> org.wso2.iot:mdm-android-agent-archetype (Creates a
>> MDM-Android agent project)
>> 2: local -> cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF Device
>> Type Archetype)
>> 3: local -> org.wso2.mdm:mdm-android-agent-archetype (Creates a
>> MDM-Android agent project)
>> 4: local -> org.wso2.cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF
>> Device Type Archetype)
>> Choose a number or apply filter (format: [groupId:]artifactId, case
>> sensitive contains): : 4
>>
>> －－
>> Zhanwen Zhou (Jason),
>>
>> 在 2016年4月11日，下午3:08，Shabir Mohamed  写道：
>>
>> Hi Zhou,
>>
>> If you still get any additional errors, please do send us the errors
>> printed in the error logs at:
>> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-
>> runtime/0.13.0/eclipse/
>>
>> so we could deduce why the device-deployer actually failed.
>>
>> Regards
>>
>> -
>> *Shabir Mohamed*
>> *Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> Email: sha...@wso2.com 
>> Mobile: +94 77 3516019 | +94 71 6583393
>>
>> On Mon, Apr 11, 2016 at 12:27 PM, Geesara Prathap 
>> wrote:
>>
>>> Hi Zhou,
>>>
>>> copied file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the
>>> repository/components/plugins folder)
>>>
>>> No need to copy any of *.jar files manually. All necessary *jar files
>>> are copied by maven archetype when building device type plugin.
>>>
>>> I found that the feature target file had been built (but I didn’t know
>>> why the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature
>>> folder of my device type, so I used following command to install it,
>>> successfully finished.
>>>
>>> the default version is set to 1.0-SNAPSHOT when building new device type
>>> plugin. If you need you can change as you require. But please define
>>> correct version, groupid and artifactId in device-deploye.xml as
>>> mention here[1].
>>>
>>>
>>>
>>> 1.
>>> https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
>>> (*branch IoTS-1.0.0-M3*)
>>>
>>> Thanks,
>>> Geesara
>>>
>>> On Mon, Apr 11, 2016 at 12:04 PM, Charitha Goonetilleke <
>>> charit...@wso2.com> wrote:
>>>
 [Adding Ayyoob & Geesara to the thread]

 Hi Zhou,

 Since we are working with next milestone release, archtype in
 product-iots master branch will not generate compatible device type plugin
 for M3 pack. It is the reason for above mentioned issues. So please
 checkout M3 compatible archtype from this link[2] and try to regenerate
 your device type with it.

 Also, with given M3 compatible archtype, you don't want to copy any jar
 file to plugins directory by your self.

 [1]
 https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M3/components/device-mgt-iot
 [2]
 

Re: [Dev] [GREG-5.2.0] Writing extension to replicate more artifact metadata in Store

[Chalitha Waldeniyage]

Very Useful.

On Mon, Apr 11, 2016 at 8:05 PM, Ayesha Dissanayaka  wrote:

> Hi,
>
> I have written this blog-post
> [1]
> on how to extend  WSO2GREG-5.2.0 - using Store extensions to replicate more
> artifact metadata in Store other than the default fields.
>
> @Praneesha: Please, include content in GREG-5.2.0 docs as relevant.
>
> [1]
> http://asadistechspace.blogspot.com/2016/04/wso2greg-520-writing-extension-to.html#.Vwu0Dl4hv7A
>
> Thanks!
> -Ayesha
>
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 Documentation Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to documentation+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>



-- 
*Chalitha Maheshwari*
Software Engineer-QA,
WSO2 Inc.

*E-mail:* chali...@wso2.com
*Mobile: *+94710 411 112
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GREG-5.2.0] Writing extension to replicate more artifact metadata in Store

[Ayesha Dissanayaka]

Hi,

I have written this blog-post
[1]
on how to extend  WSO2GREG-5.2.0 - using Store extensions to replicate more
artifact metadata in Store other than the default fields.

@Praneesha: Please, include content in GREG-5.2.0 docs as relevant.

[1]
http://asadistechspace.blogspot.com/2016/04/wso2greg-520-writing-extension-to.html#.Vwu0Dl4hv7A

Thanks!
-Ayesha


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

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

Re: [Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[云展智创]

Geesara,

Thank you very much! I can pass the building process of the new device types. 

－－
Zhanwen Zhou (Jason)

在 2016年4月11日，下午4:14，Geesara Prathap  写道：

> Hi Zhou,
> 
> Is that right to select 4 in below step?  You should select 2
> 
> What’s the difference between 2 and 4 archetype selection? In maven archetype 
> plugin groupId renamed from m3 to m4. In M3 it was named as cdmf.devicetype. 
> But m4 onwards it named as org.wso2.cdmf.devicetype. Please follow the 
> instruction in README[1]. It says everything you need to follow.
> 
> 1. https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
> 
> Thanks,
> Geesara
> 
> On Mon, Apr 11, 2016 at 1:31 PM, 云展智创  wrote:
> Hi Shabir/Geesara,
> 
> Is that right to select 4 in below step? What’s the difference between 2 and 
> 4 archetype selection?
> 
> $ mvn archetype:generate -DarchetypeCatalog=local
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; 
> support was removed in 8.0
> [INFO] Scanning for projects...
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO] 
> 
> [INFO] 
> [INFO] >>> maven-archetype-plugin:2.4:generate (default-cli) > 
> generate-sources @ standalone-pom >>>
> [INFO] 
> [INFO] <<< maven-archetype-plugin:2.4:generate (default-cli) < 
> generate-sources @ standalone-pom <<<
> [INFO] 
> [INFO] --- maven-archetype-plugin:2.4:generate (default-cli) @ standalone-pom 
> ---
> [INFO] Generating project in Interactive mode
> [INFO] No archetype defined. Using maven-archetype-quickstart 
> (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
> Choose archetype:
> 1: local -> org.wso2.iot:mdm-android-agent-archetype (Creates a MDM-Android 
> agent project)
> 2: local -> cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF Device Type 
> Archetype)
> 3: local -> org.wso2.mdm:mdm-android-agent-archetype (Creates a MDM-Android 
> agent project)
> 4: local -> org.wso2.cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF 
> Device Type Archetype)
> Choose a number or apply filter (format: [groupId:]artifactId, case sensitive 
> contains): : 4
> 
> －－
> Zhanwen Zhou (Jason), 
> 
> 在 2016年4月11日，下午3:08，Shabir Mohamed  写道：
> 
>> Hi Zhou,
>> 
>> If you still get any additional errors, please do send us the errors printed 
>> in the error logs at:
>> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/
>> 
>> so we could deduce why the device-deployer actually failed.
>> 
>> Regards
>> 
>> -
>> Shabir Mohamed
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> Email: sha...@wso2.com 
>> Mobile: +94 77 3516019 | +94 71 6583393
>> 
>> On Mon, Apr 11, 2016 at 12:27 PM, Geesara Prathap  wrote:
>> Hi Zhou,
>> 
>> copied file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the 
>> repository/components/plugins folder)
>> 
>> No need to copy any of *.jar files manually. All necessary *jar files are 
>> copied by maven archetype when building device type plugin. 
>> 
>> I found that the feature target file had been built (but I didn’t know why 
>> the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature folder 
>> of my device type, so I used following command to install it, successfully 
>> finished.
>> 
>> the default version is set to 1.0-SNAPSHOT when building new device type 
>> plugin. If you need you can change as you require. But please define correct 
>> version, groupid and artifactId in device-deploye.xml as mention here[1]. 
>> 
>> 
>> 
>> 1. https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3 
>> (branch IoTS-1.0.0-M3)
>> 
>> Thanks,
>> Geesara
>> 
>> On Mon, Apr 11, 2016 at 12:04 PM, Charitha Goonetilleke  
>> wrote:
>> [Adding Ayyoob & Geesara to the thread]
>> 
>> Hi Zhou,
>> 
>> Since we are working with next milestone release, archtype in product-iots 
>> master branch will not generate compatible device type plugin for M3 pack. 
>> It is the reason for above mentioned issues. So please checkout M3 
>> compatible archtype from this link[2] and try to regenerate your device type 
>> with it.
>> 
>> Also, with given M3 compatible archtype, you don't want to copy any jar file 
>> to plugins directory by your self.
>> 
>> [1] 
>> https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M3/components/device-mgt-iot
>> [2] 
>> https://github.com/wso2/product-iots/tree/master/modules/tools/cdmf-devicetype-archetype
>> [3] https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
>> 
>> Thanks & Regards,
>> /charithag
>> 
>> 
>> On Mon, Apr 11, 2016 at 11:10 AM, 云展智创  wrote:
>> Hi all,
>> 
>> I created a 

[Dev] [Ann] WSO2 App Cloud 3.0.0-Alpha Released!

[Punnadi Gunarathna]

WSO2 App Cloud 3.0.0-Alpha Release

WSO2 App Cloud team is pleased to announce the release of version
3.0.0-Alpha of the WSO2 App Cloud.

WSO2 App Cloud is a multi-tenant, elastic and self-service enterprise
platform that enables hosting applications written in multiple languages on
multiple runtimes. Currently supported runtimes are wso2as, msf4j and php.

The main goal of this release is to finetune the existing features and make
app cloud more stable.

Resolved Issues:

   -

   WSO2 App Cloud resolved issues
   

​​- Source repository can be found in [1]

-This release of App Cloud is available in [2]

-Documentation can be found in [3]

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 App Cloud through the public WSO2 App Cloud JIRA
.

[1] https://github.com/wso2/app-cloud/tree/v3.0.0-alpha

[2] https://newapps.cloud.wso2.com/appmgt/site/pages/index.jag
[3]https://docs.wso2.com/display/AppCloud/About+WSO2+App+Cloud



-- 

Thanks and Regards,

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


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

[Dev] WSO2 Carbon Feature Plugin 2.0.1 Released

[Niranjan Karunanandham]

*WSO2 Carbon Feature Plugin 2.0.1 Released*

The Carbon team is pleased to announce the release of Carbon Feature Plugin
2.0.1. It is now available to download from here
.

*Improvements and Bug fixes*
https://wso2.org/jira/issues/?filter=13021

*Known Issues*
https://wso2.org/jira/issues/?filter=13022

*How to Contribute*

   - WSO2 Carbon Feature Plugin code is hosted in github.
   - The Git repository is https://github.com/wso2/carbon-maven-plugins
   - Carbon Feature Plugin 2.0.1 release tag is
   https://github.com/wso2/carbon-maven-plugins/releases/tag/v2.0.1
   - Please report issues at Carbon Feature Plugin Jira,
https://wso2.org/jira/browse/CMVNPLG
   


*Contact Us *

​WSO2 Carbon developers​ can be contacted via following mailing lists:

   - WSO2 Developers List: dev@wso2.org
   - WSO2 Architecture List: architect...@wso2.org


Best Regards
Carbon Team​

-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] C5 Server startup hangs intermittently

[Rasika Perera]

Hi All,

​Didn't get this error recently. I have removed some redundant OSGi
capability headers(which was added earlier) from the code. May be it might
be the case.

Regards,
~Rasika

On Mon, Apr 11, 2016 at 4:40 PM, Sumedha Rubasinghe 
wrote:

> I added the logs. But it did not get reproduced during the short time I
> worked with it afterwards.
>
> Sajith/Rasika,
> Do you guys also get this?
>
>
> On Mon, Apr 11, 2016 at 1:53 PM, Afkham Azeez  wrote:
>
>> Was this resolved?
>>
>> On Mon, Apr 4, 2016 at 4:06 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Can we enable debug logs for "org.wso2.carbon.kernel.
>>> internal.startupresolver" package and check which component is causing
>>> the issue? I can take a look at this and find the root cause, if needed.
>>>
>>> On Mon, Apr 4, 2016 at 1:11 PM, Sumedha Rubasinghe 
>>> wrote:
>>>
 But it's intermittent. Manu also said he has faced this several times.
 AFAIU, fix to be applied @ C5 level?




 On Mon, Apr 4, 2016 at 1:08 PM, Sameera Jayasoma 
 wrote:

> Hi Sumedha,
>
> This because of a failure in netty component. It has failed to
> register transports.
>
> Thanks,
> Sameera.
>
> On Mon, Apr 4, 2016 at 1:01 PM, Sumedha Rubasinghe 
> wrote:
>
>> # Normal server bootup
>> #
>>
>> Sumedha-2:wso2uuf-1.0.0-SNAPSHOT sumedha$ bin/carbon.sh
>> JAVA_HOME environment variable is set to
>> /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
>> CARBON_HOME environment variable is set to
>> /Volumes/data/projects/wso2/uuf/M3/wso2uuf-1.0.0-SNAPSHOT
>> osgi> [2016-04-04 09:46:13,407]  INFO
>> {org.wso2.msf4j.internal.MicroservicesServerSC} - All microservices are
>> available
>> [2016-04-04 09:46:13,422]  INFO
>> {org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent}
>> - All CarbonNettyServerInitializers are available
>> [2016-04-04 09:46:13,423]  INFO
>> {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Starting
>> Netty Http Transport Listener
>> [2016-04-04 09:46:13,428]  INFO
>> {org.wso2.msf4j.internal.MicroservicesRegistry} - Added microservice:
>> org.wso2.carbon.uuf.UUFService@7f932479
>> [2016-04-04 09:46:13,509]  INFO
>> {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Netty
>> Listener starting on port 8080
>> [2016-04-04 09:46:13,511]  INFO
>> {org.wso2.carbon.kernel.internal.CarbonStartupHandler} - WSO2 Carbon
>> started in 1.303 sec
>>
>>
>>
>> # Same Server, hanged during bootup
>> #
>> Sumedha-2:wso2uuf-1.0.0-SNAPSHOT sumedha$ bin/carbon.sh
>> JAVA_HOME environment variable is set to
>> /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
>> CARBON_HOME environment variable is set to
>> /Volumes/data/projects/wso2/uuf/M3/wso2uuf-1.0.0-SNAPSHOT
>> osgi> [2016-04-04 09:45:12,668]  INFO
>> {org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent}
>> - All CarbonNettyServerInitializers are available
>> [2016-04-04 09:45:12,672]  INFO
>> {org.wso2.msf4j.internal.MicroservicesRegistry} - Added microservice:
>> org.wso2.carbon.uuf.UUFService@51f5356e
>> [2016-04-04 09:45:42,625]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
>> - Waiting on pending capability registration. Capability:
>> org.wso2.msf4j.Interceptor
>> [2016-04-04 09:45:42,626]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
>> - Waiting on pending capability registration. Capability:
>> org.wso2.msf4j.Microservice
>> [2016-04-04 09:45:42,626]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
>> - Waiting on pending capability registration. Capability:
>> org.wso2.msf4j.internal.MicroservicesServerSC
>> [2016-04-04 09:45:42,626]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
>> - Waiting on pending capability registration. Capability:
>> org.wso2.carbon.kernel.transports.CarbonTransport
>> [2016-04-04 09:45:42,626]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
>> - Waiting on pending capability registration. Capability:
>> org.wso2.carbon.kernel.deployment.DeploymentService
>> [2016-04-04 09:45:42,626]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
>> - Waiting on pending capability registration. Capability:
>> org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent
>>
>>
>>
>>
>>
>> --

Re: [Dev] [Architecture] [C5] Must Inject CarbonServerInfo when writing OSGi Test Cases

[Aruna Karunarathna]

On Mon, Apr 11, 2016 at 4:47 PM, Nilmini Perera  wrote:

> Updated the doc [1]. Hope this will do. Let me know if anything is
> incorrect.
>

Looks good. Thanks Nilmini.

>
> [1] https://docs.wso2.com/display/Carbon500/In-Container+OSGi+Testing
>
> Thanks,
> Nilmini
>
> On Fri, Apr 8, 2016 at 12:13 AM, Imesh Gunaratne  wrote:
>
>> Hi Aruna,
>>
>> On Thu, Apr 7, 2016 at 6:21 PM, Aruna Karunarathna 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> When writing OSGi Test Cases, Please Inject the CarbonServerInfo service
>>> [1]. Otherwise the container wont start properly and the test cases will
>>> fail.
>>>
>>> After injecting the service it will guarantee that the server will fully
>>> start, before running the test cases. e.g. [2]
>>>
>>
>> Would you mind mentioning what CarbonServerInfo does and why containers
>> would not start without it?
>>
>> 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
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nilmini Perera
>
> Senior Technical Writer
> WSO2 Inc.
>
> Mobile: 0094776722152
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Aruna Sujith Karunarathna *
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [C5] Must Inject CarbonServerInfo when writing OSGi Test Cases

[Nilmini Perera]

Updated the doc [1]. Hope this will do. Let me know if anything is
incorrect.

[1] https://docs.wso2.com/display/Carbon500/In-Container+OSGi+Testing

Thanks,
Nilmini

On Fri, Apr 8, 2016 at 12:13 AM, Imesh Gunaratne  wrote:

> Hi Aruna,
>
> On Thu, Apr 7, 2016 at 6:21 PM, Aruna Karunarathna  wrote:
>
>> Hi Devs,
>>
>> When writing OSGi Test Cases, Please Inject the CarbonServerInfo service
>> [1]. Otherwise the container wont start properly and the test cases will
>> fail.
>>
>> After injecting the service it will guarantee that the server will fully
>> start, before running the test cases. e.g. [2]
>>
>
> Would you mind mentioning what CarbonServerInfo does and why containers
> would not start without it?
>
> 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
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nilmini Perera

Senior Technical Writer
WSO2 Inc.

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

Re: [Dev] C5 Server startup hangs intermittently

[Sumedha Rubasinghe]

I added the logs. But it did not get reproduced during the short time I
worked with it afterwards.

Sajith/Rasika,
Do you guys also get this?


On Mon, Apr 11, 2016 at 1:53 PM, Afkham Azeez  wrote:

> Was this resolved?
>
> On Mon, Apr 4, 2016 at 4:06 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Can we enable debug logs for "org.wso2.carbon.kernel.
>> internal.startupresolver" package and check which component is causing
>> the issue? I can take a look at this and find the root cause, if needed.
>>
>> On Mon, Apr 4, 2016 at 1:11 PM, Sumedha Rubasinghe 
>> wrote:
>>
>>> But it's intermittent. Manu also said he has faced this several times.
>>> AFAIU, fix to be applied @ C5 level?
>>>
>>>
>>>
>>>
>>> On Mon, Apr 4, 2016 at 1:08 PM, Sameera Jayasoma 
>>> wrote:
>>>
 Hi Sumedha,

 This because of a failure in netty component. It has failed to register
 transports.

 Thanks,
 Sameera.

 On Mon, Apr 4, 2016 at 1:01 PM, Sumedha Rubasinghe 
 wrote:

> # Normal server bootup
> #
>
> Sumedha-2:wso2uuf-1.0.0-SNAPSHOT sumedha$ bin/carbon.sh
> JAVA_HOME environment variable is set to
> /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
> CARBON_HOME environment variable is set to
> /Volumes/data/projects/wso2/uuf/M3/wso2uuf-1.0.0-SNAPSHOT
> osgi> [2016-04-04 09:46:13,407]  INFO
> {org.wso2.msf4j.internal.MicroservicesServerSC} - All microservices are
> available
> [2016-04-04 09:46:13,422]  INFO
> {org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent}
> - All CarbonNettyServerInitializers are available
> [2016-04-04 09:46:13,423]  INFO
> {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Starting
> Netty Http Transport Listener
> [2016-04-04 09:46:13,428]  INFO
> {org.wso2.msf4j.internal.MicroservicesRegistry} - Added microservice:
> org.wso2.carbon.uuf.UUFService@7f932479
> [2016-04-04 09:46:13,509]  INFO
> {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Netty
> Listener starting on port 8080
> [2016-04-04 09:46:13,511]  INFO
> {org.wso2.carbon.kernel.internal.CarbonStartupHandler} - WSO2 Carbon
> started in 1.303 sec
>
>
>
> # Same Server, hanged during bootup
> #
> Sumedha-2:wso2uuf-1.0.0-SNAPSHOT sumedha$ bin/carbon.sh
> JAVA_HOME environment variable is set to
> /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
> CARBON_HOME environment variable is set to
> /Volumes/data/projects/wso2/uuf/M3/wso2uuf-1.0.0-SNAPSHOT
> osgi> [2016-04-04 09:45:12,668]  INFO
> {org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent}
> - All CarbonNettyServerInitializers are available
> [2016-04-04 09:45:12,672]  INFO
> {org.wso2.msf4j.internal.MicroservicesRegistry} - Added microservice:
> org.wso2.carbon.uuf.UUFService@51f5356e
> [2016-04-04 09:45:42,625]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
> - Waiting on pending capability registration. Capability:
> org.wso2.msf4j.Interceptor
> [2016-04-04 09:45:42,626]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
> - Waiting on pending capability registration. Capability:
> org.wso2.msf4j.Microservice
> [2016-04-04 09:45:42,626]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
> - Waiting on pending capability registration. Capability:
> org.wso2.msf4j.internal.MicroservicesServerSC
> [2016-04-04 09:45:42,626]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
> - Waiting on pending capability registration. Capability:
> org.wso2.carbon.kernel.transports.CarbonTransport
> [2016-04-04 09:45:42,626]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
> - Waiting on pending capability registration. Capability:
> org.wso2.carbon.kernel.deployment.DeploymentService
> [2016-04-04 09:45:42,626]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
> - Waiting on pending capability registration. Capability:
> org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent
>
>
>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



 --
 Sameera Jayasoma,
 Software Architect,

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://blog.sameera.org
 twitter: https://twitter.com/sameerajayasoma
 flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
 Mobile: 

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

[Thanuja Uruththirakodeeswaran]

On Mon, Apr 11, 2016 at 2:06 PM, Chamila De Alwis  wrote:

> Hi Pubudu,
>
> That's a good idea, however, we can't exactly map `environment` with the
> `platform` concept. How about using a new level on top of the profile
> specific level mapping to `platform`?
>
> :hierarchy:
> - "node/%{::clientcert}"
> *-
> "wso2/%{::product_name}/%{::product_version}/%{::product_profile}-%{::platform}"*
> - "wso2/%{::product_name}/%{::product_version}/%{::product_profile}"
> - "wso2/%{::product_name}/%{::product_version}/default"
> - "osfamily/%{::osfamily}"
> - "vm_type/%{::vm_type}"
> - wso2/common
> - common
>

+1 for introducing a new level in hierarchy to lookup for platform specific
data on top of profile specific data per product.

>
> This will allow us to extract the platform specific data only to one layer
> up. An example would be,
>
> puppet-modules/hieradata/dev/wso2/wso2am/1.10.0/default-kubernetes.yaml
>

It would be better to have spearate folders for platform specific yaml
files inside each product versions like below with changing the above hiera
level to: *-
"wso2/%{::product_name}/%{::product_version}/%{::product_profile}/%{::platform}"*

hieradata/dev/wso2/wso2as/

└── 5.3.0

├── default.yaml

├── <*platform*>

│   ├── default.yaml

│   ├── manager.yaml

│   └── worker.yaml

├── kubernetes

│   ├── default.yaml

│   ├── manager.yaml

│   └── worker.yaml

├── manager.yaml

└── worker.yaml


With the above structure, configs common to all platform will be there in
the products' root level hierafiles. Only the platform specific configs
related to a particular profile will be there in /.yaml
(ex: proxy_ports).



> WDYT?
>
>
> 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 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Isuru,
>>
>> Without duplicating files and adding new files, I would rather prefer to
>> use the following hierarchy. For each and every different environment we
>> can have product profiles and include the environment specific values. For
>> Kubernetes, we can include the clustering section only in manager.yaml file
>> which resides under environment Kubernetes. And the rest of the other
>> configurations can be included in the generic file folder, i.e "
>> wso2/%{::product_name}/%{::product_version}/%{::product_profile}".
>>
>>
>> :hierarchy:
>> - "node/%{::clientcert}" - - "
>> wso2/%{::product_name}/%{::product_version}/%{::environment}
>> /%{::product_profile}"
>> - "wso2/%{::product_name}/%{::product_version}/%{::product_profile}"
>> - "wso2/%{::product_name}/%{::product_version}/default"
>> - "osfamily/%{::osfamily}"
>> - "vm_type/%{::vm_type}"
>> - wso2/common
>> - common
>>
>>
>> Thank you!
>>
>> On Mon, Apr 11, 2016 at 1:07 PM, Isuru Haththotuwa 
>> wrote:
>>
>>>
>>>
>>> On Mon, Apr 11, 2016 at 12:47 PM, Gayan Gunarathne 
>>> wrote:
>>>


 On Mon, Apr 11, 2016 at 12:39 PM, Lakmal Warusawithana  wrote:

>
>
> On Mon, Apr 11, 2016 at 12:22 PM, Imesh Gunaratne 
> wrote:
>
>> Hi Chamila,
>>
>> On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis 
>> 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 

Re: [Dev] [Automation] How to apply a configuration file before starting a server using CarbonTestServerManager?

[Bhathiya Jayasekara]

Thanks for the reply Akalanka. Actually my question was about a new
separate server, but not about the server already started by the test suit.
Nuwan's suggestion should work here.

Thanks,
Bhathiya

On Mon, Apr 11, 2016 at 3:32 PM, Akalanka Pagoda Arachchi <
darsha...@wso2.com> wrote:

> We've been using the ServerConfigurationManager to achieve this in MB.
>
> import
> org.wso2.carbon.integration.common.utils.mgt.ServerConfigurationManager;
>
> ServerConfigurationManager serverManager = new
> ServerConfigurationManager(automationContext);
>
> serverManager.applyConfiguration(sourceFile, targetFile, backupConfigFile,
> restartServer);
>
>
> Thanks,
> Akalanka.
>
>
> On Mon, Apr 11, 2016 at 3:22 PM, Bhathiya Jayasekara 
> wrote:
>
>> Thanks Nuwan. Will try this.
>>
>> Thanks,
>> Bhathiya
>>
>> On Mon, Apr 11, 2016 at 3:21 PM, Nuwan Wimalasekara 
>> wrote:
>>
>>> Hi Bhathiya,
>>>
>>> You can start a new server instance using below code segment.
>>>
>>> AutomationContext regTestContext = new AutomationContext("AM", 
>>> "AMTestServer", TestUserMode.SUPER_TENANT_ADMIN);
>>>
>>> Map < String, String > startupParameterMap = new HashMap < > ();
>>> startupParameterMap.put("-DportOffset", "230");
>>>
>>> TestServerManager testServerManager = new TestServerManager(regTestContext, 
>>> null, startupParameterMap) {
>>>
>>> public void configureServer() throws AutomationFrameworkException {
>>>
>>> try {
>>> File sourceFile = new 
>>> File(TestConfigurationProvider.getResourceLocation() + "registry.xml");
>>>
>>> //copying registry.xml file to conf folder
>>> FileManager.copyFile(sourceFile, this.getCarbonHome() + 
>>> File.separator + "repository" + File.separator + "conf" + File.separator + 
>>> "registry.xml");
>>> } catch (IOException e) {
>>> throw new AutomationFrameworkException(e.getMessage(), e);
>>> }
>>> }
>>> };
>>>
>>> testServerManager.startServer();
>>>
>>>
>>>
>>> Thanks,
>>> Nuwanw
>>>
>>> On Mon, Apr 11, 2016 at 2:52 PM, Bhathiya Jayasekara 
>>> wrote:
>>>
 Hi Automation team,

 In this[1] test, we have *CarbonTestServerManager *with
 *MultipleServersManager *to spawn a new APIM server. Now I need to
 apply a modified api-manager.xml file before starting this server. How can
 I do that? Appreciate some help.

 public void setEnvironment() throws Exception {
 // to start the server from a different port offset
 serverPropertyMap.put("-DportOffset", "510");
 // start with OSGI component service
 serverPropertyMap.put("-DosgiConsole", Integer.toString(telnetPort));
 AutomationContext autoCtx = new AutomationContext();
 CarbonTestServerManager server =
 new CarbonTestServerManager(autoCtx, System.getProperty("carbon.zip"),
 serverPropertyMap);
 manager.startServers(server);
 }


 [1]
 https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/server/mgt/OSGIServerBundleStatusTestCase.java#L63

 Thanks,
 --
 *Bhathiya Jayasekara*
 *Senior Software Engineer,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <%2B94715478185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *
 *Blog: http://movingaheadblog.blogspot.com
 *

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


>>>
>>>
>>> --
>>> Nuwan Wimalasekara
>>> Senior Software Engineer - Test Automation
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> phone: +94 71 668 4620
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Senior Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <%2B94715478185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Darshana Akalanka Pagoda Arachchi,*
> *Software Engineer, WSO2*
> *+94777118016 <%2B94777118016>*
>



-- 
*Bhathiya Jayasekara*
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com

Re: [Dev] [Automation] How to apply a configuration file before starting a server using CarbonTestServerManager?

[Akalanka Pagoda Arachchi]

We've been using the ServerConfigurationManager to achieve this in MB.

import
org.wso2.carbon.integration.common.utils.mgt.ServerConfigurationManager;

ServerConfigurationManager serverManager = new
ServerConfigurationManager(automationContext);

serverManager.applyConfiguration(sourceFile, targetFile, backupConfigFile,
restartServer);


Thanks,
Akalanka.


On Mon, Apr 11, 2016 at 3:22 PM, Bhathiya Jayasekara 
wrote:

> Thanks Nuwan. Will try this.
>
> Thanks,
> Bhathiya
>
> On Mon, Apr 11, 2016 at 3:21 PM, Nuwan Wimalasekara 
> wrote:
>
>> Hi Bhathiya,
>>
>> You can start a new server instance using below code segment.
>>
>> AutomationContext regTestContext = new AutomationContext("AM", 
>> "AMTestServer", TestUserMode.SUPER_TENANT_ADMIN);
>>
>> Map < String, String > startupParameterMap = new HashMap < > ();
>> startupParameterMap.put("-DportOffset", "230");
>>
>> TestServerManager testServerManager = new TestServerManager(regTestContext, 
>> null, startupParameterMap) {
>>
>> public void configureServer() throws AutomationFrameworkException {
>>
>> try {
>> File sourceFile = new 
>> File(TestConfigurationProvider.getResourceLocation() + "registry.xml");
>>
>> //copying registry.xml file to conf folder
>> FileManager.copyFile(sourceFile, this.getCarbonHome() + 
>> File.separator + "repository" + File.separator + "conf" + File.separator + 
>> "registry.xml");
>> } catch (IOException e) {
>> throw new AutomationFrameworkException(e.getMessage(), e);
>> }
>> }
>> };
>>
>> testServerManager.startServer();
>>
>>
>>
>> Thanks,
>> Nuwanw
>>
>> On Mon, Apr 11, 2016 at 2:52 PM, Bhathiya Jayasekara 
>> wrote:
>>
>>> Hi Automation team,
>>>
>>> In this[1] test, we have *CarbonTestServerManager *with
>>> *MultipleServersManager *to spawn a new APIM server. Now I need to
>>> apply a modified api-manager.xml file before starting this server. How can
>>> I do that? Appreciate some help.
>>>
>>> public void setEnvironment() throws Exception {
>>> // to start the server from a different port offset
>>> serverPropertyMap.put("-DportOffset", "510");
>>> // start with OSGI component service
>>> serverPropertyMap.put("-DosgiConsole", Integer.toString(telnetPort));
>>> AutomationContext autoCtx = new AutomationContext();
>>> CarbonTestServerManager server =
>>> new CarbonTestServerManager(autoCtx, System.getProperty("carbon.zip"),
>>> serverPropertyMap);
>>> manager.startServers(server);
>>> }
>>>
>>>
>>> [1]
>>> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/server/mgt/OSGIServerBundleStatusTestCase.java#L63
>>>
>>> Thanks,
>>> --
>>> *Bhathiya Jayasekara*
>>> *Senior Software Engineer,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>> *Phone: +94715478185 <%2B94715478185>*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>>> *
>>> *Twitter: https://twitter.com/bhathiyax *
>>> *Blog: http://movingaheadblog.blogspot.com
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Darshana Akalanka Pagoda Arachchi,*
*Software Engineer, WSO2*
*+94777118016*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Automation] How to apply a configuration file before starting a server using CarbonTestServerManager?

[Bhathiya Jayasekara]

Thanks Nuwan. Will try this.

Thanks,
Bhathiya

On Mon, Apr 11, 2016 at 3:21 PM, Nuwan Wimalasekara  wrote:

> Hi Bhathiya,
>
> You can start a new server instance using below code segment.
>
> AutomationContext regTestContext = new AutomationContext("AM", 
> "AMTestServer", TestUserMode.SUPER_TENANT_ADMIN);
>
> Map < String, String > startupParameterMap = new HashMap < > ();
> startupParameterMap.put("-DportOffset", "230");
>
> TestServerManager testServerManager = new TestServerManager(regTestContext, 
> null, startupParameterMap) {
>
> public void configureServer() throws AutomationFrameworkException {
>
> try {
> File sourceFile = new 
> File(TestConfigurationProvider.getResourceLocation() + "registry.xml");
>
> //copying registry.xml file to conf folder
> FileManager.copyFile(sourceFile, this.getCarbonHome() + 
> File.separator + "repository" + File.separator + "conf" + File.separator + 
> "registry.xml");
> } catch (IOException e) {
> throw new AutomationFrameworkException(e.getMessage(), e);
> }
> }
> };
>
> testServerManager.startServer();
>
>
>
> Thanks,
> Nuwanw
>
> On Mon, Apr 11, 2016 at 2:52 PM, Bhathiya Jayasekara 
> wrote:
>
>> Hi Automation team,
>>
>> In this[1] test, we have *CarbonTestServerManager *with
>> *MultipleServersManager *to spawn a new APIM server. Now I need to apply
>> a modified api-manager.xml file before starting this server. How can I do
>> that? Appreciate some help.
>>
>> public void setEnvironment() throws Exception {
>> // to start the server from a different port offset
>> serverPropertyMap.put("-DportOffset", "510");
>> // start with OSGI component service
>> serverPropertyMap.put("-DosgiConsole", Integer.toString(telnetPort));
>> AutomationContext autoCtx = new AutomationContext();
>> CarbonTestServerManager server =
>> new CarbonTestServerManager(autoCtx, System.getProperty("carbon.zip"),
>> serverPropertyMap);
>> manager.startServers(server);
>> }
>>
>>
>> [1]
>> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/server/mgt/OSGIServerBundleStatusTestCase.java#L63
>>
>> Thanks,
>> --
>> *Bhathiya Jayasekara*
>> *Senior Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <%2B94715478185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>


-- 
*Bhathiya Jayasekara*
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Automation] How to apply a configuration file before starting a server using CarbonTestServerManager?

[Nuwan Wimalasekara]

Hi Bhathiya,

You can start a new server instance using below code segment.

AutomationContext regTestContext = new AutomationContext("AM",
"AMTestServer", TestUserMode.SUPER_TENANT_ADMIN);

Map < String, String > startupParameterMap = new HashMap < > ();
startupParameterMap.put("-DportOffset", "230");

TestServerManager testServerManager = new
TestServerManager(regTestContext, null, startupParameterMap) {

public void configureServer() throws AutomationFrameworkException {

try {
File sourceFile = new
File(TestConfigurationProvider.getResourceLocation() +
"registry.xml");

//copying registry.xml file to conf folder
FileManager.copyFile(sourceFile, this.getCarbonHome() +
File.separator + "repository" + File.separator + "conf" +
File.separator + "registry.xml");
} catch (IOException e) {
throw new AutomationFrameworkException(e.getMessage(), e);
}
}
};

testServerManager.startServer();



Thanks,
Nuwanw

On Mon, Apr 11, 2016 at 2:52 PM, Bhathiya Jayasekara 
wrote:

> Hi Automation team,
>
> In this[1] test, we have *CarbonTestServerManager *with
> *MultipleServersManager *to spawn a new APIM server. Now I need to apply
> a modified api-manager.xml file before starting this server. How can I do
> that? Appreciate some help.
>
> public void setEnvironment() throws Exception {
> // to start the server from a different port offset
> serverPropertyMap.put("-DportOffset", "510");
> // start with OSGI component service
> serverPropertyMap.put("-DosgiConsole", Integer.toString(telnetPort));
> AutomationContext autoCtx = new AutomationContext();
> CarbonTestServerManager server =
> new CarbonTestServerManager(autoCtx, System.getProperty("carbon.zip"),
> serverPropertyMap);
> manager.startServers(server);
> }
>
>
> [1]
> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/server/mgt/OSGIServerBundleStatusTestCase.java#L63
>
> Thanks,
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Automation] How to apply a configuration file before starting a server using CarbonTestServerManager?

[Bhathiya Jayasekara]

Hi Automation team,

In this[1] test, we have *CarbonTestServerManager *with
*MultipleServersManager *to spawn a new APIM server. Now I need to apply a
modified api-manager.xml file before starting this server. How can I do
that? Appreciate some help.

public void setEnvironment() throws Exception {
// to start the server from a different port offset
serverPropertyMap.put("-DportOffset", "510");
// start with OSGI component service
serverPropertyMap.put("-DosgiConsole", Integer.toString(telnetPort));
AutomationContext autoCtx = new AutomationContext();
CarbonTestServerManager server =
new CarbonTestServerManager(autoCtx, System.getProperty("carbon.zip"),
serverPropertyMap);
manager.startServers(server);
}


[1]
https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/server/mgt/OSGIServerBundleStatusTestCase.java#L63

Thanks,
-- 
*Bhathiya Jayasekara*
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Incorrect string value: '\xE2\x80\x91200...' for column 'UM_DESCRIPTION'

[rohit]

Hi All, 

   When trying to start wso2 API Manager, I'm stuck with this issue. It
suggest in the documentation that while creating the database one must add
'characterset latin1'. Any Suggestions?



--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/Incorrect-string-value-xE2-x80-x91200-for-column-UM-DESCRIPTION-tp134928.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Imesh Gunaratne]

On Mon, Apr 11, 2016 at 12:47 PM, Gayan Gunarathne  wrote:
>
>
> I think we can make this with with Defined Types[1][2] without creating
> duplicate set of YAML files for each platform. We can do the same as the
> example given in the document.
>
> Thanks Gayan! It is not very clear how defined types can be used for
solving this. AFAIU a defined type is a function in puppet, the problem we
have here is related to the Hiera hierarchy. More specifically how to
restructure the data structure in Hiera by introducing a factor variable to
handle platforms.

On Mon, Apr 11, 2016 at 1:07 PM, Isuru Haththotuwa  wrote:

>
> I do not think we need to duplicate the yaml files here. Sorry that the
> sample in the first reply sent by me implied so. What we can do is refactor
> out the hiera data so that data which is changing according to the platform
> (ex.: clustering section) can be moved to a different yaml file(s). For an
> example, clustering for kubernetes scenario can be included in
> *puppet-modules/hieradata/dev/wso2/kubernetes/clustering.yaml*. Here,
> 'kubernetes' is the value of the facter which is used to identify the
> environment. Similarly, other such data can be refactored out.
>

A good suggestion Isuru! May be we can try this out and later refine as
needed.

Thanks




> [1]https://docs.puppet.com/puppet/latest/reference/lang_defined_types.html
> [2]http://puppetlunch.com/puppet/hiera.html
>
>
>>
> Thanks
>
>>
>> Thanks,
>> Gayan
>>
>>
>> On Sat, Apr 9, 2016 at 8:28 AM, Imesh Gunaratne 
>> wrote:
>>
>>>
>>> On Fri, Apr 8, 2016 at 7:48 PM, Isuru Haththotuwa 
>>> 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* *



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

>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 

Re: [Dev] [Puppet Modules] Kubernetes Naming Convention

[Chamila De Alwis]

+1

This should be a consistent naming.


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com



On Mon, Apr 11, 2016 at 2:09 PM, Imesh Gunaratne  wrote:

> Hi Devs,
>
> As I see we have used 'k8' for naming Kubernetes variables. IMO this
> should be either 'k8s' or 'kubernetes':
>
> wso2::clustering :
> enabled : true
> #local_member_host : local.esb.wso2.com
> domain : wso2.esb.domain
> local_member_port : 4000
> #membership_scheme : wka
> membership_scheme : kubernetes
> sub_domain : mgt
> k8 :
>k8_master : http://172.17.8.101:8080
>k8_namespace : default
>k8_services : wso2esb-manager,wso2esb-worker
>k8_master_username :
>k8_master_password :
>
> In the above example I prefer to use kubernetes instead of k8s because we
> have used that for the membership scheme name. WDYT?
>
> [1]
> https://github.com/wso2/puppet-modules/blob/master/modules/wso2esb/templates/4.9.0/repository/conf/axis2/axis2.xml.erb#L506
>
> 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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Pushpalanka Jayawardhana]

On Mon, Apr 11, 2016 at 1:53 PM, Dinusha Senanayaka 
wrote:

> Hi IS Team,
>
> Do you have release date for identity-5.0.9 ? This fix is critical for App
> manager release.
>
We are working on to release the beta pack tomorrow.  Identity-5.0.9
release will be done with the RC pack, which will be by 25th in best case.

>
> Regards,
> Dinusha.
>
> On Mon, Apr 4, 2016 at 10:34 AM, Rushmin Fernando 
> wrote:
>
>> Thanks Pulasthi !
>>
>> App Manager WIP code can be found in [1] and [2]
>>
>> Thanks
>> Rushmin
>>
>> [1] -
>> https://github.com/wso2/carbon-appmgt/tree/feature/kernel-4.4.5-upgrade
>>
>> [2]  -
>> https://github.com/wso2/product-app-manager/tree/feature/kernel-4.4.5-upgrade
>>
>> On Fri, Apr 1, 2016 at 4:52 PM, Pulasthi Mahawithana 
>> wrote:
>>
>>> Yes, we no longer use the wso2/carbon-identity repo for development. We
>>> use the repos in 'wso2-extensions'. However the group ids, artifact ids and
>>> versions follow the same from carbon-identity.
>>>
>>> On Fri, Apr 1, 2016 at 3:56 PM, Rushmin Fernando 
>>> wrote:
>>>
 Thanks Supun !

 So is [1] obsolete now since the connector code resides in
 'wso2-extensions' account now ?


 Thanks
 Rushmin

 [1] -
 https://github.com/wso2/carbon-identity/blob/master/features/provisioning/org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature

 On Fri, Apr 1, 2016 at 3:47 PM, Pulasthi Mahawithana <
 pulast...@wso2.com> wrote:

> Hi Rushmin,
>
> This issue was due to that component being moved from carbon-commons
> to analytic commons. Isura fixed that issue with [1] and [2]. Can you
> please try now?
>
> [1]
> https://github.com/wso2-extensions/identity-extension-parent/pull/6
> [2]
> https://github.com/wso2-extensions/identity-outbound-provisioning-salesforce/pull/6
>
> On Fri, Apr 1, 2016 at 12:21 PM, Rushmin Fernando 
> wrote:
>
>>
>> Hi Devs,
>>
>> We are in the process of upgrading the Carbon Kernel version to 4.4.5
>>
>> During this upgrade we found out that
>> "org.wso2.carbon.identity.provisioning.connector.salesforce.server" 
>> feature
>> is dependenct on a non-existing feature version of
>> "org.wso2.carbon.databridge.commons.server"
>>
>> I opened a Jira to track this. [1]
>>
>> Had a chat with Pulasthi and this will be fixed with IS 5.2.0 release
>> which will happen in the next week.
>>
>> Until this is fixed, I'm proceeding with the identity 5.0.9-SNAPSHOT
>> having the issue fixed locally.
>>
>> Thanks
>> Rushmin
>>
>> [1] - https://wso2.org/jira/browse/IDENTITY-4465
>>
>> --
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> email : rush...@wso2.com
>> mobile : +94772310855
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pulasthi Mahawithana*
> Software Engineer
> WSO2 Inc., http://wso2.com/
> Mobile: +94-71-5179022
> Blog: http://blog.pulasthi.org
>



 --
 *Rushmin Fernando*
 *Technical Lead*

 WSO2 Inc.  - Lean . Enterprise . Middleware

 email : rush...@wso2.com
 mobile : +94772310855



>>>
>>>
>>> --
>>> *Pulasthi Mahawithana*
>>> Software Engineer
>>> WSO2 Inc., http://wso2.com/
>>> Mobile: +94-71-5179022
>>> Blog: http://blog.pulasthi.org
>>>
>>
>>
>>
>> --
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> email : rush...@wso2.com
>> mobile : +94772310855
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Pushpalanka.
-- 
Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
Mobile: +94779716248
Blog: pushpalankajaya.blogspot.com/ | LinkedIn:
lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Puppet Modules] Kubernetes Naming Convention

[Imesh Gunaratne]

Hi Devs,

As I see we have used 'k8' for naming Kubernetes variables. IMO this should
be either 'k8s' or 'kubernetes':

wso2::clustering :
enabled : true
#local_member_host : local.esb.wso2.com
domain : wso2.esb.domain
local_member_port : 4000
#membership_scheme : wka
membership_scheme : kubernetes
sub_domain : mgt
k8 :
   k8_master : http://172.17.8.101:8080
   k8_namespace : default
   k8_services : wso2esb-manager,wso2esb-worker
   k8_master_username :
   k8_master_password :

In the above example I prefer to use kubernetes instead of k8s because we
have used that for the membership scheme name. WDYT?

[1]
https://github.com/wso2/puppet-modules/blob/master/modules/wso2esb/templates/4.9.0/repository/conf/axis2/axis2.xml.erb#L506

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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Chamila De Alwis]

Hi Pubudu,

That's a good idea, however, we can't exactly map `environment` with the
`platform` concept. How about using a new level on top of the profile
specific level mapping to `platform`?

:hierarchy:
- "node/%{::clientcert}"
*-
"wso2/%{::product_name}/%{::product_version}/%{::product_profile}-%{::platform}"*
- "wso2/%{::product_name}/%{::product_version}/%{::product_profile}"
- "wso2/%{::product_name}/%{::product_version}/default"
- "osfamily/%{::osfamily}"
- "vm_type/%{::vm_type}"
- wso2/common
- common

This will allow us to extract the platform specific data only to one layer
up. An example would be,

puppet-modules/hieradata/dev/wso2/wso2am/1.10.0/default-kubernetes.yaml

WDYT?


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 PM, Pubudu Gunatilaka  wrote:

> Hi Isuru,
>
> Without duplicating files and adding new files, I would rather prefer to
> use the following hierarchy. For each and every different environment we
> can have product profiles and include the environment specific values. For
> Kubernetes, we can include the clustering section only in manager.yaml file
> which resides under environment Kubernetes. And the rest of the other
> configurations can be included in the generic file folder, i.e "
> wso2/%{::product_name}/%{::product_version}/%{::product_profile}".
>
>
> :hierarchy:
> - "node/%{::clientcert}" - - "
> wso2/%{::product_name}/%{::product_version}/%{::environment}
> /%{::product_profile}"
> - "wso2/%{::product_name}/%{::product_version}/%{::product_profile}"
> - "wso2/%{::product_name}/%{::product_version}/default"
> - "osfamily/%{::osfamily}"
> - "vm_type/%{::vm_type}"
> - wso2/common
> - common
>
>
> Thank you!
>
> On Mon, Apr 11, 2016 at 1:07 PM, Isuru Haththotuwa 
> wrote:
>
>>
>>
>> On Mon, Apr 11, 2016 at 12:47 PM, Gayan Gunarathne 
>> wrote:
>>
>>>
>>>
>>> On Mon, Apr 11, 2016 at 12:39 PM, Lakmal Warusawithana 
>>> wrote:
>>>


 On Mon, Apr 11, 2016 at 12:22 PM, Imesh Gunaratne 
 wrote:

> Hi Chamila,
>
> On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis 
> 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 
>> wrote:
>>
>>> Hi Gayan,
>>>
>>> On Sun, Apr 10, 2016 at 5:02 PM, Gayan Gunarathne 
>>> 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 

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Dinusha Senanayaka]

Hi IS Team,

Do you have release date for identity-5.0.9 ? This fix is critical for App
manager release.

Regards,
Dinusha.

On Mon, Apr 4, 2016 at 10:34 AM, Rushmin Fernando  wrote:

> Thanks Pulasthi !
>
> App Manager WIP code can be found in [1] and [2]
>
> Thanks
> Rushmin
>
> [1] -
> https://github.com/wso2/carbon-appmgt/tree/feature/kernel-4.4.5-upgrade
>
> [2]  -
> https://github.com/wso2/product-app-manager/tree/feature/kernel-4.4.5-upgrade
>
> On Fri, Apr 1, 2016 at 4:52 PM, Pulasthi Mahawithana 
> wrote:
>
>> Yes, we no longer use the wso2/carbon-identity repo for development. We
>> use the repos in 'wso2-extensions'. However the group ids, artifact ids and
>> versions follow the same from carbon-identity.
>>
>> On Fri, Apr 1, 2016 at 3:56 PM, Rushmin Fernando 
>> wrote:
>>
>>> Thanks Supun !
>>>
>>> So is [1] obsolete now since the connector code resides in
>>> 'wso2-extensions' account now ?
>>>
>>>
>>> Thanks
>>> Rushmin
>>>
>>> [1] -
>>> https://github.com/wso2/carbon-identity/blob/master/features/provisioning/org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature
>>>
>>> On Fri, Apr 1, 2016 at 3:47 PM, Pulasthi Mahawithana >> > wrote:
>>>
 Hi Rushmin,

 This issue was due to that component being moved from carbon-commons to
 analytic commons. Isura fixed that issue with [1] and [2]. Can you please
 try now?

 [1] https://github.com/wso2-extensions/identity-extension-parent/pull/6
 [2]
 https://github.com/wso2-extensions/identity-outbound-provisioning-salesforce/pull/6

 On Fri, Apr 1, 2016 at 12:21 PM, Rushmin Fernando 
 wrote:

>
> Hi Devs,
>
> We are in the process of upgrading the Carbon Kernel version to 4.4.5
>
> During this upgrade we found out that
> "org.wso2.carbon.identity.provisioning.connector.salesforce.server" 
> feature
> is dependenct on a non-existing feature version of
> "org.wso2.carbon.databridge.commons.server"
>
> I opened a Jira to track this. [1]
>
> Had a chat with Pulasthi and this will be fixed with IS 5.2.0 release
> which will happen in the next week.
>
> Until this is fixed, I'm proceeding with the identity 5.0.9-SNAPSHOT
> having the issue fixed locally.
>
> Thanks
> Rushmin
>
> [1] - https://wso2.org/jira/browse/IDENTITY-4465
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Pulasthi Mahawithana*
 Software Engineer
 WSO2 Inc., http://wso2.com/
 Mobile: +94-71-5179022
 Blog: http://blog.pulasthi.org

>>>
>>>
>>>
>>> --
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> email : rush...@wso2.com
>>> mobile : +94772310855
>>>
>>>
>>>
>>
>>
>> --
>> *Pulasthi Mahawithana*
>> Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022
>> Blog: http://blog.pulasthi.org
>>
>
>
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] C5 Server startup hangs intermittently

[Afkham Azeez]

Was this resolved?

On Mon, Apr 4, 2016 at 4:06 PM, Kishanthan Thangarajah 
wrote:

> Can we enable debug logs for "org.wso2.carbon.kernel.
> internal.startupresolver" package and check which component is causing
> the issue? I can take a look at this and find the root cause, if needed.
>
> On Mon, Apr 4, 2016 at 1:11 PM, Sumedha Rubasinghe 
> wrote:
>
>> But it's intermittent. Manu also said he has faced this several times.
>> AFAIU, fix to be applied @ C5 level?
>>
>>
>>
>>
>> On Mon, Apr 4, 2016 at 1:08 PM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi Sumedha,
>>>
>>> This because of a failure in netty component. It has failed to register
>>> transports.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Mon, Apr 4, 2016 at 1:01 PM, Sumedha Rubasinghe 
>>> wrote:
>>>
 # Normal server bootup
 #

 Sumedha-2:wso2uuf-1.0.0-SNAPSHOT sumedha$ bin/carbon.sh
 JAVA_HOME environment variable is set to
 /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
 CARBON_HOME environment variable is set to
 /Volumes/data/projects/wso2/uuf/M3/wso2uuf-1.0.0-SNAPSHOT
 osgi> [2016-04-04 09:46:13,407]  INFO
 {org.wso2.msf4j.internal.MicroservicesServerSC} - All microservices are
 available
 [2016-04-04 09:46:13,422]  INFO
 {org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent}
 - All CarbonNettyServerInitializers are available
 [2016-04-04 09:46:13,423]  INFO
 {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Starting
 Netty Http Transport Listener
 [2016-04-04 09:46:13,428]  INFO
 {org.wso2.msf4j.internal.MicroservicesRegistry} - Added microservice:
 org.wso2.carbon.uuf.UUFService@7f932479
 [2016-04-04 09:46:13,509]  INFO
 {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Netty
 Listener starting on port 8080
 [2016-04-04 09:46:13,511]  INFO
 {org.wso2.carbon.kernel.internal.CarbonStartupHandler} - WSO2 Carbon
 started in 1.303 sec



 # Same Server, hanged during bootup
 #
 Sumedha-2:wso2uuf-1.0.0-SNAPSHOT sumedha$ bin/carbon.sh
 JAVA_HOME environment variable is set to
 /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
 CARBON_HOME environment variable is set to
 /Volumes/data/projects/wso2/uuf/M3/wso2uuf-1.0.0-SNAPSHOT
 osgi> [2016-04-04 09:45:12,668]  INFO
 {org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent}
 - All CarbonNettyServerInitializers are available
 [2016-04-04 09:45:12,672]  INFO
 {org.wso2.msf4j.internal.MicroservicesRegistry} - Added microservice:
 org.wso2.carbon.uuf.UUFService@51f5356e
 [2016-04-04 09:45:42,625]  WARN
 {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
 - Waiting on pending capability registration. Capability:
 org.wso2.msf4j.Interceptor
 [2016-04-04 09:45:42,626]  WARN
 {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
 - Waiting on pending capability registration. Capability:
 org.wso2.msf4j.Microservice
 [2016-04-04 09:45:42,626]  WARN
 {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
 - Waiting on pending capability registration. Capability:
 org.wso2.msf4j.internal.MicroservicesServerSC
 [2016-04-04 09:45:42,626]  WARN
 {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
 - Waiting on pending capability registration. Capability:
 org.wso2.carbon.kernel.transports.CarbonTransport
 [2016-04-04 09:45:42,626]  WARN
 {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
 - Waiting on pending capability registration. Capability:
 org.wso2.carbon.kernel.deployment.DeploymentService
 [2016-04-04 09:45:42,626]  WARN
 {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
 - Waiting on pending capability registration. Capability:
 org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent





 --
 /sumedha
 m: +94 773017743
 b :  bit.ly/sumedha

>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Software Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://blog.sameera.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Associate Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com 

Re: [Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[Geesara Prathap]

Hi Zhou,

Is that right to select 4 in below step?  You should select 2

What’s the difference between 2 and 4 archetype selection? In maven
archetype plugin groupId renamed from m3 to m4. In M3 it was named as
cdmf.devicetype. But m4 onwards it named as org.wso2.cdmf.devicetype.
Please follow the instruction in README[1]
.
It says everything you need to follow.

1. https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3

Thanks,
Geesara

On Mon, Apr 11, 2016 at 1:31 PM, 云展智创  wrote:

> Hi Shabir/Geesara,
>
> Is that right to select 4 in below step? What’s the difference between 2
> and 4 archetype selection?
>
> $ mvn archetype:generate -DarchetypeCatalog=local
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
> MaxPermSize=1024m; support was removed in 8.0
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
> 
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO]
> 
> [INFO]
> [INFO] >>> maven-archetype-plugin:2.4:generate (default-cli) >
> generate-sources @ standalone-pom >>>
> [INFO]
> [INFO] <<< maven-archetype-plugin:2.4:generate (default-cli) <
> generate-sources @ standalone-pom <<<
> [INFO]
> [INFO] --- maven-archetype-plugin:2.4:generate (default-cli) @
> standalone-pom ---
> [INFO] Generating project in Interactive mode
> [INFO] No archetype defined. Using maven-archetype-quickstart
> (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
> Choose archetype:
> 1: local -> org.wso2.iot:mdm-android-agent-archetype (Creates a
> MDM-Android agent project)
> 2: local -> cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF Device
> Type Archetype)
> 3: local -> org.wso2.mdm:mdm-android-agent-archetype (Creates a
> MDM-Android agent project)
> 4: local -> org.wso2.cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF
> Device Type Archetype)
> Choose a number or apply filter (format: [groupId:]artifactId, case
> sensitive contains): : 4
>
> －－
> Zhanwen Zhou (Jason),
>
> 在 2016年4月11日，下午3:08，Shabir Mohamed  写道：
>
> Hi Zhou,
>
> If you still get any additional errors, please do send us the errors
> printed in the error logs at:
> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-
> runtime/0.13.0/eclipse/
>
> so we could deduce why the device-deployer actually failed.
>
> Regards
>
> -
> *Shabir Mohamed*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> Email: sha...@wso2.com 
> Mobile: +94 77 3516019 | +94 71 6583393
>
> On Mon, Apr 11, 2016 at 12:27 PM, Geesara Prathap 
> wrote:
>
>> Hi Zhou,
>>
>> copied file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the
>> repository/components/plugins folder)
>>
>> No need to copy any of *.jar files manually. All necessary *jar files are
>> copied by maven archetype when building device type plugin.
>>
>> I found that the feature target file had been built (but I didn’t know
>> why the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature
>> folder of my device type, so I used following command to install it,
>> successfully finished.
>>
>> the default version is set to 1.0-SNAPSHOT when building new device type
>> plugin. If you need you can change as you require. But please define
>> correct version, groupid and artifactId in device-deploye.xml as
>> mention here[1].
>>
>>
>>
>> 1.
>> https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
>> (*branch IoTS-1.0.0-M3*)
>>
>> Thanks,
>> Geesara
>>
>> On Mon, Apr 11, 2016 at 12:04 PM, Charitha Goonetilleke <
>> charit...@wso2.com> wrote:
>>
>>> [Adding Ayyoob & Geesara to the thread]
>>>
>>> Hi Zhou,
>>>
>>> Since we are working with next milestone release, archtype in
>>> product-iots master branch will not generate compatible device type plugin
>>> for M3 pack. It is the reason for above mentioned issues. So please
>>> checkout M3 compatible archtype from this link[2] and try to regenerate
>>> your device type with it.
>>>
>>> Also, with given M3 compatible archtype, you don't want to copy any jar
>>> file to plugins directory by your self.
>>>
>>> [1]
>>> https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M3/components/device-mgt-iot
>>> [2]
>>> https://github.com/wso2/product-iots/tree/master/modules/tools/cdmf-devicetype-archetype
>>> [3]
>>> https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
>>>
>>> Thanks & Regards,
>>> /charithag
>>>
>>>
>>> On Mon, Apr 11, 2016 at 11:10 AM, 云展智创  wrote:
>>>
 Hi all,

 I created a new device type using cdmf-devicetype-archetype-master
 tool, and updated the file device-deployer.xml (used IoTS-M3 SNAPSHOT, and
 copied file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the

Re: [Dev] APIM Getting SSLPeerUnverifiedException after upgrading to kernel 4.4.4

[Dinusha Senanayaka]

Hi All,

Getting same exception in App Manager also after updating to kernel-4.4.5.
What is the resolution for this, can we continue with
"-Dorg.opensaml.httpclient.https.disableHostnameVerification=true \" system
property in startup script as Harsha suggested ?

Regards,
Dinusha.

On Tue, Apr 5, 2016 at 7:18 PM, Harsha Kumara  wrote:

> Hi IS Team,
>
> It seems that the issue got resolved with the system property. We will
> needed to add it to our startup scripts. Any concerns on doing that?
>
> Thanks,
> Harsha
>
> On Tue, Apr 5, 2016 at 6:26 PM, Harsha Kumara  wrote:
>
>> Boolean.getBoolean perform system property lookup. I'll try that solution
>> and update.
>>
>> On Tue, Apr 5, 2016 at 6:20 PM, Harsha Kumara  wrote:
>>
>>> I have done some analysis on this. In API Manager initial functionality
>>> works fine. When the access token is generated SAML2BearerGrantHandler
>>> doing DefaultBootstrap.bootstrap(); in opensaml library. With the new
>>> version of the opensaml library they have
>>> perform initializeHttpClient();[1] during the bootstrap. So the underline
>>> commons http client library socket factory has changed
>>> from SSLProtocolSocketFactory to TLSProtocolSocketFactory.
>>> In TLSProtocolSocketFactory it's perform host name verification which cause
>>> this exception. When go through their code, they have tried to disable this
>>> from System property. But implementation is doing Boolean.getBoolean
>>> instead of looking from System.getPropety[2] which seems bug. If this has
>>> worked, we could have set a system property.
>>>
>>> [1]
>>> /**
>>>  *  Initializes the Apache Commons HttpClient library.
>>>  */
>>> protected static void initializeHttpClient() {
>>> if
>>> (!Boolean.getBoolean(SYSPROP_HTTPCLIENT_HTTPS_DISABLE_HOSTNAME_VERIFICATION))
>>> {
>>> ProtocolSocketFactory socketFactory =
>>> new TLSProtocolSocketFactory(null, null, new
>>> StrictHostnameVerifier());
>>> Protocol.registerProtocol("https", new Protocol("https",
>>> socketFactory, 443));
>>> }
>>> }
>>>
>>> [2]
>>> /** System property used to disable global default HTTPS hostname
>>> verification in Apache Commons HttpClient. */
>>> public static final String
>>> SYSPROP_HTTPCLIENT_HTTPS_DISABLE_HOSTNAME_VERIFICATION =
>>> "org.opensaml.httpclient.https.disableHostnameVerification";
>>>
>>> Thanks,
>>> Harsha
>>>
>>>
>>> On Tue, Apr 5, 2016 at 5:48 PM, Nuwan Dias  wrote:
>>>
 IS Team,

 It looks like the TLSProtocolSocketFactory isn't honouring the HostName
 verification parameter. It always tries to do the hostname verification.
 Looks like a buggy behaviour to me.

 This causes problems for API Manager and any other product which has a
 distributed deployment (App Manager, DAS, etc) because it prevents http
 clients within our code from accessing Admin Services of remote nodes. The
 http clients fail since the server cert is by default for localhost and
 whenever we try to access through IPs it fails. The only way to overcome
 this is to create the proper certs and deploy on the server. Which is a
 huge hassle for simple test scenarios.

 The TLSProtocolSocketFactory is being set when the SAMLBearerGrant is
 being initialized. Until then things work fine. We either have to stop it
 being set or use a version of opensaml which supports skipping the host
 name verification (like our transports allow). Otherwise this is going to
 be a huge blocker for our releases.

 Thanks,
 NuwanD.

 On Thu, Mar 17, 2016 at 7:09 PM, Sam Sivayogam  wrote:

> HI All,
>
> Had a offline chat with Pulasthi and got to know that in IS 5.0.8
> there was opensaml upgrade from 2.4.1 to 2.6.4. After going through [1] 
> got
> to know that there is a hostname verification introduced in opensaml 2.6.4
> which is not there in opensaml 2.4.1 and this is why we are getting the
> above issue after moving to carbon identity 5.0.8.
>
> We are using *CommonsHTTPTransportSender * to call key
> manager internally and from what I understood if we set the 
> *HostnameVerifier
> *parameter to *AllowAll *we should be able to get rid of this issue,
> But still we are getting this issue. Does anyone know why HostnameVerifier
> prameter is not working as expected with CommonsHTTPTransportSender ?
>
> [1]
> http://grepcode.com/file_/repo1.maven.org/maven2/org.apache.servicemix.bundles/org.apache.servicemix.bundles.opensaml/2.4.1_2/org/opensaml/ws/soap/client/http/TLSProtocolSocketFactory.java/?v=diff=2.6.4_1
>
> Thanks,
>
> On Thu, Mar 17, 2016 at 11:12 AM, Sam Sivayogam  wrote:
>
>> Hi All,
>>
>> I'm trying to to upgrade APIM's Crabon kernel to 4.4.4. during the
>> kernel upgrade i also upgraded the following
>> carbon 

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

[Pubudu Gunatilaka]

Hi Isuru,

Without duplicating files and adding new files, I would rather prefer to
use the following hierarchy. For each and every different environment we
can have product profiles and include the environment specific values. For
Kubernetes, we can include the clustering section only in manager.yaml file
which resides under environment Kubernetes. And the rest of the other
configurations can be included in the generic file folder, i.e "
wso2/%{::product_name}/%{::product_version}/%{::product_profile}".


:hierarchy:
- "node/%{::clientcert}" - - "
wso2/%{::product_name}/%{::product_version}/%{::environment}
/%{::product_profile}"
- "wso2/%{::product_name}/%{::product_version}/%{::product_profile}"
- "wso2/%{::product_name}/%{::product_version}/default"
- "osfamily/%{::osfamily}"
- "vm_type/%{::vm_type}"
- wso2/common
- common


Thank you!

On Mon, Apr 11, 2016 at 1:07 PM, Isuru Haththotuwa  wrote:

>
>
> On Mon, Apr 11, 2016 at 12:47 PM, Gayan Gunarathne 
> wrote:
>
>>
>>
>> On Mon, Apr 11, 2016 at 12:39 PM, Lakmal Warusawithana 
>> wrote:
>>
>>>
>>>
>>> On Mon, Apr 11, 2016 at 12:22 PM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Chamila,

 On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis 
 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 
> wrote:
>
>> Hi Gayan,
>>
>> On Sun, Apr 10, 2016 at 5:02 PM, Gayan Gunarathne 
>> 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 

Re: [Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[云展智创]

Hi Shabir/Geesara,

Is that right to select 4 in below step? What’s the difference between 2 and 4 
archetype selection?

$ mvn archetype:generate -DarchetypeCatalog=local
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; 
support was removed in 8.0
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Maven Stub Project (No POM) 1
[INFO] 
[INFO] 
[INFO] >>> maven-archetype-plugin:2.4:generate (default-cli) > generate-sources 
@ standalone-pom >>>
[INFO] 
[INFO] <<< maven-archetype-plugin:2.4:generate (default-cli) < generate-sources 
@ standalone-pom <<<
[INFO] 
[INFO] --- maven-archetype-plugin:2.4:generate (default-cli) @ standalone-pom 
---
[INFO] Generating project in Interactive mode
[INFO] No archetype defined. Using maven-archetype-quickstart 
(org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
Choose archetype:
1: local -> org.wso2.iot:mdm-android-agent-archetype (Creates a MDM-Android 
agent project)
2: local -> cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF Device Type 
Archetype)
3: local -> org.wso2.mdm:mdm-android-agent-archetype (Creates a MDM-Android 
agent project)
4: local -> org.wso2.cdmf.devicetype:cdmf-devicetype-archetype (WSO2 CDMF 
Device Type Archetype)
Choose a number or apply filter (format: [groupId:]artifactId, case sensitive 
contains): : 4

－－
Zhanwen Zhou (Jason), 

在 2016年4月11日，下午3:08，Shabir Mohamed  写道：

> Hi Zhou,
> 
> If you still get any additional errors, please do send us the errors printed 
> in the error logs at:
> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/
> 
> so we could deduce why the device-deployer actually failed.
> 
> Regards
> 
> -
> Shabir Mohamed
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Email: sha...@wso2.com 
> Mobile: +94 77 3516019 | +94 71 6583393
> 
> On Mon, Apr 11, 2016 at 12:27 PM, Geesara Prathap  wrote:
> Hi Zhou,
> 
> copied file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the 
> repository/components/plugins folder)
> 
> No need to copy any of *.jar files manually. All necessary *jar files are 
> copied by maven archetype when building device type plugin. 
> 
> I found that the feature target file had been built (but I didn’t know why 
> the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature folder of 
> my device type, so I used following command to install it, successfully 
> finished.
> 
> the default version is set to 1.0-SNAPSHOT when building new device type 
> plugin. If you need you can change as you require. But please define correct 
> version, groupid and artifactId in device-deploye.xml as mention here[1]. 
> 
> 
> 
> 1. https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3 
> (branch IoTS-1.0.0-M3)
> 
> Thanks,
> Geesara
> 
> On Mon, Apr 11, 2016 at 12:04 PM, Charitha Goonetilleke  
> wrote:
> [Adding Ayyoob & Geesara to the thread]
> 
> Hi Zhou,
> 
> Since we are working with next milestone release, archtype in product-iots 
> master branch will not generate compatible device type plugin for M3 pack. It 
> is the reason for above mentioned issues. So please checkout M3 compatible 
> archtype from this link[2] and try to regenerate your device type with it.
> 
> Also, with given M3 compatible archtype, you don't want to copy any jar file 
> to plugins directory by your self.
> 
> [1] 
> https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M3/components/device-mgt-iot
> [2] 
> https://github.com/wso2/product-iots/tree/master/modules/tools/cdmf-devicetype-archetype
> [3] https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
> 
> Thanks & Regards,
> /charithag
> 
> 
> On Mon, Apr 11, 2016 at 11:10 AM, 云展智创  wrote:
> Hi all,
> 
> I created a new device type using cdmf-devicetype-archetype-master tool, and 
> updated the file device-deployer.xml (used IoTS-M3 SNAPSHOT, and copied file 
> org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the 
> repository/components/plugins folder) with correct info of my device type, 
> but when I built the file "device-deployer.xml”, I got the following errors:
> 
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: 
> Could not find artifact 
> com.smartcloudex:com.smartcloudex.thermometer.feature:zip:1.0.0-SNAPSHOT in 
> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
> 
> I found that the feature target file had been built (but I didn’t know why 
> the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature folder of 
> my device type, so I used following command to install it, successfully 
> finished.
> 
> mvn install:install-file 

Re: [Dev] Add some additional information to "Tier Availability" section in API publisher.

[Nuwan Dias]

+1. A label like "Subscription Tiers" should do IMO.

Thanks,
NuwanD.

On Mon, Apr 11, 2016 at 12:38 PM, Sanjeewa Malalgoda 
wrote:

>
> Hi Team,
> In API edit wizard's manage window we have label called "Tier
> Availability". But i think its better if we can change this to "Tiers
> Available for subscribe API", "Select tiers for subscribe API". We need to
> tell user "The tiers you select here are the ones available for subscriber
> to subscribe this API". WDYT?
>
>
> ​
> Thanks,
> sanjeewa.
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>


-- 
Nuwan Dias

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

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

[Isuru Haththotuwa]

On Mon, Apr 11, 2016 at 12:47 PM, Gayan Gunarathne  wrote:

>
>
> On Mon, Apr 11, 2016 at 12:39 PM, Lakmal Warusawithana 
> wrote:
>
>>
>>
>> On Mon, Apr 11, 2016 at 12:22 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Chamila,
>>>
>>> On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis 
>>> 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 
 wrote:

> Hi Gayan,
>
> On Sun, Apr 10, 2016 at 5:02 PM, Gayan Gunarathne 
> 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 to provide a sample?
>

>
> I think we can make this with with Defined Types[1][2] without creating
> duplicate set of YAML files for each platform. We can do the same as the
> example given in the document.
>
I do not think we need to duplicate the yaml files here. Sorry that the
sample in the first reply sent by me implied so. What we can do is refactor
out the hiera data so that data which is changing according to the platform
(ex.: clustering section) can be moved to a different yaml file(s). For an
example, clustering for kubernetes scenario can be included in
*puppet-modules/hieradata/dev/wso2/kubernetes/clustering.yaml*. Here,
'kubernetes' is the value of the facter which is used to identify the

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

[Gayan Gunarathne]

On Mon, Apr 11, 2016 at 12:39 PM, Lakmal Warusawithana 
wrote:

>
>
> On Mon, Apr 11, 2016 at 12:22 PM, Imesh Gunaratne  wrote:
>
>> Hi Chamila,
>>
>> On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis 
>> 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  wrote:
>>>
 Hi Gayan,

 On Sun, Apr 10, 2016 at 5:02 PM, Gayan Gunarathne 
 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?

 Thanks

>
> Thanks,
> Gayan
>
>
> On Sat, Apr 9, 2016 at 8:28 AM, Imesh Gunaratne 
> wrote:
>
>>
>> On Fri, Apr 8, 2016 at 7:48 PM, Isuru Haththotuwa 
>> wrote:
>>>
>>>
>>> hieradata
>>> |--- dev
>>>|--- wso2
>>>| 
>>>  |--- 
>>>|-- *vm*
>>> |--
>>> default.yaml
>>> |--
>>> manager.yaml
>>> |--
>>> worker.yaml
>>>|--* docker*
>>> |--
>>> default.yaml
>>> 

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

[Gayan Gunarathne]

On Mon, Apr 11, 2016 at 12:39 PM, Lakmal Warusawithana 
wrote:

>
>
> On Mon, Apr 11, 2016 at 12:22 PM, Imesh Gunaratne  wrote:
>
>> Hi Chamila,
>>
>> On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis 
>> 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  wrote:
>>>
 Hi Gayan,

 On Sun, Apr 10, 2016 at 5:02 PM, Gayan Gunarathne 
 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 to provide a sample?

>>>

I think we can make this with with Defined Types[1][2] without creating
duplicate set of YAML files for each platform. We can do the same as the
example given in the document.

[1]https://docs.puppet.com/puppet/latest/reference/lang_defined_types.html
[2]http://puppetlunch.com/puppet/hiera.html


>
 Thanks

>
> Thanks,
> Gayan
>
>
> On Sat, Apr 9, 2016 at 8:28 AM, Imesh Gunaratne 
> wrote:
>
>>
>> On Fri, Apr 8, 2016 at 7:48 PM, Isuru Haththotuwa 
>> wrote:
>>>
>>>
>>> hieradata
>>> |--- dev
>>>|--- wso2
>>>| 
>>>  |--- 
>>>|-- *vm*
>>> |--
>>> default.yaml
>>>

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

[Lakmal Warusawithana]

On Mon, Apr 11, 2016 at 12:22 PM, Imesh Gunaratne  wrote:

> Hi Chamila,
>
> On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis 
> 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  wrote:
>>
>>> Hi Gayan,
>>>
>>> On Sun, Apr 10, 2016 at 5:02 PM, Gayan Gunarathne 
>>> 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?
>>>
>>> Thanks
>>>

 Thanks,
 Gayan


 On Sat, Apr 9, 2016 at 8:28 AM, Imesh Gunaratne  wrote:

>
> On Fri, Apr 8, 2016 at 7:48 PM, Isuru Haththotuwa 
> wrote:
>>
>>
>> hieradata
>> |--- dev
>>|--- wso2
>>| 
>>  |--- 
>>|-- *vm*
>> |--
>> default.yaml
>> |--
>> manager.yaml
>> |--
>> worker.yaml
>>|--* docker*
>> |--
>> default.yaml
>> |--
>> manager.yaml
>> |--
>> worker.yaml
>>|--
>> *kubernetes*
>> |--
>> default.yaml
>> |--
>> manager.yaml
>> 

Re: [Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[Shabir Mohamed]

Hi Zhou,

If you still get any additional errors, please do send us the errors
printed in the error logs at:
/Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-
runtime/0.13.0/eclipse/

so we could deduce why the device-deployer actually failed.

Regards

-
*Shabir Mohamed*
*Software Engineer*
WSO2 Inc.; http://wso2.com
Email: sha...@wso2.com 
Mobile: +94 77 3516019 | +94 71 6583393

On Mon, Apr 11, 2016 at 12:27 PM, Geesara Prathap  wrote:

> Hi Zhou,
>
> copied file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the
> repository/components/plugins folder)
>
> No need to copy any of *.jar files manually. All necessary *jar files are
> copied by maven archetype when building device type plugin.
>
> I found that the feature target file had been built (but I didn’t know why
> the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature folder
> of my device type, so I used following command to install it, successfully
> finished.
>
> the default version is set to 1.0-SNAPSHOT when building new device type
> plugin. If you need you can change as you require. But please define
> correct version, groupid and artifactId in device-deploye.xml as
> mention here[1].
>
>
>
> 1.
> https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3 (
> *branch IoTS-1.0.0-M3*)
>
> Thanks,
> Geesara
>
> On Mon, Apr 11, 2016 at 12:04 PM, Charitha Goonetilleke <
> charit...@wso2.com> wrote:
>
>> [Adding Ayyoob & Geesara to the thread]
>>
>> Hi Zhou,
>>
>> Since we are working with next milestone release, archtype in
>> product-iots master branch will not generate compatible device type plugin
>> for M3 pack. It is the reason for above mentioned issues. So please
>> checkout M3 compatible archtype from this link[2] and try to regenerate
>> your device type with it.
>>
>> Also, with given M3 compatible archtype, you don't want to copy any jar
>> file to plugins directory by your self.
>>
>> [1]
>> https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M3/components/device-mgt-iot
>> [2]
>> https://github.com/wso2/product-iots/tree/master/modules/tools/cdmf-devicetype-archetype
>> [3]
>> https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
>>
>> Thanks & Regards,
>> /charithag
>>
>>
>> On Mon, Apr 11, 2016 at 11:10 AM, 云展智创  wrote:
>>
>>> Hi all,
>>>
>>> I created a new device type using cdmf-devicetype-archetype-master tool,
>>> and updated the file device-deployer.xml (used IoTS-M3 SNAPSHOT, and copied
>>> file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the
>>> repository/components/plugins folder) with correct info of my device type,
>>> but when I built the file "device-deployer.xml”, I got the following errors:
>>>
>>> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
>>> Could not find artifact
>>> com.smartcloudex:com.smartcloudex.thermometer.feature:zip:1.0.0-SNAPSHOT in
>>> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
>>>
>>> I found that the feature target file had been built (but I didn’t know
>>> why the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature
>>> folder of my device type, so I used following command to install it,
>>> successfully finished.
>>>
>>> mvn install:install-file -DgroupId=com.smartcloudex
>>> -DartifactId=com.smartcloudex.thermometer.feature -Dversion=1.0.0-SNAPSHOT
>>> -Dpackaging=zip
>>> -Dfile=/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/thermometer/feature/feature/target/com.smartcloudex.thermometer.feature-1.0-SNAPSHOT.zip
>>>
>>> But when I executed the command “mvn clean install -f
>>> device-deployer.xml” again I got the following errors. Was there any
>>> mistake in my steps? Could anyone help me? Thanks.
>>>
>>> [INFO]
>>> [INFO] --- carbon-p2-plugin:1.5.3:p2-profile-gen (feature-install) @
>>> devicetype-feature-installation ---
>>> [INFO] Running Equinox P2 Director Application
>>> [INFO] Command line:
>>> /bin/sh -c cd /Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT
>>> &&
>>> /Library/Java/JavaVirtualMachines/jdk1.8.0_73.jdk/Contents/Home/jre/bin/java
>>> -jar
>>> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
>>> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
>>> file:/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/p2-repo
>>> -artifactRepository
>>> file:/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/p2-repo
>>> -profileProperties org.eclipse.update.install.features=true -installIU
>>> org.coffeeking.connectedcup.feature.group/1.9.2.SNAPSHOT,org.homeautomation.currentsensor.feature.group/1.9.2.SNAPSHOT,com.smartcloudex.feature.group/1.0.0.SNAPSHOT,
>>> -bundlepool repository/components -shared repository/components/p2
>>> -destination repository/components/default 

[Dev] Add some additional information to "Tier Availability" section in API publisher.

[Sanjeewa Malalgoda]

Hi Team,
In API edit wizard's manage window we have label called "Tier
Availability". But i think its better if we can change this to "Tiers
Available for subscribe API", "Select tiers for subscribe API". We need to
tell user "The tiers you select here are the ones available for subscriber
to subscribe this API". WDYT?


​
Thanks,
sanjeewa.
-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

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

Re: [Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[Geesara Prathap]

Hi Zhou,

copied file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the
repository/components/plugins folder)

No need to copy any of *.jar files manually. All necessary *jar files are
copied by maven archetype when building device type plugin.

I found that the feature target file had been built (but I didn’t know why
the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature folder
of my device type, so I used following command to install it, successfully
finished.

the default version is set to 1.0-SNAPSHOT when building new device type
plugin. If you need you can change as you require. But please define
correct version, groupid and artifactId in device-deploye.xml as
mention here[1].



1. https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
(*branch IoTS-1.0.0-M3*)

Thanks,
Geesara

On Mon, Apr 11, 2016 at 12:04 PM, Charitha Goonetilleke 
wrote:

> [Adding Ayyoob & Geesara to the thread]
>
> Hi Zhou,
>
> Since we are working with next milestone release, archtype in product-iots
> master branch will not generate compatible device type plugin for M3 pack.
> It is the reason for above mentioned issues. So please checkout M3
> compatible archtype from this link[2] and try to regenerate your device
> type with it.
>
> Also, with given M3 compatible archtype, you don't want to copy any jar
> file to plugins directory by your self.
>
> [1]
> https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M3/components/device-mgt-iot
> [2]
> https://github.com/wso2/product-iots/tree/master/modules/tools/cdmf-devicetype-archetype
> [3]
> https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3
>
> Thanks & Regards,
> /charithag
>
>
> On Mon, Apr 11, 2016 at 11:10 AM, 云展智创  wrote:
>
>> Hi all,
>>
>> I created a new device type using cdmf-devicetype-archetype-master tool,
>> and updated the file device-deployer.xml (used IoTS-M3 SNAPSHOT, and copied
>> file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the
>> repository/components/plugins folder) with correct info of my device type,
>> but when I built the file "device-deployer.xml”, I got the following errors:
>>
>> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
>> Could not find artifact
>> com.smartcloudex:com.smartcloudex.thermometer.feature:zip:1.0.0-SNAPSHOT in
>> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
>>
>> I found that the feature target file had been built (but I didn’t know
>> why the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature
>> folder of my device type, so I used following command to install it,
>> successfully finished.
>>
>> mvn install:install-file -DgroupId=com.smartcloudex
>> -DartifactId=com.smartcloudex.thermometer.feature -Dversion=1.0.0-SNAPSHOT
>> -Dpackaging=zip
>> -Dfile=/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/thermometer/feature/feature/target/com.smartcloudex.thermometer.feature-1.0-SNAPSHOT.zip
>>
>> But when I executed the command “mvn clean install -f
>> device-deployer.xml” again I got the following errors. Was there any
>> mistake in my steps? Could anyone help me? Thanks.
>>
>> [INFO]
>> [INFO] --- carbon-p2-plugin:1.5.3:p2-profile-gen (feature-install) @
>> devicetype-feature-installation ---
>> [INFO] Running Equinox P2 Director Application
>> [INFO] Command line:
>> /bin/sh -c cd /Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT
>> &&
>> /Library/Java/JavaVirtualMachines/jdk1.8.0_73.jdk/Contents/Home/jre/bin/java
>> -jar
>> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
>> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
>> file:/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/p2-repo
>> -artifactRepository
>> file:/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/p2-repo
>> -profileProperties org.eclipse.update.install.features=true -installIU
>> org.coffeeking.connectedcup.feature.group/1.9.2.SNAPSHOT,org.homeautomation.currentsensor.feature.group/1.9.2.SNAPSHOT,com.smartcloudex.feature.group/1.0.0.SNAPSHOT,
>> -bundlepool repository/components -shared repository/components/p2
>> -destination repository/components/default -profile default -roaming
>> Installation failed.
>> The installable unit com.smartcloudex.feature.group/1.0.0.SNAPSHOT has
>> not been found.
>> Application failed, log file location:
>> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1460350536316.log
>>
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 IoTS(Device Types) - Connected Cup Component .. SUCCESS [
>> 0.660 s]
>> [INFO] WSO2 IoTS(Device Types) - Connected Cup Component .. SUCCESS [
>> 0.025 s]
>> [INFO] WSO2 IoTS(Device Types) - Connected Cup 

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

[Imesh Gunaratne]

Hi Chamila,

On Mon, Apr 11, 2016 at 7:19 AM, Chamila De Alwis  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.

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  wrote:
>
>> Hi Gayan,
>>
>> On Sun, Apr 10, 2016 at 5:02 PM, Gayan Gunarathne 
>> 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?
>>
>> Thanks
>>
>>>
>>> Thanks,
>>> Gayan
>>>
>>>
>>> On Sat, Apr 9, 2016 at 8:28 AM, Imesh Gunaratne  wrote:
>>>

 On Fri, Apr 8, 2016 at 7:48 PM, Isuru Haththotuwa 
 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 . 

Re: [Dev] [DEV][IOT][CDMF] Errors when building new device type in IoTS using cdmf-devicetype-archetype-master

[Charitha Goonetilleke]

[Adding Ayyoob & Geesara to the thread]

Hi Zhou,

Since we are working with next milestone release, archtype in product-iots
master branch will not generate compatible device type plugin for M3 pack.
It is the reason for above mentioned issues. So please checkout M3
compatible archtype from this link[2] and try to regenerate your device
type with it.

Also, with given M3 compatible archtype, you don't want to copy any jar
file to plugins directory by your self.

[1]
https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M3/components/device-mgt-iot
[2]
https://github.com/wso2/product-iots/tree/master/modules/tools/cdmf-devicetype-archetype
[3] https://github.com/GPrathap/cdmf-devicetype-archetype/tree/IoTS-1.0.0-M3

Thanks & Regards,
/charithag


On Mon, Apr 11, 2016 at 11:10 AM, 云展智创  wrote:

> Hi all,
>
> I created a new device type using cdmf-devicetype-archetype-master tool,
> and updated the file device-deployer.xml (used IoTS-M3 SNAPSHOT, and copied
> file org.wso2.carbon.device.mgt.iot_2.0.4.SNAPSHOT.jar into the
> repository/components/plugins folder) with correct info of my device type,
> but when I built the file "device-deployer.xml”, I got the following errors:
>
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> Could not find artifact
> com.smartcloudex:com.smartcloudex.thermometer.feature:zip:1.0.0-SNAPSHOT in
> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
>
> I found that the feature target file had been built (but I didn’t know why
> the version is 1.0-SNAPSHOT, and not 1.0.0-SNAPSHOT) in the feature folder
> of my device type, so I used following command to install it, successfully
> finished.
>
> mvn install:install-file -DgroupId=com.smartcloudex
> -DartifactId=com.smartcloudex.thermometer.feature -Dversion=1.0.0-SNAPSHOT
> -Dpackaging=zip
> -Dfile=/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/thermometer/feature/feature/target/com.smartcloudex.thermometer.feature-1.0-SNAPSHOT.zip
>
> But when I executed the command “mvn clean install -f device-deployer.xml”
> again I got the following errors. Was there any mistake in my steps? Could
> anyone help me? Thanks.
>
> [INFO]
> [INFO] --- carbon-p2-plugin:1.5.3:p2-profile-gen (feature-install) @
> devicetype-feature-installation ---
> [INFO] Running Equinox P2 Director Application
> [INFO] Command line:
> /bin/sh -c cd /Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT &&
> /Library/Java/JavaVirtualMachines/jdk1.8.0_73.jdk/Contents/Home/jre/bin/java
> -jar
> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
> file:/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/p2-repo
> -artifactRepository
> file:/Users/zhanwen/Documents/WSO2/IOT/wso2iots-1.0.0-SNAPSHOT/samples/p2-repo
> -profileProperties org.eclipse.update.install.features=true -installIU
> org.coffeeking.connectedcup.feature.group/1.9.2.SNAPSHOT,org.homeautomation.currentsensor.feature.group/1.9.2.SNAPSHOT,com.smartcloudex.feature.group/1.0.0.SNAPSHOT,
> -bundlepool repository/components -shared repository/components/p2
> -destination repository/components/default -profile default -roaming
> Installation failed.
> The installable unit com.smartcloudex.feature.group/1.0.0.SNAPSHOT has not
> been found.
> Application failed, log file location:
> /Users/zhanwen/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1460350536316.log
>
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Component .. SUCCESS [
> 0.660 s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Component .. SUCCESS [
> 0.025 s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Analytics capp SUCCESS [
> 1.296 s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup CDMF Plugin  SUCCESS [
> 2.029 s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Controller Service SUCCESS
> [  2.668 s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Manager Service SUCCESS [
> 1.366 s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Agent Web app SUCCESS [
> 1.292 s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup UI . SUCCESS [
> 0.137 s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Feature Parent SUCCESS [
> 0.017 s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Feature  SUCCESS [
> 2.407 s]
> [INFO] org.homeautomation.currentsensor.analytics . SUCCESS [
> 0.110 s]
> [INFO] org.homeautomation.currentsensor.plugin for CDMF ... SUCCESS [
> 0.801 s]
> [INFO] org.homeautomation.currentsensor.controller API  SUCCESS [
> 1.831 s]
> [INFO] org.homeautomation.currentsensor.manager ... SUCCESS [
> 1.488 s]
> [INFO] org.homeautomation.currentsensor.agent . SUCCESS 

Re: [Dev] Issues with JSON Schema in representing data types and in representing an array which contains non identical elements

[Sohani Weerasinghe]

Correction : This shouldn't add for the root level.

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

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

On Mon, Apr 11, 2016 at 11:32 AM, Sohani Weerasinghe 
wrote:

> Thanks Viraj.
>
> I think this should be applied to the root level as well.
>
> {
> "$schema": "http://json-schema.org/draft-04/schema#;,
> "title": "person",
>* "value"{*
> * "id": "http://wso2jsonschema.org
> ",*
> * "type": "object*
> *},*
> "properties": {
> "firstName": {
> "id": "http://wso2jsonschema.org/firstName;,
> "type": "string"
> },
> "phone": {
> "id": "http://wso2jsonschema.org/phone;,
> "type": "array",
> "items": [{
> *  “value”:{*
> *   "id":
> "http://wso2jsonschema.org/phone/phone
> ",*
> *   "type": "number"*
> *},*
> "attributes": {
> "primary": {
> "id": "http://wso2jsonschema.org/phone/primary;,
> "type": "boolean"
> }
> }
> }]
> }
> }
> }
>
>
>
>
>
>
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Mon, Apr 11, 2016 at 11:14 AM, Sohani Weerasinghe 
> wrote:
>
>> Ok.  For an xml like below, let's have the value field as follows
>>
>> 
>>
>>xyz
>>
>>071655339
>>
>>0112655333 
>> 
>>
>> {
>>
>> "$schema": "http://json-schema.org/draft-04/schema#;,
>>
>> "title": "person",
>>
>> "id": "http://wso2jsonschema.org;,
>>
>> "type": "object",
>>
>> "properties": {
>>
>> "firstName": {
>>
>> "id": "http://wso2jsonschema.org/firstName;,
>>
>> "type": "string"
>>
>> },
>>
>> "phone": {
>>
>> "id": "http://wso2jsonschema.org/phone;,
>>
>> "type": "array",
>>
>> "items": [{
>>
>> * “value”:{*
>>
>> * "id": "http://wso2jsonschema.org/phone/phone
>> ",*
>>
>> * "type": "number"*
>>
>> * },*
>>
>> "attributes": {
>>
>> "primary": {
>>
>> "id": "http://wso2jsonschema.org/phone/primary;,
>>
>> "type": "boolean"
>>
>> }
>>
>> }
>>
>> }]
>>
>> }
>>
>> }
>>
>> }
>>
>>
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Mon, Apr 11, 2016 at 11:05 AM, Nuwan Pallewela 
>> wrote:
>>
>>> Hi Sohani,
>>>
>>> +1 for the above approaches.
>>>
>>> We have to decide on how to represent non identical elements with same
>>> name. Viraj is working on it.
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Mon, Apr 11, 2016 at 10:44 AM, Sohani Weerasinghe 
>>> wrote:
>>>
 Hi Viraj/Nuwan,

 Really appreciate your input on this

 Thanks,
 Sohani

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

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

 On Tue, Apr 5, 2016 at 12:06 PM, Sohani Weerasinghe 
 wrote:

> Hi All,
>
> This is regarding clarifying the $subject.
>
> If we consider an xml as below, we are currently generating the below
> json schema
>
> http://www.w3.org/TR/html4/;>
> susinda
> 07177101
> 011265565501
> 
>
>
> {
> "$schema": "http://json-schema.org/draft-04/schema#;,
> "title": "h:person",
> "id": "http://wso2jsonschema.org;,
> "type": "object",
> "properties": {
> "firstName": {
> "id": "http://wso2jsonschema.org/firstName;,
> "type": "string"
> },
> "phone": {
> "id": "http://wso2jsonschema.org/phone;,
> "type": "array",
> "items": [{
> "id": "http://wso2jsonschema.org/phone/0;,
> "type": "object",
> "properties": {
> "ext": {
> "id": "http://wso2jsonschema.org/phone/0/ext;,
> "type": "number"
> }
> },
> "attributes": {
> "primary": {
> "id": "http://wso2jsonschema.org/phone/0/primary;,
> "type": "boolean"
> }
> }
> }]
> }
> }
> }
>
> But the issue is, we don't have any field to define the data type for
> phone ( eg: number). So are we going to introduce a new field as below to
> define the type?
>
> "phone": {
> "id": "http://wso2jsonschema.org/phone;,
> "type": "array",
> "items": [{
> "id": "http://wso2jsonschema.org/phone/0;,
> "type": "object",
> "value":{
>   type: "number",
>   
>
>  

Re: [Dev] Issues with JSON Schema in representing data types and in representing an array which contains non identical elements

[Sohani Weerasinghe]

Thanks Viraj.

I think this should be applied to the root level as well.

{
"$schema": "http://json-schema.org/draft-04/schema#;,
"title": "person",
   * "value"{*
* "id": "http://wso2jsonschema.org
",*
* "type": "object*
*},*
"properties": {
"firstName": {
"id": "http://wso2jsonschema.org/firstName;,
"type": "string"
},
"phone": {
"id": "http://wso2jsonschema.org/phone;,
"type": "array",
"items": [{
*  “value”:{*
*   "id":
"http://wso2jsonschema.org/phone/phone
",*
*   "type": "number"*
*},*
"attributes": {
"primary": {
"id": "http://wso2jsonschema.org/phone/primary;,
"type": "boolean"
}
}
}]
}
}
}







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

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

On Mon, Apr 11, 2016 at 11:14 AM, Sohani Weerasinghe 
wrote:

> Ok.  For an xml like below, let's have the value field as follows
>
> 
>
>xyz
>
>071655339
>
>0112655333 
> 
>
> {
>
> "$schema": "http://json-schema.org/draft-04/schema#;,
>
> "title": "person",
>
> "id": "http://wso2jsonschema.org;,
>
> "type": "object",
>
> "properties": {
>
> "firstName": {
>
> "id": "http://wso2jsonschema.org/firstName;,
>
> "type": "string"
>
> },
>
> "phone": {
>
> "id": "http://wso2jsonschema.org/phone;,
>
> "type": "array",
>
> "items": [{
>
> * “value”:{*
>
> * "id": "http://wso2jsonschema.org/phone/phone
> ",*
>
> * "type": "number"*
>
> * },*
>
> "attributes": {
>
> "primary": {
>
> "id": "http://wso2jsonschema.org/phone/primary;,
>
> "type": "boolean"
>
> }
>
> }
>
> }]
>
> }
>
> }
>
> }
>
>
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Mon, Apr 11, 2016 at 11:05 AM, Nuwan Pallewela  wrote:
>
>> Hi Sohani,
>>
>> +1 for the above approaches.
>>
>> We have to decide on how to represent non identical elements with same
>> name. Viraj is working on it.
>>
>> Thanks,
>> Nuwan
>>
>> On Mon, Apr 11, 2016 at 10:44 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi Viraj/Nuwan,
>>>
>>> Really appreciate your input on this
>>>
>>> Thanks,
>>> Sohani
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Tue, Apr 5, 2016 at 12:06 PM, Sohani Weerasinghe 
>>> wrote:
>>>
 Hi All,

 This is regarding clarifying the $subject.

 If we consider an xml as below, we are currently generating the below
 json schema

 http://www.w3.org/TR/html4/;>
 susinda
 07177101
 011265565501
 


 {
 "$schema": "http://json-schema.org/draft-04/schema#;,
 "title": "h:person",
 "id": "http://wso2jsonschema.org;,
 "type": "object",
 "properties": {
 "firstName": {
 "id": "http://wso2jsonschema.org/firstName;,
 "type": "string"
 },
 "phone": {
 "id": "http://wso2jsonschema.org/phone;,
 "type": "array",
 "items": [{
 "id": "http://wso2jsonschema.org/phone/0;,
 "type": "object",
 "properties": {
 "ext": {
 "id": "http://wso2jsonschema.org/phone/0/ext;,
 "type": "number"
 }
 },
 "attributes": {
 "primary": {
 "id": "http://wso2jsonschema.org/phone/0/primary;,
 "type": "boolean"
 }
 }
 }]
 }
 }
 }

 But the issue is, we don't have any field to define the data type for
 phone ( eg: number). So are we going to introduce a new field as below to
 define the type?

 "phone": {
 "id": "http://wso2jsonschema.org/phone;,
 "type": "array",
 "items": [{
 "id": "http://wso2jsonschema.org/phone/0;,
 "type": "object",
 "value":{
   type: "number",
   

   } ,
 "properties": {
 "ext": {
 "id": "http://wso2jsonschema.org/phone/0/ext;,
 "type": "number"
 }
 },
 "attributes": {
 "primary": {
 "id": "http://wso2jsonschema.org/phone/0/primary;,
 "type": "boolean"
 }
 }
 }]
 }

 Please advice.

 Also, how are we going to represent an array which contains non
 identical elements. Are we going to introduce xsi:type?

 Really appreciate your input in proceeding with this.

 Thanks,
 Sohani

 Sohani Weerasinghe
 Software Engineer
 

Re: [Dev] Issues with JSON Schema in representing data types and in representing an array which contains non identical elements

[Viraj Rajaguru]

Hi Sohani,

Yes. we will have "value" attribute to represent the data type as mentioned
above.

And also we are working on adding xsi:type support as well.

Thanks,
Viraj.

On Mon, Apr 11, 2016 at 11:14 AM, Sohani Weerasinghe 
wrote:

> Ok.  For an xml like below, let's have the value field as follows
>
> 
>
>xyz
>
>071655339
>
>0112655333 
> 
>
> {
>
> "$schema": "http://json-schema.org/draft-04/schema#;,
>
> "title": "person",
>
> "id": "http://wso2jsonschema.org;,
>
> "type": "object",
>
> "properties": {
>
> "firstName": {
>
> "id": "http://wso2jsonschema.org/firstName;,
>
> "type": "string"
>
> },
>
> "phone": {
>
> "id": "http://wso2jsonschema.org/phone;,
>
> "type": "array",
>
> "items": [{
>
> * “value”:{*
>
> * "id": "http://wso2jsonschema.org/phone/phone
> ",*
>
> * "type": "number"*
>
> * },*
>
> "attributes": {
>
> "primary": {
>
> "id": "http://wso2jsonschema.org/phone/primary;,
>
> "type": "boolean"
>
> }
>
> }
>
> }]
>
> }
>
> }
>
> }
>
>
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Mon, Apr 11, 2016 at 11:05 AM, Nuwan Pallewela  wrote:
>
>> Hi Sohani,
>>
>> +1 for the above approaches.
>>
>> We have to decide on how to represent non identical elements with same
>> name. Viraj is working on it.
>>
>> Thanks,
>> Nuwan
>>
>> On Mon, Apr 11, 2016 at 10:44 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi Viraj/Nuwan,
>>>
>>> Really appreciate your input on this
>>>
>>> Thanks,
>>> Sohani
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Tue, Apr 5, 2016 at 12:06 PM, Sohani Weerasinghe 
>>> wrote:
>>>
 Hi All,

 This is regarding clarifying the $subject.

 If we consider an xml as below, we are currently generating the below
 json schema

 http://www.w3.org/TR/html4/;>
 susinda
 07177101
 011265565501
 


 {
 "$schema": "http://json-schema.org/draft-04/schema#;,
 "title": "h:person",
 "id": "http://wso2jsonschema.org;,
 "type": "object",
 "properties": {
 "firstName": {
 "id": "http://wso2jsonschema.org/firstName;,
 "type": "string"
 },
 "phone": {
 "id": "http://wso2jsonschema.org/phone;,
 "type": "array",
 "items": [{
 "id": "http://wso2jsonschema.org/phone/0;,
 "type": "object",
 "properties": {
 "ext": {
 "id": "http://wso2jsonschema.org/phone/0/ext;,
 "type": "number"
 }
 },
 "attributes": {
 "primary": {
 "id": "http://wso2jsonschema.org/phone/0/primary;,
 "type": "boolean"
 }
 }
 }]
 }
 }
 }

 But the issue is, we don't have any field to define the data type for
 phone ( eg: number). So are we going to introduce a new field as below to
 define the type?

 "phone": {
 "id": "http://wso2jsonschema.org/phone;,
 "type": "array",
 "items": [{
 "id": "http://wso2jsonschema.org/phone/0;,
 "type": "object",
 "value":{
   type: "number",
   

   } ,
 "properties": {
 "ext": {
 "id": "http://wso2jsonschema.org/phone/0/ext;,
 "type": "number"
 }
 },
 "attributes": {
 "primary": {
 "id": "http://wso2jsonschema.org/phone/0/primary;,
 "type": "boolean"
 }
 }
 }]
 }

 Please advice.

 Also, how are we going to represent an array which contains non
 identical elements. Are we going to introduce xsi:type?

 Really appreciate your input in proceeding with this.

 Thanks,
 Sohani

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

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

>>>
>>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>@*
>>
>>
>>
>


-- 
Viraj Rajaguru
Senior Software Engineer
WSO2 Inc. : http://wso2.com

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