.. role:: raw-html(raw)
   :format: html


**Run an Experiment on OpenpaiYarn**
========================================

The original ``pai`` mode is modificated to ``paiYarn`` mode, which is a distributed training platform based on Yarn.

Setup environment
-----------------

Install NNI, follow the install guide `here <../Tutorial/QuickStart.rst>`__.

Run an experiment
-----------------

Use ``examples/trials/mnist-tfv1`` as an example. The NNI config YAML file's content is like:

.. code-block:: yaml

   authorName: your_name
   experimentName: auto_mnist
   # how many trials could be concurrently running
   trialConcurrency: 2
   # maximum experiment running duration
   maxExecDuration: 3h
   # empty means never stop
   maxTrialNum: 100
   # choice: local, remote, pai, paiYarn
   trainingServicePlatform: paiYarn
   # search space file
   searchSpacePath: search_space.json
   # choice: true, false
   useAnnotation: false
   tuner:
     builtinTunerName: TPE
     classArgs:
       optimize_mode: maximize
   trial:
     command: python3 mnist.py
     codeDir: ~/nni/examples/trials/mnist-tfv1
     gpuNum: 0
     cpuNum: 1
     memoryMB: 8196
     image: msranni/nni:latest
   # Configuration to access OpenpaiYarn Cluster
   paiYarnConfig:
     userName: your_paiYarn_nni_user
     passWord: your_paiYarn_password
     host: 10.1.1.1

Note: You should set ``trainingServicePlatform: paiYarn`` in NNI config YAML file if you want to start experiment in paiYarn mode.

Compared with `LocalMode <LocalMode.rst>`__ and `RemoteMachineMode <RemoteMachineMode.rst>`__\ , trial configuration in paiYarn mode have these additional keys:


* cpuNum

  * Required key. Should be positive number based on your trial program's CPU  requirement

* memoryMB

  * Required key. Should be positive number based on your trial program's memory requirement

.. :githublink:`nnimsra/nni <deployment/docker/Dockerfile>`

* image

  * Required key. In paiYarn mode, your trial program will be scheduled by OpenpaiYarn to run in `Docker container <https://www.docker.com/>`__. This key is used to specify the Docker image used to create the container in which your trial will run.
  * We already build a docker image :githublink:`nnimsra/nni <deployment/docker/Dockerfile>`. You can either use this image directly in your config file, or build your own image based on it.

* virtualCluster

  * Optional key. Set the virtualCluster of OpenpaiYarn. If omitted, the job will run on default virtual cluster.

* shmMB

  * Optional key. Set the shmMB configuration of OpenpaiYarn, it set the shared memory for one task in the task role.

.. cannot find `Refer <https://github.com/microsoft/paiYarn/blob/2ea69b45faa018662bc164ed7733f6fdbb4c42b3/docs/faq.rst#q-how-to-use-private-docker-registry-job-image-when-submitting-an-openpaiYarn-job>`__

* authFile

  * Optional key, Set the auth file path for private registry while using paiYarn mode, `Refer <https://github.com/microsoft/paiYarn/blob/2ea69b45faa018662bc164ed7733f6fdbb4c42b3/docs/faq.rst#q-how-to-use-private-docker-registry-job-image-when-submitting-an-openpaiYarn-job>`__\ , you can prepare the authFile and simply provide the local path of this file, NNI will upload this file to HDFS for you.

* 
  portList  


  * 
    Optional key. Set the portList configuration of OpenpaiYarn, it specifies a list of port used in container, `Refer <https://github.com/microsoft/paiYarn/blob/b2324866d0280a2d22958717ea6025740f71b9f0/docs/job_tutorial.rst#specification>`__.\ :raw-html:`<br>`
    The config schema in NNI is shown below:

    .. code-block:: bash

       portList:
       - label: test
         beginAt: 8080
         portNumber: 2

    Let's say you want to launch a tensorboard in the mnist example using the port. So the first step is to write a wrapper script ``launch_paiYarn.sh`` of ``mnist.py``.

    .. code-block:: bash

       export TENSORBOARD_PORT=paiYarn_PORT_LIST_${paiYarn_CURRENT_TASK_ROLE_NAME}_0_tensorboard
       tensorboard --logdir . --port ${!TENSORBOARD_PORT} &
       python3 mnist.py

    The config file of portList should be filled as following:

    .. code-block:: yaml

       trial:
       command: bash launch_paiYarn.sh
       portList:
       - label: tensorboard
         beginAt: 0
         portNumber: 1

NNI support two kind of authorization method in paiYarn, including password and paiYarn token, `refer <https://github.com/microsoft/paiYarn/blob/b6bd2ab1c8890f91b7ac5859743274d2aa923c22/docs/rest-server/API.rst#2-authentication>`__. The authorization is configured in ``paiYarnConfig`` field.\ :raw-html:`<br>`
For password authorization, the ``paiYarnConfig`` schema is:

.. code-block:: bash

   paiYarnConfig:
     userName: your_paiYarn_nni_user
     passWord: your_paiYarn_password
     host: 10.1.1.1

For paiYarn token authorization, the ``paiYarnConfig`` schema is:

.. code-block:: bash

   paiYarnConfig:
     userName: your_paiYarn_nni_user
     token: your_paiYarn_token
     host: 10.1.1.1

Once complete to fill NNI experiment config file and save (for example, save as exp_paiYarn.yml), then run the following command

.. code-block:: bash

   nnictl create --config exp_paiYarn.yml

to start the experiment in paiYarn mode. NNI will create OpenpaiYarn job for each trial, and the job name format is something like ``nni_exp_{experiment_id}_trial_{trial_id}``.
You can see jobs created by NNI in the OpenpaiYarn cluster's web portal, like:

.. image:: ../../img/nni_pai_joblist.jpg
   :target: ../../img/nni_pai_joblist.jpg
   :alt: 


Notice: In paiYarn mode, NNIManager will start a rest server and listen on a port which is your NNI WebUI's port plus 1. For example, if your WebUI port is ``8080``\ , the rest server will listen on ``8081``\ , to receive metrics from trial job running in Kubernetes. So you should ``enable 8081`` TCP port in your firewall rule to allow incoming traffic.

Once a trial job is completed, you can goto NNI WebUI's overview page (like http://localhost:8080/oview) to check trial's information.

Expand a trial information in trial list view, click the logPath link like:

.. image:: ../../img/nni_webui_joblist.png
   :target: ../../img/nni_webui_joblist.png
   :alt: 


And you will be redirected to HDFS web portal to browse the output files of that trial in HDFS:

.. image:: ../../img/nni_trial_hdfs_output.jpg
   :target: ../../img/nni_trial_hdfs_output.jpg
   :alt: 


You can see there're three fils in output folder: stderr, stdout, and trial.log

data management
---------------

.. cannot find `guidance <https://github.com/microsoft/paiYarn/blob/master/docs/user/storage.rst>`__

If your training data is not too large, it could be put into codeDir, and nni will upload the data to hdfs, or you could build your own docker image with the data. If you have large dataset, it's not appropriate to put the data in codeDir, and you could follow the `guidance <https://github.com/microsoft/paiYarn/blob/master/docs/user/storage.rst>`__ to mount the data folder in container.

If you also want to save trial's other output into HDFS, like model files, you can use environment variable ``NNI_OUTPUT_DIR`` in your trial code to save your own output files, and NNI SDK will copy all the files in ``NNI_OUTPUT_DIR`` from trial's container to HDFS, the target path is ``hdfs://host:port/{username}/nni/{experiments}/{experimentId}/trials/{trialId}/nnioutput``

version check
-------------

NNI support version check feature in since version 0.6. It is a policy to insure the version of NNIManager is consistent with trialKeeper, and avoid errors caused by version incompatibility.
Check policy:


#. NNIManager before v0.6 could run any version of trialKeeper, trialKeeper support backward compatibility.
#. Since version 0.6, NNIManager version should keep same with triakKeeper version. For example, if NNIManager version is 0.6, trialKeeper version should be 0.6 too.
#. Note that the version check feature only check first two digits of version.For example, NNIManager v0.6.1 could use trialKeeper v0.6 or trialKeeper v0.6.2, but could not use trialKeeper v0.5.1 or trialKeeper v0.7.

If you could not run your experiment and want to know if it is caused by version check, you could check your webUI, and there will be an error message about version check.

.. image:: ../../img/webui-img/experimentError.png
   :target: ../../img/webui-img/experimentError.png
   :alt: 

