mirror of
https://github.com/meta-llama/llama-stack.git
synced 2025-10-03 19:57:35 +00:00
6101c8e015
# What does this PR do? <!-- Provide a short summary of what this PR does and why. Link to relevant issues if applicable. --> <!-- If resolving an issue, uncomment and update the line below --> <!-- Closes #[issue-number] --> - Fixes broken links and Docusaurus search Closes #3518 ## Test Plan The following should produce a clean build with no warnings and search enabled: ``` npm install npm run gen-api-docs all npm run build npm run serve ``` <!-- Describe the tests you ran to verify your changes with result summaries. *Provide clear instructions so the plan can be easily re-executed.* -->
26 lines
1.2 KiB
Text
26 lines
1.2 KiB
Text
---
|
|
title: Resources
|
|
description: Resource federation and registration in Llama Stack
|
|
sidebar_label: Resources
|
|
sidebar_position: 4
|
|
---
|
|
|
|
# Resources
|
|
|
|
Some of these APIs are associated with a set of **Resources**. Here is the mapping of APIs to resources:
|
|
|
|
- **Inference**, **Eval** and **Post Training** are associated with `Model` resources.
|
|
- **Safety** is associated with `Shield` resources.
|
|
- **Tool Runtime** is associated with `ToolGroup` resources.
|
|
- **DatasetIO** is associated with `Dataset` resources.
|
|
- **VectorIO** is associated with `VectorDB` resources.
|
|
- **Scoring** is associated with `ScoringFunction` resources.
|
|
- **Eval** is associated with `Model` and `Benchmark` resources.
|
|
|
|
Furthermore, we allow these resources to be **federated** across multiple providers. For example, you may have some Llama models served by Fireworks while others are served by AWS Bedrock. Regardless, they will all work seamlessly with the same uniform Inference API provided by Llama Stack.
|
|
|
|
:::tip Registering Resources
|
|
|
|
Given this architecture, it is necessary for the Stack to know which provider to use for a given resource. This means you need to explicitly _register_ resources (including models) before you can use them with the associated APIs.
|
|
|
|
:::
|