...

Dependencies of the release (upstream version, patches)

EMCO:

• https://git.onap.org/multicloud/k8s/

Azure IoT Edge Helm Charts

• https://github.com/Azure/iotedge

PCEI Location API Helm Charts

PCEI Location API Code

Simulated IoT Client Code

Azure IoT Edge Custom Software Module

https://gerrit.akraino.org/r/pceiSpec

• The ETSI MEC ISG MEC012 Location API described using OpenAPI. The API is based on the Open Mobile Alliance's specification RESTful Network API for Zonal Presence
• ETSI MEC013 V1.1.1 Location Service API
• http://www.etsi.org/deliver/etsi_gs/MEC/001_099/013/01.01.01_60/gs_mec013v010101p.pdf
  BSD-3-Clause

Differences from previous version

...

EMCO Deployment procedures: https://wikilf-akraino.akrainoatlassian.orgnet/wiki/x/EiW6AQK4-Q

PCE/3PE Deployment procedures: https://wikilf-akraino.akrainoatlassian.orgnet/wiki/x/NSW6AQLY-Q

Release Data

Module version changes

...

• Edge Multi-Cloud Orchestrator Deployment
   https://wikilf-akraino.akrainoatlassian.orgnet/wiki/x/EiW6AQK4-Q
• Azure IoT Edge Helm Charts

...

Documentation Deliverable

PCEI R4 Installation Guide

PCEI R4 End-to-End Validation Guide

PCEI R4 Release Notes - this document

Fixed Issues and Bugs

None

Enhancements

1. Helm Charts for AWS Grrengrass Core PCE App
2. Helm Charts for PCEI Location API 3PE App
3. Simulated Low Power Wide Area IoT Client
4. Custom Module for Azure IoT Edge
5. PCEI Location API Code

https://gerrit.akraino.org/r/pcei (for all items above)  

Functionality changes

None - First Release.

New Features

First Release:

1. Deployment of Azure IoT Edge using PCEI/EMCO.
2. Deployment of AWS Green Grass Core using PCEI/EMCO.
3. Deployment of PCEI Location API App (based on ETSI MEC  Location API Spec)

Version change

First Release

Deliverable

1. Edge Multi-Cloud Orchestrator Deployment
   
2. Azure IoT Edge Helm Charts
3. AWS Greeng Grass Core Helm Charts
4. PCEI Location API Heml Charts
5. PCEI Location API Code
6. Simulated IoT Client Code
7. Azure IoT Edge Custom Software Module Code

Known Limitations, Issues and Workarounds

System Limitations

• EMCO supports Kubernetes clusters only.
• EMCO UI does not support deletion/modification of projects/services/apps at this time

Known Issues

• PCEI-R4-Issue-01: Azure IoT Edge requires deployment of Custom Kubernetes CRD. Azure IoT Custom CRD deployment by EMCO fails (see manual workaround)
• PCEI-R4-Issue-02: Sometimes App tar files created on a Mac fail to be deployed by EMCO (see workaround)

Workarounds

• For PCEI-R4-Issue-01: Refer to PCEI R4 End-to-End Validation Guide, section "Add Azure CRD to Edge K8S Cluster"
• For PCEI-R4-Issue-02:
  • Download PCEI Helm Charts to a Ubuntu or CentOS Host/VM
  • Create tar App files on Ubuntu or CentOS Host/VM
  • Copy the tar App files to a Mac and use Chrome browser to load tar App files in EMCO UI
• Other workarounds:
  • For convenience, the PCEI R4 End-to-End Validation Guide uses a local Docker registry on the EDGE-K8S-2 cluster for AWS GGC and PCEI Location API App images. Any other registry could be used. However, the Helm charts values.yaml file must be updated with the correct repo values for the AWS GGC and PCEI Location API App images.

References

EMCO Deployment procedures: https://lf-akraino.atlassian.net/wiki/x/K4-Q

PCE/3PE Deployment procedures: https://lf-akraino.atlassian.net/wiki/x/LY-Q