Expand OpenManage AI documentation with architecture and deploy context.
Keeps runtime data and secrets out of git; documents relationship to OME Cockpit.
This commit is contained in:
@@ -0,0 +1,29 @@
|
||||
# OpenManage AI — ready to use
|
||||
|
||||
URL: http://atc-portal01.dell-atc.lan:3080
|
||||
|
||||
## Login
|
||||
- Email: the address you used at signup (not the display name "admin")
|
||||
- Password: your Open WebUI password
|
||||
|
||||
## Use this model
|
||||
Select **OME Copilot** (not bare llama3-70b-gptq).
|
||||
|
||||
Ask:
|
||||
- How many iDRACs are managed and how many servers are currently connected?
|
||||
- Give me the OME fleet summary
|
||||
|
||||
Expected (live from OME REST): **42 iDRACs**, **20 connected servers**.
|
||||
|
||||
## Why not raw MCP yet?
|
||||
OME native MCP requires a `login` tool, but the appliance currently drops the MCP session after login
|
||||
(`Session not found` / odd `host.docker.internal` target).
|
||||
We therefore use the **OME Fleet** tool (REST API) for reliable demo answers.
|
||||
|
||||
MCP server entry remains in External Tools (disabled) for when OAuth/session is fixed.
|
||||
|
||||
## Ops
|
||||
```bash
|
||||
cd /home/lab/openmanage && docker compose ps
|
||||
df -h / /home
|
||||
```
|
||||
Reference in New Issue
Block a user