Overview

ICN BP family intends to address deployment of workloads in large number of edges and also in public clouds using K8S as resource orchestrator in each site and ONAP-K8S as service level orchestrator (across sites).  ICN also intends to integrate infrastructure orchestration which is needed to bring up a site using bare-metal servers.  Infrastructure orchestration needs to ensure that the infrastructure software required on edge servers is installed on per site basis, but controlled from a central dashboard.  Infrastructure orchestration is expected to do following:

• Installation : First time installation of all infrastructure software.
  • Keep monitoring for new servers and install the software based on the role of the server machine.
• Patching:  Continue to install the patches (mainly security related) if new patch release is made in any one of the infrastructure software packages.
  • May need to work with resource and service orchestrators to ensure that workload functionality does not get impacted.
• Software updates:  Updating software due to new releases.

User experience needs to be as simple as possible and even novice user shall be able to setup a site

• 1st time installation:
  • User procures set of machines or racks.
  • User connects them together with switches.
  • User uses the USB or other mechanisms to boot a machine (call it as bootstrap machine) with ICN-bootstrap stack.
  • User updates the inventory of machines, defines the role of each machine and inform the central ZTP system (ICN-infra-Central) or ICN-bootstrap stack using its provided UI or via API.
  • System installs the software and verifies the installation of each software component by running tests that are part of ICN-infra.
  • User/Entity gets informed when all the machines are installed with the software.
• Addition of new server
  • User updates the site inventory with its role to the ZTP/ICN-bootstrap stack using its UI.
  • System expected to install the software.
  • System expected to verify the installation of software using tests that are part of ICN-infra.
  • User/entity gets informed when the machine is sucessfully brought online.
• Deletion of existing server:
  • User informs the ZTP/ICN-bootstrap to bring down the server.
  • System removes the software and cleans up any local disk and other persistent systems 
  • User/Entity gets informed that server can be taken off from the network and disposed of.
• Patching
• Updating

Akraino's "Integrated Cloud Native NFV & App Stack"  (ICN) Blueprint is a Cloud Native Compute and Network Framework(CN-CNF) to integrated NFV's application to the de-facto standard and setting a framework to address 5G, IOT and various Linux Foundation edge use case in Cloud Native.

ICN has ONAP as the Service Orchestration Engine(SOE) and the Cloud Native(CN) projects such as Kubernetes for Resource Orchestration Engine(ROE), Prometheus as the monitoring and alerting, OVN as the SDN controller, Container Network Interface(CNI) for Orchestration Networking, Envoy for Service proxy, Helm and Operators for package management and Rook for storage. The framework stack specifics the best configuration methodology, enables development projects, installation scripts, software package to bind CNCF and LF edge use cases together.

This document break downs the hardware requirements, software ingredient, Testing and benchmarking for the R2 and R3 release for and provides overall picture toward blue print effect in Edge use cases.

Goal:

Identify potential projects in Linux Foundation(LF) and Cloud Native Computing Foundation(CNCF)

Non - Goal:
Architecture

Gaps

Solution

Overview

Flows

Initial implementation (End of July, 2019)

R2 release

R3 release