<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-02-11 0:10 GMT+08:00 Ed Leafe <span dir="ltr"><<a href="mailto:ed@leafe.com" target="_blank">ed@leafe.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Your regular reporter, Chris Dent, is on PTO today, so I'm filling in. I'll be brief.<br>
<br>
After the flurry of activity to get as much in before the Ocata RCs, this past week was relatively calm. Work continued on the patch to have Ironic resources tracked as, well, individual entities instead of pseudo-VMs, and with a little more clarity, should be ready to merge soon.<br>
<br>
<a href="https://review.openstack.org/#/c/404472/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/404472/</a><br>
<br>
The patch series to add the concept of nested resource providers is moving forward a bit more slowly. Nested RPs allow for modeling of complex resources, such as a compute node that contains PCI devices, each of which has multiple physical and virtual functions. The series starts here:<br>
<br>
<a href="https://review.openstack.org/#/c/415920/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/415920/</a><br>
<br>
We largely ignored traits, which represent the qualitative part of a resource, and focused on the quantitative side during Ocata. With Pike development now open, we look to begin discussing and developing the traits work in more detail. The spec for traits is here:<br>
<br>
<a href="https://review.openstack.org/#/c/345138/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/345138/</a><br>
<br>
…and the series of POC code starts with:<br>
<br>
<a href="https://review.openstack.org/#/c/377381/9" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/377381/9</a></blockquote><div><br></div><div>Ed, thanks for summary! I will add comments for the PoC. I hope that can help people to understand what is about easily:</div><div><br></div><div>The first patch <a href="https://review.openstack.org/#/c/377381/9" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/377381/9</a> is about os_traits library, that is clone from <a href="https://github.com/jaypipes/os-traits" style="font-family:calibri;font-size:11pt">https://github.com/jaypipes/os-traits</a> which created by Jay. I just put it in the nova tree for implement the PoC.</div><div><br></div><div>The Traits API starts from the second patch <a href="https://review.openstack.org/#/c/376198/" style="font-family:calibri;font-size:11pt">https://review.openstack.org/#/c/376198/</a><span style="font-family:calibri;font-size:11pt"> </span> and the last one is <br>
<a href="https://review.openstack.org/#/c/376202" style="font-family:calibri;font-size:11pt">https://review.openstack.org/#/c/376202</a>. It is all about the data model and the API implement. The new added API endpoints are '/traits' and '/resource_providers/{rp_uuid}/traits'.</div><div><br></div><div>The client of Traits API is <br>
<a href="https://review.openstack.org/#/c/417288" style="font-family:calibri;font-size:11pt">https://review.openstack.org/#/c/417288</a>. It implements that the ResourceTracker reports the CPU features as traits to the placement service by Traits API.</div><div><br></div><div>The last one <a href="https://review.openstack.org/#/c/429364" style="font-family:calibri;font-size:11pt">https://review.openstack.org/#/c/429364</a> is for getting a specific list resource providers. The patch is based on Sylvain's patch <a href="https://review.openstack.org/#/c/392569" style="font-family:calibri;font-size:11pt">https://review.openstack.org/#/c/392569</a>. It adds two new filters 'required_traits' and 'preferred_traits'. Then you can a list of RPs which match the requirement of resources and traits by the request 'GET /resource_provider?resources=.....&required_traits=...&preferred_traits=....'. (The API layer patch will be submitted soon)</div><div><br></div><div>Thanks</div><div>Alex</div><div><br>
<br>
We've also begun planning for the discussions at the PTG around what our goals for Pike will be. I'm sure that there will a summary of those discussions in one of these emails after the PTG.<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
<br>
-- Ed Leafe<br>
<br>
<br>
<br>
<br>
<br>
</font></span><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></div></div><br></div></div>