David, This is one of those service provider options.
Today, we use APPC for Openstack operations like start/stop/restart/migrate/evacuate/etc? even for L3 VNF because we liked having all the Ppenstack operations in one controller (a vCE and vSBC look the same for operations like stop/stop the VM). We tie that into our closed loop and our change management functions. The functions that APPC uses (both northbound and southbound) could work on an SDNC instance (they advantage of the common platform) but we haven?t seen the need yet. Generally we have used APPC as both a L4-L7 configuration manager as well as a (L2-L7 ) cloud VNF Manager. SDNC has L2/L3 configuration, signaling , L0/L1 interface and in some instances our neutron agent for cloud networking. Since SDNC can call APPC functions through REST (or through the call node if they were co-resident) we haven?t worried too much about the VNF manager boundary. This also stems from the fact that most L2/L3 VNFs are relatively simple compared to the L4-L7 VNFs we see in vIMS and vEPC. That being said if a service provider had strong desires to separate them then it would be feasible to use the VNF Manager functions out of SDNC but would require some integration work (karaf feature bundle dependencies). Out of the box in ONAP, APPC is the one listening on DMaaP/MR for events and has the adapter (cdp-pal) to talk to Openstack so I would recommend using APPC in that mode. Brian From: onap-discuss-bounces at lists.onap.org [mailto:[email protected]] On Behalf Of Sauvageau, David Sent: Wednesday, April 19, 2017 5:16 PM To: ROSE, DANIEL V <DR695H at att.com>; Dhananjay Pavgi <DP00476350 at techmahindra.com>; HU, BIN <bh526r at att.com>; onap-tsc at lists.onap.org; onap-discuss at lists.onap.org Subject: Re: [onap-discuss] [onap-tsc] Some questions regarding Controllers in ONAP Architecture Hi Daniel. For clarification, in the context of an L3 router.
