13:00:22 <rpaik> #startmeeting Weekly Technical Discussion 13:00:22 <collabot> Meeting started Thu Mar 30 13:00:22 2017 UTC. The chair is rpaik. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:22 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 13:00:22 <collabot> The meeting name has been set to 'weekly_technical_discussion' 13:00:32 <rpaik> #topic rollcall 13:00:56 <rpaik> #info Ray Paik 13:01:46 <radez> #info Dan Radez 13:01:50 <bryan_att> #info Bryan Sullivan 13:01:56 <thaj> #info Thaj 13:02:17 <pjlynch> #info Pierre Lynch 13:03:40 <rpaik> #info request to add Euphrates pain points discussion 13:04:32 <rpaik> #topic Armada project proposal 13:04:57 <rpaik> #link https://wiki.opnfv.org/display/PROJ/Armada Armada proposal 13:06:50 <rpaik> #bryan_att presents the proposal captured in the wiki and noted that AT&T has been involved in this activity for some time 13:08:10 <rpaik> #undo 13:08:10 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x24c40d0> 13:08:34 <rpaik> #info bryan_att presents the proposal captured in the wiki and noted that AT&T has been involved in this activity for some time 13:08:54 <rpaik> #info goal is to provide the installer framework for Openstack-Helm and additional NFVI control plane components 13:11:29 <rpaik> #info pod resources for the project will also be available in the near future 13:13:07 <rpaik> #info dneary asks what the maturity of this "installer" is and bryan_att noted that it is beyond the proof-of-concept stage 13:14:55 <rpaik> #info there is on-going collaboration with the Openstack Kolla project 13:17:05 <rpaik> #info bryan_att noted that it'd be a good idea to have discussions with the Daisy team to explore collaboration opportunities 13:18:08 <rpaik> #info bryan_att also encourage community participation in the project 13:21:40 <rpaik> #info Armada will also install Kubernetes 13:24:37 <rpaik> #info 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 13:24:55 <rpaik> #topic CORD project proposal 13:25:11 <rpaik> #link https://wiki.opnfv.org/display/PROJ/CORD CORD proposal 13:25:40 <rpaik> #info bryan_att notes that this project will try to bring CORD concept to OPNFV 13:26:57 <rpaik> #info plan is to use pod resources from the CORD community 13:30:58 * ChrisPriceAB wonders if that will be aligned with pharos? 13:31:39 <rpaik> #info 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 13:32:32 <rpaik> #info dneary suggests a different project name due to trademark concenrs 13:33:46 <rpaik> #info suggestion was made to also contribute VNFs to the samplevnf project 13:37:04 <rpaik> #info bryan_att notes that HW resources from CORD will not necessarily be OPNFV Pharos-compliant 13:39:58 <rpaik> #info bryan_att is looking for addition committers/contributors for this project proposal 13:41:23 <rpaik> #info 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 13:43:03 <rpaik> #topic MANO WG build and test 13:44:15 <rpaik> #info Prakash discusses a modular integration approach for MANO 13:47:58 <rpaik> #info there is a proposal for a scenarios descriptor and vOLTE is being proposed for Opera in future releases 13:48:37 <rpaik> #info will also propose test cases for Dovetail 13:49:21 <rpaik> #topic EUAG pain points 13:51:24 <rpaik> #info Steven shares the pain points collected by the end user advisory group members and prioritization 13:52:18 <rpaik> #info there are also EPIC statements for a number of pain points 13:53:39 <rpaik> #info consideration was also given to what EUAG thought was feasible for Euphrates release 13:56:31 <rpaik> #info tallgren notes that one possibility of compiling the info in one of the release milestones (e.g. MS1) 13:57:19 <rpaik> #link https://wiki.opnfv.org/display/SWREL/Release+Milestone+Description+for+Euphrates milestone descriptions 14:00:53 <rpaik> #info tallgren notes that making pain points visible would be helpful to the technical community as a guidance 14:01:59 <rpaik> #info dneary notes that tracking progress on EUAG-TSC interaction is something that is needed 14:03:07 <rpaik> #endmeeting