Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add attempt_direct_path argument to create_channel #583

Merged
merged 19 commits into from Feb 4, 2024

Conversation

parthea
Copy link
Collaborator

@parthea parthea commented Jan 26, 2024

Fixes #482
b/267782870

@product-auto-label product-auto-label bot added the size: m Pull request size is medium. label Jan 26, 2024
@parthea parthea force-pushed the add-support-for-direct-path branch 5 times, most recently from 676ca58 to e777b53 Compare January 31, 2024 00:56
@product-auto-label product-auto-label bot added size: l Pull request size is large. and removed size: m Pull request size is medium. labels Jan 31, 2024
@parthea parthea force-pushed the add-support-for-direct-path branch 2 times, most recently from c4f537d to 257d4df Compare January 31, 2024 01:22
@parthea parthea marked this pull request as ready for review January 31, 2024 01:33
@parthea parthea requested review from a team as code owners January 31, 2024 01:33
Copy link
Contributor

@vchudnov-g vchudnov-g left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is looking good. I only reviewed the sync file and not the tests yet; I'll pick this back up tomorrow, but feel free to start responding to the comments here (or wait if you prefer; all good).

else:
# Use grpc.compute_engine_channel_credentials in order to support Direct Path.
# See https://grpc.github.io/grpc/python/grpc.html#grpc.compute_engine_channel_credentials
# TODO(b/323073050): Although `grpc.compute_engine_channel_credentials`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is public code, I would prefer to a public (GitHub) issue in this TODO.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in e9199a0

attempt_direct_path (Optional[bool]): If set, Direct Path will be attempted when
the request is made. Direct Path provides a proxyless connection which
increases the available throughput, reduces latency, and increases
reliability. Outside of GCE, the direct path request may fallback
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to spell out what GCE stands for in public docs? Not everyone looking at this file may be using GCE.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in e7e3cf7

If a `ServiceUnavailable` response is received when the request is sent, it is
recommended that the client repeat the request with `attempt_direct_path` set to `False`
as the Service may not support Direct Path. Using `ssl_credentials` with `attempt_direct_path`
set to `True` will result in `ValueError` as it is not yet supported.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
set to `True` will result in `ValueError` as it is not yet supported.
set to `True` will result in `ValueError` as this combination is not yet supported.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in e7e3cf7

Comment on lines 327 to 336
attempt_direct_path (Optional[bool]): If set, Direct Path will be attempted when
the request is made. Direct Path provides a proxyless connection which
increases the available throughput, reduces latency, and increases
reliability. Outside of GCE, the direct path request may fallback
to DNS if this is configured by the Service. This argument should only
be set in a GCE environment and for Services that are known to support Direct Path.
If a `ServiceUnavailable` response is received when the request is sent, it is
recommended that the client repeat the request with `attempt_direct_path` set to `False`
as the Service may not support Direct Path. Using `ssl_credentials` with `attempt_direct_path`
set to `True` will result in `ValueError` as it is not yet supported.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Should only be set in a GCE environment" is confusing in light of "Outside of GCE, the request may fall back". Clarify. I suspect you mean something like this:

Suggested change
attempt_direct_path (Optional[bool]): If set, Direct Path will be attempted when
the request is made. Direct Path provides a proxyless connection which
increases the available throughput, reduces latency, and increases
reliability. Outside of GCE, the direct path request may fallback
to DNS if this is configured by the Service. This argument should only
be set in a GCE environment and for Services that are known to support Direct Path.
If a `ServiceUnavailable` response is received when the request is sent, it is
recommended that the client repeat the request with `attempt_direct_path` set to `False`
as the Service may not support Direct Path. Using `ssl_credentials` with `attempt_direct_path`
set to `True` will result in `ValueError` as it is not yet supported.
attempt_direct_path (Optional[bool]): If set, Direct Path will be attempted when
the request is made. Direct Path is only available within a Google Compute
Engine environment and provides a proxyless connection which increases the
available throughput, reduces latency, and increases reliability.
- This argument should only
be set in a GCE environment and for Services that are known to support Direct
Path.
- If this argument is set outside of GCE, then this request will fail
unless the back-end service happens to have configured fall-back to DNS.
- If the request causes a `ServiceUnavailable` response, we
recommend that the client repeat the request with `attempt_direct_path` set to
`False` as the Service may not support Direct Path.
- Using `ssl_credentials` with `attempt_direct_path`
set to `True` will result in `ValueError` as this combination is not yet
supported.

(And similarly for the async version)

WDYT?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in e7e3cf7

attempt_direct_path (Optional[bool]): If set, Direct Path will be attempted when
the request is made. Direct Path provides a proxyless connection which
increases the available throughput, reduces latency, and increases
reliability. Outside of GCE, the direct path request may fallback
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
reliability. Outside of GCE, the direct path request may fallback
reliability. Outside of GCE, the direct path request may fall back

but see comment below

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in e7e3cf7

Comment on lines 395 to 397
target (str): The target service address which is converted into a format compatible with Direct Path.
If the target contains `dns:///` or does not have contain `:///`, the target will be converted in
a format compatible with Direct Path, otherwise the original target will be returned.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
target (str): The target service address which is converted into a format compatible with Direct Path.
If the target contains `dns:///` or does not have contain `:///`, the target will be converted in
a format compatible with Direct Path, otherwise the original target will be returned.
target (str): The target service address which is converted into a format compatible with Direct Path.
If the target contains `dns:///` or does not contain `:///`, the target will be converted in
a format compatible with Direct Path; otherwise the original target will be returned.

So the idea is that a :/// (except for dns:///) already denotes Direct Path, so no action is needed, correct? It might be good to be explicit about this assumption.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 44d5845

a format compatible with Direct Path, otherwise the original target will be returned.
"""

dns_prefix = "dns:///"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be helpful to clarify in a comment what the dns_prefix means, which I take it is to be explicit about an endpoint living in the Internet (ie outside GCP).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in e6ea7ec

@@ -288,6 +300,7 @@ def create_channel(
default_scopes=None,
default_host=None,
compression=None,
attempt_direct_path: Optional[bool] = None,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
attempt_direct_path: Optional[bool] = None,
attempt_direct_path: Optional[bool] = False,

Since it's meant to be a Boolean, might as well.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 0f3a0e4

Copy link
Contributor

@vchudnov-g vchudnov-g left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Nothing blocking, but I think some of my suggestions can make things tighter/clearer.

# If `ssl_credentials` is set and `attempt_direct_path` is set to `True`,
# raise ValueError as this is not yet supported.
# See https://github.com/googleapis/python-api-core/issues/590
if ssl_credentials is not None and attempt_direct_path:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we simplify to just this?:

Suggested change
if ssl_credentials is not None and attempt_direct_path:
if ssl_credentials and attempt_direct_path:

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 60b8acb

if HAS_GRPC_GCP: # pragma: NO COVER
if compression is not None and compression != grpc.Compression.NoCompression:
_LOGGER.debug(
"Compression argument is being ignored for grpc_gcp.secure_channel creation."
)
if attempt_direct_path:
warnings.warn(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency, the _LOGGER.debug in the previous lines should probably also become a warnings.warn

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 1a7578d and d96499f

Given a target, return a modified version which is compatible with Direct Path.

Args:
target (str): The target service address in the format 'hostname:port', 'dns://hostname' or other
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
target (str): The target service address in the format 'hostname:port', 'dns://hostname' or other
target (str): The target service address in the format 'hostname[:port]', 'dns://hostname[:port]' or other

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in af3a21b


Args:
target (str): The target service address in the format 'hostname:port', 'dns://hostname' or other
compatible format.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"other compatible format": link to a place that lists compatible formats, or remove this phrase which I think is puzzling by itself.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed in af3a21b

Comment on lines 405 to 406
direct_path_prefix = ":///"
if direct_path_prefix not in target:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
direct_path_prefix = ":///"
if direct_path_prefix not in target:
direct_path_separator = ":///"
if direct_path_separator not in target:

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in c0052e6

return grpc.secure_channel(
target, composite_credentials, compression=compression, **kwargs
)


def _modify_target_for_direct_path(target: str) -> str:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q: In general, an API endpoint could depend on the URL path and not just the host+port. Is this true of Google APIs? If so, where do we deal with the path part of the URI? (I realize these functions specify only host+port as inputs, so it's clear what they expect and they're doing the right thing, but I was wondering about this more general question.)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If so, where do we deal with the path part of the URI?

I believe this is part of the transcode method

Transcodes a grpc request pattern into a proper HTTP request following the rules outlined here,

def transcode(http_options, message=None, **request_kwargs):
"""Transcodes a grpc request pattern into a proper HTTP request following the rules outlined here,
https://github.com/googleapis/googleapis/blob/master/google/api/http.proto#L44-L312
Args:
http_options (list(dict)): A list of dicts which consist of these keys,
'method' (str): The http method
'uri' (str): The path template
'body' (str): The body field name (optional)
(This is a simplified representation of the proto option `google.api.http`)

https://github.com/googleapis/gapic-generator-python/blob/b4e6cfc0be8594e2575910699389600f5e92e552/gapic/templates/%25namespace/%25name_%25version/%25sub/services/%25service/transports/rest.py.j2#L372

@@ -21,7 +21,7 @@
import asyncio
import functools

from typing import Generic, Iterator, AsyncGenerator, TypeVar
from typing import AsyncGenerator, Generic, Iterator, Optional, TypeVar
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General notes:

  1. The comments from the sycn version apply here too
  2. Just a note for the future (not blocking this PR): a lot of the code seems identical or very similar to the sync code. We should consolidate sensibly to eliminate duplication. (I just filed consolidate duplicated code #593 to track more such instances)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for opening that issue! I also made changes to the async code based on the sync code feedback.

def test_create_channel_implicit(grpc_secure_channel, default, composite_creds_call):
def test_create_channel_implicit(
grpc_secure_channel,
default,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

default is too generic a name. I assume this is meant to take the google.auth.default you have patched in the decorators. Is there any way this parameter name could be made more descriptive (like auth-default, say), or does @mock preclude that?

(I realize this was pre-existing, so no need to spend too much time on this. But if it's easy...)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in d63402e

@@ -365,52 +365,92 @@ def test_wrap_errors_streaming(wrap_stream_errors):
wrap_stream_errors.assert_called_once_with(callable_)


@mock.patch("grpc.composite_channel_credentials")
@pytest.mark.parametrize(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be worth making this test function take a target parameter, and then parametrizing it as we do for test_create_channel_implicit_with_default_host below? target seems to be used the same way in both places, and this would allow us to check here the dns:/// and another-c2p:/// cases you parametrize below.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 396d8fa

@@ -298,48 +298,82 @@ def test_wrap_errors_streaming(wrap_stream_errors):
wrap_stream_errors.assert_called_once_with(callable_)


@mock.patch("grpc.composite_channel_credentials")
@pytest.mark.parametrize(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comments as in sync version apply here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 396d8fa

@parthea parthea merged commit 94726e7 into main Feb 4, 2024
27 checks passed
@parthea parthea deleted the add-support-for-direct-path branch February 4, 2024 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size: l Pull request size is large.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable DirectPath support for gRPC workflows
2 participants