Blueprint Projects API Reporting Requirements

Blueprint Projects API Reporting Requirements

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)

Who should fill in the API requirements form

  • Akraino blueprint project PTLs should fill in the API info form, as a mandatory requirement for releases R4, R5, and R6

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 (link takes you to list of uploaded forms, below that is a drag and drop / browse area for uploading forms)

  4. The API subcommittee will review inputs and verify links. PTLs can check the results in the TSC Release 6 planning table (or previously TSC Release 5 planning table or 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

Questions?

  1.  

 

Uploaded API Info Forms

 

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

 

No.

R5 Project Names

API Subcommittee member assignment

Status

Notes

1

Connected Vehicle Blueprint

thorking

Tao Wang

Brower

 

 

2

IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family

Bart Dong

thorking

Brower

 

 

3

 

 

 

 

4

ICN - Integrated Cloud-Native Family

Kuralamudhan Ramakrishnan (Deactivated)

Brower

 

Kural sent e-mail Apr 28, 2022 saying no changes for "ICN Blueprint R6 release" but not specifying which ICN BPs

Comments