aws / aws/sagemaker-python-sdk
MLFlow E2E Example Notebook
- Lingua principale
- Python
- Stelle
- 2.3k
- Fork
- 1.3k
- Merge medio
- 1g 22h
- PR unite (30g)
- 35
Descrizione
**PR**: https://github.com/aws/sagemaker-python-sdk/pull/5514
**Describe the feature you'd like**
Add a new example notebook demonstrating the complete end-to-end workflow from training a PyTorch model to deploying it for inference on SageMaker, with MLflow 3.x tracking and model registry integration.
**How would this feature be used? Please describe.**
Users who want to leverage MLflow with SageMaker V3 SDK currently lack a comprehensive example showing the full workflow. This notebook would demonstrate:
1. Connecting to SageMaker MLflow tracking server
2. Training a PyTorch model with ModelTrainer while logging metrics/params to MLflow
3. Registering the trained model to MLflow Model Registry
4. Deploying directly from MLflow registry using ModelBuilder
5. Testing the deployed endpoint
Example workflow:
```
# Train with MLflow logging
model_trainer = ModelTrainer(training_image=..., source_code=...)
model_trainer.train()
# Deploy from MLflow registry
model_builder = ModelBuilder(
model_metadata={"MLFLOW_MODEL_PATH": "models:/my-model/1", ...}
)
model_builder.build()
model_builder.deploy()
```
**Describe alternatives you've considered**
Existing notebooks cover training or inference separately, but none show the integrated MLflow workflow end-to-end.
**Additional context**
Target location: v3-examples/ml-ops-examples/
Notebook name: v3-mlflow-train-inference-e2e-example.ipynb
Prerequisites: SageMaker MLflow App (tracking server ARN)
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia in v3-examples/ml-ops-examples/ e utilizza il prerequisito dell’ARN del server di tracking di SageMaker MLflow App. Crea v3-mlflow-train-inference-e2e-example.ipynb che includa il training con PyTorch e il logging di MLflow, la registrazione del modello, il deployment tramite ModelBuilder e il test dell’endpoint; il lavoro è completo quando viene dimostrato il workflow completo.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- jupyter-notebook, python, pytorch
- Ambito
- cloud, documentation, machine-learning
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Specificata chiaramente
- Idoneità per principianti
- 25/100