[Dev] WSO2 module to use Zipkin as tracing tool
Hi, We have been trying to build a module for WSO2 to work within a Microservice environment, and participate in a tracing context (in this case with Zipkin B3 Headers -> https://github.com/openzipkin/b3-propagation/blob/master/README.md) and the result, although in beta, is here: https://github.com/jmalvarezf/wso2-zipkin-tracer We just wanted to know if that could be useful for you. Tracing is a great tool for a microservices environment, and in case you want to use WSO2 as the Api Manager, we find very important for the gateway to work within that context. The idea was to create an Axis2 module, and a handler, the first one to manage all the requests to the gateway, and the second to manage the API requests. Best regards, Jose Maria. --- Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informaci?n confidencial, siendo para uso exclusivo del destinatario, quedando prohibida su divulgaci?n copia o distribuci?n a terceros sin la autorizaci?n expresa del remitente. Si Vd. ha recibido este mensaje err?neamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboraci?n. This message (including any attachments) may contain confidential information. It is intended for use by the recipient only. Any dissemination, copying or distribution to third parties without the express consent of the sender is strictly prohibited. If you have received this message in error, please delete it immediately and notify the sender. Thank you for your collaboration. --- ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Traffic Manager HA deployment on DC/OS
Thank you all for your comments on this.We will try to follow the H2 approach, but we are facing another problem regarding the communication between Traffic Manager instances. As we are defining the service in DC/OS as one service, there is no good way to tell the node to replicate the messages received from the APIGW only to the other TM instances. We have the idea to extend the jndi.properties parsing, to allow the use of the marathon API to get information about the other instances present in the service group. Could you give us a pointer to where we have to extend this to add the functionality?Thank you all,Jose Maria-Harsha Kumara <hars...@wso2.com> escribió: -Para: JOSE MARIA ALVAREZ FERNANDEZ <josemaria.alvarezfernan...@elcorteingles.es>De: Harsha Kumara <hars...@wso2.com>Fecha: 27/02/2017 07:51Cc: "WSO2 Developers' List" <dev@wso2.org>Asunto: Re: [Dev] Traffic Manager HA deployment on DC/OSHi Jose,On Thu, Feb 23, 2017 at 10:45 PM, JOSE MARIA ALVAREZ FERNANDEZ <josemaria.alvarezfernan...@elcorteingles.es> wrote:Hi all,As you may know, we are implementing WSO2 in El Corte Ingles, and we are trying to fit Traffic Manager in our architecture, based on DC/OS and containers. We would like to know which approach you think it may be better for the Traffic Manager component. As we are in a PaaS system, we would like to be able to scale this system out without problems. a) It is our understanding that we have to create a different database schema for every TM instance that we run. We would like to know if it is possible to run this without having to create a new schema for every component (that is, share the same schema). If we create a new schema, that would force us to differentiate the component at DC/OS level, giving them different configurations for different Traffic Manager instances. b) If that is not possible, we would like to know if it is possible to run TM with H2 in memory. As there is nothing that should be persisted in the TM schema, we thought that could be possible.Message Broker(MB) instance running in TM required MB_STORE data source which shouldn't shared with TM instance.It's Ok to have H2 database for it. But by default, MB writes all messages first to the database. Enable HA in TM is same as enabling HA in CEP (https://docs.wso2.com/display/CLUSTER44x/Clustering+CEP+4.0.0). The additional JMS related changes need to be configured to communicate throttle decisions to the gateway nodes.If none of the options are viable, what deployment schema would be the best for this component, taking into account that we would like to be active/active (being able to scale out)?Thank you very much for your help and comments,Jose Maria.www.elcorteingles.es--- Este mensaje, y en su caso, cualquier fichero anexo al mismo, puedecontener información confidencial, siendo para uso exclusivo del destinatario, quedando prohibida su divulgación copia o distribución a terceros sin la autorización expresa del remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y proceda a su borrado.Gracias por su colaboración.This message (including any attachments) may contain confidential information. It is intended for use by the recipient only. Any dissemination, copying or distribution to third parties without the express consent of the sender is strictly prohibited. If you have received this message in error, please delete it immediately and notify the sender. Thank you for your collaboration. ___Dev mailing listDev@wso2.orghttp://wso2.org/cgi-bin/mailman/listinfo/dev-- Harsha KumaraSoftware Engineer, WSO2 Inc.Mobile: +94775505618Blog:harshcreationz.blogspot.com www.elcorteingles.es --- Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener información confidencial, siendo para uso exclusivo del destinatario, quedando prohibida su divulgación copia o distribución a terceros sin la autorización expresa del remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboración. This message (including any attachments) may contain confidential information. It is intended for use by the recipient only. Any dissemination, copying or distribution to third parties without the express consent of the sender is strictly prohibited. If you have received this message in error, please delete it immediately and notify the sender. Thank you for your collaboration. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Traffic Manager HA deployment on DC/OS
Hi all,As you may know, we are implementing WSO2 in El Corte Ingles, and we are trying to fit Traffic Manager in our architecture, based on DC/OS and containers. We would like to know which approach you think it may be better for the Traffic Manager component. As we are in a PaaS system, we would like to be able to scale this system out without problems. a) It is our understanding that we have to create a different database schema for every TM instance that we run. We would like to know if it is possible to run this without having to create a new schema for every component (that is, share the same schema). If we create a new schema, that would force us to differentiate the component at DC/OS level, giving them different configurations for different Traffic Manager instances. b) If that is not possible, we would like to know if it is possible to run TM with H2 in memory. As there is nothing that should be persisted in the TM schema, we thought that could be possible.If none of the options are viable, what deployment schema would be the best for this component, taking into account that we would like to be active/active (being able to scale out)?Thank you very much for your help and comments,Jose Maria. www.elcorteingles.es --- Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener información confidencial, siendo para uso exclusivo del destinatario, quedando prohibida su divulgación copia o distribución a terceros sin la autorización expresa del remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboración. This message (including any attachments) may contain confidential information. It is intended for use by the recipient only. Any dissemination, copying or distribution to third parties without the express consent of the sender is strictly prohibited. If you have received this message in error, please delete it immediately and notify the sender. Thank you for your collaboration. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [DC/OS] DC/OS 1.8 clustering support
Hello all,We have also done a small change in the mesos-membership-scheme to support overlay networks with Docker in DC/OS 1.8. This change involves using the information from Marathon API, but getting different information to form the cluster member join information.I've created a pull request against master with all the details enclosed.https://github.com/wso2/mesos-artifacts/pull/10Please review, and share your comments.Thank you all,Jose Maria. www.elcorteingles.es --- Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener información confidencial, siendo para uso exclusivo del destinatario, quedando prohibida su divulgación copia o distribución a terceros sin la autorización expresa del remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboración. This message (including any attachments) may contain confidential information. It is intended for use by the recipient only. Any dissemination, copying or distribution to third parties without the express consent of the sender is strictly prohibited. If you have received this message in error, please delete it immediately and notify the sender. Thank you for your collaboration. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [API-Import-Export] Support templates when importing APIs
Hello all,As part of our project here, we have created another pull request to try to be more agile when importing APIs, so that we don't have to compile the API every time we want to change the environment backend URLs for an API.The pull request is here:https://github.com/wso2/product-apim/pull/1294It basically affects the api-import-export application. Please, review the PR let me know your thoughts about the idea and the implementation. We haven't provided a default implementation because it is out of our scope right now, but it should be pretty easy to do something properties-based in the machine.All the details about how it works are in the PR, but comment or doubt are more than welcome.Thank you all,Jose Maria. www.elcorteingles.es --- Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener información confidencial, siendo para uso exclusivo del destinatario, quedando prohibida su divulgación copia o distribución a terceros sin la autorización expresa del remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboración. This message (including any attachments) may contain confidential information. It is intended for use by the recipient only. Any dissemination, copying or distribution to third parties without the express consent of the sender is strictly prohibited. If you have received this message in error, please delete it immediately and notify the sender. Thank you for your collaboration. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [API-Import-Export] Templating import
Hello all,Again, as part of the project here in "El Corte Ingles" in Spain, we have detected another issue that we wanted to address and contribute to the project. Basically, we like the idea of being able to modify the API bundles on runtime, and not having to save different artifacts (zips) for every of the environments that we may have. So we have introduced a step in the import process to replace wildcards with velocity in the api.json file of the API bundle zip.The idea is working fine, but before doing the pull request, I wanted to separate our custom implementation of the Template interface that we have created from the solution. But as the solution is a war that is loaded as an application, I don't see a good way to try to load the implementation from somewhere else. I've tried to leave the jar file with only the implementation in the repository/components/lib folder of the APIM, but it of course fails due to a ClassNotFound (because the interface can't be found in the OSGI bundle that was created from the jar file).Do you have a way to try and resolve the split of interface and different implementations of this, so that the classloading is not a problem? The only way I could come up with is basically forking the app and including the custom implementation as a dependency, but I wanted to avoid that.I hope this is clear, if not, please don't hesitate to ask.Thank you for your help,Jose Maria. www.elcorteingles.es --- Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener información confidencial, siendo para uso exclusivo del destinatario, quedando prohibida su divulgación copia o distribución a terceros sin la autorización expresa del remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboración. This message (including any attachments) may contain confidential information. It is intended for use by the recipient only. Any dissemination, copying or distribution to third parties without the express consent of the sender is strictly prohibited. If you have received this message in error, please delete it immediately and notify the sender. Thank you for your collaboration. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [MongoDB] MongoDB support for analytics
Hi,I'm Jose Maria Alvarez, and I'm part of one of the biggest retailers in Spain, called "El Corte Ingles". As you may know, we have a project to include WSO API-GW in our current architecture, and as part of that, we faced a problem related to the fact that you don't support MongoDB as the database backend for analytics. As this NOSQL database is very popular in our company, and has a wide support in-house and outside, we have been working in developing a datasource for MongoDB to store analytics events inside that. We think we have finished the basic implementation, as all the tests are OK now (apart from analysing how to integrate the different configuration options that Mongo has), and we would like to share the idea behind the implementation with you.Basically, the principles are:- All that is a table in the RDBMS world is going to be a collection in Mongo.- There will be no support for partitioning inside the AnalyticsRecordStore, but left to sharding support in Mongo. We need to analyze the best key or compound key in the data to have better performance when writing, but this should be done apart from the code.- We use the tenantId and the tableName to create the collection name, as you do in Cassandra implementation.- The event will be saved with the default id created by mongo, and a field called arsId for the record ID field. The map with properties will be saved the same way it's saved in cassandra, leaving values as binaries.The rest is pretty straightforward. We have tested it also in a real installation (two docker instances, one for the API-GW, one for the APIM-Analytics), and we have done pull requests in carbon-data and carbon-analytics repositories to start analyzing this:https://github.com/wso2/carbon-data/pull/133https://github.com/wso2/carbon-analytics/pull/225Could you share with me your thoughts about the principles? Are they OK from your perspective? As you may know, Mongo has a 16MB limit for a document (record). Do you think that a real event in WSO2 can exceed that size? I've been speaking with Isabelle, that is helping us integrate the product, and she told us the events are very small (apart from any custom event we would like to store), but I would also like to get your thoughts on that.Thank you,Jose Maria. www.elcorteingles.es --- Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener información confidencial, siendo para uso exclusivo del destinatario, quedando prohibida su divulgación copia o distribución a terceros sin la autorización expresa del remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboración. This message (including any attachments) may contain confidential information. It is intended for use by the recipient only. Any dissemination, copying or distribution to third parties without the express consent of the sender is strictly prohibited. If you have received this message in error, please delete it immediately and notify the sender. Thank you for your collaboration. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
