Feature Introduction
The core definition of the model repository feature is to provide a Git-based version-controlled storage system for machine learning models, enabling teams to manage model files, track versions, and collaborate across tenants. It leverages Git LFS for large file storage and integrates with MLOps workflows to bridge model development and deployment.
TOC
Advantages
- Git-native Version Control
- Track model changes via commits/branches/tags, ensuring reproducibility.
- High-Speed Transfers
- CLI/Notebook uploads leverage internal network bandwidth (e.g., AML Notebooks同机房加速).
- Cross-Tenant Sharing
- Shared models can be accessed across namespaces (e.g.,
publicas a model marketplace).
- Shared models can be accessed across namespaces (e.g.,
- Seamless Integration
- Directly deploy models from the repository to inference services.
Applicable Scenarios
- Team Collaboration
- Multiple data scientists concurrently update and version models in the same repository.
- Model Auditing
- Trace historical versions via Git commits/tags for compliance.
- Centralized Asset Management
- Organize private/shared models in a unified hub with metadata (e.g., tags/descriptions).
Value Brought
- Reproducibility
- Pin model versions via tags (e.g.,
production/v1.2) to avoid training-serving skew.
- Pin model versions via tags (e.g.,
- Efficiency
- CLI uploads bypass browser limitations for large files (>10GB).
- Security
- Tenant isolation via GitLab credentials prevents unauthorized access.
- Cost Reduction
- Eliminate redundant storage by reusing shared models (e.g., public BERT weights).
Main Features
Model Repository Creation & Deletion
- Create an empty Git-backed repository with metadata (name/description/visibility).
- Delete models after dependency checks (e.g., ensure no active inference services).
File Management
- Web UI Upload
- Drag-and-drop files/folders (limited to small/medium sizes).
- CLI/Git LFS
- Use
git lfs trackfor large files (e.g.,*.bin,*.h5). - Example:
- Use
Version Control
- Branching
- Maintain parallel versions (e.g.,
experimentalvsmainbranches).
- Maintain parallel versions (e.g.,
- Tagging
- Mark releases via UI/CLI (e.g.,
git tag -a v2.0 -m "Stable release").
- Mark releases via UI/CLI (e.g.,
- Metadata Sync
- Auto-read
README.mdfrom the default branch for model descriptions.
- Auto-read
Cross-Tenant Sharing
- Shared Models
- Set visibility to "Shared" during creation for inter-tenant access.
- Public Marketplace
- Use
publicnamespace to publish open-source models (e.g., HuggingFace conversions).
- Use
Integration with MLOps
- Deployment Ready
- One-click inference service launch from tagged model versions.
- Notebook Integration
- Pull models directly into AML Notebooks for testing:
- Pull models directly into AML Notebooks for testing:
Technical Notes
- Git LFS Requirement
- Must include
.gitattributesto specify LFS-tracked files (e.g.,*.zip filter=lfs diff=lfs merge=lfs).
- Must include
- Default Branch Rules
- Misconfigured
README.mdmetadata may block inference deployment.
- Misconfigured
Create Model Repository
Step 1
Step 2
Create an empty Repository.
Step 3
Upload Model Files
You may upload model files through either of the following methods:
Option 1: Web UI Upload
- Use the File Management interface to upload files
- Drag and drop files/folders into the designated area
- Supported formats: All model file types (.h5, .bin, .pt, etc.)
- Progress tracking with real-time upload status
Option 2: Git Command Line Upload
- Get Repository Address:
- Navigate to Detail Info → Basic Info
- Copy the Git repository URL (e.g., https://<your-domain>/<namespace>/<repo-name>.git)
-
Upload via Git: