<html><body><p><font size="2">not sure whether it will helpful , FYI</font><br><br><a href="https://developer.openstack.org/api-ref/placement/"><font size="2">https://developer.openstack.org/api-ref/placement/</font></a><br><br><font color="#333333" face="Segoe UI">The primary differences between Nova’s host aggregates and placement aggregates are the following:</font><ul><ul type="disc"><li><font color="#333333" face="Segoe UI">In Nova, a host aggregate associates a </font><i><font color="#333333" face="Segoe UI">nova-compute service</font></i><font color="#333333" face="Segoe UI"> with other nova-compute services. Placement aggregates are not specific to a nova-compute service and are, in fact, not compute-specific at all. A resource provider in the Placement API is generic, and placement aggregates are simply groups of generic resource providers. This is an important difference especially for Ironic, which when used with Nova, has many Ironic baremetal nodes attached to a single nova-compute service. In the Placement API, each Ironic baremetal node is its own resource provider and can therefore be associated to other Ironic baremetal nodes via a placement aggregate association.</font><li><font color="#333333" face="Segoe UI">In Nova, a host aggregate may have </font><i><font color="#333333" face="Segoe UI">metadata</font></i><font color="#333333" face="Segoe UI"> key/value pairs attached to it. All nova-compute services associated with a Nova host aggregate share the same metadata. Placement aggregates have no such metadata because placement aggregates </font><i><font color="#333333" face="Segoe UI">only</font></i><font color="#333333" face="Segoe UI"> represent the grouping of resource providers. In the Placement API, resource providers are individually decorated with </font><i><font color="#333333" face="Segoe UI">traits</font></i><font color="#333333" face="Segoe UI"> that provide qualitative information about the resource provider.</font><li><font color="#333333" face="Segoe UI">In Nova, a host aggregate dictates the </font><i><font color="#333333" face="Segoe UI">availability zone</font></i><font color="#333333" face="Segoe UI"> within which one or more nova-compute services reside. While placement aggregates may be used to </font><i><font color="#333333" face="Segoe UI">model</font></i><font color="#333333" face="Segoe UI"> availability zones, they have no inherent concept thereof.</font></ul></ul><br><font size="2">Best Regards! <br><br>Kevin (Chen) Ji 纪 晨<br><br>Engineer, zVM Development, CSTL<br>Notes: Chen CH Ji/China/IBM@IBMCN Internet: jichenjc@cn.ibm.com<br>Phone: +86-10-82451493<br>Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC </font><br><br><img width="16" height="16" src="cid:1__=8FBB080BDF847A038f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for Jeffrey Zhang ---05/25/2018 11:34:59 AM---Recently, i am trying to implement a function which aggrega"><font size="2" color="#424282">Jeffrey Zhang ---05/25/2018 11:34:59 AM---Recently, i am trying to implement a function which aggregate nova hypervisors</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Jeffrey Zhang <zhang.lei.fly@gmail.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">OpenStack Development Mailing List <openstack-dev@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">05/25/2018 11:34 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[openstack-dev] [nova] nova aggregate and nova placement api aggregate</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font face="Arial">Recently, i am trying to implement a function which aggregate nova hypervisors</font><br><font face="Arial">rather than nova compute host. But seems nova only aggregate nova-compute host. </font><br><br><font face="Arial">On the other hand, since Ocata, nova depends on placement api which supports</font><br><font face="Arial">aggregating resource providers. But nova-scheduler doesn't use this feature</font><br><font face="Arial">now.</font><br><br><font face="Arial">So is there any better way to solve such issue? and is there any plan which</font><br><font face="Arial">make nova legacy aggregate and placement api aggregate cloud work together?</font><br><br><br>-- <br><font size="2" face="Arial">Regards,</font><br><font size="2" face="Arial">Jeffrey Zhang</font><br><font size="2" face="Arial">Blog: </font><a href="http://xcodest.me/" target="_blank"><u><font size="2" color="#0000FF" face="Arial">http://xcodest.me</font></u></a><tt><font size="2">__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br></font></tt><br><br><BR>
</body></html>