On Wed, Feb 1, 2017 at 10:03 AM, Eric Anderson <ej...@google.com> wrote:
> On Wed, Feb 1, 2017 at 8:57 AM, Mark D. Roth <r...@google.com> wrote: > >> On Tue, Jan 31, 2017 at 12:43 PM, Eric Anderson <ej...@google.com> wrote: >> >>> >>> A more concrete flow: >>> >>> 1. client wants to connect to service.example.com >>> 2. check whether service.example.com should use a proxy. It shouldn't >>> 3. do DNS SRV resolution for _grpclb._tcp.service.example.com to >>> determine if it should use a LB. It should, and says to connect to >>> lb.example.com >>> 4. check whether lb.example.com should use a proxy. It should >>> 5. use CONNECT to lb.example.com (as a hostname) >>> >>> I recognize step 3 is speculative, but it seems any discussion as to how >>> GRPCLB+DNS works in speculative. >>> >> >> This approach would require an additional hook in the client channel >> code, separate from what we're already providing via the proxy mapper >> hook. I'd prefer to avoid providing two separate hooks for this. >> > > We will need it eventually. Otherwise we can't truly support the mixed > internal/external communication when DNS is unavailable for external hosts > (the full form of case 1). > > So the argument can be "we don't want to support it *now*" but I don't > think I could accept "we don't ever want to support it." > Do we know that there are cases where we'll need to support this? I don't doubt that there are cases where only connections to external servers should go through the proxy, but I wonder how many cases there are where users will need to use both internal and external servers with gRPC. If/when we do support this, do we have some idea how this would be configured? Is there some standard way of configuring which server names are internal vs. which are external, or would it be custom code for each environment? -- Mark D. Roth <r...@google.com> Software Engineer Google, Inc. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAJgPXp5ZCcYCjjksK1BY0iQqFWW5Qrg3X8bCRLKSjkXhHbA3EA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
