migrate-from-model-serving

Migrate MLflow ResponsesAgents from Databricks Model Serving to Databricks Apps.

183|146|Updated Jun 6, 2024
One-click install
npx skills add https://github.com/databricks/app-templates --skill migrate-from-model-serving-databricks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-model-serving
Source: https://github.com/databricks/app-templates/tree/main/agent-openai-agents-sdk/.claude/skills/migrate-from-model-serving
Command: npx skills add https://github.com/databricks/app-templates --skill migrate-from-model-serving-databricks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the migration of existing MLflow ResponsesAgents deployed on Databricks Model Serving to the more flexible and integrated Databricks Apps platform.

Core Features & Use Cases

  • Code Transformation: Converts predict()/predict_stream() methods to @invoke/@stream decorators.
  • Async Support: Optionally migrates code to an asynchronous pattern for improved concurrency.
  • Artifact Management: Downloads and reapplies original model artifacts and code dependencies.
  • Use Case: You have a critical GenAI agent running on a Model Serving endpoint, and you want to leverage the latest Databricks Apps features like integrated UI, easier deployment, and enhanced observability. This Skill handles the technical conversion for you.

Quick Start

Use the migrate-from-model-serving skill to migrate your MLflow agent from Model Serving to Databricks Apps.

Frequently Asked Questions about migrate-from-model-serving

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate MLflow agents from Databricks Model Serving to Databricks Apps?

Migrate MLflow agents to Databricks Apps by transforming class-based predict methods into decorated functions. This Skill automates converting ResponsesAgents and configures Databricks Asset Bundles for deployment on the new platform.

What is the process for converting MLflow predict methods to Databricks Apps decorators?

Converting MLflow predict methods to Databricks Apps decorators involves transforming predict and predict_stream methods into invoke and stream decorated functions. The Skill handles this code transformation for both synchronous and asynchronous execution.

Can I migrate my MLflow agent to asynchronous code when moving to Databricks Apps?

Yes, you can migrate MLflow agents to an asynchronous pattern when moving to Databricks Apps. The Skill optionally converts your code to support asynchronous operations for improved concurrency during deployment.

Does migrating to Databricks Apps handle downloading original model artifacts and dependencies?

Migrating to Databricks Apps handles downloading and reapplying original model artifacts and code dependencies. The Skill ensures your GenAI agent retains its required components throughout the deployment modernization process.

Why should I move my GenAI agent from Model Serving to Databricks Apps?

Moving GenAI agents from Model Serving to Databricks Apps provides a more flexible deployment environment with an integrated UI, easier deployment processes, and enhanced observability features for monitoring agent performance.

What are the limitations when transforming MLflow ResponsesAgents for Databricks Apps?

Transforming MLflow ResponsesAgents for Databricks Apps focuses specifically on converting class-based predict methods to decorated functions. Migration scope is limited to the Databricks ecosystem and requires configuring Databricks Asset Bundles for deployment.