15:56:56 #startmeeting Brahmaputra Release AM/EU 15:56:56 Meeting started Tue Jan 5 15:56:56 2016 UTC. The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:56:56 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:56:56 The meeting name has been set to 'brahmaputra_release_am_eu' 15:57:08 #topic roll call 16:00:02 #info Mark Beierl (StorPerf) 16:00:09 <[1]JonasB> #info Jonas Bjurel 16:00:19 #info Don Dugger (KVM) 16:00:40 #info Ana Cunha (Yardstick) 16:00:49 #info Fatih Degirmenci (Releng) 16:01:19 #info Morgan Richomme (Functest) 16:01:24 #info Chris Price (opnfvdocs) 16:01:35 #info Maryam Tahhan 16:01:42 * ChrisPriceAB is looking for the gotomeeting link 16:02:41 ChrisPriceAB: https://global.gotomeeting.com/join/341956909 16:02:48 #info Frank Brockners 16:03:20 #info Bin Hu (IPv6) 16:03:33 #info Dave Neary 16:03:50 I am on another call, and here on IRC only 16:03:53 thanks mark 16:04:21 #info currently 3 PODS for operations +1 under verification (on 8 expected) 16:05:06 #info Arno experience: installers mutualization on 1 POD is not a good solution... 16:06:16 #info Uli Kleber, Octopus 16:06:41 #info Bryan Sullivan 16:10:58 info Mark Gray 16:11:14 #info Billy O'Mahony 16:12:56 aricg: ping 16:13:52 z0d: hi 16:14:14 #info all install tools must support the "arno" scenario 16:14:30 #info deploy tools also need to identify the additional scenario's they intend to support 16:14:49 #info preferably not more than 5 scenario's per installer for Brahmaputra. 16:15:28 #info Jonas adds that once the installers have identified their scenario's we should group them to simplify testing across the matrixes 16:15:48 sorrt bin_ forgot you were not on audio 16:18:24 #info first priority secure Arno scenario (Openstack + ODL) 16:18:39 #info second scenario : list additional scenarios 16:23:03 #info It is important to state the obvious: we have to have common scenario format 16:23:24 #info Because CI and test projects need to have one/common way to specify and consume scenarios 16:24:09 #info No matter what the scenario is, the format must be common 16:24:35 #info POD/inventory/network configurations have lower priority comparing the scenario definition formats 16:25:22 Chris, question for me? 16:28:30 #info 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 16:33:20 no bin_ just letting you know we were doing some scribing for the IRC only members 16:34:12 I see, thank you 16:37:53 #info deploy tools to provide a priority list of target scenario's. 16:38:09 #info Pharos to provide available resources and a priority list of actions ongoing 16:38:35 #info Intel PODs and LF POD1 might become available towards the end of the week 16:38:55 #info Ericsson POD2 will be ready 16:39:35 #info The most crucial PODs are LF POD1 for Apex and Intel POD5 for Joid 16:39:37 #info feature/component projects need to clarify scenario dependencies and plan to configure features according to the installer tool schedules 16:41:01 fdegir: We will get onto POD5 today as top priority 16:41:55 #info feature project stable branch cutting to occur on Friday 7th January 16:42:30 #info projects should close feature development as of today. (the days between are buffer) 16:42:46 (not add more code buffer) 16:42:56 (fix the bugs buffer) 16:43:02 :) 16:43:09 Friday is 8th, and 7th is Thursday 16:43:27 00:01 Friday morning 16:43:28 January 7th, 00:00 UTC 16:43:49 isn't it Thursday morning? 16:43:50 :) 16:43:59 the day after tomorrow 16:44:29 tomorrow is last day to get all the patches submitted to master 16:45:01 (excluding installer and test projects) 16:45:17 and docs? 16:45:31 including docs 16:45:31 #info install tools, infra projects, and test projects have an offset for code freeze and branch cutting 16:45:47 #link https://etherpad.opnfv.org/p/steps_to_brahmaputra 16:45:48 offset time limit of? 16:46:01 test projects 1 week, installers 2 weeks 16:46:39 thanks fdegir 16:47:21 * fdegir might be mistaken regarding deploy tools offset 16:47:40 it says 1 week extra there for deploy and test projects as oppose to what I stated 16:48:50 #info daily scrum on #opnfv-release IRC chanel 16:49:07 #info Test and Installer projects, please check the link to see the correct offset 16:49:10 * ChrisPriceAB doesn't like his calendar 16:49:21 so that I don't misinform anyone 16:52:00 #info daily scrum meetings: 30 minutes at 06:30 PST on IRC #opnfv-release 16:52:07 I am ok 16:52:15 not sure why you can't hear me 16:52:32 thanks trevor_intel 16:53:11 bin_ is that time OK for you? as above 16:55:05 I'm all good for today 16:55:39 #endmeeting