llama-stack-mirror/llama_stack/core/server
Charlie Doern 03399cebf3 feat: introduce API leveling, post_training to v1alpha
Rather than have a single `LLAMA_STACK_VERSION`, we need to have a `_V1`, `_V1ALPHA`, and `_V1BETA` constant.

This also necessitated addition of `level` to the `WebMethod` so that routing can be handeled properly.

For backwards compat, the `v1` routes are being kept around and marked as `deprecated`. When used, the server will log a deprecation warning.

move:

post_training to v1alpha as it is under heavy development and not near its final state
eval: job scheduling is not implemented. Relies heavily on the datasetio API which is under development missing implementations of specific routes indicating the structure of those routes might change. Additionally eval depends on the inference API which is going to be deprecated, eval will likely need a major API surface change to conform to using completions properly

Signed-off-by: Charlie Doern <cdoern@redhat.com>
2025-09-26 09:42:57 -04:00
..
__init__.py chore(rename): move llama_stack.distribution to llama_stack.core (#2975) 2025-07-30 23:30:53 -07:00
auth.py refactor(logging): rename llama_stack logger categories (#3065) 2025-08-21 17:31:04 -07:00
auth_providers.py feat: Add Kubernetes auth provider to use SelfSubjectReview and kubernetes api server (#2559) 2025-09-08 11:25:10 +02:00
quota.py refactor(logging): rename llama_stack logger categories (#3065) 2025-08-21 17:31:04 -07:00
routes.py feat: introduce API leveling, post_training to v1alpha 2025-09-26 09:42:57 -04:00
server.py chore: refactor tracingmiddelware (#3520) 2025-09-23 10:14:41 -07:00
tracing.py feat: introduce API leveling, post_training to v1alpha 2025-09-26 09:42:57 -04:00