network-controller

Development

# generate protocol buffer
make pb

# make server binary
make server

# make client binary
make client

# make test (You should run this before push codes)
make test

Development with Vagrant

• Run vagrant

$ make up

• Clean vagrant VM

$ make vagrant-clean

Development with Vagrant Environment

There're at least two way to use this vagrant to develop the vortex project.

Method-one

Since the vagrant alreay install the proto-buf and golang into the ubuntu, you can use
vagrant ssh to login into the ubuntu and develop the project in that VM.
It also contains the kubectl and docker command for your development.

Method-two

If you want to develop the vortex in your local host, you can read the following instruction
to setup your docker and kubectl.

• Docker

$ export DOCKER_HOST="tcp://172.17.9.100:2376"
$ export DOCKER_TLS_VERIFY=`

Now, type the docker images and you will see the docker images in that ubuntu VM.

• Kubectl After the make up, the script will copy the kubenetes config from the VM into the tmp/config.
  You can use the following to merge that config with your own config and use the kubectl config use-context
  to switch the kubernetes cluster for your kubectl.

$ cp ~/.kube/config ~/.kube/config.bk
$ KUBECONFIG=~/.kube/config:`pwd`/tmp/admin.conf kubectl config view --flatten > tmpconfig
$ cp tmpconfig ~/.kube/config

If there're any error in the step(2), please copy the config.bk to restor your kubernets config.

Now, you can use kubectl config get-contexts to see the kubernetes-admin@kubernetes in the list and then
use the kubectl config use-context kubernetes-admin@kubernetes to manipulate the VM's kubernetes.

Usage

Run a Server

The network-controller server provide two ways to listen, TCP and Unix domain socket If you want to run as a UNIX domain socket server, you should specify a path to store the sock file and server will remove that file when server is been terminated

./server/network-controller-server -unix=/tmp/a.sock

For the TCP server, just use the IP:PORT format, for example, 0.0.0.0:50051

./server/network-controller-server -tcp=0.0.0.0:50051

Run a Client

The clinet is used for the kubernetes pod to create the veth and you can see the example yaml in example/kubernetes/*.yaml to see how to use this client.

For creating a veth for Pod, the client needs the following information

• Pod Name
• Pod Namespace
• Pod UUID
• Target Bridge Name
• The Interface Name in the container
• The server address

The first three variable can passed by the environemtn POD_NAME, POD_NAMESPACE and POD_UUID.

Bridge Name

-b or --bridge

Interface Name

-n or --nic

Server

The clinet support two way to connect to the server, TCP socket and UNIX domain socket. In the TCP mode, use the IP:PORT format to connect to TCP server

./client/network-controller-client -server=0.0.0.0:50051

Fot the UNIX domain socket mode, you should use the unix://PATH format to connect to server. Assume the path is /tmp/a.sock and you can use the following command to connect

./client/network-controller-client -server=unix:///tmp/a.sock

Following is an example of the client and you can see more use the `--help`.
```shell
./clinet/network-controller-client "-s", "unix:///tmp/grpc.sock", "-b", "br100", "-n", "eth100"