Fix abstraction violations in command_runner interface (#10715)

* Fix abstraction violations in command_runner interface

* user guide

* lint

* breaking abstraction in commands

* extra initialization commands

* more cleanup

* small fixes

* fix test_integration_kubernetes.py

* lint

Co-authored-by: root <root@ip-172-31-28-155.us-west-2.compute.internal>
Co-authored-by: Ameer Haj Ali <ameerhajali@Ameers-MacBook-Pro.local>
This commit is contained in:
Ameer Haj Ali
2020-09-15 19:11:41 +00:00
committed by Barak Michener
co-authored by root Ameer Haj Ali
parent f907c1a715
commit b9e907aa4d
6 changed files with 72 additions and 120 deletions
+1 -7
View File
@@ -461,19 +461,13 @@ You have to specify your Kubernetes namespace explicitly:
from ray.tune.integration.kubernetes import NamespacedKubernetesSyncer
sync_config = tune.SyncConfig(
sync_to_driver=NamespacedKubernetesSyncer("ray", use_rsync=True)
sync_to_driver=NamespacedKubernetesSyncer("ray")
)
tune.run(train, sync_config=sync_config)
The ``KubernetesSyncer`` supports two modes for file synchronisation. Per
default, files are synchronized with ``kubectl cp``, requiring the ``tar``
binary in your pods. If you would like to use ``rsync`` instead your pods
will have to have ``rsync`` installed. Use the ``use_rsync`` parameter to
decide between the two options.
.. _tune-log_to_file:
Redirecting stdout and stderr to files