nsm v1.2rc1 uplift

[zolug]

closes: #140

xcluster install:

>xc mkcdrom private-reg meridio; xc starts --nets_vm=0,1,2 --nvm=2 --mem=4096 --smp=4

For Identity Template Based Workload Registration:
>kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire?ref=v1.2.0-rc.1
To allow Service Account Based Workload Registration (deprecated):
>kubectl apply -k Meridio/docs/demo/deployments/spire

>helm install Meridio/docs/demo/deployments/xcluster/ovl/meridio/helm/gateway --generate-name --set masterItf=eth1,tgMasterItf=eth2 --create-namespace --namespace tg-trench-a
>helm install Meridio/docs/demo/deployments/nsm --generate-name --create-namespace --namespace nsm
>helm install Meridio/deployments/helm/ --generate-name --set trench.name=trench-a --set vlan.interface=eth1,vlan.id=100 --set ipFamily=dualstack \
--set nsm.namespace=nsm,nsm.registryService=nsm-registry-svc
(change gateway settings: >kc edit cm meridio-configuration-trench-a)
>helm install Meridio/examples/target/helm/ --generate-name --namespace default --set applicationName=target-a --set default.trench.name=trench-a

Notes:
-https://github.com/Nordix/nsm-test/tree/master/ovl/nsm-ovs#the-virtio-cksum-problem
(ovl/meridio makes the kernel calculate checksum on workers running gateways e.g. vm-201,202)
-Through ovl/meridio promisc mode is enabled for interfaces on the worker nodes used
by vpp-forwarder (including VLAN master interfaces) to allow proper L2 address resolution
-The device selector for vpp-forwarder has interface -> label mapping configured for eth0,
eth1, eth2, eth3 (to be used by VLAN NSE). (Refer to ConfigMap device-selector)
-VLAN NSE must be able to connect NSM registry directly to provide the remote VLAN functionality:
        -VLAN NSE listens on TCP rather than Unix socket (probing is affected)
        -K8s namespace where NSM is running must be provided as part of the config
-VLAN NSC and NSE images must be compatible with the deployed NSM version.
-VLAN NSE image must contain grpc_health_probe binary for probing.
-NSM interface names:
        -Name of the external VLAN interface in FE is "ext-vlan.[vlan-id]"
        -Target NSC interface name is "nsc"
        -Rest of the NSM interfaces are named by NSM based on the NSM Service Name
        and NSM Connection ID
        (https://github.com/networkservicemesh/sdk/blob/129dfffd3ca917dc3d0e10abf490a39408d05755/pkg/networkservice/common/mechanisms/kernel/utils.go#L29)

[zolug]

/reverify

[LionelJouin]

If no longer needed, maybe "docs/demo/deployments/nsm-vlan" could be removed

[LionelJouin]

I get this error with Helm 3.7.0:

2022-02-10T13:15:08.797528164Z stderr F Feb 10 13:15:08.797�[31m [FATA] [cmd:[/bin/app]] �[0merror processing rootConf from env: envconfig.Process: assigning NSM_NETWORK_SERVICES to NetworkServices: converting 'kernel://external-vlan.trench-a.red/ext-vlan.%!s(float64=100)' to type []url.URL. details: parse "kernel://external-vlan.trench-a.red/ext-vlan.%!s(float64=100)": invalid URL escape "%!s"

To fix it, replace .Values.vlan.id with (.Values.vlan.id | int)

[LionelJouin]

might be possible to remove the check if expiration time is nil, since it has been introduced when the deleted property was not part of the API.
networkservicemesh/api#81

[estinfra]

FOSS Introduction is done. Please check the logs.