Hi Srinath, On Wed, Apr 27, 2016 at 11:52 AM, Srinath Perera <srin...@wso2.com> wrote:
> Hi Imesh, > > Publishing to both gateways is not good because things fall apart when a > one publication failed. Then a one node will be out of sync and will > continue to be out of sync. > Indeed, that's true! > > Also in C5, we are dropping depsync, and ask users to use rsync ( or some > other method like NSF). > > Can't we use rsync? (e.g. write a script that will get the list of docker > instances, and sync a give repo folder against all docker instances). > > Yes rsync is a good option, to use that we might need to consider following: - We would need to run rsync in a separate container, this can be done on K8S using pods but not on Mesos at the moment. - Rsync would need a user account or a SSH key to be able to talk to the gateway manager (assuming that rsync runs on each gateway worker). Thanks > --Srinath > > > On Wed, Apr 27, 2016 at 11:11 AM, Imesh Gunaratne <im...@wso2.com> wrote: > >> Hi Nuwan, >> >> On Wed, Apr 27, 2016 at 9:18 AM, Nuwan Dias <nuw...@wso2.com> wrote: >> >>> >>> On Wed, Apr 27, 2016 at 8:59 AM, Imesh Gunaratne <im...@wso2.com> wrote: >>> >>>> >>>> On Tue, Apr 26, 2016 at 5:37 PM, Nuwan Dias <nuw...@wso2.com> wrote: >>>> >>>>> >>>>> If there are more than 1 manager nodes, we can configure the publisher >>>>> to publish APIs to all of them. >>>>> >>>> >>>> That's interesting. If so we may not need a gateway manager at all. Can >>>> you please describe how that works? Do we need to specify IP addresses of >>>> each gateway node in publisher? >>>> >>> >>> This capability is intended to handle having multiple gateway clusters. >>> For example, if you have an internal Gateway cluster and an external >>> Gateway cluster, you can specify the url of the manager node of each >>> cluster on the api-manager.xml of the Publisher. Then from the Publisher >>> UI, you can publish an API to a selected Gateway manager or both (by >>> default it publishes to all). >>> >> >> Can you please point me to the code which handles this? >> >> We should be able to introduce an extension point here and add an >> implementation for each container cluster manager, similar to the >> clustering membership schemes we implemented. This would let us dynamically >> list the available gateway nodes in the Publisher and let the Publisher >> sends the APIs to all the available gateway nodes. Then we would not need a >> gateway manager and things would be much simple and straightforward. >> >> Thanks >> >> >>> >>>> Thanks >>>> >>>>> >>>>>> - API Gateway Manager pod needs to mount a volume to persist the >>>>>> Synapse APIs. This is vital for allowing the Gateway Manager pod to >>>>>> auto >>>>>> heal without loosing the Synapse APIs on the filesystem. >>>>>> >>>>>> >>>>>> - This design does not depend on any native features of the >>>>>> container cluster management system. >>>>>> >>>>>> >>>>>> 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 TW: @imesh >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Nuwan Dias >>>>> >>>>> Technical Lead - WSO2, Inc. http://wso2.com >>>>> email : nuw...@wso2.com >>>>> Phone : +94 777 775 729 >>>>> >>>> >>>> >>>> >>>> -- >>>> *Imesh Gunaratne* >>>> Senior Technical Lead >>>> WSO2 Inc: http://wso2.com >>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>> W: http://imesh.io TW: @imesh >>>> Lean . Enterprise . Middleware >>>> >>>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Technical Lead - WSO2, Inc. http://wso2.com >>> email : nuw...@wso2.com >>> Phone : +94 777 775 729 >>> >> >> >> >> -- >> *Imesh Gunaratne* >> Senior Technical Lead >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: http://imesh.io TW: @imesh >> Lean . Enterprise . Middleware >> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > ============================ > Srinath Perera, Ph.D. > http://people.apache.org/~hemapani/ > http://srinathsview.blogspot.com/ > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Imesh Gunaratne* Senior Technical Lead WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: http://imesh.io TW: @imesh Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
