<div dir="ltr"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">John Garbutt <<a href="mailto:john@johngarbutt.com">john@johngarbutt.com</a>> 于2019年5月10日周五 下午11:28写道：<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>My main worry was to not expose host related information to end users, but noting administrators probably do what the information.</div><div><br></div><div>Looking again at the Stein spec we merged, the proposed policy rules already take care of all that.</div><div><br></div><div>I think the next step is to re-propose the spec for the Train release. I couldn't find it, but maybe you have done that already?</div><div><br></div><div>Thanks,</div><div>johnthetubaguy</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 10 May 2019 at 08:51, yonglihe <<a href="mailto:yongli.he@intel.com" target="_blank">yongli.he@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi, Everyone<br>
<br>
I synced up with Alex about comments we got at PTG. It's a long <br>
discussion, I might lost something.<br>
<br>
What i got lists below, fix me:<br>
<br>
* Remove sockets<br>
* Remove thread_policy<br>
<br>
Not sure about following comments:<br>
<br>
<br>
* Remove the cpu topology from the proposal?<br>
* Using the cpu pinning info instead of cpu set?<br>
<br>
<br>
By apply the suggestion, the API ``GET /servers/{server_id}/topology`` <br>
response gonna to be like this,<br>
<br>
and let us align what it should be:<br>
<br>
{<br>
# overall policy: TOPOLOGY % 'index<br>
"nodes":[<br>
{<br>
# Host Numa Node<br>
# control by policy TOPOLOGY % 'index:host_info'<br>
"host_numa_node": 3,<br>
# 0:5 means vcpu 0 pinning to pcpu 5<br>
# control by policy TOPOLOGY % 'index:host_info'<br>
"cpu_pinning": {0:5, 1:6},<br>
"vcpu_set": [0,1,2,3],<br>
"siblings": [[0,1],[2,3]],<br>
"memory_mb": 1024,<br>
"pagesize_kb": 4096,<br>
"cores": 2,<br>
# one core has at least one thread<br>
"threads": 2<br></blockquote></div></blockquote><div><br></div><div>I'm not sure the pagesize_kb, cores and threads. I guess Sean will have comment on them.</div><div><br></div><div>We can't get cores for threads for each numa node. The InstanceNUMACell.cpu_topology is empty only except for the dedicated cpu policy. And the Instance.cpu_topology is for the whole instance.</div><div><br></div><div>And we don't support choice page size per numa node.</div><div><br></div><div>Thanks for John and Sean's discussion in the PTG, and sorry for loss the conversation in PTG again. Actually, those are the questions Yongli is looking for. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
}<br>
...<br>
], # nodes<br>
}<br>
<br>
<br>
links:<br>
<br>
ptg:<br>
<a href="https://etherpad.openstack.org/p/nova-ptg-train" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/nova-ptg-train</a> L334<br>
<br>
spec review:<br>
<a href="https://review.opendev.org/#/c/612256/25/specs/stein/approved/show-server-numa-topology.rst" rel="noreferrer" target="_blank">https://review.opendev.org/#/c/612256/25/specs/stein/approved/show-server-numa-topology.rst</a><br>
<br>
code review:<br>
<a href="https://review.openstack.org/#/c/621476/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/621476/</a><br>
<br>
bp:<br>
<a href="https://blueprints.launchpad.net/nova/+spec/show-server-numa-topology" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/nova/+spec/show-server-numa-topology</a><br>
<br>
<br>
Regards<br>
Yongli He<br>
<br>
</blockquote></div>
</blockquote></div></div>