Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This document provides guidelines on how to manually install the Akraino IEC Release 2, including required software and hardware configurations. The steps described below are automatized in CI using Fuel@OPNFV or Compass. For details on this procedure, check the IEC Type1&2 Test Document for R2

The audience of this document is assumed to have good knowledge of networking and Unix/Linux administration.

Currently, the chosen operating system (OS) is Ubuntu 16.04 and/or 18.04.
The infrastructure orchestration of IEC is based on Kubernetes, which is a production-grade container orchestration with a rich running eco-system.
There are some options for Container Network Interface (CNI) solutions for IEC, e.g Calico, Contiv-vpp and Flannel. But the default container network interface (CNI) solution chosen for Kubernetes is Calico, which is a high performance, scalable, policy enabled and widely used container networking solution with rather easy installation and arm64 support. 

Currently MACCHIATObin board is used as a typical Type1 hardware platform, and we provided a guide on how to setup hardware. There is no explicit difference between Type1 and Type2 on the installation method of IEC Release 2.

The installation guide is mostly inherited from that of R1

...

The following sections describe the prerequisites for planning an IEC
deployment. Once these are met, installation steps provided should be followed
in order to obtain an IEC compliant Kubernetes cluster.

...

Info

Hardware requirements depend on the deployment type.
If more cluster nodes are used, the requirements for a single node can be lowered, provided that the sum of available resources is enough.

Depending on the intended usecase(s), more memory/storage might be required for running/storing the containers.

...

  • Ubuntu 16.04/18.04 is installed on each node;
  • SSH server running on each node, allowing password-based logins;
  • a user (by default named iecIEC, but can be customized via config later) is present on each node;
  • iec user IEC user has passwordless sudo rights;
  • iecIEC user is allowed password-based SSH login;

...