Re: [grpc-io] Re: Evolution of gRPCLB

2019-03-06 Thread 'Srini Polavarapu' via grpc.io
That's correct but note that xDS spec already exists as linked above and it 
is not something new that gRPC team is proposing.

On Saturday, March 2, 2019 at 8:44:45 PM UTC-8, Rama Rao wrote:
>
> Srini,
>
> Does it mean that if control plane implements the new xDS api that gRPC 
> team is going propose - gRPC services can make use of it for load balancing 
> (optionally control planes can also implement and configure 
> LoadReportService, which would be used for more intelligent load 
> balancing?) Is that right?
> Thanks,
> Rama
>
> On Sat, Mar 2, 2019 at 5:20 AM 'Srini Polavarapu' via grpc.io <
> grp...@googlegroups.com > wrote:
>
>>
>> On Friday, March 1, 2019 at 10:18:28 AM UTC-8, blazej...@gmail.com wrote:
>>>
>>>
>>> Do you work on both sides of xDS protocol, or only on the client-side 
>>> implementation?
>>>
>>
>> gRPC team does not work on the LB server side of xDS. The goal here is to 
>> be able to use existing and future xDS compatible LB servers as mentioned 
>> above. 
>>
>> -- 
>> 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+u...@googlegroups.com .
>> To post to this group, send email to grp...@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/5d61ae88-131e-47c6-b5c6-71b567c06194%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/0940fdc3-dba0-4961-a8ea-445e2a5e513b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] Re: Evolution of gRPCLB

2019-03-02 Thread Rama Rao
Srini,

Does it mean that if control plane implements the new xDS api that gRPC
team is going propose - gRPC services can make use of it for load balancing
(optionally control planes can also implement and configure
LoadReportService, which would be used for more intelligent load
balancing?) Is that right?
Thanks,
Rama

On Sat, Mar 2, 2019 at 5:20 AM 'Srini Polavarapu' via grpc.io <
grpc-io@googlegroups.com> wrote:

>
> On Friday, March 1, 2019 at 10:18:28 AM UTC-8, blazej...@gmail.com wrote:
>>
>>
>> Do you work on both sides of xDS protocol, or only on the client-side
>> implementation?
>>
>
> gRPC team does not work on the LB server side of xDS. The goal here is to
> be able to use existing and future xDS compatible LB servers as mentioned
> above.
>
> --
> 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/5d61ae88-131e-47c6-b5c6-71b567c06194%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAFfmCFE%3DsSCD%3DEfhUOgC8Myn5S-NryVTjYaM%2Bcvxxu2%3D7F-DEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[grpc-io] Re: Evolution of gRPCLB

2019-03-01 Thread 'Srini Polavarapu' via grpc.io

On Friday, March 1, 2019 at 10:18:28 AM UTC-8, blazej...@gmail.com wrote:
>
>
> Do you work on both sides of xDS protocol, or only on the client-side 
> implementation?
>

gRPC team does not work on the LB server side of xDS. The goal here is to 
be able to use existing and future xDS compatible LB servers as mentioned 
above. 

-- 
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/5d61ae88-131e-47c6-b5c6-71b567c06194%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] Re: Evolution of gRPCLB

2019-03-01 Thread Ram Kumar Rengaswamy
cc: +Gil Cukierman  +Edwin Hermans 
We are actively working on a project using a LookAside loadbalancer.
It would be great if XDS existed before deprecating grpclb,

On Fri, Mar 1, 2019 at 1:18 PM  wrote:

> As I mentioned here
> , we
> have been working on server-side gRPCLB implementation for some time and
> we'll start using it any day now. We chose gRPCLB because we needed high
> performance. It would be great to have some time for migrating to xDS,
> before gRPCLB gets removed.
>
> Do you work on both sides of xDS protocol, or only on the client-side
> implementation?
>
> W dniu czwartek, 28 lutego 2019 21:58:03 UTC+1 użytkownik Srini Polavarapu
> napisał:
>>
>> If you are using gRPCLB
>> ,
>> please read on:
>>
>> gRPC team is working on evolving the current gRPCLB functionality. We
>> will be moving away from our custom load balancing protocol and adopting xDS
>> Protocol
>> 
>> based on Envoy xDS API
>> .
>> This will allow interoperability with open source control planes that
>> support the xDS API, such as Istio Pilot
>> , go-control-plane
>>  and java-control-plane
>> . Other improvements
>> include a more flexible and improved load balancing policy configuration
>> 
>> and load reporting based on LRS
>> 
>> (load reporting service).
>>
>> The client-side implementation of xDS load balancing plugin will not be
>> compatible with the current gRPCLB protocol. Hence, the current gRPCLB
>> implementation can be considered deprecated. We are actively working on
>> the implementation of the new protocol. Expect to see a lot of progress in
>> the coming quarters, including a gRFC on the new design. If you are
>> relying on the current implementation in any way, please comment here so we
>> can figure out an appropriate time to remove it after the new
>> implementation is ready.
>>
>> --
> 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/6360c417-a8fb-47a3-a4d4-7ee99fc7867d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CA%2Bv4T%2BL9X%3Dzjyw9%3DuQssOJUGWb0RgzdqvxLr6gz8GBH0hQfKjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[grpc-io] Re: Evolution of gRPCLB

2019-03-01 Thread blazej . mroz24
As I mentioned here 
, we have 
been working on server-side gRPCLB implementation for some time and we'll 
start using it any day now. We chose gRPCLB because we needed high 
performance. It would be great to have some time for migrating to xDS, 
before gRPCLB gets removed. 

Do you work on both sides of xDS protocol, or only on the client-side 
implementation?

W dniu czwartek, 28 lutego 2019 21:58:03 UTC+1 użytkownik Srini Polavarapu 
napisał:
>
> If you are using gRPCLB 
> ,
>  
> please read on:
>
> gRPC team is working on evolving the current gRPCLB functionality. We will 
> be moving away from our custom load balancing protocol and adopting xDS 
> Protocol 
>  
> based on Envoy xDS API 
> . 
> This will allow interoperability with open source control planes that 
> support the xDS API, such as Istio Pilot 
> , go-control-plane 
>  and java-control-plane 
> . Other improvements 
> include a more flexible and improved load balancing policy configuration 
>  
> and load reporting based on LRS 
> 
>  
> (load reporting service).
>
> The client-side implementation of xDS load balancing plugin will not be 
> compatible with the current gRPCLB protocol. Hence, the current gRPCLB 
> implementation can be considered deprecated. We are actively working on 
> the implementation of the new protocol. Expect to see a lot of progress in 
> the coming quarters, including a gRFC on the new design. If you are 
> relying on the current implementation in any way, please comment here so we 
> can figure out an appropriate time to remove it after the new 
> implementation is ready.
>
>

-- 
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/6360c417-a8fb-47a3-a4d4-7ee99fc7867d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] Re: Evolution of gRPCLB

2019-03-01 Thread 'Mark D. Roth' via grpc.io
We don't currently support a way to plug in third-party resolvers and LB
policies in C-core without rebuilding it, but that's a feature we are
working on.  On the resolver side, there's a user-contributed PR that's
been in review for a while (https://github.com/grpc/grpc/pull/16617), which
you can ping if you're interested.

On Fri, Mar 1, 2019 at 5:49 AM Benjamin Krämer  wrote:

> We are currently using GRPCLB to workaround the missing name resolver
> support in C# (https://github.com/grpc/grpc/issues/11879). We will switch
> to xDS once it's implemented, but would still appreciate to get a
> possibility to use external name resolvers in c-core (doesn't have to be
> C#). grpc-java offers an experimental API for this:
> https://github.com/grpc/grpc-java/issues/1770
>
> AFAIK, c-core only supports adding custom name resolvers by compiling the
> c-core yourself, which would then allow to also use it with C#. Is this
> still the case, or is there a standard way by now?
>
> --
> 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/4a1feab9-af39-4d68-8c1a-256f4d83b164%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Mark D. Roth 
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/CAJgPXp5sDU2%3Dr0MrP4YKUfosuGXAFk3XtYL4mkmijkb8A%2BnZQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[grpc-io] Re: Evolution of gRPCLB

2019-03-01 Thread Benjamin Krämer
We are currently using GRPCLB to workaround the missing name resolver 
support in C# (https://github.com/grpc/grpc/issues/11879). We will switch 
to xDS once it's implemented, but would still appreciate to get a 
possibility to use external name resolvers in c-core (doesn't have to be 
C#). grpc-java offers an experimental API for this: 
https://github.com/grpc/grpc-java/issues/1770

AFAIK, c-core only supports adding custom name resolvers by compiling the 
c-core yourself, which would then allow to also use it with C#. Is this 
still the case, or is there a standard way by now?

-- 
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/4a1feab9-af39-4d68-8c1a-256f4d83b164%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.