Hi Jochen, Yes, gateways will be sitting behind the load balancer. The basic idea of the initial design was when spinning up a gateway node in a cluster, we need to provide a label name and the access url of the gateway. So, this access url will be the load balancer url. We have already introduced an overwrite property, where you can change the access url of the label if needed. You can find the initial discussion mail thread with subject [1].
As we are to move towards a new Admin API for label registration, we can change the access urls and other details using the API. [1] - [C5][APIM] Introducing labels based gateway environments in API Manager Thank you! On Fri, Jun 23, 2017 at 1:19 PM, Jochen Traunecker < [email protected]> wrote: > Hi Pubudu, > > I'm wondering how Gateways will get registered that have no idea about the > URLs they will be accessible? Sitting behind a load balancer and the URL of > the LB might change etc. > > Is there some document / discussion explaining how Gateways will be > registered to learn more about the approach? > > Thanks, > Jochen > > 2017-06-23 8:07 GMT+02:00 Pubudu Gunatilaka <[email protected]>: > >> Hi Lakmal, >> >> I think we have to rethink about the general use-case scenario. I have >> missed some of the points during the offline discussion we had. >> >> Let me first explain the current model. The label is a must for a gateway >> and gateway can have only one label. When you are spinning a new gateway, >> you can provide a label name with access urls. We manage access urls of the >> gateways using labels. For an API, you can select multiple labels. When you >> select an API in API Store, based on the attached labels to the API, we >> display the gateway endpoints where you can use to invoke the API. >> >> For the general use case, if we are not mandating or introducing a >> default label, we need to find a way of displaying gateway urls. One of the >> options I have in mind is to introduce a default label. It has the access >> url of the gateway. Still, we can go with the admin API and move away from >> the dynamic gateway registration. This is more suitable in order to >> introduce the permission model to the labels. The label selection is not >> mandatory when creating an API. If the user hasn't selected any label, we >> can attach the default label. >> >> Thank you! >> -- >> *Pubudu Gunatilaka* >> Committer and PMC Member - Apache Stratos >> Software Engineer >> WSO2, Inc.: http://wso2.com >> mobile : +94774078049 <%2B94772207163> >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Gruss / regards > > Jochen Traunecker > mailto: [email protected] > -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049 <%2B94772207163>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
