[Doc] Training service: Remote (#4560)

docs/source/experiment/remote.rst

@@ -1,12 +1,114 @@
 Remote Training Service
 =======================
 
-TBD
+NNI can run one experiment on multiple remote machines through SSH, called ``remote`` mode. It's like a lightweight training platform. In this mode, NNI can be started from your computer, and dispatch trials to remote machines in parallel.
+
+The OS of remote machines supports ``Linux``\ , ``Windows 10``\ , and ``Windows Server 2019``.
+
+Prerequisite
+------------
+
+
+1. Make sure the default environment of remote machines meets requirements of your trial code. If the default environment does not meet the requirements, the setup script can be added into ``command`` field of NNI config.
+
+2. Make sure remote machines can be accessed through SSH from the machine which runs ``nnictl`` command. It supports both password and key authentication of SSH. For advanced usage, please refer to :ref:`reference-remote-config-label` in reference for detailed usage.
+
+3. Make sure the NNI version on each machine is consistent. Follow the install guide `here <../Tutorial/QuickStart.rst>`__ to install NNI.
+
+4. Make sure the command of Trial is compatible with remote OSes, if you want to use remote Linux and Windows together. For example, the default python 3.x executable called ``python3`` on Linux, and ``python`` on Windows.
+
+In addition, there are several steps for Windows server.
+
+1. Install and start ``OpenSSH Server``.
+
+ 1) Open ``Settings`` app on Windows.
+
+ 2) Click ``Apps``\ , then click ``Optional features``.
+
+ 3) Click ``Add a feature``\ , search and select ``OpenSSH Server``\ , and then click ``Install``.
+
+ 4) Once it's installed, run below command to start and set to automatic start.
+
+ .. code-block:: bat
+
+ sc config sshd start=auto
+ net start sshd
+
+2. Make sure remote account is administrator, so that it can stop running trials.
+
+3. Make sure there is no welcome message more than default, since it causes ssh2 failed in NodeJs. For example, if you're using Data Science VM on Azure, it needs to remove extra echo commands in ``C:\dsvm\tools\setup\welcome.bat``.
+
+ The output like below is ok, when opening a new command window.
+
+ .. code-block:: text
+
+ Microsoft Windows [Version 10.0.17763.1192]
+ (c) 2018 Microsoft Corporation. All rights reserved.
+
+ (py37_default) C:\Users\AzureUser>
+
+Usage
+-----
+
+Use ``examples/trials/mnist-pytorch`` as the example. Suppose there are two machines, which can be logged in with username and password or key authentication of SSH. Here is a template configuration specification.
+
+.. code-block:: yaml
+
+ searchSpaceFile: search_space.json
+ trialCommand: python3 mnist.py
+ trialGpuNumber: 0
+ trialConcurrency: 4
+ maxTrialNumber: 20
+ tuner:
+ name: TPE
+ classArgs:
+ optimize_mode: maximize
+ trainingService:
+ platform: remote
+ machineList:
+ - host: 192.0.2.1
+ user: alice
+ ssh_key_file: ~/.ssh/id_rsa
+ - host: 192.0.2.2
+ port: 10022
+ user: bob
+ password: bob123
+
+The example configuration is saved in ``examples/trials/mnist-pytorch/config_remote.yml``.
+
+You can run below command on Windows, Linux, or macOS to spawn trials on remote Linux machines:
+
+.. code-block:: bash
+
+ nnictl create --config examples/trials/mnist-pytorch/config_remote.yml
 
-Temporarily placed here:
 
 .. _nniignore:
 
 .. Note:: If you are planning to use remote machines or clusters as your training service, to avoid too much pressure on network, NNI limits the number of files to 2000 and total size to 300MB. If your codeDir contains too many files, you can choose which files and subfolders should be excluded by adding a ``.nniignore`` file that works like a ``.gitignore`` file. For more details on how to write this file, see the `git documentation <https://git-scm.com/docs/gitignore#_pattern_format>`__.
 
 *Example:* :githublink:`config_detailed.yml <examples/trials/mnist-pytorch/config_detailed.yml>` and :githublink:`.nniignore <examples/trials/mnist-pytorch/.nniignore>`
+
+More features
+-------------
+
+Configure python environment
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+By default, commands and scripts will be executed in the default environment in remote machine. If there are multiple python virtual environments in your remote machine, and you want to run experiments in a specific environment, then use **pythonPath** to specify a python environment on your remote machine. 
+
+For example, with anaconda you can specify:
+
+.. code-block:: yaml
+
+ pythonPath: /home/bob/.conda/envs/ENV-NAME/bin
+
+Configure shared storage
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Remote training service support shared storage, which can help use your own storage during using NNI. Follow the guide `here <./shared_storage.rst>`__ to learn how to use shared storage.
+
+Monitor via TensorBoard
+^^^^^^^^^^^^^^^^^^^^^^^
+
+Remote training service support trial visualization via TensorBoard. Follow the guide `here <./tensorboard.rst>`__ to learn how to use TensorBoard.

docs/source/reference/experiment_config.rst

@@ -332,10 +332,12 @@ Introduction of the corresponding local training service can be found :doc:`../e
  If ``trialGpuNumber`` is less than the length of this value, only a subset will be visible to each trial.
  This will be used as ``CUDA_VISIBLE_DEVICES`` environment variable.
 
+.. _reference-remote-config-label:
+
 RemoteConfig
 ------------
 
-Detailed usage can be found `here <../TrainingService/RemoteMachineMode.rst>`__.
+Detailed usage can be found :doc:`../experiment/remote`.
 
 .. list-table::
  :widths: 10 10 80