From 29b069a17501d2078887c32fb902d2cd1da67507 Mon Sep 17 00:00:00 2001 From: Sona Sarmadi Date: Mon, 14 Oct 2019 10:00:49 +0200 Subject: Update ch 4.2, 4.3, 4.4 Getting Started uCPE mgr - Update 4.2 Install the Enea uCPE Manager - Update 4.3 Device Configuration and Provisioning - Update 4.4 VNF Management Change-Id: I3064d8e621a4e02c600e36b3abc0e408105beebf Signed-off-by: Sona Sarmadi --- .../doc/getting_started_ucpe_manager.xml | 922 +++++++++++++++------ 1 file changed, 689 insertions(+), 233 deletions(-) diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml index 9d5eecc..1663e8c 100644 --- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml +++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml @@ -5,12 +5,13 @@
Prerequisites - Listed below are the main generic prerequisites required so that the + Listed below are the main generic prerequisites required so that the uCPE Manager can be deployed on the host platform: - A uCPE device with Enea NFV Access Run Time Platform installed. + A uCPE device with Enea NFV Access Run Time Platform + installed. @@ -24,53 +25,408 @@ Install the Enea uCPE Manager Unpack the uCPE Manager and install it following the instructions - provided within the release archive: - [unpacked_folder]/dist/README. + below. - There are things to consider during the installation phase, as - there are a few steps where user input is required. In most cases, the - default values should be used. +
+ Preparing your system - Check that the CentOS machine where the uCPE Manager is installed - has the firewall disabled. + + + Open a terminal with administrative rights, i.e. log into a + bash shell with + root privileges. + - Verify that the installation has succeeded: + + Choose the target installation folder, e.g. + /opt/ems. Everything will be installed under a + folder called ucpemanager within the target + installation folder. + + - - - Point your browser to the server machine running the uCPE - Manager. - + The application files will be installed in + /opt/ems/ucpemanager/application. The database will + be installed in /opt/ems/ucpemanager/database. - - In the login screen, log in with the username: admin and password: admin. - - + + If you have multiple spindles, it is recommended to let the + application run off one and the database off the other. This will + result in optimum performance. It is also recommended that the swap + disk be the same as the one used for the application. + + + Assuming another spindle is used (/drive2) do + the following: + + + + Create a folder which will host the database (e.g. + emsDatabase). + + + + Create a soft-link that will point to this folder: + + ln -s /opt/ems/elementcenter/database /drive2/emsDatabase + + + + Follow the installation process as described below. + + +
+ +
+ Installing the uCPE Manager + + + + Open a terminal with administrative rights, i.e. log into a + bash shell with + root privileges. + + + + cd to the folder you are installing + from. + + + + Verify that the folder you are installing from contains the + following files: + + + + README + + + + install.sh + + + + doinstall.sh + + + + configureHA.sh + + + + ucpemanager-x.y-Buildz-Linux.tar.gz + + + + ReleaseNotes + + + + + + Run the following command: + + ./install.sh /opt/ems ucpemanager-x.y-Buildz-Linux.tar.gz. + + + + This command will: + + + + Extract the application files from the compressed install + kit. + + + + Install the bundled database (if the user specifies an + internal database). + + + + Install ucpemanager as a service with the + name ucpemanager. + + + + Start the ucpemanager service. + + + + + The service will be automatically started when the computer + boots up. + + Check that the CentOS machine where the uCPE Manager is + installed has the firewall disabled. + + + Verify that the installation has succeeded by: + + + + Pointing your browser to the server machine running the uCPE + Manager. + + + + In the login screen, log in with the username: admin and password: admin. + + + + In order to manage the ucpemanager service, user can run: + service ucpemanager start/stop + + Installing with the restore + option + + It is possible to use a restore file created by the "System + Backup" utility provided in the uCPE Manager, to install a system and + set it to a known state. + + + The file to be used is the zip file created by System Backup, + not the one created by the uninstall or upgrade processes described + below. + + + The name format of this file will be: + SystemBackup_MMMDD_YYYY_HHMM_SS.zip (e.g + SystemBackup_Feb19_2013_2257_42.zip). + + Follow the steps for Installation provided above and provide an + additional argument as shown below: + + "./install.sh \ +/opt/ems ucpemanager-1.0-Build8-Linux.tar.gz \ + SystemBackup_MMMDD_YYYY_HHMM_SS.zip" + + The other steps are exactly the same as specified in the + Installation instructions. There are things to consider during the + installation phase, as there are a few steps where user input is + required. In most cases, the default values should be used. +
+ +
+ Upgrading the uCPE Manager + + + + Verify that the folder you are upgrading from contains the + following files: + + + + upgrade.sh + + + + doupgrade.sh + + + + configureHA.sh + + + + ucpemanager-x.y-Buildz-Linux.tar.gz + + + + + + Run the following command: + + ./upgrade.sh /opt/ems ucpemanager-1.0-Build8-Linux.tar.gz" + + + + Running this command will: + + + + Stop the currently running ucpemanager service. + + + + Create a compressed file of the ucpemanager application + folder, called: + ucpemanager-Backup-YYYYddMMHHmm.tar.gz, which + contains a snapshot of the existing installation. + + + + Rename the application folder to + application_original. + + + + Extract the application files from the specified compressed + install kit. There will now exist a (new) application folder, with + the contents of the new kit. + + + + Start the ucpemanager service. + + + + When the ucpemanager service starts, it will recognize the fact + that an old version of the application needs to be upgraded (based upon + the existence of the application_original folder. All + the relevant data from the old installation will be copied to the new + one and the application_original folder will be + deleted. +
+ +
+ Uninstalling an existing uCPE Manager installation + + + + Verify that the folder you are uninstalling from contains the + following files: + + + + uninstall.sh + + + + douninstall.sh + + + + + + Run the following command: + + ./uninstall.sh /opt/ems + + + + Running this command will: + + + + Stop the currently running ucpemanager service. + + + + Create a compressed file of the ucpemanager application + folder, called + ucpemanager-Backup-YYYYddMMHHmm.tar.gz, which + contains a snapshot of the existing installation. + + + + Uninstall the ucpemanager service, so that it will not startup + on reboot. + + + + Uninstall the database service (if an internal database is + being used). + + + + Completely remove the contents of the + application and database + folders. + + + + After these steps, the uCPE Manager is completely removed from the + system. +
+ +
+ Restoring a previous uCPE Manager installation + + + + Verify that the folder you are restoring from contains the + following files: + + + + restore.sh + + + + dorestore.sh + + + + configureHA.sh + + + + ucpemanager-Backup-YYYYddMMHHmm.tar.gz + (the original installation snapshot, as obtained from a previous + uninstall). + + + + + + Run the following command: + + ./restore.sh /opt/ems ucpemanager-Backup-YYYYddMMHHmm.tar.gz + + + + Running this command will remove any vestiges of the existing + ucpemanager service, if they exist, and reinstall the ucpemanager + application on the specified target, restoring the data in the database + and files in the process. + + The ucpemanager service is then started and the older version is + now running on the system. +
Device Configuration and Provisioning + The following describes the steps required for setting up the + virtualization infrastructure, ensuring that a uCPE device is ready for + virtualized service deployment. The sections herein contain information + about enrolling uCPE devices into the Enea uCPE Manager, selecting + physical interfaces to be used by virtualized networking and creating + different types of bridges to enable VNF communication. The Zero Touch + Provisioning mechanism is also touched upon, as alternative to manual + configuration of the virtualization infrastructure. +
Add a uCPE device to the Management System - This section describes how to connect to an instance of NFV Access - installed on a specific uCPE device, and how to setup the virtual - infrastructure. + Enrolling uCPE devices into the Enea uCPE Manager can be + accomplished using one of the two possible methods.
Direct Connection - When using this mechanism, the uCPE Manager will periodically poll - the uCPE device, using a specified IP address as the destination, attempting - to establish a management connection. + When using this mechanism, the uCPE Manager will periodically + poll the uCPE device, using a specified IP address as the destination, + attempting to establish a management connection. Add the uCPE device running the NFV Access Run Time Platform to - the management system by selecting Devices -> Manage -> - Add. Supply information about the uCPE device, and set the - parameters that will be used to connect to it. + the management system by: + + + + Selecting in the uCPE Manager: Devices -> Manage + -> Add. + + + + Suppling information about the uCPE device, and setting the + parameters that will be used to connect to it. + + The relevant parameters are: @@ -90,19 +446,21 @@ - IP Address. IP address of the device. + IP Address. IP address of the ucPE device. - SSH Port. The NETCONF Port used for communications. + SSH Port. The NETCONF Port used for communications. Default + is set to 830. - SSH User Name. The user name for SSH connectivity. + SSH User Name. The user name for SSH connectivity. Default + user is root. @@ -115,17 +473,17 @@ Device Calls Home. This checkbox indicates the direction of - device communications. In the Manual Configuration, leave this box - blank. + device communications. For Direct Connection, leave this flag + unchecked. - Device ID. The unique instance ID of the device. This links - a device to its day-0 configuration (stored in the - offline configuration system). It is a required field if you want - to perform Zero-Touch Provisioning. + Device ID. The unique identifier of the uCPE device. This + links a device to its Day-0 configuration (stored in the offline + configuration system). It is a required field if you want to + perform Zero-Touch Provisioning.
@@ -133,24 +491,26 @@
Device Call Home Connection - Follow the same steps as described in previous section, making sure - that the Device Calls Home checkbox is selected. - - When using this mechanism, the device will initiate a connection - to the uCPE Manager for NETCONF traffic (over SSH), while the uCPE - Manager waits for a device connection. Make sure the uCPE Manager IP - address has been configured on the device. For more information please see section - Installing Enea NFV Access for more details. + Follow the same steps as described in the previous section, + making sure that the Device Calls Home checkbox is + selected this time. + + When using this mechanism, the device will initiate a connection + to the uCPE Manager for NETCONF traffic (over SSH), while the uCPE + Manager waits for a device connection. Make sure the uCPE Manager IP + address has been configured on the device. For more information please + see section Installing Enea NFV + Access for more details.
Configure NFV Infrastructure - Once a management connection with the uCPE device has been established - by using any of the supported methods, the virtualization networking - infrastructure can be configured either manually or by using Zero Touch - Provisioning. + Once a management connection with the uCPE device has been + established by using any of the supported methods, the virtualization + networking infrastructure can be configured either manually or by using + Zero Touch Provisioning. The uCPE Manager can list network interfaces found on a device by selecting the uCPE device first and then selecting @@ -162,8 +522,8 @@ - + @@ -174,27 +534,40 @@
Manual Configuration - For Manual Configuration of uCPE networking, select the uCPE device - first and then Configuration -> OpenVSwitch. - In the Host Interfaces Caps, one can find a list of available network - interfaces and their capabilities. + For Manual Configuration of uCPE networking, select the uCPE + device first and then Configuration -> + OpenVSwitch. In Host Interfaces + Caps, one can find a list of available network interfaces + and their capabilities.
Configuring Interfaces + In order to make physical network interfaces available to the + virtualization infrastructure and VNFs, they must be configured into + the management system. + + To add an interface into the uCPE Manager, select the uCPE + device, then from the top toolbar select Configuration + -> OpenVSwitch -> Host Interfaces. The available + Interface types are detailed below. + DPDK Interface Type Configuring a physical interface in DPDK mode will require a DPDK-based application (e.g. OVS-DPDK) in order to access and use the interface. An interface set as the DPDK can be attached to an - OVS-DPDK bridge. - - Select the uCPE device, then from the top toolbar - select Configuration -> OpenVSwitch - -> Host Interfaces -> - Add. + OVS-DPDK bridge. + + + Make sure the Enable DPDK checkbox is + selected in Device -> Configuration -> + DPDK, otherwise no interface can be assigned to the + DPDK. + - For DPDK mode, the user must set values for the following fields: + To add a DPDK interface under the management system, set + appropriate values for the following fields: @@ -210,26 +583,27 @@ - Dpdk-type: the kernel module that allows user space access to the - physical interface. + Dpdk-type: the kernel module that allows user space access + to the physical interface. Enea recommends using the + vfio-pci driver. Create an OpenVSwitch bridge (ovsbr0) on - the device that uses a DPDK interface, by selecting the uCPE device, - then from the top toolbar selecting Configuration - -> OpenVSwitch -> Bridges -> - Add. + the device that uses a DPDK interface type, by selecting the uCPE + device, then from the top toolbar selecting + Configuration -> + OpenVSwitch -> Bridges + -> Add. SR-IOV Interface Type - SR-IOV mode will create a number of virtual functions on the host - which can be used to route traffic to VMs. Select the uCPE device, - then from the top toolbar select Configuration - -> OpenVSwitch -> Host Interfaces - -> Add. + SR-IOV technology allows for the creation of a number of + virtual functions on the host interface, which can be used by VNFs + running on the uCPE device. - For SR-IOV mode, the user must set values for the following fields: + For SR-IOV mode configuration, the user must set values for + the following fields: @@ -254,176 +628,220 @@ - PCI Passthrough Interface + Standard Interface Type - For the PCI Passthrough a user does not have to configure a - physical interface, instead simply select the PCI address and - connect it to a virtual port when the VNF instantiation step is reached. + Some of the physical network interfaces available on a uCPE + device, including Ethernet interfaces, do not have DPDK or SR-IOV + support. Instead, the Linux kernel driver has to be used. Wi-Fi and + 4G/LTE modems can also be configured and used for virtualization + infrastructure and VNFs. + + To add Standard interfaces under the management system, the + user must set values for the following fields: + + + + Source: the name of physical interface. + + + + Networking-type: standard + + + + PCI Passthrough + Interface Type + + For the PCI Passthrough a user does not + have to configure a physical interface, instead simply select the + PCI address and connect it to a virtual port when the VNF + instantiation step is reached.
Configuring Bridges - In-band Management - - In-band Management refers to a model where both the data plane - and control plane flow over the same network path. + After networking interfaces have been added to the uCPE + Manager, the user can create the necessary OVS bridges. - In some situations, In-band Management is the only option - available to both control and configure the uCPE device, while also - allowing for data-path traffic to pass over the same physical - interface. + How to add OVS bridges in the uCPE + Manager - The main requirement in order to use this solution is to have all - traffic pass through a defined WAN physical port. - - Three types of traffic are mentioned hereafter: + + + Select the uCPE device. + - - Device management. Part of the device configuration done by the - uCPE Manager. + Select Configuration. - VNF(s) configuration. Enabling or disabling features of a - VNF. E.g. enabling/disabling the firewall or VPN setup. + Click OpenvSwitch. - Data-path. All other traffic that is not used in the - control plane and needs to reach a LAN network. + Select the Bridges option, then click Add. - + - For use-cases where latency is very important, it is - recommended to use out-of-band management with a dedicated - physical interface for the data-path. + Depending on the settings in Configuration -> + OpenVSwitch -> DPDK, OVS bridges with or without DPDK + support will be used on the uCPE device. - The solution provided by Enea for In-band management is based - upon Open vSwitch bridges which control all traffic passing through - the WAN physical port. The NFV Access platform will assume the activated - connection with the uCPE Manager should be used for In-band management. - The physical port used by the active connection will be attached to the - In-band management WAN bridge. Communication with the uCPE Manager - should not be affected, it is reestablished automatically after In-band management - activation. - - All network traffic, with the exception of any received from - the uCPE Manager, will be sent to the VNF or dropped if there - is no VNF instantiated on the uCPE device. The VNF connected to the - WAN bridge must be configured for In-band management since traffic - from the VNF manager and data-path will be sent to only one port - (WAN) of the VNF. + There are three types of bridges which can be created, each + one fulfiling a different role: + + uCPE In-band Management + bridge + + In-band Management refers to a model where both the data plane + and control plane flow over the same network path. In some + situations (e.g. the uCPE device has only one routable IP address), + this is the only option available to both control and configure the + uCPE device, while also allowing for data-path traffic to pass over + the same physical interface. + + The solution provided by Enea for in-band management is based + upon an OpenvSwitch bridge fielding all traffic passing through the + WAN physical port. As a prerequisite, the WAN physical port has to + be configured to get its IP through DHCP. Any standard or + DPDK-assigned network interface can be used for the In-Band + management bridge. - Only one VNF must be connected to the In-band management WAN - bridge. + The In-Band Management bridge must be recreated each time + the uCPE Manager IP address is changed. - - Setup Prerequisites + To create the In-Band Management bridge, the user must set + values for the following fields: - - + + + name: name of the bridge. + - + + ovs-bridge-type: inbandMgmt + - - - WAN port + + mgmt-address: select IPv4 as the type and fill in the IP + address of the uCPE Manager. + - The physical port supported by DPDK. - + + mgmt-port: the NETCONF management port. Enea recommeneds + leaving this field unchanged. + + - - Dynamic IP on WAN port + + The first VNF instantiated on the uCPE device must be + connected to the In-Band Management bridge and its WAN interface + must be configured as the DHCP client. + - The DHCP server configured to distribute the same IP address - for the same MAC. - + In-band Management bridge for + VNFs - - uCPE Manager + If VNF management can be done over a dedicated virtual + interface, its possible to extend the networking infrastructure + configuration to also access the VNF's management interface over the + WAN port. - The uCPE Manager IP address must be public (accessible - for the uCPE device) and static. - - - -
+ For this setup, three types of traffic will pass over the WAN + physical interface: - How to activate In-band Management from - the uCPE Manager + + + Device management. Part of the device configuration done + by the uCPE Manager. + - - Select the uCPE device. + VNF(s) management. Enabling or disabling features of a + VNF. E.g. enabling/disabling the firewall or VPN setup. - Select Configuration. + Data-path. All other traffic that is not used in the + control plane and needs to reach a LAN network. + + + To create a VNF In-Band Management bridge, the user must set + values for the following fields: + - Click OpenvSwitch. + name: name of the bridge. - Select the Bridges option, then click Add. + ovs-bridge-type: vnfMgmt - - - In-band management WAN DPDK bridge configuration - - - - name. Provide a name for the WAN bridge e.g. - "ibm-wan-br". - ovs-bridge-type. dpdkWan - mgmt-address. IPv4 (add the IP address of the uCPE Manager machine). - mgmt-port. 4334 - + + vnf-mgmt-address: select IPv4 as the type and fill in the + IP address for management network, e.g 10.0.0.1. + + - The connection between the uCPE device and uCPE Manager will - be recreated and all traffic will pass through the new bridge - (ibm-wan-br). The WAN port of the very first instantiated VNF must - be connected to the ibm-wan-br bridge and it - should receive the same IP address as the WAN interfaces of the uCPE device. + + VNF management interfaces must be configured in same network + as the vnf-mgmt-address of the bridge. For more + information, please see 4.4 VNF + Management. + -
- Enea In-band Management solution + Data-plane Bridge Data-plane + bridges are generic bridges used for the VNF data-plane. There are + two supported sub-types: - - - - - -
+ + + communication: allows for VNF communication towards + LAN/WAN networks. This bridge type has at least one physical + port attached to it. + - The VNF can be reached on the same IP address as the uCPE - device, e.g. https://<WAN_IP> if a HTTP - server is present on that VNF. + + integration: allows for VNF-to-VNF communication (usually + for service function chaining). This bridge type does not have + any physical port attached. + + - - The In-band management bridge must be recreated each time - the uCPE Manager IP is changed. - + To create a Data-plane bridge, the user must set values for + the following fields: + + + + name: name of the bridge. + + + + ovs-bridge-type: select communication + or integration, depending on intended usage. + For communication bridges, physical interfaces can be added to + the bridge. + +
Zero Touch Provisioning - Zero-Touch Provisioning (ZTP) refers to the process of when a device - starts up for the first time and its initial configuration is pushed down - by an external management system, so that it is setup for proper - operation without additional manual intervention by an + Zero-Touch Provisioning (ZTP) refers to the process of when a + device starts up for the first time and its initial configuration is + pushed down by an external management system, so that it is setup for + proper operation without additional manual intervention by an operator. ZTP is an alternative to Manual configuration. A variety of operations can occur as part of ZTP such as initial @@ -432,36 +850,40 @@ operator to be physically present (initially) to manage the device. - An offline configuration can be prepared in advance for the uCPE - Manager to setup the infrastructure on the device. + An offline configuration is usually prepared in advance for the + uCPE Manager to setup the virtualization infrastructure on the uCPE + device, as soon as a device enrolls into the management system.
Offline Configuration The Offline Configuration subsystem is used to pre-populate a configuration for a device that will be brought under management at - a future point in time. - - When creating an offline configuration store a - Device ID can be specified. This ID - uniquely identifies the device to be initialized. - - From the top toolbar menu select Applications -> - Offline Config -> Add. - Specify the exact value of the Device ID in the - required field. This will tag the device needed for - the initial configuration provided by the - offline configuration store. Choose Merge as the - "Default Upload Method" if you do not want any boot configuration set - on the device, to be wiped out. Selecting Replace - will set the entire device configuration to match values in the - offline configuration. + a future point in time. When creating an offline configuration store + a Device ID can be specified. This ID uniquely + identifies the device to be initialized. + + Alternatively, a wildcard can be used in the Device + ID field, which results in a configuration being pushed on + all uCPE devices upon their initial connection towards the uCPE + Manager. + + To create an offline configuration, from the top toolbar menu + select Applications -> Offline + Config -> Add. Specify the value of + the Device ID in the required field or wildcard + if appropriate. Choose Merge as the "Default + Upload Method" if you do not want any boot configuration set on the + device, to be wiped out. Selecting Replace will + set the entire device configuration to match values in the offline + configuration. After creating the Offline Config Store, access the device - through Applications -> offline config - -> Config App and provision it with the required initial - configuration. This operation mirrors what happens during regular - offline configuration. + through Applications -> offline + config -> Config App and provision + it with the required initial configuration. This operation mirrors + what happens during manual configuration described in the previous + section.
@@ -509,8 +931,9 @@ - Get access to the VNF specific VNF Manager for day 1 and 2 - configuration (in cloud or for local deployment). + Optionally, get access to the VNF specific VNF Manager for + day 1 and 2 configuration (in cloud or for local + deployment). @@ -548,18 +971,18 @@ Determine the amount of hardware resources needed for - the VNF (RAM, CPUs and Disk size). + the VNF (RAM, number of CPUs and storage size). - Determine how many Network Interfaces the VNF will - use. + Determine how many Virtual Network Interfaces the VNF + will use. - Determine the day zero configuration method from the VNF + Determine the Day-0 configuration method from the VNF Getting Started guidelines. @@ -596,14 +1019,14 @@ When prompted by the UI, make sure the VM Image radio button at the top of the onboarding screen - is selected, it will trigger a popup menu. + is selected, it will trigger a popup menu window. - This menu contains data fields where both necessary and optional - information about the VNF can be supplied. After doing so, press the - onboard button, the uCPE Manager will create the VNF package and - onboard it. + This window contains data fields where both necessary and + optional information about the VNF can be supplied. After doing so, + press the Onboard button, the uCPE Manager will create the VNF + descriptor and add it to its VNF Catalog.
Onboard a VNF @@ -634,7 +1057,7 @@ VNF Type Name. This is the name that will be used to identify this VNF. It will be shown in - the VNF tables. + the VNFs list. @@ -741,8 +1164,8 @@ Path. When a user uses the uCPE Manager to create an instance for multiple VNFs, they will be prompted to provide a data file for each entry in this table. Each type of VNF - will require different cloud-init files, e.g.: a license - file. + will require different cloud-init files, e.g.: a license file. + @@ -760,8 +1183,40 @@ Property Values - numHugePages defines the number of huge - memory pages the VNF uses (for DPDK). + + + numHugePages defines the number of huge + memory pages the VNF uses (for DPDK). + + + + vnfMgmtIpAddress: the IP address of the + VNF's management interface, connected to a + vnfMgmt bridge (e.g. 10.0.0.2). + + + + internalMgmtPort: the VNF's TCP/UDP port + used for management (e.g. 443). + + + + externalMgmtPort: the Management port + used for external access (e.g. 60001). + + + + + The last three properties are useful in conjuction with the + vnfMgmt bridge type. They allow the user to map + the internal VNF management port to an external port, useful for VNF + configuration from WAN. + + In the previous example, the internal TCP port 443 (HTTPS) was + mapped to the external port 60001, which allows the user to access + the VNF management port from a web browser e.g. + https://<WAN_IP>:60001. +
@@ -770,8 +1225,10 @@ When a VNF is onboarded and available in the VNF catalog, it can be instantiated on connected uCPE devices. The configurations provided - when the VNF is onboarded, serve as a template for instantiation. Follow - the instructions below to instantiate a VNF: + when the VNF is onboarded, serve as a template for instantiation. + + + Follow the instructions below to instantiate a VNF: @@ -788,11 +1245,11 @@ - Name (a descriptive name). + Name: a descriptive name. - Device (the uCPE device to instantiate the VNF on). + Device: the uCPE device to instantiate the VNF on. @@ -805,8 +1262,7 @@ - Set up each NIC with a driver method (DPDK or - e1000). + Set up each NIC with a driver method. @@ -839,7 +1295,7 @@
- Entering the VNF Console + Accessing the VNF console Once the VNF is deployed, the VNF console can be entered using SSH and virsh commands. The VNF Console is a typical starting point for @@ -872,4 +1328,4 @@
- + \ No newline at end of file -- cgit v1.2.3-54-g00ecf