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)
...
- You can send your questions to API subcommittee mailing list api@lists.akraino.org
- Or, leave comments at the bottom of this page
- Join API subcommittee weekly meetings (Friday morning 9:00am PST https://zoom.us/j/294712016) if you'd like to discuss your APIs with us.
- In case you don't use Microsoft Office, you can fill out the form in Google Doc https://docs.google.com/spreadsheets/d/e/2PACX-1vSbL0gDGuv1avvNSNTdpkeVP1yY-KDIjTYD_xPEIeQMMPxIu61S37ZYwr0nfyCco89EK6ikCATAjolW/pubhtml. However, you MUST download it from Google Doc and Upload to this page.
...
| No. | R5 Project Names | API Subcommittee member assignment | Status | Notes |
| 1 | Brower | |||
| 2 | Brower | No API changes expected from R5, per Bart Dong in TSC meeting . Waiting for e-mail from Bart to confirm this | ||
| 3 | ||||
| 4 | Brower | |||
| 5 | No API changes from R5, per e-mail from Salvador Fuentes | |||
| 6 | Brower | 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 | |
| 7 | Brower | No API changes from R5, per e-mail from Khemendra Kumar | ||
| 8 | Brower | |||
| 9 | Brower | |||
| 10 | ||||
| 11 | Micro MEC Ferenc Székely | Brower |
| |
| 12 | Brower | No API changes expected from R5, per Liya Yu in TSC meeting . Waiting for e-mail from Liya to confirm this. Confirmed in e-mail sent by Liya | ||
| 13 | Brower | 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 | Brower | No API changes from R5, per e-mail from Eagan Fu | |
| 15 | Brower | |||
| 16 | No API changes expected from R5, per Leo Li in TSC meeting . Waiting for e-mail from Leo to confirm this Leo confirmed by e-mail | |||
| 17 | Brower | No API changes from R5, per e-mail from Khemendra Kumar | Info for EALTEdge APIs: | |
| 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 ): | |
| 19 | Brower | No changes from R5, per e-mail from HaiHui Wang | ||
| 20 | ||||
| 21 | Brower | |||
| 22 | ||||
| 23 | Brower | 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 | ||
| 24 | Brower | |||
| 25 | Brower | No API changes from R5, per e-mail from Muhammad Hamza | ||
| 26 | ||||
| 27 | Brower | |||
| 28 | Brower | 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 | 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 |
...
- You can send your questions to API subcommittee mailing list api@lists.akraino.org
- Or, leave comments at the bottom of this page
- Join API subcommittee weekly meetings (Friday morning 9:00am PST https://zoom.us/j/294712016) if you'd like to discuss your APIs with us.
- In case you don't use Microsoft Office, you can fill out the form in Google Doc https://docs.google.com/spreadsheets/d/e/2PACX-1vSbL0gDGuv1avvNSNTdpkeVP1yY-KDIjTYD_xPEIeQMMPxIu61S37ZYwr0nfyCco89EK6ikCATAjolW/pubhtml. However, you MUST download it from Google Doc and Upload to this page.
...
- You can send your questions to API subcommittee mailing list api@lists.akraino.org
- Or, leave comments at the bottom of this page
- Join API subcommittee weekly meetings (Friday morning 9:00am PST https://zoom.us/j/294712016) if you'd like to discuss your APIs with us.
- In case you don't use Microsoft Office, you can fill out the form in Google Doc https://docs.google.com/spreadsheets/d/e/2PACX-1vSbL0gDGuv1avvNSNTdpkeVP1yY-KDIjTYD_xPEIeQMMPxIu61S37ZYwr0nfyCco89EK6ikCATAjolW/pubhtml. However, you MUST download it from Google Doc and Upload to this page.
...
- You can send your questions to API subcommittee mailing list api@lists.akraino.org
- Or, leave comments at the bottom of this page
- Join API subcommittee weekly meetings (Friday morning 9:00am PST https://zoom.us/j/294712016) if you'd like to discuss your APIs with us.
- In case you don't use Microsoft Office, you can fill out the form in Google Doc https://docs.google.com/spreadsheets/d/e/2PACX-1vSbL0gDGuv1avvNSNTdpkeVP1yY-KDIjTYD_xPEIeQMMPxIu61S37ZYwr0nfyCco89EK6ikCATAjolW/pubhtml. However, you MUST download it from Google Doc and Upload to this page.
...