From 3917af4a4ed464c4f16a7d4527aca1ecc52c8660 Mon Sep 17 00:00:00 2001 From: Martin Borg Date: Mon, 26 Aug 2019 15:01:34 +0200 Subject: Example Use-cases: Update Clavister example - Replace bundles with VNF images and update onboarding/instantiation instructions - Add cloud-init configurations - Remove descriptions of how to navigate uCPE manager GUI - Remove images that are incorrect Change-Id: I6028b396a8e698bf62ff8aa16feeef8dad6c9403 Signed-off-by: Martin Borg --- .../doc/clav_vnf_examples.xml | 374 ++++++++++++--------- 1 file changed, 206 insertions(+), 168 deletions(-) (limited to 'doc') diff --git a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml index f8ac57d..a4f011f 100644 --- a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml +++ b/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml @@ -8,34 +8,44 @@
Prerequisites - The following files are needed for this example use case: + The following files provided with your Enea NFV Access release are + needed for this example use case: FIXME - These filenames may need + to be updated - enea-nfv-access-vnf-qemux86-64.qcow2. This - image is provided with your release. + enea-nfv-access-vnf-qemux86-64.wic.qcow2 - clavister-cos-stream-<version>-virtual-x64-generic.qcow2. - This image is provided with your release. + clavister-cos-stream-<version>-virtual-x64-generic.qcow2 - License for the Clavister VNF (needed as Cloud-Init content in - the Cloud-Init tab). This file is available through the VNF - provider. + clavister_cloudinit.cfg + + + + enea-vnf-iperf-client.cfg + + + + enea-vnf-iperf-server.cfg
- Clavister VNF using Open vSwitch Bridge + Clavister VNF using an Open vSwitch Bridge - In this use-case, uCPE device 1 will run the Clavister VNF and an - Open vSwitch bridge, while uCPE device 2 will run two iPerf VNFs. + In this use-case, uCPE device 1 runs the Clavister VNF, while uCPE + device 2 runs two Enea NFV Access VNFs with iPerf client and server + applications. The uCPE devices are connected using OVS-DPDK bridges. + -
+ FIXME: New image needed + +
Clavister VNF using Open vSwitch Bridge Overview @@ -49,38 +59,21 @@
Use-case Setup - Configuring Network Interfaces on uCPE - devices: + Network Configuration: - From the uCPE Manager select uCPE device 1, then access - Configuration -> - OpenVSwitch -> Host - Interfaces -> Add. - - - - Select the network interface that will be used to connect to - uCPE device 2. Configure it for DPDK, and click - Create to send the configuration to that uCPE - device. - - - - Create an Open vSwitch bridge (ovsbr0) with - one DPDK interface, by selecting the Add button - from the Bridges tab. + Select uCPE device 1, access Configuration, add the network + interface that will be used and configure it for DPDK. - Once the bridge creation popup appears, fill-in the required - fields and add the physical interface. + Create an OVS bridge and attach the DPDK network + interface. - Repeat the steps above on uCPE device 2, using one DPDK - interface and creating another OVS bridge. + Repeat the steps above for uCPE device 2. @@ -88,103 +81,200 @@ - Select VNF -> - Descriptor -> - On-board. - - - - Select the VM Image radio button. - - - - Provide the path to the qcow image by selecting - Browse from VM image file - option. - - - - Fill the required fields below and press - Onboard: + Onboard the Clavister VNF by filling the required fields with the following + values: - Memory in MB: 1024 + VM Image File: Provide + the path to the Clavister VNF qcow2 image - Nr. of CPUs: 1 + Memory in MB: 1024 - Storage in GB: 10 + Num of CPUs: 4 - - - - - Instantiating the VNFs: - - - - A) Instantiate the Clavister VNF on uCPE - device 1: - - Select uCPE device 1, then from the top toolbar: - VNF -> Instances -> - Add. + Storage in GB: 20 - Fill in the required information about the Clavister VNF, - (the default network configuration can be used) and select - Create. + Interfaces: Add 2 + interfaces - - - - B) Instantiate two Enea VNFs (one as the - client and one as the server) on uCPE device 2: - - - Select uCPE device 2, then from the top toolbar: - VNF -> Instances -> - Add. + Cloud-init Datasource: + ConfigDrive - In the new VNF Instance window, select - the Enea VNF from the dropdown menu, configure it to act as a - server by unchecking the Client mode IPerf - box, and then click Create. + Cloud-init Disk Type: + disk + + - - Select Add once more, enable the - Client mode IPerf checkbox this time, and - click Create to instantiate the second - iPerf VNF as a client, and to run it in - client mode. - - + + Onboard the Enea VNF by filling the required fields with the following values: + + + VM Image File: Provide + the path to the Enea NFV Access VNF qcow2 image + + + + Memory in MB: + 2048 + + + + Num of CPUs: 2 + + + + Storage in GB: + 10 + + + + Interfaces: Add 1 + interface + + + + Cloud-init Datasource: + NoCloud + + + + Cloud-init Disk Type: + disk + + - + + + Instantiating the VNFs: + + + + Instantiate the Clavister VNF on uCPE device 1 using the + required fields below: + + + + Name: clavister + + + + VNF Type: Select + Clavister VNF + + + + uCPE Device: Select + uCPE device 1 + + + + Cloud Init File: + Provide the path to the Clavister cloud-init file. + + + + Interfaces: Set the interface type + to DPDK and select the OVS bridge created + above, for both interfaces. + + + + + + Instantiate the Enea iPerf server VNF on uCPE device 2 by filling + the required fields with the values below: + + + + Name: + iperf_server + + + + VNF Type: Select Enea + NFV Access VNF + + + + uCPE Device: Select + uCPE device 2 + + + + Cloud Init File: + Provide the path to the Enea VNF IPerf server cloud-init + file. + + + + Interfaces: Set the interface type to + DPDK and select the OVS bridge created above. + + + + + + Instantiate the Enea iPerf client VNF on uCPE device 2 by + filling the required fields with the values below: + + + + Name: + iperf_client + + + + VNF Type: Select Enea + NFV Access VNF + + + + uCPE Device: Select + uCPE device 2 + + + + Cloud Init File: + Provide the path to the Enea VNF iPerf client cloud-init + file. + + + + Interfaces: Set the interface + type to DPDK and select the OVS bridge created above. + + + +
Testing the Use-case - In order to check that traffic is forwarded between the two VNFs, - connect to the iPerf VNF client console: SSH -> - user (root) -> Connect and run - the following: + SSH to uCPE device 2 (Username: root) and connect to the IPerf + client VNF console: virsh list -virsh console +virsh console <id of iperf client> + + In order to check that traffic is forwarded between the VNFs, run + the following: + + # qemux86-64 login: root root@qemux86-64:~# iperf3 -c 192.168.10.10
@@ -192,11 +282,13 @@ root@qemux86-64:~# iperf3 -c 192.168.10.10
Clavister VNF using SR-IOV - In this use-case, uCPE device 1 will run the iPerf server and iPerf - client VNFs using SR-IOV, while uCPE device 2 will run the Clavister VNF - using SR-IOV with two virtual functions (vf1 and vf2): + The following use-case is essentially the same as the one detailed above, + in this scenario however, the uCPE devices are connected using SR-IOV, + with two virtual functions. + + FIXME: New image needed -
+
Clavister VNF using SR-IOV Overview @@ -210,88 +302,34 @@ root@qemux86-64:~# iperf3 -c 192.168.10.10
Use-case Setup - Configuring Network Interfaces on uCPE - devices: + Network Configuration: - On uCPE device 2, create an SR-IOV configuration with 2 - virtual functions by selecting Configuration - -> OpenVSwitch -> Host - Interfaces -> Add. - -
- SR-IOV configuration with 2 virtual functions - - - - - - -
+ Select uCPE device 1, access Configuration, + add the network interface that will be used and configure it for SR-IOV. + For sriov-mode select "adapter-pool" and "sriov-num-vfs:2". - On uCPE device 1, create an SR-IOV interface as done in step - 1. - - - - Create the iPerf server on uCPE device 1 and select - SrIovAdapterPool as an Interface type. - - - - Create the iPerf client on uCPE device 1. Select - SrIovAdapterPool as an Interface type and tick - the Client mode IPerf checkbox. + Repeat the step above for uCPE device 2. Onboarding the VNFs: - ???? + See the onboarding parameters in the use-case above. Instantiating the VNFs: - - - Instantiate the Clavister VNF on uCPE device 2: - VNF -> Instances -> - Add. - - - - Select SrIovAdapterPool as an Interface - type for both Interface 1 type and 2 type, before clicking - Create. - -
- Instantiating the Clavister VNF on uCPE device 2 - - - - - - -
- - + Use the same instantiation parameters as above, but select + interface type SrIovAdapterPool instead.
Testing the Use-case - In order to check that traffic is forwarded between the VNFs, - connect to the iPerf VNF client console by using: SSH - -> user (root) ->Connect and - run the following commands: - - virsh list -virsh console -root@qemux86-64:~# iperf3 -c 192.168.10.10 + Use the same test instructions as detailed in the use-case above.
\ No newline at end of file -- cgit v1.2.3-54-g00ecf