#opendaylight-nic: ONF NBI Session 2

Meeting summary

1. 1. is a service function (SF) an EP in terms of the intent interface? What about a service chain? (dbainbri, 21:19:34)
   2. (david commentary, and if a SF is just a new EP inserted in between two other EPs, does this mean that we need to consider that an intent isn't a src and dest EPG, but a chain for EPGs ?) (dbainbri, 21:23:54)
   3. ONFs implementation plan is to provide shared (core) intent code in the ONF GIT repo and then have that leveraged in an ONOS and ODL implementation (dbainbri, 21:29:37)
   4. ONF is funding INOCYBE to implement the core aspects of intent in ONF (dbainbri, 21:31:35)
   5. an end point registry is required and is shared state across all controllers (across domains) (dbainbri, 21:42:53)
   6. also need a "registry" of domain interconnects (dbainbri, 21:45:26)
   7. DaveL talking about a providing the intent engine a pool of resources (SF instances) and the controller picks an instance to build a SFC (dbainbri, 21:49:17)
   8. DavidB asks, if SF are EP, why not just use standard EP resolution as opposed to introduce a standard "resource pool concept"? (dbainbri, 21:50:16)
   9. there is a NBI sub group about service APIs (dbainbri, 22:50:50)
   10. (david commentary: really unclear what the purpose is or what a service API subgroup is for if we are going down an intent API model. no value in an L3 VPN API model) (dbainbri, 22:51:44)
   11. the NBI modeling group is developing API models for things like inventory and topology (dbainbri, 23:00:33)
   12. NBI modeling group is a ONF subgroup of the NBI group, formally known as NBI framework and architecture (dbainbri, 23:01:09)
   13. sess that ice cream is being served, ah the joys of technical conferences (dbainbri, 23:19:40)

Action items

1. (none)

People present (lines said)

1. dbainbri (69)
2. dmentze (34)
3. ShaunWackerly1 (21)
4. odl_meetbot (3)