make endpoint to honor sriov token

[pperiyasamy]

aims to use sriov device for client connection using kernel mechanism.

Fixes #281 and Depends on this PR

Signed-off-by: Periyasamy Palanisamy periyasamy.palanisamy@est.tech

[pperiyasamy]

/cc @Bolodya1997 @edwarnicke @denis-tingaikin

[Bolodya1997]

Suggested change

	var additionalFunc endpoint.Option
	var tokenServer networkservice.NetworkServiceServer
	switch len(sriovTokens) {
	case 0:
	tokenServer = null.NewServer()
	case 1:
	var tokenKey string
	for tokenKey = range sriovTokens {
	break
	}
	tokenServer = token.NewServer(tokenKey)
	default:
	log.FromContext(ctx).Fatalf("endpoint must be configured with none or only one sriov resource")
	}

[pperiyasamy]

done.

[denis-tingaikin]

@pperiyasamy Could you rebase this PR? :)

[pperiyasamy]

@pperiyasamy Could you rebase this PR? :)

done.

[denis-tingaikin]

I wondered if we should create a separate cmd repository for sriov supported endpoint.

Benefits of this directions are:

1. cmd-nse-icmp-responder still extremely simple.
2. cmd-nse-sriov-icmp-responder will use this inline in the main https://github.com/networkservicemesh/cmd-nse-icmp-responder/pull/286/files#diff-2873f79a86c0d8b3335cd7731b0ecf7dd4301eb19a82ef7a1cba7589b5252261R274-R289 that also will look more simple.

@edwarnicke What do you think?

[pperiyasamy]

I wondered if we should create a separate cmd repository for sriov supported endpoint.

Benefits of this directions are:

1. cmd-nse-icmp-responder still extremely simple.
2. cmd-nse-sriov-icmp-responder will use this inline in the main https://github.com/networkservicemesh/cmd-nse-icmp-responder/pull/286/files#diff-2873f79a86c0d8b3335cd7731b0ecf7dd4301eb19a82ef7a1cba7589b5252261R274-R289 that also will look more simple.

@edwarnicke What do you think?

@denis-tingaikin we just add this sriov token server chain element conditionally and this can be decided with pod spec.

cat > patch-nse.yaml <<EOF
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nse-kernel
spec:
  template:
    spec:
      containers:
        - name: nse
          env:
            - name: NSE_LABELS
              value: serviceDomain:worker.domain
            - name: NSE_CIDR_PREFIX
              value: 172.16.1.100/31
          resources:
            limits:
              worker.domain/100G: 1
EOF

so do you really think we need another repo just for this ?

[denis-tingaikin]

@pperiyasamy Yes, as I said #286 (comment) separate repo makes sense to me, but I'm fine if @edwarnicke agree to merge this PR :)