=========================================== #opnfv-meeting: Weekly Technical Discussion =========================================== Meeting started by rpaik at 13:00:22 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-30-13.00.log.html . Meeting summary --------------- * rollcall (rpaik, 13:00:32) * Ray Paik (rpaik, 13:00:56) * Dan Radez (radez, 13:01:46) * Bryan Sullivan (bryan_att, 13:01:50) * Thaj (thaj, 13:01:56) * Pierre Lynch (pjlynch, 13:02:17) * request to add Euphrates pain points discussion (rpaik, 13:03:40) * Armada project proposal (rpaik, 13:04:32) * bryan_att presents the proposal captured in the wiki and noted that AT&T has been involved in this activity for some time (rpaik, 13:08:34) * goal is to provide the installer framework for Openstack-Helm and additional NFVI control plane components (rpaik, 13:08:54) * pod resources for the project will also be available in the near future (rpaik, 13:11:29) * dneary asks what the maturity of this "installer" is and bryan_att noted that it is beyond the proof-of-concept stage (rpaik, 13:13:07) * there is on-going collaboration with the Openstack Kolla project (rpaik, 13:14:55) * bryan_att noted that it'd be a good idea to have discussions with the Daisy team to explore collaboration opportunities (rpaik, 13:17:05) * bryan_att also encourage community participation in the project (rpaik, 13:18:08) * Armada will also install Kubernetes (rpaik, 13:21:40) * consensus that it'd would be OK to bring this proposal to the TSC on April 11th, but there should be more diverse set of committers/contributors (rpaik, 13:24:37) * CORD project proposal (rpaik, 13:24:55) * LINK: https://wiki.opnfv.org/display/PROJ/CORD CORD proposal (rpaik, 13:25:11) * bryan_att notes that this project will try to bring CORD concept to OPNFV (rpaik, 13:25:40) * plan is to use pod resources from the CORD community (rpaik, 13:26:57) * dneary asks if XOS and VNFs are open source and bryan_att notes that any components that are not open source will not be brought to OPNFV (rpaik, 13:31:39) * dneary suggests a different project name due to trademark concenrs (rpaik, 13:32:32) * suggestion was made to also contribute VNFs to the samplevnf project (rpaik, 13:33:46) * bryan_att notes that HW resources from CORD will not necessarily be OPNFV Pharos-compliant (rpaik, 13:37:04) * bryan_att is looking for addition committers/contributors for this project proposal (rpaik, 13:39:58) * consensus that it'd would be OK to bring the proposal to the TSC on April 11th, but there should be more diverse set of committers/contributors plus address the project name concern (rpaik, 13:41:23) * MANO WG build and test (rpaik, 13:43:03) * Prakash discusses a modular integration approach for MANO (rpaik, 13:44:15) * there is a proposal for a scenarios descriptor and vOLTE is being proposed for Opera in future releases (rpaik, 13:47:58) * will also propose test cases for Dovetail (rpaik, 13:48:37) * EUAG pain points (rpaik, 13:49:21) * Steven shares the pain points collected by the end user advisory group members and prioritization (rpaik, 13:51:24) * there are also EPIC statements for a number of pain points (rpaik, 13:52:18) * consideration was also given to what EUAG thought was feasible for Euphrates release (rpaik, 13:53:39) * tallgren notes that one possibility of compiling the info in one of the release milestones (e.g. MS1) (rpaik, 13:56:31) * LINK: https://wiki.opnfv.org/display/SWREL/Release+Milestone+Description+for+Euphrates milestone descriptions (rpaik, 13:57:19) * tallgren notes that making pain points visible would be helpful to the technical community as a guidance (rpaik, 14:00:53) * dneary notes that tracking progress on EUAG-TSC interaction is something that is needed (rpaik, 14:01:59) Meeting ended at 14:03:07 UTC. People present (lines said) --------------------------- * rpaik (40) * collabot (4) * pjlynch (1) * bryan_att (1) * radez (1) * ChrisPriceAB (1) * thaj (1) Generated by `MeetBot`_ 0.1.4