Motivation: improve customer access and knowledge for Release 4 (R4) blueprint projects. Consistent and well-organized APIs with baseline information will increase Akraino adoption.
All R4 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.
Below are instructions for API information gathering:
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.
Click here for KubeEdge Edge Service BP API Information Form Example
Here is the release 4 BP API review meeting minutes.
(To be updated)
Item | No. | Project Name | API subcommittee member follow up | Statue | Notes |
---|---|---|---|---|---|
13 | Report Received | ||||
1 | Jiafeng Zhu | Email sent: 10/10 replied | |||
5 | Jiafeng Zhu |
| |||
6 | Jiafeng Zhu | Report Received; | |||
16 | Jane Shen | Report Received; Accepted | |||
4 | Jiafeng Zhu Jane Shen | Report Received; Accepted | presented slides | ||
14 | |||||
2 | |||||
15 | |||||
21 | Jeff Brower | Report Received | |||
9 | Jane Shen | Report Received; Accepted | |||
8 | Jane Shen | Report Received; Accepted | |||
19 | Jiafeng Zhu | Report Received; Accepted | |||
10 | Jane Shen | Report Received | |||
7 | Report Uploaded | ||||
20 | Neal Oliver | 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..... | |||
17 | Jane Shen | Email sent: 10/15 | |||
3 | Jane Shen | Report Received; Accepted | |||
18 | Jane Shen | Report Received; Accepted | |||
12 | |||||
11 |
R4 Project Names | API Subcommittee member name | Status | Notes |
Jiafeng Zhu | Email sent: 10/10 replied | ||
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 | |
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 | ||
Jiafeng Zhu | Email sent: 10/10 and 10/15 | ||
Jeff Brower | Info received from BP technical members, and Jeff and Jane have attended their weekly meetings to understand their architecture and project API usage. Jeff has created an architecture diagram showing API, CLI, and GUI interfaces. An R4 release review meeting for the BP is scheduled for 9 Dec (Jeff will attend). | Form uploaded | |
Jiafeng Zhu Jane Shen | Form uploaded | ||
Neal Oliver | 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..... | ||
5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint | Jane Shen | Email sent: 10/15 | |
Jane Shen | Email sent: 10/15 Received. | ||
Jane Shen | Email sent: 10/15 | ||
Jane Shen | Email sent: 10/15; replied Received | ||
Jane Shen | Email sent: 10/15 | ||
IEC Type 3: Android cloud native applications on Arm servers in edge for Integrated Edge Cloud (IEC) Blueprint Family | ? | ||
? |