Hi, Please find the answers inline.
On Thu, Feb 9, 2017 at 11:18 AM, Shani Ranasinghe <[email protected]> wrote: > > > On Thu, Feb 9, 2017 at 11:08 AM, Rukshan Premathunga <[email protected]> > wrote: > >> Hi all, >> >> Another confusion scenario is some GW nodes are get register and again >> could be down. The another GW will register with same label and diffrent >> URL. In this case are we allowed to update existing level-GW_url or >> disallow to register that GW? >> >> Also if existing GW url is changed how we gonna edit the label? Since we >> have not provide label editing UI feature, we should update the label info >> that are reading from configuration. >> >> If you consider a production deployment, most of the time (always) gateways will be fronted with a load balancer. Basically url of the gateway will be the hostname which points to the load balancer. As long as we keep this hostname of the load balancer unchange, behavior of the gateways does not matter. But changing the URL of an exisiting label could be useful if there is a change. May be we can provide a system parameter called 'overwrite_labels' to overwrite the URL of the gateways. By going forward, there will be no any configuration file for configuring labels. This make sure that we are not binded to a configuration file and allowing users to add any label by starting up a new gateway node. > Thanks and Regards >> >> On Wed, Feb 8, 2017 at 6:03 PM, Pubudu Gunatilaka <[email protected]> >> wrote: >> >>> Hi Shani, >>> >>> Initially, you cannot update or delete a particular label. But you can >>> add a new label by starting up a new gateway with a new label. Then if you >>> need to change the particular label in an API, you need to update that API. >>> >>> So in that case, there would be a sorting based on the label on the > publisher side? would there be an update all also? Another thing, what if > a label is not given at start up for the gateway? does that mean that > gateway will serve all API's? > For the initial implementation we haven't thought of having sorting based on the label and update all feature. In the future we will add these features. We are not mandating the providing a label at API creation stage. There will be default label which will assign if there aren't any label selection. Basically, default label will provide to the gateway node and if you haven't change that label value, default gateway will be served the API requests which have default label in the API. If there isn't any label given at startup of the gateway, that gateway will not serve any API. By doing this we enforce the gateway node to have at least the default label value. 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
