Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jiafeng Zhu, Jane Shen, Jeff Brower, Tina Tsou, Neal Oliver, James Li, Colin Hutchinson

 Meeting notes Meeting Notes -- Zhu, Brower

Agenda

  • An update on the whitepaper status - Jane
  • Infrastructure API portal discussion, continued 

...

 White paper discussion notes

-Jane - showed functional block diagram slide with app enabler and edge enabler as separate blocks
        - we can leverage ETSI MEC APIs in edge enabler
-Jeff - can we add a layer inside app enabler that Akraino blueprints can use for interworking between them
Neal - Neal would like to see draft diagrams posted
-Jane - we need to cover 2 dimensions: architecture and how-to-build things (orchestration and management)
        -architecture diagram slide is in work

...

Has been presented to TSC, pilot projects will be included in the portal (PCEI release 3 with api documentation, KubeEdge). The purpose of the portal is an entry point for users, and provide links to various sources. What about APIs from non-Akraino member projects (Google)? As long as it is open source, under Apache2Apache 2.0, we can point a link to their websites, BUT we don’t market it. 

...

Jane - mapping API to functional categories is 1st priority, 2nd priority is interworking between Akraino blueprint projects. Jane is working on a MindMap diagram showing API categories
       -can the portal include Intel's OpenNESS APIs; Neal suggested links from the portal to Intel’s interactive API documentation pages
Jane - we can use json files to define API interfaces
        -portal is somewhere in between documentation and sandbox
        -all blueprints should provide some form of API doc