Thursday, 2013-08-08

pleia2mgagne: if we're required to move to it at some point anyway for puppet 3, makes sense00:00
fungimgagne: pleia2: so i have manually confirmed both != nil and .has_key?() do what we want. if the latter is safer, then i agree we should use it00:01
*** vipul is now known as vipul-away00:01
pleia2fungi: how does .has_key?() syntax work exactly?00:03
dstufftclarkb: thanks, i'll see what I can do. It won't make it into 1.4.1 but I'll try to get it fixed00:03
mgagnefungi: would you allow a nil value to be injected in a template? I'm not sure how puppet translates undef value to erb template variables. Will it still define the variable but set it to nil?00:03
mgagnefungi: in that case, you might want != nil00:04
mgagnefungi: unless a ruby guru hit me with a stick and tell me it's not the correct way to do it00:04
pleia2fungi: ok, where did you put != nil ? just replaced "" with nil or...?00:06
*** ^d has quit IRC00:06
*** sarob has quit IRC00:12
*** sarob has joined #openstack-infra00:12
pleia2hm, with this it seems it's less easy to toggle replication for -dev servers00:13
*** arosen1 has quit IRC00:13
*** krtaylor has joined #openstack-infra00:14
fungipleia2: sorry, was afk or a bit00:14
fungi<% if replication.has_key?('replicatePermissions') -%>00:15
fungior alternatively i was also able to make this work00:15
*** sarob has quit IRC00:15
fungi<% if replication['replicatePermissions'] != nil -%>00:15
pleia2let's go with nil00:15
fungiboth of those gave us the desired end result across the entire template00:16
* pleia2 nods00:16
jog0mordred: looks like we have a fun failure http://logs.openstack.org/54/40754/1/check/gate-nova-pep8/035fcb5/console.html00:18
*** woodspa has joined #openstack-infra00:18
*** arosen1 has joined #openstack-infra00:19
*** UtahDave has quit IRC00:21
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779400:22
*** woodspa has quit IRC00:22
*** woodspa has joined #openstack-infra00:23
pleia2so that fixes the immediate problem, but I am pretty sure this makes it so both review and review-dev are now shipped with the same template and we don't want that (review-dev sending updates to git.o.o would not be so good)00:23
*** wu_wenxiang has quit IRC00:24
clarkbpleia2: I don't think there is overlap in project names, but ya that wouldn't be good00:24
fungipleia2: seems to solve the config file issue on the last patchset00:25
pleia2fungi: \o/00:25
fungipleia2: why shouldn't review-dev send updates there? we have it seding updates to github00:25
pleia2fungi: I guess it wouldn't hurt if there is no overlap00:26
fungiwe have test projects on review-dev which we use to test out things we wouldn't put in a production repo, but it's nice to have them treated the same00:26
clarkbfungi: does cgit give us good separation at the org level?00:26
*** sarob has joined #openstack-infra00:26
pleia2cgit will only serve up things in the projects.yaml anyway00:26
clarkbmy only concner would be having gtest in the same list as nova00:26
pleia2git:// will serve up everything in /var/lib/git/ though00:26
fungiclarkb: we have org-level separation00:27
fungiin cgit and on the filesystem00:27
clarkbin that case ignore me00:27
fungiit's a naive implementation, but we don't just dump them all repos into the same parent directory00:28
fungis/them//00:28
jeblairi would rather not have review-dev push to git.o.o00:28
pleia2hm, how about replicate_local? I don't think gerrit-dev does that, unless I'm missing something00:28
fungijeblair: do we want to have review-dev also stop replicating to github in that case?00:28
*** nijaba has quit IRC00:28
jeblairif it wants to push to somewhere, we can have it push to git-dev.00:29
jeblairfungi: i don't think it matters; it may as well.00:29
pleia2so right now the whole replicate [] thing is in gerrit.pp, perhaps this should instead be in review(_dev).pp ?00:29
*** nijaba has joined #openstack-infra00:29
jeblairpleia2: at least; possibly site.pp00:30
jeblairfungi: there's nothing that ties the repos on review-dev that get published to github to openstack; i don't think our silly test repos should be on git.o.o though.00:31
fungiokay, i'll buy that reasoning00:32
pleia2seems messy for our clean site.pp :)00:32
pleia2but either way00:32
jeblairpleia2: it does.  bit of a grey area.  i'd probably go with review(_dev).pp for now.00:32
*** sarob_ has joined #openstack-infra00:33
fungireasonable since that's where the original switch was exposed to enable/disable replication prior to this refactoring00:33
* pleia2 nods00:33
jeblair(on the one hand it is "how openstack configures the server", otoh, it makes it a bit difficult for us to spin up a dev gerrit instance without getting github replication thrown in to boot)00:34
*** arosen2 has joined #openstack-infra00:34
jeblairbut at least it will probably just error out in that case.00:34
clarkbjeblair: I think that is ok, they will just race each other in the force pushing :)00:35
pleia2so, is gerrit-dev replicating to anything?00:37
*** sarob has quit IRC00:37
pleia2s/is/should00:37
clarkbat the very least github and the local replica00:37
fungiit currently replicates locally and to github00:37
*** sarob_ has quit IRC00:37
*** arosen1 has quit IRC00:37
fungier, review-dev not gerrit-dev00:37
pleia2yeah, that's what I meant00:38
pleia2ah, I see review-dev.projects.yaml.erb now00:38
pleia2no overlap00:39
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779400:42
pleia2ok, hopefully that sorts it00:42
*** vipul-away is now known as vipul00:43
fungipleia2: actually not. you're going to need to pass that replication hash table down from openstack_project::review{,_dev} through openstack_project::gerrit into ::gerrit00:50
pleia2fungi: ah right00:51
fungipleia2: as that patch stands now, you have a dupe declaration of ::gerrit00:51
pleia2yeah00:51
fungiDuplicate declaration: Class[Gerrit] is already declared in file /opt/config/fungi/modules/openstack_project/manifests/gerrit.pp at line 153; cannot redeclare at /opt/config/fungi/modules/openstack_project/manifests/review_dev.pp:8300:51
* pleia2 thinks00:52
fungijust treat it like any of the other variables you see passed into openstack_project::gerrit within review{,_dev}.pp00:55
fungiand then set a default of [] for it in modules/openstack_project/manifests/gerrit.pp like you do in modules/gerrit/init.pp00:56
pleia2right right, thanks00:57
*** avtar has quit IRC01:03
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779401:04
fungicloser, but... Invalid parameter replication at /opt/config/fungi/modules/openstack_project/manifests/review_dev.pp:80 on node review-dev.openstack.org01:05
pleia2aaaah01:06
pleia2ok, I got this one01:06
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779401:08
*** Ryan_Lane has joined #openstack-infra01:08
fungicheck your commas01:10
fungioh, though you also added that default empty [] to the wrong file01:10
fungilet me mark up the review and show you what i'm suggesting01:11
pleia2sneaky commas01:11
pleia2heh, thanks01:11
*** rcleere has joined #openstack-infra01:12
*** arosen1 has joined #openstack-infra01:12
*** arosen2 has quit IRC01:13
fungisee if those inline comments make sense01:14
fungii *think* that's all you'll need01:15
*** svarnau has quit IRC01:16
*** zaro0508 has joined #openstack-infra01:16
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779401:17
fungipleia2: no errors! also the template looks like it's still generating the intended replication config so i think we're good01:20
fungionce jenkins comes back in favor, i'll cram this through since we've now addressed everyone's concerns01:20
pleia2phew01:20
harlowjaanyone got a sec, unsure whats happening with jenkins here :-/01:20
pleia2fungi: thanks for your patience, much appreciated01:20
fungiharlowja: got a link>01:20
fungi?01:20
fungipleia2: any time!01:20
*** xchu has joined #openstack-infra01:21
harlowjahttp://logs.openstack.org/62/29862/63/check/gate-cinder-python26/0479b6a/console.html unsure if u guys might have an idea here01:21
harlowjahas this been a common problem for others so far :-/01:21
harlowjaah, nm, i think i might know01:21
fungiImportError: cannot import name utils01:22
harlowjanope, nm, don't know01:22
fungican't say i've seen that one before01:22
harlowjak, hmmm, the odd part is if i run the tests locally, all good01:22
harlowjai think the import error is hiding some other problem though01:22
fungilooking closer01:23
harlowjalike the tests run but then if i run from python interpreter directly01:23
harlowja>>> from cinder.volume import utils as volume_utils01:23
harlowjaTraceback (most recent call last):01:23
harlowja  File "<stdin>", line 1, in <module>01:23
harlowja  File "cinder/volume/__init__.py", line 23, in <module>01:23
harlowja    from cinder.common import config01:23
harlowja  File "cinder/common/config.py", line 126, in <module>01:23
harlowja    help=_("Deploy v1 of the Cinder API. ")),01:23
harlowjaNameError: name '_' is not defined01:23
harlowjaso i'm wondering if that is happening when it does the import, but the import error is getting rethrown01:23
harlowjaif i use run_tests.sh though all fine01:23
fungiharlowja: looks like it's happening on 2.6 and 2.701:24
harlowjaya, sorta weird01:25
fungiharlowja: are you able to run any one of those failing tests in isolation?01:25
harlowjaattempting01:25
fungicould be something else is importing utils in an earlier test when you run it from run_tests but the ordering changes when the ci systems run it under tox/testr01:26
*** woodspa_ has joined #openstack-infra01:26
harlowjahmmm01:27
harlowjalet me see what i can find out01:27
* harlowja begins adding statements in various places, ha01:27
*** woodspa_ has quit IRC01:27
fungithough my conjecture is unlikely, given it's failing on 'from cinder.volume import utils as volume_utils'01:28
harlowjaya, something that hasn't really changed01:29
*** nijaba has quit IRC01:29
fungistale .tox virtualenvs maybe?01:30
*** nijaba has joined #openstack-infra01:30
*** woodspa has quit IRC01:30
harlowjarecreated a brand new vm just for this test, so don't think so :)01:30
fungiyeah, seems unlikely then01:30
harlowjaya, i'll see if i can figure it out, gotta be something really weird, ha01:31
fungiit's almost like utils is there but lacks an _init_.py or something?01:32
*** nati_ueno has quit IRC01:34
harlowjaunsure :-/01:35
harlowjaseems like it has one01:35
harlowjathe import error isn't so helpful, i don't think thats the real issue somehow01:36
*** Ryan_Lane has quit IRC01:41
harlowjai have a feeling it might be connected to https://github.com/openstack/cinder/commit/fa479f7b2601:41
harlowjabut not sure yet01:41
fungithat's well beyond my current level of understanding of cinder internals, unfortunately01:46
harlowjanp, i'll figure it out :)01:46
harlowjathx fungi01:47
fungiharlowja: got a little further by adding 'from cinder.openstack.common.gettextutils import _' to cinder/common/__init__.py but that's probably not the real solution01:57
harlowjaya, i think i've found out parts of it01:57
harlowjahttps://bugs.launchpad.net/oslo/+bug/1208734 and i think it was being used by some of this new code, which then caused the import to fail like that01:57
uvirtbotLaunchpad bug 1208734 in oslo "Drop openstack.common.exception" [Undecided,In progress]01:57
harlowjaalthough the import failure isn't related to that bug, i think its a side-effect01:58
bodepdI had a patch to gerrit rejected,and I don't understand why: https://gist.github.com/bodepd/618080701:58
bodepdany clues would be appreciated :)01:58
*** thomasm has joined #openstack-infra01:59
bodepdI guess it's telling me that I need to merge them separetely, can I override this? Is just a push straight to the code repo without a patch the best way to proceed?02:00
clarkbbodepd: don't circumvent gerrit02:01
clarkbit is claiming there are no new changes02:01
bodepdclarkb: and I can push something with more than 1 commit?02:02
clarkbbodepd: yes, pushing more than one commit will create a change per commit02:03
bodepdclarkb: what if I just need to sync up some branches?02:04
clarkboh you are pushing merge changes and stuff02:04
*** yaguang has joined #openstack-infra02:05
clarkbyeah so the typical backport procedure we use is cherry pick commit onto stable branch and propose for review02:05
clarkbbecause you don't get to circumvent review against $branch just because you merged to a different branch02:05
clarkbwe have occasionally setup feature branches and made the acls allow merge commits so that you can get away with a single change for a branch of development02:05
clarkbbodepd: in this case the easiest thing to do is probably to propose each of the non merge commit changes to stable/grizzly02:06
bodepdclarkb: I kind of screwed up my branches (cut the branches too early)02:06
clarkbI think the problem is you are trying to push a bunch merge commits02:06
bodepdand now I have 100s of commits02:06
mgagneclarkb: if the branch only needs the be fast-forward, what do you suggest? Can it be done in some way or can the branch be deleted and recreated?02:06
clarkbmgagne: delete and recreate if it only needs to be fast forwarded would be one quick way02:07
fungimgagne: bodepd: a ff can be simulated by deleting the branch and creating a new02:07
fungiwhat clarkb said02:07
bodepdclarkb: thanks02:07
mgagneand now we cannot delete branches by ourselves =)02:07
fungihowever i'm happy to delete it for you in just a moment02:08
mgagnebodepd: whatever we do, we should make sure it's really a fast-forward and nothing else02:08
clarkbhttps://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/gerrit/acls/openstack/swift.config is an alternative if you want to allow pushes of merge commits (in this case I think the branch move is more appropriate)02:08
fungigerrit's best and worst feature is that it forces you into one very specific workflow02:09
bodepdwhat about github?02:12
bodepddo I need to delete the branches there?02:12
mgagnebodepd: it's synced by gerrit02:12
bodepdso,02:12
fungigerrit will delete the branch from github and add the new one02:13
*** zul has quit IRC02:14
bodepdcould we get help with delete our stable/grizzly branhces?02:19
fungibodepd: absolutely02:19
fungilet me know which projects02:19
*** UtahDave has joined #openstack-infra02:19
bodepd ssh://bodepd@review.openstack.org:29418/stackforge/puppet-nova.git02:19
bodepdall on stackforge:02:19
harlowjaso ya, fungi was the removal of a class which this new code depended on, somehow that exception was the one that ended up geting thrown, more of a side-effect of the problem02:20
bodepdpuppet-nova, puppet-keystone, puppet-glance, puppet-swift, puppet-cinder, puppet-horizon, puppet-quantum, puppet-openstack02:20
fungiharlowja: okay, that *does* make sense02:20
harlowjasorta :-P02:20
harlowjanot really the real error, which sorta is sad, ha02:21
fungibodepd: so just delete the "stable/grizzly" branch from each of those?02:21
*** sarob has joined #openstack-infra02:21
bodepdyes. please.02:21
bodepdand I assume I can push a new branch to them?02:21
fungibodepd: do you need new branches created and if so do you have a list of shas you want to branch from?02:21
bodepdI need to create a new branch based on master02:21
*** emagana has quit IRC02:21
bodepdfor all of those02:21
fungioh, you may be able to push new branches once i've deleted them, but i can just branch them each from the tip of master while i'm in there if you prefer02:22
bodepdmgagne: and then we can just submit a patch for those release commits when they are merged02:22
bodepdbranching them from the tip of master woudl be perfect and appreciated02:22
fungibodepd: mgagne: i did stackforge/puppet-nova02:23
fungitake a look and make sure it's sane before i move on to the others02:23
*** Ryan_Lane has joined #openstack-infra02:24
*** erfanian has joined #openstack-infra02:24
*** melwitt has quit IRC02:26
pleia2fungi: thanks02:26
bodepdfungi: I can confirm that this looks correct.02:27
* pleia2 gets flight delay notice: Your departure is now 2:05 AM02:27
bodepdmgagne: can we merge those patches before the next ones?02:27
fungibodepd: great. doing the other 7 on your list now02:27
pleia2yeah, I definitely won't be around much tomorrow02:27
fungipleia2: wow02:27
mgagnebodepd: sorry?02:27
fungipleia2: get a nap02:27
pleia2fungi: heh, it was already a late flight, just worse now :)02:27
bodepdmgagne: I want to just go ahead and merge everything else02:28
bodepdmgagne: any objection?02:28
mgagnebodepd: I can approve02:28
mgagnebodepd: all?02:28
openstackgerritA change was merged to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779402:28
bodepdmgagne: the release patches02:29
mgagnebodepd: ok02:29
mgagnebodepd: approving02:29
*** nijaba has quit IRC02:29
*** nijaba has joined #openstack-infra02:30
*** nijaba has quit IRC02:30
*** nijaba has joined #openstack-infra02:30
bodepdfungi: if you can hold off for a minute, it make my life slightly easier02:30
bodepdfungi: if you already started, not problem02:30
bodepdas always, thanks openstack-infra02:30
mgagneyep, always there to help people out =)02:31
fungibodepd: oops, sorry02:32
fungijust finished them all02:32
pleia2fungi: ah! I didn't put an ssh key in gerrit to git, so I fear it may hang upon first attempt to replicate02:34
bodepdfungi: no worries. I can sort out which ones still need updates. thanks02:35
pleia2s/key/known_host02:35
fungipleia2: i can manually fix it while you work up a patch. what's needed in it?02:35
*** sarob has quit IRC02:35
*** sarob has joined #openstack-infra02:36
pleia2fungi: just .ssh/known_hosts file for whatever runs the git syncronization, with known_hosts populated with git.o.o's info02:36
pleia2unless it overrides it somehow, I don't see a similar definition for github02:38
fungii've stopped puppet on review.o.o for a bit and commented out the cgit section in the replication config02:38
*** sarob has quit IRC02:40
pleia2fungi: does the gerrit2 user handle replication?02:42
fungipleia2: it does, but i think it may use a keypair in ~gerrit2/review_site/etc/02:43
*** huangtianhua has joined #openstack-infra02:44
fungisee the end of https://review.openstack.org/Documentation/config-replication.html02:45
fungiso ~gerrit2/.ssh/known_hosts i guess02:45
*** huangtianhua has quit IRC02:45
jerryzcould anybody tell me why i can't see any jobs on jenkins.openstack.org dashboard?02:46
pleia2fungi: thanks, that's what I was planning on02:46
mgagnejerryz: try jenkins01 and jenkins0202:46
*** zul has joined #openstack-infra02:47
fungijerryz: if you're looking for job status, http://status.openstack.org/zuul is a better overview these days02:47
clarkbwe are trying to deemphasize jenkins itself02:47
fungipleia2: so... it looks like we're not managing ~gerrit2/.ssh/known_hosts in puppet02:47
jerryzthanks02:48
fungithere are 8 keys listed in it currently02:48
pleia2fungi: oh :)02:48
pleia2fungi: maybe we just add it manually for now and file a bug to get it sorted?02:49
pleia2everything should be set on the git.o.o side, I've added gerrit's ssh keys to it already02:50
fungipleia2: i've cached it and can authenticate via 'ssh -i review_site/etc/ssh_host_rsa_key cgit@git.openstack.org'02:51
pleia2great, we should be ok then :)02:51
fungiso assuming it's the ssh_host_rsa_key it's going to try to use, we should be set02:52
fungihowever, that seems somewhat unlikely02:52
fungiit would be odd for it to use .ssh/known_hosts yet authenticate with review_site/etc/ssh_host_rsa_key instead of .ssh/id_rsa02:54
fungii'll see if i can confirm what public key github is authorizing02:54
*** erfanian has quit IRC02:59
fungipleia2: yeah, so we're authenticating to github with ~gerrit2/.ssh/id_rsa.pub03:02
fungithat was marginally painful to confirm03:02
pleia2fungi: ok, installed the pubkey on git.o.o that looked to make the most sense from hiera03:03
*** SergeyLukjanov has joined #openstack-infra03:03
pleia2'gerrit_ssh_rsa_pubkey_contents'03:03
pleia2yeah, so that's what is in review_site/etc/ssh_host_rsa_key - not a clue what ~gerrit2/.ssh/id_rsa.pub is (wouldn't it be nice if it were the same?)03:06
fungiwell, it's not the same unfortunately because i couldn't authenticate to git.o.o with it03:07
pleia2tsk03:08
clarkbthe host rsa key is the host key03:08
clarkbso that when we switch gerrit servers everyone doesnt need to update their known hosts03:08
clarkbI think03:08
pleia2oh03:08
clarkbpub key is the thing actually used to auth with03:08
pleia2so is gerrit's id_rsa.pub in hiera?03:08
clarkbno clue and I am not on a machine I can check with03:09
clarkbmy guess is yes03:09
pleia2maybe ssh_project_rsa_pubkey_contents ?03:09
fungipleia2: i find nothing in puppet managing ~gerrit2/.ssh/id_rsa.pub but i'm going to grep hiera for the contents anyway just to see03:10
pleia2fungi: yeah, it's definitely not set up by puppet03:10
fungipleia2: and it's definitely not stashed in hiera either03:11
fungii'll add it in there as a first order of business03:12
pleia2heh, ok :)03:12
*** yaguang has quit IRC03:14
pleia2once that's in, I'll update the site.pp to include it on git.o.o so it can properly populate the authorized_keys file, then open a bug about gerrit's ssh stuff not being managed by puppet and we can tidy that up later03:14
fungipleia2: using gerrit_replication_ssh_rsa_pubkey_contents03:15
pleia2thank you!03:15
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Put correct gerrit ssh pubkey on git.o.o  https://review.openstack.org/4078803:19
fungii'll also open a bug suggesting we start managing ~gerrit2/.ssh contents in puppet03:19
pleia2that's what I meant :)03:20
*** HenryG has quit IRC03:22
fungior yes, please open the bug if you want. i totally didn't see you say that right there until i reread it just now03:22
* pleia2 does so03:23
pleia2fungi: did you add secret key to hiera too?03:24
fungipleia2: yep, i did03:24
*** arosen1 has quit IRC03:24
pleia2assuming gerrit_replication_ssh_rsa_key_contents03:24
fungiyep! i did not add the known_hosts file contents but we'll likely want to populate it from a list of vars anyway03:25
* pleia2 nods03:25
pleia2thanks03:25
openstackgerritA change was merged to openstack-infra/config: Put correct gerrit ssh pubkey on git.o.o  https://review.openstack.org/4078803:25
fungiand clean out some of the cruft currently in there03:25
fungisince there were already 8 different hosts in it before i added git.o.o03:25
fungiand i'm pretty sure no more than a couple were currently used03:26
*** yaguang has joined #openstack-infra03:26
pleia2no doubt :)03:26
fungilikely just the entry for github and the entry for connecting to its own sshd03:26
*** turul_ has joined #openstack-infra03:27
*** turul_ is now known as afazekas03:28
*** nijaba has quit IRC03:29
fungiin a few minutes once git.o.o picks up that change, i'll retest from review.o.o with the correct id and then turn puppet back on there if it works03:29
pleia2git.o.o is a bit wonky at the moment from what https://review.openstack.org/#/c/40770/ seeks to fix, not sure if that will prevent this change from going03:30
*** nijaba has joined #openstack-infra03:30
pleia2sorry, this all went more rabbit-holey than I expected :)03:30
fungieverything does03:31
fungilooking03:31
*** sandywalsh has quit IRC03:32
*** zul has quit IRC03:33
openstackgerritA change was merged to openstack-infra/config: Fix double-declaration of cgit class  https://review.openstack.org/4077003:34
*** Ryan_Lane has quit IRC03:38
*** Ryan_Lane has joined #openstack-infra03:39
*** sarob has joined #openstack-infra03:46
lifelessok so run-mirror finally beaten into shape, 12m to mirror into HP cloud03:47
lifelessmordred: would you accept a bindep using patch for pbr's tests?03:48
pleia2fungi: well, git.o.o is not all well (i'll dig into it and fix later), but the ssh key is updated anyway so you should be able to test that anyway03:49
pleia2(should fix itself on next puppet run I think)03:49
mordredlifeless: depends03:50
fungiyep, that works ow03:50
funginow03:50
mordredpbr is in the gate03:50
pleia2fungi: hooray!03:50
lifelessmordred: every change to nova does a pbr test run? or every change to nova uses pbr ?03:50
fungipuppet restarted on review.o.o now03:50
pleia2thanks03:50
*** sarob has quit IRC03:51
*** cody-somerville has quit IRC03:55
lifelessmordred: ... ?03:55
lifelessjeblair: for context, a mirror refresh in hpcloud takes 9 minutes03:57
lifelessjeblair: thats about 6 minutes longer than we want image building to be ;)03:57
lifelessjeblair: but we need to do it inline with the builds because we get latest git which may require latest mirror contents.03:57
lifelessjeblair: [I thought some hard data might be useful for you]. I'm going to time doing it from my machine too.03:58
clarkblifeless: run-mirror is probably iterating over all of the branches03:58
mordredlifeless: yes03:58
clarkbif we make that configurable you can probably make it go much quicker over just master03:58
fungii think -b master might help03:59
lifelessclarkb: fungi: time run-mirror -b remotes/origin/master --verbose -c mirror.yaml03:59
mordred-b remotes/origin/master03:59
lifeless...03:59
lifelessreal    8m58.749s03:59
lifelessuser    5m5.752s03:59
lifelesssys     0m36.284s03:59
clarkbdoes it already ahve the option? also you want to keep your pip cache around so that you only deal with the difs03:59
* fungi added that option a while back03:59
mordredlifeless: pbr gates nova and nova gates pbr03:59
lifelessclarkb: and that was a mere 3 hours after doing the initial run03:59
lifelessmordred: so? join the dots, I don't see the concern.04:00
mordredlifeless: no specific concern - just saying04:00
lifelessmordred: so I'm proposing to remove the 'apt-get-install' line in favour of something with bindep.04:00
lifelessmordred: something like apt-get install `bindep --missing`04:00
lifelessmordred: and then a other-requirements.txt file04:01
clarkblifeless: hmm, at that point its just doing a pip install -r iirc04:01
lifelessclarkb: sure, I'm not attacking or defending it. Just - you know - data.04:01
clarkbya, I am trying to figure out how to make it go faster because you gave us the data :)04:01
lifelessclarkb: :)04:01
lifelessRun: /tmp/tmpNkEUqt/venv/bin/pip install -U  --exists-action=w --download-cache=/home/ubuntu/download/pip/openstack --build /tmp/tmpNkEUqt/build -r /tmp/tmpfepvdg04:02
lifelessseems to be a/the big time sink04:02
clarkbya, I wonder if new pip is quicker?04:02
fungiit has flames and racing stripes04:02
clarkblifeless: would be interesting to see how latest pip does if you are using an older version04:02
lifelessit's running pip from a venv04:03
lifelessand auto upgrades it itself.04:03
lifelessso nyar nyar04:03
lifeless  Using download cache from /home/ubuntu/download/pip/openstack/https%3A%2F%2Fpypi.python.org%2Fpackages%2Fsource%2Fp%2Fpip%2Fpip-1.4.1.tar.gz04:03
lifeless-. 1.4.104:03
lifelessmordred: this idea came to me when I saw your comment in the project about getting the deps into the tree (right above the line in my patch [in gerrit] to fix mirroring python-ldap04:04
dstufftit'll go faster if you use --no-allow-external04:05
dstufftand turn on --allow-external Foo for only the things that need it04:05
lifelessit could be CPU bound for all I know04:05
lifelessreinstalling everything04:05
dstufftoh there's also lxml04:05
dstufftwhich takes a bunch of time04:05
lifelessit might e 'building numpy and pythonldap etc etc takes 5 minutes'04:05
*** sandywalsh has joined #openstack-infra04:06
clarkblifeless: it should only build those the first time04:06
clarkbright? or is the cahce not a build cache04:06
dstufftit's not a build cache04:06
dstufftit's a download cache04:06
lifelessclarkb: ^04:06
clarkb:/04:06
lifelessclarkb: it has to reinstall them to detect changed transitive deps.04:07
clarkbcan we have wheels yet? :)04:07
fungiwe blow away the build cache because, if memory serves, easy_install will see it and reuse different/older versions than you request04:07
dstufftyou can make a build cache04:08
pleia2hrm, /etc/ssl/private/git.openstack.org.key isn't being created04:08
dstufftfilling the cache is an explicit step though04:08
dstufftfor right now04:08
*** vogxn has joined #openstack-infra04:08
dstufftonce wheels are on by default there's a chance we'll make a global build cache04:08
fungiright. we tried using a build cache early on and it went way faster, but also didn't download new versions of things04:08
lifelessreal    8m35.737s04:09
lifelessuser    5m1.092s04:09
lifelesssys     0m35.444s04:09
*** UtahDave has quit IRC04:09
lifelessso yeah, 8m. Waaaay to slow.04:09
dstufftthis is openstack/requirements/requirements.txt?04:09
lifeless[for inline updates]04:09
clarkbglobal-requirements.txt but yes04:09
lifelessdstufft: run-mirror -b remotes/origin/master --verbose -c mirror.yaml04:12
lifelesswhere mirror.yaml is something like04:12
lifelesscache-root: /home/ubuntu/download04:12
lifelessmirrors:04:12
lifeless - name: openstack04:12
lifeless   projects:04:12
lifeless    - https://github.com/openstack/requirements04:12
lifeless   output: /home/ubuntu/mirror04:12
*** jerryz has quit IRC04:13
lifelessjog0: btw what did you mean by pointing at the git docs in my .gitignore patch?04:13
fungipleia2: looks from the log like you need to create the /etc/ssl/private directory. that's probably somewhat of a debianism04:13
pleia2fungi: ah, thanks04:14
fungior else the equivalent of the ca-certificates package for centos isn't installed04:14
* pleia2 nods04:14
fungiregardless, the dir isn't there04:14
* fungi sees how far that's going to go04:14
mordredI want to be a partof this conversation04:15
mordredbut I just went to the best caiprinha bar in São Paulo04:15
lifelessmordred: which?04:15
mordredso I will not04:15
mordredany of them04:15
lifelessmordred: which bar04:15
mordredwww.velosobar.com.br04:15
mordredVeloso04:16
mordredalso04:16
clarkblifeless: jog0 is suggesting you set those rules locally in your global git config04:16
mordredthere are fruits here that we don't have elsewhere04:16
lifelessclarkb: so we should delete the .gitconfig file?04:16
mordredlifeless: such as jabuticaba and caju04:16
clarkbno, keep it for project specific stuff like pyc files04:16
fungipleia2: /etc/pki/tls/certs and /etc/pki/tls/private on centos04:16
lifelessmordred: looks nice; have fun. Why are you in brazil btw?04:16
clarkbmordred jabuticaba is amazing04:17
lifelessclarkb: I don't understand the difference.04:17
fungipleia2: if you want to make it more technically correct04:17
mordredlifeless: because04:17
clarkbmordred my grandparents have three trees04:17
pleia2fungi: should do, I'll put together a patch for later04:17
clarkbso so good and they look funny on the tree too04:17
mordredclarkb: where are your grandparents?04:17
clarkbmordred big island hawaii04:17
pleia2fungi: how is gerrit? puppet dashboard is suspiciously quiet, want to wrap this up soon though so you can get some rest :)04:18
mordredlifeless: consegi next week - free software in government conference04:18
mordredlifeless: also, I have a lot of friends down here04:18
mordredclarkb: awesome04:18
fungipleia2: i'll be awake for a while still. about to push up a patch and then confirm we haven't broken github replication04:18
clarkbthey grow off the trunk rather than at the end of branches04:18
lifelessmordred: cool04:18
mordredlifeless: yes04:19
* mordred will now go to sleep04:19
clarkblifeless your editor files are a you thing04:19
lifelessmordred: ciao04:19
mordredclarkb: I am jealous of your grandparents04:19
clarkbpython files are a project thing04:19
mordredclarkb: tell them to grow some caju04:19
mordredit's AMAZING04:19
lifelessclarkb: editor backups are a standard understood by lots of tools; in what way are they a 'me' thing?04:19
clarkbI am not familiar with caju /me googles04:19
clarkblifeless its your editor (I personally wouldn't -1) but I think that is the argument04:20
lifelessclarkb: I think I should have this discussion with jog0 then :)04:20
mordredme just learned thigns04:20
mordredcaju == cashew truee04:20
mordredtree04:20
*** Ryan_Lane has quit IRC04:21
lifelessclarkb: as if you don't endorse it, me convincing you won't undo his -1 :)04:21
mordredin addition to the NUT04:21
mordredyou can also eat the cashew APPLE04:21
mordredwhich they make drinks from down here04:21
lifelessmordred: the pronounciation really should have given it away:)04:21
clarkbcacao before it is rotted to be chocolate is aweaome04:21
clarkbcaju sounds like that but for cashews04:21
lifelessand yes, caju is most excellent04:21
mordredSO GOOD04:22
mordredwhen you turn it in to caipirinhas04:22
lifelesswell04:24
lifelessanythinh caipirinhas is good04:24
lifelesssugar + ethanol + ice + fruit04:24
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Fix ssl location for git.o.o on CentOS  https://review.openstack.org/4079204:24
pleia2I'll get this centos thing eventually04:24
lifelessno, you won't :)04:25
pleia2haha04:26
lifelessit, like rhel, will get you04:26
fungiit will get you first04:26
fungiha04:26
pleia2nice04:26
fungilifeless beat me to the punchline there04:26
lifelesswhen it's supported for 10 years, with no change, ease of use is a rare thing, for $various reasons04:26
openstackgerritA change was merged to openstack-infra/config: Fix ssl location for git.o.o on CentOS  https://review.openstack.org/4079204:29
*** Ryan_Lane has joined #openstack-infra04:30
*** nijaba has quit IRC04:30
*** nijaba has joined #openstack-infra04:30
*** Ryan_Lane has quit IRC04:31
*** Ryan_Lane1 has joined #openstack-infra04:31
*** afazekas has quit IRC04:31
*** SergeyLukjanov has quit IRC04:33
*** rcleere has quit IRC04:37
*** rcleere has joined #openstack-infra04:39
*** nicedice_ has quit IRC04:40
*** Ryan_Lane has joined #openstack-infra04:43
*** boris-42 has joined #openstack-infra04:43
dstufftlifeless: I was bored https://gist.github.com/dstufft/08cfaf16539a56bc5eb204:44
dstufftthat's download time only04:44
lifelesscool04:44
lifelessdstufft: where's your -U :)04:45
dstufftlifeless: it's an empty venv there's nothing to upgrade04:45
*** Ryan_Lane1 has quit IRC04:45
*** nayward has joined #openstack-infra04:49
fungipleia2: that worked!04:50
pleia2fungi: almost, apache didn't start04:51
fungiyeah04:51
*** afazekas has joined #openstack-infra04:52
fungitrying it manually to get more details04:52
pleia2placing bets on whether it's selinux04:54
pleia2:)04:54
fungiNo such file or directory: httpd: could not open error log file /etc/httpd/${APACHE_LOG_DIR}/git-error.log.04:54
pleia2well that's no so bad04:54
pleia2  ErrorLog ${APACHE_LOG_DIR}/git-error.log04:57
pleia2I wonder why it expanded so weirdly04:57
pleia2or didn't expand, I guess04:58
lifelesseh05:04
lifelessrobertc@lifelesshp:~$ du -sh work/jeepyb-test/mirror/05:04
lifeless25M     work/jeepyb-test/mirror/05:04
lifelessrobertc@lifelesshp:~$ du -sh work/jeepyb-test/download/05:04
lifeless56M     work/jeepyb-test/download/05:04
lifelessafter 20m05:04
lifelessThis is what I mean by 'mirroring slow from NZ'05:04
openstackgerritJeremy Stanley proposed a change to openstack-infra/git-review: Pin hacking <0.6  https://review.openstack.org/4079905:05
openstackgerritJeremy Stanley proposed a change to openstack-infra/git-review: Wrap multiple-commit warning text  https://review.openstack.org/4080005:05
*** rcleere has quit IRC05:07
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Update httpd log directory in template for git.o.o  https://review.openstack.org/4080105:15
openstackgerritA change was merged to openstack-infra/config: Update httpd log directory in template for git.o.o  https://review.openstack.org/4080105:20
*** nayward has quit IRC05:25
*** nayward has joined #openstack-infra05:25
*** nijaba has quit IRC05:30
*** nijaba has joined #openstack-infra05:31
*** nijaba has quit IRC05:31
*** nijaba has joined #openstack-infra05:31
*** dina_belova has joined #openstack-infra05:36
*** dina_belova has quit IRC05:38
pleia2fungi: git.o.o is ok, but I think when that VM was set up port 443 wasn't opened05:39
fungipleia2: yay05:39
fungiand yeah, iptables in the puppet manifest05:39
pleia2I updated puppet05:40
pleia2added 443 in the list of ports in my initial ssl patch, but the VM itself (at least on hpcloud, I need to give it a list of ports I want open)05:40
fungipleia2: looks like it's there, yeag05:40
fungiis this on hpcloud and not rackspace?05:41
pleia2it's rackspace05:41
pleia2not sure how those VMs work with ports05:41
fungishouldn't be needed... tcpdump to the rescue05:41
fungiit's getting there and the server's sending tcp/rst05:42
pleia2huh05:43
lifelessmordred: can you use a run-mirror mirror without the html files? like will just the raw paths do?05:43
fungiyeah, netstat -lnt says nothing's listening on 44305:43
lifelessmordred: (with a file:// url to it)05:43
lifelessfungi: I so want a -i in there05:44
fungilifeless: indeed05:44
*** jhesketh has quit IRC05:46
fungipleia2: no errors in the log, so my guess is IfModule mod_ssl.c evaluates false05:46
pleia2fungi: ah, I need to finish packing and do last minute close up home things before trip, I'll see about whipping up a patch tomorrow05:47
fungipleia2: no worries. it's very close now!05:48
fungihave a safe trip05:49
pleia2thanks :)05:49
*** mikal has quit IRC05:54
*** mikal has joined #openstack-infra05:55
lifelessjust saw this in g+ - http://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/05:57
lifelessmight be worth an eyeball from one of you sysadmin types ;)05:57
*** jhesketh has joined #openstack-infra05:59
lifelessclarkb: fungi & pleia2 ^05:59
*** sshturm__ has quit IRC06:00
*** Ryan_Lane has quit IRC06:06
lifelessand wheee -06:06
lifelessreal    39m4.291s06:06
lifelessuser    6m33.628s06:06
lifelesssys     0m46.968s06:06
lifelessthats a update on a fully mirrored cache, from NZ using run-mirror -b remotes/origin/master06:06
lifelessmordred: clarkb: fungi: jeblair: ^ :) Again, just FYI.06:07
lifelessdstufft: I haven't tried your tweaked link list yet.06:07
lifelesslater..06:07
*** Ryan_Lane has joined #openstack-infra06:10
*** thomasbiege1 has joined #openstack-infra06:15
*** markmcclain has quit IRC06:19
*** nijaba has quit IRC06:30
*** nijaba has joined #openstack-infra06:31
*** pabelanger has quit IRC06:50
*** vogxn has quit IRC06:58
*** thomasbiege1 has quit IRC07:05
*** pabelanger has joined #openstack-infra07:13
*** mestery_ has joined #openstack-infra07:17
*** mestery has quit IRC07:19
*** jpich has joined #openstack-infra07:21
*** SergeyLukjanov has joined #openstack-infra07:21
*** dina_belova has joined #openstack-infra07:23
*** Ryan_Lane has quit IRC07:23
ttxmgagne: (late answer): you can list bugs and blueprints at the project group level, see for example https://bugs.launchpad.net/openstack/+bugs07:25
*** vogxn has joined #openstack-infra07:26
ttxthe problem with LP project group is that a single project can belong to only one project group... and any project can add itself to a group07:26
*** nijaba has quit IRC07:31
*** Ryan_Lane has joined #openstack-infra07:31
*** nijaba has joined #openstack-infra07:32
*** CliMz has joined #openstack-infra07:36
*** vogxn has quit IRC07:43
*** emagana has joined #openstack-infra07:44
*** thomasbiege1 has joined #openstack-infra07:54
*** dina_belova has quit IRC07:55
*** yaguang has quit IRC08:03
*** derekh has joined #openstack-infra08:07
*** thomasbiege1 has quit IRC08:12
*** dina_belova has joined #openstack-infra08:14
*** odyssey4me has joined #openstack-infra08:14
*** vogxn has joined #openstack-infra08:18
*** fbo_away is now known as fbo08:22
*** vogxn has quit IRC08:22
*** vogxn has joined #openstack-infra08:23
*** boris-42 has quit IRC08:23
*** yaguang has joined #openstack-infra08:28
*** nijaba has quit IRC08:31
*** psedlak has joined #openstack-infra08:31
*** nijaba has joined #openstack-infra08:32
*** xchu has quit IRC08:32
*** xchu has joined #openstack-infra08:44
*** ruhe has joined #openstack-infra08:45
*** Ryan_Lane has quit IRC08:49
*** dkehn has quit IRC09:01
*** thomasbiege1 has joined #openstack-infra09:07
*** yaguang has quit IRC09:13
*** yaguang has joined #openstack-infra09:14
*** xchu has quit IRC09:19
*** Ryan_Lane has joined #openstack-infra09:21
*** yaguang has quit IRC09:22
*** yaguang has joined #openstack-infra09:23
*** dina_belova has quit IRC09:27
*** dina_belova has joined #openstack-infra09:27
*** dina_belova has quit IRC09:28
*** nijaba has quit IRC09:31
*** xchu has joined #openstack-infra09:32
*** nijaba has joined #openstack-infra09:32
*** nijaba has quit IRC09:32
*** nijaba has joined #openstack-infra09:32
ekarlso-hmmm09:34
ekarlso-mordred: ping09:34
ekarlso-or anyone else rly09:34
ekarlso-getting a error when doing devstack on precise09:35
ekarlso-http://pastebin.com/ZeLWUq2c09:35
*** spiffxp has quit IRC09:35
*** Ryan_Lane has quit IRC09:36
*** spiffxp has joined #openstack-infra09:37
*** yaguang_ has joined #openstack-infra09:38
*** yaguang has quit IRC09:38
*** dkehn has joined #openstack-infra09:40
*** boris-42 has joined #openstack-infra09:40
*** ruhe has quit IRC09:50
*** Mikhail has joined #openstack-infra09:56
*** mdurnosvistov has quit IRC09:56
*** Mikhail is now known as Guest6586109:56
*** koobs has quit IRC10:08
*** koobs has joined #openstack-infra10:08
*** dina_belova has joined #openstack-infra10:10
*** xchu has quit IRC10:11
*** amotoki has quit IRC10:12
*** emagana_ has joined #openstack-infra10:14
*** mikal has quit IRC10:17
*** emagana has quit IRC10:18
*** mikal has joined #openstack-infra10:19
*** dina_belova has quit IRC10:27
*** dina_belova has joined #openstack-infra10:28
*** nijaba has quit IRC10:28
*** nijaba has joined #openstack-infra10:32
*** nijaba has quit IRC10:32
*** nijaba has joined #openstack-infra10:32
lifelessargh stab '10:35
lifeless2013-08-07 22:40:31.032 | ./setup.py:1:1: H803  git commit title ('Fix python-ldap mirroring.') should not end with period'10:35
openstackgerritlifeless proposed a change to openstack-dev/pbr: Stop checking periods in commit messages  https://review.openstack.org/4083810:37
openstackgerritlifeless proposed a change to openstack-dev/pbr: Fix python-ldap mirroring.  https://review.openstack.org/4073210:37
*** thomasbiege1 has quit IRC10:38
*** zul has joined #openstack-infra10:50
*** weshay has joined #openstack-infra10:57
*** ruhe has joined #openstack-infra10:58
*** yaguang_ has quit IRC10:59
*** yolanda has joined #openstack-infra11:05
yolandahi, i'm trying to setup a generic zuul deployment, and i'm having problems if i don't specify any project. How can i set an empty projects section into layout.yaml?11:05
*** ruhe has quit IRC11:08
*** nijaba has quit IRC11:09
*** ruhe has joined #openstack-infra11:10
*** CaptTofu has quit IRC11:13
*** CaptTofu has joined #openstack-infra11:14
*** nijaba has joined #openstack-infra11:16
*** nijaba has quit IRC11:16
*** nijaba has joined #openstack-infra11:16
*** CaptTofu has quit IRC11:19
*** CaptTofu has joined #openstack-infra11:19
yolandaany idea? i tried something like projects: ~ but it complains with MultipleInvalid: expected a list for dictionary value @ data['projects']11:20
*** dkehn has quit IRC11:20
*** dkehn has joined #openstack-infra11:24
*** woodspa has joined #openstack-infra11:25
*** mikal has quit IRC11:28
*** dina_belova has quit IRC11:28
*** mikal has joined #openstack-infra11:30
*** lcestari has joined #openstack-infra11:32
*** dina_belova has joined #openstack-infra11:34
*** HenryG has joined #openstack-infra11:35
*** emagana_ has quit IRC11:36
*** vogxn has quit IRC11:40
*** thomasbiege1 has joined #openstack-infra11:41
*** rfolco has joined #openstack-infra11:44
*** ruhe has quit IRC11:45
*** dina_belova has quit IRC11:49
*** ArxCruz has joined #openstack-infra11:49
*** ruhe has joined #openstack-infra11:51
*** weshay has quit IRC12:03
*** ruhe has quit IRC12:06
openstackgerritChuck Short proposed a change to openstack-infra/config: python3: Add python3 python-novaclient gate  https://review.openstack.org/4084812:07
*** mriedem has joined #openstack-infra12:08
*** dina_belova has joined #openstack-infra12:11
*** chuckieb has joined #openstack-infra12:16
*** dina_belova has quit IRC12:18
*** dprince has joined #openstack-infra12:21
*** sandywalsh has quit IRC12:22
*** mikal has quit IRC12:22
*** mikal has joined #openstack-infra12:24
HenryGSo I pulled the latest devstack, and now when I run stack.sh I get "ImportError: No module named pip"12:33
HenryGSeems to be due to https://github.com/openstack-dev/devstack/commit/408a4a7d1c24322b35f9a8617c7c62adeeee0dbe12:34
*** SergeyLukjanov has quit IRC12:34
HenryGBecause if I rewind to before that it works.12:35
openstackgerritChuck Short proposed a change to openstack-infra/config: python3: Add non-voting gates for clients  https://review.openstack.org/4085112:35
*** sandywalsh has joined #openstack-infra12:35
*** emagana has joined #openstack-infra12:37
*** ruhe has joined #openstack-infra12:42
*** SergeyLukjanov has joined #openstack-infra12:43
*** emagana has quit IRC12:45
*** weshay has joined #openstack-infra12:45
*** dina_belova has joined #openstack-infra12:48
*** ruhe has quit IRC12:49
*** anteaya has joined #openstack-infra12:57
*** ruhe has joined #openstack-infra12:59
*** ruhe has quit IRC13:00
*** rpodolyaka has joined #openstack-infra13:03
rpodolyakaHello, guys! I've made a few patches to sqlalchemy-migrate, which we have started to maintain recently. They enable running of the suite on different SQLAlchemy versions (0.7.x and 0.8.x) and different DB backends (MySQL and PostgreSQL in addition to SQLite). Could someone of you take a look at https://review.openstack.org/#/c/38459/ and https://review.openstack.org/#/c/40436/ , please? (the corresponding patch to openstack-infra/config is he13:08
mordredrpodolyaka: your last message cut of a little13:15
openstackgerritJiri Stransky proposed a change to openstack-infra/config: Add tuskar and tuskarclient to stackforge  https://review.openstack.org/4085613:16
*** Ryan_Lane has joined #openstack-infra13:16
rpodolyakamodred: oops... here is it:  I've made a few patches to sqlalchemy-migrate, which we have started to maintain recently. They enable running of the suite on different SQLAlchemy versions (0.7.x and 0.8.x) and different DB backends (MySQL and PostgreSQL in addition to SQLite). Could someone of you take a look at https://review.openstack.org/#/c/38459/ and https://review.openstack.org/#/c/40436/ , please? (the corresponding patch to openstack-in13:16
*** adalbas has joined #openstack-infra13:17
rpodolyakamordred: I believe, I've already shown you WIP patches. I've cleaned up them since the last time and enabled testing on MySQL and PostgreSQL13:18
mordredrpodolyaka: k. looking now13:18
mordredrpodolyaka: which is the openstack-infra/config patch?13:20
*** Ryan_Lane has quit IRC13:20
mordredthat part keeps getting cut off :)13:20
rpodolyakamodred: https://review.openstack.org/#/c/39304/13:21
rpodolyakaoops, typo :)13:21
HenryGpip problem solved -- needed to clear pip cache13:24
*** prad has joined #openstack-infra13:24
*** vogxn has joined #openstack-infra13:28
openstackgerritJiri Stransky proposed a change to openstack-infra/config: Add tuskar and tuskarclient to stackforge  https://review.openstack.org/4085613:29
*** krtaylor has quit IRC13:29
*** changbl has quit IRC13:30
*** wu_wenxiang has joined #openstack-infra13:32
*** _TheDodd_ has joined #openstack-infra13:32
fungiHenryG: great! i'm still stuck on trying to decipher ekarlso-'s websockify installation exception from earlier13:34
*** avtar has joined #openstack-infra13:36
fungiyolanda: i strongly suspect zuul hasn't been tested with an empty projects list in its layout, though jeblair may have more insights once he's around13:37
*** cody-somerville has joined #openstack-infra13:41
*** vijendar has joined #openstack-infra13:42
ttxfungi, mordred: we should apply capping to stable/folsom before it starts failing again -- any idea how to proceed ?13:44
*** ruhe has joined #openstack-infra13:45
*** ruhe has quit IRC13:45
*** afazekas has quit IRC13:47
*** vogxn has quit IRC13:48
*** ruhe has joined #openstack-infra13:50
*** pentameter has joined #openstack-infra13:56
*** dkranz has quit IRC14:00
*** mrodden has joined #openstack-infra14:06
fungittx: good question, there's probably a lot of research to be done to determine release versioning schemes used by different dependencies, and also there's a bit of a hole in that... do we hunt down all the transitive dependencies and cap them too? often that's where we wind up seeing breakages from new releases of things14:07
*** ruhe has quit IRC14:09
mordredsdague: are you on vacation already?14:09
mordredfungi: I say we start by grabbing a pip-freeze from a successful devstack run14:10
fungimordred: and just populate the global-requirements.txt with <= each entry in that?14:11
mordredfungi: yeah.14:11
fungimerged with the minimum bounds we already have in it anyway14:11
mordredfungi: yup14:11
fungiand not worry about what if a dependency makes a security-oriented point release i guess?14:12
mordredfungi: I think we'll have to deal with that as it happens14:12
mordredI think the idea that we'll magically get goodness for our stable-1 release is basically continually undercut by people doing crazy things14:12
fungiprobably so. it's a pretty large list to keep tabs on though14:12
mordredfungi: we should probably take the current requirements.txt and test-requirements.txt in requirements:stable/folsom14:13
mordredmake copies of them to the side14:13
mordredthen re-branch current master as stable/folsom14:13
mordredand then replace the contents of global-requirements with the old contents14:14
*** datsun180b has joined #openstack-infra14:14
*** afazekas has joined #openstack-infra14:14
fungiseems feasible14:14
*** krtaylor has joined #openstack-infra14:15
mordredthen backport the devstack update-requirements first stuff14:15
*** markmcclain has joined #openstack-infra14:15
*** markmcclain has quit IRC14:15
mordredthen rinse and repeat with stable/grizzly14:15
zulcan someone +1 https://review.openstack.org/#/c/40851/ please14:16
koolhead17zul, o.014:17
fungizul: how is that different from https://review.openstack.org/4032314:19
zulfungi:  damn it! i totally missed that one14:20
openstackgerritMonty Taylor proposed a change to openstack-dev/pbr: Fix pep8 error  https://review.openstack.org/4086914:21
openstackgerritMonty Taylor proposed a change to openstack-dev/pbr: Sync requirements with global requirements  https://review.openstack.org/4087014:21
openstackgerritMonty Taylor proposed a change to openstack-dev/pbr: Stop checking periods in commit messages  https://review.openstack.org/4083814:23
openstackgerritMonty Taylor proposed a change to openstack-dev/pbr: Fix python-ldap mirroring.  https://review.openstack.org/4073214:23
anteayawhere did pleia2 head off to?14:24
*** burt has joined #openstack-infra14:24
*** vogxn has joined #openstack-infra14:24
fungianteaya: pennsylvania (i think)14:25
anteayacool14:25
fungigiven her departure time, i'm going to guess that she might still be in transit14:26
*** changbl has joined #openstack-infra14:26
anteayafungi: a fair assumption14:27
*** ^d has joined #openstack-infra14:27
*** ^d has joined #openstack-infra14:27
fungimordred: to what extent is the requirements proposal tooling dependent on recent packaging assumptions for the projects? (pbr, oslo, et cetera)14:28
*** adalbas has quit IRC14:28
fungijust trying to think through where the backport pain points are going to crop up14:28
sdaguemordred: no14:28
sdagueI'm on irc through tuesday (though tuesday all meetings)14:29
fungisdague: that's not my idea of a vacation14:29
sdaguefungi: it's not vacation until wed :)14:29
fungiquite clearly14:29
mordredsdague: yay! because ... syncing things and dev-requirements == not doing the right thing14:30
mordredand I wanted to talk to you about it14:30
sdaguemordred: ok, I got a meeting right now14:30
sdaguelet's talk after14:30
mordredsdague: awesome14:31
*** xchu has joined #openstack-infra14:34
*** markmcclain has joined #openstack-infra14:40
openstackgerritA change was merged to openstack-infra/config: Add python33 tests to all openstack python clients  https://review.openstack.org/4032314:40
sdaguemordred: ok, I can not pay attention to this meeting for a bit. What's the issue?14:42
*** adalbas has joined #openstack-infra14:44
*** pabelanger_ has joined #openstack-infra14:45
*** pabelanger_ has quit IRC14:45
*** pabelanger_ has joined #openstack-infra14:45
*** pabelanger has quit IRC14:45
*** pabelanger_ is now known as pabelanger14:45
*** pabelanger_ has joined #openstack-infra14:46
mordredsdague: https://review.openstack.org/#/c/40755/1/requirements.txt14:46
*** cppcabrera has joined #openstack-infra14:46
*** zyluo has joined #openstack-infra14:46
mordredsdague: the merge is downgrading oslo.config in the target repos14:46
sdagueright, so that's expected.... yeh the pre release problem is an odd one14:47
*** pycabrera has joined #openstack-infra14:47
*** pycabrera has quit IRC14:48
sdagueok, what's the desired behavior?14:48
mordredis it time to start exploring the "upload pre-release files only as wheels to pypi?" approach?14:48
sdaguewell... maybe14:48
*** rcleere has joined #openstack-infra14:48
*** markmc has joined #openstack-infra14:48
sdaguehonestly, I think we need to think about getting other project git trees onto the unit test nodes14:49
mordredthere's two issues14:49
sdaguebecause we'll have to figure out that for neutron vs. nova14:49
mordredone is testing14:49
mordredone is being able to use the repos not on our test nodes14:49
*** pycabrera has joined #openstack-infra14:49
mordredbecause oslo.config prereleases are not on pypi, we get into the weird problem14:50
sdagueright14:50
mordredbut we didn't put them there because we don't want grizzly to get an update all of a sudden - and until pip 1.4 that's not possible14:50
*** pabelanger has quit IRC14:50
mordredBUT - we pretty much require pip 1.4 for havana now14:50
sdagueso short term, we can take into account dev requirements14:50
*** pabelanger has joined #openstack-infra14:50
*** cppcabrera has quit IRC14:50
*** pycabrera is now known as cppcabrera14:51
mordredso the idea was that we upload pre-releases of osloto pypi - but only in wheel form14:51
mordredpip less than 1.3 will not find them14:51
mordredbecause it doesn't know what wheels are14:51
markmcwhat happens if you use 1.4 with grizzly?14:51
mordredit still won't find them14:51
*** apevec has joined #openstack-infra14:51
mordredbecause grizzly does not have a pre-release version in its requirements14:51
markmcah, yes14:52
mordredso it won't upgrade oslo.config until oslo.config releases its next real release14:52
markmcyes14:52
markmchave we figured out how to do wheel-only uploads?14:52
mordredthat part should be pretty simple - slightly different upload job - but simple and easy to do14:52
sdaguemordred... that makes me realize we need to get oslo.config into stable/grizzly devstack before the oslo release14:53
mordredsdague: yes14:53
sdaguethat should be easy enough though14:53
mordredwe have some requirements and devstack backportin to do14:53
mordredso I think steps are a) short term account for dev-reqs in update.py better14:54
mordredb) backport devstack and requirements changes to stable branches14:54
sdaguemordred: yeh, a I can probably do today14:54
mordredc) get wheel support and wheel uploads properly into havana14:54
mordredI believe fungi may have started on b14:54
*** dina_belova has quit IRC14:54
sdagueit will be later this afternoon, after the qa meeting14:54
mordredI'll start hacking on c14:54
fungistarting to dig into b today, yes14:55
mordredI think first step is I'm going to add wheel building to run-mirror14:55
sdaguea) will also let me play with my update.py min versions thing14:56
mordredfungi: did we land the gate-geepyb-on-pbr-integration yet?14:56
mordredsdague: markmc will be veryhappy about that14:56
mordredhe's wanted that for AGES14:56
sdaguewhich I think we need to do as well, because our min versions is very bad14:56
fungimordred: don't remember if it's approved yet... checking14:56
sdague:)14:56
sdaguemordred: it makes me realize that crazy idea I had about random walking the version space to figure out what deps actually work....14:57
*** yaguang has joined #openstack-infra14:57
sdaguewill have most of the infrastructure in place after that14:57
fungimordred: still not passing tests... https://review.openstack.org/3817614:57
mordredsdague: ooh. I like that crazy idea!14:57
sdagueyeh, you did when I put it on the ML as well :)14:57
mordredfungi: oh sod it14:57
fungimordred: just the layout validator. i can fix it up if you need14:58
mordredfungi: can you please? I think I've hit a mental block on that change14:58
fungiyou bet14:58
sdaguemordred: your pep8 tox add to requirements is failing pep8?15:01
sdagueany chance you can get that fixed soon, so we can get your update.py patches in?15:01
mordredsdague: on it15:02
fungi"irony"15:02
sdagueI think it's just a tox config issue15:02
mordredsdague: yup. fixed15:04
openstackgerritMonty Taylor proposed a change to openstack/requirements: Remove unneeded tests dir reference  https://review.openstack.org/4000215:04
openstackgerritMonty Taylor proposed a change to openstack/requirements: Update ourselves to ourselves  https://review.openstack.org/3996315:04
openstackgerritMonty Taylor proposed a change to openstack/requirements: Add pep8 checks  https://review.openstack.org/3996715:04
dansmithmordred: linkedin just told me you went to NCSU..15:05
fungilies, all lies15:05
* fungi lives 10 minutes from ncsu main campus15:06
mordreddstufft: that is, in fact, a true statement15:06
mordredI was in CATT at the time too, in case that means anything to you15:06
fungitab completion fails you again ;)15:06
mordredGAH15:07
mordreddansmith: ^^15:07
dansmithfungi: oh?15:07
dansmithmordred: actually, it doesn't15:07
dansmithmordred: but from the date linkedin says you were there, I think the bricks must have still been fresh :P15:07
*** rscottcoyle has joined #openstack-infra15:07
mordreddansmith: it was the computer geek theme dorm back in the day15:07
dansmithmordred: oh, nice15:07
mordreddansmith: we had ethernet IN OUR DORM ROOMS15:08
dansmithheh15:08
mordredand by ethernet - I mean twisted-pair and 10base215:08
dansmiththe real stuff15:08
mordredyup15:08
mordredterminators and whatnot15:08
fungi10base5 was the real stuff ;)15:08
mordredit was very fancy15:08
mordredhaha15:08
*** boris-42 has quit IRC15:08
dansmithfungi: well, I meant the stuff with actual ether, 10base5 included :)15:09
* fungi still has nightmares about routing thicknet lines15:09
*** mrodden has quit IRC15:10
fungidansmith: are you local?15:10
dansmithfungi: no, I'm in PDX now, but I grew up in Chapel Hill and lived in Raleigh through school before I moved out here15:10
*** dkranz has joined #openstack-infra15:11
*** rnirmal has joined #openstack-infra15:11
fungiahh, cool. i've lived in chapel hill and (eww) cary over the past decade, but am in raleigh now15:11
*** mestery_ is now known as mestery15:12
clarkbThe number of north carolinians around here is scary ;)15:12
funginorth carolina is scary in general15:12
fungithough it's a little less scary here "in the city" (heh) than it was in hillbilly country where i grew up15:13
mordredfungi is a fillbilly15:14
mordredgah15:15
mordredI CANNOT TYPE THIS WEEK15:15
*** krtaylor has quit IRC15:15
jeblairi reckon we all ought to git together and have us a pig pickin sometime ;)15:16
* jeblair made barbecue this past weekend15:16
*** cppcabrera is now known as cppcabrera_afk15:17
*** dhellmann_ has quit IRC15:18
fungiooh, that does sound wonderful15:18
*** vogxn has quit IRC15:18
fungialso, i appreciate your colorful use of the term "reckon"15:19
ttxjeblair: the new zuul status view with time estimates is really useful, thx15:19
*** mrodden has joined #openstack-infra15:19
*** dhellmann has joined #openstack-infra15:19
ttxjeblair: could benefit from having all progress bars right-aligned though15:19
*** SergeyLukjanov has quit IRC15:20
*** dina_belova has joined #openstack-infra15:20
ttxwould look a lot less like a brick breaker game though15:20
*** dina_belova has quit IRC15:20
* fungi plays super breakout with the zuul status screen15:21
* ttx spent too much time playing Arkanoid when he was younger.15:21
clarkbttx: sdague wrote that change iirc15:21
clarkbits in review somewhere15:22
ttxclarkb: heh15:22
ttxhttps://review.openstack.org/#/c/39097/15:23
fungiarkanoid was neat, but i didn't play it as much as its breakout predecessors15:24
*** SergeyLukjanov has joined #openstack-infra15:25
*** dina_belova has joined #openstack-infra15:27
*** pabelanger has quit IRC15:30
*** nicedice_ has joined #openstack-infra15:30
*** vijendar has quit IRC15:31
*** ruhe has joined #openstack-infra15:32
ttxfungi: missed your anwser earlier. Transitive deps ? Hadn't thought of that. Looks like we almost need to run a pristine install, observe what gets installed, and generate the list of pinned stuff15:33
fungittx: that was basically mordred's suggestion (pip freeze after a full devstack run in stable)15:34
* fungi runs away to lunch... bbl15:34
ttxfungi: ack15:35
*** CliMz has quit IRC15:35
ttxfungi, mordred: agree that pinning deps is not about freezing them. We can still manually bump for corner cases.15:35
*** yaguang has quit IRC15:36
*** yolanda has quit IRC15:36
zaromorning15:39
anteayamorning zaro15:40
*** markmcclain has quit IRC15:41
*** pabelanger has joined #openstack-infra15:44
*** dina_belova has quit IRC15:45
*** krtaylor has joined #openstack-infra15:45
*** dina_belova has joined #openstack-infra15:47
*** yaguang has joined #openstack-infra15:49
*** cppcabrera_afk is now known as cppcabrera15:49
cppcabreran/close15:49
*** cppcabrera has left #openstack-infra15:49
*** odyssey4me has quit IRC15:52
*** jpich has quit IRC15:57
*** derekh has quit IRC15:57
*** markmc has quit IRC15:58
zarofungi: tried to assign bug 1172419 to you but i could not.  is this because i'm lacking permissions?15:58
uvirtbotLaunchpad bug 1172419 in openstack-ci "build bitrot jobs after mirror update" [Low,In progress] https://launchpad.net/bugs/117241915:58
*** rpodolyaka has left #openstack-infra15:59
*** dina_belova has quit IRC15:59
clarkb`sudo chmod 777` :/15:59
*** xchu has quit IRC16:00
*** anteaya has quit IRC16:01
*** vijendar has joined #openstack-infra16:02
*** dina_belova has joined #openstack-infra16:03
*** zaro0508 has quit IRC16:04
mriedemi see that oslo doesn't list a version constraint on pbr, does anyone know what it really requires at a minimum for building with pbr?16:04
*** datsun180b has quit IRC16:04
*** dina_belova has quit IRC16:04
clarkbmriedem: probably the latest version of pbr16:04
clarkbpbr has had a ton of bug fixes recently and I am sure mordred would want everyone to use the latest version16:05
mriedemclarkb: ok, yeah, i saw the note go out recently about the overhaul16:05
mordredyes. seriously, nothing in openstack should ever use less than 0.5.2116:05
clarkbhttps://review.openstack.org/#/c/36294/8 looks like the change that is `sudo chmod 777`ing16:05
mordred:)16:05
*** vogxn has joined #openstack-infra16:06
clarkbbut it appears to have newer draft changes16:06
*** thomasbiege2 has joined #openstack-infra16:07
*** nijaba has quit IRC16:07
*** thomasbiege1 has quit IRC16:07
*** emagana has joined #openstack-infra16:07
clarkbso I can't see if that is the case16:07
*** ruhe has quit IRC16:09
*** SergeyLukjanov has quit IRC16:11
koolhead17pleia2, ping16:13
* jeblair runs errands, biab16:13
*** fbo is now known as fbo_away16:14
*** wu_wenxiang has quit IRC16:16
openstackgerritMonty Taylor proposed a change to openstack-infra/nose-html-output: Remove nose from setup_requires  https://review.openstack.org/4090316:20
mordredclarkb: ^^ I would very much like to land that and relase16:20
mordredclarkb: do tags trigger releases of that, or are we still doing it manually?16:21
*** reed has joined #openstack-infra16:21
openstackgerritSascha Peilicke proposed a change to openstack/requirements: Require lesscpy>=0.9j  https://review.openstack.org/4091016:27
*** svarnau has joined #openstack-infra16:27
*** yaguang has quit IRC16:31
*** yaguang has joined #openstack-infra16:31
*** moted has quit IRC16:31
*** moted has joined #openstack-infra16:32
*** Ryan_Lane has joined #openstack-infra16:35
*** yaguang has quit IRC16:38
clarkbmordred manual iirc16:40
*** markmcclain has joined #openstack-infra16:42
*** anteaya has joined #openstack-infra16:47
*** emagana has quit IRC16:48
clarkbI can sort it out when I am not ferrying tourists but dont let me stop you16:50
*** ruhe has joined #openstack-infra16:51
mordredclarkb: I can just do it if you're ok with that16:51
*** mrodden has quit IRC16:55
*** mrodden has joined #openstack-infra16:56
fungizaro: without being on the bug team for a project, you can only assign and unassign a ticket to yourself but can't assign to anyone else. i'll update and address it though16:56
*** jgriffith has quit IRC16:57
*** pabelanger has quit IRC16:58
jog0lifeless: keeping editor files in the localgitignore seems like the hard way of fixing the issue, IMHO setting a global gittignore for editor related files is easier.  also keeps the repo gitignore more susinct and project related17:00
*** pabelanger has joined #openstack-infra17:01
*** dina_belova has joined #openstack-infra17:05
* fungi lists his editor files in ~/.gitignore and adds excludesfile '~/.gitignore'17:05
zarofungi: thx.17:05
fungi...in the [core] section of ~/.gitconfig17:05
*** avtar has quit IRC17:06
apevecadam_g, ttx - I'll start tagging 2013.1.317:07
*** jgriffith has joined #openstack-infra17:08
*** dina_belova has quit IRC17:08
clarkbmordred yup fine by me17:08
fungipleia2: if you're around, i played with git.o.o a bit and confirmed the missing https bits are that it's not set with listen 443 and also does't loadmodule ssl_module mod_ssl.so17:09
openstackgerritA change was merged to openstack-infra/nose-html-output: Remove nose from setup_requires  https://review.openstack.org/4090317:09
fungipleia2: also nothing's getting replicated to it yet, but i suspect we may need to restart gerrit to pick that change up17:10
mordredfungi: I, for one, favor making gerrit pick up that config setting17:11
fungimordred: you welcome our new gerrit restart overlords, eh?17:12
mordredfungi: yes17:12
fungii can float a change to subscribe the gerrit service to that file, i suppose17:12
fungistill trying to sort out your zuul layout validation fail on the jeepyb gating change. it's choking on an envvar in a shell snippet, looks like. maybe { getting interpreted by the yaml parser?17:13
bodepdI still cannot submit patches to the branches of the stackforge projects17:15
*** dina_belova has joined #openstack-infra17:15
fungibodepd: i'll check your acls got applied17:16
*** fbo_away is now known as fbo17:17
bodepdfungi: is that in the acl?17:17
fungibodepd: stackforge/puppet-nova for example definitely shows in the webui that puppet-manager-core has exclusive approval and -2/+2 review rights on refs/heads/stable/*17:17
bodepdfungi: let me try that...17:18
fungibodepd: what error do you get?17:18
bodepdit says there are no changes17:18
bodepd(no new changes)17:19
fungibodepd: following a cherry-pick and review procedure similar to https://wiki.openstack.org/wiki/StableBranch#Workflow17:19
*** nati_ueno has joined #openstack-infra17:19
*** emagana has joined #openstack-infra17:20
*** dina_belova has quit IRC17:20
fungibodepd: or if all the commits in your current branch are destined for e.g. stable/grizzly then just try 'git review stable/grizzly' and see what it says17:20
fungibodepd: similarly, (i continue to assume you're using the git-review tool here) adding a defaultbranch parameter to the .gitreview on your stable branches will allow you to not need to specify the review target branch if you're on a remote tracking branch17:22
fungia number of our projects make use of that convenience17:22
mgagnefungi: http://paste.openstack.org/show/43610/17:23
fungiwhat's the sha of the tip of your current local branch you're trying to push?17:24
mgagne0ce791d17:24
fungiahh, and gerrit says 87edf77 is the current tip of stable/grizzly there, so there definitely should be differences17:25
*** HenryG has quit IRC17:25
clarkbare you pushing any unreviewed merge commits?17:26
*** pcrews has quit IRC17:26
clarkbgerrit doesnt want you to push merge commits17:26
*** Ryan_Lane has quit IRC17:26
fungiahh, yeah if 0ce791d is a merge commit it might not think there is a relevant change17:27
mgagnea merge? it's a normal commit with an empty file added17:27
*** ruhe has quit IRC17:28
bodepdfungi: I was missing the cherry-pick command. Sorry, I did not find that document before. thanks for the link17:31
fungimgagne: does 87edf77 show up in your current patch history on your local branch? how many commits back? are there any merge commits appearing between that sha and the tip of your local branch?17:32
mgagnefungi: http://paste.openstack.org/show/43612/17:33
fungibut yes, generally gerrit's workflow best accommodates cherry-picking from your development branch into your stable branch and submitting those for review17:33
pleia2fungi: thanks! I'm going to get food and possibly a nap, then I'll get some patches in :)17:35
pleia2fungi: and I think you're right about gerrit, it's part of config files so reload/restart makes sense17:35
*** datsun180b has joined #openstack-infra17:36
fungiokay, so 0ce791d has 87edf77 as its direct parent. and git diff 87edf77..0ce791d has some change of content? (i can't remember if committing just an empty file will be sane on gerrit but i'll test that myself in a sec)17:36
apevecadam_g, ttx - tags pushed, how long should it take for tarballs to show up?17:36
*** mrodden1 has joined #openstack-infra17:36
mgagnefungi: ok, I can add content to the file17:36
ttxapevec: you got that last security patch for cinder/grizzly in ?17:36
*** mrodden has quit IRC17:36
apevecttx, yep17:36
ttxtarballs take up to 10min17:37
mgagnefungi: ok, it seems it's a bad idea to commit empty file17:37
ttxapevec: I have a script that does everything from tagging to uploading tarballs and comparing md5s17:37
ttxwe should adapt that for stable branch releases17:37
mgagnebodepd: you should be able to submit changes to stable/grizzly...17:37
apevecttx, we are using your script for stable17:37
apevecit just works17:38
ttxapevec: the upload_release one... not the mp_delivery.sh one17:38
apevechttps://github.com/ttx/openstack-releasing/blob/master/upload_release.py17:38
apevecyep17:38
ttxapevec: we should push that under gerrit somewhere too, now that we are a PROGRAM17:38
*** dprince has quit IRC17:38
ttxapevec: mp_delivery does tagging + wait + upload17:38
apevecah, I see17:39
ttxstill a bit flaky atm17:39
apevecno hands!17:39
*** SergeyLukjanov has joined #openstack-infra17:39
fungimgagne: though interestingly, i seem to be able to commit a single empty file for review... http://paste.openstack.org/show/4361317:39
nati_uenoHi who's core for review days? I wanna reviewer for https://review.openstack.org/#/c/40480/17:39
ttxapevec: you can track the jobs @ https://jenkins.openstack.org/job/glance-tarball/? for example17:40
ttxalso under http://status.openstack.org/zuul/ in the release pipe17:41
apevecttx, thanks!17:41
ttx(lower right corner of the zuul status view)17:41
mgagnefungi: could it be impossible to submit empty file to stable?17:41
*** pcrews has joined #openstack-infra17:42
*** sarob has joined #openstack-infra17:42
fungimgagne: maybe, though that seems like a side effect if so and not something gerrit would enforce directly17:42
ttxapevec: I can add you to the auto-accepted people on openstack-announce17:44
ttxapevec: which email address are you using for openstack-announce ?17:44
apevecttx, apevec@gmail.com17:44
ttxapevec: oh, you're cleared already17:45
ttxso it should just work17:45
*** thomasbiege has joined #openstack-infra17:45
*** thomasbiege2 has quit IRC17:45
* ttx calls it a day17:46
fungittx: have a great evening!17:46
ttxapevec: you seem to be on the right track now :)17:46
openstackgerritgordon chung proposed a change to openstack/requirements: add pycadf library  https://review.openstack.org/4092617:46
*** jerryz has joined #openstack-infra17:46
apevecttx, yep. have a nice evening!17:47
* ttx is a bit lost with the new jenkins setup17:47
ttxjeblair: used to check https://jenkins.openstack.org/job/nova-tarball/ but now it presents an outdated view17:48
ttxhttps://jenkins01.openstack.org/job/nova-tarball/ has the right thing17:48
ttxand jenkins02 has an empty list17:48
ttxnot sure how we can get a useful list now17:49
ttxor pertinent weather report for jobs17:49
ttxI guess you'll have to educate me. Tomorrow.17:50
*** vogxn has quit IRC17:50
fungittx: logs.openstack.org will probably be a better centralized place to pull them from17:53
*** annegentle is now known as annegentle_vacay17:53
*** _TheDodd_ has quit IRC17:55
mordredfungi, jeblair: dkranz has offered to help get fedora in the devstack gate17:56
fungioh!17:57
fungimordred: for d-g, do we need puppet to still work?17:57
mordreddkranz: I believe you want jeblair's d-g patch re-arranging config to land17:57
mordredfungi: yes17:57
fungii think at the moment we need newer puppet and hiera to support fedora1817:57
*** mrodden has joined #openstack-infra17:57
mordredalthough - I believe what we decided the other day is that we thought centos in the devstack gate would make more sense17:57
*** ^demon has joined #openstack-infra17:57
mordredsdague: ^^17:57
fungior an older ruby installed on the fedora machines would theoretically work17:58
mordredfor the same reason that we use precise17:58
mordredright?17:58
clarkbmordred the rootwrap discussion has basically become "replace openstack with a bunch of gearman workers"17:58
mordredawesome17:58
clarkbfedora or centos?17:58
mordredclarkb: right. what did we decide the other day?17:59
*** ^d has quit IRC17:59
*** thomasm has quit IRC17:59
clarkbI thibk we need something that csn run tests for 18 months17:59
clarkb6 for dev cycle 12 for stable17:59
*** ^demon is now known as ^d17:59
sdaguemordred: so centos is really a problem for devstack as a primary18:00
mordredsdague: whyfore?18:01
sdaguebecause it's still not really functional18:01
*** mrodden1 has quit IRC18:01
sdaguecentos is *sooooooo* old18:01
dkranzmordred: I think fedora is what a lot of people are using for dev so that made sense to me.18:02
mordredso - with the gate...18:02
mordredonce something goes into stable18:02
mordredwe continue testing it ont he release it was tested on when it was in dev18:02
mordredbecause of moving targets and whatnot18:02
*** _TheDodd_ has joined #openstack-infra18:02
sdaguemordred: so like, for instance, you want real neutron testing18:03
sdagueyou can't use centos, kernel doesn't do it18:03
mordredwow. stellar18:03
mordredany thought of how to handle the short lifespan of fedora on our 18 month world?18:03
sdaguemordred: so fedora is really about 14 months of updates18:03
dkranzHave to step into meeting18:03
sdaguewhich isn't 18, but it's close18:04
*** krtaylor has quit IRC18:04
*** pcrews has quit IRC18:04
* mordred really hates supporting stable -118:04
sdagueyeh, what if we just didn't with fedora18:05
sdagueonly do master and stable18:05
clarkbfedora would sit under an existing test right?18:06
sdagueclarkb: yeh, move the pg job to fedora18:06
fungiso, another wrinkle... last i looked at it there were challenges getting newer puppet to run on precise, getting older puppet to run on fedora, and getting old and new puppet to use a common master and hiera version... which takes us to two separate puppet masters or something other than puppet18:06
sdagueprobably change the queue to qpid in the process as well18:06
clarkbas long as not testing pg is ok for stable -118:06
clarkbfungi new puppet on precise should work18:07
sdagueclarkb: yeh, it's a risk, but it would leave us in a much better state than not testing fedora in master18:07
mordredI think that's not unreasonable18:07
bodepdfungi: I run new puppet on precise18:07
mordredshould we at some point work out migrating to new puppet so that we don't have to keep worrying the the ruby/puppet version problems?18:08
fungiclarkb: new puppet needs new ruby and, at least the bug reports i was looking at, the ruby backports to precise weren't new enough or had some serious bugs making them unsuitable for new puppet18:08
fungibodepd: ^ i meant18:08
clarkbmordred yes18:08
fungiof course i didn't try, so the bugs may have been out of date18:08
fungior bodepd... maybe you don't run canonical's ruby packages on precise?18:08
clarkbmordred we can use two masters and migrate in steps18:08
bodepdfungi: that is possible. I installed puppet form apt.puppetlabs.com18:09
mordredclarkb: because puppet3 only talks to puppet3 master?18:09
bodepdwhich I believe pulls in ruby 1.9.318:09
clarkbmordred yes18:09
mordrednod18:09
fungibodepd: ahh, 1.9.3 from somewhere besides canonical's precise-backports i guess. i think 1.9.2.1 or something is their latest18:10
adam_gapevec, cool. sorry i haven't been more of a help this time around, i've been traveling this week18:10
apevecadam_g, np, you get next Oct 10 release :)18:10
adam_gapevec, i have been running many test runs on the tarball since monday and everything looks good18:10
apevec2013.1.3 tarballs are ready, I'm uploading to LP18:11
* clarkb plays devils advocate.18:13
*** pcrews has joined #openstack-infra18:13
clarkbif distros arent going to invest in supporting their users for usable amounts of time should we be putting extra effort into supporting them?18:13
clarkbwe stopped testing new ubuntu because 9 months is far too short18:14
clarkb14 is better but not significatly18:14
*** jpich has joined #openstack-infra18:15
dtroyerbut 3-5 years is a bit long given the pace of Python's development churn18:15
*** dina_belova has joined #openstack-infra18:15
fungibodepd: actually, looking back at the versions, precise-updates has ruby 1.9.3.0 but i think i read something about puppet 3.x needing 1.9.3.1 or newer. any guess whether that's still the case?18:16
mordredlet me say that in a different way - how about we stop caring about stable -118:18
mordredit truly seems like we only care about it in theory18:18
mordredbut we still let its existence drive other design decisions18:19
clarkbmordred our users care about it18:19
mordredwho?18:19
dtroyerat least for Fedora, I'm fine with that.  Fedora deployments have already chosen a non-long-term-stable OS.18:19
clarkbpeople running old stuff18:19
mordredclarkb: these are theoretical people18:19
clarkbyou still se a lot of folsom discussions on the list18:19
mordredbut I don't see a lot of folsom patches18:19
* fungi still sees essex discussions18:19
fungithankfully not so many diablo discussions though18:20
mordredand I expect that _we_ are not the source of essex or folsom deployments right now18:20
*** dina_belova has quit IRC18:20
funginot unless i'm doing it in my sleep18:20
mordredgrumble. grumble.18:21
jeblairi'm back18:21
mordredyay118:21
mordredwe missed you18:21
sdagueclarkb: we can care less, by running a subset of precise jobs only18:21
jeblairi'm not keen on the infrastructure team deciding openstack's support policy...18:21
clarkb++18:22
*** mikal has quit IRC18:22
mordredjeblair: totally18:22
clarkbto jeblairs comment18:22
* mordred takes off infrastructure hat, puts on normal openstack dev hat "why do we care about stable -1?"18:22
* mordred puts infrastructure hat back on18:22
clarkbI don't want to make the decision. but do want to talk about the considerations that need to be made surrounding support18:22
*** mikal has joined #openstack-infra18:23
fungibodepd: clarkb: found it... "Ruby Bug Warning: Ruby 1.9.3-p0 has bugs that cause a number of known issues with Puppet 3.2.0 and later, and you should use a different release. To the best of our knowledge, these issues were fixed in the second public release of Ruby 1.9.3 (p125), and we are positive they are resolved in p392 (which ships with Fedora 18). Unfortunately, Ubuntu Precise ships with p0 for18:23
fungisome reason, and there’s not a lot we can do about it. If you’re using Precise, we recommend using Puppet Enterprise or installing a third-party Ruby package."18:23
fungifrom http://docs.puppetlabs.com/puppet/3/reference/release_notes.html#puppet-32018:23
jeblairmordred: at the risk of running a circular argument, because there is a team of people who (claim they) care about stable -1.18:24
mordredjeblair: yeah. nod18:24
jeblairmordred: but yeah that's the not-infrastructure-hat question18:25
mordredjeblair: more immediatley imporant - what do you think of sdague's suggestion that we run the pg/qpid tests on fedora and stop running them for stable -118:25
*** pcrews has quit IRC18:25
jeblairmordred: the idea of running fewer tests on stable-1 over time bothers me.18:26
mordredpremise being the being broken on fedora is more costly thatn stable -l1 possibly being untested in the postgres/qpid combo18:26
jeblairmordred: being broken on latest fedora, which is also something we 'support' also bothers me.  to be fair.18:26
mordredyeah18:27
mordredalso, the _way_ we're broken on fedora is definitely something that running d-g there would have caught18:27
*** zul has quit IRC18:28
jeblairmordred: if openstack is impossible to run on centos6, then, ah, it seems like someone has broken our support policy.18:28
mordredjeblair: :)18:28
mordredjeblair: I believe it's impossible to test neutron for real on centos618:29
*** pcrews has joined #openstack-infra18:29
mordredjeblair: due to too old kernel18:29
*** sarob has quit IRC18:29
*** sarob has joined #openstack-infra18:29
jeblairmordred: when you say stable-1 which of the current stable releases do you mean?18:31
sdaguejeblair: folsom18:31
mordredfolsom18:31
jeblairit's one thing to test fedora on master and the most recent stable but not older than that; but it's another thing to stop testing other things, eg postgres, on older releases.18:33
*** sarob has quit IRC18:34
sdaguejeblair: well we could do that with precise18:34
sdaguejeblair: or equiv18:34
jeblairso neutron really doesn't work on rhel at all?18:35
apevecnetns doesn't work w/ vanilla rhel kernel18:35
sdaguejeblair: not in the ways people want to use it, without an updated kernel18:35
sdagueright, exactly18:35
sdaguejeblair: rhel6 kernel is 2.6.3218:36
jeblairsdague: yes, though it's more complicated than that because they backport ALL KINDS of stuff in their kernels18:36
apevecthere's netns patches rhel6 kernel provided in RDO18:36
sdaguein 6.4 they backported openvswitch into it (which didn't exist in that kernel), but network namespaces is still not in the main kernel18:36
apevecs/patches/patched/18:36
jeblairso can we use an rdo kernel?18:37
sdaguejeblair: so I think we'd be tripping over distro issues way more if we went down that path18:37
sdaguejeblair: ok, so then what are we testing? nothing any developer is using :)18:37
jeblairsdague: what do you mean?18:37
*** mrmartin has joined #openstack-infra18:38
mrmartinre18:38
jeblairsdague: presumably something someone is deploying, since it's what the tc decided we support, presumably with reasons.18:38
sdaguejeblair: we said we would try not to break it18:38
jeblairi don't think we tried very hard18:39
sdaguejeblair: well when you can't use openvswitch namespaces18:39
sdaguebecause the distro doesn't support it18:39
sdagueyou are kind of done18:39
apevecBTW, how come I got quantum-2013.1.3.tar.gz while snaps were neutron-stable-grizzly.tar.gz ? http://tarballs.openstack.org/neutron/?C=M;O=D18:39
*** pcrews has quit IRC18:39
sdaguejeblair: and, honestly it doesn't solve the problem I actually want to solve, which is whether devstack works on fedora18:40
sdaguewhich we've got 4 people a day popping into channels asking about18:40
sdaguebecause right now it doesn't18:40
sdaguebecause we broke it18:41
sdaguebecause we don't run it in the gate18:41
jeblairsdague: i see the value of testing master on fedora.18:41
sdagueand fixing it on centos 6 wouldn't mean it's fixed on fedora, the drift is too far18:41
sdaguejeblair: ok, so that's actually all I really want to fix, having master on fedora. That should give us other options down the road as well18:42
jeblairsdague, mordred: so the last time we talked about this, i think we all acknowledged it is a really hard problem, and we did a lot of work and it took a design summit session to hash it out.18:42
sdaguejeblair: so it would clearly be dependent on a volunteer from the redhat side to get us through the hard work18:42
jeblairsdague, mordred: i think it's worth exploring how we can test on fedora, but i also don't want to throw out the extensively considered position that we came to.18:43
jeblairsdague, mordred: so maybe hashing out long-term support plans is premature at this point18:43
sdaguehowever, I wanted to at least pave the way to make sure there is nothing preventing them from making progress on it18:43
*** pabelanger has quit IRC18:43
jeblairsdague, mordred: and we just say that the low-hanging fruit of just getting one devstack run on fedora for master running is a good short/medium term goal.18:44
sdaguejeblair: I'm happy with that18:44
jeblairi mean, it's not really low-hanging, but it's the lowest of what we've got18:44
sdagueyep18:44
sdagueit would give us options though18:44
sdagueto explore from there18:44
jeblairbecause there's a huge puppet issue to deal with; one that we weren't expecting to work on this cycle18:44
sdaguejeblair: agreed18:44
jeblaircool18:45
jeblairlunchtime now18:45
sdagueit's just we, as a project, have moved from canonical being dominant distro and doing lots of work, to red hat doing a ton of work18:45
sdagueand us breaking fedora by accident is becoming an uncool thing18:45
sdaguewith all of them trying to contribute18:45
jeblairsdague: yep18:46
fungiso, from a fedora 18 standpoint, i was able to get a basic jenkins slave working with our current puppet infrastructure with the exceptions of some supposedly benign warnings from puppet agent runs and an inability to generate puppet reports into the dashboard. i think neither of those is a concern for devstack slaves (we don't repeatedly run the puppet agent from cron and we don't report from them)18:46
fungiso at this moment, we can spin up fedora 18 machines with those characteristics/minor drawbacks18:47
*** pabelanger has joined #openstack-infra18:47
jeblairfungi: we might be able to live with that18:48
*** psedlak has quit IRC18:48
fungias to devstack-gate and devstack work needed on top of that, i don't know the answer at the moment18:48
fungiand of course, fedora 19 being just around the corner (?) i don't know what new hurdles that is likely to bring18:49
fungior i guess it's out now? 2013-07-02 according to http://fedoraproject.org/wiki/Releases/19/Schedule18:50
mordredfungi: git log --color=auto --decorate oneline pyghmi --not remotes/gerrit/master18:50
mordredfungi: yeah - 19 is out18:50
mordredfungi: that line above was posted by someone in #openstack-ironic18:50
mordredwhich seems ... oh - --decorate oneline18:50
mordredI see it18:50
mordrednevermind18:50
mordrednope. mind again18:51
mordredfungi: git log --color=auto --decorate oneline18:51
mordredfatal: ambiguous argument 'oneline': unknown revision or path not in the working tree.18:51
fungithere is a --oneline option to log18:52
fungisame as --pretty=oneline18:53
mordredyes18:53
mordredbut above it's missing a --18:53
mordredI see the -- in trunk and in the versoin installed in my machine18:53
*** pcrews has joined #openstack-infra18:54
fungino clue what pyghmi is18:54
fungimord trunk of and version of what installed on your machine?18:55
fungimordred: ^18:55
fungiahh, you're talking about git-review18:55
fungii see a similar command line in there, yeah18:56
sdaguefungi: f19 is out18:56
mrmartinjeblair: do you have a few minutes to move forward the community portal project?18:56
mordredmrmartin: he's at lunch18:57
mrmartinoh really, lunch time18:57
mrmartinthe sun just gone down here18:58
*** zyluo has quit IRC18:59
sdagueoh man, finally done with meetings. so mordred the behavior we should have in update.py is to take dev-requirements.txt into account, and allow those as optionals?19:00
*** thomasm has joined #openstack-infra19:01
*** melwitt has joined #openstack-infra19:02
mordredsdague: yes. I think so - if the line matches  dev-req, we shoudl not replace it19:02
*** ruhe_ has joined #openstack-infra19:02
mordredsdague: however, here's teh real kicker - how do we deal with updates to dev-req, which would necessarily mean that everyone would not match it, and then probably get repalced with the old value?19:03
*** _TheDodd_ has quit IRC19:04
*** dina_belova has joined #openstack-infra19:04
*** sarob has joined #openstack-infra19:06
*** ^d is now known as ^demon|lunch19:07
*** sarob has quit IRC19:07
*** sarob has joined #openstack-infra19:08
*** thomasbiege has quit IRC19:10
*** _TheDodd_ has joined #openstack-infra19:11
*** sarob has quit IRC19:12
*** ruhe_ has quit IRC19:14
sdaguemordred: hmmmmmm19:16
sdaguehow good is our version parsing?19:16
sdaguelet me go play with code for a bit19:16
sdagueunrelated question19:17
*** pcrews has quit IRC19:17
sdagueto get on stackforge does the project need to sign up for the CLA and be Apache2?19:17
lifelessjog0: mmm, so I understand the mechanics you're proposing but not the motivation19:19
jog0lifeless: because every few weeks someone tries to modify .gitignore for yet another editor19:20
lifelessjog0: the only reasons I can imagine not wanting a particular file type in the project ignore is: a) makes git slow or b) will inappropriately ignore something someone would want to see in 'git status'19:20
jog0lifeless: it also makes the .gitignore files big enough that people don't really think if something should be there or not19:20
lifelessjog0: there's a limited set of editors, we could just bulk add them all. And - whats the issue, just say yes, if it makes the life of your contributors easier ?19:20
lifelessjog0: that comes back to b),yes?19:21
jog0for example should 'keeper' be in nova gitignore?19:21
clarkbsdague: no, I dont think we have solid rulea but I think open source is sufficient19:22
clarkbjeblair ^19:22
*** ruhe has joined #openstack-infra19:22
jog0also it just keeps things cleaner and prevents the issue of having to update gitignore for every project all the time19:23
*** dina_belova has quit IRC19:23
lifelessjog0: I simply don't understand the issue19:23
lifelessjog0: someone *else* proposes the update, 2 cores agree it makes sense for .gitignore, done.19:23
mordredsdague: no. it does not19:23
mordredopen source19:23
lifelessjog0: maybe 60 seconds of thought from them both, and move on.19:24
*** pcrews has joined #openstack-infra19:24
lifelessjog0: nova's .gitignore has changed 24 times.19:24
lifelessjog0: nova has > 20K commits19:25
lifelessjog0: 1 in 1000 are .gitignore : how is that an issue ?19:26
*** adalbas has quit IRC19:29
*** pcrews has quit IRC19:32
*** mrodden1 has joined #openstack-infra19:35
*** mrodden has quit IRC19:36
*** sarob has joined #openstack-infra19:36
jog0lifeless: it comes down to it seems like a non-optimal way to do it19:37
jog0I am not going to -1 the patch, its not worth that19:37
*** dina_belova has joined #openstack-infra19:37
jog0lifeless: so if you get to other cores to +2 it I am fine with it19:38
lifelessok19:38
lifelessthanks19:38
jog0lifeless: I was worried that I -1ed it for a second.19:38
jeblairmrmartin: hi there19:38
*** sarob has quit IRC19:39
*** _TheDodd_ has quit IRC19:39
jeblairmrmartin: how can i help?  would you like one of us to make the initial commit that sets up the server class in puppet, then you can work on it from there?19:39
*** sarob has joined #openstack-infra19:39
lifelessjog0: I thought you had19:39
lifelessjog0: :)19:39
*** nayward has quit IRC19:40
jog0lifeless: so did I19:40
jog0from the way you were asking19:40
lifelessjog0: sorry for the stress!19:40
*** dina_belova has quit IRC19:41
* fungi should have popped some popcorn for that one19:43
*** sarob has quit IRC19:43
*** adalbas has joined #openstack-infra19:44
jog0lifeless: haha it keeps me on my toes19:44
fungiclarkb: if you get a moment to glance at https://review.openstack.org/38176 (not sure if you're near a big enough screen) can you tell me whether i'm making sense?19:45
*** vipul is now known as vipul-away19:46
*** gyee has joined #openstack-infra19:47
*** changbl has quit IRC19:48
*** _TheDodd_ has joined #openstack-infra19:48
*** changbl has joined #openstack-infra19:50
clarkbfungi yeah jjb should treat that as a string literal I think19:50
openstackgerritSean Dague proposed a change to openstack/requirements: use dev-requirements for global sync  https://review.openstack.org/4094719:51
clarkbfungi but a subshell should work too19:52
sdaguemordred: ok, that solves the neutron problem19:53
sdaguehowever, there is a more general problem there19:53
*** annegentle_vacay has quit IRC19:53
mordredsdague: yeah?19:53
sdaguemordred: the 1.2.0b519:53
fungiclarkb: i wonder how deep the rabbit hole goes if i try to fix the parser to not error on that during the comparison tests (since it still seems to be able to parse it under normal production circustances)19:54
sdagueso what I did is just say if you are exactly in dev-requires, you can use it19:54
sdagueotherwise we set to g-r19:54
mordredwell - so maybe it's not a problem19:54
sdaguesee what you think19:54
mordredif you aren't matching, devstack is going to make you match19:55
mordredfor devstack19:55
sdagueyeh, it actually means we reintroduce skew, in theory in devstack19:55
mordredthen requirements update will generate a commit that will reset you back down to the normal19:55
sdaguehowever, in practice, we don't19:55
sdaguebecause it's olso19:55
sdagueoslo19:55
clarkbfungi idunno. may need to pdb again19:55
sdaguewhich we're using git on anyway19:55
mordredexactly19:55
sdaguemordred: but this was actually a unit test problem19:55
mordredright19:56
mordredthe unittests will then fail on the proposal to bump you back down19:56
sdagueso this will let them go through19:56
mordredbut then a human can amend that change to set it to the new g-r version19:56
sdagueyep19:56
sdagueso we can navigate with these changes19:56
mordredyah. and eventually we'll get wheels up19:56
sdagueit's just a little more manual when someone bumps dev-req19:56
mordredhow abou t...19:57
sdaguebut it won't ruin anyone19:57
mordredwe don't do automated requirements proposal jobs19:57
mordreduntil we get rid of d-r?19:57
mordredby publishing pre-release wheels19:57
sdaguemordred: yep, sounds fine to me19:57
mordredcool. it's a plan19:57
lifelessmordred: dunno if you saw my run-mirror timings :)19:58
mordredlifeless: I did not - did you do one with wheels?19:58
lifelessmordred: no. But - having done a full mirror, an incremental run was 40m19:59
lifelessreal    39m4.291s19:59
lifelessuser    6m33.628s19:59
lifelesssys     0m46.968s19:59
*** sandywalsh has quit IRC19:59
mordredlifeless: wait- it took you 40m to run run-mirror?19:59
lifelessmordred: yes.19:59
lifelessmordred: latency. NZ. HTTPS spidering.20:00
mordredwow20:00
mordredI thnk it takes us 820:00
lifelessyes20:00
lifelessThis is why I was telling you it was going to be slow.20:00
lifelessBecause, well, it is.20:00
lifelessLike you know Mysql innards, I know replication and HTTP :)20:00
lifelessdstufft has a recipe to avoid the external links except for specific packages20:01
lifelesswhich I'll play around with shortly20:01
lifelessbut I don't expect it to 'fix' it to be fast enough to be inline with a build (but rsync will be)20:01
*** vipul-away is now known as vipul20:02
*** mrmartin has quit IRC20:02
sdaguedtroyer: you about?20:05
*** pabelanger has quit IRC20:06
sdaguewanted to get to the bottom of the devstack fedora fix, and if we have one that everyone can like20:06
openstackgerritJames E. Blair proposed a change to openstack-infra/devstack-gate: WIP: new nodepool  https://review.openstack.org/4095220:09
jeblairmordred, clarkb, fungi: do (some of) you have a minute to take a look at https://review.openstack.org/40952 ?20:10
jeblairit's a skeleton for the new nodepool code20:10
*** emagana has quit IRC20:10
jeblairand i want to double check the approach20:10
mordredjeblair: looking20:10
*** sandywalsh has joined #openstack-infra20:10
*** emagana has joined #openstack-infra20:11
jeblair(though it basically works without actually touching any servers or images at this point; that code is fairly well established, so next up is basically plugging the old stuff into the new)20:11
fungii could stand a break from trying to wrap my head around jjb's parameter replacement recursion, sure20:12
*** locke105 has quit IRC20:13
jeblairNodePool is the interesting class; it has a gearman worker (NodeUpdateWorker) that responds to gearman events that i expect zuul to send when a job starts or stops on a devstack (or any) node.20:14
jeblairwhen the worker gets a complete event, it spawns a thread to cleanup (currently: delete) the server20:14
fungioh, 40952 reminds me that i meant to look into why hold status didn't work for me the last time i tried it (since some of the recent refactoring), but i guess this will obviate that anyway20:14
sdagueso anyone else want to +2 this - https://review.openstack.org/#/c/39967/20:15
jeblairfungi: yeah, in this, hold should hold forever20:15
sdagueit's blocking checks for people, as they don't pass pep820:15
fungii *think* currently one of the update scripts isn't checking for hold and is resetting it to delete20:15
jeblairthe nodepool's main thread runs in a continous loop that currently does what the launch job does (calculate deficit and launch nodes).  but it spawns a thread for every machine it launches20:16
jeblairthen there are two functions that get called periodically; one to update images, and then one to delete anything that we might have missed somehow (and also delete old images).20:17
*** mrodden has joined #openstack-infra20:17
jeblairboth of those correspond pretty closely to the update image and reap jobs, except this reap function should only need to run every few hours, since most deletions will be handled by the gearman worker20:17
fungisdague: that checks out, so approved20:18
jeblaira possible problem is that if there are a lot of threads running at once, we might hit rate limit errors with openstack; but i think the best approach is to just play the odds there and retry (with sleeps) if needed.20:18
*** locke105 has joined #openstack-infra20:19
fungijeblair: so the per-launch threads only stick around until the machine is into a ready state, or persist until machine deletion?20:19
jeblairfungi: until it's ready, then they exit20:19
fungik20:19
jeblairfungi: then new per-delete threads are spawned by the gearman worker when it gets notified a job is finished20:20
jeblairoh, and of course, this presupposes the new gearman-plugin disable-on-complete feature is being used to protect against duplicate runs20:20
fungiokay, so the thread persists from the time the task is initiated until it gets a completion response?20:20
*** mrodden1 has quit IRC20:20
sdaguefungi: you want to tackle the one of top of it as well20:21
fungisdague: sure, why not20:21
jeblairfungi: yeah, it'll poll continuously.  we can probably give it, say, a 30 minute insane-cloud-provider timeout too.20:21
openstackgerritSergey Lukjanov proposed a change to openstack-infra/reviewstats: Add savanna to projects  https://review.openstack.org/4095320:21
*** vipul is now known as vipul-away20:22
fungijeblair: ahh, makes sense. i was figuring we'd need an escape hatch there because, well, clouds20:22
*** dkranz has quit IRC20:23
fungibut still, too many insane cloud provider incidents and we could see a huge pile of threads20:24
mordredjeblair: generally makes sense20:24
mordredjeblair: also, I like that it is modular enough that I can imagine where a dib workflow would plug in20:24
jeblairmordred: excellent20:24
fungior i guess the pool limit will keep the thread count from getting too high, i guess we just might wind up with no machines because none are actually launching. and that's already happened before so not exactly a regression20:25
apevecinteresting, how did that happen? change-id hash collision https://review.openstack.org/#/q/I130528ae946e8888d35c25e468b4ea6ac29db0cf,n,z20:25
apevecexactly in the example I have in https://wiki.openstack.org/wiki/StableBranchRelease#Rinse.2C_Repeat20:25
jeblairapevec: i wonder where Dirk got his change-id from20:27
jeblairperhaps he copied it from the other change.  or perhaps he should buy a lottery ticket.20:27
apevecyep :)20:27
fungiyeah, 31377 came later and very well may have been copied from 28741 (the milestone bump on the same project)20:28
apevecbut usually you just let hook generate it20:28
apevecwhy would you copy it20:28
fungiit would be faaar from the first incident of commit message copy/paste induced errors i've seen involving change-id headers20:28
sdaguedtroyer: how are you feeling about landing your devstack fix for fedora, and doing the other cleanups later?20:29
apevecfungi, bump was on stable branch, this commit is on master20:29
jeblairmordred, fungi: ok, i'm going to continue to hack in that general direction20:29
fungiapevec: the why doesn't matter so much. i've seen it from poorly edited squashes, backports/forwardports or anything which might include old commit message data. also simply possible gerrit uses a very bad prng20:30
apevecyeah, whatever20:30
fungijeblair: definitely. still reading through but looks good so far20:31
apevecI'll change example in wiki :)20:31
fungiapevec: oh! you did say it was in the wiki20:31
apevecheh, copying from wiki would be even stranger20:31
fungiapevec: he almost certainly copied it from the wiki when he tried to do something without having a commit hook installed, gerrit told him he needed a change id, and so he set out to look for one ;)20:31
jeblairAhhh20:32
dtroyersdague: [back from lunch]  I'm ready for the install_pip.sh patch to go in.  it isn't complete but unblocks the next level of stuff20:32
sdaguecool, I'm good with it especially given how many folks it's blocking20:32
*** ^demon|lunch is now known as ^d20:33
sdaguedtroyer: however, I realized there is actually a problem with mordred's requirements update method20:33
sdaguewhich is reclone on requirements repo20:33
sdagueand those updates won't take in the trees20:33
sdaguebecause they are changed20:33
dtroyerI think there are other problems too but am stuck on something else at the moment to chase it down.  that's one reason I wanted a flag20:34
mordredsdague: gah20:34
sdaguedtroyer: yeh20:34
sdagueI'm wondering if what we actually want to do is have update.py take a flag to update to another place20:34
sdaguethen install that file20:34
sdaguethen we aren't changing git repo files20:35
dtroyeri think that would solve what I saw too20:36
sdagueok, I'll try to tackle that tomorrow20:36
*** sarob has joined #openstack-infra20:39
*** ruhe has quit IRC20:41
*** dina_belova has joined #openstack-infra20:42
*** vipul-away is now known as vipul20:43
*** dina_belova has quit IRC20:46
*** pcrews has joined #openstack-infra20:47
*** woodspa has quit IRC20:47
*** dina_belova has joined #openstack-infra20:52
*** jpich has quit IRC20:52
*** SergeyLukjanov has quit IRC20:54
*** SergeyLukjanov has joined #openstack-infra20:54
*** dina_belova has quit IRC20:56
*** thomasm has quit IRC20:58
*** ArxCruz has quit IRC20:58
*** svarnau has quit IRC21:01
*** sarob has quit IRC21:01
*** sarob has joined #openstack-infra21:02
*** rfolco has quit IRC21:06
*** sarob has quit IRC21:07
*** apevec has quit IRC21:09
openstackgerritA change was merged to openstack/requirements: Add pep8 checks  https://review.openstack.org/3996721:11
*** krtaylor has joined #openstack-infra21:13
openstackgerritA change was merged to openstack/requirements: Update ourselves to ourselves  https://review.openstack.org/3996321:16
openstackgerritA change was merged to openstack/requirements: Remove unneeded tests dir reference  https://review.openstack.org/4000221:16
openstackgerritJeremy Stanley proposed a change to openstack-infra/jenkins-job-builder: Handle KeyError in deep_format()  https://review.openstack.org/4097321:20
*** cody-somerville has quit IRC21:20
*** cody-somerville has joined #openstack-infra21:21
bodepdjeblair: you have a sec?21:22
bodepdor anyone can answer: I have some questions about what will happen when: https://review.openstack.org/#/c/37715 gets merged21:22
fungibodepd: there will be a coordinated gerrit outage to actually perform the rename during a low-activity period21:24
fungibodepd: http://ci.openstack.org/gerrit.html#renaming-a-project21:24
bodepdfungi: ok. what about the old project in github? it will still exist with redirects?21:24
fungithat's the general process we follow21:25
bodepdfungi: thanks!21:25
*** sarob has joined #openstack-infra21:25
fungidevelopers consuming the old remote names should be urged to update them21:25
fungigithub doesn't provide project redirects afaik21:25
fungiwe usually rename the project directly in github21:26
bodepdthat is what I am trying to figure out.21:26
fungiand then we tell everyone to use the new name21:26
bodepdI just merged quantum->neutron21:27
bodepdbut now,all tests will be broken21:27
fungiusually at least some subset of users are taken by surprise when it happens, don't subscribe to relevant mailing lists, whatever21:27
bodepdb/c puppet can't load modules from teh wrong project21:27
bodepdso, I'm in an inconsistent broken state21:27
bodepdas of 1 minute ago (or at least I'm pretty sure I am)21:28
fungibodepd: mmm, so tests passed on the change itself, but the change breaks future test runs once merged? that seems like a missing test21:28
*** dansmith has quit IRC21:28
fungione exit strategy there is to have a gerrit admin manually merge a revert commit for that change21:29
fungiand then come up with additional tests to prevent similar breakage in the future21:29
*** vipul is now known as vipul-away21:31
jgriffithanybody else encountering funny things trying to install test-requirements?21:31
jgriffithie: http://paste.openstack.org/show/43630/21:31
fungidid this just suddenly start? is that timestamp on line #2 utc or mountain time?21:32
jgriffithfungi: mountain21:32
bodepdfungi: the problem is that puppet-quantum is actually broken atm21:32
jgriffithfungi: I've been having weirdness last night and today21:33
fungiso just a minute ago then21:33
bodepdfungi: b/c all of the class names are nuetron::x, so they cannot be loaded21:33
jgriffithfungi: correct21:33
jgriffithoddly latest devstack attempt seemed to come up21:33
bodepdfungi: https://github.com/blog/1508-repository-redirects-are-here21:33
fungiooh!21:33
jgriffithhowever there I'm seeing a bunch of failures tryign unit tests21:33
jgriffithdue to subunit parser FAIL21:33
jgriffith???21:33
fungithe ooh was for github project redirects finally existing21:34
jgriffithand I tried copying the *new* requriements files that devstack mods over as well21:34
*** dansmith_ has joined #openstack-infra21:34
jgriffithdarn :)21:34
fungijgriffith: i think ekarlso- pasted something similar this morning... looking back in my scrollback21:35
bodepdfungi: can we rename the repo by transfering?21:35
bodepdfungi: so that it will rediret?21:35
*** dansmith_ is now known as dansmith21:35
bodepdfungi: that would make my life pretty simple today :)21:35
fungijgriffith: http://pastebin.com/ZeLWUq2c21:35
bodepdfungi: just reviewed that doc. that is the way you already do it :)21:36
fungibodepd: well, we still need to schedule an outage for gerrit to do the renaming21:36
bodepdfungi: can we just rename it in github first?21:36
*** nayward has joined #openstack-infra21:36
jgriffithfungi: interesting... so that might be similar to what I get when trying to pull in a review and run_tests.sh on it21:36
bodepd(this shoudl work if the redirect works)21:36
fungibodepd: we will continue replicating to the old remote name21:37
bodepdwhich is redirected to the new one21:37
bodepdfungi: ^21:37
fungibodepd: also i think anyone trying to commit changes to gerrit will get rejections if they try to use the new name21:37
bodepdfungi: we will update the gitreview config file last21:38
bodepdand time that with the outage21:38
fungiit's worth trying...21:38
jgriffithfungi: hmmm... nova has the same problem21:38
bodepdfungi: I'm just spitballing here,so that I can get tests passing21:38
bodepdfungi: and give you guys time to prepare for the outage21:38
jgriffithok, I'll poke a bit, see if all the tests fail in Nova as well like they do in Cinder21:38
bodepdfungi: and even if it breaks, everything is broken anyways21:38
fungijeblair: mordred: clarkb: thoughts on whether a github project rename (given the new redirect functionality mentioned in the https://github.com/blog/1508-repository-redirects-are-here announcement) would present any immediate issues?21:39
*** annegentle has joined #openstack-infra21:40
*** nayward has quit IRC21:40
bodepdfungi: let me know. I'm about to send out the 'everything may explode' email21:43
jeblairfungi: not immediately21:44
fungiokay, wanting to get a little consensus before i go potentially making things harder on us because i didn't think something through21:44
bodepdfungi: I agree. I'm pretty sure it's going to work, but I also just put a cowboy hat on21:44
fungijeblair: any concerns with me renaming stackforge/puppet-quantum to stackforge/puppet-neutron on github now, in advance of a later outage to rename it on gerrit at some convenient date and time?21:45
fungithe way i read that, github should continue to see our mirror updates to -quantum and reroute them to -neutron accordingly21:46
clarkbfungi: we don't use pages anymore and everything else should just work (tm)21:46
fungiseems to be the theory at any rate21:47
*** beagles is now known as beagles_biab21:48
*** dina_belova has joined #openstack-infra21:52
*** markmcclain has quit IRC21:54
*** dina_belova has quit IRC21:57
jeblairfungi: oh, erm, i'd rather not do that21:58
jeblair(a) confusion (b) manage_projects uses the github api; i'd rather not test that in production21:59
jeblairalso, i don't think we've even scheduled the gerrit rename yet?21:59
fungiafaik we have not, no21:59
*** SergeyLukjanov has quit IRC21:59
openstackgerritgordon chung proposed a change to openstack/requirements: add pycadf library  https://review.openstack.org/4092621:59
jeblairfungi: i thought you meant doing the rename during the gerrit downtime22:00
fungibodepd was hoping this would get him out of a scrape, but maybe the easier path forward is to help him revert changes or turn his tests non-voting long enough to revert commits himself22:00
jeblairfungi: yeah, if something goes wrong with manage projects, we could have a _big_ cleanup on our hands.  i'd recommend those other ideas.22:01
*** vipul-away is now known as vipul22:01
bodepdjeblair: an even crazier question is could I have differnet branches point at different repos22:03
bodepdjeblair: fungi you guys must be doing this over and over again for neutron?22:03
jeblairbodepd: we did it once22:04
fungibodepd: for the official repositories we took one giant outage to rename everything everywhere it touched ci/infra22:04
fungiand then let the individual projects referencing quantum clean things up internally after the fact22:04
bodepdare there not a ton of peripheral projects that still ahve to do the same thing?22:05
fungithere were transitional bootstrapping packages with a new release of the old name and other things to help that along22:05
fungii think the only other stackforge project with "quantum" in its name besides yours may be the chef cookbook for quantum and it hasn't renamed yet that i've noticed22:06
*** burt has quit IRC22:07
jeblairfungi: it's 'networking'22:07
fungioh, so it is22:08
jeblairthey dodged that one i think.22:08
fungiindeed22:08
clarkbya, which is why one of my suggestions when the puppet folk were looking at this was to switch to service name and not projects names22:09
bodepdyep22:09
clarkbdprince didn't like that iirc22:10
clarkbI think consistency may have been part of that decisions, it would be inconsistent or you ahve to do that same to all of the other projects22:10
bodepdis it the project name that determines what repo to clone to?22:12
*** mriedem has quit IRC22:12
bodepdhow is openstack core handling the fact that stable/grizzly branches need to be pushed to quantum and not neutron?22:12
clarkbthey are pushed to neutron22:12
bodepdthat is the last piece of the puzzle that is confusing me22:12
bodepdI thought the whole point of stable branhces is not to break backwards compat22:13
bodepdthat seems like a massive break22:13
bodepd(as in, your code is gone)22:13
clarkbiirc it is backward compat because the repo says neutron but hte code says quantum22:13
clarkbits just a name22:13
bodepdwell, it's a location.22:14
bodepdso,any script would expect to download code (potentially) and then use it22:14
bodepdI guess it's way more problematic with puppet (or is it...)22:14
clarkbanyone dealing with source should expect to have these problems22:14
clarkbif you deal with releases nothing changes22:15
bodepdthen why do you need branhces?22:15
bodepdif everyone can reliably deal with released versions for everything22:15
bodepdanyways,I'm not being productive, just arguing circular logic22:15
*** markmcclain has joined #openstack-infra22:16
bodepdfungi: I don't mind if the build/test machine is down for a little while, I just need to know when it can get back up.22:18
*** changbl has quit IRC22:18
bodepdjeblair: what about just merging this: https://review.openstack.org/#/c/3771522:19
bodepdjeblair: and I will just fix everything when it blows up?22:19
bodepdjeblair:  and the gerrit/github names will be out of sync until you guys have time to clean it up22:20
clarkbI am not arguing that everyone can use released versions and the branches are there to support released versions22:21
clarkbbut source repos move22:21
clarkbeither from bzr to git or from name/foo to name/bar22:21
fungibodepd: some of that will tell manage-projects to create a new empty project called puppet-neutron, with everything that entails (local repo, github mirror, et cetera)22:22
fungiand then we won't be able to easily perform the rename itself22:22
bodepdfungi: and the verdict is no on a manual rename?22:22
bodepdfungi: without downtime/associated changes in gerrit22:23
fungibodepd: the steps we normally follow involve ninja-coordinating the merger of that change with offlining gerrit to run a bunch of update queries on its database amd move things around on the filesystem22:23
fungidoing those tasks at different times wouldn't really work. you'd end up with divergence22:24
bodepdfungi: let me know when you guys could do it, so I can send a notice that the project is going to stop until then22:24
mgagneare you saying that we should have better planned the rename and sync with infra? =)22:24
*** weshay has quit IRC22:24
fungiwith a proper move, the review history and open reviews get repointed to the new name, peoples watch lists in gerrit get updated, et cetera22:24
bodepdmgagne: yep. for some reason, I thought it had all been thought through22:25
fungiand we move/rename the remote clones at the same time, all before briging gerrit back online22:26
fungiit really doesn't handle having those sorts of things changed out from under it live22:26
fungibodepd: i take it you can't just revert the commits which did the name change inside the puppet module until the project rename happens?22:27
*** fbo is now known as fbo_away22:29
bodepdfungi: I think we have a workaround to take the pressure off22:32
*** ^d has quit IRC22:32
fungithat's excellent news!22:33
*** vijendar has quit IRC22:33
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Gate jeepyb and openstack/requirements on pbr  https://review.openstack.org/3817622:35
jeremybfungi: pbr?22:37
fungii think that ^ should work around the validation false positive22:37
fungiuntil the jjb change can be groomed to fix the parser22:37
fungijeremyb: what about pbr?22:38
jeremybfungi: is that a beer or?22:39
fungihttp://github.com/openstack-dev/pbr (python build reasonableness)22:40
jeremybok, notbeer22:40
fungipbr is definitely not beer22:40
jeremyb:)22:40
fungii've drank it before22:40
fungidefinitely not beer22:40
fungi"yeast soda" is perhaps the best term i have for that class of beverage22:40
jeremybfakebeer? :)22:40
jeremybi've had it maybe twice. don't really remember it22:41
*** afazekas has quit IRC22:41
clarkbhey now, pbr and rainier are an important part of the NW beer market22:41
jeremybi like natty bo22:41
clarkboh no22:41
jeremybnatty boh*22:42
*** adalbas has quit IRC22:43
*** afazekas has joined #openstack-infra22:44
*** sarob has quit IRC22:45
*** datsun180b has quit IRC22:45
*** sarob has joined #openstack-infra22:46
*** _TheDodd_ has quit IRC22:47
*** prad has quit IRC22:47
jeblairgah22:48
jeblairclarkb, mordred: hpcloud has still not fixed the "can't have dots in a keypair name" bug22:48
jeblairso, uh,22:48
jeblairopenstackjenkins2 now has a keypair we can't delete22:48
*** sarob has quit IRC22:49
clarkb:/22:49
jeblairi'll open a support ticket to delete it22:49
clarkbjeblair: are you doing that with a CLI client or the web UI or both?.22:49
fungiick22:49
jeblairclarkb: both22:50
jeblaircase opened22:51
* fungi assumes they rolled their own access key management there22:51
clarkbiirc HP keystone is not keystone22:51
jeblairbtw, i opened a support ticket loooong ago about the problem in general22:51
openstackgerritSean Dague proposed a change to openstack/requirements: use dev-requirements for global sync  https://review.openstack.org/4094722:53
fungii love opening a ticket with a provider about "your system breaks when i try to do this" and it's promptly closed with "i went ahead and took care of it for you"22:53
*** dina_belova has joined #openstack-infra22:53
jeblairno kidding.  there should be a support tracker _and_ a bug tracker.22:54
*** rcleere has quit IRC22:54
*** vipul is now known as vipul-away22:55
*** vipul-away is now known as vipul22:55
*** dina_belova has quit IRC22:58
*** jrex_laptop has joined #openstack-infra23:00
fungithat split tends to not work particularly well in a service provider portal because most customers don't know the difference and pick one at random, but it is definitely possible for the people triaging tickets to be able to identify the difference between a bug report and a support request and route them to the correct places23:03
*** sarob has joined #openstack-infra23:07
*** pentameter has quit IRC23:08
lifelesswhy does glanceclient depend on 'setuptools-git' ?23:09
lifelessit's breaking pbr - http://logs.openstack.org/69/40869/1/check/gate-pbr-devstack-vm-rawinstall/d79baff/console.html.gz23:09
lifelessjeblair: fungi: agreed that the split doesn't work well - in fact I think its artificial and driven by the poor capabilities of most? all? bug trackers.23:10
lifelessthere's a continuum and any single report should be able to segue between23:10
fungii'm willing to bet mordred already has a change molding in review to remove setuptools-git dependencies remaining in any projects23:10
clarkblifeless: looks like latest released glanceclient needs setuptools_git but tip of master does not23:11
clarkband vice versa for requirements on pbr23:11
fungisounds like they should just release earlier and oftener23:11
lifelesswe can't land changes in pbr at all until this is resolved....23:12
bodepdjust let me know when you guys are going to do that maintainance. It will require lots of code changes that need to be coordinated23:12
lifelessbut I don't grok all the moving parts nor long term direction here yet, so I'm going to just go waaaaaah23:12
lifelessand point at mordred23:12
*** rnirmal has quit IRC23:13
clarkblifeless: mordred is a good person to point at. My understanding is that glanceclient should release a new version, once thay have been updated to stop depending on d2to123:15
lifelessIs there an asymmetric gate thing going on here?23:16
lifelessPresumably this worked. How did it stop working ?23:16
clarkblifeless: I don't think it is asymmetric gate, I think it is related to setuptools madness where external forces are breaking us23:16
fungior possibly due to tests using released client libraries instead of vcs23:18
clarkbfungi: I think we flip flopped on that recently23:19
clarkbwe now test with vcs23:19
fungioh?23:19
clarkbyeah because sdague wants to test a known state (++)23:19
fungii knew we wanted to, just didn't know if it had all gotten working yet23:20
sdaguewe're only testing with vcs in devstack gate23:21
clarkbwhich is what the pbr rawinstall should use23:21
sdagueok23:21
sdagueI think we're 100% covered there... except which services does pbr turn on?23:21
fungiand presumably also want vcs dependencies in unit tests instead of our releases?23:21
clarkbit uses the d-g hooks to run its tests after d-g sets everything up23:21
clarkbsdague: I believe it isn't spinning up any services, just relying on the copying of source repos then testing that all of them install23:22
*** pabelanger_ has quit IRC23:23
*** pabelanger has joined #openstack-infra23:23
fungioh, and if project a declares a requirement on project b, we're installing project a from source and project b gets satisfied from released packages i guess23:24
clarkboh ya23:25
clarkbso order is important...23:25
fungiwhich means we need to bootstrap skynet into pbr so it can divine the entire dependency graph before running any of the install tests23:25
sdagueor just trust dtroyer got it right :)23:26
sdaguefortunately... no circ-deps yet23:26
fungiuntil the next time one of the projects decides to declare a new dependency on another of the projects again23:26
sdaguenobody ever changes requirements... :)23:27
sdaguehttp://openstackreactions.enovance.com/2013/08/when-someone-requests-a-feature-freeze-exception/23:28
notmynamemordred: are ya bored? need something exciting to talk about? really just in a good mood and want it to end? I want to talk about swift and pbr https://review.openstack.org/#/c/28892/23:28
* sdague glares at mordred for turning on E125 on requirements repo.....23:29
lifelesswhats E125?23:29
*** sdake_ has quit IRC23:29
clarkblifeless: alignment of line continuations in the if condition23:29
mroddenis it possible to get someone to nuke this from lodgeit? http://paste.openstack.org/show/43635/23:29
mroddenhas some host name info and such that i would rather not be available out there forever23:30
sdagueit is my least favorite pep8 rule. Because it means you can't use emacs indenting.23:30
clarkbimportant to note it is purely a pep8 the tool rule and not a pep 8 the pep rule23:31
mroddenis that the one where you have to have 4 space indent instead of 8?23:31
jeblairi think it should be disabled in the requirements repo23:31
sdaguemrodden: no it's the one that disallows23:31
clarkbpep 8 the pep has examples that contradict pep8 the tool in the pep 8 pep itself23:31
sdagueif (foo23:31
sdague    and bar):23:31
sdague    do_it()23:32
mroddenoh23:32
jeblairmrodden: https://github.com/jcrocholl/pep8/issues/126 for some more light reading23:32
dstufftspace indents in a if condition is bad23:32
mroddenjeblair: lol was just reading that23:32
dstufft4 space*23:32
notmynameit's always so hard to script "when appropriate.." rules. maybe we should switch to coding in TeX and let Knuth handle our formatting23:32
clarkbmrodden: re deleting a paste, I can't do it currently but that data isn't secret imo23:33
clarkbthere is an uber generic hostname with now domain23:33
clarkband a path...23:33
mroddenyeah... i can deal with it23:33
*** vipul is now known as vipul-away23:33
mroddenits just internal CI shit i'm working on23:34
jeblairnotmyname: that would {\it rock}.23:34
clarkbI think the pep8 rule the tool rule exists because the pep8 author must be a vim user. vim's python handling does that by default23:36
*** changbl has joined #openstack-infra23:36
jeblairclarkb: i have no idea what you just said23:36
*** nayward has joined #openstack-infra23:37
clarkbE125 exists because vim does that to your code23:37
jeblairdstufft: so i don't actually care.  when i bring this up, people seem under the misapprehension that i actually have an opinion on this; i don't.23:37
mroddenclarkb is correct...23:37
jeblairdstufft: what i _do_ care about is that there is a standard so that different tools can follow it.23:37
jog0ohh the E125 discussion23:38
fungisee, it's actually a cleverly disguised resurgence of the old vi vs emacs wars23:38
jog0so looking for some reviews on https://review.openstack.org/#/q/status:open+project:openstack-infra/config+branch:master+topic:nomergealerts,n,z23:38
dstufftjeblair: :)23:38
jeblairdstufft: so i am not happy that the pep8 tool does something that contradicts the pep8 spec, and half the tools do one thing, and half the other.23:38
dstufftI don't use any tools tbh23:38
dstuffttypically23:38
jog0jeblairi like how the standard keeps changing, every so often I notice a update to pep8 itself23:38
jeblairdstufft: specs and standards are good.  we should be clear in them and follow them.23:38
lifelesspep8 is a moving target23:39
jeblairlifeless: slowly moving23:39
lifelessjeblair: yes23:39
lifelessjeblair: but moving23:39
lifelessjust blacklisted 'import *' for instance23:39
jeblairalso, i'm okay with standards changing.  otherwise, they'd be irrelevant over time.23:39
dstufftalso not universally good23:39
lifelesswhich is weird, as thats a damn language feature.23:39
* fungi is pretty good at using glaciers for target practice23:39
dstufft:V23:39
lifelessjeblair: yes, things need updating; I wasn't whinging about pep8 evolving.23:40
jeblairone recent change to the pep8 standard was from barry, who made something clear that should have been obvious because all the python code ever did it, but the standard wasn't explicit, so the pep8 tool authors went and did their own thing again.23:40
clarkbdstufft: that is what we have # noqa for :)23:40
mroddeni'm so confused... i have nothing in pip or apt-get but this system thinks i have requests 1.2.3 in my site-packages....23:40
jog0so I thought pep was a python enhanchemnt proposal and I asusmed propsals don't change23:40
*** fifieldt has joined #openstack-infra23:40
jog0after being accepted23:40
dstufftmrodden: lol23:40
dstufftjog0: depends on he type of PEP23:41
dstufftmrodden: there's cases where that can happen23:41
openstackgerritSean Dague proposed a change to openstack/requirements: add option for adding a suffix to output files  https://review.openstack.org/4099523:41
*** nayward has quit IRC23:41
jog0dstufft: I know that now, ...23:41
jeblairdstufft: esp with the recent big changes to pep8, i think either versioning or superceding (rfc-style) might be worth considering23:41
dstufftPEPs have superceding built in23:42
dstufftor rather a mechanism for doing so23:42
dstufftI suspect the PEP8 canges wern't made a new PEP just because of the cultural uh, ca't think of the word, but everyone knows what "PEP8" is, it's the style guide23:42
jog0so we have hijacked 'pep8' ourselves23:43
jog0as our style guide tests are all called 'pep8'23:43
jog0even thought that is a tiny part23:43
clarkbjog0: thats an implementation detail23:43
dstufftand strictly speaking PEP8 is only for the stdlib, but the community took it up and used it elsewhere, but very few projects that do use all of the rules23:44
clarkbjog0: which is easy to fix now that zuul doesn't need to stop everything to reload its config23:44
clarkbjog0: but previously applying that across the board coule have been quite painful23:44
dstufftso the term "pep8" is already super overloaded23:44
*** vipul-away is now known as vipul23:44
jeblairjog0: we can (and probably should/will) rename the jobs easily enough; the pep8 tool is more guilty of hijacking, i think.23:44
jog0yeah i figured there is no rush to rename23:44
sdaguemordred:  https://review.openstack.org/40995 is the infrastructure to not overwriting the files in g-r updates23:44
sdaguelet me know what you think about it23:45
jog0clarkb: got a question about the x-vrif-minus-2 stuff23:45
clarkbsure23:45
jog0should I just remove the entire openstack-dev section23:46
jog0or the events section23:46
jeblairjog0: (btw, i don't think that's worked in >1 year)23:46
jgriffithmordred: ping23:46
clarkbjog0: the entire openstack-dev section as removing the merge events basically noops that section23:46
jog0clarkb: thanks23:46
clarkbjog0: as an alternative we could look into fixing the x-vrif-minus-2 stuff23:46
openstackgerritJoe Gordon proposed a change to openstack-infra/config: Don't post merges in openstack-dev and openstack-nova  https://review.openstack.org/4068523:47
jog0clarkb: should of said that a minute ago ...23:47
jog0I don't think the -2 is very useful in the main room though23:47
clarkbjog0: agreed23:48
clarkbmust better in the project specific rooms if we get it working again23:48
jog0clarkb: yeah23:48
mroddenso why would stevedore importing an API plugin be finding conflicting requirements other than requirements.txt23:48
jog0anyway thanks, time to find some food23:48
fungii find it amusing (though understand) that the software devs are less interested in seeing merge notifications. in here that's the main thing i want notifications about from a systems dev perspective, because i want to know where to look first when things begin breaking23:49
sdaguemrodden: because stevedore freezes requirements23:49
sdagueand some other package probably installed a different version later23:49
mroddenso stevedore is the one with the requirement?23:49
jog0fungi: the time between merge and deploy for dev is longer then in here  Ithink23:50
sdaguemrodden: no, entry points capture the requirements at setup.py time23:50
mroddenits complaining because something brought in requests==1.2.3 and something has a >=1.1,<1.2.323:50
sdaguemrodden: right23:50
jog0but yeah its funny how that works23:50
sdaguethis is actually why I've been getting us to global-requirements in the gate for the last 3 weeks :)23:50
mroddenso...23:51
mroddeni'm lost...23:51
*** Ryan_Lane has joined #openstack-infra23:51
sdagueso before we started using entry points....23:51
lifelessin the mists of time23:51
sdaguewe were installing and uninstalling libraries left right and center23:51
mroddenyep, get that part23:51
sdaguewe actually used to install / uninstall python-keystone client 4 - 6 times every devstack build23:51
sdagueflipping versions23:52
mroddenew23:52
sdaguebefore entry points, if the code loaded and worked, all was good23:52
*** jpeeler has quit IRC23:52
sdagueafter entry points / stevedore, we encode metadata at setup.py time for each package23:52
sdagueso if you install an incompatible version later, you'll get those kinds of fails to load23:52
sdaguewe were always doing it wrong23:53
sdaguenow when we doing it wrong, it hurts a lot more23:53
mroddenwhere did it get encoded?23:53
*** zul has joined #openstack-infra23:53
mroddenrequirements.txt?23:53
sdaguein the egg info I think23:53
mroddenooo23:53
*** dina_belova has joined #openstack-infra23:53
sdaguehonestly the entrypoint / stevedore thing is a little fuzzy for me on mechanics23:54
sdaguebut the effects are clear :)23:54
sdagueand the solution is to brute force everyone to use one list23:54
sdaguewhich is what we've been doing in the gate for a week23:54
sdagueand still polishing the solution23:54
mroddenok...23:54
mroddenis there a way i can unscrew this up for now...23:55
mroddeneverytime i tox --recreate i hit the same thing23:55
sdaguehow old is your devstack?23:55
mroddenits not a devstack23:55
mroddenjust neutron23:55
clarkbpkg_resources is doing the check iirc23:56
clarkbwhich the entrypoint imports and makes use of23:56
fungidoes any of this pain ease up with the new entrypointless pbr implementation?23:57
*** dina_belova has quit IRC23:57
clarkbfungi: yes, entrypointless pbr does not check aiui23:57
clarkbfungi: one of the things slowing entrypoints down was all of the checking. pbr wanted more speed so ditched that23:57
fungialso, racing stripes23:57

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