Overview
Motivation: improve customer access and knowledge for Release 4 (R4) and R5 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.
...
- 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.
...
| No. | R5 Project Names | API Subcommittee member assignment | Status | Notes |
| 1 | Brower | Per notice from WANG Tao (Tucker Wang), no changes from R4 | ||
| 2 | Brower | Per e-mail from Bart 7Sep21, no changes from R4 | ||
| 3 | ||||
| 4 | Brower | Per notice from Kural 5Aug21, no change from R4 | ||
| 5 | ICN - Multi-Tenant Secure Cloud Native Platform Salvador Fuentes (Deactivated) | API form uploaded 24 May e-mail questions exchanged 20Jul21 Scheduled for review by API subcommittee API subcommittee review completed and info accepted | Ike asked about OpenAPI compliance. PTL indicates gRPC fits their needs and no plans for future OpenAPI compliance | |
| 6 | Brower | Per e-mail from Khemendra 26Aug21, no changes from R4 | ||
| 7 | Brower | Per e-mail from Khemendra 26Aug21, no changes from R4 | ||
| 8 | Brower | Per e-mail from Sukhdev 5Aug21, no change from R4 | ||
| 9 | Brower | Per e-mail from Ricardo 10Aug21, he uploaded R5 API info forms for both KNI blueprints, with no substantive changes from R4. The API subcommittee has a review scheduled for of the new API info forms and will update this table afterwards | Ricardo notes "the only difference with their previous R4 API form is they are now using: - Kubernetes 1.20 instead of 1.18 (OpenShift is Kubernetes, so both versions are correlated)" | |
| 10 | See above note | |||
| 11 | Micro MEC Ferenc Székely | Brower | Per e-mail from Liya Yu 21Sep21, no changes from R4 | |
| 12 | Brower | |||
| 13 | Brower | Tina mentioned during API subcommittee meeting there is no change to API info for the I-VICS blueprint. Sent e-mail 27Aug21 to Sihui Wang and Simmy Zhang to confirm. Confirmed by Sihui in e-mail 30Aug21 | ||
| 14 | 5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint | Brower | Per e-mail from Eagan Fu 15Aug21, no change from R4 | |
| 15 | Brower | API info form uploaded , API subcommittee review scheduled for API info form reviewed | According to API info form, no APIs offered or consumed, as the Blueprint constructs and provides an Android cloud run-time environment for user applications. Suggest to ask a few questions on TSC call and verify our understanding. | |
| 16 | Per e-mail from Leo (li@socnoc.ai) 11Aug21, no change from R4 | Per Tina, Yihui Wang stepped down as PTL. They will hold a PTL election soon | ||
| 17 | Brower | Per e-mail from Khemendra 20Aug21, no changes from R4 | Khemendra notes they upgraded the upstream project (Edge Gallery version 1.1 from 0.9 version) and have uploaded an updated API form with API document and definition links for EdgeGallery version 1.1 | |
| 18 | Brower | Per API Subcommittee meeting 30Jul21, no change from R4 | PCEI R5 API Doc: | |
| 19 | Brower | Per e-mail from Zifan 8Aug21, no change from R4 | ||
| 20 | ||||
| 21 | Brower | Per e-mail from Prem 31Jul21, no "new features/bugs". Per e-mail from Prem 27Aug21, confirmed no new API changes | see notes in R4 table below | |
| 22 | ||||
| 23 | Brower | API info form uploaded to API subcommittee page , and currently under review, with email questions pending to blueprint team before voting to approve this blueprint as part of R5 "Batch 2" blueprints. Approved informally . | Smart Cities R5 API Document | |
| 24 | Brower | API info form uploaded by Asif , scheduled for review by API Subcommittee | ||
| 25 | Brower | Ashvin Kumar uploaded API info form. API subcommittee revie9w review scheduled for Review completed and info accepted | The form was originally uploaded 27Aug21 but had a file corruption issue | |
| 26 | ||||
| 27 | Brower | Per e-mail , Deepak is in process of uploading API info form Form uploaded by Deepak, API subcommittee review scheduled for | Wiki page with API info: R5 API Document |
...