mlflow/mlflow

[FR] Deployment plugin for Cortex

Fechada

#6.962 aberto em 3 de out. de 2022

 (5 comentários) (0 reação) (1 responsável)Python (3.904 forks)batch import
area/dockerarea/model-registryarea/modelsarea/server-infraenhancementhelp wantedintegrations/databricks

Métricas do repositório

Stars
 (17.127 estrelas)
Métricas de merge de PR
 (Mesclagem média 2d 9h) (246 fundiu PRs em 30d)

Description

Willingness to contribute

No. I cannot contribute this feature at this time.

Proposal Summary

Create a model deployment plugin for Cortex

Motivation

What is the use case for this feature?

Simplifying the integration between MLflow Model Registry and Cortex

Why is this use case valuable to support for MLflow users in general?

Cortex was recently acquired by Databricks, so it seems likely that more and more MLflow users will consider it for model deployment/serving

Why is this use case valuable to support for your project(s) or organization?

Cortex sounds like it manages spot instances in AWS better than other serving tools, so the cost savings would be beneficial

Why is it currently difficult to achieve this use case?

As far as I understand, deploying models from the MLflow registry requires mlflow models serve (or the equivalent Python API), and this can only be done for environments with supported plugins

Details

No response

What component(s) does this bug affect?

  • area/artifacts: Artifact stores and artifact logging
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages
  • area/examples: Example code
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/pipelines: Pipelines, Pipeline APIs, Pipeline configs, Pipeline Templates
  • area/projects: MLproject format, project running backends
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/server-infra: MLflow Tracking server backend
  • area/tracking: Tracking Service, tracking client APIs, autologging

What interface(s) does this bug affect?

  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
  • area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
  • area/windows: Windows support

What language(s) does this bug affect?

  • language/r: R APIs and clients
  • language/java: Java APIs and clients
  • language/new: Proposals for new client languages

What integration(s) does this bug affect?

  • integrations/azure: Azure and Azure ML integrations
  • integrations/sagemaker: SageMaker integrations
  • integrations/databricks: Databricks integrations

Guia do colaborador