Tuesday, 2013-02-19

*** troytoman is now known as troytoman-away00:01
*** flaper87 has quit IRC00:01
*** colinmcnamara has quit IRC00:07
*** lillie has quit IRC00:07
*** lillie has joined #openstack-meeting00:08
*** lillie has quit IRC00:09
*** lillie- has joined #openstack-meeting00:10
*** stevebaker has quit IRC00:11
*** stevebaker has joined #openstack-meeting00:12
*** roampune has left #openstack-meeting00:14
*** sdake has joined #openstack-meeting00:17
*** stevebaker has quit IRC00:19
*** stevebaker has joined #openstack-meeting00:27
*** dontalton has quit IRC00:27
*** eharney has quit IRC00:33
*** bencherian has joined #openstack-meeting00:36
*** anteaya has quit IRC00:43
*** lillie- is now known as lillie00:43
*** rnirmal has quit IRC00:50
*** sacharya has joined #openstack-meeting00:52
*** yamahata has quit IRC00:56
*** rongze has joined #openstack-meeting00:56
*** lillie has quit IRC01:05
*** lillie- has joined #openstack-meeting01:06
*** mrodden has quit IRC01:09
*** shang has joined #openstack-meeting01:09
*** yamahata has joined #openstack-meeting01:09
*** stevebaker has quit IRC01:12
*** stevebaker has joined #openstack-meeting01:12
*** yaguang has joined #openstack-meeting01:18
*** jog0_ has joined #openstack-meeting01:19
*** sleepsonthefloor has quit IRC01:19
*** hemna has joined #openstack-meeting01:22
*** jog0 has quit IRC01:23
*** markwash has quit IRC01:23
*** bdpayne has quit IRC01:26
*** otherwiseguy has quit IRC01:39
*** mrodden has joined #openstack-meeting01:40
*** danwent has joined #openstack-meeting01:47
*** dprince has joined #openstack-meeting01:51
*** salv-orlando has quit IRC01:56
*** pcm_ has joined #openstack-meeting02:12
*** hemna has quit IRC02:14
*** sacharya1 has joined #openstack-meeting02:19
*** johnpur has joined #openstack-meeting02:19
*** sacharya has quit IRC02:22
*** dprince has quit IRC02:25
*** pcm_ has quit IRC02:25
*** gary has joined #openstack-meeting02:33
*** gary is now known as Guest8712802:33
*** markmcclain has quit IRC02:34
*** shang_ has joined #openstack-meeting02:35
*** Guest87128 has left #openstack-meeting02:36
*** shang has quit IRC02:37
*** bdpayne has joined #openstack-meeting02:42
*** Mandell has quit IRC02:49
*** johnpur has quit IRC02:51
*** vipul is now known as vipul|away02:52
*** hemna has joined #openstack-meeting02:55
*** shang_ has quit IRC02:59
*** psedlak has joined #openstack-meeting03:00
*** novas0x2a|laptop has quit IRC03:01
*** emagana has joined #openstack-meeting03:02
*** bdpayne has quit IRC03:02
*** ladquin has quit IRC03:06
*** vipul|away is now known as vipul03:08
*** nati_ueno has joined #openstack-meeting03:08
*** markmcclain has joined #openstack-meeting03:22
*** sarob has quit IRC03:24
*** nati_ueno_2 has joined #openstack-meeting03:24
*** martine has joined #openstack-meeting03:25
*** nati_ueno has quit IRC03:25
*** emagana has quit IRC03:33
*** emagana has joined #openstack-meeting03:35
*** asalkeld has quit IRC03:47
*** yamahata_ has joined #openstack-meeting03:48
*** lbragstad has joined #openstack-meeting03:53
*** fifieldt has quit IRC03:58
*** sleepsonthefloor has joined #openstack-meeting03:58
*** hemna_ has joined #openstack-meeting04:00
*** hemna has quit IRC04:04
*** topol has quit IRC04:05
*** topol has joined #openstack-meeting04:06
*** dabo has quit IRC04:07
*** dabo has joined #openstack-meeting04:07
*** sivel has quit IRC04:07
*** sivel has joined #openstack-meeting04:09
*** nati_ueno has joined #openstack-meeting04:12
*** nati_ueno has quit IRC04:14
*** bdpayne has joined #openstack-meeting04:14
*** nati_ueno has joined #openstack-meeting04:15
*** nati_ueno_2 has quit IRC04:15
*** adjohn has quit IRC04:21
*** kmartin has quit IRC04:23
*** Mandell has joined #openstack-meeting04:25
*** danwent has quit IRC04:28
*** rongze has quit IRC04:29
*** rongze has joined #openstack-meeting04:30
*** sandywalsh has quit IRC04:31
*** bdpayne has quit IRC04:46
*** maurosr has quit IRC04:46
*** martine has quit IRC04:50
*** emagana has quit IRC04:50
*** emagana has joined #openstack-meeting04:50
*** saschpe has quit IRC04:54
*** saschpe has joined #openstack-meeting04:54
*** bencherian has quit IRC04:58
*** emagana has quit IRC05:03
*** nati_ueno_2 has joined #openstack-meeting05:04
*** nati_ueno has quit IRC05:06
*** ketan985 has joined #openstack-meeting05:08
*** ketan985 has quit IRC05:09
*** ketan985 has joined #openstack-meeting05:09
*** maoy has quit IRC05:13
*** maoy has joined #openstack-meeting05:14
*** maoy has quit IRC05:15
*** kmartin has joined #openstack-meeting05:25
*** bdpayne has joined #openstack-meeting05:30
*** adjohn has joined #openstack-meeting05:32
*** adjohn has quit IRC05:36
*** bgmccollum has left #openstack-meeting05:42
*** markmcclain has quit IRC05:44
*** shang has joined #openstack-meeting05:46
*** sacharya1 has quit IRC05:46
*** garyk has quit IRC05:47
*** adjohn has joined #openstack-meeting05:51
*** nati_ueno has joined #openstack-meeting05:52
*** almaisan-away is now known as al-maisan05:54
*** nati_ueno_2 has quit IRC05:55
*** bdpayne has quit IRC06:08
*** bdpayne has joined #openstack-meeting06:26
*** al-maisan is now known as almaisan-away06:31
*** almaisan-away is now known as al-maisan06:34
*** topol has quit IRC06:41
*** garyk has joined #openstack-meeting06:51
*** kmartin has quit IRC06:51
*** hemna_ has quit IRC06:52
*** hemna_ has joined #openstack-meeting07:05
*** obondarev has joined #openstack-meeting07:13
*** nati_ueno has quit IRC07:14
*** nati_ueno has joined #openstack-meeting07:14
*** mrunge has joined #openstack-meeting07:16
*** bdpayne has quit IRC07:18
*** nati_ueno has quit IRC07:19
*** shang has quit IRC07:24
*** shang has joined #openstack-meeting07:31
*** nati_ueno has joined #openstack-meeting07:41
*** rongze has quit IRC07:45
*** asalkeld has joined #openstack-meeting07:47
*** salv-orlando has joined #openstack-meeting07:47
*** lillie- is now known as lillie07:48
*** rafaduran has joined #openstack-meeting08:02
*** nati_ueno has quit IRC08:06
*** nati_ueno has joined #openstack-meeting08:06
*** flaper87 has joined #openstack-meeting08:07
*** nati_ueno has quit IRC08:11
*** egallen has joined #openstack-meeting08:24
*** egallen has quit IRC08:42
*** jhenner has joined #openstack-meeting08:54
*** dosaboy has joined #openstack-meeting09:00
*** egallen has joined #openstack-meeting09:01
*** egallen_ has joined #openstack-meeting09:09
*** egallen has quit IRC09:09
*** egallen_ is now known as egallen09:09
*** Mandell has quit IRC09:13
*** egallen has quit IRC09:13
*** egallen has joined #openstack-meeting09:20
*** jhenner has quit IRC09:20
*** derekh has joined #openstack-meeting09:22
*** egallen has quit IRC09:23
*** gongysh has quit IRC09:42
*** afazekas has joined #openstack-meeting09:43
*** egallen has joined #openstack-meeting09:44
*** gongysh has joined #openstack-meeting09:45
*** salv-orlando_ has joined #openstack-meeting09:45
*** salv-orlando has quit IRC09:45
*** salv-orlando_ is now known as salv-orlando09:45
*** egallen has quit IRC09:45
*** boris-42 has quit IRC09:59
*** salv-orlando has quit IRC10:00
*** adjohn has quit IRC10:08
*** BobBall has quit IRC10:09
*** ketan985 has quit IRC10:10
*** salv-orlando has joined #openstack-meeting10:25
*** Razique has joined #openstack-meeting10:30
*** vkmc has joined #openstack-meeting10:41
*** adjohn has joined #openstack-meeting10:42
*** psedlak has quit IRC10:46
*** egallen has joined #openstack-meeting10:51
*** adjohn has quit IRC10:52
*** egallen has quit IRC11:09
*** jhenner has joined #openstack-meeting11:14
*** adjohn has joined #openstack-meeting11:18
*** adjohn has quit IRC11:23
*** anniec has joined #openstack-meeting11:28
*** anniec has quit IRC11:28
*** anniec has joined #openstack-meeting11:28
*** pcm_ has joined #openstack-meeting11:30
*** pcm_ has quit IRC11:31
*** pcm_ has joined #openstack-meeting11:32
*** dhellmann has joined #openstack-meeting11:34
*** adjohn has joined #openstack-meeting11:49
*** adjohn has quit IRC11:54
*** psedlak has joined #openstack-meeting11:57
*** maurosr has joined #openstack-meeting12:00
*** maurosr has quit IRC12:00
*** maurosr has joined #openstack-meeting12:01
*** timello_ has quit IRC12:04
*** radez is now known as radez_g0n312:05
*** maurosr has quit IRC12:07
*** timello_ has joined #openstack-meeting12:14
*** maurosr has joined #openstack-meeting12:18
*** adjohn has joined #openstack-meeting12:19
*** yamahata has quit IRC12:20
*** yamahata has joined #openstack-meeting12:23
*** adjohn has quit IRC12:24
*** sandywalsh has joined #openstack-meeting12:30
*** martine has joined #openstack-meeting12:31
*** al-maisan is now known as almaisan-away12:34
*** martine has quit IRC12:41
*** martine has joined #openstack-meeting12:42
*** timello_ has quit IRC12:48
*** adjohn has joined #openstack-meeting12:50
*** krtaylor has quit IRC12:52
*** adjohn has quit IRC12:55
*** egallen has joined #openstack-meeting12:56
*** timello_ has joined #openstack-meeting13:07
*** markvoelker has joined #openstack-meeting13:08
*** mrunge has quit IRC13:10
*** egallen has quit IRC13:11
*** lbragstad has quit IRC13:12
*** dolphm has joined #openstack-meeting13:20
*** adjohn has joined #openstack-meeting13:21
*** ladquin has joined #openstack-meeting13:22
*** yaguang has left #openstack-meeting13:22
*** vishy has quit IRC13:22
*** saschpe has quit IRC13:23
*** saschpe has joined #openstack-meeting13:23
*** Slower has quit IRC13:25
*** adjohn has quit IRC13:25
*** Slower has joined #openstack-meeting13:25
*** timello_ has quit IRC13:27
*** krtaylor has joined #openstack-meeting13:28
*** vishy has joined #openstack-meeting13:30
*** timello_ has joined #openstack-meeting13:37
*** spzala has joined #openstack-meeting13:38
*** darraghb has joined #openstack-meeting13:45
*** adjohn has joined #openstack-meeting13:52
*** adjohn has quit IRC13:55
*** dhellmann has quit IRC13:55
*** eharney has joined #openstack-meeting13:56
*** dprince has joined #openstack-meeting13:56
*** gongysh has quit IRC13:58
*** Razique has quit IRC14:01
*** topol has joined #openstack-meeting14:04
*** anteaya has joined #openstack-meeting14:06
*** fesp has joined #openstack-meeting14:07
*** flaper87 has quit IRC14:08
*** troytoman-away is now known as troytoman14:09
*** mtreinish has joined #openstack-meeting14:15
*** woodspa has joined #openstack-meeting14:25
*** kmartin has joined #openstack-meeting14:30
*** mattray has joined #openstack-meeting14:32
*** gongysh has joined #openstack-meeting14:34
*** fnaval has quit IRC14:35
*** lbragstad has joined #openstack-meeting14:36
*** tongli has joined #openstack-meeting14:41
*** dontalton has joined #openstack-meeting14:52
*** adjohn has joined #openstack-meeting14:53
*** fnaval has joined #openstack-meeting14:54
*** almaisan-away is now known as al-maisan14:54
*** adjohn has quit IRC14:57
*** radez_g0n3 is now known as radez14:58
*** AlanClark has joined #openstack-meeting15:00
*** maoy has joined #openstack-meeting15:00
*** markmcclain has joined #openstack-meeting15:03
*** dhellmann has joined #openstack-meeting15:04
*** bencherian has joined #openstack-meeting15:06
*** ctracey has quit IRC15:08
*** markvan has joined #openstack-meeting15:08
*** dontalton has quit IRC15:09
*** ctracey has joined #openstack-meeting15:09
*** ndipanov has quit IRC15:10
*** fesp is now known as flaper8715:15
*** beagles has quit IRC15:18
*** beagles has joined #openstack-meeting15:19
*** sacharya has joined #openstack-meeting15:23
*** zykes- has quit IRC15:23
*** adjohn has joined #openstack-meeting15:24
*** nati_ueno has joined #openstack-meeting15:24
*** ndipanov has joined #openstack-meeting15:25
*** kmartin has quit IRC15:26
*** troytoman is now known as troytoman-away15:28
*** adjohn has quit IRC15:28
AlanClarkping ttx15:30
ttxAlanClark: pong15:31
*** zykes- has joined #openstack-meeting15:32
*** cp16net is now known as cp16net|away15:32
*** cp16net|away is now known as cp16net15:32
*** sacharya has quit IRC15:33
*** rnirmal has joined #openstack-meeting15:33
*** otherwiseguy has joined #openstack-meeting15:34
*** john5223 has joined #openstack-meeting15:34
AlanClarkttx - The board would like to  see if the TC would be interested in holding a joint F2F meeting on April 14 (The Sunday before the Summit)15:34
ttxAlanClark: I can discuss that in the TC meeting today.15:34
AlanClarkttx perfect15:35
ttxAlanClark: what time ? A lot of us (including me) have already their plane tickets15:35
AlanClarkwe were thinkng 2pm to 5pm then dinner at 6pm15:35
AlanClarkThe board will be meeting starting at 9am15:35
ttxAlanClark: beh. My plane lands around 6pm15:36
*** noslzzp has quit IRC15:36
ttxAlanClark: also the tricky part is that we don't know who will be on the TC by then15:36
ttxsince we're having elections in two weeks15:37
ttxbut I'll talk about it and see how doable it is15:37
AlanClarkttx hmmm please do.  I'd be interested for their feedback15:38
*** garyTh has joined #openstack-meeting15:38
AlanClarkttx one topic I was thinking would be to finish up the IncUp and present our report to the joint meeting15:39
ttxyeah, that would be great15:39
AlanClarkttx  we toss around ideas of trying to hold a joint meeting during the Summit week but figured that TC members would be to busy15:41
*** troytoman-away is now known as troytoman15:42
*** AlanClark__ has joined #openstack-meeting15:42
*** luis_fdez has joined #openstack-meeting15:43
*** cp16net is now known as cp16net|away15:45
*** AlanClark has quit IRC15:46
*** lglenden has joined #openstack-meeting15:47
*** radez is now known as radez_g0n315:51
*** al-maisan is now known as almaisan-away15:52
*** yaguang has joined #openstack-meeting15:52
*** adjohn has joined #openstack-meeting15:54
*** danwent has joined #openstack-meeting15:58
*** adjohn has quit IRC15:59
*** anniec has quit IRC16:03
*** luis_fdez has left #openstack-meeting16:03
*** hanrahat has joined #openstack-meeting16:03
*** nati_ueno_2 has joined #openstack-meeting16:04
*** hanrahat has quit IRC16:05
*** noslzzp has joined #openstack-meeting16:06
*** nati_ueno has quit IRC16:07
*** ndipanov has quit IRC16:08
*** egallen has joined #openstack-meeting16:10
*** cp16net|away is now known as cp16net16:12
*** bdpayne has joined #openstack-meeting16:12
*** kmartin has joined #openstack-meeting16:13
*** sacharya has joined #openstack-meeting16:18
*** gyee has joined #openstack-meeting16:19
*** ndipanov has joined #openstack-meeting16:22
*** gongysh has quit IRC16:23
*** emagana has joined #openstack-meeting16:24
*** koolhead17 has joined #openstack-meeting16:25
*** adjohn has joined #openstack-meeting16:25
*** egallen has quit IRC16:28
*** SunSlayer has joined #openstack-meeting16:29
*** SunSlayer has quit IRC16:30
*** adjohn has quit IRC16:30
*** lillie has quit IRC16:30
*** lillie- has joined #openstack-meeting16:31
*** adjohn has joined #openstack-meeting16:32
*** mrodden1 has joined #openstack-meeting16:33
*** Gordonz has joined #openstack-meeting16:34
*** garyk has quit IRC16:35
*** Gordonz has quit IRC16:35
*** mrodden has quit IRC16:35
*** Gordonz has joined #openstack-meeting16:36
*** mrodden1 has quit IRC16:37
*** nati_ueno_2 has quit IRC16:38
*** nati_ueno has joined #openstack-meeting16:38
*** egallen has joined #openstack-meeting16:38
*** anniec has joined #openstack-meeting16:41
*** anniec has quit IRC16:42
*** adjohn has quit IRC16:43
*** mrodden has joined #openstack-meeting16:45
*** mrodden has quit IRC16:46
*** mrodden has joined #openstack-meeting16:46
*** AlanClark__ has quit IRC16:49
*** AlanClark__ has joined #openstack-meeting16:50
*** garyk has joined #openstack-meeting16:50
*** diogogmt has joined #openstack-meeting16:51
*** reed has joined #openstack-meeting16:58
*** radez_g0n3 is now known as radez17:00
*** egallen has quit IRC17:00
*** colinmcnamara has joined #openstack-meeting17:03
*** ctracey has quit IRC17:04
*** ctracey has joined #openstack-meeting17:05
*** yaguang has quit IRC17:06
*** egallen has joined #openstack-meeting17:07
*** emagana has quit IRC17:12
*** jhenner has quit IRC17:14
*** heckj has joined #openstack-meeting17:15
*** bencherian has quit IRC17:21
*** sarob has joined #openstack-meeting17:24
*** egallen has quit IRC17:25
*** sarob has quit IRC17:25
*** sarob has joined #openstack-meeting17:26
*** nati_ueno_2 has joined #openstack-meeting17:26
*** troytoman is now known as troytoman-away17:26
*** annegentle has joined #openstack-meeting17:28
*** rafaduran has quit IRC17:30
*** nati_ueno has quit IRC17:30
*** ctracey has quit IRC17:34
*** ctracey has joined #openstack-meeting17:34
*** gyee has quit IRC17:35
*** nati_ueno_2 has quit IRC17:39
*** hemnafk is now known as hemna17:39
*** nati_ueno has joined #openstack-meeting17:39
*** lloydde has joined #openstack-meeting17:40
*** YorikSar has joined #openstack-meeting17:44
*** dhellmann is now known as dhellmann-afk17:46
*** gyee has joined #openstack-meeting17:46
*** diogogmt has quit IRC17:48
*** diogogmt has joined #openstack-meeting17:50
*** annegentle has quit IRC17:53
*** kwss has joined #openstack-meeting17:54
*** nachi has joined #openstack-meeting17:55
*** reed has quit IRC17:57
*** henrynash has joined #openstack-meeting17:58
*** dwchadwick has joined #openstack-meeting17:59
*** markwash has joined #openstack-meeting17:59
*** rellerreller has joined #openstack-meeting18:00
*** garyTh has quit IRC18:00
henrynashhi18:01
dwchadwickhi18:01
heckjIt's that time!18:01
*** bencherian has joined #openstack-meeting18:01
heckjo/18:01
heckj#startmeeting keystone18:01
openstackMeeting started Tue Feb 19 18:01:37 2013 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
dolphmo/18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
heckjagenda at #link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Agenda_for_next_meeting18:01
heckjIf you haven't noticed, we have a whole new WIki18:01
heckj(going to take some getting used to)18:02
spzalaHi all!18:02
*** gordc has joined #openstack-meeting18:02
topolhi18:02
dolphmawesome18:02
heckjI know we're all crankin' busy with code reviews and hacking and the like, so I'll keep this as quick as I can18:02
heckj#topic high priority issues/bugs/etc18:03
*** garyTh has joined #openstack-meeting18:03
*** openstack changes topic to "high priority issues/bugs/etc (Meeting topic: keystone)"18:03
gyeeheckj, /auth/tokens vs /auth18:03
*** Mandell has joined #openstack-meeting18:03
heckjWe've got some security CVE's getting announced to the public today - in general, I think we're looking pretty good there, but there's also the new EC2 issue that gyee spotted18:03
heckjgyee: will add to list18:03
heckjdolphm: you've been cranking on resolving that bug - anything pending/outstanding? help needed?18:04
*** jog0 has joined #openstack-meeting18:05
*** FallenPegasus has joined #openstack-meeting18:05
dolphmthis is the nasty part https://review.openstack.org/#/c/22327/18:05
*** jog0 has quit IRC18:05
*** FallenPegasus is now known as MarkAtwood18:05
dolphmin short, our tests don't always create the default domain ID, so they won't pass if we enable domain validation ... so i'm trying to resolve that18:05
*** derekh has quit IRC18:05
*** jog0 has joined #openstack-meeting18:05
*** brich1 has joined #openstack-meeting18:05
heckjword18:06
*** nati_ueno has quit IRC18:06
heckjdolphm: can any of us help, or just keep an eye to help review https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Agenda_for_next_meeting?18:06
heckjdamnit18:06
heckjreview: https://review.openstack.org/#/c/22327/18:06
heckj#link https://review.openstack.org/#/c/22327/18:06
dolphmif anyone else has any test infrastructure updates in review to make that happen, i'd appreciate them being pointed out to me :)18:06
*** nati_ueno has joined #openstack-meeting18:06
dolphmwould love to steal them and get them merged :P18:06
heckjOk - so let's move on and run through the feature freeze updates18:07
heckjayoung: around?18:07
*** jpich has joined #openstack-meeting18:08
heckjlet's start with gyee's "/auth/tokens vs /auth"18:08
heckjgyee: what's the summary?18:08
dolphm#link https://review.openstack.org/#/c/21943/18:08
dolphmayoung wants to change /v3/auth to /v3/auth/tokens in order to support, for example, an x509 authentication response18:09
gyeeayoung wants /auth/tokens for HATEOAS support18:09
gyeeI am fine with that, just want to make sure we are doing the right thing18:10
dolphmi'm not confident that changing the resource is the best approach for supporting that18:10
dolphmif you're providing the same request in either case, and you want a different response back, you would normally provide a different Accept header18:10
*** nati_ueno has quit IRC18:11
heckjdolphm: that's definitely the more formal way of doing with REST, but we haven't been very strict on that point up until now.18:11
dolphmi'm a little lost on how this is different from the UUID -> PKI change18:11
dolphmif it's even feasible to replace tokens within openstack with something else18:12
*** darraghb has quit IRC18:12
heckjfrom my perspective, the UUID -> PKI change didn't change anything except config on the server, leaving the resource with the exact same content types if I recall18:12
dolphmand lastly, if it would be expected for the client to make the determination of what they get back, rather than the server's implementation18:12
dolphmheckj: correct18:12
dolphmheckj: i'm not clear from ayoung on what exactly x509 would be replacing18:13
dolphmheckj: or if it's something that's in addition to tokens18:13
gyeeyeah, supporting multiple token format at the same time sound dangerous18:13
gyeeayoung around?18:13
heckjI think it's perfectly reasonable if it's clear what we're intending, but it's obviously not at this point.18:13
dolphmbottom line is that i'm not clear on the end goal or how the API is currently incompatible with that end goal, so i'm not comfortable in approving API-level changes to accommodate the unknown18:14
heckjhe was earlier - dunno - maybe grabbing lunch of something18:14
dolphmi keep saying ayoung hoping he'll get a ping :)18:14
heckjyeah :-)18:14
heckjOkay - we clearly need ayoung's input here to help describe, so we'll shelve this for the moment18:15
gyee /auth/tokens is standing in between a -1 and +2 from ayoung right now :)18:15
dolphmregardless of all this discussion, i don't think gyee's feature-add should be blocked on the issue18:15
dwchadwickdolphm: if you are not clear on the end goal, then perhaps it would help to write up what the model for tokens currently is, and what it should be in the future18:15
gyeedolphm, agreed18:15
dolphmif we want to change the API, and we consider it to be long-term broken at a fundamental level, we can change it and make a follow up patch after feature freeze18:16
heckjagreed as well18:16
dwchadwickthis issue is not an API issue at heart. It is a conceptual model issue18:16
heckjgyee: does this solve your issue?18:16
*** adjohn has joined #openstack-meeting18:17
gyeeheckj, yeah, now I just need some +1s or 2s :)18:17
heckjkk18:17
heckjHenry - let's switch to you18:17
henrynashok18:17
heckjhenrynash: what's the word on policy engine and namespaces18:17
dolphmgyee: just noticed you pushed another patch, will review asap18:17
topolgyee, you are close to a +1 from me. did you see my comments18:17
gyeetopol, yes, I addressed them in configuration.rst and the handler interface18:18
dolphmhenrynash's test failure on https://review.openstack.org/#/c/22109/ is apparently reproducible -- is it legit?18:18
gyeemade it clear how the plugins are being invoked18:18
topolgyee, OK, cool. I will re-review18:18
henrynashso both are either approved or just need the final button pressed…but both are failing with random failures in jenkings/gate18:18
henrynashthe same code passed yesterday...18:18
YorikSardolphm: It's some PyPI fail.18:19
heckjsubmit a recheck on those - saw a comment in #infra earlier this morning that said the testing was infra and fixed/working now18:19
henrynashyep18:19
YorikSarI had my change request failed as well.18:19
henrynashheckj: did that earlier, and email from ci folks said not to do that anymore while they reolve18:19
heckjah - oops :-)18:19
heckjI guess we'll just wait for the word then18:20
*** kwss has quit IRC18:20
heckjstill, sounds like it's all headed in the right direction there. Any issues?18:20
henrynashheckj: indeed, although annoying timing (as it alwayys is)18:20
henrynashonly thing I haven't done was on the query filters…dolph you were saying you would rather it be two consecutive decorators...18:20
henrynash….which I had trouble making work….I fixed up all the other suhhestions (including pushing the filtering into the wrap_collection)18:21
heckjseparate protect and fileter?18:21
dolphmheckj: yes18:21
dolphmhenrynash: i wouldn't block on that18:21
dolphmhenrynash: i think it'd be semantically clearer and easier to maintain18:22
dolphmhenrynash: it'd be nice if they shared code at the very least, as someone pointed out18:22
henrynashdolphm: well i split out all the common code into a submodule they both call18:22
dolphmhenrynash: cool18:23
henrynashonly other one of me is whether Guang, you need me to layer some domain token issuing on top of your v3 auth change?18:23
henrynashi had kinda assumed that it would come out in the wash!18:24
henrynashbut if I need to do something, let me know and I'm on it18:24
gyeehenrynash, yeah, I left that part to you18:25
henrynashgyee: ok, no problem….I saw where you planned it to be18:25
dolphmhenrynash: your tests pass offline, correct?18:25
gyeehenrynash, thanks18:25
*** ndipanov has quit IRC18:25
*** MarkAtwood has quit IRC18:26
henrynashdolphm: yes…and passed online last night18:26
dolphmhenrynash: if we approve, ci team appears to be following up and ensuring things merge18:26
dolphmjeblair specifically (thanks!)18:26
*** sarob has quit IRC18:26
*** MarkAtwood has joined #openstack-meeting18:26
heckjOkay - next topic then18:27
YorikSarCan I propose another change request to be merged before feature freeze? https://review.openstack.org/20928 has been reviewed, had to be rebased and cleaned and now looks like ready.18:27
heckjWas just going to ask if there was any other reviews that wanted/needed attention18:27
YorikSarI felt it18:28
heckjheh18:28
dolphmthat one should be easy to get in18:28
*** nati_ueno has joined #openstack-meeting18:28
heckjI'd think so too - the nasty remaining item seems to be the trusts work, and ayound is hiding from us18:29
YorikSarWe had some discussion with Brant here and even he gave me +118:29
heckjrequest to review #link https://review.openstack.org/#/c/20928 please18:29
dolphmhopefully he's grinding through API changes :)18:29
heckjOkay - I'll be updating the blueprints page on various pieces in a few, and we've got the release meeting.18:30
heckjRight now, I'm planning on requesting the we hold the cut for keystone until these biggies are all merged in.18:30
heckjtrusts is the only one that I see at significant risk right now18:30
*** egallen has joined #openstack-meeting18:31
dwchadwicktrusts is intertwined with tokens.18:31
gyeeheckj, they need to get in by today or 21st?18:31
dolphmgyee: today18:31
gyeesheet!18:31
heckjyeah, ttx had requested today - I'll be requesting an extension at the release meeting18:31
dolphmgyee: jenkins issues are causing a delay18:31
heckjheh - they always do...18:32
heckj#topic open discussion18:33
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:33
topolheckj, for us new folks can you explain the ramifications of the feature freeze date?18:34
topolhow rigid??18:34
dolphmtopol: quite rigid -- nothing but bug fixes and docs can merge to master for the next few weeks18:34
heckjtopol: we basically have bug fixes, integration tests to run, and docs to tweak up between here and the grizzly RC18:35
topolso the ldap group stuff for example. Is that considered stuff we will fix via bugs or is it deferred to havana?18:35
YorikSartopol reads my mind18:36
heckjif you want to add a new capability somewhere, we've generally done that in a feature branch or side branch, which we'll accept for general merging after we cut the branches and open for development for Havanna18:36
heckjtopol: Given that's not new functionality from the API/external perspective, I think you can easily fill that in, but be ready to make dual patches - merge to master and then backport to RC candidates18:36
dolphmtopol: if implementation isn't going to land before feature freeze, implement it ASAP and we'll work it out case by case? anything that smells like a feature must be incredibly well justified as being necessary18:36
heckjlooks like that one may be a jump ball :-)18:38
* heckj is going to be distracted for a few… bbiab18:39
topolWell,  https://review.openstack.org/#/c/21327/13  is muddying the waters for me.  Its not clear to me what we want the backend LDAP structure to look like18:40
dolphmtopol: how does that impact things?18:40
topolNeed ayoung here :-)18:40
dolphmlol k18:40
YorikSartopol: tenant_id was something strange in LDAP from the beginning.18:40
ayoungsorry, I am here18:41
ayoungwas busy coding18:41
dolphmyay18:41
topolYay ayoung18:41
YorikSarI don't see how this change does something to LDAP structure.18:41
dolphmalso yay for code18:41
dolphmbrb18:41
* ayoung reads up18:41
YorikSarThe only change is that we can let projects be something simpler than groupOfNames now.18:42
ayoungugh18:42
topolayoung,  its not clear to me what the ldap structure should look like. given our conversation last night it appeared stuff was changin18:42
ayoungOK,  so X509....18:42
ayoungtokens suck18:42
ayoungto use an industry term18:42
ayoungand what I want to do, but am not ready to propose18:42
ayoungis to replace tokens with X50918:43
*** egallen has quit IRC18:43
ayoungthey can have a private key in them that can be used to both secure the connection and ensure the id of the user....you ll know this...18:43
gyeeyay on PKI :)18:43
ayoungso, if we do X509, or some other format18:43
dwchadwickayoung. you mean public key18:43
ayoungsay openID, oauth, saml ,cameleoparduck whatever18:43
ayoungdwchadwick, don't start18:44
ayoungyes, I mean publich key18:44
ayoungthe short of it18:44
ayoungis that they may all come in as content tyep HTML or whatever18:44
ayoungbut we need to distinguish based on the objet itself18:44
ayoungso auth was supposed to be a container, with token just the first impl18:45
ayoungkapish?18:45
ayoungdwchadwick, and, btw, I love your input, just not when I have code freeze in a couple hours. :)18:45
*** lcheng has joined #openstack-meeting18:45
gyeeayoung, dolphm was arguing why can't we do Content: application/x509 or something18:45
*** psedlak has quit IRC18:46
ayounggyee, because openid and oath will both probably come in as http18:46
ayoungand because we don't want to mix tokens with X509s18:46
dolphm"what I want to do is to replace tokens with X509" completely totally abandon X-Auth-Token, X-Subject-Token, etc?18:46
ayoungin revocation lists18:46
dwchadwickayoung: we have already  catered for this in our design. We now support various incoming token formats18:46
ayoungdolphm, yes18:46
dolphmayoung: +2 for /auth/tokens then -- that's the clarification i was looking for18:47
ayoungdwchadwick, and I think this is where your design would slot int18:47
ayoungwhew18:47
ayoungok,  so on to ldap....18:47
ayoungLDAP sucks18:47
ayoungI think I am going to start all my speeches that way18:48
topolayoung, but not going anywhere18:48
YorikSarNot that much  :)18:48
ayoungheh18:48
ayoungok,  proeject don't have members anymore18:48
ayoungprojects are really just a container for resources and those containers are controlled outside of keystone18:48
ayoungall we do is privide roles for users in containers18:48
ayoungusers belong to groups and user belong to domain, but not projects18:48
dolphmayoung: all that depends on the use case :(18:49
ayoungso groupOfName no longer is required18:49
YorikSarWe can change it to organizationalUnit18:49
dolphmayoung: e.g. some deployments want keystone to handle domains, projects and roles but not users18:49
ayoungYorikSar, yeah, probably makes sense18:49
ayoungdolphm, right, but we still need a user record locally18:49
ayoungdolphm, for the full ldap use case18:50
ayoungwe need18:50
YorikSarAnd purge all code that deals with members18:50
ayoungto be able to specify how to populat the local users18:50
topolayoung, so I have no idea what the ldap structure should look like and I need to verify it wont blow chunks like it does now18:50
ayoungfor example, not all users in the corporate LDAP are going to have access to keystone at all18:50
YorikSarWe can isolate them by some subtree, attribute or just take all users from some collection.18:51
ayoungYorikSar, organizationalUnit  for the project, and then roles done as organizationalROles as they are now is probably the right fit.  Might be worth running past the AD smart people though18:51
topolayoung, a sample ldap structure would help me18:51
dwchadwickAyoung: you dont alter the LDAP structure to give people permissions, but rather you give them appropriate attributes18:52
YorikSarI don't think that AD cares about this.18:52
dwchadwickThe LDAP structure should be irrelevant18:52
dwchadwickAnd anyway if you want to use corporate LDAPs, they will all have different structures18:52
gyeedwchadwick, agreed18:53
ayoungdwchadwick, so there are two competing things here, one of which is the default schema that we support, and which I am trying to make as inclusive as possible,  the second is what do we do to adapt to other peoples LDAP schems.18:53
topolayoung, +118:53
ayoungso topol is dealing with the first issue first18:53
ayounghow to represent projects18:53
ayoungwe were doing it as group of names18:53
ayoungbut I think that is problematic18:53
dwchadwickI suggest you use attribute mappings for this18:53
YorikSarbtw, groupOfNames was broken for AD iirc18:53
ayoungdwchadwick, not between now and code freeze, but YES YES YES for Havana18:54
ayoungI'd argue it is priority18:54
ayoungYorikSar, yes it was18:54
YorikSarBecause AD does not allow subentries for groupOfNames.18:54
ayoungyou can't put roles under them18:54
YorikSarou will work even better.18:54
gyeeAD is not LDAP :)18:54
YorikSarLDAP is a protocol and AD supprots it ;)18:54
dwchadwickgyee: +1000018:54
*** mrodden has quit IRC18:55
ayoungYorikSar, and LDAP embraces and extends it18:55
topolgroupOfNames is giving me fits even with openldap18:55
ayoungdolphm, you back yet?18:55
ayoungOK,  so on trusts18:55
ayoungone issue I just hit18:55
ayoungdeleting a trust using DELETE.18:55
YorikSartpool: Huh? We ran tempest with OpenLDAP and it was fine.18:55
*** cp16net is now known as cp16net|away18:56
dolphmyes, i'm following along18:56
ayoungI was origianlly going to mark these fields as invisible in the DB, but now I m being asked to list enabled and disabld trusts18:56
dolphm< 4 minutes18:56
*** cp16net|away is now known as cp16net18:56
ayoungI want trusts to be immutable so i would rather not support PATCH18:56
dolphmayoung: what do you mean invisible?18:56
ayoungso do I make a delete be a real delete,18:56
ayoungdolphm, actually, like tokes18:56
dwchadwickI would say yes18:57
dolphmayoung: that's fine, but you originally proposed enabled and disabled listing?18:57
ayoungenables means returns in list18:57
*** cdub_ has joined #openstack-meeting18:57
dwchadwickYou dont want zombie trusts hanging around18:57
ayoungand disabled means  they don't show up18:57
dwchadwickYou do want audit trails, but this is a different issue18:57
ayoungdwchadwick, so, on the audit trail thing, I was thinking that people need a way to query the disabled trusts18:57
dolphmayoung: so you're looking for a soft delete behavior?18:57
ayoungand administrators need to be able to purge disabled trusts18:57
ayoungdolphm, yeah18:58
dwchadwickyou can have the concept of suspend and resume18:58
dwchadwickrevoke though is a different issue18:58
topolYorikSar, what I meant is GroupOfNames requires some attributes that werent coming in and matching the ProjectAPI attributes18:58
dolphmayoung: side note, definitely add a comment on immutability and lack of PATCH support to your API Conventions section18:59
dolphmerr API Resources18:59
dolphmexceptions need to be explicitly noted18:59
*** radez is now known as radez_g0n318:59
YorikSartopol: Does they require something besides at least one member? It was solved long ago with dumb_member.18:59
ayoungdolphm, I'va added immutabilty.  I WIll explicily referene PATCH18:59
dwchadwickYou could use Patch for suspend and resume trusts19:00
dwchadwickeven for extending the lifetime of a trust19:00
ayoungdolphm, so, for now, is DELETE -> disabled ok?19:00
*** lloydde has quit IRC19:00
topolYorikSar, devstack was not sending in a description.  But it sounds like you can point me in the right direction19:00
heckjgotta wrap this19:00
topolmember was an issue as well19:00
heckj#endmeeting19:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:00
openstackMeeting ended Tue Feb 19 19:00:55 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-19-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-19-18.01.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-19-18.01.log.html19:01
YorikSartopol: We've fixed it locally as well.19:01
topolYorikSar, can I call you?19:01
*** markvan has quit IRC19:01
jeblairhello ci/infra people!19:01
*** brich1 has left #openstack-meeting19:01
jeblair#startmeeting infra19:02
openstackMeeting started Tue Feb 19 19:02:16 2013 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
fungi'allo!19:02
*** spzala has quit IRC19:02
jeblair#link previous meeting: http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-12-19.04.html19:02
pleia2o/19:02
*** markvan has joined #openstack-meeting19:02
jeblair#topic wiki upgrade19:03
*** openstack changes topic to "wiki upgrade (Meeting topic: infra)"19:03
jeblairit happened!19:03
fungiwe weekend-wiki'd!19:03
jeblairi have not heard any complaints19:03
fungithere were some concerns expressed in irc about missing table contents19:03
pleia2I fixed up a link on our own InfraTeam page today, text links to uploaded images didn't quite work19:04
jeblairfungi: do we have links for sample pages with problems?19:04
fungii re-added wikiness to the old-wiki vhost so people could compare and copy19:04
jeblairfungi: +119:04
*** jbr_1 has joined #openstack-meeting19:04
jeblairshould we set a sunset for that?  2 weeks?19:04
fungijeblair: we asked for examples but i don't think anyone provided them other than to say "tables"19:04
fungijeblair: sounds good to me19:04
mordredo/19:05
*** AlanClark__ has quit IRC19:05
fungii'll send a reply to the maintenance announcement mentioning we turned that on and will be turning it off again on some date two weeksish from now19:05
jeblair#action fungi disable old-wiki sometime after mar 119:05
jeblairfungi: sounds great19:06
*** AlanClark__ has joined #openstack-meeting19:06
jeblair#link https://wiki.openstack.org/wiki/WikiMigration19:06
fungiand asking people to follow up with examples of what got missed i guess19:06
jeblairi started that page with quick notes on cleaning up common errors19:06
pleia2I should probably add this one to that page https://wiki.openstack.org/w/index.php?title=InfraTeam&diff=18149&oldid=1600819:07
*** danwent has quit IRC19:07
pleia2the :File: syntax for linked files19:07
jeblairpleia2: there was a page that auto-listed broken file links, i guess it didn't include broken _attachment_ links...19:07
* pleia2 nods19:07
jeblairpleia2: but maybe there's a similar page with a different name?  might be worth a look19:07
mordredoh neat! I don't think I'd need that picture...19:08
*** sacharya has quit IRC19:08
pleia2yeah, I'll poke around19:08
fungii did work out and fix the broken embedded youtube vids19:08
*** gordc has left #openstack-meeting19:08
fungipretty sure i got them all, but added a note to the migration tips page19:08
fungijust in case anyone stumbles across more19:09
jeblaircool.  any more wiki stuff?19:10
jeblairttx: ping19:10
jeblairdo we need to discuss bug triage, or is that left over on the agenda from last time?19:11
fungii think that was new, to discuss items which came up during triage19:11
jeblair(i'm stalling on the CLA topic because an action item from last meeting was ttx wants to discuss cla)19:12
jeblair#topic bug triage19:12
*** openstack changes topic to "bug triage (Meeting topic: infra)"19:12
fungiin case we needed any input and/or action items coming from any of it19:12
jeblairfungi: yes, i think you're right..  mordred updated some bugs i think19:12
pleia2I don't think there is anything at the moment19:13
jeblairi think that just leaves some questions for pabelanger and the qa folks...19:13
pleia2probably a good thing to cycle back to on a regular basis though19:14
jeblairso it sounds like things should be _reasonably_ up to date.19:14
jeblairpleia2: +119:14
fungi"bugs: we have them. we should fix them"19:14
*** jaypipes has quit IRC19:14
*** sacharya has joined #openstack-meeting19:14
jeblair#topic jenkins slave operating systems19:14
*** openstack changes topic to "jenkins slave operating systems (Meeting topic: infra)"19:14
jeblairfungi: how's the quantal stuff going?19:14
fungias last week, the static slaves are fine and we have some stackforge guinea-pigging on those with no complaints so far19:15
mordredwoot19:15
fungijclouds stuff was pending me hearing back from pvo and/or rackspace19:15
fungii've heard nothing, need to pester them again19:15
jeblair#action fungi pester rax about jclouds quantal image issues19:16
fungirecap on that is, probably busted image metadata for quantal. don't know much beyond that19:16
fungiescalated by pvo to their image team19:16
fungithat's all i've got on that topic for now19:16
jeblairi think i'd like to hold off moving more projects to quantal till we can use jclouds19:16
* fungi agrees19:16
fungii'd like to be able to burst while we transition19:17
jeblair#topic IANA OID19:17
*** openstack changes topic to "IANA OID (Meeting topic: infra)"19:17
fungiooh, did we get one assigned?19:17
jeblairso lauren got an email asking if the foundation had registered an OID with IANA19:17
fungithis would be primarily for quantum virtual network devices, if memory serves19:17
jeblairi am not aware of that...19:18
jeblairof that having happened, that is19:18
clarkbI haven't heard of it happening19:18
jeblairwell, i think the iana oid would mostly be used for ldap stuff19:18
jeblairthis was in the context of keystone development19:18
jeblairthough ttx mentioned that the idea of getting an OUI for networking had come up19:18
jeblairi believe OUI's cost money?  OIDs do not19:19
fungiahh, right, not an ieee oui. my mistake19:19
jeblairmordred: do you recall any previous conversations about an IANA OID?19:19
jeblairit's not in the list, so.19:20
mordredI remember that we had one19:20
jeblairoh?19:20
mordredI mean, a conversation19:20
jeblairoh19:20
*** adjohn has quit IRC19:20
mordredI think jaypipes might have been involved?19:20
jeblairokay, so it sounds like the keystone devs would like one.19:21
mordredand/or we might have talked about doing it19:21
mordredawesome19:21
mordredwe should probably track those in some manner :)19:21
jeblairprobably i should sync up with them, and then register one on behalf of the foundation...?19:21
jeblairi'll file a bug19:21
jeblairi'm not entirely sure how it would be used...19:21
fungimight make sense to have an enterprise oid assigned for custom snmp mibs as well19:22
jeblairfungi: yeah, i think it's the same registry19:22
mordredcan we get a set of them?19:22
jeblairgenerally they are used for private trees within an enterprise19:22
jeblairmordred: it's a tree19:22
mordredawesome19:22
jeblairmordred: so you stick whatever you want under it19:22
fungiyeah, carve it up however we want19:22
*** markvan has quit IRC19:23
jeblairwhat i'm not sure is whether it's appropriate to start publishing mibs, or ldap object classes, etc, as part of our products that actually use those...19:23
jeblairif so, we may also need to do some bookeeping on our side too19:24
jeblairthat is, take responsibility for registering values underneath our OID19:24
jeblairi mean, that could just start out as a wiki page19:25
fungiwe'll definitely want someone keeping that from turning into a free-for-all mess anyway19:25
clarkb++19:25
*** ryanpetrello has joined #openstack-meeting19:25
jeblair#action jeblair chat with keystone devs about OID PEN, possibly get PEN19:26
fungiand yeah, if it's on the wiki, maybe that someone is everyone19:26
jeblair#topic askbot19:26
*** openstack changes topic to "askbot (Meeting topic: infra)"19:26
*** annegentle has joined #openstack-meeting19:26
*** annegentle has quit IRC19:27
jeblairit looks like we're just going to outsource the running of the askbot server to the askbot folks19:27
*** annegentle has joined #openstack-meeting19:27
jeblairso i'm going to spin up some servers for them and hand them off19:27
pleia2jeblair: great, can you update https://bugs.launchpad.net/openstack-ci/+bug/1082784 ?19:27
uvirtbotLaunchpad bug 1082784 in openstack-ci "Add ask.openstack.org" [High,Triaged]19:27
jeblairi think that's simplest for everyone, and since they're on contract, hopefully they'll just take care of it19:28
jeblairi'd like it to be in our public infrastructure, but we didn't seem to be overrun with new volunteers begging to sysadmin the service.19:28
fungiand according to the discussion yesterday, the way to escalate issues with the ask server is to e-mail the developer directly?19:28
*** jaypipes has joined #openstack-meeting19:29
jeblairfungi: yep19:29
clarkbthat was my understadning19:29
fungii'm eager to see how that works out19:29
jeblairyeah.  well, it's not a critical piece of developer infrastructure.  :)19:30
fungipoint19:30
jeblairokay, we better start talking about the cla now19:31
jeblair#topic CLA19:31
*** openstack changes topic to "CLA (Meeting topic: infra)"19:31
fungias discussed, i sent a more eye-catching announcement to the dev ml a week ago and also hyped it on the project/release meeting last week19:31
fungii just e-mailed lsell about it too, at jeblair's urging19:32
jeblairfungi: reed also mentioned it in the community newsletter19:32
fungiyes, saw that. intended to thank him when i see him next19:32
jeblairfungi: i got an email from jbryce this morning relaying a request from some lawyers that we add a sentence:19:32
jeblair"In return, the Project Manager shall not use Your Contributions in a way that is contrary to the public benefit or inconsistent with its nonprofit status and bylaws in effect at the time of the Contribution."19:32
jeblairthat's apparently in the apache cla (it says foundation instead of project manager)19:33
fungioh, fun. if he could be explicit about where to put it19:33
jeblairand they wanted to restore that to our cla19:33
fungii'll be happy to put a review through asap19:33
*** cp16net is now known as cp16net|away19:33
jeblairfungi: same place as the apache cla, one sec19:33
fungimimic where it lives on apache's then?19:33
fungiyeah19:33
fungii can do that, no sweat19:33
jeblair#link http://www.apache.org/licenses/icla.txt19:33
fungialso the main change for this weekend is rebased and up for review19:34
fungi#link https://review.openstack.org/1409919:34
fungiplease give it a once over, but it's mimicking what's been on review-dev for months19:34
jeblairfungi: i think you should also probably send a notice to the ml about that change too.19:34
fungithe dev ml or the infra ml?19:35
jeblairfungi: since part of this is to give people time to review the new cla too.19:35
fungijeblair: i linked the new cla from last week's "important" announcement to the dev ml19:35
fungithe cla itself is not in that change since the file is already installed on the gerrit servers19:36
jeblairfungi: oh sorry, let me rephrase...19:36
*** eglynn has joined #openstack-meeting19:36
jeblairfungi: after the new sentence is added to the cla file on the gerrit servers, i think you should send a notice to that effect to the -dev mailing list19:36
fungioh, absolutely19:37
jeblairto bring to their attention that it has been slightly revised since thet last time19:37
fungi#action fungi send follow-up announcement and mention last-minute cla amendment19:37
jeblair(poor choice of words on my part earlier, by change i meant "change to the cla text" not "change under review in gerrit")19:37
jeblairwe got changes coming out of our ears19:37
jeblairttx: reping19:38
fungiother than the above, we're still on track for this weekend obviously19:39
*** n0ano has quit IRC19:39
*** markvan has joined #openstack-meeting19:39
fungiand will likely need all hands on deck come monday, to triage devs who don't read the ml and ignore error messages from git19:39
jeblair+119:39
jeblairmordred: i hope you're not on a plane monday19:40
pleia2I'll be out of town fri-sun (speaking at SCaLE), but I'll be back monday19:40
*** nachi has quit IRC19:40
fungior, if i anger the gods on sunday, to help with whatever breakage i inadvertently get us into19:40
jeblairpleia2: cool, i think reed is going to scale19:40
pleia2jeblair: yeah19:41
clarkbI will be around19:41
clarkbfungi: you should have an irc bot that responds with infos :)19:41
fungiclarkb: i intend to change the /topic in -infra and -dev at least19:42
jeblairfungi: oh, just to fill in the rest of the context, apparently that line was omitted from the original cla because openstack llc wasn't a non-profit.19:42
fungi...and the openstack foundation is. got it19:42
jeblair(or will be rsn)19:42
*** cp16net|away is now known as cp16net19:42
fungisoon come19:42
anteayateach me what to say, and I can help Monday19:42
fungianteaya: you bet!19:43
jeblair#topic open discussion19:43
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:43
jeblairthings on my plate include:19:43
jeblairreviewing zaro's patches19:43
jeblairgrenade testing19:44
jeblairsomething about tempest cli testing i think.. maybe there's a patch to turn it on and we just need to approve it?19:44
jeblairi have such a review backlog :(19:44
fungiso what's the decision on quantal slaves vs cloud archive?19:44
fungialso, we'd like to do another git-review release tag very soon if possible19:44
jeblairi _think_ the consensus is that cloud archive doesn't apply...19:44
pleia2yeah19:45
fungianteaya: sorry about the cloud archive patch, but it was a great learning experience!19:45
jeblairanteaya: yeah, sorry that didn't end up as merged code, but it was still really useful19:45
anteayafungi, it is, I don't take any decision personally19:45
jeblairanteaya: we can still close the bug.  ;)19:45
anteayajeblair, okey dokey19:45
fungianteaya: i've abandoned almost as many patches as i've had merged, i suspect ;)19:45
jeblairanteaya: any runners-up you might like to work on?19:46
anteayafungi, glad I am starting of on a good foot then, :D19:46
anteayaannegentle, and ladquin and I are about to ambush fungi when meeting is over19:46
anteayathere are a lot of doc/ci bugs languishing19:46
fungioh, also i've got a proposed new release for the puppet-dashboard puppet module to deal with an updated dependency. needs review and release19:46
*** novas0x2a|laptop has joined #openstack-meeting19:46
anteayathat if we have a tutorial on it, ladquin and I can address19:47
jeblairanteaya: awesome!19:47
annegentlewoo19:47
pleia2fungi: ah yes, I need to get my puppet dashbord test env running, testing that is on my list19:47
fungianteaya: i'm always glad to teach. the more people who know how to fix stuff, the less the rest of us need to fix ;)19:47
anteayafungi, figured you would feel that way19:47
ladquincool19:47
anteayawe are waiting to pounce in -infra at the end of the meeting19:48
pleia2reading the backlog from the weekend was helpful for me too, so thanks fungi :)19:48
jeblairspending a week documenting jjb was one of the best time investments i've made on this project.  :)19:48
fungialways time well spent19:48
*** adjohn has joined #openstack-meeting19:48
fungimordred: if you and saper want to hash out interrelationships between your git-review patch and his, i'll see about retesting and merging them19:49
fungiotherwise git-review is in decent shape and most of the pending patches are dealt with now. and i'm trying to find time to implement the shell mock tests we discussed19:50
clarkbI am still not able to run nova absolute-limits with the jenkins creds19:50
clarkbI am probably missing some obscure flag to novaclient19:50
fungior else it's an hpcloudism preventing you from doing that19:51
fungidid you try against rackspace too?19:51
clarkbno it works with my personal account19:51
fungiahh19:51
clarkbso in theory it is possible19:51
fungifreaky19:51
*** sdake_z has joined #openstack-meeting19:51
clarkbthe jenkins account is also wonky. the web gui doesn't work with it19:51
clarkbamong other things19:51
fungiseems like we need them to take a hard look at that account in general19:52
fungii assume it was an early adopter19:52
clarkbmordred: do you have any insight on that?19:52
ttxjeblair: pong19:53
jeblairttx: anything you want to say about the cla?19:53
ttxnope, no reamrk19:53
* fungi say "cla good"19:53
ttxremark19:53
ttxcla good19:53
jeblaircool.19:53
fungis/good/necessary evil/19:53
jeblairs/necessary even/unecessary evil/19:54
fungiarguably, yes19:54
funginecessary according to some lawyers19:54
jeblairbut fortunately, we don't have to argue that here and now.  :)19:54
*** gabrielhurley has joined #openstack-meeting19:55
fungittx: did you have other infra items to bring up? 4 minutes left!19:55
jeblair#action mordred yell at hpcloud to fix the openstackjenkins account19:55
jeblair#endmeeting19:57
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:57
openstackMeeting ended Tue Feb 19 19:57:04 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-19-19.02.html19:57
jeblairthanks all!19:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-19-19.02.txt19:57
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-19-19.02.log.html19:57
ttxWho is around for the TC meeting ?20:00
sdake_zhi20:00
annegentlehey howdy hey20:00
russellbhi20:00
*** markmc has joined #openstack-meeting20:00
notmynamehere20:00
eglynno/20:00
*** mrodden has joined #openstack-meeting20:00
markmchey20:00
gabrielhurley\o20:00
mordredo/20:01
heckjo/20:01
ttxthat makes 8, plenty enough20:01
*** danwent has joined #openstack-meeting20:01
annegentleI might need to duck out and in in 45 mins.20:01
ttxjaypipes, bcwaldon, jgriffith, vishy: join when you can20:02
danwenthere20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Feb 19 20:02:07 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
jaypipeso/20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
ttxAgenda for today is:20:02
ttx#link http://wiki.openstack.org/Governance/TechnicalCommittee20:02
vishyhi20:02
ttx(on brand-new wiki)20:02
ttx#topic Joint Board / TC F2F meeting on April 1420:02
*** openstack changes topic to "Joint Board / TC F2F meeting on April 14 (Meeting topic: tc)"20:02
ttxThe Board is proposing that we hold a common BoD/TC face-to-face meeting on the Sunday before the Summit20:02
ttxSomething like 2pm to 5pm then dinner at 6pm.20:02
ttxThis raises a few issues... some of us (including me) already have booked non-refundable conflicting plane tickets20:03
bcwaldonttx: hey hey20:03
ttxAlso we don't really know who will be on the TC, as we are renewing 10/12 members in the upcoming elections20:03
ttxComments ? Should we answer, we can try to be there, but best effort only ?20:03
ttxThe goal was to wrap up the conclusions of the Incubation/Core committee20:04
mordredI think that best-effort is probably all we _can_ offer20:04
ttxwhich should hopefully be completed by then20:04
markmcif folks have tickets booked, that's bad news20:04
markmcespecially ttx20:04
*** jhenner has joined #openstack-meeting20:04
markmccould we do a breakfast together?20:04
*** jhenner has quit IRC20:04
ttxWe could also do an evening thing, starting at 6pm and ending in dinner20:05
*** koolhead17 has quit IRC20:05
russellbprobably the best if we actually want everyone there20:05
ttxOK, I'll answer depending on how needed people are, prefer a late or early thing during the week20:06
ttxif optional, then sunday is fine20:06
jgriffitho/20:06
* heckj nods20:06
ttxdoes that sound good ?20:06
annegentleSunday's tough, maybe another week day20:06
ttxthe know that getting people in regular hours will be impossible20:06
mordredthe rest of the week is out because of the summit20:06
ttxso that means doing early or late in the day20:07
*** sandywalsh has quit IRC20:07
markmcand keeping it short20:07
mordredand the board members yelled at bryce after the last time that we had a meeting scheduled over top of sessions20:07
mordredkeeping it short is definitely ++20:07
ttxOK, I'll come up with an answer, though I'm pretty sure AlanClark will see this log20:07
ttx#topic End-of-cycle graduation review (cont'd)20:08
*** openstack changes topic to "End-of-cycle graduation review (cont'd) (Meeting topic: tc)"20:08
ttxLast week both projects presented why they think they are ready to be integrated in the Havana release cycle20:08
ttxWe also reviewed their release process alignment status, which was positive20:08
ttxBrian suggested we continue the review serially rather than in parallel20:08
ttxIf there is no objection to that...20:08
ttx...then I suggest that Heat goes first... since nijaba from Ceilometer is not around for this meeting20:08
markmcttx, do we absolutely need to reach a decision today?20:09
eglynnserially within a single meeting, or?20:09
eglynnor accross multiple meetings?20:09
ttxserially within one or two meetings20:09
eglynnk20:09
ttxdepending how fast we go20:09
ttxobjections ?20:09
eglynnI can speak for ceilo in any case if we get to it today20:09
ttxeglynn: we should touch it, but maybe not finish it, today.20:10
eglynnk20:10
ttx#topic Technical stability and architecture maturity assessment, Heat20:10
*** openstack changes topic to "Technical stability and architecture maturity assessment, Heat (Meeting topic: tc)"20:10
ttxIn this section I'd like to make sure that (1) the project is currently usable and (2) the architecture is now stable (no full rewrite needed during Havana cycle)20:10
sdake_zsure20:11
ttxFor Heat the only questions seem to be around template / API, and the need to support more than just AWS cloudformation.20:11
ttxsdake: could you give us your view on that ?20:11
sdake_zheat is basically a parser20:11
sdake_zwhich is contained in one file20:11
sdake_zif someone wants another template format, simply write another parser.py20:12
sdake_zso no rewrite required20:12
sdake_zapi as far as I am concerned is in good shape20:12
ttxso the architecture is pretty simple... and stable ?20:12
sdake_zour architecture has not changed in 9 months20:12
sdake_zcode base was stable when we went into incubation, but even more bugfree now ;)20:13
sdake_zone area where our code base will change..20:13
sdake_zwe have this directory called resources20:13
sdake_zit contains things that launch vms, eips, etc.20:13
sdake_zit contains something called nested stacks - ie: RDS20:13
sdake_za relational database service20:13
*** AlanClark__ has quit IRC20:13
sdake_zwe would prefer those not be nested stacks and instead use openstack apis where avialable20:14
*** AlanClark__ has joined #openstack-meeting20:14
*** shardy has joined #openstack-meeting20:14
sdake_zatm there are no openstack apis for rds but if there are, we will merge to use those apis20:14
sdake_zthere are other resource types as well20:14
russellbso to be clear, in the absence of a db service, you have code that knows how to set up an instance with a database on it, that kind of thing, right?20:14
sdake_zload balancer20:14
sdake_zright20:14
russellbk20:14
sdake_zbut those are not major architectural changes, only changes in how we interface with openstack20:15
ttxmakes sense20:15
russellbbut you want to kill those off when an API is available ... makes sense20:15
ttxother questions on technical stability and architecture maturity, before we talk about the scope ?20:15
sdake_zwould like to do so yes - and add more resources as projects like moniker hit the wire20:15
markmcwhat's the story with the cloudwatch impl?20:15
heckjsdake_z: does the architecture support switching those out without major rewrites as new things come available?20:15
markmcis there a deprecation plan?20:15
ttxs/as/if/20:15
markmcor is it already optional and you can use another implementation?20:15
sdake_zyes, each resource is a .py file20:15
sdake_zwith a standard programming api20:16
shardymarkmc: we plan to move to using ceilometer when the features we need are there20:16
markmcshardy, will there be much work to make that move?20:16
heckjsdake_z: thanks20:16
markmcshardy, they should be compatible, so no major user impact right?20:16
sdake_zre cloudwatch, want to remove it from the code base as soon as ceilo is in place, have had discussions with ceilo team about alerting and that seems positive20:16
markmccool20:17
shardymarkmc: There will be a bit of rework in the engine to decouple things, but nothing major, no20:17
markmchow about the metadata server, heat still has its own read/write server?20:17
shardymarkmc: I've been putting off that rework waiting for the ceilo stuff to be ready20:17
shardymarkmc: No, all resource metadata is now served via the CFN or ReST API20:18
shardywe removed the metadata server20:18
sdake_zthe metadata server would disappear once ceilo is in20:18
gabrielhurleyhow do you determine which resource modules to use? do you use keystone's service catalog, or config flags, or...?20:18
sdake_zgabrielhurley not sure i understand question20:18
gabrielhurleyyou were talking about trading out resource .py modules20:18
sdake_zshardy I think markmc was tlaking about cloudwatch server process20:18
gabrielhurleyif there are competing implementations, how do you determine which ones to use?20:19
markmcno, I was asking about the metadata server that at one point you wanted to use nova's metadata server20:19
markmcbut the issue was that it was readonly20:19
shardysdake_z: well he mentioned CW then metadata - the CW stuff is in progress, but the separate metadata service has been removed now20:19
sdake_zgabrielhurley there is a name space - for example OS::HEAT::Reddwarf20:19
markmcthe server that e.g. cfn-trigger or whatever talks to?20:19
* markmc waves hands20:19
jd__hi20:20
sdake_zeach resource.py contains the namespace resource it is responsible for20:20
shardymarkmc: It all talks to either the CFN or Cloudwatch API now, there is no heat-metadata anymore20:20
*** sandywalsh has joined #openstack-meeting20:20
shardywhich means everything is authenticated/signed20:20
markmcshardy, ok, thanks20:20
gabrielhurleysdake_z so the resource files are namespaced for each impementor, but how do you determine which one to use? I'm trying to understand if this is an "operator must configure" or "dynamically determine what's available" situation.20:20
sdake_zgabrielhurley you put in the template file which resource you want to use and which parameters you want to pass it20:21
shardygabrielhurley: there is a mapping of class name to template name in each resource implementation20:21
gabrielhurleywhat happens if I (as an end user) put in my template a resource which is not available20:21
markmcgabrielhurley, I don't think there are any competing implementations of a single resource type atm20:21
gabrielhurleyor worse, a resource which is available from a different implementor20:21
sdake_zgabrielhurley you get a parse error if there is no resource available20:21
shardygabrielhurley: I'd expect template validation to fail20:22
sdake_zin the example of databases...20:22
*** Yada has joined #openstack-meeting20:22
gabrielhurleyokay. that's what I was trying to understand. I think that architecture is gonna need more work as the ecosystem expands, but that's fine for now.20:22
sdake_zok sounds good ;)20:22
ttxany more questions before we discuss scope ?20:22
shardygabrielhurley: the resource implementations are pluggable now, so the architecture is extensible20:23
*** dhellmann-afk is now known as dhellmann20:23
ttx#topic Scope complementarity, Heat20:23
*** openstack changes topic to "Scope complementarity, Heat (Meeting topic: tc)"20:23
ttxIn this section I'd like to discuss the desirability of integrate Ceilometer in the common OpenStack Havana release20:24
ttxWe don't really have name guidelines yet that define what is off-limits for "OpenStack" resource focus20:24
markmcyou mean Heat :)20:24
eglynns/Ceilometer/Heat/20:24
mordreds/Ceilomter/Heat/20:24
gabrielhurleylol20:24
russellbs/Ceilometer/Heat/20:24
ttxoops20:24
markmcheh20:24
ttxSo at this point we can only apply technical guidelines20:24
ttxIs the project complementary in scope, or overlapping with others ?20:24
ttxAre there other projects in our community covering the same scope ?20:24
ttxDoes it integrate well with current integrated projects ? Does it form a coherent product ?20:24
ttx(that's what you get by reshuffling me)20:24
sdake_zwe are only project in this space inside incubation/core20:24
sdake_zintegrates extremely well with other projects including full keystone auth20:25
notmynamettx: "does it forma conherent product" get's into openstack in-general guidelines, not technical things20:25
sdake_zas far as coherent product, again, i'd like to see the rds and autoscaling and other features come out of heat into other projects so we could use those directly20:25
ttxpersonally I place it in the same category as Horizon, an integration point20:25
ttxnotmyname: true20:25
markmcas a service which pulls together our APIs, I love it20:26
markmcit's a pretty natural expansion of scope, I think20:26
mordred++20:26
ttxnotmyname: for some pretty large definition of "coherent"20:26
markmcobviously, one of our largest competitors has something similar20:26
mordredhehe20:26
gabrielhurleyit provides a functionality which a lot of openstack consumers are clamoring for... but it's definitely an expansion more than a compliment.20:26
markmcand there's a lot of interest in application level orchestration20:26
*** radez_g0n3 is now known as radez20:26
mordredfwiw, we also had conversations with rob at dell about ways that heat can be complimentary to crowbar20:27
annegentlehow much do changes to the OpenStack APIs affect Heat's templates? Are templates versioned somehow?20:27
* annegentle wonders about integrated releases20:28
sdake_zannegentle we generate a version against a specific version of openstack - ie heat for havana integrates against havana apis20:28
vishymy crowbar, you are looking fine today...20:28
mordredvishy: :)20:28
markmcheh20:28
shardyannegentle: but changes in the service api's heat uses will not change the template syntax (unless you're using a new feature specific to a release, e.g the new Quantum based resources)20:29
ttxmore questions on scope ?20:29
gabrielhurleysdake_z: one of openstack's goals is to be version N-1 compatible. how does Heat feel on that front?20:29
ttxit feels the heat20:29
sdake_zwe follow openstack processes - so that seems reasonable20:29
annegentleshardy: sdake_z ok, thanks20:30
gabrielhurleycool20:30
sdake_zalthough atm that is not implemented in the architecture20:30
sdake_zgabrielhurley i would expect python-* libs to be backwards compatible for the most part though so should be straightforward20:31
gabrielhurleysdake_z: you'd think that, wouldn't you. ;-)20:31
heckjheh20:31
mordredgabrielhurley: :)20:31
sdake_znaive i guess :)20:31
gabrielhurleyyou'll learn :-D20:31
ttxsee why I put horizon and heat in the same bag, they are already forming a group20:31
shardygabrielhurley: sorry, do you mean python version?20:31
gabrielhurleyshardy: no, openstack release version20:32
shardygabrielhurley: k, thanks20:32
ttx#topic Final Q&A and vote, Heat20:32
*** openstack changes topic to "Final Q&A and vote, Heat (Meeting topic: tc)"20:32
ttxFinal questions/discussion before we vote on Heat graduation ?20:32
ttxdoubts, objections...20:33
annegentleo/20:33
annegentleone more Q, are you documenting your own API somewhere?20:33
sdake_zthat needs to be done - although there is some basic docs already in the source tree20:33
sdake_zbut they need love20:33
sdake_zwe should speak offline about your expectations re documentatoin20:33
sdake_zso we can deliver what you want20:34
annegentlesdake_z: yes and I want to be sure we meet user expectations for docs20:34
ttxother final questions ?20:34
danwenti think something like heat is very valuable.  To me the only question is whether it makes sense to put one such template/orchestration approach as the "official" one.20:34
* mordred registers his support for both the concept and the codebase20:34
annegentlesdake_z: is the size of the API like "16 calls" -- basically CRUD on templates? Want a ballpark20:34
danwentif no one has concerns, I think the team has done a great job building heat and integrating, so i'm generally supportive20:35
sdake_zI believe 9 - just  a guess tho20:35
mordredespecially since we've got projects moving towards figuring out how to integrate other orchestration system with heat, rather than just competitive20:35
annegentlesdake_z: ok thanks, yeah that sounds right20:35
ttxok, ready to vote ?20:35
mordredso from my end, it doesn't seem like adding heat will block other things from playing in the ecosystem - but rather will enable things20:36
mordred(that's related to danwent's concern above)20:36
danwentmordred: i agree, as long as others see it that way as well.20:36
ttx#startvote Approve graduation of Heat (to be integrated in common Havana release)? yes, no, abstain20:36
openstackBegin voting on: Approve graduation of Heat (to be integrated in common Havana release)? Valid vote options are yes, no, abstain.20:36
openstackVote using '#vote OPTION'. Only your last vote counts.20:36
markmc#vote yes20:37
mordred#vote yes20:37
russellb#vote yes20:37
gabrielhurley#vote yes20:37
ttx#vote yes20:37
jgriffith#vote yes20:37
danwent#vote yes20:37
heckj#vote abstain20:37
notmyname#vote no20:37
ttx30 more seconds20:38
annegentle#vote yes20:38
gabrielhurleyttx: in general, it might be good to ping people at the start of a vote20:38
ttxhmm20:39
gabrielhurleyfor those who aren't looking at IRC, it's not always apparent that a timed vote is happening20:39
ttxwho are we missing20:39
danwentgabrielhurley: do you mean you're not hanging on every word of the discussion? :P20:39
russellbvishy: ping20:39
* annegentle sets up a notification for vote :)20:39
ttxjaypipes, vishy ^20:39
gabrielhurleybcwaldon: ping20:39
*** dwchadwick has left #openstack-meeting20:39
vishy#vote yes20:39
bcwaldonI'm looking!20:39
gabrielhurleylol20:39
heckjheh20:39
gabrielhurleytick tock20:39
bcwaldon#vote yes20:39
ttxok, 10 more seconds20:40
ttx#endvote20:40
openstackVoted on "Approve graduation of Heat (to be integrated in common Havana release)?" Results are20:40
jaypipes#vote yes20:40
openstackyes (10): markmc, bcwaldon, ttx, vishy, annegentle, russellb, jgriffith, mordred, gabrielhurley, danwent20:40
openstackabstain (1): heckj20:40
openstackno (1): notmyname20:40
ttxjaypipes: :P20:40
gabrielhurleyjaypipes: just missed it ;-)20:40
jaypipesyeh, sorry, on yet another call :(20:40
ttxsdake: congrats20:40
ttx#topic Technical stability and architecture maturity assessment, Ceilometer20:40
*** openstack changes topic to "Technical stability and architecture maturity assessment, Ceilometer (Meeting topic: tc)"20:40
markmccongrats sdake_z, shardy and co.20:40
sdake_ztx - blame the developers ;)20:41
*** lglenden_ has joined #openstack-meeting20:41
eglynn#link https://wiki.openstack.org/wiki/Ceilometer/Graduation#Is_our_architecture_stable.3F20:41
ttxso... making sure that (1) the project is currently usable and (2) the architecture is now stable (no full rewrite needed during Havana cycle)20:41
ttxDuring the Grizzly cycle, Ceilometer appeared to adapt its architecture to external pressure from new consumers20:41
dhellmannttx, we made incremental changes but nothing major20:41
* mordred has to drop off for a plane flight ... thinks ceilometer is great20:42
ttxBut the linnked doc explains the architecture is now pretty flexible and shouldn't change, iirc20:42
eglynnwe could see that pressure as a positive (connoting a healthy, sustainable community attracting wide interest)20:42
ttxcertainly20:42
jd__thanks mordred :)20:42
* gabrielhurley appreciates that ceilometer has pushed to move useful functionality into oslo20:42
notmynameI'm concerned that CM is generating monitoring data but claiming usefulness for billing calculations20:42
heckjgabrielhurley: +120:43
* annegentle will be back shortly20:43
eglynnnotmyname: we want that data acquisition for metering and monitoring to shared infrastructure20:43
notmynameeglynn: but they have very different requirements20:43
notmynameeglynn: specifically, you must be able to reliably recreate your numbers when used in a billing context20:44
*** rellerreller has quit IRC20:44
*** lglenden has quit IRC20:44
eglynnyes and the architecture is intended to be flexible enough to address these differing requirements20:44
gabrielhurleywhat I've heard from the ceilometer team is that they're doing metrics, and if some people try to use that for billing that's their choice (or folly, if you prefer)20:44
notmynameand the logs are the persistent source of those numbers, but you are simply using messages sent in the course of the request20:44
dhellmannnotmyname: and polling, and auditing notifications20:44
* notmyname has mostly looked at the swift parts, since that's what I know20:45
eglynnnotmyname: we have a multi-publish framework that allows measurements for different backends to travel via different conduits20:45
eglynnnotmyname: so for example for metric, trade off currency versus completeness20:45
eglynnnotmyname: for metering/billing ... do the opposite trade-off20:45
eglynnnotmyname: the idea is not to force the metrics and metering data to be shoehorned into the same bucket20:46
eglynn(with the exact same QoS etc.)20:46
notmynameeglynn: is CM an aggregation point for whatever metering/etc you are using (like keystone for auth, cinder for blocks)?20:47
*** annegentle has quit IRC20:47
eglynnnotmyname: yes, CM can acquire and aggregate measurements from many different source including the one you mention20:47
*** agentle_ has joined #openstack-meeting20:47
eglynnnotmyname: and also publish to different backends20:48
eglynnnotmyname: e.g. one backend would be the CM metering store20:49
eglynnnotmyname: another would be the future CW service20:49
eglynn(i.e. the integrated Synaps engine)20:49
notmynamewhat backends do you provide as part of the code today?20:49
eglynnnotmyname: just one, the CM collector/metering store/CM API service20:50
eglynnnotmyname: but the archiecture was specifically evolved during G to accomodate others20:50
*** Vek has joined #openstack-meeting20:50
notmynameand so, eg, if you wanted something for correctness (like billing), you'd provide your own?20:50
eglynnnotmyname: well we envisage the metering store mentioned above would be suitable for that purpose20:51
eglynnnotmyname: (i.e. we don't throw metering data on the floor, though another backend might do sample or discard delayed data etc.)20:52
notmynamewhat scale has it been tested at?20:52
jd__it's actually already used by some to do that, like DreamHost20:52
eglynnnotmyname: its currently deployed in DreamHost20:52
eglynndhellmann can speak to the scale there20:53
dhellmannour current cluster is fairly small20:53
notmynamesmall == 100s req/sec? 10s req/sec?20:54
notmynameI understand if you can't really share that ;-)20:54
dhellmannI would share, but I don't have those numbers20:54
eglynnwe can agree though that its a non-trivial production deployment, or?20:55
eglynns/agree/surmise/20:55
notmynameif others have questions, please ask. /me is ready to vote20:55
ttxwe need to talk about scope a bit first20:56
dhellmanneglynn: yes, it's a non-trivial deployment, just not seeing a lot of traffic at this point20:56
notmynameya, I know my thoughts there ;-)20:56
ttxany more question on Technical stability and architecture maturity N20:56
ttx?20:56
agentle_are the meters in https://wiki.openstack.org/wiki/EfficientMetering in production?20:56
dhellmannagentle_: yes. a better list is at http://docs.openstack.org/developer/ceilometer/measurements.html20:57
notmynamewhy would you emit volume units not in bytes?20:57
dhellmannIIRC, we've updated the formal docs, and not gone back and updated that design document20:57
*** stevebaker has quit IRC20:57
* agentle_ sighs :)20:57
dhellmannnotmyname: where?20:57
notmynamedhellmann: on agentle_'s link20:58
agentle_mostly I sigh because Google finds the wiki first20:58
dhellmannnotmyname: ok, that's out of date20:58
eglynnagentle_: note that adding a meter is a relatively straight forward task, the archiecture is highly extensible ... so we'd expect that list to grow20:58
agentle_eglynn: yup, understood20:58
heckjhttp://docs.openstack.org/developer/ceilometer/index.html20:58
*** SunSlayer has joined #openstack-meeting20:58
jgriffithnotmyname: Cinder does everything in GB so makes sense to me20:58
ttxlooks like we are running out of time -- I propose we do scope complementarity and vote next week, unless nobody has any question on scope20:58
russellbshould add the up to date link to the top of the wiki page20:58
russellbthat should avoid confusion20:58
dhellmannrussellb: good idea, I'm doing that now20:59
agentle_what is kwapi?20:59
eglynnon units, we rationalized our units usage during G so that its now much more consistent & logical20:59
*** dprince has quit IRC20:59
ttxeglynn: yay incubation.20:59
jgriffith+1 for GiB BTW :)20:59
jd__agentle_: an energy monitoring tool see https://github.com/stackforge/kwapi21:00
ttxok, we'll continue (and finish) the ceilometer review next week, thanks everyone21:00
ttxbig meeting ahead21:00
ttx#endmeeting21:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:00
openstackMeeting ended Tue Feb 19 21:00:24 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-19-20.02.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-19-20.02.txt21:00
notmynamejgriffith: ya, that makes sense if it's your fundamental unit (and well communicated). I've seen lots of confusion and rounding issues when bytes weren't used. I'm happy that the newer list uses bytes (at least for swift)21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-19-20.02.log.html21:00
ttxmarkmc, heckj, notmyname, bcwaldon, jgriffith, vishy, gabrielhurley, danwent: still around ?21:00
jgriffithnotmyname: good point21:00
jgriffitho/21:00
danwento/21:00
markmcyep21:00
gabrielhurleyhi21:01
rainyahihi21:01
heckjurg21:01
notmynamehere21:01
bcwaldonhello!21:01
ttx#startmeeting project21:01
vishyhi21:01
openstackMeeting started Tue Feb 19 21:01:39 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: project)"21:01
openstackThe meeting name has been set to 'project'21:01
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:01
ttx#topic General announcements21:01
*** openstack changes topic to "General announcements (Meeting topic: project)"21:01
vishyttx: i have a cross-project gating concern to bring up21:01
ttxsure, just a sec21:02
vishycan you add it to the agenda?21:02
ttxwe'll do it at the end of general discussion21:02
ttxIf we don't change anything, you have until the end of the day (i.e. tomorrow morning in Europe) to merge features for Grizzly...21:02
*** timello_ has quit IRC21:02
ttxBut given that the gate was not exactly in stellar condition today, looks like some /could/ benefit from pushing back one day21:02
ttxdoes anyone thinnk that would make things better ? There is a lot left on the table right now21:03
vishyttx: my concern relates specifically to that21:03
ttxvishy: ok, then go ahead :)21:03
danwentttx: i'd rather just see more things get a 1-day extension21:03
danwentttx: if we leave the door wide open, i'm not sure the gating will be any better tomorrow.21:03
ttxAt the very minimum one day would help to get all approved stuff processed.21:03
vishyttx: i think we should add a day and temporarily turn off the full tempest run on the gate21:03
bcwaldonit won't affect much from Glance's point of view, but I see it being super-helpful to Nova21:03
vishyit is making the merge cycle too slow21:03
heckjI'd be good with that for the last bit here - it's really been grinding quite a bit21:04
russellbit's been a bit problematic since it was enabled, but amplified this week21:04
ttxvishy: the trick is... are you sure you can reenable it afterwards ? i.e. how to be sure you dodn't break anything ?21:04
ttxjeblair, mordred: ping21:04
vishyttx: we leave it in the check so we will see failures pretty quickly21:04
markmcthe gate does seem to be getting really backed up21:05
markmceven aside from the pypi issues21:05
Vek*nod* indeed21:05
ttxsdague: thoughts ?21:05
sdaguewell, my thoughts are a lot of people showed up out of the woodwork in the last 72 hours to try to get code merged :)21:06
*** maurosr has quit IRC21:06
ttxsdague: indeed. Important stuff shoudl have been merged ages ago21:06
sdagueI generally think it's not a great idea, but I also understand the concern to get stuff merged21:06
vishywe need a longer term solution for improving the gate time, but I'm thinking a temporary fix to get the current backlog cleared would be helpful.21:06
Veksdague: I think that happens for deadlines :)21:06
russellbsdague: but others were saying that it has taken 8 hours to a couple days to get stuff merged even before the last days21:06
*** Mr_T has joined #openstack-meeting21:06
russellbit hasn't *only* been a problem this week21:06
jgriffithrussellb: +121:06
sdaguerussellb: we've been on a big run up the last 2 weeks21:06
*** sdake_z has quit IRC21:07
sdagueit would be good to pull some stats at some point on that21:07
ttxvishy: did you run the idea to the CI folks ? i.e. how doable is it ?21:07
vishyclarkb said it would be pretty easy to temporarily disable / post-run it21:07
sorenIs this because a single Tempest run occasionally takes 8 hours to run or is it because of sequencing of patches or something entirely different?21:07
ttxpersonally I'd much prefer to postpone stuff to H and reduce the number of things that we ahve to process21:07
sdagueoverall I don't like the idea, because I feel like it turns off an important net. But I do get we need to balance it with stuff that needs to get merge.21:07
ttxrather thah turning off checks and praying21:07
vishysoren it is the serialization of patches + 1.5 hours per run21:08
russellbsoren: single run doesn't take that long, but a single failure causes everything behind it to have to run again21:08
markmcif we leave folks feeling their code didn't get merged in grizzly because of the gate ...21:08
markmcvishy's proposal makes sense to me21:08
clarkbwell its possible not necessaroly very easy. we would have to stop zuul to reload its config21:08
vishymarkmc: right that is my concern21:08
clarkbjeblair ^21:09
sorenrussellb: I know it doesn't *usually* take that long. I just wondered if it occasionally did. IOW whether this was a tempest problem.21:09
ttxok. let's not spend the whole meeting discussing that21:09
russellbsoren: *nod*  sorry for stating obvious :)21:09
vishythere is stuff that has been churning back and forth and i would hate to postpone it for gate reasons21:09
*** johnpur has joined #openstack-meeting21:09
Vekgoing forward, perhaps that's something that should be run only on a regular basis on the tree?  i.e., nightly, we run that set of tests and log bugs for any errors that crop up?21:09
ttxlet's discuss this in #openstack-dev after this meeting21:09
ttxin all cases we add a day ?21:09
davidkranzThere is a tempest hourly build. If folks acted like that breaking was the same as a gate failure for urgency, that could be a compromise.21:09
markmcwe could just be more open to FFEs of course21:09
ttxShit *will* happen on the last day, whenever that last day is.21:09
sdaguedavidkranz: we turned off the hourly21:09
sdagueto save CI resources21:09
davidkranzsdague: Heh.21:10
sdaguebecause we had the gate21:10
davidkranzsdague: We could reverse that temporarily.21:10
ttxplease. Let's discuss that in 50min in #openstack-dev. We have lots of ground to cover in meeting21:10
ttx<ttx> in all cases we add a day ?21:10
vishyyes21:11
russellb+1 for adding a day imo, fwiw21:11
ttxok21:11
gabrielhurley+121:11
ttx#info Feature Freeze pushed back to EOD Wednesday, Feb 2021:11
*** matiu_ has joined #openstack-meeting21:11
*** matiu_ has joined #openstack-meeting21:11
ttx#info Starting Thursday, only features granted a FeatureFreeze exception should be approved.21:11
ttxIn this meeting we'll review the remaining open blueprints and see if they should be granted an exception if they fail to make it tomorrow21:11
ttxSo it's time to be strong and start saying "no".21:11
markmcnoooooo21:11
ttxmarkmc, mordred, annegentle, sdague/davidkranz/jaypipes: quick updates from Stable/CI/QA/Docs teams ?21:12
agentle_Book Sprint Next Week!21:12
ttxDiscussion on opportunity to turn off some gate tests at 22:00 UTC in #openstack-dev21:12
markmcnothing to report from me on stable, 2012.2.4 scheduled for 2013-04-1121:12
ttxgreat, thx21:12
*** johnpur has left #openstack-meeting21:13
ttx#topic Oslo status21:13
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:13
ttx#link https://launchpad.net/oslo/+milestone/grizzly-321:13
ttx2 open blueprints:21:13
ttxcfg-move-opts-between-groups21:13
ttxadvanced-matchmaking21:13
markmcthe first will definitely make it, it's basically got 2 +2s21:13
markmcthe second I'm behind on21:13
markmcthere is a patch, some concerns about testing21:14
ttxshould the other just be deferred to H if it fails to make it in time ?21:14
markmcit would be a fine FFE, unlikely to impact anything else21:14
markmcand has been in the works for quite a while21:14
markmcslow reviewers was mainly the problem (including me)21:14
*** matiu_ has quit IRC21:14
ttxI'm reluctant with FFEs in oslo libraries21:14
russellbthat one will only affect zmq rpc driver21:14
russellbso i think it's ok for FFE21:14
markmcnow, there is the question of ...21:15
*** timello_ has joined #openstack-meeting21:15
ttxmarkmc: how much time do you need ?21:15
markmccode getting into oslo-incubator doesn't mean the code is synced to projects yet21:15
russellbtrue story.21:15
markmcttx, I can probably make a call on it tomorrow21:15
ttxmarkmc: ^ that's what I mean by being reluctant with oslo FFEs21:15
markmcthe other oslo thing21:15
ttxyou still need to sync the code in21:15
markmcis making projects use oslo-config21:15
markmchttps://review.openstack.org/#/q/I4815aeb8a9341a31a250e920157f15ee15cfc5bc,n,z21:15
markmcnova, glance and cinder patches all still need to be merged21:16
markmcbeing bitten by gate issues and lots of conflicts21:16
markmcshould make it tomorrow21:16
ttxmarkmc: ok, would be great to get them in gate tomorrow :)21:16
ttxLooking at g3-targeted bugs, 1 bug left. Is it G3-critical, or should it be moved to the RC1 buglist ?21:17
markmcyeah, I must ping mikal about that21:17
ttx(or deferred ?)21:17
markmcit's probably not all that critical21:17
heckjBTW: making projects use oslo-config for the venv setup is a real PITA21:17
ttxAnything else on the oslo topic ?21:17
heckjmerged that in this morning, and it promptly bit us hard21:17
markmcheckj, how do you mean?21:18
heckjYou need oslo-config to run the process which installs the project depedencies.21:18
*** sleepsonthefloor has quit IRC21:18
*** kmartin has quit IRC21:18
heckjchicken and egg kind of issue21:18
gabrielhurleythat ^^21:18
markmcah21:18
markmcyeah, that caught me by surprise21:18
* markmc isn't even sure why it's using cfg21:18
markmcwill investigate21:18
heckjmarkmc: I'll find the specifics and ping you separately21:19
markmcit's not used by jenkins21:19
markmcsince everything is tox21:19
markmcthat's what I tested with too21:19
ttxok21:19
markmcheckj, thanks21:19
ttx#topic Keystone status21:19
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:19
ttxheckj: o/21:19
ttx#link https://launchpad.net/keystone/+milestone/grizzly-321:19
ttxA lot of stuff still in progress here...21:20
heckjheyoo21:20
ttxGiven recent progress I'm not really convinced giving it a few more days will get them all merged...21:20
ttxWhat do we absolutely need to have in grizzly release to make it coherent ?21:20
heckjactually, I'm pretty confident about all but the trusts piece21:20
ttxconfident as in... merging today ?21:21
heckjThe final reviews have been chugging through nicely, and all the devs are in sync21:21
heckjyeah, as in merging today21:21
ttxgood news21:21
heckjtrusts… well, here's the hat coming out21:21
heckjI'd like to ask for a featurefreeze extension for trusts21:21
ttxhow much time do you need ?21:21
heckjayoung was asking for end of the week earlier21:22
heckj(friday)21:22
ttxI'm ready to grant anything... just need to be convinced that it will make it. Been promised this for "the end of the week" quite a few times alareday21:22
ttxalready21:22
heckjayoung - you here to speak on your coding behalf?21:22
heckj(he was very head's down earlier today)21:22
ttxalso that's only if the rest really makes it, obviously :)21:23
heckjyep21:23
ttx#infor considering FFE for trusts21:23
ttxYou also have two in the grizzly series without milestone set:21:23
ttxdomain-name-spaces and domain-scoping (completed?)21:23
ttxwhat about them ?21:23
Vekttx: s/#infor/#info/21:24
ttx#info considering FFE for trusts21:24
ttxVek: thanks21:24
Vekwelcome.21:24
heckjboth are going in with the final bits of authn for V321:24
heckjwhich we're expecting merged this afternoon21:24
ttxheckj: ok, I see.21:25
heckjmost of it was already there, just pending the auth side of it21:25
ttxLooking at targeted bugs, 5 bugs on list. Should any of those be fixed in G3, or can I move them all to the RC1 buglist ?21:25
heckjall can be safely moved to the RC1 buglist21:25
ttxok thx21:25
ttxAnything more about Keystone ?21:25
heckjthat's it from me21:26
ttx#topic Swift status21:26
*** openstack changes topic to "Swift status (Meeting topic: project)"21:26
ttxnotmyname: o/21:26
ttx#link https://launchpad.net/swift/+milestone/1.8.021:26
ttxLet's make it quick ;) Is 1.8.0 starting to crystallize ?21:26
notmynameya, we're fine, AFAIK21:26
ttxsometimes in first half of March ?21:27
notmynamewhat's the final date for inclusion on grizzly?21:27
notmynamewe'll cut the release when it's ready. I'm still anticipating mid-march21:27
ttxThe first RCs are expected in first half of March21:27
notmynameok21:27
ttxnotmyname: Anything you wanted to mention ?21:27
notmynamenothing omes to mind21:28
ttx#topic Glance status21:28
*** openstack changes topic to "Glance status (Meeting topic: project)"21:28
ttxnotmyname: thx21:28
ttxbcwaldon: o/21:28
ttx#link https://launchpad.net/glance/+milestone/grizzly-321:28
bcwaldonttx: hey!21:28
rainyalalalalala21:28
bcwaldonrainya: you're on thin ice21:28
ttxlooks like this was trimmed down21:28
bcwaldonttx: yes, actively working on it21:28
ttx4 blueprints left21:29
bcwaldonttx: I want an FFE for image locations and image sharing21:29
*** kmartin has joined #openstack-meeting21:29
bcwaldonthe domain logic bp has one patch left that markwash won't let me see21:29
bcwaldonand common image properties is in review21:29
ttxbcwaldon: how much time do you need for those two ?21:29
bcwaldonttx: well, that's hard to answer21:29
bcwaldonttx: image sharing has several reviews up, so I expect that to be early next week at the latest21:30
bcwaldonttx: image locations is dependent on me not being lazy tonight21:30
*** adjohn has quit IRC21:30
bcwaldonbut I would give that the same target21:30
ttx#info FFEs for glance-api-v2-image-sharing and multiple-image-locations21:30
bcwaldonyes21:30
ttxall the rest will be deferred if it doesn't pass the deadline tomorrow21:30
bcwaldonalready did so for a couple of bps21:31
bcwaldonthose bugs can bump to rc1 too21:31
ttxsaw that. Thanks21:31
ttxall bugs can bump ? ok.21:31
ttxincluding bug 1102476 ?21:31
uvirtbotLaunchpad bug 1102476 in glance "Latest json-patch draft (10) is incompatibile with Images API v2 implementation" [Critical,Triaged] https://launchpad.net/bugs/110247621:31
bcwaldonttx: to rc121:31
bcwaldonor am I thinking of things incorrectly21:32
ttxAnything more on Glance ?21:32
bcwaldonnot from me21:32
ttx#topic Quantum status21:32
*** openstack changes topic to "Quantum status (Meeting topic: project)"21:32
ttxdanwent: hi!21:32
ttx#link https://launchpad.net/quantum/+milestone/grizzly-321:32
danwenthello21:32
danwentdo i need to remind you?21:32
ttxno I read21:32
danwent:)21:33
ttx3 High stuff21:33
ttxlbaas-namespace-agent21:33
ttxlbaas-haproxy-driver21:33
ttxmultiple l3 and dhcp agents21:33
ttxwhich ones do you need FFEs for ?21:33
danwentI do not expect to need an FFE for the l3/dhcp agents one21:33
danwentwe will need one for the lbaas blueprints.21:34
ttxdanwent: you mean, should make it in time ?21:34
danwentttx: yes, should make it by tonight21:34
ttxI'll yell if it doesn't21:34
danwenti'm still planning on closing gate to non-high blueprints tonight21:34
danwentwe've already had too much last minute stuff thrown in21:34
ttx#info FFe for lbaas-namespace-agent / lbaas-haproxy-driver21:34
danwentand I don't want to encourage it more :)21:34
ttxyes.21:35
ttxThe remaining ones are all Medium/Low, should be deferred to H if they don't make it tomorrow.21:35
danwentwe also have an important nova blueprint that I want to highlight21:35
danwenthttps://blueprints.launchpad.net/nova/+spec/nova-quantum-security-group-proxy21:35
danwentvishy and markmc have been giving it love though, so hopefully its in good shape21:35
ttx21 bugs in your g3-targeted buglist. Should any of those be fixed in G3, or can I move them all to the RC1 buglist ?21:35
ttxWe'll have a short G3 gestation period due to pushing back FF one day21:36
danwentthat's what i'm figuring out today.  will work with markmclain, our bug master on that21:36
danwentwell, quantum will have a bonus bug day then :P21:36
ttxdanwent: could you keep me posted on that ?21:36
danwentttx: on moving bugs out of g-3?21:36
ttxyeah. or move them all to RC121:37
ttx(the milestone was created)21:37
danwentyes sir.  will do it today.  some bugs have already been moved over.21:37
ttxI need to know if I should block on it21:37
ttxAnything else on Quantum ?21:37
danwenti'm not aware of any blockers21:37
danwentbut will recheck21:37
danwentnope21:38
*** sarob has joined #openstack-meeting21:38
ttx#topic Cinder status21:38
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:38
ttxdanwent: thx!21:38
ttxjgriffith: hi!21:38
ttx#link https://launchpad.net/cinder/+milestone/grizzly-321:38
jgriffithhello21:38
jgriffithShould be good21:38
ttxlet's see, 7 left21:38
jgriffithespecially with another day21:38
jgriffiththingee will likely have the two docs ones tonight21:38
jgriffithI'll have snap meta finished tonight as well21:39
jgriffithThe others just need to get through the gates and rebasing21:39
ttxwhich ones should get an FFe if by pure lack of luck they don't make it ?21:39
*** johnpur has joined #openstack-meeting21:39
jgriffithMaybe just snapshot-meta AFAIC21:39
* ttx 's best friend is called Murphy21:39
jgriffithAnd the Fibre Channel21:39
jgriffithOh... backups21:40
jgriffithcrap21:40
*** adjohn has joined #openstack-meeting21:40
Vekbest friend.  Worst enemy.  same difference...21:40
jgriffithOk... those three, but that's it!21:40
ttxjgriffith: if you end up needing more than one I'll shoot the others randomly21:40
jgriffithBut I expect them all to make it in on their own21:40
*** stevebaker has joined #openstack-meeting21:40
jgriffithK21:40
*** eglynn_ has joined #openstack-meeting21:41
ttx#info preemptive FFe for volume-backups update-snap-metadata fibre-channel-block-storage, if only one is needed21:41
jgriffithttx: thx21:41
ttx#info preemptive FFe for volume-backups update-snap-metadata fibre-channel-block-storage, if only one is neededit21:41
ttxarh21:42
Vekheh.21:42
ttx1 bug in the targeted bug list21:42
*** eglynn has quit IRC21:42
jgriffithyeah, thingee is on it21:42
jgriffithShould be done tonight21:42
ttxok21:42
ttxAnything more in Cinder ?21:42
jgriffithNope21:42
ttx#topic Nova status21:42
*** openstack changes topic to "Nova status (Meeting topic: project)"21:42
ttxvishy: o/21:42
ttx#link https://launchpad.net/nova/+milestone/grizzly-321:43
vishyhi21:43
ttxOK, so which one(s) of the remaining stuff would you ask an FFe for if they fail to make it tomorrow ?21:44
vishyok so going down the list21:44
vishyreal unique keys I don't know if we can mark complete if the next patch merges since there are more unique keys we need21:44
vishythe api-samples additions we should just target to rc-121:45
ttxno, just defer it to havana for more unique keys work21:45
*** cp16net is now known as cp16net|away21:45
russellbvishy: seems like something we could just re-scope and call "complete", and open a new bp for what we want to get done in havana21:45
vishythey are testing additions so they don't need feature freeze21:45
sdaguevishy: yeh, I was talking with boris, it's one of 1021:45
vishyrussellb: that is fine with me21:45
sdague#2 and #3 are testing21:45
ttxrussellb: ++21:45
ttxvishy: +121:45
vishysdague: i notice that his tests actually failed21:45
vishymigration testing sdague thoughts on that one?21:46
sdaguevishy: I added a new test in boris's code, we need to resolve something21:46
vishyif we can't get https://blueprints.launchpad.net/nova/+spec/nova-quantum-security-group-proxy in by tomorrow i think an ffe is reasonable21:46
sdaguevishy: I'd say we've got about 50% of the interesting cases covered21:46
ttxpowervm-compute-resize-migration is marked completed but has https://review.openstack.org/#/c/22243 open21:46
sdagueI figured the rest we could get after g-3 as it's test additions21:46
ttxnova-quantum-security-group-proxy21:46
vishysdague: ok so migration testing is rc1 also21:47
ttx#info ffe for nova-quantum-security-group-proxy21:47
russellbi think the quantum one is FFE worthy21:47
*** rnirmal has quit IRC21:47
sdaguethe quantum one is big, so it should have eyes if it's getting an FFE21:47
vishyi think this one is also worthy of an ffe if it doesn't make it: https://blueprints.launchpad.net/nova/+spec/default-rules-for-default-security-group21:47
vishyalthough that one probably will make it21:47
sdaguevishy: +1 to the last one, but I think it's just about in21:47
ttx#info FFE for default-rules-for-default-security-group (if needed)21:48
vishyutilization i think we decided to push21:48
ttxvishy: anything else ?21:48
vishythe fibre channel one will make it21:48
vishyit just got owned by gating twice21:48
vishythe hotplug one is close21:48
vishyrxtx should be in21:48
ttxowned by gating.21:48
ttxvishy: 9 bugs in your g3-targeted buglist. Should any of those be fixed in G3, or can I move them all to the RC1 buglist ?21:49
ayoungI'm here....and yes, I was heads down21:49
vishyso i think we're good21:49
vishylooking at bugs21:49
ttxbug 1130146 is critical21:49
uvirtbotLaunchpad bug 1130146 in nova "Unit tests broke with recent commit" [Critical,In progress] https://launchpad.net/bugs/113014621:49
*** tongli has quit IRC21:49
russellbthe critical one has approved patches21:49
russellbin line to merge ...21:49
ttxayoung: how much time do you need for trusts21:49
Vekthe ultimate bug is in testr, though, I think.21:50
russellbVek: ah, well workaround in line to merge at least21:50
Vekalthough what's merging covers legitimate bugs.21:50
ttxvishy: ok, so review the bugs and defer to RC1 anything not g3-critical21:50
vishyk21:50
*** dolphm has quit IRC21:50
ttxvishy: powervm-compute-resize-migration is marked completed but has https://review.openstack.org/#/c/22243 open21:50
russellblooks like it is completed21:51
ayoungttx, We are close....It depends on how brutal dolph is in the code reviews21:51
russellband that is just a bug fix21:51
ttxrussellb: ok21:51
* russellb approves21:51
ttxAny question on Nova ?21:51
ttx#info FFE for keystone/trusts, but need to be completed this week21:52
ayoungttx, right now, it is rebased behing the v3 api fix.  I'd like to say a day.21:52
ttx#topic Horizon status21:52
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:52
*** kspear has joined #openstack-meeting21:52
ttxgabrielhurley: hey21:52
ttx#link https://launchpad.net/horizon/+milestone/grizzly-321:52
gabrielhurleyhi21:52
ttxOnly quantum-lbaas left21:53
gabrielhurleyyep21:53
gabrielhurley:-D21:53
*** martine has quit IRC21:53
ttxwould you require an FFe for that if it misses the deadline tomorrow ?21:53
gabrielhurleyprobably not21:53
gabrielhurleythe code there will likely be ready in time for the deadline21:53
ttxok21:53
gabrielhurleybut it depends on Quantum finishing their haproxy plugin code21:54
ttxwell, they requested an FFe for that21:54
ttxso it's a bit unlikely to make it21:54
danwentttx: hey...21:54
gabrielhurleyyeah, I'm not really sure what to do about it21:55
gabrielhurleywhether it's better to make the Horizon BP an FFE contingent on the Quantum FFE, or what...21:55
danwentgabrielhurley: if its not ready, we can live with cli only for lbaas21:55
ttxdanwent: +121:55
ttxgabrielhurley: Still have 8 bugs targeted to grizzly-3. Can I move to RC1 any that doesn't get merged by tomorrow ? Or is there anything in particular you'd rather see fixed in grizzly-3 ?21:56
gabrielhurleyI'm not gonna merge it until I get the OK from danwent so let's discuss it again when they get their FFE request in21:56
gabrielhurleyttx: rc1 is fine for bugs21:56
danwentgabrielhurley: ok, i will keep you in the loop.  thursday is our next touch point on lbaas.21:56
ttxgabrielhurley: means you need an ffe for quantum-lbaas21:57
gabrielhurleyapparently so21:57
ttx(it won't land in g3)21:57
gabrielhurleysorry, I'm multi-tasking horribly right now21:57
ttx#info FFe for quantum-lbaas21:57
ttxAnything more on Horizon ?21:57
gabrielhurleynope. got a ton of great stuff merged lately, so that's awesome.21:57
ttx#topic Incubated projects21:58
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:58
ttxAnyone from heat/ceilometer ?21:58
sdakehi21:58
ttx#link https://launchpad.net/heat/+milestone/grizzly-321:58
*** pcm_ has quit IRC21:58
sdakeall green21:58
*** markvoelker has quit IRC21:58
ttxcool21:58
sdake~10 bugs in rc121:59
ttxneed to figure out if the tarball generation is up to par21:59
ttxlast time I checked it was... different21:59
sdakei merged your patch this morning21:59
ttxok21:59
sdakeand merged a version patch21:59
sdakeso hopefully that fixes it21:59
ttxyeah, might have fixed it21:59
ttxanyone from ceilo ?21:59
ttx#link https://launchpad.net/ceilometer/+milestone/grizzly-321:59
*** cp16net|away is now known as cp16net22:00
eglynn_circa 4 bugs that will have to retarget'd at RC1 I think22:00
ttxeglynn_: What should I do with anything that is not completed by tomorrow ?22:00
eglynn_one BP also in danger of not making it22:00
eglynn_ttx: the one BP just started probably won't involve any code landing22:01
eglynn_(a pure testing task)22:01
eglynn_the outsanding bugs will be retargeted at RC1 if they're not complete tmrw22:01
ttxeglynn_: ok, i'll just defer to H anything that doesn't make it, unless you tell me otherwise22:01
ttx(for blueprints)22:01
ttxand that's all we have for time22:02
eglynn_ttx: sounds reasonable22:02
*** jhenner has joined #openstack-meeting22:02
ttx#endmeeting22:02
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:02
openstackMeeting ended Tue Feb 19 22:02:06 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-02-19-21.01.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-02-19-21.01.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-02-19-21.01.log.html22:02
ttxThanks everyone22:02
gabrielhurleythanks ttx22:02
ttxDiscussion on turning off some gate tests in #openstack-dev now22:02
gabrielhurleyand Horizon meeting here22:02
gabrielhurley#startmeeting horizon22:02
openstackMeeting started Tue Feb 19 22:02:46 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:02
*** openstack changes topic to " (Meeting topic: horizon)"22:02
openstackThe meeting name has been set to 'horizon'22:02
*** Vek has left #openstack-meeting22:02
gabrielhurleyI'm gonna keep this as short as possible 'cuz I'm distracted currently22:03
gabrielhurley#General22:03
gabrielhurley#topic General22:03
*** openstack changes topic to "General (Meeting topic: horizon)"22:03
gabrielhurleyPhenomenal work everyone for all the code and reviews in the last two weeks22:03
gabrielhurleyseriously, great work22:03
gabrielhurleywe totally made it22:03
*** gary_th has joined #openstack-meeting22:03
gabrielhurleynow the important thing is to test test test and find/fix bugs22:03
gabrielhurley#topic blueprints and bugs22:04
*** openstack changes topic to "blueprints and bugs (Meeting topic: horizon)"22:04
gabrielhurleyThe only open blueprint is the Quantum LBaaS one, and that's dependent on Quantum getting their FFE22:04
gabrielhurleyso... we'll just sit on that one.22:04
gabrielhurleyBug-wise, I've pared the list in G3 down to things that have assignees22:04
gabrielhurleyI'll roll them forward to RC1 if they're not done in the next day or two22:05
gabrielhurleyAnything you find from here on should go into the RC1 milestone. The goal is to identify release-blocking bugs.22:05
*** garyTh has quit IRC22:06
gabrielhurleyCurrently the only one I see as blocking is https://bugs.launchpad.net/horizon/+bug/1129190 because they were identified as needed improvements on the review for the blueprint22:06
uvirtbotLaunchpad bug 1129190 in horizon "some improvement for network-topology pane" [High,Confirmed]22:06
gabrielhurleybut I'm sure we'll discover more important bugs as we get into the testing phase22:06
gabrielhurleyso it's important to keep a close eye on the bug list22:06
*** eglynn_ has quit IRC22:06
gabrielhurleythat's about all I have.22:06
gabrielhurley#topic discussion22:06
*** openstack changes topic to "discussion (Meeting topic: horizon)"22:07
gabrielhurleyI open the floor to everyone else22:07
*** belliott has joined #openstack-meeting22:07
jpichAre "regular" non-blocker bugs still ok to focus on for fixing, or less important? I'm a bit confused with the different dates (I thought today was code freeze for everything)22:07
gabrielhurleyabsolutely okay22:08
gabrielhurleytoday is code freeze for features22:08
gabrielhurleywell, actually tomorrow now22:08
gabrielhurleythere's been a global +1 day22:08
*** stevebaker has quit IRC22:08
gabrielhurleybugfixes can go in as long as we're rolling RC candidates, but the bar gets higher with each successive RC22:08
gabrielhurleyso in RC1 we can fix anything we feel needs fixing22:09
gabrielhurleyif we do an RC2 it has to be urgent stuff22:09
gabrielhurleyif (heaven forbid) there's an RC3 it's only critical show-stoppers22:09
gabrielhurleyyou get the idea22:09
gabrielhurleydon't count on there being more than an RC122:09
jpichOk, cool! RC1 is March 14th, is it? https://wiki.openstack.org/wiki/GrizzlyReleaseSchedule22:09
* jpich trying to read this right this time22:09
gabrielhurleyI think that's correct22:10
gabrielhurleyseems like a long time, but yeah22:10
jpichCheers :)22:10
*** dontalton has joined #openstack-meeting22:11
*** jhenner has quit IRC22:11
*** SunSlayer has left #openstack-meeting22:11
gabrielhurleygreat22:13
gabrielhurleyokay22:13
gabrielhurleyanything else from anybody?22:13
gabrielhurleycool!22:14
gabrielhurleythanks everyone, same time next week22:14
gabrielhurley#endmeeting22:14
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:14
openstackMeeting ended Tue Feb 19 22:14:24 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-02-19-22.02.html22:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-02-19-22.02.txt22:14
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-02-19-22.02.log.html22:14
jpichEfficient22:14
kspearthanks gabriel22:14
jpichCheers22:14
gabrielhurleyheh22:14
gabrielhurleyI try22:14
gabrielhurleylater y'all22:14
*** gabrielhurley has quit IRC22:14
*** markmc has left #openstack-meeting22:15
*** Mr_T has left #openstack-meeting22:17
*** stevebaker has joined #openstack-meeting22:17
*** lcheng has quit IRC22:18
*** kspear has quit IRC22:19
*** salv-orlando_ has joined #openstack-meeting22:21
*** anteaya has left #openstack-meeting22:21
*** donaldngo_hp has joined #openstack-meeting22:22
*** woodspa has quit IRC22:22
*** markvan has quit IRC22:23
*** salv-orlando has quit IRC22:24
*** salv-orlando_ is now known as salv-orlando22:24
*** kmansel has joined #openstack-meeting22:28
*** stevebaker has quit IRC22:29
*** jhenner has joined #openstack-meeting22:29
*** AlanClark__ has quit IRC22:29
*** AlanClark__ has joined #openstack-meeting22:30
*** nati_ueno has quit IRC22:30
*** Yada has left #openstack-meeting22:33
*** jbr_1 has quit IRC22:33
*** nati_ueno has joined #openstack-meeting22:34
*** shardy has left #openstack-meeting22:35
*** sleepsonthefloor has joined #openstack-meeting22:36
*** nati_ueno_2 has joined #openstack-meeting22:37
*** stevebaker has joined #openstack-meeting22:38
*** jpich has quit IRC22:43
*** afazekas has quit IRC22:48
*** dolphm has joined #openstack-meeting22:50
*** dolphm has quit IRC22:50
*** dolphm has joined #openstack-meeting22:50
*** johnpur has quit IRC22:55
*** soren has quit IRC23:00
*** MarkAtwood has quit IRC23:00
*** soren has joined #openstack-meeting23:01
*** MarkAtwood has joined #openstack-meeting23:02
*** john5223 has quit IRC23:03
*** lglenden_ has quit IRC23:04
*** sarob has quit IRC23:04
*** metral_ has quit IRC23:06
*** dosaboy has quit IRC23:07
*** fnaval has quit IRC23:11
*** mtreinish has quit IRC23:11
*** lbragstad has quit IRC23:11
*** flaper87 has quit IRC23:12
*** jhenner has quit IRC23:13
*** maoy has quit IRC23:23
*** diogogmt has quit IRC23:25
*** agentle_ has quit IRC23:26
*** sacharya has quit IRC23:26
*** ayoung has quit IRC23:29
*** fnaval has joined #openstack-meeting23:34
*** fnaval has quit IRC23:34
*** almaisan-away is now known as al-maisan23:34
*** fnaval has joined #openstack-meeting23:34
*** al-maisan is now known as almaisan-away23:35
*** yamahata has quit IRC23:37
*** AlanClark__ has quit IRC23:38
*** AlanClark__ has joined #openstack-meeting23:38
*** markvan has joined #openstack-meeting23:42
*** metral has joined #openstack-meeting23:43
*** fifieldt has joined #openstack-meeting23:47
*** sarob has joined #openstack-meeting23:52
*** ravikumar_hp has joined #openstack-meeting23:52

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