Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

44032 Commits

279 Branches

381 Tags

1.3 GiB

Tag: Branch: Tree: cdc1c1afaf

Commit Graph

Author	SHA1	Message	Date
Richard Belleville	7adf2f5c65	Implement first pass at Python XDS interop client. I discovered a couple of existing shortcomings while implementing this client that mean this is not yet ready for inclusion in CI. I nonetheless want to get an early review and integrate this to the master branch, in the interest of small easily reviewable code changes. The first problem was that the bazel build has apparently never pulled roots.pem in as a data dependency. This appears not to have been a problem until XDS enters into the mix. This has been added into the Bazel build with a small change to the pyx_library rule. The larger problem is that there is currently no public Python API to get a peer's identity from the client side. This is crucial to determining the correctness of an interaction of a client-server pair under XDS. I intend to add such an method to the RpcContext interface in an upcoming PR and use it in the interop client. For the moment, I simply fake the peer details. Finally, I add a knob to run_xds_tests.py allowing multiple instances of this test to exist at once. Multiple instances forwarding to the same port cannot exist on GCE, so this enables multiple people to run tests at the same time.	5 years ago
Lidi Zheng	c34bef4ca4	Format all Bazel files with buildifier	5 years ago
Naresh	3af1aaadab	Basic setup to build gRPC Python with Bazel Building gRPC Python with Bazel has been one of the long requested additions to gRPC (#8079). Doing so had been made complex by the fact that Bazel itself is still in active development. There has been extensive work on building Cython code at tensorflow, which can be reused for gRPC's purposes as well. Major included changes required for building grpcio with Bazel are: - Include Cython as a third party Bazel package, to compile the Cython parts of gRPC Python. - Include rules for Python autoconfiguration so Python headers can be detected by cygrpc.	7 years ago

Author

SHA1

Message

Date

Richard Belleville

7adf2f5c65

Implement first pass at Python XDS interop client.

I discovered a couple of existing shortcomings while implementing this
client that mean this is *not yet ready for inclusion in CI*. I
nonetheless want to get an early review and integrate this to the master
branch, in the interest of small easily reviewable code changes.

The first problem was that the bazel build has apparently never pulled
roots.pem in as a data dependency. This appears not to have been a
problem until XDS enters into the mix. This has been added into the
Bazel build with a small change to the pyx_library rule.

The larger problem is that there is currently no public Python API to
get a peer's identity from the client side. This is crucial to
determining the correctness of an interaction of a client-server pair
under XDS. I intend to add such an method to the RpcContext interface in
an upcoming PR and use it in the interop client. For the moment, I
simply fake the peer details.

Finally, I add a knob to run_xds_tests.py allowing multiple instances of
this test to exist at once. Multiple instances forwarding to the same
port cannot exist on GCE, so this enables multiple people to run tests
at the same time.

5 years ago

Lidi Zheng

c34bef4ca4

Format all Bazel files with buildifier

5 years ago

Naresh

3af1aaadab

Basic setup to build gRPC Python with Bazel

Building gRPC Python with Bazel has been one of the long requested
additions to gRPC (#8079). Doing so had been made complex by the fact
that Bazel itself is still in active development.

There has been extensive work on building Cython code at tensorflow,
which can be reused for gRPC's purposes as well.

Major included changes required for building grpcio with Bazel are:
- Include Cython as a third party Bazel package, to compile the Cython
parts of gRPC Python.
- Include rules for Python autoconfiguration so Python headers can be
detected by cygrpc.

7 years ago

3 Commits (cdc1c1afaf20c623719d20002304050ee108fc6f)