Skip to content

Scaffold of inference related documentation#378

Open
schuups wants to merge 16 commits intoeth-cscs:mainfrom
schuups:inference-l1
Open

Scaffold of inference related documentation#378
schuups wants to merge 16 commits intoeth-cscs:mainfrom
schuups:inference-l1

Conversation

@schuups
Copy link
Copy Markdown
Contributor

@schuups schuups commented Apr 20, 2026

I am creating this PR primarily to get a rendered version for discussion with Pablo and team.

Feel free to adapt to fit the overall guidelines of our docs.

https://cscs-docs-preview.svc.cscs.ch/378/services/inference

@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

Updated contact information and added a brief introduction to inference services.
@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

@naevtamarkus
Copy link
Copy Markdown
Contributor

Adding description of inference services, as well as having both Stefano and Pablo as entry points for service design.

Updated the title and introductory text for the LLM Inference API service documentation.
@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

@bcumming
Copy link
Copy Markdown
Member

I made a few tweaks to file names and link names.
The pattern for links is
ref-inference for the top level index
ref-inference-api for the L1 API service. All sub-links on that page should start with ref-inference-api-
Each other page in inference will have a top level link ref-inference-X where X is a short description of the service.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

Updated the LLM Inference API service documentation to clarify beta status, usage requirements, and token consumption details. Added information on service limitations, access requests, and future improvements.
@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378


!!! todo
Instead of adding a screenshot, can't we
Add a screenshot to see how to obtain the API key
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this need a screenshot?

And, is the method for obtaining API keys documented elsewhere in our docs? If it is, link to that (and improve those docs if needed). That way we document everything once.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@naevtamarkus I am aware of the process but I don't have access to it to take printscreens. Can you do this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should say that this is temporary implementation (e.g., the API key is managed in a strange way vs. standards... i.e. the key is visible (not hidden), and not revokable, etc...)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is already explained in the limitations... I would avoid having "construction site" warnings all over the doc, but rather explain how it works "today" and change the doc when we change things... would you agree?

Updated the API documentation to include more details on participation in the Beta and clarified project key management.
@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

Clarified data usage policies and removed redundancy regarding sensitive data.
@github-actions
Copy link
Copy Markdown

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, or 📝 job summary for details.

Unrecognized words (1)

toget

To accept these unrecognized words as correct and remove the previously acknowledged and now absent words, you could run the following commands

... in a clone of the git@github.com:schuups/cscs-docs.git repository
on the inference-l1 branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/92453f59cac8985482dfc301a8ece4c6d7de8a0c/apply.pl' |
perl - 'https://github.com/eth-cscs/cscs-docs/actions/runs/24881853683/attempts/1' &&
git commit -m 'Update check-spelling metadata'

@github-actions
Copy link
Copy Markdown

preview available: https://cscs-docs-preview.svc.cscs.ch/378

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants