incubator-cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lu Heng <h...@anytimechinese.com>
Subject Re: RE: 超出Host的VM
Date Thu, 19 Jul 2012 16:06:39 GMT
这方案的具体成本大概在什么规模?

如果在可接受范围内的话我们有兴趣,呵呵

还有就是这个胖节点的性能如何。

2012/7/19 Kim Goh <jggao@clustertech.com>:
>
> 对,虚拟出来了只有,就只有一个节点,也只安装一个操作系统
> 发件人: Frank Zhang
> 发送时间: 2012-07-18 02:33
> 收件人: cloudstack-users-cn; 'jggao'
> 主题: RE: RE: 超出Host的VM
> 这个‘胖节点’,对于客户看到的就只是一个VM吗?
>
>> -----Original Message-----
>> From: Kim Goh [mailto:jggao@clustertech.com]
>> Sent: Tuesday, July 17, 2012 10:19 AM
>> To: cloudstack-users-cn; cloudstack-users-cn@incubator.apache.org
>> Subject: 回复: RE: 超出Host的VM
>>
>> 其实我们的虚拟化,有两个方向,一个服务器虚拟化为若干个虚拟机来跑
>> 业务为大众所熟知和使用
>>
>> 另外一个方向就是把多个物理机器虚拟化为一个胖节点,这个其实也是已
>> 经成熟了的技术,在我所在的高性能计算领域也用的不少,最近武汉大学
>> 有一个院系就已经找我们提供过这样的整体方案支持.
>> 等我实施完这个项目,可以来和大家一起分享经验.
>> 如果使用上面我说的这种技术的支持,就技术而言,完全可以出现某个虚
>> 拟机所分配的资源大于host server cluster中最胖的节点.
>>
>> 可惜这个解决方案比较昂贵,而且底层网络仅允许使用infiniband.软件
>> license也有点小贵.
>>
>> 发件人: Frank Zhang
>> 发送时间: 2012-07-17 07:15
>> 收件人: cloudstack-users-cn@incubator.apache.org
>> 主题: RE: 超出Host的VM
>> 那没有办法了,毕竟软件是受硬件限制的
>>
>> > -----Original Message-----
>> > From: Lu Heng [mailto:h.lu@anytimechinese.com]
>> > Sent: Monday, July 16, 2012 2:36 PM
>> > To: cloudstack-users-cn@incubator.apache.org
>> > Subject: Re: 超出Host的VM
>> >
>> > 但这个会大大提高部署复杂程度,比如说我们最近一个客户的部署实
>> 例:
>> >
>> > 客户要求在美国128GB内存的数据库服务器一台,64GB的前端HTTP
>> 服
>> > 务器一台,需要冗余备份。客户在欧洲有一套物理服务器的解决方案
>> > (同样是64GB的前端网页服务器,128GB的数据库服务器)。两地使
>> > 用Any-Cast
>> >
>> > 我们在美国给客户推荐使用我们的云解决方案,给客户做的解决方案
>> 如
>> > 下:
>> > 32GB的WEB VM两台,做负载平衡。
>> > 128GB的VM一台,做数据库服务器,和欧洲的同步。
>> >
>> > 但目前的问题是,我们的HOST标准内存都是32GB,在不改动硬件的
>> 情
>> > 况下,只能调整为以下
>> > 16GB的WEB VM四台,做负载平衡。
>> > 16GB的数据库服务器8台,做负载平衡,同时和欧洲同步(负载平衡
>> +
>> > 与欧洲数据库实时同步),这个增加配置难度N倍。
>> >
>> > 而且客户的应用程序方面还要做调整,但如果我们增加HOST的内存
>> 到
>> > 144GB,我们又需要即时增加硬件投资,即使我们目前的可用内存在集
>> > 群里的,目前全部可用内存超过1000GB。
>> >
>> > 有任何的idea关于更好的解决方案嘛?
>> > On Mon, Jul 16, 2012 at 7:52 PM, Frank Zhang <Frank.Zhang@citrix.com>
>> > wrote:
>> > > 个人觉得没有希望,而且这不是将来的方向。
>> > > 单个VM超出host的资源,在非虚拟化世界里其实就类似于大型机,
>> > 单个机器拥有大量资源用于运算。
>> > > 但目前的趋势是通过软件方法将普通机器集群起来,例如分布式计
>> 算,
>> > 来达到甚至超过大型机的。
>> > >
>> > >
>> > >> -----Original Message-----
>> > >> From: Lu Heng [mailto:h.lu@anytimechinese.com]
>> > >> Sent: Monday, July 16, 2012 12:58 AM
>> > >> To: cloudstack-users-cn@incubator.apache.org
>> > >> Subject: Re: 超出Host的VM
>> > >>
>> > >> 但如果单个VM永远大不过单个HOST的话。。。大规模计算永远
>> 得
>> > 靠
>> > >> 老办法(多个服务器做平衡等等)。
>> > >>
>> > >> 未来有希望嘛。。。?
>> > >>
>> > >> On Mon, Jul 16, 2012 at 6:50 AM, Edison Su <Edison.su@citrix.com>
>> wrote:
>> > >> >
>> > >> >
>> > >> > Sent from my iPhone
>> > >> >
>> > >> > On Jul 14, 2012, at 2:13 PM, "Lu Heng" <h.lu@anytimechinese.com>
>> > wrote:
>> > >> >
>> > >> >> Hey colleagues:
>> > >> >>
>> > >> >> 我想问的是目前似乎不能让单个VM使用资源超出HOST服务器
>> 的
>> > 资
>> > >> 源。如,如果Host server是32GB
>> > >> >> RAM的话,单个VM能同时使用多个HOST server的资源吗?
>> > >> >>
>> > >> >> 如果HOST SERVER不能实现资源整合分配的话,似乎和云的概念
>> > 有些
>> > >> 不符合。
>> > >> >>
>> > >> >> 目前市面上的其他解决方案似乎都不能让单个VM使用超过
>> HOST
>> > 的
>> > >> 物理资源。
>> > >> >
>> > >> > 有个公司叫3leaf system,做的东西就跟你说的很像,把多个x86服
>> > 务器
>> > >> 整合成一个服务器,但是这个公司已经破产了。。。
>> > >> >>
>> > >> >> --
>> > >> >> --
>> > >> >> Kind regards.
>> > >> >> Lu
>> > >> >>
>> > >> >> This transmission is intended solely for the addressee(s)
shown
>> above.
>> > >> >> It may contain information that is privileged, confidential
or
>> > >> >> otherwise protected from disclosure. Any review, dissemination
>> > >> >> or use of this transmission or its contents by persons other
>> > >> >> than the intended addressee(s) is strictly prohibited. If
you
>> > >> >> have received this transmission in error, please notify this
>> > >> >> office immediately and e-mail the original at the sender's
>> > >> >> address above by replying to this message and including the
text of
>> the transmission received.
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> --
>> > >> Kind regards.
>> > >> Lu
>> > >>
>> > >> This transmission is intended solely for the addressee(s) shown above.
>> > >> It may contain information that is privileged, confidential or
>> > >> otherwise protected from disclosure. Any review, dissemination or
>> > >> use of this transmission or its contents by persons other than the
>> > >> intended addressee(s) is strictly prohibited. If you have received
>> > >> this transmission in error, please notify this office immediately
>> > >> and e-mail the original at the sender's address above by replying
>> > >> to this message and including the text of the transmission received.
>> >
>> >
>> >
>> > --
>> > --
>> > Kind regards.
>> > Lu
>> >
>> > This transmission is intended solely for the addressee(s) shown above.
>> > It may contain information that is privileged, confidential or
>> > otherwise protected from disclosure. Any review, dissemination or use
>> > of this transmission or its contents by persons other than the
>> > intended addressee(s) is strictly prohibited. If you have received
>> > this transmission in error, please notify this office immediately and
>> > e-mail the original at the sender's address above by replying to this
>> > message and including the text of the transmission received.



-- 
--
Kind regards.
Lu

This transmission is intended solely for the addressee(s) shown above.
It may contain information that is privileged, confidential or
otherwise protected from disclosure. Any review, dissemination or use
of this transmission or its contents by persons other than the
intended addressee(s) is strictly prohibited. If you have received
this transmission in error, please notify this office immediately and
e-mail the original at the sender's address above by replying to this
message and including the text of the transmission received.
Mime
View raw message