#opnfv-meeting: Weekly Technical Discussion

Meeting summary

1. Roll Call (bh526r, 12:58:26)
   1. Bin Hu (bh526r, 12:58:32)
   2. Parker Berberian (bh526r, 12:59:01)
   3. Sawyer Bergeron (bh526r, 12:59:20)
   4. Fatih Degirmenci (fdegir, 12:59:44)
   5. David McBride (bh526r, 12:59:48)
   6. Jack Morgan (jmorgan1, 13:00:02)
   7. Manuel Buil (bh526r, 13:01:50)
   8. Greg Oberfield (bh526r, 13:04:49)
   9. Trevor Cooper (trevor_intel, 13:05:51)
   10. Trevor Cooper (bh526r, 13:05:51)
   11. https://wiki.opnfv.org/download/attachments/37683335/OPNFV_XCI_ProjectProposal.pdf?api=v2 (fdegir, 13:06:07)
   
   
2. XCI Project Proposal (bh526r, 13:06:34)
   1. https://wiki.opnfv.org/download/attachments/37683335/OPNFV_XCI_ProjectProposal.pdf?api=v2 (bh526r, 13:06:50)
   2. https://wiki.opnfv.org/display/PROJ/XCI (bh526r, 13:07:04)
   3. Prakash Ramchandran (bh526r, 13:07:33)
   4. Daniel Balsiger (bh526r, 13:08:00)
   5. Mark Shostak (bh526r, 13:08:14)
   6. Bin Yang (bh526r, 13:15:02)
   7. Mark asked that there are lots of confusion about the name. Mark suggested to change the name to distinguish the original CI framework from the new work in the proposal (bh526r, 13:17:04)
   8. Mark asked if there is any specific scope, because what is specified there is quite scope and vague (bh526r, 13:20:49)
   9. Is there anything specific? (bh526r, 13:21:04)
   10. Fatih mentioned CI/CD (bh526r, 13:21:41)
   11. Fatih clarified the toolchain means the specific installer, e.g. Bifrost, Ansible, Kubespray etc. (bh526r, 13:22:30)
   12. Trevor mentioned that XCI means facilitating CI/CD in the past, but now the scope has changed, and including CNTT, and not sure what is the objective (bh526r, 13:23:38)
   13. Another is FuncTest, the history is that it is competing. Has this been resolved? (bh526r, 13:24:21)
   14. Fatih said the key here is the lack of support from OPNFV community (bh526r, 13:24:54)
   15. Bring CI/CD methodology, and bring upstream components (bh526r, 13:25:44)
   16. Installer projects didn't support XCI at that time (bh526r, 13:26:14)
   17. Because of lack of support, we brought toolchain (bh526r, 13:26:42)
   18. This caused confusion of expanded scope (bh526r, 13:26:57)
   19. Fatih said there is no competition with FuncTest (bh526r, 13:28:11)
   20. Mark said Xtesting v.s. XCI (bh526r, 13:28:44)
   21. Fatih said Xtesting name was after XCI (bh526r, 13:29:05)
   22. Mark thinks we need to differentiate those 2 - CI/CD and installer/toolchain (bh526r, 13:30:03)
   23. Marked if those 13 committers are from legacy XCI or new people? (bh526r, 13:32:06)
   24. Fatih said only 3 are from legacy XCI (bh526r, 13:32:20)
   25. Fatih finally said XCI is an installer project, an integration project and a CI/CD project (bh526r, 13:37:38)
   26. Prakash asked what happened to Releng? (bh526r, 13:38:04)
   27. Fatih said there is still a Releng. XCI is not doing CI/CD toolchain, but methodology (bh526r, 13:38:45)
   28. Bin asked what was the reason that XCI lack of support from OPNFV community? (bh526r, 13:41:32)
   29. Fatih said there might be other installers and competing priorities (bh526r, 13:41:56)
   30. business relevancy, upstream support and competing priorities (bh526r, 13:42:40)
   31. LFN TAC recommendation - https://wiki.lfnetworking.org/display/LN/Infrastructure+Working+Group+Summary+Report (jmorgan1, 13:56:25)
   32. Bin suggested 3 things: (bh526r, 14:01:19)
   33. (1) Communicate with FuncTest and get their feedback, because FuncTest is a critical dependency of XCI proposal as it states today (bh526r, 14:02:10)
   34. (2) Separate installer part from CI/CD part. make a separate proposal of Ansible/Kubespray/Bifrost installer so that it will satisfy vendor's business as well as some operator's needs. This is because operators will have different needs and we need to meet them with variety of installers and technologies, and vendors also need to differentiate their business (bh526r, 14:05:40)
   35. (3) Consolidate the effort of CI/CD into the experimentation that OPNFV is initiating based on TAC's recommendation, which OPNFV TSC agreed to and started to experiment (bh526r, 14:06:39)
   36. Mark further suggested to have CNTT's input to this XCI proposal, and all agreed (bh526r, 14:07:43)
   37. Bin and Mark will work out how to make CNTT's input, and when/where to discuss etc. The goal is to make it happen as soon as we can (bh526r, 14:08:19)
   
   
3. AOB (bh526r, 14:08:33)
   1. Next week, we will discuss the rest of 2 project proposals, LaaS and Airship installer. All agreed (bh526r, 14:09:13)
   2. Then whenever it is ready, we will discuss revised XCI proposal, if Fatih is willing to make revision based on suggestion, as well as CNTT's input. Time/Day TBD (bh526r, 14:10:29)

Action items

1. (none)

People present (lines said)

1. bh526r (50)
2. fdegir (3)
3. collabot` (3)
4. jmorgan1 (2)
5. trevor_intel (1)
6. mbuil (1)