Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[edge_orchestrator+edge_model_serving] Rethink the way we serve model #83

Open
bojeanson opened this issue Feb 18, 2025 · 0 comments
Open

[edge_orchestrator+edge_model_serving] Rethink the way we serve model #83

bojeanson opened this issue Feb 18, 2025 · 0 comments

Comments

@bojeanson
Copy link
Collaborator

bojeanson commented Feb 18, 2025 •
edited
Loading

Description

Answer the folowing questions:

  • What information should have the edge_orchestrator on the edge_model_serving to get predictions ?
  • Should we only provide an URL to the edge_orchestrator to get predictions ?
  • What about the different models exposed by the edge_model_serving ? the versions ?
  • What about the hardcoded enum for the ModelName ? Should it be dynamic ?

Acceptance criteria

  • Have a clear design of how the edge_orchestrator interact with the edge_model_serving
  • Create the related tickets
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bojeanson