Attu 3.0 Beta 成为Milvus多集群运维控制台

Attu used to feel like a lightweight console for one Milvus instance. 𝗔𝘁𝘁𝘂 𝟯.𝟬 𝗕𝗲𝘁𝗮 𝗶𝘀 ...

精选理由

Milvus 的 Attu 3.0 Beta 支持多集群管理了,状态重启不丢失,挂载一个卷就行,运维更省心。

AI 摘要

Attu 3.0 Beta 从轻量级单实例控制台升级为多集群 Milvus 运维控制台。关键变化是本地状态持久化:通过数据库存储集群配置、agent 对话历史、自定义技能和 LLM 配置。用户只需挂载一个 Docker 卷(-v attu-data:/data),即可在容器重启后保留工作区。这使得 Attu 从临时工具变为可持久化使用的运维平台。

原文 · Milvus

Attu used to feel like a lightweight console for one Milvus instance. 𝗔𝘁𝘁𝘂 𝟯.𝟬 𝗕𝗲𝘁𝗮 𝗶𝘀 ...

Attu used to feel like a lightweight console for one Milvus instance. 𝗔𝘁𝘁𝘂 𝟯.𝟬 𝗕𝗲𝘁𝗮 𝗶𝘀 𝗯𝗲𝗰𝗼𝗺𝗶𝗻𝗴 𝗮𝗻 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝘀 𝗰𝗼𝗻𝘀𝗼𝗹𝗲 𝗳𝗼𝗿 𝗺𝘂𝗹𝘁𝗶-𝗰𝗹𝘂𝘀𝘁𝗲𝗿 𝗠𝗶𝗹𝘃𝘂𝘀 𝘄𝗼𝗿𝗸. 𝗢𝗻𝗲 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗮𝗸𝗲𝘀 𝘁𝗵𝗮𝘁 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹: 𝗹𝗼𝗰𝗮𝗹 𝘀𝘁𝗮𝘁𝗲 𝗻𝗼𝘄 𝘀𝘂𝗿𝘃𝗶𝘃𝗲𝘀 𝗿𝗲𝘀𝘁𝗮𝗿𝘁𝘀. In 2.x, Attu was stateless. Restart the container, and your saved connections were gone. You rebuilt the workspace from scratch. 𝗜𝗻 𝟯.𝟬, 𝗔𝘁𝘁𝘂 𝘀𝘁𝗼𝗿𝗲𝘀 𝗹𝗼𝗰𝗮𝗹 𝘀𝘁𝗮𝘁𝗲 𝗶𝗻 𝗮 𝗱𝗮𝘁𝗮𝗯𝗮𝘀𝗲, 𝗶𝗻𝗰𝗹𝘂𝗱𝗶𝗻𝗴:• cluster configs • agent conversation history • custom skills • LLM config 𝗠𝗼𝘂𝗻𝘁 𝗼𝗻𝗲 𝗗𝗼𝗰𝗸𝗲𝗿 𝘃𝗼𝗹𝘂𝗺𝗲: -𝘃 𝗮𝘁𝘁𝘂-𝗱𝗮𝘁𝗮:/𝗱𝗮𝘁𝗮 𝗮𝗻𝗱 𝘆𝗼𝘂𝗿 𝘄𝗼𝗿𝗸𝘀𝗽𝗮𝗰𝗲 𝗰𝗮𝗻 𝗻𝗼𝘄 𝗰𝗮𝗿𝗿𝘆 𝗼𝘃𝗲𝗿 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝘀𝗲𝘀𝘀𝗶𝗼𝗻𝘀, 𝘀𝘂𝗿𝘃𝗶𝘃𝗶𝗻𝗴 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝗿𝗲𝘀𝘁𝗮𝗿𝘁𝘀. It turns Attu from something you open and close into somethi milvus.io/blog/attu-3-0-… text as you work. It means you can configure your LLM provider once, build a pre-launch checklist as a reusable agent skill, and pick up a diagnostic conversation days later without re-explaining the problem. 𝗙𝘂𝗹𝗹 𝗯𝗿𝗲𝗮𝗸𝗱𝗼𝘄𝗻 𝗼𝗻 𝘁𝗵𝗲 𝗠𝗶𝗹𝘃𝘂𝘀 𝗯𝗹𝗼𝗴: https://t.co/oFAc2cIyFx 💬 0 🔄 0 ❤️ 0 👀 70 ⚡

Attu 3.0 Beta 成为Milvus多集群运维控制台 · AI 热点