Update AI Rolling Demo 1.9 with latest agentic sample updates#21
Merged
thepetk merged 7 commits intoredhat-ai-dev:ai-rolling-demo-1_9from Jan 29, 2026
Merged
Conversation
* Update logic for RAG Metadata caching Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com> * Remove .git suffix from URL Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com> * Add tests for RAG metadata regen Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com> * Fix ruff linting err Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com> * Address PR review and ty linter Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com> * Update Llama Stack run config for openai to ollama Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com> * Update Ollama Deployment to pull embedding model Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com> --------- Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com>
* Add CI/CD for App, Llama Stack Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com> * Update .github/workflows/image.yaml Co-authored-by: Theofanis Petkos <thepetk@gmail.com> * Update .github/workflows/image.yaml Co-authored-by: Theofanis Petkos <thepetk@gmail.com> * Update .github/workflows/image.yaml Co-authored-by: Theofanis Petkos <thepetk@gmail.com> --------- Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com> Co-authored-by: Theofanis Petkos <thepetk@gmail.com>
Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com>
…v#20) discovered during testing of the performance agent that the github add comment tool call was failing for the k8s top outpu. investigation confirmed that the output exceeded the max length for a github comment, so adding some truncating logic to adhere to the size limit also broke out failure processing for creating and issue from failure processing for adding comments; we should at least note the github issue creation, with an indicator if any of the comment failed finally, added a timeout to the comment tool calls, as failure/retry at the openai/LLS level lead to huge delays from the UI perspective (one instance or 1200 seconds).
Assisted-by: Claude Opus 4.5 Generated-by: Cursor Signed-off-by: Maysun J Faisal <maysunaneek@gmail.com>
Contributor
Author
Contributor
Author
gabemontero
approved these changes
Jan 28, 2026
maysunfaisal
approved these changes
Jan 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


What does this PR do?:
@gabemontero @maysunfaisal that's a rebase PR to bring the
ai-rolling-demo-1_9branch above latestmainso we can consume those changes in the Rolling Demo.Which issue(s) this PR fixes:
N/A
PR acceptance criteria:
Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened and linked to this PR, if they are not in the PR scope due to various constraints.
Tested and Verified
Documentation (READMEs, Product Docs, Blogs, Education Modules, etc.)
How to test changes / Special notes to the reviewer:
Will test and verify everything works on a test cluster of mine