Skip to content

Latest commit

 

History

History
103 lines (81 loc) · 3.91 KB

README.md

File metadata and controls

103 lines (81 loc) · 3.91 KB
Raw

NSM over interdomain vL3 network

Description

This example show how can be configured NSM over interdomain via vL3 network.

flowchart TB
    nse-vl3-vpp1-.-vl3-ipam
    nse-vl3-vpp2-.-vl3-ipam
    nse-vl3-vpp1---nse-vl3-vpp2  
    nsm1-.-registry
    nsm2-.-registry
    subgraph cluster1
    nsc1---nsm1---nse-vl3-vpp1
    end
    subgraph cluster2
    nsc2---nsm2---nse-vl3-vpp2
    end
    subgraph floating domain
    vl3-ipam
    registry
    end
Loading

Requires

Make sure that you have completed steps from interdomain

Run

1. Deploy

Start vl3 ipam and register vl3 network service in the floating domain.

Note: By default ipam prefix is 172.16.0.0/16 and client prefix len is 24. We also have two vl3 nses in this example. So we expect to have two vl3 addresses: 172.16.0.0 and 172.16.1.0 that should be accessible by each client.

kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=7a2735f6f8c8ed02d058c1a6a2f04846a3d88cad

Deploy a vl3-NSE and a client on the cluster1:

kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=7a2735f6f8c8ed02d058c1a6a2f04846a3d88cad

Deploy a vl3-NSE and a client on the cluster2:

kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=7a2735f6f8c8ed02d058c1a6a2f04846a3d88cad

2. Wait for clients to be ready

kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l app=alpine -n ns-floating-vl3-basic
kubectl --kubeconfig=$KUBECONFIG1 wait --for=condition=ready --timeout=1m pod -l app=alpine -n ns-floating-vl3-basic

3. Check connectivity

Get assigned IP address from the vl3-NSE for the NSC2 and ping from the remote client (NSC1):

ipAddr2=$(kubectl --kubeconfig=$KUBECONFIG2 exec -n ns-floating-vl3-basic pods/alpine -- ifconfig nsm-1)
ipAddr2=$(echo $ipAddr2 | grep -Eo 'inet addr:[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'| cut -c 11-)
kubectl --kubeconfig=$KUBECONFIG1 exec pods/alpine -n ns-floating-vl3-basic -- ping -c 4 $ipAddr2

Ping vl3 nses from cluster1:

kubectl --kubeconfig=$KUBECONFIG1 exec pods/alpine -n ns-floating-vl3-basic -- ping -c 4 172.16.0.0
kubectl --kubeconfig=$KUBECONFIG1 exec pods/alpine -n ns-floating-vl3-basic -- ping -c 4 172.16.1.0

Get assigned IP address from the vl3-NSE for the NSC1 and ping from the remote client (NSC2):

ipAddr1=$(kubectl --kubeconfig=$KUBECONFIG1 exec -n ns-floating-vl3-basic pods/alpine -- ifconfig nsm-1)
ipAddr1=$(echo $ipAddr1 | grep -Eo 'inet addr:[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'| cut -c 11-)
kubectl --kubeconfig=$KUBECONFIG2 exec pods/alpine -n ns-floating-vl3-basic -- ping -c 4 $ipAddr1

Ping vl3 nses cluster2:

kubectl --kubeconfig=$KUBECONFIG2 exec pods/alpine -n ns-floating-vl3-basic -- ping -c 4 172.16.0.0
kubectl --kubeconfig=$KUBECONFIG2 exec pods/alpine -n ns-floating-vl3-basic -- ping -c 4 172.16.1.0

Cleanup

Cleanup floating domain:

kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=7a2735f6f8c8ed02d058c1a6a2f04846a3d88cad

Cleanup cluster2 domain:

kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=7a2735f6f8c8ed02d058c1a6a2f04846a3d88cad

Cleanup cluster1 domain:

kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=7a2735f6f8c8ed02d058c1a6a2f04846a3d88cad