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.
...
Attachments | ||||
---|---|---|---|---|
|
R6 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 | Brower | |||
2 | Brower | |||
3 | ||||
4 | Brower | |||
5 | ||||
6 | Brower | |||
7 | Brower | |||
8 | Brower | |||
9 | Brower | |||
10 | ||||
11 | Brower |
| ||
12 | Brower | |||
13 | Brower | |||
14 | 5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint | Brower | ||
15 | Brower | |||
16 | ||||
17 | Brower | |||
18 | Brower | |||
19 | Brower | |||
20 | ||||
21 | Brower | |||
22 | ||||
23 | Brower | |||
24 | Brower | |||
25 | Brower | |||
26 | ||||
27 | Brower | |||
28 | Brower | Per e-mail from Colin Peters , blueprint consumes Kubernetes and EdgeX APIs |
R6 API Review Meeting Minutes
R5 API Information Collection and Review Status
...