Creation Methods
AI development and optimization require frequent iterations and debugging. Modifications in datasets, training code, or parameters affect the quality of models. If the metadata of the development process cannot be centrally managed, the optimal model may fail to be reproduced.
With ModelArts, you can create AI applications using meta models from training jobs, OBS, or container images, and centrally manage all iterated and debugged AI applications.
Constraints
- After deploying a model in an ExeML project, it is automatically added to the AI application list. ExeML-generated AI applications can only be deployed, not downloaded.
- All users can create AI applications and manage AI application versions at no cost.
Meta Model Sources
- Importing a Meta Model from a Training Job: Create a training job in ModelArts to train a model. After obtaining a desired model, use it to create an AI application for service deployment.
- Importing a Meta Model from OBS: If you use a mainstream framework to develop and train a model locally, you can upload the model to an OBS bucket based on the model package specifications, import the model from OBS to ModelArts, and use the model to create an AI application for service deployment.
- Importing a Meta Model from a Container Image: If an AI engine is not supported by ModelArts, you can use it to build a model, import the model to ModelArts as a custom image, and use the image to create an AI application for service deployment.
Supported AI Engines for ModelArts Inference
If you import a model from OBS to ModelArts and use it to create an AI application, the following AI engines and versions are supported.
- Runtime environments marked with recommended are from unified images, which will be used as mainstream base images for inference. Unified images provide comprehensive installation packages. For details, see Preset Dedicated Images for Inference.
- Images of the old version will be discontinued. Use unified images instead.
- The base images to be removed are no longer maintained.
- A runtime environment of a unified image is named in the following format: <AI engine and version> - <Hardware and version: CPU, CUDA, or CANN> - <Python version> - <OS version> - <CPU architecture>
- Each preset AI engine has its default model start command. Do not modify it unless necessary.
Engine |
Runtime Environment |
Note |
---|---|---|
TensorFlow |
python3.6 python2.7 (unavailable soon) tf1.13-python3.6-gpu tf1.13-python3.6-cpu tf1.13-python3.7-cpu tf1.13-python3.7-gpu tf2.1-python3.7 (unavailable soon) tensorflow_2.1.0-cuda_10.1-py_3.7-ubuntu_18.04-x86_64 (recommended) |
|
Spark_MLlib |
python2.7 (unavailable soon) python3.6 (unavailable soon) |
|
Scikit_Learn |
python2.7 (unavailable soon) python3.6 (unavailable soon) |
|
XGBoost |
python2.7 (unavailable soon) python3.6 (unavailable soon) |
|
PyTorch |
python2.7 (unavailable soon) python3.6 python3.7 pytorch1.4-python3.7 pytorch1.5-python3.7 (unavailable soon) pytorch_1.8.0-cuda_10.2-py_3.7-ubuntu_18.04-x86_64 (recommended) |
|
MindSpore |
aarch64 (recommended) |
aarch64 can only be used to run models on Snt3 chips.
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot