| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 215711454
|
|
|
|
| |
PiperOrigin-RevId: 211833041
|
|
|
|
| |
PiperOrigin-RevId: 207147507
|
|
|
|
| |
PiperOrigin-RevId: 206397604
|
|
|
|
|
|
| |
implementation-less skeleton.
PiperOrigin-RevId: 204188173
|
|
|
|
| |
PiperOrigin-RevId: 200251004
|
|
|
|
| |
PiperOrigin-RevId: 200095692
|
|
|
|
| |
PiperOrigin-RevId: 199362908
|
|
|
|
| |
PiperOrigin-RevId: 198894470
|
|
|
|
|
|
| |
or an environment variable) within TPUClusterResolver
PiperOrigin-RevId: 197494335
|
|
|
|
| |
PiperOrigin-RevId: 196196939
|
|
|
|
| |
PiperOrigin-RevId: 193735742
|
|
|
|
| |
PiperOrigin-RevId: 192388250
|
|
|
|
|
|
| |
This change allows advanced input pipelines (e.g. StreamingFilesDataset, or split-pipelines that use py_func's) to run in GKE- and GKE-like enviornments.
PiperOrigin-RevId: 191897639
|
|
|
|
| |
PiperOrigin-RevId: 190878279
|
|
|
|
| |
PiperOrigin-RevId: 188261273
|
|
|
|
|
|
| |
string handling processes.
PiperOrigin-RevId: 188180206
|
|
|
|
| |
PiperOrigin-RevId: 188051422
|
|
|
|
|
|
| |
This change integrates the TPUClusterResolver with GKE's support for Cloud TPUs
PiperOrigin-RevId: 187961802
|
|
|
|
| |
PiperOrigin-RevId: 187047094
|
|
|
|
| |
PiperOrigin-RevId: 186528023
|
|
|
|
| |
PiperOrigin-RevId: 184350480
|
|
|
|
|
|
|
|
| |
Adds "cluster_resolver_pip" as a dependancy to opensource contrib, and applies a standard `remove_undocumented` to clear extra symbols.
Docs are build from a bazel bulid, and without this change the cluster resolvers are not directly accessible in "tf.contirb.cluster_resolver" during the docs build, so they do not get documented.
PiperOrigin-RevId: 183993115
|
|
|
|
|
|
| |
supplied to the TPUClusterResolver
PiperOrigin-RevId: 182270565
|
|
|
|
|
|
| |
are public (https://www.googleapis.com/discovery/v1/apis/tpu/v1alpha1/rest).
PiperOrigin-RevId: 176710985
|
|
|
|
|
|
|
|
| |
easily specify the grpc connection string using ClusterResolvers rather than specifying the IP address manually.
Also fixes a bug in the `TPUClusterResolverTest` that caused tests to not run at all.
PiperOrigin-RevId: 174398488
|
|
|
|
| |
PiperOrigin-RevId: 173889798
|
|
|
|
|
|
| |
instead use a standard definition file stored in GCS.
PiperOrigin-RevId: 170960877
|
|
|
|
| |
PiperOrigin-RevId: 168650887
|
|
|
|
|
|
| |
to the GCE and TPU Cluster Resolvers, then we will use the GoogleCredentials.get_application_default() credentials. If users want to pass in no credentials at all, then they will have to pass in "None" explicitly.
PiperOrigin-RevId: 164659129
|
|
|
|
|
|
| |
rather than an object, so we need to use dict-syntax to access it.
PiperOrigin-RevId: 164033254
|
|
|
|
|
|
| |
Cluster Resolver classes within this are visible to open source TensorFlow users.
PiperOrigin-RevId: 163733781
|
|
|
|
|
|
| |
allow users to have a better experienec when specifying one or multiple Cloud TPUs for their training jobs by allowing users to use names rather than IP addresses.
PiperOrigin-RevId: 163393443
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
END_PUBLIC
---
Commit daa67ad17 authored by Jonathan Hseu<vomjom@vomjom.net>
Committed by Frank Chen<frankchn@gmail.com>:
Remove unittest import (#11596)
---
Commit 491beb74c authored by A. Unique TensorFlower<gardener@tensorflow.org>
Committed by TensorFlower Gardener<gardener@tensorflow.org>:
BEGIN_PUBLIC
Automated g4 rollback of changelist 162423171
PiperOrigin-RevId: 162541442
|
|
|
|
| |
PiperOrigin-RevId: 162466482
|
|
|
|
|
|
|
|
| |
instance group APIs, with support (in conjunction with UnionClusterResolver) for mapping multiple instance groups into one TensorFlow job (see the `testUnionMultipleInstanceRetrieval` test for details).
This should simplify creating and using standardized grpc TensorFlow server based instances using Compute Engine instance groups for distributed training.
PiperOrigin-RevId: 161443891
|
|
|
|
| |
PiperOrigin-RevId: 159373397
|
|
|
|
| |
PiperOrigin-RevId: 158565259
|
|
retrieving cluster information for running distributed TensorFlow.
Implementations of this class would eventually allow users to simply point TensorFlow at a cluster management endpoint, and TensorFlow will automatically retrieve the host names/IPs and port numbers of TensorFlow workers from the cluster management service.
PiperOrigin-RevId: 158358761
|