Re: [Dev] Traffic Manager HA deployment on DC/OS

[Pubudu Gunatilaka]

Hi,

Please go through the articles [1] and [2] which describes the scalable
traffic manager patterns.

[1] -
http://wso2.com/library/articles/2016/10/article-scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-1/
[2] -
http://wso2.com/library/articles/2016/10/article-scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-2/

Thank you!

On Tue, Feb 28, 2017 at 4:34 PM, JOSE MARIA ALVAREZ FERNANDEZ <
josemaria.alvarezfernan...@elcorteingles.es> wrote:

> 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.alvarezfernandez@
> elcorteingles.es>
> De: Harsha Kumara <hars...@wso2.com>
> Fecha: 27/02/2017 07:51
> Cc: "WSO2 Developers' List" <dev@wso2.org>
> Asunto: Re: [Dev] Traffic Manager HA deployment on DC/OS
>
>
> Hi 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, 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
>>
>>
>
>
> --
> Ha

Re: [Dev] Traffic Manager HA deployment on DC/OS

[JOSE MARIA ALVAREZ FERNANDEZ]

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  escribió: -Para: JOSE MARIA ALVAREZ FERNANDEZ De: Harsha Kumara Fecha: 27/02/2017 07:51Cc: "WSO2 Developers' List" Asunto: Re: [Dev] Traffic Manager HA deployment on DC/OSHi Jose,On Thu, Feb 23, 2017 at 10:45 PM, JOSE MARIA ALVAREZ FERNANDEZ  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

Re: [Dev] Traffic Manager HA deployment on DC/OS

[Harsha Kumara]

Hi 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, 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
>
>


-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Traffic Manager HA deployment on DC/OS

[Abimaran Kugathasan]

Hi Jose,

I'm sorry, we need a separate database for each Traffic Manager node. What
you understood if correct. Sorry for the confusion.

On Mon, Feb 27, 2017 at 9:57 AM, Abimaran Kugathasan 
wrote:

> Hi 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.
>>
>
> I guess, by scheme you mean database, if so, we don't need seperate
> database for each Traffic manager nodes. You need to have one database
> among your Traffic Manager nodes.
>
> You can refer Traffic manager deployment patterns here [1] and [2]
>
>
>>
>> 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.
>>
>
> We don't encourage H2 database in production.
>
>>
>> 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)?
>>
>
> Additionally you can refer API Manager clustering guide here [3]. And,
> common deployement patterns here [4]
>
>
> [1] : http://wso2.com/library/articles/2016/10/article-
> scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-1/
> [2] : http://wso2.com/library/articles/2016/10/article-
> scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-2/
> [3] : https://docs.wso2.com/display/CLUSTER44x/Clustering+
> API+Manager+2.0.0
> [4] : https://docs.wso2.com/display/CLUSTER44x/API+
> Manager+Deployment+Patterns
>
>
>> 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
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820 <+94%2077%20392%202820>
>
> 
> 
>   
> 
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820


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

Re: [Dev] Traffic Manager HA deployment on DC/OS

[Abimaran Kugathasan]

Hi 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.
>

I guess, by scheme you mean database, if so, we don't need seperate
database for each Traffic manager nodes. You need to have one database
among your Traffic Manager nodes.

You can refer Traffic manager deployment patterns here [1] and [2]


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

We don't encourage H2 database in production.

>
> 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)?
>

Additionally you can refer API Manager clustering guide here [3]. And,
common deployement patterns here [4]


[1] :
http://wso2.com/library/articles/2016/10/article-scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-1/
[2] :
http://wso2.com/library/articles/2016/10/article-scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-2/

[3] : https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+2.0.0
[4] :
https://docs.wso2.com/display/CLUSTER44x/API+Manager+Deployment+Patterns


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


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820


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

[Dev] Traffic Manager HA deployment on DC/OS

[JOSE MARIA ALVAREZ FERNANDEZ]

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