You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 41 Next »

(Under Construction)

Overview

  • 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. 

  • 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.


Procedure

Below are instructions for API information gathering:

  1. Download the API information form (Click to download) or you can use this link to fill out then download the form from Google Drive. 
  2. Follow steps below to fill in the API info form
  3. Upload the form before  (Click to upload)
  4. 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?

API Review Meeting Minutes

Here is the release 4 BP API review meeting minutes.

API Information Collection Status

(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



5Jiafeng Zhu
  • Email sent: 10/10 and 10/15 
  • Participated ELIOT weekly meeting 10/21, and demonstrated how to fill out the API Info Form
  • Report Received;


6Jiafeng Zhu

Report Received;




16Jane 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



19Jiafeng Zhu

Report Received;

Accepted



10

Micro-MEC

Jane ShenReport Received

7





20Neal 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.....



17Jane ShenEmail sent: 10/15

3

Jane Shen

Report Received;

Accepted



18Jane Shen

Report Received;

Accepted



12



11






R4 Project Names

API Subcommittee member name

Status

Notes

Connected Vehicle Blueprint

Jiafeng Zhu

Email sent: 10/10 

replied


ELIOT IoT Gateway Blueprint

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

ELIOT SD-WAN/WAN Edge/uCPE Blueprint

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


ELIOT AIoT in Smart Office

Jiafeng Zhu

Email sent: 10/10 and 10/15 


IoT Workloads at the Smart Device Edge - Predictive Maintenance (with a Thermal Imaging Camera, vibration sensors, etc.)

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

ICN - Integrated Cloud-Native Family

Jiafeng Zhu

Jane Shen

Form uploaded

Private LTE/5G ICN

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


Micro-MEC

Jane Shen

Email sent: 10/15

Received.


Radio Edge Cloud (REC)

Jane Shen

Email sent: 10/15


Enterprise Applications on Lightweight 5G Telco Edge

Jane Shen

Email sent: 10/15; replied

Received


Public Cloud Edge Interface (PCEI) Blueprint

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

?



IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

?




Uploaded API Info Forms

 

No files shared here yet.



  • No labels