r all users
if he want(set the topology in image property), otherwise they use the default
one(vcpu num=socket num).
2014-01-17
Wangpan
发件人：Chet Burgess
发送时间：2013-12-22 07:28
主题：Re: [openstack-dev] [Nova] Blueprint: standard specification of guest CPU
topology
收件人："OpenStack D
After reading up on the proposed design I have some concerns, primarily around
the use of image properties to represent the topology.
While I see the relationship between images and CPU topology (as referenced in
the wiki Windows licenses and its restrictions on sockets being a prime
example) i
On 12/03/2013 04:08 AM, Daniel P. Berrange wrote:
On Tue, Dec 03, 2013 at 01:47:31AM -0800, Gary Kotton wrote:
Hi,
I think that this information should be used as part of the scheduling
decision, that is hosts that are to be selected should be excluded if they
do not have the necessary resources
Sent: 03 December 2013 12:03
> To: 'Daniel P. Berrange'; OpenStack Development Mailing List (not for usage
> questions)
> Subject: RE: [openstack-dev] [Nova] Blueprint: standard specification of
> guest CPU topology
>
> Hi,
>
> I think the concept of allow
Hi,
I think the concept of allowing users to request a cpu topology, but have a few
questions / concerns:
>
> The host is exposing info about vCPU count it is able to support and the
> scheduler picks on that basis. The guest image is just declaring upper limits
> on
> topology it can support.
On 12/3/13 12:08 PM, "Daniel P. Berrange" wrote:
>On Tue, Dec 03, 2013 at 01:47:31AM -0800, Gary Kotton wrote:
>> Hi,
>> I think that this information should be used as part of the scheduling
>> decision, that is hosts that are to be selected should be excluded if
>>they
>> do not have the nece
On Mon, Dec 02, 2013 at 11:05:02PM -0800, Vui Chiap Lam wrote:
> Hi Daniel,
>
> I too found the original bp a little hard to follow, so thanks for
> writing up the wiki! I see that the wiki is now linked to the BP,
> which is great as well.
>
> The ability to express CPU topology constraints for
On Tue, Dec 03, 2013 at 01:47:31AM -0800, Gary Kotton wrote:
> Hi,
> I think that this information should be used as part of the scheduling
> decision, that is hosts that are to be selected should be excluded if they
> do not have the necessary resources available. It will be interesting to
> know
instead of best-match is necessary. It seems deciding what to
>pick other that the first item in the list requires logic similar to
>that used to arrive at the list in the first place.
>
>Cheers,
>Vui
>
>- Original Message -
>| From: "Daniel P. Berrange"
>|
,
Vui
- Original Message -
| From: "Daniel P. Berrange"
| To: openstack-dev@lists.openstack.org
| Sent: Monday, December 2, 2013 7:43:58 AM
| Subject: Re: [openstack-dev] [Nova] Blueprint: standard specification of
guest CPU topology
|
| On Tue, Nov 19, 2013 at 12:15:51PM
On Tue, Nov 19, 2013 at 12:15:51PM +, Daniel P. Berrange wrote:
> For attention of maintainers of Nova virt drivers
Anyone from Hyper-V or VMWare drivers wish to comment on this
proposal
> A while back there was a bug requesting the ability to set the CPU
> topology (sockets/cores/thread
es = 8, max_threads = 2 }
>
> Conversely if it knows that the memory size of the flavour will exceed
> one NUMA node, then it will want to force use of multiple sockets and
> discourage cores/threads
>
>preferred = { max_sockets = 64, max_cores = 2, max_threads = 1 }
{ max_sockets = 64, max_cores = 2, max_threads = 1 }
Again, I think we want to just keep it fairly dumb & simple to start
with.
> 发件人："Daniel P. Berrange"
> 发送时间：2013-11-19 20:15
> 主题：[openstack-dev] [Nova] Blueprint: standard specification of guest CPU
> topology
> 收件
y_topology):
my question is that, how/where we can get these two parameters
'preferred_topology, mandatory_topology'?
from the nova config file? or get from the hypervisor?
Thanks again.
2013-11-20
Wangpan
发件人："Daniel P. Berrange"
发送时间：2013-11-19 20:15
主题：[openstack-d
For attention of maintainers of Nova virt drivers
A while back there was a bug requesting the ability to set the CPU
topology (sockets/cores/threads) for guests explicitly
https://bugs.launchpad.net/nova/+bug/1199019
I countered that setting explicit topology doesn't play well with
booting im
15 matches
Mail list logo
