Spec: SR-IOV forwarder Device Plugin about cmd-forwarder-sriov HOT 2 CLOSED

Question... if we are statically configuring services to PFs... how does that link up with the real registry for the network service registry domain?

If we are configuring multiple capabilities for each PF... how does that map to the Device Plugin scheduling URL that has one capability?

from cmd-forwarder-sriov.

1. My fault - it is not a service but serviceDomain. We can make some assumption that there is some set of Endpoints over the PF labeled as serviceDomain=... and there is at least one of them registered with the service we need. If not, request will fail on discovery stage.

2. PF provides multiple token names: { service/intel, service/10G }. After client selects VF using one of the tokens, all the other tokens are marked as closed and set unhealthy for Device Plugin so it stops scheduling them to clients and reschedules clients for which those devices has been allocated.

PF = 2 * { service: intel, 10G } -> []{ 
    service/intel{1} - free,
    service/10G{2} - free,
    service/intel{3} - free,
    service/10G{4} - free
}
client-1  -allocate->  service/intel{1} - allocated
client-2  -allocate->  service/intel{3} - allocated
client-3  -allocate->  service/10G{2} - allocated
client-1    -use->    service/intel{1} - inUse, service/10G{4} - closed (first close free, then allocated)
client-3    -use->    service/10G{2} - inUse, service/intel{3} - closed (don't close inUse)
* * * reschedule client-2 to another node * * *

from cmd-forwarder-sriov.