Documentation

  • N/A
  • 20.12
  • 04/07/2021
  • Public Content
  • Download as PDF

Install
Converged Edge Insights

Converged Edge Insights
installs the Open Network Edge Services Software (OpenNESS) toolkit in Network Edge mode, setting up a subsystem consisted of an Edge Controller and one or more Edge Nodes.
For development purposes, you can set up the Edge Controller and Edge Node on a single device. A multi-device set up is recommended for production on deployment scenarios.
Converged Edge Insights
enables both set up modes with the same installation process.
During the installation, you will be prompted to enter your product key. This key is in the email you received from the Intel® Registration Center. Contact if you do not have this email message.
The steps below explain how to:
  • Prepare your target system.
  • Copy the package.
  • Complete the installation steps.

Prerequisites

Ensure that the following conditions are met properly to ensure smooth installation process.
  1. Hardware Requirements
    Make sure you have a fresh CentOS* 7.8.2003 installation with the hardware specified in Edge Node.
  2. Proxy Settings
    If you are behind a proxy network, please ensure that proxy addresses are configured in the system.
    export http_proxy=<proxy-address>:<proxy-port> export https_proxy=<proxy-address>:<proxy-port>
  3. Date and Time
    Make sure that the Date and Time are in sync with current local time.
  4. OpenNESS supports two different modes:
    • For Single Device mode, you need one machine. (Both controller and edge node will be on same device.)
    • For Multi Device mode, make sure you have at least two machines (one for controller and other(s) for edge node).
      Multi Device mode is not supported in this release.
  5. IP Address Conflict
    Make sure that the Edge Controller IP does not conflict with OpenNESS reserved IP addresses. For more details, refer to the Troubleshooting section.

Step 1: Prepare the Single Node Cluster (Controller/Edge Node) System

Make sure your Edge Controller has a fresh installation of
CentOS* Linux
that corresponds to the version of
Converged Edge Insights
that you downloaded. If you need help installing
CentOS* Linux
, follow these steps:
  1. Skip this step if
    CentOS* Linux
    7 is not installed on Edge Controller. If CentOS* is installed already, verify the version with command:
    cat /etc/centos-release
    Go to step 3 if the version of
    CentOS* Linux
    7 is 7.8.2003.
  2. Download the
    CentOS* Linux
    7.8 (2003) DVD ISO file (CentOS-7-x86_64-Minimal-2003.iso) from download-portal-1 or download-portal-2 to any device, such as your desktop/laptop. Download the file from the download-portal, which provides better download speed.
  3. Use an imaging application to create a bootable flash drive using the
    CentOS* Linux
    7 ISO file downloaded earlier.
  4. Power off your Edge Controller, insert the USB drive, and power on the system. If the Edge Controller doesn't boot from the USB drive, change the boot priority in the system BIOS.
  5. Follow the prompts to install
    CentOS* Linux
    with the default configurations. For detailed instructions, see the CentOS* guide.
  6. Select
    GNOME-Desktop
    from INSTALLATION SUMMARY > SOFTWARE > SOFTWARE SELECTION.
  7. Power down your
    Edge Controller System
    and remove the USB drive.
  8. Power up the
    Edge Controller System
    . You will see
    CentOS* Linux
    is successfully installed. Verify CentOS version with command:
    cat /etc/centos-release
    The result must be similar to
    CentOS* Linux
    release 7.8.2003 (Core)
    .
  9. Log on as the root user:
    su root
    Login with root user is required for enabling
    Converged Edge Insights
    to install system kernel packages.
  10. The static hostname for the
    Edge Controller System
    must be unique and it can't be
    localhost
    . Verify the hostname:
    hostnamectl | grep Static | cut -d':' -f2
    If the hostname is
    localhost or
    consists of upper case alphabet (A-Z) or special characters (._~$#@%^&*()), configure a hostname for the
    Edge Controller System
    :
    hostnamectl set-hostname <hostname>
    Hostname must contain only lower-case alphanumeric characters, "-" and it must start and end with an alphanumeric character.
  11. Enable SSH connections.
    systemctl start sshd systemctl enable sshd

Step 2: Copy the
Converged Edge Insights
.zip File to the
Edge Controller System

This installation process is on the Edge Controller.
In this step you copy
Converged Edge Insights
to your
Edge Controller System
.
  1. Copy converged_edge_insights.zip from the system on which you downloaded the installation package to the Home directory on your Edge Controller System. You can use a USB flash drive to copy the file. The icon of the installation package looks like the following:

Step 3: Extract the
Converged Edge Insights
Software

In this step you extract
converged_edge_insights.zip
. You need to be on the
Edge Controller System
to complete these steps.
  1. Make sure you have a working Internet connection.
  2. Open a new terminal as a root user and move the downloaded zip package to the
    /root
    folder.
    su root mv converged_edge_insights.zip /root
  3. Go to the
    /root
    directory using the following command and unzip the RI:
    cd /root unzip converged_edge_insights.zip
    If you download the file more than once, each download beyond the first is appended by a number.

Step 4: Install the Software

You will now run a script that will download components and install
Converged Edge Insights
on your
Edge Controller System
. Ensure that you always run this script on your Edge Controller System.
The software installation will take 2 to 3 hours. The completion time depends on your target systems and Internet connection.
  1. Run these commands:
    chmod 775 edgesoftware ./edgesoftware install
    Installation logs are available at:
    /var/log/esb-cli/Converged_Edge_Insights_<version>/<Component_name>/install.log
  2. Type the product key at the prompt:
  3. During the installation, you will be prompted to configure few things before installing OpenNESS. Refer to the screenshot below to configure.
    Multi Device is not supported in this release. Select Single Device when prompted to select the type of installation.
    If you are using an Azure instance, enter the Private IP address as the IP address of the Controller.
  4. When the installation is complete, you see the message
    Installation of package complete
    and the installation status for each module.

(Optional) View the Harbor User Interface

Once OpenNess 20.12 is installed successfully, you can view the Harbor User Interface (UI).
To access the Harbor UI, log onto
https://{Kubernetes_Control_Plane_IP}:30003
with username
admin
and password
Harbor12345
.
For example, visit https://192.168.10.12:30003 with username
admin
and password
Harbor12345
.

Troubleshooting

  • Pods Status Check
    Verify that the pods are
    Ready
    as well as in
    Running
    state using the following command:
    kubectl get pods -A
    You will see an output similar to the following:
    If any pods are in
    ImagePullBackOff
    state, manually pull the images using:
    docker login docker pull <image-name>
    If any pods are not in
    Running
    state, use the following command:
    kubectl describe -n <namespace> pod <pod_name>
  • Docker Pull Limit Issue
    If a Docker pull limit error is observed, log in with your Docker premium account.
    If Harbor pods are not in
    Running
    state, log in using the following command:
    docker login
    If Harbor pods are in
    Running
    state, log in using the following commands:
    docker login docker login https://<Machine_IP>:30003  <Username – admin> <Password - Harbor12345>
  • Installation Failure
    If the OpenNESS installation has failed on pulling the OpenNESS namespace pods like Grafana, Telemetry, TAS, etc., reboot the system. After rebooting, execute the following command:
    reboot su  swapoff -a  systemctl restart kubelet (Wait till all pods are in “Running” state.) ./edgesoftware install
  • Pod Status shows ContainerCreating for a long time
    If pod status shows
    ContainerCreating
    or
    Error
    or
    CrashLoopBackOff
    for 5 minutes or more, run the following commands:
    reboot su swapoff -a systemctl restart kubelet (Wait till all pods are in “Running” state.) ./edgesoftware install
  • Subprocess:32 Issue
    If you see any error related to subprocess, run the following command:
    pip install --ignore-installed subprocess32==3.5.4
  • IP Address Range Allocation Conflicts
    The OpenNESS Experience kits deployment uses, allocates, and reserves a set of IP address ranges for different CNIs and interfaces. The server or host IP address should not conflict with the default address allocation. If there is a critical need for the server IP address used by the OpenNESS default deployment, you must modify the default addresses used by OpenNESS.
    The following files specify the CIDR for CNIs and interfaces. These are the IP address ranges allocated and used by default.
    flavors/media-analytics-vca/all.yml:19:vca_cidr: "172.32.1.0/12" group_vars/all/10-default.yml:90:calico_cidr: "10.243.0.0/16" group_vars/all/10-default.yml:93:flannel_cidr: "10.244.0.0/16" group_vars/all/10-default.yml:96:weavenet_cidr: "10.32.0.0/12" group_vars/all/10-default.yml:99:kubeovn_cidr: "10.16.0.0/16,100.64.0.0/16,10.96.0.0/12" roles/kubernetes/cni/kubeovn/controlplane/templates/crd_local.yml.j2:13: cidrBlock: "192.168.{{ loop.index0 + 1 }}.0/24"
    The address
    192.168.x.y
    is used for SR-IOV and interface service IP address allocation in Kube-ovn CNI. Therefore, it is not allowed as a server IP address, which conflicts with this range. We recommend that you completely avoid the address range defined by the netmask because it may conflict with routing rules.
    For example, if the server/host IP address must use
    192.168.x.y
    , there is a conflict because this range is used for SR-IOV interfaces in OpenNESS by default. The IP address range for
    cidrBlock
    in the
    roles/kubernetes/cni/kubeovn/controlplane/templates/crd_local.yml.j2
    file can be changed to
    192.167.{{ loop.index0 + 1 }}.0/24
    to use some other IP segment for SR-IOV interfaces.
If you're unable to resolve your issues, go to the .

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.