Versions Compared

Key

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

IEC Gerrit and Source Code

The bulk of Integrated Edge Cloud (IEC) as of Akraino Release 1 is entirely made up of components of the Integrated Edge Cloud (IEC) Blueprint Family. The IEC family consists of source code repositories starting with the prefix "iec/" and can be found by searching the Akraino Gerrit using this URL: https://gerrit.akraino.org/r/admin/repos/q/filter:iec.. The code reviews  across all these repositories may be found using this URL:  https://gerrit.akraino.org/r/q/projects:%22iec/%22.

Repository Link: https://gerrit.akraino.org/r/gitweb?p=iec.git;a=tree

...

$ ls

ci deploy docs LICENSE misc README.rst src tox.ini


$ tree -L 3

├── ci
│   └── labs
│   └── arm
├── deploy
│   └── compass
│   ├── deployIEC.sh
│   ├── deploy.sh
│   └── deployVM.sh
├── docs
│   ├── conf.py
│   ├── conf.yaml
│   ├── index.rst
│   ├── release
│   │   ├── api
│   │   ├── installation
│   │   └── release-notes
│   └── requirements.txt
├── LICENSE
├── misc
│   └── type1
│   ├── macbin
│   └── README.md
├── README.rst
├── src
│   ├── foundation
│   │   ├── api
│   │   ├── hot
│   │   └── scripts
│   ├── use_cases
│   │   └── seba_on_arm
│   └── xConnect
│   └── README
└── tox.ini


IEC Repo Code Structure Description

./iec/docs

  • The documentation in this directory provides a more detailed introduction to IEC

...

  • A series of scripts are provided to build the IEC infrastructure platform, including: building the k8s cluster and configuring the container network solution.

./iec/src/foundation/scripts/cni

  • Various CNIs which are supported with installations on arm platform, the available CNIs could be referred from the following figure:

Image Added

./iec/src/foundation/service_mesh

  • A service mesh deployment sample of Bookinfo for arm64 platform

./iec/src/use_cases/seba_on_arm/

  • SDN-Enabled Broadband Access (SEBA) is an Exemplar Platform being built by the ONF and CORD community, which would also be a first use case of IEC. We provide  SEBA source repositories, compiling scripts, test scripts and SEBA installation guide on Arm.

./iec/src/type3_AndroidCloud

./iec/src/type5_SmartNIC

./iec/misc/type1/macbin/

  • This dir contains the miscellaneous information about IEC Type 1 device and software info. Currently we choose the MACCHIATObin board as the main Type 1 hardware platform.

Future development of Integrated Edge Cloud (IEC) will include additional workflows as well as enhancements to the edge reference stack with more advanced support for remote edge, edge cloud with cloud native platforms and VMs. High performance container and VM networking and related eco-systems are highly appreciated, for Arm64 and/or x86_64 platforms. Any related works are also welcome.

IEC Static Code Check

Currently, a source code commit to IEC code repo usually would be subject to a code syntax check under Akraino Jobbuilder job by Tox, which would check the following types of code in general:

...

  • git commit message checks, RST checks, shellcheck checks use default configurations;
  • pylint uses [2] to allow some common errors/warnings to be ignored;
  • yamllint uses [3] to allow unquoted truthy values, ignore missing document start markers.

REC Gerrit and Source Code

The bulk of Radio Edge Cloud as of Akraino Release 1 is entirely made up of components of the Telco Appliance Blueprint Family because REC is the first instance of this blueprint family. The TA family consists of source code repositories starting with the prefix "ta/" and can be found by searching the Akraino Gerrit using this URL: https://gerrit.akraino.org/r/#/admin/projects/?filter=ta%252F and code reviews across all these repositories may be found using this URL: https://gerrit.akraino.org/r/#/q/projects:%22ta/%22

The Radio Edge Cloud itself can be found in this repository: https://gerrit.akraino.org/r/#/admin/projects/rec which consists primarily of a YAML file that is input to the new (as of Akraino Release 1) release of the Regional Controller which now uses a YAML file as input for learning how to deploy new types of blueprints. The purpose of the YAML file is to inform the Regional Controller of where to find executable workflows and other resources. As of Akraino Release 1 there is one REC workflow, the create workflow, which uses the ISO DVD images generated by the Akraino Jenkins Continuous Integration system (driven by the Telco Appliance Jenkins Jobs in https://gerrit.akraino.org/r/gitweb?p=ci-management.git;a=tree;f=jjb/ta;h=15c15cc0cebff25fdf61b6a0c95885a8e7fd41f1;hb=HEAD and stored in Nexus) and the TA Remote Installer (https://gerrit.akraino.org/r/gitweb?p=ta/remote-installer.git;a=tree ) to deploy the REC.

Future development of Radio Edge Cloud will include additional workflows as well as enhancements to the Telco Appliance Blueprint Family. O-RAN's RAN Intelligent Controller (RIC) has currently released its "Release Zero" and is anticipated to produce a Release 1 of its own later this year. The REC workflows and Continuous Deployment testing will expand to include future RIC releases and full appliance functional and performance testing as they become available.

...