You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Summary

Public Cloud Edge Interface (PCEI) is implemented based on Edge Multi-Cluster Orchestrator (EMCO). PCEI Release 4 (R4) supports deployment of Public Cloud Edge (PCE) Apps from two Public Clouds (Azure and AWS), deployment of a 3rd-Party Edge (3PE) App (an implementation of ETSI MEC Location API App), as well as the end-to-end operation of the deployed PCE Apps using simulated Low Power Wide Area (LPWA) IoT client

Components of the release

  1. Edge Multi-Cloud Orchestrator
  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

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/pcei


Differences from previous version

None. This is the first release of PCEI

Upgrade Procedures

None.

EMCO Deployment procedures: https://wiki.akraino.org/x/EiW6AQ

PCE/3PE Deployment procedures: https://wiki.akraino.org/x/NSW6AQ

Release Data

Module version changes

None.

Document Version Changes

Initial versions.

Software Deliverable

          https://github.com/Azure/iotedge

  • AWS Greeng Grass Core Helm Charts
  • PCEI Location API Heml Charts
  • PCEI Location API Code
  • Simulated IoT Client Code
  • Azure IoT Edge Custom Software Module Code

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

Documentation Deliverable

PCEI R4 Installation Guide

PCEI R4 End-to-End Validation Guide

Fixed Issues and Bugs

None

Enhancements


Functionality changes

New Features

Version change

Deliverable

Known Limitations, Issues and Workarounds

System Limitations

Known Issues

Workarounds

References

  • No labels