#opnfv-meeting: Weekly Technical Discussion

Meeting started by rpaik at 13:00:22 UTC (full logs).

Meeting summary

  1. rollcall (rpaik, 13:00:32)
    1. Ray Paik (rpaik, 13:00:56)
    2. Dan Radez (radez, 13:01:46)
    3. Bryan Sullivan (bryan_att, 13:01:50)
    4. Thaj (thaj, 13:01:56)
    5. Pierre Lynch (pjlynch, 13:02:17)
    6. request to add Euphrates pain points discussion (rpaik, 13:03:40)

  2. Armada project proposal (rpaik, 13:04:32)
    1. 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)
    2. goal is to provide the installer framework for Openstack-Helm and additional NFVI control plane components (rpaik, 13:08:54)
    3. pod resources for the project will also be available in the near future (rpaik, 13:11:29)
    4. 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)
    5. there is on-going collaboration with the Openstack Kolla project (rpaik, 13:14:55)
    6. 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)
    7. bryan_att also encourage community participation in the project (rpaik, 13:18:08)
    8. Armada will also install Kubernetes (rpaik, 13:21:40)
    9. 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)

  3. CORD project proposal (rpaik, 13:24:55)
    1. https://wiki.opnfv.org/display/PROJ/CORD CORD proposal (rpaik, 13:25:11)
    2. bryan_att notes that this project will try to bring CORD concept to OPNFV (rpaik, 13:25:40)
    3. plan is to use pod resources from the CORD community (rpaik, 13:26:57)
    4. 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)
    5. dneary suggests a different project name due to trademark concenrs (rpaik, 13:32:32)
    6. suggestion was made to also contribute VNFs to the samplevnf project (rpaik, 13:33:46)
    7. bryan_att notes that HW resources from CORD will not necessarily be OPNFV Pharos-compliant (rpaik, 13:37:04)
    8. bryan_att is looking for addition committers/contributors for this project proposal (rpaik, 13:39:58)
    9. 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)

  4. MANO WG build and test (rpaik, 13:43:03)
    1. Prakash discusses a modular integration approach for MANO (rpaik, 13:44:15)
    2. there is a proposal for a scenarios descriptor and vOLTE is being proposed for Opera in future releases (rpaik, 13:47:58)
    3. will also propose test cases for Dovetail (rpaik, 13:48:37)

  5. EUAG pain points (rpaik, 13:49:21)
    1. Steven shares the pain points collected by the end user advisory group members and prioritization (rpaik, 13:51:24)
    2. there are also EPIC statements for a number of pain points (rpaik, 13:52:18)
    3. consideration was also given to what EUAG thought was feasible for Euphrates release (rpaik, 13:53:39)
    4. tallgren notes that one possibility of compiling the info in one of the release milestones (e.g. MS1) (rpaik, 13:56:31)
    5. https://wiki.opnfv.org/display/SWREL/Release+Milestone+Description+for+Euphrates milestone descriptions (rpaik, 13:57:19)
    6. tallgren notes that making pain points visible would be helpful to the technical community as a guidance (rpaik, 14:00:53)
    7. 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 (full logs).

Action items

  1. (none)


People present (lines said)

  1. rpaik (40)
  2. collabot (4)
  3. pjlynch (1)
  4. bryan_att (1)
  5. radez (1)
  6. ChrisPriceAB (1)
  7. thaj (1)


Generated by MeetBot 0.1.4.