yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #41024
[Bug 1515490] [NEW] It must be less than cores per socket of host,when specify the VM ’s single numa_node vcpus is odd number(cpu_policy=dedicated)
Public bug reported:
1. version
kilo 2015.1.0
2. Relevant log files:
nova-scheduler.log
2015-11-12 12:56:50.472 27408 INFO nova.filters [req-70882f90-d48e-4ca0-8b09-b15a82df792f 9c67877ee37b47e989148a776862c7b8 40fc54dc632c4a02b44bf31d7ff15c82 - - -] Filter NUMATopologyFilter returned 0 hosts for instance 890d0215-5033-44ac-bb8c-3b90ce0db6a4
3. Reproduce steps:
3.1 environment described
I have one compute node with 32 cpus,
It’s numa_topology is as follows:
2 sockets * 8 cores * 2 thread = 32
this mean this host have 2 numa_node,and have 16 cpu on per numa_node
3.2 create a flavor with 30 cpus:
[root@nail-SBCJ-5-3-13 nova(keystone_admin)]# nova flavor-show 30cpu
+----------------------------+-------+
| Property | Value |
+----------------------------+-------+
| OS-FLV-DISABLED:disabled | False |
| OS-FLV-EXT-DATA:ephemeral | 0 |
| disk | 1 |
| extra_specs | {} |
| id | 7 |
| name | 30cpu |
| os-flavor-access:is_public | True |
| ram | 512 |
| rxtx_factor | 1.0 |
| swap | |
| vcpus | 30 |
+----------------------------+-------+
3.3 Set the numa properties as follows(numa_node1:15 vcpu numa_node2:15 vcpu),then,create vm use the flavor
nova flavor-key 30cpu set hw:numa_nodes=2 hw:numa_cpus.0="0-14" hw:numa_mem.0=256 hw:numa_cpus.1="15-29" hw:numa_mem.1=256 hw:cpu_policy=dedicated
Expected result: create success
Actual result : create failed
Error log: ----> 2. Relevant log files
3.4 Set the numa properties as follows again(numa_node1: 14 vcpu numa_node2: 16 vcpu),then,create vm use the flavor
nova flavor-key 30cpu set hw:numa_nodes=2 hw:numa_cpus.0="0-13" hw:numa_mem.0=256 hw:numa_cpus.1="14-29" hw:numa_mem.1=256 hw:cpu_policy=dedicated
Expected result: create success
Actual result : create success
3.5 create another flavor with 14 cpus(numa_node1:7 vcpu numa_node2:7 vcpu),Set the numa properties as follows,then,create vm use the flavor
nova flavor-key 14cpu set hw:numa_nodes=2 hw:numa_cpus.0="0-6" hw:numa_mem.0=256 hw:numa_cpus.1="7-13" hw:numa_mem.1=256 hw:cpu_policy=dedicated
Expected result: create success
Actual result : create success
OR (numa_node1:6 vcpu numa_node2:8 vcpu)
nova flavor-key 14cpu set hw:numa_nodes=2 hw:numa_cpus.0="0-5" hw:numa_mem.0=256 hw:numa_cpus.1="6-13" hw:numa_mem.1=256 hw:cpu_policy=dedicated
Expected result: create success
Actual result : create success
4
The above results show that:
It must be less than cores per socket of host,when specify the VM ’s single numa_node vcpus is odd number (when cpu pining policy = dedicated)。
but if the number is even number does not exist this kind of situation。
I don't think it is reasonable
** Affects: nova
Importance: Undecided
Status: New
** Tags: numa
** Summary changed:
- It must be less than cores per socket of host,when specify the VM ’s single numa_node vcpus is odd number
+ It must be less than cores per socket of host,when specify the VM ’s single numa_node vcpus is odd number(cpu_policy=dedicated)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1515490
Title:
It must be less than cores per socket of host,when specify the VM ’s
single numa_node vcpus is odd number(cpu_policy=dedicated)
Status in OpenStack Compute (nova):
New
Bug description:
1. version
kilo 2015.1.0
2. Relevant log files:
nova-scheduler.log
2015-11-12 12:56:50.472 27408 INFO nova.filters [req-70882f90-d48e-4ca0-8b09-b15a82df792f 9c67877ee37b47e989148a776862c7b8 40fc54dc632c4a02b44bf31d7ff15c82 - - -] Filter NUMATopologyFilter returned 0 hosts for instance 890d0215-5033-44ac-bb8c-3b90ce0db6a4
3. Reproduce steps:
3.1 environment described
I have one compute node with 32 cpus,
It’s numa_topology is as follows:
2 sockets * 8 cores * 2 thread = 32
this mean this host have 2 numa_node,and have 16 cpu on per numa_node
3.2 create a flavor with 30 cpus:
[root@nail-SBCJ-5-3-13 nova(keystone_admin)]# nova flavor-show 30cpu
+----------------------------+-------+
| Property | Value |
+----------------------------+-------+
| OS-FLV-DISABLED:disabled | False |
| OS-FLV-EXT-DATA:ephemeral | 0 |
| disk | 1 |
| extra_specs | {} |
| id | 7 |
| name | 30cpu |
| os-flavor-access:is_public | True |
| ram | 512 |
| rxtx_factor | 1.0 |
| swap | |
| vcpus | 30 |
+----------------------------+-------+
3.3 Set the numa properties as follows(numa_node1:15 vcpu numa_node2:15 vcpu),then,create vm use the flavor
nova flavor-key 30cpu set hw:numa_nodes=2 hw:numa_cpus.0="0-14" hw:numa_mem.0=256 hw:numa_cpus.1="15-29" hw:numa_mem.1=256 hw:cpu_policy=dedicated
Expected result: create success
Actual result : create failed
Error log: ----> 2. Relevant log files
3.4 Set the numa properties as follows again(numa_node1: 14 vcpu numa_node2: 16 vcpu),then,create vm use the flavor
nova flavor-key 30cpu set hw:numa_nodes=2 hw:numa_cpus.0="0-13" hw:numa_mem.0=256 hw:numa_cpus.1="14-29" hw:numa_mem.1=256 hw:cpu_policy=dedicated
Expected result: create success
Actual result : create success
3.5 create another flavor with 14 cpus(numa_node1:7 vcpu numa_node2:7 vcpu),Set the numa properties as follows,then,create vm use the flavor
nova flavor-key 14cpu set hw:numa_nodes=2 hw:numa_cpus.0="0-6" hw:numa_mem.0=256 hw:numa_cpus.1="7-13" hw:numa_mem.1=256 hw:cpu_policy=dedicated
Expected result: create success
Actual result : create success
OR (numa_node1:6 vcpu numa_node2:8 vcpu)
nova flavor-key 14cpu set hw:numa_nodes=2 hw:numa_cpus.0="0-5" hw:numa_mem.0=256 hw:numa_cpus.1="6-13" hw:numa_mem.1=256 hw:cpu_policy=dedicated
Expected result: create success
Actual result : create success
4
The above results show that:
It must be less than cores per socket of host,when specify the VM ’s single numa_node vcpus is odd number (when cpu pining policy = dedicated)。
but if the number is even number does not exist this kind of situation。
I don't think it is reasonable
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1515490/+subscriptions
Follow ups