googleapis / googleapis/python-aiplatform

Allow Model.upload not to use any serving contianer

未关闭
#2,034 0 条评论 3 个 reaction 已指派 0 人 在 GitHub 查看
api: vertex-ai
主要语言
Python
星标
905
派生
465
平均合并
1 天 13 小时
30 天内合并 PR
44

描述

Currently `aiplatform.Model.upload()` requires user to specify the `server_container_image_uri` ([link](https://cloud.google.com/vertex-ai/docs/samples/aiplatform-upload-model-sample#aiplatform_upload_model_sample-python)):
```
model = aiplatform.Model.upload(
display_name=DISPLAY_NAME,
artifact_uri=URI,
serving_container_image_uri="gcr.io/cloud-aiplatform/prediction/pytorch-cpu.1-9:latest"
)
```
It is clear the requirement comes from AutoML platform to allow model for ease of Endpoint deployment (which is a great and nicely streamlined feature!). However, it would be really optimal to allow flexibility of no needing to specify the serving container.

Particular need comes when user just wants to use VertexAI as Tracking and Registry service without fully leveraging AutoML with further Endpoint deployment (which requires embedded HTTP server within the service container).

It would be really convenient to the user to just be able to register the model for further consumption without having to bother about service capability. Current workaround is to still specify a dummy service container as above, but not having to assign any container resources would be better.

Thanks!

贡献指南

打开贡献指南

调研方向

Start at the aiplatform.Model.upload entry point and trace how serving_container_image_uri is validated and passed to Vertex AI. Clarify the registration-only behavior and its API constraints, then add coverage showing that a model can be registered without a serving container while preserving the existing deployment path.

由索引模型根据 Issue 内容生成。

评估

技术栈
gcp, python
领域
cloud, machine-learning
Issue 类型
功能
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。