内部虚拟服务器场(如实时场)的 XEN 与 KVM 的状态

发布于 2024-09-15 22:47:36 字数 956 浏览 1 评论 0原文

所以我们有一个生命服务器农场,传统的东西没有虚拟化。暂时保持这种状态。我们讨论的服务器是:负载均衡器、DB master、DB Slaves (2x)、Webservers (2x)、CMS 服务器。每个场总共有 7 台服务器。

我们希望拥有一对多的相当精确的生命结构“副本”,以供内部使用。

  • 测试/登台:在上线前发现错误,如果我们不使用相同的软件配置,这些错误可能会漏掉。 调试/
  • 基准测试:与测试相同,但使用额外的工具。调试标志并与 Tetsing/Staging 隔离,以免干扰 QA。旨在更深入地了解我们的实时系统
  • 开发/实验的情况:更改系统组件、软件版本、库和配置以提高性能、开发人员效率、面向未来的系统等。

总而言之 3 个虚拟“每个农场都有 7 个虚拟服务器,整齐地隔离。

现在我知道这可以通过许多不同风格的虚拟化来实现。问题是,什么是最好的?从战略角度来看,我们不想使用 VMware 不开源的做法。看看 XEN 和 KVM,这两个开源虚拟化领域最大的参与者,我很想听到一些关于选择什么/如何选择的建议。网络似乎尚未决定。

附加信息:

  • 我们购买的服务器硬件的“使用寿命”将为 2-3 年
  • 如果这是选择虚拟化技术时要考虑的因素,我们以后有可能将系统迁移到云环境中
  • 高负载场景中服务器群/服务器的隔离非常重要。当有人在实验农场中造成严重破坏时,QA 不应该受到影响
  • 高效的资源使用当然值得赞赏(内存过量使用/共享页面?自动在硬盘驱动器上共享对象,如 linux-vserver hashify?)
  • 定期维护要求和易于管理

我知道 一切都在进行中,但如果您能告诉我您对现在选择什么的看法,因为我们希望使用该技术至少 3 年,建立并重用专有技术,我将不胜感激。也许最终我们都会意识到,XEN 或 KVM 都不是决定这场战斗的因素,而是其他因素。这方面的启示对我们现在来说更有价值。

ps:不要发火:D

so we have a life server Farm, conventional stuff not virtualized. This is to stay that way for the time beeing. The servers we are talking about are: Loadbalancer, DB master, DB Slaves (2x), Webservers (2x), CMS server. All in all 7 servers per farm.

We want to have one to many rather exact "copies" of the life structure for inhouse purposes.

  • Testing/Staging: to find bugs before live that might slip through if we do not use the same software-configuration
  • Debugging/Benchmarking: Same like testing but with additional tools. debug flags and isolated from Tetsing/Staging to not interfeer with QA. Intended to get a deeper insight into how things are on our live-systems
  • Development/Experimental: Changing System Components, Software-Versions, Libraries and Configuration to improve performance, developer effectivness, future-proofing our systems etc.

All in all 3 virtual "farms" a 7 virtual servers each, neatly isolated.

Now I know this can be achieved with many different flavors of virtualization. The Questions is, what is the best? VMware not beeing open source is nothing we would like to use on a strategic point of view. Looking at XEN and KVM, the two biggest players in open source virtualization I would love to hear some advise on what/how to select. The Web seems undecided.

Additional Info:

  • "life time" of the server hardware that we purchase will be 2-3 years
  • There is the possibility that we might migrate systems into cloud-environments later, if that is a factor to consider in the selection of the virtualization-technology
  • Isolation of Server-Farms/Servers in High-Load scenarios is important. QA should not suffer when someone wrecks havoc in the experimental farm
  • Efficent ressource usage is of course appreciated (memory overcommitment/shared pages? Automaticly Shared objects on hard-drive like the linux-vserver hashify?)
  • Regular maintenance requierements and easy of management

I know things are in the flow but I would appreciate if you would tell me your opinion on what to choose right now seeing we want to live with the technique for at least 3 years, build up and reuse know-how. Also maybe in the end we can all realize that neither one, XEN or KVM is deciding the battle but other factors. Enlightenment in that regards is even more valuable to us right now.

p.s.: and lets not flame :D

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

小巷里的女流氓 2024-09-22 22:47:36

我无法帮助您解决问题,但如果您告诉我们您需要在 7 台服务器中的每台服务器上运行什么操作系统,以及至少大约这些服务器必须响应哪些资源要求(RAM、大容量存储、 CPU、网络)。

I can't help with your query, but maybe it would help others if you told us what OS you need to run on each of the 7 servers, and at least approximately what resource requirements those servers must respond to (RAM, mass storage, CPU, network).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文