Skip to content

Conversation

@tisnik
Copy link
Contributor

@tisnik tisnik commented Aug 1, 2025

Description

LCORE-247: getting started, running LCS from a container

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up service version
  • Bump-up dependent library
  • Bump-up library or tool used for development (does not change the final image)
  • CI configuration change
  • Konflux configuration change
  • Unit tests improvement
  • Integration tests improvement
  • End to end tests improvement

Related Tickets & Documents

  • Related Issue #LCORE-247

Summary by CodeRabbit

  • Documentation
    • Expanded and restructured the getting started guide with detailed instructions for deploying Lightspeed Core Stack (LCS) with Llama Stack in both separate process and embedded library modes.
    • Added step-by-step setup, configuration examples, and verification commands for each deployment mode.
    • Improved clarity with new sections, prerequisites, and configuration file examples.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 1, 2025

Walkthrough

The docs/getting_started.md documentation was extensively expanded and reorganized. It now provides detailed, step-by-step instructions for deploying the Lightspeed Core Stack (LCS) with Llama Stack in two modes: as a separate process and as a Python library within the container. Configuration examples and verification steps were added.

Changes

Cohort / File(s) Change Summary
Documentation Expansion & Restructuring
docs/getting_started.md
Replaced the previous section with a comprehensive, multi-part guide covering containerized deployment of LCS with Llama Stack, including prerequisites, setup, configuration examples, and verification steps for both process and library modes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Host
    participant LlamaStack
    participant LCSContainer

    User->>Host: Pull LCS container image (podman)
    User->>Host: Install Llama Stack (if separate process)
    User->>LlamaStack: Start Llama Stack server (if separate process)
    User->>Host: Prepare configuration files (run.yaml, lightspeed-stack.yaml)
    User->>LCSContainer: Run LCS container with configs mounted
    LCSContainer->>LlamaStack: Connect via TCP (if separate process)
    User->>LCSContainer: Verify LCS functionality
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

Poem

🐇
A stack of lightspeed, shining bright,
Now clearer paths for day and night.
With Llama’s help, both near and far,
In docs we find just where we are.
Two ways to run, both now explained—
Our getting started guide, unchained!
Hop on, deploy, let knowledge reign.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (8)
docs/getting_started.md (8)

30-41: Fix TOC indentation to silence markdown-lint (MD007).

Indentation is off by two spaces for the level-2 items, triggering MD007. Align all second-level bullets to exactly two spaces.

-    * [Retrieving *Lightspeed Core Stack* image](#retrieving-lightspeed-core-stack-image)
-        * [Prerequisites](#prerequisites-2)
-        * [Retrieve the image](#retrieve-the-image)
+  * [Retrieving *Lightspeed Core Stack* image](#retrieving-lightspeed-core-stack-image)
+    * [Prerequisites](#prerequisites-2)
+    * [Retrieve the image](#retrieve-the-image)

62-68: Unify list bullet style.

Mixing * (top-level) and - (nested) violates MD004. Either switch the top-level markers to - or convert all nested ones to *. Consistency keeps linters quiet and improves readability.

-* Local deployment
+– Local deployment-* Running from a container
+– Running from a container

967-971: Grammar: plural agreement.

“… no other packages nor tools need to be installed,” not “needs”.

-... image is needed and no other packages nor tools needs to be installed.
+... image is needed and no other packages nor tools need to be installed.

1035-1039: Avoid “able to”; use “can” for concision.

-*Lightspeed Core Stack* image is able to run LCS service
+*Lightspeed Core Stack* image can run the LCS service

1146-1155: Add language identifier to fenced code block (MD040).

-```
+```bash
 uv run llama
 …

---

`1166-1172`: **Same issue—specify language on fenced block.**

```diff
-```
+```text
 Traceback (most recent call last):
 …

---

`1332-1337`: **Repeat: add language identifier.**

```diff
-```
+```text
 INFO 2025-07-29 …

---

`1521-1524`: **Use “cannot” instead of “can not”.**

```diff
-... and the standard port mapping can not be leveraged there.
+... and the standard port mapping cannot be leveraged there.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 00d18c2 and c1023c2.

📒 Files selected for processing (1)
  • docs/getting_started.md (3 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/getting_started.md

30-30: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


31-31: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


32-32: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


33-33: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


34-34: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


35-35: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


36-36: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


37-37: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


38-38: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


39-39: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


40-40: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


41-41: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


42-42: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


43-43: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


44-44: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


45-45: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


46-46: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


67-67: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


67-67: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


981-981: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


1147-1147: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


1168-1168: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


1333-1333: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🪛 LanguageTool
docs/getting_started.md

[grammar] ~969-~969: Ensure spelling is correct
Context: ...* image is needed and no other packages nor tools needs to be installed. ### Ret...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~1037-~1037: As a shorter alternative for ‘able to’, consider using “can”.
Context: ... process Lightspeed Core Stack image is able to run LCS service that connects to Llama ...

(BE_ABLE_TO)


[style] ~1523-~1523: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...container and the standard port mapping can not be leveraged there. This configuration ...

(CAN_NOT_PREMIUM)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build-pr
🔇 Additional comments (1)
docs/getting_started.md (1)

1528-1532: Typo: “OLS image” → “LCS image”.

Readers may confuse this with “Open Shift” or something else.

-Llama Stack can be used as a library that is already part of OLS image.
+Llama Stack can be used as a library that is already part of the LCS image.

@tisnik tisnik force-pushed the lcore-247-getting-started-update- branch from c1023c2 to 5e52026 Compare August 1, 2025 08:56
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (5)
docs/getting_started.md (5)

30-42: Normalize list-indentation to silence MD007 warnings

The first-level list under “Running from container” is indented with 4 spaces instead of 2, and all nested bullets inherit that offset. GitHub renders it, but the markdownlint noise and inconsistent visual hierarchy make future edits harder.

-* [Running from container](#running-from-container)
-    * [Retrieving *Lightspeed Core Stack* image](#retrieving-lightspeed-core-stack-image)
+* [Running from container](#running-from-container)
+  * [Retrieving *Lightspeed Core Stack* image](#retrieving-lightspeed-core-stack-image)

(Apply the same 2-space rule to the subsequent sub-lists down to Line 41.)


968-971: Typo: replace “model” with “mode”

Current wording switches terminology mid-sentence:

-In the second model, the Llama Stack …
+In the second mode, the Llama Stack …

981-985: List style drifts from “*” to “-”

For consistency with earlier sections (and to quiet MD004) swap the leading dashes for asterisks or vice-versa project-wide.


1164-1170: Add language hint to fenced block (MD040)

The block shows terminal output; label it text (or bash if you want highlighting of the prompt) so fenced-block linters stop flagging it.

-``` 
+```text
   usage: llama [-h] {model,stack,download,verify-download} ...

1516-1520: Prefer absolute path when mounting the config file

Using a relative host path relies on the caller’s CWD and breaks easily in scripted environments:

-podman run -it --network host -v lightspeed-stack.yaml:/app-root/lightspeed-stack.yaml:Z …
+podman run -it --network host \
+  -v $(pwd)/lightspeed-stack.yaml:/app-root/lightspeed-stack.yaml:Z …

This small change makes the command copy-&-paste-safe.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c1023c2 and 5e52026.

📒 Files selected for processing (1)
  • docs/getting_started.md (3 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: in the lightspeed-stack project, the `user_data_dir` field in `userdatacollection` should remain as ...
Learnt from: onmete
PR: lightspeed-core/lightspeed-stack#278
File: src/models/config.py:134-134
Timestamp: 2025-07-23T14:28:45.788Z
Learning: In the lightspeed-stack project, the `user_data_dir` field in `UserDataCollection` should remain as `str` type rather than `DirectoryPath` because the directory might not exist at configuration validation time and is only created later during runtime execution.

Applied to files:

  • docs/getting_started.md
🪛 markdownlint-cli2 (0.17.2)
docs/getting_started.md

30-30: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


31-31: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


32-32: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


33-33: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


34-34: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


35-35: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


36-36: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


37-37: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


38-38: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


39-39: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


40-40: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


41-41: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


42-42: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


43-43: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


44-44: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


45-45: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


46-46: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


62-62: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


63-63: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


63-63: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


64-64: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


64-64: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


65-65: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


66-66: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


66-66: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


67-67: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


67-67: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


981-981: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


1168-1168: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🪛 LanguageTool
docs/getting_started.md

[grammar] ~969-~969: Ensure spelling is correct
Context: ...* image is needed and no other packages nor tools need to be installed. ### Retr...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~1523-~1523: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...container and the standard port mapping can not be leveraged there. This configuration ...

(CAN_NOT_PREMIUM)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: e2e_tests

@tisnik tisnik merged commit 0b0a530 into lightspeed-core:main Aug 1, 2025
17 of 18 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Aug 6, 2025
18 tasks
@coderabbitai coderabbitai bot mentioned this pull request Aug 26, 2025
15 tasks
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.

1 participant