Date
at 10:00AM EDT
Meeting Link: https://zoom.us/j/399880266
Discussed
- Record the Meeting!! (issue with Zoom recording)
- Introductions
- Welcome New Committers! Congratulations Eric and Matthieu: Committer Promotion Request for [ExtAPI]
- Update on code contribution Ludovic Robert
- working Docker, performance, security, license info, risk management
- Sonar is not picking up code coverage. Trying to resolve with Linux Foundation
- Documentation: Updated on Readthedocs: http://onap.readthedocs.io/en/latest/submodules/externalapi/nbi.git/docs/offeredapis/index.html
- Amdocs team performed test and identified some bugs that will be put into Jira
- CII Badging update Andy Mayer
- See: https://bestpractices.coreinfrastructure.org/en/projects/1771
- will update based on Orange input
- Need participation in Service IM Tiger team: see: https://doodle.com/poll/aunfy6s8pker82bs
- Action: Need to publish Service Order Model; Service Catalog; Service Inventory to Modeling sub-committee: ALL
- Modeling sub-committee invite: Modeling sub-committee meetings
- Next Time:
- Document API style used for External API at Legato interface reference point
- Casablanca use cases for External API
- Modeling of external facing APIs for ONAP and other ONAP projects (e.g., CLI)
- Alignment on API styles for ONAP external APIs
- Slide updates for MEF meeting on External API and Legato (Wednesday Morning) Andy Mayer; Ludovic Robert; Bithika; Mehmet Toy; Abinash Vishwakarma; mark gibson; Neil Thayer
Last time
- R3+ Interlude discussion Mehmet Toy
- Elastic EVC use case impacts on Legato and Interlude
- It may be possible to apply Service Catalog, Service Ordering, Service Inventory to Interlude
- Action: Andy Mayer to send Mehmet invite to modeling discussion
- Explore possible inclusion of future ONAP use case for Elastic Connectivity Service Mehmet Toy, Andy Mayer, Parviz Yegani
- Relationship with IETF L2 & L3 SM?
- Need for End to End use case within the ONAP Context Mehmet Toy; Andy Mayer (review with arch team)
- ACTION: Recommend end-to-end interactions based on LSO Operational Threads Mehmet Toy; mark gibson; Jack Pugaczewski; Andy Mayer (review with arch team); Include scope of Presto wrt ONAP
- ACTION: Possible application of External API at PRESTO with SDNC interactions with domain controllers (VOLTE use case) Possibly Jack Pugaczewski?
- Could possibly be part of R3 Casablanca scope
Working:
- Continue ExtAPI Design for Beijing Ludovic Robert
- Update: Removed VNF creation from scope and notification feature from scope
- Utilizing the ExternalAPI/NBI repo for Beijing code
- Making good progress for 29 March milestone
- Documentation
- Repo committs
- ACTION: Need to schedule meetings with SDC, SO, and A&AI to discuss API mapping; Also Run-time Catalog.
- ISSUE: Is SDC Providing CSAR from Catalog API? Could SDC provide a simple service view with input parameters of the service?
- ISSUE: Does SO require customer on instantiation requests? Is A&AI really keeping Customer (or Consumer) information?
- Begin Interlude Use Case discussion
- Dana Bobko will present an API Versioning proposal (NEXT WEEK )
- User Stories / Use Cases; State Models; Sequence diagrams for External and Internal interactions with ONAP components Andy Mayer
- End-to-end Operation Threads
- Service Catalog
- Query Service Catalog
- Retrieve Service Model
- Service Ordering
- Place Service Order
- Query Service Order
- Retrieve Service Order
- Delete Service Order
- Retrieve Service Order State
- Subscribe to Service Order Notifications
- Receive Service Order Notifications
- Service Inventory
- Query Service Inventory
- Retrieve Service
- Retrieve Service State
- Service Topology (spec only)
- Query Service Topology
- Retrieve Service Topology
- License Management (spec only)
- Receive License Usage Notifications
- Recording:
Upcoming:
- Next call will take place on 21 March 2018
- Architectural considerations for External APIs (mapping to ONAP components)
- User Stories / Use Cases; State Models; Sequence diagrams for External and Internal interactions with ONAP components
- Continue review and refinement of ONAP Common Model UML (Service Abstraction focus)
- Discussion on coordination with Architecture, Modeling, and MSB efforts (Alexander Vul)
Action items