Monday, 2013-09-23

*** ianw has joined #openstack-infra00:09
*** ericw has joined #openstack-infra00:10
*** annegentle has quit IRC00:10
*** annegentle has joined #openstack-infra00:12
*** ericw has quit IRC00:13
Alex_Gaynorjeblair: do you ahve a screen shot of what the NNFI visualizer looks like?00:15
*** dkehn has quit IRC00:16
*** ericw has joined #openstack-infra00:19
*** notmyname_ has joined #openstack-infra00:19
*** jhesketh has quit IRC00:23
*** kpepple has quit IRC00:23
*** fbo_away has quit IRC00:23
*** enikanorov-w has quit IRC00:23
*** ekarlso has quit IRC00:23
*** bearhands has quit IRC00:23
*** NobodyCam has quit IRC00:23
*** lyz has quit IRC00:23
*** vishy has quit IRC00:23
*** notmyname has quit IRC00:23
*** jmeridth has quit IRC00:23
*** jhesketh has joined #openstack-infra00:24
*** notmyname_ is now known as notmyname00:24
*** kpepple has joined #openstack-infra00:27
*** lyz has joined #openstack-infra00:27
*** bearhands has joined #openstack-infra00:27
*** NobodyCam has joined #openstack-infra00:28
*** ekarlso has joined #openstack-infra00:29
*** dkliban has joined #openstack-infra00:34
*** thomasm has joined #openstack-infra00:40
*** SlickNik_ has joined #openstack-infra00:40
*** dcramer_ has joined #openstack-infra00:40
*** annegentle has quit IRC00:43
*** ericw has quit IRC00:43
*** dprince has joined #openstack-infra00:43
*** thomasm has quit IRC00:43
*** annegentle has joined #openstack-infra00:44
*** SlickNik_ has quit IRC00:46
*** sarob has joined #openstack-infra00:49
*** mrda has joined #openstack-infra00:50
*** sarob has quit IRC00:53
*** yaguang has joined #openstack-infra00:56
*** blamar has joined #openstack-infra00:59
*** jhesketh__ has quit IRC01:02
*** michchap_ has quit IRC01:05
*** michchap has joined #openstack-infra01:07
*** dkehn has joined #openstack-infra01:09
*** ryanpetrello has joined #openstack-infra01:10
mrdahey everyone, I'm having a little trouble signing the Individual Contributor Licence Agreement in gerrit.  Anyone able to help me?01:18
clarkbmrda: sure01:21
clarkbmrda: can you be more specific about the issue(s)?01:21
mrdaclarkb:  So I'm on https://review.openstack.org/#/settings/new-agreement , have clicked the ICLA.01:22
mrdaIt's prefilled my name and email address from launchpad01:22
lifelessmrda: velkommen01:22
lifelessmrda: but so far you haven't described an issue :)01:22
mrdaI've entered my address, country and phone number (not incl fax), entered "AGREE" in the "Compete the agreement" box01:22
mrda...which allows me to click the "Submit Agreement" button.  But all that does is to remove the AGREE text, and grey out the button.01:23
mrdaRevisiting my profile shows me that it hasn't registered my agreement.  It just like there's an error on form submission (without error text).01:23
mrdalifeless:  hey, glad to be here ;)01:24
*** dprince has quit IRC01:24
clarkbmrda: weird, if there is an error it should feed that back to you. Have you signed up with the OpenStack foundation? and if so is the email you are using when signing the ICLA the same one you have provided the foundation?01:25
mrdayes, same email address01:25
clarkbmrda: also what is your Account ID according to https://review.openstack.org/#/settings/01:25
mrda812501:25
*** Ryan_Lane has joined #openstack-infra01:26
clarkbthere are no preexisting CLA agreements according to the DB for that account01:27
mrdaclarkb:  Chrome 29 on Ubuntu 13.04, FWIW01:29
clarkbI wonder if the foundation side isn't accepting connections from gerrit or responding to gerrit /me pulls out laptop to check logs01:29
mrdaclarkb:  foundation profile: http://www.openstack.org/community/members/profile/1296501:30
*** lcestari has quit IRC01:31
*** Ryan_Lane has quit IRC01:32
clarkbI don't see anything in the logs that scream at me as being related to the foundation side doing something funny but my browser can't get www.openstack.org01:35
clarkbso I think that theory is still a possibility01:36
clarkband unfortunately I don't have access to things on that end.01:36
clarkbjeblair: fungi ^01:36
*** CaptTofu has joined #openstack-infra01:37
mrdaclarkb:  just tried Firefox, doesn't work there either :-/01:39
clarkbmrda: ya, I think this is an issue on the foundation side. http://www.openstack.org is dead01:39
*** lcestari has joined #openstack-infra01:39
mrdamrda:  oh well, glad it's not me :)  Thanks for your help.01:40
clarkbmrda: if jeblair and/or fungi show up I believe they may be able to look into the foundation stuff01:40
mrdaclarkb:  thanks01:40
clarkbmrda: the way CLA signing works is Gerrit collects the info from you, gpg encrypts it and POSTs it to a server at the foundation. The foundation does a 1:1 correlation based on name and email (or maybe just email) and if everythign lines up returns a 200 response to Gerrit01:41
jheskethumm, openstack.org (the website at least) works for me01:42
clarkbjhesketh: interesting, it isn't up for me01:42
jheskethyep, and I can log in01:42
* clarkb tries the phone01:42
fungiseems up01:42
jheskethmrda: can you ping openstack.org?01:43
clarkboh man derp01:43
clarkbI may be pebkacing /me checks a thing01:43
clarkbyup pebkac. proxies should diaf01:44
clarkbfungi: any other suggestions on what to look at?01:44
fungii'll try resubmitting my contact info in gerrit to make sure the connector's not broken01:44
fungibut will take me a couple minutes01:44
mrdafungi:  thanks01:44
*** sarob has joined #openstack-infra01:49
lifelessclarkb: you had a broken proxy ?01:49
clarkblifeless: yes, I had neglected to remove my proxy settings after using the wire in the conference room all week01:50
lifeless:P01:50
lifelessclarkb: ah, not a broken proxy. Broken proxy config :)01:50
*** sarob has quit IRC01:54
clarkbthough oddly my phone isn't happy with it either and that shouldn't be behind any proxy01:54
clarkbnow it works I think chrome was taking a break01:56
fungimrda: seems fine for me. after submitting i get... "Contact information last updated on Sep 23, 2013 at 1:54 AM."01:57
*** ryanpetrello has quit IRC01:58
clarkbfungi: do CLA signing errors end up in error_log? I see some sshd connection restsets and some tracebacks for melody but that is it01:58
clarkbprobably worth tracking down which ssh peer is doing that01:59
clarkbbut not tonight01:59
mrdafungi:  Do you have any ideas on how I can proceed?  Just tried again to no avail.01:59
*** ericw has joined #openstack-infra02:00
fungiwell, there wouldn't be cla signing errors. possibly contact filing errors but the two are distinct and separate processes, they just happen to both be accessible from that same screen02:01
fungiyou can still try them as separate steps02:01
fungii notice that the submit button for submitting my contact information seems to have hung my browser after displaying the update notice02:03
mrdafungi:  So I've signed up as a foundation member, now just wanting to sign the ICLA from gerrit.02:03
funginot on a real computer at the moment, but i'm going to see if i can poke around in the database and confirm whether it updated02:04
mrdafungi:  thanks02:04
clarkbfungi: I can check your account if that is easier02:04
fungimrda: you can try agreeing without filling in the contact info on that screen, and then submit the contact info separately in your gerrit account settings page02:06
*** w_ is now known as olaph02:06
mrdafungi:  cool, shall try.02:06
fungiclarkb: i can get to it, just typing speed here is at best 10wpm02:06
mrdafungi:  same problem, even not filling in the contact info.  The "Submit Agreement" button greys out, and it removes the "AGREE" text, but no ICLA agreement signed.02:08
fungihuh02:08
clarkbfungi: ya the failure mode seems to be different than any other related to the CLA that I have seen before02:11
clarkbparticularly since the was no mix up in CLA selection according to the DB (account_agreements has no rows for account 8125)02:11
fungiwell, the db does reflect my contact info update at least, so the connection to the foundation member system is intact02:12
*** SlickNik_ has joined #openstack-infra02:13
*** Ryan_Lane has joined #openstack-infra02:13
mrdaclarkb, fungi: Just tried it via an iPhone. Same result.  So I think it's not browser related.  Has anyone else signed the contributor agreement today?02:17
*** fbo_away has joined #openstack-infra02:17
*** enikanorov-w has joined #openstack-infra02:17
*** vishy has joined #openstack-infra02:17
*** jmeridth has joined #openstack-infra02:17
*** sungju has joined #openstack-infra02:18
*** sungju has quit IRC02:18
*** sarob has joined #openstack-infra02:19
*** sarob has quit IRC02:24
fungiit's hard to say since that's not timestamped by gerrit02:26
fungii'm looking to see if any lib updates happened in the past day or two02:27
mikalmrda: I wonder what the chrome developer tools network accesses thing says02:31
fungino deb updates of note in the past week or so which could be involved02:34
fungiand last modified times on the gerrit warfile and its java deps are months back02:35
mrdafungi, clarkb, mikal: I found the problem. PEPKAC. It's "I AGREE", not "AGREE".  Sorry for wasting your time.02:42
fungimrda: ha! good catch02:42
fungidefocusing the input field with the wrong content will gray out that button02:43
fungican't believe it didn't dawn on me that's what you were seeing02:44
mrdafungi:  I'm not sure why my brain saw "enter I AGREE in the box to the left" as needing me to enter "AGREE" when it should have been "I AGREE".  Thanks again!02:45
fungino worries. glad it's sorted02:46
clarkbfungi: thanks for helping out02:47
*** zehicle has joined #openstack-infra02:47
*** sarob has joined #openstack-infra02:50
fungiyw02:52
*** sarob has quit IRC02:55
*** amotoki has quit IRC02:56
*** blamar has quit IRC02:57
*** ericw has quit IRC02:58
*** SlickNik_ has quit IRC02:59
*** ericw has joined #openstack-infra02:59
*** ericw has quit IRC03:03
*** annegentle has quit IRC03:05
*** dims has quit IRC03:06
*** SergeyLukjanov has joined #openstack-infra03:06
*** annegentle has joined #openstack-infra03:08
*** CaptTofu has quit IRC03:11
*** CaptTofu has joined #openstack-infra03:12
*** ericw has joined #openstack-infra03:12
*** dcramer_ has quit IRC03:25
*** slong has joined #openstack-infra03:29
*** sarob has joined #openstack-infra03:50
*** sarob has quit IRC03:55
*** SergeyLukjanov has quit IRC04:17
*** michchap_ has joined #openstack-infra04:18
*** michchap has quit IRC04:21
*** michchap has joined #openstack-infra04:28
*** michchap_ has quit IRC04:31
*** michchap has quit IRC04:42
*** michchap has joined #openstack-infra04:45
*** alexpilotti has joined #openstack-infra04:46
*** annegentle has quit IRC04:49
*** sarob has joined #openstack-infra04:51
*** annegentle has joined #openstack-infra04:53
*** sarob has quit IRC04:55
*** afazekas has joined #openstack-infra05:01
*** UtahDave has quit IRC05:02
*** senk has joined #openstack-infra05:09
*** senk has quit IRC05:13
*** jhesketh has quit IRC05:20
openstackgerritA change was merged to openstack-infra/devstack-gate: Enable q-vpn service  https://review.openstack.org/4733505:24
*** bearhands is now known as comstud05:35
*** amotoki has joined #openstack-infra05:47
*** sarob has joined #openstack-infra05:52
*** sarob has quit IRC05:56
*** yolanda has joined #openstack-infra06:07
*** senk has joined #openstack-infra06:10
*** Ryan_Lane has quit IRC06:13
*** senk has quit IRC06:14
*** SlickNik_ has joined #openstack-infra06:24
*** AJaeger has joined #openstack-infra06:33
*** Ryan_Lane has joined #openstack-infra06:43
*** jhesketh has joined #openstack-infra06:47
*** jhesketh__ has joined #openstack-infra06:47
*** xchu has joined #openstack-infra06:49
*** pblaho has joined #openstack-infra06:50
*** sarob has joined #openstack-infra06:52
*** sarob has quit IRC06:57
*** SlickNik_ has quit IRC06:57
*** fbo_away is now known as fbo07:12
*** dizquierdo has joined #openstack-infra07:13
*** yportnova has joined #openstack-infra07:19
*** jcoufal has joined #openstack-infra07:23
*** SergeyLukjanov has joined #openstack-infra07:32
*** flaper87|afk is now known as flaper8707:32
*** adam_g has quit IRC07:42
*** adam_g has joined #openstack-infra07:42
*** adam_g has quit IRC07:42
*** adam_g has joined #openstack-infra07:42
*** sarob has joined #openstack-infra07:53
*** pabelanger has quit IRC07:53
*** jhesketh__ has quit IRC07:53
*** jhesketh__ has joined #openstack-infra07:55
*** pabelanger has joined #openstack-infra07:55
*** pabelanger has quit IRC07:55
*** pabelanger has joined #openstack-infra07:55
*** Ryan_Lane has quit IRC07:58
*** sarob has quit IRC07:58
*** kpavel has joined #openstack-infra08:04
*** kpavel_ has joined #openstack-infra08:05
*** dizquierdo has left #openstack-infra08:08
*** kpavel has quit IRC08:09
*** kpavel_ is now known as kpavel08:09
*** shardy_afk is now known as shardy08:10
*** Ryan_Lane has joined #openstack-infra08:28
*** Ryan_Lane has quit IRC08:32
*** dizquierdo has joined #openstack-infra08:39
*** boris-42 has joined #openstack-infra08:41
*** jhesketh has quit IRC08:52
*** sarob has joined #openstack-infra08:53
*** sarob has quit IRC08:57
*** Ryan_Lane has joined #openstack-infra08:58
*** mrda has quit IRC08:59
*** winston-d has quit IRC09:04
*** Ryan_Lane has quit IRC09:05
*** markmc has joined #openstack-infra09:11
*** alexpilotti has quit IRC09:14
*** ruhe has joined #openstack-infra09:29
*** sarob has joined #openstack-infra09:54
*** sarob has quit IRC09:58
*** SlickNik_ has joined #openstack-infra10:01
*** jcoufal has quit IRC10:04
*** ruhe has quit IRC10:05
*** ruhe has joined #openstack-infra10:11
*** mrda has joined #openstack-infra10:19
*** yaguang has quit IRC10:21
*** xchu has quit IRC10:22
*** pcm_ has joined #openstack-infra10:26
*** pcm__ has joined #openstack-infra10:30
*** pcm_ has quit IRC10:32
*** SergeyLukjanov has quit IRC10:36
*** ruhe has joined #openstack-infra10:50
*** hashar has joined #openstack-infra10:50
*** boris-42 has quit IRC10:51
*** sarob has joined #openstack-infra10:54
*** sarob has quit IRC10:59
*** SlickNik_ has quit IRC11:03
*** SergeyLukjanov has joined #openstack-infra11:05
*** hashar_ has joined #openstack-infra11:09
*** hashar has quit IRC11:10
*** hashar_ is now known as hashar11:10
*** dims has joined #openstack-infra11:12
*** w_ has joined #openstack-infra11:23
*** olaph has quit IRC11:25
*** ruhe has quit IRC11:27
*** pcm__ has quit IRC11:29
*** CaptTofu has quit IRC11:33
*** mkerrin has quit IRC11:37
*** CaptTofu has joined #openstack-infra11:42
*** CaptTofu has quit IRC11:45
*** CaptTofu has joined #openstack-infra11:46
*** ruhe has joined #openstack-infra11:46
*** ArxCruz has joined #openstack-infra11:46
sdagueso apparently we never released the gerrit lib with the bulk query defined?11:46
sdagueany chance we could do that today, I'd actually like to use it in a tool for tempest11:47
*** CaptTofu has quit IRC11:49
*** CaptTofu has joined #openstack-infra11:49
*** weshay has joined #openstack-infra11:49
*** CaptTofu has quit IRC11:51
*** CaptTofu has joined #openstack-infra11:51
*** sarob has joined #openstack-infra11:55
openstackgerritSean Dague proposed a change to openstack-infra/gerritlib: fix param ordering to fix review function  https://review.openstack.org/4782111:59
*** sarob has quit IRC11:59
*** cppcabrera has joined #openstack-infra12:04
*** mrda has quit IRC12:04
*** lcestari_ has joined #openstack-infra12:09
*** CaptTofu has quit IRC12:11
*** CaptTofu has joined #openstack-infra12:11
*** boris-42 has joined #openstack-infra12:13
*** thomasm has joined #openstack-infra12:24
*** rfolco has joined #openstack-infra12:27
*** thomasbiege has joined #openstack-infra12:31
*** adalbas has joined #openstack-infra12:34
*** thomasbiege has quit IRC12:35
*** dkliban has quit IRC12:36
fungii'm sure it's doable. we'll likely have enough people around for consensus once the earth spins a little more12:41
*** zehicle has quit IRC12:42
sdaguesilly earth roundness12:45
sdagueok, time to migrate to office anyway12:45
sdagueI did manage to write a nice little script to run through old reviews and get jenkins to recheck on them, to expose merge conflicts12:45
fungisdague: neat!12:47
*** ruhe has quit IRC12:50
*** dims has quit IRC12:53
*** zehicle has joined #openstack-infra12:53
*** dims has joined #openstack-infra12:54
*** alexeyo has joined #openstack-infra12:57
*** sandywalsh has quit IRC12:57
*** alexeyo has quit IRC13:00
*** pcm_ has joined #openstack-infra13:00
*** alexeyo has joined #openstack-infra13:01
*** prad has joined #openstack-infra13:01
*** dprince has joined #openstack-infra13:03
*** prad has quit IRC13:05
*** dcramer_ has joined #openstack-infra13:05
alexeyohi all13:06
alexeyoI have been working on a scheduler redesign and stumbled upon the following problem: http://logs.openstack.org/67/45867/4/check/gate-nova-python26/087aba0/console.html13:06
*** rustlebee is now known as russellb13:08
*** sandywalsh has joined #openstack-infra13:10
*** amotoki has quit IRC13:10
*** dkliban has joined #openstack-infra13:12
*** julim has joined #openstack-infra13:12
*** julim has quit IRC13:13
*** CaptTofu has quit IRC13:15
alexeyofungi hi13:15
*** CaptTofu has joined #openstack-infra13:16
*** jhesketh__ has quit IRC13:16
alexeyoapparently I can't add requirements anymore (link to log above)13:16
*** mriedem has joined #openstack-infra13:17
alexeyois it an ok behavior?13:17
*** CaptTofu has quit IRC13:17
*** julim has joined #openstack-infra13:17
*** mriedem has quit IRC13:17
*** CaptTofu has joined #openstack-infra13:17
*** mriedem has joined #openstack-infra13:18
sdaguealexeyo: you have to change global requirements first, you can't make requirements change in a project unless their are already matching lines in global requirements13:18
*** dprince has quit IRC13:19
alexeyoI see, so I have to make a regular commit to openstack/requirements with my would-be requirement first, right?13:21
fungialexeyo: that's been the case throughout the entire havana development cycle as well as at least part of the grizzly cycle. also, getting additions to the global requirements list approved is fairly unlikely to happen between now and when we start work on the icehouse release13:21
*** mriedem has quit IRC13:22
*** ryanpetrello has joined #openstack-infra13:22
alexeyookay, so it has to be approved to be a global requirement first and only after that I could add it to project's reqs, do i get this rigth?13:23
*** mriedem has joined #openstack-infra13:23
mordredmorning13:23
fungithe hope is that we give downstream packagers and integrators a period of stability in our dependency lists throughout the release candidate period, and also free up developers to fix release-critical bugs rather than working on new features13:23
fungialexeyo: yes, the requirements reviewers, in addition to making sure it's a safe time in the development cycle to add/change the requirements list (early after the last release is generally better), the additions are also checked for licensing conformance, release versioning stability and other sorts of concerns13:24
*** jcoufal has joined #openstack-infra13:24
mordredalexeyo: zigo has expressed interest in getting the sqlalchemy req changed, and zul has confirmed that ubuntu is ok with 0.813:25
mordredI have no idea if that will actually get changed this cycle13:25
*** sarob has joined #openstack-infra13:25
boris-42mordred imho I very worried about switching to sqla0.813:25
zuli think we need to have a session at ODS for the requirements project13:25
alexeyoI see13:26
boris-42mordred I wrote a lot of sqla hacks so there could be a lot of hidden bugs that won't be tested by our current tests..13:26
fungizul: that'll make at least three summits in a row we've had a session about the requirements project. almost as if it's taken on a life of its on13:26
boris-42mordred we should test all this stuff by hands before..13:27
zulfungi:  yeah i think we need something written down for it13:27
alexeyoso in case one needs a new requirement for a new feature where should he/she start?13:27
zulyeah13:27
zulalexeyo:  like processes stuff13:28
fungiboris-42: well, at the moment my crude test of sqla 0.8.x is definitely not happy in devstack-tempest jobs, no idea about unit tests even... https://review.openstack.org/4774513:28
alexeyozul: sorry, didn't get this one13:28
*** changbl has quit IRC13:29
boris-42fungi we planned migration to sqla 0.8 after all projects switch to oslo-db code13:29
*** tvb has joined #openstack-infra13:29
boris-42fungi end when we test all by hands and fix all bugs13:29
*** SergeyLukjanov has quit IRC13:29
*** tvb has quit IRC13:29
*** tvb has joined #openstack-infra13:29
zulalexeyo:  things like when would it not be ok to change requirements13:29
*** dkranz has joined #openstack-infra13:29
*** sarob has quit IRC13:29
boris-42fungi so we should avoid bumping version of sqla at this moment imho =)13:30
fungiboris-42: oh, i entirely agree--the change i uploaded was purely a test to see where things stand with regard to integration tests. i have no vested interest there13:30
alexeyowhat I am trying to say is that if one decides to build a new feature and needs an extra package to make it work then it is not clear how to start with integrating this feature13:31
alexeyoespecially if it is the only one to use this package13:31
alexeyo(at least for now)13:31
fungialexeyo: general recommendations are, 1. follow the openstack-announce and openstack-dev mailing lists so you know what's going on (release freezes for example), 2. submit a change to the project you're working on which includes that new requirement and leave a comment on that change that requirements tests won't pass until the requirement gets added to the global list, 3. if core reviewers on that13:32
fungiproject are in favor of your change submit a corresponding change to openstack/requirements noting which change needs it13:32
*** tvb has quit IRC13:33
alexeyowhile there is no feature for which a requirement is needed it is pointless to approve it, while requrements are not satisfied the feature won't pass the gate13:33
*** bnemec has joined #openstack-infra13:33
*** matty_dubs|gone is now known as matty_dubs13:33
sdaguealexeyo: global requirements are there to ensure that anything that openstack might depend on is something the distros are able to package, and passes sanity checking around licensing and maintainability13:34
*** SergeyLukjanov has joined #openstack-infra13:34
mordredboris-42: I agree with you - but apparently ubuntu and debian have both upgraded themselves already, so I'm also a little worried about what happens for people trying to run on ubuntu from packages13:34
boris-42mordred fuuuu*13:34
boris-42=)13:34
mordred:)13:34
alexeyofungi: thanks, it is becoming much clearer now13:34
fungialexeyo: also if the requirement change is a new dependency, then it's worth discussing on the openstack-dev ml well ahead of time to see whether there are any likely concerns, particularly if there's something unusual about it13:34
zulmordred:  we tested it and reported stuff that we see and even helped fixed them13:35
sdaguezul: then why can't keystone start on 0.8?13:35
sdagueyou guys have a patch for that?13:35
zulsdague:  it does for us13:35
sdagueit seems like a big disconnect13:35
zulit does im not exactly sure debian'13:36
zuldebian's problem13:36
zul(new keyboard)13:36
sdaguezul: well it doesn't with pure upstream, so I'm curious what's been patched to make it work13:36
*** rpodolyaka has joined #openstack-infra13:36
zulsdague:  im not sure13:36
*** blamar has joined #openstack-infra13:37
sdaguethat's the logger head that we're add right now, the fact that we can't start keystone on 0.8, but the distros can, means there is a difference that needs to get resolved13:37
fungizul: it doesn't work on our devstack-tempest tests (see http://logs.openstack.org/45/47745/1/check/gate-tempest-devstack-vm-full/7aa67c7/console.html for example)13:37
sdagueit's an import issue13:37
sdaguefrom what I can tell13:37
zulsdague:  maybe we have a patch in the sqlachemy package13:37
mordredgah13:37
sdaguezul: that's entirely possible13:37
* mordred punches someone13:37
mordredthe distro-patches-upstream thing is vastly overused, btw13:38
zulmordred:  so sue me ;)13:38
mordredzul: lawsuit in mail13:38
sdaguezul: anyone from canonical able to help unwind this? us doing archaeology on debs without a guide isn't the fastest way to resolve13:38
sdaguemordred: it could have been a debian patch as well that was inherited13:38
mordredsdague: yup. I believe all the distros are more or less equally to blame in the general state of things there13:39
*** DennyZhang has joined #openstack-infra13:39
fungizul: http://logs.openstack.org/45/47745/1/check/gate-tempest-devstack-vm-full/7aa67c7/logs/screen-key.txt.gz "CRITICAL log logging_excepthook cannot import name exceptions"13:39
zulsdague:  fastest way is to install ubuntu precise in a vm with the cloud archive and run your tempest tests13:39
fungithat may be a red herring tho13:39
zulfungi:  yeah thats an api change with sqlalchemy13:39
rpodolyaka...looks like I'm late for the party... are you guys looking for a particular patch which made sqlalchemy-migrate work with sqlalchemy 0.8.x?13:40
fungizul: on that note! we just tried to upgrade to using cloud archive over the weekend13:40
zulfungi:  oh?13:40
zuldid it blow up?13:40
fungizul: libvirt 1.x was a bit of a problem for us13:40
zulfungi:  how so?13:40
fungisplodey13:40
fungiwe had to do an emergency rollback to get devstack working again13:40
mordredrpodolyaka: we're trying to figure out why sqla 0.8 works if you install everything from distro packages, and doesn't if you install from pip13:41
mordredrpodolyaka: we're surmising that there is a patch in the distro packages somewhere13:41
*** w_ is now known as olaph13:41
sdaguefungi: actually, on that front, you got a copy of the bum image somewhere? I'd like to exactly replicate it if possible13:41
rpodolyakamordred: Ubuntu (or Fedora) guys patched it. it's really small. I'll post a link to it in a few minutes13:41
fungisdague: we deleted the image, but even if we did have, our "openstack" providers don't know how to make a public glance yet (well, it's apparently in progress in both of them but not officially ready yet)13:42
zulmordred:  this is compat patch for sqlachemy migrate fql sqla 8.0 http://summit.openstack.org/cfp/details/10913:42
rpodolyakamordred: https://github.com/stackforge/sqlalchemy-migrate/commit/74ccf7a39762020671bf73820bae030d4b28bc9613:42
zuloops no it isnt13:42
zulhttp://paste.ubuntu.com/6145576/13:42
rpodolyakamordred: so we already have it master of sqlalchemy-migrate13:42
rpodolyakamordred: and this one too  https://github.com/stackforge/sqlalchemy-migrate/commit/2ff11c176af15cae3a5ea0223ee3fc236f1eab1313:43
fungisdague: btw, do you have links to any of the changes/logs for the failures we saw? i didn't think to make a note of any for posterity13:43
mordredah! wow, I love it when there's folks who actually know what's going on!13:44
rpodolyaka:)13:44
mordredso - step one is "release a new sqlalchemy-migrate" - step two is "tests sqla 0.8 again until boris-42 is happy" - step three is "bump requirements" - step four is "profit" ?13:45
boris-42step 4 .....13:45
boris-42step 5 PROFITTT13:45
boris-42=)13:45
mordredboris-42: :)13:46
fungisdague: if not, no worry, i can probably dig one up13:46
sdaguefungi: I made a bug, but launchpad's not letting me log in right now13:46
sdagueso finding it... more difficult13:46
zulboris-42:  https://bugs.launchpad.net/cinder/+bug/1206561 (cinder sqla8 bug)13:47
uvirtbotLaunchpad bug 1206561 in cinder "Migration tests fail with sqlalchemy 0.8" [Undecided,New]13:47
boris-42zul ouch=)13:47
fungisdague: no worries, i just realized my sqla req bump triggered it too13:48
fungizul: http://logs.openstack.org/45/47745/1/check/gate-tempest-devstack-vm-full/f926000/console.html "Server bac84e47-cc28-46ea-ba71-3f740bdee508 failed to reach ACTIVE status within the required time (400 s)."13:49
*** alexeyo has quit IRC13:49
fungizul: apparently libvirt was dying behind the scenes13:49
zulfungi:  you have the libvirt log for it? :)13:50
zul/var/log/libvirtd13:50
sdaguezul: I don't think we capture that13:50
fungizul: i'm looking but i don't theink13:50
fungiwhat sdague said13:50
zulok13:50
sdaguen-cpu just stops13:50
*** rcleere has quit IRC13:50
*** DennyZhang has quit IRC13:50
*** DennyZhang has joined #openstack-infra13:51
*** mrmartin has joined #openstack-infra13:51
sdagueok, is launchpad not letting anyone else in?13:51
fungisdague: working for me13:51
fungisdague: what project did you open the bug against?13:52
sdaguenova13:52
sdaguehttps://bugs.launchpad.net/nova/+bug/122897713:53
uvirtbotLaunchpad bug 1228977 in nova "n-cpu seems to crash when running with libvirt 1.0.6 from ubuntu cloud archive" [High,New]13:53
sdagueit's in the recheck list13:53
fungiaha, bug 122897713:53
uvirtbotLaunchpad bug 1228977 in nova "n-cpu seems to crash when running with libvirt 1.0.6 from ubuntu cloud archive" [High,New] https://launchpad.net/bugs/122897713:53
fungioh, you just linked it13:53
zulwait why are you guys using 1.0.6?13:53
fungizul: that's what installed as soon as we added ubuntu cloud archive to our sources13:54
zulhavana-proposed has 1.1+ though?13:54
openstackgerritMarton Kiss proposed a change to openstack-infra/config: Groups-dev drupal drush update to 6.0.0  https://review.openstack.org/4783813:55
sdaguezul: it's whatever was in havana/updates13:55
fungizul: perhaps https://review.openstack.org/45896 was wrong?13:55
fungiyeah, precise-updates/havana13:55
*** michchap has quit IRC13:56
zuli dunno maybe you guys might want to used havana-proposed13:56
*** michchap has joined #openstack-infra13:56
zulor precise precise-proposed13:57
fungizul: i think part of the goal is to test our changes against the libs ubuntu has already tested and approved13:57
zulah ok13:57
mordredyes. that is correct13:57
fungiso it might make more sense to wait until what's in precise-updates/havana works with our tests, and then start using it going forward13:57
mordred(I really love this particular chicken and egg)13:58
sdaguezul: there is also the issue of asymetry, because if packages are dropping into there without having proven themselves in our gate first, then we can have what happened this weekend13:59
sdaguewhere an ubuntu package update blocks all code merge for 16 hours13:59
*** michchap has quit IRC13:59
*** michchap has joined #openstack-infra14:00
sdagueok... so lp login isn't working today, and lp is being extra slow in sending reset email14:00
sdaguethat makes for a bad way to start a monday14:01
fungisdague: granted, we already have that (precise security updates could in theory cause it too)14:01
*** CaptTofu has quit IRC14:01
sdaguefungi: yes, though the risk surface on that is less14:01
*** CaptTofu has joined #openstack-infra14:02
fungiand even with some dependency caps in place, it doesn't entirely stop new/broken packages on pypi from causing the same14:02
sdagueit would be good to make sure the image can run devstack gate before it promotes14:02
sdaguefungi: sure14:02
fungisdague: we do already perform a sanity check on the candidate image before it gets used, so that might just be a question of extending what constitutes sanity14:03
*** tvb has joined #openstack-infra14:05
*** tvb is now known as Guest7263614:05
sdaguefungi: ok, cool, where is that in code base?14:05
fungisdague: currently looking for it in nodepool14:06
*** Guest72636 has quit IRC14:06
mordredsdague: we've talked about doing that in the future when we're dib based for images14:07
sdaguemordred: cool14:07
mordredsdague: I'm mildly concerned about making it too strong though14:07
mordredsdague: because we _want_ to know when upstream breaks us14:08
mordredand if we just stop promoting images14:08
mordredno one will notice14:08
sdaguemordred: well we need signalling on it14:08
sdagueso we know there was a fail14:08
mordredso far, our track record on watching signallying not related to code reviews is bad :(14:08
fungisdague: right now here's what goes on for an image update... https://git.openstack.org/cgit/openstack-infra/nodepool/tree/nodepool/nodepool.py#n34014:08
openstackgerritMarton Kiss proposed a change to openstack-infra/config: Groups-dev distbuild checked wrong Git repository commit hash  https://review.openstack.org/4784414:10
fungisdague: while a full tempest run is probably something which would need more work to integrate, some devstack-specific sanity checks in https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/nodepool/scripts/prepare_devstack.sh might help?14:13
fungior https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/nodepool/scripts/devstack-cache.py14:13
fungianything which didn't make the resultant image unsuitable for reuse is potentially a candidate14:14
*** rnirmal has joined #openstack-infra14:15
*** ruhe has joined #openstack-infra14:19
*** rcleere has joined #openstack-infra14:22
*** CaptTofu has quit IRC14:22
*** CaptTofu has joined #openstack-infra14:22
mordredfungi: https://review.openstack.org/4784814:24
mordredfungi: there's the basic/simple version of the tox update we want for everyhone14:24
*** CaptTofu has quit IRC14:25
fungiexcellent14:25
*** rcleere has quit IRC14:25
*** rcleere has joined #openstack-infra14:26
*** sarob has joined #openstack-infra14:26
fungithat seems to jive with the couple of reviews of yours i already went through14:26
*** CaptTofu has joined #openstack-infra14:26
*** rcleere has quit IRC14:27
*** markmcclain has joined #openstack-infra14:28
*** dprince has joined #openstack-infra14:29
*** sarob has quit IRC14:30
*** CaptTofu has quit IRC14:31
*** dkranz has quit IRC14:31
*** CaptTofu has joined #openstack-infra14:32
jd__mordred: around?14:32
mordredjd__: always14:34
sdaguemordred: yeh, so that's probably a good summit session. A better way to get a handle on status of some non code review initiated changes14:34
mordredsdague: ++14:34
jd__mordred: we just realized that the MANIFEST.in from Horizon is bugged14:35
jd__mordred: I think nobody noticed because pbr use git ls-files rather than MANIFEST.in if sdist is run from a git clone14:35
jd__mordred: I wonder if it shouldn't be better to always pick MANIFEST.in if it's there14:35
mordreduhm. one sec - let me llok so I have better context14:35
jd__mordred: pbr/packaging.py around line 54514:36
mordredoh!14:36
mordredno, I know that14:36
mordredI wanted to see horizon's manifest.in14:36
mordredthat's a crazy MANIFEST.in file14:36
jd__somehow14:36
mordredwhy don't we just remove it?14:36
*** zehicle has quit IRC14:37
mordredor, replace it just with one that has exclude openstack_dashboard/local/local_settings.py14:37
mordredsince that seems to be the only thing locally that would need to be added in addition to what pbr does14:37
jd__mordred: I think we could remove it14:37
jd__that's the fix for Horizon14:37
jd__the other question that remains to me, is pbr having a good behaviour prefering git ls-files over MANIFEST.in, in general14:38
mordredin any case - pbr _should_ use both14:38
jd__ah :)14:38
jd__that's a valid answer to that remaining question14:38
mordredbut it's going to process them in a sequence14:38
mordredand it's possible that we're doing them in a bad order14:38
mordredin terms of processing things like exclude + include lines14:38
mordredjd__: what was the bug you uncovered in horizon? like, which thing happened or didn't happen?14:39
jd__mordred: horizon/conf/__init__.py file isn't included for example14:39
mordredjd__: wow, really?14:40
jd__yup14:40
jd__you can try easily by copying your git clone, rm -rf .git and run python setup.y sdist14:40
mordredoh! no.14:41
mordredthat's not supported14:41
mordredat14:41
mordredall14:41
mordrednever has been14:41
mordreddon't intend for it to be14:41
mordredif that's a thing that people want to support, it's a complete design change and would require a decently large amount of work14:41
jd__what?14:41
*** dafter has joined #openstack-infra14:42
jd__I don't follow you14:42
mordredwe do not expect python setup.py sdist to work outside of a git repo14:42
jd__running sdist while there's a MANIFEST.in is supported AFAIU14:42
mordrednot by OpenStack it's not14:42
*** dafter is now known as tvb14:42
mordred(I understand it's supported by python itself)14:42
jd__mordred: this isn't nice to packages :)14:42
jd__packagers14:42
*** tvb has quit IRC14:42
*** tvb has joined #openstack-infra14:42
mordredsure it is14:42
mordredin fact14:43
mordredit's exactly in line with how packaging is supposed to work14:43
mordredpackagers are supposed to consume the tarball that upstream produces14:43
mordredthey are NOT supposed to produce their own14:43
jd__fair enough14:43
*** dkranz has joined #openstack-infra14:43
*** datsun180b has joined #openstack-infra14:43
mordredand - if they want to use something like git-buildpackage - I strongly recommend the --pristine-tarball optiion and git import-tarball14:44
mordredscuse me - import-orig14:44
* mordred needs to write a specific write up on this - it keeps coming up14:44
jd__mordred: agreed, talking with zigo14:44
jd__about this14:44
mordredjd__: if there are ways in which I can better help packaging workflow though, I definitely want to do them - there is a 100% chance there are things I have not thought about :)14:46
*** pcrews has joined #openstack-infra14:46
jd__mordred: well having the ability to build the SOURCES.txt correctly from scratch would be nice I think14:47
jd__and it's not that far away14:47
mordredjd__: is SOURCES.txt not doing the right thing?14:47
jd__mordred: well it depends heavily on the context you are building it14:47
fungipart of the problem here, particularly with some of the gbp howtos, is that they're written to help package maintainers cope with upstreams who don't produce releases and/or don't generate tarballs, and so they assume workflows which are counter to what we're doing in openstack14:47
jd__like I said, in Horizon depending on you being in a git clone or not, MANIFEST.in is taking into account or not and does not generate the same14:48
mordredjd__: I have horizon/conf/__init__.py in my SOURCES.txt when I make a tarball14:48
mordredoh - you still mean outside of a git clone14:48
jd__yes :)14:48
mordredyou should never be running commands in packaging that regenerate that14:48
jd__for example that works fine with Ceilometer, but not Horizon14:48
mordredreally14:48
jd__mordred: yeah, YMMV I guess, though using upstream tarballs is fine with me14:49
mordredah - ceilometer seems to be maintaining a MANIFEST.in file14:49
jd__I just need to convince zigo :)14:49
mordredwe gave up on maintaining those in favor of git about 1.5 years ago because the tarballs would consistently have things missing14:49
mordredjd__: I agree with what fungi said above - the 'right' way to do packaging involves consuming upstream tarballs if they exist14:50
fungigbp has plenty of support for consuming upstream tarballs, so i still can't figure out why there's been such resistance to using that in the debian openstack packaging workflow14:50
mordredthat's the reason that debian has a .orig.tar.gz in the set of files associated with it14:50
mordredthe only reason gbp has support for the other thing is for hipster upstreams who do not release anything14:50
mordredif the packager produces his own orig.tar.gz, then there is no way to verify that the contents are what they are claimed to be14:51
mordreddebian's .orig.tar.gz shoudl be binary == to openstack's released .tar.gz14:51
mordredit becomes even more important when we start signing our tarballs14:52
fungii'm particularly concerned that by not using our tarballs, debian is carrying source packages with regenerated orig tarballs which do not match checksums in our release announcements or on our tarballs server/pypi/lp/et cetera14:52
*** rcleere has joined #openstack-infra14:52
*** fbo is now known as fbo_away14:52
mordredfungi: exactly14:52
mordredit's a giant bug14:52
fungiwhat mordred said14:52
mordredand should be fixed14:52
*** zehicle has joined #openstack-infra14:52
mordredwith haste14:52
mordredbecause otherwise the entire design of debian packaging is being subverted14:52
fungiand i really suspect the culprit is blind following of some howto which told someone how to use gbp with $random_project which doesn't publish tarballs14:53
* mordred needs to write a howto doc14:53
*** dizquierdo has quit IRC14:54
* fungi goes to check what's landed in sid/jessie recently14:55
*** mrmartin has quit IRC14:56
zulfyi we use upstream tarballs for our releases ;)14:57
*** zehicle has quit IRC14:59
fungioh, for starters, they're repacking our tarballs with xzi15:00
fungip15:00
mordredwhy?15:00
fungihttp://ftp.de.debian.org/debian/pool/main/n/nova/nova_2013.1.3.orig.tar.xz15:00
mordredsigh15:00
fungibecause $shiny_new_thing15:00
mordredfungi: sorry. I forgot. gzip is terrible15:01
mordredfungi: should we release .tar.bz2 and .tar.xz to maybe prevent people from doig that?15:01
*** sarob has joined #openstack-infra15:01
jeblair don't forget rar15:01
fungiadmittedly it's about 50% the size of our tarball for nova, but still that's tiny to start with15:01
*** tvb has quit IRC15:02
fungii would not be opposed to having our tarball jobs start publishing .tar.xz versions and including their checksums in future release announcements if ttx doesn't object15:02
*** tvb has joined #openstack-infra15:03
*** sarob_ has joined #openstack-infra15:03
*** tvb is now known as Guest8217515:03
*** thedodd has joined #openstack-infra15:04
*** sarob has quit IRC15:04
fungicurrent consensus is there's little point to releasing .tar.bz2 if you also do .tar.xz and .tar.gz since xzip performs at least as well as bzip2 under most circumstances and for everyone else who doesn't have $shiny_new_tool there's still your tried-and-true gzip version15:04
ttxfungi: they should at least keep the same .tar inside the recompressed thing15:04
*** Guest82175 is now known as tvb15:04
ttxi.e. if you take the signed .gz and their thing and uncompress it, you should end up with the same .tar15:05
*** tvb is now known as Guest3168215:05
ttxThat's been the rule for recompressing in debian packaging15:05
*** changbl has joined #openstack-infra15:05
ttxso that they don't lose the verification chain15:06
fungittx: yeah, they don't. (just compared checksums for unxz nova_2013.1.3.orig.tar.xz and gunzip nova-2013.1.3.tar.gz)15:06
ttxnow *that* would be bad debian packaging.15:07
* ttx with his debian packager hat on15:07
fungitheir nova tarball, uncompressed, is also much smaller than ours15:07
fungidiffing the contents now to see what's left out15:07
pabelangerfungi, I though dfsg was to be append if modifying the upstream tarball?15:09
mordredfungi: that's probably because they're actually not using our tarball at all, but are re-generating it from source incorrectly, afaict15:09
*** sarob_ has quit IRC15:09
mordredpabelanger: I believe you are correct15:09
mordredbecause the only valid reason in debian for modifying the upstream tarball is to fix dfsg violations15:09
pabelangermordred, yes, that is my understanding also15:09
fungipabelanger: that's convention when the tarball is repacked specifically for compliance with debian free software guidelines15:10
mordredjd__: you may have just awakened the beast which is a channel full of old-school debian packagers15:10
pabelangerfungi, Oh, I see15:10
fungithere are actually other circumstances where the package maintainer might need to repack a tarball, but generally it should be avoided unless those are very, very good reasons15:10
pabelangerfungi, agreed15:11
jd__mordred: :-)15:11
fungiand it's still convention to at least modify the name of the orig tarball when doing that, yes15:11
Shrewsmordred: this change (http://lists.openstack.org/pipermail/openstack-dev/2013-September/015495.html) should be made to stackforge project too, i assume?15:11
mordredShrews: yes. it will make everyone happier15:11
fungipabelanger: and also a get-orig-source target is good in the debian/rules to make it easy for others to repeat the repacking process deterministically15:11
mordredShrews: if it doesn't make you happier, you're wrong15:12
fungipabelanger: and a readme.source file to describe precisely why it was repacked15:12
*** zigo_ has joined #openstack-infra15:13
fungiokay, so it looks like the debian regenerated nova 2013.1.3 tarball omits our AUTHORS, ChangeLog, PKG-INFO and nova.egg-info while including .gitignore and .gitreview, and also strips a blank line from the end of setup.cfg15:18
*** reed has joined #openstack-infra15:18
fungibasically, didn't run setup.py sdist15:18
mordredyup15:19
pabelangerDo we know why they are regenerating the tarball or is it just a static part of there process?15:19
mordredI consider that a bug15:19
mordredpabelanger: I believe they are following the "how to consume an upstream git repo" process, rather than the "how to consume an upstream tarball" process15:19
jd__you can ask zigo_ directly :)15:20
mordredhey zigo_15:20
mordredwe're talking smack about you15:20
pabelangermordred, Ah, ya, that would do it15:20
mordredbut it's really because we'd like to help15:20
zigo_mordred: Adding *.py in the "recursive-include horizon" line of the MANIFEST.in fixed our problems.15:20
zigo_mordred: I believe that's a bug in the original MANIFEST.in of horizon, which nobody really uses.15:21
*** mgagne has joined #openstack-infra15:22
mordredzigo_: it is not a bug in the original MANIFEST.in, it's a bug in the debian packaging15:22
mordredzigo_: what can I do to move you away from not using our tarballs?15:22
fungizigo_: the bigger question is why you're distributing tarballs in your source packages which claim to be original upstream tarballs, but aren't15:22
mordredright. what fungi said15:22
zigo_fungi: I haven't claim such thing.15:23
mordredzigo_: nova_2013.1.3.orig.tar.xz15:23
zigo_mordred: And?15:23
mordredzigo_: is not, in fact, related to nova_2013.1.3.tar.gz15:23
fungizigo_: the tarball does not include a readme.source explaining why you're not using upstream tarballs, nor a get_orig_source target in debian/rules15:23
mordredit's contents are wrong, for one15:23
zigo_Probably switching to .xz compression would be a good start. Removing the ChangeLog which is huge, and which the FTP masters *refused* would also help.15:24
fungiand yes, most importantly, it lacks files generated by our sdist and the checksums are obviously different from what we sign and attest to in release announcements15:24
fungiftpmaster said our ChangeLog file was unsuitable for inclusion in the source tarball?15:24
fungiwhy, specifically?15:24
flaper87dhellmann: ping15:25
zigo_fungi: For a binary of let's say 30KB, it adds about 1.5 MB of changelog.15:25
dhellmannflaper87: pong15:25
zigo_Multiply this by the number of .deb, and you get a quite bad result.15:25
zigo_Also, dealing with pristine-tar branch and upstream branch is *very* annoying.15:25
fungizigo_: just because it's in the orig tarball doesn't mean it needs to get included in the packages15:26
zigo_With tags, I got everything contained in a single packaging branch.15:26
zigo_That's a lot more convenient.15:26
mordredzigo_: but it's the right thing to do if upstream has an orig tarball15:26
zigo_Well, it's what *you* think is right! :)15:26
*** Guest31682 is now known as tvb15:26
fungias upstream, yes15:26
zigo_Explain to me why it's not valid to use what's in the Git...15:26
*** tvb has quit IRC15:26
*** tvb has joined #openstack-infra15:26
mordredyou aren't using it right15:26
flaper87dhellmann: hey, I wanted to know if we could let those 3 requirement patches related to marconi land. The 3 of them are blocking other patches and that's going to slow down the work until ith development cycle begins15:26
mordredzigo_: if you want to use our git as a source15:27
fungizigo_: because upstream says it's not what they release?15:27
dhellmannflaper87: let me look again15:27
flaper87dhellmann: https://review.openstack.org/#/c/46757/15:27
mordredyou need to run python setup.py sdist in the context of our git repo so that you get the correct metadata into the package15:27
flaper87dhellmann: https://review.openstack.org/#/c/47580/15:27
mordredwhich your package is missing15:27
zigo_fungi: Well, upstream is not always right. For example, upstream tries to write in /usr/share in horizon...15:27
flaper87dhellmann: https://review.openstack.org/#/c/47582/15:27
mordredzigo_: that's completely different15:27
fungizigo_: i would consider that a bug, definitely15:27
mordredzigo_: that's what the upstream tarball does at install time15:27
flaper87The 3 of them are *marconi specific* and don't affect any other module15:27
mordredwhich you control via the files in debian/15:28
flaper87I mean, not directly15:28
zigo_mordred: I'm only replying to "because upstream says so", saying that this is not a valid argumentation... :)15:28
mordredzigo_: I agree. I do not think it's a valid argument either.15:28
dhellmannflaper87: the change to falcon bothers me because it implies there is not actually any work being done to investigate moving off of falcon, as promised15:28
mordredI'm saying, as a packager, regenerating the upstream tarball incorrectly15:28
mordredbecause it's 'more convenient'15:28
mordredis not the right thing to do15:28
dhellmannflaper87: I think the other changes were just for stability at this point in the cycle15:28
mordredupstream has nothing to do with it15:28
sdaguezul: so your havana libvirt / qemu requires ceph?15:29
mordredalso, you are breaking the ability to track that the software came from where you said it came from15:29
zulsdague:  i believe so what are you seeing?15:29
dhellmannflaper87: I'd be ok with letting those other 2 in if mordred agrees15:29
mordredsince, by regenerating the tarball, the fingerprints can no longer be folloed15:29
flaper87dhellmann: AFAIR, the request was to study the possibility to move away from falcon which we'll do https://blueprints.launchpad.net/marconi/+spec/pecan-framework15:29
zigo_mordred: Just explain to me why using the git sources is wrong then! Last time at the summit, I asked what was different, and the only thing you told me was that there was a ChangeLog and an AUTHORS file.15:29
flaper87dhellmann: but AFAIR, it wasn't a strong requirement15:29
sdaguezul: well, it's not a devstack dep, and apparently it's not a hard enough requirement to blow things up early15:29
mordreddhellmann: point me at a thing?15:29
flaper87that doesn't mean we're not considering / evaluating that, though15:30
sdagueok, so apparently I'm close enough to try to replicate now15:30
mordredzigo_: it's wrong because you are reporting bugs in our MANIFEST.in files15:30
dhellmannmordred: https://review.openstack.org/#/c/47580/ and https://review.openstack.org/#/c/47582/15:30
mordredzigo_: which means you're doing something which is causing things to not operate as designed15:30
zulsdague:  ive ran libvirt with ceph though pretty much everyday so I dont know what you are seeing15:30
zigo_mordred: Well, it really *is* a bug this time.15:30
mordredit's not15:30
dhellmannflaper87: I have a hard time reconciling new features going into falcon with the idea that marconi could become less dependent on it.15:30
mordredthe tarballs I produce work fine15:31
sdaguezul: well you have symbol linkage, so you can't even start a 64bit guest, unrelated to openstack, unless you have ceph installed15:31
zigo_mordred: How come "python setup.py install" doing the wrong thing isn't a bug???15:31
zulsdague:  erm?15:31
zulsdague:  can you open up a bug please15:31
flaper87dhellmann: but falcon development doesn't depend on Marconi. It's its own release cycle, bugs fixes and whatnot. I understand your concern, though.15:31
*** tvb has quit IRC15:31
mordredzigo_: MANIFEST.in does not affect operation of setup.py install15:31
sdaguezul: sure, once I get further on this tempest thing15:32
*** tvb has joined #openstack-infra15:32
*** tvb has joined #openstack-infra15:32
mordredzigo_: so, if you had to modify that file to get a file instaled15:32
zulsdague:  k15:32
mordredthen you are doing something wrong a step before15:32
mordredwhich is that you are improperly generating a source tarball15:32
dhellmannflaper87: right, I don't actually care about falcon development per se, but if marconi is depending on new features of falcon that doesn't say to me there is serious work being done to think about moving to the same toolset the rest of us are using15:32
mordredwhich is why the file was not there for you to install15:32
zigo_mordred: Let's agree that we don't agree... :)15:32
fungizigo_: also, i still find it hard to believe that ftpmaster would tell you our changelog files had to be removed from our tarballs to be redistributable. i can understand that they wouldn't want you including it in the binary packages because of multiplicity issues, but insisting that you repack the upstream tarball to remove the upstream changelog doesn't sound like something they would insist on15:33
mordredzigo_: ok. well, just understand that I'm not going to fix bugs in any openstack project that are due to you as a downstream interacting with my output in ways that I've EXPLICITLY said are not supported15:33
mordredif you're ok with that, then I am ok with agreeing to disagree :)15:33
jd__dhellmann: flaper87: I wanted to say about that, that anyhow I got the feeling that's something the TC will have to take into consideration when voting for incubation ending15:33
zigo_fungi: You are right.15:33
*** lcestari_ has quit IRC15:33
dhellmannjd__: good point, so perhaps we should wait for that discussion to happen15:34
zigo_mordred: You wont add a -1 to a patch to the MANIFEST.in of horizon, will you?15:34
flaper87dhellmann: there are serious considerations going on but no serious work just yet. As I mentioned before, that's part of our plan before going into graduation but again, although it wasn't a strong requirement during the incubation voting (AFAIR) we've marked that blueprint as essential15:34
jd__dhellmann: hm I'm not sure it's going to happen soon15:34
zigo_mordred: I can change my way of packaging things later on, but right now, it's a bit late for me before Havana anyway.15:34
dhellmannjd__: oh, right, that's savanah that's being discussed tomorrow, I was confused15:34
jd__mordred: zigo_: taking a step back, I still think there's a little bug with pbr having different behaviour wrt .git/MANIFEST.in15:35
mordredzigo_: fair.15:35
mordredjd__: I still haven't seen a usecase that describes one of those15:35
mordredjd__: _except_ where the .git repo isn't present15:35
fungizigo_: other requests which "upstream" might honor to make our released tarballs more usable downstream include carrying an xz-compressed version, and possibly finding ways to summarize the changelog to not be quite to massive15:35
fungier, quite SO massive15:36
mordredjd__: and in those cases, it's not pbr doing it, it's trying to operate in a context where there is no git metadata and where we don't maintain support for that in MANIFEST.in15:36
pabelangerFWIW: There is a best practices for repacking source tarballs: http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-origtargz Might help close the gap15:36
jd__mordred: what about "I use pbr. I don't want to include in my sdist tarball everything that is in my git, so I wrote a MANIFEST.in. pbr doesn't take it into account"15:36
dhellmannflaper87: well, I've only voted -1, so if mordred removes the freeze on requirements changes then my vote can be overridden. if we need to discuss it more, maybe the mailing list would be a better venue.15:36
mordredjd__: if you can give me a test case where pbr is ignoring a MANIFEST.in that exists, I will accept it15:36
pabelangerEG: You should upload packages with a pristine source tarball if possible, but there are various reasons why it might not be possible. This is the case if upstream does not distribute the source as gzipped tar at all, or if upstream's tarball contains non-DFSG-free material that you must remove before uploading.15:36
mordredjd__: I do not believe that is what has been descirbed thusfar today15:36
mordredflaper87, dhellmann: crap. too many conversations... lemme try to read scrollback on this one15:37
dhellmannflaper87: and I'll subscribe to that blueprint, too15:37
dhellmannmordred: the marconi folks need some requirements updated, but we were under a freeze so I voted -1 on 2 (and -1 for a diff. reason on a third)15:37
flaper87dhellmann: cool, thanks15:38
jd__mordred: hm... pbr tried to include my whole $HOME because it (or a git command) looked recursively to find a .git and it ended up finding /home/jd/.git … so it ignored MANIFEST.in and blowed up (I've a big home ya know)15:38
mordredflaper87: oy. I do not like the response from kgriff on that patch15:38
mordredjd__: ok. so, that sounds like a bug I could potentially investigate fixing. finding a .git dir outside of the actual current source tree is certainly a bug15:40
*** bnemec has quit IRC15:41
*** markmc has quit IRC15:41
jd__mordred: yep -- though bypassing it with SKIP_GIT_SDIST=1 solved the problem for that time15:41
*** bnemec has joined #openstack-infra15:41
sdaguezul: where do you want to me to file the bug report?15:41
zulsdague:  at your convience15:42
sdaguezul: no, under what project15:42
*** olaph has quit IRC15:42
sdaguethis is basically the crux of the issue15:42
sdaguecloud-archive-test:~> ldd /usr/bin/qemu-system-x86_64 | grep librbd15:42
sdaguelibrbd.so.1 => /usr/lib/librbd.so.1 (0x00007f09c32bf000)15:42
zulubuntu-cloud-archvie15:42
mordredflaper87: so, I need to read these reviews a little more closely, but I really do need to close the loop with you guys on this pecan/falcon thing15:42
zulneed to reboot15:43
*** zul has quit IRC15:43
mordredflaper87: adding new projects to openstack that are in active rebellion against overall openstack design choices is not something we can afford to do15:43
flaper87mordred: I understand. What I can say is that we're seriously investigating the migration to Pecan and both implementations will be tested and benchmarked. Again, there's nothing against using Pecan instead of Falcon but my understanding from our incubation meeting is that priorities were around the storage backends, integration with other OpenStack projects and the client15:43
*** yaguang has joined #openstack-infra15:44
mordredflaper87: it's the way it's worded in that blueprint that has me concerned15:44
mordredbecause it sounds like "we'll seriously look at it because we were asked to, but we're going to test to see how good pecan is at being falcon, and if it's not as good at being falcon as falcon is, then we're going to decide to not switch"15:45
openstackgerritAntoine Musso proposed a change to openstack-infra/jenkins-job-builder: doc: fix up strict errors  https://review.openstack.org/4786115:45
flaper87mordred: I wouldn't say Marconi is in active rebellion against openstack design choices. We've been integrating the project since its early stages. We've been using all tools and respecting all OpenStack standards and tools15:45
mordredflaper87: well, except for falcon15:45
flaper87mordred: when we started using falcon, the pecan discussion wasn't even started. We couldn't afford migrating the whole thing at that moment15:46
flaper87that's the only reason why we kept it15:46
mordredgrumble15:47
flaper87anyway, don't get me wrong here.15:47
*** zul has joined #openstack-infra15:48
*** mrodden1 has quit IRC15:49
mordredflaper87: yeah, same here. I basically just want to make sure we don't dig ourselves more of a hole15:49
sdaguezul: https://bugs.launchpad.net/cloud-archive/+bug/122925515:49
uvirtbotLaunchpad bug 1229255 in cloud-archive "qemu-system-x86_64 is linked to librbd.so so will not exec unless ceph is installed" [Undecided,New]15:49
zulsdague:  cool ill have a look15:49
openstackgerritAntoine Musso proposed a change to openstack-infra/jenkins-job-builder: stop ignoring doc/source/*  https://review.openstack.org/4786215:50
flaper87mordred: totally agree, whatever is better for the whole project and the community.15:50
sdaguezul: also it looks like n-cpu didn't crash, it's deadlocked with that version of libvirt15:51
zulsdague: im going to try to reproduce this in the afternoon15:51
*** kgriffs has joined #openstack-infra15:51
zulhow did you create the deadlock?15:51
flaper87mordred: it would be really cool to let the other 2 patches land for now15:52
sdaguerunning tempest on a 4 core machine15:52
flaper87we can discuss the falcon one a bit further15:52
sdaguetox -e full15:52
kgriffshey guys15:52
sdaguehas 4 simultaneous processes hitting things15:52
mordredkgriffs: you missed all the fun!15:54
*** danger_fo_away is now known as danger_fo15:54
kgriffsheh15:54
kgriffsso I heard15:54
*** olaph has joined #openstack-infra15:55
mordredkgriffs: tl;dr - falcon stuff - ongoing dev in falcon, concern that will make it harder to be able to migrate off, manifesting in conversation around bumping the falcon req in openstack/requirements15:55
kgriffsok15:56
*** dprince has quit IRC15:56
mordredkgriffs: with the main concern (ironically) that I don't want pecan v. falcon to become a bigger deal or even continue to be a deal15:56
kgriffsyes, I agree15:56
mordredit's possible that this conversation may indicate the opposite of that :)15:56
*** zehicle has joined #openstack-infra15:59
*** rpodolyaka has left #openstack-infra15:59
mordredkgriffs: but the underlying concern I've got is in revisiting everything every time we add a new project. pecan v. falcon itself on its merits I actually care very little about. what I care more about is that we made a consolidated project direction decisions last summit, and now it seems like there is a change we're going to reopen that line of thought15:59
mordredand long term, having the same thing over and over and over again is just not scalable16:00
*** mrodden has joined #openstack-infra16:00
mordredso as long as we're on the same page about _that_, I can shut up for a while16:00
*** matty_dubs is now known as matty_dubs|lunch16:02
zigo_mordred: & fungi: https://bugs.launchpad.net/horizon/+bug/1229264 (reported the fact that horizon trying to write into /usr/share/openstack-dashboard/openstack_dashboard/local/)16:03
uvirtbotLaunchpad bug 1229264 in horizon "Horizon tries to write in /usr/share/openstack-dashboard/openstack_dashboard/local" [Undecided,New]16:03
zigo_Ooops! :)16:03
zigo_uvirtbot: Thanks!16:03
uvirtbotzigo_: Error: "Thanks!" is not a valid command.16:03
mgagnehaha16:03
fungizigo_: i agree that's ugly16:04
zigo_I already have a symlink to local_settings.py in /etc ...16:04
zigo_:)16:04
kgriffsmordred: I don't think anyone is arguing that it was silly to continue maintaining the OpenStack WSGI framework.16:05
fungizigo_: probably some examples from other existing django-based webapps packaged for debian might help16:05
sdaguefungi: https://bugs.launchpad.net/cloud-archive/+bug/122897716:05
uvirtbotLaunchpad bug 1228977 in nova "n-cpu seems to crash when running with libvirt 1.0.6 from ubuntu cloud archive" [High,New]16:05
fungizigo_: though the horizon peeps may have this worked out already and just slipped up in that one situation16:05
sdaguelooks like a hard lockup actually16:05
fungisdague: awesome!16:05
sdaguezul: that's for you as well, I put it on cloud-archive as well16:06
*** hashar is now known as hasharCal16:06
*** hasharCal is now known as hasharCall16:06
zulack16:06
*** zehicle has quit IRC16:06
zigo_fungi: There's not much more django apps packaged in Debian. apt-rdepends -r python-django gives me: bcfg2-web, dicoweb, djagios, graphite-web, insanity-web, mumble-django, and it seems to be it.16:08
fungizigo_: you're on the cutting edge then (try not to get cut too badly!)16:09
zigo_:)16:09
zigo_I actually am going to bed.16:09
zigo_:)16:09
zigo_(midnight over here...)16:09
*** flaper87 is now known as flaper87|afk16:11
mordredkgriffs: oh gosh no. I'm certain no one is arguing that. I'm more concerned that we're going to end up down another rathole of two different frameworks with each side claiming "it's too much work for us to switch"16:12
*** UtahDave has joined #openstack-infra16:13
mordredzigo_: heh. come on - midnight is when it's time to get up and go drinking!16:13
kgriffsmordred: sounds like this has happened before?16:14
*** dims has quit IRC16:14
mordredkgriffs: some times I feel like the only thing I do in openstack is mediate between diametrically opposed sets of people who want to use different libraries16:14
kgriffsheh16:15
zigo_mordred: Probably when we'll be in HK. There's boats to Macao directly from the venue, it's a *must do* ! :)16:15
mordredkgriffs: if you want some fun reading - go search the mailing list archives for the initial eventlet vs. twisted conversation16:15
mordredzigo_: woot!16:15
kgriffsI totally understand the benefits from consolidating libraries16:15
*** cthulhup_ has joined #openstack-infra16:16
*** wchrisj has joined #openstack-infra16:16
kgriffsthat being said, in my experience it is virtually impossible to consolidate down to 1 library/thing in any organization that is much bigger than a startup.16:16
hub_capmordred: thats just mean... the eventlet/twisted convo.. dont do it kgriffs16:16
kgriffsthe best you can do is minimize the chaos16:16
kgriffsbasically, not all projects are the same, and one-size-fits all doesn't always fit16:17
kgriffsthat being said, the reasons for using different things or rolling your own are often more based on emotion than data16:17
*** pcrews_ has joined #openstack-infra16:19
*** boris-42 has quit IRC16:19
*** zehicle has joined #openstack-infra16:20
*** pcrews has quit IRC16:20
mordredindeed to the emotion bit16:21
mordredthe thing is, we're SO big that if we let thigns proliferate at a natural rate, things would quickly become crazy16:21
mordredwhich means I get to be the person who is frustrating to people a bunch16:21
kgriffsyeah16:21
kgriffsyou have to constantly fight the entropy. :p16:22
mordredyup16:22
mordredI'm fearing that this particular one is going to die a heat-death of emotion, since we have the author of both frameworks involved, which means someone is going to be sad eventually16:22
mordredand I don't like when people are sad16:23
jd__NIH syndrom strikes again16:23
mordredotoh, 1200 devs16:23
kgriffsheh16:23
mordredso, sometimes people are sad16:24
kgriffsTBH, I'm more interested in *what* is right, not *who* is right16:24
mordredyup16:24
kgriffsFalcon was started because nothing existed that does what it does16:24
jd__"When I get sad, I stop being sad and be awesome instead."16:24
jd__True story.16:24
kgriffsFWIW, in the case of Marconi, the Falcon-based WSGI driver is already done, and we have been planning on writing a Pecan one before graduation, so at least you don't have to worry about the "it's too hard to switch" argument coming from my guys16:24
jeblairjd__: do you accomplish that by drinking? ;)16:25
kgriffsif Pecan is awesome and fast enough, we will totally use it16:25
mordredgreat16:25
clarkbmorning16:25
mordredclarkb: don't read the scrollback16:25
mordredclarkb: you will go blind16:25
zaromorning16:25
kgriffsbut if it isn't, then we need to decide to either fix Pecan or allow 3 frameworks in OpenStack16:25
jd__jeblair: I've heard that can help :-)16:25
kgriffs(Pecan, Falcon, swob)16:25
clarkbmordred: but now I must out of curiousity16:25
kgriffsor something like that16:25
mordredkgriffs: indeed. well, fwiw, pecan lives in stackforge now, so fixing should be something openstack can accomplish16:26
mordredbut, you know, that bridge, when we get there16:26
kgriffsyep16:26
mordredI just wanted to be clear the the pecan work was a real thing before approving updates to falcon things in requirements (the conversations have always been slightly vague and stuff)16:27
kgriffsyes, it is a real thing and is on our list of "must do" prior to graduation16:28
kgriffsrough list here: https://wiki.openstack.org/wiki/Marconi/Incubation/Graduation#To_Do16:28
*** yidclare has joined #openstack-infra16:28
mordredawesome16:28
*** yidclare has left #openstack-infra16:29
mordredso - for your current three reqs patches, we _are_ in requirements freeze - how urgent are there/should we look at FFE for them? or can they wait until icehouse opens?16:29
*** julim has quit IRC16:29
*** afazekas has quit IRC16:37
*** reed has quit IRC16:37
kgriffsmordred: tbh, I don't think we need pylru at all (need to benchmark one more time to be sure)16:38
*** reed has joined #openstack-infra16:38
kgriffsfalcon 0.1.7 we can wait on16:39
kgriffsmmh3 is the tricksy one16:39
*** pblaho has quit IRC16:40
*** adam_g has quit IRC16:40
kgriffswe have a patch that needs some kind of stable hash that won't change between python versions or anything, as is reasonably fast.16:40
kgriffslet me noodle on that a bit - may be an alternative.16:40
mordredkgriffs: we _can_ do a freeze exception - especially since it's only for a thing that isn't part of havanna16:40
mordredit just requires slightly more chatting and stuff16:41
mordreddhellmann, Alex_Gaynor: ^^ thoughts?16:41
Alex_Gaynormordred: what's the question?16:41
*** reed has quit IRC16:41
mordredpossible FFE for mmh3 for marconi16:41
*** reed has joined #openstack-infra16:42
*** julim has joined #openstack-infra16:42
Alex_Gaynorkgriffs: was just using sha considewred?16:43
*** yaguang has quit IRC16:43
*** zehicle has quit IRC16:43
*** kpavel has quit IRC16:43
kgriffsyes, but it is too slow16:43
kgriffsactually, we used MD5 which is faster than SHA16:43
*** adam_g has joined #openstack-infra16:43
*** adam_g has quit IRC16:43
*** adam_g has joined #openstack-infra16:43
kgriffsbut still, dropped our req/sec quite a bit in benchmarking16:43
Alex_Gaynorkgriffs: what about siphash :D16:44
kgriffs(Marconi is a data API, and we have high-throughput reqs)16:44
* kgriffs looking16:44
Alex_Gaynorkgriffs: (Sorry I'm thinking about the FFE question, just spitballing as I do)16:44
dhellmannmordred: I'm ok with adding mmh3, since nothing else uses that. It doesn't bring in any other dependency conflicts, does it?16:44
Alex_Gaynornot that siphash is in the stdlib16:44
*** wchrisj has quit IRC16:45
dhellmannmordred: although I'll defer to Alex_Gaynor's superior knowledge of alternatives. :-)16:45
mordreddhellmann: no. it's clean - no other depends16:45
mordredclaims 2 and 3 support (which I suppose is the point)16:45
mordredthis:16:45
mordred    'License :: Public Domain',16:45
mordredis a little funny, but should be fine16:46
kgriffsit is slow on PyPy but I plan to fix that. ;)16:46
kgriffs(needs some cffi love)16:46
Alex_GaynorBut it does work on pypy?16:46
kgriffsis crc32 already in the deps?16:46
kgriffsyes, it works16:46
kgriffs(mmh3 works on pypy)16:46
*** jcoufal has quit IRC16:47
kgriffs(doesn't look like crc32 is in there)16:47
Alex_Gaynorcrc32 is in the stdlib16:47
Alex_Gaynorbinascii module IIRC16:47
kgriffsoh, right. duh16:47
dhellmannjeblair: how hard would it be to add checkboxes to the requirements project in gerrit for things like "supports python3" and "supports pypy"?16:48
kgriffsi suppose we could maybe use that for our particular need (crc32)16:48
jeblairdhellmann: very easy if we upgrade to gerrit 2.616:48
* kgriffs keeps forgetting how extensive python stdlib is16:48
* dhellmann hopes that's a "when" rather than an "if" ;-)16:48
*** dcramer_ has quit IRC16:49
kgriffsguys, let me look at a couple alternatives to mmh3 and get back to you in a bit16:49
jeblairdhellmann: zaro is working on getting some stuff upstream so we can support WIP; otherwise we would need to ditch WIP because we don't have the manpower to maintain a gerrit fork.16:49
dhellmannjeblair: ah, right, that's come up before16:49
dhellmannkgriffs: post what you find to the review for mmh3 if you still need it, and I'll +216:50
kgriffscool, sounds like a plan16:50
mordredzaro: what's the latest on that? still blocked on "nice patch, but could you also drastically expand the scope of the patch?"16:52
mordredhasharCall: who's your gerrit core dude again?16:52
* cppcabrera would love to see "supports python 3", "supports pypy" checkboxes in gerrit16:52
hasharCallmordred: ^d16:52
clarkbmordred: re sqlalchemy funness, we should reduce the restriction on the upper bound, do whatever fixing is necessary then move the lower bound (thinking back to keystoneclient problems earlier this cycle)16:52
hasharCallmordred: Chad "^d" Horohoe.16:52
*** svarnau has joined #openstack-infra16:52
mordredhasharCall: thanks16:52
hasharCallmordred: if not available you can ask for qchris who is Europe based, though he is no more working on Gerrit.16:53
*** hemnafk is now known as hemna16:54
mordredzomg.16:54
mdennyI'm setting up havana h3 deployment on 4 nodes Ubuntu 12.04.3 - Controller node, Network node, 2 Compute nodes16:54
mordredthe upstream gerrit people have added "Diffy Cuckoo"16:54
mdennyController node has ntp, Mysql, keystone, RabbitMQ, Glance and Neutron working as expected.16:55
mordredmdenny: almost certainly the wrong channel16:55
mdennyapt-get install -y novnc  novnc : Depends: libjs-swfobject but it is not installable16:55
zaromordred, jeblair, dhellmann : patch is here.. https://gerrit-review.googlesource.com/#/c/48254/16:55
mordredmdenny: this is for people running the openstack developer infrastructure - you probably want #openstack or possibly #openstack-dev16:55
mdennymordred: Thanks16:55
*** SergeyLukjanov has quit IRC16:56
zaromordred, jeblair, dhellmann : i believe i've got what they want this time.  mfick says he will take a look at it today.16:57
*** zehicle has joined #openstack-infra16:57
mordredzaro: w00t!16:58
jeblairzaro: excellent; it seems like there was little response to your RFC thread which was one of the outcomes that mfick anticipated16:58
mordredzaro: that would be the best thing that's ever happened16:58
*** pcrews_ has quit IRC16:58
jeblairmeaning, it seems no one feels strongly or objects to applying it to those permissions16:59
*** pcrews_ has joined #openstack-infra16:59
zaroit became a larger change than i expected.  i've gone thru testing it and it seems to be working pretty well.17:00
jeblairooh, i like the shaded vote box... "User cannot vote in this category".  that will be nice for identifying core people17:00
jeblairmordred: ^17:00
*** matty_dubs|lunch is now known as matty_dubs17:02
*** zehicle has quit IRC17:03
mordredjeblair: ++17:04
openstackgerritJay Pipes proposed a change to openstack-infra/config: Enable gate on OpenStack Chef Repository  https://review.openstack.org/4788017:04
*** KurtMartin has joined #openstack-infra17:04
mordredjeblair: I'm happy for them that they have automatic verification of changes. I'm a little sad that they wrote their own thing17:05
*** hasharCall has quit IRC17:05
jeblairmordred: they are insane17:06
mordredjeblair: the new projects list page is nice too17:06
mordredjeblair: https://gerrit-review.googlesource.com/#/admin/projects/plugins/avatars/external17:06
zaromordred: i don't think it includes tests though.17:07
*** kgriffs is now known as kgriffs_afk17:11
*** mrmartin has joined #openstack-infra17:13
*** BobBall is now known as BobBall_Away17:14
mordredhttps://gerrit.googlesource.com/plugins%2Frename-project17:14
mordredI wonder if that would allow us to rename on a live server?17:14
*** jerryz has joined #openstack-infra17:15
mordredwell, if it existed, that would be even better17:15
mordreddhellmann: there is a tuskar thread on openstack-dev you might be interested in17:18
hub_capmordred: hey dude im tryign to do this refactoring for ya on the client, and i got things pretty far, but im hitting a wonderful wall of reviews... so im going ot have to play people-review-tag for a while to get some new oslo / keystoneclient things done17:21
*** gyee has joined #openstack-infra17:21
*** markmcclain1 has joined #openstack-infra17:21
*** markmcclain has quit IRC17:22
jerryzjeblair: ping17:22
jeblairjerryz: pong17:22
*** lcestari_ has joined #openstack-infra17:23
jerryzjeblair: i am switching to nodepool from d-g, but when launching a instance, the nodepool server can not access it.17:23
jerryzjeblair: the authorized_keys does not have server's public key17:23
jeblairjerryz: in our puppet modules, we configure the ssh public key for the jenkins user17:24
mordredhub_cap: cool. let me know if you want me to help!17:24
jeblairjerryz: so for us the process is: nodepool spins up a server to build an image from, logs in with the key it creates, runs puppet which installs the jenkins ssh key, then saves the image17:25
hub_caproger mordred. its more of a 3 people w/ 3 different ideas thing. i might get a ML chain started and ask you to thwack people17:25
mordredhub_cap: point me at the reviews?17:25
jeblairjerryz: then nodepool spins up new servers from that image and uses the jenkins ssh key to log into them (what key it uses for that is configured in nodepool.yaml)17:25
*** pcrews_ has quit IRC17:25
jeblairjerryz: so to summarize the missing documentation:17:26
hub_capwhats the general stance on stackforge projects? should we not integrate them until they go incubated, or integrated even? im looking specifically @ designate for dns support in trove17:26
jerryzmy problem is when creating the snap_image, the key is not injected to my image17:26
jeblairjerryz: you should run _something_ in the image creation scripts that installs a known ssh key, and then you should configure nodepool.yaml to use that ssh key for the login check it does when it launches a server17:26
mordredhub_cap: you should not integrate with them in such a way that you would need to start including them in your trunk gating17:27
mordredhub_cap: including experimental/optional support for them is fine17:27
jerryzyou mean i should copy and paste the public key manually while the image is being created17:27
hub_cap<3 as always mordred17:27
mordredjerryz: yes.17:28
*** pcrews_ has joined #openstack-infra17:28
jeblairjerryz: no, there's a step where it runs some scripts before creating the snap image; so you should do something there to create the key17:28
jeblairmordred: yes?  manually?17:28
mordredwell, not MANUALLY - I meant in the script17:28
* mordred butts out of the conversation - jeblair is doing fine17:28
jeblairjerryz: it might help to know some context -- do you want images that are just like ours (with our puppet config, etc), or are you using it for something else?17:29
jerryzjeblair: yes17:30
*** sarob has joined #openstack-infra17:30
jerryzjeblair: only difference is my nodepool server is not manged by puppet17:30
jeblairjerryz: ok, so if you are using our nodepool setup scripts (the ones at http://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/nodepool/scripts )17:31
*** SergeyLukjanov has joined #openstack-infra17:31
jeblairjerryz: then you can just set the "NODEPOOL_SSH_KEY" environment variable to contain the public key when you run nodepool17:31
jerryzi have already copied those scripts to the location where nodepool.yaml specifies17:31
jeblairjerryz: it does the same thing that the devstack gate ssh key variable used to do....17:31
jerryzjeblair: that is what i missed17:32
jeblairjerryz: where it substitutes your public key for jenkins17:32
jeblairjerryz: then configure nodepool.yaml to use the private key, and you should be good to go17:32
fungiahh, sorry i didn't think to suggest overriding it with that the other night jerryz17:32
jeblairjerryz: you can look at http://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/nodepool/scripts/prepare_node.sh17:32
jeblairfungi, jerryz: nodepool docs are high on my list, sorry i'm a bit behind17:32
jeblairbut the general mechanism is that nodepool will pass through any NODEPOOL_* environment variables to the scripts17:33
jeblairso you can pass anything else you need to the scripts that way as well17:33
jeblair(that's also what i use to test nodepool locally)17:34
*** julim has quit IRC17:35
jerryzthanks17:35
jeblairjerryz: you're welcome!17:36
*** ruhe has quit IRC17:38
*** kgriffs_afk is now known as kgriffs17:41
*** pcrews_ has quit IRC17:42
*** dprince has joined #openstack-infra17:46
clarkbthe electrical outlets in my cube work again \o/17:49
mordredw00t!17:50
*** boris-42 has joined #openstack-infra17:50
mgagneclarkb: you can now plug back that coffee maker :D17:50
*** jerryz_ has joined #openstack-infra17:50
*** jerryz has quit IRC17:50
*** nicedice has joined #openstack-infra17:51
*** pcrews_ has joined #openstack-infra17:54
*** kgriffs is now known as kgriffs_afk17:55
*** jerryz_ has quit IRC17:55
fungiand the space heater17:56
hub_capclarkb: did u see my email to u about ovz+iscisd ?17:56
*** ArxCruz has quit IRC17:56
*** Ryan_Lane has joined #openstack-infra17:56
*** moted has quit IRC17:57
*** moted has joined #openstack-infra17:58
clarkbhub_cap: not yet17:59
clarkbhub_cap: oh actually yes17:59
hub_capyou will get a kick out of it17:59
clarkbthat email I loled17:59
*** morganfainberg has quit IRC17:59
clarkbhub_cap: mordred stevebaker pleia2 https://etherpad.openstack.org/testing-heat-trove-with-dib18:00
hub_capbut i have afeeling, if we file a bug, it will get fixed18:00
hub_capand fast18:00
*** sarob has quit IRC18:00
clarkbthat is from ^ my whiteboard18:00
pleia2clarkb: thanks18:00
hub_capyes thx18:00
*** mestery has quit IRC18:01
zaromordred: can i get a review from you for this one since you tried to do the same thing?  https://gerrit-review.googlesource.com/#/c/48254/18:01
zaromordred: oops meant this one.. https://review.openstack.org/#/c/45329/18:01
*** kpavel has joined #openstack-infra18:01
*** jerryz has joined #openstack-infra18:01
*** morganfainberg has joined #openstack-infra18:02
*** ruhe has joined #openstack-infra18:03
*** ArxCruz has joined #openstack-infra18:03
*** ruhe has quit IRC18:03
openstackgerritA change was merged to openstack-infra/jenkins-job-builder: stop ignoring doc/source/*  https://review.openstack.org/4786218:05
*** fbo_away is now known as fbo18:06
*** morganfainberg has quit IRC18:06
*** morganfainberg has joined #openstack-infra18:07
*** morganfainberg has quit IRC18:07
*** mestery has joined #openstack-infra18:08
*** morganfainberg has joined #openstack-infra18:08
clarkbmordred: have you sorted out why some of your tox.ini changes for tox 1.6 seem to hate the setup.py develop stuff?18:14
clarkbjeblair: fungi mordred https://review.openstack.org/#/c/47393/ I think we should merge that asap to avoid conflicts18:16
clarkbalso possibly fix the comment in tthere about global requirements18:16
hub_capmordred: and co, what ever came of the "vote thru gerrit" stuff ?18:17
clarkbhub_cap: its up and should be useable18:17
hub_capWHAT!?!? i wanna test it18:17
hub_capi just did a #fakevote in my channel18:17
clarkboh I don't know if it is ready for general consumption18:17
hub_capand ya it didnt go over too well.. is there a rtfm tutorial on it clarkb ?18:17
clarkbI think it was created for the TC18:17
hub_capawwwwwwww18:17
*** melwitt has joined #openstack-infra18:18
hub_capbuild me up just to break me down clarkb18:18
clarkbhub_cap: meetbot has a vote mechanism for in meeting votes18:18
hub_capyes then i have to wait for my meeting... :(18:18
jeblairhub_cap: you should wait for your meeting, unless you're trying to subvert democracy.  :)18:18
hub_capshhhhh18:19
clarkbhub_cap: the basic idea is you have a project in gerrit that tracks proposals as gerrit changes, this way the TC can make proposals offline that everyone can think through and not make up their minds in an hour18:19
hub_capsee thats what i want, more of a offline vote process18:19
clarkbthen as positions are formed individuals can vote on the change, then if approved change is merged leaving a record of the decision18:19
hub_capso u know, if you arent in a meeting you can still vote :) (not to subvert democracy)18:19
jeblairhub_cap: lot's of people do it, you're in good company!  Nixon... Reagan... Bush... Bush... Obama... wow you're looking positively presedential.  :)18:20
* hub_cap puts a tie on18:20
clarkbbut I am not sure that works if you mulitplex many sets of decisions makers on a single project18:20
hub_capso do yall think thats something a ptl could use for a project vote?18:20
clarkbI think the process is sound, it may require more projects though18:21
clarkbjeblair: ^18:21
fungiclarkb: i'm good with merging 47393 now, as it's no longer saturday18:21
fungiotherwise, yes, rebase hell ensues18:22
fungiapproved18:22
clarkbfungi: cool and ty18:22
fungiwill keep an eye on the gate for a while after it merges18:22
jeblairhub_cap: so every change to a project is already a project vote; i think the innovation here is that the tc didn't have a code project it could do that with, now it does.18:22
clarkbfungi: awesome, there is another change in the queue that needs to be rechecked after that merges, I will recheck that change18:22
jeblairhub_cap: but i'm guessing you're talking about more long-ranging items where a change isn't ready or appropriate yet18:22
clarkbjeblair: good point18:22
hub_capjeblair: or something thats maybe not code related, at least in the short term (which i believe is a paraphrase of what you just said, ya?)18:23
jeblairhub_cap: but you could still do that with documentation patches, or something similar...18:23
fungiclarkb: yeah, there are several stacked behind it which need rechecks after it merges18:23
jeblairpatches to README, TODO files, etc...18:24
hub_capthats a good point jeblair18:24
*** kiranmurari has joined #openstack-infra18:24
jeblairhub_cap: the main thing i'd suggest is try not to be too different than other openstack projects... if you experiment with something like that, make sure people in meetings or mailing lists know about it -- so you don't subvert democracy.  :)18:24
*** dcramer_ has joined #openstack-infra18:24
clarkbfungi: merge conflict already :(18:24
fungipoop18:25
fungifixing18:25
clarkbfungi: can you correct that comment about global requirements as well18:25
jeblairhub_cap: (and if it's awesome, it may become standard for other projects)18:25
clarkbfungi: jeblair left it inline18:25
fungiwill do--missed it earlier18:25
kiranmurarikoolhead17: heyy...18:26
hub_capjeblair: and then people would like me!18:26
hub_capoh wait....18:26
hub_capthats probably not true18:26
hub_capill try to think of something that requires a changeset but is minimal overhead and experiment18:27
hub_capuse the tool i already got so to speak18:27
hub_captoo bad recording the vote result will result in a rebase / re-review lol18:28
openstackgerritA change was merged to openstack-infra/zuul: add forge author identity privilege to support pushing refs to gerrit  https://review.openstack.org/4723318:29
*** tstevenson has joined #openstack-infra18:29
clarkbhub_cap: ya, that is a possibility (I expect that may become an issue with the TC project depending on how things are recorded within git)18:30
openstackgerritAndreas Jaeger proposed a change to openstack-infra/config: Publish atom.xml for manuals  https://review.openstack.org/4789718:30
clarkbI suppose a different file could be used for each proposal there18:30
openstackgerritJames E. Blair proposed a change to openstack-infra/zuul: Fix NNFI bug with two failing changes at head  https://review.openstack.org/4789818:30
kiranmurarihello folks, i need to get a couple of posts removed from planet.openstack.org...18:31
jeblairclarkb, fungi, mordred: ^ that is a bug that I have seen in production; it could allow incorrectly tested changes to merge18:31
hub_capclarkb: thats what im going w/ right now (doc/votes/{some_proposal}18:31
clarkbjeblair: looking18:31
jeblairkiranmurari: i believe if you remove them from your feed they will be removed automatically18:32
kiranmurarii deleted them from our wordpress blog, but before that they got populated on planet and don't go away from planet18:32
jeblairkiranmurari: when did you remove?18:32
kiranmurarijeblair: thanks for the pointer... but its been almost 36 hrs that i deleted them from our wordpress... but they are still appearing on planet :(18:32
*** Ajaeger1 has joined #openstack-infra18:33
jeblairkiranmurari: which posts?18:33
kiranmurarijeblair: te title of both the posts is 'Summary: OpenStack India Day, 2013' and the author is 'kiranmurari'18:33
kiranmurarijeblair: therez been a slight goofup so had to delete them18:34
mrmartinfungi: hi18:37
fungimrmartin: hi there! what's next on the groups-dev agenda?18:37
mrmartincould you review my two patches: https://review.openstack.org/#/c/47838/ and https://review.openstack.org/#/c/47844/18:37
fungimrmartin: sure18:38
mrmartinone of them is updating drush to 6.0.0 from 5.9.0 and the other one repairs a bug that affects auto-site deployment18:38
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Fix pep8 errors in modules dir  https://review.openstack.org/4764418:38
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Remove launchpad_sync module  https://review.openstack.org/4764318:38
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Remove the now vestigal pyflakes tox env  https://review.openstack.org/4764118:38
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Remove pyflakes jobs  https://review.openstack.org/4739318:38
fungiclarkb: ^18:38
clarkbfungi: ty18:38
clarkbjeblair: zuul change reviewed. lgtm18:38
fungi(rebased and edited out that one offending comment)18:38
mrmartinit was checking a bad git file for recent commit hash18:38
* fungi is reading through jeblair's nnfi fix and then will take a look at the groups-dev fixes18:39
*** sarob has joined #openstack-infra18:39
mordredzomg. too much scrollback18:41
jeblairmordred: can you look at kiranmurari's question about planet?18:42
mordredlooking18:43
*** sarob has quit IRC18:44
kiranmurarijeblair: thx18:44
mordredkiranmurari, jeblair: planet does some caching, so it might not see the upstream deletions18:44
mordredI _believe_ we can just delete the planet cache which will cause the next run of planet to run uncached18:44
*** cody-somerville has joined #openstack-infra18:44
sdaguemordred: I believe you are correct on the cache front18:45
kiranmurarimordred: thatz what i expected... is it something like PlanetData18:45
jeblairmordred: ok.  is there a tunable that will make it cache less aggressively?18:45
openstackgerritA change was merged to openstack-infra/config: Remove pyflakes jobs  https://review.openstack.org/4739318:45
openstackgerritA change was merged to openstack-infra/zuul: Fix NNFI bug with two failing changes at head  https://review.openstack.org/4789818:45
*** kgriffs_afk is now known as kgriffs18:46
mordredfeed_timeout    = 2018:46
mordredbut I don't really konw what 20 means18:46
clarkbjeblair: fungi: I have not approved https://review.openstack.org/#/c/47636/ because it is semi process related and figured having more reviewers look at it could only help (the code looks fine)18:46
jeblairhttp://www.intertwingly.net/code/venus/docs/config.html says Number of seconds to wait for any given feed18:46
mordredkiranmurari: what's the url of your blog?18:47
sdaguejeblair: I think it's like recheckwatch, there really is no cache cleaning18:47
jeblairmordred, sdague: the current behavior seems broken; everything it needs to DTRT is in the http headers18:47
kiranmurarijeblair: http://www.openstackindia.wordpress.com18:47
jeblairsdague: recheckwatch cleans its cache.  :)18:47
sdagueok, fair :)18:47
kiranmurarimordred: link above18:47
mordredjeblair: agree18:47
mordredjeblair: cache_keep_entries might be interesting to us - although I agre with you re: http headers18:48
mordredah18:49
*** cthulhup_ has quit IRC18:49
mordredwe're not running the expunge command18:49
*** CaptTofu has quit IRC18:49
jeblairoh neat18:49
*** vipul is now known as vipul-away18:49
jeblairjog0, clarkb: i'm curious about https://review.openstack.org/#/c/47636/18:49
*** vipul-away is now known as vipul18:50
jeblairit references a bug that was marked wontfix for the ossa project, but not nova18:50
jeblairpresumably it was rechecked in the context of nova, not ossa since ossa does not have a project in gerrit18:50
*** ruhe has joined #openstack-infra18:51
fungithat's a good question... how should recheckwatch operate in the face of a bug with multiple bugtasks18:51
jeblairin nova, it is in progress and fix committed on two branches...18:51
jeblairso i'm not convinced that's a great example for that fix18:51
*** ruhe has quit IRC18:51
fungiit's a great example of something though18:51
jeblairfungi: yes :)18:52
jeblairi'll write something in the review18:52
fungifor example, someone might still recheck a grizzly change against that bug because it's not committed there yet18:52
fungiand the ossa project doesn't have any code repositories (not that recheckwatch knows anything about lp/git matchups)18:53
clarkbjeblair: thank you18:53
fungiso basically recheckwatch is somewhat ignorant of per-project and per-branch bugtasks in the context of a change which could be affected by a bug18:54
fungiand that seems like it would require a rather nontrivial solution18:54
clarkbfungi: it should be able to do a set union of all the states and if something not in the closed list is present treat the bug as open18:55
jeblairfungi: i'm not convinced it would be hard.  it _does_ know what projects have triggered rechecks, so it can examine bug states for all of those.18:55
clarkbjeblair: zaro: does https://review.openstack.org/#/c/46124/ need rebasing?18:56
kiranmurarimordred: jeblair: sdague: the cache can be expunged from admin interface or with 'python planet.py -x config.ini' - http://www.intertwingly.net/code/venus/docs/admin.html18:56
*** wchrisj has joined #openstack-infra18:56
fungiyeah, i guess a 100% solution would be hard but a 95% solution might not be too complicated18:56
*** morganfainberg has quit IRC18:57
*** morganfainberg has joined #openstack-infra18:57
kiranmurarimordred: jeblair: sdague: but i hope that wouldn't expunge the whole cache!!!18:58
dhellmannmordred: thanks for the pointer to the tuskar thread, I've responded18:59
jeblairfungi, clarkb: but that won't work because then we would start ignoring openstack-ci bugs19:00
mordredkiranmurari: it does not seem to do _anything_ helpful19:02
jeblairfungi, clarkb: I think the change is okay as-is.19:03
openstackgerritAndreas Jaeger proposed a change to openstack-infra/config: Use Jenkins templates for old manual jobs  https://review.openstack.org/4769119:03
*** hashar has joined #openstack-infra19:04
openstackgerritA change was merged to openstack-infra/config: Make "Won't Fix" a closed status in recheckwatch  https://review.openstack.org/4763619:05
*** sarob has joined #openstack-infra19:10
*** dmakogon_ has joined #openstack-infra19:11
sdaguehey, so 26 jobs are blowing up a lot on failed to clone issues - https://jenkins02.openstack.org/job/gate-nova-python26/3893/console19:12
sdagueany idea if rack fell over in a funny way19:12
sdaguethis is https://bugs.launchpad.net/openstack-ci/+bug/122935219:13
uvirtbotLaunchpad bug 1229352 in openstack-ci "intermitent failure of git clone from git.openstack.org" [Critical,In progress]19:13
sdagueand if you look at the gate right now, there are 2 py26 fails there that will cause resets that are that issue (I had reverified one earlier)19:14
fungisdague: corrupt workspaces i think, saw one last week19:15
sdagueok, 3 in a row in a couple of hours seems suspicous though19:15
fungiagreed19:15
fungisdague: which slaves besides centos6-6?19:16
sdagueonly centos 26 as far as I know19:16
sdague2013-09-23 19:08:57.131 | Building remotely on centos6-2 in workspace /home/jenkins/workspace/gate-nova-python2619:17
fungi-2 as well, okay19:17
sdague2013-09-23 18:54:46.663 | Building remotely on centos6-2 in workspace /home/jenkins/workspace/gate-nova-python2619:17
sdagueok, these are both on -219:17
fungithe one in your bug was -619:17
fungitaking them both out of service for abit19:18
sdagueok cool19:18
sdagueyeh, these are still in the gate19:18
fungibut yes if i try to remote update in the workspace for that job on -6 the remote does hang up on me19:18
sdagueI was just looking before I flushed a bunch of code to figure out how backed up things are19:19
fungiit *is* possible for a change to foul up the .git directory in a workspace such that we can't gerrit-git-prep any longer, though not sure yet if that's what's happened19:20
*** ArxCruz has quit IRC19:21
*** ArxCruz has joined #openstack-infra19:22
*** ArxCruz has quit IRC19:22
*** tvb has quit IRC19:27
*** tvb has joined #openstack-infra19:28
fungii saved a copy of the broken workspace from -8 last week and can compare to it as well19:28
*** tvb is now known as Guest4853619:28
fungii'm starting to wonder if gerrit-git-prep shouldn't do a git gc before git remote update19:32
*** sarob has quit IRC19:34
fungiso far on each occurrence of these i've seen, git fsck reports one or more dangling commits which git gc takes care of and after that git remote update works fine19:35
fungithough it's entirely possible the dangling commits reported by fsck are unrelated and some other side effect of te gc is what's getting it working again19:36
sdaguefungi: ok, -5 is bad now too19:39
sdague2013-09-23 19:33:18.964 | Building remotely on centos6-5 in workspace /home/jenkins/workspace/gate-nova-python2619:39
sdaguethat failed in the gate19:39
fungifixing19:44
mordredfungi: maybe if ! `git remote update`; then git gc ; git remote upate ; fi  ?19:46
fungimordred: sure, that might make snese19:47
fungisense too19:47
*** yolanda has quit IRC19:48
sdagueyeh, -5's killed 2 gate changes atm19:49
*** ruhe has joined #openstack-infra19:52
mroddenso ... i must have missed something ... is Tuskar the new Ironic or is it the new Tripleo?19:52
jeblairthis is really helpful for exercising nnfi19:52
jeblairit's like chaos monkey for zuul19:53
*** dmakogon__ has joined #openstack-infra19:53
*** dmakogon_ has quit IRC19:53
*** dmakogon__ has quit IRC19:53
*** dmakogon_ has joined #openstack-infra19:53
SpamapSwhat is the session store for gerrit? I've had to re-sign-in quite a few times today.19:54
*** schwicht has joined #openstack-infra19:54
sdaguejeblair: so is nnfi actually happening?19:54
sdaguethe UI just not updating for it/19:54
sdague?19:54
jeblairSpamapS: any chance you had multiple tabs open?  try closing them all and starting over19:54
*** Guest48536 is now known as tvb19:55
*** tvb has joined #openstack-infra19:55
SpamapSjeblair: yeah I always have quite a few open19:55
jeblairsdague: yes, nnfi is in production; the change to make it apparent on the status screen is in review.  i'm fixing bugs with both19:55
sdaguejeblair: cool19:55
fungijeblair: our entire developer base is like chaos monkey for all of our infrastructure19:55
sdagueheh19:55
SpamapSjeblair: is there some server affinity magic going on?19:55
sdagueyeh, well the gate's good and busy today as well. Trying to help clear the boards on some easy stuff19:56
jeblairSpamapS: no -- google javascript magic19:56
jog0mordred: http://docs-draft.openstack.org/26/47226/5/check/gate-hacking-docs/9610239/doc/build/html/ nice!19:56
jeblairSpamapS: if you have a tab with an old session around, it will invalidate a newer session19:56
jeblairSpamapS: so if you sign in, you need to not use any tabs that were opened during an older session19:56
jeblairSpamapS: (but openening new tabs with your new session is fine)19:57
SpamapSjeblair: weird19:57
jeblairSpamapS: isn't GWT great?19:57
mordredjog0: sexy right?19:57
mordredSpamapS: Java! It's for winners!19:58
jog0mordred: very19:58
mordredjog0: I just did the same thing for tripleo-incubator19:58
mordredspeaking of ...19:58
jog0the formatting is really nice good job to whoever did that one19:58
mordredjeblair: for people who have been relying on github's md/rst rendering feature, I've been going through and moving the files into sphinx trees19:58
mordredjeblair: which, rather than adding rst/md render support to cgit, I think is actually the right-er answer19:59
mordredjog0: that's using dhellmann's oslo.sphinx thing19:59
jog0dhellmann: ^ great job19:59
clarkbsorry stepped away for lunch19:59
dhellmannjog0: I just put our theme in a library, no big deal. :-)20:00
*** sarob has joined #openstack-infra20:00
fungi"librarification: it's a big deal"20:01
dhellmannfungi: I think that should be Oslo's motto :-)20:02
*** fbo is now known as fbo_away20:02
clarkbjeblair: I think https://review.openstack.org/#/c/46124/ needs a rebase then we can push it through20:02
jog0dhellmann: ++20:03
fungiall the projects need pithy mottoes20:04
dhellmann& t-shirts20:04
clarkbif only you could print moving gifs on tshirts20:05
fungimordred: i agree--that was actually my feeling on the cgit autorendering proposal. i'm in favor of contextual syntax highlighting, but rendering is really best published somewhere20:05
dhellmannclarkb: the fiber optics don't do well in the washing machine20:05
mtreinishjog0: about https://review.openstack.org/#/c/47491/ I think to use tox to run flake8 as a gating job we need a setup.py(and other changes to tox.ini) does that mean it's time to use cookiecutter?20:06
jeblairmordred, sdague: the current nnfi visualizer i'm working on doesn't handle the current status because there's a change with three items directly behind it.  iow, zuul is creating more complex trees than i anticipated.20:06
jog0mtreinish: you read my mind20:06
clarkbmtreinish: correct and yes. jog0 mentioned cookiecuttering elasticRecheck for these reasons and to make it setup.py installable because that will help deployment20:06
jog0was about to do that unles you want to go20:06
mtreinishjog0: no you get the honors20:06
*** rockyg has joined #openstack-infra20:06
openstackgerritA change was merged to openstack-dev/hacking: Move the hacking guidelines to sphinx docs  https://review.openstack.org/4722620:06
jog0will do it in a but20:07
jeblairmordred, sdague: (that can happen with some kinds of failing changes)20:07
jog0bit*20:07
*** julim has joined #openstack-infra20:08
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Garbage collect Git repos in gerrit-git-prep  https://review.openstack.org/4791520:09
fungisdague: mordred: ^ maybe like that20:09
clarkbfungi: is git having a hard time dealing with lots of unreachable commits?20:10
fungiclarkb: it's entirely possible20:10
mtreinishjog0: ok I do have the update for 47491 ready that adds the pep8 job to be gating on the project. I can push that out20:10
jog0go for it20:10
fungiclarkb: though the places i've seen this, fsck generally only mentions a handful of dangling commits20:10
fungiclarkb: and seems to just be nova+centos620:11
clarkbinteresting20:11
clarkbnova is a large repo and centos6 comes with old git20:11
clarkbnova may be large/special enough to tickle bugs in that old git (sounds familiar)20:12
fungiyep. i have four example workspaces (so far) if you want to play around with them20:12
fungiall exhibiting basically the same behavior with differing dangling commits reported by fsck and all fixed by gc20:12
fungiand i tested that specific conditional block on one as well, just for completeness, before submitting for review20:13
*** vipul is now known as vipul-away20:13
*** vipul-away is now known as vipul20:13
clarkbfungi: our change looks good to jeblair and I. I didn't +approve it because it hasn't been through check tests first, but g-g-p isn't check tested and the zuul queues are a bit long irght now20:13
fungiyeah20:14
openstackgerritMatthew Treinish proposed a change to openstack-infra/config: Add elastic-recheck to openstack-infra  https://review.openstack.org/4749120:15
fungisince config doesn't share a gate queue with anything, i'll just punch it through20:15
fungiotherwise things could just get worse before they get better20:16
clarkb++20:16
lifelessjeblair: btw I mailed openstack-infra@lists.o.o about the baremetal testing plan20:18
*** ruhe has quit IRC20:19
*** Ajaeger1 has quit IRC20:19
openstackgerritA change was merged to openstack-infra/config: Remove the now vestigal pyflakes tox env  https://review.openstack.org/4764120:20
openstackgerritA change was merged to openstack-infra/config: Garbage collect Git repos in gerrit-git-prep  https://review.openstack.org/4791520:20
*** dkliban has quit IRC20:22
*** kiranmurari has quit IRC20:22
*** dprince has quit IRC20:30
*** SergeyLukjanov has quit IRC20:30
mordredjeblair: stellar20:31
clarkbfyi I just approved https://review.openstack.org/#/c/46499/ I plan on keeping an eye on that but if you see anything funny with teh bug commit message stuff let me know20:31
Ryan_Lanehey, are you guys using elastic search for anything?20:32
clarkbRyan_Lane: we are20:32
Ryan_Lanedo you have it installed via package?20:32
clarkbRyan_Lane: I am using their debian packages20:32
Ryan_LaneI'd like to add https://www.mediawiki.org/wiki/Extension:CirrusSearch to the wiki20:33
clarkbRyan_Lane: which allows me to install a specific version which logstash is cranky about20:33
*** sandywalsh has quit IRC20:33
Ryan_Lanebut that requires adding elastic search to the instance20:33
Ryan_Lanehow are you adding the package without a repo? does puppet allow evil things like that? :D20:33
clarkbRyan_Lane: it does let me show you20:33
Ryan_Laneeeeeeevil. heh20:34
Ryan_Lane(wikimedia just keeps a custom repo for stuff like this)20:34
clarkbRyan_Lane: https://git.openstack.org/cgit/openstack-infra/config/tree/modules/logstash/manifests/elasticsearch.pp#n25 lines 25 to 4120:34
openstackgerritA change was merged to openstack-infra/jeepyb: Alter comments left on 'Related' bugs  https://review.openstack.org/4649920:35
Ryan_Laneheh. nice20:35
clarkbtotally insecure, but acceptable for the logstash stuff20:35
Ryan_Laneyeah, was about to pm you about how insecure that is ;)20:35
Ryan_Laneshould atleast hash the package and check it against the sha1 they provide20:36
clarkbyeah20:36
clarkbRyan_Lane: if you add that I will gladly use it :)20:36
*** morganfainberg has quit IRC20:36
clarkbRyan_Lane: I will probably add that when I next need to upgrade elasticserach20:36
clarkbwhich will happen soonish20:36
Ryan_Laneheh. ok. I'll try. should be as easy as an onlyif20:36
*** morganfainberg has joined #openstack-infra20:37
Ryan_Lanehm. maybe not20:37
clarkbRyan_Lane: it should be as we can provide the sha1/md5 to check against directly in the puppet20:37
*** sarob has quit IRC20:38
Ryan_Laneright, but package doesn't have it20:38
clarkboh20:38
clarkb:(20:38
*** sarob has joined #openstack-infra20:38
Ryan_Laneso, maybe a chained exec20:38
Ryan_Laneget, check, and package that depends on check20:38
clarkband have the check delete the .deb if the sha/md5 doesn't match to be doubly sure puppet can't do anything with it20:39
Ryan_LaneI think about saner ways :)20:39
clarkbsanity? what is that20:39
Ryan_Laneyeah20:39
Ryan_Laneit may be possible to just make the download also do a check20:39
clarkboh maybe do wget/curl support such things?20:39
Ryan_Lanemaybe. I'll see20:40
clarkbwe can check in https://git.openstack.org/cgit/openstack-infra/config/tree/modules/logstash/manifests/init.pp#n40 too.20:42
* Ryan_Lane nods20:42
*** sarob has quit IRC20:42
Ryan_Lane:D20:44
Ryan_Lanelet's switch it to https, too20:44
clarkb++ do they support https?20:44
Ryan_LaneI guess http is fine, assuming we check the hash20:44
Ryan_Lanehttps://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.90.5.deb20:44
clarkbmight as well use the https20:44
* Ryan_Lane nods20:45
*** sandywalsh has joined #openstack-infra20:45
*** KurtMartin is now known as kmartin20:45
clarkblifeless: https://review.openstack.org/#/c/46557/1 does that cause problems for you? If you are using our sudoers module which will be used by the user virtual resource instantiation then you will get an admin group20:47
clarkblifeless: so I don't think it will cause problems20:47
openstackgerritMatthew Treinish proposed a change to openstack-infra/jeepyb: Revert "Remove tempest from list of projects that direct release."  https://review.openstack.org/4792120:47
mtreinishdkranz: ^^^ from the irc meeting last week20:48
dkranzmtreinish: Thanks. I gave it my +1 :)20:49
*** mrmartin has quit IRC20:50
hub_caphey wheres the magic bit to start logging irc channels?20:50
hub_capwhere bit, im assuming, is in some project like config maybe?20:51
lifelessclarkb: I have an admin group I think, so should be fine20:51
clarkbhub_cap: https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/manifests/eavesdrop.pp#n2520:52
lifelessclarkb: though it's in a copy-pasted file, so needs manual porting.20:52
hub_cap<3 clarkb20:52
clarkblifeless: ok thanks20:52
hub_capill be submitting a changeset shortly clarkb :)20:52
*** dmakogon_ has left #openstack-infra20:54
DennyZhangDoes anyone know about tempest stress: I've run a tempest stree, how can I get the performance report, like the error rate, througput, latency, etc?20:54
openstackgerritMichael Basnight proposed a change to openstack-infra/config: Add trove channel to eavesdrop  https://review.openstack.org/4792420:54
clarkbDennyZhang: you will want to ask in #openstack-qa20:54
DennyZhangthanks, clarkb20:55
*** dims has joined #openstack-infra20:55
*** svarnau_ has joined #openstack-infra20:56
*** svarnau has quit IRC20:56
*** wchrisj has quit IRC20:57
openstackgerritA change was merged to openstack-infra/config: Make ci-launch directory readable by admin users  https://review.openstack.org/4655720:57
clarkbjeblair: does https://review.openstack.org/#/c/46607/1 conflict with the nnfi changes you are making? if not I will approve21:00
*** amotoki has joined #openstack-infra21:01
*** markmcclain1 has quit IRC21:03
*** markmcclain has joined #openstack-infra21:03
jeblairclarkb: all kinds of conflict, but i'll rebase.21:07
jeblairclarkb: (so feel free to aprv)21:08
*** cppcabrera has left #openstack-infra21:08
*** sarob has joined #openstack-infra21:09
clarkbjeblair: thanks21:11
*** sarob has quit IRC21:13
*** pcrews_ has quit IRC21:15
*** lifeless has quit IRC21:17
*** emagana has joined #openstack-infra21:17
*** thomasm has quit IRC21:18
mordredclarkb, fungi: this is now my current oldest outstanding patch: https://review.openstack.org/#/c/40068/921:18
mordredclarkb, fungi it's been sitting there for 10 days with no feedback21:18
mordredclarkb, fungi could I bother you for a review? :)21:18
*** lifeless has joined #openstack-infra21:19
openstackgerritRyan Lane proposed a change to openstack-infra/config: Separate logstash/elasticsearch and verify hash  https://review.openstack.org/4792821:19
Ryan_Laneclarkb: ^^ that hasn't been tested.21:19
*** lcestari_ has quit IRC21:19
*** kpavel has quit IRC21:20
clarkbRyan_Lane: thanks21:21
Ryan_Laneyw21:21
clarkbmordred: starred21:21
mordredfungi: also, if you get a chance, https://review.openstack.org/#/c/41945 could use some love21:21
clarkbjeblair: safe to approve the corresponding zuul change as well?21:22
openstackgerritA change was merged to openstack-infra/config: Don't show a revision when it's "None"  https://review.openstack.org/4660721:22
openstackgerritA change was merged to openstack-infra/config: Add job to propose tag merges  https://review.openstack.org/4192721:23
*** lifeless has quit IRC21:25
*** pcrews_ has joined #openstack-infra21:25
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Gerrit docs improvements - user and groups.  https://review.openstack.org/4500121:25
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Document review.pp parameters a bit.  https://review.openstack.org/4496921:25
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Make gerrit DB setup match actual practice.  https://review.openstack.org/4499321:25
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Phase 3 infra bootstrap docs: gerrit.  https://review.openstack.org/4497021:27
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Improve Zuul docs.  https://review.openstack.org/4516321:27
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Document push key acceptance.  https://review.openstack.org/4516221:27
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Document basic admin hints for jeepyb.  https://review.openstack.org/4504321:27
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Document Jenkin slave management.  https://review.openstack.org/4534521:27
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Improve Jenkins documentation.  https://review.openstack.org/4521521:27
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Explain API projects a little.  https://review.openstack.org/4511121:27
mordredclarkb: I just rebased the -1'd changes out of that set21:27
clarkbcool, I can swing back around to those after the current review round21:27
*** dkliban has joined #openstack-infra21:29
mordredclarkb: I'm doing them - most of them have 2x +2 anyway21:30
*** sarob has joined #openstack-infra21:31
*** boris-42 has quit IRC21:31
openstackgerritA change was merged to openstack-infra/config: Document review.pp parameters a bit.  https://review.openstack.org/4496921:33
openstackgerritA change was merged to openstack-infra/config: Make gerrit DB setup match actual practice.  https://review.openstack.org/4499321:33
openstackgerritA change was merged to openstack-infra/config: Gerrit docs improvements - user and groups.  https://review.openstack.org/4500121:33
clarkbmordred: did you also want jeblair to review https://review.openstack.org/#/c/40068/9 ?21:34
clarkbmordred: also, that script depends on stuff in openstack/requirements, what do you think about putting that script in the repo?21:35
clarkbmordred: instead of in openstack-infra/config? the translations jobs make sense in config because we run them for all the projects and they don't depend on eg projects.txt21:36
mordredclarkb: hrm. I could put it in requirements.txt21:36
clarkbfungi: is fifieldt near UTC or towards australia/asia?21:36
mordredor, blah, requirements21:36
*** svarnau_ has quit IRC21:36
clarkbmordred: I think either works, was just putting that out there21:36
fungiclarkb: he's in australia most of the time, not sure about today specifically21:36
*** julim has quit IRC21:37
clarkbfungi: just remembered we need to sort out nova and cinder then I need to do trove on transifex21:37
mordredclarkb: otoh, it has the jenkins git config stuf fin it21:37
mordredclarkb: let's just leave it there for now21:37
fungiahh, yes21:37
*** svarnau has joined #openstack-infra21:37
mordredit seems more jenkins-y than not21:37
clarkbmordred: ok21:38
clarkbmordred: it has my +2 I haven't approved yet as I have a hunch jeblair may want to take a look at it21:38
fungimordred: i agree also because the script depends on things in arbitrary branches of requirements, so does it need branch-specific versions? and if not, which branch does it live in normally?21:38
*** boris-42 has joined #openstack-infra21:38
fungiso outside the requirements repo makes more sense to me21:38
mordredfungi: nod21:38
*** zehicle has joined #openstack-infra21:39
clarkbmordred: oh speaking of branches does that job need to handle all the branches?21:39
clarkbwe pin the translation stuff to master only21:39
*** mriedem has quit IRC21:40
*** dkranz has quit IRC21:40
Ryan_Lane-_- I'm getting warnings on unnamespaced global variables, but I'm referencing variables from the parameterized class21:40
Ryan_Laneis there some specific way to list a namespace for that, or should the warnings just be ignored?21:40
openstackgerritA change was merged to openstack-infra/config: Groups-dev drupal drush update to 6.0.0  https://review.openstack.org/4783821:42
clarkbRyan_Lane: I wonder if $version is special in puppet land? what you have should work I think21:42
Ryan_Laneit probably is21:42
clarkbRyan_Lane: you can try ${elasticsearch::version}21:42
Ryan_Lanethis is something I hate about puppet21:42
clarkbor use something like $ver21:42
Ryan_LaneI'll do elasticsearch_version21:43
fungiclarkb: at the moment we pin requirements jobs to master, but want to start branching on havana21:43
Ryan_Lanestupid, stupid puppet21:43
openstackgerritA change was merged to openstack-infra/config: Groups-dev distbuild checked wrong Git repository commit hash  https://review.openstack.org/4784421:43
openstackgerritA change was merged to openstack-infra/config: Document basic admin hints for jeepyb.  https://review.openstack.org/4504321:43
openstackgerritA change was merged to openstack-infra/config: Explain API projects a little.  https://review.openstack.org/4511121:43
openstackgerritA change was merged to openstack-infra/config: Document push key acceptance.  https://review.openstack.org/4516221:43
fungiclarkb: to prevent projects from introducing requirements changes in stable releases, or to sync them up when needed21:43
openstackgerritA change was merged to openstack-infra/config: Improve Zuul docs.  https://review.openstack.org/4516321:43
openstackgerritA change was merged to openstack-infra/config: Improve Jenkins documentation.  https://review.openstack.org/4521521:43
openstackgerritA change was merged to openstack-infra/config: Document Jenkin slave management.  https://review.openstack.org/4534521:43
openstackgerritA change was merged to openstack-infra/config: Phase 3 infra bootstrap docs: gerrit.  https://review.openstack.org/4497021:44
clarkbfungi: requirements changes in stable releases should be fine unless we start pinning them when we release21:44
clarkbwhich is something we seem to go back and forth on21:44
*** pcm_ has quit IRC21:44
*** pcrews_ has quit IRC21:44
openstackgerritRyan Lane proposed a change to openstack-infra/config: Separate logstash/elasticsearch and verify hash  https://review.openstack.org/4792821:44
fungiclarkb: and our pre-havana answer at this point is going to be pinning supported stable-1 to the current releases of all dependencies, including transitive ones21:44
*** pcrews_ has joined #openstack-infra21:44
fungiclarkb: point being, say in 4 months a new version of some lib comes out which breaks multiple projects for havana, we would love to be able to update openstack/requirements stable/havana branch and have changes automatically generated for all projects listing that particular dependency21:45
clarkbright21:46
clarkbfungi: or we just pin them all21:46
openstackgerritA change was merged to openstack-dev/cookiecutter: Add a CONTRIBUTING file with bug tracker info  https://review.openstack.org/4765821:46
clarkbwhich is the alternative we seem to decide we should do then go back on21:46
*** dizquierdo has joined #openstack-infra21:46
fungiwell, pin has a couple different meanings (or at least granularities) here21:47
clarkbpin means foo==X.Y21:47
*** lifeless has joined #openstack-infra21:47
clarkbor >=X.Y,<X.Y+121:47
*** DennyZhang has quit IRC21:47
fungiright, well >=whatever_was_already_listed,<=todays_specific_version21:47
clarkbbut basically stop testing against any thing new21:48
fungiand including all transitive dependencies in the list in the releases where we're hard-pinning them21:48
clarkbI think where I am confused is why are we doing it for stable+1 but not stable+0?21:49
fungibecause those have a tendency to move on their own and right now we don't limit what they can be since we don't list them at all21:49
mordredclarkb, fungi: I'm not sure that scrit handles branches21:49
clarkbmordred: it doesn't. The question is should it21:49
clarkbmordred: if we pin all the things on stable then it doesn't need to21:49
mordredclarkb: we still might update the pins21:49
clarkbbut fungi suggests it will need to for stable+0 but not stable+121:49
clarkbmordred: I think you can do that manually21:50
fungimordred: the script doesn't specifically handle multiple branches right now. the reason for moving the hard-coded list of projects out of the script and into the requirements repo was so that we could branch it later as needed21:50
*** dizquierdo has quit IRC21:50
mordrednod21:50
mordredok. howabout we defer deciding what to do with automatic requirements proposals for stable branches until such a time as we know what we want to do21:51
fungiclarkb: the why stable vs. stable-1 was mostly up to ttx. i think the rationale was that most recent stable might still want loose version caps on dependencies to support security/bugfix updates from them automatically21:51
clarkbmordred: wfm21:51
fungivs stable-1 where we just hard-cap it at today's specific version, add in all transitive dependencies and ignore it from then on21:52
clarkbfungi: :/ I think I get the argument, but we don't like snowflakes around here21:52
clarkband that creates 3 of them21:52
fungiclarkb: yes, i personally don't care about the distinction. we could just hard-cap all dependencies on release day, but we still need something to prevent individual projects from landing non-conforming dependency changes without coordination21:53
mordredyes. which is why I think from an infra perspective, the mechanism should be identical across branches21:54
mordredfrom a content perspective, we can do different thigns with teh files in the repos21:54
mordredjog0: https://review.openstack.org/#/c/47491/3 <-- you were talking about re-doing the repo on top of a cookiecutter repo, yeah? do you want to do that before we suck your stuff in?21:54
*** dkehn is now known as dkehn_away21:54
*** boris-42 has quit IRC21:55
fungii also don't think we're in a great position to backport the current requirements enforcement to folsom, might be able to get it working for grizzly okay, but for havana it should be a slam dunk since they're already basically in sync21:55
jog0mordred: yeah21:55
jog0doing t a we speak21:55
clarkbfungi: I wouldn't worry about folsom too much as it goes away in a month21:55
jog0that as we*21:55
*** CaptTofu has joined #openstack-infra21:55
clarkbfungi: agreed about havana21:56
fungiclarkb: right. however hard-capping grizzly in a month might be easier than backporting the requirements enforcement to it21:56
clarkbya, so maybe we keep the snowflakes for one cycle21:56
mordredjog0: k. I'm going to WIP that patch then just to be sure. un-wip it when you're ready?21:57
jog0sounds good21:57
*** matty_dubs is now known as matty_dubs|gone21:57
mordredclarkb, jd__: I believe we can't land this: https://review.openstack.org/#/c/45862/ because we reverted cloud-archive, right? fungi <--?21:58
fungimordred: ahh, yep21:58
mtreinishmordred: actually I made an indentation mistake in https://review.openstack.org/#/c/47491/3/modules/openstack_project/files/jenkins_job_builder/config/projects.yaml21:58
clarkbmordred: good catch21:58
mtreinishI was about to respin it21:58
mordredmtreinish: well, just re-submit when you guys are ready and cookiecuttered21:58
*** weshay has quit IRC21:59
mtreinishmordred: ok21:59
* fungi needs to semi-afk for a bit... past due to start cooking dinner22:00
openstackgerritA change was merged to openstack-infra/gerritlib: fix param ordering to fix review function  https://review.openstack.org/4782122:01
*** sarob has quit IRC22:04
*** sarob has joined #openstack-infra22:04
*** mrda has joined #openstack-infra22:05
clarkbmordred: Shrews: I have reviewed https://review.openstack.org/#/c/46741/ any feedback on that?22:06
*** rockyg has quit IRC22:07
jog0mordred: cookiecutter failes flake8 heh22:07
*** rockyg has joined #openstack-infra22:07
clarkbha22:07
mtreinishheh22:07
*** sarob has quit IRC22:09
*** rockyg has quit IRC22:09
*** rockyg has joined #openstack-infra22:09
*** rockyg has quit IRC22:10
*** rockyg has joined #openstack-infra22:11
jog0ohh its the - in the name22:11
*** jhesketh has joined #openstack-infra22:11
openstackgerritRyan Lane proposed a change to openstack-infra/config: Add elasticsearch to the mediawiki node  https://review.openstack.org/4793322:12
mordredjog0: hrm.22:12
jog0folders named 'elastic-recheck'22:12
*** changbl has quit IRC22:13
clarkbfungi: do you guys chat with fifieldt tomorrow morning? any chance you can point him #openstack-infra's way? possibly during the meeting? want to sort out the transifex things22:13
fungiclarkb: 2200-2300 utc tomorrow22:14
*** amotoki has quit IRC22:14
mordredclarkb, fungi, jeblair: see #openstack-dev for amusing anecdotes about just how stupid the cloudbees jenkins-as-a-service+pull-requests is22:15
mordredor - just how good our stuff is22:16
Ryan_Lanehm. ${elasticsearch_version} still gives me the same warning in the lint22:16
Ryan_LaneI guess I'll try scoping to ${elasticsearch::version}22:17
*** tvb has quit IRC22:18
openstackgerritRyan Lane proposed a change to openstack-infra/config: Separate logstash/elasticsearch and verify hash  https://review.openstack.org/4792822:19
fungimordred: wow, atrocious22:19
clarkbRyan_Lane: weird, I am not sure why it is doing that then22:19
*** vipul is now known as vipul-away22:20
Ryan_Laneme neither. puppet perplexes me sometimes22:20
*** vipul-away is now known as vipul22:22
dhellmannjeblair, clarkb, fungi : I thought you'd find this cloudbees error (caused by amending a commit and re-pushing to github) fun: https://netflixoss.ci.cloudbees.com/job/aminator-pull-requests/119/22:22
mgagneRyan_Lane: try ${version} ?22:22
Ryan_Lanemgagne: that's what I started with :)22:22
mgagneRyan_Lane: please use $ in your param name22:24
Ryan_Laneshit, am I missing that?22:24
mgagneRyan_Lane: don't know? you check? =)22:24
Ryan_Laneah, the other param in that one doesn't use it either22:25
clarkbfungi: https://review.openstack.org/#/c/46805/ when dinner is over. Is that to accomodate projects where the project name != the project name?22:25
*** adalbas has quit IRC22:25
Ryan_Lanethat's what I get for following the code that's there ;)22:25
fungiclarkb: yes, wsme in git vs WSME tarball22:25
mgagneRyan_Lane: puppet-lint or syntax should have cried about it. :-/22:25
jog0mtreinish: pushing cookie cutter changes22:26
jog0still have some code reworking but that can wait22:26
Ryan_Lanemgagne: it didn't because it wasn't used in the manifest, but in an erb22:26
clarkbfungi: thanks22:26
openstackgerritRyan Lane proposed a change to openstack-infra/config: Separate logstash/elasticsearch and verify hash  https://review.openstack.org/4792822:26
Ryan_Lanemgagne: thanks for catching that ;)22:27
mgagneRyan_Lane: np22:27
openstackgerritA change was merged to openstack-infra/config: Add trove channel to eavesdrop  https://review.openstack.org/4792422:27
jog0mtreinish: pushed22:29
jog0mordred: patch is ready, unless mtreinish found another bug22:31
*** openstack has joined #openstack-infra22:31
openstackgerritClark Boylan proposed a change to openstack-infra/zuul: Update tox.ini to current standards  https://review.openstack.org/4739122:36
clarkbmordred: ^ I rebased that for you22:36
*** rcleere has quit IRC22:39
*** rcleere has joined #openstack-infra22:39
*** thedodd has quit IRC22:43
*** dims has quit IRC22:43
openstackgerritRyan Lane proposed a change to openstack-infra/config: Add elasticsearch to the mediawiki node  https://review.openstack.org/4793322:43
*** rcleere has quit IRC22:43
clarkbwe are a bit behind on available centos6 nodes. I think nnfi must have increased throughput such that we are not keeping up again22:44
openstackgerritKhai Do proposed a change to openstack-infra/config: Setup private gerrit for security reviews  https://review.openstack.org/4793722:46
clarkbjeblair: re NNFI, it appears that more than one failed change can be in the gate queue at a time22:47
clarkbjeblair: shouldn't we always have a max of 1?22:47
clarkboh wait, things that can't merge will be skipped22:47
clarkbbut actual failures should be restarted if they are behind a different failure22:47
*** zehicle has quit IRC22:49
*** cthulhup has joined #openstack-infra22:50
openstackgerritKhai Do proposed a change to openstack-infra/config: Setup private gerrit for security reviews  https://review.openstack.org/4793722:50
*** vipul is now known as vipul-away22:51
mtreinishjog0: sorry I was driving home. Yeah the indent is wrong in projects.yaml22:51
*** datsun180b has quit IRC22:51
mtreinish4 spaces instead of 222:51
clarkbI just approved https://review.openstack.org/#/c/47644/ which makes the python we have in openstack-infra/config flake8 clean22:52
clarkbI will keep my eyes open for breakage22:52
zaroclarkb: would you like to handle adding new params to heira for this? https://review.openstack.org/#/c/4793722:53
sdagueclarkb: nice22:53
clarkbzaro: not yet, it would be good to get some feedback on whether or not we need all of them and if they should be different than normal gerrit22:54
*** cthulhup has quit IRC22:54
clarkbdhellmann: https://review.openstack.org/#/c/47702/1 doesn't the rawinstall test cover your concern?22:54
openstackgerritMatthew Treinish proposed a change to openstack-infra/config: Add elastic-recheck to openstack-infra  https://review.openstack.org/4749122:55
mtreinishjog0, clarkb: ^^^ That should fix the tab22:55
zaroclarkb: what is the forum for that?22:55
clarkbzaro: the change you have in gerrit is perfect22:56
zaroi've set it to WIP because of the dependency on heira params.  should i remove WIP so others will review?22:57
clarkbzaro: I think it should still be WIP then you can solicit reviews here or in the meeting tomorrow22:57
jeblairclarkb: yeah; sorry i'm bogged down in status page javascript.  it's taking quite a bit of work.22:57
clarkbmordred: https://review.openstack.org/#/c/47702/ reviewed. Is my comment about rawinstall correct?22:58
clarkbjeblair: I figured22:58
zaroclarkb: cool, thx.22:58
clarkbjeblair: what is the yeah referring to? (I have pinged you a couple times)22:58
jeblairclarkb: nnfi22:58
*** dims has joined #openstack-infra23:00
*** vipul-away is now known as vipul23:01
jheskethjeblair, clarkb: Just wondering if you have time to take a quick look at this: https://review.openstack.org/#/c/46871/23:05
jhesketh(specifically my last comment)23:05
clarkbjhesketh: looking23:07
jheskethcheers23:08
*** dcramer_ has quit IRC23:08
*** kgriffs is now known as kgriffs_afk23:15
*** rnirmal has quit IRC23:15
*** danger_fo is now known as danger_fo_away23:20
clarkbjhesketh: reviewed and turbo-hipster is a great name for an SNES usb controller with a turbo button23:21
*** thomasm has joined #openstack-infra23:21
*** changbl has joined #openstack-infra23:22
jheskethwe have this thing where we just randomly generate names until a good one comes up23:22
jheskethlaughing-spice formats logs for me23:22
jheskethclarkb: thanks for reviewing :-)23:22
*** hemna is now known as hemnafk23:24
mordredjhesketh: turbo-hipster?23:28
clarkbmordred: do you have 15 minutes? I have found so many things while reviewing23:28
clarkbmordred: would like to just run through them now with you if possible23:28
jheskethmordred: https://github.com/rcbau/turbo-hipster23:28
*** tvb has joined #openstack-infra23:29
*** tvb is now known as Guest3162423:29
mordredoh wow23:29
mordredjeblair: did you see turbo-hipster? (I know you're in javascript land, but you might find it interesting)23:29
clarkbmordred: I am just going to start https://review.openstack.org/#/c/46996/ is a potentially backward incompatible change. Are we just biting the bullet as pbr hasn't been included in an integrated release yet?23:30
* mordred HATES the name... but ...23:30
* mordred did release a piece of software called pbr23:30
mordredso23:30
* mordred probably should shut up23:30
clarkbmordred: https://review.openstack.org/#/c/46736/ has a major bug in it (see comments)23:30
clarkbwe sorry23:31
jog0mtreinish: thanks23:31
clarkbwow "er sorry" https://review.openstack.org/#/c/46741/ is the one with a bug23:31
mordredclarkb: both aX and devX are pre-release versions23:31
clarkbmordred: can you confirm my comment on https://review.openstack.org/#/c/47702/ is correct?23:32
jog0mordred: any comments on how to do the code layout for elastic-search, with the dash in the name and all23:32
mordredclarkb: and we've never made any claim about monotonic increasing numbers (and tell people to use PBR_VERSION to override)23:32
mordredjog0: replace the - with a _23:32
jog0mordred: and leave the name of the repo?23:33
clarkbmordred: cool I will approve that then23:33
mordredjog0: and then there is _either_ a bug in cookiecutter, or in our template, for producing a python package of that name23:33
*** Guest31624 has quit IRC23:33
clarkbmordred: https://review.openstack.org/#/c/47164/ should be abandoned or we need to discuss it with lifeless23:33
mordredjog0: yes. and of the pypi package23:33
mordredclarkb: good question. Shrews: https://review.openstack.org/#/c/46741/23:34
jog0mordred: so elastic-recheck/elastic_recheck/code.py ?23:34
mordredyeah23:34
jog0and pip isntall elastic-recheck, import elastic_recheck23:34
mordredyeah23:34
jog0makes sense to me23:34
jog0thanks23:34
*** gyee has quit IRC23:34
mordredsure!23:35
*** rfolco has quit IRC23:35
jog0mtreinish mordred: now that the repo is close to being under -infra, which reminds me we need to create the  gerrit groups for it, I will draft the email to announce it23:35
lifelessclarkb: right, tie is not python.23:36
clarkbjog0: the groups will be greated when the change merges then we can populate them23:36
lifelessmordred: ^23:36
jog0clarkb: neato23:36
* jog0 eates a really late lunch .. and dislikes jury duty23:38
clarkbI was going to approve the dev pbr change but noticed http://logs.openstack.org/96/46996/2/check/gate-tempest-devstack-vm-postgres-full/b7f8302/console.html fails anyone seen that before?23:39
clarkbI can't find an obvious bug for it on the recheck page or in the tempet bug list23:39
mordredlifeless: btw - you may also want to check out turbo-hipster23:40
mordredlifeless: it's a zuul-gearman based non-jenkins job runner23:40
jog0clarkb: I think I have seen that23:40
clarkbmordred: https://review.openstack.org/#/c/47164/ can that be abandoned?23:40
jog0check logstash :)23:40
jog0and fie a bug, we can always mark as a dup later23:41
*** mrodden has quit IRC23:41
mordredlifeless: are you saying that there is not python code in tie?23:41
clarkbok will do23:41
mordredlifeless: (I agree that that patch was a mistake given current state of tie repo - just asking)23:43
clarkbmordred: I think there is a setup.py and that is it23:45
clarkbbefore I forget I will probably leave a little early tomorrow as I am going to a Mariners game and need to be there in time for the first pitch23:46
*** mrda has quit IRC23:47
*** arosen has quit IRC23:47
*** thomasm has quit IRC23:48
*** dkliban has quit IRC23:49
*** matsuhashi has joined #openstack-infra23:50
*** dcramer_ has joined #openstack-infra23:50
*** arosen has joined #openstack-infra23:51
openstackgerritJoshua Hesketh proposed a change to openstack-infra/config: Test nova changes against a real database  https://review.openstack.org/4687123:51
reeda question about the concept of 'committer' on gerrit23:51
reedthis changeset: https://review.openstack.org/#/c/41213/23:51
reedowner is sukhdev, committer is Markmc23:51
jheskethclarkb: when you have a moment I've updated the job checker to have a list of non jjb jobs23:52
reedthis review: https://review.openstack.org/#/c/46796/ has sukhdev owner and committer...23:52
*** mrodden has joined #openstack-infra23:52
reednow, question is: what is 'committer' again?23:52
clarkbreed: owner is the person that pushed the first patchset. commit auther authored the patch, committer committed the patch23:52
clarkbreed: author and committer can be different if for example someome else rebases a commit for you to fix merge conflicts23:53
clarkbjhesketh: looking23:53
reedso author is not necessarily the owner?23:53
*** mrodden1 has joined #openstack-infra23:54
jheskethreed: you can change author via git commands23:54
reedoh, wait.. author is what we need23:54
jheskethbut the owner still owns the review23:54
reedlet me look at this again23:54
*** dkranz has joined #openstack-infra23:54
jheskethreed: something like  git commit --amend --author "New Author Name <email@address.com>"  ?23:55
reedyeah... ok, I think I got it right23:55
clarkbjhesketh: reviewed, there was one small thing that snuck by after your testing :)23:55
jheskethwoops!23:56
openstackgerritJoshua Hesketh proposed a change to openstack-infra/config: Test nova changes against a real database  https://review.openstack.org/4687123:56
*** mrodden has quit IRC23:57
clarkbAlex_Gaynor: https://review.openstack.org/#/c/47756/2 does requirements pass when run under pypy?23:57
clarkbAlex_Gaynor: any chance you could leave a comment with testing info?23:57
*** sarob has joined #openstack-infra23:57
*** pcm_ has joined #openstack-infra23:58
reedproblem is that gerrit json api only exposes the uploader and the owner http://gerrit.googlecode.com/svn-history/r6507/documentation/2.2.1/json.html#patchset23:58
*** dcramer_ has quit IRC23:59
*** sarob_ has joined #openstack-infra23:59
*** Ryan_Lane has quit IRC23:59
*** pcm_ has joined #openstack-infra23:59
*** Ryan_Lane1 has joined #openstack-infra23:59
*** Ryan_Lane1 is now known as Ryan_Lane23:59
*** Ryan_Lane has joined #openstack-infra23:59

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