16:00:35 <dmcbride> #startmeeting OPNFV release
16:00:35 <collabot`> Meeting started Tue Nov  8 16:00:35 2016 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:35 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:00:35 <collabot`> The meeting name has been set to 'opnfv_release'
16:00:58 <dmcbride> #topic roll call
16:01:08 <jose_lausuch1> #info Jose Lausuch
16:01:19 <jmorgan1> #info Jack Morgan
16:01:24 <bryan_att> #info Bryan Sullivan
16:01:26 <leifmadsen> #info Leif Madsen
16:01:26 <StuartMackie> #info Stuart Mackie
16:01:28 <aricg> #info Aric Gardner
16:01:28 <fzhadaev> #info Fedor Zhadaev
16:01:30 <dmcbride> #info David McBride
16:01:33 <sofiawallin> #info Sofia Wallin
16:02:33 <kongwei> #info kongwei
16:02:46 <morgan_orange> #info Morgan Richomme
16:04:38 <leifmadsen> this topic seems off topic...
16:06:12 <uli-k> #info Uli Kleber
16:08:43 <jose_lausuch1> #link https://build.opnfv.org/ci/view/functest/job/functest-fuel-baremetal-daily-colorado/
16:08:44 <dmcbride> #topic Colorado 2.0
16:09:00 <jose_lausuch1> http://testresults.opnfv.org/reporting/functest/release/colorado/index-status-fuel.html
16:09:08 <dmcbride> #info Fuel is now stable
16:10:08 <jose_lausuch> the guys are working on SFC and are targeting colorado 3.0
16:10:29 <dmcbride> #info fdio issues will not be included in Col 2.0
16:10:31 <jose_lausuch> SFC scenario is already Boron
16:10:45 <jose_lausuch> but SR1 might be uplifted
16:11:05 <dmcbride> #info ongoing problems with SFC related to ODL
16:12:24 <dmcbride> #info issue identified by fzhadaev was resolved by aricg
16:12:39 <dmcbride> #info fzhadaev acknowledges that he has seen the fix
16:12:44 <aricg> #info release documentation now being put in the correct directory in google storage
16:13:58 <dmcbride> #topic Danube
16:17:48 <dmcbride> #info can we combine scenarios?
16:18:29 <dmcbride> #info uli-k suggests keeping scenarios separate until close to release, then combining
16:20:34 <dmcbride> #info jonas suggests having all scenarios associated with an installer handled by one scenario owner
16:25:18 <bryan_att> e.g. for Fuel it could be various types of Bears
16:25:19 <jose_lausuch> I think it could contain at least some idea about what it contains (i.e. ODL, ... )
16:26:09 <bryan_att> For Apex, mountains
16:26:32 <bryan_att> For Joid, types of magic...
16:27:04 <aricg> ^ +1
16:29:40 <jose_lausuch> or same projects trying to develop/integrate more test cases
16:33:29 <dmcbride> #topic escalator / Daisy
16:34:04 <jose_lausuch> fatih is on vacation, yes
16:34:25 <jmorgan1> jose_lausuch: must be nice ;)
16:34:55 <aricg> opnfv-helpdesk@rt.linuxfoundation.org
16:36:42 <jose_lausuch> is daisy already running in CI ?
16:37:54 <jmorgan1> jose_lausuch: not that I know of, we still need to identify two CI POD for this installer
16:38:41 <jose_lausuch> ok, then we can't add it to the Functest dashboard yet :) as soon as we see Functest results for Daisy, we will include it
16:46:11 <dmcbride> #info jmorgan1 points out that approval of Escalator dependent upon providing 2 PODs
16:46:26 <jose_lausuch> you can always use the functest smoke to verify the installation
16:46:40 <jose_lausuch> but does escalator have a specific "feature" to be verified?
16:52:53 <jmorgan1> from my understanding, daisy is doing virtual deployemnt, do they plan to support  bare metal deployment?
17:03:51 <morgan_orange> jose_lausuch: I think if escalator is doing what I think it is doing we should have a test 1) get SUT version 2) run escalator 3) check SUT version to be sure that each components have been ugraded . We should also be able to run a test during escalator processing to be sure we did not lose things during the migration...
20:59:58 <AAR> hey , can anyone tell when will the Colorado release 2.0 will be out ? thanks
23:20:34 <dmcbride> #endmeeting