#opnfv-meeting: Brahmaputra Release AM/EU

Meeting summary

1. roll call (debrascott, 15:57:08)
   1. Mark Beierl (StorPerf) (mbeierl, 16:00:02)
   2. Jonas Bjurel ([1]JonasB, 16:00:09)
   3. Don Dugger (KVM) (n0ano, 16:00:19)
   4. Ana Cunha (Yardstick) (anac, 16:00:40)
   5. Fatih Degirmenci (Releng) (fdegir, 16:00:49)
   6. Morgan Richomme (Functest) (morgan_orange, 16:01:19)
   7. Chris Price (opnfvdocs) (ChrisPriceAB, 16:01:24)
   8. Maryam Tahhan (mtahhan_, 16:01:35)
   9. Frank Brockners (frankbrockners, 16:02:48)
   10. Bin Hu (IPv6) (bin_, 16:03:20)
   11. Dave Neary (dneary, 16:03:33)
   12. currently 3 PODS for operations +1 under verification (on 8 expected) (morgan_orange, 16:04:21)
   13. Arno experience: installers mutualization on 1 POD is not a good solution... (morgan_orange, 16:05:06)
   14. Uli Kleber, Octopus (uli-k_, 16:06:16)
   15. Bryan Sullivan (bryan_att, 16:06:41)
   16. Billy O'Mahony (billyoma, 16:11:14)
   17. all install tools must support the "arno" scenario (ChrisPriceAB, 16:14:14)
   18. deploy tools also need to identify the additional scenario's they intend to support (ChrisPriceAB, 16:14:30)
   19. preferably not more than 5 scenario's per installer for Brahmaputra. (ChrisPriceAB, 16:14:49)
   20. Jonas adds that once the installers have identified their scenario's we should group them to simplify testing across the matrixes (ChrisPriceAB, 16:15:28)
   21. first priority secure Arno scenario (Openstack + ODL) (morgan_orange, 16:18:24)
   22. second scenario : list additional scenarios (morgan_orange, 16:18:39)
   23. It is important to state the obvious: we have to have common scenario format (fdegir, 16:23:03)
   24. Because CI and test projects need to have one/common way to specify and consume scenarios (fdegir, 16:23:24)
   25. No matter what the scenario is, the format must be common (fdegir, 16:24:09)
   26. POD/inventory/network configurations have lower priority comparing the scenario definition formats (fdegir, 16:24:35)
   27. Just to note that the jobs on jenkins with scenarios are just placeholders and will probably change whenever first scenario format is realized by any of the installers (fdegir, 16:28:30)
   28. deploy tools to provide a priority list of target scenario's. (ChrisPriceAB, 16:37:53)
   29. Pharos to provide available resources and a priority list of actions ongoing (ChrisPriceAB, 16:38:09)
   30. Intel PODs and LF POD1 might become available towards the end of the week (fdegir, 16:38:35)
   31. Ericsson POD2 will be ready (fdegir, 16:38:55)
   32. The most crucial PODs are LF POD1 for Apex and Intel POD5 for Joid (fdegir, 16:39:35)
   33. feature/component projects need to clarify scenario dependencies and plan to configure features according to the installer tool schedules (ChrisPriceAB, 16:39:37)
   34. feature project stable branch cutting to occur on Friday 7th January (ChrisPriceAB, 16:41:55)
   35. projects should close feature development as of today. (the days between are buffer) (ChrisPriceAB, 16:42:30)
   36. install tools, infra projects, and test projects have an offset for code freeze and branch cutting (ChrisPriceAB, 16:45:31)
   37. https://etherpad.opnfv.org/p/steps_to_brahmaputra (fdegir, 16:45:47)
   38. daily scrum on #opnfv-release IRC chanel (ChrisPriceAB, 16:48:50)
   39. Test and Installer projects, please check the link to see the correct offset (fdegir, 16:49:07)
   40. daily scrum meetings: 30 minutes at 06:30 PST on IRC #opnfv-release (ChrisPriceAB, 16:52:00)

Action items

1. (none)

People present (lines said)

1. ChrisPriceAB (27)
2. fdegir (21)
3. bin_ (7)
4. morgan_orange (5)
5. debrascott (3)
6. trevor_intel (3)
7. collabot` (3)
8. mbeierl (2)
9. frankbrockners (1)
10. billyoma (1)
11. n0ano (1)
12. mdgray (1)
13. aricg (1)
14. dneary (1)
15. bryan_att (1)
16. uli-k_ (1)
17. anac (1)
18. mtahhan_ (1)
19. z0d (1)
20. [1]JonasB (1)