• 全部
  • 经验案例
  • 典型配置
  • 技术公告
  • FAQ
  • 漏洞说明
  • 全部
  • 全部
  • 大数据引擎
  • 知了引擎
产品线
搜索
取消
案例类型
发布者
是否解决
是否官方
时间
搜索引擎
匹配模式
高级搜索

超融合软件支持X86、arm架构混合部署吗啊啊

2小时前提问
  • 0关注
  • 0收藏,32浏览
粉丝:0人 关注:0人

问题描述:

github.com/anrancunyushi/3p3/issues/297

github.com/anrancunyushi/3p3/issues/296

github.com/anrancunyushi/3p3/issues/295

github.com/anrancunyushi/3p3/issues/294

github.com/anrancunyushi/3p3/issues/293

github.com/anrancunyushi/3p3/issues/292

github.com/anrancunyushi/3p3/issues/291

github.com/anrancunyushi/3p3/issues/290

github.com/anrancunyushi/3p3/issues/289

github.com/anrancunyushi/3p3/issues/288

github.com/anrancunyushi/3p3/issues/287

github.com/anrancunyushi/3p3/issues/286

github.com/anrancunyushi/3p3/issues/285

github.com/anrancunyushi/3p3/issues/284

github.com/anrancunyushi/3p3/issues/283

github.com/anrancunyushi/3p3/issues/282

github.com/anrancunyushi/3p3/issues/281

github.com/anrancunyushi/3p3/issues/280

github.com/anrancunyushi/3p3/issues/279

github.com/anrancunyushi/3p3/issues/278

github.com/anrancunyushi/3p3/issues/277

github.com/anrancunyushi/3p3/issues/276

github.com/anrancunyushi/3p3/issues/275

github.com/anrancunyushi/3p3/issues/274

github.com/anrancunyushi/3p3/issues/273

github.com/anrancunyushi/3p3/issues/272

github.com/anrancunyushi/3p3/issues/271

github.com/anrancunyushi/3p3/issues/270

github.com/anrancunyushi/3p3/issues/269

github.com/anrancunyushi/3p3/issues/268

github.com/anrancunyushi/3p3/issues/267

github.com/anrancunyushi/3p3/issues/266

github.com/anrancunyushi/3p3/issues/265

github.com/anrancunyushi/3p3/issues/264

github.com/anrancunyushi/3p3/issues/263

github.com/anrancunyushi/3p3/issues/262

github.com/anrancunyushi/3p3/issues/261

github.com/anrancunyushi/3p3/issues/260

github.com/anrancunyushi/3p3/issues/259

github.com/anrancunyushi/3p3/issues/258

github.com/anrancunyushi/3p3/issues/257

github.com/anrancunyushi/3p3/issues/256

github.com/anrancunyushi/3p3/issues/255

github.com/anrancunyushi/3p3/issues/254

github.com/anrancunyushi/3p3/issues/253

github.com/anrancunyushi/3p3/issues/252

github.com/anrancunyushi/3p3/issues/251

github.com/anrancunyushi/3p3/issues/250

github.com/anrancunyushi/3p3/issues/249

github.com/anrancunyushi/3p3/issues/248

github.com/anrancunyushi/3p3/issues/247

github.com/anrancunyushi/3p3/issues/246

github.com/anrancunyushi/3p3/issues/245

github.com/anrancunyushi/3p3/issues/244

github.com/anrancunyushi/3p3/issues/243

github.com/anrancunyushi/3p3/issues/242

github.com/anrancunyushi/3p3/issues/241

github.com/anrancunyushi/3p3/issues/240

github.com/anrancunyushi/3p3/issues/239

github.com/anrancunyushi/3p3/issues/238

github.com/anrancunyushi/3p3/issues/237

github.com/anrancunyushi/3p3/issues/236

github.com/anrancunyushi/3p3/issues/235

github.com/anrancunyushi/3p3/issues/234

github.com/anrancunyushi/3p3/issues/233

github.com/anrancunyushi/3p3/issues/232

github.com/anrancunyushi/3p3/issues/231

github.com/anrancunyushi/3p3/issues/230

github.com/anrancunyushi/3p3/issues/229

github.com/anrancunyushi/3p3/issues/228

github.com/anrancunyushi/3p3/issues/227

github.com/anrancunyushi/3p3/issues/226

github.com/anrancunyushi/3p3/issues/225

github.com/anrancunyushi/3p3/issues/224

github.com/anrancunyushi/3p3/issues/223

github.com/anrancunyushi/3p3/issues/222

github.com/anrancunyushi/3p3/issues/221

github.com/anrancunyushi/3p3/issues/220

github.com/anrancunyushi/3p3/issues/219

github.com/anrancunyushi/3p3/issues/218

github.com/anrancunyushi/3p3/issues/217

github.com/anrancunyushi/3p3/issues/216

github.com/anrancunyushi/3p3/issues/215

github.com/anrancunyushi/3p3/issues/214

github.com/anrancunyushi/3p3/issues/213

github.com/anrancunyushi/3p3/issues/212

github.com/anrancunyushi/3p3/issues/211

github.com/anrancunyushi/3p3/issues/210

github.com/anrancunyushi/3p3/issues/209

github.com/anrancunyushi/3p3/issues/208

github.com/anrancunyushi/3p3/issues/207

github.com/anrancunyushi/3p3/issues/206

github.com/anrancunyushi/3p3/issues/205

github.com/anrancunyushi/3p3/issues/204

github.com/anrancunyushi/3p3/issues/203

github.com/anrancunyushi/3p3/issues/202

github.com/anrancunyushi/3p3/issues/201

github.com/anrancunyushi/3p3/issues/200

github.com/anrancunyushi/3p3/issues/199

github.com/anrancunyushi/3p3/issues/198

github.com/anrancunyushi/3p3/issues/197

github.com/anrancunyushi/3p3/issues/196

github.com/anrancunyushi/3p3/issues/195

github.com/anrancunyushi/3p3/issues/194

github.com/anrancunyushi/3p3/issues/193

github.com/anrancunyushi/3p3/issues/192

github.com/anrancunyushi/3p3/issues/191

github.com/anrancunyushi/3p3/issues/190

github.com/anrancunyushi/3p3/issues/189

github.com/anrancunyushi/3p3/issues/188

github.com/anrancunyushi/3p3/issues/187

github.com/anrancunyushi/3p3/issues/186

github.com/anrancunyushi/3p3/issues/185

github.com/anrancunyushi/3p3/issues/184

github.com/anrancunyushi/3p3/issues/183

github.com/anrancunyushi/3p3/issues/182

github.com/anrancunyushi/3p3/issues/181

github.com/anrancunyushi/3p3/issues/180

github.com/anrancunyushi/3p3/issues/179

github.com/anrancunyushi/3p3/issues/178

github.com/anrancunyushi/3p3/issues/177

github.com/anrancunyushi/3p3/issues/176

github.com/anrancunyushi/3p3/issues/175

github.com/anrancunyushi/3p3/issues/174

github.com/anrancunyushi/3p3/issues/173

github.com/anrancunyushi/3p3/issues/172

github.com/anrancunyushi/3p3/issues/171

github.com/anrancunyushi/3p3/issues/170

github.com/anrancunyushi/3p3/issues/169

github.com/anrancunyushi/3p3/issues/168

github.com/anrancunyushi/3p3/issues/167

github.com/anrancunyushi/3p3/issues/166

github.com/anrancunyushi/3p3/issues/165

github.com/anrancunyushi/3p3/issues/164

github.com/anrancunyushi/3p3/issues/163

github.com/anrancunyushi/3p3/issues/162

github.com/anrancunyushi/3p3/issues/161

github.com/anrancunyushi/3p3/issues/160

github.com/anrancunyushi/3p3/issues/159

github.com/anrancunyushi/3p3/issues/158

github.com/anrancunyushi/3p3/issues/157

github.com/anrancunyushi/3p3/issues/156

github.com/anrancunyushi/3p3/issues/155

github.com/anrancunyushi/3p3/issues/154

github.com/anrancunyushi/3p3/issues/153

github.com/anrancunyushi/3p3/issues/152

github.com/anrancunyushi/3p3/issues/151

github.com/anrancunyushi/3p3/issues/150

github.com/anrancunyushi/3p3/issues/149

github.com/anrancunyushi/3p3/issues/148

github.com/anrancunyushi/3p3/issues/147

github.com/anrancunyushi/3p3/issues/146

github.com/anrancunyushi/3p3/issues/145

github.com/anrancunyushi/3p3/issues/144

github.com/anrancunyushi/3p3/issues/143

github.com/anrancunyushi/3p3/issues/142

github.com/anrancunyushi/3p3/issues/141

github.com/anrancunyushi/3p3/issues/140

github.com/anrancunyushi/3p3/issues/139

github.com/anrancunyushi/3p3/issues/138

github.com/anrancunyushi/3p3/issues/137

github.com/anrancunyushi/3p3/issues/136

github.com/anrancunyushi/3p3/issues/135

github.com/anrancunyushi/3p3/issues/134

github.com/anrancunyushi/3p3/issues/133

github.com/anrancunyushi/3p3/issues/132

github.com/anrancunyushi/3p3/issues/131

github.com/anrancunyushi/3p3/issues/130

github.com/anrancunyushi/3p3/issues/129

github.com/anrancunyushi/3p3/issues/128

github.com/anrancunyushi/3p3/issues/127

github.com/anrancunyushi/3p3/issues/126

github.com/anrancunyushi/3p3/issues/125

github.com/anrancunyushi/3p3/issues/124

github.com/anrancunyushi/3p3/issues/123

github.com/anrancunyushi/3p3/issues/122

github.com/anrancunyushi/3p3/issues/121

github.com/anrancunyushi/3p3/issues/120

github.com/anrancunyushi/3p3/issues/119

github.com/anrancunyushi/3p3/issues/118

github.com/anrancunyushi/3p3/issues/117

github.com/anrancunyushi/3p3/issues/116

github.com/anrancunyushi/3p3/issues/115

github.com/anrancunyushi/3p3/issues/114

github.com/anrancunyushi/3p3/issues/113

github.com/anrancunyushi/3p3/issues/112

github.com/anrancunyushi/3p3/issues/111

github.com/anrancunyushi/3p3/issues/110

github.com/anrancunyushi/3p3/issues/109

github.com/anrancunyushi/3p3/issues/108

github.com/anrancunyushi/3p3/issues/107

github.com/anrancunyushi/3p3/issues/106

github.com/anrancunyushi/3p3/issues/105

github.com/anrancunyushi/3p3/issues/104

github.com/anrancunyushi/3p3/issues/103

github.com/anrancunyushi/3p3/issues/102

github.com/anrancunyushi/3p3/issues/101

github.com/anrancunyushi/3p3/issues/100

github.com/anrancunyushi/3p3/issues/99

github.com/anrancunyushi/3p3/issues/98

github.com/anrancunyushi/3p3/issues/97

github.com/anrancunyushi/3p3/issues/96

github.com/anrancunyushi/3p3/issues/95

github.com/anrancunyushi/3p3/issues/94

github.com/anrancunyushi/3p3/issues/93

github.com/anrancunyushi/3p3/issues/92

github.com/anrancunyushi/3p3/issues/91

github.com/anrancunyushi/3p3/issues/90

github.com/anrancunyushi/3p3/issues/89

github.com/anrancunyushi/3p3/issues/88

github.com/anrancunyushi/3p3/issues/87

github.com/anrancunyushi/3p3/issues/86

github.com/anrancunyushi/3p3/issues/85

github.com/anrancunyushi/3p3/issues/84

github.com/anrancunyushi/3p3/issues/83

github.com/anrancunyushi/3p3/issues/82

github.com/anrancunyushi/3p3/issues/81

github.com/anrancunyushi/3p3/issues/80

github.com/anrancunyushi/3p3/issues/79

github.com/anrancunyushi/3p3/issues/78

github.com/anrancunyushi/3p3/issues/77

github.com/anrancunyushi/3p3/issues/76

github.com/anrancunyushi/3p3/issues/75

github.com/anrancunyushi/3p3/issues/74

github.com/anrancunyushi/3p3/issues/73

github.com/anrancunyushi/3p3/issues/72

github.com/anrancunyushi/3p3/issues/71

github.com/anrancunyushi/3p3/issues/70

github.com/anrancunyushi/3p3/issues/69

github.com/anrancunyushi/3p3/issues/68

github.com/anrancunyushi/3p3/issues/67

github.com/anrancunyushi/3p3/issues/66

github.com/anrancunyushi/3p3/issues/65

github.com/anrancunyushi/3p3/issues/64

github.com/anrancunyushi/3p3/issues/63

github.com/anrancunyushi/3p3/issues/62

github.com/anrancunyushi/3p3/issues/61

github.com/anrancunyushi/3p3/issues/60

github.com/anrancunyushi/3p3/issues/59

github.com/anrancunyushi/3p3/issues/58

github.com/anrancunyushi/3p3/issues/57

github.com/anrancunyushi/3p3/issues/56

github.com/anrancunyushi/3p3/issues/55

github.com/anrancunyushi/3p3/issues/54

github.com/anrancunyushi/3p3/issues/53

github.com/anrancunyushi/3p3/issues/52

github.com/anrancunyushi/3p3/issues/51

github.com/anrancunyushi/3p3/issues/50

github.com/anrancunyushi/3p3/issues/49

github.com/anrancunyushi/3p3/issues/48

github.com/anrancunyushi/3p3/issues/47

github.com/anrancunyushi/3p3/issues/46

github.com/anrancunyushi/3p3/issues/45

github.com/anrancunyushi/3p3/issues/44

github.com/anrancunyushi/3p3/issues/43

github.com/anrancunyushi/3p3/issues/42

github.com/anrancunyushi/3p3/issues/41

github.com/anrancunyushi/3p3/issues/40

github.com/anrancunyushi/3p3/issues/39

github.com/anrancunyushi/3p3/issues/38

github.com/anrancunyushi/3p3/issues/37

github.com/anrancunyushi/3p3/issues/36

github.com/anrancunyushi/3p3/issues/35

github.com/anrancunyushi/3p3/issues/34

github.com/anrancunyushi/3p3/issues/33

github.com/anrancunyushi/3p3/issues/32

github.com/anrancunyushi/3p3/issues/31

github.com/anrancunyushi/3p3/issues/30

github.com/anrancunyushi/3p3/issues/29

github.com/anrancunyushi/3p3/issues/28

github.com/anrancunyushi/3p3/issues/27

github.com/anrancunyushi/3p3/issues/26

github.com/anrancunyushi/3p3/issues/25

github.com/anrancunyushi/3p3/issues/24

github.com/anrancunyushi/3p3/issues/23

github.com/anrancunyushi/3p3/issues/22

github.com/anrancunyushi/3p3/issues/21

github.com/anrancunyushi/3p3/issues/20

github.com/anrancunyushi/3p3/issues/19

github.com/anrancunyushi/3p3/issues/18

github.com/anrancunyushi/3p3/issues/17

github.com/anrancunyushi/3p3/issues/16

github.com/anrancunyushi/3p3/issues/15

github.com/anrancunyushi/3p3/issues/14

github.com/anrancunyushi/3p3/issues/13

github.com/anrancunyushi/3p3/issues/12

github.com/anrancunyushi/3p3/issues/11

github.com/anrancunyushi/3p3/issues/10

github.com/anrancunyushi/3p3/issues/9

github.com/anrancunyushi/3p3/issues/8

github.com/anrancunyushi/3p3/issues/7

github.com/anrancunyushi/3p3/issues/6

github.com/anrancunyushi/3p3/issues/5

github.com/anrancunyushi/3p3/issues/4

github.com/anrancunyushi/3p3/issues/3

github.com/anrancunyushi/3p3/issues/2

github.com/anrancunyushi/3p3/issues/1

github.com/anrancunyushi/jjc/issues/1

github.com/anrancunyushi/i1e/issues/1

 

4 个回答
粉丝:7人 关注:0人

目前主流的超融合软件,不支持将x86和ARM架构的服务器直接部署在同一个超融合集群中。但可以通过“分开部署、统一管理”的方式来实现混合架构的运维管理。

1. 为什么不能混合部署到同一个集群?

这主要是由超融合架构的技术原理决定的,主要有以下几个硬性门槛:

  • CPU指令集不兼容:超融合的核心是计算虚拟化,运行在x86服务器上的虚拟机,其操作系统和应用都是基于x86指令集编译的,无法在ARM CPU上运行。同一个集群内,虚拟机的“热迁移”等核心功能也无法在不同指令集间实现。

  • 分布式存储层限制:超融合的分布式存储依赖于所有节点运行完全一致的底层代码来保证数据的一致性、复制和纠错。异构节点会极大增加存储软件的复杂度和不稳定风险,目前没有厂商实现这一功能。

  • 管理与运维复杂度:硬件驱动、性能优化、故障排查在异构环境下变得异常复杂,这违背了超融合简化运维的核心设计初衷。

2. 主流厂商的支持策略

虽然不能“混部”,但几乎所有主流超融合厂商都支持“双栈并行”的统一管理,即支持分别组建纯x86集群和纯ARM集群,并通过一个管理平台进行统一监控和运维。

厂商/产品支持策略描述部署/管理方式
华为超融合产品(如FusionCube)支持x86/ARM双生态,例如有基于鲲鹏ARM架构的独立产品型号。通过统一管理平台分别管理x86资源池和ARM资源池。
H3CUIS超融合软件支持X86和ARM服务器的混合部署但请注意,这里的“混合部署”是指将两类服务器分别加入不同的资源池,再通过UIS Manager进行统一管理。分开部署,统一管理。即分别建立X86资源池和ARM资源池,禁止虚拟机跨架构迁移。
深信服支持ARM和C86(海光x86)双栈并行,为客户提供“双栈一致”的云平台方案。分别部署两套资源池,通过超融合的硬件屏蔽设计,让上层业务获得一致的调用体验,下层运维实现统一管控。
超聚变超融合解决方案FusionOne HCI兼容x86、ARM、GPU、NPU等最全算力虚拟化。支持多算力集群统一管理。
宏杉科技全面兼容x86、ARM等多架构处理器及主流GPU。提供异构算力支撑。

此外,一些开源或云原生方案也提供了支持:

  • 开源方案:如Proxmox VE,支持在同一个集群中混合使用x86和ARM节点。

  • 云原生方案:如UCloudStack,其虚拟化引擎支持X86和ARM架构体系。

3. 部署建议与决策指南

在规划你的异构超融合环境时,可以参考以下建议:

  • 首选方案:独立集群 + 统一管理
    这是目前最主流、最稳妥的方案。分别组建一个纯x86集群和一个纯ARM集群。虽然资源无法在集群间弹性共享,但管理简单、性能可预测,能获得厂商的完整技术支持。

  • 技术选型建议

    • 明确工作负载:将传统的Windows应用、商业数据库部署在x86集群上;将原生为ARM编译的云原生应用、容器化工作负载部署在ARM集群上。

    • 选择生态成熟的厂商:如果你计划大规模部署ARM超融合集群,务必选择对该架构有深度优化和大量生产案例的厂商,例如华为、H3C、深信服等。

  • 一个重要的技术限制
    即使通过上层管理平台实现了统一纳管,也无法实现跨x86和ARM架构的虚拟机迁移、克隆或备份恢复。业务系统需要根据其自身的操作系统和应用兼容性,选择部署在匹配的服务器架构上

暂无评论

粉丝:2人 关注:9人

不支持。H3C UIS超融合软件目前不支持在同一集群内混合部署X86和ARM架构的服务器节点。

暂无评论

粉丝:8人 关注:0人

可共用管理WEB,集群内建一个X86 一个ARM主机池即可

但也只是方便管理而己

暂无评论

粉丝:43人 关注:1人

支持的,不同主机池就可以

暂无评论

编辑答案

你正在编辑答案

如果你要对问题或其他回答进行点评或询问,请使用评论功能。

分享扩散:

提出建议

    +

亲~登录后才可以操作哦!

确定

亲~检测到您登陆的账号未在http://hclhub.h3c.com进行注册

注册后可访问此模块

跳转hclhub

你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作

举报

×

侵犯我的权益 >
对根叔社区有害的内容 >
辱骂、歧视、挑衅等(不友善)

侵犯我的权益

×

泄露了我的隐私 >
侵犯了我企业的权益 >
抄袭了我的内容 >
诽谤我 >
辱骂、歧视、挑衅等(不友善)
骚扰我

泄露了我的隐私

×

您好,当您发现根叔知了上有泄漏您隐私的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您认为哪些内容泄露了您的隐私?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)

侵犯了我企业的权益

×

您好,当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到 pub.zhiliao@h3c.com 邮箱,我们会在审核后尽快给您答复。
  • 1. 您举报的内容是什么?(请在邮件中列出您举报的内容和链接地址)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
  • 3. 是哪家企业?(营业执照,单位登记证明等证件)
  • 4. 您与该企业的关系是?(您是企业法人或被授权人,需提供企业委托授权书)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

×

原文链接或出处

诽谤我

×

您好,当您发现根叔知了上有诽谤您的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您举报的内容以及侵犯了您什么权益?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔社区有害的内容

×

垃圾广告信息
色情、暴力、血腥等违反法律法规的内容
政治敏感
不规范转载 >
辱骂、歧视、挑衅等(不友善)
骚扰我
诱导投票

不规范转载

×

举报说明