Versions Compared

Key

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

Overview

  • Motivation: improve customer access and knowledge for blueprint projects. Consistent and well-organized APIs with baseline information will increase Akraino adoption

  • All project APIs will be organized and published on the API map page of the Akraino API Portal.  The API Portal will include both API map navigation and search capability, to allow customers to investigate APIs they may need

  • In addition to blueprint projects' mandatory baseline API info, optional information about (a) telco network interface APIs, and (b) Kubernetes environment APIs info will be collected. This will be used to support one-stop API presentation, analysis, comparison, finding similar APIs, and sandbox/sample code
  • The TSC has asked the API subcommittee to identify commonality between APIs, and possibly identify a “base” set of Akraino edge computing APIs. This is future work, under discussion
  • This page contains API info for Releases R4-R6​, in reverse chronological order (i.e. most recent first)

...

...

No.

R5 Project Names

API Subcommittee member assignment

Status

Notes

1Brower

2Brower

No API changes expected from R5, per Bart Dong in TSC meeting . Waiting for e-mail from Bart to confirm this


3



4Brower

5

Brower



6Brower

No API changes from R5, per e-mail from Khemendra Kumar

Info for ELIOT IOTGateway APIs:

https://wiki.akraino.org/display/AK/ELIOT+R6+IOTGateway+API+documentation
7Brower

8

Brower



9Brower



10



11Brower


 


12Brower

No API changes expected from R5, per Liya Yu in TSC meeting . Waiting for e-mail from Liya to confirm this


13Brower

No API changes from R5, per e-mail from ZhuMing Zhang  


14

5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint

Feng Yang

Brower

15Brower



16

Brower

No API changes expected from R5, per Leo Li in TSC meeting . Waiting for e-mail from Leo to confirm this


17

Brower

No API changes from R5, per e-mail from Khemendra Kumar

18

Brower

Revised API info form sent to Oleg per his requirements (see API Subcommittee meeting minutes for details)

Note - PCEI Blueprint R6 API documentation located here (as of ):

https://wiki.akraino.org/x/Qy0wAw

19Brower

No changes from R5, per e-mail from HaiHui Wang  


20


21

Brower



22


23Brower

No API changes expected from R5, per TSC meeting discussion . Waiting for e-mail from Jason or Jack to confirm this.

Update - API form uploaded by Jason , scheduled for review at API subcommittee meeting  

Approved by API subcommittee at weekly meeting



24Brower



25Brower



26



27Brower



28Brower

Per e-mail from Colin Peters  , blueprint consumes Kubernetes and EdgeX APIs

API info form uploaded  

Scheduled for review by API subcommitte 

API info form reviewed and approved during API subcommittee meeting  


29

Robot Basic Architecture Based on SESS

Haruhisa Fukano

Brower

Per e-mail from Inoue Reo blueprint does not export or consume APIs

API info form uploaded by Inoue Reo , scheduled for API subcommittee review  

Reviewed and approved by API subcommittee

They are uploading an API info form indicating no APIs, along with comments about possible future API usage  

R6 API Review Meeting Minutes

...

...

...

...