Open Stack

Hi, Eric and Jay,

The VCPU/Disk/RAM allocation ratio are set to 0.0 by default, and resource tracker would reset it to valid values in  https://github.com/openstack/nova/blob/master/nova/objects/compute_node.py#L199.
But it looks the value is set back to 0.0 by some function(I'm not sure who does it...), so xenserver CI is broken. Any suggestion about that?
Looks libvirt works well, do they set allocation ratio in the configure file?

Thank you very much.

BR.
Naichuan Sun

-----Original Message-----
From: Naichuan Sun 
Sent: Wednesday, August 29, 2018 7:00 AM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject: RE: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

Thank you very much for the help, Bob, Jay and Eric.

Naichuan Sun

-----Original Message-----
From: Bob Ball [mailto:bob.ball at citrix.com] 
Sent: Wednesday, August 29, 2018 12:22 AM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

> Yeah, the nova.CONF cpu_allocation_ratio is being overridden to 0.0:

The default there is 0.0[1] - and the passing tempest-full from Zuul on https://review.openstack.org/#/c/590041/ has the same line when reading the config[2]:

We'll have a dig to see if we can figure out why it's not defaulting to 16 in the ComputeNode.

Thanks!

Bob

[1] https://git.openstack.org/cgit/openstack/nova/tree/nova/conf/compute.py#n386
[2] http://logs.openstack.org/41/590041/17/check/tempest-full/b3f9ddd/controller/logs/screen-n-cpu.txt.gz#_Aug_27_14_18_24_078058
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev