Tuesday, 2013-12-17

*** xchu has joined #openstack-dev00:00
*** markwash has joined #openstack-dev00:01
*** jcooley_ has quit IRC00:02
*** mlavalle has quit IRC00:03
*** dolphm has quit IRC00:05
*** jhesketh__ has joined #openstack-dev00:05
*** kenperkins has joined #openstack-dev00:05
*** jcooley_ has joined #openstack-dev00:06
*** hemna is now known as hemnafk00:06
*** kenperkins has quit IRC00:07
*** jcooley_ has quit IRC00:08
*** tonix has quit IRC00:08
*** nermina has joined #openstack-dev00:08
*** marekd|away has joined #openstack-dev00:08
*** markwash has quit IRC00:09
*** kenperkins has joined #openstack-dev00:09
*** jcooley_ has joined #openstack-dev00:10
*** pmathews has quit IRC00:11
*** kenperkins has quit IRC00:11
*** kenperkins has joined #openstack-dev00:12
*** mikeoutland has joined #openstack-dev00:14
*** DennyZhang has joined #openstack-dev00:14
*** eharney has quit IRC00:15
*** DennyZhang has quit IRC00:15
*** DennyZhang has joined #openstack-dev00:16
*** mriedem has joined #openstack-dev00:17
*** rnirmal has quit IRC00:19
*** teran has quit IRC00:20
*** amotoki has joined #openstack-dev00:21
*** buzztroll has joined #openstack-dev00:21
*** xchu has quit IRC00:23
*** mriedem has quit IRC00:23
*** rfolco has quit IRC00:24
*** teran has joined #openstack-dev00:24
*** dkranz has joined #openstack-dev00:24
*** s0mik has quit IRC00:25
*** mriedem has joined #openstack-dev00:25
*** s0mik has joined #openstack-dev00:26
*** nermina has quit IRC00:27
*** DennyZhang has quit IRC00:27
*** diogogmt has quit IRC00:29
*** mriedem has quit IRC00:29
*** Mandell has quit IRC00:31
*** marun has joined #openstack-dev00:31
*** jamielennox is now known as jamielennox|away00:32
*** Alexei_987 has quit IRC00:32
*** nelsnelson is now known as nelsnelson_away00:32
*** sthaha has joined #openstack-dev00:33
*** sthaha has quit IRC00:33
*** sthaha has joined #openstack-dev00:33
*** yamahata has joined #openstack-dev00:33
*** Mandell has joined #openstack-dev00:34
*** buzztroll has quit IRC00:34
*** nermina has joined #openstack-dev00:36
*** nelsnelson_away has quit IRC00:36
*** dims has quit IRC00:37
*** freyes has joined #openstack-dev00:38
*** faramir1 has joined #openstack-dev00:38
*** dims has joined #openstack-dev00:39
*** comay has quit IRC00:40
bknudsonmorganfainberg: did you have a suggestion for a better commit message for https://review.openstack.org/#/c/50488/ ?00:40
morganfainbergbknudson, oh, uhm00:41
*** markwash has joined #openstack-dev00:41
morganfainbergbknudson, i think my only concern was the "and" in the commit message00:41
morganfainbergbknudson, it used to be <closes> \n and \n <closes>00:42
morganfainbergbknudson, that was solved.00:42
*** morazi has quit IRC00:42
*** michchap has quit IRC00:42
morganfainbergi'll +2/+A it.00:42
bknudsonmorganfainberg: ok, thanks. that one has had plenty of reviews.00:42
morganfainbergbknudson, actually... my browser isn't loading review.openstack.org atm00:42
*** michchap has joined #openstack-dev00:42
morganfainbergbknudson, let me see if i can figure it out. if not, you can reference this irc chat and +2/+A :)00:43
morganfainbergbknudson, there we og.  dns was ... lame00:43
*** comay has joined #openstack-dev00:46
*** freyes has quit IRC00:47
*** dims has quit IRC00:47
*** xqueralt has quit IRC00:48
spandheusing nova-api, is there a way to get information about deleted VMs for a tenant/user?00:48
spandheI actually want to see quota usage from the api, but seems that will be available in havana00:49
*** sthaha has quit IRC00:49
*** pixelb has joined #openstack-dev00:49
*** sthaha has joined #openstack-dev00:49
*** novas0x2a|laptop has quit IRC00:50
*** jcooley_ has quit IRC00:50
*** teran_ has joined #openstack-dev00:50
*** mriedem has joined #openstack-dev00:52
*** jcooley_ has joined #openstack-dev00:53
*** teran has quit IRC00:53
*** JordanRinke_afk is now known as JordanRinke00:54
*** nosnos has joined #openstack-dev00:54
*** kenperkins has quit IRC00:57
*** sarob has joined #openstack-dev00:57
*** dims has joined #openstack-dev01:02
*** nelsnelson has joined #openstack-dev01:03
*** e0ne has quit IRC01:04
*** mrodden has quit IRC01:04
*** nosnos has quit IRC01:06
*** nosnos has joined #openstack-dev01:06
*** sarob has quit IRC01:07
*** sarob has joined #openstack-dev01:08
*** dcahill has quit IRC01:10
*** alex_xu has joined #openstack-dev01:10
*** sarob has quit IRC01:12
*** spandhe has quit IRC01:13
*** mohits has quit IRC01:13
*** jsavak has quit IRC01:14
*** stevemar has joined #openstack-dev01:15
*** jamielennox|away is now known as jamielennox01:15
*** freyes has joined #openstack-dev01:16
*** bingbu has joined #openstack-dev01:17
*** sarob has joined #openstack-dev01:17
*** pixelb has quit IRC01:21
*** nermina has quit IRC01:22
*** alop has quit IRC01:26
*** bingbu has quit IRC01:26
*** bswartz has quit IRC01:28
*** bswartz has joined #openstack-dev01:30
*** rods has quit IRC01:30
*** xarses has quit IRC01:34
*** bdpayne has quit IRC01:34
*** buzztroll has joined #openstack-dev01:35
*** amcrn has quit IRC01:37
*** colinmcnamara has quit IRC01:37
*** buzztroll has quit IRC01:39
*** buzztroll has joined #openstack-dev01:40
*** lbragstad has quit IRC01:40
*** yaguang has joined #openstack-dev01:40
*** ljjjustin has joined #openstack-dev01:41
*** joesavak has joined #openstack-dev01:42
*** bingbu has joined #openstack-dev01:42
*** lbragstad has joined #openstack-dev01:43
*** nermina has joined #openstack-dev01:43
*** jsavak has joined #openstack-dev01:43
*** ljjjustin has quit IRC01:46
*** joesavak has quit IRC01:47
*** epim has quit IRC01:47
*** melwitt has quit IRC01:48
*** ljjjustin has joined #openstack-dev01:48
*** s0mik has quit IRC01:50
*** shakayumi has joined #openstack-dev01:51
*** jergerber has quit IRC01:53
*** mrodden has joined #openstack-dev01:53
*** nermina has quit IRC01:54
*** buzztroll has quit IRC01:54
*** akrivoka has quit IRC01:55
*** mrodden1 has joined #openstack-dev01:55
*** tanisdl has quit IRC01:55
*** jayg is now known as jayg|g0n301:56
*** sushils has quit IRC01:57
*** mrodden has quit IRC01:57
*** radix_ has quit IRC01:58
*** nati_ueno has quit IRC02:01
*** dolphm has joined #openstack-dev02:04
*** agntdrake has quit IRC02:04
*** angdraug has quit IRC02:05
*** jcooley_ has quit IRC02:08
*** s0mik has joined #openstack-dev02:10
*** dave_tucker has quit IRC02:11
*** s0mik has quit IRC02:14
*** teran has joined #openstack-dev02:14
*** e0ne has joined #openstack-dev02:15
*** markvoelker1 has joined #openstack-dev02:17
stevemarayoung: filling in extension_data in an extension data, what should we put for namespace and updated?02:17
ayoungstevemar, something that someone would have to think really hard about, so that it slips unnoticed through the code review02:17
*** teran_ has quit IRC02:18
stevemar:)02:18
ayoungusually namespace is the extension name02:18
ayoungupdated is the time the extension was updated, but we probably haven't been keeping those up to date02:18
*** erkules_ has joined #openstack-dev02:18
ayoungjust put the current time in there02:18
*** buzztroll has joined #openstack-dev02:19
*** bingbu has quit IRC02:19
*** e0ne has quit IRC02:20
*** devoid has joined #openstack-dev02:21
*** erkules has quit IRC02:21
*** xarses has joined #openstack-dev02:22
*** xmltok_ has quit IRC02:23
stevemarayoung: m'alright02:24
*** nermina has joined #openstack-dev02:24
*** markwash has quit IRC02:24
*** bingbu has joined #openstack-dev02:25
*** xjiujiu has joined #openstack-dev02:28
*** giroro_ has quit IRC02:28
*** phschwartz is now known as phschwartz_aw02:28
*** devoid has quit IRC02:29
*** nati_ueno has joined #openstack-dev02:30
*** nermina has quit IRC02:31
*** faramir1 has quit IRC02:31
*** Mandell has quit IRC02:32
*** Ruetobas has joined #openstack-dev02:35
*** xjiujiu has quit IRC02:35
*** xjiujiu has joined #openstack-dev02:35
*** Ruetobas has quit IRC02:39
*** Ruetobas has joined #openstack-dev02:40
*** jp_at_hp1 has quit IRC02:40
*** jsavak has quit IRC02:42
*** reed has quit IRC02:42
*** ayoung has quit IRC02:44
*** xjiujiu has quit IRC02:44
*** xjiujiu has joined #openstack-dev02:44
*** xjiujiu has joined #openstack-dev02:46
*** vkozhukalov has joined #openstack-dev02:48
*** Ruetobas has quit IRC02:48
*** Ruetobas has joined #openstack-dev02:48
*** freyes has quit IRC02:49
*** jimjiang has quit IRC02:51
*** faramir1 has joined #openstack-dev02:51
*** jimjiang has joined #openstack-dev02:52
*** dims has quit IRC02:53
*** dims has joined #openstack-dev02:53
*** renlt has joined #openstack-dev02:53
*** mikeoutland has quit IRC02:55
*** jimjiang has quit IRC02:57
*** _dbalog has joined #openstack-dev02:57
*** jimjiang has joined #openstack-dev02:58
*** giulivo has quit IRC03:00
*** ctracey is now known as ctracey|away03:01
*** nermina has joined #openstack-dev03:04
*** xjiujiu has quit IRC03:05
*** thomasem has joined #openstack-dev03:06
*** yamahata__ has quit IRC03:06
*** yamahata__ has joined #openstack-dev03:06
*** thomasem has quit IRC03:12
*** paragan has joined #openstack-dev03:14
*** paragan has quit IRC03:14
*** paragan has joined #openstack-dev03:14
*** faramir1 has quit IRC03:16
*** buzztroll has quit IRC03:18
*** ljjjustin has quit IRC03:21
*** rushiagr has joined #openstack-dev03:23
*** shakayumi has quit IRC03:24
*** dolphm has quit IRC03:25
*** faramir1 has joined #openstack-dev03:29
*** dolphm has joined #openstack-dev03:30
*** rcleere has joined #openstack-dev03:35
*** otherwiseguy has quit IRC03:40
*** rongze has joined #openstack-dev03:40
*** maxskew has joined #openstack-dev03:45
*** arnaud has quit IRC03:51
*** arnaud__ has quit IRC03:51
*** bingbu has quit IRC03:51
*** rraja has joined #openstack-dev03:52
*** buzztroll has joined #openstack-dev03:53
*** aveiga has quit IRC03:53
*** jecarey has joined #openstack-dev03:54
*** jimjiang has quit IRC03:55
*** mriedem has quit IRC03:55
*** jimjiang has joined #openstack-dev03:56
*** aditirav has joined #openstack-dev03:57
*** aditirav has quit IRC03:58
*** aditirav has joined #openstack-dev03:58
*** renlt has quit IRC03:59
*** renlt has joined #openstack-dev03:59
*** mdomsch has joined #openstack-dev04:01
*** bingbu has joined #openstack-dev04:04
*** dolphm has quit IRC04:05
*** mikeoutland has joined #openstack-dev04:07
*** maxskew has left #openstack-dev04:11
*** buzztroll has quit IRC04:12
*** itooon has joined #openstack-dev04:14
*** chandankumar has joined #openstack-dev04:16
*** DennyZhang has joined #openstack-dev04:18
*** DennyZhang has quit IRC04:21
*** DennyZhang has joined #openstack-dev04:22
*** DennyZhang has quit IRC04:23
*** DennyZhang has joined #openstack-dev04:24
*** pmathews has joined #openstack-dev04:24
*** jimjiang has quit IRC04:25
*** eglynn_ has quit IRC04:25
*** jimjiang has joined #openstack-dev04:26
*** buzztroll has joined #openstack-dev04:26
*** pmathews has quit IRC04:28
*** DennyZhang has quit IRC04:29
*** aeperezt has quit IRC04:31
*** rongze has quit IRC04:33
*** epopt37 has quit IRC04:34
*** DennyZhang has joined #openstack-dev04:38
*** buzztroll has quit IRC04:42
*** pmathews has joined #openstack-dev04:43
*** buzztroll has joined #openstack-dev04:46
*** epopt37 has joined #openstack-dev04:46
*** pdevine has joined #openstack-dev04:49
*** Mandell has joined #openstack-dev04:49
*** SergeyLukjanov has joined #openstack-dev04:49
*** rongze has joined #openstack-dev04:55
*** sarob_ has joined #openstack-dev04:56
*** sarob has quit IRC04:58
*** rongze_ has joined #openstack-dev04:59
*** jecarey has quit IRC04:59
*** rongze has quit IRC05:00
*** sarob_ has quit IRC05:01
*** aditirav_ has joined #openstack-dev05:03
*** rushiagr has quit IRC05:04
*** rongze_ has quit IRC05:04
*** qs201 has joined #openstack-dev05:05
*** qs201 has quit IRC05:07
*** aditirav has quit IRC05:07
*** aditirav_ has quit IRC05:07
*** DennyZhang has quit IRC05:09
*** aditirav has joined #openstack-dev05:09
*** tserong has quit IRC05:13
*** teran has quit IRC05:13
*** rraja has quit IRC05:14
*** rektide has quit IRC05:17
*** zaitcev has quit IRC05:20
*** stevemar has quit IRC05:20
*** reed has joined #openstack-dev05:21
*** guohliu has joined #openstack-dev05:23
*** sandywalsh_ has quit IRC05:23
*** achampion has quit IRC05:23
*** achampion has joined #openstack-dev05:24
*** alop has joined #openstack-dev05:26
*** reed has quit IRC05:26
*** cdub_ has quit IRC05:29
*** neeti has joined #openstack-dev05:29
*** alop has quit IRC05:30
*** alop has joined #openstack-dev05:32
*** spzala_ has quit IRC05:32
*** cpallares has quit IRC05:33
*** sgordon has quit IRC05:33
*** achampion has quit IRC05:33
*** achampion has joined #openstack-dev05:33
*** haomaiwang has joined #openstack-dev05:34
*** cdub has joined #openstack-dev05:35
*** buzztroll has quit IRC05:35
*** garyk has quit IRC05:35
*** bingbu has quit IRC05:36
*** sandywalsh_ has joined #openstack-dev05:39
*** Ryan_Lane has quit IRC05:41
*** Ryan_Lane has joined #openstack-dev05:42
*** prekarat has joined #openstack-dev05:44
*** Ryan_Lane has quit IRC05:46
*** markwash has joined #openstack-dev05:47
*** rohitk has joined #openstack-dev05:48
*** bingbu has joined #openstack-dev05:49
*** ffio has quit IRC05:50
*** jhesketh__ has quit IRC05:50
*** jhesketh__ has joined #openstack-dev05:51
*** sgordon has joined #openstack-dev05:52
*** aditirav has quit IRC05:56
*** aditirav_ has joined #openstack-dev05:56
*** erkules_ has quit IRC05:56
*** aditirav_ has quit IRC05:57
*** swaT30 has quit IRC05:58
*** aditirav has joined #openstack-dev05:58
*** rushiagr has joined #openstack-dev05:58
*** erkules_ has joined #openstack-dev05:59
*** ffio has joined #openstack-dev05:59
*** swaT30 has joined #openstack-dev06:00
*** itooon_ has joined #openstack-dev06:00
*** aditirav_ has joined #openstack-dev06:02
*** itooon has quit IRC06:02
*** itooon_ is now known as itooon06:02
*** erkules_ is now known as erkules06:04
*** aditirav has quit IRC06:04
*** aditirav_ is now known as aditirav06:04
*** edleafe- has quit IRC06:06
*** edleafe has joined #openstack-dev06:06
*** Hien has quit IRC06:07
*** Hien has joined #openstack-dev06:07
*** aditirav has quit IRC06:07
*** kenperkins has joined #openstack-dev06:08
*** aditirav has joined #openstack-dev06:08
*** adalbas has quit IRC06:12
*** bdpayne has joined #openstack-dev06:12
*** teran has joined #openstack-dev06:14
*** rongze has joined #openstack-dev06:15
*** sgordon has quit IRC06:17
*** rraja has joined #openstack-dev06:18
*** DennyZhang has joined #openstack-dev06:19
*** teran has quit IRC06:19
*** aditirav_ has joined #openstack-dev06:23
*** aditirav has quit IRC06:23
*** aditirav_ is now known as aditirav06:24
*** finchd has joined #openstack-dev06:26
*** DennyZhang has quit IRC06:27
*** DennyZhang has joined #openstack-dev06:28
*** avishay has joined #openstack-dev06:28
*** adalbas has joined #openstack-dev06:29
*** DennyZhang has left #openstack-dev06:30
*** aditirav has quit IRC06:33
*** djinni_ has quit IRC06:34
*** yeylon__ has joined #openstack-dev06:34
*** alex_klimov has joined #openstack-dev06:34
*** rushiagr has quit IRC06:36
*** sgordon has joined #openstack-dev06:36
*** boris-42 has joined #openstack-dev06:36
*** markvoelker1 has quit IRC06:36
*** djinni has joined #openstack-dev06:36
*** markwash has quit IRC06:37
*** alop has quit IRC06:39
*** alex_klimov has quit IRC06:39
*** sthaha has quit IRC06:40
*** markwash has joined #openstack-dev06:40
*** alex_klimov has joined #openstack-dev06:41
*** bdpayne has quit IRC06:42
*** harlowja is now known as harlowja_away06:43
*** HenryG has quit IRC06:43
*** rushiagr has joined #openstack-dev06:43
*** tonyfy has joined #openstack-dev06:45
*** SergeyLukjanov has quit IRC06:45
*** buzztroll has joined #openstack-dev06:46
*** nshaikh has joined #openstack-dev06:48
*** marun has quit IRC06:49
*** buzztroll has quit IRC06:51
*** DennyZhang has joined #openstack-dev06:51
*** vkozhukalov has quit IRC06:51
*** DennyZhang has left #openstack-dev06:54
*** ngoracke1 has quit IRC06:54
*** pdevine has quit IRC06:55
*** DennyZhang has joined #openstack-dev06:56
*** garyk has joined #openstack-dev06:56
*** vartom11111119 has joined #openstack-dev06:58
*** bingbu has quit IRC07:00
*** sgordon has quit IRC07:01
*** michchap has quit IRC07:02
*** kenperkins has quit IRC07:02
*** michchap has joined #openstack-dev07:03
*** neelashah1 has quit IRC07:03
*** jcooley_ has joined #openstack-dev07:03
*** denis_makogon has joined #openstack-dev07:05
*** markwash has quit IRC07:06
*** Abhishek_ has joined #openstack-dev07:07
*** jcooley_ has quit IRC07:07
*** jcooley_ has joined #openstack-dev07:09
*** pmathews has quit IRC07:10
*** HenryG has joined #openstack-dev07:10
*** rushiagr has quit IRC07:11
*** rushiagr has joined #openstack-dev07:11
*** jamielennox is now known as jamielennox|away07:11
*** bingbu has joined #openstack-dev07:12
*** jcooley_ has quit IRC07:14
*** aditirav has joined #openstack-dev07:14
*** yolanda has joined #openstack-dev07:15
*** tserong has joined #openstack-dev07:16
*** mikeoutland has quit IRC07:20
*** jhesketh__ has quit IRC07:20
*** boris-42 has quit IRC07:21
*** DennyZhang has quit IRC07:22
*** doron_afk has joined #openstack-dev07:29
*** Abhishek_ has quit IRC07:30
*** vartom11111119 has quit IRC07:31
*** vartom111111110 has joined #openstack-dev07:31
*** nelsnelson has quit IRC07:31
*** nelsnelson has joined #openstack-dev07:32
*** urulama has joined #openstack-dev07:33
*** zul has quit IRC07:34
*** rohitk has quit IRC07:35
*** DennyZhang has joined #openstack-dev07:35
*** ig has joined #openstack-dev07:37
*** afazekas has joined #openstack-dev07:37
*** DennyZhang has quit IRC07:40
*** evgenyf has joined #openstack-dev07:41
*** lsmola_ has joined #openstack-dev07:44
*** flaper87|afk is now known as flaper8707:46
*** jimjiang has quit IRC07:47
*** jimjiang has joined #openstack-dev07:48
*** ig1 has joined #openstack-dev07:49
*** ig1 has quit IRC07:50
*** ig has quit IRC07:50
*** ig has joined #openstack-dev07:50
*** julienvey_ has joined #openstack-dev07:54
*** venum has joined #openstack-dev07:58
*** mrunge has joined #openstack-dev08:00
*** teran has joined #openstack-dev08:02
*** arozumenko has joined #openstack-dev08:02
*** kbrierly has quit IRC08:03
*** kdbrierly has quit IRC08:08
*** aditirav has quit IRC08:08
*** amotoki has quit IRC08:09
*** aditirav has joined #openstack-dev08:09
*** xga_ has joined #openstack-dev08:10
*** xga has quit IRC08:10
*** xga_ has quit IRC08:13
*** xga has joined #openstack-dev08:13
ttxnotmyname: o/08:14
notmynamehowdy :-)08:14
*** e0ne has joined #openstack-dev08:14
notmynamebrief update for swifty things: python-swiftclient is nearing a 2.0 release08:14
notmynamewhen https://review.openstack.org/#/c/33473/ lands, both the final 1.x and 2.0 will be tagged08:14
notmynamethe 2.0 is important because it adds cert checking08:15
notmynameon by default08:15
ttxnotmyname: heh, yes08:15
notmynameand this may break existing clients08:15
notmynameso I'll also tag a final 1.x to get everything that's been merged08:15
notmynamebefore that08:15
ttxsounds good08:15
ttxthat last review seems in good shape08:16
ttxso hopefully will happen before the holiday season08:16
notmynamenot really. looks like it may have an issue. just overheard another review of it in -swift08:16
*** moted has quit IRC08:16
notmynamebut yes, I hope so08:16
notmynameI'm hoping for tomorrow, actually08:17
ttxit's all +1 now but maybe there is more to it08:17
ttxanything you wanted to see discussed at the meeting ?08:17
notmynamebut that brings us to the major issue of the day: gate checks08:17
*** tkammer has joined #openstack-dev08:17
notmynameyes. gate checks08:17
notmynamefirst, have you heard of other groups in openstack having issues getting things through the gate?08:17
ttxOK, adding to the agenda08:18
* ttx was fearing the agenda was a bit light but it suddenly got heavier :)08:18
ttxnotmyname: yes, most people got bitten by the sphinx issue last week08:18
ttxit delayed 2013.2.1 from Thursday to Today08:18
notmynamethe sphinx issue was a big deal, but a nice one-off. the problem that I see is that it wasn't really that unusual from a gate status perspective08:19
notmynamettx: anything beyond that? what we're seeing is that approved patches take _days_ to land08:19
notmynamewith many reverify comments08:19
notmynameand groking the logs to do the right bugs is a major time sink08:20
notmynameeg right now a perfectly good patch only has  ~70% chance of passing http://not.mn/gate_status.html08:20
ttxnotmyname: my understanding was that it was mostly the time to process the backlog, but maybe the non-deterministic issues got busier yesterday08:20
notmynamewhich is .2% chance for the current gat eto clear08:21
ttxnotmyname: let's discuss that at meeting later today08:21
*** sergmelikyan has joined #openstack-dev08:21
ttxnotmyname: pretty sure sgaue will have a clearer status than I have08:21
notmynamettx: please read the text on my graph page to prep08:21
ttxsdague*08:21
ttxnotmyname: will do andI'll link it on the agenda, too08:21
notmynamethanks08:21
notmynamettx: so what I want is 3 things08:22
notmyname1) know if this is a systemic thing (which I suspect it is) affecting all projects08:22
notmyname2) find a source rather than just the knowledge of something being wrong08:22
notmyname3) find a way forward. this must be more than "we'll pay more attention to bugs in the hand-curated elastic-recheck list"08:23
notmynamethings like: can we redo the way gate queues are managed?08:23
notmynamedo we need to reconsider the way integration tests are done?08:23
notmynamedo we need to reconsider the dev methodology?08:24
ttxnotmyname: ok, good topic, will try to get the right people around08:24
notmynamettx: anyway, it's a huge topic, and IMO a huge problem. one that is causing a _lot_ of frustration, at least on our side of things08:24
notmynameand I'm scared that if it continues the consequences may be dire08:25
ttxnotmyname: ack08:25
*** AMike has quit IRC08:25
*** pfreund has joined #openstack-dev08:26
ttxnotmyname: ok, then see you at the meeting later08:26
notmynamettx: k, thanks08:26
*** vkozhukalov has joined #openstack-dev08:26
*** denis_makogon has quit IRC08:26
*** jtomasek has joined #openstack-dev08:28
*** avishayb has joined #openstack-dev08:29
*** teran has quit IRC08:30
*** noorul has quit IRC08:33
*** gszasz has joined #openstack-dev08:34
*** zul has joined #openstack-dev08:34
*** jcoufal has joined #openstack-dev08:34
*** jhesketh_ has quit IRC08:34
*** DennyZhang has joined #openstack-dev08:36
*** marios has quit IRC08:37
*** DinaBelova has joined #openstack-dev08:37
*** giulivo has joined #openstack-dev08:37
chandankumarsdague, ping08:38
*** marios has joined #openstack-dev08:38
*** kbrierly has joined #openstack-dev08:38
*** rushiagr has quit IRC08:38
*** rushiagr2 has joined #openstack-dev08:38
*** AMike has joined #openstack-dev08:38
*** jimjiang has quit IRC08:39
*** jimjiang has joined #openstack-dev08:40
*** achampion has quit IRC08:40
*** krast has joined #openstack-dev08:40
*** ifarkas has joined #openstack-dev08:40
*** DennyZhang has quit IRC08:41
*** achampion has joined #openstack-dev08:41
*** amuller has joined #openstack-dev08:43
*** HenryG has quit IRC08:43
*** rushiagr2 has quit IRC08:44
*** HenryG has joined #openstack-dev08:44
*** corXi has joined #openstack-dev08:45
*** xingchao has joined #openstack-dev08:45
*** AMike has quit IRC08:45
*** jhesketh_ has joined #openstack-dev08:46
*** AMike has joined #openstack-dev08:46
*** AMike has quit IRC08:46
*** AMike has joined #openstack-dev08:46
*** urulama has quit IRC08:47
*** ygbo has joined #openstack-dev08:47
*** fbo_away is now known as fbo08:47
*** devvesa has joined #openstack-dev08:47
*** _dbalog has quit IRC08:48
*** _dbalog has joined #openstack-dev08:48
*** corXi has quit IRC08:49
*** rushiagr2 has joined #openstack-dev08:49
*** corXi has joined #openstack-dev08:50
*** ogelbukh has joined #openstack-dev08:50
*** jaimegil has joined #openstack-dev08:51
*** asalkeld has quit IRC08:51
*** haypo has joined #openstack-dev08:53
*** asalkeld has joined #openstack-dev08:53
kashyapchandankumar, Please don't do a 'naked ping', post your topic (ping re: blah). He's in EST time-zone & must be sleeping.08:54
*** noorul has joined #openstack-dev08:54
*** urulama has joined #openstack-dev08:54
*** nermina has quit IRC08:56
*** omachace has joined #openstack-dev08:56
chandankumarkashyap, for this bug, https://bugs.launchpad.net/tempest/+bug/120120108:58
uvirtbotLaunchpad bug 1201201 in tempest "Document how to install tempest without devstack" [Wishlist,Confirmed]08:58
chandankumarit is telling about which helper script?08:58
haypohi. i'm trying to update Oslo-incubator in oslo-messaging, but openstack/common/gettextutils.py now depends on a Python module "babel" whereas i don't see this dependency anywhere08:58
*** salv-orlando has quit IRC09:00
*** rushiagr2 is now known as rushiagr09:00
*** jistr has joined #openstack-dev09:00
*** vartom111111110 has quit IRC09:00
*** nshaikh has left #openstack-dev09:00
*** ndipanov_gone is now known as ndipanov09:01
*** prekarat has quit IRC09:01
*** boden has joined #openstack-dev09:02
kashyapchandankumar, IIUC, *you*/bug-asignee has to prepare an install helper script. Hence the bug.09:02
*** prekarat has joined #openstack-dev09:04
chandankumarkashyap, i need more info on helper script, it is related to install tempest through puppet or anisble.09:04
chandankumar?09:04
kashyapWhy don't you try yourself & post the observations on which is optimal.09:05
*** xga has quit IRC09:05
*** xga has joined #openstack-dev09:06
*** nosnos has quit IRC09:07
*** nosnos has joined #openstack-dev09:07
*** jpich has joined #openstack-dev09:07
*** derekh has joined #openstack-dev09:07
*** irenab has joined #openstack-dev09:07
*** SergeyLukjanov has joined #openstack-dev09:08
*** SergeyLukjanov has quit IRC09:09
*** yassine has joined #openstack-dev09:09
Adri2000am I the only one who would prefer all meeting/event times to be announced in UTC rather than pacific/eastern/... ? :)09:09
*** SergeyLukjanov has joined #openstack-dev09:09
StevenKHow about both?09:10
*** reidrac has joined #openstack-dev09:11
persiaboth is even worse than non-UTC09:11
*** mindpixel has joined #openstack-dev09:11
StevenKWed 1000EST (Wed 1500Z) is bad?09:11
persiaYes, because 1000EST can also be interpreted as 2400Z, depending on local interpretation09:13
chandankumarkashyap, ok Thanks :)09:13
lifelesspersia: uh, but Z adds the disambiguator09:13
lifelesspersia: without that you only have multiple local interpretations09:13
Adri2000then why not western europe time? japan time as well?09:13
* persia agrees with Adri200009:13
lifelesspersia: so surely both is strictly better than non-UTC alone?09:13
*** marekd|away is now known as marekd09:14
lifelesspersia: also, how the hell are you?09:14
persialifeless: Yes, but UTC alone is better, especially when people get confused about UTC offsets arund the equinox09:14
*** omachace has quit IRC09:14
lifelesspersia: did you get to the HK summit?09:14
*** omachace has joined #openstack-dev09:15
persialifeless: No.  I wasn't quite thinking clearly (losses in the family).  I'm better now.  How are you?09:15
*** Ryan_Lane has joined #openstack-dev09:15
*** reidrac has quit IRC09:15
lifelesspersia: oh, thats sad news. I'm great :)09:15
lifelesspersia: Cynthia is not growing as fast as the dr's would like, which is a little concerning, but it's early days in the analysis, nothing to panic about [yet]09:16
yolandahi, i want to create a new feature under oslo, what's the right process to do it? first create a blueprint here? https://blueprints.launchpad.net/oslo/09:17
persiaOof.  May all be well.09:17
*** boden has quit IRC09:17
yolandait's related to that change: https://review.openstack.org/#/c/61128/09:18
lifelessinteresting09:18
lifelessso I at least am confused about when things move to olso.09:18
lifelessI've been told that they go into the incubator once multiple projects want to use it - but that first they start in one project.09:18
lifelessdhellmann: ^ will be the authority09:19
*** johnthetubaguy has joined #openstack-dev09:19
*** yamahata has quit IRC09:19
lifelessIf it's a feature level item, or something needing discussion, then a blueprint is often a useful control point.09:19
lifelessyolanda: was this discussed at the summit?09:19
*** Ryan_Lane has quit IRC09:20
yolandalifeless, no, we had a blueprint into Ubuntu, and we decided to raise question upstream09:20
*** athomas has joined #openstack-dev09:20
*** mrunge has quit IRC09:20
lifelessyolanda: ok, so I would send an email to the openstack-dev list09:20
yolandaso i just chose one component and keystone, sent a change request to grab opinions about it, and see what's the better way09:20
lifelessyolanda: because this is something that will eventually impact everyone09:20
yolandalifeless, ok, so i should send an email asking about opinions for it?09:21
lifelessyolanda: (and for instance, I'm extremely puzzled why folk would want to leak this information out).09:21
lifelessyolanda: yeah, definitely.09:21
*** mancdaz_away is now known as mancdaz09:21
*** mrunge has joined #openstack-dev09:21
lifelessI'm fairly sure a bunch of opsec folk will want to understand the benefit of disclosing this operational detail [at all, nevermind in every response]09:21
lifelessyolanda: Then there's the overhead question - why include this in every response; if it's diagnostic material, why not just include it in response to OPTIONS: *09:22
persiayolanda: Do you have a link to the Ubuntu blueprint?  What benefit do you expect?09:22
yolandayes, blueprint is here https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-server-app-banner-updates09:23
yolandathe intention is for stats collection mostly09:23
*** aspiers_ is now known as aspiers09:23
*** safchain has joined #openstack-dev09:24
yolandathe way i've thought about it, is to include that on config file, and distribution should be statically written in config file, so it's few extra overhead, as call is already parsing this config file anyway09:25
yolandaand as it's included in config file, it can be disabled if people don't want it in their deployment09:26
*** eglynn has joined #openstack-dev09:27
*** lucasagomes has joined #openstack-dev09:31
*** DennyZhang has joined #openstack-dev09:32
*** neeti has quit IRC09:32
lifelessI'm talking overhead on the wire09:34
lifelesswe make lots of API responses between services09:34
lifelesslike nova -> keystone09:34
lifelessextra fat in the response should have some value to the user09:34
*** exed has joined #openstack-dev09:35
*** vkozhukalov has quit IRC09:35
*** neeti has joined #openstack-dev09:35
lifelessyolanda: anyhow, - highly recommend a list discussion09:37
yolandalifeless, i just sent the email now09:37
lifelesscool, thanks09:37
*** Abhishek_ has joined #openstack-dev09:39
*** ffio has quit IRC09:39
*** noorul has quit IRC09:41
shardyDoes anyone from stable-maint know why Heat 2013.2.1 has been released without merging all the fixes queued for stable/havana?09:41
*** nelsnelson has quit IRC09:41
*** nelsnelson has joined #openstack-dev09:42
*** andreaf has quit IRC09:43
*** renlt has quit IRC09:43
*** martyntaylor has joined #openstack-dev09:44
*** bingbu has quit IRC09:46
*** danpb has joined #openstack-dev09:46
*** faramir1 has quit IRC09:46
*** martyntaylor1 has joined #openstack-dev09:47
*** rohitk has joined #openstack-dev09:47
*** teran has joined #openstack-dev09:47
*** martyntaylor has quit IRC09:48
*** noorul has joined #openstack-dev09:50
*** vkozhukalov has joined #openstack-dev09:50
*** haypo has left #openstack-dev09:51
*** boris-42 has joined #openstack-dev09:52
*** teran has quit IRC09:52
*** nati_ueno has quit IRC09:53
*** DennyZhang has quit IRC09:54
*** nati_ueno has joined #openstack-dev09:55
*** SergeyLukjanov has quit IRC09:55
*** SergeyLukjanov has joined #openstack-dev09:57
*** teran has joined #openstack-dev09:58
*** JordanP has joined #openstack-dev09:59
*** max_lobur_afk is now known as max_lobur10:00
*** iartarisi has joined #openstack-dev10:00
*** doron_afk is now known as doron10:00
*** teran has quit IRC10:02
*** pixelb has joined #openstack-dev10:03
*** faramir1 has joined #openstack-dev10:04
*** diakunchikov__ has quit IRC10:06
*** aditirav has quit IRC10:07
*** aditirav has joined #openstack-dev10:09
*** sahid has joined #openstack-dev10:10
*** rushiagr has quit IRC10:13
*** xingchao has quit IRC10:13
*** comay has quit IRC10:13
*** comay has joined #openstack-dev10:14
*** rushiagr has joined #openstack-dev10:14
*** rcleere has quit IRC10:15
*** rcleere has joined #openstack-dev10:15
*** itooon has quit IRC10:17
*** itooon has joined #openstack-dev10:20
*** krast has quit IRC10:21
*** neeti has quit IRC10:22
*** nshaikh has joined #openstack-dev10:22
*** neeti has joined #openstack-dev10:22
*** rushiagr has quit IRC10:25
*** Shaan7 has quit IRC10:27
*** doron is now known as doron_afk10:28
*** teran has joined #openstack-dev10:29
*** paragan has quit IRC10:31
*** jcooley_ has joined #openstack-dev10:33
*** rushiagr has joined #openstack-dev10:33
*** jcooley_ has quit IRC10:38
*** rushiagr2 has joined #openstack-dev10:39
*** vkozhukalov has quit IRC10:40
*** rushiagr has quit IRC10:40
*** jp_at_hp has joined #openstack-dev10:41
*** tonyfy has quit IRC10:42
*** tkammer has quit IRC10:42
*** tkammer has joined #openstack-dev10:42
*** jcooley_ has joined #openstack-dev10:43
*** rods has joined #openstack-dev10:44
*** sushil_ has joined #openstack-dev10:44
*** mrunge has quit IRC10:47
*** zul has quit IRC10:47
*** jcooley_ has quit IRC10:48
*** jcooley_ has joined #openstack-dev10:48
*** xqueralt has joined #openstack-dev10:48
*** zul has joined #openstack-dev10:48
*** sushil_ has quit IRC10:49
*** martyntaylor1 has quit IRC10:50
*** athomas has quit IRC10:51
*** vkozhukalov has joined #openstack-dev10:52
*** jcooley_ has quit IRC10:52
*** sushil_ has joined #openstack-dev10:53
*** mrunge has joined #openstack-dev10:53
*** jcooley_ has joined #openstack-dev10:53
*** xingchao has joined #openstack-dev10:54
*** athomas has joined #openstack-dev10:55
*** jaimegil has quit IRC10:57
*** jcooley_ has quit IRC10:58
*** jcooley_ has joined #openstack-dev10:58
*** xingchao_ has joined #openstack-dev10:59
*** SergeyLukjanov has quit IRC11:01
*** xingchao has quit IRC11:03
*** jcooley_ has quit IRC11:03
*** itooon has quit IRC11:03
pixelbjd__ re ceilometer havana wsme cap. Would this commit be compat with wsme-0.5b5 or does it need 0.5b6? https://github.com/openstack/ceilometer/commit/e4a1a4f11:03
*** jcooley_ has joined #openstack-dev11:04
*** rushiagr2 has quit IRC11:05
*** rushiagr3 has joined #openstack-dev11:05
*** guohliu has quit IRC11:05
*** flaper87 is now known as flaper87|afk11:07
*** jcooley_ has quit IRC11:08
*** ruhe has joined #openstack-dev11:08
*** xingchao_ has quit IRC11:08
*** evgenyf has quit IRC11:09
*** markmc has joined #openstack-dev11:09
*** amuller_ has joined #openstack-dev11:10
*** nati_ueno has quit IRC11:10
*** nati_ueno has joined #openstack-dev11:11
*** ArminderS- has quit IRC11:11
*** DinaBelova has quit IRC11:11
*** irenab has quit IRC11:11
*** amuller has quit IRC11:11
*** teju_ has joined #openstack-dev11:12
*** akrivoka has joined #openstack-dev11:12
*** nati_uen_ has joined #openstack-dev11:12
*** rushiagr3 is now known as rushiagr11:14
*** pcm has joined #openstack-dev11:14
*** safchain has quit IRC11:14
*** jcooley_ has joined #openstack-dev11:14
*** nati_ueno has quit IRC11:15
*** reidrac has joined #openstack-dev11:16
*** pcm has quit IRC11:16
pixelbjd__, I guess not since it removes some validation code11:16
*** pcm has joined #openstack-dev11:16
*** evgenyf has joined #openstack-dev11:16
*** marun has joined #openstack-dev11:17
*** jimjiang has quit IRC11:17
*** jimjiang has joined #openstack-dev11:18
*** jcooley_ has quit IRC11:19
*** jcooley_ has joined #openstack-dev11:19
*** rongze has quit IRC11:19
*** teju_ has quit IRC11:20
*** jcooley_ has quit IRC11:23
*** jcooley_ has joined #openstack-dev11:24
*** jimjiang has quit IRC11:25
*** DinaBelova has joined #openstack-dev11:25
*** jimjiang has joined #openstack-dev11:26
*** SergeyLukjanov has joined #openstack-dev11:26
*** kushal has joined #openstack-dev11:27
*** salv-orlando has joined #openstack-dev11:28
*** jcooley_ has quit IRC11:29
*** jcooley_ has joined #openstack-dev11:30
*** jimjiang has quit IRC11:31
*** SergeyLukjanov has quit IRC11:34
*** jcooley_ has quit IRC11:34
*** jcooley_ has joined #openstack-dev11:35
*** rfolco has joined #openstack-dev11:36
*** unicell_ has quit IRC11:36
*** unicell has joined #openstack-dev11:36
*** unicell has quit IRC11:36
*** unicell has joined #openstack-dev11:36
*** SergeyLukjanov has joined #openstack-dev11:37
*** noorul has quit IRC11:37
*** xqueralt has quit IRC11:38
*** xqueralt has joined #openstack-dev11:38
*** jcooley_ has quit IRC11:39
*** jcooley_ has joined #openstack-dev11:40
*** zoresvit has joined #openstack-dev11:41
*** jimjiang has joined #openstack-dev11:42
*** ruhe has quit IRC11:42
*** ruhe has joined #openstack-dev11:43
*** rongze has joined #openstack-dev11:44
*** jcooley_ has quit IRC11:45
*** rongze_ has joined #openstack-dev11:45
*** ArxCruz has joined #openstack-dev11:45
*** jcooley_ has joined #openstack-dev11:46
*** salv-orlando has quit IRC11:47
*** jaimegil has joined #openstack-dev11:47
*** rods has quit IRC11:48
*** venum has quit IRC11:48
*** ruhe has quit IRC11:48
*** zaneb has quit IRC11:49
*** rongze has quit IRC11:49
*** Alexei_987 has joined #openstack-dev11:50
*** itooon has joined #openstack-dev11:50
*** HenryG has quit IRC11:50
*** jcooley_ has quit IRC11:50
*** jcooley_ has joined #openstack-dev11:51
*** jimjiang has quit IRC11:51
*** jimjiang has joined #openstack-dev11:53
*** chandankumar has quit IRC11:53
*** chandankumar has joined #openstack-dev11:53
*** kutija has joined #openstack-dev11:53
marunuh, anybody else having issues with restacking due to nova-* services running as daemon and persisting past screen being killed?11:54
*** jcooley_ has quit IRC11:55
*** jcooley_ has joined #openstack-dev11:56
*** jimjiang has quit IRC11:57
*** jimjiang has joined #openstack-dev11:58
*** drewlander has joined #openstack-dev11:58
*** mkollaro has joined #openstack-dev11:59
*** jcooley_ has quit IRC12:01
*** jcooley_ has joined #openstack-dev12:01
*** zaneb has joined #openstack-dev12:02
*** noorul has joined #openstack-dev12:02
*** CaptTofu has quit IRC12:02
*** CaptTofu has joined #openstack-dev12:03
*** jimjiang has quit IRC12:03
*** rongze_ has quit IRC12:03
*** jimjiang has joined #openstack-dev12:04
*** lucasagomes is now known as lucas-hungry12:05
*** teran_ has joined #openstack-dev12:05
*** jcooley_ has quit IRC12:05
*** shakayumi has joined #openstack-dev12:06
*** teran has quit IRC12:08
*** rushiagr2 has joined #openstack-dev12:08
*** rushiagr has quit IRC12:09
*** salv-orlando has joined #openstack-dev12:10
*** salv-orlando has quit IRC12:10
*** glenng has quit IRC12:11
*** jimjiang has quit IRC12:11
*** jcooley_ has joined #openstack-dev12:11
*** rushiagr3 has joined #openstack-dev12:11
*** jimjiang has joined #openstack-dev12:12
*** rushiagr2 has quit IRC12:13
*** corXi has quit IRC12:13
*** corXi has joined #openstack-dev12:13
*** CaptTofu has quit IRC12:14
*** CaptTofu has joined #openstack-dev12:14
*** jcooley_ has quit IRC12:15
*** dstanek has quit IRC12:16
*** jcooley_ has joined #openstack-dev12:16
*** akscram has quit IRC12:17
*** Abhishek_ has quit IRC12:17
*** hajay_ has joined #openstack-dev12:19
*** jcooley_ has quit IRC12:21
*** jcooley_ has joined #openstack-dev12:21
*** jaimegil has quit IRC12:22
*** martyntaylor has joined #openstack-dev12:22
*** dave_tucker has joined #openstack-dev12:24
*** jcooley_ has quit IRC12:25
*** corXi has quit IRC12:26
*** corXi has joined #openstack-dev12:26
*** jcooley_ has joined #openstack-dev12:26
*** jruzicka has joined #openstack-dev12:27
*** jaimegil has joined #openstack-dev12:27
*** FunnyLookinHat has joined #openstack-dev12:27
*** faramir1 has quit IRC12:28
*** nshaikh has left #openstack-dev12:28
*** dolphm has joined #openstack-dev12:29
*** mkollaro1 has joined #openstack-dev12:30
*** mkollaro has quit IRC12:30
*** jcooley_ has quit IRC12:30
*** jcooley_ has joined #openstack-dev12:31
*** devvesa has quit IRC12:32
*** marios_ has joined #openstack-dev12:33
*** marios_ has quit IRC12:33
*** yaguang has quit IRC12:33
*** paragan has joined #openstack-dev12:33
*** rongze has joined #openstack-dev12:34
*** yolanda has quit IRC12:35
*** jaimegil has quit IRC12:35
*** yolanda has joined #openstack-dev12:36
*** tdruiva has joined #openstack-dev12:36
*** jcooley_ has quit IRC12:36
*** jcooley_ has joined #openstack-dev12:37
*** jcooley_ has quit IRC12:37
*** tdruiva has quit IRC12:37
*** kutija has quit IRC12:37
*** jcooley_ has joined #openstack-dev12:38
*** tdruiva has joined #openstack-dev12:38
*** corXi has quit IRC12:38
*** e0ne has quit IRC12:38
*** corXi has joined #openstack-dev12:40
*** morazi has joined #openstack-dev12:40
*** rongze has quit IRC12:42
*** jcooley_ has quit IRC12:42
*** tdruiva has quit IRC12:42
*** jcooley_ has joined #openstack-dev12:43
*** jcooley_ has quit IRC12:43
*** abramley has quit IRC12:45
*** jcooley_ has joined #openstack-dev12:49
*** gszasz has quit IRC12:50
*** nosnos has quit IRC12:51
*** nurla has joined #openstack-dev12:51
*** tdruiva has joined #openstack-dev12:52
*** athomas has quit IRC12:53
*** gszasz has joined #openstack-dev12:53
*** jcooley_ has quit IRC12:54
*** andreaf has joined #openstack-dev12:54
*** jcooley_ has joined #openstack-dev12:54
*** exed has quit IRC12:54
*** irenab has joined #openstack-dev12:54
*** aditirav has quit IRC12:55
*** SergeyLukjanov has quit IRC12:56
*** mkollaro has joined #openstack-dev12:57
*** kutija has joined #openstack-dev12:58
*** SergeyLukjanov has joined #openstack-dev12:58
*** jimjiang has quit IRC12:59
*** jcooley_ has quit IRC12:59
*** jcooley_ has joined #openstack-dev13:00
*** exed has joined #openstack-dev13:00
*** jimjiang has joined #openstack-dev13:00
*** athomas has joined #openstack-dev13:00
*** mkollaro1 has quit IRC13:00
ttxmarkmcclain: around?13:01
markmcclainttx: hi13:01
ttxstill doing 1:1s here, no time to set up my logged office channel13:01
markmcclainok13:01
*** mkollaro has quit IRC13:02
ttxhttps://launchpad.net/neutron/+milestone/icehouse-213:02
*** gszasz has quit IRC13:02
*** afazekas has quit IRC13:02
ttxonly one to triage: https://blueprints.launchpad.net/neutron/+spec/floating-ip-extra-route13:02
markmcclainyeah… still on the fence on that one13:02
ttxlooks like you beat the tide13:02
markmcclainyeah13:03
ttxGood progress too overall13:03
*** sthaha has joined #openstack-dev13:03
*** sthaha has quit IRC13:03
*** sthaha has joined #openstack-dev13:03
markmcclainyeah we have a healthy mix in review now which is good13:03
ttxmarkmcclain: a few dependency issues that might be worth exploring:13:04
*** xga has quit IRC13:04
*** xga_ has joined #openstack-dev13:04
ttxdnsmasq-mode-keyword (Medium, scollins, icehouse-2) depends on ipv6-feature-parity (Undefined, markmcclain, icehouse-3) ?13:04
*** jcooley_ has quit IRC13:04
markmcclainoops.. I'll fix that13:04
*** jimjiang has quit IRC13:04
*** gargya has joined #openstack-dev13:04
ttxsame for vif-attribute-for-hairpinning (Medium, scollins, icehouse-2)13:04
*** jcooley_ has joined #openstack-dev13:04
ttxsame for ipv6-provider-nets-slaac (Low, comcast-openstack, icehouse-2)13:04
ttxall depending on ipv6-feature-parity13:04
markmcclainah all of the ipv6 ones13:04
ttxwas ipv6-feature-parity recently moved to i3 ?13:05
*** jimjiang has joined #openstack-dev13:05
markmcclainnot intentionally13:06
*** yassine has quit IRC13:06
markmcclainmay have accidentally selected wrong milestone in the dropdown13:06
*** rushiagr3 has quit IRC13:06
*** nati_uen_ has quit IRC13:06
*** yassine has joined #openstack-dev13:06
ttxmarkmcclain: yeah, sounds like something you should at least ttry to get in i2... otherwise could slip (again)13:06
*** mkollaro has joined #openstack-dev13:07
markmcclainyeah… I'll also reparent a few to make the dep a cleaner13:07
ttxmarkmcclain: once that's fixed it all looks good. If you get bored during the holidays you can start triaging the i3 blueprints13:08
markmcclaina gift to myself :)13:08
ttxmarkmcclain: is there anything you'd like to discuss at the meeting today ?13:08
markmcclainno13:08
markmcclainno 1:1 next Tuesday right?13:09
ttxWe'll skip the next two meetings, I think13:09
*** jcooley_ has quit IRC13:09
ttx24 and 31...13:09
markmcclainok13:09
*** e0ne has joined #openstack-dev13:09
ttxso we'll skip the 1:1s as well13:09
ttxmarkmcclain: see you later!13:09
*** xingchao has joined #openstack-dev13:09
markmcclaintalk to you this evening13:09
*** jcooley_ has joined #openstack-dev13:10
*** shakayumi has quit IRC13:10
*** jimjiang has quit IRC13:11
*** shakayumi has joined #openstack-dev13:11
*** _dbalog has quit IRC13:12
*** jimjiang has joined #openstack-dev13:12
*** flaper87|afk is now known as flaper8713:13
*** e0ne has quit IRC13:14
*** jcooley_ has quit IRC13:14
*** jcooley_ has joined #openstack-dev13:14
ttxdhellmann: around?13:15
dhellmannhi, ttx!13:15
*** haomaiwang has quit IRC13:15
ttxdhellmann: good morning!13:15
ttxhttps://launchpad.net/oslo/+milestone/icehouse-213:15
dhellmannttx: good afternoon!13:15
*** haomaiwang has joined #openstack-dev13:15
ttxhttps://blueprints.launchpad.net/oslo/+spec/middleware-request-id needs a priority (or be booted)13:15
*** shakayumi has quit IRC13:15
*** ruhe has joined #openstack-dev13:16
ttxotherwise looks good13:16
dhellmannyeah, I was just looking at that one -- I need to track down the owner13:16
ttxhttps://launchpad.net/oslo.messaging/+milestone/icehouse-2 looks good13:16
dhellmannmarkmc has done a good job keeping that organized13:16
ttxA bit too many "not started" I think, with the holidays coming up13:17
ttx(on the "oslo" side)13:17
*** yamahata has joined #openstack-dev13:17
dhellmannyeah, a few of those are mine, and I expect to have some time to start the high priority one this week13:17
ttxok13:17
dhellmannthe others may slide, but I'll give them until the first of the year in case people are planning to work on them during the holidays13:17
*** jimjiang has quit IRC13:17
ttximprove-config-discovery-for-docs (Medium, doug-hellmann, icehouse-2) depends on remove-import-side-effects (Undefined, doug-hellmann, No milestone) ?13:17
*** rongze has joined #openstack-dev13:18
dhellmannhmm, those are related but I don't think the dependency is strictly true13:18
dhellmannmaybe it's backwards13:18
*** dolphm has quit IRC13:18
dhellmannthe config discovery stuff can (and should) be done before the other work, so I guess I set that relationship up wrong13:18
ttxdhellmann: ok, I'll fix it13:18
dhellmannsorry about that, I didn't notice I'd done that13:19
*** jimjiang has joined #openstack-dev13:19
*** mrunge has quit IRC13:19
*** jcooley_ has quit IRC13:19
ttxotherwise all looks good13:19
ttxdhellmann: anything you want to discuss at the cross-project meeting later ?13:19
*** jcooley_ has joined #openstack-dev13:19
dhellmannno, I don't think so13:20
ttxWe'll skip the next two 1:1s and cross-project meeting fwiw13:20
ttx(on the 24 and the 31)13:20
dhellmannok, makes sense13:20
*** urulama has quit IRC13:20
ttxdhellmann: ok, then I'll see you at the meeting(s) later13:21
dhellmannok, thanks, see you then13:21
ttxthx!13:21
*** thomasem has joined #openstack-dev13:21
*** haomaiwa_ has joined #openstack-dev13:22
*** afazekas has joined #openstack-dev13:22
*** dolphm has joined #openstack-dev13:23
*** ilyashakhat has joined #openstack-dev13:23
*** haomaiwang has quit IRC13:24
*** jimjiang has quit IRC13:24
*** haomaiwa_ has quit IRC13:24
*** jcooley_ has quit IRC13:24
*** ilyashakhat_ has quit IRC13:24
*** e0ne has joined #openstack-dev13:25
*** tdruiva has quit IRC13:25
*** tdruiva has joined #openstack-dev13:26
*** jcooley_ has joined #openstack-dev13:26
*** dolphm has quit IRC13:27
*** sandywalsh_ has quit IRC13:29
*** ruhe is now known as ruhe_13:29
*** jcooley_ has quit IRC13:30
*** jimjiang has joined #openstack-dev13:30
*** ruhe_ is now known as ruhe13:31
*** haomaiwang has joined #openstack-dev13:31
*** doron_afk is now known as doron13:31
*** jcooley_ has joined #openstack-dev13:32
*** rods has joined #openstack-dev13:32
*** jdob has joined #openstack-dev13:35
*** jimjiang has quit IRC13:35
*** jimjiang has joined #openstack-dev13:36
*** jcooley_ has quit IRC13:36
*** boris-42 has quit IRC13:37
*** ig has quit IRC13:37
*** jcooley_ has joined #openstack-dev13:37
*** Shaan7 has joined #openstack-dev13:37
*** Shaan7 has quit IRC13:37
*** Shaan7 has joined #openstack-dev13:37
*** martyntaylor has quit IRC13:38
*** ruhe is now known as ruhe_13:38
*** buzztroll has joined #openstack-dev13:38
*** ig has joined #openstack-dev13:39
*** Nikolay_1t has quit IRC13:39
*** jobewan_ has joined #openstack-dev13:39
*** jobewan_ has quit IRC13:39
*** rongze_ has joined #openstack-dev13:39
*** jobewan_ has joined #openstack-dev13:40
*** ig has quit IRC13:40
*** jobewan_ has quit IRC13:40
*** ruhe_ is now known as ruhe13:41
*** ig has joined #openstack-dev13:41
*** jimjiang has quit IRC13:41
*** sandywalsh_ has joined #openstack-dev13:42
*** jimjiang has joined #openstack-dev13:42
*** AMike has quit IRC13:42
*** jcooley_ has quit IRC13:42
*** AMike has joined #openstack-dev13:43
*** AMike has quit IRC13:43
*** AMike has joined #openstack-dev13:43
*** jcooley_ has joined #openstack-dev13:43
*** rongze has quit IRC13:43
*** jobewan has joined #openstack-dev13:43
*** tosate has joined #openstack-dev13:44
*** gargya_ has joined #openstack-dev13:44
*** gargya__ has joined #openstack-dev13:45
*** gargya has quit IRC13:45
*** gargya__ is now known as gargya13:46
ttxjgriffith: around?13:47
*** rongze_ has quit IRC13:48
*** jcooley_ has quit IRC13:48
*** jcooley_ has joined #openstack-dev13:48
*** rongze has joined #openstack-dev13:48
*** tosate has quit IRC13:48
*** irenab has quit IRC13:48
*** gargya_ has quit IRC13:48
*** buzztroll has quit IRC13:48
*** rongze_ has joined #openstack-dev13:49
*** jimjiang has quit IRC13:49
*** dolphm has joined #openstack-dev13:49
*** dsirrine has joined #openstack-dev13:49
*** dvarga has joined #openstack-dev13:50
*** martyntaylor has joined #openstack-dev13:50
*** mkollaro1 has joined #openstack-dev13:51
*** mkollaro has quit IRC13:51
*** dolphm has quit IRC13:51
*** dolphm_ has joined #openstack-dev13:51
*** afazekas has quit IRC13:51
*** jcooley_ has quit IRC13:52
*** rongze has quit IRC13:53
*** shakayumi has joined #openstack-dev13:54
*** dprince has joined #openstack-dev13:54
*** jcooley_ has joined #openstack-dev13:54
*** buzztroll has joined #openstack-dev13:54
*** jcooley_ has quit IRC13:54
*** asselin has quit IRC13:55
*** asselin has joined #openstack-dev13:55
*** itooon has quit IRC13:55
*** martyntaylor has quit IRC13:56
*** tris has quit IRC13:56
*** itooon has joined #openstack-dev13:56
*** jcooley_ has joined #openstack-dev13:56
*** xga has joined #openstack-dev13:56
*** xga_ has quit IRC13:56
*** rfolco has quit IRC13:56
*** pfreund has quit IRC13:56
*** lsmola_ has quit IRC13:56
*** jimjiang has joined #openstack-dev13:57
*** corXi has quit IRC13:58
*** gargya_ has joined #openstack-dev13:58
*** corXi has joined #openstack-dev13:58
*** dolphm_ has quit IRC13:58
*** lxsli has joined #openstack-dev13:58
*** gargya has quit IRC13:59
*** cpallares has joined #openstack-dev13:59
*** gargya_ is now known as gargya13:59
*** HenryG has joined #openstack-dev14:00
*** corXi has quit IRC14:00
*** glenng has joined #openstack-dev14:00
*** corXi has joined #openstack-dev14:01
*** jcooley_ has quit IRC14:01
*** jimjiang has quit IRC14:01
*** corXi has joined #openstack-dev14:01
*** jcooley_ has joined #openstack-dev14:01
*** tris has joined #openstack-dev14:01
*** jimjiang has joined #openstack-dev14:01
*** gszasz has joined #openstack-dev14:02
*** gargya_ has joined #openstack-dev14:02
*** martyntaylor has joined #openstack-dev14:03
*** yaguang has joined #openstack-dev14:03
*** dolphm has joined #openstack-dev14:03
*** sthaha has quit IRC14:04
*** jdob has quit IRC14:04
*** jdob_ has joined #openstack-dev14:04
*** hajay__ has joined #openstack-dev14:05
*** gargya has quit IRC14:05
*** gargya_ is now known as gargya14:06
*** jcooley_ has quit IRC14:06
*** aeperezt has joined #openstack-dev14:06
*** jcooley_ has joined #openstack-dev14:07
*** heyongli has joined #openstack-dev14:07
*** e0ne_ has joined #openstack-dev14:07
*** dolphm has quit IRC14:08
*** rfolco has joined #openstack-dev14:08
*** hajay_ has quit IRC14:08
*** MaxV has joined #openstack-dev14:09
*** hajay__ has quit IRC14:09
*** lsmola_ has joined #openstack-dev14:10
*** pfreund has joined #openstack-dev14:11
*** e0ne has quit IRC14:11
*** alop has joined #openstack-dev14:11
*** jcooley_ has quit IRC14:12
*** jcooley_ has joined #openstack-dev14:13
*** akscram has joined #openstack-dev14:13
*** clayb has joined #openstack-dev14:14
*** eharney has joined #openstack-dev14:15
*** jimjiang has quit IRC14:16
*** jcooley_ has quit IRC14:17
*** jimjiang has joined #openstack-dev14:17
*** abramley has joined #openstack-dev14:17
*** stannie has joined #openstack-dev14:18
*** jcooley_ has joined #openstack-dev14:18
*** kbringard has joined #openstack-dev14:18
*** jcooley_ has quit IRC14:18
*** joesavak has joined #openstack-dev14:18
*** jdob_ has quit IRC14:18
*** jdob has joined #openstack-dev14:18
*** nermina has joined #openstack-dev14:19
*** jcooley_ has joined #openstack-dev14:20
*** jimjiang has quit IRC14:22
*** danielbruno has joined #openstack-dev14:22
*** afazekas has joined #openstack-dev14:23
*** doron is now known as doron_afk14:23
*** jimjiang has joined #openstack-dev14:23
*** jcooley_ has quit IRC14:24
*** tris has quit IRC14:25
*** dolphm has joined #openstack-dev14:25
*** jcooley_ has joined #openstack-dev14:25
*** tris has joined #openstack-dev14:25
*** radez_g0n3 is now known as radez14:26
*** KurtMartin has joined #openstack-dev14:26
*** jimjiang has quit IRC14:27
*** yamahata__ has quit IRC14:27
*** abramley has quit IRC14:28
*** mindpixel has quit IRC14:28
*** yamahata__ has joined #openstack-dev14:28
*** jcooley_ has quit IRC14:29
*** jcooley_ has joined #openstack-dev14:30
*** mindpixel has joined #openstack-dev14:30
jgriffithttx: hola14:30
*** andreaf has quit IRC14:31
*** ruhe has quit IRC14:31
*** shakayumi has quit IRC14:31
*** yamahata has quit IRC14:32
ttxjgriffith: we can do your 1:1 now if you want (originally scheduled at 13:45 UTC)14:33
jgriffithttx: yes please14:33
*** jimjiang has joined #openstack-dev14:33
*** markmcclain has quit IRC14:33
*** yamahata has joined #openstack-dev14:34
ttxhttps://launchpad.net/cinder/+milestone/icehouse-214:34
jgriffithttx: sorry... thought we werwe 14:4514:34
ttxlooks good, one left to triage @ https://blueprints.launchpad.net/cinder/+spec/cinder-backup-recover-api14:34
*** jcooley_ has quit IRC14:34
*** mriedem has joined #openstack-dev14:34
jgriffithttx: on it14:35
ttxjgriffith: there is also a dependency issue:14:35
jgriffithttx: which one?14:35
ttxcopy-volume-to-image-task-flow (Low, abhijeet-malawade, icehouse-2) depends on create-volume-flow (Undefined, anastasia-karpinska, No milestone)14:35
jgriffithaye14:36
jgriffithtaskflow, smaskflow14:36
*** Shaan7 has quit IRC14:36
jgriffithttx: I still need to sync with those folks14:36
jgriffithttx: I'm a bit unclear of their plans here TBH14:36
*** Shaan7 has joined #openstack-dev14:37
* jgriffith is making a note to sort these at tomorrows meeting14:37
ttxjgriffith: cool, that's about it. Good progress overall14:37
ttxwe'll skip the next 2 1:1s and cross-project meetings14:37
jgriffithYeah, I'm happy with how things are going the milestone14:37
jgriffithindeed...14:37
jgriffithHappy Holidays!14:37
ttxis there anything you want to see discussed at the meeting today ?14:37
jgriffithNope14:38
jgriffithsaving my troulbe for the new year ;)14:38
jgriffithtrouble14:38
ttxjgriffith: ok then, see you there14:38
*** abramley has joined #openstack-dev14:39
*** davidhadas has joined #openstack-dev14:39
jgriffithttx: thanks!14:39
*** jcooley_ has joined #openstack-dev14:39
*** rushiagr3 has joined #openstack-dev14:41
*** jayg|g0n3 is now known as jayg14:42
*** xingchao has quit IRC14:43
*** jcooley_ has quit IRC14:44
*** ruhe has joined #openstack-dev14:44
*** rohitk has quit IRC14:44
*** FunnyLookinHat has quit IRC14:45
*** jcooley_ has joined #openstack-dev14:45
*** glenng has quit IRC14:45
*** glenng has joined #openstack-dev14:45
*** n0ano has joined #openstack-dev14:45
*** heyongli has quit IRC14:45
*** jasondotstar has joined #openstack-dev14:46
*** yolanda has quit IRC14:48
*** burt has joined #openstack-dev14:48
*** mtreinish has quit IRC14:48
*** alpha_ori has quit IRC14:48
jgriffithsdague: ic you assigned yourself: https://bugs.launchpad.net/cinder/+bug/126173114:49
uvirtbotLaunchpad bug 1261731 in cinder "Unable to deactivate LVM snapshot" [Undecided,In progress]14:49
*** pixelb has quit IRC14:49
*** yolanda has joined #openstack-dev14:49
jgriffithsdague: assuming just change: https://github.com/openstack/cinder/blob/master/cinder/brick/local_dev/lvm.py#L577 to info14:49
jgriffithsdague: I'll leave it to you, if you don't have time lemme know14:49
*** jcooley_ has quit IRC14:49
*** topol has joined #openstack-dev14:49
sdaguejgriffith: there is actually a patch out there14:50
*** dperaza has joined #openstack-dev14:50
sdaguejgriffith: https://review.openstack.org/#/c/62622/14:50
sdagueI changed them to debug14:50
*** pixelb has joined #openstack-dev14:50
sdaguebecause if it all just works, then the end user doesn't really care14:50
*** redbo has quit IRC14:50
sdagueonly devs that want to see that it tried a recovery14:50
*** jcooley_ has joined #openstack-dev14:51
*** redbo has joined #openstack-dev14:51
*** heyongli has joined #openstack-dev14:51
*** mtreinish has joined #openstack-dev14:51
*** alpha_ori has joined #openstack-dev14:51
*** ayoung has joined #openstack-dev14:51
*** nkinder has quit IRC14:52
*** aron28 has joined #openstack-dev14:52
*** aron28 is now known as syed_armani14:53
*** syed_armani has left #openstack-dev14:53
*** syed_armani has joined #openstack-dev14:54
*** buzztroll has quit IRC14:54
*** mfer has joined #openstack-dev14:54
*** jcooley_ has quit IRC14:55
*** mindpixel has quit IRC14:55
*** ffio has joined #openstack-dev14:55
*** jcooley_ has joined #openstack-dev14:55
*** jecarey has joined #openstack-dev14:57
*** gargya has quit IRC14:57
*** david-lyle_ has joined #openstack-dev14:57
*** xingchao has joined #openstack-dev14:58
*** _dbalog has joined #openstack-dev14:58
*** chandankumar has quit IRC14:59
*** achampion has quit IRC14:59
*** e0ne_ is now known as e0ne15:00
syed_armanitristanC: ping15:00
*** achampion has joined #openstack-dev15:00
*** xingchao has quit IRC15:00
*** jcooley_ has quit IRC15:00
ttxdolphm: around?15:00
*** markmcclain has joined #openstack-dev15:01
*** mriedem has quit IRC15:01
tristanCsyed_armani: pong!15:01
*** Ryan_Lane has joined #openstack-dev15:01
dolphmttx: got rescheduled to do the project status update webinar thing right now :)15:01
syed_armanitristanC: I am wondering if you are working on this bug --> https://bugs.launchpad.net/horizon/+bug/120296515:01
*** tkammer has quit IRC15:01
uvirtbotLaunchpad bug 1202965 in nova "The name VCPUs (total) of Hypervisors is confusing" [Undecided,In progress]15:01
dolphmttx: i'll poke you when i'm done?15:01
ttxdolphm: yay15:01
ttxdolphm: yes, we'll see when we can talk15:01
tristanCsyed_armani: oups, I forgot to de/assigned myself. I tried to but my change is more complex than excepted :(15:02
ttxrussellb: interested in stealing the slot ?15:02
tristanCsyed_armani: so no15:02
*** mriedem has joined #openstack-dev15:02
*** jcooley_ has joined #openstack-dev15:02
syed_armanitristanC: :( , thx!!15:02
*** buzztroll has joined #openstack-dev15:03
russellbttx: hey, sure we can go ahead and start15:03
ttxhttps://launchpad.net/nova/+milestone/icehouse-215:03
russellbi have a deadline set for this thursday15:03
*** matiu has quit IRC15:03
russellbfor getting blueprints approved for icehouse-215:03
ttxrussellb: ok15:03
russellbthe rest will be deferred15:03
*** vijendar has joined #openstack-dev15:03
*** aditirav has joined #openstack-dev15:04
russellblots of critical bugs unassigned, too ...15:04
russellball gate bugs though15:04
russellband people don't really like to assign themselves, even if they are pitching in debugging15:04
ttxmore work needed on rpc-major-version-updates-icehouse ?15:04
russellbyes, that should be set back to good progress15:04
russellbwill fix15:04
*** xga has quit IRC15:05
russellbit was all done, but then i abandoned some of it and have to redo it15:05
*** xingchao has joined #openstack-dev15:05
*** davidhadas has quit IRC15:05
russellbchanged15:05
ttxrussellb: ok, I think we'll see clearer after Thursday15:05
russellbhope so15:05
ttxmaybe I'll ping you again then, so that we can have it clean and tidy for the holidays15:05
russellbsure that's fine15:06
russellbprobably Friday15:06
ttxbecause next 2 weeks we'll skip 1:1s and meetings15:06
russellbsince EOD is deadline15:06
russellbif you're around friday15:06
ttxsure. Ping me if i forgot about it15:06
russellbheh will try15:06
russellbi can put it on my calendar15:06
*** mindpixel has joined #openstack-dev15:07
ttxrussellb: little point in discussing progress until that's done.15:07
ttxrussellb: anything you want to discuss at the meeting today ?15:07
*** matiu has joined #openstack-dev15:07
*** doron_afk is now known as doron15:08
*** neeti has quit IRC15:08
*** davidhadas has joined #openstack-dev15:08
*** xga has joined #openstack-dev15:08
russellbi don't think so15:08
*** david-lyle_ has quit IRC15:08
ttxrussellb: ok then, see you there15:08
russellbthanks15:08
*** david-lyle_ has joined #openstack-dev15:08
notmynamerussellb: have you seen http://not.mn/gate_status.html ?15:09
ttxdavid-lyle: we can talk now if you're around15:10
david-lyle_sure, here15:10
russellbnotmyname: just saw it a bit ago this morning15:10
russellbnotmyname: presumably you follow the "state of the gate" reports on the list?15:10
ttxdavid-lyle: https://launchpad.net/horizon/+milestone/icehouse-215:10
ttxdavid-lyle: status looks good15:11
notmynamerussellb: yes15:11
ttxdavid-lyle: progress is good15:11
*** rushiagr3 is now known as rushiagr15:11
*** alex_xu has quit IRC15:11
ttxdavid-lyle: we might have trouble discussing the dependency issue with ceilometer, as jd__ will miss the meeting today15:12
david-lyle_ttx: several bps are close to landing15:12
*** stevemar has joined #openstack-dev15:12
jd__ttx: nah I might be there15:12
ttxjd__: oh, cool15:12
ttxFTR: horizon/ceilometer-api-enhancements <- ceilometer/statistics-order-by-and-limit-for-grouped-query15:12
*** safchain has joined #openstack-dev15:13
ttxjd__: or we can discuss it now if you prefer15:13
jd__ttx: I've 10 minutes if that's enough :)15:13
*** KurtMartin has quit IRC15:13
*** KurtMartin has joined #openstack-dev15:14
ttxwe can try15:14
*** KurtMartin has quit IRC15:14
ttxdavid-lyle: what do you need from ceilometer to complete that one ?15:14
david-lyle_ttx: I've asked lsmola to split the Horizon bp into two parts, one that depends on the ceilometer bp, and one that is the remainder15:14
*** otherwiseguy has joined #openstack-dev15:15
ttxand do the dependent one once the feature hits in ceilometer ?15:15
david-lyle_yes, that way it's not completely blocked15:15
ttx(i.e. target the dependent one to "next")15:15
david-lyle_yes15:15
ttxdavid-lyle: that works15:15
*** alunduil has quit IRC15:16
*** kevinconway has joined #openstack-dev15:16
*** hajay_ has joined #openstack-dev15:16
ttxjd__: that statistics-order-by-and-limit-for-grouped-query won't get done in icehouse, right ?15:16
david-lyle_we'll see if we can make that split happen today15:16
ttxdavid-lyle: that would be great, thx15:16
*** ngoracke has joined #openstack-dev15:16
*** gszasz has quit IRC15:16
ttxdavid-lyle: anything you'd like to see discussed at the meeting today ?15:16
ttxdavid-lyle: we'll skip the next 2 weeks 1:1s and meetings, fwiw15:16
*** FunnyLookinHat has joined #openstack-dev15:17
jd__ttx: no assignee, so I won't count on it15:17
ttxjd__: ok15:17
*** gszasz has joined #openstack-dev15:17
david-lyle_ttx: I think we're ok, just need to keep making progress15:17
*** ngoracke1 has joined #openstack-dev15:17
ttxdavid-lyle: thx! see you at meeting later15:17
david-lyle_ttx: thanks15:18
david-lyle_dolphm: what's the proper way to change the author on an existing gerrit review?15:18
david-lyle_--amend --author doesn't seem to work15:19
*** hajay_ has quit IRC15:20
*** dave_tucker has quit IRC15:20
*** urulama has joined #openstack-dev15:21
*** lucas-hungry is now known as lucasagomes15:21
*** ngoracke has quit IRC15:21
*** nelsnelson has quit IRC15:21
*** nelsnelson has joined #openstack-dev15:21
*** pfreund has quit IRC15:22
*** heyongli has quit IRC15:23
*** neelashah has joined #openstack-dev15:25
*** urulama has quit IRC15:25
*** AlanClark has joined #openstack-dev15:25
*** yamahata has quit IRC15:26
*** spzala has joined #openstack-dev15:27
*** DinaBelova has quit IRC15:30
*** ffio has quit IRC15:31
*** drewlander has quit IRC15:32
*** amuller_ has quit IRC15:33
*** rnirmal has joined #openstack-dev15:34
*** ayoung has quit IRC15:34
*** mindpixeler has joined #openstack-dev15:39
*** tanisdl has joined #openstack-dev15:39
*** sarob has joined #openstack-dev15:40
*** rollietikes has joined #openstack-dev15:40
*** sarob has quit IRC15:40
stevemarayoung: what should we do about bug 126162215:40
uvirtbotLaunchpad bug 1261622 in keystone "change text or behaviour of the admin token in keystone.conf" [High,Confirmed] https://launchpad.net/bugs/126162215:40
*** mikeoutland has joined #openstack-dev15:40
*** sarob has joined #openstack-dev15:40
*** luisg has quit IRC15:40
*** reed has joined #openstack-dev15:40
*** mindpixel has quit IRC15:42
*** DinaBelova has joined #openstack-dev15:42
*** sarob has quit IRC15:43
*** tkammer has joined #openstack-dev15:43
*** CaptTofu has quit IRC15:44
*** jergerber has joined #openstack-dev15:45
*** carl_baldwin has joined #openstack-dev15:45
*** rraja has quit IRC15:45
*** sarob has joined #openstack-dev15:45
dolphmdavid-lyle_: that's exactly what should work15:46
dolphmdavid-lyle_: actually gerrit probably won't reflect the new authorship for the review level, but the latest patchset should reflect it15:47
*** jcoufal has quit IRC15:47
*** sarob has quit IRC15:48
dolphmttx: o/ free15:48
*** sarob_ has joined #openstack-dev15:48
david-lyle_dolphm: ok, issue has been launchpad expiring the review while being worked on, so just changing the author might not work15:48
*** SergeyLukjanov has quit IRC15:48
dolphmdavid-lyle_: expiring the review or bug?15:48
*** DinaBelova has quit IRC15:48
dolphmdavid-lyle_: or gerrit expiring the review after a downvote?15:48
david-lyle_dolphm: that latter15:49
david-lyle_the15:49
ttxdolphm: let's try to do it quickly now ?15:49
dolphmdavid-lyle_: i'm familiar with that problem :P maybe -ci can bump the expiry up from a week?15:49
*** bswartz has quit IRC15:49
dolphmttx: sure, if you have time15:49
david-lyle_dolphm: thanks15:49
ttx10min15:49
*** corXi has quit IRC15:49
*** luisg has joined #openstack-dev15:49
ttxdolphm: https://launchpad.net/keystone/+milestone/icehouse-215:50
dolphmi still owe you federation blueprint dependency unwinding btw15:50
ttxdolphm: still two to prioritize in there15:50
ttxhttps://blueprints.launchpad.net/keystone/+spec/service-scoped-tokens15:50
ttxhttps://blueprints.launchpad.net/keystone/+spec/name-spaced-roles15:50
*** mlavalle has joined #openstack-dev15:50
*** alex_klimov has quit IRC15:50
*** julienvey_ has quit IRC15:50
*** vkozhukalov has quit IRC15:51
*** corXi has joined #openstack-dev15:51
*** aeperezt has quit IRC15:51
ttxdolphm: there is another dep issue with:15:52
ttxsaml-id (Medium, marek-denis, icehouse-2) depending on auth-domain-architecture (Undefined, No assignee, No milestone)15:52
*** doron is now known as doron_afk15:52
dolphmthat's the federation-related bp unwinding i owe you :)15:52
ttxoh, that too. ok :)15:53
*** sarob_ has quit IRC15:53
ttxotherwise progress looks good15:53
*** salv-orlando has joined #openstack-dev15:53
thomasemjaypipes, Hey, would you have any time today to chat a bit about some schema concerns that were brought to my attention for our event/trait tables in Ceilometer? :)15:53
ttxdolphm: anything you want to discuss at meeting later ?15:53
dolphmi don't believe so15:53
ttxdolphm: we'll skip next two weeks (1:1s and meeting)15:53
dolphmah cool15:53
jaypipesthomasem: absolutely. in about an hour work?15:53
thomasemjaypipes, Wanted to get your thoughts since we're in the process of load testing the drivers. That'd work great!15:54
ttxdolphm: ok, so those two are the only things you need to fix (untriaged stuff and federation unwind)15:54
ttxdolphm: see you at meeting later15:54
dolphmttx: /salute15:54
ttxthx!15:54
*** alexpilotti has joined #openstack-dev15:54
jaypipesthomasem: sounds good. ttyl.15:54
*** mriedem has quit IRC15:55
*** nkinder has joined #openstack-dev15:55
dolphmdhellmann: global requirements patch you might be interested in https://review.openstack.org/#/c/61198/15:55
*** aditirav_ has joined #openstack-dev15:56
*** jecarey has quit IRC15:56
*** dolphm is now known as dolphm_afk15:57
*** johnthetubaguy1 has joined #openstack-dev15:57
*** viktors has joined #openstack-dev15:58
*** aditirav has quit IRC15:58
*** johnthetubaguy has quit IRC15:58
*** boris-42 has joined #openstack-dev15:59
mfercan anyone direct me to a standard on api versioning, features, and how trunk is always usable?15:59
*** xingchao has quit IRC15:59
mferi'm trying to understand how new features affect apis, how the versions change, and how to write clients against this16:00
*** aditirav_ has quit IRC16:00
*** Ruetobas has quit IRC16:01
*** pmathews has joined #openstack-dev16:01
*** alunduil has joined #openstack-dev16:01
*** bdpayne has joined #openstack-dev16:02
*** radez is now known as radez_g0n316:02
*** bnemec_ is now known as bnemec16:02
sdagueannegentle_: you about.16:02
*** eharney has quit IRC16:03
*** aditirav has joined #openstack-dev16:03
*** Ruetobas has joined #openstack-dev16:03
*** eharney has joined #openstack-dev16:03
*** noorul has quit IRC16:03
*** drewlander has joined #openstack-dev16:03
*** aeperezt has joined #openstack-dev16:03
annegentle_sdague: here!16:03
sdagueso I continue to be confused by the commit message request16:03
*** reidrac has quit IRC16:04
sdagueopenstack/governace: publish docs to docs.openstack.org16:04
annegentle_sdague: it looks wide-scoped to me16:04
annegentle_sdague: I want it narrowly scoped in the git history16:04
sdagueseems pretty clear that it would be governance docs16:04
annegentle_sdague: even with the metadata16:04
annegentle_sdague: it gave me pause and might do the same to others16:04
topolsdague, is there a URL that describes how many builds OpenStack does a day.  I remember hearing you quote a value. I cant remember what it was16:04
sdagueso this infrastructure would allow you to publish anything out of the repo16:05
sdaguethough nothing is currently published, because we need to restructure (or add symlinks) to make that work16:05
annegentle_sdague: yes but we wouldn't convert all docs16:05
sdagueannegentle_: maybe, maybe not. This change doesn't really get affected either way16:05
sdaguetopol: http://dague.net/2013/10/27/openstack-ci-by-the-numbers/ was a point in time16:07
*** Ruetobas has quit IRC16:07
*** drewlander has quit IRC16:07
*** teju_ has joined #openstack-dev16:08
topolsdague, is there a good number I can quote for number of builds a day?16:10
topolsdague, wasnt it like 800?16:10
sdaguethe most recent numbers I've got are the ones above, and they are really scoped to the week level16:11
sdagueyou could go mine elastic search, that's what I did16:12
*** Guest53164 is now known as antonym16:12
*** mikeoutland has quit IRC16:13
*** Ruetobas has joined #openstack-dev16:13
*** rnirmal has quit IRC16:13
*** hcc has joined #openstack-dev16:14
*** martyntaylor has quit IRC16:14
*** rnirmal has joined #openstack-dev16:14
*** DennyZhang has joined #openstack-dev16:14
*** HenryG has quit IRC16:14
*** jistr has quit IRC16:14
*** HenryG has joined #openstack-dev16:14
*** markwash has joined #openstack-dev16:16
annegentle_sdague: in the land of governance I think it's best to scope definitively even in meta messaging like commit messages. Not digging my heels in, but being particular about scope and wording for 15 years from now. Our future selves will appreciate the detail.16:16
sdagueannegentle_: but this change doesn't actually specify in any way what content will get web published16:17
*** garyk has quit IRC16:17
sdagueit's actually generic infrastructure for a docs jobs16:18
*** hcc has quit IRC16:18
sdaguecontent tbd16:18
annegentle_sdague: then I want to define what content is intended in the commit message. Unless your intentions are for all docs?16:18
sdagueannegentle_: my intention is for content decisions to be made on their own merrits in the future16:18
annegentle_sdague: I'd also really prefer we investigate build jobs to the wiki, but there's not really a way to discuss that other than -2 on that review...16:19
annegentle_sdague: which seems overbearing16:19
sdagueso I think that is a worthy discussion that should come onto the agenda if you want to16:20
annegentle_sdague: I can bring it up at the TC16:20
*** omachace has left #openstack-dev16:20
annegentle_sdague: when we review the patch (which is on the agenda)16:20
sdagueI'm honestly pretty negative on publish to the wiki16:20
annegentle_sdague: that's cool, we'll discuss16:20
sdaguebecause I think we actually have a really solid workflow of docs, with review, with anyone able to contribute to go to static trees16:21
*** paragan has quit IRC16:21
sdaguesure16:21
*** buzztroll has quit IRC16:21
*** sstent has joined #openstack-dev16:22
sstentAnyone seen this error in conductor before? Expected exception during message handling (Could not find binary nova-compute on host compute-1)16:22
*** mdomsch has quit IRC16:22
*** buzztroll has joined #openstack-dev16:24
*** DennyZhang has quit IRC16:24
*** jecarey has joined #openstack-dev16:24
*** DennyZhang has joined #openstack-dev16:24
*** tan has quit IRC16:24
*** ifarkas has quit IRC16:25
*** markmcclain has quit IRC16:26
*** xqueralt has quit IRC16:26
*** akrivoka has quit IRC16:27
*** martyntaylor has joined #openstack-dev16:27
*** iartarisi has quit IRC16:28
*** kenperkins has joined #openstack-dev16:28
*** corXi has quit IRC16:28
*** jecarey_ has joined #openstack-dev16:28
*** jcooley_ has quit IRC16:30
*** teju_ has quit IRC16:31
*** xga has quit IRC16:31
*** jecarey has quit IRC16:31
*** DennyZhang has quit IRC16:33
*** doron_afk is now known as doron16:33
*** DennyZhang has joined #openstack-dev16:33
*** MaxV has quit IRC16:34
*** pberis has quit IRC16:34
*** dolphm_afk has quit IRC16:35
*** CaptTofu has joined #openstack-dev16:35
*** xga has joined #openstack-dev16:35
*** herndon has joined #openstack-dev16:35
*** ayoung has joined #openstack-dev16:35
*** rcleere has quit IRC16:37
*** MaxV has joined #openstack-dev16:37
*** Mandell has quit IRC16:37
*** CaptTofu has quit IRC16:37
*** CaptTofu has joined #openstack-dev16:37
*** CaptTofu has quit IRC16:38
*** CaptTofu has joined #openstack-dev16:38
*** adalbas has quit IRC16:41
sstentAnyone seen this error in conductor before? Expected exception during message handling (Could not find binary nova-compute on host compute-1)16:42
*** martyntaylor has quit IRC16:43
*** mrodden1 has quit IRC16:44
*** doron is now known as doron_afk16:44
*** BLZbubba_ has quit IRC16:44
*** arozumenko has quit IRC16:44
*** arozumenko has joined #openstack-dev16:44
markwashttx: good evening16:45
*** hemna has joined #openstack-dev16:45
*** BLZbubba has joined #openstack-dev16:46
*** mindpixeler has quit IRC16:47
ttxmarkwash: hi!16:48
*** doron_afk has quit IRC16:48
ttxhttps://launchpad.net/glance/+milestone/icehouse-216:48
ttxlooks good16:49
markwashcool16:49
*** mindpixel has joined #openstack-dev16:49
markwashI guess now is our weekly opportunity to highlight mordred16:49
markwashbut he's not even here!16:49
ttxhiding under that mtaylor guy I think16:50
markwashah16:50
ttxanything you want to discuss at meeting today ?16:50
markwashnothing that comes to mind16:50
ttxwe'll skip next 2 weeks of 1:1s & meetings fwiw16:51
markwashttx: okay sounds fine16:51
ttxok see you at meeting today !16:51
markwashlaters16:52
*** tkammer has quit IRC16:53
*** yaguang has quit IRC16:53
*** rongze_ has quit IRC16:53
*** mindpixel has quit IRC16:53
*** rongze has joined #openstack-dev16:53
*** adalbas has joined #openstack-dev16:54
jaypipesthomasem: arighty. ready when you are.16:54
*** SergeyLukjanov has joined #openstack-dev16:54
*** mkollaro1 has quit IRC16:55
ttxhub_cap: around?16:56
*** vijendar has quit IRC16:56
*** vijendar has joined #openstack-dev16:56
hub_capttx aye16:57
hub_caplets burn thru this :)16:57
ttxhttps://launchpad.net/trove/+milestone/icehouse-216:57
ttxlooks good16:57
ttxgood progress too16:57
hub_capyes some things are trickling in16:57
hub_capive added a new i3 bp in the last ~30 min16:58
hub_capive nuked all the essential bps down to high16:58
ttxyou might want to set assignees for all blueprints on https://blueprints.launchpad.net/trove/icehouse16:58
hub_caproger16:58
ttxnothing else, all looks good for the next two weeks16:59
*** rcleere has joined #openstack-dev16:59
*** afazekas has quit IRC16:59
*** aditirav has quit IRC16:59
ttx(we won't have 1:1s or cross-project meetings for the next 2 weeks)16:59
ttxhub_cap: anything you want to see discussed at the cross-project meeting later ?16:59
*** drewlander has joined #openstack-dev16:59
hub_capso we wont have it 2x?16:59
*** angdraug has joined #openstack-dev16:59
hub_capor skip one week?16:59
ttxhub_cap: yes. You fly solo16:59
ttx2x16:59
hub_caphehe cool17:00
hub_caphopefully my autopilot will work, like in airplane17:00
ttxno interest in tracking status early in milestones anyway17:00
hub_capsue17:00
hub_capsure17:00
ttx(once the roadmap is set)17:00
hub_capok well awesome! im feeling good, nothing to really mention at todays meeting17:00
*** simo is now known as simo_out17:01
hub_capi just hate bps ;)17:01
ttxhub_cap: any other question on milestoning, while I'm here ?17:01
*** pberis has joined #openstack-dev17:01
*** haomaiwang has quit IRC17:02
*** pberis has quit IRC17:02
*** mrodden has joined #openstack-dev17:02
*** haomaiwang has joined #openstack-dev17:02
*** evgenyf has quit IRC17:03
*** stevemar has quit IRC17:03
ttxhub_cap: ok, see you at meeting later17:03
*** romcheg has quit IRC17:03
hub_capcu ttx17:04
hub_capthx17:04
*** xjiujiu has joined #openstack-dev17:04
*** devoid has joined #openstack-dev17:05
*** devoid has left #openstack-dev17:05
*** garyk has joined #openstack-dev17:05
*** gordc has joined #openstack-dev17:05
*** kenperkins has quit IRC17:05
*** ayoung has quit IRC17:06
*** pdevine has joined #openstack-dev17:06
*** noorul has joined #openstack-dev17:06
*** DennyZhang has quit IRC17:07
*** Abhishek_ has joined #openstack-dev17:07
*** haomaiwang has quit IRC17:07
*** davidhadas has quit IRC17:09
*** reed has quit IRC17:09
*** kbringard has quit IRC17:09
*** teran_ has quit IRC17:10
*** pablosan has joined #openstack-dev17:11
*** sushil_ has quit IRC17:13
shardygiulivo: Hi17:13
*** flaper87 is now known as flaper87|afk17:13
giulivoshardy, I know you'd want to kill me now17:13
*** markmc has quit IRC17:13
giulivoI suspected that was going to happen, not only with you17:13
shardygiulivo: I'm just trying to understand what makes tempest special, in that you don't have to follow the same blueprint process as every other project?17:13
giulivothat probably *I* don't know the process17:14
shardygiulivo: Not a big deal, but we want to track getting the various heat tests into tempest, and BPs seem the best way to do that17:14
shardygiulivo: I can understand having etherpads for team task coordination, but IMHO they don't replace BPs17:15
*** pablosan has quit IRC17:15
shardyhow will you track (accurately) what you deliver over the release cycle?17:15
*** kbringard has joined #openstack-dev17:15
*** bswartz has joined #openstack-dev17:15
giulivoI understant , this was actually a quite big issue with tempest as the general opinion is that blueprints aren't appropriate for new tests17:15
*** saju_m has joined #openstack-dev17:16
giulivoI think the general idea is that we should at least try to use only _a single_ blueprint per component when tracking new tests17:16
*** e0ne has quit IRC17:16
giulivoblueprints in tempest also have to deal with improvements to the framework itself17:16
shardygiulivo: Hmm. OK, that is, uh, very different to the process I'm familiar with17:17
giulivobut that won't allow to track new tests per release17:17
shardygiulivo: Can you link the discussion where this was decided please?17:17
shardygiulivo: No, you won't really be able to track anything, as you can't tag a commit with a line in an etherpad17:18
*** sushils has joined #openstack-dev17:18
*** pablosan has joined #openstack-dev17:18
giulivoshardy, so for scenarios, we have a single blueprint (across components) and that is targeted to a release17:18
*** ayoung has joined #openstack-dev17:18
*** Shaan7 has quit IRC17:18
*** Shaan7 has joined #openstack-dev17:18
giulivofor the api tests, tracking per component get things better organized but doesn't allow for good tracking17:19
*** max_lobur is now known as max_lobur_afk17:19
*** stevemar has joined #openstack-dev17:19
shardygiulivo: So if you land 200 new scenario tests, accross all openstack projects, that's tracked via *one* BP?17:19
giulivoshardy, yes that is17:19
*** BLZbubba has quit IRC17:20
*** martyntaylor has joined #openstack-dev17:20
shardygiulivo: OK, well let it be noted, I think you're making a mistake, but at least we now know what is expected17:20
*** gyee has joined #openstack-dev17:20
shardygiulivo: Is there an openstack-dev thread communicating this new process?17:21
* shardy maybe missed it17:21
giulivoshardy, yes I'll post a few links17:21
giulivobut honestly, for the purpose of tracking new tests, a single blueprint (maybe per component), per release, is quite good17:21
*** ruhe has quit IRC17:21
*** dave_tucker has joined #openstack-dev17:21
giulivoI don't see why spreading them around in more and more blueprints would help anyway17:21
*** ffio has joined #openstack-dev17:21
*** urulama has joined #openstack-dev17:22
*** sushils has quit IRC17:22
*** ruhe has joined #openstack-dev17:22
giulivoshardy, so this was introduced here: http://lists.openstack.org/pipermail/openstack-dev/2013-December/021922.html17:22
*** viktors has left #openstack-dev17:23
*** sushils has joined #openstack-dev17:24
shardygiulivo: Blueprints allow sharing tasks, and tracking those tasks (automatically through commit tags)17:24
shardyNeither of those things can be done accurately via an etherpad17:24
*** nermina has quit IRC17:24
giulivoI hear you on that, but I still don't think multiple blueprints would help either17:25
*** kbringard1 has joined #openstack-dev17:25
*** saju_m has quit IRC17:25
*** glucas has joined #openstack-dev17:25
giulivofor scenarios (which easily are cross-component) a single blueprint per release seems feasible17:25
*** utlemming has quit IRC17:25
giulivofor the single components, what do you think about a single bp per release, per components?17:26
*** urulama has quit IRC17:26
*** kbringard has quit IRC17:27
*** ayoung has quit IRC17:27
*** mikeoutland has joined #openstack-dev17:27
giulivothat is mainly the direction I tried to take now with heat, where I considered this https://blueprints.launchpad.net/tempest/+spec/tempest-heat-integration the "master plan" for the icehouse release17:27
*** jswarren has joined #openstack-dev17:27
*** ayoung has joined #openstack-dev17:28
giulivoshardy, I see as we speak more bp for heat are getting in17:29
*** kbringard1 has quit IRC17:29
*** xjiujiu has quit IRC17:29
shardygiulivo: We have been raising BP's, which were going to be linked as dependencies to the heat-integration umbrella BP17:30
*** kbringard has joined #openstack-dev17:31
*** jruzicka has quit IRC17:31
shardythen we can divide the various tasks up, allocate them to different people, and track the progress via launchpad17:31
*** xjiujiu has joined #openstack-dev17:31
*** kenperkins has joined #openstack-dev17:31
*** exed has quit IRC17:31
shardygiulivo: Or we can juggle multiple bit-rotted etherpads and have everyone get in an uncoordinated mess17:31
*** kenperkins has quit IRC17:31
*** xarses has quit IRC17:32
shardygiulivo: If this is the direction tempest has agreed, fair enough, but the granularity you propose to track things at makes no sense to me17:32
*** andreaf has joined #openstack-dev17:32
shardyone BP should be something you can allocate to one person, so you have a point of contact for status, and you avoid duplicated effort17:33
giulivoso I think we definitely don't want to have a blueprint per test, despite that providing greatest granularity17:33
*** JordanP has quit IRC17:33
shardygiulivo: So you would propose we just track stuff in an etherpad, and divide the allocation of the various tests up that way?17:34
*** gothicmindfood has joined #openstack-dev17:34
*** s2r2 has quit IRC17:35
shardyI understand the overhead involved with the BP/bug process is hard to manage, but IMO it does basically work, so short-circuiting it like this seems weird and counter-productive17:35
*** exed has joined #openstack-dev17:36
giulivoas you noted, there has been an attempt to use bugs, but then we had duplicates17:36
*** martyntaylor has quit IRC17:37
*** Shaan7 has quit IRC17:37
*** ruhe has quit IRC17:37
giulivoTODO items in the blueprint seem an intermediate measure; having blueprints which document tests that should be added aren't really useful, there is a lot of tests that could be added17:38
*** s2r2 has joined #openstack-dev17:38
shardygiulivo: If every project stopped doing issue tracking because they had duplicate bugs, there would be chaos ;)17:39
shardygiulivo: raising a bp can also be used as a statement of intent, by a developer, to do some work17:39
*** rongze has quit IRC17:39
giulivoshardy, indeed, that is the good way to use bp, I agree17:40
*** rongze has joined #openstack-dev17:40
giulivoso bugs were instead just leftovers with comments about missing tests, frequently duplicated by "super" blueprints17:40
shardygiulivo: I agree that randomly raising blueprints for wishlist items you have no intention of doing isn't helpful, but at least on heat most of our BPs aren't like that17:40
shardygiulivo: So in this case, most of the heat tempest BPs are a statement of intent, where we have decided to have a push and get some better Heat testing into tempest17:41
*** d0ugal has quit IRC17:41
*** zoresvit has quit IRC17:41
*** MaxV has quit IRC17:41
*** mancdaz is now known as mancdaz_away17:42
shardygiulivo: It would be valuable to get early feedback on the variouys tests (ie if they will be accepted), but if you feel that is too much overhead, we'll track them ourselves and just post the patches17:42
*** exed has quit IRC17:42
*** dstanek has joined #openstack-dev17:42
*** mancdaz_away is now known as mancdaz17:42
shardyThat is the other benefit of BPs, details of what will be done, and discussion17:42
giulivoshardy, well I think this will turn useful if people contributing tests can use it17:42
*** zoresvit has joined #openstack-dev17:43
shardygiulivo: I am describing the process every openstack project uses, AFAIK17:43
*** arnaud has joined #openstack-dev17:43
*** arnaud__ has joined #openstack-dev17:43
*** Underbyte has joined #openstack-dev17:43
*** jcooley_ has joined #openstack-dev17:43
giulivoshardy, I got that but is that the case for "new tests"? we use that for new features in the framework or to enable support for new components17:43
*** hemna has quit IRC17:44
*** vkozhukalov has joined #openstack-dev17:44
shardygiulivo: I don't see why it can't be both - most of the code in the tempest tree is tests right?17:44
*** utlemming has joined #openstack-dev17:44
*** hemna has joined #openstack-dev17:44
*** atiwari has joined #openstack-dev17:45
giulivoshardy, sure it is so again, I found the intermediate solution of a single blueprint to fit well but, let me discuss that in the meeting so maybe we can come up with a stronger decision17:45
*** ygbo has quit IRC17:46
*** markwash has quit IRC17:46
*** JordanRinke has quit IRC17:46
*** Drankis has joined #openstack-dev17:47
*** Drankis has quit IRC17:47
*** Drankis has joined #openstack-dev17:47
*** drankis_ has joined #openstack-dev17:47
shardygiulivo: Ok, cool thanks17:47
*** SumitNaiksatam has quit IRC17:48
shardygiulivo: FWIW, my suggestion is to use BPs for new test development, but not to triage/approve those without an assignee17:48
*** reed has joined #openstack-dev17:49
*** zoresvit has quit IRC17:49
*** sarob has joined #openstack-dev17:49
giulivoshardy, agreed so the discussion would basically be about merging it in a single bp or not, correct?17:50
*** sarob has quit IRC17:51
shardygiulivo: Yes, I think it should be valid to allow folks to raise BPs for individual tests, then link them as dependencies to the "master plan" for a particular project17:51
*** ndipanov has quit IRC17:51
*** jcooley_ has quit IRC17:51
*** abramley has quit IRC17:51
*** sarob has joined #openstack-dev17:51
shardygiulivo: Not that everyone should use that process, of one giant BP works for them, but I think it's a valid and familiar workflow for many of us17:51
*** mancdaz is now known as mancdaz_away17:51
shardys/of/if17:51
*** jcooley_ has joined #openstack-dev17:51
*** eglynn has quit IRC17:52
*** danpb has quit IRC17:52
*** radix_ has joined #openstack-dev17:53
giulivothanks for pinging and taking some time to discuss it17:53
*** JordanRinke has joined #openstack-dev17:53
*** rongze has quit IRC17:53
*** rongze has joined #openstack-dev17:54
*** sahid has quit IRC17:54
*** d0ugal has joined #openstack-dev17:54
*** d0ugal has quit IRC17:54
*** d0ugal has joined #openstack-dev17:54
*** gothicmindfood has quit IRC17:54
*** d0ugal has quit IRC17:55
*** nermina has joined #openstack-dev17:55
*** markmcclain has joined #openstack-dev17:55
*** xjiujiu has quit IRC17:55
*** sarob has quit IRC17:55
*** tanisdl_ has joined #openstack-dev17:56
*** jcooley_ has quit IRC17:56
*** tanisdl has quit IRC17:56
*** tanisdl_ is now known as tanisdl17:56
*** nati_ueno has joined #openstack-dev17:56
*** derekh has quit IRC17:58
*** syed_armani has quit IRC17:58
*** safchain has quit IRC17:58
morganfainbergdstanek, looking at your comments, after meeting might discuss more-real-time than via gerrit17:59
*** dolphm_afk has joined #openstack-dev17:59
dstanekmorganfainberg: sounds good18:00
*** dolphm_afk is now known as dolphm18:00
*** rpodolyaka1 has joined #openstack-dev18:00
*** hajay_ has joined #openstack-dev18:00
*** xarses has joined #openstack-dev18:00
*** jecarey_ has quit IRC18:01
*** nati_uen_ has joined #openstack-dev18:02
*** jamielennox|away is now known as jamielennox18:03
*** amcrn has joined #openstack-dev18:03
*** nati_uen_ has quit IRC18:04
*** nati_uen_ has joined #openstack-dev18:04
*** shinylasers has joined #openstack-dev18:05
*** nati_uen_ has quit IRC18:05
*** ffio has quit IRC18:05
*** shinylasers has quit IRC18:05
*** nati_ueno has quit IRC18:05
*** nati_uen_ has joined #openstack-dev18:05
*** d0ugal has joined #openstack-dev18:06
*** shinylasers has joined #openstack-dev18:06
*** sushils has quit IRC18:06
*** shinylasers has quit IRC18:06
*** d0ugal has quit IRC18:06
*** d0ugal has joined #openstack-dev18:07
*** d0ugal has quit IRC18:07
*** jcooley_ has joined #openstack-dev18:08
*** d0ugal has joined #openstack-dev18:08
*** d0ugal has joined #openstack-dev18:08
*** d0ugal has quit IRC18:08
tellesnobregadolphm: is there a way that i can limit actions on the policy json by the domain, i tried domain_id=%(domain_id)s and i authenticated with a domain scoped token, but it doesnt work18:09
*** d0ugal has joined #openstack-dev18:10
*** d0ugal has quit IRC18:10
*** d0ugal has joined #openstack-dev18:10
*** d0ugal has quit IRC18:10
*** gothicmindfood has joined #openstack-dev18:11
jamielennoxtellesnobrega: have a look at the policy.v3cloudsample.json for some examples18:12
tellesnobregajamielennox: thanks18:12
jamielennoxyou will need to set a role as well, as all that will check on it's own is that there is a domain18:12
*** shinylasers has joined #openstack-dev18:12
*** markwash has joined #openstack-dev18:12
*** shinylasers has quit IRC18:13
*** davidhadas has joined #openstack-dev18:13
*** d0ugal has joined #openstack-dev18:13
*** d0ugal has joined #openstack-dev18:13
*** d0ugal has quit IRC18:13
*** jcooley_ has quit IRC18:13
jamielennoxayoung has a blog post recently with some fairly detailed examples, adam.younglogic.com and have a look back trhough the history18:13
*** shinylasers has joined #openstack-dev18:13
*** shinylasers has quit IRC18:13
ayoungtellesnobrega, http://adam.younglogic.com/2013/11/policy-enforcement-in-openstack/18:14
tellesnobregajamielennox: i have a role that i created and setted the domain for it18:14
tellesnobregaayoung: i've already used this post to guide through the first tests18:15
tellesnobregait worked nicely here, but my problem is about the domain, how to check if the user is owner of the domain on context to allow it to perform actions18:15
*** jkyle_ is now known as jkyle18:16
*** jkyle is now known as Guest7516918:16
rpodolyaka1dhellmann: ping18:17
dhellmannrpodolyaka1: in a meeting, email me?18:17
*** dhellmann is now known as dhellmann_18:17
rpodolyaka1dhellmann_: ack18:17
*** jtomasek has quit IRC18:17
*** rongze has quit IRC18:18
*** Guest75169 has quit IRC18:18
jamielennoxsdague: i'm consistently failing grenade with this error: http://logs.openstack.org/01/59601/10/check/check-grenade-dsvm/bd0d43b/logs/new/screen-s-proxy.txt.gz18:18
jamielennoxsdague: can you have a look and tell me if it's something you know about?18:19
*** d0ugal has joined #openstack-dev18:19
*** rfolco has quit IRC18:20
*** rfolco has joined #openstack-dev18:21
*** SumitNaiksatam has joined #openstack-dev18:21
*** pdevine has quit IRC18:22
*** athomas has quit IRC18:22
*** harlowja_away is now known as harlowja18:22
*** d0ugal has joined #openstack-dev18:22
*** d0ugal has quit IRC18:22
*** d0ugal has joined #openstack-dev18:22
sdake_giulivo tempest meeting is not here https://wiki.openstack.org/wiki/Meetings - do you know the times?18:23
giulivosdague, sure, i added the topic in the agenda18:24
*** d0ugal has joined #openstack-dev18:24
*** d0ugal has quit IRC18:24
giulivohttps://wiki.openstack.org/wiki/Meetings/QATeamMeeting18:24
giulivosdake, ^^ sorry18:24
*** mnaser has quit IRC18:24
*** davidhadas_ has joined #openstack-dev18:24
sdake_oh thanks - :)18:24
giulivosdake, it's referenced as QA team meeting not Tempest team meeting18:25
*** vipul is now known as vipul-away18:26
*** shinylasers has joined #openstack-dev18:26
*** shinylasers has quit IRC18:26
*** abramley has joined #openstack-dev18:26
*** d0ugal has joined #openstack-dev18:26
*** mnaser has joined #openstack-dev18:26
*** d0ugal has joined #openstack-dev18:27
*** d0ugal has quit IRC18:27
*** d0ugal has joined #openstack-dev18:27
sdake_giulivo reading scrollback, I think the issue is that we would prefer tests to be tracked in blueprints from a downstream perspective18:27
*** shinylasers has joined #openstack-dev18:27
*** d0ugal has joined #openstack-dev18:27
*** d0ugal has quit IRC18:27
*** d0ugal has joined #openstack-dev18:27
sdake_etherpads change, items get deleted or added, whether we like launchpad or not, we are stuck with it :)18:27
sdake_it creates a permanent record of changes, which is what downstreams want18:28
*** shinylasers has joined #openstack-dev18:28
*** davidhadas has quit IRC18:28
*** shinylasers has quit IRC18:28
*** shinylasers has joined #openstack-dev18:28
sdake_all openstack projects run using launchpad and blueprints - test = new feature = blueprint18:29
*** blamar has quit IRC18:29
*** shinylasers has quit IRC18:29
*** d0ugal has joined #openstack-dev18:29
sdake_while I'm certain the idea of using etherpads didn't evolve out of a vacuum, just trying to understand the rationale, because it doesn't fit with what I would have expected18:29
*** shinylasers has joined #openstack-dev18:29
*** shinylasers has quit IRC18:29
*** shinylasers has joined #openstack-dev18:30
*** shinylasers has quit IRC18:30
*** shinylasers has joined #openstack-dev18:31
*** shinylasers has quit IRC18:31
*** tdruiva_ has joined #openstack-dev18:32
*** shinylasers has joined #openstack-dev18:32
*** shinylasers has quit IRC18:32
*** MaxV has joined #openstack-dev18:33
*** shinylasers has joined #openstack-dev18:33
*** tdruiva_ has quit IRC18:35
*** arozumenko1 has joined #openstack-dev18:35
*** tdruiva has quit IRC18:35
*** d0ugal has joined #openstack-dev18:36
*** d0ugal has quit IRC18:36
*** d0ugal has joined #openstack-dev18:36
*** tdruiva has joined #openstack-dev18:36
giulivosdake, I think the etherpad should only cover the "assignments" issue18:36
*** eglynn has joined #openstack-dev18:36
*** vkozhukalov has quit IRC18:36
*** d0ugal has joined #openstack-dev18:36
*** arozumenko has quit IRC18:36
*** tan has joined #openstack-dev18:37
*** d0ugal has joined #openstack-dev18:37
*** d0ugal has quit IRC18:37
*** d0ugal has joined #openstack-dev18:37
sdake_giulivo I see you have added something for the 19th, i'll make sure to attend to add my viewpoint as a heat-core dev18:37
*** vkozhukalov has joined #openstack-dev18:37
*** ifarkas has joined #openstack-dev18:37
giulivosdake, indeed18:38
sdake_i gotta run dr appointment thanks!18:38
*** hartsocks has joined #openstack-dev18:38
*** Abhishek_ has quit IRC18:38
*** blamar has joined #openstack-dev18:39
*** d0ugal has joined #openstack-dev18:40
*** d0ugal has joined #openstack-dev18:40
*** d0ugal has quit IRC18:40
*** athomas has joined #openstack-dev18:40
*** alexpilotti has quit IRC18:42
*** jcoufal has joined #openstack-dev18:42
*** d0ugal has joined #openstack-dev18:42
*** d0ugal has quit IRC18:42
*** d0ugal has joined #openstack-dev18:42
*** jistr has joined #openstack-dev18:44
*** sarob has joined #openstack-dev18:44
*** jcooley_ has joined #openstack-dev18:44
*** jcooley_ has quit IRC18:44
*** jcooley_ has joined #openstack-dev18:45
*** d0ugal has joined #openstack-dev18:45
*** d0ugal has quit IRC18:45
*** d0ugal has joined #openstack-dev18:45
*** jcooley_ has quit IRC18:46
*** jcooley_ has joined #openstack-dev18:46
*** vipul-away is now known as vipul18:46
*** bcrochet has quit IRC18:47
*** d0ugal has joined #openstack-dev18:47
*** d0ugal has quit IRC18:47
*** d0ugal has joined #openstack-dev18:47
*** d0ugal has joined #openstack-dev18:48
*** d0ugal has joined #openstack-dev18:48
*** d0ugal has quit IRC18:48
*** garyk has quit IRC18:49
*** garyk has joined #openstack-dev18:49
*** kushal has quit IRC18:49
*** d0ugal has joined #openstack-dev18:50
*** Drankis has quit IRC18:50
*** johnthetubaguy1 has quit IRC18:50
*** jcooley_ has quit IRC18:50
*** d0ugal has quit IRC18:51
*** jcooley_ has joined #openstack-dev18:51
*** lucasagomes has quit IRC18:51
*** MaxV has quit IRC18:51
*** d0ugal has joined #openstack-dev18:52
*** MaxV has joined #openstack-dev18:52
*** mikeoutland has quit IRC18:52
*** johnthetubaguy has joined #openstack-dev18:53
*** prekarat has quit IRC18:53
*** MaxV has quit IRC18:53
*** nati_ueno has joined #openstack-dev18:53
*** d0ugal has quit IRC18:54
*** d0ugal has joined #openstack-dev18:54
*** bcrochet has joined #openstack-dev18:54
*** MaxV has joined #openstack-dev18:54
*** jcooley_ has quit IRC18:55
*** spzala has quit IRC18:56
*** Mandell has joined #openstack-dev18:56
*** nati_uen_ has quit IRC18:57
*** MaxV has quit IRC18:58
*** rushiagr has quit IRC18:59
*** Alexei_987 has quit IRC18:59
*** vipul is now known as vipul-away19:01
ayoungdolphm, Here's the proposal:19:01
ayoungIf the client is trying to do v3, and the url ends in v2.0, chop if off and do discovery19:02
*** fabiog has joined #openstack-dev19:02
ayoungWe can't do less than that19:02
fabiogmorganfainberg: ping19:02
*** jtomasek has joined #openstack-dev19:02
*** fabiog has quit IRC19:02
morganfainbergdstanek, ok, so in the refactor for the controller(s), which logic seemed to be missing frmo the delte_user / delete_group etc?  I was trying to limit change in logic in the same space i refactored where the logic occured19:03
dolphmatiwari: your example illustrates redirects, which means the client is involved; it's the same pattern as illustrated in the other two diagrams mentioned during the meeting19:03
marekdmorganfainberg: i agree with you and ECP. I don't see any value in having federation via SAML only with browsers.19:03
jamielennoxfabiog: have a link handy?19:03
morganfainbergdstanek, i'm happy to change the logic, but want to make sure we're headed in a good direction :)19:03
*** fabio_ has joined #openstack-dev19:03
*** fabio_ is now known as fabiog19:03
atiwaridolphm, we can avoid it for now as per summit it was not the focus for now19:03
*** thomasm_ has joined #openstack-dev19:03
morganfainbergfabiog, Let me know if you have any questions about my comment i just posted (during the meeting)19:03
dstanekmorganfainberg: the only thing that's different is that one has a try-except right?19:04
dolphmatiwari: yeah, that specifically example isn't part of "use case 1", right?19:04
ayoungthe other things I was suggesting, such as appending v3 on to the URL, while ugly, reflet the reality that we don't have a caching strategy in place, and so we can't remember the results of previous discovery19:04
ayoungSo I think they fall into "necessary performance hacks" but we can punt on them to start19:04
dolphmayoung: so, implement a caching strategy?19:04
morganfainbergdstanek, correct.  since deletes look up the ref and that would fail and fail the deletion19:04
atiwaridolphm, yes. let not discuss it19:04
*** jcooley_ has joined #openstack-dev19:04
morganfainbergdstanek, figured it was sane to just move on and not explode.19:04
*** vartom111119 has joined #openstack-dev19:05
ayoungdolphm, all of that is performance tune.19:05
ayoungso, yes19:05
ayoungbut we need to have the v3 api deal with getting a v2.0 url19:05
morganfainbergdstanek, and i didn't want to move the delete_token* and credential deletes to the manager, imo the manager shouldn't cross talk to other managers unless it's really needed19:05
*** salv-orlando has quit IRC19:05
morganfainbergdstanek, it seems that manager crossing is more of a "controller" business logic thing19:05
*** Drankis has joined #openstack-dev19:05
dstanekmorganfainberg: no what i was saying is that you that duplication in the controller itself now19:06
dstanekmorganfainberg: i agree that since deletes are idempotent that the try-except is a good thing - so why is it not in the delete_* methods?19:06
dstanekmorganfainberg: this if that's the case the code is exactly the same19:07
morganfainbergdstanek, oh i see, move the try/excepts down19:07
*** thomasem has quit IRC19:07
fabiogmorganfainberg, a standard object method can be registered n times19:07
*** Nikolay_St has joined #openstack-dev19:07
fabiogmorganfainberg, if we go this route we put the burden in the extension code19:07
fabiogwhich is fine with me19:07
morganfainbergfabiog, correct, but @classmethod can't reference (let's use a bad example, oauth consumers) oauth_api.delete_consumer19:07
morganfainbergfabiog, since that is a bound instance method.  and likely on a user delete you'd want to cleanup consumers19:08
fabiogmerganfainberg, not sure I am following you19:08
fabiogmerganfainberg, right19:08
dstanekmorganfainberg: if you moved it down then you can just call the delete_* methods from the for loop19:08
*** jcooley_ has quit IRC19:08
morganfainbergdstanek, ah. yes i agree, i think that is a massive change though (and likely affects tempest and a ton of tests that rely on delete returning an error if things don't exist)19:09
dstanekmorganfainberg: also i noticed that the logic in the "delete group" for loop is not the same as delete_group()19:09
morganfainbergdstanek, i'm happy to tackle that aspect separately19:09
morganfainbergdstanek, let me check what i changed there.19:09
*** nati_ueno has quit IRC19:10
*** danjared_ has quit IRC19:10
fabiogmerganfainberg, can't you call an instance of the Driver from there to take care of that?19:10
dstanekmorganfainberg: does that mean the having the change in _delete_domain_contents() may also break tempest?19:10
morganfainbergdstanek, ah, i think we catch that above since groups don't cross domains?19:10
morganfainbergdstanek, on line 60319:10
morganfainbergdstanek, if you think it is an issue i can add the users from a group to the "user_refs" (make it a set instead)19:11
*** zaitcev has joined #openstack-dev19:11
*** hajay_ has left #openstack-dev19:11
morganfainbergaround like 611, i don't want to loop through 3 user lists.  we already do 219:11
*** dvarga has quit IRC19:11
*** mikeoutland has joined #openstack-dev19:11
morganfainbergand the domain lookup logic in delete_group is superceeded by r['domain_id']19:12
morganfainbergdstanek, i think we're safe on that one, since we really didn't test broken deletes19:12
*** melwitt has joined #openstack-dev19:12
*** rongze has joined #openstack-dev19:13
*** nati_ueno has joined #openstack-dev19:13
shardyayoung: Hi19:13
ayoungshardy, wazzup19:13
*** Mandell has quit IRC19:13
morganfainbergfabiog, @classmethods are created (effectively) at definition time.  how do you call an instance of a driver from a non-instance-bound method, 'cls' doesn't have the reference.  i'm trying to make sure we aren't blueprinting issues into our examples here19:13
atiwariguys I need some blessing on https://review.openstack.org/#/c/61897, whenever have time.19:13
shardyayoung: Got a moment to follow up on the x509/oauth discussion for in-instance users?19:13
*** Mandell has joined #openstack-dev19:14
ayoungshardy, oauth?19:14
ayoungSure19:14
dstanekmorganfainberg: will that code on line 603 include all users of the groups being deleted?19:14
morganfainbergdstanek, if groups don't bridge domains, yes19:15
shardyayoung: I'm trying to figure out what the roadmap is as there seem to be several aspects missing for oauth (client support, signature generation/validation, auth middleware)19:15
morganfainbergdstanek, if they do, i think we have other issues19:15
ayoungshardy, I don't think you want oauth19:15
morganfainbergdstanek, and this whole bit of code should be scrapped.19:15
shardyayoung: re your x509 comment, is that some future thing, or is it ready now?19:15
morganfainbergdstanek, i don't see how a group could bridge an IdP (sorry not domain, IdP)19:15
*** dolphm has quit IRC19:16
shardyayoung: Ok, dolphm indicated the opposite, hence myself (and therve) have been trying to figure it out :)19:16
morganfainbergdstanek, (scrub "domain" in relation to group and replace with IdP where possible)19:16
*** herndon has quit IRC19:16
ayoungshardy, x509 can be used now, but it is not a general purpose solution.  It implieas a degree of infrastructure that the Heat team may not be able to count on being available19:16
*** dvarga has joined #openstack-dev19:16
ayoungyes, I know, but oauth, according to the spec and the implementation, is short term delegation19:16
shardyayoung: Ok, for now, I'm working on using a trust, to delegate to a "proxy user" who will create an ec2 keypair with a trust scoped token19:16
*** rushiagr has joined #openstack-dev19:16
shardythen the keypair can be used to authenticate, impersonating the user owning the heat stack, but with minimal roles19:17
shardyayoung: but some users don't want ec2tokens19:17
shardyso I'm trying to figure out he alternative19:17
ayoungshardy, the root problem, as I understand it, is that we have nothing in Keystone to represent the  entity to whom you need to delegate19:17
*** sarob has quit IRC19:17
shardyand I also don't really like the reliance on the proxy user19:17
ayoungits basically the same problem as KDS...we have not IdM for all of the undercloud19:18
*** rongze has quit IRC19:18
shardyayoung: right, so I'm creating a heat_proxy_user in a heat_proxy tenant, who has no roles19:18
ayoungso you need a long term login mechanism for that user.19:18
shardyjust so I can delegate to the proxy so I can leverage trusts to role-limit access19:18
ayoungDon't misue trusts to do that19:18
*** gyee has quit IRC19:18
shardyayoung: Well AFAICS there is no alternative?19:19
morganfainbergfabiog, i think we need put the burden on the extension code to "do the right thing" in registration etc.  if there is nothing to do (because a previous instance acted on the notification) it should be easy to skip.19:19
ayoungec2creds made the same mistake19:19
shardyayoung: the alternative is every user who creates a heat stack has to be admin19:19
morganfainbergfabiog, i'm fine with removing my -1, just wanted to make sure we thought this through before pushing it in19:19
shardybecause currently we create a new user to own every ec2 keypair we put in an instance19:19
ayoungno19:19
*** gothicmindfood has quit IRC19:19
ayoungthe alkternative is that the heat user gets multiple trusts set up19:20
ayoungand you need to do password sync19:20
*** herndon has joined #openstack-dev19:20
dstanekmorganfainberg: looks like the sql backend enforces a group in be within a domain so i think that filter is enough - is that a requirement of backends?19:20
ayoungI *think* yo uare trying to avoid giving too much power to one user19:20
ayoungwhich is a noble effort19:20
*** jcoufal-mob has joined #openstack-dev19:20
fabiogmorganfainberg, you have a valid point19:20
*** danjared has joined #openstack-dev19:20
shardyayoung: I'm trying to limit what the credentials we put in the (implicitly untrusted) instance can do19:20
shardyayoung: but still enable authentication with out API19:21
morganfainbergdstanek, with LDAP i can confirm it's the same, since LDAP is non-domain aware19:21
shardyayoung: normal (non admin) users must be able to use whatever method we provide, so trusts is a good starting point19:21
fabiogmorganfainberg, I am trying to make sure that the solution is robust enough to avoid bad practices and at the same time re-use the Drivers to put the data in sync19:21
morganfainbergdstanek, i think it is a fair-assessment that it is a requirement (though not hard-enforced anywhere but the backend)19:21
shardybut the reliance on ec2-keypairs is a problem19:21
*** jcoufal-mob has quit IRC19:22
morganfainbergfabiog, i totally understand, which is why i wanted to discuss it instead of -1 and let you figure it out :)19:22
ayoungshardy, you are asking me a hard problem.  I don't have an easy answer for you.19:22
shardyayoung: One observation is, if we made token expiry optional for trust scoped tokens, all our problems would be solved19:22
*** jcoufal-mob has joined #openstack-dev19:22
shardyayoung: Is that even a possibility?19:22
ayoungshardy, no19:22
morganfainbergfabiog, it warrants a think through vs a "nope, i don't like it"19:22
ayoungno no no noi no noi no no non negatory19:22
ayoungshardy, the question is "how do I delegate to an ephemeral user"19:23
morganfainbergayoung, +++ no non-expiring bearer tokens please19:23
shardyayoung: Well that is all we're doing, by proxy, by using other non-expiring credentials which can be used to obtain a token19:23
fabiogmorgainfainberg, do you think that introducing a singleton class that is not the controllers would be a better approach?19:23
*** urulama has joined #openstack-dev19:23
*** jcooley_ has joined #openstack-dev19:23
shardyonly it introduces a lot of pain because it's a non-core extension (ec2tokens) and doesn't use the standard auth_token middleware19:23
*** ruhe has joined #openstack-dev19:23
*** jcoufal has quit IRC19:23
morganfainbergfabiog, if the controllers were made singletons - it might be easier.19:24
shardyayoung: I agree, this is a hard problem, but it's existed since heat started, and I'm making a real effort to understand how to solve it19:24
ayoungshardy, tokens are authorization documents, not authentication.  I said X509 because it is the industry standard for that.  It still would require a user to be authenticated as, though, in order for the trust to work.  Oauth avoids some of that by using consuemrs instreadof users,  but so what19:24
morganfainbergfabiog, but i don't know if that is the best approach either.19:24
*** johnthetubaguy has quit IRC19:24
fabiogmorganfainberg, no I am talking about a new class, like notification handler19:24
fabiogwhich has the callbacks19:24
*** troytoman-away is now known as troytoman19:25
morganfainbergfabiog, oh so you'd ... map a callback instance to all "controllers" of a type?19:25
*** xqueralt has joined #openstack-dev19:25
ayoungshardy, I think the right answer is to havea heat domain, and each instance is a new user, and the heat manager should beable to create heat users that have no roles, to consume trusts.  These users would be authenticated via X509 if possibble, but symmetric shared secrets (authgened passwords) is the fallback for the trivial case19:25
morganfainbergcallback logic singleton that is?19:25
*** jcooley_ has quit IRC19:25
ayoungby "instance" I mean19:25
fabiogmorganfainberg, more of an extension.19:26
ayoungthe heat proxy user19:26
ayoungnot one for all users, but one per workflow19:26
ayoungwe call them users, but really they are nothing more than placeholder accounts19:26
shardyayoung: interesting, so that is essentially an extension to what I'm doing, where we replace the fixed "proxy user" with the per-instance user in the heat domain19:26
*** Mandell has quit IRC19:26
fabiogmorganfainberg, because if the extension registers several times there could be really nasty effects and it is going to be hard to debug19:26
morganfainbergfabiog, by using inheritance or a metaclass? or?19:26
ayoungused to minimize damage if one should get compromised19:26
*** MaxV has joined #openstack-dev19:26
*** yolanda has quit IRC19:26
shardyayoung: I like that idea, as although it still means the overhead of creating lots of users in keystone, they won't be visible to users in their domain19:27
*** urulama has quit IRC19:27
morganfainbergfabiog, remember the issue still occurs that the singleton needs to be aware of the instantiated objects (and the like)19:27
shardyayoung: I assume trust delegation/impersonation can work accross domains?19:27
ayoungshardy, yes.  POKI is better than symmetric here, and X509 is the best method to do PKI, but it works with lesser methods19:27
ayoungyes, trusts is cross domina19:27
ayoungdomain19:27
morganfainbergfabiog, or are you advocating a completely new class that gets all the dependancies added etc (@dependancy) that has logic to handle the callback?19:28
shardyayoung: This is very cool, thanks for working through this, what you suggest may work well for us :)19:28
*** rpodolyaka1 has left #openstack-dev19:28
morganfainbergfabiog, sorry i'm tracking a few conversations, so i need it spelled out somtimes :P19:28
fabiogmorganfainberg, yes, this is what I am advocating19:28
ayoungshardy, glad to hear it19:28
*** jasondotstar is now known as jclark_19:28
*** jcooley_ has joined #openstack-dev19:28
*** jclark_ is now known as jasondotstar19:28
shardyayoung: Can I write up what we've discussed in a wiki page, and ask you to review it please?19:29
ayoungshardy, yep19:29
morganfainbergfabiog, i like that approach better.19:29
*** sarob has joined #openstack-dev19:29
shardyayoung: Thanks, I'll ping you a link later!19:29
fabiogmorganfainberg, if there is a way of making that class a singleton and using the @dependency inject the Driver we should be good19:29
fabiogmorganfainberg, do you think that is feasible?19:29
ayoungfabiog, it is rare that you want a true singleton19:29
*** thomasem has joined #openstack-dev19:29
morganfainbergayoung, in this case, i think he does.19:29
ayoungwaht you want is a known named instance of a class, and the current dep injection does that19:30
ayoungmorganfainberg, I doubt it19:30
*** Mandell has joined #openstack-dev19:30
morganfainbergayoung, a single object that doesn't get re-instantiated (ever) to handle the callbacks on events for extenstion notifications19:30
*** harlowja is now known as harlowja_away19:30
*** marekd is now known as marekd|away19:30
ayoungmorganfainberg, one per extension?19:30
morganfainbergayoung, though it doesn't need to be a "singleton" in mechanics, just in use (duck-typed languages and all)19:30
stevebakerttx: ping?19:30
ttxstevebaker: hai!19:30
*** jcooley_ has quit IRC19:31
*** jcooley_ has joined #openstack-dev19:31
ttxstevebaker: https://launchpad.net/heat/+milestone/icehouse-219:31
*** romcheg has joined #openstack-dev19:31
morganfainbergfabiog, i think if you use something akin to the @dependancy.provides mechanism, that should be sufficient to avoid issues with multiple instantiations19:31
ttxstevebaker: only one to set priority for: https://blueprints.launchpad.net/heat/+spec/add-parameter-label-to-template19:31
ttxand 4 missing assignees19:32
ttxerr.. make that 519:32
morganfainbergayoung, yes, one per extension, since hte logic would be different per extension19:32
fabiogmorganfainberg, so I don't need a new class, I can just use that in the current controllers19:32
ttxstevebaker: made progress in finding assignees for them ?19:32
stevebakerttx: that is in discussion, it may be rejected http://ask-openstackux.rhcloud.com/question/119/should-heat-pass-parameter-labels-to-horizon/19:32
*** thomasm_ has quit IRC19:32
ttxstevebaker: ok, keep in undefined until you know19:33
morganfainbergfabiog, hm. i think you could do it with the @dependancy mechanism19:33
*** colinmcnamara has joined #openstack-dev19:33
stevebakerttx: I asked for volunteers, maybe one blueprint was assigned from that19:33
*** colinmcnamara has quit IRC19:33
morganfainbergfabiog, you likely don't need to involve the controllers at all19:34
ttxstevebaker: I think if nobody is signed up for them at his point you might consider removing from the milestone19:34
morganfainbergfabiog, if you used @dependancy.provides to call a "register_subscriptions" the manager could do the callback for youy19:34
stevebakerttx: agreed19:34
morganfainbergfabiog, the controller doesn't need to be involved at all.19:34
ttxstevebaker: or maybe drop them to "Low" prio and give it one more week19:34
*** eglynn has quit IRC19:35
ttxstevebaker: everything else, including progress, looks good to me19:35
stevebakerttx: I'll go through each one and make a call19:35
ttxstevebaker: we'll skip the next 2 1:1s and cross-project meetings19:35
*** e0ne has joined #openstack-dev19:35
ttx(on te 24 and 31)19:35
*** rushiagr has quit IRC19:36
morganfainbergfabiog, so you get the "<dependancy>_api" as the listener.  not a true singleton, but the registration code isn't called externally on subsequent instances. ( cc ayoung, no singleton needed)19:36
ttxstevebaker: do you have anything specific you want to see discussed at the meeting later ?19:36
stevebakerttx: actually I won't be back until Jan 619:36
ayoungmorganfainberg, yep, good enough19:36
*** markwash has quit IRC19:36
ttxstevebaker: awesome, enjoy19:36
dstanekmorganfainberg: i think i have to come back and look at that more - feels wrong to have a refactor add duplication19:37
fabiogmorganfainberg, let me see if I got it: I register methods that are in the ExampleManager, which are under the dependency.provider and I am done?19:37
stevebakerttx: I'll find out tomorrow if we skip 2 weeks of heat meetings, or just one. I'll let you know if there is a fill-in ptl to delegate to for the first week of jan19:37
morganfainbergdstanek, i know. it's actually reducing some duplication.19:37
ttxstevebaker: next meeting is on the 7th, so you should be back19:38
morganfainbergdstanek, it doesn't feel like it.  the credential_api code was icky so i pushed that code down and just called managers directly19:38
*** dave_tucker_ has joined #openstack-dev19:38
stevebakerttx: ok, cool19:39
morganfainbergdstanek, i have one more patchset in that chain but it's a doozy so i want to get these two done.  i can include further de-dup and idempotent-awesomeness at that point.  heck i think a chunk of that code cleaning out the domain can be removed as well since some bugs were fixed19:39
ttxstevebaker: see you at meeting in 80min19:39
dstanekmorganfainberg: i like how you moved the credentials methods out - i'm just struggling with the delete changes19:39
fabiogmorganfainberg, something like: core.ExampleManager.project_created_notification19:39
morganfainbergfabiog, well you'll want to do it in the section of the code that handles the dependancy and making sure it's instantiated19:40
*** utlemming has quit IRC19:40
morganfainbergbut yes19:40
*** utlemming has joined #openstack-dev19:40
stevebakerttx: ack19:40
*** sstent has quit IRC19:40
*** epim has joined #openstack-dev19:41
morganfainbergdstanek, if you think about it from the standpoint of removing instantiation of a controller to call delete, and calling the logic directly, it makes it a bit more palatable19:41
fabiogmorganfainberg, ok. will do the changes later today. Thanks19:41
*** ayoung is now known as ayoung_xc-ski19:41
*** rollietikes has quit IRC19:41
*** colinmcnamara has joined #openstack-dev19:41
*** arozumenko1 has quit IRC19:42
morganfainbergdstanek, it was doing a pretty heavy process to de-dupe code.19:42
*** sushils has joined #openstack-dev19:42
morganfainbergdstanek, let me know what you decide so i can work on either correcting it or slating more cleanup in the chain :)19:44
dstanekmorganfainberg: in your opinion where does that logic belong?19:44
*** dprince has quit IRC19:44
*** CaptTofu has quit IRC19:45
morganfainbergdstanek, in my opinion controllers shouldn't instantiate eachother for logic.  it should be in the manager apis19:45
*** dprince has joined #openstack-dev19:45
morganfainbergdstanek, this is an odd case because domain cleanup is ... odd19:45
*** CaptTofu has joined #openstack-dev19:46
dstanekmorganfainberg: do the managers typically call other managers?19:46
morganfainbergdstanek, no.19:46
morganfainbergdstanek, well... in a couple cases yes19:47
*** nermina has quit IRC19:47
therveshardy, I'm very interested in that wiki page as well :)19:47
morganfainberge.g. token, token_provider19:47
*** dave_tucker_ has quit IRC19:48
morganfainbergand assignment -> identity19:48
morganfainbergi guess we could push this down to the identity api19:48
morganfainberg(the delete credentials part)19:48
*** mikeoutland has quit IRC19:48
morganfainbergand we, in theory, could push the delete_tokens_for* down to the token manager19:48
*** yassine has quit IRC19:49
morganfainbergayoung_xc-ski, bknudson, your opinion on managers calling other manager logic?  Should that be more of a controller thing?  (e.g. delete_credentials_for_user called from a controller or from identity_api manager on user_delete)19:50
*** jimjiang has quit IRC19:50
morganfainbergdstanek, ^19:50
morganfainbergpersonally, i think managers should have as little cross communication as possible.19:50
*** jimjiang has joined #openstack-dev19:51
morganfainbergit should rely on the "business logic" to pull that data together, i.e. controllers19:51
*** jcooley_ has quit IRC19:51
morganfainbergotherwise it seems silly to have controllers and manager layers.19:51
dstanekmorganfainberg: that mean that you'd be back to having controllers use other controller right?19:51
*** jcooley_ has joined #openstack-dev19:51
*** vipul-away is now known as vipul19:51
bknudsonmorganfainberg: manager makes more sense than controller19:51
*** jcoufal-mob has quit IRC19:52
bknudsoncontroller should just be taking the request and converting it to call to manager19:52
*** vipul-away has joined #openstack-dev19:52
*** jtomasek has quit IRC19:53
*** atiwari has quit IRC19:53
morganfainbergdstanek, if we were to de-dupe that code completely, yes back to controlellers instantiating and calling controllers19:53
dstanekbknudson: this aligns with my understanding that the manager layer is the same as a service layer in other architectures19:53
bknudsoncall it the service layer if you like, that's what I think it's supposed to be.19:54
*** bdpayne has quit IRC19:54
morganfainbergbknudson,dstanek, maybe my cognitive dissonance is the assignment vs idenity sides19:54
morganfainbergperhaps credential falls more to identity side than otherwise.19:54
dstanekmorganfainberg: or that logic of "when a user is deleted their credentials are deleted" can be pushed to the manager in one place19:54
morganfainbergsimilar to the delete_tokens_for<thing>19:55
bknudsonmorganfainberg: thing with identity is you apparently won't be able to resolve users with federation (I think)19:55
*** epim has quit IRC19:55
bknudsonyou won't be able to say "get me the user for this id"19:56
morganfainbergbknudson, actually i was thinking one step further19:56
*** jimjiang has quit IRC19:56
*** jcooley_ has quit IRC19:56
morganfainbergbknudson, what if identity (keystone) was made into a federated source, same limitations as other idps19:56
morganfainberg(heck even separate process)19:56
*** neoXsys has quit IRC19:56
morganfainbergperhaps, the right answer is to make a "clean_up_for_user" "cleanup_for_group" type method19:57
*** yolanda has joined #openstack-dev19:57
morganfainbergon the manager that can be called with just the relevant ids19:57
morganfainbergdoesn't do any checking19:57
bknudsonmorganfainberg: this is in assignments?19:57
*** jimjiang has joined #openstack-dev19:57
*** pberis has joined #openstack-dev19:58
*** nermina has joined #openstack-dev19:58
morganfainbergbknudson, the code being discussed is domainv3 controller and the _delete_domain_contents method19:58
bknudson(irc messages seem to be coming in slowly for me)19:58
morganfainbergbknudson, same. getting bursty/delays19:58
morganfainbergbknudson, i think we might be headed for a netsplit19:58
*** jcooley_ has joined #openstack-dev19:59
bknudsonmorganfainberg: is there a domain manager?19:59
*** MaxV has quit IRC19:59
morganfainbergbknudson, no, that is part of assignment19:59
*** dhellmann_ is now known as dhellmann19:59
dstanekbknudson: we were talking about https://review.openstack.org/#/c/62197/5/keystone/identity/controllers.py19:59
*** Alexei_987 has joined #openstack-dev19:59
*** colinmcnamara has quit IRC19:59
morganfainbergbknudson, ^19:59
*** MaxV has joined #openstack-dev20:00
morganfainbergactually... i think i have a solution.20:00
*** novas0x2a|laptop has joined #openstack-dev20:00
bknudsonmorganfainberg: so if I had to guess what domainv3._delete_domain_contents should do is it should tell the identity manager to delete and it should tell the assignment manager to delete20:00
*** jcooley_ has quit IRC20:00
morganfainbergbknudson, that was what we are currently doing.  it just has some duplicated code added in because the groupv3 and userv3 controllers do similar things20:01
*** d0ugal has quit IRC20:01
morganfainbergbknudson, so you see sem-duplicated code in the different controlelrs20:01
morganfainbergbknudson, previously it would instantiate the controller and pass the request into that controller to do the work.20:02
morganfainbergwhich... seems broken.20:02
morganfainbergalso makes it impossible to separate assignment controllers from identity controllers20:02
*** jimjiang has quit IRC20:03
*** d0ugal has joined #openstack-dev20:03
*** d0ugal has quit IRC20:03
*** d0ugal has joined #openstack-dev20:03
*** d0ugal has quit IRC20:03
bknudsonmorganfainberg: thanks for cleaning this up!20:03
*** d0ugal has joined #openstack-dev20:03
*** d0ugal has quit IRC20:03
*** d0ugal has joined #openstack-dev20:03
*** MaxV has quit IRC20:04
morganfainbergbknudson, i am trying to make identity and assignment as split as possible so we can support federation and the like without as much mess.  similarly moving controllers and routers around to make things friendlier.20:04
bknudsonmorganfainberg: "project_cntl = ProjectV3()" -- WTFLOL20:04
morganfainbergbknudson, the next patchset after the suffle will be to complete the per-domain-identity patch that didn't make it into havana20:04
*** jtomasek has joined #openstack-dev20:05
*** ifarkas has quit IRC20:05
morganfainbergbknudson, i know.  right?20:05
*** d0ugal has joined #openstack-dev20:05
*** ArxCruz has quit IRC20:06
bknudsonmorganfainberg: this is going to be a great cleanup20:06
morganfainbergbknudson, just don't hate me too much for the next patchset in the chain...and the use of metaclasses20:06
*** radez_g0n3 is now known as radez20:07
bknudsonmorganfainberg: seems like keystone shouldn't be this complicated.20:07
bknudsonreally, it doesn't do that much20:07
morganfainbergbknudson, i know someone who would agree with you20:07
morganfainbergbknudson, i am working on the cleanup slowly.20:07
morganfainbergbknudson, and it is getting there.20:07
morganfainbergbknudson, but there is a lot of cleanup (also the V2 api disappearing will help a lot)20:08
bknudsondoing operations like deleting all the projects or all the users in a domain is not scalable anyways20:08
morganfainbergbknudson, i totally agree with you20:08
morganfainbergbknudson, as far as i am concerned, domains have 2 modes "enabled and disabled" never deleted20:09
morganfainbergwhcih solves this "cleanup" issue20:09
*** jimjiang has joined #openstack-dev20:09
dstanekmorganfainberg: bknudson: are we really getting all of the users from the backend and then iterating over them to filter?20:10
*** mdomsch has joined #openstack-dev20:10
morganfainbergbut that is a much further reaching argument.  and i am aiming for the "fix things one item at a time" instead of "here is a massive change, deal with it"20:10
morganfainbergdstanek, yes.20:10
*** heckj has joined #openstack-dev20:10
morganfainbergdstanek, which is a bad assumption that you can do that i hope to correct in this dev cycle20:10
*** neoXsys has joined #openstack-dev20:10
bknudsonwe should require domain to be disabled before delete it20:10
*** heckj has quit IRC20:10
morganfainbergbknudson, already is the case20:10
bknudsondstanek: user_refs = self.identity_api.list_users()20:11
morganfainbergbknudson, can't delete a domain that is not disabled afaict20:11
*** heckj has joined #openstack-dev20:11
bknudsonmorganfainberg: great!20:11
*** vkozhukalov has quit IRC20:11
bknudsondstanek: actually does list_users multiple times...20:11
dstanekbknudson: yes :-(20:11
morganfainbergi shall be "fixing" that in more changes down the line.20:12
morganfainbergi hope20:12
bknudsonand it's not just the users for the domain either, it's all users in all domains.20:12
morganfainbergbknudson, sort-of.20:13
morganfainbergwell for the "primary" idp20:13
morganfainbergwould miss all secondary idps.20:13
dstanekbknudson: right, that has got to hurt on big installations20:13
morganfainbergbknudson, but the per-domain-identity stuff is only partially working as is20:14
*** harlowja_away is now known as harlowja20:14
morganfainbergbknudson, http://git.openstack.org/cgit/openstack/keystone/tree/keystone/identity/controllers.py#n640 enabled domains can't be deleted20:14
bknudsonmaybe what's missing is a "service" layer between the controllers and managers20:14
morganfainbergbknudson, perhaps.  but the controllers already _mostly_ provide that.20:15
morganfainbergthey have the dependancies etc.20:15
dstanekbknudson: isn't that what the manager layer is responsible for?20:15
*** denis_makogon_ has joined #openstack-dev20:16
morganfainbergdstanek, it's split between controllers and managers20:16
*** sgordon has joined #openstack-dev20:16
morganfainbergbasically, i think we should make a determination that it's either a manager purview or a controller purview20:16
dstanekmorganfainberg: imo the controllers shouldn't have any real logic beyond web related stuff20:16
dsantos_hi, I'm trying to get users by project using keystone v3. I saw in the api-ref that I should do a GET to v3/projects/​{project_id}​/users but I got a 404. Could someone help me?20:16
*** dolphm has joined #openstack-dev20:17
*** Drankis has quit IRC20:17
bknudsondstanek: right, but look at https://review.openstack.org/#/c/62197/5/keystone/identity/controllers.py _delete_domain_contents20:17
bknudsonit's talking to identity and tokens for example20:17
*** alexpilotti has joined #openstack-dev20:17
morganfainbergi am not convinced we need an extra layer to do cross-manager talking.20:18
bknudsonthe controllers are doing way too much20:18
*** heckj has left #openstack-dev20:18
morganfainbergbknudson, dstanek , its a tough situation because of the direction things are headed with federation etc20:19
*** vipul-away is now known as vipul20:19
bknudsonI agree with dstanek -- assuming he thinks the controllers should just be taking the request and forwarding it to a service layer20:19
bknudsonservice layer can talk to the managers20:19
*** aelkikhia has joined #openstack-dev20:19
*** markmc has joined #openstack-dev20:19
*** denis_makogon_ is now known as denis_makogon20:19
*** aelkikhia has quit IRC20:19
morganfainbergbknudson, so should @protect still occur at the controller?20:19
dstanekbknudson: yes, that's it; i was saying earlier that we may want to push some of that logic into the managers instead of duplicating it in the controller20:20
*** mtaylor is now known as mordred20:20
morganfainbergso what we're talking about here is making what "most" of the controllers are now a service layer, and adding a "request handler" above it20:20
morganfainberg?20:21
morganfainbergand rename current "controlelrs" to service layer and new request handler the new controller layer?20:21
*** dolphm has quit IRC20:21
* morganfainberg thinks this wont be doable in Icehouse.20:21
bknudsonI just don't think that the managers are the right place for it since they're independent.20:22
bknudsonmorganfainberg: yes, that's essentially it.20:22
bknudsonI see it more as pushing what controllers are doing now into a service layer.20:22
morganfainbergstrictly from a volume of change perspective20:22
morganfainberghrm. actually20:22
dstanekin smaller steps i think pushing controller logic into the manager (which right now i see as that services layer)20:22
bknudsonit's a refactoring so would give us something to do for m3.20:22
*** Drankis has joined #openstack-dev20:22
morganfainbergdstanek, i don't want to push logic down to the managers just to pull it back up20:23
morganfainbergdstanek, that is "make work"20:23
dstanekmorganfainberg: where would you pull it up to?20:23
bknudsonfor some reason our v3 controllers are subclasses of v2 controllers now, aren't they?20:23
bknudsonso they can share code.20:24
morganfainbergbknudson, yes =/20:24
dstanekbknudson: yes20:24
morganfainbergok, i think i can do this in a quick smallish refactor20:24
*** ayoung_xc-ski is now known as ayoung20:24
morganfainbergthat just sets the stage for shuffling the code up/down where appropriate20:24
dstanekmorganfainberg: cool20:25
*** johnthetubaguy has joined #openstack-dev20:25
ayoungmorganfainberg, sorry I'm late to the party.  I think that Managers will become the real business logic, not the controllers.  Controllers are for talkoing to the outside world, but internal call go manager to manager, not controller to controller20:25
*** jkyle has joined #openstack-dev20:25
ayoungwhich, as I read up, is about where you guys landed20:26
morganfainbergayoung, i am convinced we need another "service layer"20:26
ayoungnope20:26
ayoungmanager is biz logic20:26
morganfainbergayoung, managers are pivot points for drivers20:26
ayoungcontroller is binding to the outside world20:26
ayoungbut not just20:26
jkyleis there a call sequence diagram for nova volume-attach operations? Like how it's passed around, who consumes what from whom, and at which stage?20:26
morganfainbergayoung, i think we're lacking a clear definition here though20:27
*** eglynn has joined #openstack-dev20:27
morganfainbergayoung, there are cases where the manager "layer" is insufficient20:27
ayoungmorganfainberg, let the complexity emerge...yes, there might be the occasional time it is called for, we will see.20:27
morganfainbergayoung, notably the whole "identity" aspect where identity is losing a lot of the reliability with the federation movement20:27
ayoungmorganfainberg, you can always have a manager call not reflected in the underlying driver20:28
morganfainbergreliability of data being avaialble directly20:28
morganfainbergfair enough, i think we're going to see the opposite problem we're seeing now as we move there.20:28
*** epim has joined #openstack-dev20:31
*** vipul is now known as vipul-away20:31
bknudsonayoung: we already have operations too complicated for manager - see https://review.openstack.org/#/c/62197/5/keystone/identity/controllers.py20:32
bknudson_delete_domain_contents20:32
bknudsonit operates on multiple managers -- so which manager would have the logic?20:32
*** rfolco has quit IRC20:33
*** johnthetubaguy has quit IRC20:33
*** jecarey has joined #openstack-dev20:33
*** mrunge has joined #openstack-dev20:33
*** SumitNaiksatam has quit IRC20:34
bknudsonI see the "service" layer as sitting under controllers and above managers... it would have operations like "domain_service.delete()" that the controllers would call rather than "assignment_api.delete_domain()"20:34
ayoungbknudson, I doubt it.20:35
*** markwash has joined #openstack-dev20:35
morganfainbergayoung, so would _delete_domain_contents just go on the assignment manager?20:35
ayoungmorganfainberg, yes, and we get users out of domains20:35
morganfainbergayoung, working on it.20:35
ayoungmorganfainberg, you were the one that realized it was a mistake to put them there.20:36
morganfainbergayoung, trying to get the cleanup done so it's easy to remove them.20:36
*** richardboswell has joined #openstack-dev20:36
ayoungdomains are top level assignement groupings...20:36
morganfainbergayoung, which is where this patchset and the subsequent ones are headed20:36
ayoungso assignments should own them20:36
ayoungyep20:36
morganfainbergi can push this logic down in this cleanup patchset or i can do it later on.  both will accomplish the same thing.  i'm trying to keep the changesets as digestable as possible20:37
ayoungSo really, the problem is that we have a tangled up model right now, not that we have something that the current manager abstraction can't solve.20:37
ayoungmorganfainberg, you are doing things right AFAICT20:37
* morganfainberg has a ton of work to do this cycle.20:38
*** eglynn has quit IRC20:38
bknudsonthis is why I think it's too early to promise stability of manager interfaces.20:39
*** gyee has joined #openstack-dev20:39
morganfainbergbknudson, thankfully the public interfaces of the managers isn't too bad to maintain most of the issue(s) we're seeing are internal-workings.20:40
morganfainbergbknudson, i am also not oposed to raising an exception saying "this moved, no you can't has it anymore" for a cycle.20:40
morganfainbergif something can't be maintained.20:40
morganfainbergit's not about 100% maintaining interfaces, it's also about communicating what changed to out-of-tree developers20:41
bknudsonI don't think we should mix the responsibility of "talking to different backends" (sql vs kvs) with "business logic"20:42
*** epim has quit IRC20:42
*** vipul-away is now known as vipul20:43
morganfainbergbknudson, the biggest argument i could make for a service layer is it would allow caching to really be much clearer at the pivot point vs somewhere in the middle of business logic.20:43
*** pixelb has quit IRC20:44
morganfainbergand it would make cache invalidations easier (biggest argument for the -complexity-of-code- standpoint)20:44
bknudsonmorganfainberg: the pivot point for caching being the managers?20:44
morganfainbergbknudson, yes.20:44
morganfainbergbknudson, put cache/invalidation logic in at that point.20:45
morganfainbergright now it's a mix20:45
morganfainbergsame as the rest of the manager code.20:45
*** nelsnelson has quit IRC20:45
morganfainbergunless we are also looking to cache the results of business logic (which we ... usually don't)20:45
*** nelsnelson has joined #openstack-dev20:46
bknudsonhaving a sane and obvious place to put caching logic is a good reason for a refactoring20:46
dstanekmorganfainberg: if you split the business logic out of the managers would the managers end up just being pass thrus to the backend?20:46
morganfainbergdstanek, pivot + caching20:46
morganfainbergdstanek, if i were to do that split20:46
morganfainbergdstanek, if it didn't have caching logic, it would just pass through20:46
morganfainbergbknudson, that would also make it much easier to avoid the kwargs issue20:47
dstanekmorganfainberg: interesting...i don't know enough about the current arch to have an opinion yet, but i do like what you are saying20:47
*** sarob_ has joined #openstack-dev20:47
morganfainbergno kwargs on the managers, means caching is always possible service layer might need optional args20:48
morganfainbergbut it would be a lot less call <method> that calls _<method> just to avoid kwargs20:48
morganfainbergbecause memoization and invalidations with kwargs becomes a nightmare20:48
*** epim has joined #openstack-dev20:49
*** drewlander has quit IRC20:49
bknudsonI think we're always going to have kwargs as long as we support "extra" fields?20:49
morganfainbergi _think_ it would be doable without a lot of making merges a nightmare.20:49
*** sarob has quit IRC20:49
bknudson(or the equivalent of kwargs)20:50
morganfainbergbknudson, and the service layer makes that easy to handle. since it does that work and passes fixed areguments to the backend20:50
morganfainbergbknudson, s/makes/wouldmake20:50
*** itooon has quit IRC20:50
morganfainbergbknudson, it's just about placing the optional args in a place that it wont affect the in-line caching20:51
morganfainbergbknudson, but this can still all be technically solved w/o the need of a service layer for now20:52
morganfainbergso.20:52
morganfainbergback to the original discussion20:52
*** vipul is now known as vipul-away20:52
*** sarob_ has quit IRC20:52
morganfainberghandling the refactors and direction20:52
ayoungsince dolph is so set against hacking the v2.0 off the urls...we need a new endpoint for Keystone20:52
morganfainbergayoung, i vote bbq_identity20:53
*** itooon has joined #openstack-dev20:53
ayoungjquery?  http://benalman.com/projects/jquery-bbq-plugin/20:53
morganfainbergbknudson, dstanek, how much refactoring now vs say post m220:53
morganfainbergi'm trying to clean things up that affect config and the like now... for obvious reasons20:54
*** eglynn has joined #openstack-dev20:54
morganfainbergayoung, not what i was going for but sure20:54
morganfainbergand do i push that logic down to the assignment manager so i can move on with the cleanup needed to get users out of domains20:55
morganfainbergor is it fine as is for this patchset and more logic shuffle will occur in subsequent ones20:56
*** dolphm has joined #openstack-dev20:56
*** jtomasek has quit IRC20:57
bknudsonmorganfainberg: as long as your cleaning things up then we'll be getting closer to where we want to be.20:58
ayoungbknudson, ++20:58
morganfainbergbknudson, and there is lots of cleanup planned.20:58
bknudsonlike removing creating controller WTFs.20:58
*** Drankis has quit IRC20:59
morganfainbergunfortunately, there is some user-facing terms we can't "get rid of" for a while20:59
*** jtomasek has joined #openstack-dev20:59
morganfainbergbut that will come with time.20:59
morganfainbergbknudson, ayoung, dstanek, ok i'm going to ask we leave that review as is, and i'll continue with cleanups and get that logic pushed down into the manager down the line.21:00
morganfainbergi apologize for the slight duplication of code, it is only temporary though21:00
morganfainbergand we can discuss splitting pivot/caaching down away from biz logic when we get towards m321:01
morganfainbergsicne i think that change will make landing things like federation much harder21:01
dstanekmorganfainberg: that works for me...i'll change my vote21:01
*** epim has quit IRC21:02
morganfainbergdstanek, bknudson, ayoung , btw, good convo here on this topic. feel like we're making progress.21:02
*** jistr has quit IRC21:02
*** markvoelker1 has joined #openstack-dev21:02
dstanekbknudson: thoughts on my comment on https://review.openstack.org/#/c/58311/ ?21:03
ayoungdolphm, if you nix the URL parsing, we need new endpoints21:03
ayoungspecificallyt, we need ones that will allow discoverability to work, while leaving the old broken ones in place21:03
*** d0ugal has quit IRC21:03
*** d0ugal has joined #openstack-dev21:04
*** radsy has joined #openstack-dev21:04
fabiogmorganfainberg, just pushed a new patch with your required changes, please have a look21:04
*** etoews1 has joined #openstack-dev21:04
*** d0ugal has quit IRC21:04
*** d0ugal has joined #openstack-dev21:04
*** jasdeepH has joined #openstack-dev21:04
dstanekayoung: do you have a link to the gist (or whatever) we were discussing yesterday in regards to the API versioning21:04
ayounghttps://blueprints.launchpad.net/python-keystoneclient/+spec/endpoint-versioning dstanek21:05
*** mdomsch has quit IRC21:05
bknudsondstanek: I mentioned in patch set 2 that I didn't think this was the right fix - https://review.openstack.org/#/c/58311/2/keystone/tests/fixtures/cache.py21:05
*** jasdeepH has quit IRC21:05
bknudsonit's fixing the symptom and not the problem.21:05
*** samuelbercovici has joined #openstack-dev21:05
etoews1dtroyer_zz: yt?21:06
*** sandywalsh_ has quit IRC21:06
*** samuelbercovici has quit IRC21:06
*** topol has quit IRC21:06
bknudsonayoung: the identity spec says what the version strings are, so while parsing the url is not ideal, it should work.21:06
ayoungbknudson, its a hack, I admit it.  But its like a hack you use to get through a dense jungle vine...just don't hack your own foot21:07
*** pberis has quit IRC21:07
dstanekbknudson: did your load_backends patch ever merge?21:07
*** fabiog has quit IRC21:07
*** dims has quit IRC21:08
bknudsondstanek: do any of my patches ever merge??21:08
dstanekbknudson: that code isn't about fixing the symtom at all it's about moving setup/teardown into a fixture21:09
*** dims has joined #openstack-dev21:09
dstanekbknudson: i think you are right about the change that needs to happen, but that's another patch for another day21:09
*** glenng has quit IRC21:10
*** yamahata has joined #openstack-dev21:10
dstanekbknudson: i'm going to see if i can use that as a way to setup the cache; it provides a great seam for initialization code21:10
*** eglynn has quit IRC21:10
bknudsondstanek: but it also moves "del cache.REGION.backend" from teardown to setUp21:10
bknudsondstanek: https://review.openstack.org/#/c/58311/4/keystone/tests/core.py does "del cache.REGION.backend" in tearDown21:11
*** jimjiang has quit IRC21:11
dstanekbknudson: i can introduce a patch that moves it first, but it wouldn't change the content of my patch21:11
bknudsondstanek: actually, the load_backends change did merge.21:11
dstanekbknudson: fixtures will typically put teardown things in the setup; that's the pattern on how they work21:12
bknudsondstanek: the patch that moves it would be fixing the symptom and not the problem.21:12
*** jimjiang has joined #openstack-dev21:12
*** vipul-away is now known as vipul21:12
dstanekbknudson: https://pypi.python.org/pypi/fixtures#creating-fixtures21:13
dstanekbknudson: i'm taking the exact same logic that already exists and moving it into a fixture21:13
bknudsondstanek: don't you do addCleanup to do cleanup stuff?21:14
ayoungbknudson, it is extra stupid for us, cuz keystoneclient already knows the correct auth_url to use to get the token.  We don';t even need the service catalog21:15
bknudsonthere's an example on that page: self.addCleanup(delattr, self, 'frobnozzle')21:15
*** sgordon has quit IRC21:16
dstanekbknudson: ah i see...if i remove the two lines that make the tests work would that change your mind?21:16
bknudsondstanek: yes21:17
*** pberis has joined #openstack-dev21:17
bknudsondstanek: well, you'd remove the two lines and replace it with self.addCleanup()21:17
*** sandywalsh_ has joined #openstack-dev21:17
*** jimjiang has quit IRC21:17
dstanekbknudson: so that mean that the tests would still be broken21:18
*** jimjiang has joined #openstack-dev21:18
bknudsondstanek: right, this change is a refactoring and not a fix21:19
dstanekbknudson: part of setting up the test is making sure that the cache is in the correct state to begin the test - that's all that does21:19
dstanekbknudson: i'll break it up into 2 commits21:20
*** nati_ueno has quit IRC21:20
*** d0ugal has quit IRC21:20
bknudsondstanek: how was the cache in the correct state before?21:20
dstanekbknudson: before my patch?21:21
bknudsondstanek: yes, as the code is now... the cache isn't in the correct state so how do the tests pass?21:21
*** tdruiva_ has joined #openstack-dev21:22
dstanekbknudson: they pass on accident when run as a part of the full test suite; they fail individually; https://bugs.launchpad.net/keystone/+bug/125130021:22
uvirtbotLaunchpad bug 1251300 in keystone "test_cache_layer_*_crud depend on test execution order" [Low,In progress]21:22
*** jimjiang has quit IRC21:23
dstaneka happy accident, but still and accident21:23
morganfainbergbknudson, dstanek , the first test can't use caching basically21:23
morganfainbergdstanek's fix solves that21:23
*** e0ne has quit IRC21:23
*** jimjiang has joined #openstack-dev21:23
morganfainbergit's a silly race i didn't account for in the testing suite21:23
*** urulama has joined #openstack-dev21:24
*** d0ugal has joined #openstack-dev21:24
*** d0ugal has joined #openstack-dev21:24
morganfainbergrace-like condition21:24
*** d0ugal has quit IRC21:24
morganfainbergor uhm sometrhing21:24
*** yolanda has quit IRC21:24
dstaneksomething in the test suite configures the cache before those tests run21:24
bknudsonI think the problem is that we've got "stuff" happening at import time.21:24
dstanekwhen you run them in isolation that's not happening21:24
bknudsonand we shouldn't be doing that "stuff" at import time.21:24
*** tdruiva has quit IRC21:25
dstanekbknudson: i agree and i think your load_backends seam would be a great place to fix it21:25
morganfainbergdstanek, it's in services.py that does it21:25
morganfainbergdstanek, i think21:25
dstanekbknudson: also we are talking about global state because of how the decorator works21:25
*** xqueralt has quit IRC21:25
morganfainbergdstanek, and the tests don't load the config until afterwards unlike the real-keystone startup21:25
*** yassine has joined #openstack-dev21:26
bknudsonglobal state :(21:26
morganfainbergbknudson, sadly, hard to get around that in some cases.21:26
dstanekmorganfainberg: i believe you are right about services.py21:27
morganfainbergbknudson, notably since caching memoization decorator is an instance-bound method to the cache region21:27
bknudsondstanek: well, if that's what we have to do... at least take a look at a change in load_backends.21:27
morganfainbergdstanek, +awesome to any cleanup making that better :)21:27
dstaneki feel like today has been a productive day and i haven21:28
*** nati_ueno has joined #openstack-dev21:28
dstanek't written much code yet21:28
*** urulama has quit IRC21:28
morganfainbergdstanek, this is whayt the summit felt like to me.21:28
*** jimjiang has quit IRC21:29
morganfainbergdsantos_, i saw a question you were asking higher up.  did you figure it out?21:29
morganfainbergdsantos_, sorry just realized i hadn't responded to you yet.21:29
*** sgordon has joined #openstack-dev21:29
*** sgordon has quit IRC21:29
*** sgordon has joined #openstack-dev21:29
*** d0ugal has joined #openstack-dev21:30
*** d0ugal has joined #openstack-dev21:30
*** d0ugal has quit IRC21:30
*** jimjiang has joined #openstack-dev21:30
*** colinmcnamara has joined #openstack-dev21:30
*** d0ugal has joined #openstack-dev21:31
*** d0ugal has joined #openstack-dev21:31
*** d0ugal has quit IRC21:31
dstanekbknudson: looks like it merged two days ago...i'll start to play21:31
ayoungdolphm, OK, so what if we put all of the available versions on both the /v2.0 sand /v3 pages?  THat way, even if I give the wrong auth_url, we can run discovery and find the right one21:32
*** razumovalex has joined #openstack-dev21:32
*** gszasz has quit IRC21:32
bknudsonayoung: I like that idea.21:32
bknudson(and I also don't have a problem with parsing url)21:33
*** d0ugal has joined #openstack-dev21:33
ayoungbknudson, it would have to be something like "other_versions"21:33
ayoungwhich is a new API change and all that21:33
ayoungcould be in the links, though21:33
*** glenng has joined #openstack-dev21:35
*** jimjiang has quit IRC21:35
*** d0ugal has joined #openstack-dev21:35
*** d0ugal has joined #openstack-dev21:35
*** d0ugal has quit IRC21:35
*** jimjiang has joined #openstack-dev21:36
bknudsonayoung: wondering if we need it in the /v3 response?21:37
bknudsonI thought the problem was just existing catalogs that have /v2.0?21:37
ayoungbknudson, true21:37
*** mikeoutland has joined #openstack-dev21:38
ayoungbknudson, what we really need is to be able to look at the response and say "this is not the version I want"21:38
*** d0ugal has joined #openstack-dev21:38
*** d0ugal has joined #openstack-dev21:38
*** d0ugal has quit IRC21:38
*** dprince has quit IRC21:38
bknudsonayoung: so you'll request /v2.0 ... how does it know that it's v2 or v3? and how does it know what version you wanted?21:39
*** briancline has quit IRC21:39
ayoungbknudson, cuz you asked for a v3 client21:39
*** d0ugal has joined #openstack-dev21:39
*** d0ugal has quit IRC21:39
ayoungbknudson, this is so flipping broken....all of discovery is broken, and we let ourselves get hungf up on this?21:40
ayoungARGH!21:40
ayoungIts not like I had an approach that would fix this or anthing either.21:40
*** glenng1 has joined #openstack-dev21:40
ayounggrumble21:40
*** d0ugal has joined #openstack-dev21:41
*** d0ugal has joined #openstack-dev21:41
*** d0ugal has quit IRC21:41
bknudsonayoung:  the v2 response does say "id": "v2.0"21:41
bknudsonayoung: but I thought you wanted to avoid a round-trip to the server?21:41
bknudsonputting the v3 endpoint in the v2.0 version response would help with discovery21:41
*** d0ugal has joined #openstack-dev21:41
*** d0ugal has quit IRC21:41
*** d0ugal has joined #openstack-dev21:41
ayoungbknudson, I jsut want to hack the URLs.21:42
ayoungI don';t want to playu oin this horse and poiny show21:42
* ayoung can't type too annoyed21:42
*** glenng has quit IRC21:42
*** dvarga has quit IRC21:42
ayounghere is the thing...we say "h, you have to do discovery" but then all of the rest of theAPI is based on a-priori knowledge21:43
*** mikeoutland has quit IRC21:43
*** mriedem has joined #openstack-dev21:43
*** razumovalex has quit IRC21:44
bknudsonwe only have version discovery and not all API discovery21:45
*** neelashah has quit IRC21:45
termie_ayoung: here here brother21:46
*** termie_ is now known as termie21:46
*** termie has quit IRC21:47
*** termie has joined #openstack-dev21:47
* ayoung summoned a termie, 21:47
*** d0ugal has joined #openstack-dev21:48
*** d0ugal has joined #openstack-dev21:48
*** d0ugal has quit IRC21:48
*** d0ugal has joined #openstack-dev21:48
*** d0ugal has joined #openstack-dev21:49
*** d0ugal has quit IRC21:49
*** d0ugal has joined #openstack-dev21:49
*** yfried has joined #openstack-dev21:49
termieayoung: be careful what you wish for21:49
dstanekayoung: are there examples of other APIs that do discovery?21:50
ayoungtermie, you mean I'll end up with OCL?21:50
termieayoung: you'll end up with that anyway21:50
*** dave_tucker has quit IRC21:50
ayoungdstanek, APIs don'21:50
ayoungt do sicovery, clients do21:50
termieayoung: i just haven't read all the scrollback so i may not actually be agreeing with you :p21:50
ayoungAPIs don't do discovery, clients do21:50
*** glenng1 is now known as glenng21:50
yfried asking again here (redirected from infra):21:50
yfriedHi guys, I'm looking to get the external connectivity (ie - ping 8.8.8.8) on the devstack-neutron gate so this patch can work: https://review.openstack.org/#/c/55146/21:50
yfriedcan any one help me?21:50
yfriedor to put it another way - are we sure the gate doesn't have external connection at the moment?21:50
*** mikeoutland has joined #openstack-dev21:51
dstanekayoung: right, i meant that support (or encourage)21:51
*** jasondotstar has quit IRC21:51
ayoungtermie, heh, the problem is that we have two versions of the API, v2.0 and v3, and we've been telling everyone fo so long that they need to register then endpoints with v2.0, and now we want to tell them go to v3, and they are all "No way."21:51
*** briancline has joined #openstack-dev21:52
termiev3 = vLulz21:52
ayoungdstanek, Yeah, its called a web brower.  We can't actually use one with Keystone because we hand back broken links.  Which I tried to fix way back when21:52
ayoungtermie, I knew you were going to say that21:52
ayoungcuz you said it before21:52
*** BLZbubba has joined #openstack-dev21:52
termieayoung: repitition is the key to propaganda21:52
ayoungtermie, I am thinking that version numbers in URLs are not the right way to go21:52
*** Darkness650 has joined #openstack-dev21:52
*** MaxV has joined #openstack-dev21:53
Alexei_987dhellmann: Hi do you have some time to chat?21:53
*** bknudson has quit IRC21:53
*** rnirmal has quit IRC21:53
dhellmannAlexei_987: I'm in the release project meeting at the moment21:53
dstanekayoung: your definition of discovery seems to be different than conneg - at least in my current understanding21:53
termieayoung: my gut assumption is that we could have dealt with versions in a better, backwards compatible way21:53
* dhellmann has too many meetings :-/21:53
*** vartom111119 has quit IRC21:53
Alexei_987dhellmann: when you'll be available?21:53
dhellmannAlexei_987: 10 minutes or so?21:54
ayoungtermie, I've seen some recommendations that it should be handled via content_types.  Something bothers me about that, can't quite put my finger on it, but it seems better than what we do now21:54
Alexei_987dhellmann: cool, ping me when ready21:54
*** bknudson has joined #openstack-dev21:54
ayoungBut something in the request should say "I want the old version blah" but the URL is the good name of the object21:54
ayoungshouldn't be the url21:55
*** ohnoimdead has joined #openstack-dev21:56
termiehmm, i think i wrote an update to this with explicit descriptions of how to do versioning: https://wiki.openstack.org/wiki/EasyApi21:56
*** yeylon__ has quit IRC21:56
termieanyway, that's cool, you guys go do your own thing21:56
termiei'll go back to making it as irrelevant as possible by coding around it in ocl ;)21:57
ApsuThe more standards the better!21:57
ApsuOpen as in choice, yo21:57
dstanekayoung: it would have to be a combination of content-types and a hypertext driven workflow21:57
termieoo, that update is allllmost 3 years old21:57
termievishy: oo, almost the 3-year anniversary of EasyApi21:58
*** e0ne has joined #openstack-dev21:58
termievishy: drinks on the 28th? ;)21:58
*** jcoufal has joined #openstack-dev21:59
ayoungtermie, while I hope you are successful, Einstein said it so well  "There is a race between mankind and the universe. Mankind is trying to build bigger, better, faster, and more foolproof machines. The universe is trying to build bigger, better, and faster fools. So far the universe is winning."22:00
*** e0ne has quit IRC22:00
*** nati_uen_ has joined #openstack-dev22:01
termieayoung: "Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction."22:01
ayoungSounds like your driving philosophy22:01
termiejust some random einstein quote that is probably made up22:02
dhellmannAlexei_987: ready, if you are22:02
termiebut seems to point in a more productive direction than yours22:02
Alexei_987dhellmann: I'm here22:02
*** nati_uen_ has quit IRC22:03
Alexei_987dhellmann: working on one patch I've became bored of passing context object all around22:03
*** SumitNaiksatam has joined #openstack-dev22:03
Alexei_987dhellmann: what do you think about following approach - https://review.openstack.org/#/c/62639/2/ironic/common/context.py22:03
*** branen has quit IRC22:03
*** nati_ueno has quit IRC22:03
*** nati_uen_ has joined #openstack-dev22:03
dhellmannAlexei_987: have a look at the locals module in oslo-incubator22:03
*** dstanek has quit IRC22:04
Alexei_987dhellmann: yep :)22:04
dhellmannAlexei_987: also consider whether this new "global" makes testing more difficult22:04
Alexei_987why?22:04
*** melwitt has quit IRC22:04
*** melwitt has joined #openstack-dev22:04
dhellmannAlexei_987: as a general rule, I would prefer an explicit argument22:04
*** mfer has quit IRC22:04
termieAlexei_987: because most of testing revolves around overriding conditions in specific cases22:05
Alexei_987dhellmann: but it's passed through 10 methods and never used22:05
ayoungtermie, mayhaps...I didn't design keystone, just came along later and tried to do with it what needed to be done.  I wouldn't claim that I was the right person to do this, just that there was a vacuum, and a need.  I never wanted to do all this anyway.  I wanted to be...22:05
ayounga lumberjack22:05
termieayoung: have you seen my beard?22:05
*** colinmcnamara has quit IRC22:05
termieayoung: http://instagram.com/p/iCZIJIKdiH/22:05
dhellmannAlexei_987: it introduces something else to mock out (or clear) rather than inject from a test method22:05
ayoungtermie, no. I think I've only seen you with the mustache22:06
Alexei_987dhellmann: https://review.openstack.org/#/c/62639/2/ironic/tests/conductor/test_manager.py22:06
termie(i just got a haircut)22:06
*** melwitt1 has joined #openstack-dev22:06
dhellmannAlexei_987: it sounds like maybe the stack is overly complex, then?22:06
*** alunduil has quit IRC22:06
*** melwitt has quit IRC22:06
Alexei_987dhellmann:  well in ironic it makes sense, cause most of the stuff is executed with used context, and some stuff requires admin context22:06
Alexei_987dhellmann: so it can escalate privileges for 1 action and release just after22:07
dhellmannAlexei_987: sure, I get why it's needed, I'm just saying 10 levels that don't use it seems like a lot of layers of abstraction22:08
morganfainbergtermie, oh hi!22:08
termiemorganfainberg: good day to you, sir22:08
ayoungtermie, Ok, so the problem is the service catalog which we return in the Keystone token.  Would you recommend we drop that?  I know you suggested Zookeeper or a compatable service registration/discovery point,m byut I never quite got your larger vision22:08
Alexei_987dhellmann: well we have a lot of abstractions around22:08
dhellmannAlexei_987: yep :-)22:08
*** ArxCruz has joined #openstack-dev22:09
termieayoung: which part of it is the problem?22:09
termieayoung: i can tell you my vision, but it'd be useful to get the succinct backstory22:09
Alexei_987dhellmann: so what do you think in general? does pros outweigh the cons?22:09
dhellmannAlexei_987: I still prefer an explicit argument :-/22:09
*** melwitt1 has quit IRC22:10
Alexei_987dhellmann: Ok yet another patch abandoned22:10
*** melwitt has joined #openstack-dev22:10
ayoungtermie, all of the operations that the keystone client performs are based on the URLs that come back from the endpoints list.  We've been telling people to put v2.0 in them22:10
*** markmcclain has quit IRC22:10
Alexei_987dhellmann: thanks clearing this out22:10
dhellmannAlexei_987: sorry22:10
*** jdob has quit IRC22:11
Alexei_987dhellmann: no problem it was just a draft proposal22:11
ayoungand since people have been doing this, and writing clients against Keystone that work on this assumption, if we change the endpoints (drop the versions) we break all the clients out there22:11
dhellmannAlexei_987: ok22:11
*** Darkness650 has left #openstack-dev22:11
termieayoung: the catalog is returning v2, or the clients are using v2 instead of what the catalog returns?22:11
ayoungthe catalog returns http://host:500/v2.022:12
termieayoung: and if it returned http://host:5000/v3.11 what would happen?22:12
*** DennyZhang has joined #openstack-dev22:13
ayoungwell, a v3.11 client would work fine, and everyone else would be broken22:13
termieayoung: or http://host:2001?22:13
termieayoung: why would the client be broken? you just mean that the client assumes the version is 2?22:13
*** pberis has quit IRC22:13
ayoungso, that is what we would want, and that, right now, breaks everything, but we can fix that...we have the discovery mechanism  to find out what versions are supported, but it is not used by default yet22:13
termieayoung: if it responds correctly to their request there shouldn't be an issue, right?22:13
*** pberis has joined #openstack-dev22:14
*** davidhadas_ has quit IRC22:14
termieayoung: so, right now there is a v2 and a v3 way to request a token, i assume22:14
ayoungyes22:14
ayoungbut requesting a token is done a-priori22:14
ayoungyou set the AUTH_URL22:14
ayoungand call a specific client22:14
*** athomas has quit IRC22:14
*** pberis has quit IRC22:14
termieayoung: and then we discover other endpoints, some of which may have versions you know about and some of which may not22:15
ayoungright...I think all of the other services are doing versioned endpoints due to our bad example22:15
*** bswartz has quit IRC22:15
termieayoung: don't worry, it isn't keystone itself's bad example22:15
termieayoung: just rackspace's22:16
termieayoung: but regardless of the versioning bit, the answer is either a) smarter responses or b) better clients22:16
ayoungso I want to start with b22:16
morganfainbergtermie, a bit of both a and b?22:16
ayoungIE...look at the url, and if it has a version on it, hack it off22:16
*** d0ugal has quit IRC22:17
termiemorganfainberg: sometimes, but then you can run into things like html vs browsers22:17
*** xmltok_ has joined #openstack-dev22:17
termiemorganfainberg: and quirksmode22:17
termiewhere nobody knows the statemachine that will be traversed to decide the answer22:17
*** joesavak has quit IRC22:17
ayoungwe can make the server smarter over time, but client needs to work with older servers, and needs to be smart today22:17
*** pcm__ has joined #openstack-dev22:17
*** ruhe has quit IRC22:17
termieso with b, you have stuff that will do it's damndest to figure out the correct call and have extensive tests written to make sure it works against everything, like Universal RSS Parser in the day22:17
*** sgordon has quit IRC22:18
morganfainbergtermie, fair point.  but i'd like somewhat smarter responses... it's personal view.22:18
morganfainbergtermie, oh good example22:18
*** markmc has quit IRC22:18
termieOCL, btw, has probably a good handle on that because it was written while refusing to work on the APIs22:18
termiebecause i've washed my hands of them22:18
*** d0ugal has joined #openstack-dev22:18
*** d0ugal has joined #openstack-dev22:18
*** d0ugal has quit IRC22:18
termieon the smarter response side we can try to guess which client is asking, sort of like a User-Agent in the web22:19
termiei don't really like the way websites do that, because it tends to fuck up when i am writing test stuff22:19
*** teran has joined #openstack-dev22:19
*** d0ugal has joined #openstack-dev22:19
*** d0ugal has quit IRC22:19
*** d0ugal has joined #openstack-dev22:19
termieand it menas tons of my code has inserted false user-agents over the years22:19
*** dave_tucker has joined #openstack-dev22:19
morganfainbergtermie, i like the concept of "supports capability of" being sent in22:20
termieso, i've tended to lean towards b22:20
*** d0ugal has joined #openstack-dev22:20
*** d0ugal has joined #openstack-dev22:20
*** d0ugal has quit IRC22:20
morganfainbergand the server giving something useful back based upon that22:20
morganfainbergdefaulting to "basic" functionality22:20
termiesure, additional info lets client decide, but older stuff is still an issue22:20
termiein farmboy, the thing i've been working on recently, i still have a config value for whether you are supporting neutron or not22:20
morganfainbergtermie, right.22:20
*** d0ugal has joined #openstack-dev22:20
*** d0ugal has quit IRC22:20
*** d0ugal has joined #openstack-dev22:20
*** pcm has quit IRC22:20
*** d0ugal has joined #openstack-dev22:21
*** d0ugal has quit IRC22:21
*** d0ugal has joined #openstack-dev22:21
morganfainbergtermie, it's a question of where to stick the logic22:21
termiemorganfainberg: yup, i think i made that clear in my previous statements ;)22:21
*** d0ugal has joined #openstack-dev22:21
morganfainbergtermie, i like setting a minimum bar (sorry Ie7, go away) and expand from there22:21
morganfainbergoffering optional/better handling (Responses) if supported by the client, and let the client decide22:21
termiemorganfainberg: somebody will still end up writing universal rss parser and being well loved for it22:22
morganfainbergagain, totally personal bias22:22
termiemorganfainberg: or at least tolerated at your conferences22:22
morganfainbergtermie, i know. ;)22:22
termiei apparently am being called into a coffee run22:22
morganfainbergtermie, anyway i'll let you get back to the original topic now that we've tangented some22:22
*** d0ugal has joined #openstack-dev22:22
*** d0ugal has joined #openstack-dev22:23
*** d0ugal has joined #openstack-dev22:23
*** d0ugal has quit IRC22:23
termieayoung: brb after coffee and will explain the zookeeper vision22:23
*** d0ugal has joined #openstack-dev22:23
*** d0ugal has quit IRC22:23
*** d0ugal has joined #openstack-dev22:23
ayoungtermie, cool22:23
*** d0ugal has joined #openstack-dev22:24
*** d0ugal has quit IRC22:24
*** d0ugal has joined #openstack-dev22:24
*** jobewan has quit IRC22:25
*** d0ugal has joined #openstack-dev22:25
*** d0ugal has quit IRC22:25
*** d0ugal has joined #openstack-dev22:25
*** pcm__ has quit IRC22:26
*** glenng has quit IRC22:26
*** yassine has quit IRC22:28
*** d0ugal has joined #openstack-dev22:28
*** d0ugal has quit IRC22:28
*** d0ugal has joined #openstack-dev22:28
*** jimjiang has quit IRC22:28
*** jimjiang has joined #openstack-dev22:29
*** boris-42 has quit IRC22:29
*** d0ugal has joined #openstack-dev22:30
*** d0ugal has joined #openstack-dev22:30
*** d0ugal has quit IRC22:30
*** d0ugal has joined #openstack-dev22:33
*** nermina has quit IRC22:33
*** d0ugal has joined #openstack-dev22:34
*** d0ugal has quit IRC22:34
*** d0ugal has joined #openstack-dev22:34
*** d0ugal has joined #openstack-dev22:35
*** d0ugal has joined #openstack-dev22:35
*** d0ugal has quit IRC22:35
*** nermina has joined #openstack-dev22:38
*** d0ugal has joined #openstack-dev22:38
*** d0ugal has joined #openstack-dev22:38
*** d0ugal has quit IRC22:38
*** d0ugal has joined #openstack-dev22:40
*** danielbruno has quit IRC22:41
*** aeperezt has quit IRC22:42
*** jmontemayor has joined #openstack-dev22:44
*** sarob has joined #openstack-dev22:44
*** DennyZhang has quit IRC22:44
*** gordc has quit IRC22:45
*** SergeyLukjanov has quit IRC22:46
*** stevemar has quit IRC22:50
*** troytoman is now known as troytoman-away22:50
termieayoung: I RETURN22:50
*** jmontemayor has quit IRC22:51
termieayoung: the idea with the zookeeper etc thing is that the real solution we are trying to solve here is a place to store reliable information about where to locate the things in our system22:51
*** dave_tucker has quit IRC22:51
termieayoung: and there already exist significantly more reliable / available codebases for doing just that then some random crap we're going to add to keystone22:52
*** dave_tucker has joined #openstack-dev22:52
morganfainbergtermie, ++22:52
termieayoung: that already deal in things like paxos and fault tolerance22:52
*** thomasem has quit IRC22:52
termieayoung: so why invent a broken wheel22:52
termieayoung: zookeeper was based on models in use by large companies already, whereas i haven't heard anybody on keystone besides maybe myself pushing for any of those ideas22:53
termieayoung: if somebody is running a large cloud, they need a reliable service in the middle to find this information22:53
ApsuIf only we had a lightweight protocol for accessing a sort of index. A directory perhaps.22:54
termieayoung: and additionally they tend to need a way to do things like outtages and drain out a datacenter22:54
*** loq_mac has joined #openstack-dev22:55
*** buzztroll has quit IRC22:56
*** yfried has quit IRC22:56
*** sarob has quit IRC22:57
*** aeperezt has joined #openstack-dev22:58
termieayoung: so, long story shorter, have a scheme for storing service information in zookeeper, teach openstack services how to use that, probably let keystone shim some information in front of it, and eventually define the "catalog" service in terms of it22:58
*** dave_tucker has quit IRC22:59
*** johnthetubaguy has joined #openstack-dev22:59
*** dave_tucker has joined #openstack-dev22:59
*** jimjiang has quit IRC23:00
*** dims has quit IRC23:01
*** jimjiang has joined #openstack-dev23:01
*** jcoufal has quit IRC23:01
*** MaxV has quit IRC23:01
*** jpich has quit IRC23:01
*** denis_makogon has quit IRC23:02
*** arnaud__ has quit IRC23:02
*** arnaud has quit IRC23:02
*** harlowja is now known as harlowja_away23:02
*** mrunge has quit IRC23:02
ayoungI return from shoveling...and read up23:02
*** nkinder has quit IRC23:03
ayoungtermie, what does zookeeper have going for it that LDAP does not?23:03
*** iccha_ is now known as iccha-dinner23:03
*** pablosan has quit IRC23:04
*** kevinconway has quit IRC23:04
*** MaxV has joined #openstack-dev23:04
*** johnthetubaguy has quit IRC23:04
ayoungI know that "regions" is where we first discussed this.  I am guessing the zookeeper has a smart way of saying "here is the right service for someone in your location"23:04
*** melwitt1 has joined #openstack-dev23:05
*** melwitt has quit IRC23:05
*** kbringard has quit IRC23:05
*** mikeoutland has quit IRC23:05
*** harlowja_away is now known as harlowja23:05
*** MaxV has quit IRC23:05
*** Farooque has joined #openstack-dev23:05
*** mikeoutland has joined #openstack-dev23:06
termieayoung: i barely know how to answer that question, do any of these overlap with ldap? http://en.wikipedia.org/wiki/Apache_ZooKeeper#Typical_use_cases23:06
*** lsmola_ has quit IRC23:06
ayoungtermie, yeah.  the D in LDAP is Directory.  LDAP is just the protocol.23:06
ayoungYou stick things in LDAP that you want to find later23:06
*** jtomasek has quit IRC23:07
ayoungusers, printers, Queus23:07
*** eharney has quit IRC23:07
ayoungQueues23:07
termieayoung: i didn't see the word directory on that page23:07
morganfainbergayoung, zookeeper is more dynamic.23:07
ayoungmorganfainberg, I get the sense that it is more workload focused23:07
morganfainbergayoung, as in, i see LDAP as a more permanent store23:07
ayoungtermie, naming service and directory are often used interchangably, which is why I brought it up23:08
termieayoung: is it just that you've worked with ldap so much that you always talk about? almost nobody else ever does23:08
Ryan_LaneI don't see how zookeeper or ldap are alike at all23:08
termieayoung: it has done a job in the past, one it is still used for, which is listing email addresses in outlook23:08
ayoungtermie, its from the enterprise world...not the startup world23:08
termieRyan_Lane: smaes23:08
termieRyan_Lane: sames23:08
Ryan_Laneldap is just another datastore23:09
ayoungI am not at all familiaer with Zookeeper, which is why I am asking23:09
Ryan_Laneit's a permanent datastore that has a very strict schema23:09
termieayoung: well i feel like if you read that short wikipedia page you'll have a better idea23:09
Ryan_Laneand an awkward protocol :D23:09
morganfainbergtermie, so am i understanding this correctly: basically register a service w/ ZK on startup (etc) and derive catalog/endpoints based upon that.  if you start the service elsewhere it registers and is available23:10
*** david-lyle_ has quit IRC23:10
morganfainbergtermie, rely on that as the "catalog" vs the templates or ... sql or whatever in ks now23:10
*** dstanek has joined #openstack-dev23:10
morganfainbergtermie, or am i making an extra leap here that isn't needed23:10
morganfainberg?23:10
termiemorganfainberg: in reality it is usually used almost opposite, the thing starting the serivce looks to zk on startup to find out where it should go23:10
morganfainbergtermie, ah23:10
morganfainbergtermie, ok i was inverting it23:11
*** burt has quit IRC23:11
ayoungtermie, I did...I read it back when you first told me about it.  Here is the things that have come up recently that I think we need to sort out:  we have huge number of machines running 'stack and there is no centralized naming or location services for them.  Then, for the end uers, they have the smae problem, but * 1000 cuz they are using virtual machines23:11
termiemorganfainberg: but it is also used in the way you describe23:11
morganfainbergtermie, i can see it being useful in both ways within OS.23:11
*** e0ne has joined #openstack-dev23:11
ayoungso my question was:  are you thinking zookeeper as a service that end users get from the openstack deployment, or something for internal use, or for both?23:11
termiemorganfainberg: yup23:11
morganfainbergayoung, i would (at least initially) see it as internal and it gets used to generate the data provided to end-users23:12
termieayoung: something they get in an openstack deployment that they'll probably want to base internal things off of as well23:12
termieayoung: i think initially we'll still be shimming the data into keystone23:12
termiebecause ocean boiling23:12
*** vijendar has quit IRC23:12
*** mikeoutland has quit IRC23:13
*** vijendar has joined #openstack-dev23:13
termiebut the protocol can easily be used directly23:13
glucastermie: you mean zookeeper initially as a layer on top of keystone?23:13
termieglucas: nay, i just mean things still use the catalog23:13
glucasah23:13
shardyayoung: https://wiki.openstack.org/wiki/Heat/Blueprints/InstanceUsers23:13
termieglucas: so initially just start building that catalog from the zk23:13
ayoungtermie, so would it make sense that each nova compute node would be registered with zookeeper? Cells?23:14
morganfainbergglucas, that is exactly where i saw it.23:14
*** nermina has quit IRC23:14
shardyayoung: If you can add anything, pleas do, particularly to clarify the x509 section ;)23:14
morganfainbergglucas, ^23:14
termieayoung: maybe? it definitely makes sense that the service locations are23:14
ayoungshardy, listen in to termie 's conversation...23:14
*** cpallares has quit IRC23:14
morganfainbergtermie, ayoung, we could use auth_token middleware to register the service...it's dirty hack but....23:15
*** thomasem has joined #openstack-dev23:15
termieayoung: i think once people learn how the tool works they will be able to figure out how much data is reasonable ot put in there23:15
morganfainbergand derive keystone's location from that connection to zk as well23:15
termiemorganfainberg: just have the ervices register themselves?23:15
morganfainbergtermie, possibly23:15
ayoungmorganfainberg, question of trust23:15
*** e0ne has quit IRC23:16
*** dims has joined #openstack-dev23:16
morganfainbergayoung, it's not fully baked, might have that issue.  depends on the control ZK can provide23:16
termieregistering of services is something that is done on the order of 1 request every minute or hour or day23:16
*** thomasem has quit IRC23:16
termiethat's not a hard scalability goal to hit23:16
*** thomasem has joined #openstack-dev23:16
ayoungmorganfainberg, its the same general problem as freeipa:  you want to know a new X is coming in, so you pre-allocate a resource for it, but you also give X a secret, one time use, that it can use to register23:17
morganfainbergtermie, ayoung, i need to spend some more time looking into ZK to know how feasable it would be, but it might be possible.23:18
termiemorganfainberg: how feasible what is?23:18
morganfainbergtermie, auto-registration could be.23:18
ayoungtermie, so I think I've been addressing the same problem, but using older technologies.  LDAP and FreeIPA do a lot of the same things.  Gives you Kerberos based SSO and X509 management.  I'm trying to see where a FreeIPA based approach would fall down, and what the scalability benefits of Zookeeper are.23:18
morganfainbergtermie, or at least from the ephemeral 'child' sense.23:19
morganfainbergin zk23:19
termiemorganfainberg: it is as easy as an authenticated call to your keystone service registry thing at the moment, no?23:19
ayoungLDAP assumes a fairly static set up, but should be able to handle the physical side...I was thinking that the virtual machine side might be too dynamic23:19
morganfainbergtermie, probably23:19
*** yamahata has quit IRC23:20
termiemove the backend, then move the frontend == backwards compat23:20
*** vijendar has quit IRC23:20
ekarlsostrptime('17/Dec/2013:20:11:51 +0100', '%d/%b/%Y:%X %z') < works in py3 but 2.7 ?23:20
*** _dbalog has quit IRC23:20
*** sgordon has joined #openstack-dev23:21
*** alunduil has joined #openstack-dev23:21
ayoungtermie, I was also unclean because Zookeeper calls itself a configuration service, and I was wondering where the line was between what you do with Zookeeper and what you do with Puppet.23:21
termieayoung: not particularly related23:22
*** reed has quit IRC23:22
sudorandom+1 for service registry for OpenStack in general. Zookeeper is likely not the only viable option though so I'd keep that in mind. I read 'zookeeper' during this conversation as a number of possible tools. Here's one possible alternative: https://github.com/coreos/etcd23:23
termieayoung: configuration as in it stores the configuration you look up, for example if the things starting services look at it at startup to know who to talk to23:23
*** thomasem has quit IRC23:23
termieayoung: where as puppet is sort of an integrated configration application (as in it applies configurations) service23:23
ekarlsotermie: can I bother you boss to ask what the discussion is? like a 30k foot view23:24
*** urulama has joined #openstack-dev23:24
ayoungekarlso, read up..started with me asking about his vision for integrating with zookeeper23:25
ayoungekarlso, which came up in the "regions" context23:25
termieekarlso: we're discussing how things like the service catalog should be stored/updated/interpreted23:25
termieekarlso, ayoung: came up in the regions context because i made the claim that the regions solution is solving a symptom not a cause23:26
*** xmltok_ has quit IRC23:26
*** shardy is now known as shardy_afk23:26
ayoungtermie, so, instead of an auth_url, we would give the client a Zookeeper url.  The client would ask "where is keystone" and get a token from there, but no service catalog.  THen it would go to zookeeper and say "now where is nova"?23:26
termieayoung: probably not, no23:26
ekarlsoah ok23:27
termieayoung: you would give an auth_url that is a keystone instance, depending on your internal architecture that is probably routed based on config loaded from zk in your internal bits, to a load balanced keystone, that thing tosses you a token as normal with a catalog that was generated from zk23:28
ayoungtermie, so Keystone would front zookeeper to the end user23:28
termieayoung: if we are removing the catalog lookup from the token call, you would have a separate call to a catlaog service that builds the catalog from zk23:28
ayoungzookeeper would be an internal service that the end use does not talk to directly, at least not for Open Stack related calls.23:28
morganfainbergtermie, which i think is a good approach, remove the catalog from the token that is23:29
termieayoung: yeah, end user is not going to talk to it23:29
*** urulama has quit IRC23:29
termieayoung: internal users mights23:29
termieayoung: but that is probably out of scope23:29
ayoungmorganfainberg, I always saw that as a performance tweak23:29
termieit is a useful tool so people tend to use it for things once they find out it is there23:29
*** asalkeld has quit IRC23:29
*** radsy has quit IRC23:29
*** asalkeld has joined #openstack-dev23:30
sudorandomI think of service registry as an internal service similar to where rabbitmq fits in.23:30
ayoungtermie, I was thinking about it in terms of end users.  It looks like it is used for long running tasks, Hadooplike23:30
termiemorganfainberg: i think the catalog is fine in the token, personally, because plenty of things will need the data nayway, i don't reall ylike the format but it seaves a common call23:30
*** xmltok_ has joined #openstack-dev23:30
termieayoung: it is used for things like, "my service is starting up and wants to know where the memcache and db backends it can connect to are"23:31
termieayoung: which is basically internal discovery23:31
*** buzztroll has joined #openstack-dev23:31
*** xmltok_ has quit IRC23:31
ayoungtermie, OK, you answered the big question.  It is an internal service.  I agree, we need one.23:32
morganfainbergtermie, the issue is that it actually has gotten too large in some cases and causes errors with header sizes23:32
* ayoung needs to go be a dad now.23:32
*** xmltok_ has joined #openstack-dev23:32
morganfainbergtermie, we've had to construct it as "optional" in the token data in some cases23:32
termiemorganfainberg: well, that is probably solvable by adding things asking for specific endpoints to the token call23:32
morganfainbergtermie, fair point, perhaps it would be nice ot have the option to reference a stand-alone service catalog23:33
morganfainbergtermie, again, client / use case specific23:33
termiemorganfainberg: aye, i think a standalone service is not a bad idea23:33
morganfainberg*shrug* things to think about when we have a central service.23:33
termiemorganfainberg: are you stuffing the entire response into a header?23:33
morganfainbergtermie, PKI tokens kindof do that23:33
termiemorganfainberg: part of the point is that keystone should not be a single instance23:33
morganfainbergtermie, i agree with that23:34
morganfainbergtermie, 100%23:34
*** jmontemayor has joined #openstack-dev23:34
termiethings like ZK can actually be central services because they are designed to be23:34
termiebut keystone should spawn a bunch of instances that get appropriately routed by your network config23:35
morganfainbergtermie, totally makes sense to me.23:35
termiewhich, in various places, are actually also configured by zk23:35
termie(because it is a popular place to store that kind of data)23:36
termiesudorandom: re other options, definitely look at them and come up with some pros and cons23:37
termiesudorandom: zookeeper, for all its warts, has tended to be the one teams i've been part of have come to decide on23:37
termiesudorandom: so that's my initial guess at the right solution23:38
*** p4tux has quit IRC23:39
*** p4tux has joined #openstack-dev23:39
*** BLZbubba has quit IRC23:39
*** glucas has quit IRC23:39
*** glucas has joined #openstack-dev23:40
*** romcheg has quit IRC23:41
*** mikeoutland has joined #openstack-dev23:42
*** sthaha has joined #openstack-dev23:42
*** tdruiva_ has quit IRC23:44
*** tdruiva has joined #openstack-dev23:44
jamielennoxdamn, missed all of that - i like the idea of a central service catalog that isn't keystone and pushing that out of the token, it's important then i think that we can fetch an entire global service catalog and expect the services to extract the right one from the list23:44
jamielennoxbut that is something that is fairly easily re-used23:45
*** branen has joined #openstack-dev23:46
*** rcleere has quit IRC23:47
*** dolphm has quit IRC23:47
*** jmontemayor has quit IRC23:48
*** tdruiva has quit IRC23:49
*** dstanek has quit IRC23:51
*** jhesketh__ has joined #openstack-dev23:53
*** fbo is now known as fbo_away23:55
*** SumitNaiksatam has quit IRC23:56
*** faramir1 has joined #openstack-dev23:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!