Skip to content

Commit

Permalink
docs: don't require custom build for sriov-cni
Browse files Browse the repository at this point in the history
The latest image works just fine since multus relies on checkpoint
file to extract device ids to pass to sriov-cni, so no changes in the
cni are needed.
  • Loading branch information
booxter committed Dec 4, 2018
1 parent d008f4e commit 7337f0e
Showing 1 changed file with 1 addition and 7 deletions.
8 changes: 1 addition & 7 deletions docs/sriov.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,16 +183,10 @@ EOF
$ ./cluster/kubectl.sh create -f $GOPATH/src/github.com/intel/sriov-network-device-plugin/images/sriovdp-daemonset.yaml
```

Deploy SR-IOV CNI plugin with device ID support, which allows networks to be
configured in `mode2` (networks referring to resource names instead of
configuring PCI pools themselves).
Deploy SR-IOV CNI plugin.

```
$ go get -u -d github.com/intel/sriov-cni/
$ cd $GOPATH/src/github.com/intel/sriov-cni/images
$ git checkout dev/k8s-deviceid-model
$ ./build_docker.sh
$ vi images/sriov-cni-daemonset.yaml # change to refer to local sriov-cni:latest
$ ./cluster/kubectl.sh create -f $GOPATH/src/github.com/intel/sriov-cni/images/sriov-cni-daemonset.yaml
```

Expand Down

0 comments on commit 7337f0e

Please sign in to comment.