2018-04-24 20:53 GMT+08:00 Eric Fried <openstack at fried.cc>: > > The problem isn't just checking the traits in the nested resource > > provider. We also need to ensure the trait in the exactly same child > > resource provider. > > No, we can't get "granular" with image traits. We accepted this as a > limitation for the spawn aspect of this spec [1], for all the same > reasons [2]. And by the time we've spawned the instance, we've lost the > information about which granular request groups (from the flavor) were > satisfied by which resources - retrofitting that information from a new > image would be even harder. So we need to accept the same limitation > for rebuild. > > [1] "Due to the difficulty of attempting to reconcile granular request > groups between an image and a flavor, only the (un-numbered) trait group > is supported. The traits listed there are merged with those of the > un-numbered request group from the flavor." > (http://specs.openstack.org/openstack/nova-specs/specs/ > rocky/approved/glance-image-traits.html#proposed-change) > [2] > https://review.openstack.org/#/c/554305/2/specs/rocky/ > approved/glance-image-traits.rst at 86 Why we can return a RP which has a specific trait but we won't consume any resources on it? If the case is that we request two VFs, and this two VFs have different required traits, then that should be granular request. > > > __________________________________ > ________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180424/061c9901/attachment.html>