The sfc-controller example in Contiv-vpp project can not work as description #29
Comments
|
@Jingzhao123 |
|
On master branch |
|
Please try to combine contiv/vpp master branch and ligato/sfc-controller dev branch. |
|
IBut please wait for PR #31 |
|
Or change the Dockerfiles as you did before for alpine versions.... |
|
@Jingzhao123 About these two I now that they work together: Actually it is only prerequisite to our aim to make work that contiv k8s sfc example |
|
@stanislav-chlebec |
|
Hi
What I tried:
1
I prepared contiv/vpp images – branch dev (included contiv/vpp#1464):
https://cloud.docker.com/u/contivvpp/repository/list?name=arm64&namespace=contivvpp&page=1
docker pull contivvpp/ui-arm64:v2.1.3-98-g1e8734b51
docker pull contivvpp/stn-arm64:v2.1.3-98-g1e8734b51
docker pull contivvpp/ksr-arm64:v2.1.3-98-g1e8734b51
docker pull contivvpp/crd-arm64:v2.1.3-98-g1e8734b51
docker pull contivvpp/cni-arm64:v2.1.3-98-g1e8734b51
docker pull contivvpp/vswitch-arm64:v2.1.3-98-g1e8734b51
docker pull contivvpp/dev-vswitch-arm64:v2.1.3-98-g1e8734b51
docker pull contivvpp/dev-vswitch-arm64:v2.1.3-98-g1e8734b51-13f5dcf9152287e06b9b5d67774b9f4b576ebaa7
docker pull contivvpp/vpp-binaries-arm64:13f5dcf9152287e06b9b5d67774b9f4b576ebaa7
2
I prepared manifest-arm64.yaml3_v2.1.3-98-g1e8734b51
(the file k8s/contiv-vpp/values-latest.yaml – were changed tags from latest to v2.1.3-98-g1e8734b51)
helm template --name my-release ../contiv-vpp -f ./values-latest.yaml,./values-arm64.yaml,./values.yaml --set vswitch.defineMemoryLimits=true --set vswitch.hugePages1giLimit=8Gi --set vswitch.memoryLimit=8Gi > manifest-arm64.yaml3
3
I fixed the configuration of /etc/vpp/contiv-vswitch.conf – added clause – on both of my servers:
socksvr {
default
}
4.
I started kubernetes with contiv/vpp network plugin – two nodes
sudo kubeadm init --token-ttl 0 --pod-network-cidr=10.1.0.0/16
...
kubectl apply -f manifest-arm64.yaml3_v2.1.3-98-g1e8734b51
5
I modified k8s/example/sfc-controller files according of my setup
6
I followed the README guide at https://github.com/contiv/vpp/tree/master/k8s/examples/sfc-controller:
set-node-labels
kubectl apply -f sfc-controller.yaml
kubectl apply -f configMaps.yaml
kubectl apply -f vnf1.yaml
kubectl apply -f vnf2.yaml
kubectl apply -f vnf3.yaml
kubectl apply -f vnf4.yaml
stanislav@contivvpp:~/contivppnetwork/vpp$ kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
contiv-crd-4lrs7 1/1 Running 0 3h51m
contiv-etcd-0 1/1 Running 0 3h51m
contiv-ksr-hkjph 1/1 Running 0 3h51m
contiv-sfc-controller-6rb4x 1/1 Running 0 72m
contiv-vswitch-sr8ck 1/1 Running 0 3h51m
contiv-vswitch-v9jsb 1/1 Running 0 3h51m
coredns-86c58d9df4-4cbgp 1/1 Running 0 11h
coredns-86c58d9df4-pp6q6 1/1 Running 0 11h
etcd-contivvpp 1/1 Running 0 11h
kube-apiserver-contivvpp 1/1 Running 0 11h
kube-controller-manager-contivvpp 1/1 Running 0 11h
kube-proxy-c68pg 1/1 Running 0 11h
kube-proxy-hcmqv 1/1 Running 0 11h
kube-scheduler-contivvpp 1/1 Running 0 11h
stanislav@contivvpp:~/contivppnetwork/vpp$
7
I had an issue when the vnfX pods were pending
I had to issue commands
kubectl label nodes contivvpp role=affinity --overwrite=true
kubectl label nodes vppagent role=no-affinity --overwrite=true
to fix this
8
In spite of this the vnf pods are crashing
stanislav@contivvpp:~/contivppnetwork/vpp$ kubectl get pods
NAME READY STATUS RESTARTS AGE
vnf1 0/1 Pending 0 45m
vnf2 0/1 CrashLoopBackOff 13 45m
vnf3 0/1 Pending 0 45m
vnf4 0/1 CrashLoopBackOff 13 44m
stanislav@contivvpp:~/contivppnetwork/vpp$
stanislav@contivvpp:~/contivppnetwork/vpp$ cat /etc/vpp/contiv-vswitch.conf
unix {
nodaemon
cli-listen /run/vpp/cli.sock
cli-no-pager
coredump-size unlimited
full-coredump
}
nat {
endpoint-dependent
translation hash buckets 1048576
translation hash memory 268435456
user hash buckets 1024
max translations per user 10000
}
api-trace {
on
nitems 500
}
dpdk {
dev 0002:01:00.2
uio-driver vfio-pci
}
acl-plugin {
use tuple merge 0
}
socksvr {
default
}
stanislav@contivvpp:~/contivppnetwork/vpp$
stanislav@contivvpp:~/contivppnetwork/vpp$ cat k8s/contiv-vpp/values-latest.yaml
---
vswitch:
image:
tag: v2.1.3-98-g1e8734b51
cni:
image:
tag: v2.1.3-98-g1e8734b51
ksr:
image:
tag: v2.1.3-98-g1e8734b51
crd:
image:
tag: v2.1.3-98-g1e8734b51
stanislav@contivvpp:~/contivppnetwork/vpp$
From: Jingzhao123 <[email protected]>
Sent: Monday, March 18, 2019 10:54 AM
To: ligato/sfc-controller <[email protected]>
Cc: Stanislav Chlebec <[email protected]>; Mention <[email protected]>
Subject: Re: [ligato/sfc-controller] The sfc-controller example in Contiv-vpp project can not work as description (#29)
@stanislav-chlebec<https://github.com/stanislav-chlebec>
Hi
Is it OK on dev version? Actually, i still do not verify it on dev version. When i using the latest version, i found that the vnf pod can not create memif interface. Is the issue same with yours?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#29 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Aek0u_WZ-WBsX2FGtXbm9KL04GpBYT9tks5vX2IggaJpZM4bYmlv>.
|
|
Used ligato/sfc-controller-arm64 built on dev branch
Used ligato/vpp-agent-arm64 built on dev branch
From: Jingzhao123 <[email protected]>
Sent: Monday, March 18, 2019 10:54 AM
To: ligato/sfc-controller <[email protected]>
Cc: Stanislav Chlebec <[email protected]>; Mention <[email protected]>
Subject: Re: [ligato/sfc-controller] The sfc-controller example in Contiv-vpp project can not work as description (#29)
@stanislav-chlebec<https://github.com/stanislav-chlebec>
Hi
Is it OK on dev version? Actually, i still do not verify it on dev version. When i using the latest version, i found that the vnf pod can not create memif interface. Is the issue same with yours?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#29 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Aek0u_WZ-WBsX2FGtXbm9KL04GpBYT9tks5vX2IggaJpZM4bYmlv>.
|
|
The reasom why vxlan tunnels are not created is probably here: |
|
FYI By a correct one: Corrected errors "dst_network":"192.168.40.31" should be "dst_network":"192.168.40.31/32" |
This was referenced Apr 2, 2019
|
I have the same problem as @Jingzhao123. Have you please any suggestions because i have changed the sfc-controller.yaml as indicated in #33 but no good result |
|
Is there any solution to fix the problem in the SFC controller source. I have done the manual solution of @stanislav-chlebec but i have always long vxlan names and the VNFs crash (CrashLoopBackOff). Which file from the SFC source code is about the generated VXlan names please? |
|
Hi, |
|
SFC controller demo is now superseded by SFC functionality built into Contiv-VPP CNI itself. Still work in progress, but already does something. Take a look at https://github.com/contiv/vpp/tree/master/k8s/examples/sfc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am doing some work about sfc-controller on K8s with Contiv-vpp. I deploy a sfc-controller environment for testing based on following instructions https://github.com/contiv/vpp/tree/master/k8s/examples/sfc-controller. But it can not work. Is there anyone can help me about it?
Firstly, i do not find any new created vxlan tunnel on host network
Secondly, I also find that there is no memif interface created in vnf pod.
The text was updated successfully, but these errors were encountered: