[{"data":1,"prerenderedAt":226},["ShallowReactive",2],{"\u002Fen\u002Fblogs\u002F20260605ubmc":3,"content-doc-\u002Fzh\u002Fblogs\u002F20260605ubmc":4,"surround-\u002Fzh\u002Fblogs\u002F20260605ubmc":219},null,{"id":5,"title":6,"author":7,"body":11,"category":209,"company":3,"coverImage":29,"date":210,"description":211,"extension":212,"location":3,"logo":3,"logoDark":3,"meta":213,"navigation":214,"path":215,"seo":216,"stem":217,"version":3,"__hash__":218},"content\u002Fzh\u002Fblogs\u002F20260605UBMC.md","打破业务边界：openUBMC 北向自接入，重构BMC创新落地模式",[8],{"name":9,"description":10},"于飞","openUBMC社区委员会委员&openUBMC开源软件专家，十五年管理软件产品化经验，先后负责鲲鹏\u002F昇腾多个代次产品的管理软件设计。",{"type":12,"value":13,"toc":194},"minimark",[14,19,23,31,47,50,53,56,60,63,66,72,75,82,88,94,100,103,105,109,112,117,120,126,129,133,136,142,145,149,152,158,161,163,167,170,172,176],[15,16,18],"h2",{"id":17},"_01-bmc-创新的最后一公里困在哪里","01 BMC 创新的“最后一公里”困在哪里？",[20,21,22],"p",{},"作为算力基础设施核心统一管理底座，BMC 向来以门槛高著称。开发者除了软件技能，还得懂服务器硬件、数据中心运维、部件适配等。这套知识体系横跨算法、软件和硬件，天然就把很多人挡在门外。伴随算力产业升级， BMC 的集成模式、交付形态与核心职责迎来全新变革：",[20,24,25],{},[26,27],"img",{"alt":28,"src":29,"title":30},"alt text","\u002Fcategory\u002Fblog\u002F20260605UBMC-boke\u002F%E5%9B%BE%E7%89%871.png","图：BMC集成和交付新模式",[32,33,34,38,41,44],"ul",{},[35,36,37],"li",{},"芯片级调优、部件故障智能诊断、硬件预加载、特性校准等系统调优职责不断下沉；",[35,39,40],{},"AI安全防护（入侵检测、合规审计、供应链可信、业务性能调优）成为刚需；",[35,42,43],{},"AIOps推动北向接口重构，端云深度联动与协作诊断成为常态；",[35,45,46],{},"Agentic BMC统一互操作规范（标准MCP、嵌入式LLM能力）也在加速落地。",[20,48,49],{},"然而，传统BMC的开发模式相对封闭、周期漫长，每一项新需求的接入都高度依赖固件团队。硬件调优、算法、安全、运维等领域的专家，即便有成熟的创新想法，也因为不掌握BMC底层开发技能，难以快速落地。",[20,51,52],{},"于是出现了一个尴尬的局面：领域专家有想法，BMC 有部署优势，但两者之间横亘着技术鸿沟。这正是BMC创新应用最难跨越的“最后一公里”。",[54,55],"hr",{},[15,57,59],{"id":58},"_02-破局之道北向自接入让bmc从封闭架构升级为开放应用平台","02 破局之道：北向自接入，让BMC从封闭架构升级为开放应用平台",[20,61,62],{},"为破解上述行业痛点，openUBMC 创新性提出北向自接入概念，重新定义BMC开发与交付模式。",[20,64,65],{},"简单来说，北向自接入是一套面向上层开发者、领域专家的开放式组件接入体系，核心宗旨为让专业的人做专业的事，剥离 BMC 底层硬件适配、编译部署等复杂工作，允许非专职开发人员独立开发、接入运维、安全、调优类功能组件，彻底打破行业技术壁垒。",[20,67,68],{},[26,69],{"alt":28,"src":70,"title":71},"\u002Fcategory\u002Fblog\u002F20260605UBMC-boke\u002F%E5%9B%BE%E7%89%872.png","图：openUBMC Service&AI agent runtime架构",[20,73,74],{},"具体而言，openUBMC Service & AI agent runtime架构提供了四项关键能力：",[20,76,77,81],{},[78,79,80],"strong",{},"硬件统一访问","：屏蔽底层差异，提供标准化温度、功耗、故障日志等监测接口，开发者无需关心IPMI\u002FRedfish协议。",[20,83,84,87],{},[78,85,86],{},"组件安全托管","：组件运行于独立沙箱，资源配额隔离，单组件崩溃不影响系统，支持热升级与原子回滚；支持AI推理引擎与特征工程库，算法专家直接调用。",[20,89,90,93],{},[78,91,92],{},"北向标准集成","：组件声明能力后，框架快速适配Redfish、SNMP、WEB等北向接口，无缝对接上层网管与云平台。",[20,95,96,99],{},[78,97,98],{},"集群协同调度","：支持组件批量部署至大规模节点，实现状态聚合、告警关联与统一配置下发。",[20,101,102],{},"北向自接入使非 BMC 开发者能够快速开发、部署创新组件，从根本上重构了 BMC 开发交付模式—从“整机厂商交付完整固件”演进为“第三方发布独立组件，按需组装”。",[54,104],{},[15,106,108],{"id":107},"_03-底层支撑三大架构创新筑牢自接入能力底座","03 底层支撑：三大架构创新，筑牢自接入能力底座",[20,110,111],{},"上述能力的实现，离不开底层架构的系统性重构。平台彻底摒弃传统单体架构，重构为微组件化开放架构，从上层组件迭代、底层硬件适配、开发工具链到生态市场完成全链路升级，为北向自接入能力提供坚实技术底座：",[113,114,116],"h3",{"id":115},"创新一微组件架构让第三方应用塞得进去跑得稳","创新一：微组件架构：让第三方应用“塞得进去、跑得稳”",[20,118,119],{},"传统 BMC 固件是单体架构，所有功能揉在一起。openUBMC 将其拆分为微组件，每个组件可以独立开发、编译、发布、升级。",[20,121,122],{},[26,123],{"alt":28,"src":124,"title":125},"\u002Fcategory\u002Fblog\u002F20260605UBMC-boke\u002F%E5%9B%BE%E7%89%873.png","图：openUBMC微组件架构",[20,127,128],{},"组件之间通过契约式接口通信，运行环境相互隔离—一个组件崩溃，不会拖垮整个 BMC。组件声明的管理能力映射到北向接口（Redfish\u002FWEB\u002FSNMP 等），开发者无需关心协议细节。",[113,130,132],{"id":131},"创新二南向驱动标准化让北向组件叫得动任何硬件","创新二：南向驱动标准化：让北向组件“叫得动”任何硬件",[20,134,135],{},"针对服务器零部件适配乱象，openUBMC 统一南向硬件接入标准，打破行业“七国八制”的适配困局。部件厂商可独立开发、发布驱动，真正实现一次开发、全域复用，交付主体从整机厂商下沉至部件厂商。",[20,137,138],{},[26,139],{"alt":28,"src":140,"title":141},"\u002Fcategory\u002Fblog\u002F20260605UBMC-boke\u002F%E5%9B%BE%E7%89%874.png","图：南向驱动交付新模式",[20,143,144],{},"算法专家聚焦数据应用，运维专家深耕高阶功能，硬件架构师专注差异化设计—各司其职，最大化释放研发价值。",[113,146,148],{"id":147},"创新三开放应用市场让组件灵活组合按需安装","创新三：开放应用市场：让组件“灵活组合，按需安装”",[20,150,151],{},"开发者将组件发布至 Conan 仓库，整机厂商或用户可根据业务需求，从应用市场中灵活挑选组件，组装出自定义的 BMC 固件。系统自动处理组件间的依赖关系，一键完成固件构建与打包，全流程自动化。",[20,153,154],{},[26,155],{"alt":28,"src":156,"title":157},"\u002Fcategory\u002Fblog\u002F20260605UBMC-boke\u002F%E5%9B%BE%E7%89%875.png","图：应用组件按需装配",[20,159,160],{},"目前社区已上架 30+ 开源组件，形成“开发-发布-组合-交付”和“开发-发布-安装”的完整闭环，让组件真正实现一次开发、灵活复用。",[54,162],{},[15,164,166],{"id":165},"_04-展望北向自接入规范进行时","04 展望：北向自接入规范进行时",[20,168,169],{},"openUBMC 技术委员会主席宋铜铃在 KADC openUBMC 分论坛上表示，北向自接入统一规范已正式启动编制，预计 2026 年底发布。依托完整的南北向标准体系建设，openUBMC 将打通全链路开发壁垒，助力每一个创新想法快速落地，推动 BMC 从传统管理平台，进化为全领域的创新舞台，为算力基础设施智能化升级筑牢坚实底座。",[54,171],{},[15,173,175],{"id":174},"欢迎关注openubmc","欢迎关注openUBMC",[32,177,178,187],{},[35,179,180,181],{},"社区官网：",[182,183,184],"a",{"href":184,"rel":185},"https:\u002F\u002Fwww.openubmc.cn",[186],"nofollow",[35,188,189,190],{},"代码仓地址：",[182,191,192],{"href":192,"rel":193},"https:\u002F\u002Fgitcode.com\u002FopenUBMC",[186],{"title":195,"searchDepth":196,"depth":196,"links":197},"",4,[198,200,201,207,208],{"id":17,"depth":199,"text":18},2,{"id":58,"depth":199,"text":59},{"id":107,"depth":199,"text":108,"children":202},[203,205,206],{"id":115,"depth":204,"text":116},3,{"id":131,"depth":204,"text":132},{"id":147,"depth":204,"text":148},{"id":165,"depth":199,"text":166},{"id":174,"depth":199,"text":175},"essentials","2026\u002F06\u002F05","openUBMC 创新性提出北向自接入概念，重新定义BMC开发与交付模式","md",{},true,"\u002Fzh\u002Fblogs\u002F20260605ubmc",{"title":6,"description":211},"zh\u002Fblogs\u002F20260605UBMC","_8dAUU3O17TcmrKTSCXlIpgQOKrnOaHQf6gLwdepVps",[220,223],{"path":221,"title":222},"\u002Fzh\u002Fblogs\u002F20250815","商业实践 | 宝德计算：基于openUBMC智能串口屏的应用实践",{"path":224,"title":225},"\u002Fzh\u002Fblogs\u002F20260723ubmc","刀片服务器健康管理破局：昆仑太科依托 openUBMC 北向自接入实现整机协同",1793275600718]