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