cc: +Gil Cukierman <[email protected]> +Edwin Hermans <[email protected]> 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 <[email protected]> wrote: > As I mentioned here > <https://groups.google.com/d/topic/grpc-io/d3etvZqctWc/discussion>, 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 >> <https://github.com/grpc/grpc/blob/618a3f561d4a93f263cca23abad086ed8f4d5e86/doc/load-balancing.md>, >> 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 >> <https://github.com/envoyproxy/data-plane-api/blob/master/XDS_PROTOCOL.md> >> based on Envoy xDS API >> <https://github.com/envoyproxy/data-plane-api/blob/master/API_OVERVIEW.md>. >> This will allow interoperability with open source control planes that >> support the xDS API, such as Istio Pilot >> <https://istio.io/docs/concepts/traffic-management/>, go-control-plane >> <https://github.com/envoyproxy/go-control-plane> and java-control-plane >> <https://github.com/envoyproxy/java-control-plane>. Other improvements >> include a more flexible and improved load balancing policy configuration >> <https://github.com/grpc/proposal/blob/master/A24-lb-policy-config.md> >> and load reporting based on LRS >> <https://github.com/envoyproxy/envoy/blob/master/api/envoy/service/load_stats/v2/lrs.proto> >> (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 [email protected]. > To post to this group, send email to [email protected]. > 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 > <https://groups.google.com/d/msgid/grpc-io/6360c417-a8fb-47a3-a4d4-7ee99fc7867d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To post to this group, send email to [email protected]. 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.
