[RFE] Add anti_affinity_group to binding:profile

[Hongbin Lu]

In SRIOV scenario, it is a common use case that a VM has two ports and users want to have the two ports scheduling to two different PFs for redundancy.

The proposal for Neutron is to introduce a new key 'anti_affinity_group' in binding:profile. The value of 'anti_affinity_group' is a unique ID for grouping neutron ports. Nova is responsible to schedule ports that has the same 'anti-affinity_group' to different PFs.

Nova BP: https://blueprints.launchpad.net/nova/+spec/schedule-vm-nics-to-different-pf

[Pawel Suder (pasuder)]

Seems to be related to https://blueprints.launchpad.net/nova/+spec/sriov-bond

IMO should be marked as duplicated. If there is any other case which is not covered under SRIOV bond, please reply.

[Hongbin Lu (hongbin.lu)]

Actually, I am the assignee of that BP which is created for Nova. It is a cross-project effort with Neutron and this RFE is the neutron counter-part.

[Miguel Lavalle (minsel)]

It makes sense to me. Let's bring it to the drivers meeting

[Miguel Lavalle (minsel)]

This RFE was discussed and approved during today's Neutron drivers meeting

[Manjeet Singh Bhatia (manjeet-s-bhatia)]

can't we already add a key, val like we add local_link info incase of physical switch ?
we can still modify the code to assign some value to it by default, each port will have affinity =0 by default means that port want to be on its own ? for all other ids expect 0 nova can infer if they are same they belong to same group ?

[Igor D.C. (igordc)]

Quick link to the Neutron drivers meeting mentioned by Miguel: http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-01-25-14.00.log.html

[Ruijing (ruijing-guo)]

We may need to handle QoS part.

[Li Zhouzhou (lizhouzhou)]

I don't think it worked well for sriov port bonding. IMO, it only supports active-backup. Bond Mode0 (balance-rr) will set same mac in two vNic, however the vf mac isn't changed. So, the vm communication will failed.