...
Here are R4 BP API review meeting minutes.
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.
Who should fill in the API requirements form
- Akraino blueprint project PTLs should fill in the API info form, as a mandatory requirement for R4 and R5.
Procedure
Below are instructions for API information gathering:
- Download the API information form (Click to download) or you can use this link to fill out then download the form from Google Drive.
- Follow steps below to fill in the API info form
- Upload the form before (Click to upload)
- The API subcommittee will review inputs and verify links. PTLs can check the result from TSC Release 4 planning table
You can select API categories by choosing values from drop down lists embedded in the Excel spreadsheet. If you believe your project API doesn't fit existing categories, please explain in the "Comments" field and specify how your project APIs would be better categorized.
- Additional information of any type may be added to the "Comments" field. Don't hesitate to let us know why specific APIs are fundamental / important to your project.
- Please double check all links that you've filled in the form, and make sure they link to the latest version of your project.
- If you have no relevant APIs exported or consumed, please explain why this is the case in the Comments field.
Examples
Click here for KubeEdge Edge Service BP API Information Form Example
Questions?
- 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.
Uploaded API Info Forms
...
| Attachments | ||||
|---|---|---|---|---|
|
R5 API Information Collection and Review Status
Note – updates in this table are made by API subcommittee members only. PTLs should fill out the spreadsheet above, and then upload under "Uploaded API Info Forms" above.
...
R5 Project Names
...
API Subcommittee member assignment
...
Status
...
Notes
...
...
...
...
...
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
...
...
...
Network Cloud and TF (Tungsten Fabric) Integration Project
...
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 4.7 instead of 4.5
(OpenShift is Kubernetes, so both versions are correlated)"
...
...
See above note
...
Per e-mail from Liya Yu 21Sep21, no changes from R4
...
...
...
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
...
5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint
...
...
API info form uploaded , API subcommittee review scheduled for
API info form reviewed
...
...
...
...
Brower
...
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
...
...
Brower
...
Per API Subcommittee meeting 30Jul21, no change from R4
...
PCEI R5 API Doc:
https://wiki.akraino.org/x/qgHkAg
...
...
...
...
Brower
...
Per e-mail from Prem 31Jul21, no "new features/bugs". Per e-mail from Prem 27Aug21, confirmed no new API changes
...
...
...
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 .
...
...
API info form uploaded by Asif , scheduled for review by API Subcommittee
...
...
Ashvin Kumar uploaded API info form. API subcommittee review scheduled for
Review completed and info accepted
...
Federated Multi-Access Edge Cloud Platform
...
Per e-mail , Deepak is in process of uploading API info form
Form uploaded by Deepak, API subcommittee review scheduled for
...
R5 API Review Meeting Minutes
R4 API Information Collection and Review Status
Note – updates in this table are made by API subcommittee members only. PTLs should fill out the spreadsheet above, and then upload under "Uploaded API Info Forms" above.
...
R4 Project Names
...
API Subcommittee member assignment
...
Status
...
Notes
...
...
Jiafeng Zhu
...
Email sent: 10/10
replied
Form uploaded 15Dec
Scheduled for review by API subcommittee 21Dec 6:00p PST (22Dec 10:00a CST)
Review discussion: BP will add PaaS APIs, re-upload form
API subcommittee review completed and info accepted
...
...
First round email exchange on 12/09 with instruction link sent.
Form uploaded
Scheduled for review by API subcommittee 21Dec 6:00p PST (22Dec 10:00a CST)
Review discussion: BP will add PaaS APIs, re-upload form
API subcommittee review completed and info accepte
...
...
Jane Shen
...
Email sent: 10/15
Form uploaded
API subcommittee review completed and info accepted
...
...
Jiafeng Zhu
Jane Shen
...
Form uploaded
API subcommittee review completed and info accepted
BP reviewed on TSC 16 Dec.
API Sub committee 12/4/2020 meeting minutes
Slides presented with API related info:
| View file | ||||
|---|---|---|---|---|
|
...
...
Jiafeng Zhu
...
Email sent: 10/10 and 10/15
Try to join their weekly meeting, but none was in the meeting
Participated ELIOT weekly meeting 10/21, and demonstrated how to fill out the API Info Form
Form uploaded
Review completed during API subcommittee meeting 11Dec
BP reviewed on TSC 16 Dec.
...
...
Jiafeng Zhu
...
Email sent: 10/10 and 10/15
Try to join their weekly meeting, but none was in the meeting
Participated ELIOT weekly meeting 10/21, and demonstrated how to fill out the API Info Form
Review completed during API subcommittee meeting 11Dec
BP reviewed on TSC 16 Dec.
...
...
Jeff Brower
...
Form uploaded
Scheduled for review at API subcommittee meeting 18Dec
API subcommittee review completed and info accepted
...
...
Jane Shen
...
Form uploaded
API subcommittee review completed and info accepted
...
...
Jane Shen
...
Form uploaded
API subcommittee review completed and info accepted
...
...
Jane Shen
...
Email sent: 10/15
Email received
Form uploaded
API subcommittee review scheduled for
API subcommittee review completed and info accepted
...
...
Hechun replied by e-mail 12Jan, form is in progress
Form uploaded
API subcommittee review scheduled for
API subcommittee review completed and info accepted
...
...
Email sent 2Feb20 Hechun and Liya Yu, and 9Feb20 Hechun and Zhongwan Hao
Form uploaded
API subcommittee review scheduled for
API Subcommittee completed and info accepted
...
5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint
...
Jane Shen
...
Email sent: 10/15
Form uploaded
Reviewed by API subcommittee
API subcommittee review completed and info accepted
...
IEC Type 3: Android cloud native applications on Arm servers in edge for Integrated Edge Cloud (IEC) Blueprint Family
...
Jeff Brower
(assignment transferred from Jane Shen 15Jan21)
...
E-mail discussion 21Jan, they have no APIs consumed or exported but still need to fill out the form with BP name and explain current and future API status in the comments
Form uploaded , reviewed by API subcommittee
API subcommittee review completed and info accepted
...
...
Jeff Brower
...
Jiafeng sent e-mail 27Oct, Yihui replied 28Oct
Form uploaded
Scheduled for review by API subcommittee 21Dec 6:00p PST (22Dec 10:00a CST)
API subcommittee review completed and info accepted
...
...
Jane Shen
...
Email sent: 10/15; replied
Form received by e-mail
Form uploaded
API subcommittee review completed and info accepted
...
...
Jane Shen
...
Email sent: 10/15
Form uploaded on 4Jan21
Scheduled for review at API subcommittee meeting
API subcommittee review completed and info accepted
...
...
Form uploaded
API subcommittee review completed and info accepted
...
...
Form uploaded
API subcommittee review completed and info accepted
...
...
Ike Alisson
(assignment transferred from Neal Oliver 15Jan21)
...
Have not joined their group meeting yet, as it is a double-conflict in meeting schedule. Will attempt to work with them offline.
Received response email. Still need to follow up.....
Prem replied by e-mail 12Jan, form is in progress
Form uploaded
API subcommittee review scheduled for
API subcommittee review completed and info accepted
...
...
Jeff Brower
...
Form uploaded
Scheduled for review by API subcommittee 11Dec
Review completed during BP project meeting 11Dec. Updated API info form will be uploaded by V S
Form uploaded by V S on 18 Dec, will be reviewed by API subcommittee on 8 Jan
API subcommittee review completed and info accepted
...
...
Jiafeng Zhu
...
Email sent: 10/10 and 10/15
...
R4 API Review Meeting Minutes
Here are R4 BP API review meeting minutes.