Wednesday, 2011-08-03

*** amccabe has quit IRC00:26
*** medberry is now known as med_out00:29
*** heckj has quit IRC00:36
*** jmckenty_ has joined #openstack-dev00:49
*** jmckenty_ has quit IRC00:54
*** jakedahn has quit IRC00:56
*** mgius has quit IRC00:58
*** mwhooker has quit IRC01:04
*** HugoKuo_ has joined #openstack-dev01:09
*** HugoKuo has quit IRC01:09
*** negronjl has joined #openstack-dev01:20
*** jdurgin has quit IRC01:27
*** dragondm has quit IRC01:33
*** Tushar has quit IRC01:46
*** jakedahn has joined #openstack-dev01:47
*** mfer has joined #openstack-dev02:33
*** mfer has quit IRC02:34
*** mfer has joined #openstack-dev02:35
*** mfer has quit IRC03:05
*** negronjl` has joined #openstack-dev03:17
*** negronjl` has quit IRC03:17
*** martine_ has joined #openstack-dev03:29
*** martine_ has quit IRC03:43
*** negronjl` has joined #openstack-dev03:46
*** dolphm_ has joined #openstack-dev03:48
*** negronjl has quit IRC03:48
*** negronjl has joined #openstack-dev03:48
*** dolphm_ has quit IRC03:51
*** negronjl has quit IRC03:51
*** dolphm_ has joined #openstack-dev03:51
*** negronjl` is now known as negronjl03:51
*** dolphm_ has quit IRC03:52
*** negronjl has quit IRC03:54
*** negronjl has joined #openstack-dev03:54
*** negronjl has quit IRC04:25
*** negronjl has joined #openstack-dev04:33
*** negronjl has joined #openstack-dev04:35
*** negronjl has quit IRC04:36
*** negronjl has joined #openstack-dev04:36
*** negronjl has quit IRC04:37
*** negronjl has joined #openstack-dev04:37
*** zaitcev has quit IRC04:42
*** mwhooker has joined #openstack-dev05:07
*** RobertLaptop has joined #openstack-dev05:18
*** zedas has quit IRC06:01
*** termie has quit IRC06:01
*** zedas has joined #openstack-dev06:02
*** termie has joined #openstack-dev06:02
*** mwhooker has quit IRC06:07
HugoKuo_http://pastebin.com/HrZsgjWd      while the additional compute node fire up instance  , failed with this error in r136006:44
*** reidrac has joined #openstack-dev07:11
*** mnour has quit IRC07:18
*** nickon has joined #openstack-dev07:57
*** mnour has joined #openstack-dev08:09
*** chemikadze has quit IRC08:13
*** chemikadze has joined #openstack-dev08:17
*** darraghb has joined #openstack-dev08:58
*** mnour has quit IRC09:06
*** mnour has joined #openstack-dev09:06
*** mnour has quit IRC09:20
*** mnour has joined #openstack-dev09:20
*** mnour has quit IRC09:34
*** mnour has joined #openstack-dev09:35
*** tudamp has joined #openstack-dev10:13
tudamphi all10:28
tudampi'm doing some testing with the distribute scheduler10:28
tudampi saw that using libvirt get_host_stats is not implemented10:28
tudamptodo?10:28
tudampor i can find an initial implementation in some branch?10:30
*** rods has joined #openstack-dev10:41
*** yamahata has joined #openstack-dev10:49
*** BK_man_ has joined #openstack-dev11:14
*** BK_man has quit IRC11:15
*** BK_man_ is now known as BK_man11:15
*** chemikadze has quit IRC11:16
*** markvoelker has joined #openstack-dev11:18
*** mfer has joined #openstack-dev11:21
blamartr3buchet: negative, not currently working on lp815957, I originally thought I knew what was up... dprince might be though11:52
*** bcwaldon has joined #openstack-dev11:53
*** chuck_ has joined #openstack-dev12:05
*** chuck_ has quit IRC12:06
*** chuck_ has joined #openstack-dev12:06
*** zul has quit IRC12:07
*** chuck_ is now known as zul12:07
*** zul has joined #openstack-dev12:07
bcwaldonmtaylor: tarmac doesn't appear to be merging branches :(12:08
*** jkoelker has joined #openstack-dev12:32
*** yamahata has quit IRC12:36
*** AhmedSoliman has joined #openstack-dev12:38
*** sandywalsh has joined #openstack-dev12:40
*** bsza has joined #openstack-dev12:50
*** nmistry has joined #openstack-dev12:55
*** chemikadze has joined #openstack-dev12:57
chemikadzeIs there any method to get compute's host name where VM is running?13:00
chemikadzeThrough API of course.13:01
*** nmistry has quit IRC13:06
bcwaldonnope, you'll have to use 'nova-manage vm list'13:29
bcwaldonchemikadze: ^13:29
*** kbringard has joined #openstack-dev13:35
*** amccabe has joined #openstack-dev13:50
openstackjenkinsProject keystone build #62: SUCCESS in 55 sec: http://jenkins.openstack.org/job/keystone/62/13:52
openstackgerritVerification of a change to openstack/keystone failed: Added support for versioned openstack MIME types  https://review.openstack.org/12013:52
openstackjenkinsdolph.mathews: Added support for versioned openstack MIME types13:52
*** dragondm has joined #openstack-dev14:04
sorenbcwaldon: It looks stuck. I'll kick it.14:22
bcwaldonsoren: thanks14:22
sorenbcwaldon: It's doing *something* now :)14:23
*** alfred_mancx has joined #openstack-dev14:23
*** cp16net has joined #openstack-dev14:26
zykes-what's a endpoint in keystone ?14:28
*** dprince has joined #openstack-dev14:33
dolphmzykes-: "Endpoint represents a service that a tenant could consume." -keystone dev guide14:37
*** mnour has joined #openstack-dev14:38
zykes-and diff for enpoint template vs endpoint ?14:40
tudampi'm doing some testing with the distribute scheduler14:43
tudampi saw that using libvirt get_host_stats is not implemented14:43
tudamp i can find an initial implementation in some branch?14:43
dolphmmtaylor: I'm not seeing a specific reason as to why this failed: https://jenkins.openstack.org/job/keystone-pylint/68/14:47
sorenhttps://jenkins.openstack.org/job/keystone-pylint/68/console14:48
sorendolphm: It seems to somewhere test whether 0 -ne 0. Which is false.14:48
sorendolphm: Do you know which script it runs?14:48
dolphmsoren: no clue14:49
*** nickon has quit IRC14:51
dolphmzykes-: all endpoints have-a template, and basically there's one template per tenant... i don't know much more beyond that14:51
kbringardthe thing I'd be curious to see, is some documentation explaining how Keystone "terms" map to Nova terms14:52
kbringardfor instance, tenant is kind of like a project14:52
sorendolphm: Ah, I was barking up the wrong tree.14:52
kbringardbut not exactly14:52
sorendolphm: It's pylint itself. Hang on.14:52
dolphmkbringard: that's been discussed quite a bit (esp on the mailing list) but I'm not sure i've seen anything officially documented14:53
kbringardyea… I suppose over time the keystone terms will just become the de-facto14:53
annegentlekbringard: dolphm: the keystone doc talks of it generically now, but certainly it could be updated: http://docs.openstack.org/incubation/identitydevguide/content/Tenant-d1e94.html14:54
annegentlesince it really depends on the service provider's implementation14:54
kbringardannegentle: right, and thanks.. that's good info14:54
dolphmkbringard: i'm personally under the impression that "tenant" is a horrible term, because it confuses absolutely everyone coming from nova/swift... and everyone explains "tenant" as being some type of "resource" ... so why not just call it a "resource" instead?14:54
kbringarddolphm: yea...14:55
kbringardI dunno, I generally just find that I bang my head against it until I figure out how it works then sort of create terms in my own mind14:55
kbringardwhich isn't a slam on how OpenStack does things, it's just how I learn best14:55
sorendolphm: Ah, I know what's going on.14:56
dolphmsoren: explain! i'm curious14:56
sorendolphm: pylint only returns succesfully if the code it examined was completely clean.14:57
dolphmsoren: which is definitely not the case14:57
*** rnirmal has joined #openstack-dev14:57
sorendolphm: Nope :)14:58
dolphmsoren: i know pylint returns a status code that you have to interpret bitwise14:58
sorendolphm: I think I fixed it. It's running again now.14:58
dolphmcool14:58
sorendolphm: Exactly. It returns 31 here.14:58
soren32 means usage error.14:58
sorenSo anything below that just means it found something to complain about. Which is a success in this context.14:58
sorenSo if $? < 32, I just exit 0 instead.14:59
dolphmsoren: 31 == 0b1111114:59
sorenYeah, it's all of them :)14:59
dolphmso basically failures across the board14:59
sorenerk.. https://jenkins.openstack.org/job/keystone-pylint/69/console15:00
sorenmtaylor: https://jenkins.openstack.org/job/keystone-pylint/69/console  <--- This job doesn't work if you do a "build now". Is that expected?15:00
dolphmsoren: i think it needs more internets15:01
*** mnour has quit IRC15:01
*** reidrac has quit IRC15:04
sorendolphm: Nah, it seems to try to access '$GERRIT_REFSPEC'15:05
sorenRather than whatever the variable called GERRIT_REFSPEC contains.15:05
* soren is on a unit testing frenzy15:06
dolphmsoren: https://jenkins.openstack.org/job/keystone-pylint/68/parameters/?15:06
sorendolphm: Right.15:06
sorendolphm: It probably gets all of those when it's triggered by Gerrit.15:07
dolphmsoren: ah15:07
sorendolphm: ...but it wasn't thig time. I just clicked "Build now".15:07
soren...which became build 69.15:07
dolphmcan we trigger it from gerrit?15:07
sorenNo clue.15:07
mtaylorsoren: you need to re-trigger it15:07
sorenmtaylor: I don't know how.15:08
* soren hasn't used Gerrit at all yet.15:08
openstackgerritVerification of a change to openstack/keystone failed: Added support for versioned openstack MIME types  https://review.openstack.org/12015:08
mtaylorsoren: if you go to build 68, and click retrigger (which I just did) it will re-do it with appropriate version info15:08
sorenOh!15:08
sorenAnd blow away the existing data?15:08
dolphmmtaylor: i assume i don't have that option, right?15:08
mtaylorsoren: nope. it does a whole new thing15:08
sorenmtaylor: Oh, lovely.15:09
sorenmtaylor: I though "re-trigger" was a Gerrit operation.15:09
sorenthought, even.15:09
mtaylorsoren: in the future, build now should also work and should build against trunk. at the moment, we have a build step which is working around a bug in the git plugin15:09
sorenmtaylor: Hm... Does it also reuse the same build steps?15:09
sorenEr..15:10
sorenMy bad.15:10
mtaylorsoren: it should use the current build steps15:10
sorenI misspelled 32.15:10
mtaylorhehe15:10
kbringarddoes keystone have it's own repo? or are we not building packages for it yet?15:11
openstackgerritA change was merged to openstack/keystone: Added support for versioned openstack MIME types  https://review.openstack.org/12015:11
dolphmkbringard: https://github.com/openstack/keystone and no15:12
kbringardcool, yea, I have the code checked out, just didn't know if there were packages yet, thanks!15:12
mtaylorsoren: yay! neat. thanks!15:12
sorenmtaylor: No problem. The same fix probably needs to be applied in a number of other places, I presume?15:12
dolphmmtaylor: soren: thanks!15:13
mtaylorsoren: eventually, yeah - keystone is the only one using a jenkins pylint job to prevent merges so far though15:13
dolphmmtaylor: can you revise our pylint threshold when you get a chance? (just broke 800.... @ 791)15:13
sorenmtaylor: Ok.15:13
mtaylordolphm: yes! and good job!15:13
mtaylordolphm: done. it's now at 79115:14
sorenGood grief...15:15
* soren is looking at the API exposed by virt drivers in Nova.15:15
* soren is not impressed15:15
DavieyAre bzr branches still being reviewed?15:16
sorenFor nova?15:16
Davieyyah15:16
sorenYes.15:16
DavieyCoulda fooled me :)15:16
sorenNova hasn't gone git yet.15:16
sorenDaviey: *chuckle* Which mp?15:16
Davieydamn it.. i just checked and it has15:17
Davieyegg on MY face.15:17
mtaylormmm. egg15:18
kbringardspeaking of which, I want breakfast15:18
mtaylorright?15:18
kbringardtotally15:18
mtaylordammit Daviey15:18
kbringardjust killed productivity for everyone in a TZ where it's morning15:19
kbringardI know someone else was just asking, but I have a quick question about the endpoint_templates table in the keystone.db15:20
kbringardfrom what I can tell, the only thing it seems to care about is the internal_url15:20
kbringardhow does the public_url and admin_url come into play there?15:20
kbringardactually, I lied, I see how the admin_url is used15:23
kbringardI don't entirely get the difference between the internal_url and the public_url15:23
*** mwhooker has joined #openstack-dev15:23
*** zaitcev has joined #openstack-dev15:37
tr3buchetdprince: are you working on lp81595715:39
dprincemtaylor: Hey man. I is tarmac working again?15:39
mtaylordprince: yes.15:40
dprincetr3buchet: I will if we need me to.15:40
creihtIs nova going to move to using unittest2?15:40
dprincetr3buchet: I was able to resolve the issue by using --flat_injected=false15:40
ttxvishy: I'm working on improving privilege separation in Nova, see https://blueprints.launchpad.net/nova/+spec/improve-privsep15:40
ttxvishy: feel free to target to d4/Medium of something15:40
ttxs/of/or/15:40
dprincetr3buchet: We use the openstack guest agent to inject the network right?15:41
tr3buchetdprince: correct15:42
dprincetr3buchet: In any case it appears that network injection is hosed. I don't use that feature since I use the agent w/ XenServer.15:42
tr3buchetyou are talking about the mounting vhd type of network injection?15:42
dprincetr3buchet: Yes.15:43
tr3buchetyikes, what's broken about it?15:43
westmaasyou guys were talking about different bugs :)15:43
westmaasbug 81595715:43
uvirtbotLaunchpad bug 815957 in nova "lazy load operation of attribute 'network' cannot proceed" [Medium,Confirmed] https://launchpad.net/bugs/81595715:43
westmaasbug 81786615:44
uvirtbotLaunchpad bug 817866 in nova "xenserver instance build timeout with xvdd" [Undecided,Invalid] https://launchpad.net/bugs/81786615:44
tr3buchetha, well i guess that settles the issue15:44
dprincetr3buchet: Yeah. Sorry man. I was talking about the same bug in multiple windows and got confused.15:44
tr3buchetno problems15:44
tr3bucheteasier this way since we aren't both working on it15:44
tr3bucheti can take a look at that one after i get this settled if you like15:45
*** alfred_mancx has quit IRC15:45
dolphmkbringard: just got back to my desk after looking everywhere for eggs... i could only find deviled eggs15:46
kbringardhmmmm, deviled eggs are good15:46
openstackgerritMonty Taylor proposed a change to openstack/openstack-ci: Add script to fix the email problem on gerrit.  https://review.openstack.org/13615:46
tr3buchetthey are delicious15:46
tr3bucheti could eat a dozen deviled eggs15:46
tr3buchetright now15:46
dolphmkbringard: yeah but i didn't know how long they had been sitting out lol15:46
tr3buchetactually15:46
kbringardhaha15:46
tr3buchetdamn these blueberries15:47
kbringardlol at tr3buchet15:47
openstackgerritA change was merged to openstack/openstack-ci: Add script to fix the email problem on gerrit.  https://review.openstack.org/13615:47
kbringarddolphm: ah, the old deviled egg gamble15:47
dprincetr3buchet: I'd like to look at it ... but probably not today.15:48
*** heckj has joined #openstack-dev15:49
dprincemtaylor: Is this hung: https://jenkins.openstack.org/job/nova-tarmac/109707/console15:50
mtaylordprince: oh for crying out loud15:50
*** nati has joined #openstack-dev15:51
tr3buchetdprince: good i'd like to play with gerrit today anyhow15:51
mtaylordprince: that seems like the same problem. I'm going to cry15:51
dprincemtaylor: enighten me. Can I help fix this?15:52
mtaylordprince: no. so - I'm verifying with the lp admins - but a few days ago, launchpad installed an haproxy in front of the bzr servers and set a connection timeout on it15:52
mtaylordprince: tarmac is holding open an idle bzr connection while running the test, and bzrlib is not handling the disconnect properly ... so yesterday they increased the timeout until the real bugfix could be done15:53
mtaylordprince: this is either that resurfacing, or it's something else - but I'm poking the lp admins about it already15:54
dprincemtaylor: Cool. Thanks man. So it really is just hung then. Good to know.15:54
mtaylordprince: totally. gotta say - running gerrit on a machine we control certainly makes it nice from a "I can fix it when it breaks" perspective :)15:54
creihtany keystone devs around?15:55
mtaylorcreiht: no, they're all off looking for eggs to eat after Daviey mentioned eggs earlier this morning :)15:56
kbringardlol15:56
creihthah15:56
kbringardI made some scrambled eggs… cook it up with some cottage cheese…. mmmm15:56
* mtaylor bangs head against desk15:56
kbringardhaha, sorry15:56
kbringardI'd offer you some, but I'm guessing you're nowhere near Colorado Springs15:57
dolphmcreiht: <--15:57
dolphmi'm back, i couldn't find any eggs15:57
creihtdolphm: howdy15:57
dolphmwell, trustworthy eggs15:58
dolphmwhat's up?15:58
creihtthere were bagles in the break room this morning :)15:58
dolphmwhich one?15:58
creihtcloud break room15:58
creihtI think they are gone now15:58
dolphmsouth station?15:58
creihtmain street?15:58
creihtI think15:58
dolphmcloud is all spread out lol15:58
creihthah15:59
creihttrue15:59
creihtdolphm: so back to keystone :)15:59
creihtthe unit testing seems a bit akward to me16:00
creihtawkward16:00
dolphmcreiht: you speak truth16:01
creihthehe16:01
dolphmmany are not actually unit tests16:01
dolphmmost of them depend on the server to be running16:01
* ttx goes to check the neighbour hens to see if any eggs are left16:01
creihtwell and you run all the tests, but then have to scroll back to look if everything succeeded16:01
dolphmsome unit tests aren't even being used16:01
* creiht loves it when his neighbor brings over fresh eggs16:02
creihtdolphm: oh so yeah, that is really bad :)16:02
dolphmtest_keystone.py needs to be deleted, and replaced with a test suite16:02
pvodolphm: qq, not sure if you know the answer thought… with nova integration with keystone, what client is being used to test?16:02
pvothought/though16:02
dolphmclient of what? keystone?16:03
pvoclient of nova16:03
creihtand for example, test_tenants.py fails16:03
pvokeystone doesn't have a specific client, I assume. It integrates with the service apis.16:03
creihtbut doesn't seem to get run in the overall test run16:03
creihtgotta run to lunch16:03
dolphmpvo: right16:03
*** yogirackspace has joined #openstack-dev16:04
dolphmcreiht: these are problems i would love to understand and then make go away!16:04
pvoso, to test with nova, swift, etc… are the clients being modified to use keystone? if so, which clients?16:04
dolphmpvo: that's not something i'm directly aware of, but i believe nova is being updated to use keystone as we speak (?)16:05
pvowell, there are 2 pieces of that puzzle. nova will have to verify the token but the client will have to know how to talk to keystone to to the token exchange initally as well.16:06
dolphmpvo: that's a fair statement16:08
Vekmy brainstorm on how to address this: http://wiki.openstack.org/ClientAuthenticationPlugin16:10
sandywalshI have the nova middleware integration working with keystone now, but I'd like to have a suitable client to use and do something meaningful16:10
sandywalsh(based on the keystone integration docs)16:10
sandywalshI can hack on novaclient  ... but only if no one else is already gone down that path16:11
*** TimR has joined #openstack-dev16:11
sandywalshdolphm ^^16:12
dolphmso, what would help you?16:12
openstackgerritYogeshwar Srikrishnan proposed a change to openstack/keystone: Changes to support services.  https://review.openstack.org/13716:13
sandywalshhmm, perhaps not a lot, the examples are pretty good ... just need to make sure that I'm not treading on any toes16:13
sandywalshthat said, I don't know a lot on the problem yet :)16:14
sandywalshs/on/about/16:14
*** tudamp has left #openstack-dev16:15
*** tudamp has joined #openstack-dev16:15
dolphmi feel like a nova dev could probably point you in the right direction better than i16:16
sandywalshdolphm, k, I was really just wondering if someone on the keystone team had already earmarked that story (novaclient/keystone integration) ... and if I should hold off or not16:17
VekI actually posted an email about this subject to the list, but only got one (not actually very helpful) response...16:17
*** AhmedSoliman has quit IRC16:19
openstackgerritMonty Taylor proposed a change to openstack/openstack-ci: Changed the default gerrit username to match reality.  https://review.openstack.org/13816:22
dolphmsandywalsh: from my perspective, i'd say go for it... but that's just my perspective16:25
sandywalshdolphm, :) works for me16:25
tudampVek: I think what is missing only someone who says, "I begin to do" :)16:33
openstackgerritMonty Taylor proposed a change to openstack/openstack-ci: Update the update script to set email correctly.  https://review.openstack.org/13916:33
*** mwhooker has quit IRC16:33
tr3buchetanyone else seeing this in trunk:16:34
tr3buchetRunning pep8 ...16:34
tr3buchetnova/api/openstack/create_instance_helper.py:95:1: W293 blank line contains whitespace16:34
dolphmOpen question: On nova/swift/etc, are tests analyzed by pylint?16:35
*** adambergstein has joined #openstack-dev16:35
Vekdolphm, question: isn't 2 core approves sufficient to approve a keystone patch?  Or am I mistaken about which of my reviewers is core?  :)16:37
mtaylordolphm: pylint --rcfile=pylintrc -f parseable bin/* nova16:38
openstackgerritA change to openstack/openstack-ci has been rejected: Update the update script to set email correctly.  https://review.openstack.org/13916:38
mtaylorVek: the only people in the keystone core team are jesse and ziad16:39
Vekso I *am* mistaken about which of my reviewers is core :)  Thanks :)16:40
mtaylorVek: If additional people should be added to that group, you guys just let me know :)16:40
VekI'm sure they will; I'm not really deep enough into any of the openstack projects yet for me to call myself anything approaching "core"16:41
mtaylor:)16:42
openstackjenkinsProject keystone build #63: SUCCESS in 49 sec: http://jenkins.openstack.org/job/keystone/63/16:42
openstackjenkinskevin.mitchell: Determine is_admin based on 'Admin' role; remove dead project_ref code;16:42
*** jdurgin has joined #openstack-dev16:48
*** tudamp_ has joined #openstack-dev16:51
*** tudamp has left #openstack-dev16:51
openstackgerritMonty Taylor proposed a change to openstack/openstack-ci: Update the update script to set email correctly.  https://review.openstack.org/13916:52
*** mnour has joined #openstack-dev16:52
dolphmmtaylor: yogi wants pylint to ignore everything in the keystone.test module ... not sure how i feel about that16:53
mtaylordolphm: I'm also not sure how I feel about that16:54
mtaylordolphm: actually, I am - I don't like it - but I'm not sure how _strongly_ I feel about that16:54
dolphmmtaylor: same16:54
dolphmmtaylor: https://review.openstack.org/#patch,sidebyside,137,1,.pylintrc16:54
*** BK_man has quit IRC16:54
zykes-what's pylint vs pep8 ?16:55
mtaylordolphm: I think I'm fine with that for now perhaps? I'd like to see the test code be clean as well in the future16:55
mtaylorzykes-: two different linting tools - pep8 checks for compliance with the python coding style guidelines (PEP8) ... pylint checks the code for things that are common errors or things that could be confusing and cause errors16:56
zykes-mtaylor: like ?16:56
zykes-for pylint16:56
dolphmunused variables, referencing a class variable that hasn't been initialized properly16:57
zykes-ah ok16:57
jeblairmtaylor, dolphm, yogirackspace: what could be a problem is getting pylint to 0 with the test module commented out.  and then bumping up the limit again to work on that.  just somethig to keep in mind.17:02
jk0anyone else noticing LP taking forever to update diffs on MPs?17:04
dolphmjeblair: i agree... we're going to fix any issues in there eventually anyway, why not do it along the way, and track it?17:05
dolphmpersonally, if `ignore=test` is added to our pylint rc, i'm just going to remove it locally17:06
*** Tushar has joined #openstack-dev17:06
*** mattray has joined #openstack-dev17:06
Tusharsleepsonthefloor: Are you there?17:08
sleepsonthefloorHey Tushar17:08
Tusharsleepsonthefloor:I want to change the format for security group rules, every rule will always have a single group or cidr. so there is no need to use plurals and shouldn't be a list.what do you think?17:09
sleepsonthefloorTushar - that makes sense17:10
*** jakedahn has quit IRC17:11
Tusharsleepsonthefloor: Ok, thanks.17:11
jk0mtaylor: LP still pretty backed up?17:15
jk0or jenkins rather17:15
*** mgius has joined #openstack-dev17:16
mtaylorjk0: there is some weirdness with timeouts that I'm looking in to17:16
jk0I'm noticing merge diffs aren't updating either17:17
*** darraghb has quit IRC17:20
mtaylorGREAT17:21
openstackgerritA change was merged to openstack/openstack-ci: Update the update script to set email correctly.  https://review.openstack.org/13917:22
openstackgerritA change was merged to openstack/openstack-ci: Changed the default gerrit username to match reality.  https://review.openstack.org/13817:22
*** dprince has quit IRC17:22
* Vek slowly breaks Gerrit17:25
*** heckj has quit IRC17:25
Vekactually, more accurately, I'm slowly breaking jenkins, or so it would seem.17:26
Vekmtaylor: see https://review.openstack.org/#change,131 , particularly the pylint build failure and my last comment on the patch.17:26
* Vek makes the assumption that mtaylor is a person to point this out to...17:27
mtaylorVek: ah yes! we should install depends on your build host17:28
mtaylorVek: can you tell me which things need installed?17:28
Vekdefinitely nova and glance and their respective dependencies.17:35
VekI'm not familiar with swift, but swift_auth presumably imports something.17:35
openstackgerritMonty Taylor proposed a change to openstack/openstack-ci-puppet: Silence unneeded output.  https://review.openstack.org/14017:35
Vekit does.  We should also make sure to install webob17:35
Vekthat's what I know of off the top of my head...17:36
*** alfred_mancx has joined #openstack-dev17:37
mtaylorhrm. ok. this may take a few minutes to sort17:38
Vekfigured as much :)17:38
mtaylor:)17:38
mtaylorjeblair: ^^^17:38
mtaylorjeblair: apparently keystone needs a bunch of modules installed on their slave :)17:39
jeblairmtaylor: okay, looking into it17:39
*** mnour has quit IRC17:43
dolphmmtaylor: jeblair: what else?17:44
dolphm(other modules)17:44
jeblairdolphm, mtaylor: "unable to import" pylint errors: http://paste.openstack.org/show/2032/17:48
dolphmjeblair: none of those are installed?17:49
mtaylorwhat's dtest?17:49
dolphmmtaylor: a test framework that we have a sample test for, but which we're not using17:49
mtaylordolphm: no. we don't have packages yet, so we didn't have a build-dep list for you17:49
Vekthat's the test framework I wrote for integrated testing...17:49
Veksomeone migrated the tests away, then, because I contributed several tests using dtest17:50
jeblairi'll update our puppet config for that host and see if i can get these installed17:51
*** jakedahn has joined #openstack-dev17:51
mtaylorso, the overall policy is that we require any deps to be installable via apt17:51
mtaylorin the case of dtest - I think we should decide: if we're keeping it, we need to package it, if we're not, then we should make sure it doesn't wind up being a dep17:52
zykes-why is "Tokens" stored in a alternate db then the rest of the stuff in KeyStone ?17:52
Vekdtest is on pypi, but I'm not aware of anyone having packaged it.17:52
kbringardzykes-: that is a good question17:52
kbringardthat I was wondering myself17:52
Vekzykes: keystone may not be able to modify the user store.17:52
dolphmzykes-: great question... i can sort of answer17:52
Vek(that's my guess)17:53
zykes-why shouldn't it be able to modify it ?17:53
mtaylorVek: well, packaging isn't a problem - I've actually got to package another thing for glance today... it's just a matter of deciding if that's what needs to be done (I'm just saying that because there seems to be differing opinions about whether or not it's being used)17:53
zykes-like in what cases is that ?17:53
dolphmzykes-: kbringard: yogi wanted to "experiment" with storing a single model in a different database, and ended up committing his experiment17:53
kbringardlol17:53
zykes-dolphm: not cleaned up afterwards ?17:53
kbringardso it'll eventually go to a single DB model?17:54
*** cp16net_ has joined #openstack-dev17:54
dolphmzykes-: kbringard: i have an open review which removes the "alterdb" stuff from keystone.conf, and all introduces three alternative backend configurations, which are cycled through during testing17:54
kbringardI was thinking it maybe had something to do with keeping the "static" admin tokens logically separate from everything else17:54
Vekwell, what I'm thinking is, what if you get your authentication information out of, say, an LDAP store, but don't want the keystone server to be able to modify it17:54
*** alfred_mancx has quit IRC17:55
Vekin that case, it might be easier to keep the tokens in a different store.17:55
dolphmkbringard: nothing like that17:55
kbringardyea17:55
dolphmkbringard: or rather, nothing that ambitious :)17:55
kbringardthat was purely a guess17:55
kbringardhehe17:55
zykes-cycles how dolphm ?17:55
dolphmzykes-: https://review.openstack.org/#change,13217:56
*** cp16net has quit IRC17:56
dolphmzykes-: my next goal is to apply automatic test discovery to all of keystone.test, which means all tests will execute in a single "row" like a test suite, which means we can delete "keystone/test/unit/test_keystone.py"... the catch is that we have a lot of unreferenced failing tests17:57
*** alfred_mancx has joined #openstack-dev17:58
*** rnirmal has quit IRC18:00
*** tudamp has joined #openstack-dev18:01
*** rnirmal_ has joined #openstack-dev18:01
*** mwhooker has joined #openstack-dev18:02
jeblairVek, mtaylor, dolphm: everything but dtest is installed on the keystone build slave now18:03
openstackgerritJames E. Blair proposed a change to openstack/openstack-ci-puppet: Add keystone dependencies to keystone jenkins slave.  https://review.openstack.org/14118:05
openstackgerritA change was merged to openstack/keystone: Determine is_admin based on 'Admin' role; remove dead project_ref code; pass auth_token into request context; pass user_id/project_id into request context instead of their refs  https://review.openstack.org/13118:06
Vekthat did it for me, thanks :)18:07
jeblairyou're welcome!18:07
dolphmVek: why doesn't DTestCase extend unittest.TestCase?18:08
Vekdolphm: because unittest and dtest are incompatible, largely.18:10
dolphmhow so?18:11
Vekdtest approaches its basic testing and test running in a completely different manner from unittest, because it has the constraint of doing dependencies and auto-threading of tests.18:12
dolphmcan you not accomplish the same constraint by starting from unittest?18:12
VekI looked at extending unittest and/or nose, and decided it would be easiest to start from scratch18:13
Veklargely because of the need for thread safety.18:13
zykes-dolphm: difference on the admin api and the legacy one ?18:14
dolphmby legacy do you mean 'service api'?18:15
zykes-yes18:15
zykes-something rackspace stuff?18:15
dolphmadmin is currently a superset of the service api, but is not defined as such18:15
dolphmservice api is sort of the public api for clients to authenticate with18:15
zykes-but does it need the legacy auth stuff ?18:16
dolphmwhile the admin api is for, say, nova itself to manage keystone through, and validate client tokens, etc18:16
dolphmlegacy auth is a reimplementation of "auth 1.0 / 1.1" ... rackspace-specific stuff18:16
dolphm1.0 and 1.1 really don't have anything to do with 'keystone' ... 'keystone' starts at 2.018:16
zykes-remove code ? M)18:17
openstackjenkinsProject swift build #301: SUCCESS in 30 sec: http://jenkins.openstack.org/job/swift/301/18:17
*** jakedahn_ has joined #openstack-dev18:17
openstackjenkinsTarmac: Bug #820185: Intermittent TypeError NoneType in atexit handler of unit tests18:17
dolphmwhich code?18:17
openstackjenkinsWork around what appears to be a Python standard library bug by silencing18:17
uvirtbotLaunchpad bug 820185 in swift "Intermittent TypeError NoneType in atexit handler of unit tests" [Undecided,Fix committed] https://launchpad.net/bugs/82018518:17
openstackjenkinsexceptions in the logging library.18:17
zykes-"'keystone-legacy-auth', options, args)18:18
zykes-from bin/keystone18:18
*** jakedahn has quit IRC18:19
*** jakedahn_ is now known as jakedahn18:19
*** mszilagyi has joined #openstack-dev18:19
zykes-do you use vi dolphm ?18:23
dolphmzykes-: nope18:26
zykes-there's alot of spaces that aren't used on empty lines..18:27
dolphmzykes-: just random trailing whitespace?18:27
zykes-no, in general, you see alot of "^........." spaces18:28
zykes-in NormalizingFilter under "self.conf = conf"18:29
zykes-there's some18:29
dolphmzykes-: just tested it.. my ide (pydev) is set to auto-remove that18:30
zykes-wonder who's doing that then ;p18:30
dolphmzykes-: i'm not saying it not me... i have too many dev environments18:32
zykes-other public projects ?18:32
*** jakedahn has quit IRC18:33
dolphmi mean, i run pydev on os x and ubuntu on this laptop, i run pydev on os x and ubuntu on another laptop, and on debian at home18:33
zykes-ah18:34
dolphmi also fall back on nano/gedit/whatever sometimes, i used komodo about a month ago18:34
dolphmi'm sure they're not all exactly the same18:34
dolphmmore importantly, i don't view whitespace on any of them :) but i do find useless whitespace annoying when i stumble on it18:35
*** KnuckleSangwich has joined #openstack-dev18:36
creihtdolphm: so I'm supposed to evaluate the whole git/gerrit workflow18:37
creihtThe first thing that stood out to me that could use some help for keystone were the unit tests18:38
creihtbut that seems like it needs more than just a couple of quick fixes18:38
*** jakedahn has joined #openstack-dev18:39
creihtthough I may still be able to find some small things that can help18:40
*** tudamp has quit IRC18:40
creihtI need to dig further, but alas I have meetings most of the rest of the day :/18:40
*** tudamp has joined #openstack-dev18:44
annegentlemtaylor: around?18:45
dolphmcreiht: i totally agree18:46
dolphmcreiht: working on tests as we speak!18:46
creihthehe18:46
*** jakedahn_ has joined #openstack-dev18:47
*** jakedahn has quit IRC18:48
*** jakedahn_ is now known as jakedahn18:48
openstackgerritJohn Dickinson proposed a change to openstack/keystone: updated README with more accurate swift info  https://review.openstack.org/14218:49
*** cp16net has joined #openstack-dev18:49
*** alfred_mancx has quit IRC18:50
notmynamedolphm: (or other keystone devs): so now what? I've proposed a merge to keystone, pushed it to gerrit, ....?18:51
creihtlol18:53
notmynamejust want to understand the tools if I'm going to be expected to use them18:54
dolphmnotmyname: two or more people have to review it, and if all is good, jenkins will run tests on it, check it for pylint issues, and then merge it into openstack/keystone18:54
notmynamedolphm: who do I talk to about configuring those things (2 reviews, pylint, etc)?18:55
*** nati has quit IRC18:55
dolphmnotmyname: i can either help or point you in the right direction18:55
notmynamejeblair: ^?18:55
dolphmnotmyname: the right direction usually being jeblair, mtaylor, or soren18:56
notmynameok18:56
*** nati has joined #openstack-dev18:56
dolphmnotmyname: for pylint, we have a '.pylintrc' in the root of the project18:56
notmynamejeblair: mtaylor: soren: is the idea that all projects using git+gerrit will use the same rules? is there any way to override those rules? (eg can a core dev merge in a "small" change without 2 reviews?)18:57
jaypipesnotmyname: no.19:00
notmynameto which? ;-)19:00
*** alfred_mancx has joined #openstack-dev19:00
jaypipesnotmyname: projects can decide what policies they wish to enforce. the only policy we have is that there is no human-gatekeeper.19:00
notmynameok19:00
jaypipesnotmyname: just email jeblair after talking with the swift contribs what your preference is.19:01
jaypipesnotmyname: you can have mtaylor and jeblair put as few or as many barriers as you want (pep8, pylint, whatever you want).19:01
*** rnirmal_ has quit IRC19:02
*** rnirmal has joined #openstack-dev19:02
*** bsza has quit IRC19:03
*** bsza has joined #openstack-dev19:03
jaypipesnotmyname: also, to be clear, the keystone code review process has some automated barriers (currently pylint checks), but for small, non-contentious pull requests, any keystone-core dev can set the review to +2 to "send it on" to Jenkins and the automated builders. As long as nobody has done a -1 review on the patch, that's enough to send it on.19:05
jaypipesnotmyname: but, as mentioned, you can set up whatever policies fit the swift team best.19:05
jaypipesnotmyname: and thx for trying it out. appreciate the feedback and questions.19:05
*** cp16net has quit IRC19:07
*** mdomsch has joined #openstack-dev19:11
*** TimR has quit IRC19:13
*** TimR has joined #openstack-dev19:14
openstackgerritYogeshwar Srikrishnan proposed a change to openstack/keystone: Changes to support services.  https://review.openstack.org/13719:20
*** mnour has joined #openstack-dev19:21
*** deshantm_laptop has joined #openstack-dev19:21
*** adambergstein has quit IRC19:22
notmynamejaypipes: jeblair: will all reviews for all projects be listed for everyone? (eg https://review.openstack.org/#q,status:open,n,z)19:23
jaypipesnotmyname: good question. I'm not sure. jeblair or mtaylor?19:23
*** nati has quit IRC19:23
*** TimR has quit IRC19:32
*** TimR has joined #openstack-dev19:33
*** adambergstein has joined #openstack-dev19:36
openstackgerritYogeshwar Srikrishnan proposed a change to openstack/keystone: Changes to support services.  https://review.openstack.org/13719:37
*** tudamp has quit IRC19:45
*** cp16net has joined #openstack-dev19:46
openstackjenkinsProject swift build #302: SUCCESS in 29 sec: http://jenkins.openstack.org/job/swift/302/19:47
openstackjenkinsTarmac: added Ewan to authors file19:47
notmynamejaypipes: jeblair: mtaylor: also, with gerrit forces updates to reviewed code be submitted essentially a new review submission (although it has the same gerrit id). since each review is one commit (squashed before review) it becomes difficult for the reviewer to see what's changed between the two submissions19:49
jaypipescomstud, s1rp: https://blueprints.launchpad.net/glance/+spec/split-unified-api. Targeted to Essex.19:49
comstudcools19:49
*** nati_ has joined #openstack-dev19:50
jaypipesnotmyname: Diff from Previous Set button should show what you want...19:51
notmynameok19:51
notmynamejaypipes: got any examples of this?19:57
jaypipesnotmyname: *blush* I confused what ttx had said earlier about this feature as already being in Gerrit.. apparently, it's not done yet: http://code.google.com/p/gerrit/issues/detail?id=37919:58
jaypipesnotmyname: sorry man :(19:58
jaypipesnotmyname: I'm hoping mtaylor or jeblair have a solution or a suggestion on this. I think they're both afk right now.19:59
*** bcwaldon has quit IRC20:04
*** bcwaldon has joined #openstack-dev20:06
notmynamejaypipes: jeblair: mtaylor: seems to me that using gerrit removes almost all of the reasons for using github (github's pull request/issue management being one of them). so why use github at all and not something simple like gitweb or gitorious or something at git.openstack.org?20:13
notmynameie the gerrit workflow replaces github20:14
jaypipesnotmyname: do you really want to get into this conversation again?20:15
notmynamejaypipes: I'm offering my thoughts as requested. also, I don't think there was ever a conversation on gerrit20:15
notmynameI'm not arguing git vs bzr20:15
termie(git)20:16
zykes-dolphm: what's the difference of the stuff under controllers and IdentityService class ?20:16
jaypipesugh.20:16
dolphmzykes-: looking..20:16
jaypipesnotmyname: we've had the "why can't we just use GitHub as is" conversation already a hundred times.20:17
termiefunny that people would keep asking for that20:17
jaypipestermie: seriously, dude, not today.20:17
dolphmzykes-: don't know!20:18
zykes-:|20:19
zykes-is there any plans to "commonize" stuff ? like wsgi.py under projects...20:19
zykes-config.py20:19
yogirackspacecontrollers deal with contents coneversion and if any needed any endpoint related stuff20:19
dolphmzykes-: it looks like hte controllers all use config.SERVICE which *is* IdentityService20:19
zykes-what's the "class IdentityService" then under service.py dolphm ?20:20
yogirackspacewhere else services are designed not to deal with domain models20:20
dolphmzykes-: ask yogi ^20:20
yogirackspacethat was the reason for seperation20:20
kbringardoh, hey Yogi20:21
zykes-yogirackspace: ?20:21
yogirackspacesorry services are designed  to deal with domain models20:21
kbringardI may need to read back if you answered this already, but I was wondering if you could explain what the public_url is for in keystone20:21
dolphmyogirackspace: these things should be documented at the module level, because it's definitely not clear20:21
*** cp16net has quit IRC20:22
zykes-domain models is what yogirackspace ?20:22
yogirackspacepublic_url  are urls that the end users of a service could actualluy use to consume the service20:22
kbringardso it's similar to a vhost of sorts?20:23
*** cp16net has joined #openstack-dev20:23
kbringardbecause, in theory I  could put some external IP as the internal_url and have that be the public_url too, right?20:23
yogirackspaceyou could20:24
yogirackspaceinternal ip is for services to use among themselfes20:24
yogirackspacethey all might be under same network20:24
zykes-yogirackspace: what is the diff on controllers stuff and the identityservice stuff ?20:24
yogirackspacecontrollers were to do deal with endpoint conversions and stuff like that20:26
zykes-and the identity service ?20:26
yogirackspacesxample a req object might not be there for services at all20:26
kbringardso the public_url is more for the software to know what people will be coming in from, and not necessarily something for keystone to use to talk on, since it's going to use the admin_url and the internal_url20:27
yogirackspaceit was supposed to deal with domain level operations without worrying about the data conversions20:27
kbringardah, OK20:27
yogirackspaceits more for actual users to consume respective services20:28
yogirackspacethey wud use the public url along with the tokens to perform operations on individual service20:29
kbringardah, OK20:30
kbringardgot it20:30
kbringardthanks :-)20:30
yogirackspacecool20:30
kbringardif you have a moment, I have a couple other questions too :-D20:30
yogirackspacesure20:30
kbringardbut I don't want to derail you from real work20:30
yogirackspaceu cud email me or any one from the team20:30
yogirackspaceu cud email openstack list we ll answer20:31
jaypipesnotmyname: I've noted your feedback on Gerrit (summary: it sucks, we should really just be using GitHub anyway). I'll include it in the email creiht asked me to send out about Gerrit.20:31
kbringardok, dolphm gave me your address so I'll just email you, if you don't mind20:31
yogirackspacesure20:32
yogirackspace:)20:32
dolphmmtaylor: problems! you there?20:34
notmynamejaypipes: is that really what I said? now having actually used gerrit in a limited way (ie one commit), I'm asking questions that I have based on my experience with our workflow20:36
jaypipesnotmyname: it was very clear to me what you were saying.20:37
dolphmjaypipes: the new Change-Id required-for-every-commit is borked20:37
jaypipesdolphm: could you explain, pls?20:37
*** sandywalsh has quit IRC20:38
notmynamejaypipes: I never once offered a value judgement on gerrit20:38
zykes-what's the reason for having "wsgi.py" and those files independant in each project?20:38
dolphmjaypipes: i have the hook installed, i pulled from openstack/keystone which did an auto-merge (and thus a commit with no change-id), i did my own (normal) commit with a change-id, and then tried to git review... the merge is blocking my review20:38
dolphmzykes-: excellent question - i'm sort of hoping they get swallowed by openstack-common20:39
zykes-is there any such project ?20:39
*** bcwaldon has quit IRC20:40
jaypipesnotmyname: I'm not sure anyone would read your comment above and not think that it was value judgment.20:40
dolphmzykes-: i think it was just started20:40
dolphmzykes-: https://github.com/openstack/openstack-skeleton20:41
jaypipesnotmyname: not talking about the questions regarding diff and about listing all projects in the review screen. you know what comment I am referring to.20:41
dolphmzykes-: i guess skeleton != common ... doesn't solve duped code20:42
jaypipesdolphm: skeleton is the baking ground for common, which is why skeleton includes an openstack/ directory (that is openstack-common).20:42
jaypipesdolphm: since nobody can seem to agree on even the simplest of things between the projects, openstack-common is basically dead on arrival until someone says "this is a skeleton project with an openstack lib that works."20:43
dolphmjaypipes: well anyway, i'm looking forward to importing it and dumping all the out-of-scope code in keystone :)20:44
jaypipesdolphm: you and me both.20:45
edayjaypipes: to be fair, I think notmyname was only asking if there was a reason we were still using github for code hosting if we're not using issues or pull requests. I think the answer is so we don't have to host our own code hosting too, and you can still use GH for branch/fork management20:47
jaypipesdolphm: so, re: the changeId hook, gotta link?20:47
notmynameeday: correct. but with gerrit you don't even use the branches in github (since gerrit is the one managing them)20:48
dolphmjaypipes: http://paste.openstack.org/show/2034/20:49
jaypipesnotmyname: what do you mean by "you don't even use the branches in github"?20:49
termiejaypipes, notmyname: i assume meaning that we push to gerrit rather than pushing to github and issuing pull requests20:50
notmynamejaypipes: all my branch management is local with gerrit since gerrit handles all of the merging20:50
dolphmi use my own github fork to sync between my own workstations..20:50
jaypipestermie: right. because  GitHub's pull requests are inadequate and it's not open source, so we can't edit it for our needs.20:51
termiejaypipes: i didn't bring that up20:51
termiejaypipes: :D20:51
jaypipesnotmyname: ok, well, I'll take your word that your question was an honest question and not just yet another jab at not using GitHub for everything. eday answered your question: so we don't have to do code hosting ourselves.20:52
termietangentially, i've written some stuff that allows easy migration of issues, milestones and blueprints from lp to gh, in case anybody else is interested20:54
jaypipesno20:54
jaypipestermie: for bugs/blueprints/milestones, personally for Glance I'm not interested in giving up lots of functionality to get rounded corners in the UI.20:56
jaypipesdolphm: ok, so reading through your link there, it looks like the commit hook should recognize a merge commit and not error on the Change-Id being missing. correct?20:57
*** alfred_mancx has quit IRC20:57
dolphmjaypipes: yessir20:57
jaypipesdolphm: k, lemme grab jim and chat when he gets back. thx for your patience.20:58
termiejaypipes: rounded corners AND gradients20:58
dolphmjaypipes: np20:58
jaypipestermie: ah, sorry, forgot about that.20:58
mtaylordolphm, jaypipes hey, whazzup?20:58
jaypipestermie: and a groovy 404 image that moves with your mouse pointer. glad they spent the time to get that done!20:59
dolphmyo20:59
termiejaypipes: gravatar integration! that stuff is hot20:59
dolphmmtaylor: relevant: http://paste.openstack.org/show/2034/20:59
jaypipestermie: lol20:59
dolphmtermie: but can they do rounded corners on my gravatar?20:59
jaypipesdolphm: I'm sure if you found them and bought enough micro-brews they'd do it.21:00
dolphmjaypipes: i would actually hate that... my gravatar is square and fuck you if you try and make it shiny21:00
termiedolphm: sounds like a chrome extension to me, i have one to remove most of the icons and extra content on the launchpad pages21:00
jaypipesdolphm: might even prioritize it over smaller features like an email interface...21:01
edaywe could just use browser plugins to style LP to look like GH :)21:01
termieeday: i wish it were that easy21:01
jaypipeseday: I would die. that would be awesome. :)21:01
dolphmlol21:01
dolphmmtaylor: so, after this change-id guard-ignoring-merges issue, can you add a zero-tolerance pep8 blocker on keystone?21:02
mtaylornotmyname, jaypipes: hey! I'm only half-reading the scrollback ... we're replicating to github because it's an easier place for people to do the whole "fork/pull" thing than asking them to clone directly from gerrit - and because people seem to like that as an easy to understand place to go to find a copy of the code21:02
creihtjaypipes: I'm not trying to stir the hornet's nest, but I think you were a bit unfair and mis-characterized his question21:03
termiemtaylor: but we're also completely supplanting the usual flows people are used to when using github21:03
mtaylordolphm: I think jeblair is actually the person to look at the Change-ID thing - but I know in the past that if the Change-ID has a space before it or is not on the final line, things get wonky. jim should be done with lunch soon21:03
creihtI still think it is a valid question, if we are only using github for code hosting, and not any other features, why do we not host it ourselves?21:03
creihtwe are already hosting the gerrit stuff21:03
mtaylorsure. well, we _do_ host it ourselves21:03
termiemtaylor: people are used to seeing a project, forking and issuing pull requests, we don't want them to do anything but look at the code?21:04
creihtand there are some decent tools that allow for the git hosting (like gitorious)21:04
mtaylorgithub is a mirror for conveniece for people who would like to fork code there21:04
dolphmmtaylor: the issue is that the Change-Id hook doesn't add ID's on merges, and then gerrit is blocking21:04
mtaylorcreiht: totally - and I have no objections to also running a gitorious mirror or something of that nature21:04
mtaylordolphm: hrm. yes. we need to loop in jeblair21:05
dolphmmtaylor: should i just email him?21:05
mtaylordolphm: he's just at lunch - should be back soon21:06
mtaylordolphm: but yeah, you can also email him21:06
creihtmtaylor: then I vote that the canonical location should be something like git.openstack.org, and we keep the github as a mirror21:06
jeblairhiya21:06
creihtto avoid confusion21:06
jeblairi'm caught up on scrollback. :)21:06
dolphmjeblair: hola21:06
*** jjm has quit IRC21:06
creihtotherwise if github is the cannonical location for the source, you are going to have a lot of people trying to contribute the github way21:07
termiecreiht, mtaylor: and maybe get some bugzilla love in there to remove lp completely21:07
*** _cerberus_ has quit IRC21:07
mtaylortermie: you REALLY hate launchpad don't you21:07
*** mnaser has quit IRC21:08
mtaylorcreiht: I'd be fine with something like that ... shall we look in to what that looks like and make some suggestions on how it could work?21:08
* creiht shrugs21:08
jeblairthis is fun: i'm researching the change-id on merge commit problem, and my own documentation on the openstack wiki just came up as result #3 in google21:08
creihtI'm just making observations21:08
mtaylor:)21:08
dolphmjeblair: win!21:08
*** mdomsch has quit IRC21:09
termiemtaylor: yup, but not in a particularly emotional way, it is more like it is a roadblock between me and a pleasurable working environment21:09
termieour gerrit has a particularly lovely color scheme, btw, which is why i thought of bugzilla21:10
mtaylortermie: fair enough. I mean - I feel that way about bugzilla, so I know what you're talking about at least :)21:10
notmynamemtaylor: I think it could be valuable to see what other git hosting options look like if we aren't using the particular featureset that github offers21:10
*** _cerberus_ has joined #openstack-dev21:10
mtaylornotmyname: there are some examples already of folks doing a git+gerrit+gitorious setup ... jeblair, who was that project we were looking at who did that?21:10
*** jaypipes has quit IRC21:11
jeblairmtaylor: mahara21:11
notmynamemtaylor: I tend to agree with termie that using github but not any of the standard github "ways" will probably cause much confusion21:11
jeblairhttps://wiki.mahara.org/index.php/Developer_Area/Developer_Tools21:11
mtaylornotmyname, creiht: definitely would be happy to look at those21:11
jeblairgitorious does support openid; that could make cross-tool SSO nicer21:12
mtaylor++21:12
mtaylorjeblair: we can run our own gitorious, right? so we could actually manage the SSO stack in a sensible manner? (I'm imagining people would like it if they didn't have to have a lp account to do things)21:13
mtaylor(not saying we need to - just thinking out loud)21:13
jeblairand yes, self-hosting git repos (including turning on gitweb support in gerrit) are other options we can consider.  i have deferred experimenting with gitweb and gerrit since we've been considering github as the public facing code hosting, but i do know that gerrit has goot integration with it21:13
jeblairmtaylor: yes, i'm agnostic about what the sso stack _is_, but do think we should have one.21:14
jk0I might have missed this (and don't want to stir anyting up) but why aren't we just using github for hosting and code reviews?21:14
jk0instead of gerret21:14
mtaylorjk0: the main reason is lack of a workflow state in github pull requests21:14
mtaylorjk0: which then makes jenkins integration pre-merge a bit difficult to model in a consistent manner21:15
jeblairdolphm: regarding merge commits, apparently using "git pull --rebase" can help avoid them21:15
jk0it's probably not ideal but we could just come up with our own way to give thumbs up or down21:15
mtaylorjk0: yeah, we went down that road for a bit21:15
jk0right now on LP you could still approve w/o two +1s, couldn't you?21:15
jeblairdolphm: i'm still leaning toward "merge commits don't fit well in our recommended workflow", so my first idea would be to try to avoid them.21:15
jk0or does jenkins know better21:15
mtaylorjk0: different thing21:16
mtaylorjk0: it's not about enforcing vote vs. approve policy21:16
dolphmjeblair: it's not really a merge.. it was just a pull21:16
*** mnaser has joined #openstack-dev21:16
termiemtaylor, jk0: there is still a person involved clicking 'merge this'...21:16
mtaylorjk0: it's about the difference between tracking votes and holding the state of the request itself21:16
dolphmjeblair: which, yes, has a merge, but it's not like i'm merging in someone else's commits that haven't already been through gerrit/jenkins21:16
jeblairdolphm: pulls can be either ff or merge depending on what has happened to the remote21:16
jeblairdolphm: do you have a github location where you can push your repo?21:17
jk0mtaylor: yeah, it would be a pain, but I think we could get used to it21:17
dolphmjeblair: yep21:17
termiemtaylor, jk0: were i discussing this i would probably claim that much of our process comes from a lp-centric image of the world, while other people have indeed successfully used other processes21:17
jeblairnotmyname: 12:23 <+notmyname> jaypipes: jeblair: will all reviews for all projects be listed for everyone? (eg https://review.openstack.org/#q,status:open,n,z)21:18
jk0termie / mtaylor: that's my point.. why not consider a new process?21:18
mtaylortermie, jk0: people TOTALLY use other processes - the actual driving factor here is the jenkins-runs-pre-merge workflow to produce a gated trunk21:18
jk0or just a workaround (manually doing stuff) until we can find something better21:18
jeblairnotmyname: yes, they'll all be there.  However, this page: https://review.openstack.org/#q,is:watched+status:open,n,z21:18
mtaylorjk0: because there is nothing broken in the process?21:18
*** jjm has joined #openstack-dev21:19
mtaylorjk0: I'm not saying others wouldn't also work21:19
jeblairnotmyname: (My -> watched changes) should show you changes that are interesting to you based on what project groups you are a member of21:19
notmynamejeblair: good21:19
jk0mtaylor: not saying anything's broken, but like termie said we're sticking to the LP style of merges which led to gerret21:19
jeblairnotmyname: 12:49 <+notmyname> jaypipes: jeblair: mtaylor: also, with gerrit forces updates to reviewed code be submitted essentially a new review submission (although it has the same gerrit id). since each review is one  commit (squashed before review) it becomes difficult for the reviewer to see what's changed between the two submissions21:20
creihtjk0:++21:20
*** jaypipes has joined #openstack-dev21:20
mtaylorjk0: not really - it's not really about lp or gh style merges - it's about serving a jenkins shotgun on the trunk21:20
jeblairnotmyname: i _think_ that should be handled by selecting "Patch history" while viewing a diff21:21
mtaylorjk0: gerrit happens to feed the ability to have code reviews trigger testing and then flow in to merging to trunk - and is already tightly integrated with jenkins21:21
termiemtaylor, jk0: my hypothetical statement wasn't referring to merges specifically, but embedded process in general21:21
jeblairnotmyname: where you can thes select whether to diff based on base, or any submitted patchset21:21
notmynamejeblair: do you have any examples? it's something that is fairly common21:21
jeblairnotmyname: here is a simple change that has 2 patchsets: https://review.openstack.org/#change,13921:21
termiemtaylor, jk0: an example of which might be having a bot merge your code for you21:22
jk0termie / mtaylor: sure, that's why I think we should expore a few more options before making gerret official (or is it too late?)21:22
notmynamejeblair: so how do I see the diff between the patchsets?21:22
mtaylorjk0: so - here's the thing ... at the moment, we have the current process, which has a fairly well designed set of requirements21:23
dolphmnotmyname: select a patch set under "Old Version History"21:23
jaypipesnotmyname: https://review.openstack.org/#patch,sidebyside,139,2,update_gerrit_users.py21:23
jaypipesnotmyname: select patch set 1 under Old Version History, then hit side by side on the file...21:23
mtaylorjk0: and we have thoughts that we could do something else, but of those myriad possible something elses (and there are honestly many different ways we could go here) they are all essentially just possibilities that don't have sets of requirements21:24
mtaylorjk0: so without a concrete problem to solve, I'm pretty sure we'd start "exploring" things, but with nothing other than personal preference or things people happen to have done before guiding us21:24
jaypipescreiht: sorry, got disconnected.. reading back in log.21:25
*** dolphm has quit IRC21:25
jeblairnotmyname: yes, using "old version history" will change the file list on the main page for the change.  then when you are doing a side by side diff of a file, "patch history" will let you change what the diff is based on21:25
jk0mtaylor: that's fair enough. at the very least, I'd really like to see a new UI for gerret (hopefully nokia will not let us down)21:26
notmynamejeblair: ya, trying that out now.21:26
mtaylorjk0: I mean, gerrit wasn't my first choice, but as I've worked with it, I've become pretty pleased with its possibilities and extra pleased with how comprehensively it's integreated with jenkins21:26
mtaylorjk0: ++21:26
mtaylorjk0: although the nice thing is that if one of us gets enterprising, we can certainly patch the UI21:26
termielulz21:27
jk0true, and I'm sure that will have to happen eventually21:27
mtayloryes. I agree21:27
jeblairjk0: i don't know if nokia is working on a whole new ui, but they are making some usability changes around patch viewing21:27
jk0because that's one of the worst UIs I've ever seen, no offense to anyone21:27
mtaylornot first on my list of things to do - but it's on there21:27
termiejk0: bugzilla!21:27
mtaylorjk0: what termie said21:27
mtaylor:)21:27
jk0haha21:27
jeblairgerrit is based on google web toolkit.21:27
termiejeblair: aka nobody is ever going to touch that ui21:28
mtaylortermie: I dunno - it might piss of steve jobs one day and he might have some rounded corners and some brushed metal added21:28
termiemtaylor: ?21:29
mtaylorjk0: there's also an ssh/command-line interface if you're in to that sort of thing21:29
termiemtaylor: brushed metal is so 200521:29
mtaylortermie: I can't keep up with apple fashion trends. what are we on now? white? that's passe too, right?21:30
jk0mtaylor: very much so21:30
jeblairi realize this is the opposite of rounded corners, but yeah, there is a command line interface for many actions as mtaylor mentioned, and if you hit '?' in the web ui, you'll get a keyboard shortcut reference21:30
jk0the more things I can do out of my screen shell, the better21:30
mtaylorjk0: I think you can do a LOT of things via command line21:31
mwhookerwhat's the status of doctests within openstack. I see there are none. would people be amenable to adding them, or would they prefer the tests go in separate modules?21:31
jk0I'll have to look more into it when I get time21:31
jeblairjk0: https://review.openstack.org/Documentation/cmd-index.html21:31
jk0nice, thanks jeblair21:31
jeblairnp21:31
termiemtaylor, jk0: btw, i'm fine with gerrit, i just think we will also get pull requests on gh, and i think it is disappointing to also use lp21:32
jk0yeah, I'm not sure we should even have a GH mirror21:32
jk0no point in it if we're hosting our own repo21:32
mtaylortermie: definitely agree on the first, totally understand the second ... let's keep talking about how we can deal with the lp thing in a way that doesn't kill our release management side21:32
*** markvoelker has quit IRC21:33
*** Tushar has quit IRC21:33
termiewhoa dudes, bugzilla has rounded corners now: https://bugzilla.mozilla.org/show_bug.cgi?id=30933021:35
uvirtbotMozilla bug 309330 in Location Bar "unable to force the download of a location bar address" [Enhancement,Unconfirmed: ]21:35
mtaylorjk0, termie: jeblair and I will put together some thoughts on alternatives to the github mirror - I think that's a really good point21:35
mtaylortermie: CRAZY21:36
notmynamemtaylor: thanks21:36
mtaylornotmyname: my pleasure! I really do want our infrastructure to make sense for everyone - and I think at some point we'll get there! :)21:37
notmynameso one more question: I think this is something that is being evaluated as one of a "vetted set" of options, right? the existing bzr/lp process will still be available? or is this designed to be _the_ way openstack dev is done?21:39
*** jkoelker has quit IRC21:41
termiethe latter, as i understand it21:41
edaywell, according to the last PPB vote, it was a tie (options vs one way)21:43
termieexciting21:43
mtaylornotmyname: I have my opinions there- and I sort of want the second21:43
edaynotmyname: so I think we'll need to revisit that once jbryce has the autonomy doc done21:44
mtaylornotmyname: s/sort of/completely/21:44
notmynamegood to know21:45
jeblairmtaylor: i think dolphm is still gone, but i'm leaning toward rebase being the right answer for merge commits21:46
*** bsza has quit IRC21:46
jeblairie, rebase and don't submit merge commits to gerrit21:46
edayjeblair: would the rebase happen pre or post review?21:47
*** sandywalsh has joined #openstack-dev21:47
jeblaireday: pre -- dolphm's problem is that he ended up with a merge commit when updating his working branch21:48
jeblaireday: so i think the suggestion would be "if you update your working branch from upstream, use git pull --rebase"21:48
edayjeblair: I guess I should ask which which use of rebase as well. basically, I'd hate to loose the commit history during review if there was one to do it in chunks21:49
jeblairso with gerrit, each commit becomes a change (which is one reason we don't want merge commits; they generate extra changes)21:51
jeblairso if there is a meaningful commit history where commits should be individually reviewed (or reviewed in sequence), that makes sense to upload several commits21:51
*** deshantm_laptop has quit IRC21:51
jeblairbut we recommend squashing what we're calling "checkpoint commits" before uploading them for review21:52
jeblairie, if you work on a change for a long time and check in your work frequently, but each of those commits shouldn't be reviewed, only the result, then squash them21:52
jeblair(devs can always keep their private history on another branch if they want)21:53
edayOk. I guess I was thinking it would be squashed post-review right before trunk (could do ff-only then for trunk maybe?)21:57
edayBut what you say makes sense, if it's big enough to want to review different commits, should probably be different reviews :)21:57
jeblairright now we have gerrit set to ff or merge when necessary, which gives it a little more flexibility in merging patches21:58
jeblairso gerrit itself can create merge commits to facilitate dev B's change getting merged after dev A's, without dev B having to rebase21:58
jeblairotherwise, devs would likely need to rebase after any change to trunk, which would be...annoying. :)21:59
mwhookerif I wanted to get the discussion about doctests going, where would be the best place to pose it?21:59
termieit has already begun21:59
termie(because you just started it)22:00
mwhookerboom22:00
mwhookerwhat if I were to commit some doctests and modify run_tests to run nose with --with-doctests22:00
mwhookerchecking, of course, that it doesn't slow down the tests too much22:00
*** joar has joined #openstack-dev22:01
joarDoes Swift fully support the python-cloudfiles bindings?22:01
mwhookerI'm yak shaving the nova/api/openstack/common.py file and notice there are essentially doctests describing behavior of, eg, get_id_from_href22:02
mwhookerso it would be nice to formalize those22:02
*** nati_ has quit IRC22:12
*** TimR has quit IRC22:13
*** TimR has joined #openstack-dev22:14
creihtjoar: the python-cloudfiles bindings should work with swift22:16
*** RobertLaptop has quit IRC22:17
*** j05h has joined #openstack-dev22:18
*** j05h has left #openstack-dev22:18
*** RobertLaptop has joined #openstack-dev22:19
joarthanks creiht!22:22
joarIs there any service out there using openstack currently?22:22
creihtjoar: swift is what backs cloud files22:24
creihtat rackspace22:24
joarOk, that's great.22:24
creihtthere are several other deployments of swift22:25
creihtInternap, Nephoscale, Korea Telecom off the top of my head22:25
creihtCan't speak for Nova22:26
creihtWikimedia was experimenting with it to store images for wikipedia, but I never heard if they turned it all the way on22:27
joarcreiht: I was actually wondering because I needed to confirm that my development will also work with Swift setups.22:27
creihtahh cool22:28
creihtit should then22:28
joarBut if Cloud Files  are powered by Swift, I've already done so.22:28
joar:)22:28
creihtcool, may I ask which tool?22:28
joarMediaGoblin22:28
joaror GNU MediaGoblin22:29
creihtThe only main difference between the two, is to make the auth endpoint url configurable22:29
joarYes, that's implemented :)22:29
joaralso servicenet.22:29
creihtcool22:29
joarWorks perfect, the images load 4.5 times as fast as the CSS ;)22:29
creihthaha22:29
joarTo the defense of the CSS it's hosted via pagekite.22:30
joarhttp://mg.jwandborg.pagekite.me/u/joar/m/4e39b15fd9d7834655000000-balloons-3/22:30
creihtthat's pretty cool22:30
openstackgerritMonty Taylor proposed a change to openstack/openstack-ci-puppet: Silence unneeded output.  https://review.openstack.org/14022:32
joarcreiht: Yeah, it is :)22:34
Daviey23:36 < pakaran> 5*50/30k you mean22:37
Davieyhmm, not sure what happend there22:38
*** kbringard has quit IRC22:40
*** mattray has quit IRC22:43
openstackgerritMonty Taylor proposed a change to openstack/openstack-ci-puppet: Silence unneeded output.  https://review.openstack.org/14022:45
openstackgerritA change was merged to openstack/openstack-ci-puppet: Silence unneeded output.  https://review.openstack.org/14022:46
*** amccabe has quit IRC22:51
openstackgerritVish Ishaya proposed a change to openstack/keystone: Adds support for authenticating via ec2 signatures  https://review.openstack.org/12723:03
*** yogirackspace has left #openstack-dev23:05
*** jakedahn has quit IRC23:19
*** rnirmal has quit IRC23:42
*** jc_smith has joined #openstack-dev23:56

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