2019-10-03

The drivers have indicated that there will not be a proposal for the Frankfurt timeframe.

2019-09-17 ArchCom

A PoC on the API GW, integration fabric have performed a PoC.  Davide did a introduction focussing on that it provides a means to show how to connect external APIs to ONAP. 

Manoj introduced: https://wiki.onap.org/display/DW/API+Fabric+Proof+of+Concept+Demo+Details 

• There was an introduction via slides then several demos
• It was commented that this is not connected to AAF at this stage, but has its own way to connect to authentication providers.
• The demos described the different GW plans
• The PoC was to demonstrate different roles of the API GW.
• The ingress gateway from the ISTIO project needs to be looked at
• There was feedback "https://github.com/apigee/istio-mixer-adapter/tree/master/adapter.  This is ISTIO integration with Apigee.  If POC takes care of ISTIO mixer integration with Gravitee, that would be of great help."
• It is based on gravittee
• Suggestion next step, see about the suitability for the External API .....
• Look to come bac kin a few week.

2019-06-04 ArchCom

There a discussion in preperation for the DDF.  The idea was to go more into use cases, then the functionalilty required, then the project structure.

–

2016-05-21 Archcom

Manoj has created a project proposal for discussion: https://wiki.onap.org/pages/viewpage.action?pageId=63999345  .  As authors, they are not yet sure whether it should be a new project, or functionality to existing projects, however to document the idea the project template has been res-used.  It covers:

• Consistency in API Management across projects
• API Façade and Standard API Development
• Integration with 3rd Party and Legacy Applications
• Finding balance between Platform functionality and Use Case functionality

Discussion

2019-05-21 ArchCom:

• Haibin was indicating that the API GW.  ZTE have an internal solution which can be opensourced.
• ArchCom doesn't see this as a new functional component.
• ArchCom views that the APIGW functionally in MSB with the following notes:
  • ArchCom recomends that the APIGW functionality resides in MSB.
  • Monaj and Huabin to discuss the technology evolution and return to ArchCom, iether with an agreed evolution of expressing different needs
  • There was a discussino about ExtGW in MSB vs External APIs.  External APIs exposes functional capabilities. ExtGW in MSB is communication connection.

2019-05-14 ArchCom:

• Continue the discussion from last week
• The problem statement:
  • Different API Management approaches
  • Stands alignment is a priority, could be a common components
  • External integratin might require interability  with legacy and 3rd party components
  • Evolution of platform functional capability vs use case capability.
• There were suggestions that the API GW "plugs" into the MSB.
• It is not to replace the existing APIs, but to create an abstraction layer or a set of abstraction layers.
• There was comments to look a bit broader regarding possible re-use of existing 3PP source code.
• Next Steps:
  • Dig more into the functional archtiecture implitation
  • Discuss more the the required functionalities

2019-05-07 ArchCom:

Manoj prosented: slides. https://wiki.onap.org/download/attachments/50202249/APIGW_ONAP_Archcomm_v0.1.pdf?api=v2

• Haubing, mentioned MSB has an internal "external GW".
• There are ONAP components that use GPRC and REST interfaces directly.
• The problem statement is a critical slide:
  • There was questions regarding whether the problem statement was shared with PTLs

This was an introduction - Come back after speaking more with MSB and External APIs.  There is a call for the request to clarify the problem statement.