========================================= #opnfv-meeting: Brahmaputra Release AM/EU ========================================= Meeting started by debrascott at 15:56:56 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-01-05-15.56.log.html . Meeting summary --------------- * roll call (debrascott, 15:57:08) * Mark Beierl (StorPerf) (mbeierl, 16:00:02) * Jonas Bjurel ([1]JonasB, 16:00:09) * Don Dugger (KVM) (n0ano, 16:00:19) * Ana Cunha (Yardstick) (anac, 16:00:40) * Fatih Degirmenci (Releng) (fdegir, 16:00:49) * Morgan Richomme (Functest) (morgan_orange, 16:01:19) * Chris Price (opnfvdocs) (ChrisPriceAB, 16:01:24) * Maryam Tahhan (mtahhan_, 16:01:35) * Frank Brockners (frankbrockners, 16:02:48) * Bin Hu (IPv6) (bin_, 16:03:20) * Dave Neary (dneary, 16:03:33) * currently 3 PODS for operations +1 under verification (on 8 expected) (morgan_orange, 16:04:21) * Arno experience: installers mutualization on 1 POD is not a good solution... (morgan_orange, 16:05:06) * Uli Kleber, Octopus (uli-k_, 16:06:16) * Bryan Sullivan (bryan_att, 16:06:41) * Billy O'Mahony (billyoma, 16:11:14) * all install tools must support the "arno" scenario (ChrisPriceAB, 16:14:14) * deploy tools also need to identify the additional scenario's they intend to support (ChrisPriceAB, 16:14:30) * preferably not more than 5 scenario's per installer for Brahmaputra. (ChrisPriceAB, 16:14:49) * 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) * first priority secure Arno scenario (Openstack + ODL) (morgan_orange, 16:18:24) * second scenario : list additional scenarios (morgan_orange, 16:18:39) * It is important to state the obvious: we have to have common scenario format (fdegir, 16:23:03) * Because CI and test projects need to have one/common way to specify and consume scenarios (fdegir, 16:23:24) * No matter what the scenario is, the format must be common (fdegir, 16:24:09) * POD/inventory/network configurations have lower priority comparing the scenario definition formats (fdegir, 16:24:35) * 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) * deploy tools to provide a priority list of target scenario's. (ChrisPriceAB, 16:37:53) * Pharos to provide available resources and a priority list of actions ongoing (ChrisPriceAB, 16:38:09) * Intel PODs and LF POD1 might become available towards the end of the week (fdegir, 16:38:35) * Ericsson POD2 will be ready (fdegir, 16:38:55) * The most crucial PODs are LF POD1 for Apex and Intel POD5 for Joid (fdegir, 16:39:35) * feature/component projects need to clarify scenario dependencies and plan to configure features according to the installer tool schedules (ChrisPriceAB, 16:39:37) * feature project stable branch cutting to occur on Friday 7th January (ChrisPriceAB, 16:41:55) * projects should close feature development as of today. (the days between are buffer) (ChrisPriceAB, 16:42:30) * install tools, infra projects, and test projects have an offset for code freeze and branch cutting (ChrisPriceAB, 16:45:31) * LINK: https://etherpad.opnfv.org/p/steps_to_brahmaputra (fdegir, 16:45:47) * daily scrum on #opnfv-release IRC chanel (ChrisPriceAB, 16:48:50) * Test and Installer projects, please check the link to see the correct offset (fdegir, 16:49:07) * daily scrum meetings: 30 minutes at 06:30 PST on IRC #opnfv-release (ChrisPriceAB, 16:52:00) Meeting ended at 16:55:39 UTC. People present (lines said) --------------------------- * ChrisPriceAB (27) * fdegir (21) * bin_ (7) * morgan_orange (5) * debrascott (3) * trevor_intel (3) * collabot` (3) * mbeierl (2) * frankbrockners (1) * billyoma (1) * n0ano (1) * mdgray (1) * aricg (1) * dneary (1) * bryan_att (1) * uli-k_ (1) * anac (1) * mtahhan_ (1) * z0d (1) * [1]JonasB (1) Generated by `MeetBot`_ 0.1.4