据我所知，5.6版本是短期支持的。
现在，我正在用AOS 5.5.3.1的2 8000 6节点AOS-AHV簇部署两个Oracle 12C RAC簇。
它涉及使用具有多个VDisk，网络相关配置，Linux相关调整等的音量组等...
当然，有了5.5.3.1（到目前为止，最新的GA版本在长期支持中），我没有VGLS选择，每个卷组的I/O都由一个CVM管理。
另一方面，使用AOS 5.6，我可以在每个CVM和群集上的每个节点存储中分配此负载。
这对弹性，性能和资源分配产生了重大影响。
问题是两个，我需要一些建议。
1）即使在短期支持中，也可以更好地升级到5.6？
2）是否可以使用“ vg.update load_balance_vm_attacchments”更新卷的配置“飞行”，或者我应该重新创建CHE量？（是否有第三枪或其他相关程序？）
非常感谢
向上
最好的答案乔恩
@UPX<\/user-mention>
\r\n1) If you're specifically wanting VGLB's performance capabilities (which are top notch, I was part of the team that worked on validating that features top end performance), then yes, 5.6++ is a good fit.
\r\n
\r\nIf you're worried about supportability, note that all STS releases should get at least two patches (example, 5.6, 5.6.1, 5.6.2) before that branch is moved out to another STS release, like 5.8, 5.8.1, etc. These come roughly every ~4-5 weeks, so the
\r\n
\r\nIf you're worried about catching bugs, which hey, we're a software company, every software company has bugs, especially in STS\/\"Current Release\" type train models ala us, Microsoft, Citrix, and now VMW ... you could settle on maintenance releases within a STS, like 5.6.1, 5.6.2, then wait to go to other STS releases like 5.8.1, or 5.8.2 (which at time of writing is roughly right around the corner). That should keep you pretty safe.
\r\n
\r\n2) If you haven't figured it out already, you CAN update the load_balance_vm_attachments after creation, however, you have to do it with the VM's off or VG detached from the VM(s). We did this, as to get the targets to log back in again, detach\/reattach or reboot anyhow
\r\n
\r\nI haven't personally tried that with RAC, it would be worth playing around with on a test instance to make sure you fully understand the implications there.","className":"post__content__best_answer"}">
查看原件
\r\n1) If you're specifically wanting VGLB's performance capabilities (which are top notch, I was part of the team that worked on validating that features top end performance), then yes, 5.6++ is a good fit.
\r\n
\r\nIf you're worried about supportability, note that all STS releases should get at least two patches (example, 5.6, 5.6.1, 5.6.2) before that branch is moved out to another STS release, like 5.8, 5.8.1, etc. These come roughly every ~4-5 weeks, so the
\r\n
\r\nIf you're worried about catching bugs, which hey, we're a software company, every software company has bugs, especially in STS\/\"Current Release\" type train models ala us, Microsoft, Citrix, and now VMW ... you could settle on maintenance releases within a STS, like 5.6.1, 5.6.2, then wait to go to other STS releases like 5.8.1, or 5.8.2 (which at time of writing is roughly right around the corner). That should keep you pretty safe.
\r\n
\r\n2) If you haven't figured it out already, you CAN update the load_balance_vm_attachments after creation, however, you have to do it with the VM's off or VG detached from the VM(s). We did this, as to get the targets to log back in again, detach\/reattach or reboot anyhow
\r\n
\r\nI haven't personally tried that with RAC, it would be worth playing around with on a test instance to make sure you fully understand the implications there.","className":"post__content__best_answer"}">
