Tuesday, 2012-08-21

*** markmcclain has joined #openstack-meeting00:02
*** fss has quit IRC00:03
*** fss has joined #openstack-meeting00:06
*** asalkeld has quit IRC00:08
*** nati_ueno has joined #openstack-meeting00:10
*** alexpilotti has quit IRC00:11
*** kindaopsdevy has joined #openstack-meeting00:18
*** kindaopsdevy has quit IRC00:19
*** zhuadl has quit IRC00:23
*** johnpostlethwait has quit IRC00:26
*** dolphm has quit IRC00:27
*** heckj has quit IRC00:30
*** nati_uen_ has joined #openstack-meeting00:31
*** lloydde has quit IRC00:32
*** nati_uen_ has quit IRC00:33
*** nati_ueno_2 has joined #openstack-meeting00:34
*** nati_uen_ has joined #openstack-meeting00:34
*** nati_ueno has quit IRC00:36
*** dwcramer has joined #openstack-meeting00:39
*** s0mik has quit IRC00:43
*** dolphm has joined #openstack-meeting00:45
*** nati_ueno has joined #openstack-meeting00:47
*** asalkeld has joined #openstack-meeting00:48
*** ncode has quit IRC00:49
*** asalkeld has joined #openstack-meeting00:49
*** nati_uen_ has quit IRC00:51
*** nati_ueno has quit IRC00:53
*** nati_ueno has joined #openstack-meeting00:57
*** ryanpetr_ has quit IRC00:59
*** SumitNaiksatam has quit IRC01:03
*** nati_ueno_2 has quit IRC01:20
*** nati_ueno_2 has joined #openstack-meeting01:20
*** markmcclain has quit IRC01:21
*** jakedahn_zz is now known as jakedahn01:21
*** gyee has quit IRC01:28
*** nati_ueno has quit IRC01:29
*** dendrobates is now known as dendro-afk01:31
*** Gordonz has quit IRC01:31
*** cp16net is now known as cp16net|away01:31
*** cp16net|away is now known as cp16net01:31
*** jakedahn is now known as jakedahn_zz01:36
*** Mandell has quit IRC01:43
*** nati_ueno_2 has quit IRC01:45
*** anniec has quit IRC01:49
*** PotHix has quit IRC01:56
*** dendro-afk is now known as dendrobates01:58
*** dprince has quit IRC02:00
*** jakedahn_zz is now known as jakedahn02:01
*** s0mik has joined #openstack-meeting02:02
*** jakedahn is now known as jakedahn_zz02:03
*** novas0x2a|laptop has quit IRC02:09
*** ncode has joined #openstack-meeting02:12
*** dolphm has quit IRC02:19
*** matwood_ has quit IRC02:25
*** matwood has joined #openstack-meeting02:26
*** blamar has quit IRC02:29
*** ewindisch has joined #openstack-meeting02:30
*** dendrobates is now known as dendro-afk02:37
*** turlough has joined #openstack-meeting02:40
*** turlough has quit IRC02:40
*** turlough has joined #openstack-meeting02:40
*** johnpur has left #openstack-meeting02:43
*** danwent has quit IRC02:44
*** dendro-afk is now known as dendrobates02:44
*** dwcramer has quit IRC03:03
*** danwent has joined #openstack-meeting03:07
*** turlough has joined #openstack-meeting03:10
*** johnpostlethwait has joined #openstack-meeting03:10
*** s0mik has quit IRC03:10
*** dwcramer has joined #openstack-meeting03:16
*** s0mik has joined #openstack-meeting03:18
*** fss has quit IRC03:26
*** tgall_foo has joined #openstack-meeting03:29
*** justinsb has quit IRC03:29
*** blamar has joined #openstack-meeting03:32
*** rkukura has left #openstack-meeting03:34
*** Mandell has joined #openstack-meeting03:35
*** s0mik has quit IRC03:36
*** littleidea has joined #openstack-meeting03:36
*** dayou has joined #openstack-meeting03:46
*** andrewsmedina has quit IRC03:47
*** andrewsmedina has joined #openstack-meeting03:49
*** dayou has left #openstack-meeting03:49
*** s0mik has joined #openstack-meeting04:02
*** turlough has quit IRC04:07
*** turlough has joined #openstack-meeting04:07
*** matwood_ has joined #openstack-meeting04:17
*** tgall_foo has quit IRC04:19
*** matwood has quit IRC04:21
*** matwood_ is now known as matwood04:21
*** nati_ueno has joined #openstack-meeting04:28
*** sacharya1 has quit IRC04:34
*** turlough has quit IRC04:36
*** johnpostlethwait has quit IRC04:37
*** zhuadl has joined #openstack-meeting04:49
*** andrewsmedina has quit IRC04:50
*** andrewsmedina has joined #openstack-meeting04:52
*** dayou has joined #openstack-meeting04:58
*** s0mik has quit IRC05:02
*** dolphm has joined #openstack-meeting05:05
*** andrewsmedina has quit IRC05:08
*** matwood has quit IRC05:12
*** matwood has joined #openstack-meeting05:13
*** matwood_ has joined #openstack-meeting05:23
*** matwood has quit IRC05:28
*** matwood_ is now known as matwood05:28
*** ryanpetrello has joined #openstack-meeting05:35
*** anniec has joined #openstack-meeting05:36
*** Mandell has quit IRC05:36
*** edgarmagana has quit IRC05:38
*** ryanpetrello has quit IRC05:39
*** johnpostlethwait has joined #openstack-meeting05:50
*** Mandell has joined #openstack-meeting05:56
*** johnpostlethwait has quit IRC05:57
*** almaisan-away is now known as al-maisan06:10
*** littleidea has quit IRC06:17
*** dolphm has quit IRC06:20
*** dayou has quit IRC06:22
*** al-maisan is now known as almaisan-away06:46
*** shang has quit IRC06:47
*** rafaduran has joined #openstack-meeting06:54
*** salv-orlando has joined #openstack-meeting06:59
*** garyk has joined #openstack-meeting07:05
*** anniec_ has joined #openstack-meeting07:25
*** shang has joined #openstack-meeting07:27
*** anniec has quit IRC07:28
*** anniec_ is now known as anniec07:28
*** dolphm has joined #openstack-meeting07:37
*** EmilienM has joined #openstack-meeting07:39
*** derekh has joined #openstack-meeting07:43
*** Mandell has quit IRC07:47
*** zhuadl has quit IRC07:56
*** rafaduran has quit IRC07:59
*** zhuadl has joined #openstack-meeting08:00
*** rafaduran has joined #openstack-meeting08:12
*** almaisan-away is now known as al-maisan08:18
*** darraghb has joined #openstack-meeting08:34
*** nati_ueno has quit IRC09:13
*** danwent has quit IRC09:32
*** danwent has joined #openstack-meeting09:46
*** ncode has quit IRC09:46
*** dolphm has quit IRC09:51
*** zhuadl has quit IRC10:05
*** danwent has quit IRC10:38
*** al-maisan is now known as almaisan-away10:45
*** rohitk has joined #openstack-meeting11:05
*** dansmith has quit IRC11:16
*** dansmith has joined #openstack-meeting11:16
*** fss has joined #openstack-meeting11:21
*** alpha_ori has quit IRC11:34
*** alpha_ori has joined #openstack-meeting11:36
*** swifterdarrell has quit IRC11:36
*** swifterdarrell has joined #openstack-meeting11:37
*** dwcramer has quit IRC11:40
*** jkoelker has quit IRC11:41
*** jkoelker has joined #openstack-meeting11:41
*** almaisan-away is now known as al-maisan11:59
*** al-maisan is now known as almaisan-away11:59
*** almaisan-away is now known as al-maisan11:59
*** shang has quit IRC12:01
*** mnewby has joined #openstack-meeting12:02
*** swifterdarrell has quit IRC12:06
*** swifterdarrell has joined #openstack-meeting12:06
*** mnewby has quit IRC12:11
*** shang has joined #openstack-meeting12:14
*** hggdh has quit IRC12:23
*** fss has quit IRC12:25
*** cdub has quit IRC12:26
*** cdub has joined #openstack-meeting12:26
*** al-maisan is now known as almaisan-away12:27
*** almaisan-away is now known as al-maisan12:35
*** hggdh has joined #openstack-meeting12:48
*** fss has joined #openstack-meeting12:53
*** dprince has joined #openstack-meeting13:01
*** mnewby has joined #openstack-meeting13:04
*** andrewsmedina has joined #openstack-meeting13:09
andrewsmedina/part/13:20
*** andrewsmedina has left #openstack-meeting13:20
*** jrd-redhat has quit IRC13:27
*** reed has joined #openstack-meeting13:28
*** ayoung has joined #openstack-meeting13:30
*** PotHix has joined #openstack-meeting13:33
*** mnewby has quit IRC13:37
*** mnewby has joined #openstack-meeting13:39
*** zhuadl has joined #openstack-meeting13:45
*** dansmith has quit IRC13:55
*** dolphm has joined #openstack-meeting13:59
*** nati_ueno has joined #openstack-meeting14:02
*** nati_ueno has quit IRC14:03
*** mnewby has quit IRC14:03
*** mnewby has joined #openstack-meeting14:04
*** derekh has quit IRC14:04
*** nati_ueno has joined #openstack-meeting14:09
*** jrd-redhat has joined #openstack-meeting14:12
*** Gordonz has joined #openstack-meeting14:12
*** dkehn has joined #openstack-meeting14:12
*** Gordonz has quit IRC14:14
*** tgall_foo has joined #openstack-meeting14:14
*** tgall_foo has joined #openstack-meeting14:14
*** Gordonz has joined #openstack-meeting14:14
*** littleidea has joined #openstack-meeting14:20
*** ewindisch has joined #openstack-meeting14:21
*** nikhil_ has joined #openstack-meeting14:23
*** nikhil_ is now known as Guest6024514:23
*** Guest60245 has quit IRC14:25
*** rnirmal has joined #openstack-meeting14:28
*** sacharya has joined #openstack-meeting14:28
*** s0mik has joined #openstack-meeting14:34
*** al-maisan is now known as almaisan-away14:41
*** littleidea has quit IRC14:42
*** littleidea has joined #openstack-meeting14:43
*** primeministerp has joined #openstack-meeting14:47
*** s0mik has quit IRC14:48
*** AndrewWeiss has joined #openstack-meeting14:50
primeministerpAndrewWeiss: Andrew you made it14:54
AndrewWeiss:P14:54
primeministerpHyper-V meeting will start in aprox 5 min14:54
*** dwcramer has joined #openstack-meeting14:55
*** pnavarro has joined #openstack-meeting14:57
primeministerppnavarro: pedro!14:57
*** ryanpetrello has joined #openstack-meeting14:58
primeministerp#startmeeting15:00
openstackMeeting started Tue Aug 21 15:00:25 2012 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
primeministerpHi everyone15:00
primeministerpWelcome to the openstack/hyper-v discussion15:01
primeministerp#topic status of the code!15:01
*** openstack changes topic to "status of the code!"15:01
primeministerpSo we were able to get a feature freeze excemption which allowed the code to be excepted15:01
primeministerpmany thanks to the community and nova core devs for the help in this process15:02
primeministerpAnyone testing the hyper-v code can now file bugs through the normal channels15:02
primeministerpI have updated the wiki to reflect that.15:03
primeministerpAlso there are still some areas of documenation that need to be completed anyone wanting to help contribute to docs, please contact me directly15:04
primeministerp#topic CI Status15:04
*** openstack changes topic to "CI Status"15:04
primeministerpI'm still working to get the ci up and running, I've been plagued by hardware failures the last two weeks so hopefully i'm beyond that now15:05
*** zhuadl has quit IRC15:05
primeministerpI should have something in place by the end of the week15:05
primeministerpto hopefully begin running the smokestack tests on hyper-v15:06
primeministerpmoving on15:06
primeministerp#topic Blueprints for Grizzly15:06
*** openstack changes topic to "Blueprints for Grizzly"15:06
primeministerpWe should begin thinking about key area's that need to be addressed for the Grizzly cycle15:06
primeministerpthe two that are high priority15:07
primeministerp1. Quantum15:07
primeministerp2. RDP console access15:07
primeministerpPeople should be thinking about other area's that need to be addressed15:07
primeministerpAn additonal area could possibly be porting cinder to be able to use windows iscsi targets15:08
primeministerppnavarro: would that be something of interest?15:08
AndrewWeissprimeministerp: what are some ideas floating around for RDP access?15:08
pnavarroor keystone with Active Directory?15:08
primeministerppnavarro: that is also a key area15:08
primeministerppnavarro: however others are also currently looking into that15:09
primeministerppnavarro: hopefully we can get some coordination at the summit and pool efforts15:09
primeministerppnavarro: if people are already considering working on that15:09
primeministerpAndrewWeiss: currently there has been some investigation on using FreeRDP15:09
AndrewWeissok15:09
pnavarro#agreed15:10
primeministerpcurrently it is possible to connect to the vm console through hyper-v15:10
primeministerpwe would need to work on the freerdp project to help stabilize that code15:10
primeministerphopefully then create maybe a nova-rdp-proxy of sorts15:10
primeministerpand also allow integration into horizion15:11
primeministerphowever that all needs to be discussed15:11
AndrewWeissthat would be pretty nice15:11
primeministerpquite honestly both that quantum are pretty big tasks15:11
primeministerppnavarro: do you think you'll be able to attend the conf, if i'm unable to get some help for that on my end?15:12
*** nati_ueno has quit IRC15:13
*** markmcclain has joined #openstack-meeting15:13
primeministerppnavarro: we can discuss later if possible15:13
pnavarroprimeministerp: holidays is not a problem I have free days, I'm going to see if I can find a flight/hotel affordable15:14
primeministerppnavarro: we can talk about the hotel15:14
primeministerppnavarro: i'd share a room if it comes to that15:14
pnavarroprimeministerp: ok, we'll talk later15:14
primeministerppnavarro: pnavarro however i'm still trying to secure my own trip15:14
primeministerppnavarro: anyway we need to get you there15:15
primeministerpok let's open the floor for discussion15:15
primeministerp#topic open discussion15:15
*** openstack changes topic to "open discussion"15:15
primeministerpanyone have anything they would like to add/discuss15:15
AndrewWeissprimeministerp: anyone doing some security analyses on the hyper-v integration?15:16
primeministerpI know alessandro pilotti is at a conf this week15:16
primeministerpAndrewWeiss: good question15:16
primeministerpAndrewWeiss: and no15:16
primeministerpis the answer15:16
primeministerpAndrewWeiss: right now most deployments have been strictly developement driven15:16
AndrewWeissthat's what i assumed15:17
primeministerpAndrewWeiss: I know i have not implemented encryption in my setups yet15:17
primeministerpAndrewWeiss: however it's definately on my mind15:17
AndrewWeissprimeministerp: any chance I can be of help to that?15:17
primeministerpAndrewWeiss: it's just been a matter of cycles right now and lack of them15:17
primeministerpAndrewWeiss: definately15:17
primeministerpAndrewWeiss: ideally we need to implement it in a secure manner, then document that15:18
primeministerpAndrewWeiss: let's talk off line, I can definately use the hands in the lab15:18
primeministerpAndrewWeiss: as long as you can get the clearance and the cycles15:18
AndrewWeissprimeministerp: ok, that  sounds great15:18
primeministerpAndrewWeiss: if you know what i mean15:18
primeministerp;)15:18
AndrewWeisshaha for sure15:18
primeministerpAndrewWeiss: also if you want to start quick you can help w/ the documentaiton15:19
AndrewWeissprimeministerp: yea i was thinking that's somewhere i can start15:19
primeministerpAndrewWeiss: I have a good chunk done but need to finish up some key areas15:19
primeministerpannegentle: ping15:19
*** rafaduran has quit IRC15:19
primeministerpannegentle: any way to hook up AndrewWeiss with the necessary license to assist in our hyper-v documentation efforts15:19
pnavarroprimeministerp: I have experience with Oxygen, so if you need help to transform DOC to docbook15:20
primeministerppnavarro: did you see what i've started w/15:20
pnavarroprimeministerp: not yet, it's in github?15:21
primeministerp#link https://github.com/ppouliot/openstack-docs-hyper-v15:21
primeministerppnavarro: that's what I have now15:21
primeministerpannegentle was kind enough to provide me with the original docs15:22
primeministerpI have them commented in that15:22
pnavarrook, I'll take a look15:22
primeministerpI have added the outline as well as most of the installing from source15:22
primeministerpand tweaks15:22
primeministerppnavarro: check out the other repo too15:23
primeministerpAndrewWeiss: you might want to check that out as well15:23
AndrewWeissprimeministerp: ok, will do15:23
primeministerpAndrewWeiss: also make sure you email annegentle regarding an oxygen license for hyper-v documentation15:24
primeministerppnavarro: anything to add15:24
AndrewWeissprimeministerp: ok15:24
pnavarroprimeministerp: any status about puppet stuff?15:25
primeministerppnavarro: hehe15:25
primeministerppnavarro: so i've been working with the puppet guys15:25
primeministerppnavarro: we've hit a problem with the powershell executing15:25
primeministerpthat I haven't figured out yet15:25
primeministerpif you look at that repo15:25
primeministerpand dig down15:25
primeministerpI 've cleaned out it15:26
primeministerpit's most of the framework15:26
primeministerpup until the point where we need to get the code from git15:26
primeministerpall the powershell for setting the tidbits for openstack features  is there15:26
primeministerphowever some need to get cleaned up and15:26
primeministerpwhat i've been testing is the add_hyper-v_feature.pp15:26
primeministerponce i get that to work the rest should come quick15:26
primeministerpif you want to help, i'll take it15:27
primeministerpbasically i've been running the init.pp15:27
primeministerpwhich should run the one above15:27
pnavarroI've tried puppet, but I have more experience with Chef15:27
primeministerppnavarro: well15:27
primeministerppnavarro: we need to do that too15:28
primeministerppnavarro: and all the commands15:28
primeministerpare in those puppet manifiests15:28
pnavarroI've seen you are in the crowbar skype group, any feedback from them?15:28
primeministerppnavarro: i've been talking with them15:28
primeministerphowever, i'm not ready for them yet15:28
primeministerppnavarro: and they are working on some major enhancements to crowbar15:28
primeministerppnavarro: to make it more agnostic15:29
primeministerppnavarro: i've already got some chef bits pulled together15:29
primeministerppnavarro: ideally we do both15:29
primeministerppnavarro: more people who can get it out there the better15:30
pnavarroprimeministerp: I've installed crowbar many times in some POC's, so I can help in the future15:30
primeministerppnavarro: good to know15:30
primeministerpanything else?15:30
pnavarronot from my side15:31
primeministerpok then, until next week.   Keep testing everyone.  File bugs please.15:31
primeministerp#endmeeting15:31
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"15:31
openstackMeeting ended Tue Aug 21 15:31:48 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-15.00.html15:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-15.00.txt15:31
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-15.00.log.html15:31
*** AndrewWeiss has quit IRC15:32
*** ryanpetrello has quit IRC15:32
*** ryanpetrello has joined #openstack-meeting15:35
*** andrewbogott_afk is now known as andrewbogott15:38
*** pnavarro has quit IRC15:40
*** cp16net is now known as cp16net|away15:48
*** cp16net|away is now known as cp16net15:48
*** dcramer_ has joined #openstack-meeting15:48
*** alexpilotti has joined #openstack-meeting15:48
alexpilottiHi guys15:49
*** dwcramer has quit IRC15:51
*** yousi has joined #openstack-meeting15:52
*** sacharya has quit IRC15:55
*** tgall_foo has quit IRC15:56
*** lloydde has joined #openstack-meeting16:00
*** yousi has quit IRC16:01
*** andrewbogott is now known as andrewbogott_afk16:01
*** ryanpetrello has quit IRC16:07
*** andrewbogott_afk is now known as andrewbogott16:08
*** sacharya has joined #openstack-meeting16:13
*** kindaopsdevy has joined #openstack-meeting16:13
*** alexpilotti has quit IRC16:14
*** alexpilotti_ has joined #openstack-meeting16:14
*** alexpilotti_ is now known as alexpilotti16:14
*** Mandell has joined #openstack-meeting16:20
*** kindaopsdevy has quit IRC16:27
*** alexpilotti has quit IRC16:29
*** ryanpetrello has joined #openstack-meeting16:35
*** EmilienM has left #openstack-meeting16:36
*** EmilienM has joined #openstack-meeting16:37
*** anniec has quit IRC16:39
*** ayoung has quit IRC16:40
*** ayoung has joined #openstack-meeting16:48
*** jog0 has joined #openstack-meeting16:49
*** reed has quit IRC16:51
*** darraghb has quit IRC16:57
*** cp16net is now known as cp16net|away16:59
*** s0mik has joined #openstack-meeting17:01
*** patelna has joined #openstack-meeting17:03
*** cp16net|away is now known as cp16net17:04
*** danwent has joined #openstack-meeting17:05
*** anniec has joined #openstack-meeting17:08
*** anniec_ has joined #openstack-meeting17:08
*** Ravikumar_hp has joined #openstack-meeting17:10
*** mattray has joined #openstack-meeting17:11
*** anniec has quit IRC17:12
*** anniec_ is now known as anniec17:12
*** ryanpetr_ has joined #openstack-meeting17:13
*** ryanpetrello has quit IRC17:13
*** dendrobates is now known as dendro-afk17:14
*** johnpur has joined #openstack-meeting17:16
*** ryanpetrello has joined #openstack-meeting17:18
*** ryanpetr_ has quit IRC17:18
*** ryanpetrello has quit IRC17:21
*** ryanpetrello has joined #openstack-meeting17:22
*** ncode has joined #openstack-meeting17:31
*** garyk has quit IRC17:34
*** mattray has quit IRC17:39
*** marek_ has joined #openstack-meeting17:47
*** hggdh has quit IRC17:53
*** kevin9999 has joined #openstack-meeting17:58
ayoungKeystone!17:58
ayoungdolphm, no heckj today?17:59
dolphmayoung: haven't seen him today17:59
dolphmayoung: he responded to a bug ~2 hours ago though, it looks like18:00
ayoungno gyee18:00
ayoungdolphm, anyone else besides mnewby that we should call in?18:01
dolphmayoung: no one specific, afaik18:01
ayoungPeople just don't understand how sexy Keystone is18:02
*** heckj has joined #openstack-meeting18:02
ayoungw00t18:02
heckjo/18:02
heckjrunning slow today guys, sorry18:02
heckj#startmeeting18:02
ayoungNP18:02
openstackMeeting started Tue Aug 21 18:02:35 2012 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
heckj#topic: bugs and rc18:02
*** openstack changes topic to ": bugs and rc"18:02
heckjI spent some of this morning triaging bugs - have a few that I need to dig into a bit more18:03
ayoungheckj, anything buring?18:03
ayoungburning18:03
heckjthey're been a number of bugs filed about making auth_token more standalone - primary driver to it being that folks don't want to have to install all of keystone to get the auth_token pieces18:03
heckjThere's also a number of tracebacks and other quirks across various pieces - lots of recent bugs filed around using auth_token with swift18:04
ayoungheckj, does it belong in openstackcommon?18:04
heckjseems like that's a weak spot - maybe more so with documentation than anything else, but a weak spot none the less18:04
*** mattray has joined #openstack-meeting18:04
heckjayoung: At some point, yes - I don't think we're ready to shift it over there quite yet though.18:04
ayoungheckj, well, I am partially to blame.  PKI pulls in some deps18:04
heckjIt doesn't feel like that API is really stable at this point with the additions of what we're doing with the PKI token pieces, but I think we'll be able to shift that within another release18:05
ayoungSo could we somehow generate a library for it?18:05
*** inteq has joined #openstack-meeting18:05
dolphmauth_token *should* be dependent on keystoneclient18:05
ayoungkeystone/common and keystone/middleware/auth_token18:06
heckja library, or a more limited package set of some form I think - I think that would solve most of the desires there18:06
dolphmnew home? keystoneclient.middleware.auth_token18:06
ayoungdolphm, isn't keystone client the CLI?18:06
dolphmayoung: the CLI runs on top of a full python library18:06
heckjif we're going to do that, I'd rather just move it into openstack-common18:06
dolphmheckj: that's more intuitive18:07
*** dendro-afk is now known as dendrobates18:07
heckjOn top of that, I think the clients need to be doing more to converge - the sort of inadvertant separation that occured over the past two release cycles is a bad place to be in18:07
heckjdtroyer was starting something about an "openstack" client - don't know current state, but I'd like to support that explicitly18:07
ayoungI'm not ready to surrender control of auth_token yet18:08
heckjayoung: that's my sense as well18:08
ayoungI also think a CLI is a very different thing from a web integration piece18:08
dolphmheckj: https://launchpad.net/python-openstackclient18:08
heckjI think we'll also need to make some changes in auth_token when we get into supporting V3 API as well, so having it in a separate repo will be a pain point for making progress there18:08
ayoungauth_token is really an extensioon to  HTTProtocol18:08
ayoungand could, in theory, be implemented in multiple languages18:09
heckj#link https://launchpad.net/python-openstackclient18:09
heckj(thanks dolphm ^^)18:09
*** matwood has quit IRC18:09
dolphmit would make sense to me that the python library be implemented in keystoneclient, and python-openstackclient uses that to implement the CLI (as the stated goal of openstackclient is a common shell across openstack)18:09
heckjthere's also a "security" bug reported, alhtough I don't think it's really a security issue18:10
heckjsec for the link18:10
dolphmheckj: it's not18:10
*** matwood has joined #openstack-meeting18:10
dolphmheckj: bout to mark it invalid18:10
heckjdolphm: +1 - it's a complaint that the API wasn't documented, but is intended18:10
dolphmheckj: it's documented, just not where the user expected18:11
heckjdolphm: didn't mean to throw that on your shoulders this morning - added you as subscriber so you could see it18:11
*** matwood has quit IRC18:11
ayoungwhy didn't https://review.openstack.org/#/c/10579/ get re smokestacked?18:11
dolphmheckj: no worries18:12
heckjayoung: dunno there, maybe ping mtaylor or jeblair for insight?>18:12
mtayloraroo?18:13
mtaylorheckj: we don't run smokestack18:13
heckjAh - well, you're not gunna help there then :-)18:13
heckjmtaylor: who does?18:13
ayoungmtaylor, is there an equivalent to recheck for smokestack?18:13
ayoungfor gerrit18:13
mtaylorayoung: nope. we have no control over it18:14
mtaylorit's all dprince18:14
heckjthanks18:14
heckjwe look like we're keeping up well on reviews18:15
ayoungheckj, dolphm so that is the only thing I think I have in my pipeline that was submitted buy someone else that should go through18:15
heckjwhich brings me to my next topic...18:15
heckj#topic OCF scripts18:15
*** openstack changes topic to "OCF scripts"18:15
dolphmmnewby: ?18:15
dolphmayoung: who's the someone else18:16
mnewbydolphm: hi18:16
ayoungapevec18:16
* dolphm waves at mnewby -- didn't mean to summon you18:16
heckjdolphm: the specific review that ayoung posted above18:16
dolphmagh18:16
dolphmah*18:16
ayoungdolphm, I mean that 10579 (submitted by apevec) is something I am shepherding through18:16
dolphmOCF?18:17
ayoungthe only other change I have in my pipeline is mine for PKI...we can hold off on that until after OCF18:17
heckjYeah - ocf scripts18:17
ayoungIsn't that Oracle Cluster File?  no wait, that has an S18:17
ayoungwhat is OCF?18:17
heckjThe OCF scripts are scripts that can be used with pacemaker to manage resources. I orginally thought it would be fine to include a set in our repo to make them easily available18:17
*** rohitk has quit IRC18:18
dolphmsomething i'm not qualified to review, for sure18:18
heckjbcwaldon brought up a really good point - his opinion is that anything in our repo should be fully supported - and we just don't have a lot of background or detail to be able to support, review, etc. OCF scripts - plus it's specific to actually ANOTHER project (pacemaker), so perhaps it wasn't actually appropriate to put into our repo18:18
ayoungheckj, I concur with that analysis18:19
ayoungI couldn't review it.  I don't even know what OCF expands to.18:19
heckjheh18:19
dolphmsatellite project? http://osdir.com/ml/openstack-cloud-computing/2012-02/msg00883.html18:19
heckjdolphm: I think that's where it really belongs18:20
ayoungI thought that was the general consensus from the IRC discussion18:20
dolphmheckj: did anyone ever setup a directory of satellite projects? last i heard it would be through sourceforge?18:20
dolphmbut i've never seen one18:20
heckjTHere was some talk of a site that would list these things, including people's github repos and such, so that related projects could be found, but support/stability/etc attestation wasn't comign from core openstack projects18:20
heckjthere was a site planned called stackforge, but no end-user facing setup was created - mtaylor did some great work to expand where we can apply gerrit and CI tools, but that's where it ended18:21
heckjI'm talking with some other folks to try and re-invigorate that effort to get something up and running18:21
heckjsounds like solid consensus on that commit though, so I'll follow it up with email and relevant review comments18:22
heckj#action heckj to follow up on moving OCF scripts elsewhere18:22
dolphmcool18:22
mtaylor++18:22
heckjayoung: you said you had another review item?18:22
heckj#topic ayoungs review thing18:22
mtaylorwe have a stackforge github org that things can go in pretty easily18:22
*** openstack changes topic to "ayoungs review thing"18:22
mtaylorand stuff18:22
heckjmtaylor: ++18:22
ayoungheckj, PKI revocation.18:22
mtaylor(and get hooked in to gerrit, should that be a useful thing)18:22
*** andrewbogott is now known as andrewbogott_afk18:23
heckj#topic PKI revocation18:23
*** openstack changes topic to "PKI revocation"18:23
heckjtake it away18:23
ayoungI just reposted for review...asuming we get it through in the next day or so,  doees it get merged over to the Folsom branch somehow, or are we going to cut RC1 from master?18:23
dolphmmaster i believe18:23
heckjttx will cut RC1 from master18:24
ayoungOK.  So I am set with that...so here is what I found18:24
*** rohitk has joined #openstack-meeting18:24
ayoungthe Vary Header gets set, but only for JSON18:24
ayoungI was doing the Revocation list as straight text18:24
heckjI haven't pestered mtaylor in detail with email about enabling a feature branch - which I thought we'd do for dolph's V3 api implementation work18:24
dolphmayoung: is there a reason why it's not / can't be in JSON?18:24
ayoungbut...it is a signed document,  which means that it should be does via some standard or other, and sure enough18:24
ayoung#link http://tools.ietf.org/html/rfc184718:25
heckjoh boy...18:25
ayoungNow,  I just found out today how to generate that format from openssl.  It is not too bad18:25
ayoungBut...I am not going to do that, not yet18:25
ayoungI am going to return the revocation list in a JSON document.18:26
dolphmayoung: does the client need to specify Accept: multipart/signed ?18:26
heckjayoung: just thinking that doing this right is more complex than I'd like for the timeframe we're in around release18:26
dolphmneed / should18:26
*** summation has joined #openstack-meeting18:26
ayoungdolphm, good question.  I don't know.  I don't think we/eventlet checks that....18:26
*** summation has quit IRC18:26
dolphmayoung: keystone checks accept headers today18:26
ayoungOK18:27
dolphmayoung: although i think application/json is assumed if one is not provided18:27
dolphmotherwise application/xml is mildly supported18:27
dolphmheckj: which reminds me of a v3 issue ^ actually18:28
ayoungdolphm, yeah...18:28
heckjyeah18:28
ayoungI'd love it if we could hit keystone from a web browser directly18:28
ayoungbut that would mean to default to HTML18:28
dolphmheckj: the {'entity': {...}} conversation we had about the entity containers ...18:28
ayoungwe can do that in V3...but it might break things on the landing page18:28
dolphmheckj: sort of needed for easy xml support18:28
heckjdolphm: AHHH!!18:28
*** anniec has quit IRC18:28
heckjdolphm: I wondered why we were doing that18:29
*** anniec has joined #openstack-meeting18:29
dolphm{'this': {'attr': 'value'}} becomes <this attr="value" />18:29
heckjdolphm: yep, makes sense when you think about translation18:29
*** inteq has quit IRC18:29
heckjWe're veering off from ayoung's topic though -18:30
ayoungheckj, not necessarilty18:30
dolphmand now back to our regularly scheduled program18:30
ayoungI think we need to put a focus on proper rest for Grizzly18:30
heckjOk… wasn't sure what you needed, or if you got it with the checking vary-headers in the client18:30
ayoungand that means we should support multiple content types.18:30
*** matwood has joined #openstack-meeting18:30
ayoungSo, I am not sure if the multipart/signed is right long term...I can investigate that18:31
heckjayoung: I agree, although I don't know how far down the HATEOS road I really want to go with this18:31
ayoungheckj, this is how far I want to go18:31
heckjayoung: we can get into some hellashis complexity with using mime headers and such for versioning and request types - I would MUCH prefer to keep that simple18:31
ayounghit the landing page, use basic auth (or cert or kerberos in the future)18:32
ayoungget apage with a link for everything that I can do18:32
dolphmheckj: i'm definitely not a fan of using mime types of versions - ick18:32
ayoungbe able to do it all from a browser using a sparse HTML UI18:32
heckjayoung: doesn't that overlap pretty heavily with what's happening in horizon?18:33
ayoungheckj, dolphm that is fine.  Lets make the design decisions explicit18:33
ayoungheckj, not really.  This is for our use18:33
ayoungand for the Keystone administrator18:33
ayoungso they can diagnose with Horizon out of the picture18:33
ayoungalso for the end user scripting/integrating with Keystone18:33
dolphmnothing is stopping a browser-side javascript-keystoneclient from existing, either18:33
*** rohitk has quit IRC18:34
ayoungdolphm, well..not quite true18:34
ayoungsame origin policy is still in the way18:34
heckjayoung: I love it as a dev tool - not so sure about building up a user experience for keystone admins with it though...18:34
dolphmright, but nothing is stopping someone from deploying keystone on the same domain as a JS client18:34
heckjayoung, dolphm : related: CORS support blueprint to enable that18:34
ayoungheckj, Keystone is the rich tool.  This is a debugging and testing tool18:35
ayoungheckj, right....doesn't exist yet18:35
heckjayoung: yep - agreed18:35
ayoungCORS that is18:35
heckjyeah18:35
ayoungBut also, I think, if we were to build it that way,  the Javascript client would consume pieces of it that don't yet exist:  figuring out what data to put together for a form should be drive off a query from tjhe server18:36
ayoungso...I'd like to make HTML a 1st class marshalling format for Grizzly18:36
* dolphm runs18:36
ayoungayoung, catches up with dolphm trips him, and drags him back to the meeting18:37
heckjuh, well - wow18:37
ayoungheckj, simple, simple HTML:18:37
* dolphm distracts ayoung with the xml middleware and makes another break for it18:37
ayoungresults come back in a <DL><DT><DD> ... form18:37
dolphmayoung: have you seen our application/xml support implementation?18:38
dolphmayoung: keystone.middleware.core.XmlBodyMiddleware18:39
ayoungheckj, the same rules that go for XML should work for HTML,  and then the whole thing should be browser friendly.  Otherwise, we are not doing REST, we are just doing another SOAP18:39
heckjayoung: Oh sure… throw out the "I'll beat you with a brick of SOAP" card…18:39
ayoungdolphm, right18:39
heckjayoung: WTF, let's give it a shot, see how it rolls. It'll be useful for us doing dev at least18:40
*** salv-orlando has quit IRC18:40
heckjSomewhat side note:18:40
heckjhttplib2 broke my heart yesterday18:40
heckj(novaclient and us… built on it)18:40
heckjin the case of a timeout, with the current "release" of it, it automatically retries the connect...18:40
heckjmeaning that if you were running through a proxy, and the request timed out, it would double it...18:41
dolphmayoung: how do incoming HTML requests look? are they just multipart/form-data encoded?18:41
heckjthat's been made configurable in master of httplib2 development tree, but not yet released.18:41
dolphmheckj: i saw your tweet lol18:41
dolphmheckj: double the expected block time, i imagine?18:42
heckjdolphm: we're repackaging httplib2 with the fix ourselves short term18:42
ayoungdolphm, you mean from a browser?  What kind of requests?  POST or GET?18:42
dolphmayoung: POST18:42
dolphmayoung: and PATCH18:42
ayounghaven't looked at patch yet.18:43
dolphmayoung: looks just like POST, except the resource isn't a collection18:43
ayoungdolphm, I have to admit,  I have been doing AJAX for so long that I am not sure.18:43
dolphmayoung: i believe the PUT operations in V3 don't require a request/response body18:43
ayoungI had libraries managing it for me last project.18:44
heckjayoung, dolphm Any word from David Chadwick? Said he'd be on IRC, but I don't know what his nick would be...18:44
ayounghe's on the wrong IRC server18:44
heckjah18:44
dolphmheckj: (who's david chadwick?)18:44
heckjdolphm: he's the guy that's been talking about federation and the use cases they need18:45
dolphmah cool18:45
ayoungdolphm, wrote a Federated Keystone proof of concept18:45
heckjd.w.chadwick@kent.ac.uk18:45
dolphmoh yeah18:45
dolphmi remember him18:45
ayoungSent him the URL for Freenode18:46
heckjayoung: thanks18:46
dolphmattribute based authz?18:46
ayoungdolphm, those links from last week?18:46
ayounghttp://etherpad.openstack.org/GrizzlyKeystoneSessions18:47
dolphmayoung: i'm thinking back to the essex conference, hadn't heard from him since18:47
ayoungheckj, dolphm so the thing I wanted to make sure was that for the V3 API, we weren't assuming JSON by default.  I think that will not allow the browsers to do HTML.18:48
ayoungAnd instead, require an Accepts header.18:48
dolphmayoung: we can make it required, the clients i've seen are good about specifying it18:48
heckjayoung: that seems quite reasonable18:48
dolphmayoung: i know i'm lazy when it comes to curl/etc, but that's my fault :)18:49
ayoungdolphm, its easy if you just cut/paste....18:49
heckjsounds like we should make some quick doc notes in our dev docs with relevant cut/paste usefulness :-)18:49
ayoungyep18:50
ayoungcan we #action that?18:50
ayoungor decision or whatnot?18:50
dolphmrequire appropriate accept headers?18:51
ayoungdolphm, yes,. that18:51
dolphmand require appropriate content-type while we're at it?18:51
heckj#action ayoung to scribble up some cut and paste URL examples with appropriate accept headers for dev docs18:52
dolphm(we might already require appropriate content-type)18:52
heckj#action: V3 API (all of us to implement) will require accept headers18:52
heckjgood ^ ?18:52
dolphmso, i've got a giant chunk of v3 implemented18:53
dolphmi haven't touched /tokens yet, though18:53
ayounggood18:53
heckjnice18:53
ayoungdolphm, I can take a look once I've knocked out revocation.18:54
dolphmayoung: heckj: let me know when ya'll want to take a peek -- otherwise i'll keep chugging away offline18:54
ayoungdolphm, OK...will do18:54
heckjdolphm: I'll find out the feature branch idea that monty had and start that thread in email18:55
dolphmayoung: heckj: majorish change from my last review on policy -- i'm implementing a single router deployed to both :5000 and :35357 by default -- not making any distinction between API's whatsoever18:55
ayoungdolphm, I like that!18:55
heckjdolphm: I think that's a good way to go.18:55
ayoungI would really really really like to be able to deploy on a single port.18:55
dolphmayoung: heckj: to compensate, i'd like to write some whitelist middleware for people that want it, which would only allow "public"-friendly calls to make it through ... but i wouldn't include it in keystone.conf.sample by default18:56
heckjdolphm: seems reasonable - toss up a relevant blueprint on that, will you?18:56
dolphmheckj: sure18:56
heckjayoung: related - IANA declined our request for another port # - so "35357" is our official port, and will stay that way18:56
dolphmIMO, splitting up the API across multiple ports is a deployment concern, with MUCH better solutions on that side of the fence than what we're "enforcing" today18:57
ayoungheckj, as well they should....but personally, I want to be able to deploy on 443....18:57
dolphmheckj: cool18:57
heckjI think if we get policy implemented in our own API, we can and should drop this to a single port18:57
heckjayoung: word18:57
ayoungOK, that is 15:00.  We now turn into pumpkins18:58
* dolphm runs from mtaylor18:58
ayounger..I guess the chat room turns into a pumpkin, and we turn back into mice.18:58
heckjayoung, dolphm - can one of you stand in for me in the release meeting today?18:58
* mtaylor ties up dolphm and feeds him to jenkins18:58
heckj'#endmeeting18:58
heckj#endmeeting18:58
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"18:58
openstackMeeting ended Tue Aug 21 18:58:53 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:58
ayoungheckj, dolphm would be happy to18:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-18.02.html18:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-18.02.txt18:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-18.02.log.html18:58
heckjbefore I get fed to Gerrit...18:58
ayoungheh heh18:59
mtaylor#startmeeting19:01
openstackMeeting started Tue Aug 21 19:01:01 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
mtaylorCI anybody?19:01
jeblairmtaylor: say "#meetingname CI" please19:01
mtaylor#meetingname CI19:01
openstackThe meeting name has been set to 'ci'19:01
mtaylorNEAT19:01
jeblairthx19:01
mtaylorwhen did that happen?19:01
jeblairmtaylor: it's always been there -- i was going to look into adding that, and found it in the code19:01
* mtaylor has brain damage clearly19:01
mtaylorwe should tell people19:01
jeblairmtaylor: i believe it will change the output for logs19:01
mtaylorheckj: did you see that?19:01
jeblairmtaylor: better yet --19:01
jeblairmtaylor: i think we should make it a required argument for "startmeeting"19:02
dolphmcooool19:02
mtaylorjeblair: ++++19:02
dolphmis that why the meeting name was "keystone something something" for like a year?19:02
jeblairmtaylor: why don't you endmeeting and we'll see where it goes?19:02
mtaylor#endmeeting19:02
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"19:02
openstackMeeting ended Tue Aug 21 19:02:32 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-19.01.html19:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-19.01.txt19:02
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-19.01.log.html19:02
mtaylorthat did nothing19:02
jeblair:(19:02
jeblairokay, well, i'll keep digging.19:02
mtaylor#meetingname CI19:02
mtaylordamn19:02
mtaylor#startmeeting19:03
openstackMeeting started Tue Aug 21 19:03:00 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
mtaylor#meetingname CI19:03
openstackThe meeting name has been set to 'ci'19:03
mtayloroh wel19:03
jeblairmtaylor: in general, how about the idea of "#startmeeting ci"19:03
mtaylor++19:03
jeblairmtaylor: and making sure the logs go to /meetings/ci/DATE19:03
mtayloralso - now that we have logs.o.o ...19:03
mtaylorlogs.o.o/meetings/ci/DATE ?19:03
jeblairmtaylor: logs.o.o is build logs...19:03
jeblairmtaylor: perhaps logs isn't the right name for that19:03
jeblairmtaylor: we could change the build logs to "builds.openstack.org" if we want to use "logs" for irc logs19:04
jeblairmtaylor: but currently, the host for irc logs is http://eavesdrop.openstack.org/meetings/19:04
mtaylorjeblair: just a thought19:04
heckjmtaylor: nope - didn't see that19:04
jeblairnow's a good time to get all this straight, before we have to add any redirects.  :)19:04
mtaylorit is - I was just thinking that we don't necessarily have to keep the logs on the same server as the bot19:04
mtaylorbut I may also be making things more confuseling19:04
jeblairmtaylor: oh, er, then we'd have to copy them.19:04
jeblairmtaylor: or use afs.19:05
mtaylorjeblair: we should totally be using AFS19:05
jeblairmtaylor: i think i've just bootstrapped a meetbot test host, so i can work out the details without having to use #openstack-meeting.  :)19:05
mtaylorneat19:06
mtaylorso - that being said ...19:06
mtayloryou wanna tell people about logs.o.o (since I know we have tons of onlookers)19:06
jeblairsure19:06
jeblairclarkb and I have been working on a project to move all of the build logs and reports onto a static html server19:07
* annegentle looks on19:07
jeblairhttp://logs.openstack.org/19:07
*** mawagon1 has joined #openstack-meeting19:07
jeblairit turns out the more build history and reporting jenkins maintains...19:07
*** kevin9999 has quit IRC19:07
jeblairthe slower it gets.  it's just not meant to scale to the level we're using it at...19:07
jeblairso the idea is to put all the build information on the static server19:08
jeblairand tell jenkins it doesn't have to keep as much of it around19:08
jeblairthis also means that developers won't have to log into launchpad and wait 5 minutes to find out why a build failed19:08
mtaylor++19:09
* mtaylor thinks it will be popular19:09
jeblairas we'll link directly from gerrit to logs.o.o when it's all done19:09
mtaylorso, when you do that, how will people get pretty reports of their test output?19:09
jeblairgood question monty!19:09
jeblairclarkb is rolling out a nose html output plugin...19:09
jeblairand we'll copy an html test report over to logs.o.o19:10
jeblairsimilarly for coverage reports, etc.19:10
mtaylorthat sounds great!19:10
jeblairwe've already got the devstack logs copying over19:10
mtaylordoes it have nifty little javascript controls to expand sections?19:10
jeblairclarkb: ?19:10
jeblairhere's an example set of check jobs for a keystone change:  http://logs.openstack.org/11737/1/check/19:11
jeblair(that's the change and patchset numbers in there, so it's easy to find things)19:11
clarkbit does19:11
*** andrewbogott_afk is now known as andrewbogott19:11
mtaylorclarkb: excellent19:11
*** maoy has joined #openstack-meeting19:12
mtaylornow that we have the html output plugin, what's between us and having zuul spit these links into gerrit reviews?19:12
jeblairmtaylor: i want to make sure all the jobs are putting all of their data their first19:12
clarkbthe output will look like the sample here http://tungwaiyip.info/software/sample_test_report.html19:12
*** Shrews has joined #openstack-meeting19:12
maoygreetings. :)19:12
jeblairmtaylor: basically nothing -- but we have to merge a change into all the projects first19:12
jeblairi invited maoy to join us19:13
jeblairbecause he wanted to chat about the pylint job he's working on19:13
mtaylorsweet19:13
mtaylor#topic pylint19:13
*** openstack changes topic to "pylint"19:13
clarkbthat change is adding the plugin to the test-requires19:13
mtaylorok - wait, before we do pylint...19:13
mtaylordo we really need that in test-requires?19:13
mtaylorit's not actually a plugin we're expecting devs to run locally, are we?19:14
maoyclarkb: are you talking about pylint or something else?19:14
clarkbit isn't, but we need the plugin to be installed into the virtual env19:14
jeblairmtaylor: no, but we need it to be installed in the venv19:14
*** kindaopsdevy has joined #openstack-meeting19:14
clarkbmaoy: something else19:14
mtaylorAH19:14
mtaylorbother19:14
mtaylorok19:14
mtaylorthat's gonna suck19:14
jeblairmtaylor: why?19:14
mtaylorjust merging that everywhere...19:14
jeblairmtaylor: isn't that what test-requires is for?19:14
jeblairmtaylor: oh, yes.  :)19:15
mtaylormaster, s/e, s/d of all projects19:15
jeblairmtaylor: and to stable/* branches too! :)19:15
* mtaylor cries19:15
mtaylorwe might need to get that in soon before ttx thinks it's a new feature and therefore subject to FF19:15
clarkbcan we specify the dependency in run-tox somehow?19:16
jeblairheh "echo 'nosehtmloutput >> tools/test-requires'"19:17
jeblair^ bad idea, don't do it.19:17
uvirtbotjeblair: Error: "bad" is not a valid command.19:17
*** fss has quit IRC19:17
mtaylorthat's right uvirtbot ... "bad" is NOT a valid command19:18
*** heckj has quit IRC19:18
mtaylorjeblair: "grep nosehtmloutput tools/test-requires 2>&1 || echo 'nosehtmloutput >> tools/test-requires'"19:18
mtaylorI think would be more correct19:19
jeblairmtaylor: do you want to go down that road?19:19
mtaylorjeblair: not REALLY19:19
mtaylorbut I wouldn't mind if tox could do dependency injection via arguments or env vars...19:19
jeblairi think we can propose a bunch of one-liners today19:19
jeblairmtaylor: yes, i would like that too.19:19
mtaylorwe're digressing ...19:20
mtaylorpylint!19:20
mtaylormaoy: hey there19:20
maoyyo19:20
jeblairmaoy: so your question to me...19:20
jeblairmaoy: was whether we could have pylint report to gerrit but not count its vote19:20
maoyhttps://jenkins.openstack.org/job/gate-nova-pylint/32/console19:20
maoythis is what it looks like when there is a bug, pretty sweet19:20
jeblairmaoy: is that something you want to do in the long run, or do you still want it to eventually be a real gating job?19:21
maoyjeblair: hard to say.. might not be that a bad idea to do it for a few months..19:21
maoyin openstack i guess that's "long"? :)19:21
jeblairhttp://logs.openstack.org/11444/9/silent/gate-nova-pylint/32/console.html19:22
jeblairthere's the new static url for that.  :)19:22
jeblairmaoy: (that was our previous meeting topic)19:22
*** novas0x2a|laptop has joined #openstack-meeting19:22
mtaylorthat's SO MUCH QUICKER to load19:22
maoyoh. i c..19:22
maoyhttps://jenkins.openstack.org/job/gate-nova-pylint/32/violations/file/nova/utils.py/?19:22
maoyanything static for this type?19:23
jeblairmaoy: no... remeber in the code review i mentioned i would like either an html or formatted text report?19:23
jeblairmaoy: this is why19:23
maoyjeblair: yup. this is really nice..19:24
maoyjeblair: i can stand it being this slow. :)19:24
maoynot very very slow. :)19:24
jeblairmaoy: so if you output something nice to the console, or to a separate html or txt file, we can copy it over.19:24
*** markmcclain has quit IRC19:24
clarkbpylint has an html output format19:25
jeblairmaoy: i'm not clear -- are you saying you prefer slow and the pretty jenkins output?19:25
mtaylorjeblair: so - a generalized pylint and pep8 output format to html converter...19:25
mtayloror what clarkb said19:25
jeblairclarkb: yes, but maoy's script hides it19:25
* mtaylor shuts up - jeblair and clarkb have things well in hand19:25
maoyclarkb: jeblair is right. I had to parse pylint's output so no html from pylint.19:26
maoyjeblair: I think the current output format is good enough for me. :)19:26
maoyjeblair: but I wonder if it's possible to link the result of this to Jenkin's comment in Gerrit.19:27
jeblairmaoy: so why not turn it on as a gate job when it's ready?19:27
maoyjeblair: that would take a while for people to get comfortable with it as a gate job I guess.19:28
jeblairmaoy: do you think people are going to pay attention to it if it's not a gate job?19:28
maoyjeblair: I think so. For example, smokestack is not gate job per se19:29
maoybut it's a warning sign19:29
*** ryanpetrello has quit IRC19:29
maoybut I guess it's not some existing function that's already available to use in Jenkins, right?19:30
jeblairi just remember people not ever really caring if they increased the pylint count, unless we gated on it, and the one project we were gating on pylint eventually got tired of it.19:30
clarkbas a quick hack to get parsable output and html can you simply run pylint twice?19:30
mtaylorclarkb: he needs to filter the already seen errors from the output19:31
clarkbah19:31
jeblairmaoy: correct, it's not an existing feature; it would be a (fairly small) change to zuul to do that.19:31
maoyckarkb: mtaylor is right. but we do have parsable output now19:31
jeblairmaoy: if we think that's the way we want to go, i can add that to zuul19:32
jeblairmtaylor: you were around in the old pylint days, what do you think?19:33
maoythe spectrum is silent pipeline -> warning in jenkins -> gate function.19:34
* LinuxJedi suddenly imagines mtaylor dressed as Obiwan19:34
jeblairLinuxJedi: what's oubiwann wearing then?19:34
maoyat the moment it seems I have enough headwind to do it as a gate function19:34
LinuxJedijeblair: a dusty old cloak, and talks about the good old days when he turned boys evil or something19:35
maoybut silent pipeline seems a bit too silent..19:35
jeblairso the change to zuul would be that an individual job could be marked as non-voting, so it could be included in the check and gate pipelines, but its vote isn't counted when determining whether to run the success or failure actions.19:36
maoyjeblair: that's exactly what I was hoping for..19:36
jeblairzuul would report "gate-nova-pylint: FAILURE", but if nothing else failed, the overall verified status would still be +1 or +2.19:36
*** bcwaldon has joined #openstack-meeting19:36
*** markmcclain has joined #openstack-meeting19:37
clarkbis that much better than simply running it as a check test and not a gate test?19:37
clarkbI would be worried about confusing people19:37
jeblairclarkb: that's a good idea too, but that would mean a -1 verified vote on check, and the same change could get a +2 verified vote on gate...19:37
maoyclarkb: interesting. I haven't thought about that..19:37
*** marek_ has quit IRC19:38
jeblairclarkb: that's also a change in how the system currently works... anyone who ignores verified=-1 changes would be disrupted by that19:38
jeblairclarkb: but otherwise, does make a lot of sense.19:38
maoyjeblair: good pt. might slightly confusing..19:38
clarkbya I think either way some education has to happen.19:39
LinuxJediprobably would have made more sense in a 0-2 rating on verified19:39
clarkbso picking the less painful route which appears to be not counting a test against the verified vote is the way to go19:39
jeblairwe can annotate the test in the message with "non-voting" or something if that's helpful.19:39
LinuxJedi++19:40
maoyor is it possible for jenkins to post another comment separately just to show pylint result as FYI?19:40
LinuxJedithe way gerrit works that would initially hide one or the other comment19:40
jeblairmaoy: and it generates email, so we try to keep the number of comments down19:40
LinuxJedithat too :)19:40
maoygot it..19:41
jeblairokay, so i think we're all leaning toward the non-voting test solution....19:41
maoy+1 on that19:41
jeblairmaoy: i'll work that up and point you at the change when it's ready19:41
maoyjeblair: thanks much. i'll talk to other nova folks to see their opinion.19:42
*** ryanpetrello has joined #openstack-meeting19:42
maoyjeblair: one thing is that pylint job does take a while to run.. not sure if it matters19:42
clarkbtempest currently takes about 15 minutes I think19:43
jeblairmaoy: it takes about as long as the unit tests, and we run all the jobs in parallel, so there's no net change19:43
jeblairand yeah, tempest takes even longer.  :)19:43
maoycool..19:43
jeblairmaoy: we even test multiple changes in parallel (that's what zuul is all about)19:43
maoybtw, there is some change in lintstack19:44
maoypreviously there is a pylint_exception committed in the source tree to record what errors have been seen before19:44
LinuxJedinow we just need to work on a way of testing changes before people write them19:44
maoyin the new code, that file is auto generated from HEAD~1 every time so there is no need to maintain that19:45
jeblairLinuxJedi: easy "tox && /bin/false".  they all fail.19:45
LinuxJedilol :)19:45
jeblairmaoy: that may be a problem.19:45
maoyhttps://review.openstack.org/#/c/11444/9/tools/lintstack.sh19:46
maoythat's how I deal with it now..19:46
jeblairmaoy: that makes some assumptions about the state of the git tree that may not be correct.19:47
* jeblair is thinking19:47
mtaylorjeblair: actually - interestingly enough - if you have a sequence of merges19:49
mtaylorjeblair: shouldn't the first merge in the sequence throw the pylint error, but then others in the sequence not?19:49
maoyare you guys thinking about merges with multiple parents?19:50
jeblairso the thing i'm considering is...19:50
mtaylormaoy: no, we do a lot of things in support of parallel testing19:50
jeblairwell, i am also thinking of merge commits19:50
jeblairwhat if HEAD is a merge commit?19:50
mtaylorme. that too19:51
mtaylormmm. that too19:51
jeblair(it usually is, currently)19:51
maoyoh. you mean the files could be in use by other tests, like the unit tests?19:51
jeblairmaoy: let's talk about that in a second -- first let's focus on "HEAD is a merge commit"19:51
*** ryanpetr_ has joined #openstack-meeting19:51
*** jk0 has joined #openstack-meeting19:51
jeblairmaoy: you are comparing HEAD to HEAD~1...19:51
*** dhellmann has joined #openstack-meeting19:51
jeblairmaoy: wouldn't that compare the commit "Merge 'my change'" with "my change"19:52
* mtaylor believes jeblair is correct19:52
maoynot really.. see the git logs here: https://jenkins.openstack.org/job/gate-nova-pylint/32/console19:53
maoysomehow it's fast-forwarded so HEAD is not a merge commit19:53
jeblairmaoy: i mean, it might compare "Merge 'my change'" with "the previous head", but that depends on the order of the parent commits, which i'm not sure is guaranteed.19:53
jeblairmaoy: we fast-forward if possible, but that's only possible if you have rebased immediately before testing19:54
jeblairmaoy: otherwise, we merge, which is usually what happens when changes actually land19:54
jeblairmaoy: see the commit history here: https://github.com/openstack/nova/commits/master19:54
*** ryanpetrello has quit IRC19:54
maoyjeblair: it seems that git review is doing that rebase automatically now19:54
jeblairmaoy: yes.  and that's actually about to change19:55
jeblairmaoy: future versions won't do that anymore.19:55
jeblairi think we're about to run out of time..19:55
maoyjeblair: ok.. so what should I compare to against HEAD if not HEAD~1?19:55
jeblairmaybe we should continue this conversation in #openstack-infra19:55
mtaylorI think next step here is that we need to test the HEAD v. HEAD~1 logic in some different scenarios19:56
mtaylorand also continue the discussion in #openstack-infra19:56
maoyagree19:56
mtaylork. I'm calling it19:56
maoyI have to leave for half an hour around 4pm EDT (i.e. in 5 minutes)..19:56
mtaylor#endmeeting19:57
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"19:57
openstackMeeting ended Tue Aug 21 19:57:01 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-19.03.html19:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-19.03.txt19:57
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-19.03.log.html19:57
*** Shrews has left #openstack-meeting19:59
*** heckj has joined #openstack-meeting20:00
*** markmc has joined #openstack-meeting20:00
*** ewindisch_ has joined #openstack-meeting20:13
*** Ravikumar_hp has quit IRC20:14
*** ewindisch has quit IRC20:15
*** ewindisch_ is now known as ewindisch20:15
*** Ravikumar_hp has joined #openstack-meeting20:18
*** dprince has quit IRC20:18
*** cp16net is now known as cp16net|away20:21
*** markmcclain has quit IRC20:22
*** jk0 has left #openstack-meeting20:23
*** markmcclain has joined #openstack-meeting20:27
*** markmcclain has quit IRC20:33
*** markmcclain has joined #openstack-meeting20:34
*** mrmartin has joined #openstack-meeting20:39
*** oubiwann1 has joined #openstack-meeting20:43
*** cp16net|away is now known as cp16net20:44
*** dcramer_ has quit IRC20:48
*** dolphm has quit IRC20:53
*** jrd-redhat has quit IRC20:53
*** heckj has quit IRC20:56
*** johnpur has quit IRC20:56
*** johnpur has joined #openstack-meeting20:57
*** gabrielhurley has joined #openstack-meeting20:59
*** jimfehlig has joined #openstack-meeting20:59
ttxo/20:59
*** anniec has quit IRC21:00
bcwaldonhey hey21:00
notmynameo/21:00
ayoungO/21:00
ayoungstanding in for heckj21:00
gabrielhurleyttx: I'll be your devcamcar today21:00
ttxheckj, notmyname, bcwaldon, jgriffith, vishy, danwent: around ?21:01
bcwaldonttx: I was first!21:01
ttxayoung: oh, noted21:01
danwento/21:01
notmynamettx: heh21:01
notmynamehere21:01
ttxsome weird lag here21:01
bcwaldonsuuuure21:02
ttxso... still missing jgriffith, vishy21:02
jgriffitho/21:02
ttxok, let's start21:02
ttx#startmeeting21:02
openstackMeeting started Tue Aug 21 21:02:43 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttx#info We are under FeatureFreeze for everything but Swift, so please take extra care in reviews21:03
ttx#info Core reviewers should flag changes that add a new feature, modify the behavior without fixing a bug, modify translatable strings or add/modify a configuration option21:03
ttx#topic Keystone status21:03
*** openstack changes topic to "Keystone status"21:03
ttxayoung: o/21:03
ttx#link https://launchpad.net/keystone/+milestone/folsom-rc121:04
ttxSo one blueprint was granted an exception, yours :)21:04
ttx* https://blueprints.launchpad.net/keystone/+spec/pki21:04
ttxayoung: How far are you ? I couldn't really find reviews linked to this...21:04
ayoungPKI was done for a while, with the exception of Revocation.  Revocation was merged last week21:05
ttxIIUC that means it's now all in ?21:05
ayoungthere is a bug that is up for review21:05
*** thingee has joined #openstack-meeting21:05
ayoungttx, yes, in master21:05
ttxayoung: ok, will mark that blueprint implemented. The bug was targeted to folsom-rc1 ?21:05
ayoungHeh, it will be shortly.21:06
ttxhmm, apparently not21:06
ttxok :)21:06
ttxMore generally, your RC bug list is very empty21:06
ttxSomehow I doubt those two listed issues are the only one standing between you and a release-quality RC1 :)21:06
vishyo/21:07
ttxWould be good to go through bugs and start targeting all bugs you think should be fixed before we can release Folsom21:07
vishy(btwo)21:07
ayounghttps://bugs.launchpad.net/keystone/+bug/103830921:07
uvirtbotLaunchpad bug 1038309 in keystone "auth_token fails to fetch revocation list" [Undecided,In progress]21:07
ayoungttx, heckj was doing just that21:07
ttxayoung: targeted21:07
ttx#action heckj to go through keystone buglist and target release blockers to RC1 where appropriate21:08
ayoungfrom today's keystone meeting:21:08
*** anniec has joined #openstack-meeting21:08
ayounghttp://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-18.02.html21:08
ttxLooking at triage now... looks like you triaged them all ?21:08
ayoungJoe was very busy21:09
ttxayoung: I think once the RC buglist is built you should be in good shape21:09
ayoungAgreed21:09
ayoungwe've been trying to keep an eye to stability21:09
ttxayoung: then it's all downhill with bugfixing and bug assignment to RC121:10
*** mawagon1 has left #openstack-meeting21:10
ttxayoung: anything else you wanted to mention ?21:10
ayoungNo, I think those are the important things21:10
ttxQuestions about Keystone ?21:10
*** devananda has quit IRC21:11
ttx#topic Swift status21:11
*** openstack changes topic to "Swift status"21:11
notmynamehi21:11
ttxnotmyname: o/21:11
ttxnotmyname: Did you send that email with your 2.0 thoughts ?21:11
*** mnewby has quit IRC21:11
notmynameI did not. I'm still collecting them21:12
ttx#action notmyname to send an email to openstack-dev with 2.0 thoughts21:12
notmynameturns out it's an issue with lots of factors :-)21:12
ttxnotmyname: for the release date, would be good if it was before Sep 1321:13
ttxi.e. at least two weeks away from release21:13
notmynamehow about sept 13 then?21:13
ttx(common release)21:13
ttxnotmyname: works for me21:13
notmynamettx: is that for the QA'd release or the RC?21:13
ttxQA'd release21:13
*** lifeless has joined #openstack-meeting21:14
notmynameah21:14
*** mnewby has joined #openstack-meeting21:14
notmynameok. we'll see what we can do21:14
*** mrmartin has quit IRC21:14
ttxok, keep me posted21:14
ttxnotmyname: anything else ?21:14
notmynamewe have a lot of changed I'd like to see get in21:14
notmynamenope21:14
ttxif there are so many changes it might make sense to include 1.6.1 in Folsom21:15
ttxand keep 2.0 as an early Grizzly thing21:15
notmynameor 1.7 in folsom and 2.0 "later"21:16
notmyname;-)21:16
ttxheh21:16
* ttx holds on before creating a 2.0 in Folsom series :)21:17
ttxQuestions on Swift ?21:17
ttx#topic Glance status21:17
*** openstack changes topic to "Glance status"21:17
ttxbcwaldon: around ?21:17
*** oubiwann1 has quit IRC21:18
ttxlet's skip to Quantum, Brian told me he might have to leave IRC for a few21:18
ttx#topic Quantum status21:18
*** openstack changes topic to "Quantum status"21:18
ttxdanwent: yo21:18
*** oubiwann1 has joined #openstack-meeting21:18
danwenthello21:18
ttxdanwent: congrats by the way21:18
danwentthanks :)21:18
danwentshe's right by me… hope you can't hear her scream via IRC :)21:19
ttxI can just imagine21:19
ttx#link https://launchpad.net/quantum/+milestone/folsom-rc121:19
ttxGot only two standing Quantum-code-related exceptions on that list:21:19
ttx* https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp (nati)21:19
danwentyes, still need to send you mail, sorry21:19
ttx* https://blueprints.launchpad.net/quantum/+spec/test-agent (nati)21:19
ttxThe rest is either completed, doc, devstack or quantumclient related, IIUC21:19
danwentthat is true in terms of blueprints.21:20
danwentthere are two other items that are tracked as bugs, but are signfiicant enough that i'm treating them like FFE items.21:20
danwentxml support21:20
danwentand the last phase of bob's provider networks branch21:20
ttxdanwent: hmm, we'll come back to those later21:20
danwentanything that smells like an FFE, I've told people needs to be proposed for non-WIP review by next monday21:20
ttxdanwent: how are those two above doing ?21:20
danwentthe bps or the bugs?21:21
ttx(nati's ones)21:21
danwentboth are under review already (they have been since F-3)21:21
danwentthe test-agent is for testing only21:21
danwentand is pretty close21:21
danwentthe multi-host DHCP, i need to re-review since providing feedback.21:21
danwentmulti-host patch got much smaller in review, which is good.21:22
ttxboth should land before the end of week ?21:22
danwentI would say by start of next week, giving them the weekend, as nati is on vacation at least part of this week.21:22
danwentthough he's responding to reviews (or at least has been so far).21:22
mtaylordanwent, ttx: status on quantum in devstack-gate?21:23
danwentmtaylor: glad that you mentioned it.  we were going to wait for one of the above items, but after discussing it at the meeting yesterday, we're just going to go ahead with a simple gate to start.21:23
mtaylordanwent: great!21:23
danwentmtaylor: will send you email after the meeting, but have told team this is top priority21:23
*** maoy has quit IRC21:24
danwent(assuming we can get some devstack review help)21:24
mtaylordanwent: you always make me super-happy21:24
mtaylordanwent: we'll prioritize that21:24
danwentgreat, thanks.21:24
jeblair+121:24
ttxdanwent: link to devstack review ?21:24
danwenthttps://review.openstack.org/#/c/10828/21:24
ttx#help devstack review help needed https://review.openstack.org/#/c/10828/21:24
ttxok, so about those two bugs-that-look-like-features21:25
danwentyes21:25
ttxXMl support sounds like something I'd prefer to have a blueprint about21:25
ttxif only to track the major features that landed in Folsom21:25
ttxNo so sure about the other one, which looks like a gap bug21:26
danwentagreed.  I will up to to a BP.  we had a branch proposed for review for XML support during F-3, but I wasn't happy with it.  I told the two people who really wanted XML support in Folsom that they could have a week to clean it up and get it approved.21:26
danwentttx: yes, other one is last bit of something that landed in F-3.  we could have deferred the BP, but instead we created a 'follow-on' bug.21:26
ttxdanwent: not really happy to see that landing now, tbh. It affects the work of QA people quite a bit21:26
danwentttx: the xml?21:27
ttxand as famous examped showed, untested XML is like no XML21:27
ttxexamples*21:27
ttxdanwent: yes21:27
danwenti'm ok with you denying it…21:27
danwentif it makes you unhappy21:27
*** oubiwann1 has quit IRC21:27
danwentit doesn't make me very happy either21:27
danwentbut the folks seem close, so I told them to take a shot.21:27
ttxhmm, we'll discuss that offline21:27
ttx#action danwent/ttx to discuss XML support FFE status21:28
danwentand if it didn't make the core devs happy by monday, we'd drop it from folsom21:28
ttxLooking at bugs now... good list21:28
annegentledanwent: the API spec under review has XML samples21:28
annegentlebut yes discuss offline21:28
ttxDid you go through the complete open bugs list to build it ?21:28
danwentannegentle: yes, we will have to remove those if it doesn't make it.21:28
annegentledanwent: noted21:28
danwentttx:  not yet.  can do it today… i'll pull the baby card :)21:28
ttxWould be great to get people assigned to each of those too21:29
ttxdanwent: also someone should carete that XML support blueprint21:29
ttxcreate*21:29
danwentyes.  I filed a few more last night, as there are some squishy points on integration of nova + quantum that we need to firm up ASAP.21:29
danwentttx: I will21:29
ttx(Generally when noone is assigned to them they don't progress fast enough for RC1.)21:29
ttx(the bugs)21:29
ttxLooking at bug triaging, you also have 22 untriaged21:29
danwentttx: my bad.  will do full bug pass today21:30
ttxdanwent: delagate, dude :)21:30
*** dolphm has joined #openstack-meeting21:30
*** oubiwann1 has joined #openstack-meeting21:30
danwentttx: good point :)21:30
*** s0mik has quit IRC21:30
annegentleor danwent: man up, daddy-o :)21:30
ttx#action danwent and team to triage all bugs and build the RC bug list21:30
ttxdanwent: Anything else ?21:30
annegentlesleep, schmeep21:30
annegentle:)21:30
danwentnope, clearly have a bit of catch-up to do.  will ping you offline about xml. and will ping CI people about gate.21:31
ttxQuestions on Quantum ?21:31
ttxbcwaldon: back?21:31
bcwaldonttx: yes21:31
ttx#topic Glance status21:31
*** openstack changes topic to "Glance status"21:31
ttx#link https://launchpad.net/glance/+milestone/folsom-rc121:31
ttxNo exception, yay21:31
ttxLooking at bugs, I see you got a decent list of RC bugs21:32
*** ewindisch has quit IRC21:32
bcwaldonyepper, just a buncha bugs21:32
bcwaldonI pushed off bugfixin until now21:32
ttxIs that list reasonably complete ? i.e. did you go through the whole open bugs list ?21:32
bcwaldonyes21:32
ttxAwesome.21:32
*** dolphm has quit IRC21:32
bcwaldonI might expect to see a few more added21:32
bcwaldonbut maybe not21:32
ttxWell, you did your homework, I see.. anything specific you wanted to mention ?21:32
bcwaldonwe'll see :)21:32
bcwaldonI did want to highlight my message to the ML covering Glance's Folsom release http://markmail.org/message/rpewwtqcb2qxa5t521:33
*** dhellmann has quit IRC21:33
bcwaldonthat has some good info in it for people not following glance development too closely21:33
ttxbcwaldon: yes, I just read it. Will definitely help in release notes and messaging around folsom release21:33
mtaylor++21:33
bcwaldonyes, I'll condense it down for official release notes21:33
*** oubiwann1 has quit IRC21:34
bcwaldonthats it from me21:34
ttxQuestions on Glance ?21:34
ttx#topic Cinder status21:34
*** openstack changes topic to "Cinder status"21:34
jgriffithYo21:34
ttxjgriffith: o/21:34
*** s0mik has joined #openstack-meeting21:34
ttx#link https://launchpad.net/cinder/+milestone/folsom-rc121:35
*** dhellmann has joined #openstack-meeting21:35
ttxNo exception either, yay21:35
jgriffith:)21:35
jgriffithQuotas should be closing as soon as I get reviews21:35
ttxOn the bug side though, you should start to aggressively triage your bug list and mark more of those RC (by targeting them to folsom-rc1)...21:35
ttx... as I suspect Cinder is more than 3 bugs away from perfection ?21:35
jgriffithThe Netapp ones I have to find Ben.. he's been MIA since last week21:35
jgriffithLOL21:35
jgriffithSure.. that sounds good21:35
ttxYou also have 11 untriaged bugs that you should probably go through21:35
jgriffithI have plans for most of them21:35
jgriffithI want to get input from the core team in tomorrows meeting though21:36
ttx#action jgriffith and Cinder team to triage new bugs and come up with a list of release blockers21:36
jgriffithThere will be at least 4 added to RC1 after tomorrow21:36
* ttx prefers known targeted bugs to unknown quality21:36
jgriffithfair enough21:37
ttxjgriffith: that's all I had for you... anything you wanted to mention ?21:37
jgriffithNope... just pushing these, then trying to get everybody to pitch in on docs21:37
*** ryanpetr_ has quit IRC21:37
ttxLess exceptions give more time for bugfixing and documentation, yay21:38
annegentlejgriffith: just to clarify, both nova-volume and cinder will exist as options in folsom, correct?21:38
jgriffithAnybody wants to help with reviews that would be great21:38
jgriffithannegentle: yes21:38
*** oubiwann1 has joined #openstack-meeting21:38
jgriffithannegentle: There will be a synch between the two after RC121:38
annegentle#info the docs need to cover both nova-volume and cinder21:38
jgriffithOr for RC121:38
ttxjgriffith: are you lacking reviewers ?21:38
jgriffithThis week I seem to be21:38
ttx#help Cinder reviewers wanted21:39
ttxQuestions on Cinder ?21:39
ttx#topic Nova status21:39
*** openstack changes topic to "Nova status"21:39
ttxvishy: hey21:39
ttx#link https://launchpad.net/nova/+milestone/folsom-rc121:39
*** ryanpetrello has joined #openstack-meeting21:39
ttxvishy: ?21:40
vishyhi21:40
ttxHi! Looking at standing exceptions:21:40
ttx* https://blueprints.launchpad.net/nova/+spec/scheduler-resource-race21:40
ttxvishy: Under review ? How close is it ?21:40
vishyi think very21:41
ttxcool.21:41
ttx* https://blueprints.launchpad.net/nova/+spec/os-api-network-create21:41
ttxwhat about this one ?21:41
vishyactually the first is implemented21:41
vishythe second we were giving a chance to the author to fix it, or else markmc will update it21:41
markmcI sorted out the blocking API issues today21:42
ttxvishy: ok will mark it done21:42
vishyI think we will have him do it since the author is not doing much21:42
ttx* https://blueprints.launchpad.net/nova/+spec/project-specific-flavors21:42
markmcttx, network-create isn't done yet21:42
ttxmarkmc: right21:42
markmcttx, network-associate is21:42
*** patelna has quit IRC21:42
vishyk so it looks good21:42
ttxmarkmc: I think vishy's point was that scheduler-resource-race was done... right ?21:42
vishyjust needs an approval it is good by me21:43
vishyttx: correct21:43
markmcah21:43
vishyso the project-specific flavor just needs some reviews21:43
vishyi think it is good21:43
ttxvishy: ok, so everything should be in by mid-week, cool21:43
ttxexcept the network-create stuff which shoiuld get done by the end of the week ?21:43
vishyno i didn't realize it is done21:44
vishye21:44
vishyeverything should be in by thursday i think21:44
med_?21:44
*** rnirmal has quit IRC21:44
ttxOK. We also have late FFEs requested by mtaylor:21:44
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2012-August/000750.html21:44
vishyso the remaining question is whether to let the entry point stuff in21:44
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2012-August/000751.html21:44
vishyi like that it simplifies external drivers.21:44
ttxvishy: I think it's relatively harmless21:45
vishyif so it will probably make external drivers much happier21:45
mtaylorit _should_ failover to current behavior in case someone is making use of the current import-basd behavior21:45
vishymarkmc: thoughts?21:45
ttxvishy: it either loads or doesn't, so easy to see problems ?21:45
markmcvishy, haven't look properly yet and don't really understand what it's all about21:45
mtaylorit breaks the unittest suite REALLY quickly when it's broken :)21:45
* markmc plans to look in the morning21:45
mtaylormarkmc: tl;dr - ability to use entry points to load virt and scheduler drivers21:46
ttxvishy: maybe decide by next Nova's meeting ?21:46
vishymarkmc: it allows drivers to be loaded from entrypoints in addition to class names21:46
ttxand in the mean time, keep it in review ?21:46
vishyttx: sounds good21:46
vishywe will discuss it in the meeting21:46
*** patelna has joined #openstack-meeting21:47
markmcif it's harmless, we can assume FFE probably?21:47
mtaylorvishy: fwiw, I'm AFK starting tomorrow - but if something minor needs to get tweaked, I'm more than happy for someone to edit and re-push those21:47
ttx#action nova-core and ttx to review FFE for entry point stuff by Thursday21:47
ttxmarkmc: I have to have a deeper look, but on the tin it says it's harmless21:47
ttxvishy: Switching to RC bugs now, you got 11 targeted21:48
ttxBut I think you can't really target until some serious triaging is done. A huge effort is needed in that area. We have 101 untriaged bugs21:49
ttxI feel like we won't have a good RC list until we get those confirmed and prioritized.21:49
ttxvishy: Do you have a plan to handle that ?21:49
vishyttx: yes, I've just been targetting the ones that i find myself21:49
markmcwow, 10121:49
vishyttx: yeah it is hard to keep up but nova-core is focusing on bugs so i hope we can.21:49
ttxit's a shitty job but needs to be done.. and the sooner the better21:49
ttxI can help, within my limited abilities.21:50
markmcI'm up for a bug triage day if we got a handful of nova-core folks together21:50
ttxmarkmc: I'm in vacation next week, so can't really coordinate that21:50
ttxbut I can give you the keys to the party hall21:51
ttxvishy: do you think a bugday would help ?21:51
ttxor just asking everyone in nova-core to do 15 ?21:51
vishywe need a bug 2 weeks21:52
vishyevery day should be a bug day21:52
ttxvishy: yes at this point we ned to get the list back to 0.. then handle incoming reports21:53
ttxnee*21:53
ttxd21:53
ttxvishy: so asking everyone to take at least 101/nova-core bugs ?21:53
*** dolphm has joined #openstack-meeting21:54
*** koolhead17 has joined #openstack-meeting21:55
ttxrunning out of time21:55
ttx#action vishy to find a way to get untriaged bugcount to 021:55
ttxQuestions on Nova ?21:55
annegentleo/21:55
*** littleidea has quit IRC21:55
ttxannegentle: go ahead21:55
annegentle It looks like https://blueprints.launchpad.net/nova/+spec/disable-server-extensions is marked as "Implemented" but I didn't see doc additions to document the changes, what's a good plan for that?21:55
annegentleweird underlines, sorry21:55
annegentle(asking vishy )21:56
ttxlooks like we lost him, we'll let him answer asynchronously21:56
ttx#topic Horizon status21:56
*** openstack changes topic to "Horizon status"21:56
ttxgabrielhurley: hey21:56
gabrielhurleyttx: hi21:56
ttx#link https://launchpad.net/horizon/+milestone/folsom-rc121:56
ttxNo feature freeze exception, let's look at the RC bug list...21:57
ttxgabrielhurley: only 8 open bugs on the RC bug list ?21:57
gabrielhurleythere's a recent request for an FFE for quantum public network support. I haven't seen code yet, so I'm holding off on seeing how invasive it is before deciding to ask for an FFE21:57
*** ewindisch has joined #openstack-meeting21:57
ttxgabrielhurley: good to know, thanks21:57
gabrielhurleyand yeah, the bug list is accurate21:57
gabrielhurleyprobably handle all of it this week21:57
*** Gordonz has quit IRC21:57
ttxgabrielhurley: fwiw given that horizon is at the downstream of everything else it's fair that you ask a bit late21:58
ttx(foir FFE)21:58
gabrielhurleyheh. thanks.21:58
ttxDid you go through the whole bug list to target blockers ?21:58
ttxI see one critical bug not targeted yet: bug 96788221:58
uvirtbotLaunchpad bug 967882 in horizon "Volumes, volume snapshots, instance snaphots and keypairs all show cross-tenant info when logged in as admin" [Critical,Confirmed] https://launchpad.net/bugs/96788221:58
ttxlooks like it needs to be de-prioritized or RC1-targeted :)21:59
gabrielhurleythat one is a known issue in nova, though I hear they may have recently patched it21:59
gabrielhurleyit's not actually a horizon fix, just a reminder21:59
gabrielhurleyand yeah, I go through the whole backlog periodically21:59
ttxhmm, any way we could not keep that bug open if it's just a reminder ?22:00
gabrielhurleysure. I'll do something with it22:00
ttxOn the triaging side, you look on top of it...22:00
ttxgabrielhurley: Anything else you wanted to mention ?22:00
gabrielhurleyyessir22:00
gabrielhurleydon't believe so. just test away!22:00
ttxQuestions for Horizon ?22:00
ttxannegentle: looks like you'll have to ask vishy offline. Or at the Nova meeting Thursday22:01
ttx#topic Other Team reports22:01
*** openstack changes topic to "Other Team reports"22:01
annegentleshall I do a creiht sigh just for the effect?22:01
ttxannegentle: that would do it22:01
ttxAny other team lead with a status report ?22:01
annegentleo/22:01
* annegentle sighs22:01
annegentleAs you saw from my mailing list note, now's the time to kick docs up a notch.22:01
*** ayoung has quit IRC22:01
vishyannegentle: it is going to be part of the api testing i'm putting together22:01
annegentleWe're going to be moving reviews through22:01
annegentleI've got a new CLI guide in review at https://review.openstack.org/#/c/11744/22:01
annegentle#help Please review new CLI guide at https://review.openstack.org/#/c/11744/22:02
annegentlevishy: ok, I'll also log doc bugs such as "document os-multiple-create"22:02
markmcttx, just a note that openstack-common has branched for folsom22:02
*** EmilienM has quit IRC22:02
markmcttx, projects should be syncing from stable/folsom until grizzly opens22:02
ttx#info openstack-common has branched for folsom, projects should be syncing from stable/folsom until grizzly opens22:02
ttx#topic Open discussion22:03
*** openstack changes topic to "Open discussion"22:03
ttxAnything else, anyone ?22:03
*** patelna has quit IRC22:03
*** oubiwann1 has quit IRC22:03
* ttx moves the discussion about nova bug triaging to #openstack-dev22:04
ttx#endmeeting22:04
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"22:04
openstackMeeting ended Tue Aug 21 22:04:04 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-21.02.html22:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-21.02.txt22:04
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-21.02.log.html22:04
ttxgood $END_OF_DAY everyone22:04
*** anniec_ has joined #openstack-meeting22:05
*** anniec has quit IRC22:06
*** anniec_ is now known as anniec22:06
*** gabrielhurley has left #openstack-meeting22:07
*** ryanpetrello has quit IRC22:08
*** kindaopsdevy has quit IRC22:10
*** matwood has quit IRC22:11
*** matwood has joined #openstack-meeting22:12
*** oubiwann1 has joined #openstack-meeting22:13
*** dolphm has quit IRC22:19
*** markmcclain has quit IRC22:19
*** markmc is now known as mcaway22:20
*** oubiwann1 has quit IRC22:24
*** aclark_ has joined #openstack-meeting22:24
*** ewindisch has quit IRC22:27
*** sacharya has quit IRC22:37
*** mnewby has quit IRC22:38
*** mnewby has joined #openstack-meeting22:39
*** mnewby has quit IRC22:39
*** mnewby has joined #openstack-meeting22:39
*** kindaopsdevy has joined #openstack-meeting22:42
*** matwood has quit IRC22:42
*** ewindisch has joined #openstack-meeting22:42
*** ryanpetrello has joined #openstack-meeting22:43
*** ryanpetrello has quit IRC22:45
*** jimfehlig has quit IRC22:53
*** anniec_ has joined #openstack-meeting23:07
*** anniec has quit IRC23:09
*** anniec_ is now known as anniec23:09
*** shang has quit IRC23:10
*** lloydde has quit IRC23:12
*** aclark_ has quit IRC23:14
*** oubiwann1 has joined #openstack-meeting23:15
*** mnewby has quit IRC23:18
*** oubiwann2 has joined #openstack-meeting23:28
*** oubiwann1 has quit IRC23:28
*** dolphm has joined #openstack-meeting23:29
*** dolphm has quit IRC23:34
*** dhellmann has quit IRC23:37
*** oubiwann2 has quit IRC23:37
*** markmcclain has joined #openstack-meeting23:37
*** ryanpetrello has joined #openstack-meeting23:39
*** s0mik has quit IRC23:43
*** dhellmann has joined #openstack-meeting23:45
*** thingee has left #openstack-meeting23:50
*** Ravikumar_hp has quit IRC23:52
*** ryanpetr_ has joined #openstack-meeting23:54
*** ryanpetrello has quit IRC23:57

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