Monday, 2015-06-29

*** Longgeek has quit IRC00:00
*** stevemar has quit IRC00:10
*** mmedvede has joined #openstack-meeting00:10
*** stevemar has joined #openstack-meeting00:10
*** trey has quit IRC00:10
*** JRobinson__ is now known as JRobinson__afk00:11
*** trey has joined #openstack-meeting00:16
*** stevemar has quit IRC00:19
*** stevemar has joined #openstack-meeting00:20
*** miguelgrinberg has quit IRC00:26
*** darrenc is now known as darrenc_afk00:26
*** DericHorn-HP has joined #openstack-meeting00:28
*** eliqiao has joined #openstack-meeting00:30
*** mmedvede has quit IRC00:31
*** bill_az has quit IRC00:36
*** trey has quit IRC00:36
*** eliqiao has quit IRC00:37
*** sankarshan_away is now known as sankarshan00:37
*** eliqiao has joined #openstack-meeting00:37
*** PrashantS has quit IRC00:38
*** PrashantS has joined #openstack-meeting00:38
*** DericHorn-HP has quit IRC00:40
*** ddieter__ has quit IRC00:41
*** PrashantS has quit IRC00:43
*** banix has quit IRC00:46
*** JRobinson__afk is now known as JRobinson__00:47
*** eliqiao1 has joined #openstack-meeting00:51
*** eliqiao has quit IRC00:53
*** darrenc_afk is now known as darrenc00:58
*** arvinchou_ has quit IRC01:06
*** dmacpher has joined #openstack-meeting01:14
*** xingchao_ has joined #openstack-meeting01:26
*** banix has joined #openstack-meeting01:27
*** miguelgrinberg has joined #openstack-meeting01:28
*** markvoelker has joined #openstack-meeting01:30
*** markvoelker has quit IRC01:35
*** vilobhmm has quit IRC01:35
*** puranamr has quit IRC01:37
*** Yanyanhu has joined #openstack-meeting01:39
*** jasondotstar has joined #openstack-meeting01:40
*** ddieterly has joined #openstack-meeting01:42
*** Yanyanhu has quit IRC01:45
*** Yanyanhu has joined #openstack-meeting01:45
*** puranamr has joined #openstack-meeting01:45
*** asettle is now known as asettle-afk01:46
*** ddieterly has quit IRC01:46
*** vilobhmm has joined #openstack-meeting01:49
*** Longgeek has joined #openstack-meeting01:59
*** Sukhdev has joined #openstack-meeting02:01
*** stevemar has quit IRC02:07
*** stevemar has joined #openstack-meeting02:08
*** Longgeek has quit IRC02:11
*** VW_ has joined #openstack-meeting02:12
*** nadeem has joined #openstack-meeting02:14
*** yamamoto has joined #openstack-meeting02:18
*** ddieterly has joined #openstack-meeting02:22
*** xingchao_ has quit IRC02:23
*** stevemar has quit IRC02:30
*** stevemar has joined #openstack-meeting02:31
*** xingchao_ has joined #openstack-meeting02:38
*** neelashah1 has joined #openstack-meeting02:42
*** mwagner_afk has joined #openstack-meeting02:43
*** aranjan has joined #openstack-meeting02:49
*** neelashah1 has quit IRC02:55
*** larainema has joined #openstack-meeting02:55
*** haomaiwang has joined #openstack-meeting02:59
*** SumitNaiksatam has quit IRC03:01
*** SumitNaiksatam has joined #openstack-meeting03:01
*** nadeem has quit IRC03:05
*** asettle-afk is now known as asettle03:07
*** Longgeek has joined #openstack-meeting03:07
*** achanda has joined #openstack-meeting03:11
*** tobe has joined #openstack-meeting03:12
*** jckasper has quit IRC03:13
*** VW_ has quit IRC03:14
*** sigmavirus24_awa is now known as sigmavirus2403:15
*** achanda has quit IRC03:18
*** markvoelker has joined #openstack-meeting03:19
*** haomaiwang has quit IRC03:19
*** haomaiwang has joined #openstack-meeting03:19
*** Longgeek has quit IRC03:20
*** VW_ has joined #openstack-meeting03:20
*** markvoelker has quit IRC03:23
*** aranjan has quit IRC03:26
*** asettle has quit IRC03:29
*** asettle has joined #openstack-meeting03:29
*** sbalukoff has quit IRC03:32
*** sdake has joined #openstack-meeting03:32
*** jasondotstar has quit IRC03:32
*** jasondotstar has joined #openstack-meeting03:33
*** haomaiwang has quit IRC03:34
*** vilobhmm has quit IRC03:34
*** sdake has quit IRC03:36
*** haomaiwang has joined #openstack-meeting03:37
*** sigmavirus24 is now known as sigmavirus24_awa03:38
*** sigmavirus24_awa is now known as sigmavirus2403:39
*** sdake has joined #openstack-meeting03:39
*** ddieterly has quit IRC03:39
*** epico has joined #openstack-meeting03:40
*** baoli has quit IRC03:46
*** baoli has joined #openstack-meeting03:48
*** baoli has quit IRC03:48
*** baoli has joined #openstack-meeting03:48
*** sigmavirus24 is now known as sigmavirus24_awa03:49
*** baoli has quit IRC03:49
*** puranamr has quit IRC03:51
*** aimon_ has joined #openstack-meeting03:51
*** yamada-h has joined #openstack-meeting03:51
*** coolsvap|away is now known as coolsvap03:52
*** armax has joined #openstack-meeting03:54
*** aimon has quit IRC03:54
*** tobe has quit IRC03:55
*** yamada-h has quit IRC03:55
*** tobe has joined #openstack-meeting03:56
*** tobe has quit IRC03:56
*** rushiagr_away is now known as rushiagr03:57
*** aranjan has joined #openstack-meeting03:58
*** sdake_ has joined #openstack-meeting03:58
*** tobe has joined #openstack-meeting03:59
*** Sukhdev has quit IRC04:01
*** sdake has quit IRC04:02
*** rushiagr is now known as rushiagr_away04:03
*** stevemar has quit IRC04:03
*** stevemar has joined #openstack-meeting04:04
*** comay has quit IRC04:06
*** JRobinson__ is now known as JRobinson__afk04:09
*** Apoorva has joined #openstack-meeting04:10
*** puranamr has joined #openstack-meeting04:11
*** tobe has quit IRC04:13
*** haomaiwang has quit IRC04:13
*** puranamr has quit IRC04:16
*** banix has quit IRC04:20
*** Apoorva has quit IRC04:20
*** xingchao_ has quit IRC04:21
*** xingchao_ has joined #openstack-meeting04:23
*** xingchao_ has quit IRC04:23
*** irenab has quit IRC04:27
*** DericHorn-HP has joined #openstack-meeting04:30
*** zhhuabj_ has quit IRC04:35
*** ddieterly has joined #openstack-meeting04:40
*** DericHorn-HP has quit IRC04:41
*** ddieterly has quit IRC04:44
*** zhhuabj_ has joined #openstack-meeting04:51
*** doude has quit IRC04:57
*** VW_ has quit IRC04:58
*** lpeer has joined #openstack-meeting05:00
*** sudipto has joined #openstack-meeting05:01
*** DericHorn-HP has joined #openstack-meeting05:02
*** DericHorn-HP has quit IRC05:06
*** JRobinson__afk is now known as JRobinson__05:07
*** markvoelker has joined #openstack-meeting05:08
*** puranamr has joined #openstack-meeting05:08
*** asettle has quit IRC05:10
*** markvoelker has quit IRC05:12
*** Longgeek has joined #openstack-meeting05:17
*** ociuhandu has quit IRC05:21
*** Longgeek has quit IRC05:25
*** Longgeek has joined #openstack-meeting05:25
*** puranamr has quit IRC05:26
*** Murali has joined #openstack-meeting05:33
*** Longgeek has quit IRC05:34
*** Longgeek has joined #openstack-meeting05:34
*** ddieterly has joined #openstack-meeting05:41
*** etoews has quit IRC05:43
*** ddieterly has quit IRC05:45
*** puranamr has joined #openstack-meeting05:46
*** SridharG has joined #openstack-meeting05:47
*** prazumovsky has joined #openstack-meeting05:49
*** puranamr has quit IRC05:51
*** jasondotstar has quit IRC05:53
*** Murali has quit IRC05:54
*** tobe has joined #openstack-meeting05:56
*** tobe has quit IRC05:58
*** tobe_ has joined #openstack-meeting05:58
*** harshs has joined #openstack-meeting05:59
*** harshs has left #openstack-meeting05:59
*** DericHorn-HP has joined #openstack-meeting06:01
*** ub has joined #openstack-meeting06:04
*** DericHorn-HP has quit IRC06:05
*** adiantum has quit IRC06:09
*** larainema has quit IRC06:11
*** larainema has joined #openstack-meeting06:12
*** zhhuabj_ has quit IRC06:12
*** jtomasek has joined #openstack-meeting06:13
*** yamada-h has joined #openstack-meeting06:13
*** sahid has joined #openstack-meeting06:14
*** stevemar has quit IRC06:16
*** stevemar has joined #openstack-meeting06:16
*** xingchao_ has joined #openstack-meeting06:17
*** sbalukoff has joined #openstack-meeting06:22
*** numan has joined #openstack-meeting06:23
*** armax has quit IRC06:26
*** _nadya_ has joined #openstack-meeting06:26
*** yamada-h has quit IRC06:27
*** zhhuabj_ has joined #openstack-meeting06:29
*** stevemar has quit IRC06:30
*** watanabe_isao has joined #openstack-meeting06:32
*** scheuran has joined #openstack-meeting06:34
*** adiantum has joined #openstack-meeting06:34
*** dmacpher has quit IRC06:36
*** lufix has joined #openstack-meeting06:37
*** adiantum has quit IRC06:42
*** ddieterly has joined #openstack-meeting06:42
*** arnaud____ has joined #openstack-meeting06:43
*** ddieterly has quit IRC06:46
*** haomaiwang has joined #openstack-meeting06:46
*** irenab has joined #openstack-meeting06:51
*** jlanoux has joined #openstack-meeting06:55
*** markvoelker has joined #openstack-meeting06:56
*** yamada-h has joined #openstack-meeting06:57
*** mpaolino has joined #openstack-meeting06:59
*** safchain has joined #openstack-meeting06:59
*** VW_ has joined #openstack-meeting06:59
*** ociuhandu has joined #openstack-meeting07:01
*** markvoelker has quit IRC07:01
*** yamada-h has quit IRC07:02
*** VW_ has quit IRC07:03
*** mpaolino has quit IRC07:04
*** ociuhandu has quit IRC07:06
*** breitz1 has joined #openstack-meeting07:08
*** breitz has quit IRC07:08
*** yamada-h has joined #openstack-meeting07:11
*** yamada-h has quit IRC07:11
*** Longgeek has quit IRC07:13
*** Longgeek has joined #openstack-meeting07:13
*** ociuhandu has joined #openstack-meeting07:14
*** elo has joined #openstack-meeting07:15
*** mpaolino has joined #openstack-meeting07:17
*** amotoki has joined #openstack-meeting07:17
*** ildikov has quit IRC07:20
*** aranjan has quit IRC07:22
*** mpaolino has quit IRC07:22
*** mrunge has joined #openstack-meeting07:24
*** maishsk_afk has joined #openstack-meeting07:25
*** maishsk_afk is now known as maishsk07:26
*** lsmola has joined #openstack-meeting07:26
*** egallen has joined #openstack-meeting07:26
*** yamamoto has quit IRC07:27
*** zz_ttrifonov is now known as ttrifonov07:27
*** jlanoux has quit IRC07:29
*** stevemar has joined #openstack-meeting07:30
*** yamamoto has joined #openstack-meeting07:31
*** epico has quit IRC07:32
*** stevemar has quit IRC07:33
*** mpaolino has joined #openstack-meeting07:36
*** devvesa has joined #openstack-meeting07:36
*** epico has joined #openstack-meeting07:36
*** mpaolino has quit IRC07:42
*** jtomasek has quit IRC07:42
*** ddieterly has joined #openstack-meeting07:43
*** neeti has joined #openstack-meeting07:44
*** ddieterly has quit IRC07:47
*** pnavarro|off has joined #openstack-meeting07:50
*** saggi has quit IRC07:51
*** pnavarro|off has quit IRC07:51
*** pnavarro has joined #openstack-meeting07:52
*** mpaolino has joined #openstack-meeting07:55
*** arnaud____ has quit IRC07:57
*** toscalix has joined #openstack-meeting07:59
*** snikitin_ has left #openstack-meeting08:01
*** jlanoux has joined #openstack-meeting08:01
*** hashar has joined #openstack-meeting08:02
*** mpaolino has quit IRC08:02
*** xingchao_ has quit IRC08:02
*** numan has quit IRC08:07
*** hashar has quit IRC08:07
*** numan has joined #openstack-meeting08:08
*** ildikov has joined #openstack-meeting08:08
*** hashar has joined #openstack-meeting08:11
*** yamada-h has joined #openstack-meeting08:12
*** ygbo has joined #openstack-meeting08:13
*** mpaolino has joined #openstack-meeting08:15
*** yamada-h has quit IRC08:17
*** xingchao_ has joined #openstack-meeting08:19
*** mpaolino has quit IRC08:21
*** hichihara has quit IRC08:22
*** puranamr has joined #openstack-meeting08:22
*** aranjan has joined #openstack-meeting08:23
*** dguerri` is now known as dguerri08:23
*** Gerald_K has joined #openstack-meeting08:24
*** puranamr has quit IRC08:25
*** aranjan has quit IRC08:28
*** jtomasek has joined #openstack-meeting08:28
*** larainema has quit IRC08:28
*** larainema has joined #openstack-meeting08:28
*** yassine has joined #openstack-meeting08:32
*** derekh has joined #openstack-meeting08:33
*** xingchao_ has quit IRC08:34
*** phil has joined #openstack-meeting08:35
*** mpaolino has joined #openstack-meeting08:35
*** phil is now known as Guest5768608:35
*** sudipto has quit IRC08:36
*** sudipto has joined #openstack-meeting08:38
*** Longgeek has quit IRC08:38
*** ityaptin has joined #openstack-meeting08:40
*** watanabe_isao has quit IRC08:41
*** mpaolino has quit IRC08:41
*** ddieterly has joined #openstack-meeting08:43
*** beagles has quit IRC08:44
*** yamada-h has joined #openstack-meeting08:44
*** markvoelker has joined #openstack-meeting08:45
*** puranamr has joined #openstack-meeting08:45
*** mrmartin has joined #openstack-meeting08:46
*** JRobinson__ has quit IRC08:47
*** kbyrne has quit IRC08:47
*** jhenner has joined #openstack-meeting08:48
*** ddieterly has quit IRC08:48
*** markvoelker has quit IRC08:50
*** puranamr has quit IRC08:50
*** dguitarbite has joined #openstack-meeting08:53
*** mpaolino has joined #openstack-meeting08:53
*** kbyrne has joined #openstack-meeting08:53
*** ndipanov has joined #openstack-meeting08:54
*** afazekas_ has joined #openstack-meeting08:56
*** mpaolino has quit IRC09:00
*** maishsk has quit IRC09:02
*** maishsk_afk has joined #openstack-meeting09:03
*** pelix has joined #openstack-meeting09:03
*** maishsk_afk has quit IRC09:04
*** maishsk_afk has joined #openstack-meeting09:04
*** maishsk_afk is now known as maishsk09:05
*** doude has joined #openstack-meeting09:08
*** belmoreira has joined #openstack-meeting09:10
*** yamamoto has quit IRC09:11
*** mpaolino has joined #openstack-meeting09:11
*** Longgeek has joined #openstack-meeting09:12
*** maishsk has quit IRC09:15
*** sudipto has quit IRC09:16
*** mpaolino has quit IRC09:17
*** stevemar has joined #openstack-meeting09:20
*** mrmartin has quit IRC09:20
*** lpeer_ has joined #openstack-meeting09:21
*** stevemar has quit IRC09:22
*** lpeer has quit IRC09:23
*** aranjan has joined #openstack-meeting09:23
*** puranamr has joined #openstack-meeting09:26
*** aranjan has quit IRC09:28
*** breitz1 has quit IRC09:28
*** yamamoto has joined #openstack-meeting09:29
*** mpaolino has joined #openstack-meeting09:29
*** fawadkhaliq has joined #openstack-meeting09:30
*** henrynash has quit IRC09:30
*** breitz has joined #openstack-meeting09:30
*** puranamr has quit IRC09:32
*** mpaolino has quit IRC09:36
*** maishsk_afk has joined #openstack-meeting09:44
*** ddieterly has joined #openstack-meeting09:44
*** maishsk_afk has quit IRC09:47
*** mpaolino has joined #openstack-meeting09:48
*** ddieterly has quit IRC09:49
*** puranamr has joined #openstack-meeting09:53
*** puranamr has quit IRC09:57
*** Yanyanhu has quit IRC09:59
*** sudipto has joined #openstack-meeting10:00
*** sdake_ is now known as sdake10:01
*** lpeer__ has joined #openstack-meeting10:02
*** uschreiber_ has joined #openstack-meeting10:03
*** uschreiber_ has quit IRC10:05
*** lpeer_ has quit IRC10:06
*** yamahata has quit IRC10:16
*** Murali has joined #openstack-meeting10:18
*** aranjan has joined #openstack-meeting10:24
*** henrynash has joined #openstack-meeting10:26
*** haomaiwang has quit IRC10:26
*** yamada-h has quit IRC10:27
*** aranjan has quit IRC10:29
*** prazumovsky has quit IRC10:32
*** Gerald_K has quit IRC10:33
*** markvoelker has joined #openstack-meeting10:34
*** _nadya_ has quit IRC10:34
*** _nadya_ has joined #openstack-meeting10:35
*** lufix has quit IRC10:35
*** egallen has quit IRC10:35
*** epico has quit IRC10:36
*** rossella_s has quit IRC10:37
*** dims has joined #openstack-meeting10:37
*** rossella_s has joined #openstack-meeting10:37
*** lufix has joined #openstack-meeting10:37
*** _nadya_ has quit IRC10:39
*** markvoelker has quit IRC10:40
*** henrynash has quit IRC10:42
*** IanGovett has joined #openstack-meeting10:42
*** subscope has joined #openstack-meeting10:42
*** ddieterly has joined #openstack-meeting10:45
*** henrynash has joined #openstack-meeting10:47
*** afazekas__ has joined #openstack-meeting10:49
*** ddieterly has quit IRC10:50
*** jhenner1 has joined #openstack-meeting10:50
*** subscope has quit IRC10:52
*** afazekas_ has quit IRC10:53
*** jhenner has quit IRC10:53
*** fawadkhaliq has quit IRC10:53
*** b3nt_pin has joined #openstack-meeting10:54
*** b3nt_pin is now known as Guest3867010:54
*** afazekas__ has quit IRC10:54
*** egallen has joined #openstack-meeting10:57
*** yamada-h has joined #openstack-meeting10:57
*** hogepodge has quit IRC10:58
*** hogepodge has joined #openstack-meeting11:00
*** _nadya_ has joined #openstack-meeting11:02
*** yamada-h has quit IRC11:02
*** samueldmq has joined #openstack-meeting11:05
*** afazekas__ has joined #openstack-meeting11:07
*** lpeer has joined #openstack-meeting11:08
*** Gerald_K has joined #openstack-meeting11:08
*** lpeer__ has quit IRC11:08
*** yamamoto has quit IRC11:08
*** ildikov has quit IRC11:08
*** hashar has quit IRC11:10
*** coolsvap is now known as coolsvap|away11:10
*** Guest38670 is now known as beagles11:12
*** kgroves has joined #openstack-meeting11:15
*** claudiub has joined #openstack-meeting11:17
*** henrynash has quit IRC11:18
*** mpaolino has quit IRC11:20
*** ildikov has joined #openstack-meeting11:22
*** aranjan has joined #openstack-meeting11:25
*** egallen has quit IRC11:26
*** baoli has joined #openstack-meeting11:28
*** dguerri is now known as dguerri`11:28
*** aranjan has quit IRC11:29
*** baoli has quit IRC11:30
*** baoli has joined #openstack-meeting11:30
*** markvoelker has joined #openstack-meeting11:35
*** fawadkhaliq has joined #openstack-meeting11:36
*** lpeer_ has joined #openstack-meeting11:37
*** maishsk_afk has joined #openstack-meeting11:37
*** maishsk_afk is now known as maishsk11:37
*** markvoelker has quit IRC11:40
*** lpeer has quit IRC11:40
*** baoli has quit IRC11:41
*** sdake has quit IRC11:43
*** ddieterly has joined #openstack-meeting11:46
*** fawadkhaliq has quit IRC11:46
*** egallen has joined #openstack-meeting11:48
*** dguerri` is now known as dguerri11:48
*** kgroves has quit IRC11:49
*** tobe_ has quit IRC11:49
*** ddieterly has quit IRC11:51
*** tochi has quit IRC11:51
*** _nadya_ has quit IRC11:52
*** hashar has joined #openstack-meeting11:52
*** _nadya_ has joined #openstack-meeting11:52
*** markvoelker has joined #openstack-meeting11:55
*** ildikov_ has joined #openstack-meeting11:56
*** hogepodge has quit IRC11:56
*** _nadya_ has quit IRC11:57
*** ildikov has quit IRC11:57
*** yamamoto has joined #openstack-meeting12:01
*** hogepodge has joined #openstack-meeting12:02
*** mrunge has quit IRC12:02
*** rfolco has joined #openstack-meeting12:04
*** dprince has joined #openstack-meeting12:06
*** matrohon has joined #openstack-meeting12:06
*** mrunge has joined #openstack-meeting12:07
*** weshay has joined #openstack-meeting12:07
*** xyhuang has joined #openstack-meeting12:10
*** VW_ has joined #openstack-meeting12:11
*** MaxPC1 has joined #openstack-meeting12:11
*** bknudson has quit IRC12:16
*** erlon has joined #openstack-meeting12:17
*** sudipto has quit IRC12:18
*** VW_ has quit IRC12:19
*** yamamoto has quit IRC12:22
*** banix has joined #openstack-meeting12:23
*** aysyd has joined #openstack-meeting12:23
*** egallen has quit IRC12:23
*** dkusidlo has joined #openstack-meeting12:24
*** raildo has joined #openstack-meeting12:25
*** annemccormick has joined #openstack-meeting12:25
*** aranjan has joined #openstack-meeting12:26
*** dguerri is now known as dguerri`12:28
*** larainema has quit IRC12:28
*** larainema has joined #openstack-meeting12:28
*** tellesnobrega has joined #openstack-meeting12:30
*** jungleboyj has quit IRC12:30
*** yamamoto has joined #openstack-meeting12:30
*** aranjan has quit IRC12:31
*** dguerri` is now known as dguerri12:32
*** devvesa has quit IRC12:35
*** yamamoto has quit IRC12:35
*** ivasev has joined #openstack-meeting12:35
*** bknudson has joined #openstack-meeting12:36
*** mtreinish has quit IRC12:40
*** mtreinish has joined #openstack-meeting12:40
*** ddieterly has joined #openstack-meeting12:41
*** bill_az has joined #openstack-meeting12:45
*** fawadkhaliq has joined #openstack-meeting12:47
*** rbowen has joined #openstack-meeting12:48
*** rbowen has quit IRC12:48
*** rbowen has joined #openstack-meeting12:48
*** baoli has joined #openstack-meeting12:48
*** eharney has quit IRC12:48
*** maishsk has quit IRC12:49
*** devvesa has joined #openstack-meeting12:49
*** sankarshan is now known as sankarshan_away12:49
*** numan has quit IRC12:50
*** maishsk_afk has joined #openstack-meeting12:50
*** ildikov_ has quit IRC12:51
*** fawadkhaliq has quit IRC12:51
*** yamamoto has joined #openstack-meeting12:52
*** banix has quit IRC12:52
*** banix has joined #openstack-meeting12:54
*** ajayaa has joined #openstack-meeting12:56
*** henrynash has joined #openstack-meeting12:56
*** _nadya_ has joined #openstack-meeting12:56
*** stevemar has joined #openstack-meeting12:57
*** radez_g0n3 is now known as radez12:57
*** zeddii has joined #openstack-meeting12:57
*** marrusl has joined #openstack-meeting12:57
*** pabelanger has joined #openstack-meeting12:58
*** DericHorn-HP has joined #openstack-meeting12:59
*** hogepodge has quit IRC13:00
*** stevemar has quit IRC13:00
*** _nadya__ has joined #openstack-meeting13:01
*** _nadya_ has quit IRC13:01
ttx#startmeeting releaseteam13:01
openstackMeeting started Mon Jun 29 13:01:36 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: releaseteam)"13:01
openstackThe meeting name has been set to 'releaseteam'13:01
ttxAgenda for today at
ttxyou can add extra topics as-needed13:02
*** hogepodge has joined #openstack-meeting13:02
*** sankarshan_away is now known as sankarshan13:02
ttx#topic Liberty-1 milestone postmortem13:02
*** mrunge has quit IRC13:02
*** openstack changes topic to "Liberty-1 milestone postmortem (Meeting topic: releaseteam)"13:02
ttxWe used to track work there13:02
ttxCame up with a checklist that I think we can publish on the wiki for reuse in future milestones13:03
ttxany objection to that ?13:03
dhellmannthe list worked well for me, so let's start with this one and add things if we find them13:03
*** krtaylor has quit IRC13:04
ttxWe had a number of issues with the new tools, most of them fixed13:04 needs some work to be more idempotent13:04
ttxI'll move the remaining tasks to our main wiki page13:04
ttxagreed on idempotency13:05
ttxour mix of shell and python isn't ideal for that though13:05
ttxwhich is why I deferred that task forever now :)13:05
dhellmannyeah, I was thinking about that last week when thinking about the automation tool13:05
*** fifieldt has joined #openstack-meeting13:06
dhellmannI might rewrite in python, converting bits of it to a library that makes reuse easier13:06
ttxWe'll come up with some python library to do the tagging and all13:06
ttxI suspect there is some git python library we can use to avoid shelling out from python13:06
*** jwcroppe has quit IRC13:06
dhellmannwe might even be able to reuse parts of pbr13:06
ttxyep, this is more an enhacement once we cover the urgent stuff13:07
*** ildikov_ has joined #openstack-meeting13:07
*** jwcroppe has joined #openstack-meeting13:07
ttxI'll take the action to break up that etherpad into a checklist and a number of tasks on the main etherpad13:07
ttx#action ttx to break up the L1 etherpad into a checklist and a number of tasks on the main etherpad13:08
*** jlvillal has quit IRC13:08
ttxanything else on liberty-1 ? I think we survived the transition to new tracking / new versioning gracefully13:08
dhellmannyes, it has gone fairly smoothly so far13:08
dhellmannhave we had any feedback from the distros, or is it too early for them to be looking at packaging?13:09
*** maishsk_afk has quit IRC13:09
ttxno feedback yet13:09
ttxprobably too early13:09
* ttx checks13:09
ttxdone at Ubuntu13:10
ttx 2:12.0.0~b1-0ubuntu113:10
ttxmeans we ahven't completely borked our communication plan around this13:10
ttxalright, next topic13:11
ttx#topic Deliverables13:11
*** openstack changes topic to "Deliverables (Meeting topic: releaseteam)"13:11
ttxWanted to discuss this concept and see how we can make progress on it, if we need to13:11
*** hogepodge has quit IRC13:11
ttxthe idea is that there already are a number of repositories that are released in sync13:11
*** puranamr has joined #openstack-meeting13:11
ttxby in sync I mean with same tag at the same time13:11
*** jwcroppe has quit IRC13:12
ttxthe archetypal example here is openstack/neutron*13:12
ttxopenstack/neutron + openstack-neutron-*aas13:12
ttxsince those days a lot of things are called openstack/neutron*13:12
*** hogepodge has joined #openstack-meeting13:12
*** jruano has joined #openstack-meeting13:12
*** jruano has quit IRC13:12
dhellmannwould you expect the releases for those things to all use the same release notes?13:13
ttxThose 4 repos are tagged at the same time with the same version number, and form a single "deliverable"13:13
ttxdhellmann: they do. Also share the same Launchpad project13:13
ttxwhich makes "release pages" quite consistent on that end13:13
*** ddieterly has quit IRC13:13
ttxWe have another project that has the same profile13:13
*** maishsk_afk has joined #openstack-meeting13:13
ttxopenstack/sahara releases together with sahara-extra and sahara-image-elements13:14
*** peristeri has joined #openstack-meeting13:14
dhellmannin that case using the same file in the releases repo might make sense13:14
ttxright, which is why I think it should be deliverable-oriented13:14
* dhellmann checks to see if that spec is approved13:14
dhellmannno, it's not13:14
dhellmannI thought we might get that approved last week, and I might start building the tool, but that didn't happen.13:15
*** yamamoto has quit IRC13:15
ttxNow, if we recognize that this concept exists, I think we need to take over releasing for sahara-extra and sahara-image-elements. So far Sergey has been on deck to tag at the same time13:15
dhellmannI could update the spec to make it work for deliverables, since it's a relatively minor change to the filename and schema13:15
ttxdhellmann: yeah, i wouldn't bother on spec and just iterate on format/tool13:15
dhellmannyeah, we should probably do all of them13:15
ttxI don't see any other obvious candiadte, though I think some of the -ui projects would like to do the same13:16
*** krtaylor has joined #openstack-meeting13:16
ttxMy main question at this point is.. if we recognize those are things, where should we keep track of them13:17
dhellmannthe yet-to-be-created releases repository seems like the obvious candidate13:17
ttxI can see some value in introducing the concept in projects.yaml (since that would allow deliverable-level tags), but that may be overkilkl13:17
dhellmannone file per deliverable per branch, as you proposed13:17
*** maishsk_afk has quit IRC13:17
dhellmannyeah, let's try to keep the format there simple if we can13:18
ttxRight, we could consider that a release property and just encode it in the release system13:18
ttxbecause that is what it is... describe how to release that "thing"13:18
ttxmy only objection would be that from a use point of view, they should consume deliverables, not repositories13:19
ttxi.e. it's easier for them to be presented with deliverables, rather than hunt down some obscure repo to find that sahara comes with sahara-extra13:19
*** jlvillal has joined #openstack-meeting13:19
*** MeganR has joined #openstack-meeting13:20
*** Zhongjun has joined #openstack-meeting13:20
ttxand therefore if those are the things users see, and tags are meant to describe things for users... at least some tags would make better sense being applied at deliverable-level13:20
*** eharney has joined #openstack-meeting13:20
dhellmannwe could use the release data to render some web pages, too, if that would be useful13:20
*** baoli has quit IRC13:20
dhellmannbut I see what you mean13:21
ttxpractical example: the project list on the website. They want to see "sahara" there, not openstack/sahar distinct from sahara/extra13:21
*** henrynash has quit IRC13:21
ttxwhich is why I'm still a bit hesitant to keep it completely off the governance repo13:21
ttxbut then, the release repo definitely is the right place to start13:22
dhellmannif we add deliverables as a parallel construct to "projects" and just refer again to the repo names, that won't break any of the tools currently parsing the projects.yaml file and will give us the deliverable relationships13:22
*** neelashah1 has joined #openstack-meeting13:22
*** mpaolino has joined #openstack-meeting13:22
dhellmannthe other option is to add a layer under "projects" to name each deliverable, but that's going to break some other tools13:22
*** MeganR has left #openstack-meeting13:22
ttxdhellmann: thought about the first option but you end up with either a lot of one-repo deliverables, or tags that can't be applied at that layer13:23
*** jwcroppe has joined #openstack-meeting13:24
dhellmanneither way we have a lot of one-repo deliverables, don't we?13:24
ttxanyway, we'll see about introducing it at governance layer and the cost/benefit there13:24
*** julim has joined #openstack-meeting13:24
ttxit's not really our call, but the TC's13:24
*** yamamoto has joined #openstack-meeting13:24
*** kebray has joined #openstack-meeting13:24
ttxLet's move on13:25
ttxi'll try to mock up how it could look like to minimize tool disruption13:25
ttx#topic Bug branches13:26
*** openstack changes topic to "Bug branches (Meeting topic: releaseteam)"13:26
ttxdhellmann: i s13:26
* dhellmann hands ttx a fresh keyboard13:26
ttxdhellmann: I suspect you were the one adding the note about those on the etherpad ?13:26
dhellmannyes, that's right13:26
ttxlight yellow13:26
ttxcould you summarize for the audience ?13:27
dhellmannthe idea here is to have something that acts like a feature/ branch, where it's tested against master, but isn't called "feature"13:27
*** aranjan has joined #openstack-meeting13:27
dhellmannwe had a case last week where it would have been convenient to release an oslo library not off of master, but we didn't want to create a stable branch for it yet13:27
*** amitgandhinz has joined #openstack-meeting13:27
*** sudipto has joined #openstack-meeting13:27
*** maishsk_afk has joined #openstack-meeting13:28
*** maishsk_afk is now known as maishsk13:28
dhellmannbug branches would let us do that, cutting a branch from say 1.12.0 to release 1.12.1, requiring a backport but not pulling everything from master13:28
dhellmannIIRC, the case was oslo.db because master no longer includes the namespace package, so we'll be releasing 2.0.0 this week13:28
ttxto me it's more like a release branch (the same way we branch off rc1 before release) that we craete after-the-fact13:28
ttxmy question is.. why did you need 1.12.1 ?13:28
dhellmannyeah, I wanted to be careful with the name to reflect that it is really meant for bug releases only13:29
*** Gerald_K has quit IRC13:29
dhellmannthere was a minor fix that was in master but it landed after the namespace removal13:29
dhellmannI think they ended up working around it, since we didn't get the branch stuff merged13:29
dhellmannthe zuul change landed, but is needed, too13:29
ttxSo, my take on it is that it's a slippery slope13:29
ttxyou don't want to do that for minor things, only in exceptional cases. Otherwise you'll end up with everyone trying to backport a change without some other changes and asking for point releases outside of stable branches13:30
dhellmannI think, as we go on, this is something we're going to find ourselves wanting to do infrequently, but when we do want it, it will be more expedient than correctly reverting feature changes13:30
dhellmannyes, we would definitely want to make it clear this is for exceptional cases13:31
dhellmanndims, do you remember what the oslo.db bug fix was for?13:31
ttxI think it's a tool in our toolkit for libraries, where we encourage people to only use tagged things13:31
dimsdhellmann: lookng up13:31
ttxFor services (where we support consuming master branch directly) not so much13:31
*** puranamr has quit IRC13:31
*** aranjan has quit IRC13:31
*** lpeer__ has joined #openstack-meeting13:31
dhellmannyes, that feels appropriate13:31
*** lpeer_ has quit IRC13:31
*** singlethink has joined #openstack-meeting13:32
dims"Remove implicit RequestContext decoration"13:32
dhellmannwe *may* want to use it for security fixes for server projects going to intermediate releases, but I think that's the only case13:32
dimsChange-Id: I143f30c41e788c7aa9887c0e994f49ee55c9465113:32
ttxI just fear that every security fix will trigger one of those now13:32
dhellmannah, right, oslo.db was using oslo.context but didn't declare it's dependency on it13:32
dimsdhellmann: y and neutron did not like some decoration that was happening in enginefacade i think13:33
*** zz_jgrimm is now known as jgrimm13:33
ttxi.e. you would end up having to do stable releases but also backport for current master release, in addition to master13:33
dhellmannttx: well, we only have to approve them in cases where a non-backwards compatible change is in master13:33
dhellmannand that will come up much less often for server releases13:33
ttxso only when you bump X ?13:33
dhellmannonly when bumping X would happen if you release from master, yes13:34
dhellmannwe could have done all of this using a feature branch, but I thought the name "feature" was misleading enough to introduce a new branch type13:34
ttxI'd still keep that option for significant things. Security fixes, regressions in last release, crazy bug13:34
ttxthat we can't wait to fix13:35
ttxbasically things where there is time pressure and asking people to bump to X+1 in thaht timeframe is unreasonable13:35
dhellmannwhen we get to the point where we're releasing all the libs weekly, we'll have much less pressure to do one of these anyway13:35
ttxit's the same story as feature branches. It's a great tool to have, but a slippery slope if everything is developed this way13:36
*** absubram has quit IRC13:36
ttxwhich is why creating them goes through some oversight13:36
*** absubram has joined #openstack-meeting13:36
ttxI definitely agree bug branches are a thing though, so we might want to document them13:36
*** kebray has quit IRC13:36
ttx(the feature branch chapter in project team guide is still due anyway)13:36
dhellmannok, I will add a bug branch chapter13:37
dhellmann#action dhellmann document using bug branches in project team guide13:37
ttxanything else on that topic ?13:37
dhellmannnone here13:38
ttxok, next topic then13:38
ttx#topic New release model tags13:38
*** openstack changes topic to "New release model tags (Meeting topic: releaseteam)"13:38
*** prad has joined #openstack-meeting13:38
ttxI started jolting notes on the maion etherpad and split them out to:13:38
*** nelsnelson has joined #openstack-meeting13:38
*** afazekas__ has quit IRC13:38
ttxBasically, with the recent changes I'm not sure the current release model tags help us or anyone13:39
ttxI listed the current taxonomy at the top13:39
*** hogepodge has quit IRC13:39
*** mrmartin has joined #openstack-meeting13:39
ttxThen the issues we have with it, which make them painful to use for us to determine anything13:39
ttxLet me summarize here13:40
ttxCurrently we have:13:40
*** sudipto has quit IRC13:40
ttxrelease:managed (missing some managed stuff, applied at repo level)13:40
ttxrelease:at-6mo-cycle-end (includes all services with a final $series release)13:40
ttxrelease:independent (means will do intermediary releases, or does not follow milestones)13:40
ttxrelease:has-stable-branches (means it has stable/$series)13:40
ttxIssues we have with that taxonomy:13:40
*** hogepodge has joined #openstack-meeting13:41
ttxat-6mo-cycle-end does not include client libraries (basically it is used to also mean type:service) so it's misleading to our users13:41
ttxhas-stable-branches is not applied to things that do stable/1.0 for example, so it's misleading too13:41
ttxhas-stable-branches currently really means that there is a final release at end of cycle ... precisely what at-6mo-cycle-end should really mean.13:41
ttxindependent may actually not be independent (difficult to understand when combined with others)13:41
ttxI'd like to come up with something that (1) conveys useful information to consumers in general and (2) that we can still use to derive tooling and policy13:42
ttxI think the current model fails at both now13:42
dhellmannyes, I agree it's not sufficient13:42
ttxrelease:managed is still pretty ok, it should just be applied at team level13:42
*** prad has quit IRC13:43
dhellmannthe new tag definitions look more useful, based on what we just did for this milestone13:43
ttxits meaning is clear and we have a use for it13:43
*** thangp has joined #openstack-meeting13:43
ttxtheer are basically 3 release models, and communicating which follows what is, I think relevant to all13:43
*** mtanino has joined #openstack-meeting13:43
ttxmaking the 3 release models a combination of other properties of which not all combinations are possible was, I think, a mistake13:44
ttxjust the result of design by committee on that initial set of tags, and pressure from projects that wanted to collect all possible tags13:44
dhellmannwe were also trying to be narrowly focused13:44
*** esheffield has joined #openstack-meeting13:45
ttxand we didn't have type:service/library13:45
*** andreykurilin__ has joined #openstack-meeting13:45
ttxso we encoded a bit of it there13:45
*** ctrath has joined #openstack-meeting13:45
*** dkusidlo has quit IRC13:45
*** balajiiyer has joined #openstack-meeting13:46
*** sudipto has joined #openstack-meeting13:46
ttxTo answer your etherpad question...13:46
dhellmannI'd like, eventually, for the distinctions based on type to be less important13:46
ttxIf the project intends to make a release, even if it never pushed a tag, it should use model-independent13:46
*** xyhuang has left #openstack-meeting13:46
dhellmannI corrected my verb tense to make that question more clear -- I'm thinking of things like tools directories or specs that are never "released"13:47
*** dkusidlo has joined #openstack-meeting13:47
*** deepika has joined #openstack-meeting13:47
dhellmannthe second case is someone just not getting around to applying a tag in the governance repo13:48
*** irenab has quit IRC13:48
*** ItSANgo_ has quit IRC13:48
ttxdhellmann: I think the second case should be model-independent. But I see your point13:48
*** mmedvede has joined #openstack-meeting13:49
dhellmannso we default to independent unless otherwise specified?13:49
ttxone chooses to actively have no release. So having a tag to describe that might be good13:49
ttxdhellmann: I think you are right13:49
ttxno tag should mean "we have no idea yet"13:49
dhellmannyeah, it's annoying to have to do that but from a browsability perspective I think we need it13:49
ttxalso we can see with project repo additions that they often come with no tag13:50
ttxand that should therefore convey the "unknown" state or a non-affirmative default state (like "well, no idea yet")13:51
dhellmannyes, I was thinking of writing a little test thing to require some release indicator, and anything else we know we want at least one of13:51
*** eharney has quit IRC13:51
ttxno-release is affirming "we know this won't get released"13:51
dhellmannto do that, we would need a release:model-no-releases or soemthing13:51
ttxdifferent from "well, we haven't decided yet"13:51
dhellmannthat makes the list_projects_by_tags tool simpler, too13:51
*** sahid has quit IRC13:52
*** rvasilets_ has joined #openstack-meeting13:52
ttxit's also slightly disjoing from tags. The governance repo for example has tags, but isn't released13:52
*** sahid has joined #openstack-meeting13:52
*** fzdarsky has joined #openstack-meeting13:52
*** jecarey has joined #openstack-meeting13:52
ttxok, I think we are onto something on the model side, that leaves stable branches13:52
ttxI thihnk that tag has no valud if it's not attached to a stable branch policy13:53
*** fallenpegasus has quit IRC13:53
ttxotherwise you don't know what you get13:53
ttxso there is value for "follows-stable-branch-policy"13:53
dhellmanndon't we have a policy on stable branches already? or is that just tribal knowledge, and not written down?13:53
ttxwhich is slightly clearer than "managed-by-stable-maint-official"13:54
ttxwe have a policy, but it's enforced by the stable-maint team13:54
ttxthere are rogue stable branches out there13:54
ttxthings that the stable branch policy won't support for one reason or another13:54
ttxstable branch team I mean13:54
dhellmannso maybe we need stable:managed, stable:follows-policy, stable:independent13:54
*** igordcard_ has quit IRC13:55
ttxI'd argue that the first two are the same13:55
ttxsince the only thing the stable-maint-core team does is ensure that policy is followed13:55
dhellmannah, ok then13:55
*** prad has joined #openstack-meeting13:55
ttxI just don't see the value of stable:indep I guess13:55
ttx"some" backports ?13:55
dhellmannI think it's useful to indicate that a project does backports, and may maintain more old versions than policy requires13:56
dhellmannthat's the gnocchi case, right?13:56
ttxyes, the gnocchi case is that it follows a different policy13:57
ttxundocumented so I can't tell what I get there13:57
ttxI suspect, some backports.13:57
*** superdan is now known as dansmith13:57
*** stpierre has joined #openstack-meeting13:57
ttxbut can they break me ? no idea? Is config option addition fair game ? dunno. Can I change strings ?13:58
*** sigmavirus24_awa is now known as sigmavirus2413:58
ttxwill my translation hold ?13:58
*** dkusidlo has quit IRC13:58
dhellmannright, so if the idea is to provide more info to users, telling them "there's some sort of backport policy, but it's not standard" at least lets them know to talk to the dev team about it13:58
ttxok, I can see that13:58
dhellmannor look for it to be documented elsewhere13:58
*** boris-42 has joined #openstack-meeting13:59
*** amotoki has quit IRC13:59
*** kebray has joined #openstack-meeting13:59
dhellmannand maybe we end up with some new "policy" evolving out of projects copying what they do, and then they can document that in the governance repo eventually13:59
*** DericHorn-HP has quit IRC13:59
*** subscope has joined #openstack-meeting13:59
ttxOK, will work on all that as soon as we manage to pass the current round of horizontal changes13:59
*** sahid has quit IRC13:59
ttxLast topic was Server versioning: mapping versions to series13:59
ttxbut no time left14:00
*** sahid has joined #openstack-meeting14:00
ttxit was about rediscussing how to achieve that14:00
ttxwe can move that to #openstack-relmgr-office14:00
ttxThanks everyone!14:00
*** openstack changes topic to "OpenStack Meetings ||"14:00
openstackMeeting ended Mon Jun 29 14:00:43 2015 UTC.  Information about MeetBot at . (v 0.1.4)14:00
openstackMinutes (text):
boris-42#startmeeting Rally14:01
openstackMeeting started Mon Jun 29 14:01:00 2015 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: Rally)"14:01
openstackThe meeting name has been set to 'rally'14:01
boris-42ping andreykurilin__ rvasilets_14:01
*** pratap has joined #openstack-meeting14:01
boris-42andreykurilin__: you are on holidays no?14:02
*** DericHorn-HP has joined #openstack-meeting14:02
andreykurilin__boris-42: yes, but I'm online now:)14:02
boris-42kun_huang: ping14:02
*** adahms has joined #openstack-meeting14:02
boris-42kun_huang: hi hi14:03
boris-42stpierre: ping14:03
boris-42stpierre: hi there14:03
kun_huangactually fixtures upgrades block us again...14:03
*** fawadkhaliq has joined #openstack-meeting14:03
boris-42kun_huang: hm?14:03
*** ItSANgo has joined #openstack-meeting14:03
kun_huangblock unit test14:03
*** subscope has quit IRC14:04
kun_huangthere are some hidden bugs in rally14:04
*** bryan_att has joined #openstack-meeting14:04
boris-42kun_huang: hm14:04
andreykurilin__kun_huang: what kind of bugs?14:04
boris-42kun_huang: my patch works well14:04
boris-42kun_huang: except trivial bug in pep14:05
*** pratap has quit IRC14:05
kun_huangthis line14:05
boris-42kun_huang: and?14:06
*** eharney has joined #openstack-meeting14:06
boris-42kun_huang: it doesn't fail for me..14:06
kun_huanggoing into your tox env, pip install fixtures --upgrade, back to normal env14:07
kun_huangrun tox -e py26, failed14:07
*** cody-somerville has quit IRC14:07
kun_huangfixtures upgraded today...14:07
boris-42kun_huang: omh14:08
*** fawadkhaliq has quit IRC14:08
boris-42kun_huang: omg14:08
kun_huangthe latest one, failed again14:08
boris-42kun_huang: so many upgrades...14:08
kun_huangthe failed two test cases both have "self.get_fm.cleanUp()"14:08
kun_huangI don't understand on this ...14:08
boris-42kun_huang: that one seems like a bug14:09
boris-42kun_huang: just need to remove that line14:09
boris-42kun_huang: that you specified14:10
kun_huangI'm not sure for that line14:10
kun_huangare you sure for that?14:10
*** ItSANgo has quit IRC14:10
*** ItSANgo has joined #openstack-meeting14:10
*** absubram has quit IRC14:11
boris-42kun_huang: nope14:11
boris-42kun_huang: seems like kiran is working on it14:12
* boris-42 kun_huang:
openstackLaunchpad bug 1469644 in Rally "Rally jenkins fails due to fixtures 1.3.0" [Undecided,In progress] - Assigned to Kiran (rkiran)14:12
*** rjaiswal has joined #openstack-meeting14:12
*** ItSANg___ has joined #openstack-meeting14:12
andreykurilin__boris-42: we can't merge such fix:(14:13
kun_huangwe two found it in my afternoon14:13
boris-42andreykurilin__: that one is not a proper fix14:13
boris-42kun_huang: ok I will investigate it today14:13
kun_huangbtw, removing that line can't fix this14:13
kun_huangTraceback (most recent call last):14:13
kun_huang  File "tests/unit/plugins/openstack/scenarios/nova/", line 58, in test_failed_server_status14:13
kun_huang    server_manager.create("fails", "1", "2"))14:13
kun_huang  File "/Users/Gareth/celtics/rally/.tox/py27/lib/python2.7/site-packages/testtools/", line 422, in assertRaises14:13
kun_huang    self.assertThat(our_callable, matcher)14:13
kun_huang  File "/Users/Gareth/celtics/rally/.tox/py27/lib/python2.7/site-packages/testtools/", line 435, in assertThat14:13
kun_huang    raise mismatch_error14:13
kun_huangtesttools.matchers._impl.MismatchError: <MagicMock name='get_from_manager()' id='4466724112'> returned <MagicMock name='get_from_manager()()' id='4466814096'>14:13
kun_huangRan 1661 tests in 21.935s (-0.247s)14:13
boris-42rakhmerov: thanks for fixing mistral client14:13
kun_huangFAILED (id=46, failures=2)14:13
kun_huangerror: testr failed (1)14:13
boris-42kun_huang: please14:13
boris-42kun_huang: use paste14:13
kun_huangokay :)14:14
rakhmerovboris-42, np. My apologies again for the mess..14:14
*** absubram has joined #openstack-meeting14:15
boris-42so okay we will fix this14:15
boris-42let's move to next topics14:15
*** absubram has quit IRC14:15
boris-42#topic Import Optimization14:15
*** openstack changes topic to "Import Optimization (Meeting topic: Rally)"14:15
boris-42I almost finished the patch that optimizes imports14:16
*** pabelanger has left #openstack-meeting14:16
*** mrunge has joined #openstack-meeting14:16
boris-42so it just imports plugins if they are required14:17
*** ItSANgo has quit IRC14:17
boris-42as a result I saw that it's not enough to fix the issue and it takes about 300ms to start Rally14:17
kun_huangseems nice14:17
boris-42another big issue is sqlalchemy that starts about 80ms14:17
boris-42so I will try to hack more and reduce time at least to 200ms14:17
boris-42and hope that that will be enough to do live bash completition14:18
*** jecarey has quit IRC14:18
*** stevemar has joined #openstack-meeting14:19
boris-42andreykurilin__: stpierre ^14:19
andreykurilin__boris-42: "+58, -24" is quite small change for you:)14:20
boris-42andreykurilin__: LOL14:21
boris-42andreykurilin__: I didn't finished it14:21
boris-42andreykurilin__: I will need one more small change to +2500 -2500014:21
*** albertw has joined #openstack-meeting14:21
boris-42albertw: hi there14:21
*** dims has quit IRC14:21
boris-42albertw: it's our regular weekly meeting14:21
boris-42albertw: btw gates are against broken with something *new* released14:22
boris-42albertw: so no worries about -1 from Jenkins =(14:22
*** Fdot has joined #openstack-meeting14:23
albertwboris-42: thanks. I was wondering why things were failing.14:23
*** mrunge has quit IRC14:23
boris-42albertw: last two weeks was hell for us14:23
*** henrynash has joined #openstack-meeting14:23
andreykurilin__openstack is too stable for our gates :(14:23
boris-42albertw: neutron 2 times, heat,  mistral, fixtures..14:23
andreykurilin__boris-42: you worgot ceilometer14:24
boris-42andreykurilin__: ah yep14:24
*** baoli has joined #openstack-meeting14:24
boris-42albertw: ^ so we can't do actually anything with this except fix/wait_for_fixes14:24
*** dims has joined #openstack-meeting14:24
*** subscope has joined #openstack-meeting14:24
*** yamahata has joined #openstack-meeting14:25
boris-42so okay14:26
boris-42#topic Open Disucssion14:26
*** openstack changes topic to "Open Disucssion (Meeting topic: Rally)"14:26
boris-42Actually, as msdubov left team14:26
boris-42we should find somebody who is able to do Agenda for each meeting14:27
boris-42stpierre: andreykurilin__ rvasilets_ ^14:27
*** aranjan has joined #openstack-meeting14:28
boris-42so everybody will be able to attend to meeting14:28
stpierrethis meeting is at the start of my day, so i vote for someone else so that i don't have to worry about it friday afternoon before leaving for the weekend.14:28
stpierreif neither andrey or roman can do it, of course i'm happy to step in14:28
andreykurilin__boris-42: do we have agenda at mailing-list ?14:29
andreykurilin__*only at mailint-list14:29
boris-42andreykurilin__: nope14:29
*** kir_ has joined #openstack-meeting14:29
rvasilets_if you show me how to do this14:29
rvasilets_I'll try14:30
boris-42rvasilets_: ok14:30
boris-42rvasilets_: so it's simple we should fix this page14:30
boris-42rvasilets_: to add somewhere whole paragraph about meetings agenda14:30
boris-42rvasilets_: then we should create a sepcial wiki page for that14:31
boris-42rakhmerov: sorry14:31
boris-42rvasilets_: ^14:31
boris-42rvasilets_: there is already14:32
boris-42rvasilets_: so the idea is to collect all topics that we should disucss14:32
boris-42rvasilets_: regularly and write them there14:32
*** henrynash has quit IRC14:32
andreykurilin__it's a bit outdated:D14:32
*** cody-somerville has joined #openstack-meeting14:32
*** aranjan has quit IRC14:32
boris-42andreykurilin__: yep14:32
boris-42andreykurilin__: but we need to keep full history14:32
boris-42andreykurilin__: with links to the logs14:33
*** galstrom_zzz is now known as galstrom14:33
boris-42andreykurilin__: yep14:33
boris-42rvasilets_: are you ready ?)14:33
rvasilets_you are talking about this page ?14:33
boris-42rakhmerov: nope14:34
boris-42rvasilets_: nope14:34
boris-42rakhmerov: sorry one more time14:34
rvasilets_I think it would be better to swap holder of agenda sometimes. Because as I understand its boring)14:35
*** kylek3h has joined #openstack-meeting14:35
boris-42rvasilets_: yep that sounds good14:36
boris-42rvasilets_: e.g. everybody can do it 2 weeks14:36
boris-42rvasilets_: and change with next14:36
*** rossella_s has quit IRC14:36
rvasilets_ok I'll start14:37
boris-42andreykurilin__: stpierre kun_huang ^14:37
*** ddieterly has joined #openstack-meeting14:37
*** rossella_s has joined #openstack-meeting14:37
*** haleyb has joined #openstack-meeting14:37
*** sdake has joined #openstack-meeting14:37
*** dguitarbite has quit IRC14:37
stpierreok, sounds good14:37
andreykurilin__ok, sound reasonable14:37
rvasilets_you will show me how to do it right in private messages)14:37
*** garthb has joined #openstack-meeting14:37
*** annegentle has joined #openstack-meeting14:37
*** garthb_ has joined #openstack-meeting14:37
kun_huangno problem :)14:38
*** ayoung has joined #openstack-meeting14:38
*** annegentle has quit IRC14:38
*** etoews has joined #openstack-meeting14:39
*** annegentle has joined #openstack-meeting14:39
boris-42okay nice14:39
boris-42so we will make a schedule and we will keep agends/logs up to date14:39
boris-42and make this meeting more useful14:40
*** sdake_ has joined #openstack-meeting14:40
boris-42do we have something to discuss?14:40
andreykurilin__no :(14:41
*** yamamoto has quit IRC14:41
*** DericHorn-HP has quit IRC14:41
kun_huangboris-42: there is a set of patches about sahara/swift14:41
kun_huangneed review14:41
*** Apoorva has joined #openstack-meeting14:42
andreykurilin__boris-42: what about adding regular topic "stuck reviews"?14:42
*** amakarov_away is now known as amakarov14:43
boris-42andreykurilin__: ya that sounds good14:43
boris-42kun_huang: yep yep we have issues with review throughput...14:43
*** yamamoto has joined #openstack-meeting14:43
kairat_kushaevandreykurilin__: How about heat issues to analyze=)14:43
*** sdake has quit IRC14:43
boris-42kun_huang: ?14:44
boris-42kairat_kushaev: ? )14:44
kun_huangI'm working on review work now14:45
kairat_kushaevboris-42: I mean when can we proceed to analyze why heat is failing14:45
kun_huangbut I don't know sahara details14:45
andreykurilin__kairat_kushaev: heh. today is a holiday in Ukraine. non-working day. :P14:45
*** MIDENN_ has quit IRC14:45
*** fzdarsky has quit IRC14:45
kairat_kushaevandreykurilin__: OK=)14:45
boris-42kairat_kushaev: heh I really don't know why it started failing...14:45
kairat_kushaevboris-42: We did some investigation but I need to understand what nova-network is doing at some moment. Anyway I will pink Andrey this week14:46
andreykurilin__boris-42, kairat_kushaev: Maybe we can move heat job from nova-network to neutron?14:47
*** dkusidlo has joined #openstack-meeting14:47
boris-42andreykurilin__: yep that seems like a good idea14:47
kairat_kushaevboris-42: I have a second question that was raised during review of some patches14:47
boris-42kairat_kushaev: ?14:47
andreykurilin__And I'll try to debug nova-network this week14:47
kairat_kushaevandreykurilin__: seems reasonable14:47
kairat_kushaevboris-42: OS is updating very fast. So what versions we should support in rally14:48
*** fallenpegasus has joined #openstack-meeting14:48
andreykurilin__kairat_kushaev: all14:48
andreykurilin__* as much as it possible14:48
boris-42andreykurilin__: +214:49
*** ajayaa has quit IRC14:49
stpierrecan we reduce that to "all versions supported by upstream"?14:49
boris-42stpierre: nope14:49
stpierrei don't feel like we should particularly care if rally works against grizzly (it doesn't)14:49
*** fawadkhaliq has joined #openstack-meeting14:49
boris-42stpierre: so there is people that use grizzly and so on..14:49
andreykurilin__and if you install rally in virtual env, it'll work with grizzly14:50
*** ddieterly has quit IRC14:50
andreykurilin__if we create stable branches(stable/icehouse, stable/juno and etc), we will add a lot of extra stuff(backporting patches)14:51
stpierrei certainly agree that's a bad approach14:51
boris-42stpierre: so let's try to imporve framework14:52
stpierrebut we don't have the CI infrastructure for making sure that rally works on older versions, and i think it's foolhardy to pretend that we can make our scenarios work for everything14:52
boris-42stpierre: so we will be able to support old versions in more transparent way14:52
*** ildikov_ has quit IRC14:52
*** _nadya__ has quit IRC14:52
boris-42stpierre: so better framework / better ci14:52
boris-42stpierre: can help us14:52
*** hichihara has joined #openstack-meeting14:52
stpierreit can help us, but scope that expands without bound is not possible to satisfy.14:53
*** _nadya_ has joined #openstack-meeting14:53
stpierrei.e., if someone filed a bug against a scenario that doesn't work on Diablo, should we care?14:53
*** dmacpher has joined #openstack-meeting14:53
boris-42stpierre: if it is possible to fix, why not?)14:53
boris-42stpierre: in any case by trying to support older version we are facing real production issues14:54
boris-42stpierre: knowing such issues allows us to make better framework14:54
stpierrea) we've got better things to do than set up diablo openstack to test the fix; b) we have no diablo CI resources, so we can't ensure that it stays fixed; c) that's going to *greatly* overcomplicate the code in the future because the APIs have changed significantly since older versions14:54
stpierrekairat_kushaev and i ran into an issue just last week where we've got probably two dozen extra lines of hacky code in one of the heat scenarios because kilo heat is good and juno heat is terrible14:55
stpierreand that's *juno*14:55
stpierre("good" might be overstating it, but you get the idea)14:55
*** taturn has joined #openstack-meeting14:55
andreykurilin__taturn: hi14:56
stpierrei think we need to limit ourselves to what we can realistically test14:56
boris-42taturn: hi14:56
taturni am new here14:56
boris-42taturn: so welcome=)14:57
taturnand the bad thing for me is i am not good at english14:57
*** fawadk has joined #openstack-meeting14:57
taturnby the way i am from china14:57
*** webber__ has joined #openstack-meeting14:57
*** _nadya_ has quit IRC14:57
*** mdenny has joined #openstack-meeting14:57
*** ub has quit IRC14:57
kairat_kushaevPerhaps we need some minimal requirements14:57
stpierreright now, that means four versions, which IMO is more than enough to keep us very busy14:58
boris-42stpierre: agree with this14:58
*** pradipta has joined #openstack-meeting14:58
boris-42stpierre: in any case our framework sux14:58
andreykurilin__stpierre: simple example. Mirantis just released mos-6.1, which is "kilo", so most of mirantis customers use juno today and will start upgrading to "liberty" in near future. I suppose there is a lot of such examples14:58
boris-42stpierre: to have scenarios for specific versions..14:58
*** jecarey has joined #openstack-meeting14:58
*** SridharG has left #openstack-meeting14:58
andreykurilin__*will start upgrading to kilo14:58
boris-42andreykurilin__: and we have customers that use grizlly14:59
stpierreboris-42: yeah, that will help14:59
stpierremost of our customers are on grizzly14:59
boris-42stpierre: so we need to keep grizzly wokring14:59
stpierreno, we really don't14:59
*** maishsk has quit IRC14:59
boris-42stpierre: =)14:59
*** irenab has joined #openstack-meeting14:59
boris-42so in any case14:59
boris-42we should finish14:59
boris-42this meeting14:59
stpierreeven if we just test what's currently supported, we're going to be testing four versions (and troubleshooting icehouse devstack issues, which is terrible enough)15:00
taturni donot know what u r saying15:00
*** openstack changes topic to "OpenStack Meetings ||"15:00
openstackMeeting ended Mon Jun 29 15:00:17 2015 UTC.  Information about MeetBot at . (v 0.1.4)15:00
openstackMinutes (text):
*** ijw has joined #openstack-meeting15:00
*** fawadkhaliq has quit IRC15:00
*** patrickeast has joined #openstack-meeting15:01
andreykurilin__taturn: let's move to #openstack-rally chat15:01
anteaya#startmeeting third-party15:01
openstackMeeting started Mon Jun 29 15:01:19 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: third-party)"15:01
*** henrynash has joined #openstack-meeting15:01
openstackThe meeting name has been set to 'third_party'15:01
anteayaanyone here for the third party meeting?15:01
*** ctrath has quit IRC15:01
*** albertw has left #openstack-meeting15:01
*** eantyshev has joined #openstack-meeting15:02
*** ctrath has joined #openstack-meeting15:03
anteayathanks to asselin for charing last weeks meeting15:03
*** Alexey_Nexenta has joined #openstack-meeting15:03
*** stpierre has left #openstack-meeting15:03
anteayareminder that asselin's common-ci sprint is coming up July 8 & 915:03
*** carl_baldwin has joined #openstack-meeting15:03
*** Murali has quit IRC15:04
*** jtomasek has quit IRC15:04
anteayadoes anyone have anything they wish to discuss at today's third party meeting?15:04
*** absubram has joined #openstack-meeting15:04
anteayataturn: you are in a meeting channel15:05
anteayataturn: if you wish to participate in the third party meeting you are welcome, but please contribute something of use15:05
anteayataturn: the general discussion channel is #openstack-dev15:05
*** ildikov_ has joined #openstack-meeting15:05
taturnsorry i am new here15:06
taturnlet me use translater to know what u said  i am a chinese15:06
anteayataturn: yeah I saw that in the rally meeting15:06
*** jruano has joined #openstack-meeting15:06
anteayataturn: I gave you some guidance15:06
anteayaso does anyone have anything pertient to share at today's meeting15:07
*** Fdot has quit IRC15:07
*** dkusidlo has quit IRC15:07
*** annp has joined #openstack-meeting15:07
anteayaso if noone has anything of any importance to share at today's third party meeting15:08
*** Fdot has joined #openstack-meeting15:08
lennybnot me15:08
anteayahow about we find more productive uses of our time?15:08
anteayahi lennyb, thanks15:08
*** Fdot has quit IRC15:08
eantyshevour Zuul occasionally falls into busyloops of a kind:
eantyshevwhich happens after reconfiguration15:09
anteayadoes it ever break out of the loop?15:09
eantyshevanteaya: Not until zuul-server restarted15:09
anteayaso after you reconfigure zuul you need to restart it?15:10
lennybeantyshev: are you using the latest upstream?15:10
eantyshevsometimes, yes15:10
*** ociuhandu has quit IRC15:10
patrickeasti saw that happen to mine on friday night, filled up like 70GB of log file with that error :(15:10
anteayapatrickeast: was a zuul restart the solution?15:10
patrickeasti did the same thing, killed zuul, pulled all the latest changes and restarted15:10
*** claudiub has quit IRC15:11
patrickeastunsure if there was an update that fixed it, but it went away15:11
eantyshevlennyb: sure15:11
anteayaeantyshev: when did you first notice this behaviour?15:11
lennybyantyshev: may it be related to the late patches that were added. there was some fix related to the loop ( I even think it was yours )15:12
eantyshevanteaya: that happened last Thursday at 3pm15:13
*** jckasper has joined #openstack-meeting15:13
*** sudipto has quit IRC15:13
*** ociuhandu has joined #openstack-meeting15:13
anteayaeantyshev: so this is recent behaviour then15:13
anteayaeantyshev: next time you restart zuul can you be sure to pull the most recent patches15:13
anteayaeantyshev: and if the looping behaviour persists are you willing to file a bug against zuul?15:14
*** ramashri has joined #openstack-meeting15:14
*** jungleboyj has joined #openstack-meeting15:14
eantyshevanteaya: it dissapears every time after restart15:14
anteayaeantyshev: right, I'm asking if you are willing to pull the latest patches and evaluate if a patchset fixes the situation15:15
anteayaeantyshev: and if it doesn't, if you are willing to file a bug against zuul15:15
*** Guest57686 has quit IRC15:15
*** dannywilson has joined #openstack-meeting15:16
*** ctrath has left #openstack-meeting15:16
anteayaeantyshev: are you willing to file a bug against zuul if you keep seeing this?15:16
eantyshevanteaya: Zuul is up-to-date, AFAIU, head last updated on Jun12 (Support external cross-project dependencies in ui).  And I'd rather investigate it myself, though15:16
anteayaeantyshev: oh okay15:16
anteayaeantyshev: can you let us know if you find anything?15:17
patrickeastwhy not file a bug and assign it to yourself?15:17
anteayaa bug report allows others to track progress15:17
anteayapatrickeast: good point15:17
anteayaand you can update teh bug status as you work on it15:17
eantyshevthen I'll make this a bug15:17
*** dannywilson has quit IRC15:18
anteayait is a workflow which is considered friendlier in an open source spac15:18
anteayathanks eantyshev15:18
*** dannywilson has joined #openstack-meeting15:18
anteayais the storyboard link for zuul15:18
anteayaanything more on this topic?15:18
eantyshevpatrickeast: did you experienced busyloops too? can you share the piece of your debug logs?15:19
*** dkusidlo has joined #openstack-meeting15:20
patrickeasteantyshev: yea i’ll go dig up the links15:20
*** yamamoto has quit IRC15:20
anteayadoes anyone have any other topic to discuss?15:21
*** sudipto has joined #openstack-meeting15:21
patrickeastsame callstack, different patchset15:22
*** andreykurilin__ has left #openstack-meeting15:22
ociuhanduhi all, sorry for being late15:22
anteayaociuhandu: np15:22
ociuhanduanteaya: I’ve seen a quite long thread discussing about third-party CI voting rights15:22
anteayaociuhandu: do you have anything you wish to discuss today?15:22
*** taturn has left #openstack-meeting15:22
anteayaociuhandu: yes the discussion is taking place on the mailing list15:22
anteayaand voting isn't a right, it is at best a permission15:23
eantyshevpatrickeast: thanks!15:23
ociuhanduand it seems that the topic heads towards non-voting CIs15:23
anteayathe decision to allow any ci voting permissions lies with the ptl of the project in question15:23
*** _nadya_ has joined #openstack-meeting15:23
*** e0ne has joined #openstack-meeting15:23
anteayaindividual projects can make the decision that works best for their project15:23
*** yamamoto has joined #openstack-meeting15:23
*** dwalleck has joined #openstack-meeting15:24
anteayaI don't expect openstack wide consensous on this15:24
anteayathe ability to grant permissions on cis lies with the ptl of the project in question15:24
*** DericHorn-HP has joined #openstack-meeting15:25
*** e0ne is now known as e0ne_15:25
ociuhanduanteaya: from what I have seen it seems that though this started from one project it’s now involving multiple projects and they seem to lean towards the same direction15:25
*** e0ne_ is now known as e0ne15:25
*** rbowen has quit IRC15:26
anteayaociuhandu: okay15:26
ociuhandubut i see your point, so we’ll have to discuss them with the individual project ptls15:26
*** nadeem has joined #openstack-meeting15:26
anteayadid you have any point you wanted to make about that?15:26
anteayaI have no say in what the decision is15:26
*** david-ly_ is now known as david-lyle15:27
anteayaI encourage you to participate in the thread if you have a perspective you wish to ensure others know about15:27
ociuhanduwell, as a general idea i feel that telling now any third-party that we’ll revoke any kind of voting rights kind of defeats the purpose of the CI requirements in the first place15:27
anteayayou are welcome to have that opinion15:28
ociuhanduas in, you have to have a reliable CI but we don’t let you say if a patch is good or not15:28
krtaylorociuhandu, I disagree, comments are useful, if they are reliable15:28
anteayaand I do agree that it is frustrating from the perspective of teh ci operators15:28
anteayaas the message seems to keep changing15:28
ociuhandu(since anyway everyone is complaining about the noise the CIs add to the commenting section)15:28
*** geoffarnold has quit IRC15:28
*** nadeem has quit IRC15:28
*** dwalleck has quit IRC15:28
anteayahowever the infra message is clear, if you have a gerrit ci account, you are expected to adheare to infra requirements15:29
anteayaall else is up to the individual projects15:29
*** aranjan has joined #openstack-meeting15:29
wznoinskhi all15:29
ociuhanduok, thanks15:29
anteayawznoinsk: hello15:29
*** dwalleck has joined #openstack-meeting15:29
anteayaociuhandu: welcome, thanks for bringing it up15:29
*** armax has joined #openstack-meeting15:29
*** belmoreira has quit IRC15:29
anteayaociuhandu: I encourage you to comment on the mailing list thread, and discuss it with the project you are testing15:30
*** dwalleck has quit IRC15:30
*** rbowen has joined #openstack-meeting15:30
anteayaanything more on this topic?15:30
wznoinskociuhandu: I think it came down with recent changes to not to ahve integrated releases15:31
ociuhanduanteaya: will do, just wanted to get a deeper understanding on this from the infra perspective15:31
*** singlethink has quit IRC15:31
*** arnaud____ has joined #openstack-meeting15:31
*** dkusidlo has quit IRC15:31
anteayaociuhandu: sure, the infra perspective is about gerrit accounts, voting permissions and many other decisions are up to the projects15:31
*** thedodd has joined #openstack-meeting15:32
*** _nadya_ has quit IRC15:32
*** Fdot has joined #openstack-meeting15:32
anteayadoes anyone have anything else they wish to discuss today?15:32
wznoinskin short, cores will be looking at CIs results less by the looks of things15:32
anteayawznoinsk: I don't understand either of your last two statements15:33
anteayawznoinsk: can you try again to express your point?15:33
*** hemnafk is now known as hemna15:33
*** ajmiller has joined #openstack-meeting15:33
*** aranjan has quit IRC15:34
anteayaor shall we move on?15:35
*** amrith is now known as _amrith_15:35
* anteaya is uncertain if waiting is a worthy use of time15:35
anteayaI'm not trying to dismiss what you said wznoinsk, I'm trying to understand it15:35
wznoinskanteaya: sure, when there was any enforcing of the features in releases, cores/ptls were interested in the tests CI provide as a wider testing ground for features, now when we report rather than enforce and a lot of neutron code went out of tree, cores/ptl are not directly looking at whether they work or not15:36
*** ajayaa has joined #openstack-meeting15:36
anteayawell to be honest it never was the job of the core reviewers to review the ci jobs15:36
wznoinskto me CIs are becoming the help to features devs only15:36
anteayait was and is the responbility of the ci/driver maintainer15:37
anteayawell becoming/is yes15:37
wznoinskanteaya: not saying it was, but as for features that were promised in a release it was  a good testing ground15:37
anteayait just is taking some folks a while to realize that15:37
anteayano it was15:37
anteayaI am saying it was and is15:37
*** yassine has quit IRC15:37
*** achanda has joined #openstack-meeting15:37
*** yassine has joined #openstack-meeting15:37
*** lufix has quit IRC15:38
*** aimon_ has quit IRC15:38
anteayathe ci results are meant for the consumption of the driver maintainer15:38
krtaylorexcept in the case of infra ci15:38
anteayaand others just look to see if the driver maintainer is paying attention or not15:39
wznoinskthe help to devs yes, I never said cores job was to look at the CI results, it was more of an additional info15:39
*** flashgordon has quit IRC15:39
anteayakrtaylor: no, especially in the case of infra ci15:39
*** webber__ has quit IRC15:39
anteayawznoinsk: right15:39
anteayathe addtional info being wether the driver maintainer was paying attention or not15:40
*** pbourke has quit IRC15:40
*** moha_hunt has joined #openstack-meeting15:40
anteayaanything more here?15:40
*** dwalleck has joined #openstack-meeting15:40
*** pbourke has joined #openstack-meeting15:40
*** dwalleck has quit IRC15:40
wznoinskI sort of don't like the fact the more loose rights we have now (big tent, 4 OPENs etc) the less we pay attention to proper testing of all of that... I'm not saying cores/ptls should be looking after it tho15:40
anteayawznoinsk: I don't like it either15:41
anteayawznoinsk: I am out of suggestions for what to do about it though15:41
anteayawznoinsk: if you have any contructive thoughts I am looking for suggestions15:41
wznoinskideally some sort of certified CI badge would be good to have15:41
anteayaI'm not certifying anything15:42
wznoinsksome CI ops are interest-less, some are looking after well, but may stop doing so if there's no real value it in anymore - that would hurt openstack testing15:42
anteayaI have opinions on the use of the word certified15:43
anteayahere is a thread from last year on the topic in case you missed it15:43
anteayawznoinsk: I agree15:43
anteayavalues are important15:43
ttxnot necessarily "certified" but at least recognized as good. Some tag that says "CI actually means something here" could be interesting15:43
ttxdifficult to define though15:44
anteayaand experiencing a lack of values is hard to give or recieve guidance15:44
wznoinskanteaya: well, maybe "powered by Openstack CI suite" could be for CIs using downstream-puppet when you have it done with proper self-diagnosis15:44
*** PrashantS has joined #openstack-meeting15:44
wznoinskanteaya: only throwing thoughts here...15:44
anteayawznoinsk: sure15:44
anteayabrainstorming is good15:44
*** ruhe has joined #openstack-meeting15:44
anteayaI have nothing to offer, unfortunately, though I wish I did15:44
anteayabut I definitely feel a lack of values15:45
anteayathere used to be values15:45
anteayaand I can't find them today15:45
*** PrashantS has quit IRC15:45
anteayanot sure what to do about that15:45
wznoinskttx: it is difficult, once we agree on who values from CIs (and these are devs and components vendors imho only atm) we would make the certification/recognition right15:45
*** hashar has quit IRC15:45
*** PrashantS has joined #openstack-meeting15:45
* anteaya reiterates she has opinions on the use of the word certified15:46
*** yamamoto has quit IRC15:46
*** Sukhdev has joined #openstack-meeting15:46
anteayabut identifying what we value15:46
anteayaor what is valued15:46
*** scheuran has quit IRC15:46
*** dwalleck has joined #openstack-meeting15:46
anteayaand recognizing when that value is respecting15:46
*** e0ne has quit IRC15:46
anteayaI support that15:47
anteayaas well as all those words15:47
anteayavalues, recogniztion and respect15:47
*** sarob has joined #openstack-meeting15:47
wznoinskon the other hand, if infra plans to extend their testing, why not to do it using community (3rd party ci)?15:47
*** e0ne has joined #openstack-meeting15:48
*** dmacpher is now known as dmacpher-afk15:48
*** annegentle has quit IRC15:48
anteayaif infra plans to extend their testing15:48
anteayadoes infra plan to extend their testing?15:48
anteayaif so this is news to me15:48
anteayawhat plans does infra have15:48
anteayaand what tests are being extended15:48
anteayaand how?15:48
*** annegentle has joined #openstack-meeting15:49
*** matrohon has quit IRC15:49
anteayawznoinsk: what are you reading or referencing that leads you to these conclusions?15:49
wznoinskthere were couple of talks on the summit about testing, some ppl wanted to have more testing, I don't know whether that's in projects plan (to extend by additional distro testing ie.) which would be eventually thrown at infra15:49
*** adahms has quit IRC15:49
anteayado the summit sessions have names?15:50
*** asselin_ has joined #openstack-meeting15:50
anteayadistro testing?15:50
anteayathat is a new one for me15:50
*** dzimine has joined #openstack-meeting15:50
anteayawe are discussing packaging repos, that were hoped to be shared by different distros and are looking less likely now15:50
anteayahi asselin_15:50
anteayawe have talks every summit about testing15:51
*** dwalleck has quit IRC15:51
anteayasince we have a whole project dedicated to the topic, the qa project15:51
anteayaI'm light on details on how this is affecting infra15:51
anteayaI'm not saying its not, I'm saying I don't have the same perspective you have15:52
anteayaand need some detail or references to understand15:52
anteayaand right now I have none15:52
wznoinskanteaya: ok, my 'if infra' was 'in case infra' rather than 'because infra wants to increase testing'15:52
*** alop has joined #openstack-meeting15:52
anteayawell infra is consuming the common-ci solution15:52
anteayaas fast as new modules are merged15:53
*** e0ne is now known as e0ne_15:53
anteayaso in terms of infra should use the common-ci solution15:53
anteayawe are15:53
asselin_yes! :)15:53
anteayaas soon as there is anything to consume15:53
anteayaasselin_: thanks for all your hard work!15:53
anteayaso we seem to be in a close to wrap up place15:54
anteayaI'll just remind folks that when discussing topics15:54
anteayait is really helpful to not assume anyone else knows the details of what you are talking about15:54
anteayaso bringing links with you is really helpful15:54
*** hichihara has quit IRC15:54
anteayaetherpads, mailing list threads, summit session topics, anything15:55
anteayaplease bring the link so that others, who may be interested in understanding what you are trying to say, can follow along15:55
*** e0ne_ is now known as e0ne15:55
anteayaanything more for today before we wrap up?15:55
*** flashgordon has joined #openstack-meeting15:55
asselin_re common-ci solution. I'll request zuul patches to merge today15:56
anteayaasselin_: wonderful15:56
*** pgbridge has joined #openstack-meeting15:56
asselin_so next, requesting reviews on the nodepool patches15:56
anteayahave you links so taht those present can review quickly if they wish15:56
*** devkulkarni has joined #openstack-meeting15:56
asselin_looking for link now15:57
*** derekh has quit IRC15:58
asselin_didn't find the others....but ping we later if you're interested....15:58
anteayathank you asselin_15:58
anteayathanks all for your attendance and participation today15:58
anteayasee you next week15:59
*** openstack changes topic to "OpenStack Meetings ||"15:59
openstackMeeting ended Mon Jun 29 15:59:04 2015 UTC.  Information about MeetBot at . (v 0.1.4)15:59
openstackMinutes (text):
*** patrickeast has left #openstack-meeting15:59
*** gyee has joined #openstack-meeting16:00
*** topol has joined #openstack-meeting16:00
rakhmerov#startmeeting Mistral16:00
openstackMeeting started Mon Jun 29 16:00:47 2015 UTC and is due to finish in 60 minutes.  The chair is rakhmerov. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Mistral)"16:00
openstackThe meeting name has been set to 'mistral'16:00
*** fawadk has quit IRC16:01
*** yamamoto has joined #openstack-meeting16:01
*** puranamr has joined #openstack-meeting16:02
rakhmerovanyone here?16:03
*** dwalleck has joined #openstack-meeting16:03
devkulkarnihi rakhmerov16:03
rakhmerovhow are you?16:03
devkulkarnidoing fine16:03
xylan_kongrakhmerov: hi16:03
*** tariqne has joined #openstack-meeting16:03
rakhmerovxylan_kong, hi16:03
*** leeantho has joined #openstack-meeting16:04
rakhmerovok, let's start the meeting16:04
rakhmerovthe agenda is at:
rakhmerov#topic Review action items16:04
*** openstack changes topic to "Review action items (Meeting topic: Mistral)"16:04
rakhmerovthere was just one AI16:05
rakhmerovNikolayM: discuss yaql 1.0 with Murano team16:05
rakhmerovNikilayM, you're here?16:05
xylan_kongdidn't met him today16:05
*** ajayaa has quit IRC16:05
rakhmerovruhe, do you happen to know where we are going to have YAQL 1.0 in global requirements?16:06
rakhmerov...where -> when ...16:06
ruherakhmerov: JFYI the main driver of yaql 1.0 adoption in Murano, Stan Lagun, is currently on a long sick leave, so there was not much progress in this area recently in Murano16:06
rakhmerovooh, ok16:06
*** jlanoux has quit IRC16:07
rakhmerovso we'll keep this AI active16:07
ruheyeah. Murano team keeps this item as a must have in Liberty16:07
rakhmerov#action NikolayM: talk to Stan Lagun about YAQL 1.0 inclusion into global requirements16:07
rakhmerovruhe, ok, got it16:07
*** annegentle has quit IRC16:07
rakhmerovthat's good16:07
rakhmerovwe just wanted to switch to it asap because it's kind of a part of Mistral DSL from a user perspective16:08
*** rwsu has joined #openstack-meeting16:08
rakhmerovbut that's ok16:08
rakhmerov#topic Current status (progress, issues, roadblocks, further plans)16:08
*** openstack changes topic to "Current status (progress, issues, roadblocks, further plans) (Meeting topic: Mistral)"16:08
rakhmerovlet's quickly report our statuses, as usually16:08
xylan_kongmy status16:09
xylan_kong* get rid of openstack/common package, to comply with the whole upstream behavior16:09
xylan_kong* fix some bugs and review work16:09
xylan_kong* write a proposal for removing utils.wf_trace module16:09
rakhmerovxylan_kong, is that openstack/common task considered completed?16:10
xylan_kongyes, sure16:10
rakhmerovok, perfect16:10
*** mrmartin has quit IRC16:10
*** geoffarnold has joined #openstack-meeting16:10
rakhmerovas far as that wf_trace module, what's wrong with it?16:10
rakhmerovwhy do you want to replace it?16:10
rakhmerovwe might have discussed it with you a while ago16:11
xylan_kongit's ok :-) just a little redundant IMO16:11
rakhmerovI don't remember though16:11
*** unicell has quit IRC16:11
*** comay has joined #openstack-meeting16:11
rakhmerovok, so when are you planning to come up with your proposal?16:11
xylan_kongjust a little weird we add a module to implement a feature that oslo.log has16:11
*** puranamr has quit IRC16:12
rakhmerov#action xylan_kong: proposal to replace utils.wf_trace with oslo.log16:12
*** radek__ has joined #openstack-meeting16:12
rakhmerovok, I think it's more or less clear, just want to see some details on that16:12
rakhmerovmy status: implemented "Workflow variables" and released Liberty 1 last week, also discussed and reviewed a bunch of changes with the team16:12
*** puranamr has joined #openstack-meeting16:13
rakhmerovI made a mistake with client versioning on Friday so had to fix it today16:13
*** lazy_prince has joined #openstack-meeting16:13
rakhmerovspent a lot of time on that16:13
devkulkarni+1 rakhmerov16:13
xylan_kongyeah, i notice that, nice work16:13
*** singlethink has joined #openstack-meeting16:14
rakhmerovnice work?? you kidding? :) I actually deserve a serious punishment :)16:14
xylan_kongwe correct it anyway16:14
rakhmerovanyway, it's ok now16:14
*** DericHorn-HP has quit IRC16:14
rakhmerovdevkulkarni: btw, sorry that I can't catch you in our IRC channel16:15
devkulkarnirakhmerov: :) is the new client released to global-requirements?16:15
rakhmerovyou write usually when I'm asleep )16:15
rakhmerovdevkulkarni: we need to fix and merge this patch:
rakhmerovhoping it'll be done very soon16:15
devkulkarnirakhmerov: no worries.. I am in US Central16:15
rakhmerov1-2 days16:15
rakhmerovyeah, I guess I'm 12 hours ahead of you )16:16
devkulkarnirakhmerov: ok, will keep an eye out on it16:16
rakhmerovdevkulkarni: so do you have a problem because of a Mistral client versioning as well?16:16
rakhmerovyou're working on solum, right?16:16
devkulkarnirakhmerov: I guess so.. I had added an open dicussion item16:17
*** aimon has joined #openstack-meeting16:17
*** henrynash has quit IRC16:17
devkulkarniyes, I am part of the solum team16:17
*** DericHorn-HP has joined #openstack-meeting16:17
devkulkarniis this issue similar to what you were seeing?16:17
*** galstrom is now known as galstrom_zzz16:17
rakhmerovgive me a sec..16:17
rakhmerovI'll check16:17
xylan_kongi saw it16:18
rakhmerovyeah, exact same issue16:18
rakhmerovit should be now ok16:18
*** NikolayM has joined #openstack-meeting16:18
NikolayMhi everyone16:18
xylan_kongNikolayM: hi16:18
rakhmerovhey, NikolayM16:18
devkulkarni rakhmerov: you mean it should not happen after the above mentioned patch is merged, right?16:18
rakhmerovI kept that action item for you about figuring our YAQL 1.0 perspectives16:19
*** claudiub has joined #openstack-meeting16:19
rakhmerovdevkulkarni: nope, it's not related with that patch16:19
*** henrynash has joined #openstack-meeting16:19
devkulkarnioh okay16:19
NikolayMmy status: Implementing new RPC layer, have an idea to not use pika but use kombu instead (because it is already in global-requirements)16:19
*** arnaud____ has quit IRC16:19
rakhmerovit was happenning because of wrong tags in git history16:19
rakhmerovdevkulkarni: so basically I pushed by mistake16:20
*** asselin_ has quit IRC16:20
*** s3wong has joined #openstack-meeting16:20
devkulkarnirakhmerov: ok, got it. and you mentioned you fixed that this morning. got it.16:20
rakhmerovthen I pushed the right one, 0.3.0 but PBR can't build the project for 0.3.0 if there's a greater version (
*** m4dcoder has joined #openstack-meeting16:21
*** puranamr_ has joined #openstack-meeting16:21
rakhmerovso, devkulkarni: keep in mind that the right version for the client now is 1.0.016:21
devkulkarnirakhmerov: ok, makes sense. thanks for addressing this issue.16:21
rakhmerovI sent out the info about that in ML16:21
m4dcoderhey, Renat. sorry i'm late.16:21
rakhmerovdevkulkarni: btw, I have a question for you16:21
devkulkarnirakhmerov: sure16:21
*** beekneemech has joined #openstack-meeting16:21
rakhmerovm4dcoder: hey! no problem16:21
rakhmerovdevkulkarni: does Solum still use Mistral API v1.0?16:22
rakhmerovor switched to v2?16:22
rakhmerovv2 is the latest16:22
devkulkarniI think we are still on v116:22
devkulkarniwhen was v2 released?16:22
rakhmerovpretty long time ago actually16:22
rakhmerovthe thing is that stable/kilo doesn't support v1 anymore16:22
rakhmerovthe corresponding code has been removed16:23
devkulkarniI see.. I will have to go back and check.16:23
devkulkarnioh okay. thanks for the heads up16:23
*** puranamr has quit IRC16:23
rakhmerovso you may want to check that and let us know, we can help you switch to v216:23
*** bnemec has quit IRC16:23
devkulkarniI will get with the solum team to check where we are with it16:23
devkulkarnisounds good16:23
rakhmerovfeel free to ask our help16:23
devkulkarnisure thing.16:24
devkulkarniyou guys have been pretty helpful :)16:24
rakhmerovyou're very welcome16:24
rakhmerovm4dcoder: can you print your status quickly?16:24
m4dcodersure. working on the "resume" bp.16:25
*** ygbo has quit IRC16:25
m4dcoderand then right now just waiting for team to help me with the mysql/psql patch (mysql version and deadlock in scheduler)16:25
rakhmerovI see16:25
*** puranamr_ has quit IRC16:26
rakhmerovsorry, I didn't read your last email carefully16:26
rakhmerovabout mysql16:26
rakhmerovwhat I understood from it is that MySQL 5.5 doesn't support even milliseconds16:26
*** puranamr has joined #openstack-meeting16:26
rakhmerovbut I don't know if we even need them16:26
rakhmerovwhat do you think?16:26
m4dcoderlooks like it unless i'm mistaken.16:27
*** fawadkhaliq has joined #openstack-meeting16:27
NikolayMcan we use different variants with 5.5 and 5.6?16:27
NikolayMsay, use fractional secs in 5.6 and do not use if 5.516:27
*** puranamr_ has joined #openstack-meeting16:27
rakhmerovmy whole point is: I'd like to be compatible with other OpenStack projects in that regard16:27
rakhmerovNikolayM, yes, something like this16:27
*** puranamr has quit IRC16:27
rakhmerovI just don't want to lose the ability to work on mysql 5.516:28
m4dcoderi think we do need msec at the minimum unless we have no choice.  we can have actions/tasks launched msec about from each other.16:28
*** spligak has joined #openstack-meeting16:28
*** larainema has quit IRC16:28
*** doude has quit IRC16:28
*** puranamr has joined #openstack-meeting16:28
rakhmerovotherwise, imagine that we installed OpenStack where all projects are tested agains 5.5 but we'll have to have another mysql 5.6 specifically for Mistral16:28
*** Zhongjun has quit IRC16:28
*** larainema has joined #openstack-meeting16:28
m4dcoderif we are sticking with 5.5, then we will have to change how timestamp is compared in the models.  because right now, the unit tests fail at self.assertEqual(created, fetched) where created has fractional seconds in timestamps.16:29
*** baoli has quit IRC16:29
rakhmerovI think it's just a wrong test case16:29
*** aranjan has joined #openstack-meeting16:29
*** baoli has joined #openstack-meeting16:31
rakhmerovok, m4dcoder, in any case we still owe you a review for your last patch16:31
*** nadeem has joined #openstack-meeting16:31
rakhmerovas far as the deadlock, it's one of the things I'm going to tackle this week16:31
*** nadeem has quit IRC16:31
rakhmerovmyself or NikolayM16:32
rakhmerovhe also knows all the pitfalls16:32
*** nadeem has joined #openstack-meeting16:32
*** puranamr_ has quit IRC16:32
*** yamahata has quit IRC16:32
rakhmerov#action rakhmerov: check Winson's info about deadlocks occurring in scheduler16:32
rakhmerovm4dcoder: btw, does that deadlock only happens with mysql?16:33
m4dcoderit happends with psql16:33
*** radek_ has joined #openstack-meeting16:33
rakhmerovmsql is fine?16:34
*** radek__ has quit IRC16:34
*** aranjan has quit IRC16:34
m4dcoderi don't recall.  i was testing that mostly on postgresql.  but i can try and let you know later today.16:34
rakhmerovit's a usefull info actually16:34
*** dwalleck has quit IRC16:34
rakhmerovyeah, the thing is that we run Mistral with mysql all the time and scheduler works16:35
rakhmerovthen can you pls send us your configuration for both Mistral and Postgres?16:35
*** krtaylor has quit IRC16:35
m4dcodersure i'll sent that to you later today16:35
rakhmerovso that we could see all TX properties applied to your operations16:35
rakhmerovok, thanks16:35
*** henrynash has quit IRC16:35
NikolayMI think it is by the reason of using engine directly in tests16:36
*** comay has quit IRC16:36
NikolayMin tests, we even don't use the engine client but use engine16:36
*** sahid has quit IRC16:36
NikolayMand in end of each test we delete all stuff from the DB, right?16:36
rakhmerov#action m4dcoder: send conf files for Mistral and Postgres to investigate deadlocks in scheduler16:37
NikolayMisn't it a block for DB?16:37
*** maxdml has joined #openstack-meeting16:37
*** unicell has joined #openstack-meeting16:37
*** comay has joined #openstack-meeting16:37
NikolayMwhat do you think, guys?16:38
rakhmerovNikolayM: it's supposed to be but if it really happens only for Postgres then I believe Winson's Postgres DB is not just propertly configured16:38
rakhmerovas we require in scheduler16:38
*** yamamoto has quit IRC16:38
*** jckasper has quit IRC16:38
NikolayMooh, I guess it also happens for mysql16:38
rakhmerovmay be16:38
m4dcoderIf that's the case, then you'll need to provide some instruction on how to properly configure it.16:38
*** dwalleck has joined #openstack-meeting16:39
rakhmerovm4dcoder: yes, our fault16:39
*** henrynash has joined #openstack-meeting16:39
rakhmerovNikolayM: your assumption about not using engine client also looks interesting16:39
m4dcoderno one's fault.  just need some clarification and i'm reporting what i'm observing.16:39
*** dguerri is now known as dguerri`16:40
rakhmerov#info Do we need to use engine client in unit tests instead of engine directly?16:40
rakhmerovm4dcoder: yes, sure16:40
rakhmerovanyway, I'm sure we'll get it done soon16:40
devkulkarnimy topic in open-discussion has been already covered. need to run.. signing-off. thanks rakhmerov for the help.16:40
*** devvesa has quit IRC16:40
rakhmerovit's the interesting and important issue but the fix should be simple16:40
*** devkulkarni has left #openstack-meeting16:41
rakhmerovdevkulkarni: thanks for coming!16:41
*** maurosr has quit IRC16:41
*** yamamoto has joined #openstack-meeting16:41
*** radek_ has quit IRC16:41
rakhmerovok, what else do we have on a plate...16:41
*** neeti has quit IRC16:41
rakhmerov#topic Duplicating messages on executors16:41
*** openstack changes topic to "Duplicating messages on executors (Meeting topic: Mistral)"16:41
rakhmerovunfortunately, we don't have the author of this topic today with us16:42
xylan_kongrakhmerov: what's that mean?16:42
xylan_kongdo you know that?16:42
rakhmerovbut I'd like to ask you wether you faced it or not?16:42
rakhmerovyeah, xylan_kong, let me explain16:42
*** timello has quit IRC16:43
*** Swami has joined #openstack-meeting16:43
*** jgrimm has quit IRC16:43
rakhmerovso folks from alcatel lucent (Limor, Moshe, Noa) say that when Mistral engine puts a message into MQ (to run action) then more than one executor can poll it from MQ16:43
rakhmerove.g. 216:43
*** annp has quit IRC16:43
rakhmerovI don't really know how the heck that may happen16:43
rakhmerovbut maybe you came across this issue16:44
rakhmerovm4dcoder: did you?16:44
xylan_kongrakhmerov: i can test it tomorrow with the latest code16:44
rakhmerovoooh, wait a second16:45
rakhmerovI actually got an email from them with their configuration and topology16:45
*** xingchao_ has joined #openstack-meeting16:45
rakhmerovit says they use QPID16:45
rakhmerovnot RAbbit16:45
xylan_kongi heard from Limor about this issue, but i don't meet in fact16:45
*** henrynash has quit IRC16:45
rakhmerovook, looks like it's qpid16:46
rakhmerovnot rabbit16:46
xylan_kongyes, they use qpid, i guess rabbitmq doesn't have this problem16:46
*** dwalleck has quit IRC16:46
rakhmerovyep, then it should be tested with qpid16:46
rakhmerovmaybe qpid should be tuned somehow, dunno16:46
*** henrynash has joined #openstack-meeting16:47
*** radek_ has joined #openstack-meeting16:47
rakhmerovalright, anyway, we could spend some time investigating it16:47
xylan_kongi'm not familiar with qpid, are you?16:47
rakhmerovI'm not either16:47
rakhmerovjust heard about it briefly16:47
rakhmerovI think it should be rather a BP than a bug though since we've never even thought about using qpid16:48
xylan_konganyway, i will test it again with rabbitmq to ensure it's ok with the latest code16:48
rakhmerovwell, as far as rabbit we would have noticed that because we run it mostly every day16:49
*** maurosr has joined #openstack-meeting16:49
xylan_kongyes, actually16:49
*** DericHorn-HP has quit IRC16:49
rakhmerovwhat I mean is that we need to aim to make it work with qpid intentionally16:49
rakhmerovit's a BP16:49
*** zz_jgrimm has joined #openstack-meeting16:49
rakhmerov#action rakhmerov: create a BP to make Mistral work with qpid behind oslo.messaging16:49
*** ildikov_ has quit IRC16:50
*** arvinchou_ has joined #openstack-meeting16:50
*** timello has joined #openstack-meeting16:50
rakhmerovok, don't know what else to say on this topic16:50
rakhmerovneeds to be tested and investigated16:50
*** yamamoto has quit IRC16:51
rakhmerovI guess eventually we need to create a new gate that would run functional tests with qpid16:51
rakhmerov#topic Liberty-2 planning16:51
*** openstack changes topic to "Liberty-2 planning (Meeting topic: Mistral)"16:51
rakhmerovguys, also I was going to talk about Liberty 2 plans but looks like we're running out of time today16:52
*** galstrom_zzz is now known as galstrom16:52
rakhmerovso my suggestion is to send a list of BPs and bugs that are most important for you16:52
*** dwalleck has joined #openstack-meeting16:52
rakhmeroveither to myself or even better to openstack-dev16:52
xylan_kongok, no problem16:53
rakhmerovso that I could collect them, assign them etc. etc.16:53
*** balajiiyer has quit IRC16:53
*** changbl has quit IRC16:53
*** DericHorn-HP has joined #openstack-meeting16:53
rakhmerovI, of cource, have a high-level picture but also want to hear from you16:53
*** yamamoto has joined #openstack-meeting16:54
rakhmerov#action xylan_kong, m4dcoder, NikolayM, LimorStotland: send a list of desired BPs and bugs for Liberty-2 so that we could plan16:54
*** dguitarbite has joined #openstack-meeting16:54
*** mrmartin has joined #openstack-meeting16:54
rakhmerov#topic Open Discussion16:55
*** openstack changes topic to "Open Discussion (Meeting topic: Mistral)"16:55
rakhmerovm4dcoder: how is that pause/resume thing going?16:55
m4dcoderrakhmerov: i have not seem the problem with multiple executors getting same action from rabbitmq.16:55
rakhmerovok, yes16:55
m4dcodergood progress with pause/resume.16:56
rakhmerovdoes that patch on review completes it?16:56
rakhmerovyou're planning to do something else?16:56
*** dwalleck has quit IRC16:57
*** Murali has joined #openstack-meeting16:57
*** Fdot has quit IRC16:57
m4dcoderhowever, my colleagues and i are debating (just now) whether we should let users change input data on resume.  the patch was WIP to let dmitri see where i'm at.  no need to review yet.16:57
*** vigneshvar has joined #openstack-meeting16:57
m4dcoderpatch is WIP not complete yet.16:58
rakhmerovyeah, I know16:58
rakhmerovok, keep us posted please16:58
rakhmerovok, guys, I think it's time to end our meeting16:58
rakhmerovthanks a lot for coming!16:58
rakhmerovsee you next time16:59
xylan_kongok, see you16:59
*** openstack changes topic to "OpenStack Meetings ||"16:59
openstackMeeting ended Mon Jun 29 16:59:15 2015 UTC.  Information about MeetBot at . (v 0.1.4)16:59
openstackMinutes (text):
*** mpaolino has quit IRC16:59
*** rluethi has joined #openstack-meeting16:59
*** m4dcoder has quit IRC16:59
*** e0ne has quit IRC16:59
*** matjazp has joined #openstack-meeting17:00
vigneshvarmatjazp: hi17:00
rluethihi all17:00
matjazphi all17:00
matjazpvigneshvar: hey17:00
vigneshvarhi all17:00
dguitarbite#startmeeting training-guides17:00
openstackMeeting started Mon Jun 29 17:00:58 2015 UTC and is due to finish in 60 minutes.  The chair is dguitarbite. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: training-guides)"17:01
openstackThe meeting name has been set to 'training_guides'17:01
dguitarbiteRoll call17:01
dguitarbiteI see that the agenda is outdated17:02
matjazpdguitarbite: standard topics, I guess17:02
*** Murali has quit IRC17:02
dguitarbiteSO what is the important topic for today?17:02
rluethiwe fixed the bug. yay.17:02
*** xingchao_ has quit IRC17:03
rluethithanks, sayali, vigneshvar.17:03
dguitarbite#topic training-labs17:03
*** armax has quit IRC17:03
*** openstack changes topic to "training-labs (Meeting topic: training-guides)"17:03
vigneshvarrluethi: :)17:03
dguitarbiteThat is good news17:03
rluethiit was yet another race.17:03
*** krtaylor has joined #openstack-meeting17:03
dguitarbiteThis patch should solve the issue. I will run repeat test overnight17:04
dguitarbiteand report back the stats. prob next meeting17:04
*** cody-somerville has quit IRC17:05
*** armax has joined #openstack-meeting17:05
*** armax has quit IRC17:05
*** dwalleck has joined #openstack-meeting17:05
*** yamamoto has quit IRC17:05
vigneshvarvigneshvar: I still have some doubts on it. Figuring it out17:05
*** mwagner_afk has quit IRC17:06
matjazpdguitarbite: we still need CI for the labs.. anyone has any idea where to get necessary infra for it?17:06
dguitarbitematjazp, Yes17:06
*** yamamoto has joined #openstack-meeting17:06
rluethimatjazp: the main problem with labs CI is still that we don't have a kvm backend yet.17:06
dguitarbiteWe need KVM backend17:07
dguitarbiterluethi, +117:07
*** ivar-lazzaro has joined #openstack-meeting17:07
dguitarbiteAnd also the CI will be shared for testing the labs and install-guides. I guess we will run in parallel from this point on.17:07
dguitarbiteI suggest waiting a bit for the same. Hopefully we should have this out by Liberty release.17:07
matjazpsure, but virtbox will stay, right? some ppl will try this on it regardless of the kvm option17:07
dguitarbitematjazp, yes17:07
dguitarbiteWe will add virtualbox support too.17:08
dguitarbiteIt should be very similar. And with Python some issues on Windows should be resolved which we currently face with BASH.17:08
dguitarbitematjazp, although the question of packaing python windows binaries is still hanging17:08
dguitarbitebut it works for sure.17:08
*** lsmola has quit IRC17:09
rluethimatjazp: virtualbox support needs to stay in, agreed.17:09
*** sankarshan is now known as sankarshan_away17:09
rluethinot needing KVM is one of our main advantages.17:09
*** yamamoto has quit IRC17:09
*** Alexey_Nexenta has quit IRC17:10
matjazpin the mean time, we should just do this CI thing in the beefier VM, install VBox and run scripts as they are..17:10
dguitarbitematjazp, In future I also plan to add USB Booting Clusters17:10
dguitarbiteso the base OS should not matter much17:10
rluethimatjazp: you lost me there. can you elaborate?17:10
*** baoli has quit IRC17:11
dguitarbitematjazp, The issue is to add VirtualBox related scripts for a few months. I am not sure if the infra team would be happy with that.17:11
dguitarbiteMeaning setting up the environment for VirtualBox!17:11
matjazpwe can do testing of bash scripts in the somwhat larger VM? OR if we can get it, in the bare metal box17:11
dguitarbiteYes, we could do that17:11
*** kebray has quit IRC17:12
*** baoli has joined #openstack-meeting17:12
*** lpeer__ has quit IRC17:12
*** annegentle has joined #openstack-meeting17:12
rluethimatjazp: which somewhat larger vm?17:13
dguitarbitematjazp, Here is my plan17:13
matjazpIdeal would be to put a fresh copy of OS on bare metal, install Vbox and test osbash scripts. It could even be a job that runs one a day, not necessary for every commit17:13
dguitarbite1. Get Training guides promoted from incubation. Get labs as seperate repository (training-labs) under training-guides17:13
dguitarbiteAnd then propose the CI changes17:13
dguitarbiteKVM backend would be added somewhere along the way.17:13
dguitarbiteI am going to sit and plan this thing out completely with Andreas Jaeger on Wed. Also meanwhile add the Landing page for training etc.17:14
matjazprluethi: we can put everything inside a large VM (large=more RAM), run cluster inside on Vbox, just to see if everything works.. I doubt it would be fast enough to test race conditions... or maybe, it would be even better, as it would be slow17:14
rluethimatjazp: oh, you mean using the openstack ci infrastructure and install virtualbox there?17:14
dguitarbiteJust trying to figure out the best possible way and sequence, along with the least disruptive path.17:14
*** sigmavirus24 is now known as sigmavirus24_awa17:15
dguitarbitematjazp, that should not be considered. I understand your logic, but the third level virt! would cause lots of races17:15
dguitarbiteand lead the jobs to fail or with so many exceptions that it would not make any sense17:15
matjazprluethi: well... yes, but I'm afraid we don't fit in onfra framework... no one want's Vbox as a dependency17:15
dguitarbiteWe would need 1st level virt for the VM's17:15
dguitarbiteand with the install-gudies automated testing, we will have more reasons to request the same.17:16
*** balajiiyer has joined #openstack-meeting17:16
*** sdake has joined #openstack-meeting17:16
matjazpdguitarbite: yes, but we don't have bare metal boxes, do we? so maybe race conditions would emerge even more frequently on SLOW nested VM17:16
rluethiwell, at least we have the scripts in place so everyone can test at home.17:17
*** achanda has quit IRC17:17
rluethiand with the new functionality, we can test starting from a snapshot which speeds things up a lot.17:17
*** PrashantS has quit IRC17:17
*** PrashantS has joined #openstack-meeting17:18
dguitarbitematjazp, We can request more stuff when we are independent project and also we can get better hardware (may be once a week or fortnight). Also having the install-gudies team with us would make it easier to achieve,17:18
*** exploreshaifali has joined #openstack-meeting17:18
*** mrmartin has quit IRC17:18
dguitarbitethe worst case we get good KVM VM's, then we configure them to run the scripts directly (but networking issues) and I am not exactly sure how to do this one or even if its possible.17:19
*** sayalilunkad has joined #openstack-meeting17:19
vigneshvarwhen we say testing we need to test with windows as well right17:19
dguitarbitematjazp, and again netsted virtualization in KVM is much better (faster) w.r.t. virtualbox.17:19
*** sdake_ has quit IRC17:20
dguitarbitevigneshvar, Not in the CI17:20
sayalilunkadSorry about the delay17:20
dguitarbitesayalilunkad, hi17:20
vigneshvarsayalilunkad: hi17:20
dguitarbitevigneshvar, testing could be done on Windows but I cannot gurantee automated CI testing.17:20
matjazpdguitarbite: it is, and it doesn't matter if the testing is really slow, we don't have a lot of changes in  the code17:20
matjazpvigneshvar: is right.. if we "support" Win, than we should test it17:21
vigneshvar But if we have nested virtualization we could do for both !! is n't it17:21
dguitarbitematjazp, exactly. Once a fortnight works for our use-case. And also it would be easier to acquire this time during low load (sunday's for ex.) from the infra team.17:21
*** tariqne has quit IRC17:21
dguitarbitevigneshvar, KVM support for netsted virtualization is inbuilt in the Linux kernel17:22
dguitarbiteand its much faster as it has very low overhead.17:22
*** PrashantS has quit IRC17:23
vigneshvardguitarbite: I meant for testing virtual box , we could use a large kvm VM17:23
vigneshvarand then test both windows as well as linux (vbox)17:23
dguitarbitevigneshvar, yes, but that will not necessarily make it faster.17:23
vigneshvardguitarbite: True17:24
matjazpvbox is slow and it doesn't support HW nested virt.... it is so slow that devstack I can't really run nested windows guests in a virtualised openstack... Just booting takes forewer :(17:24
dguitarbitevigneshvar, I tried this some time back on a 32 GB i7 machine17:24
matjazp*that IN devstack17:24
dguitarbiteConclusion is similar to what matjazp says17:25
matjazpdguitarbite: and that is a machine that almost noone in the training has with them17:25
vigneshvardguitarbite: I accept that. I just felt that testing might be incomplete17:25
*** hogepodge has quit IRC17:26
dguitarbitematjazp, I know. I was just trying to see if scaling up works in this case.17:26
matjazpvigneshvar: if we could get a bare metal box (e.g. via ironic in openstack?), than this is all moot point17:27
*** hogepodge has joined #openstack-meeting17:27
rluethivigneshvar: we should aim for complete test coverage, but we take one step after the other and we may never get there :-)17:27
dguitarbite#topic general-discussion17:28
*** openstack changes topic to "general-discussion (Meeting topic: training-guides)"17:28
vigneshvarrluethi: right17:28
vigneshvarmatjazp: +117:28
dguitarbiterluethi, +117:30
*** changbl has joined #openstack-meeting17:30
*** ramashri has quit IRC17:30
*** aranjan has joined #openstack-meeting17:31
rluethiso I guess we're done!?17:31
*** dontalton has joined #openstack-meeting17:32
dguitarbiteI am quite busy this week. But by the end of the this week or early next week I will send an email to the docs ML with the plan.17:32
*** ajayaa has joined #openstack-meeting17:32
dguitarbiterluethi, I guess so.17:32
dguitarbiteAny other topic?17:32
matjazpwhat about shifting meeting time, as sean asked? discuss on ML?17:32
*** xyang1 has joined #openstack-meeting17:33
dguitarbiteI need to see the mail.17:33
sayalilunkadtokyo summit sessions?17:33
sayalilunkadI would like to keep one on the labs17:33
*** yamahata has joined #openstack-meeting17:33
vigneshvarsayalilunkad: +117:33
sayalilunkadand maybe a hands on too17:33
dguitarbiteI dont mind moving the meeting timing. May be make it much better for CEST this time.17:33
matjazpsayalilunkad: sean can't be here until then17:33
rluethimatjazp: sean didn't indicate any alternatives. "some other time" is not all that helpful.17:33
dguitarbiterluethi, I assume we all discuss the common free time we all have most of the weeks.17:34
*** balajiiyer1 has joined #openstack-meeting17:34
*** ajmiller has quit IRC17:34
*** singlethink has quit IRC17:34
*** aranjan has quit IRC17:35
*** ajmiller has joined #openstack-meeting17:35
sayalilunkadcool, we can discuss that on the ML17:36
*** balajiiyer has quit IRC17:36
*** sahid has joined #openstack-meeting17:36
sayalilunkadrluethi dguitarbite what do you guys think about the labs session for tokyo ?17:36
sayalilunkaddeadline for proposals is july 15th I guess17:37
*** yassine has quit IRC17:37
rluethisayalilunkad: would love to do it, but whether I can afford to be there is uncertain17:37
sayalilunkadwe can always propose it, we need to get selected first :)17:38
*** padkrish has joined #openstack-meeting17:38
rluethipropose away.17:38
dguitarbitesayalilunkad, I like the idea. We need to advertise a bit more about this.17:40
dguitarbiteAny other topic?17:40
sayalilunkadok, lets have a call soon then.17:40
vigneshvarmay be we should decide by this week17:40
dguitarbitesayalilunkad, for the session more than hands on I would like to suggest joining the upstream-training part.17:41
dguitarbiteIf that is ok with you.17:41
sayalilunkaddguitarbite: I agree. Will write an email to stef about that17:41
dguitarbiteOk, thanks :).17:41
dguitarbitesayalilunkad, I guess you missed this but Roger has fixed the race with metadata. So we should have working Juno cluster!17:42
sayalilunkadoh awesome! I am yet to take a look at that.17:42
*** pvaneck has joined #openstack-meeting17:42
matjazpsayalilunkad: stef changed jobs17:42
matjazphe is at dreamhost now17:42
dguitarbitematjazp, what?17:42
matjazpnot sure who will take his job at the foundation?17:43
dguitarbiteSo will he not participate again?17:43
sayalilunkadmatjazp: oh. so doesn't hold his position witht he foundation?17:43
dguitarbiteI assumed that upstream-training was not exactly fixed to his role at Foundation If I am correct.17:43
matjazpsayalilunkad: don't know, but I guess that he'll be busy with new assigments?17:44
matjazpdguitarbite: sure, but he was the "go to guy" for that :)17:44
dguitarbitematjazp, yeah17:44
dguitarbitefingers crossed in that case.17:44
sayalilunkadmatjazp: ah yes.17:44
matjazpmaybe sean has some more info about upstream training... we should ask him over ML17:45
*** kebray has joined #openstack-meeting17:45
*** ItSANg___ has quit IRC17:45
*** exploreshaifali has quit IRC17:45
*** ItSANgo_ has joined #openstack-meeting17:45
*** Sukhdev has quit IRC17:46
*** achanda has joined #openstack-meeting17:46
*** armax has joined #openstack-meeting17:46
*** marun has joined #openstack-meeting17:46
*** lazy_prince has quit IRC17:47
dguitarbiteSo anything else?17:47
matjazpI'm good17:47
rluethime too17:47
*** nadeem has left #openstack-meeting17:47
*** safchain has quit IRC17:48
dguitarbiteOk, so lets end it.17:48
matjazpsee you next week17:48
*** openstack changes topic to "OpenStack Meetings ||"17:49
openstackMeeting ended Mon Jun 29 17:49:01 2015 UTC.  Information about MeetBot at . (v 0.1.4)17:49
openstackMinutes (text):
*** singlethink has joined #openstack-meeting17:49
*** rluethi has left #openstack-meeting17:49
*** PrashantS has joined #openstack-meeting17:49
*** dguitarbite has quit IRC17:49
*** annegentle has quit IRC17:49
*** pelix has quit IRC17:51
*** spzala has joined #openstack-meeting17:51
*** annegentle has joined #openstack-meeting17:51
*** matjazp has quit IRC17:52
*** rvasilets_ has left #openstack-meeting17:54
*** enikanorov2 has quit IRC17:55
*** niclem has joined #openstack-meeting17:55
sarob#startmeeting akanda18:00
openstackMeeting started Mon Jun 29 18:00:08 2015 UTC and is due to finish in 60 minutes.  The chair is sarob. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: akanda)"18:00
openstackThe meeting name has been set to 'akanda'18:00
*** mwagner_afk has joined #openstack-meeting18:02
sarobanyone else?18:02
*** maxdml has quit IRC18:03
*** sigmavirus24_awa is now known as sigmavirus2418:03
sarobagenda is sloppy this morning18:04
*** dzimine has left #openstack-meeting18:04
sarob#topic last meeting action items18:05
*** openstack changes topic to "last meeting action items (Meeting topic: akanda)"18:05
sarobi had the only task action18:05
sarobi cleared out the builder repo18:05
*** novas0x2a|laptop has joined #openstack-meeting18:05
sarobi still need to clear out the github:akanda repos18:05
sarobi will get that going today18:05
sarob#action sarob clear out github:akanda repos with readme to current repos18:06
sarobmoving on18:06
sarob#topic m1 cleanup18:06
*** openstack changes topic to "m1 cleanup (Meeting topic: akanda)"18:06
*** annemccormick has quit IRC18:07
*** kebray has quit IRC18:07
sarobi will cut m1 today from last thursday unless there are any objections18:07
*** annemccormick has joined #openstack-meeting18:07
sarobdoc updates and lbaas get pushed to m218:07
*** enikanorov2 has joined #openstack-meeting18:08
*** kebray has joined #openstack-meeting18:08
*** pradipta has quit IRC18:08
*** ivar-laz_ has joined #openstack-meeting18:09
sarobstill no adam_g or davidlenwell?18:09
*** ivar-laz_ has quit IRC18:10
*** yamamoto has joined #openstack-meeting18:10
*** ivar-laz_ has joined #openstack-meeting18:10
adam_goh hey18:10
adam_gwrestling with wifi at this cafe18:10
sarobadam_g: he18:10
*** ivar-laz_ has quit IRC18:11
*** _nadya_ has joined #openstack-meeting18:11
*** ivar-laz_ has joined #openstack-meeting18:12
sarobupdating lbaas and docs to m218:12
*** ivar-lazzaro has quit IRC18:12
sarobany comments on m1 ?18:13
sarobokay moving on18:13
sarob#topic starting m218:13
*** openstack changes topic to "starting m2 (Meeting topic: akanda)"18:14
*** earlephilhower has joined #openstack-meeting18:14
*** earlephilhower has quit IRC18:14
*** pnavarro has quit IRC18:14
sarobdavidlenwell is making a lot a changes with the lbaas driver bp18:14
*** earlephilhower has joined #openstack-meeting18:14
*** sayalilunkad has quit IRC18:15
*** yamamoto has quit IRC18:15
adam_gmissing and
adam_gboth of those could be squashed into one18:15
*** crc32 has joined #openstack-meeting18:15
sarobhmm, true18:16
*** _nadya_ has quit IRC18:16
*** ttrifonov is now known as zz_ttrifonov18:16
sarob#action sarob squash and into one bp and set to M218:16
*** sayalilunkad has joined #openstack-meeting18:17
sarobmarkmcclain: any comments on the driver patch?18:17
markmcclainI've only given a cursory look since the tests were failing18:18
*** sayalilunkad has quit IRC18:18
markmcclainI'm home all this week so I can give it a deeper dive18:18
sarobmarkmcclain: cool18:19
*** ctrath has joined #openstack-meeting18:20
sarobmarkmcclain: you want to take on
sarobmarkmcclain: seems that there shouldnt be much to getting it working since vrrp is already running18:21
*** SumitNaiksatam has quit IRC18:21
markmcclainsure.. it will be next week ebfore I'll be able to get started on it18:21
adam_gmarkmcclain, you might be interested in reviewing and corresponding spec if you have time, too. sorta *just works*, i feel like ive overlooked something18:22
sarobryanpetrello: do you want to take a stab at
sarobryanpetrello: i seem to remember you had some ideas around that18:23
*** novas0x2a|laptop has quit IRC18:23
markmcclainadam_g: awesome I'll add it to the queue18:23
markmcclainsarob: the circuit breaker was probably more from me18:23
sarobmarkmcclain: opps, okay18:24
markmcclainit just came from a prod issue ryanpetrello had faced18:24
*** Sukhdev has joined #openstack-meeting18:24
sarobmarkmcclain: you want to take that on as well then?18:24
markmcclainI'm short of bandwidth to take it on at the moment18:25
markmcclainalso the work for the spares pool might mitigate this somewhat18:26
sarobmarkmcclain: okay, i will leave it hang for now18:26
sarobmarkmcclain: right18:26
*** ivar-laz_ has quit IRC18:26
adam_gi put a initial spec up for the pooling stuff18:27
adam_gi think that'll be blocked on the rug clustering18:27
*** ivar-lazzaro has joined #openstack-meeting18:27
*** jhenner1 has quit IRC18:28
sarobadam_g: you want to own the ha and pooling bp?18:28
adam_gsarob, sure. tho both will probably block on baby unless someone else picks them up while im out18:29
sarobscaling and pooling bp that is18:29
sarobbaby blocker, classic18:29
*** ajayaa has quit IRC18:29
*** _nadya_ has joined #openstack-meeting18:29
*** Sukhdev has quit IRC18:30
*** ijw has quit IRC18:30
*** ivar-lazzaro has quit IRC18:31
sarobleaving vpnaas hanging as well for now18:31
*** amakarov is now known as amakarov_away18:31
*** ivar-lazzaro has joined #openstack-meeting18:32
sarobpuranamr: ideas on
puranamrsarob, did not still put in the bp, but collecting some ideas18:33
puranamrwill wet it and start making additions18:33
*** VanL has joined #openstack-meeting18:33
*** ociuhandu has quit IRC18:34
sarobpuranamr: you should write up a spec18:34
sarobpuranamr: i can help with that18:34
puranamrsarob, sure18:34
*** novas0x2a|laptop has joined #openstack-meeting18:35
*** achanda has quit IRC18:35
*** IlyaG has joined #openstack-meeting18:36
*** achanda has joined #openstack-meeting18:36
*** padkrish has quit IRC18:36
*** NikolayM has quit IRC18:36
sarobid apprec some feedback on as well18:36
*** IlyaG has quit IRC18:37
sarobim hounding davidlenwell on creating a spec for
sarobso y'all deep dive on that when i goes out today18:37
*** singlethink has quit IRC18:38
*** singleth_ has joined #openstack-meeting18:38
*** ildikov_ has joined #openstack-meeting18:38
sarobany other comments on m2 bp?18:38
*** ivar-lazzaro has quit IRC18:38
adam_gnone here18:38
*** nelsnels_ has joined #openstack-meeting18:38
adam_ga spec on the lbaas stuff would be helpful18:38
sarobadam_g: required is better word ;)18:39
adam_gsarob, yes18:39
sarobmoving on ...18:39
adam_glike, the spec should have been written and approved before implementing :)18:39
*** ivar-lazzaro has joined #openstack-meeting18:40
sarobadam_g: yeah, that is a detail that got missed18:40
*** padkrish has joined #openstack-meeting18:40
sarob#topic any other business18:41
*** achanda has quit IRC18:41
*** openstack changes topic to "any other business (Meeting topic: akanda)"18:41
*** nelsnelson has quit IRC18:41
*** afazekas_ has joined #openstack-meeting18:41
markmcclainnothing from me18:42
*** singleth_ has quit IRC18:43
sarobokay dorky details then18:43
*** bryan_att has quit IRC18:43
*** maxdml has joined #openstack-meeting18:43
*** stevemar has quit IRC18:43
sarobwe are 23rd on reviews18:43
adam_gwhat does that mean?18:44
*** krtaylor has quit IRC18:44
*** fawadkhaliq has quit IRC18:44
sarobon openstack projects18:44
*** stevemar has joined #openstack-meeting18:44
*** padkrish has quit IRC18:44
sarobbetter stat18:45
*** padkrish has joined #openstack-meeting18:45
sarobwe are 7th on stackforge commits18:45
sarobit meaning almost nothing18:46
*** novas0x2a|laptop has quit IRC18:46
*** jdurgin has joined #openstack-meeting18:46
sarobbut it does put our stuff next to other groups on a list18:46
sarobthats all the exciting other business i have18:47
sarobpuranamr: anything from you?18:47
*** barrett has joined #openstack-meeting18:47
sarobadam_g: hows baby watch going?18:48
adam_gsarob, good. im on pager duty. due date is wednesday.18:48
sarobadam_g: exciting its almost here18:49
*** padkrish has quit IRC18:49
markmcclainadam_g: exciting times18:49
*** deepika has quit IRC18:50
sarobadam_g: great big ball of good vibes18:50
sarobim going to call the meeting on a good note18:50
sarobeveryone have a great week18:51
*** markvoelker_ has joined #openstack-meeting18:51
*** openstack changes topic to "OpenStack Meetings ||"18:51
*** Sukhdev has joined #openstack-meeting18:51
openstackMeeting ended Mon Jun 29 18:51:35 2015 UTC.  Information about MeetBot at . (v 0.1.4)18:51
openstackMinutes (text):
*** vigneshvar has quit IRC18:52
*** markvoelker has quit IRC18:52
*** xingchao_ has joined #openstack-meeting18:52
*** nelsnels_ has quit IRC18:53
*** VanL has quit IRC18:54
*** nelsnelson has joined #openstack-meeting18:54
*** banix has quit IRC18:54
*** Rockyg has joined #openstack-meeting18:55
*** banix has joined #openstack-meeting18:55
*** xingchao_ has quit IRC18:56
*** sudipto has quit IRC18:57
*** markvoelker_ has quit IRC18:57
*** banix has quit IRC18:57
*** markvoelker has joined #openstack-meeting18:57
*** MeganR has joined #openstack-meeting18:58
*** padkrish has joined #openstack-meeting19:00
*** _amrith_ is now known as amrith19:00
*** padkrish has quit IRC19:00
*** cloudrancher has joined #openstack-meeting19:00
*** natez has joined #openstack-meeting19:01
geoffarnoldSlow start?19:01
*** harshs has joined #openstack-meeting19:01
*** padkrish has joined #openstack-meeting19:01
barrettHi All19:01
*** hogepodge has quit IRC19:02
barrett#startmeeting product_team19:02
openstackMeeting started Mon Jun 29 19:02:14 2015 UTC and is due to finish in 60 minutes.  The chair is barrett. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: product_team)"19:02
openstackThe meeting name has been set to 'product_team'19:02
*** DrBacchus has joined #openstack-meeting19:02
barrettLet's start by taking role call19:02
*** claudiub has quit IRC19:02
*** hogepodge has joined #openstack-meeting19:03
*** jckasper has joined #openstack-meeting19:03
barrettShamail - are you on?19:03
barrettI think it could be a light meeting given the upcoming 4th of July holiday.19:04
*** Apoorva has quit IRC19:04
geoffarnoldOne action I had19:04
geoffarnoldI reached out to Tom to see if there was going to be an Operators Midcycle19:04
geoffarnoldno response19:04
*** ijw has joined #openstack-meeting19:05
geoffarnoldchecked a couple of the other regulars: they hadn't heard anyhing19:05
barrettHmmm, not sure what else we can do to get that one rolling...19:05
Rockygyeah.  Nothing yet.  The size might be a problem19:05
*** rbowen has quit IRC19:05
barrettMaybe we should plan to not try and align with that and set a date for us to meet...?19:05
barrettHi sarob19:05
*** Shamail has joined #openstack-meeting19:06
geoffarnoldDo we want to meet f2f?19:06
*** Apoorva has joined #openstack-meeting19:06
geoffarnoldAh, good. sarob might know19:06
*** banix has joined #openstack-meeting19:06
sarobbarrett: hi!19:06
*** cloudrancher has left #openstack-meeting19:06
Shamailhi everyone19:06
sarobShamail: hi19:06
geoffarnoldsarob, hae you heard anything about an ops midcycle?19:06
barrettgeoffarnold: I'd like to do that if we have can find a time/place that gives us critical mass.19:06
*** VanL has joined #openstack-meeting19:06
barrettHi Shamail19:06
geoffarnoldBased on we're probably looking at mid-Aug19:07
geoffarnoldShall I send out a Doodle poll?19:08
*** cloudrancher has joined #openstack-meeting19:08
*** novas0x2a|laptop has joined #openstack-meeting19:08
barrettGeoffarnold - Pls do. We're looking for meeting area and dates I think.19:09
sarobgeoffarnold: i havent19:09
ShamailAre we giving up on co-location with ops (since we don't know when they are meeting)?19:09
Shamailhi cloudrancher19:09
barrettshamail: I think we should consider that.19:09
geoffarnoldOK, Doodle can do dates, and I'll ask for preferred locations in the comments19:09
Shamailgeoffarnold: Can you also make one of the options 'co-locate with date/place for ops midcycle'?19:10
Shamailor will doodle not allow that19:10
barrettGeoffarnold: Sounds good; If there's an Intel facility in the area where people want to meet, we can probably host it.19:10
ShamailDitto for EMC locations as well barrett19:10
barrettShamail - I think the question is how long do we want to wait for the Ops midcycle to get set?19:10
sarobif y'all want to meet in livermore19:11
geoffarnoldLet's not wait. Aug scheduling is a pain19:11
sarobmy office is always available19:11
ShamailMakes sense barrett19:11
barrettgeoffarnold: +119:11
geoffarnoldLivermore is suppoosed to break 100F tomorrow19:11
Shamailsounds goood geoffarnold19:11
barrettOK - anything else on this topic?19:11
barrettIf not we'll move on19:12
geoffarnoldOK, I'll send out the poll today, look for responses by end of week19:12
natezwhile I'm new here, I have to agree waiting until August will impact the time we have available to plan something impactful for Tokyo.19:12
*** boris-42 has quit IRC19:12
natezI'm very interested in meeting f2f if we can get a center of mass.  with or without the operators meetup.19:12
barrettnatez: Are you thinking second half of July?19:13
geoffarnoldThe trouble with 2nd half July is this:
ShamailYeah...second half of July is already tight between sprints, OSCON, and BoD meeting.19:14
natezwhen I look at August openstack events, it's filling up.  July is more condusive for me beyond the week of OSCON.19:14
RockygEarly August...19:14
RockygDefCore is in Austin week after OSCon, with board meeting right before19:15
barrettI think it would be hard to make it happen before OSCON.19:15
Shamailgeoffarnold: to the bat mobile! I mean doodle poll!19:15
natezhow about somewhere August 1-14?19:15
*** afazekas_ has quit IRC19:15
barrettnatez: +119:15
ShamailLet's conduct the poll19:16
barrettGeoffarnold: We'll leave the doodle in your capable hands. Thanks19:16
barrettLet's move on19:16
sarobyes, plz19:16
ShamailDate ranges look good natez, please vote on the poll.19:16
barrettWe'll revisit in next week's meeting with the poll results inhand.19:16
barrett#topic Use Case Repo19:16
*** openstack changes topic to "Use Case Repo (Meeting topic: product_team)"19:16
barrettRockyG: Do you have any news on this one?19:17
*** fawadkhaliq has joined #openstack-meeting19:17
RockygShould have patch before TC tomorrow.19:17
barrettHow long after that til it could go live?19:17
RockygThis week.  Since it's new, it doesn't need to wait for a repo migration.19:18
*** dguerri` is now known as dguerri19:18
barrettAll sounds good, sounds like we can target posting our use cases next week.19:19
*** ociuhandu has joined #openstack-meeting19:19
RockygI have a question on format. We have user stories and use cases.19:19
RockygUser stories tend to be a workflow.  Use cases are generally a single action?19:20
*** VanL has quit IRC19:20
barrettShamail: Do you want to take that one?19:20
RockygIf Use cases are really small, we'll have hundreds to thousands.19:20
*** dguerri is now known as dguerri`19:20
ShamailUser Stories tend to reflect the purpose of why we are doing something, whereas use case generally implies how it is done/leveraged19:20
ShamailUser Stories tend to be small but get broken into tasks (one user story could generate a lot of tasks)19:21
RockygRight.  and each task is a use case? Or....?19:21
ShamailI think what you are describing would be a task (versus a use case) Rockyg19:21
barrettAnd is a task equal to a BP?19:22
*** mrmartin has joined #openstack-meeting19:22
ShamailUse Case is similar to User Story but User Story leaves more autonomy19:22
RockygHmm.  Ok.19:22
ShamailEach task is equal to a unit of work, so yeah19:22
ShamailExample might be easiest19:22
*** achanda has joined #openstack-meeting19:22
geoffarnoldWiki page, please, with approved taxonomy. We keep going over this.19:22
barrettgeoffarnold: +119:23
Shamailworking on it geoffarnold! sorry for the delay :(19:23
RockygJust an FYI.  We'll need to track BPs, Specs, and RFEs (bugs that are new feature requests)19:23
ShamailRockyg: +119:23
ShamailUser Story: "As a operator, I want to be notified when my instances are offline"19:23
ShamailTask: Make UI for showing instance status19:23
ShamailTask: Conduct polling to check instance availability19:23
ShamailTask: Configure email capabilities for notification19:24
ShamailThis is just an example19:24
Shamailbut I am hoping it shows the domain of user story versus tasks19:24
barrettWorks for me19:26
RockygSo, here is some large site operators' use cases.  I'd love to get your breakdown of what is and isn't and how to convert it to use cases:
ShamailI'll try to update the team on the progress of building common taxonomy (we can discuss the initial draft as a team)19:26
ShamailThanks Rockyg, i'll give it a shot19:26
Shamailbarrett: Can you please assign an action?19:26
*** fawadk has joined #openstack-meeting19:26
*** mrmartin has quit IRC19:26
RockygIt's a great start and we can use your work to inform Ops how to better write these up.19:27
*** fawadkhaliq has quit IRC19:27
*** DrBacchus has quit IRC19:27
RockygFYI a couple of ops will be taking these to the Neutron midcycle for discussion on how to implement19:27
barrett#action Shamail to review Large Site Operators use cases and map to our User Story/Task taxonomy19:27
ShamailThe goal is to hopefully make it easier to capture the high-level request while leaving the architecture/implementation up to the dev teams.  This way the burden is reduced on the user story generators and dev teams have full control of how/what they see as its manifestation.19:28
*** maurosr has quit IRC19:28
ShamailI think we're good with this topic for now.  Agreed?19:28
barrettShamail - Do you want to discuss the email you sent about Themes/Epics & User Stories?19:28
*** DrBacchus has joined #openstack-meeting19:28
barrettOr are you good with this?19:29
*** fzdarsky has joined #openstack-meeting19:29
ShamailLet's put that on the schedule for next week please.  I want to send it out to the ML (after a few of you have had a chance to modify the draft)19:29
ShamailWe can then answer questions next week versus explain it19:29
ShamailI'll make sure to send it out to the ML by Thursday.  It would be good to get the information out there before the repo.19:30
barrett#action Carol to add topic on Epics/Themes/User Stories to Agenda for next week's meeting with  Shamail to lead19:30
*** ItSANgo_ has quit IRC19:30
barrettOK next topic19:30
*** ItSANgo_ has joined #openstack-meeting19:30
barrett#topic Work FLow19:31
*** openstack changes topic to "Work FLow (Meeting topic: product_team)"19:31
barrettShamail - you have this one too19:31
ShamailDo you recall what this topic was about?  Sorry :\19:31
ShamailIs this tied to the other topic of workflow of themes -> user stories -> BP etc?19:32
*** dwalleck has quit IRC19:32
barrettYes, I think it is how they get gathered, turned into design summit input, and how roadmap is generated as outcome19:32
*** maurosr has joined #openstack-meeting19:32
ShamailAh got it!19:32
*** armax has quit IRC19:32
barrettDo you want to discuss now or defer?19:33
ShamailI can discuss it briefly and then take away an action item after the groups feedback19:33
ShamailAs everyone is aware, we want to be able to aggregate feedback from the various working groups and then share that feedback with the project teams by the design summit.  Finally, we want to also ensure that the future intentions/directions of projects are also available to the community in an easy to consume manner.19:34
ShamailTo support this workflow: We have five main tasks that must be completed... 1) obtain user stories from WGs in a standard format 2) aggregate the user stories in a common location/format and allow other groups to "show support" for the user story 3) prioritize the user stories19:35
*** padkrish has quit IRC19:36
Shamail4) work with the project teams at the design summit to share the user stories and the calculated priorities.  We also need to capture the outcome from the design summit (as it pertains to the user stories) in this step as well19:36
*** padkrish has joined #openstack-meeting19:37
Shamail5) Once we know which user stories are being worked on for a release, we need to be able to show them on a standard roadmap (working with Lauren on this one) as well as dashboards that show status for the user stories and one for the epic as well19:37
RockygOK.  small question.  Do we want to call the repo use-cases or user-stories?  We have time to change it, but just barely19:38
ShamailStretch goal: We should revisit the "top 10 prioritized user stories" against the items worked on and report out the percentage to the TC/BoD19:38
barrettShamail: Do the epics get defined as part of step #3 or ahead of it?19:38
ShamailEpics would be defined at step 2 (as we aggregate)19:38
ShamailGood point Rockyg19:38
ShamailI personally vote for userstories but usecases works too.19:39
*** mwagner_afk has quit IRC19:39
barrettshamail: +119:39
*** maurosr has quit IRC19:39
*** timello has quit IRC19:39
Rockyguserstories or user-stories?19:39
ShamailSo this is the high-level flow, if we agree with the premise and function of our group in this workflow then I can write up something a bit more detailed for review19:39
*** padkrish_ has joined #openstack-meeting19:40
barrettuser-stories is good for me19:40
Shamailopenstack-userstories or openstack-user-stories, hmm...19:40
Shamailbarrett: +119:40
*** maurosr has joined #openstack-meeting19:40
*** timello has joined #openstack-meeting19:40
barrettrockyg: OK?19:40
*** padkrish has quit IRC19:41
*** banix has quit IRC19:41
RockygYup.  Action item it, please?19:41
ShamailOnce we come up with a standard template, we can email the various working groups and user committee to let them know about the format and ask for their help in capturing the requirements in a standard manner19:41
barrett#action Rockyg to use the name user-stories for the repo name19:42
*** dwalleck has joined #openstack-meeting19:42
ShamailThe challenge with this workflow is two-fold... 1) The aggregation and formatting task might fall on us and we don't have that many active people yet so it could be quite a burden (depending on demand)19:42
cloudrancherbarrett: +119:42
barrettshamail: We were working toward a deadline for user stories of last week/this week....19:43
*** DrBacchus has quit IRC19:43
Shamail2) For the design summit, we will need people that already have working relationships with the project teams and we would need to request about 20-30 minutes of team to present19:43
*** rbowen has joined #openstack-meeting19:43
Shamailthis will also require people19:43
*** toscalix has quit IRC19:44
*** dwalleck has quit IRC19:44
Shamailbarrett: agreed, but I don't think we are following the top half of this workflow for the pilot right?  The user stories in the pilot are being created/submitted by us19:44
*** novas0x2a|laptop has quit IRC19:44
barrettShamail - Yes, that's true19:44
Shamailfor this go-around, we probably need to pick up the workflow at #219:44
*** annegentle has quit IRC19:45
Shamailso external groups formatting properly will be something we need to engage on M+19:45
ShamailThe aggregation will be simpler to since we only need to work with 5-1019:45
barrettShamail: For the M-design summit and the Pilot process we're running now, I think we'll need to have an owner for the top user stories we want to move through the design process and that owner will need to assemble a team of folks to engage with the appropriate teams19:45
Shamailuser stories19:45
Shamailbarrett: +119:45
*** fawadk has quit IRC19:46
Shamailthe owner of the user stories and the person that engages at the summit can be different people19:46
barrettOK, I think we can change topics which is to talk about how to run Steps 2&3 for the Pilot19:46
ShamailThe owner of the user story will effectively be the source for clarifying any questions that may come up as well as leading the BP creation process19:46
ShamailSounds good19:47
barrett#topic User Story Review/Consolidation/Prioritization19:47
*** openstack changes topic to "User Story Review/Consolidation/Prioritization (Meeting topic: product_team)"19:47
RockygThere are also a number of use cases coming out of the DefCore discussion right now.  Mostly Nova/Glance with a touch of Neutron related19:47
*** dguerri` is now known as dguerri19:47
ShamailTime check: 13 minutes19:47
barrettConsolidating Use Cases into Epics19:48
barrettSorry, User Stories... Consider an Epic the same as a Theme19:48
*** achanda has quit IRC19:48
barrettThe proposal is to start with the Themes we used in Vancouver19:49
barrettconsolidate User Stories as it makes sense around these, and then identify the themactic groupings for the remaining User Stories19:50
*** annegentle has joined #openstack-meeting19:50
barrettFor the Criteria for Selecting the top User stories for this Pilot Phase19:50
barrettI'm proposing 319:50
barrett Cross Project User Stories  (requiring BPs in multiple projects)19:51
barrettAddresses needs of multiple market-segments (Enterprise, HPC, Telco, etc)19:51
*** pnavarro has joined #openstack-meeting19:51
barrettCan be implemented in M-development cycle   - Though I have some concerns about this one...19:51
Shamailbarrett: +1 on all three criteria19:52
barrettWith this work completed, we'd take the ordered list to the Cross-project team meeting for review and input to enable us to finalize19:52
*** padkrish_ has quit IRC19:52
*** padkrish has joined #openstack-meeting19:53
barrettComments? Suggestions?19:53
*** matrohon has joined #openstack-meeting19:53
*** rellerreller has joined #openstack-meeting19:53
Shamailbarrett: I agree with it all19:54
cloudrancherWould the themes allow split into minimum viable, and stretch or are they the bare mininum to be usable19:54
*** galstrom is now known as galstrom_zzz19:54
Shamailwhat are your concerns with implemented in M?19:54
barrettcloudrancher: I think they would span the entire spectrum19:54
barrettShamail: Too small of a feature to move the needle...19:55
barrettI'm impatient... :)19:55
ShamailI agree with barrett, the themes would allow for coverage of all areas and we can add a new one if we are missing some19:55
Shamailgotcha barrett19:55
RockygThat's where the defcore use cases might work.  Small work in three projects with big impact19:55
barrettRockyg: I like it!19:56
*** pnavarro has quit IRC19:56
RockygThe theme for those are usability/compatibility19:56
ShamailRockyg: +119:56
*** stevemar has quit IRC19:56
Rockyg1) i want to know what my external IP address is19:56
*** rellerreller_ has joined #openstack-meeting19:57
barrettI'll take the action item to send this out to the ML, and try to assign a timeline or event for the steps..19:57
*** ddieterly has joined #openstack-meeting19:57
Rockyg2) I want to just Upload an image (glance v2 api work)19:57
*** stevemar has joined #openstack-meeting19:57
Rockyg3) I forget, but it may be images across clouds19:57
barrett#action Carol to send info to ML on consolidation/prioritization/review next steps and time for this Pilot phase19:57
ShamailSounds good barrett19:57
*** rellerreller has quit IRC19:58
*** annegent_ has joined #openstack-meeting19:58
barrettRockyg: Is there a place where we can find these?19:58
ShamailShould I focus on capturing defcore ones before the network segmentation ones?19:58
*** galstrom_zzz is now known as galstrom19:58
*** _nadya_ has quit IRC19:58
Rockygthere are two ML discussions between Monty and John Garbutt.  I'll post the links to the ML list19:58
barrettWe're almost out of time, I want to remind everyone that the Tokyo session proposals are due 7/15. Let's cover that next week.19:59
barrettAny other opens/reminders before we wrapup?19:59
barrettgoing, going...20:00
Shamailtake care everyone!20:00
*** openstack changes topic to "OpenStack Meetings ||"20:00
openstackMeeting ended Mon Jun 29 20:00:13 2015 UTC.  Information about MeetBot at . (v 0.1.4)20:00
barrettYou too!20:00
*** achanda has joined #openstack-meeting20:00
openstackMinutes (text):
*** Shamail has quit IRC20:00
*** galstrom is now known as galstrom_zzz20:01
*** natez has left #openstack-meeting20:01
*** annegentle has quit IRC20:01
*** otter768 has quit IRC20:03
*** dwalleck has joined #openstack-meeting20:05
*** ijw has quit IRC20:05
*** ddieterly has quit IRC20:08
*** stevemar has quit IRC20:08
*** banix has joined #openstack-meeting20:09
*** dwalleck has quit IRC20:10
*** dwalleck has joined #openstack-meeting20:11
*** kgroves has joined #openstack-meeting20:11
*** ctrath has quit IRC20:12
*** ctrath has joined #openstack-meeting20:12
*** rellerreller_ has left #openstack-meeting20:12
*** stevemar has joined #openstack-meeting20:15
*** baoli has quit IRC20:16
*** galstrom_zzz is now known as galstrom20:17
*** ityaptin_laptop has joined #openstack-meeting20:17
*** cloudrancher has quit IRC20:18
*** Longgeek has quit IRC20:21
*** achanda has quit IRC20:22
*** Swami has quit IRC20:23
*** maishsk_afk has joined #openstack-meeting20:23
*** maishsk_afk is now known as maishsk20:24
*** novas0x2a|laptop has joined #openstack-meeting20:24
*** novas0x2a|laptop has quit IRC20:24
*** novas0x2a|laptop has joined #openstack-meeting20:25
*** jruano has quit IRC20:26
*** annemccormick has quit IRC20:26
*** dontalton has quit IRC20:26
*** rbowen has quit IRC20:28
*** annegent_ has quit IRC20:28
*** julim has quit IRC20:29
*** annegentle has joined #openstack-meeting20:29
*** jungleboyj has quit IRC20:30
*** maurosr has quit IRC20:30
*** maurosr has joined #openstack-meeting20:30
*** timello has quit IRC20:31
*** ivasev has quit IRC20:31
*** boris-42 has joined #openstack-meeting20:31
*** timello has joined #openstack-meeting20:31
*** rbowen has joined #openstack-meeting20:31
*** Prashant_ has joined #openstack-meeting20:33
*** claudiub has joined #openstack-meeting20:34
*** timello has quit IRC20:36
*** PrashantS has quit IRC20:36
*** zz_jgrimm has quit IRC20:37
*** maurosr has quit IRC20:37
*** krtaylor has joined #openstack-meeting20:38
*** thedodd has quit IRC20:38
*** krtaylor has quit IRC20:39
*** VanL has joined #openstack-meeting20:39
*** krtaylor has joined #openstack-meeting20:40
*** Swami has joined #openstack-meeting20:40
*** jgrimm has joined #openstack-meeting20:45
*** maurosr has joined #openstack-meeting20:46
*** annegentle has quit IRC20:46
*** timello has joined #openstack-meeting20:46
*** VanL has quit IRC20:47
*** armax has joined #openstack-meeting20:48
*** claudiub has quit IRC20:49
*** stevemar has quit IRC20:49
*** echoingumesh has joined #openstack-meeting20:49
*** stevemar has joined #openstack-meeting20:50
*** maurosr has quit IRC20:51
*** Sukhdev has quit IRC20:51
*** timello has quit IRC20:52
*** jgrimm has quit IRC20:52
*** vnod has joined #openstack-meeting20:54
*** jgrimm has joined #openstack-meeting20:55
*** stevemar has quit IRC20:55
*** maurosr has joined #openstack-meeting20:56
*** timello has joined #openstack-meeting20:56
*** rfolco has quit IRC20:57
*** marun has quit IRC20:58
*** novas0x2a|laptop has quit IRC20:59
*** galstrom is now known as galstrom_zzz21:00
*** spzala has quit IRC21:00
*** novas0x2a|laptop has joined #openstack-meeting21:01
*** marun has joined #openstack-meeting21:02
*** badveli has joined #openstack-meeting21:03
*** ijw has joined #openstack-meeting21:04
*** annegentle has joined #openstack-meeting21:05
*** kgroves has quit IRC21:06
*** marrusl has quit IRC21:06
*** banix has quit IRC21:08
*** maxdml has quit IRC21:08
*** Rockyg has quit IRC21:09
*** Prashant_ has quit IRC21:09
*** PrashantS has joined #openstack-meeting21:10
*** dwalleck has quit IRC21:11
*** maurosr has quit IRC21:11
*** timello has quit IRC21:12
*** ityaptin_laptop has quit IRC21:13
*** jgrimm has quit IRC21:13
*** krtaylor has quit IRC21:13
*** radek_ has quit IRC21:13
*** PrashantS has quit IRC21:14
*** kebray has quit IRC21:15
*** padkrish has quit IRC21:15
*** padkrish has joined #openstack-meeting21:15
*** marrusl has joined #openstack-meeting21:16
*** aysyd has quit IRC21:16
*** matrohon has quit IRC21:18
*** fzdarsky has quit IRC21:18
*** banix has joined #openstack-meeting21:18
*** ijw has quit IRC21:19
*** aloga_ has joined #openstack-meeting21:19
*** dprince has quit IRC21:20
*** jungleboyj has joined #openstack-meeting21:20
*** stevebak` has joined #openstack-meeting21:21
*** maishsk has quit IRC21:21
*** dwalleck has joined #openstack-meeting21:22
*** Longgeek has joined #openstack-meeting21:22
*** maishsk has joined #openstack-meeting21:22
*** galstrom_zzz is now known as galstrom21:23
*** dwalleck has quit IRC21:23
*** mmedvede has quit IRC21:23
*** ctrath has quit IRC21:23
*** stevebak` has quit IRC21:24
*** mwagner_lap has joined #openstack-meeting21:26
*** padkrish has quit IRC21:27
*** VanL has joined #openstack-meeting21:27
*** Sukhdev has joined #openstack-meeting21:27
*** VanL_ has joined #openstack-meeting21:28
*** galstrom is now known as galstrom_zzz21:29
*** jhenner has joined #openstack-meeting21:31
*** kevinbenton has quit IRC21:31
*** topol has quit IRC21:31
*** padkrish has joined #openstack-meeting21:32
*** ivar-laz_ has joined #openstack-meeting21:32
*** VanL has quit IRC21:32
*** peristeri has quit IRC21:34
*** ivar-lazzaro has quit IRC21:35
*** aloga_ has quit IRC21:36
*** galstrom_zzz is now known as galstrom21:36
*** harshs has quit IRC21:36
*** jhenner has quit IRC21:37
*** crc32 has quit IRC21:42
*** thangp has quit IRC21:43
*** IanGovett has quit IRC21:45
*** eharney has quit IRC21:45
*** VanL_ has quit IRC21:49
*** timello has joined #openstack-meeting21:50
*** badveli has quit IRC21:50
*** maurosr has joined #openstack-meeting21:51
*** krtaylor has joined #openstack-meeting21:52
*** zz_jgrimm has joined #openstack-meeting21:52
*** Longgeek has quit IRC21:56
*** amitgandhinz has quit IRC21:58
*** weshay has quit IRC22:00
*** claudiub has joined #openstack-meeting22:00
*** sdake_ has joined #openstack-meeting22:01
*** aranjan has joined #openstack-meeting22:01
*** ijw has joined #openstack-meeting22:02
*** neelashah1 has quit IRC22:03
*** ijw has quit IRC22:03
*** ijw has joined #openstack-meeting22:03
*** otter768 has joined #openstack-meeting22:04
*** sdake has quit IRC22:04
*** otter768 has quit IRC22:09
*** Rockyg has joined #openstack-meeting22:09
*** padkrish has quit IRC22:11
*** MaxPC1 has quit IRC22:11
*** Rockyg has quit IRC22:12
*** Rockyg has joined #openstack-meeting22:13
*** ayoung has quit IRC22:14
*** spzala has joined #openstack-meeting22:14
*** balajiiyer1 has quit IRC22:15
*** dwalleck has joined #openstack-meeting22:17
*** jungleboyj has quit IRC22:17
*** aranjan has quit IRC22:17
*** absubram has quit IRC22:19
*** bknudson has quit IRC22:20
*** aranjan has joined #openstack-meeting22:20
*** padkrish has joined #openstack-meeting22:21
*** tsekiyama has joined #openstack-meeting22:21
*** mmedvede has joined #openstack-meeting22:21
*** tsbot_ has joined #openstack-meeting22:22
*** annegentle has quit IRC22:22
*** annegentle has joined #openstack-meeting22:23
*** dwalleck has quit IRC22:23
*** dwalleck has joined #openstack-meeting22:24
*** aranjan has quit IRC22:25
*** prad has quit IRC22:31
*** mwagner_lap has quit IRC22:32
*** sarob has quit IRC22:35
*** ivar-laz_ has quit IRC22:35
*** annegentle has quit IRC22:35
*** ivar-lazzaro has joined #openstack-meeting22:36
*** rossella_s has quit IRC22:36
*** rossella_s has joined #openstack-meeting22:37
*** yassine has joined #openstack-meeting22:38
*** novas0x2a|laptop has quit IRC22:39
*** novas0x2a|laptop has joined #openstack-meeting22:40
*** galstrom is now known as galstrom_zzz22:43
*** spzala has quit IRC22:45
*** yassine has quit IRC22:47
*** otter768 has joined #openstack-meeting22:49
*** annegentle has joined #openstack-meeting22:50
*** dims_ has joined #openstack-meeting22:55
*** asettle has joined #openstack-meeting22:55
*** barrett is now known as Guest8273522:57
*** weshay has joined #openstack-meeting22:58
*** barrett1 has joined #openstack-meeting22:58
*** dims has quit IRC22:59
*** dims_ has quit IRC23:00
*** otter768 has quit IRC23:02
*** sdake has joined #openstack-meeting23:02
*** jecarey has quit IRC23:02
*** ijw has quit IRC23:05
*** sdake_ has quit IRC23:05
*** ijw has joined #openstack-meeting23:05
*** xyang1 has quit IRC23:05
*** ijw has quit IRC23:07
*** ijw has joined #openstack-meeting23:07
*** JRobinson__ has joined #openstack-meeting23:08
*** ijw has quit IRC23:10
*** sbalukoff has quit IRC23:10
*** markvoelker has quit IRC23:13
*** annegentle has quit IRC23:13
*** dguerri is now known as dguerri`23:17
*** ijw has joined #openstack-meeting23:18
*** sarob has joined #openstack-meeting23:19
*** fallenpegasus has quit IRC23:21
*** echoingumesh has quit IRC23:22
*** echoingumesh has joined #openstack-meeting23:22
*** hichihara has joined #openstack-meeting23:23
*** larainema has quit IRC23:24
*** yamamoto has joined #openstack-meeting23:24
*** nelsnelson has quit IRC23:26
*** kylek3h has quit IRC23:27
*** echoingumesh has quit IRC23:27
*** Sukhdev has quit IRC23:27
*** galstrom_zzz is now known as galstrom23:29
*** vivek-ebay has joined #openstack-meeting23:30
*** aranjan has joined #openstack-meeting23:31
*** jasondotstar has joined #openstack-meeting23:31
*** asettle has quit IRC23:31
*** asettle has joined #openstack-meeting23:32
*** boris-42 has quit IRC23:32
*** yamada-h has joined #openstack-meeting23:32
*** KunalGandhi has joined #openstack-meeting23:34
*** yamada-h has quit IRC23:37
*** tochi has joined #openstack-meeting23:37
*** padkrish has quit IRC23:38
*** jwcroppe_ has joined #openstack-meeting23:38
*** padkrish has joined #openstack-meeting23:39
*** novas0x2a|laptop has quit IRC23:40
*** claudiub has quit IRC23:42
*** novas0x2a|laptop has joined #openstack-meeting23:42
*** jwcroppe has quit IRC23:42
*** padkrish has quit IRC23:43
*** jwcroppe_ has quit IRC23:43
*** aimon has quit IRC23:43
*** garthb__ has joined #openstack-meeting23:44
*** garthb_ has quit IRC23:48
*** garthb has quit IRC23:48
*** garthb__ has quit IRC23:49
*** jwcroppe has joined #openstack-meeting23:50
*** markvoelker has joined #openstack-meeting23:51
*** sajeesh has joined #openstack-meeting23:53
*** Longgeek has joined #openstack-meeting23:54
*** topol has joined #openstack-meeting23:54
*** jhenner has joined #openstack-meeting23:54
*** marun has quit IRC23:54
*** alop has quit IRC23:55
*** yamamoto has quit IRC23:56
*** dannywil_ has joined #openstack-meeting23:57
*** vnod has quit IRC23:57
*** maxdml has joined #openstack-meeting23:58
*** Swami has quit IRC23:58
*** Sukhdev has joined #openstack-meeting23:59

Generated by 2.14.0 by Marius Gedminas - find it at!