[ 
https://issues.apache.org/jira/browse/HDDS-15915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arafat Khan resolved HDDS-15915.
--------------------------------
    Fix Version/s: 2.3.0
       Resolution: Fixed

> Document Recon chatbot gateway provider and update JCEKS setup in admin guide
> -----------------------------------------------------------------------------
>
>                 Key: HDDS-15915
>                 URL: https://issues.apache.org/jira/browse/HDDS-15915
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Arafat Khan
>            Assignee: Arafat Khan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.3.0
>
>
> Update the Recon AI Assistant admin guide to cover:
> Gateway provider ({{{}provider=gateway{}}})
>  * New section for OpenAI-compatible gateways (LiteLLM, etc.)
>  * Document {{{}gateway.base.url{}}}, {{{}gateway.api.key{}}}, 
> {{{}gateway.models{}}}, {{default.model}}
>  * Example config; note aliases must match gateway exactly (no auto-discovery)
>  * Add {{gateway}} to supported providers table
>  * Clarify UI groups models by prefix; backend uses {{gateway}}
>  * Note: no {{anthropic.base.url}} — use {{gateway}} for Claude behind one 
> endpoint
> JCEKS (expand existing section)
>  * Add {{ozone.recon.chatbot.gateway.api.key}} alias example
>  * Document keystore password via {{HADOOP_CREDSTORE_PASSWORD}} or 
> {{hadoop.security.credstore.java-keystore-provider.password-file}}
>  * Warn: remove plaintext keys when using JCEKS (fallback exists)
>  * Verification: {{{}/chatbot/health{}}}, empty {{getconf}} for api key when 
> JCEKS-only
>  * Failure behavior: bad password → all aliases unreadable; missing key → 
> {{{}llmClientAvailable:false{}}}, {{/chat}} may 500
>  * Rotation: {{hadoop credential create/delete}} + Recon restart



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to