Merge branch 'folder-refactor' of github.com:Microsoft/pai into zhaoyu/port-conflict

docs/pai-build/pai-build.md

@@ -11,7 +11,7 @@ We have two parts of Pai-build: `build script` and `build context`.
     - **core**: all build logic implementation scripts are put under `build/core/` folder. ``build_center.py`` contains main execution process. ``build_handler.py`` is used to define single component build process. ``build_utility.py`` contains the utility methods like docker client.
     - **model**: ``dependency_graph.py`` and ``config_model.py`` are put under `build/model/` folder. ``dependency_graph.py`` defines **ServiceNode** and **ServiceGraph** to help construct component dependency graph. ``config_model.py`` defines build configuration model.
 - **build context:** All components’ **source code**, **build context** and **deployment related code** will be put under ``src`` folder.
-    - Each component's build context will bu put under ``src/${componentName}/build`` folder. Component owner should put corresponding ``dockerfiles`` here, and define its dependency in ``components.dep``. if component needs define customize actions before or after image build, he can prepare ``build-pre.sh`` and ``build-post.sh`` file.
+    - Each component's build context will be put under ``src/${componentName}/build`` folder. Component owner should put corresponding ``dockerfiles`` here, and define its dependency in ``components.dep``. if component needs define customize actions before or after image build, he can prepare ``build-pre.sh`` and ``build-post.sh`` file.
         - **dockerfiles**: All public dockerfiles current component provides. Pai-build will execute *docker build* with all files which extension is **.dockerfile** and the image name will be same as filename.
         - **components.dep**: Dependency list to determine components build sequence. Dependency wrote in ``components.dep`` should just be component name and make sure it can be found under src folder. Pai-build will copy the item’s whole folder to ``src/${componentName}/dependency/``.
         - **build-pre.sh**: Define customize action before build.  If component needs to do preparation before image build, component owner can implement in ``build-pre.sh`` file.
@@ -27,7 +27,7 @@ Build image by using ```pai_build.py``` which put under ``build/``. for the conf
 ### Build infrastructure services <a name="Service_Build"></a>
 
 ```
-python pai_build.py build -c /path/to/configuration-dir/ [ -s component-list ]
+sudo ./pai_build.py build -c /path/to/configuration-dir/ [ -s component-list ]
 ```
 
 - Build the corresponding component.
@@ -36,7 +36,7 @@ python pai_build.py build -c /path/to/configuration-dir/ [ -s component-list ]
 ### Push infrastructure image(s) <a name="Image_Push"></a>
 
 ```
-python pai_build.py push -c /path/to/configuration-dir/ [ -i image-list ]
+sudo ./pai_build.py push -c /path/to/configuration-dir/ [ -i image-list ]
 ```
 
 - tag and push image to the docker registry which is configured in the ```cluster-configuration```.