[placement][ptg] Open Questions

Balázs Gibizer balazs.gibizer at ericsson.com
Mon May 6 09:14:00 UTC 2019

On Mon, May 6, 2019 at 3:23 AM, Chris Dent <cdent+os at anticdent.org> 
> A few questions we failed to resolve during the PTG that we should
> work out over the next couple of weeks.
> * There are two specs in progress related to more flexible ways to
>   filter traits:
>    * any trait in allocation candidates
> https://protect2.fireeye.com/url?k=d24a660a-8ec044e0-d24a2691-0cc47ad93e32-6536d6dba76bfa81&u=https://review.opendev.org/#/c/649992/
>    * support mixing required traits with any traits
> https://protect2.fireeye.com/url?k=dbbffb10-8735d9fa-dbbfbb8b-0cc47ad93e32-545ba4b564785811&u=https://review.opendev.org/#/c/649368/
>   Do we have pending non-placement features which depend on the
>   above being completed? I got the impression during the
>   nova-placement xproj session that maybe they were, but it's not
>   clear. Anyone willing to state one way or another?

 From the first spec:
"This is required for the case when a Neutron network maps to more than 
one physnets but the port's bandwidth request can be fulfilled from any 
physnet the port's network maps to."
So yes there is a use case that can only be supported if placement 
supports any traits in a_c query. It is to support multisegment neutron 
networks with QoS minimum bandwidth rule and with more than one segment 
mapped to physnet. A reason we did not discussed it in detail is that 
the use case was downprioritized on my side. (see 
https://etherpad.openstack.org/p/ptg-train-xproj-nova-neutron L40)

> * We had several RFE stories already in progress, and have added a
>   few more during the PTG. We have not done much in the way of
>   prioritizing these. We certainly can't do them all. Here's a link
>   to the current RFE stories in the placement group (this includes
>   placement, osc-placement and os-*).
>   https://storyboard.openstack.org/#!/worklist/594
>   I've made a simple list of those on an etherpad, please register
>   you +1 or -1 (or nothing) on each of those. Keep in mind that
>   there are several features in "Update nested provider support to
>   address train requirements" and that we've already committed to
>   them.

Did you forget to paste the etherpad link?

> Please let me know what I've forgotten.
> --
> Chris Dent                       ٩◔̯◔۶           
> https://protect2.fireeye.com/url?k=2e065f7d-728c7d97-2e061fe6-0cc47ad93e32-0c1780ffb89507f5&u=https://anticdent.org/
> freenode: cdent                                         tw: @anticdent

More information about the openstack-discuss mailing list