#opnfv-meeting: Weekly Technical Discussion 150

Meeting started by bh526r at 12:59:52 UTC (full logs).

Meeting summary

  1. Roll Call (bh526r, 13:00:18)
    1. Qiao Fu (bh526r, 13:00:26)
    2. Daniel Balsiger (bh526r, 13:00:41)
    3. Bin Hu (bh526r, 13:00:46)
    4. Pierre Lynch (bh526r, 13:01:04)
    5. Qihui Zhao (bh526r, 13:01:11)
    6. Georg Kunz (bh526r, 13:01:42)
    7. Frank Brockners (bh526r, 13:02:05)
    8. Li Ying (bh526r, 13:02:41)
    9. Mike Fix (bh526r, 13:02:52)
    10. Dan Xu (bh526r, 13:04:03)
    11. Rex Lee (mj_rex, 13:04:19)
    12. Al Morton (bh526r, 13:04:28)
    13. Murtuza Khan (bh526r, 13:04:46)
    14. Mark Shostak (bh526r, 13:04:53)
    15. Al Morton (acmacm, 13:05:30)
    16. Trevor (bh526r, 13:08:25)
    17. Trevor Cooper (bh526r, 13:08:30)
    18. Manuel Buil (bh526r, 13:08:51)
    19. Sunku Ranganath (bh526r, 13:09:41)

  2. Continue Discussion on How to Support CNTT in OPNFV (Qiao Fu) (bh526r, 13:09:54)
    1. Qiao Fu indicated that although she originally planned to present a new project proposal CNTT-RI, CNTT itself needs some more discussion internally. So this will be postponed until it is ready by CNTT (bh526r, 13:10:48)
    2. Qiao shared a slides deck of OPNFV Strategy for CNTT (bh526r, 13:11:42)
    3. Qiao first introduced ongoing work in CNTT - Reference Model (RM), Reference Architecture (RA), and Reference Implementation (RI) & Verification (bh526r, 13:13:49)
    4. Now CNTT is evaluating test projects and test cases in OPNFV, and doing gap analysis (bh526r, 13:15:16)
    5. Mike Fix indicates that he is the liaison in terms of Chapter 8 RI & Verification. We communicated with test leads through email. (bh526r, 13:16:07)
    6. Mike Fix encourages everyone to contribute to Chapter 8 (bh526r, 13:17:04)
    7. Georg Kunz asked if the emails could include mailing list to ensure the open and transparency. (bh526r, 13:17:47)
    8. Bin indicated that CNTT business is primarily conducted in its own mailing lists. Everyone is encouraged to subscribe to those mailing lists. (bh526r, 13:19:41)
    9. Mike Fix did send to those CNTT mailing lists (bh526r, 13:19:59)
    10. Qiao Fu shared an overall structure about how CNTT and OPNFV will interact, and how OPNFV projects (feature projects, installer projects and test projects) can be organized in a high level (bh526r, 13:21:18)
    11. Qiao thinks that we should have this new CNTT-RI feature project as a starting point (bh526r, 13:22:42)
    12. Qiao also worried about installer projects, not so active (bh526r, 13:23:07)
    13. And another question is the gap of testing (bh526r, 13:23:33)
    14. Frank asked if Qiao has worked with any installers and got any confirmation (bh526r, 13:24:28)
    15. Qiao said the only confirmation was from Airship Installer. (bh526r, 13:24:50)
    16. Another active installer is Fuel, and Qiao never received confirmation from Fuel regarding support of CNTT (bh526r, 13:25:41)
    17. Georg asked test case analysis and test harness (bh526r, 13:26:06)
    18. Mike Fix said that CNTT is doing gap analysis. (bh526r, 13:26:39)
    19. Qiao said that she already created a wiki page for CNTT-RI project proposal, so she is looking for feedback from community (bh526r, 13:27:28)
    20. Qiao shared her idea about how we should promote progress in OPNFV (bh526r, 13:28:13)
    21. (1) Bring new project and resources (bh526r, 13:29:03)
    22. (2) finalize details of RA (bh526r, 13:29:23)
    23. and how RI should be done (bh526r, 13:29:46)
    24. (3) installer resources (bh526r, 13:30:00)
    25. (4) testing resources (bh526r, 13:30:07)
    26. (5) what to do with those projects that are not directly related to CNTT (bh526r, 13:31:36)
    27. (6) a new WG for CNTT, which coordinates with those projects for CNTT (bh526r, 13:32:09)
    28. Guangzhi Yang (bh526r, 13:33:12)
    29. Qiao asked what is eventual vision of OPNFV? We should discuss it in OPNFV (bh526r, 13:35:03)
    30. Georg also concurred. Some kind of structure - CNTT WG, test WG, etc. (bh526r, 13:36:02)
    31. also how the new project can trigger the testing (bh526r, 13:36:32)
    32. Frank mentions that it is contribution driven, so we need to bring new resources (bh526r, 13:37:01)
    33. Frank thinks what Fu Qiao suggested very aligned with current OPNFV projects and process (bh526r, 13:37:33)
    34. And it just naturally flows it, brings new resources, and makes it happen (bh526r, 13:38:13)
    35. Qiao thinks we are lacking vision, and perhaps community needs a clear vision (bh526r, 13:39:09)
    36. Frank thinks that once we have new projects, and we will have new resources (bh526r, 13:39:43)
    37. Bin suggested that we reserve 20 minutes of every TSC meeting starting from next week (9/3) to discuss those questions regarding vision. (bh526r, 13:47:26)
    38. All agreed (bh526r, 13:47:45)

  3. Report the Discussion Result in CNTT Meeting on Wednesday 8/21 (Trevor Cooper) (bh526r, 13:48:09)
    1. Trevor described examples of different flavors of compute etc. (bh526r, 13:49:52)
    2. e.g. large CPU small memory, is it correct? or vice versa small CPU, large RAM? (bh526r, 13:50:41)
    3. we need to work out those controversial configurations (bh526r, 13:51:04)
    4. Mark Shostak asked if Trevor thought about the comments CNTT gave in the discussion? (bh526r, 13:54:29)
    5. Mark asked Trevor to reply to Mark's email regarding those details (bh526r, 13:55:38)
    6. e.g. capacity, performance, standard unit, etc. (bh526r, 13:55:59)
    7. Trevor thinks we need more input from community, e.g. test projects etc. (bh526r, 13:58:39)
    8. Mike Fix indicated that he already incorporated some of Trevor's contribution to Chapter 8 (bh526r, 13:59:00)
    9. Trevor thinks it could be topic in Test WG (bh526r, 13:59:25)
    10. Al indicated that someone can propose an agenda, and Test WG can discuss it (bh526r, 14:00:40)
    11. We can find a time, because schedule changes (bh526r, 14:01:08)
    12. Trevor suggested to start this Thursday (bh526r, 14:01:18)
    13. Trevor and Al will work together to schedule the discussion at 8am Thursday this week 8/29 (bh526r, 14:04:59)

  4. AOB (bh526r, 14:05:04)
    1. CNTT Reference Architecture Discussion Mailing List (bh526r, 14:07:52)
    2. https://lists.opnfv.org/g/cntt-tech-refa (bh526r, 14:07:56)
    3. CNTT Reference Model Discussion Mailing List (bh526r, 14:08:09)
    4. https://lists.opnfv.org/g/cntt-tech-refm (bh526r, 14:08:25)
    5. CNTT Governance (bh526r, 14:10:00)
    6. https://lists.opnfv.org/g/cntt-gov (bh526r, 14:10:05)
    7. CNTT Technical Steering Committee (bh526r, 14:10:40)
    8. https://lists.opnfv.org/g/cntt-tech-steering (bh526r, 14:10:45)
    9. Meeting adjourned (bh526r, 14:11:14)


Meeting ended at 14:11:19 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. bh526r (83)
  2. collabot` (3)
  3. acmacm (1)
  4. mj_rex (1)


Generated by MeetBot 0.1.4.