#opnfv-meeting: Brahmaputra weekly planning meeting

Meeting summary

1. roll call (ChrisPriceAB, 15:01:57)
   1. Frank Brockners (frankbrockners, 15:02:12)
   2. Kevin Luehrs (LSOAPI) (KLuehrs, 15:02:19)
   3. Maryam Tahhan (maryamtahhan, 15:02:19)
   4. Ana Cunha (Yardstick) (anac1, 15:02:23)
   5. Chris Price (ChrisPriceAB, 15:02:25)
   6. Fatih Degirmenci (fdegir, 15:02:30)
   7. Chris Price (opnfvdocs) (ChrisPriceAB, 15:02:34)
   
   
2. rollcall (debrascott, 15:02:56)
   1. Uli (octopus) (uli-k, 15:02:59)
   2. n0ano (n0ano, 15:03:49)
   
   
3. Agenda (debrascott, 15:04:02)
   1. billyoma (OVSNFV) (billyoma, 15:04:06)
   2. https://wiki.opnfv.org/releases/brahmaputra/minutes (debrascott, 15:04:10)
   3. Mark Beierl (StorPerf_ (mbeierl, 15:04:14)
   4. trevor_intel (trevor_intel, 15:04:28)
   5. Bin Hu (IPv6) (bin_, 15:04:34)
   6. Morgan Richomme (Functest) (morgan_orange, 15:05:09)
   
   
4. weekly reports (debrascott, 15:05:51)
   1. Vikram Dham (QTIP) (VikramDham, 15:08:56)
   2. Ashlee Young (ONOSFW) (ashyoung, 15:11:42)
   3. IDEA: Have someone create a dashboard that can attempt to show project status for all known projects? (mbeierl, 15:17:01)
   4. AGREED: the group agrees to stick to etherpad reporting until such time as we have viable and useful tools that may prove worth migrating to (ChrisPriceAB, 15:19:20)
   5. ACTION: have someone create a dashboard that can show all project status (debrascott, 15:19:22)
   6. ACTION: PTL's report weekly on etherpad please. :) (ChrisPriceAB, 15:19:32)
   7. ACTION: Debra to send reminder on Wednesdays (debrascott, 15:19:53)
   
   
5. Pharos (debrascott, 15:21:03)
   1. Do PTLs understand what they need for infrastructure as of today (debrascott, 15:22:30)
   2. for opnfvdocs I just need VM's for compilation and our artifact store. No concerns from my side with minimum infrastructure needs. (ChrisPriceAB, 15:23:25)
   3. Bob M (Armband) still trying to understand what they need, seeking feedback help from experienced projects (debrascott, 15:24:21)
   4. Trevor explains Pharos plans for Brahmaputra (debrascott, 15:24:59)
   5. I actually need to find info on how OPNFV uses Jenkins to check out git projects, run a compile/package script and upload artifacts to the artifact store (mbeierl, 15:25:51)
   6. StorPerf is a new project that does not have anything in place yet. (mbeierl, 15:26:41)
   7. Trevor explaining they are working on user guides, tools, dashboards, booking & reservation systems, all of these in order to make these useful for projects (debrascott, 15:27:36)
   8. Trevor explains that Pharos needs engagement from community lab owners (company has stated they have a lab available to the community) to do this work (debrascott, 15:29:06)
   9. Its not enough to say you have a lab available, you need to provide the resources to participate with the Pharos team (debrascott, 15:30:21)
   10. https://gerrit.opnfv.org/gerrit/#/c/2271/ (fdegir, 15:31:30)
   11. to understand what the Pharos needs to do, they need engagement from individual projects to express what they need from Pharos (debrascott, 15:31:40)
   12. http://artifacts.opnfv.org/octopus/1463/docs/opnfv-jjb-usage.html (fdegir, 15:32:16)
   13. need some consistency across labs in order to help developers use them efficiently (debrascott, 15:33:28)
   14. clarification, labs should be diverse, but consistency is needed in how to access the labs and how to see what is there (debrascott, 15:34:50)
   15. best mechanism to ask Pharos team questions is to join their IRC meeting (debrascott, 15:36:35)
   16. for projects that need specialized configurations for release ready testing that can’t be done in LF lavs, Pharos also needs to create definition of “release ready lab” (debrascott, 15:41:16)
   17. LF labs have required specialized skills to configure & use, how to simplify the required sklls so that the labs are very repeatable experience no matter who is available (debrascott, 15:46:40)
   18. ACTION: PTLs give feedback on how they are using labs today and for Brahmaputra (debrascott, 15:47:17)
   19. ACTION: PTLs give feedback on long term needs for lab infrastructure to Pharos (debrascott, 15:48:08)
   20. ACTION: projects provide feedback as to who they have available to support Pharos/lab activities (debrascott, 15:49:46)
   21. ACTION: Debra to start table on wiki to identify what they need from infrastructure & describe what you need to do in the labs (as specific as possible) (debrascott, 15:51:49)
   22. The dependencies needed for build, test and so on need to be documented as well (fdegir, 15:52:11)

Action items

1. have someone create a dashboard that can show all project status
2. PTL's report weekly on etherpad please. :)
3. Debra to send reminder on Wednesdays
4. PTLs give feedback on how they are using labs today and for Brahmaputra
5. PTLs give feedback on long term needs for lab infrastructure to Pharos
6. projects provide feedback as to who they have available to support Pharos/lab activities
7. Debra to start table on wiki to identify what they need from infrastructure & describe what you need to do in the labs (as specific as possible)

Action items, by person

1. debra
   1. Debra to send reminder on Wednesdays
   2. Debra to start table on wiki to identify what they need from infrastructure & describe what you need to do in the labs (as specific as possible)
2. UNASSIGNED
   1. have someone create a dashboard that can show all project status
   2. PTL's report weekly on etherpad please. :)
   3. PTLs give feedback on how they are using labs today and for Brahmaputra
   4. PTLs give feedback on long term needs for lab infrastructure to Pharos
   5. projects provide feedback as to who they have available to support Pharos/lab activities

People present (lines said)

1. debrascott (24)
2. ChrisPriceAB (21)
3. fdegir (10)
4. mbeierl (8)
5. collabot (6)
6. frankbrockners (5)
7. anac1 (2)
8. morgan_orange (2)
9. KLuehrs (2)
10. uli-k (2)
11. B_Smith (1)
12. n0ano (1)
13. VikramDham (1)
14. ashyoung (1)
15. bin_ (1)
16. trevor_intel (1)
17. billyoma (1)
18. maryamtahhan (1)
19. debra (0)
20. rpaik (0)