Open Stack

Thanks, Eric and Chris.

Can this scheme address this use case?
     I have a set of compute hosts, each with several NICs of type T. Each NIC has a set of PFs: PF1, PF2, .... Each PF is a resource provider, and each has a separate custom RC: CUSTOM_RC_PF1, CUSTOM_RC_PF2, ... . The VFs are inventories of the associated PF's RC. Provider networks etc. are traits on that PF. The use case is to schedule a VM with several Neutron ports coming from the same NIC card and tied to specific networks.

Let us say we (somehow) translate this to a set of request groups like this:
    resources_T1:CUSTOM_RC_PF1 = 2  # Note: T is the NIC name, and we are asking for VFs as resources.
    traits_T1:CUSTOM_TRAIT_MYNET1 = required
    resources_T2:CUSTOM_RC_PF2 = 1
    traits_T2:CUSTOM_TRAIT_MYNET2 = required
    "same_subtree=%s" %  ','.join(suffix for suffix in all_suffixes if suffix.startswith('T'))

Will this ensure that all allocations come from the same NIC card? Do I have to create a 'resourceless RP' for the NIC card that contains the individual PF RPs as children nodes?

P.S.: Ignore the comments I added to https://storyboard.openstack.org/#!/story/2005575#comment-122255. 

Regards,
Sundar

> -----Original Message-----
> From: Eric Fried <openstack at fried.cc>
> Sent: Saturday, May 4, 2019 3:57 PM
> To: openstack-discuss at lists.openstack.org
> Subject: Re: [placement][nova][ptg] resource provider affinity
> 
> For those of you following along at home, we had a design session a couple of
> hours ago and hammered out the broad strokes of this work, including rough
> prioritization of the various pieces. Chris has updated the story [1] with a
> couple of notes; expect details and specs to emerge therefrom.
> 
> efried
> 
> [1] https://storyboard.openstack.org/#!/story/2005575