Resource scheduling and cluster management for AI
Перейти к файлу
Yanjie Gao 3574ffda9d
[doc] update job retry doc link to section level (#1662)
* update job retry faq link

* update the link area
2018-11-30 11:39:10 +08:00
build Compare to `None` using identity `is` operator (#1630) 2018-11-14 13:33:13 +08:00
deployment fix memory limits (#1707) 2018-11-16 11:57:30 +08:00
docs [doc] update job retry doc link to section level (#1662) 2018-11-30 11:39:10 +08:00
examples [auto-test][example][tested] Add username support for auto-test to keep away path conflict (#1679) 2018-11-09 14:08:11 +08:00
marketplace Delete cntk_g2p.yaml from marketplace for it always failed; (#1526) 2018-10-17 16:45:31 +08:00
src make node manager tolerate disk and memory pressure (#1784) 2018-11-29 14:50:01 +08:00
subprojects/frameworklauncher [Launcher]: Upgrade httpcomponents.version (#1730) 2018-11-20 17:27:22 +08:00
.gitattributes Change the line ending character of js and css file to LF. 2018-03-07 13:09:53 +08:00
.gitignore restruct hadoop folder 2018-08-13 20:12:56 +08:00
.travis.yml Upgrade Node.js version of webportal & rest server to 8 (Carbon) (#1453) 2018-11-19 12:41:17 +08:00
Jenkinsfile always notify paialert (#1713) 2018-11-16 15:59:31 +08:00
LICENSE Initial commit 2017-09-25 04:24:56 -07:00
README.md Update README.md (#1621) 2018-11-07 11:11:01 +08:00
paictl.py [paictl] Add new command. paictl config get-id [-c kube-config-path] (#1699) 2018-11-16 10:18:51 +08:00
pailogo.jpg add logo 2018-04-18 19:37:06 +08:00
sysarch.png update system architecture section 2017-11-24 16:18:19 +08:00

README.md

Open Platform for AI (OpenPAI) alt text

Build Status Issues Pull Requests Coverage Status Version

OpenPAI is an open source platform that provides complete AI model training and resource management capabilities, it is easy to extend and supports on-premise, cloud and hybrid environments in various scale.

Table of Contents

  1. When to consider OpenPAI
  2. Why choose OpenPAI
  3. How to deploy
  4. How to use
  5. Resources
  6. Get Involved
  7. How to contribute

When to consider OpenPAI

  1. When your organization needs to share powerful AI computing resources (GPU/FPGA farm, etc.) among teams.
  2. When your organization needs to share and reuse common AI assets like Model, Data, Environment, etc.
  3. When your organization needs an easy IT ops platform for AI.
  4. When you want to run a complete training pipeline in one place.

Why choose OpenPAI

The platform incorporates the mature design that has a proven track record in Microsoft's large-scale production environment.

Support on-premises and easy to deploy

OpenPAI is a full stack solution. OpenPAI not only supports on-premises, hybrid, or public Cloud deployment but also supports single-box deployment for trial users.

Pre-built docker for popular AI frameworks. Easy to include heterogeneous hardware. Support Distributed training, such as distributed TensorFlow.

Most complete solution and easy to extend

OpenPAI is a most complete solution for deep learning, support virtual cluster, compatible Hadoop / kubernetes eco-system, complete training pipeline at one cluster etc. OpenPAI is architected in a modular way: different module can be plugged in as appropriate.

How to deploy

1 Prerequisites

Before start, you need to meet the following requirements:

  • Ubuntu 16.04
  • Assign each server a static IP address. Network is reachable between servers.
  • Server can access the external network, especially need to have access to a Docker registry service (e.g., Docker hub) to pull the Docker images for the services to be deployed.
  • All machines' SSH service is enabled, share the same username / password and have sudo privilege.
  • Need to enable NTP service.
  • Recommend no Docker installed or a Docker with api version >= 1.26.
  • See hardware resource requirements.

2 Deploy OpenPAI

2.1 Customized deploy
2.2 Single Box deploy

How to use

How to train jobs

Cluster administration

Resources

  • The OpenPAI user documentation provides in-depth instructions for using OpenPAI
  • Visit the release notes to read about the new features, or download the release today.
  • FAQ

Get Involved

  • StackOverflow: If you have questions about OpenPAI, please submit question at Stackoverflow under tag: openpai
  • Report an issue: If you have issue/ bug/ new feature, please submit it at Github

How to contribute

Contributor License Agreement

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Who should consider contributing to OpenPAI?

  • Folks who want to add support for other ML and DL frameworks
  • Folks who want to make OpenPAI a richer AI platform (e.g. support for more ML pipelines, hyperparameter tuning)
  • Folks who want to write tutorials/blog posts showing how to use OpenPAI to solve AI problems

Contributors

One key purpose of PAI is to support the highly diversified requirements from academia and industry. PAI is completely open: it is under the MIT license. This makes PAI particularly attractive to evaluate various research ideas, which include but not limited to the components.

PAI operates in an open model. It is initially designed and developed by Microsoft Research (MSR) and Microsoft Search Technology Center (STC) platform team. We are glad to have Peking University, Xi'an Jiaotong University, Zhejiang University, and University of Science and Technology of China join us to develop the platform jointly. Contributions from academia and industry are all highly welcome.