Monday, 2013-08-05

mordredlifeless: the manifests dir is dropped from class paths00:00
mordredlifeless: so modules/foo/manifests/init.pp would probably contain the foo class00:00
mordredlifeless: files in templates are available to be installed on the machine after being passed through erb00:00
mordredwith every varialbe in the referencing scope injected into the scope of the template00:00
mordredto see an example of that - git grep 'template\('00:01
mordredfor instance, in modules/gerrit/manifests/init.pp - you'll see content => template('gerrit/replication.config.erb'),00:01
mordredwhich means that the results of expanding modules/gerrit/templates/replication.config.erb via erb should be placed at the location at the top of the stanze00:02
mordredlifeless: resources are indicated by a type, then a name, then parameters00:02
mordredlifeless: so file { '/home/gerrit2/review_site/etc/replication.config': content => template('gerrit/replication.config.erb'), } is declaring a file resource with the name /home/gerrit2/review_site/etc/replication.config00:03
mordredin any given DAG, there can only be one instantiation of a resource of the same name00:03
mordredmany resources tend to use their name parameter as the default value of the most interesting parameter00:04
mordredin the case of file, $name will be the default for path =>00:04
mordredthe rest is just cargo culting existing examples and iterating until it works00:05
mordred:)00:05
lifelessok00:05
lifelessthank you!00:05
lifelessfungi: if you're offering to draft it, that would be awesome. I'll read through and make sure I understand afterwards, so I can actually help in future.00:06
fungilifeless: sure, i'll be happy to here in a bit. i'm excited to see us get rsync working there for the various reasons discussed00:06
lifelessfungi: I'll put up a full set of whats-needed in etherpad - https://etherpad.openstack.org/rsync00:08
mordredwhat you don't fully understand all of puppet from that description?00:10
lifelessmordred: It's enough for me to dig and follow through00:11
lifeless-very- helpful00:11
lifelessdoesn't mean I've internalised it yet00:11
mordred++00:12
*** nijaba has quit IRC00:16
*** nijaba has joined #openstack-infra00:17
*** nijaba has quit IRC00:17
*** nijaba has joined #openstack-infra00:17
*** sarob has joined #openstack-infra00:17
mordredfungi: btw - my friends band, Teen Girl Scientist Monthly, is playing the Cave in Chapel Hill tonight at 1000:19
mordredthey're one of the ones I work with up here00:19
mordredShrews: ^^00:19
*** sarob has quit IRC00:22
Shrewsmordred: ugh, picking up some friends at the airport at 11. would've liked to have seen them.00:23
*** CaptTofu has quit IRC00:28
*** CaptTofu has joined #openstack-infra00:29
fungimordred: oh, wow. too bad we're old fuddy-duddies and turning in early00:30
* fungi should have planned ahead00:30
Shrewsmordred: where are they tomorrow?00:42
*** CaptTofu has quit IRC00:53
*** CaptTofu has joined #openstack-infra00:53
*** pabelanger has joined #openstack-infra01:01
*** nijaba has quit IRC01:16
*** nijaba has joined #openstack-infra01:17
*** nijaba has quit IRC01:17
*** nijaba has joined #openstack-infra01:17
*** sarob has joined #openstack-infra01:19
*** sarob has quit IRC01:23
*** yaguang has joined #openstack-infra01:40
*** sarob has joined #openstack-infra01:50
lifelessfungi: o/01:51
*** yaguang has quit IRC01:52
fungilifeless: working on it now, but on the wearable so my typing's a little slow01:52
lifelessfungi: oh cool! just hadn't heard anything :>01:52
fungigradually getting faster on this 7-key chording keyboard ;)01:53
*** yaguang has joined #openstack-infra01:53
*** sarob has quit IRC01:54
lifelessdo you have a HUD?01:55
*** CaptTofu has quit IRC02:01
*** CaptTofu has joined #openstack-infra02:02
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Add a read-only rsync server to the pypi mirror  https://review.openstack.org/4014002:03
fungilifeless: ^02:03
lifelesswicked02:03
fungilifeless: yeah, it's a converted pair of dvd viewer goggles02:04
fungionly 640x480 on ntsc, but usable02:05
fungithere are finally hdmi 720p res models on the market this year at reasonable prices, so i'll likely upgrade soon02:07
lifelessfungi: I so want to play with that in HK, if possible.02:07
funginot really planning to risk bringing diy electronics through customs this time around02:08
lifelessah, fair enough02:09
lifelesssad state of affairs02:09
fungithe usa is far too paranoid, i'd mostly worry about getting detained on re-entry02:10
fungibut next domestic trip where i think i might bump into you, i'll be sure to bring it along02:11
lifelesscool02:11
fungiby then it'll probably be smaller and better all 'round02:12
fungii've got a ton of general improvements in the works for it02:13
*** nijaba has quit IRC02:16
*** nijaba has joined #openstack-infra02:17
*** nijaba has quit IRC02:17
*** nijaba has joined #openstack-infra02:17
*** woodspa has quit IRC02:19
*** sarob has joined #openstack-infra02:20
*** sarob has quit IRC02:25
*** pabelanger has quit IRC02:30
clarkbfungi: when are you in seattle? I think lifeless is planning a trip here too (but I think you will miss each other)02:35
fungiclarkb: earlier, yeah. we're there for a week starting the 17th of this month, then at sea for a week02:39
*** pabelanger has joined #openstack-infra02:42
fungitalking about making reservations for brunch at the space needle on the 18th if anybody wants to go (i expect the locals consider that to be on par with recreational oral surgery, but christine wants to do cheesy tourist things)02:46
lifeless16-20 sept for me02:48
*** yaguang has quit IRC02:49
fungiyeah, so i'm missing you by a month02:49
*** sarob has joined #openstack-infra02:51
lifelesswhere are you based?02:53
fungiopposite end of the rock, raleigh, north carolina, several thousand miles from seattle02:54
*** sarob has quit IRC02:55
lifelessthat makes it what 2200 for you?02:55
fungifor people who abide by local time here, it's 22:5602:56
fungiaka "eastern daylight time"02:57
lifelesskk02:59
*** yaguang has joined #openstack-infra03:01
*** esp has joined #openstack-infra03:06
*** yaguang has quit IRC03:06
*** esp has quit IRC03:07
*** yaguang has joined #openstack-infra03:08
*** dkliban has joined #openstack-infra03:13
*** nijaba has quit IRC03:16
*** HenryG has quit IRC03:17
*** nijaba has joined #openstack-infra03:18
*** nijaba has quit IRC03:18
*** nijaba has joined #openstack-infra03:18
*** sarob has joined #openstack-infra03:21
*** sarob has quit IRC03:25
*** SergeyLukjanov has joined #openstack-infra03:39
*** bnemec_away is now known as bnemec03:43
*** sarob has joined #openstack-infra03:52
*** sarob has quit IRC03:56
*** pabelanger has quit IRC03:58
*** pabelanger has joined #openstack-infra04:14
*** niska has quit IRC04:15
*** nijaba has quit IRC04:17
*** nijaba has joined #openstack-infra04:18
hub_capmordred: thx for merging the python-netaddr stuffs in devstack04:22
*** sarob has joined #openstack-infra04:22
*** sarob has quit IRC04:27
*** niska has joined #openstack-infra04:39
hub_capour issues look to be fixed at present mordred clarkb etc04:42
*** emagana has joined #openstack-infra04:44
*** boris-42 has joined #openstack-infra04:46
*** sarob has joined #openstack-infra04:53
lifelessHi; what blockers are there to landing https://review.openstack.org/#/c/39858/ ? in -config ?04:55
lifelessother than no infra folk in my tz ?04:55
lifelesswe're blocked on landing the packaging stuff until it's in.04:55
*** sarob has quit IRC04:57
*** dguitarbite has joined #openstack-infra05:01
*** marun has joined #openstack-infra05:05
dstufftlifeless: just noticed you called me out in an email, checking now05:08
dstufftlifeless: fwiw I mostly ignore gerrit email because there's a metric ton of it05:09
lifelessdstufft: there is that05:15
lifelessdstufft: fedora folk having pip install -U distribute uninstall setuptools05:15
*** pabelanger has quit IRC05:16
*** afazekas_ has joined #openstack-infra05:17
*** nijaba has quit IRC05:17
*** nijaba has joined #openstack-infra05:17
*** nicedice has quit IRC05:20
*** dina_belova has joined #openstack-infra05:22
*** sarob has joined #openstack-infra05:24
*** dina_belova has quit IRC05:25
*** sarob has quit IRC05:28
*** SergeyLukjanov has quit IRC05:40
*** emagana_ has joined #openstack-infra05:41
*** emagana has quit IRC05:44
*** sarob has joined #openstack-infra05:55
*** sarob has quit IRC06:00
*** emagana_ has quit IRC06:00
*** amotoki has joined #openstack-infra06:10
*** nijaba has quit IRC06:18
*** nijaba has joined #openstack-infra06:18
*** nijaba has quit IRC06:18
*** nijaba has joined #openstack-infra06:18
*** sarob has joined #openstack-infra06:25
*** odyssey4me has joined #openstack-infra06:28
*** sarob has quit IRC06:30
*** tian has joined #openstack-infra06:32
*** dguitarbite has quit IRC06:36
*** odyssey4me has quit IRC06:46
*** odyssey4me has joined #openstack-infra06:53
*** sarob has joined #openstack-infra06:56
*** nijaba has quit IRC06:59
*** sarob has quit IRC07:00
*** boris-42 has quit IRC07:07
*** nijaba has joined #openstack-infra07:08
*** nijaba has quit IRC07:08
*** nijaba has joined #openstack-infra07:08
*** thomasbiege has joined #openstack-infra07:08
*** Vivek has quit IRC07:15
*** xchu has joined #openstack-infra07:17
*** Vivek has joined #openstack-infra07:17
*** Vivek is now known as Guest5837607:17
*** thomasbiege has quit IRC07:19
*** sarob has joined #openstack-infra07:26
*** psedlak has joined #openstack-infra07:31
*** sarob has quit IRC07:31
*** psedlak has quit IRC07:35
*** psedlak has joined #openstack-infra07:35
*** fbo_away is now known as fbo07:39
*** xchu has quit IRC07:43
*** sarob has joined #openstack-infra07:57
*** sarob has quit IRC08:01
*** boris-42 has joined #openstack-infra08:07
*** afazekas_ is now known as afazekas_food08:07
*** BobBall_Away is now known as BobBall08:08
*** xchu has joined #openstack-infra08:08
*** nijaba has quit IRC08:08
*** nijaba has joined #openstack-infra08:09
*** nijaba has quit IRC08:09
*** nijaba has joined #openstack-infra08:09
*** sarob has joined #openstack-infra08:27
*** sarob has quit IRC08:32
*** __cyril__ has joined #openstack-infra08:40
*** ruhe has joined #openstack-infra08:50
*** sarob has joined #openstack-infra08:58
*** sarob has quit IRC09:02
*** Ryan_Lane has quit IRC09:05
*** nijaba has quit IRC09:08
*** nijaba_ has joined #openstack-infra09:08
*** lifeless has quit IRC09:10
*** fbo is now known as fbo_away09:11
*** afazekas_ has joined #openstack-infra09:13
*** fbo_away is now known as fbo09:14
*** lifeless has joined #openstack-infra09:20
*** dkehn_ has joined #openstack-infra09:22
*** dkehn has quit IRC09:23
*** sarob has joined #openstack-infra09:28
*** sarob has quit IRC09:32
*** dkliban has quit IRC09:34
*** dina_belova has joined #openstack-infra09:37
*** SergeyLukjanov has joined #openstack-infra09:38
*** sarob has joined #openstack-infra09:59
*** sarob has quit IRC10:04
*** nijaba has joined #openstack-infra10:08
*** nijaba has quit IRC10:08
*** nijaba has joined #openstack-infra10:08
*** nijaba_ has quit IRC10:08
*** xchu has quit IRC10:09
*** dina_belova has quit IRC10:11
*** ruhe has quit IRC10:15
*** NobodyCam has quit IRC10:25
*** devananda has quit IRC10:28
*** sarob has joined #openstack-infra10:29
*** yaguang has quit IRC10:34
*** sarob has quit IRC10:34
*** ruhe has joined #openstack-infra10:43
*** boris-42_ has joined #openstack-infra10:44
*** boris-42 has quit IRC10:45
*** jhesketh_ has quit IRC10:45
*** boris-42_ is now known as boris-4210:45
*** jhesketh_ has joined #openstack-infra10:46
*** dina_belova has joined #openstack-infra11:02
*** nijaba has quit IRC11:08
*** nijaba has joined #openstack-infra11:08
*** nijaba has quit IRC11:08
*** nijaba has joined #openstack-infra11:08
*** jhesketh_ has quit IRC11:22
*** sarob has joined #openstack-infra11:30
*** woodspa has joined #openstack-infra11:34
*** sarob has quit IRC11:35
*** lcestari has joined #openstack-infra11:46
*** jhesketh_ has joined #openstack-infra11:48
openstackgerritSascha Peilicke proposed a change to openstack/requirements: Drop Cheetah global requirement  https://review.openstack.org/4020611:50
*** weshay has joined #openstack-infra11:56
*** NobodyCam has joined #openstack-infra11:57
*** devananda has joined #openstack-infra11:59
*** dina_belova has quit IRC11:59
*** sarob has joined #openstack-infra12:01
*** sandywalsh has quit IRC12:02
*** beagles has joined #openstack-infra12:03
*** sarob has quit IRC12:06
*** nijaba_ has joined #openstack-infra12:08
*** dina_belova has joined #openstack-infra12:09
*** nijaba has quit IRC12:09
*** sandywalsh has joined #openstack-infra12:15
*** rfolco has joined #openstack-infra12:15
*** thomasem has joined #openstack-infra12:20
*** CaptTofu has quit IRC12:22
*** CaptTofu has joined #openstack-infra12:22
*** HenryG has joined #openstack-infra12:25
*** ruhe has quit IRC12:27
*** ruhe has joined #openstack-infra12:27
*** adalbas has quit IRC12:28
*** chrisstreeter has joined #openstack-infra12:32
*** chrisstreeter has quit IRC12:35
*** krtaylor has quit IRC12:40
*** chrisstreeter has joined #openstack-infra12:40
*** chrisstreeter has quit IRC12:41
openstackgerritThierry Carrez proposed a change to openstack-infra/odsreg: Allow multiple allocations for a topic  https://review.openstack.org/4021212:43
*** chuckieb has joined #openstack-infra12:44
*** adalbas has joined #openstack-infra12:44
openstackgerritDavid Caro proposed a change to openstack-infra/jenkins-job-builder: Added matrix trigger option to email-ext publisher  https://review.openstack.org/4021412:49
*** xchu has joined #openstack-infra13:01
*** sarob has joined #openstack-infra13:02
*** sarob has quit IRC13:06
*** nijaba has joined #openstack-infra13:09
*** nijaba_ has quit IRC13:09
*** dkehn_ is now known as dkehn13:10
*** ruhe has quit IRC13:18
*** dprince has joined #openstack-infra13:18
*** dina_belova has quit IRC13:20
*** dina_belova has joined #openstack-infra13:21
*** ruhe has joined #openstack-infra13:21
*** pentameter has joined #openstack-infra13:24
*** mriedem has joined #openstack-infra13:24
*** dina_belova has quit IRC13:25
*** dina_belova has joined #openstack-infra13:25
*** pabelanger has joined #openstack-infra13:26
*** dina_belova has quit IRC13:30
*** kirankv has joined #openstack-infra13:32
*** krtaylor has joined #openstack-infra13:32
*** ruhe has quit IRC13:35
*** changbl has quit IRC13:35
*** jpeeler has quit IRC13:37
*** jpeeler has joined #openstack-infra13:38
*** jpeeler has joined #openstack-infra13:38
*** pabelanger has quit IRC13:39
sdagueany coremudgeons around that could hold a vm? I think the fastest way to get to the bottom of this grenade issue is to poke around on it it after the fail13:44
*** ruhe has joined #openstack-infra13:44
fungisdague: how frequent are they? that will determine what tack i take with trying to catch one13:44
sdaguefungi: it's one job13:44
sdagueit's the proposed change to get us to updating from requirements13:45
sdagueso I can trigger the job that will fail it now13:45
fungiah, simple13:45
fungii may be able to reproduce without holding one, just following my test simulation instructions in the d-g readme13:45
sdaguefungi: https://jenkins.openstack.org/job/gate-grenade-devstack-vm/24561/13:46
sdagueif you hold that vm13:46
sdagueyou've got about 30 minutes before it finishes13:46
sdaguebut it *will fail*13:46
fungican do13:46
sdaguethanks much13:47
*** dina_belova has joined #openstack-infra13:48
*** vijendar has joined #openstack-infra13:49
*** fifieldt has quit IRC13:54
*** _TheDodd_ has joined #openstack-infra13:56
fungisdague: 15.185.189.23 is the slave. it's marked held and i've added the rsa ssh key from your lp profile to the jenkins user on it13:56
*** prad_ has joined #openstack-infra13:57
*** ruhe has quit IRC14:00
*** blamar has quit IRC14:00
sdaguefungi: cool14:01
sdaguethanks14:01
sdagueman, you guys are sensible and use your class A for public facing stuff :)14:01
*** adalbas has quit IRC14:02
*** sarob has joined #openstack-infra14:04
*** odyssey4me has quit IRC14:04
*** dina_belova has quit IRC14:04
*** sarob has quit IRC14:08
*** wu_wenxiang has joined #openstack-infra14:09
*** nijaba_ has joined #openstack-infra14:09
*** nijaba has quit IRC14:10
*** blamar has joined #openstack-infra14:10
*** fbo is now known as fbo_away14:12
*** afazekas_ has quit IRC14:13
*** rnirmal has joined #openstack-infra14:17
*** dina_belova has joined #openstack-infra14:17
*** dina_belova has quit IRC14:18
*** adalbas has joined #openstack-infra14:18
fungiwho's "you guys"? the hpcloud peeps i guess14:18
*** dina_belova has joined #openstack-infra14:20
fungigrr... sdague: sorry, looks like that vm got deleted14:20
fungii think the recent d-g refactoring no longer notices if a vm is set to hold state when it marks for deletion14:20
*** fbo_away is now known as fbo14:21
*** dkranz has quit IRC14:21
fungisdague: i'm manually launching an identical vm right now where i'll fire up the same test and get you ssh access to it, then i'll track down where we broke the hold state stuff in d-g14:24
*** datsun180b has joined #openstack-infra14:25
*** burt has joined #openstack-infra14:26
*** ruhe has joined #openstack-infra14:27
*** vogxn has joined #openstack-infra14:30
*** dolphm has joined #openstack-infra14:31
sdaguefungi: ok, cool14:32
sdaguefungi: sorry "you guys" == HP14:32
* fungi is not hp, but will gladly accept this award on their behalf14:33
*** pcrews has joined #openstack-infra14:33
sdagueheh, yeh, I remembered now14:34
*** cthulhup_ has joined #openstack-infra14:35
*** sarob has joined #openstack-infra14:35
*** cthulhup_ has quit IRC14:36
*** emagana has joined #openstack-infra14:37
sdaguefungi: ummm.... any idea why grenade-core is empty?14:38
sdaguehttps://review.openstack.org/#/admin/groups/188,members14:38
*** sarob has quit IRC14:39
funginone whatsoever14:39
fungiit does seem to be used in the grenade project acl, so it ought to have users14:39
fungiit's also not self-managed (owned by administrators instead)14:40
fungiwho do you want in it?14:40
fungialso, i assume it was in use previously? i'll look to see if that acl changed recently to create a new core group14:41
*** dkliban has joined #openstack-infra14:41
*** rcleere has joined #openstack-infra14:42
*** markmcclain has joined #openstack-infra14:43
fungisdague: the acl used to reference devstack-core instead, then you proposed https://review.openstack.org/36902 which merged about 3 weeks ago to create grenade-core14:44
fungiwe probably just never added anyone to it after that14:44
sdagueheh, ok14:44
sdagueyeh, can you put dtroyer and I as +2 on it14:44
fungicoming right up14:44
*** wu_wenxiang has quit IRC14:46
fungiyou're both in grenade-core now14:46
sdagueawesome, thanks14:48
*** cppcabrera has joined #openstack-infra14:52
*** cppcabrera has left #openstack-infra14:53
fungii've got gate-grenade-devstack-vm running on a manually-launched vm now with the same changeset and parameters used in the job you pointed me to, so i'll give you a heads up once it fails and get you the ip address so you can look around14:54
*** Guest98707 has joined #openstack-infra14:54
*** Guest98707 has quit IRC14:55
*** CliMz has joined #openstack-infra14:57
*** CliMz has joined #openstack-infra14:58
sdaguefungi: awesome, thank you14:59
*** emagana has quit IRC15:00
mordredmorning sdague !15:01
sdaguemorning15:01
mordredsdague: I made some progress on some things after you left on friday - but not the grenade issue15:01
sdagueyeh, fungi is spinning me up a vm for the grenade thing, so I can poke aroun15:02
*** changbl has joined #openstack-infra15:02
*** sarob has joined #openstack-infra15:05
mordredawesome15:06
burtmordred: thanks for getting the dependency hell cleaned up.  Clean Precise + devstack works now.15:06
mordredburt: w00t!15:08
mordredburt, sdague I'm going to be an ass about persuing the larger patch, btw15:09
*** nijaba_ has quit IRC15:09
mordredsdague: I think that, with the work we're doing on global requirements, chasing the distro packages for python packages is a waste of time and counter productive15:10
*** nijaba has joined #openstack-infra15:10
*** sarob has quit IRC15:10
mordredsdague: although, if we had a tool such as the one you discuss on the code review, I could see that being decent15:10
burtmordred: sounds good. I'll be an ass if devstack breaks again for me.15:11
mordred:)15:11
sdagueyeh, I think realistically packages vs. pip is actually the same problem as different pip installs in different projects15:11
*** rnirmal_ has joined #openstack-infra15:12
*** rnirmal has quit IRC15:13
*** rnirmal_ is now known as rnirmal15:13
*** vogxn has quit IRC15:14
*** mrodden1 has quit IRC15:14
mordredsdague: I just responded more long form on the review15:16
mordred(since probably if there is a back and forth it would be good to capture it there)15:16
*** xchu has quit IRC15:17
ttxJust looked into setting up CIVS locally so that we can run ballots through alternative algorithms to see how well they perform.15:18
ttxPretty simple stuff.15:18
mordredttx: neat! should we consider running our own for real? or just for testing?15:19
*** dkranz has joined #openstack-infra15:19
ttxI think letting a third-party run the voting infra is sort of a feature15:19
sdaguemordred: sure, or bring it out to the mailing list15:20
ttxmordred: but yes, I almost convinced myselff to write a puppet recipe for setting it up15:20
sdaguetypically that's what I've done when there turns out to be an actual dispute in the review15:20
*** reed has joined #openstack-infra15:20
ttxmordred: it uses weird patching of Perl files with configuration values15:20
mordredttx: good point re: third party running it being a feature15:21
fungisdague: you should be able to ssh to 166.78.161.26 as jenkins now. that manual run produced the same failure as the job console log you pointed me to (note i simply followed the instructions in the d-g readme for simulating a job)15:21
*** __cyril__ has left #openstack-infra15:21
sdaguefungi: thanks, I'm in15:22
fungisdague: let me know when you're done with it (take your time though) so i can delete it15:22
ttxfungi, jeblair: Make sure to enable "Enable detailed ballot reporting" option on future elections you set up15:22
fungittx: does that provide access to the anonymized raw data for analysis?15:23
ttxfungi, jeblair: that way we can download the anonymized ballots and run the results through various algorithms and see how well/bad they perform15:23
fungiperfect15:23
*** blamar has quit IRC15:23
*** amotoki has quit IRC15:24
ttxfungi: we need to "test" the representative proportional algorithm in particular.15:24
ttxactually...15:24
ttxwe don't even need to run our own to do that.15:24
jeblairfungi, clarkb, mordred: so, ah, jbryce has moved openstack.org email to something new and it can no longer be managed in the cloud sites webui.15:24
sdaguemordred: so.... the issue seems to be that oslo.config gets installed in grizzly because it's coming from pip15:25
*** ruhe has quit IRC15:25
sdaguebut in havana, with global requirements, we use the git tree15:25
ttxwe can set up a "test" consultation and upload results on the CIVS site itself.15:25
sdaguebut don't install15:25
ttxI guess I reproduced the install for no good reason :)15:25
sdagueand as such nova-manage is picking up the pip installed tree and not the git tree15:25
sdaguehow do we go about addressing that?15:25
fungijeblair: is that what his message meant? i had never tried to manage my o.o mailbox via anything besides imap15:25
fungittx: setting up your own provides additional insights into its inner workings at least, i would expect15:27
sdaguedo we just install oslo.* as well as doing setup.py ?15:27
*** emagana has joined #openstack-infra15:27
sdaguesorry, setup.py develop15:27
*** emagana has quit IRC15:27
ttxfungi: it does :)15:27
openstackgerritMonty Taylor proposed a change to openstack-dev/hacking: Synced with global requirements  https://review.openstack.org/4006515:27
jeblairfungi: yeah;  i have asked him for an admin account, but considering the number of system-y mailboxes we manage, i think the whole root team should have either one shared admin account, or one each.15:28
jeblairon the plus side, that is perhaps one less thing colocated in the main rackspace account; now it's just dns and cloud sites.15:29
fungijeblair: good point15:29
fungii had entirely forgotten that was also going to affect the role addresses15:30
*** ^d has joined #openstack-infra15:30
*** ^d has joined #openstack-infra15:30
*** mrodden has joined #openstack-infra15:30
*** mgagne has joined #openstack-infra15:31
*** vijendar has quit IRC15:31
*** CliMz has quit IRC15:31
*** ruhe has joined #openstack-infra15:32
mordredjeblair: oh, that's great! it's wonderful that it's being managed by something other than the world-class email admin we have...15:32
*** vogxn has joined #openstack-infra15:32
*** blamar has joined #openstack-infra15:33
*** blamar has quit IRC15:33
mordredsdague: wait, didn't we add that already?15:33
jeblairmordred: it sounded like it's another rackspace thing, maybe a new version of their hosted email service or something.15:33
jeblairmordred, ttx: one of my talks has been accepted at linuxcon europe15:35
mordredjeblair: same here15:35
sdaguemordred: no, we were just doing this - https://github.com/openstack-dev/devstack/blob/master/lib/oslo15:35
* ttx skips15:35
* mordred looks15:35
sdaguemordred: so is my only issue I need to add setup.py install there?15:35
jeblairttx: bummer  :(15:35
mordredno - it should do the same thing15:35
mordredsdague: setup_develop should be running pip install -e now15:36
ttxjeblair: it's like release week +115:36
sdaguemordred: pip install isn't the issue15:36
sdaguemordred: here is the issue15:36
sdaguein grenade15:36
*** blamar has joined #openstack-infra15:36
*** sarob has joined #openstack-infra15:36
sdagueduring grizzly install:15:36
ttxjeblair: aka summit week -215:36
sdague * pip install oslo.conf 1.115:36
sdaguedo lots of stuff15:36
sdagueduring havana upgrade:15:37
sdaguepull oslo.config from git15:37
jeblairttx: ah, your only chance to unwind.15:37
sdaguerun python setup.py develop in oslo.config tree15:37
sdague(but we don't install it15:37
ttxjeblair: it's actually summit scheduling high tide15:37
sdagueso ... /usr/local/lib/python2.7/dist-packages/oslo15:37
sdagueis still 1.1.115:37
ttxjeblair: not sure I will unwind at all.15:37
sdaguenot the git version15:37
mordredbut the easy-install.pth file in /usr/local/lib/python2.7/dist-packages should have an entry15:38
sdagueit does15:39
sdagueapparently that's not good enough?15:39
reeddoes anybody here knows the number of downloads from tarballs on launchpad?15:39
jeblairttx: ugh.  well, uh, enjoy your current holiday.  :)15:39
mordredlooking15:39
sdaguemordred: http://paste.openstack.org/show/43203/15:39
*** sarob has quit IRC15:40
mordredsdague: that's what I expect that to look like15:42
sdaguemordred: well with that setup, /usr/local/bin/nova-manage can't run15:43
sdagueit's picking up bad old oslo15:43
sdaguehttp://paste.openstack.org/show/43207/15:43
mordredsdague: we could pip uninstall oslo.config before the setup_develpo call15:43
sdaguesure, is that the right fix?15:44
mordredin lib/oslo15:44
sdaguevs. installing oslo15:44
mordredtough to say - I'm connecting to that box right now - but min internet is SLOWWWWWWW15:44
sdagueok15:44
mordredgah. I have no keys on tha tmachine15:45
mordredsdague: on that machine, try pip uninstall oslo.config and then cd /opt/stack/new/oslo.config and pip install -e .15:45
mordredand see if it at least fixes it15:45
sdaguejenkins@testserver:~$ sudo pip uninstall oslo.config15:46
sdagueCan't uninstall 'oslo.config'. No files were found to uninstall.15:46
mordrednice15:46
mordredI love pip15:46
*** sarob has joined #openstack-infra15:46
sdagueso, you're putting in the "Why OpenStack hates Python" talk for pycon, right?15:46
sdaguebecause I seriously want to see your crazy on stage rant for that15:46
mordredsdague: I need to step out for lunch ... but I've got a good idea of how to reproduce the issue and poke at iterations when I get back15:47
sdagueok, cool15:47
sdagueI'm pretty sure this is the last issue to get through15:47
sdagueso could this be because nova-manage is now all command entry points?15:48
sdagueok, guess we'll go and get lunch here as well15:49
*** rustlebee is now known as russellb15:50
*** sarob has quit IRC15:51
*** ruhe has quit IRC15:52
*** danger_fo_away has quit IRC15:54
*** kirankv has quit IRC15:54
chmoueljey guys15:57
chmouelthis job has failed https://review.openstack.org/#/c/40172/15:57
chmouelon postgres vm15:57
chmouelbut the log didn't get uploaded15:58
chmoueli.e: http://logs.openstack.org/72/40172/1/gate/gate-tempest-devstack-vm-postgres-full/b30425115:58
*** danger_fo_away has joined #openstack-infra15:58
*** danger_fo_away is now known as danger_fo15:59
NobodyCamI have a question for -infra15:59
jeblairchmouel: there was a jenkins error; the devstack node was deleted before it started15:59
jeblairchmouel: i'm working on making that more robust; i hope to have an improvement in a couple of weeks16:00
fungiNobodyCam: you're in the right place then16:00
jeblairchmouel: it's getting a harder, but you can find the jenkins job with a little work; it's here: https://jenkins.openstack.org/job/gate-tempest-devstack-vm-postgres-full/39112/console16:01
NobodyCamis there a way to get the diff between 1 file in a review with out all the other base changes? (ie. not using the old version pull-down)16:02
fungiNobodyCam: here's the trick i use for that...16:02
NobodyCam:)16:02
fungiNobodyCam: view the current patchset's copy of that file diffed against base16:02
* NobodyCam takes notes16:02
fungiNobodyCam: then change the base patchset to the one you want to compare against16:03
*** emagana has joined #openstack-infra16:03
fungiNobodyCam: then look at which file ha a green "already seen it" checkmark over to the right16:03
fungiyou still have to wade through previous patchsets changes in the same file, but at least you can pick it out of the mess of other changed files16:04
fungier, not previous patchsets changes but other rebased changes in the same file16:04
chmoueljeblair: we have seen some of these errors since this morn16:04
fungiNobodyCam: not perfect, but helps whittle it down. it also helps that i've probably seen the intervening changes and probably remember what was in them to some extent16:05
NobodyCamok ya I have a case whre patch #3 was approved kicked back with please rebase and not the patch has grown by onle line.. lol just trying to find that one line16:06
NobodyCams/not/now16:06
*** vijendar has joined #openstack-infra16:06
fungiNobodyCam: you might also use git show on the old and new patchsets and then diff the results. bit of a pain, and probably introduces some additional noise, but might help16:07
NobodyCam:)16:07
fungiNobodyCam: or open up both patchsets in separate browser windows side by side. also not great but...16:07
NobodyCamyep...16:07
fungiin other words, i haven't found an ideal solution to the problem16:08
NobodyCam:-p16:08
*** nijaba_ has joined #openstack-infra16:10
NobodyCamthank you fungi :)16:10
*** nijaba has quit IRC16:10
fungiNobodyCam: yw. sorry i didn't have a better answer16:10
pleia2good morning16:11
NobodyCam:)16:11
fungimorning pleia216:11
NobodyCamits all good16:11
zaromorning.16:11
*** nicedice has joined #openstack-infra16:11
*** changbl has quit IRC16:14
fungimorning zaro16:17
*** SergeyLukjanov has quit IRC16:17
*** changbl has joined #openstack-infra16:20
*** dina_belova has quit IRC16:21
*** psedlak has quit IRC16:22
*** vogxn has quit IRC16:23
*** ruhe has joined #openstack-infra16:26
NobodyCamTY fungi! separate browser windows did the trick16:27
fungiNobodyCam: great. if you ever stumble across a better way, i'd be thrilled to know about it ;)16:27
NobodyCam:)16:28
fungii suspect something could be engineered diff'ing cleaned-up output from git show on both patchsets, but no idea whether that wheel's already been invented somewhere16:29
*** boris-42 has quit IRC16:29
*** vogxn has joined #openstack-infra16:33
*** fbo is now known as fbo_away16:33
*** changbl has quit IRC16:35
clarkbmorning16:37
fungimorning clarkb16:37
fungiNobodyCam: actually, i just stumbled across one dirty solution to the problem... cherry-pick the new patchset onto the old one and the delta should in theory show that way16:38
*** weshay has quit IRC16:40
zaroclarkb: morning.16:43
zaroclarkb: hey, zmq plugin isn't showing up on jenkins plugin manager.  i think we are missing something.16:43
dansmithis there a bug open for the swift port conflict thing? I was thinking this has been a known issue for a while, causing chance failures due to binding to 6xxx ports.. ?16:44
jeblairzaro, clarkb: i agree; i noticed that when i tried to use the new puppet resource for it.16:44
clarkbzaro: do we need to register it with them through some second channel?16:45
clarkbI haven't done anything like that16:45
zaroclarkb: i think we may just need to upload the pom.xml as well.16:45
zarojeblair: puppet resource?  which one?16:46
*** pcrews has quit IRC16:46
zaroclarkb: that would be my first guess. if that doesn't work, then it may be linked to the jenkins wiki somehow.16:46
clarkbzaro: there is a new puppet defined resource to install jenkins plugins16:48
zarojeblair: it's available in the jenkins-ci repo: http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/zmq-event-publisher/16:49
NobodyCamfungi: Ahh yes that might do it.. I try it next time I run across that issue!16:49
jeblairzaro: see http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/zmq-event-publisher/16:49
jeblairoops16:50
jeblairzaro: see: https://review.openstack.org/#/c/40041/16:50
fungiNobodyCam: i tested it niavely on a non-trivial rebase where some merge conflict resolution had been employed and got an error from git about an empty resulting commit, so it will probably work at least some of the time for that16:50
fungier, naively16:50
*** sarob has joined #openstack-infra16:51
*** sarob has quit IRC16:52
*** sarob has joined #openstack-infra16:52
zarojeblair: clarkb : i'll upload the pom.xml for the zmq plugin to see if it appears.  it may take a few hours to propogate thru.  i've heard it can take as long as 24 hrs.16:53
*** sarob_ has joined #openstack-infra16:53
*** ruhe has quit IRC16:54
*** bearhands is now known as comstud16:54
*** psedlak has joined #openstack-infra16:55
*** sarob_ has quit IRC16:55
*** sarob_ has joined #openstack-infra16:56
*** sarob has quit IRC16:57
harlowja_mordred just say no to packages ?? ;)17:00
sdaguedansmith: that's why it's still off by default in devstack17:01
sdagueswift conflicts with X server ports17:01
dtroyersdague, mordred: I just sent a wall of text re the package vs pip discussion to the ML, trying to summarize what we know and what is in https://review.openstack.org/40019.  Please correct freely where necessary.17:04
sdaguedtroyer: great17:04
*** pabelanger has joined #openstack-infra17:06
jeblair_TheDodd_: ping17:06
pleia2can someone do me a favor and check to see if /home/cgit/.ssh/authorized_keys on git.o.o is populated?17:07
pleia2(trying to see if I properly defined the contents variable in my puppet config)17:07
jeblairpleia2: will do17:07
pleia2thank you17:08
jeblairpleia2: gerrit-code-review@gerrit.openstack.org17:08
jeblairpleia2: yes17:08
*** dina_belova has joined #openstack-infra17:08
pleia2jeblair: thanks17:08
*** nijaba_ has quit IRC17:09
*** nijaba has joined #openstack-infra17:10
*** nijaba has quit IRC17:10
*** nijaba has joined #openstack-infra17:10
*** emagana has quit IRC17:15
clarkbI noticed one issue with proposal.slave over the weekend. I think Jenkins' ssh private key was managed by hand previously so pushes to gerrit are failing. I will fix that with a puppet change17:15
*** emagana_ has joined #openstack-infra17:16
jeblairclarkb: fyi the private key showed up for the new jenkins masters (so it's not completely broken)17:16
clarkbjeblair: I think I am just missing the flag to the jenkins user that includes the key17:17
*** nati_ueno has joined #openstack-infra17:17
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Revert "Make gate-tempest-devstack-vm-neutron non-voting"  https://review.openstack.org/4025017:19
*** odyssey4me has joined #openstack-infra17:20
dansmithsdague: http://logs.openstack.org/37/40237/1/check/gate-grenade-devstack-vm/6809c95/logs/new/screen-s-container.txt.gz17:21
dansmithsdague: seems on in grenade...17:21
jeblairclarkb, fungi: would you mind reviewing https://review.openstack.org/#/c/39774/1 ?17:22
clarkblooking17:22
*** SergeyLukjanov has joined #openstack-infra17:22
mordreddstufft: convoluted questions for you17:22
mordredsdague: I have reproduced the situation very simply with oslo.config17:23
mordreddstufft: pip install oslo.config # installs 1.1.1 from pypi ; git clone git://github.com/openstack/oslo.config ; cd oslo.config ; sudo pip install -e .17:24
mordreddstufft: after the above17:24
mordred>>> oslo.config.__file__17:24
clarkbjeblair: sdague does https://review.openstack.org/#/c/39774/1 mean we preinstall the requirements prior to running devstack?17:24
mordred'/usr/local/lib/python2.7/dist-packages/oslo/config/__init__.pyc'17:24
*** pabelanger has quit IRC17:24
clarkbor is devstack consuming the requirements list?17:24
mordreddstufft: so, the local thing is being installed into the easy-install.pth file17:24
mordredclarkb: it's slightly more complex17:24
mordredclarkb: in each setup_develop function call in devstack17:24
mordredclarkb: we call requirements:update.py17:25
sdagueclarkb: there is a devstack change that hasn't landed yet which will do what monty says17:25
mordredclarkb: which will update the local requirements list in the repo we are about to install from with the appropriate lines from the global list17:25
sdaguedansmith: so that seems like swift wasn't shut down correctly17:25
clarkbsdague: dansmith it is possible that the slave is being used more than once17:26
jeblairclarkb: strictly speaking i don't think it should matter for the actual zuul layout change; if any of what they describe is not in place, it will just be a sort of no-op run -- changes will merge if a standard devstack run succeeds.17:26
mordreddstufft: also, pip uninstall oslo.config is a no-op17:26
clarkbsdague: dansmith we fixed one problem that allowed that, but it is possible something else is also causing that to happen17:26
*** changbl has joined #openstack-infra17:26
*** sarob_ has quit IRC17:27
clarkbjeblair: ya, not required now. Just wondering what the gameplan was because I thought mordred had something different in mind with the pbr rawinstall stuff17:27
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add httpd ssl support to git.openstack.org  https://review.openstack.org/4025317:27
jeblairclarkb: indeed; i like knowing gameplans too.  :)17:27
*** sarob has joined #openstack-infra17:27
pleia2hm, that didn't go well as I wanted17:27
openstackgerritA change was merged to openstack-infra/config: Cleanup unneeded Jenkins vars.  https://review.openstack.org/3960717:27
mordredclarkb: rawinstall tests different things17:27
clarkbmordred: it tests ability to install, devstack with requirements will test ability to work17:28
mordredright17:28
mordredrawinstall also tests ability for us to build a mirror with a given set of requirements :)17:28
jeblairclarkb: according to d-g logs, the node dansmith pointed to was not used twice.17:28
mordredso -will adding this req break our mirror building job in a way we need to know about17:28
openstackgerritDavid Caro proposed a change to openstack-infra/jenkins-job-builder: Added matrix trigger option to email-ext publisher  https://review.openstack.org/4021417:29
sdaguejeblair: I've seen fails like this before, I wonder if swift in stable added a new service that doesn't get shut down17:29
clarkbjeblair: +2 from me. I haven't approved it to give fungi a chance to look at it17:29
clarkbjeblair: sdague but feel free to approve if you are in a rush17:29
mordredclarkb: the patch above from sdague sets us up for the other change sdague and I are working on17:31
mordredoh yeah - basically what jeblair said17:31
*** ruhe has joined #openstack-infra17:31
*** pcrews has joined #openstack-infra17:32
*** sarob has quit IRC17:32
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add httpd ssl support to git.openstack.org  https://review.openstack.org/4025317:33
*** gyee has joined #openstack-infra17:36
*** boris-42 has joined #openstack-infra17:36
harlowja_qq, is there any good set of slides that i can refer some of the yahoo people to that shows how awesome the CI in openstack is?? like something that explains the setup and stuff, would like to send something to them, but not sure if anything exists :)17:37
mordredharlowja_: we have _many_ slides17:37
mordredfrom what pov do you want?17:38
harlowja_hmmm, higher level i guess to start17:38
harlowja_like arcitecture maybe17:38
mordredharlowja_: http://docs.openstack.org/infra/publications/overview/17:38
harlowja_thx17:38
mordredmight be a good first step17:38
harlowja_def17:38
harlowja_that is :)17:38
harlowja_thx mordred17:38
mordredharlowja_: we could also probably arrange for one of us to come out and do the dog and pony show at some point17:39
harlowja_hehe17:39
harlowja_possibly17:39
*** sarob has joined #openstack-infra17:39
harlowja_who's the pony this time?17:39
mordredwhoever you want it to be ;)17:39
*** vogxn has quit IRC17:39
harlowja_lol17:39
*** sarob has joined #openstack-infra17:39
openstackgerritClark Boylan proposed a change to openstack-infra/config: Add Jenkins SSH key to proposal.slave.  https://review.openstack.org/4025417:39
clarkbjeblair: ^ that should fix the ssh key situation on proposal.slave.o.o17:40
harlowja_mordred i'll see how this goes, might take u up on that :)17:40
mordredsdague: pip uninstsall _before_ the oslo.config seup_develop seems to work17:41
sdaguemordred: yeh, I've got that in the new grenade patch17:42
sdaguehopefully with enough permissions this time17:42
mordredsdague: and I think I'm somewhat comfortable with the approach since what we're doing, namely, testing an upgrade from an old version installed via pip to a new version installed from trunk with setup.py develop is enough of a shift in approach that it not working naturally is not shocking17:43
sdaguesure17:43
sdagueit still seems like this is a pip bug though17:43
*** burt has quit IRC17:43
mordredsdague: also, once we're doing havana to icehouse, the structure of the install will be the same, and oslo.config for havana will be coming from stable.havana, so it should be less crazy17:43
sdagueespecially as you can't uninstall it17:43
mordredsdague: I _totally_ agree17:43
mordredsdague: I'd like to run through it with dstufft and see what the chances are of getting the pattern fixed in pip17:44
sdagueI sometimes feel like openstack is a giant icebreaker going through the arctic seas smashing into an through python bugs the whole way17:44
mordredya17:44
sdaguewhich I guess is a good thing for everyone17:45
sdaguejust never fun to be the one who hits the bugs first :)17:45
mordredsdague: btw - on the 'stop installing python packages from apt' - I'm also on board with never installing from pip17:45
mordredit's purely the mix of packages + pip on the same machine that seems to be just not designed to work17:45
mordredso, I also think that an approach where we had apt and yum repos available built from requirements.txt would be, well, extra work, but also something we should be able to expect to actually operate predictably17:46
*** Guest58376 is now known as Vivek17:47
mordredharlowja_: which is anvil now? all pip? or all pkgs?17:48
harlowja_all rpms17:48
*** Vivek is now known as Guest8466117:48
mordrednod17:48
harlowja_not strongly tied to rpms, but thats just what we've implemented17:48
sdagueit's unfortunate that the python install tools slam into regular directories17:48
harlowja_ya17:48
mordredsure - just wondering which route of pain and death you'd done down17:48
harlowja_not 'deb' route yet :-p17:48
harlowja_rpm route hasn't been so bad17:49
mordredsdague: dstufft is writing a PEP about that, btw17:49
*** Guest84661 is now known as VivekVC17:49
harlowja_anvil did have ubuntu support, but it wasn't really being maintained so i took it out for now17:49
mordredsdague: to call out the need for python and distro packaging to be able to co-exist17:49
*** VivekVC has quit IRC17:49
*** VivekVC has joined #openstack-infra17:49
*** VivekVC is now known as Vivek17:49
sdaguemordred: it is one of the things I like about ruby's gem, it installs into /var/lib/gems, so out of the way. It also allows for version specification on import17:49
mordredsdague: yeah. perl have support baked in too17:50
mordredthe real problem comes in that python upstream doesn't have two different places for distro and non-distro add-on libraries17:50
clarkbcabal too17:50
harlowja_just there are in openstack always going to be annoyances like libvirt bindings17:50
mordredyup17:51
mordredah libvirt17:51
harlowja_lol17:51
mordredso - the biggest problem we'd fact, if we went down the route of making packages from our own software, and only installing anywhere via distro packages, are things that need newer versions of libs than what's in the distro17:52
mordredbecause we have in the past maintained apt repos with backports of python dependencies17:52
mordredand it was a nightmare17:52
*** apevec has joined #openstack-infra17:52
harlowja_just make them on the fly :)17:52
mordredbut waiting on the distro means a 6 month cycle17:52
harlowja_not for RHEL17:53
mordredharlowja_: yeah. that one is tempting17:53
harlowja_thats like a 3+ year cycle ;)17:53
mordredharlowja_: if only upstream packaging sources were consumable in a predictable manner17:53
*** odyssey4me has quit IRC17:53
mordredharlowja_: how do you determine the appropriate distro package naming for intra-depends?17:53
harlowja_so RH has a pretty basic way of appending 'python-' onto all there packages17:54
harlowja_and we also have a map for weird cases17:54
harlowja_*yaml map17:54
harlowja_making an example, one sec17:54
mordredok. that answers the question17:54
mordredexistence of manually curated exception map17:55
harlowja_ya17:55
mordredk. cool.. good to know17:55
harlowja_aka https://github.com/stackforge/anvil/blob/master/conf/distros/rhel.yaml#L817:55
harlowja_:-p17:55
sdaguemordred: so https://review.openstack.org/#/c/39574/ now passes, with the explicit uninstall17:55
mordredI mean, we already maintain logic around special cases - such as adding pyparsing and pycffi to requireents.txt even though they're transitive17:56
mordredsdague: w00t!17:56
sdaguedtroyer: can you take a look at https://review.openstack.org/#/c/39574/17:56
mordredsdague: then I say we land that - it at least lets us gate moving forwar17:56
*** dina_belova has quit IRC17:57
mordredsdague: btw - once this is landed, perhaps we should make the grenade gate symmetrical?17:57
sdagueyeh, I want dtroyer to sanity check it first17:57
harlowja_then mordred we can introspect the yum repositories (very useful that yum is in python) to do matching and all that17:57
sdaguemordred: sure, once the other devstack thing lands17:57
mordredsdague: oh yeah - no, I want to get solid first :)17:57
sdagueI'd like to get this finished for reals first17:57
mordredsdague: o - I wrote the update projects stuff17:58
harlowja_mordred apt is also in python, so u can likely make a tiny program to do the yumfind like stuff there also17:58
*** odyssey4me has joined #openstack-infra17:58
harlowja_just not sure about that, ha17:58
mordredsdague: https://review.openstack.org/#/c/40068/17:58
*** Ryan_Lane has joined #openstack-infra17:58
sdagueman... we're past 40k reviews?17:58
mordredoh yeah17:58
clarkbsdague: yes, and we failed at getting review 40k17:58
harlowja_lol17:59
mordredI tried really hard17:59
sdagueheh17:59
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add git-daemon to cgit server.  https://review.openstack.org/3659317:59
sdaguedansmith tried hard to get 30k, and missed it as well17:59
clarkbhmm /me rereviewes 40068 it seems important17:59
dansmithI missed it by 2, IIRC18:00
sdagueyeh, that sounds right18:00
clarkbmordred: does https://review.openstack.org/#/c/40068/1..2/modules/jenkins/files/slave_scripts/propose_requirements_update.sh do something that `git diff --quiet` doesn't?18:00
harlowja_mordred in the anvil tools, py2rpm (which also is responsible for making pips -> rpms) has a option to just convert the damn package names, so thats how we are using it in most of the rest of anvil to do the name conversion (providing said tool the name mapping)18:01
harlowja_./tools/py2rpm --convert pip setuptools18:01
harlowja_Requires: python-pip18:01
harlowja_Requires: python-setuptools18:01
harlowja_for exampel18:01
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add git-daemon to cgit server.  https://review.openstack.org/3659318:01
harlowja_anyway, back to my other work, try anvil out if u want, seems like a larger discussion around packaging/pips though :)18:01
clarkbharlowja_: does it name the pip executable wrong too?18:02
mordredclarkb: maybe not? should I just use git diff --quiet?18:02
harlowja_clarkb, lol18:02
harlowja_actually clarkb i think the new packages on epel are actually putting binaries for 'pip-python, pip'18:02
harlowja_so they are fixing that one :-p18:02
clarkbharlowja_: I ask because our centos nodes symlink /usr/bin/pip to whatever centos installs it as18:02
clarkbnice18:02
clarkbmordred: I think we use git diff --quiet elsewhere18:02
mordredclarkb: great. I'll update it18:03
harlowja_clarkb ya i never understood that, was it just to be cool, idk18:03
clarkbmordred: for me at least that is easier to understand that a grep and test18:03
mordredharlowja_: it was because there was a pre-existing perl program called pip18:03
harlowja_ah18:03
harlowja_well there u go, learn something new everyday18:03
harlowja_i just thought it was to be diffferent :-P18:03
mordredclarkb:     if git diff --quiet ; then18:04
mordred?18:04
*** Ryan_Lane has quit IRC18:04
clarkbya18:04
clarkbmordred: er18:04
clarkbmordred: I think you may need to invert it18:04
clarkbmordred: ya, exit code 1 if there are differences and you want to do stuff if there are differences18:05
mordredyup18:05
mordred$ if ! git diff --quiet ; then echo "changes" ; fi18:05
mordredchanges18:05
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Update projects when requirements change  https://review.openstack.org/4006818:05
*** ruhe has quit IRC18:05
jeblairmordred: can you do a shallow clone?18:06
mordredjeblair: can I? I'll be submitting back up to gerrit18:06
dtroyersdague: looks good.  two minor comments but they're not blockers18:06
mordredjeblair: I'm not sure i've ever tried submitting changes to gerrit on a shallow clone - but I'm more than happy to make that change18:07
jeblairmordred: my understanding is that your HEAD commit should be okay; i think it's worth trying.18:07
clarkbwill git review complain if it looks to see how far ahead of $branch you are?18:08
jeblaircould always not use git review18:08
mordredjeblair: git clone --help says you can't push from a shallow clone18:08
sdaguedtroyer: ok, your call. you want me to respin, or push it now and I'll put out a fix patch?18:08
jeblairmordred: ok then18:08
mordredjeblair: I actually toyed with the idea of trying to use devstack-gate nodes ... but then realized that those don't have the key :)18:10
dtroyersdague: clean it up if you have time, I always forget to come back around and clean things up like this18:10
*** nijaba_ has joined #openstack-infra18:10
openstackgerritJames E. Blair proposed a change to openstack-infra/config: testing  https://review.openstack.org/4025818:10
jeblairmordred: ^ from shallow clone.18:10
*** nijaba has quit IRC18:11
mordredjeblair: AWESOME18:11
jeblairmordred: also, istr we wanted to have cached copies of the repos on all jenkins nodes; but i don't think anyone has done that.18:11
mordredjeblair:  I will make that change18:11
sdaguedtroyer: will do18:11
jeblairmordred, clarkb: also, that was using git review.18:11
clarkbcool18:11
mordredjeblair: I'll put cached copies on the slaves on my tdl18:11
mordredjeblair: git clone --shallow=1 ?18:12
jeblairdepth=118:12
mordredfacepalm. yes. that's what I meant :)18:12
jeblairok, back to my jenkinses.18:12
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Update projects when requirements change  https://review.openstack.org/4006818:12
mordredjeblair: my precious, my preciousssss18:12
mordredsdague: btw - I've been purposely not landing any requirements changes in order to wait for the gating18:13
clarkbmordred: https://review.openstack.org/#/c/40254/1 you will need that for 40006818:14
mordredsdague: also, I had an idea for an additional gate check for requrements...18:14
harlowja_mordred a PBR question, is it recommended now that everyone use the python setup.py test functionality that exists18:14
*** Ryan_Lane has joined #openstack-infra18:14
sdaguemordred: ok, we should have it all today18:14
mordredsdague: if we put a hook in devstack somewhere that would allow us to instal things after upgrading setuptools but before installing things18:14
harlowja_btw thx for PBR, a+ ;)18:15
mordredsdague: then we could write a thing that would install any _new_ requirement in the file18:15
mordredto make sure that adding it doesn't screw up other things18:15
mordredbut18:15
mordrednow that I've said that18:15
mordrednevermind18:15
mordredwe'll know that for sure once someone adds it to a project18:15
sdaguedtroyer: ok latest round of grenade patch is up18:16
dkranz mordred DO you think you could give a quick review for https://review.openstack.org/#/c/39291/3 (doc auto-gen in tempest)18:17
dtroyersdague: +2…shall I push it on in?18:17
*** sandywalsh has quit IRC18:17
dtroyermordred: I'm thinking I want to extract the python prereq install like I did the packages in tools/install_prereqs.sh.  That way it can be used outside of stack.sh to get things right beforehand18:19
sdaguedtroyer: yes please18:19
sdagueplus the one below it that we need (should be in the deps list)18:19
*** pabelanger has joined #openstack-infra18:19
*** dina_belova has joined #openstack-infra18:20
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add httpd ssl support to git.openstack.org  https://review.openstack.org/4025318:21
fungimordred: added a couple inline comments to 40068 but lgtm18:22
*** krtaylor has quit IRC18:26
openstackgerritA change was merged to openstack-infra/config: Add Jenkins SSH key to proposal.slave.  https://review.openstack.org/4025418:26
clarkbwhere are we on reenabling neutron tests?18:29
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: add devstack gate to requirements changes  https://review.openstack.org/3977418:29
fungisdague: ^ rebased for a merge conflict18:29
fungiclarkb: https://review.openstack.org/4025018:29
clarkbsdague: nati_ueno can I approve ^ ?18:31
*** sarob has quit IRC18:31
*** odyi has quit IRC18:31
*** sarob has joined #openstack-infra18:31
nati_uenoclarkb: I think we can approve it. Failure rate still looks good https://gist.github.com/nati/615817818:31
*** vipul is now known as vipul-away18:32
sdagueclarkb: go for it18:32
clarkbdone18:33
* fungi grips the safety bar tightly18:33
bodepdcan I delete a branch?18:33
bodepdin gerrit?18:33
bodepdI tried and it failed18:33
fungibodepd: you tried pushing an empty local refname to the remote name?18:34
clarkbbodepd: I think you need extra permissions. force push iiirc18:34
*** sandywalsh has joined #openstack-infra18:34
bodepdI can try that18:34
bodepdnah, I think it's a permissions issue18:35
*** fbo_away is now known as fbo18:35
bodepdfungi: I tried that and I tried the push --delete18:35
bodepdboth resulted in the same error (as did --force)18:35
jeblairbodepd: also try the web ui at https://review.openstack.org/#/admin/projects/18:35
*** sarob has quit IRC18:35
bodepd! [remote rejected] grizzly (can not delete references)18:35
*** dprince has quit IRC18:35
openstackbodepd: Error: "remote" is not a valid command.18:35
openstackgerritA change was merged to openstack-infra/config: Revert "Make gate-tempest-devstack-vm-neutron non-voting"  https://review.openstack.org/4025018:36
sdaguefungi: cool, I've got another one sitting on top of that18:36
sdagueI'll rebase it as well here in a second18:37
fungisdague: oops, i'd have done that one too if i'd noticed18:37
*** odyi has joined #openstack-infra18:37
* fungi curses that gerrit only expands the dependencies section when there's a pending parent, but not for a child18:37
sdaguehmmm.... jenkins fail again - https://jenkins.openstack.org/job/gate-grenade-devstack-vm/24647/18:37
*** boris-42 has quit IRC18:38
clarkbfungi: and automagically scrolls below the commit message18:39
fungiclarkb: yes, i reserve separate curses for that behavior18:39
jeblairsdague: no it's not18:39
sdaguejenkins is gone very sad18:39
sdaguejeblair: no?18:39
jeblairsdague: that job was aborted18:39
sdagueok, what aborted it?18:40
jeblairsdague: so when zuul knows that it's useless to continue running tests for a change, it aborts those tests18:40
jeblairsdague: note on http://status.openstack.org/zuul/ it's two changes behind openstack/heat38467,2 which failed python27 tests18:40
sdagueok, so ZUUL showed it as an ERROR18:40
jeblairsdague: the change ahead of it has several tests aborted18:40
jeblairsdague: jenkins reported back to zuul a FAILURE result.  sometimes based on exactly when in the process jenkins aborts a job, it returns 'failure' instead of 'aborted'.18:41
*** boris-42 has joined #openstack-infra18:41
jeblairsdague: jenkins aborting tests is... weird.  we're lucky it works at all.18:41
clarkbjeblair: sdague I think it has to do with who ends up catching the timeout exception18:41
sdagueok18:41
clarkbs/timeout/abort/18:41
sdagueyeh, a heat stable looks to have been the thing that tripped the rest of the gate18:42
clarkbsimilar mechanism in place for both things18:42
sdaguejeblair: we aren't kicking out on a single fail?18:42
jeblairzuul could probably mask that and continue to report 'aborted' instead.  this is a case of more accuracy being less helpful.  :)18:42
jeblairsdague: no, only merge failures18:42
apevecfungi, jeblair - what made all periodic-tempest-* fail? https://jenkins.openstack.org/job/periodic-tempest-devstack-vm-stable-grizzly/126/18:43
jeblairsdague: i think* it's still the case that failures ahead often cause false failures behind.18:43
apevec./safe-devstack-vm-gate-wrap.sh fails w/o output?18:44
jeblairsdague: * (i don't have data to back that up; just noting observations)18:44
sdaguejeblair: ok, I thought we could pull out and restart the rest of the queue on first fail18:44
clarkbapevec: yes the wrap script is quiet18:44
clarkbapevec: however, we capture what it is doing and stick it in a log file18:44
jeblairsdague: the head, yes, and we do that, but not anything behind the head, because things ahead may not have failed yet18:44
clarkbapevec: http://logs.openstack.org/periodic/periodic-tempest-devstack-vm-stable-grizzly/devstack-precise-hpcloud-az3-182671/126/logs/devstack-gate-setup-workspace-new.txt18:44
jeblairapevec: i just tracked that down, it's my fault18:44
sdagueoh, ok, I thought it was resolved to change that18:45
*** melwitt has joined #openstack-infra18:45
sdaguebecause, for instance, right now we're just blocking the gate for 20 minutes until the heat job finishes18:45
jeblairapevec: i need to reconfigure the jobs to accomodate a recent change i made; i'll push a change for that later today.18:45
jeblairsdague: we did not resolve to change that18:45
sdagueok18:45
*** yolanda has joined #openstack-infra18:45
jeblairsdague: any of the 3 jobs of the change at the head of the queue could fail still18:46
sdaguethey could18:46
jeblairsdague: which would invalidate the heat failure in question18:46
sdaguebut they wouldn't cause that one to pass18:46
jeblairsdague: so we would have to test that again18:46
yolandahi, i'm trying to automate gerrit installation. Is there some way to setup an initial ssh key without adding that from the web interface?18:46
sdaguein this case, they wouldn't :) it's a stable job, nothing ahead of it is18:46
jeblairsdague: we know that, but zuul doesn't.18:46
apevecjeblair, thanks! so I'm looking fwd to no email on stable-maint tomorrow18:46
sdagueright, do you have a good query to tell us how often the recovery would have worked, and how often we're just waiting on fail?18:47
clarkbyolanda: an initial ssh key for a user?18:47
sdaguebecause in my experience the wait is way more common18:47
fungiyolanda: the only mechanisms gerrit has for that are the webui and injecting directly into its backend database with an insert query, as far as i know18:47
jeblairsdague: i do not.18:47
sdaguebut I don't have the data18:47
yolandasounds ugly18:47
fungiyolanda: we used to do the latter, pulling them from launchpad profiles. it was ugly, and didn't solve the problem of needing to stuff your key into a webui anyway18:48
fungijust happened to be a different webui18:48
yolandaso it's a manual step that every user should do, right?18:49
fungiyolanda: every user who wants to submit changes or use gerrit's ssh interface18:49
fungiyolanda: users can still comment on changes without doing that18:49
yolandafungi, yes, trying to setup the gerrit ssh interface18:49
clarkbjeblair: what did the timer trigger in zuul break in the periodic jobs?18:51
*** krtaylor has joined #openstack-infra18:51
jeblairsdague: mordred was brainstorming about the possibility of having zuul start running tests assuming that (in this example) that heat change does eventually get ejected.  i think that would be useful and not unfairly penalize changes that may merge, though it's not trivial.18:53
mordred++18:53
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: add missing neutron-full job to neutron gate  https://review.openstack.org/3977518:53
fungisdague: went ahead and rebased the other one on top of it for you18:54
*** sarob has joined #openstack-infra18:55
*** burt has joined #openstack-infra18:55
clarkbjeblair: that would be really neat. Do you expect to test like that beyond a fail depth of 1?18:55
mordredclarkb: I think essentially it winds up creating a tree of changes18:56
clarkbmordred: yes, which is problematic with a finite set of reources18:57
fungii suppose with a cap on how many changes up the gate we'll branch to spawn parallel testing on failure, it could be tractable18:58
bodepdI tried all of those things and failed18:58
* jeblair goes back to his jenkinses18:58
bodepdperhaps I don't have the right permissions?18:58
mordredwell, I think we already have built in caps on how much we can run at once18:59
mordredso I think we'd eventually queue things18:59
clarkbI hope this math is correct. If N is the number of changes in the gate then we currently run log_2 N tests compared to the branching situation described18:59
mordredand then a solid path of success or failure would emerge and start pruning swaths of tree18:59
fungibodepd: i dug into our acls and didn't immediately see where we'd granted force push permissions to a group for any existing project, though it's possible that's the correct permission on refs/*18:59
jeblairwe will not grant force push19:00
fungibodepd: alternatively, owner permission might solve it, though we haven't done that either19:00
fungibodepd: but i'll happly delete branches on request for you19:01
jeblairfungi: i think owner may at least make the webui work; and i'd be open to that.19:01
*** vipul-away is now known as vipul19:01
fungiright now we only have admiistrators as owner group for any project19:01
fungier, administrators19:01
fungibodepd: which project? we can try that out19:01
jeblairyeah; i'd want to understand what that would entail, but if it is just branch deletion and project description, i'd be okay with that for stackforge projects.19:02
clarkbssh key is in place on proposal.slave. Once we see that has fixed the jobs that push to gerrit I will delete tx.slave19:02
mordredjeblair: I'd be ok with owner perms on stackforge projects19:03
clarkbhttps://review.openstack.org/Documentation/access-control.html#category_owner supports the theory19:03
*** dprince has joined #openstack-infra19:05
fungiwell, it is a superset of other access though, since it allows granting/revoking any other permissions19:05
*** sarob has quit IRC19:06
fungi"Users who are members of an owner group can [...] Grant/revoke any access rights"19:06
*** sarob has joined #openstack-infra19:07
*** nijaba has joined #openstack-infra19:11
*** nijaba has quit IRC19:11
*** nijaba has joined #openstack-infra19:11
*** sarob has quit IRC19:11
*** boris-42 has quit IRC19:11
*** Ryan_Lane has quit IRC19:11
jeblairwell nm then.19:11
*** apevec has quit IRC19:11
*** nijaba_ has quit IRC19:12
clarkblooks like you can delegate subbranch space ownership, but that doesn't really help here19:12
*** lcestari has quit IRC19:13
*** lcestari has joined #openstack-infra19:14
*** sarob has joined #openstack-infra19:14
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779419:14
fungiso anyway, bodepd, the answer seems to be branch deletion will need you to ask in here, on the openstack-infra ml or via a bug filed against openstack-ci on lp19:14
fungibodepd: but if you have a list of the projects+branches you want deleted, i'll be happy to take care of it19:15
yolandafungi, i added my ssh keys into gerrit interface, and now i'm trying ssh -vv -p 29418 91.189.93.38 gerrit version19:15
yolandabut it gives me permission denied, although i pasted my correct keys19:15
yolandai'm logged into gerrit using sso19:15
fungiyolanda: is your username in gerrit the same as your local username?19:15
yolandais there something i'm missing?19:15
fungiyolanda: check the username you have listed at https://91.189.93.38/#/settings/19:17
yolandafungi, no, my username in gerrit is the one from sso: yolanda.robla@canonical.com19:17
fungiyolanda: that's the username field in gerrit, or the email address field?19:17
fungiyolanda: the "username" in gerrit is where you set what ssh account name you intend to use when connectnig19:18
yolandaoh, username is empty, i need also to add it manually?19:19
fungiyolanda: yes, click there and put in what ssh username you want19:19
fungithe way to think about it is that ssh authentication (username, keys) is bootstrapped manually from your web interface identity19:20
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779419:21
yolandafungi, i did a mistake with the user, but there isn't any possibility to update it?19:22
*** Ryan_Lane has joined #openstack-infra19:22
fungiyolanda: yet another shortcoming of gerrit. the only way to edit the username for an account is via an update query on the backend database19:23
*** Ryan_Lane has quit IRC19:23
openstackgerritA change was merged to openstack-infra/config: add devstack gate to requirements changes  https://review.openstack.org/3977419:23
fungiyolanda: if you look in your gerrit db, the account_external_ids table should have an entry mapping your numeric account_id to an external_id like "username:something"19:24
fungiyolanda: you could actually just delete that row from the table and then see if the webui willlet you enter it again (rather than futzing with an update query)19:24
openstackgerritA change was merged to openstack-infra/config: add missing neutron-full job to neutron gate  https://review.openstack.org/3977519:25
fungisdague: ^ both merged successfully this time19:25
sdaguenice19:26
fungiyolanda: apparently earlier versions of gerrit used to support changing usernames through the settings page, but then they disabled it because they implemented the ability to add user branches win which they embedded the username rather than the account id, and didn't want to have to engineer a way to automatically rename those19:27
fungiseems silly to me, but that's the justification i found on their discussion list a while back when i tracked it down19:28
bodepdfungi: I accidentally created a grizzly branch for quantum19:29
*** Ryan_Lane has joined #openstack-infra19:29
fungibodepd: i'll kiwf19:29
bodepdstackforge/puppet-quantum : grizzly19:29
yolandafungi, and what's the workaround?19:29
bodepdfungi: thanks!19:30
*** gyee has quit IRC19:30
yolandai'm just working on a charm so i could destroy the service and redeploy it, but in the real world what should be the solution?19:30
mordredfungi: have you ever used the userbranch  thing?19:30
fungibodepd: so get rid of "grizzly" but keep "stable/grizzly" as is?19:30
mgagnefungi: yes19:31
fungiyolanda: in the real world, i connect to the mysql database with the mysql client locally from a shell account on the gerrit server, query the account_external_ids table to see what the username was for that user, then issue an sql update query to replace it with what they want19:32
fungimordred: i've never tried it out, no19:32
*** psedlak has quit IRC19:32
fungimgagne: bodepd: should be all set now19:32
mgagnefungi: thanks!19:32
fungiyolanda: it's ugly, but so far only comes up about once or twice a month19:33
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779419:33
*** mriedem has quit IRC19:34
*** boris-42 has joined #openstack-infra19:35
*** Ryan_Lane has quit IRC19:35
*** sandywalsh has quit IRC19:36
*** ArxCruz has joined #openstack-infra19:37
*** ruhe has joined #openstack-infra19:38
bodepdfungi: thanks!19:39
jeblairin a brand new jenkins installation it creates a file called "secret.key.not-so-secret"19:41
jeblairthat just about sums up the jenkins security model19:41
*** ruhe has quit IRC19:41
*** dina_belova has quit IRC19:43
fungiha19:43
fungithat's classic19:43
mordredjeblair: fantastic19:44
*** sandywalsh has joined #openstack-infra19:45
*** vijendar has quit IRC19:48
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779419:49
* pleia2 mutters about aligned rockets19:49
*** mriedem has joined #openstack-infra19:49
mordredsdague: the grenade changes landed, I'm rechecking https://review.openstack.org/#/c/35705/19:49
jeblairhttps://jenkins01.openstack.org/ and https://jenkins02.openstack.org/ exist19:54
jeblairwith a basic version of the global config xml files i manually copied into place (i have that in a tarball, so we can work on puppetizing it)19:55
fungipleia2: see security-related comment on the https change19:56
fungipleia2: other than that, lgtm19:56
*** vipul is now known as vipul-away19:56
fungijeblair: too awesome!19:56
*** vipul-away is now known as vipul19:56
pleia2fungi: thanks!19:56
jeblairworking on jenkins-jobs now19:56
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add httpd ssl support to git.openstack.org  https://review.openstack.org/4025319:57
pleia2hm, actually19:58
fungipleia2: puppet lint rejects your offering on 3779419:58
*** dhouck has quit IRC19:58
fungioh, puppet syntax actually20:00
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add httpd ssl support to git.openstack.org  https://review.openstack.org/4025320:00
pleia2there, fixed up all ssl permissions20:00
pleia2fungi: hrm, reviewing20:00
fungipleia2: you have an extra <% end -%> in replication.config.erb20:01
fungiseems to be the gist of its complaint20:01
pleia2ah, good eyes20:01
fungii only know to recognize that because i've done it myself on at least a few occasions20:02
openstackgerritElizabeth Krumbach Joseph proposed a change to openstack-infra/config: Add replication of git from gerrit to git.o.o  https://review.openstack.org/3779420:03
pleia2too much copying around of things in that file :)20:03
pleia2should be better now20:03
fungicopy+paste... both the cause of and solution to most coding errors20:04
*** SergeyLukjanov has quit IRC20:07
*** nijaba has quit IRC20:09
fungipleia2: cgit@git.openstack.org:/var/lib/git/${name}.git works with no protocol specifier (e.g., ssh://)?20:11
*** nijaba has joined #openstack-infra20:11
pleia2fungi: good question20:11
*** vipul is now known as vipul-away20:11
fungiwasn't sure if that had been tested20:11
pleia2fungi: I tested one version of it that I had, but it's been several revisions+weeks so I better give it a go again20:12
fungipleia2: looks like it should be fine the way you have it... https://review.openstack.org/Documentation/config-replication.html20:13
pleia2fungi: that was it - github is ssh right?20:13
pleia2I think I just copied what it was doing there20:14
*** boris-42 has quit IRC20:14
fungiyeah, seems that way20:14
pleia2yeah, remember reading the docs now :)20:14
fungilgtm!20:14
pleia2and I'm assuming that ${name} will expand properly20:15
pleia2I don't have a setup quite this complex in testing20:15
*** vipul-away is now known as vipul20:17
yolandafungi, i was able to log in and use ssh commands, but i need to have the privilege to create-account. How can i set it up, still more user interface needed?20:18
fungiyolanda: https://your.gerrit.server/#/admin/projects/All-Projects,access20:20
*** vijendar has joined #openstack-infra20:20
yolandaso manual setup is needed20:21
fungiyolanda: in that acl we have a "Global Capabilities" section at the top with an "Administrate Server" permission delegated to a group called "Administrators" and the members of that group are able to create-account20:21
fungiyolanda: if you look on the filesystem, parallel to the other org/project directories you'll see a project called "All-Projects"20:22
yolandafungi, i cannot see that screen, i only see the reference: refs/*, but no global capabilities section20:22
fungiyolanda: okay, it's likely a chicken-and-egg issue there... you probably have an initial gerrit administrator account of some kind which can modify that20:23
fungiyolanda: you can probably just add your account_id as a member of Administrators with an update to the account_group_members table20:24
yolandatouching directly mysql?20:27
fungion our gerrit, Administrators is group_id 1 (that's probably typical of most any gerrit server), but you ca confirm on yours by looking in the account_group_names table20:27
jeblairwoo!  JJB is running on jenkins01 and jenkins0220:28
fungiyolanda: well, normally when you set up a gerrit from scratch i think you get an administrator account initially which is expected to be used to do most of the initial configuration in the webui. it's been a little while since i built one from google's instructions, though zaro may be able to confirm20:28
mordredjeblair: woot20:28
fungijeblair: sounds very close20:28
mordredfungi, yolanda whoever is the first person to log in to the gerrit ttw gets admin access mgically20:28
clarkbjeblair: exciting20:29
yolandamordred, i use sso, and i've logged for first time with my user, but no admin rights20:29
fungioh, right, mordred just built one recently too20:29
yolandai'm on anonymous and registered users group only20:30
jeblairclarkb, fungi, mordred: i'm going to be slowly taking persistent slaves offline one at a time to move them to the new masters.20:30
clarkbjeblair: ok20:30
mordredjeblair: I suppoert you in that20:30
clarkbjeblair: any particular partitioning scheme you want to use for that?20:30
jeblair(i'll leave a reason note in the webui as i do that)20:30
fungijeblair: sounds like delicate surgery--let me know if you need any assistance on parts of that20:30
jeblairclarkb: how about odds to jenkins01 and evens to jenkins02?20:31
clarkbjeblair: wgm20:31
fungithat makes sense to me (and then divvy up special-purpose slaves at random)20:31
clarkb*wfm20:31
jeblairthat'll let us use our current crop on the two masters and leave room for expansion20:31
jeblairfungi: i was planning on leaving special purpose slaves attached to jenkins.o.o for now20:32
fungithat works too20:32
jeblairfungi: and in the long run, continue to segregate them for improved security20:32
clarkb++20:32
jeblair(but possibly move them to a replacement jenkins.o.o)20:32
fungidefinitely20:32
jeblairanyway, if we expand to 3 test-running masters, we'll need a new system, but this'll hold us for a bit i hope.20:32
fungiheralding back to our "slaves are trusted by jenkins to run arbitrary code on their master" discussion20:32
fungidid anybody on #jenkins follow up to your questions about that?20:33
fungii never saw a response if so20:33
jeblairfungi: i didn't see one.20:33
fungi:(20:33
fungiwell, we have a near-term workaround of putting untrusted slaves on untrusted masters, and a longer-term possibility of moving the sensitive slaves off jenkins entirely20:34
*** yolanda has quit IRC20:34
fungiso i am less worried now20:34
jeblairyep20:35
clarkbis there any concern that a master could become a gearman cleint?20:36
clarkbin addition to having just a bunch of workers?20:36
clarkboverall I think it is a better security situation but something like jenkins becoming a gearman client would worry me20:37
jeblairclarkb: it already is20:37
clarkboh20:37
jeblairclarkb: that is a concern, that a master could take jobs it shouldn't be taking...20:37
jeblairclarkb: however, if it doesn't have the creds to do something like publish an artifact20:38
jeblairclarkb: the security situation isn't that bad (but annoying, because our job didn't get run)20:38
jeblairclarkb: we could address that (later) by segregating the gearman queues20:38
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Add new jenkins masters to zuul firewall  https://review.openstack.org/4028020:40
jeblairclarkb, fungi, mordred: speaking of which, could i get a speedy review on that brown bag? ^20:40
clarkbyup20:40
* mordred look20:40
jeblairthanks20:40
clarkbI am going to kick into review mode now that lunch has been had. I will start with that change20:40
clarkbwe really need a better story for firewall management across our "clusters" of things20:41
clarkbbut that lgtm20:41
clarkbmaybe that would be a good first candidate for salting?20:41
fungioh, mordred was looking too. sorry, i already approved20:41
mordredfungi: all good20:42
openstackgerritA change was merged to openstack-infra/config: Add new jenkins masters to zuul firewall  https://review.openstack.org/4028020:43
clarkbnotmyname: had a chance to think about https://review.openstack.org/#/c/39388/ ?20:43
*** dina_belova has joined #openstack-infra20:44
notmynameclarkb: I actually don't remember the last answer I gave you ;-)20:44
clarkbnotmyname: you said you would catch up on work and hopefully let me know by the end of last week :)20:44
notmynameclarkb: ah, ok :-)20:44
clarkbfungi: mordred https://review.openstack.org/#/c/39513/ want to look at that and make sure I didn't butcher the logo too horribly?20:45
*** fbo is now known as fbo_away20:46
*** odyssey4me2 has joined #openstack-infra20:46
clarkbmordred: for https://review.openstack.org/#/c/33204/ how comfortable are we with making that change? eg will we have to do a bunch of manual surgery to fix setuptools before devstack-gate will update itself?20:46
russellbheads up guys ... i'm about to push a novaclient release.  we haven't done one in months.  ping me if something crops up that could be caused by it so i can help address it asap.20:46
mordredrussellb: k20:46
mordredrussellb: I _think_ we should be ok20:47
mordredrussellb: oh - hey, you know what?20:47
russellbyeah i think so too, but figured it didn't hurt to mention it20:47
*** fbo_away is now known as fbo20:47
mordredrussellb: if you're going to release on, removing d2to1 from the requirements and the setup_requires would be nice20:47
mordredI was just about to start pushing out patches for that20:47
russellbmordred: ok, i can wait20:47
fungiwe always love heads up on potential breakage, no matter how unlikely20:47
mordredlemme send you a patch real quick20:47
russellbk20:47
russellbfungi: :-)20:47
notmynameclarkb: I'm looking back over the recent patches that have merged. I don't see the test running20:48
*** dina_belova has quit IRC20:48
notmynameclarkb: eg https://review.openstack.org/#/c/39361/20:49
*** odyssey4me has quit IRC20:49
clarkbnotmyname: it isn't running in the gate, only as part of the check tests that run when you submit patches20:50
notmynameclarkb: ok20:50
clarkbnotmyname: on that example change the test ran and was reported in the last comment from July 3020:50
*** odyssey4me2 has quit IRC20:50
notmynameah ok20:51
fungireasoning being that devs will almost certainly never look at non-voting test results after approval, so they're a waste of resources to run in the gate pipeline20:51
fungiunless you're trying to collect post-facto statistics on them20:52
mordredrussellb: https://review.openstack.org/40282 there's a full sync (what we're about to start running in the gate)20:52
notmynameclarkb: and https://jenkins.openstack.org/job/gate-swift-devstack-vm-functional/ is the aggregate page, right?20:53
russellbmordred: ok ... put my +2, but will wait to see tests pass, and then bug someone else to approve20:53
clarkbnotmyname: yes, however we delete logs older than a day there20:54
mordredrussellb: ++ thanks20:54
clarkbnotmyname: so you are looking at an aggregate of the last 24 hours or so20:54
*** dina_belova has joined #openstack-infra20:54
mordredfungi: got a sec for an easy change that's blocking lifeless ? https://review.openstack.org/#/c/39858/20:54
notmynameclarkb: ok, that's ok (makes sense for now)20:54
jeblairnotmyname: we can make a graph of success/failure over a longer period (but can't associate those points with individual changes)20:54
lifelessmordred: yes that is the one20:54
notmynameclarkb: jeblair: start gating. +120:54
fungiclarkb: logo looks great20:55
fungimordred: having a look20:55
clarkbnotmyname: awesome. I can push that change through20:55
notmynameclarkb: jeblair: now, let's figure out how to make probe tests run on a patch ;-)20:56
clarkbmordred: https://review.openstack.org/#/c/33204/ has new comments20:56
notmynameand by "let's" I mean, "you guys have fun"20:56
clarkbunfortunately a lot has changed since you first proposed the pbr for devstack-gate change20:56
jeblairnotmyname: refresh my memory about probe tests please?20:56
notmynamejeblair: between unit tests and functests. the probe tests start and stop various services in the cluster as a whole and ensure that stuff like handoffs and replication and etc work20:57
clarkbnotmyname: change is approved. It will take a few minutes to percolate into zuul, but you will be gating on that shortly20:57
sdaguemordred: 16 mins until the global-requirements devstack results come back20:58
sdaguehad to rebase it again20:58
jeblair(jenkins is nearly idle, which is frustrating my attempts to actually see if the new masters work!)20:58
clarkbfungi: https://review.openstack.org/#/c/35104/ is that something I should be focusing on yet?20:58
mordredjeblair: I can push patches if that would be helpful...20:58
*** dina_belova has quit IRC20:58
openstackgerritA change was merged to openstack-infra/config: Vote and gate on swift functional tests.  https://review.openstack.org/3938820:58
clarkbmordred: you can address comments in 33204 :)20:58
jeblairmordred: it would, actually, especially ones with python26 tests20:58
mordredjeblair: I can _VERY_ easily trigger requirement update patches...20:58
mordredclarkb: on it20:58
*** psedlak has joined #openstack-infra20:58
clarkbjeblair: for the other launch slaves how are we setting the maximum slave numbers20:59
*** psedlak has quit IRC20:59
clarkbjeblair: did you take 96 and divide by 3?20:59
*** ArxCruz has quit IRC21:00
jeblairclarkb: i have not done that yet; but i intend to start them small to make sure they work, then up to 96/3, then 96/2.21:00
fungiclarkb: yeah 35104 is cool. i wanted to try spinning those tests up on some out-of-service jenkins slaves just to confirm that the nondeterministic shutil problems were mine and not intrinsic to how the tests are written, but haven't gotten to it yet (and i should feel bad)21:01
jeblairclarkb, fungi, mordred: the new version of jenkins has that global 'credential storage' thing; which may necessitate a change to how devstack-gate launches slaves.  i'll be finding that soon.21:01
clarkbfungi: ok, we can land the tests and make them non voting if you are worried21:02
fungiclarkb: alternative tack there, i think, is that i should just propose a change to enable python26,27,33 tests on git-review first (with a no-op in place) and then recheck that change21:02
fungiclarkb: they're not actually being run yet anyway21:02
mordredjeblair: patches incoming21:02
clarkbfungi: I like the idea of enabling them that way and rechecking the change to add the tests21:02
clarkbfungi: it will make reviewing the tests easier too21:02
mordredjog0: ping21:03
fungiclarkb: also for the pbr-ization change that depends on, i think i'd like to tag a git-review release on the change ahead of it (top of master now or any trivial fixes we squeeze ahead of it at the last minute)21:03
*** gyee has joined #openstack-infra21:04
jeblairmordred: thank you https://jenkins01.openstack.org/job/gate-python-glanceclient-python26/1/21:04
clarkbfungi: ++21:04
mordredjeblair: w00t21:04
mordredjeblair: for once an automated patch bomb from me is useful!21:04
fungiclarkb: thinking being that the release which switches to pbr is a fairly major packaging change for the tool, so having alast known good version to point people at with no outstanding fixes pending would be good21:05
jeblairmordred: that job is history!  it just might be the first job run as part of a distributed multi-master jenkins system.  :)21:05
mordredmaybe I'll tweet that21:05
clarkbfungi: indeed. The switch to pbr hasn't been uneventful, I think there is value in releasing first to have as much time to test the pbr change as possible21:06
jeblairand it succeeded.21:06
fungiclarkb: just in case it tickles problems on $random_platform like freebsd or mac osx or arch linux or who knows where some people run this21:06
clarkbjeblair: congrats21:06
clarkbI remember the scheming about this from almost a year ago21:06
jeblairclarkb: and now we have our preciouses21:06
fungii need to run off and dine, but will beat on those things when i get back in a bit21:06
clarkbfungi: ok, I will hold off reviewing those two git review changes until after you have jenkins reporting test results back21:08
zarojeblair: awsome!21:08
jeblairzaro: thanks to your plugin.  :)21:08
jeblairmordred: want to see something cool that i did not anticipate?21:09
mordredjeblair: yes!21:09
jeblairmordred: despite the fact that these didn't work (the jobs need a small change); check out https://jenkins.openstack.org/job/periodic-tempest-devstack-vm-stable-grizzly/126/21:09
jeblairmordred: it shows all the periodic tempest jobs together...21:09
jeblairmordred: because of the way i grouped them in the zuul layout -- they form a zuul build set.  :)21:10
clarkbnice21:10
mordredneat!21:10
clarkbjeblair: because they all belong to tempest's periodic pipeline?21:10
jeblairclarkb: oh, i forgot to answer -- it looks like the way gearman plugin starts the job, the default parameter doesn't get set; so we just need to set ZUUL_BRANCH in the job itself rather than as a paremeter.21:11
jeblair(i like that better anyway)21:11
jeblair(or alternately, to have ZUUL set the branch parameter; but that needs a little more sophistication in the timer trigger)21:11
*** nijaba_ has joined #openstack-infra21:11
*** thomasem has quit IRC21:11
jeblairclarkb: yes (tempest periodic pipeline)21:11
mordredjeblair: so, I have another patch bomb loaded if you want another21:12
*** pabelanger has quit IRC21:12
jeblairmordred: not atm; i'm probably a while from the next time i need major testing; bombing isn't useful for me, but you may not want to wait.21:12
*** nijaba has quit IRC21:12
clarkbjeblair: I prefer setting it in the job too21:13
clarkbjeblair: I like keeping tools simple and the timer trigger shouldn't do much more than trigger on a timer imo21:13
mordredjeblair: ok. I'll do this one (it's updating the contents of the last one, which are slightly off)21:13
jog0mordred: pong21:19
mordreduhm. python-swiftclient does not participate in the devstack gate21:21
notmynamemordred: is there a reason or is that an oversight?21:22
clarkbmordred: correct, I remember asking about that once and I believe the reason is it doesn't intersect anything in the gate21:22
mordredwe install it21:22
sdaguemordred: and we have a winner21:22
sdaguehttps://review.openstack.org/#/c/35705/21:22
mordredand with the new coordinated requirements gating, I think we should add it, else we're going to get burned21:22
clarkbmordred: I agree21:22
*** vipul is now known as vipul-away21:23
mordredsdague: AWESOME21:23
clarkbmordred: as that adds an intersection21:23
sdaguedtroyer: https://review.openstack.org/#/c/35705/ you want to give it a look, and +A if you like it21:23
mordredjeblair: ^^21:23
*** woodspa has quit IRC21:24
openstackgerritRussell Bryant proposed a change to openstack-infra/reviewstats: Update nova-core membership  https://review.openstack.org/4029721:24
mordredjog0: so - with the new things we're doing with requirements, I think hacking 0.7 in the global reqs files is a potential issue21:24
*** pabelanger has joined #openstack-infra21:24
dtroyersdague: I was looking at it on fedora/centos.  no joy yet but I think that's still due to the pip installation problems21:24
mordredjog0: and we need to come up with a strategy21:24
sdaguedtroyer: that's my guess21:25
clarkbmordred: earlier I suggested treating it like pep8,21:25
clarkbmordred: allow new rules in at the beginning of a cycle21:25
sdaguedtroyer: I think we have to unwind fedora after this21:25
*** dkranz has quit IRC21:25
mordredjog0: because we're about to start proposing requirements update patches automatically to all of the projects every time reuqirements changes21:25
mordredjog0: and right now, that's going to fail for most projects because of hacking 0.721:26
dtroyersdague: yeah, too many things at once isn't going well ;)21:26
mordredsdague: I agree21:26
sdaguealso, I think we need a volunteer, possibly from red hat, to help get fedora up as a devstack target21:26
clarkbmordred: https://review.openstack.org/#/c/35705/16/functions where does REQUIREMENTS_DIR come from?21:26
dstufftFedora, slightly more broken than ubuntu with regards to pip21:26
clarkbmordred: that is set by a previous change to add openstack/requirements to devstack?21:26
sdagueclarkb: lib/infra21:26
mordredsdague: I'll write a mailing list message about pip/pkgs21:27
dtroyerIan has been doing a lot along those lines, specifically for rhel6 but I think if rhel6 is happy fedora is ahppy in general21:27
openstackgerritA change was merged to openstack-infra/reviewstats: Update nova-core membership  https://review.openstack.org/4029721:27
mordreddtroyer: yeah - the main problem is the rpm vs. pip interaction on fedora/rhel21:27
sdaguedtroyer: yeh, but I'd really like to know on each devstack change if it's actually going to work on fedora21:27
sdagueso if the pg target was on fedora, that would be really handy21:27
sdaguewe do kind of officially support both latest ubuntu and fedora, but we only run integration on ubuntu21:28
dtroyeragreed…we've set fedora as the target and that's where I want to focus.21:29
jeblairperhaps we should run it on centos instead (due to the same release cycle concerns that led us to chose centos for the unit tests?)21:29
mordred++21:30
clarkb++21:30
lifelessstevebaker: probably worth checking the design here; then doing it - avoiding round trips21:30
mordredand we've already got partial centos support in the pool21:30
clarkbmordred: centos should work from a puppet perspective because unittest slave is a superset of the d-g slave image21:30
mordredstevebaker: I believe you want to add pypi-jobs to python-jobs21:30
mordredas in- I think you want both21:30
mordredclarkb: ^^ if they want to do pypi publication, that's right, right?21:31
clarkbwe would need multiple image support in d-g. I think that exists simply by adding the ready slaves number >0 to an image in the DB21:31
clarkbmordred: yes21:31
mordredyes. it does21:31
jeblairclarkb: d-g has (and has used) multiple image support21:31
mordredwe had oneiric slaves already21:31
stevebakeroh, ok. layout is now looking like this http://paste.openstack.org/show/43238/21:31
clarkboh ya, and it is as simple as adding the row in the DB right?21:31
jeblairclarkb: yep21:32
jog0mordred: yeah that will make things a little tricky21:32
sdaguejeblair: then centos would need to become a first class citizen on devstack21:32
jeblairclarkb: will be added with 'devstack-{imagename}' label21:32
clarkbstevebaker: I don't think you need the post mirror jobs21:32
jog0mordred: and you want to propose the most up to date deps every time right?21:32
stevebakerclarkb: ok21:32
sdaguejeblair: f19 would be much better21:32
mordredjog0: we do21:32
clarkbstevebaker: so remove lines 13 and 14 and the last character of line 1221:32
jeblairsdague: how close are centos/fedora for our needs?21:32
sdaguejeblair: I think f19 is the right target, centos is so old21:33
sdaguethere are so many work arounds you need21:33
jog0mordred: and i don't like the idea of blocking until the new rules are fixed21:33
jeblairsdague: the tc decided to support latest ubuntu/fedora without breaking LTS/RHEL.21:33
mordredso... the thing with latest fedora and why it might be a problem21:33
mordredis the reason we ditched oneiric21:33
clarkbsdague: the problem with that is the distro upstreams iterate too quickly and don't support the older things long enough21:33
jog0mordred: don't you need something for the general case of non-backwards compat changes?21:33
clarkbsdague: so you run into a situation where you have unsupported releases doing all your testing while you wait for HP/rackspace to update their image list21:34
jeblairsdague: in my view, that makes LTS/RHEL a reasonable LCD for tests.21:34
mordredthat being - we like to continue testing stable releases on the thing we tested them on at release time21:34
stevebakerclarkb: how about this? http://paste.openstack.org/show/43239/21:34
clarkbthe other problem is when you are trying to test stable/folsom and it doesn't run on f2021:34
mordredand f19 doesn't have the same lifespan as our stable releases21:34
*** dprince has quit IRC21:34
mordredjog0: we're about to start syncing requirements automatically in the devstack gate21:34
clarkbstevebaker: that looks good. Don't forget to update projects.yaml in modules/openstack_project/files/jenkins_job_builder/config21:35
mordredjog0: so people wanting to consume new upstream versions of things that are incompat are going to have to do work anyway21:35
jog0but we don't run hacking in devstack21:35
mordredjog0: that's right - but hacking seems to be the only thing where the model is breaking21:35
clarkbstevebaker: zuul layout.yaml tells zuul which tests to run and projects.yaml tells jenkins job builder which job templates to instantiate and apply to jenkins itself21:35
stevebakerok21:35
jog0mordred: hrmm we could add some special log in for this case21:36
jog0logic*21:36
mordredjog0: https://review.openstack.org/#/q/status:open+branch:master+topic:openstack/requirements,n,z fwiw21:37
jog0if this is only for devstack and not unit tests then is this still an issue?21:37
mordredit's not a gate breaking issue21:37
mordredit's that we willbe proposing patches to update things21:37
mordredand theyu'll be breaking on pep821:37
sdaguejeblair: so the problem is lots of things don't work on RHEL6. And lots of them are only fixed by RDO packages later (including replacement kernels)21:38
sdagueI think you'll massively take a hit in dev velocity if people need to wait for RH6 RDO to fix something21:38
mordredmaybe the answer there is that someone just has to fix the proposed changes21:38
lifelessmordred: btw per request I'm reviewing https://review.openstack.org/#/q/status:open+project:openstack-dev/pbr,n,z daily21:38
mordredlifeless: thanks. I appreciate that21:38
jog0mordred: actaully yeah that would work21:38
*** krtaylor has quit IRC21:38
lifelessmordred: but everything there either failed V or has -1's already. I'm not dogpiling :).21:38
mordredjog0: that's what I'm doing right now on the client libs21:39
jog0hacking x goes out, and auto dep patch goes out21:39
mordredlifeless: :) I'm deferring those for a bit to work on other things21:39
jog0it braeks someone has to fix it before it merges21:39
sdagueRHEL6 is almost as old as lucid21:39
clarkbjog0: mordred: I think that will be particularly painful with nova and other high volume projects21:40
mordredjog0: right. although also I think in general if we add new hacking checks midcycle too many times someone will kill us21:40
clarkbjog0: mordred: the gate will break every time hacking updates and there will be a huge rush to push fixes in and you end up in a rebase mess21:40
mordredo, back to what clarkb said - we shoudl probably aply the pep8 policy here21:40
mordredwhich is only rev the release once per cycle21:40
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Remove ZUUL_BRANCH peridic job parameter  https://review.openstack.org/4030121:41
clarkbsdague: I don't think we disagree that it is suboptimal. But you open yourself to a bunch of problems trying to track latest version of distros when you don't have galnce service21:41
jog0clarkb mordred: yeah but that is a managable issue.  or someone disables the new tests in a seperate patch21:41
*** UtahDave has joined #openstack-infra21:41
sdaguemordred: so honestly, I'd wait on force updating requirements in the projects. We've solved it in the devstack side of the gate now, and I think we should discuss with a wider ptl audience to figure out the unit test side21:41
jeblairdtroyer: what is http://partnerweb.vmware.com/programs/vmdkimage/debian-2.6.32-i686.vmdk about?21:42
clarkbsdague: ubuntu and fedora both have short periods of support now. Short enough that it is possible to end up in a spot with no security updates coming from upstream21:42
jeblairdtroyer: i just started a wget on it and it says it will take 48 minutes to download21:42
jog0clarkb: when a new hacking is cut we just propose some disable new tests that are non-trivial to fix right away patches21:42
openstackgerritSteve Baker proposed a change to openstack-infra/config: Do not run python jobs for tripleo-image-elements  https://review.openstack.org/3985821:42
jog0and once those merge merge new reqs patch21:42
dtroyerjeblair: IIRC that's the default image that should only be downloaded for vsphere (checking)21:43
sdagueclarkb: so there is no way for us to push our own ami in?21:43
clarkbjog0: how is that different than what I propose?21:43
clarkbjog0: my solution does it with a single change to a single repo though21:43
sdagueclarkb: fedora looks like it's giving folks a year21:43
*** mriedem has quit IRC21:43
jeblairdtroyer: yeah, that looks right21:43
clarkbsdague: currently our cloud providers do not give us push access to glance21:43
jeblairdtroyer: devstack-gate has a naive way of caching images and gets them all.21:44
sdaguejeblair: yes, that's their "cirros like" image21:44
jog0clarkb: well in devstack hacking doesn't matter, but for the actual 'pep8' tests I assume those come from local reqs21:44
clarkbsdague: you can do something nasty like takeover node, but that is less than ideal21:44
sdagueclarkb: hmph, that's the suck21:44
jeblairit takes d-g 14 minutes to download it inside of hpcloud21:44
stevebakerclarkb, jeblair, getting closer?  https://review.openstack.org/#/c/39858/21:44
sdaguethat actually seems kind of crazy, when they fixing that?21:44
mordredsdague: they are both working on it21:44
jog0mordred clarkb: I am not fully on board with  hacking release only at beginning of cycle, so far we have done between milestones21:45
sdaguemordred: so after they fixed that, would we be able to think about fedora?21:45
*** fbo is now known as fbo_away21:45
jog02x a year is too infrequent for some things21:45
clarkbstevebaker: yup. are the python jobs not actually used in that project? If so maybe remove that line from projects.yaml?21:45
jeblairi'm less concerned about the timing of new releases than clarkb is21:45
jeblairi feel like that's a minor inconvenience to deal with after we agree on what we ought to be testing based on other reasons (such as release cycle lifetime)21:46
clarkbjog0: I am not advocating you release twice a year. I am advocating we pin the projects twice a year21:46
*** rnirmal has quit IRC21:46
jog0clarkb: that is effectively the same thing21:46
openstackgerritSteve Baker proposed a change to openstack-infra/config: Do not run python jobs for tripleo-image-elements  https://review.openstack.org/3985821:46
stevebakerclarkb: done21:46
jog0clarkb: if no one uses it who cares about the releases21:46
clarkbjeblair: I think release cycle lifetime and length of support are related problems21:47
*** changbl has quit IRC21:48
notmynameclarkb: FWIW, running swift funcational tests locally takes around 70 seconds (on my VM). seems that jenkins takes about 10 minutes21:48
clarkbif length of distro support is <= length of openstack support you will have trouble even without the ability to upload your own images (maybe that is what you mean by it being more important)21:48
clarkbnotmyname: I believe those tests are setting up devstack21:48
clarkbnotmyname: on a single use fresh VM each time hence the additional time21:49
*** sarob_ has joined #openstack-infra21:49
jog0clarkb: I am saying twice a year is not enogh when these are tests written just for us, but  roughly 4x a year at most21:49
notmynameclarkb: ya, ok. (perhaps a perfect use case for openstack + docker)21:49
jeblairclarkb: yes; i'm a bit more concerned about the backend; there are ways we can speed up the frontend (takeovernode, apt-get dist-upgrade, glance) but it's not worth engineering if we don't _want_ to support them because they aren't compatible with our lifecycle.21:50
clarkbjog0: I get that, but hacking feels like the same type of upstream as pep821:50
mordrednotmyname: it's because we need a running cloud21:50
*** dkliban is now known as dkliban_afk21:50
mordrednotmyname: and the only place we currently have to get one of those is by running devtack21:50
sdagueclarkb: I think the difference is that if we only release on boundaries, you'll be getting more code copy / pasted back into the projects21:51
sdagueso they can get extra checks21:51
mordrednotmyname: unfortunatley, openstack+docker isn't likely to help, because we'd still need to run devstack in the docker21:51
mordredand _getting_ a new fresh machine for us takes 0 seconds21:51
notmynamemordred: ya, just thinking about preseeding stuff21:51
mordredsince we pre-spin them in the pool21:51
mordredwe already do that :)21:51
sdaguemaybe if hacking had new checks off by default until a release boundary and there was a way to opt in21:52
clarkbsdague: how is that different than pinning pep8 though?21:52
*** sarob has quit IRC21:52
clarkbpep8 releases often and can provide more checks, but we have collectively agreed to follow a consistent set of rules for six months21:53
sdagueclarkb: because we're writing the hacking rules during a release cycle based on the review feedback we constantly need to give people21:53
sdagueto actively reduce review overhead21:53
*** sarob_ has quit IRC21:53
mordredbut our new checks are written specifically in response to things the project is doing21:53
jog0clarkb: what they said21:54
*** dina_belova has joined #openstack-infra21:54
clarkbfungi: https://review.openstack.org/#/c/37461/ weren't you involved in that situation? do you know if we can remove that pin?21:55
notmynamemordred: odd dependency tree in https://review.openstack.org/#/c/40120/. is the migration to pbr required for that patch?21:55
mordrednotmyname: it is not. I can rebase that if you'd like21:56
*** dolphm has quit IRC21:56
notmynamemordred: it would allow it to get merged ;-)21:56
clarkbnotmyname: mordred did that for every pbr migration and it was a pain point :)21:56
mordrednotmyname: it was on top of the pbr patch because of the following patch which is about working on the autosyncing stuff21:56
*** vipul-away is now known as vipul21:56
mordrednotmyname: we're about to be doing auto-updating from reuqirements in the devstack gate, which will have issues if you're not on pbr ... so I'd love to re-visit the pbr patch at your convenience21:57
notmynameso we're getting to the point of having computers write our code for us now? ;-)21:58
*** dina_belova has quit IRC21:59
clarkbnotmyname: I think jenkins is the number one contributor if you go by lines changed :)21:59
notmynamewhich we all know is the right way to measure progress22:00
clarkball of the stats people neglect to give the infra team credit for that :)22:00
*** vijendar has quit IRC22:00
notmyname(the stats numbers that are published are somewhat of an annoyance to me)22:00
clarkband to be fair Jenkins is just applying translation updates. the translators should be getting the credit22:01
jeblairwe could forge that if we had the info...22:01
jeblairmordred: and actually, we have the info for reqs changes...22:01
notmynamemordred: your commit message says you added copyright headers. you patch added license headers. shall I kill the merge process?22:02
jeblairmordred: you should set the git author to be == to os/requirements git author22:02
jeblairoh, but i bet you amend old commits, don't you?  that gets to be harder.22:02
*** burt has quit IRC22:04
mordrednotmyname: it is a copyright license header ... so I don't think that copyright header is egregiously incorrect - but I will re-spin if you feel differently22:04
notmynamemordred: seems that there is obviously not a copyright line in any of those files. obviously I'm fine with the change (my initial +2/+1), but the commit message seems confusing for when someone (ie me) has to go back through history to see what happened22:06
clarkbmgagne: is there a way to tell puppet lint to ignore errors on a specific line?22:06
clarkbpabelanger: ^22:06
*** sarob has joined #openstack-infra22:06
mgagneclarkb: not that I'm aware of. I guess you are looking for pep8 like flags22:07
clarkbmgagne: ya,22:07
clarkber yes, let me give you a link to the thing I have a problem with22:07
mgagneclarkb: funny, I'm working on fixing (again) puppet-lint for our modules22:07
clarkbmgagne: the namevar for a resource can be exposed through $name right?22:08
notmynamemordred: to be explicit, yes I would like to see a commit message that is clearer for when we need to do `git blame` or `git shortlog` six months from now22:08
mgagneclarkb: yes, and $title in some circumstances22:08
clarkbmgagne: the inline comment on https://review.openstack.org/#/c/37794/22:09
clarkbmgagne: your feedback would be valuable22:09
mgagneclarkb: oh god. I'll check22:09
clarkbpleia2: ^22:09
openstackgerritSteve Baker proposed a change to openstack-infra/config: Do not run python jobs for tripleo-image-elements  https://review.openstack.org/3985822:10
*** mrodden has quit IRC22:10
mordrednotmyname: great! on it22:11
mordrednotmyname: patches incoming22:11
*** nijaba_ has quit IRC22:11
*** nijaba has joined #openstack-infra22:12
*** nijaba has quit IRC22:12
*** nijaba has joined #openstack-infra22:12
mgagneclarkb: check is looking for "${"22:13
mgagneclarkb: https://github.com/sbryant/puppet-lint/blob/master/lib/puppet-lint/plugins/check_strings.rb#L6422:13
mgagneclarkb: but removing {} would trigger "variable not enclosed in {}"22:14
mordrednotmyname: also - I mentioned a gate automation need to escalate our conversation about pbr - I just verified that that is incorrect22:14
mordrednotmyname: I still am ready to re-have that conversation - but I have the appropriate safeguards in place for the other things around requirements processing to work22:14
mordredjeblair: AH - my brain JUST NOW was able to read your text above22:15
clarkbmgagne: and single quoting the string will fail because there is a varialbe in an uninterpoaltable string?22:15
mgagneclarkb: yes22:15
mordredjeblair: I am re-committing, but I'm pulling based on topic22:15
mgagneclarkb: trying something on my side: would escaping { with \ do the job?22:15
clarkbmgagne: I think if we can single quote that string we will be fine which is why I was looking for a way to annotate the line to ignore lint errors22:15
mordredjeblair: so I could add in co-authored-by lines22:16
clarkbmgagne: oh maybe22:16
mordredjeblair: OR - I could not re-commit22:16
mgagneclarkb: puppet-lint isn't that fancy sorry ^^'22:16
mordredjeblair: I could commit, forging author information, and commit on top of the last one22:16
mordredjeblair: so that they depend on each other22:16
jeblairmordred: co-authored-by might be a good way of compromising between attribution and not annoying people with multiple auto commits.22:16
mordredjeblair: but each have the author of the change22:16
mordredjeblair: ++22:16
mordredjeblair: mind if we file that as a feature enhancement for the future?22:17
jeblairmordred: (perhaps if they are merged quickly in practice without recommits, we could back down later)22:17
clarkbmordred: https://review.openstack.org/#/c/37987/4/modules/openstack_project/files/zuul/layout.yaml does that play nice with the eventual state of the requirements world?22:17
jeblairmordred: sure22:17
mordredsdague: also- when you said you wanted to hold off on auto-update patches ...22:17
mordredclarkb: yes. the -requirements jobs will not change22:17
clarkbmordred: I have a hunch we may end up breaking savanna if things in the requirements world move away from them22:17
clarkbmordred: ok, only devstack and friends change?22:18
mordredclarkb: I was musing earlier that we sohuld make the auto-requirements patch creation an opt-in process for projects like savanna that might want that22:18
jeblairI'm starting a graceful shutdown of jenkins01 and jenkins02 to work on the credential store thing.22:18
mordredalso - futher feature request22:19
clarkbjeblair: have fun22:19
clarkbjeblair: out of curiousity are we running latest jenkins release?22:19
clarkbor are you using the same jenkins verson across the baord?22:19
jeblairclarkb: 01 and 02 are; jenkins.o.o is not22:19
clarkbcool22:19
mordredjeblair: I saw puppet patches forplugins come across - are you using those for these guys?22:21
mgagneclarkb: it does not work22:21
clarkbmgagne: :(22:21
mgagneclarkb: I end up with "test $\{name\} test" in my file22:21
clarkbmgagne: what if $\{name\} is in a double quoted string?22:22
jeblairmordred: yes, i did use the patch i proposed.22:22
clarkbof course that will also fail lint because no variable will be in that string22:22
mgagneclarkb: I'll try22:22
mordredjeblair: excellent. I thnk that's sexy22:22
jeblairmordred: bodepd gave it to us.  it's cool.  :)22:22
*** pentameter has quit IRC22:22
clarkbanyone else want to review https://review.openstack.org/#/c/38119/4 before I approve it? It adds some python3 compatibilty to jeepyb and bumps the hacking version22:23
clarkbmordred: https://review.openstack.org/#/c/38176/ is that going to be fixed?22:24
mgagneclarkb: WARNING: double quoted string containing no variables on line 222:24
mordredclarkb: yes. right noiw22:25
clarkbmgagne: I expected that. This makes me sad22:25
mgagneclarkb: I'm a sad panda too now22:25
mgagneclarkb: I'll try to see if I can hack something22:25
*** prad_ has quit IRC22:26
openstackgerritMonty Taylor proposed a change to openstack-infra/config: Gate jeepyb and openstack/requirements on pbr  https://review.openstack.org/3817622:28
mordredclarkb: ^^22:28
mordredthere you go22:28
mordredyou know what - once we have that - our requirements are going to have the HELL tested out of them22:29
*** datsun180b has quit IRC22:30
clarkbI am -2'ing changes like https://review.openstack.org/#/c/38114/ since global-requirements.txt makes it a noop22:33
mgagneclarkb: I think I had the worst idea ever22:33
clarkbmgagne: I am ready for it22:33
mgagneclarkb: testing atm22:33
mordredI think I believe there is enough testing on requirements now that I'm going to start reviewing them22:34
mordredtoo22:34
mordredclarkb: how about just abandoning those22:34
clarkbmordred: I can do that too22:35
mgagneclarkb: chomp("file:///var/lib/git/\${name}.git\n")22:35
clarkbahahahahahah sorry22:36
mgagneclarkb: there's an exception for \n in the check22:36
clarkbthat is glorious22:36
clarkbmgagne: can you reply to my comment on the change with that info?22:36
mgagneclarkb: sure22:36
clarkbawesome, thank you for looking at this22:37
mgagneclarkb: np22:37
clarkbmordred: abandoned22:39
mordredwoot22:39
openstackgerritMonty Taylor proposed a change to openstack/requirements: Bump pbr requirment to 0.5.21  https://review.openstack.org/4011722:39
clarkbmordred: will git handle the file rename gracefully or will everyone need to rebase? I think rebasing is necessary22:40
mordredclarkb: what file rename?22:40
*** krtaylor has joined #openstack-infra22:40
mordredah. hrm. anyone with a patch to test-requirements will need to rebase22:41
mordredrequirements.txt shoudl be fine22:41
clarkbmordred: I can leave comments on all of those changes in a bit22:41
clarkbmordred: https://review.openstack.org/#/c/38176/4/modules/openstack_project/files/jenkins_job_builder/config/requirements.yaml does conflict with the savanna zuul layout change22:42
mordredwhat?22:42
clarkbmordred: you are removing the -install job22:42
openstackgerritJames E. Blair proposed a change to openstack-infra/devstack-gate: Use Jenkins credentials store if specified  https://review.openstack.org/4031022:42
clarkboh, I am mixingthe jobs up again22:42
clarkbignore me22:43
mordred:)22:43
jeblairclarkb, mordred: can you aprv https://review.openstack.org/40310 ?22:43
mordredon it22:43
jeblairi plan to handle the migration by stopping puppet on all the devstack-launch nodes22:43
jeblairand manually applying the change i'm about to propose only to the new ones22:43
jeblairthat should allow old devstack-launch to work as it has been, while updating the new ones with the new behavior22:44
jeblairi have tested that manually on devstack-launch01 (with jenkins01)22:44
clarkbreviewing22:44
*** emagana_ has quit IRC22:45
clarkbjeblair: then we will let devstack-launch.slave die on the vine?22:45
jeblairclarkb: yep22:45
jeblairclarkb: i anticipate that happening very soon, so i'm not too worried about just leaving puppet off on that node22:45
clarkbwfm22:45
clarkbapproved22:46
jeblairclarkb: actually, i think we can even keep puppet going everywhere (now that i'm writing the config change)22:48
clarkbjeblair: don't apply the credentials change to the config on the old host?22:48
jeblairyeah22:49
clarkbmordred: fungi https://review.openstack.org/#/c/40301/ will make apevec happy22:50
clarkbI will approve 40301 in a bit to make sure it gets in before the next round of periodic jobs22:50
openstackgerritA change was merged to openstack-infra/jeepyb: Allow hacking 0.6.0 and fix versions  https://review.openstack.org/3811922:51
jeblairclarkb, mordred: we need to work on getting my puppet changes merged22:51
jeblairso that we can allow jjb to run on the new jenkins nodes22:51
mordredjeblair: I will now do that22:51
jeblairmordred, clarkb: https://review.openstack.org/#/c/40041/ is the tip22:52
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Use jenkins credentials store with d-g  https://review.openstack.org/4031222:53
jeblairplus that ^22:53
clarkbok reviewing22:54
*** dina_belova has joined #openstack-infra22:55
mordredjeblair: chain +2 by me22:55
mordredthere are a couple fo small things people have brought up - but I'm fine with addressing those in a follow on22:55
clarkbjeblair: should I be picky about the plugins? eg do we need the bazaar plugin?22:55
jeblairclarkb: propose a change to remove them?22:56
jeblair(which won't remove them, but hey, they're already installed so...)22:56
clarkbjeblair: ok we can clean up later like mordred suggested22:56
mordredyeah, something tells me we're going to tinker with this for a while22:56
jeblairclarkb, mordred: i'm replying to the comments.22:57
*** changbl has joined #openstack-infra22:58
mordredjeblair: ok. I believe I have now reviewed all of your patches22:59
*** dina_belova has quit IRC22:59
openstackgerritA change was merged to openstack-infra/config: Remove ZUUL_BRANCH peridic job parameter  https://review.openstack.org/4030123:00
clarkbjeblair: ok I am approving that chain23:01
clarkband done23:01
jeblairi responded to all the comments; i do think there are things to fixup, but we can hit them in new patches.23:01
clarkbmordred: why are we pinning things like test resources? https://review.openstack.org/#/c/37911/1/test-requirements.txt23:02
*** beagles has quit IRC23:02
mordredclarkb: to give a minimum lower bound23:03
*** kpepple_ has quit IRC23:03
*** kpepple has joined #openstack-infra23:03
openstackgerritA change was merged to openstack-infra/config: Add jenkins::plugin defined resource type  https://review.openstack.org/3961523:03
clarkbmordred: but why?23:03
openstackgerritA change was merged to openstack-infra/config: Don't automatically restart jenkins on plugin changes  https://review.openstack.org/4004023:03
mordredalso - that was the point of that patch, to add lower bounds to anything with an aupper bound to make parsing things easier23:03
*** wayneeseguin has quit IRC23:03
openstackgerritA change was merged to openstack-infra/config: Add current jenkins plugins  https://review.openstack.org/4004123:03
*** jcooley has quit IRC23:03
mordredclarkb: you _know_ that if there is a comma list, the first will be power23:03
clarkbmordred: the discussion we had after the broken xattr stuff implied we want to know when upstream breaks us23:03
mordredlower23:03
mordredI duno23:04
clarkbgiving a lower bound to have a lower bound prevents that23:04
mordredwhy?23:04
jeblairmordred: your devstack change is in danger of failing due to a failed (flaky?) neutron test.23:04
mordredjeblair: wow23:04
mordredit's been so long since that's been the case23:04
clarkbmordred: because if testresources 0.4 or whatever comes out we will never use it23:04
*** sarob has quit IRC23:04
mordredclarkb: you are talking about upper bounds23:05
clarkbmordred: er ya23:05
clarkbs/pinning/setting an upper bound/23:05
*** wayneeseguin has joined #openstack-infra23:05
*** sarob has joined #openstack-infra23:05
openstackgerritMathieu Gagné proposed a change to openstack-infra/config: Fix puppet-lint for bare puppet modules  https://review.openstack.org/4031423:05
mordredclarkb: I believe that we, in general, have decided that we _do_ want to protect against breaking changes from upstream at times by pinning in requirements23:05
mordredthat's different than protecting by rejecting things from the mirror in the gate23:06
*** jcooley has joined #openstack-infra23:06
clarkbwe are not rejecting things from the mirror in the gate23:06
mordredI know, because we do not want to23:06
clarkbI feel like every time we discuss this I come away with a different impression of what people want23:06
mordredit's differnet issues23:06
*** beagles has joined #openstack-infra23:06
clarkbmordred: what is the issue here?23:06
jeblairclarkb: the upper bounds are supposed to be set such that they will include stable or security-style updates, but not breaking api changes.23:06
mordredwe want what is expressed in the file to be somethign that will work in reality outside of our systems23:07
jeblairclarkb: that's vague, up to interpretation, and varies by project policy for every upstream project.23:07
clarkbI feel like that particular pin was pulled out of a hat randomly23:07
mordredso putting a bound there is fine, because someone downloading nova from the internet and installing it will get the set of software described23:07
clarkblifeless is really good about backward compat23:07
clarkbso I think what I am hearing is the in the general case we may want to pin upper bounds as necessary23:08
mordredyes23:08
mordredalthough, we tend to be mildly agressive23:08
clarkbso now I am focusing on that particular pin. Any idea why?23:08
mordredno23:08
mordredI do not have strong feelings about that pin23:08
lifelessclarkb: I'm good but not perfect :)23:08
clarkbI do because zigo and others tried pulling this before... and I told them all no because it was busy work that didn't get us anyhting23:09
mordredjeblair: I also got a lost on a grenade tests23:09
clarkbI think some people feel that they must package the upper bounds....23:09
clarkbrather than understand the range is acceptable23:09
*** sarob has quit IRC23:09
jeblairmordred: "gate-grenade-devstack-vm: SUCCESS" ?23:10
fungiclarkb: yeah, https://review.openstack.org/37461 is the follow up to requirements i *should* have proposed but forgot. it was in there to support nova, removed by my https://review.openstack.org/38012 change23:10
jeblairmordred: for 35705,1623:10
mordredjeblair: this was for a keystoneclient23:10
*** nijaba has quit IRC23:10
* fungi is scrollbacking for a bit, looks like23:10
mordredjeblair: https://review.openstack.org/#/c/40284/23:10
mordredjeblair: http://logs.openstack.org/84/40284/2/check/gate-grenade-devstack-vm/20f630b : LOST in 12m 02s23:11
*** nijaba has joined #openstack-infra23:12
clarkbmordred: see comments on https://review.openstack.org/#/c/39967/23:14
clarkbfungi: I have approved 37461, we'll have to see how it does in the gate with all of the new shinyness23:16
jeblairmordred: that node was re-used because the first job was aborted while waiting for the devstack-inprogress job23:17
*** rcleere has quit IRC23:18
mordredclarkb: only need from future importprint_function when you're going to use one of the new print function features23:18
jeblairmordred: which eventually finished after the second job started; and likewise, the complete job from the first job also finished, and then the node was deleted while the second job was running.23:18
jeblairclarkb: i believe i'm at the point where we could merge your change that tests for idleness before deleting a node23:19
clarkbmordred: does it not depend on order of import? I am too lazy to go around and figure out what the order should be23:19
clarkbjeblair: oh, is that still a good thing? I have abandoned it and need to remove the race condition23:19
clarkbjeblair: but I can do that if you want23:19
mordredclarkb: nope23:19
jeblairclarkb: if it needs work, it may not be worth it...23:19
clarkbjeblair: its not much work, I have to set the node to offline before checking if it is idle23:19
clarkbjeblair: one extra line basically23:20
jeblairoh we don't want to set the node to offline23:20
jeblairthat confuses the hell out of people23:20
clarkboh23:20
clarkbbut it is a safe thing to do23:20
clarkband removes the idle check race condition23:20
*** vipul is now known as vipul-away23:20
jeblairwe'll see lots of people in here saying "hey i got an error because the node is offline"23:20
clarkb:/23:20
jeblairclarkb: we used to do that, before doing the relabel23:20
jeblairclarkb: the other thing is that even that is still subject to errors23:21
clarkbdoes jenkins ignore the offline state at times?23:21
jeblairclarkb: since the result of your change is that we allow jobs to run on nodes that have already been used (but not had their labels updated)...23:22
clarkbwhich change?23:22
stevebakerclarkb, jeblair, any chance of another look at https://review.openstack.org/#/c/39858/ ?23:22
jeblairclarkb: with the current runtime for the label update jobs being so high, it's possible that the first job might actually get far enough to affect the second.23:23
jeblairclarkb: the change under discussion.  :)23:23
clarkbjeblair: it doesn't allow that to happen. It tries to reduce the size of the crater if it does happen23:23
jeblairclarkb: so it's basically substituting one error for another, hopefully with better odds23:23
clarkbjeblair: and log the case23:23
jeblairclarkb: if it does not allow job to run on a node that has already been used (but just not had the label updated) then we should not merge it because that's the problem that we're seeing.23:24
clarkbstevebaker: yup looking now. I feel bad ps4 appears to be a result of my bad suggestion in ps223:24
stevebakerheh, now we know23:24
jeblairclarkb: at any rate, the work i'm starting next will hopefully eliminate this (and other) problems23:25
clarkbjeblair: I get that it isn't the best fix for a problem, but it is a fix that we could put in now... I think that was what I was going for. I understand we can do it better iwth a lot of work and in the meantime we could use something like that to avoid large explosions23:26
jeblairclarkb: i agree, which is why i said i'm okay merging it, before you indicated that it needed more work.23:27
jeblairclarkb: also you indicated it did not solve the problem at hand.23:27
*** sandywalsh has quit IRC23:27
clarkbcorrect I don't think it solves all instances of run a job twice on the node23:27
*** pcrews has quit IRC23:27
clarkbit solves the we killed the node while your test was running problem23:27
jeblairwhich i believe only happens if a node is re-used.  and i believe the only time that is currently happening is because the first job is aborted while waiting on the label job.23:28
clarkbgotcha23:28
jog0sdague: can you take a look at https://review.openstack.org/#/c/39140/23:28
jog0sdague: its the blocker for hacking 0.723:29
jog0clarkb: FYI hacking 0.7 is a bug fix release that fixes a broken test23:29
jeblairstevebaker, lifeless: tie can build an sdist but not run pep8?23:30
stevebakerthere is no python, but it is packaged with pbr23:30
clarkbreed: https://review.openstack.org/#/c/38761/23:31
bodepdjeblair: surprised to see you finish that patch off23:31
bodepdjeblair: but thanks :)23:32
jeblairbodepd: i had an immediate use for it.  it was timely.  thank you.  :)23:32
reedclarkb, checking23:32
reedclarkb, can't approve it23:33
clarkbjeblair: and by adding multiple launch slaves and reducing the total pool per launch slave we should see the instance of that decrease?23:33
lifelessjeblair: thats correct23:33
clarkbreed: I know, but I can approve it if you give it a +123:33
reeddone23:33
lifelessjeblair: it has no python code in it; it's using setup.py to build the distribution just because.23:33
clarkbreed: thanks23:33
jeblairclarkb: i hope that jenkins will be more responsive under less load, while i work on the d-g updates.23:33
jeblairclarkb: (we may not want to increase our slave count too much while that's in progress)23:33
*** wu_wenxiang has joined #openstack-infra23:34
clarkb++23:34
*** danger_fo is now known as danger_fo_away23:34
jeblairlifeless: do the shell scripts themselves get packaged?  if not, what does?23:34
openstackgerritA change was merged to openstack-infra/config: Do not run python jobs for tripleo-image-elements  https://review.openstack.org/3985823:34
stevebakerthanks, now we need to do the same for disimage-builder ;)23:35
openstackgerritA change was merged to openstack-infra/config: Use jenkins credentials store with d-g  https://review.openstack.org/4031223:35
lifelessjeblair: they do, by the setup.py/setup.cfg stuff23:35
*** vipul-away is now known as vipul23:36
jeblairlifeless: ok.  thanks.  fascinating.23:36
*** mrodden has joined #openstack-infra23:36
openstackgerritA change was merged to openstack-infra/config: Add french list openstack-fr  https://review.openstack.org/3876123:37
lifelessjeblair: we're happy to do it differently if that will help23:38
clarkbfungi: you still around? https://review.openstack.org/#/c/39992/1 has the IPV6 var been added to the env files?23:38
lifelessjeblair: main reason to use setup.py was conformity - avoinding a new toolchain in the project.23:38
clarkbI will aprove 39992 if it has23:38
jeblairlifeless: i have no alternate suggestions.  i really do find it an interesting use of the python packaging and distribution system.23:39
clarkbfungi: also you may want to get reservations at shiros if you can. I am not sure what their wait list is like23:41
stevebakeradmittedly it is an expedient way of adding dib and tie as installed dependencies in devstack23:42
*** sandywalsh has joined #openstack-infra23:42
jeblairit does seem to have that going for it.  if you're pip installing 500 other things, what's one or two more? :)23:42
bodepdjeblair: glad to help!23:43
stevebakerindeed23:43
clarkbbodepd: https://review.openstack.org/#/c/39611/2 makes me sad23:44
clarkbbodepd: any idea why it is blowing up like that?23:44
clarkbbodepd: and any chance you can paste the traceback in a place where formating is preserved?23:44
*** jrex_laptop has joined #openstack-infra23:46
mgagneAre launchpad teams and gerrit groups supposed to be synced?23:46
clarkbmgagne: not anymore23:46
mgagneclarkb: should I want to add a new core reviewers, this would have to be done in gerrit right?23:46
clarkbmgagne: there were when we used lp to manage the CLA but we stopped doing that in favor of the CLA stuff in gerrit and now all gerrit groups are managed through gerrit23:46
clarkbmgagne: yup23:46
mgagneclarkb: thanks for the info23:46
bodepdclarkb: no idea23:47
bodepdclarkb: I just replaced it with package { pip } and moved on23:48
bodepdjenkins is hard to install :(23:48
clarkbmordred: https://review.openstack.org/#/c/39207/ what is with putting pbr on the exclusion list? Don't you forcefully update setup.py?23:48
clarkbbodepd: we use jenkins' .debs23:48
bodepdclarkb: I unfortunately have xml templates23:49
*** Shrews has quit IRC23:49
bodepdclarkb: which makes me terrified to change any versions23:49
bodepdclarkb: I actually hate jenkins b/c of its crappy API23:50
bodepdclarkb: can we just move to build bot? (if it's any better...)23:50
clarkbbodepd: ask mordred. I believethe answer is "NO!"23:50
jeblairbodepd: zuul doesn't depend on jenkins, so you could hook anything up to gearman to run your jobs.23:51
bodepdI was thinking about that today23:51
bodepdI'm going to defer to what-ever you guys do for now23:52
jeblairbodepd: i think we may start doing that for some jobs eventually (as are the wikipedia folks).  but the hard part is having a system that both runs untrusted random code submitted by anyone on the internet, and also builds your release artifacts.23:52
jeblairso, um, we'll be thinking about it carefully. :)23:53
*** shardy has quit IRC23:54
bodepdyeah23:55
bodepdcode review?23:55
*** dina_belova has joined #openstack-infra23:55
bodepdrequire a +1 from core before running CI is a pain, but the solution to that problem...23:55
clarkbbodepd: for the pip failure, I think that may be related to pbr, setuptools, and distribute madness23:55
jeblairwe run jobs on patchset uploaded (by popular demand; that was our initial stance)23:55
clarkbbodepd: is your package {} ensuring latest?23:56
bodepdno23:56
bodepdwait, let me check...23:56
jeblairbodepd: also, obfuscated code would probably slip by.23:56
bodepdhttps://gist.github.com/bodepd/616074823:56
bodepdjeblair: openstack itself is much more at risk for that IMO23:57
fungiclarkb: on 39992, yes that var was added to all the shell config snippets on the master (i think i left a review comment to that effect in it when i uploaded, but need to finish catching up on scrollback before i go hunting)23:57
clarkbbodepd: hmm that is essentially what the pip module is doing, this is very odd23:57
bodepdclarkb: yeah, I didn't understadn it either.23:57
bodepdthe pip package installs a few other packages23:58
clarkbfungi: you did, I see it now23:58
bodepdmaybe the version of those is no good for zuul?23:58
clarkbbodepd: it installs things like python all dev so that you have python headers if pip installed things need them23:58
bodepdI can recreate23:58
bodepdit'll take about 10 minutes23:58
clarkbbodepd: its possible. I am thinking it is related to the setuptools madness23:58
fungiclarkb: adding shiros to the hit list, thanks!23:58
bodepdis there something I should try?23:58
bodepdclarkb: ^^^ like removing setuptools from the pip class?23:59
clarkbbodepd: if you recreate try uninstalling python-pkg-resources python-setuptools then install python-pip and pip install -U setuptools23:59

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