Hi Eric,
thanks for this detailed answer
J
This is quite interesting. We didn’t expected this behavior. Maybe it would be good to place this in the documentation, maybe with
this picture ;)
But this raises a few new questions for us. I try to explain:
·
Do we need for
alternate setup two UIs if we don’t want to use the REST interface or CLI-Tool?
o
One for «Gateway Alpha» and one for «Gateway Beta»?
o
Because I think you can only connect one elasticseach instance with the UI. Am I right on this?
o
What about the metrics in this use case
à leads to two UIs?
·
For the «one logical gateway»
o
If I understand you correctly this would mean that I also have to configure only one gateway in my UI and can add X more
without adding them into the UI.
I just have to point them against the same elasticsearch instance.
I also post this mail to the github issue, so we can stay within the mailinglist.
Thanks again,
Florian
Von: Eric Wittmann <eric.wittmann@redhat.com>
Gesendet: Friday, 30 November 2018 14:57
An: Volk, Florian <Florian.Volk@scheer-group.com>
Cc: chttl582@gmail.com; Marc Savy <marc.savy@redhat.com>; Kihm, Benjamin <Benjamin.Kihm@scheer-group.com>; Gebert, Alfred <Alfred.Gebert@scheer-group.com>; apiman-user@lists.jboss.org
Betreff: Re: [Apiman-user] [DKIM] Re: publish api to specific gateway
Sure no problem. The typical use-case for having multiple Gateway nodes is to scale the gateway layer horizontally and then put a load balancer in front of them. So for example you might start up 5 apiman gateway instances and configure
them all to use the same Elasticsearch instance for persistence (i.e. where to store configuration info like which APIs have been published). In this use-case, every gateway instance has the same set of APIs "published" to it. You can publish an API from
the UI/manager to **any** of the gateway instances and they will all know about that API. This is the "Single Logical Gateway" use-case -- the UI/manager and all consumers don't know or care how many gateway nodes there are - there could be 1 node, or there
could be 100. It behaves the same logically.
An **alternate** use case for having multiple gateways is when you actually want different APIs to be deployed to different gateways. So let's say you wanted Gateway Alpha to be able to proxy traffic to APIs A, B, and C. Then you have
Gateway Beta which you want to proxy traffic to APIs C, D, and E. In that case, consumer traffic MUST be routed through Gateway Alpha in order to access APIs A and B. Consumer traffic MUST be routed through Gateway Beta to access APIs D and E. Finally,
consumer traffic can be routed to **either** Gateway Alpha or Gateway Beta in order to access API C. Think of this as the "Two Logical Gateways" use-case.
In order to achieve the "Two Logical Gateways" use-case, you will need **two** separate persistence stores (Elasticsearch instances). Then you configure Gateway Alpha to use persistence store #1 and configure Gateway Beta to use persistence
store #2.
Note that you can have multiple gateway nodes for EACH of the two logical gateways. So for example you could have 5 gateway instances all pointing to persistence store #1 - these 5 nodes would make up a single logical gateway called "Gateway
Alpha". Then you could have 10 gateway instances all pointing to persistence store #2 - and these would be a single logical gateway called "Gateway Beta".
Here is a diagram of what the architecture might look like:
Hi Eric,
now I’m confused. We use Elasticsearch as backend. If I understand you correctly it would mean that
we have to setup an Elasticsearch instance for each gateway?
On the other point, if the gateways operate as logical unit, why is there a configuration option in
the ui?
Can you explain this a little bit more detailed? Maybe you have a configuration example.
Regards,
Florian
Von: Eric Wittmann
<eric.wittmann@redhat.com>
Gesendet: Friday, 30 November 2018 14:22
An: Volk, Florian <Florian.Volk@scheer-group.com>
Cc: chttl582@gmail.com; Marc Savy <marc.savy@redhat.com>; Kihm, Benjamin <Benjamin.Kihm@scheer-group.com>;
Gebert, Alfred <Alfred.Gebert@scheer-group.com>;
apiman-user@lists.jboss.org
Betreff: Re: [Apiman-user] [DKIM] Re: publish api to specific gateway
Are both gateways using the same persistent storage? Each gateway would need separate, independent persistence otherwise they will behave as a single "logical" gateway.
Hello together,
I was interested in this and made a short test in my loacal environment and I am able to reproduce
this.
I created a ticket on github for this (https://github.com/apiman/apiman/issues/711).
We may can fix this shortly.
Regards,
Florian
Von:
apiman-user-bounces@lists.jboss.org
<apiman-user-bounces@lists.jboss.org>
Im Auftrag von Jon Huang
Gesendet: Friday, 30 November 2018 03:28
An: marc.savy@redhat.com
Cc: apiman-user@lists.jboss.org
Betreff: [DKIM] Re: [Apiman-user] publish api to specific gateway
Dear Marc
Yes I untick another gateway however request towards both gateways still works.
Besides I tried to publish API via admin REST API (post api version then put gateway info), both gateways forwards request too.
Before filing a bug is there any apigw setting I shall check? (such as parameter in apiman.properties or etc...)
Regards
Apologies for the terribly slow reply. We've had so much spam I've missed legitimate emails like this.
Did you explicitly untick the other gateway? Was this via the UI or the API?
Dears
When I new an API, I have to choose which gateway to publish. (select list at Gateway section in the implementation tab).
However after creating a client app and contract for test, I found request via another gateway still works.
(I guest when publishing to gateway 1 and request via gateway 2 shall fail)
Am I misunderstanding or I miss some settings to make it work?
_______________________________________________
Apiman-user mailing list
Apiman-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user
_______________________________________________
Apiman-user mailing list
Apiman-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user
