17:18:13 <colindixon> #startmeeting tws
17:18:13 <odl_meetbot> Meeting started Mon Mar 27 17:18:13 2017 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:18:13 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:18:13 <odl_meetbot> The meeting name has been set to 'tws'
17:18:18 <colindixon> #topic intro to ONAP
17:18:41 <colindixon> #info Brian Freeman introduces ONAP (which is the merger of OpenECOMP and Open-O)
17:19:35 <colindixon> #Info open sourcing the core of the network automation platform will help reduce costs for each service provider and provide faster/easier ways to bring VNFs into the ecosystem
17:20:21 <colindixon> #info brief overview of the architecture including all the marjor components
17:21:37 <colindixon> #info the entire page of stuff is a heat template that will be deployed into 11 VMs and each VM contains docker containers, DCAE "unfolds" into a hadoop cluster with another few VMs
17:22:03 <colindixon> #Info everything but DCAE comes up in ~15 minutes, in about ~30-45 minutes everything is up, there's then robot tests
17:23:31 <colindixon> #info there are robot tests that do health tests for all the VMs as well as ones that onboard some sample VNFs and do end-to-end tests
17:27:53 <colindixon> #info building the SDNC from OpenDaylight involves some added features inside, e.g., A&AI
17:28:25 <colindixon> #info the APPC is the same, but with more things
17:30:31 <colindixon> #info DG (directed graphs) are the key points of how you configure, build and deploy interesting things in ONAP
17:33:02 <colindixon> #info shows a REST API call node in the directed graph makes calls, in this case, it's calling to SDN-C to then call into APP-C
17:33:48 <colindixon> #Info example of the simple Admin Interface running on port 8843
17:34:36 <colindixon> #info svlogic.log has log messages from instantiating/running directed graphs
17:36:13 <colindixon> #info record nodes in the DGs are what actually create log entries in the log files
17:36:44 <colindixon> #info a list of SDN-C Karaf features
17:37:29 <colindixon> #info sliapi is the main module, properties and restapi nodes in the the directed graph, dblib talks to MySQL, etc.
17:39:52 <colindixon> #info app-c is similar but a bit different, they have some other REST adaptors
17:40:02 <colindixon> #Info there are similar, but somewhat more app-focuses Karaf features
17:40:11 <colindixon> #Info app-c is sdn-c + some more things
17:41:18 <colindixon> #info they're built from Beryllium-SR2 OpenDaylight
17:42:42 <colindixon> #Info things that are not in the open source version of SDN-C, some nodes, e.g., BGP/PECP and PCEP backbone control, those are not in open source now
17:46:17 <colindixon> #info colindixon asks and brianF confirms that PNFs and VNFs are intentionally converged and not really a relevant distinction unless it's not possible
17:47:59 <colindixon> #info among other things BGP, PCEP and things are harder to find demo-able devices to control
17:49:04 <colindixon> #Info colindixon asks what's included in SDN-C and APP-C that actually get used, Brian says that NETCONF and BGP and PCEP are included from OpenDaylight, they also have adaptors for chef and other things for APP-C
17:49:17 <colindixon> #info in general layer 2-3 is doing stuff with NETCONF and CLI adapators
17:49:54 <colindixon> #info LuisGomez asks what VES is, AT&T uses it, it's a telemetry format to get information from the network
17:50:34 <colindixon> #info the SNMP collector wasn't included, VES over HTTP was used in place of that in part because the demo VNFs use it
17:51:26 <colindixon> #info LuisGomez asks how they use Kafka, Brian says it's used in two ways: one is it's ues in handling TOSCA information and spinning up VMs, It's also used for getting information betwen the SDN-C DCAE and A&AI
17:52:15 <colindixon> #Info BrianF says DMaaP is based on Kafka, will also have file-based pub-sub where files, e.g., 1 GB, might be published and consumed
17:53:54 <colindixon> #info APP-C is the generic VNF-M in ONAP (or at least OpenECOMP)
17:54:58 <colindixon> #info this is different from ETSi mano to some extent where there are device-specific VNF-Ms
17:56:04 <colindixon> #info colindixon asks when can we see code? BrianF says that if you're a platinum member, you can see it now and have been able to for ~2 weeks.
17:56:50 <colindixon> #info phrobb notes that their waiting on things being renamed from OpenECOMP and Open-O to ONAP as well as actually merging code in general to a new architectural diagram.
18:00:23 <colindixon> #info BrianF says that there will be 63 gerrit repos for the 11 VMs, "it's a little complex to build"
18:00:53 <colindixon> #Info takes ~20 GB of disk space once you get you .m2 repo and you can't run everything in a single VM, you really need a hosting environent to run it
18:01:38 <colindixon> #Info they've been using rackspace (mentioned a bunch of times earlier)
18:01:42 <colindixon> #endmeeting