Wednesday, 2015-01-28

*** krtaylor has joined #openstack-sprint00:35
omrimkrtaylor: Hi10:01
*** rfolco has joined #openstack-sprint11:09
fungii still need to get some breakfast, but will be ready to pitch in shortly13:00
mmedvedehi all!14:35
fungihowdy mmedvede!14:37
fungii'm starting in on reviewing the https://review.openstack.org/#/q/topic:+module-split+status:open,n,z changes. if anyone has sprint-related changes they want reviewed make sure to use the "module-split" topic14:38
mmedvedefungi:  This one could require special treatment https://review.openstack.org/#/c/150713/14:38
fungialso reminder to those who are lurking, we're keeping notes at https://etherpad.openstack.org/p/puppet-module-split-sprint14:39
mmedvedebasically, zuul project is already there, so that would prevent it from getting updated from new upstream14:39
fungimmedvede: thanks for pointing that out. i'll double-check and yes, we'll need to think about whether it makes sense to push --force the new repo on top of that or propose the changes from it14:41
fungion a positive note, it looks like the initial commit there is the one manage-projects creates, so i think it's no real loss if we overwrite14:42
fungiseems we added it back in june14:42
mmedvedefungi: yes, the repository is rather empty14:43
fungiand no changes in gerrit, open or closed14:43
fungialso 150713 isn't really necessary. that change won't do anything... the import work is going to end up being entirely manual for it14:44
fungiso no need to add that line to the projects.yaml file14:44
fungii'll go ahead and take care of it once we have an additional person look over the github.com/Triniplex-Test/puppet-zuul contents to confirm14:45
mmedvedefungi: understood. I would mark it WIP, and abandon later. Probably would need to remove Depends-On from https://review.openstack.org/#/c/150712/14:46
mmedvedefungi: Triniplex-Test repositories are not updated automatically. But I have push rights to it, so I have updated the ones needed for my patches14:47
fungimmedvede: awesome. i'm going through it now just to make sure it's what i expect14:48
mmedvedejust in case somebody thinks they are automatically updated14:48
fungimmedvede: lgtm. let's get a second reviewer to make a pass through that repo and then i'll push it in over top the old one14:50
mmedvedeok14:52
*** mestery has quit IRC15:01
*** dteselkin has joined #openstack-sprint15:04
krtaylorhi everyone15:12
*** SergeyLukjanov has joined #openstack-sprint15:13
SergeyLukjanovhey folks15:13
jesusaurushello15:13
mmedvedehi15:13
clarkbmorning though I am not quite ready for the day to start15:14
krtaylorI'll start doing some reviews -> https://review.openstack.org/#/q/topic:module-split,n,z15:15
*** jeblair has joined #openstack-sprint15:18
asselin_good morning15:29
mmedvedeasselin_: morning15:30
asselin_sweston should have the triniplex modules being updated. Either way, we should double check all repos15:32
mmedvedeasselin_: I do not think Triniplex-Test repos are updated15:33
mmedvedeasselin_: I have been pushing for my patches there though15:33
mmedvedeasselin_, sweston: I have noticed some modules on Triniplex-Test are definitely not right, e.g. https://github.com/Triniplex-Test/puppet-lodgeit, I had force-pushed a couple15:35
* asselin_ looking15:36
*** mrmartin has joined #openstack-sprint15:38
mrmartino/15:38
asselin_mmedvede, I don't see lodgeit here: https://github.com/openstack-infra/system-config/tree/master/modules15:38
mmedvedeasselin_: it has been merged/split out already15:39
asselin_mmedvede, today?15:39
* asselin_ reviewing latest patches15:40
mmedvedeasselin_: no. Lodgeit did not use Triniplex-Test upstream15:40
mmedvedeso it was not a problem15:41
asselin_ok15:41
mrmartinasselin_: what's the next step with this review: https://review.openstack.org/#/c/149953/ ?15:44
asselin_mrmartin, another core will +2 & +A15:45
mrmartinok15:45
asselin_mrmartin, then we need to remove it from system-config15:45
asselin_mrmartin, example: https://review.openstack.org/#/c/150814/15:46
mrmartinbut after approval, I need to add the .gitreview and module dependency files?15:46
asselin_mrmartin, yes that too15:46
mrmartinok, then I'm waiting :)15:46
asselin_mrmartin, you should have a patch like this to remove from system-config: https://review.openstack.org/#/c/150814/15:47
mrmartinok, then I'm writing those patches15:47
asselin_mrmartin, thanks15:47
fungiokay, so did anyone have any specific thoughts on how (or whether) we need to plan for merge conflicts? i guess at this point they're merely changes to the sorted projects.yaml list but since the entries have a common prefix they're often going to be in context proximity anyway15:50
fungii'm inclined to just upload rebases as needed while i'm reviewing15:50
asselin_fungi, ++15:51
fungiabout to approve 149994 which will create openstack-infra/puppet-openstackid so wanted to make sure this is coordinated as much (or as little) as needed15:51
asselin_looking15:51
asselin_fungi, looks good to me15:52
asselin_fungi, do you think merging  non-alphabetical will help reduce merge conflicts?15:54
asselin_also, should we try to keep https://review.openstack.org/#/c/150712/2/modules.env alphabetical?15:55
mmedvedeasselin_: that is what I am trying to do15:56
mmedvedeasselin_: should reduce probability of merge conflicts15:56
asselin_the file is already non-alpha, perhaps we shoudl fix that first?15:56
fungiasselin_: not sure what you mean by merging non-alphabetical15:57
fungiwhat is non-alpha about that file? we have a job that checks it stays in alpha order15:57
asselin_fungi, e.g. pick something in the first half of the alphabet, then the second half of the alphabet, then back to the first.15:58
jesusaurusdoesnt order matter in modules.env because of possible dependencies?15:58
fungiasselin_: oh, sorry, i was talking about projects.yaml15:58
funginow i see you were not15:58
asselin_fungi, https://github.com/openstack-infra/system-config/blob/master/modules.env#L6315:58
fungiyeah15:59
asselin_jesusaurus, good question....15:59
jeblairhi there, i'm here now15:59
fungii'm not sure if it will help anyway. the number of rebases will likely be roughly the same regardless15:59
jeblairwhere's our etherpad?15:59
asselin_jeblair, does order matter here:  https://github.com/openstack-infra/system-config/blob/master/modules.env#L6315:59
asselin_jeblair, https://etherpad.openstack.org/p/puppet-module-split-sprint16:00
fungiwe should just avoid rebasing the ones which start spontaneously merge-conflicting with one another until we're ready to approve them, so that we don't rebase them multiple times unnecessarily16:00
asselin_fungi, ++16:00
jeblairasselin_: i don't think order matters (it may have an effect, but shouldn't _matter_)16:00
fungiokay, fire in the hole. 149994 is approved16:01
krtaylorhehheh16:03
krtaylorI just pushed bup16:03
fungidid anybody else get a chance to look over github.com/Triniplex-Test/puppet-zuul ? short story there is that we've had a dead (initial manage-projects commit, no changes proposed ever) openstack-infra/puppet-zuul since june, so i'm planning to push --force that split content if it looks okay16:03
* krtaylor looks16:03
asselin_fungi, I'll double check now16:03
jeblairokay, what do i do?  pick a change ready to go and approve it?16:04
mmedvedefungi: I have rechecked, diff with current system-config shows no differences16:04
asselin_fungi, matches: https://github.com/Triniplex-Test/puppet-zuul/commits/master https://github.com/openstack-infra/system-config/commits/master/modules/zuul16:04
fungijeblair: that's what i've been doing. approve them all and let the gate sort them out ;)16:04
krtaylorre: puppet-zuul  lgtm16:05
clarkbshould we leave a note in -infra that system-config and project-config should be treated as frozen today while we do this?16:05
fungiclarkb: oh, good idea16:05
krtaylor+116:05
mmedvedeclarkb: +116:05
asselin_clarkb, +116:05
fungis/frozen/ignored/ if you want the truth16:05
asselin_fungi, :)16:06
fungisince we're all focused on reviewing sprint-related changes16:06
*** reed has joined #openstack-sprint16:06
jeblairare people writing removal changes after the create changes land?16:07
fungimrmartin: thanks for 150831. i'll +2 it once i confirm creation of the new project worked16:07
jeblairoh, nm16:08
jeblairi had a bad query16:08
asselin_jeblair, there are quite a few removal changes16:08
jeblairhttps://review.openstack.org/#/q/status:open+branch:master+topic:module-split,n,z16:08
fungii think it should be safe to write them before the corresponding new project changes are approved16:08
jeblairis what i really want16:08
fungiahh, yep16:08
fungithe query in the etherpad is a little overly-specific16:08
jeblairfixing16:08
jeblairoh, no, the ep is right, gerrit just was being helpful as i clicked around16:09
fungiahh, heh16:09
fungiand yeah, i checked the etherpad after i said that. seems right16:09
fungimorningbrain16:09
*** mestery has joined #openstack-sprint16:10
krtaylorthe description, why?  is it needed?  it seems worthless (just a restating of the project)16:11
jeblairkrtaylor: it shows up in github (and possibly other places in the future)16:11
krtaylorjeblair, ah, ok16:11
asselin_mrmartin, actually, can you update the commit messages a bit for yours? to include the removal patch? https://review.openstack.org/#/c/149953/16:12
mrmartinasselin_: I can16:13
asselin_mrmartin, like this one: https://review.openstack.org/#/c/150699/16:13
asselin_mrmartin, the two related patches should link to each other16:13
asselin_mrmartin, thanks16:13
mrmartinWould you like to see just the Needed-By line?16:13
asselin_mrmartin, I'm ok with that since today's the split16:14
asselin_split sprint16:14
mrmartinbut it will lost all of the +1's :(16:14
jeblairwe could probably waive that today...16:15
jeblairif folks wanted to... since we're focused entirely on this16:15
mrmartincan I rewrite this on gerrit ui?16:15
jeblairmrmartin: yes16:15
asselin_mrmartin, seems you can update the commit message in gerrit ui. didn't realize that16:17
mrmartinasselin_: yeap, it creates a new patches automagically16:17
mrmartinpatches / patchset16:17
fungii'm not at all concerned about needed-by, and am in fact double-checking regardless of depends-on headers since these follow an obvious pattern16:18
jeblairfungi, clarkb: erm, should we just kill recheckwatch?16:19
clarkbwfm16:19
fungijeblair: i'd be fine with that. i never got any indication that it was every used by anyone16:19
jeblairincluding, at this point, us.16:19
fungii've pointed out the url to the rss feeds periodically, but never seen anyone else mention it16:19
jeblairit has rss feeds?16:20
fungioh, recheckwatch16:20
fungisorry, i was thinking of openstackwatch16:20
fungiduh16:20
fungiyeah, totally safe to ditch recheckwatch16:20
asselin_ok I see that's mine. :)16:22
jeblairasselin_: sorry i didn't spot that sooner :(16:23
mrmartinare the gate puppet apply FAILURES normal in that case? https://review.openstack.org/#/c/150831/16:23
asselin_jeblair, no problem16:23
fungimrmartin: yes16:24
mrmartinok.16:24
fungimrmartin: they fail until the new project exists. i just rechecked it now that it does16:24
jeblairhow about i stack some changes that have merge conflicts together and re-upload?16:25
fungiokay, i'm going to go ahead and push --force github.com/Triniplex-Test/puppet-zuul into gerrit now unless there are any objections or anyone else wants to look it over first16:26
jeblairfungi: ++16:26
fungijeblair: that also seems fine16:26
asselin_jeblair, ok, updated the system config change to just delete it altogether: https://review.openstack.org/#/c/140431/16:26
fungiasselin_: thanks!16:26
jeblair16:28 < openstackgerrit> James E. Blair proposed openstack-infra/project-config: Add puppet-logstash as split out module  https://review.openstack.org/15070616:28
jeblair16:28 < openstackgerrit> James E. Blair proposed openstack-infra/project-config: Add puppet-nodepool as split out module  https://review.openstack.org/15071416:28
jeblair16:28 < openstackgerrit> James E. Blair proposed openstack-infra/project-config: Add puppet-meetbot as split out module  https://review.openstack.org/15069916:28
jeblaircould folks re-review those real quick?16:28
asselin_all I have a 30 minute meeting now. will be back soon16:30
fungisure16:30
jeblairclarkb: please review my patches! ^ :)16:31
jeblair(well, they are not mine, but my rebases of them)16:31
clarkbare all of the triniplex repos up to date?16:32
fungialso, i think any non-urgent patches to those modules still sitting in system-config should just get -2'd when we're done and ask the change owners to resubmit to the appropriate new project16:32
jeblairfungi: ++16:32
fungisort of like we did with the project-config split16:32
jeblairor possibly even abandoned16:33
mmedvedeclarkb: no16:33
jeblairoh neat!16:33
mmedvedeclarkb: Triniplex-Test are not all up to date16:33
jeblairi thought this was all scripted and kept up to date :/16:33
mmedvedejeblair: it used to. I can push there, so I did update some of the modules there to use for patches I submitted16:34
mmedvedeWe have to check them manually, unfortunately16:35
jeblairmmedvede: okay, so you're in charge of that for now.  :)16:35
jeblairmmedvede: can you comment on those 3 patches and verify that their repos are up to date?16:35
mmedvedejeblair: on it16:36
mmedvedethanks for the rebase16:36
clarkbso I should hold off on +2'ing anything?16:39
jeblairclarkb: sounds like it....  i think we should establish some process here so we can get through these quickly.  i'd like to stop doing this after today.  :)16:40
jeblairso it seems like we need folks to (a) create temp split repos; (b) write split changes; (c) write removal changes; (d) write boilerplate puppet/gitreview changes; (e) verify the contents and up-to-date-ness of split repos; (f) review changes16:42
jeblairit seems like we're set up to have one person do a,b,c,d for each repo by grabbing a task in storyboard.  shall we stick with that?16:43
clarkbI think so, it keeps units of work coupled so we don't miss a step for one project16:44
jeblairi sort of thought someone was doing (a) for all the repos, but i guess not16:44
fungii thought the ones asselin_/krtaylor did were being maintained that way16:45
fungiusing sweston's script in cron or something16:46
jeblairit would be a big help... but if that's the case, i don't understand why we have changes pointing to repos other than that, that may or may not be up to date :(16:46
jeblairclarkb: mmedvede have verified that those 3 repos are up to date, feel free to review those changes16:47
swestonsweston's ears perk up16:47
clarkbdoing that now16:47
jeblairsweston: i thought there was a bunch of github repos with all of our puppet modules split out and being kept up to date.  do you know if that's the case?16:48
sweston yes, so the last time I wrote a patch for asselin I stopped the script so that I could troubleshoot.  I need to restart it, it has not run in a while16:49
mmedvedesweston: I have forced pushed a couple of repos there16:49
jeblairsweston: any chance you can get that going now, or should we just switch to having folks run things on their own?16:49
swestonjeblair: nope, I can do it in about 5 minutes16:50
swestonjeblair: are you doing the split today?16:50
clarkbI need to pop out to drop larissa off at work back in a bit (I did review that stack jeblair rebased)16:50
jeblairsweston: yes, today is our sprint, and we're going to get all of the modules split today.16:50
swestonjeblair: ok, I will make myself available today, and re-start the script now16:51
swestonjeblair: is it the 28th already? ;-)16:51
mmedvedesweston: check this https://github.com/Triniplex-Test/puppet-lodgeit16:51
mmedvedebefore restarting script16:52
jeblairsweston: great, thanks!  where are the modules?16:52
mmedvedesweston: it is not correct, and there are several more repositories like that one16:52
fungimrmartin: were you going to propose an initial change to openstack-infra/puppet-openstackid (adding .gitreview, rakefile and puppet metadata) now that it's created?16:52
krtaylorI used my github repo because I know (and verified) that is has not changed16:52
swestonjeblair: they are in the triniplex test repo mmedvede referenced16:53
mrmartinfungi: yeap I'm doing that16:53
swestonmmedvede: besides being out of date, is there anything else wrong with the repo?16:53
mrmartinonly one question here, it must depend on puppet-redis module, how can I add this dependency to puppet metadata?16:53
fungimrmartin: great. presumably we want that before we approve 15083116:53
jeblairnibalizer, jesusaurus: ^ question from mrmartin16:54
mmedvedesweston: yes, it is not a split repo. Check the contents16:54
mrmartinso I guess, need to approve the puppet redis patch too before this16:54
mmedvedesweston: it is supposed to have only lodgeit, but it has all the modules16:54
swestonmmedvede: yup, you are correct, this may be a bug16:55
swestonmmedvede: give me a moment to restart the split script, and we will troubleshoot further16:55
fungimrmartin: i'm looking at the redis one now16:55
mmedvedesweston: you are not force pushing to Triniplex-Test, correct? because if you do, please do not enable the script, it would rewrite good repositories that I have updated16:56
swestonmmedvede: I can push to Triniplex instead16:56
jeblairsweston, mmedvede: and we just approved 3 changes that clone from triniplex-test, so we should keep meetbot, logstash, and nodepool stable there for a while16:57
mmedvedejeblair: +116:58
jeblairfungi, mrmartin: i have +2d redis,askbot,drupal; did not aprv since fungi is looking16:58
swestonjeblair, mmedvede: ok, will do.  I will run the script against Triniplex instead.  Sound good?16:58
mrmartinjeblair: ok, we need the redis first, to finalize openstackid too16:58
jeblairfungi: what did you approve earlier?16:59
fungijeblair: puppet-openstackid16:59
mmedvedesweston: wfm, thank you.16:59
fungiAJaeger had already +2'd16:59
jeblairi'm keeping status at the bottom of the etherpad16:59
fungiand i double-checked the repo content was current16:59
fungioh, great idea16:59
nibalizero/ good morning17:00
pleia2good morning17:01
fungifor those who got kicked off the etherpad, looks like it fell over again when everyone from the nova meetup was coming online. seems more than coincidence17:01
jeblairnibalizer, pleia2: sweston is working on getting his script that auto-pushes split modules to github going again17:02
nibalizercool17:02
pleia2great17:02
jeblairnibalizer, pleia2: probably the most helpful thing would be to claim some modules in https://storyboard.openstack.org/#!/story/302 and write changes for them, assuming that sweston will have up to date modules at https://github.com/Triniplex17:03
jeblairfungi: are you going to aprv askbot and drupal too?17:04
pleia2sure thing, thanks jeblair17:05
fungijeblair: yep, already looking at them17:05
fungijust getting the bookeeping straight17:05
fungier bookkeeping (no keeping boo!)17:05
asselin_Hi, I'm back17:06
nibalizercool17:07
fungiit's worth noting that mrmartin's split repo for puppet-askbot already has the boilerplate added17:10
fungiso it won't in theory need a separate change for that17:10
nibalizermrmartin: the dependencies section of this can be used as an example of how to set one module dependent on another https://github.com/puppet-community/puppet-module-puppetboard/blob/master/metadata.json17:11
mrmartinfungi: I can remove that if required17:11
fungimrmartin: no need. technically that one's not a module "split" since it's a new project anyway17:11
asselin_fungi, mrmartin is that really a split or a new one?17:11
asselin_fungi, ++17:11
mrmartinasselin_ :) good point17:11
fungibut might as well roll it into this17:11
mrmartinyou need to roll in that anyway, so this is the best time :)17:12
fungiyep, not complaining just making sure everyone's aware it's a little special17:12
mrmartinnibalizer: how will you add a dependency, for example our puppet-redis module?17:13
nibalizerin that location put openstackci-redis17:14
nibalizerfor versions idunno17:14
* jeblair creates two new gertty dashboards17:15
mrmartinok, so it means, those modules will be uploaded to puppetforge under openstackci ?17:16
jeblairi pasted my gertty dashboard config into the etherpad if anyone is interested17:17
fungisaw that--thanks!17:17
nibalizermrmartin: eventually, there is some stuff in flight for geting automated puppetforge deploys, i don't think thats in scope today though17:18
jeblairlogstash/meetbot/nodepool are cloned now17:18
mrmartinok, because if we add this dependency in metadata.json it won't harm us, because our modules are coming from git repo directly defined in modules.env, right?17:19
swestonjeblair, mmedvede: ok, script is re-started ... the first split takes about an hour, I will update you with progress as I have it17:19
jeblairsweston, mmedvede: we have imported the 3 repos in triniplex-test now, so i believe there are no approved changes depending on any triniplex repo now.  you're all clear to do whatever you need17:20
nibalizermrmartin: correct17:20
swestonjeblair: ok17:21
fungihttp://git.openstack.org/cgit/openstack-infra/puppet-zuul is up to date now too, so adding it to the created list17:21
mmedvedesweston: awesome17:21
jeblairasselin_: can you write the puppet boilerplate changes for meetbot, logstash, and nodepool?17:22
asselin_jeblair, sure17:22
mmedvedeasselin_: I can add the boilerplate if you did not start on it yet17:26
asselin_mmedvede, didn't start yet. just about to17:27
mmedvedeasselin_: I have it all setup, should be quick for me17:27
asselin_mmedvede, ok, you do it. I'll pick another module17:27
jeblairyay more modules!17:27
pleia2nibalizer: can you set a topic of module-split on your changes?17:35
nibalizersure17:36
nibalizeris the only way to do that cli to set the branch tite?17:36
nibalizerer branch title17:36
jeblairpleia2, nibalizer: alse recall gerrit lets you set the topic through the ui17:36
jeblair(gertty too)17:36
jeblairnibalizer: and in the future, you can do "git review -t module-split" so it is set when you upload regardless of branch name17:36
pleia2have to be the owner of the change to set it though17:37
pleia2(re: gerrit ui)17:37
jeblairpleia2: oh!17:37
nibalizercool17:38
jeblairpleia2: i guess that must be another permission that has leaked into administrators... :(17:38
pleia2jeblair: yeah, seems so, I can only fiddle with commit message and change-id on other people's patches17:38
jeblairfailed: [git02.openstack.org] => {"changed": false, "disabled": false, "error": true, "rc": 1}17:39
jeblairstdout: Notice: Run of Puppet configuration client already in progress; skipping  (/var/lib/puppet/state/agent_catalog_run.lock exists)17:39
jeblairfungi: ^ do you grok that?17:39
nibalizerpleia2: topic attached :)17:40
jeblairfungi: switching to #openstack-infra17:41
asselin_jesusaurus, these don't quite match?? https://github.com/jesusaurus/puppet-cgit/commits/master https://github.com/openstack-infra/system-config/commits/master/modules/cgit17:42
asselin_maybe it's ok? need more eys17:42
pleia2nibalizer: fyi, looks like we're also using Depends-on: and Needed-by: in the commit messages to match up -system and -project patches that are related, I'm cribbing from asselin_'s patches, ie: https://review.openstack.org/#/c/150859/ & https://review.openstack.org/#/c/150860/17:42
nibalizerah okay17:43
asselin_fungi, jeblair are we still doing the depends-on and needed-by? not sure if that's needed anymore?17:44
jeblairpleia2, asselin_: i think we can waive that for simplicity during the sprint17:48
pleia2ah ok, good to know :)17:48
asselin_nibalizer, ^^17:49
nibalizercool!17:49
jeblairis mostly for coordination under normal conditions, but now we've got etherpads with lists of things and we're really focused on it, so not strictly necessary17:49
pleia2wfm17:49
clarkbI am making tea. will be back for reviews shortly17:50
nibalizerso, not to rock the boat, but the subversion module is 4 lines, and is only used once, so we could remove it entirely and replace the usage of it in wiki.pp with package { 'subversion': }17:50
nibalizerthoughts?17:50
jeblairnibalizer: ++17:51
clarkb+117:51
nibalizeraight ill spin up that change real fast17:51
nibalizerPSA to others, be on the watch for trivial modules like subversion that can be just refactored into /dev/null17:53
nibalizer(git review -t)++17:57
jeblairnibalizer: ++ we also nixed recheckwatch -- even though it is not trivial, it's not actually used (we just need to remove it)17:57
nibalizerheh17:57
nibalizernicely done17:57
jeblairmmedvede, asselin_: what's the best way to verify that a repo is up to date?17:58
asselin_jeblair, I use github:17:58
mmedvedejeblair: I was doing recursive diff between the repo in question and the latest checkout of system-config/modules/<module>17:58
asselin_1. open the new project in github & click on "commits"17:59
mmedvedejeblair: and also what asselin_ is saying, just making a quick look through commits17:59
asselin_2. https://github.com/openstack-infra/system-config/tree/master/modules, pick your module17:59
asselin_then there's an 'circle like icon' on the top right18:00
asselin_"browse commits for this branch"18:00
asselin_3. quick visual inspection of the 218:00
jeblairasselin_: makes sense.  also "git diff ." in the local module dir should match the commit list for the new repo.18:01
jeblairmmedvede: i like the clone + recursive diff -- 2 commands and provides a conclusive negative quickly18:02
jeblairso maybe it's good to do the recursive diff first and double check with the commit list18:02
jeblairanyway, it looks like triniplex-test/puppet-gerrit is out of date by one commit18:02
jeblairso i -1d that change18:02
mmedvedejeblair: this is command '    diff -r -u -x.git <repo_in_question> system-config/modules/$module'18:02
mmedvedejeblair: checking puppet-gerrit18:03
asselin_another 30 minute meeting. back soon18:03
nibalizerjeblair: im glad that you are checking the upstreams rigorously18:04
jeblairmmedvede: oh i may have been wrong about puppet-gerrit18:05
jeblairnibalizer: well, trying at any rate :)18:05
mmedvedejeblair: rechecked puppet-gerrit, seems fine18:05
mmedvedestill up to date18:05
jeblairmmedvede: yep, i agree. sorry about that.  so puppet-gerrit is ready18:06
jeblairfungi, clarkb: want to aprv? ^18:06
clarkbjeblair: looking18:06
mrmartinthis seems to be empty: https://git.openstack.org/cgit/openstack-infra/puppet-redis/ but this patchset seems to be passed: https://review.openstack.org/#/c/149953/18:07
jeblairand yeah, anyone who wants to do the recursive-diff and commit list check to verify that repos are up to date, please do so, and leave a comment to that effect on changes18:07
nibalizeri'm setting my project-config changes to depend on each other18:07
mrmartinand it is not synced to github18:07
nibalizerthat way its not rebase-city18:07
jeblairnibalizer: sounds good18:07
clarkbjeblair: done18:07
jeblairmrmartin: yeah, i believe that's because of the ansible bug we found (i moved the discussion of that over to infra)18:07
nibalizeritll still maybe be rebase city because we're all messing about int projects.yaml, but at least this way we have a chance18:08
jeblairmrmartin: i was hoping the next pass would fix it18:08
mrmartinam I need to do something?18:08
clarkbso I assume once we have a bunch of new projects we then go through the system-config changes and review/approve those to start using the new modules18:08
jeblairclarkb: yeah, keep status updated at the bottom of the etherpad: https://etherpad.openstack.org/p/puppet-module-split-sprint18:08
clarkbmrmartin: let me look18:08
jeblairclarkb: should basically just move projects down through that list18:08
clarkbjeblair: I see the list now thanks18:09
fungimrmartin: i don't think so, we just need to double-check that it fixed itself (or manually intervene)18:09
mrmartinok.18:09
jeblairfungi, clarkb, mrmartin: i think puppet is running there now18:09
jeblairlet's see the result of this run18:09
nibalizerwow storyboard as a tool to quickly add people to subtasks is AMAZING18:11
* mrmartin going to eat something, I'll look back later18:14
pleia2hm, are we using Triniplex-Test or Triniplex?18:16
jeblairpleia2: sweston is getting the script going on triniplex18:17
jeblairso aiui, we should write changes assuming that will be up to date (soonish)18:17
pleia2ok18:17
swestonjeblair, pleia2, mmedvede:  looks like first sync is done, and updates are running.  I will look for inconsistencies in about half an hour, as soon as I am free, but feel free to help yourself in the meantime.18:18
pleia2thanks sweston18:19
swestonpleia2: yw18:19
jeblairfungi, mrmartin: redis,drupal,askbot repos are created18:20
mmedvedesweston: thanks18:21
swestonmmedvede: yw18:21
jeblairha!  i don't know whether "puppet-elastic_recheck" comes before or after "puppet-elasticsearch" in our alphabetization check :)18:23
* fungi hopes it's using posix (ascii byte value) sort order18:25
nibalizerooops, i've been doing triniplex-test18:28
* nibalizer will update18:28
nibalizerfungi: i wonder if puppet can handle a module called elastic\arecheck :D18:29
jeblairi tried one, we'll see.  :)18:29
nibalizererp18:29
jeblairand forgot to set topic.  fixing18:29
asselin_i'm back18:30
jeblairclarkb, fungi: 150698 150705 150711 are ready for aprv18:32
clarkbjeblair: rgr looking now18:32
asselin_yeah. I hit the alphabetic issues back here: https://review.openstack.org/#/c/140523/ so in doubt, follow those other files18:33
jeblairi've rechecked the other newly created changes, should have results on those soon18:34
fungion it18:34
fungisorry, was stuffing my face real quick18:35
clarkbjeblair: and when you say those are ready you checked that the repos exist now? /me assumes so and reviews18:35
jeblairi was planning on only eating puppet modules18:36
clarkboh tests wouldn't pass until that happens right?18:36
jeblairclarkb: yes and yes.  i move them from "split merged" to "repos created" after i verify that they exist on git.o.o.  then i 'recheck'18:36
clarkbfungi is beating me to them18:36
fungijeblair: clarkb: 150831 too18:36
fungiright?18:36
jeblairyep, missed that one18:37
fungiclarkb: sorry, since you're reviewing them too i'll leave off the approval18:37
asselin_jeblair, recheckwatch is used here: remove it? https://github.com/openstack-infra/system-config/blob/master/modules/openstack_project/manifests/zuul_prod.pp#L10418:38
clarkbfungi: no problem I sa don't wait for me18:38
clarkbfungi: its mostly cookiecutter anyways and jeblair did the hard bit18:38
jeblairasselin_: yep.  can all go away.18:38
fungiyup18:38
asselin_will do18:38
jesusaurusasselin_: oh was i not on latest master?18:41
* jesusaurus looks at the diff18:41
asselin_jesusaurus, not sure....18:41
jeblairapproved asterisk creation18:42
jeblairand iptables18:44
clarkbok puppet-gerrit is on git.o.o I am going to recheck the system-config  change for that module18:44
jeblairapproved reviewday add18:46
jeblairyeah, the alphabetization is the other way18:47
mrmartinfungi: the openstackid fails on puppetlint, here: https://github.com/openstack-infra/puppet-openstackid/blob/master/manifests/init.pp#L52 do you remember for this boolean value?18:47
fungifixing merge conflicts on 150705 and 150711 now18:47
mrmartinwhat you suggest, make a real boolean from this value, or some change required in lint rules?18:48
clarkbmrmartin: making it a real boolean should be fine just make sure you double check ewhere it is used and fix an comparison that might expect a string18:48
clarkbmrmartin: but ruby/erb should coerce true the boolean to 'true' the string when writing it out if that is necessary they just won't be equivalent when compared to each other18:49
jesusaurusasselin_: they look the same to me, what differences are you seeing?18:52
asselin_jesusaurus, hmm...maybe it's just different in the github ui that I was using?18:53
asselin_jesusaurus, 4th commit here is different: https://github.com/jesusaurus/puppet-cgit/commits/master18:54
asselin_than this one: https://github.com/openstack-infra/system-config/commits/master/modules/cgit18:54
asselin_maybe it's just the 2 "reverts"18:55
clarkbfungi: I reapproved the two you rebased so hopefully those get in soon18:56
jeblairapproved planet add18:57
jesusaurusasselin_: oh, interesting, git-subtree seems to have dropped both the revert commit and the reverted commit18:57
fungiclarkb: thanks18:57
jeblairthat is interesting.  i did not know it would do that.18:58
mmedvedejesusaurus: I've noticed that too, subtree split tends to get rid of null-effect commits18:58
jesusaurustoday i learned...18:59
fungi150828 and 150834 are also good to go but going to merge-conflict so i'll rebase them now19:00
jeblairso i'd prefer the full history with reverts, but i'm also not so tied to that that i think we need to rework the current process.  so i'm inclined to say that we should accept the output of subtree (where it removes null-effect commits)19:04
jeblairanyone object?19:04
asselin_let me check triniplex19:04
clarkbjeblair: I too prefer full history but am not worried enough about it to change the process19:04
asselin_but i'm not tied to it either19:04
jeblairasselin_: oh, do you think triniplex has a different process?19:05
asselin_just want to compare19:05
mmedvedejeblair: I also prefer history with reverts19:05
asselin_seems to have the reverts: https://github.com/Triniplex/puppet-cgit/commits/master19:05
mmedvedeI would say if there is a flag for subtree to allow null-effect commits, we should use it. Otherwise we have to change the workflow19:06
jesusaurusoh, has triniplex already made repos for all of the modules?19:07
asselin_jesusaurus, yes, sweston is running his script to create all the repos19:08
jeblairjesusaurus: yes, sweston just ran the script to update them (so we need to carefully double check them)19:08
mmedvedehehe19:08
jeblairthat's interesting that has has the commits.  seems like we should use that then.19:08
jesusaurusi was going off of storyboard to see which ones weren't in progress yet19:08
asselin_jesusaurus, no, storyboard is accurate.19:09
asselin_jesusaurus, sweston's script just creates the repo. but you can use it for the actual moduel you pick in storyboard19:09
nibalizerjeblair: ++ to using subtree and ya it sucks that its not perfect but hey lets get this done19:09
jesusaurusasselin_: oh, ok, so all of the repos are created, and storyboard 'progress' just means that we are creating the changes to propose in gerrit?19:12
jeblairsweston's script does a bit more than just subtree19:12
asselin_jesusaurus, yes19:12
pleia2https://github.com/Triniplex/puppet-mediawiki looks a bit funny with the templates/apache bit there, thoughts? (templates/apache as a directory structure does exist in system-config)19:18
clarkbpleia2: if you hover over it github tells you why they are being special19:19
mrmartinpleia2: what's wrong with that?19:19
clarkb"this path skips through empty dirs"19:19
pleia2clarkb: ah, thanks19:19
jesusaurusasselin_: ive updated the patch to point at triniplex-test19:20
mrmartinwe have a very old apache module, and it is a typical way to customise the vhost config of apache19:20
asselin_jesusaurus, ok19:20
clarkbpleia2: they use a similar font color for submodules too19:20
pleia2clarkb: I guess I just don't look at github much19:22
* nibalizer gonna go hunt down a burrito, be back in a bit19:25
jeblairnibalizer: you have comments on 150888 and 15089119:25
clarkbfinally I think https://review.openstack.org/#/c/150814/ is ready19:30
pleia2I need to run out for some pre-travel things, probably lunch too19:30
jesusauruswhats the difference between triniplex and triniplex-test? is it important to not use triniplex-test?19:31
fungifor puppet metadata.json are we okay ignoring dependencies for now and worrying about that later? for example, mmedvede's comment at https://review.openstack.org/#/c/150885/1/metadata.json19:31
asselin_jesusaurus, use triniplex. triniplex-test seems to be outdated19:31
clarkbfungi: for us it should continue to work because of how we use install modules. but eventually we should clean it up and properly list deps19:32
asselin_otherwise it's the same...we didn't want to update triniplex-test b/c some in-flight changes19:32
jesusaurusahh, ok19:32
fungiclarkb: yeah, i figured for the sake of expediency that can be left as a future lhf exercise19:32
fungijust want to make sure we're all on the same page19:32
jeblairpleia2: thanks!19:33
jeblairi just approved statusbot, sudoers, tmpreaper, accessbot, releasestatus, graphite, mediawiki, unbound, user, and ssh19:34
fungiawesome19:35
clarkb150814 too19:36
clarkbpretty sure its ready. jenkins says +119:36
funginibalizer: the only complaint with 150888 seems to be whitespace, so i'll fix that for you19:36
*** krtaylor has quit IRC19:41
jeblairi've updated the etherpad with info for commiters and reviewers based on our current processes19:42
swestonmmedvede: if it's really crucial, I believe that we can do a filter on the split for null-effect commits19:44
swestonif anybody has any questions I am back, and can answer them now ;-)19:44
jeblairsweston: my understanding is that whatever you are doing for triniplex is correct -- i think asselin_ said that your repo does have the revert commits19:45
mmedvedesweston: I think we came to conclusion we want to keep null-effect commits19:45
asselin_sweston, yes it did19:45
* mmedvede in meeting for the next 30 minutes19:46
swestonjeblair, mmedvede, asselin_ : ok.  yes, all commits are kept by the current logic19:46
jeblairi am going to make and eat food now.  hopefully some changes will have merged by the time i get back.19:46
funginibalizer: i'm updating 150891 for you based on reviewer feedback too19:46
jeblair(looks like there are a few more project-config changes that could be reviewed)19:47
clarkbI am going to make a review pass now before lunch19:47
clarkbpleia2: https://review.openstack.org/#/c/150903/ needs alphabetizing19:48
clarkbjeblair: any reason you didn't approve 150926?19:49
*** krtaylor has joined #openstack-sprint19:53
fungi150885 is ready too19:54
nibalizerfungi: thanks for doing that, sorry to make more work for you19:55
funginibalizer: not at all. that was trivial19:55
clarkbasselin_: for https://review.openstack.org/#/c/150854/3 was there something specific that concerned you about the two repos being different?20:00
clarkbasselin_: diff for me says they are the same but I figured I would double chekc since your comment implies maybe it needed more scrutiny20:00
asselin_clarkb, we got that resolved20:01
clarkbasselin_: cool so I am good to approve?20:01
asselin_yes20:01
clarkbdone20:01
jeblairclarkb: i did; mmedvede uploaded a new patch20:06
jeblairlooks like a rebase20:06
jeblairaprvd20:06
clarkbjeblair: oh missed that sorry20:06
jeblairor rather, asselin_ uploaded a new patch20:07
jesusaurusclarkb: the difference was in git-subtree dropping a commit and the revert immediately following it20:10
clarkboh that was in that repo20:10
asselin_these are a bit different: https://github.com/Triniplex/puppet-exim/commits/master20:16
asselin_https://github.com/openstack-infra/system-config/commits/master/modules/exim20:16
asselin_nibalizer, you comment that they're good right? maybe visual inspection isn't sufficient? ^^20:18
asselin_https://review.openstack.org/#/c/150946/120:18
* asselin_ going for lunch20:20
nibalizerasselin_: so what i've been doing is subtree splitting in my own local checkout20:24
nibalizerthen comparing that to the commit history on the triniplex github20:25
nibalizerand im largely ignoring incidents of commit/revert showing up or not showing up, since we've established we don't care too much about that20:26
fungi150894 and 150892 are merge-conflicting with master now, so i'll rebase them20:26
jeblairback20:28
*** rfolco has quit IRC20:30
fungi150924 and 150859 look like they're probably shortly getting kicked out of the gate on merge conflicts with other approved changes20:32
fungiyep, 150924 just came back. rebasing now20:33
jeblairi approved the deletes that were reday20:33
fungithanks20:34
nibalizerasselin_: minor issue https://review.openstack.org/#/c/140431/20:34
clarkbpleia2: is there a project-config change for graphtie split? I see the system config change but not the project-config change20:38
asselin_nibalizer, thanks fixed20:38
jeblairasselin_: i think that in 150946 the difference is that a merge commit is missing.  the actual commits are there.  i believe that's probably to be expected in a history rewrite like this and is okay.20:38
pleia2clarkb: looking, I thought I had20:38
pleia2clarkb: doh, half done, finishing now20:38
pleia2and needs a rebase now anyway, so will redo from current master20:39
jeblairasselin_: would you agree with that?20:39
* asselin_ looking20:39
pleia2clarkb: wait, it was already merged: https://review.openstack.org/#/c/150916/20:40
clarkbpleia2: oh no wonder I didn't see it. just waiting for the repo to end up on the mirrors then?20:40
clarkbit merged recently enough that I probably just need to be more patient20:40
pleia2clarkb: yeah, it was recent20:40
pleia2I'm so happy we're doing this today, fosdem talk on Saturday is about puppet and we're in much better shape than the first couple times I've given similar talks :)20:42
pleia2look how great we are with all our split out modules20:42
asselin_nibalizer, jeblair ok I think it's fine20:42
krtaylorrebased both bup patches, they should be ready for review 150830 and 15089520:48
jeblairpleia2: ++!20:48
krtaylorhehheh20:48
fungipleia2: heh, the tarnished silver soup tureen calling the kettle black, are we?20:51
jesusaurusis the remove_nginx class still used/needed or can we just delete it?20:51
jeblairjesusaurus: just delete20:51
fungijesusaurus: i believe it can just disappear20:51
fungiif it _is_ used anywhere, delete the use of it while you're at it20:52
jesusauruswill do20:52
fungibut i think i already found/removed a lot of them if not all20:52
jeblairpuppet-askbot has a boilerplate change that can be aprvd20:52
pleia2fungi: turns out it's actually valuable in the talk that we did it "wrong" previously, we have a whole spec that talks about to do it the right way20:53
fungipleia2: absolutely20:53
pleia2or that's what I tell myself20:53
jeblairpuppet-gerrit as well20:54
jeblairmmedvede: i think puppet-elasticsearch is ready for a boilerplate patch20:58
jeblairmmedvede: oh, sorry, my repo was up to date.  it has already landed.  nm.20:59
jeblairwill update etherpad20:59
fungithe redis and openstackid boilerplate changes are also ready for another +2/approval20:59
pleia2https://github.com/Triniplex/puppet-lodgeit is empty (and was called "lodgetit" in storyboard, fixed after giggles)21:00
jeblairfungi: can you re-examine 135376 (there are comment replies to you there)21:00
jeblairsweston, mmedvede: can you look into puppet-lodgeit?21:02
pleia2oh, there is already a puppet-lodgeit module21:02
fungijeblair: nibalizer: thanks, approved 13537621:02
mmedvedejeblair: looking21:02
pleia2http://git.openstack.org/cgit/openstack-infra/puppet-lodgeit/21:02
pleia2so I don't think we need to do that one afterall21:02
jeblairpleia2: oh, oops, it's already done21:02
fungipleia2: maybe we missed the follow-on delete change for it?21:02
mmedvedeoh yes, I think it was merged / split a while back21:02
jeblairmmedvede, sweston: sorry, nevermind21:03
fungipleia2: nope, it's definitely absent from system-config so we're fine21:03
pleia2fungi: it's actually been there for a while, come to think of it21:03
jeblairit's marked as merged, but has no assignee in storyboard21:03
fungiyeah, i seem to remember it going in early as a proving ground for the process21:03
jeblairadded jesusaurus to it for completeness21:04
asselin_yes I marked it merged but didn't know who21:04
asselin_also 'github' is merged, but I put myself there accidently. not sure who did that one21:04
asselin_(and I can't remove myself)21:04
clarkbhrm still no puppet-graphite21:04
jeblairclarkb: most recent git04 encountered the timeout bug21:05
jesusaurusjeblair: oh whoops, thanks21:05
fungijeblair: we're also hitting it in centos jobs, like this just now http://logs.openstack.org/85/150885/1/gate/gate-infra-puppet-apply-centos6/a4f455f/console.html#_2015-01-28_20_29_42_74121:06
nibalizerfungi: neato!21:06
swestonjeblair: no worries21:07
jeblairfungi: it seems like the git servers are under a lot of load right now?21:07
*** ianw has joined #openstack-sprint21:07
fungijeblair: i'm looking in cacti for any sign of the issue21:07
clarkbI recently looked at cacti and bw use is low21:07
clarkbwhich I would expect to correspond to load21:07
clarkbbut I was looking at front ends not backends21:08
jeblairthey have been seeing load spikes recently21:09
mmedvedejhesketh: are you working on ehterpad_lite module? It was unassigned in storyboard21:09
clarkbjeblair: appears to correspond to spikes in disk activity21:10
clarkbbut not bw21:10
asselin_2 modules left unassigned in storyboard: mysql_backup & packagekit21:11
fungiyeah, load spikes up to ~10021:11
ianwis being unable to login to storyboard a known thing?21:11
jeblairianw: no, best to move back to #infra and ask about that21:12
fungithose load spikes on the git backends are hitting different servers at different times, so almost certainly something pounding git.o.o from a single source and getting persisted to one backend at a time21:13
jeblairboilerplate for puppet-zuul is ready for aprv21:15
clarkbjeblair: reviewing21:16
jeblairrebasing 15088821:17
clarkbpuppet zuul boilerplate is approved21:18
clarkbstepping out for food back in a bit21:18
pleia2asselin_: all assigned \o/21:19
fungiwe've got a nice pipeline of changes flowing through that etherpad now21:20
jeblairrebasing 15093221:20
ianwfixed storyboard link in 136959 (puppet-httpd)21:20
fungirebasing 15093621:21
fungioh, and 150926 since i had them stacked previously21:22
asselin_pleia2, yup :)21:22
nibalizerasselin_: merge conflict on https://review.openstack.org/#/c/150926/21:23
* asselin_ looking21:24
nibalizerer it looks like fungis on it21:24
asselin_ok21:24
fungiyeah, mentioned above i was rebasing them21:25
fungirebasing 15085921:28
*** mrmartin has quit IRC21:30
jeblairrebasing 15088221:31
jeblairand 15088121:31
fungirebasing 15089121:34
asselin_FYI: I "assigned" in storyboard  the previously merged/deleted  modules to the commiter who removed them21:36
jeblair++21:36
jesusaurusrebasing 15092021:36
fungipuhpow21:37
jeblair150830 can use a +321:38
jeblairand 150974, 150978, and 15098421:40
jeblairasselin_: 150968 has a -1 comment21:44
asselin_lookin21:44
asselin_jeblair, fixed & rebased21:46
jeblairlogstash is already in boilerplate merged (last step)21:49
asselin_pleia2, needs rebase https://review.openstack.org/#/c/150914/21:51
jeblairrebasing 15087321:52
asselin_pleia2, I'll rebase 15091421:52
pleia2k, thanks21:53
fungiyeah, at this point i think if a sprint change needs a rebase or cosmetic fixes, it's faster to just do it than -1 or ping someone21:53
jheskethMorning21:54
jheskethFeel free to ping me for reviews etc21:54
jeblairjhesketh: awesome; check out the info on the etherpad: https://etherpad.openstack.org/p/puppet-module-split-sprint21:55
jeblairjhesketh: all of the modules have been assigned,  so we're mostly reviewing/approving/rebasing changes now21:55
jeblairjhesketh: at the bottom of the etherpad, i'm moving names of modules down those 4 sections to help keep track of the workflow for them21:56
jheskethOkay cool, thanks21:57
jeblairrebasing 15089421:57
fungiwe have a pile of new needed rebases. i'll take 150950, 150903 and 15083021:59
clarkbfungi I really want a picture of the no rebase sign now22:00
fungiclarkb: http://static.lolyard.com/lol/no-rebase.jpg22:01
fungi(proving my point of why bother to bring a camera when someone else has already taken all the pictures of the places i'm going and posted them to the internet)22:02
jeblairrebaisg 15091022:03
jeblairrebasing 15093322:05
fungirebasing 15090522:06
nibalizerfungi: whoa22:06
nibalizerthats kinda mind blowing22:06
nibalizerplus they probably got the lighting right and had a better camera anyways...22:06
pleia2fungi: your camera logic is no fun :)22:07
fungipleia2: but characteristically lazy22:08
fungirebasing 15085722:08
jeblairbtw, we should be keeping the modules.env list in alpha order22:11
jeblairi know there isn't a check for that, but it helps (a little) with rebases22:11
jeblairi will update 150852 to reorder22:11
nibalizerjeblair: it didn't start that way but yea i agree its a good idea22:11
fungi150960 has an alpha order failure in projects.yaml. i'll upload a fixed version22:13
asselin_At this point, I think we should fix as part of rebasing changes22:14
jeblairasselin_: makes sense22:14
mmedvedeAre all of the modules need to be split? Because some of them are not on storyboard, e.g. kerberos22:14
jeblairah, that's a late addition22:15
asselin_mmedvede, I synced storybaord with the spec.22:15
jeblairi think it was added after spec approval.  we can/should split it i think.22:15
asselin_mmedvede, also the premerge of project-config is only what was in the spec22:15
fungiasselin_: jeblair: yeah, as i rebase changes to modules.env i've been trying to tease them closer into alpha order22:15
mmedvedeasselin_: ok, thanks for that. Forgot about the pre-merge...22:16
nibalizerwhat should i be doing to help?22:16
jeblairnibalizer: i think we're mostly watching for conflicts and rebasing at this point22:18
jeblairmmedvede: might have some more modules to add to the list?22:18
mmedvedejeblair: checking now22:18
mmedvedeI have pushed kerberos22:19
mmedvedeBut forgot about the pre merge, need to fix that22:19
jeblairmmedvede: i'm guessing there will similarly be an openafs module22:19
jeblairfixing 15096122:20
nibalizerjeblair: ya, it seems like at this point it becomes de-parallelized and cores have to line things up/rebase/+a22:20
jeblairwell, anyone can rebase/recheck; i'm doing very little +Aing22:20
jeblairi am half-tempted to try to stack all of the changes, but what's already in zuul, etc, makes that a bit complex22:21
jesusaurusfungi: oh, you fixed 150960. i was trying to figure out why it didnt think i was making a change22:21
fungijesusaurus: yep, mentioned in scrollback22:22
nibalizeri feel like if I try to rebase anything i'll just step fungi's toes22:22
* jesusaurus goes back to adding boilerplate22:22
funginibalizer: not at all! before i rebase anything i mention it in here and keep an eye on what anyone else says they're rebasing/fixing22:22
fungiso as to avoid any more duplication of effort than we're already stuck with22:23
jeblairrebasing 15096222:23
fungitaking a break for a few to heat up dinner22:24
nibalizerokay22:25
nibalizerim gonna take a stab then!22:25
mmedvedeIs it possible to unassign task in storyboard? Can not add a new task without assigning it to myself...22:25
jeblairmmedvede: i would ask krotscheck in #openstack-infra22:26
asselin_mmedvede, not that I know of. but I've been able to create new tasks unassigned22:26
mmedvedejeblair, asselin_: thx22:26
* asselin_ going for a 30 minute meeting22:30
* nibalizer gonna rebase 15086122:31
clarkbhttps://review.openstack.org/#/c/150960/ looks like it got caught in rebasing? should be ready for approval though22:31
clarkbjeblair: fungi ^22:31
fungirebasing 15097222:32
fungirebasing 15091722:35
clarkbwhenever people say "rebasing" I think of the "reloading" yells in L4D22:35
nibalizergonna rebase 150882 even though jim did it an hour ago22:36
fungithere will be a lot of that unless we stack them all22:37
mmedvedeadded 5 more modules into storyboard. They all have no changes pre-merged yet22:37
nibalizeryea... should we try to stack?22:37
nibalizerim trying to mentally figure out if we eventually converge or if it just cycles22:37
nibalizeri think it conversges22:37
jeblairif we do so, we need to stack _everything_ and we can't let anything merge that isn't stacked because of the octomerge issue22:37
krtayloroctomerge? sounds like a Bond character22:39
jeblairre-alphabetizing 15088822:41
jeblairjhesketh: are you around to start helping out on approvals?22:44
jeblairrebasing 15093222:45
jeblairoh that one just needed to be un-based (its parent was messed up)22:46
jeblair(stacking fail)22:46
jheskethjeblair: sorry in about 20min?22:50
fungijhesketh: there's still plenty to chew on, i think22:52
nibalizerjeblair: so this one is wildly unalphabetized https://review.openstack.org/#/c/150857/2/modules.env does that mean i should rebase it?22:52
jeblairnibalizer: only if it needs a rebase22:54
jeblairnibalizer: (zuul queue position is too precious now to waste :)22:55
nibalizermk22:56
nibalizerso i can detect that by pulling it down and attepmting to rebase onto master22:56
nibalizeror i can press that button22:56
nibalizerbut im worried about that button, never been super sure what it does22:56
jeblairnibalizer: the button will (if needed) create a new patchset, so don't do that right now22:57
jeblairnibalizer: zuul will return a patch conflict immediately on enquing, so once it's in check, zuul will tell us if it conflicts with master; however, once it moves to gate, it still might conflict with something ahead22:58
jeblairnibalizer: so sometimes we get +1 and the -2 on these22:58
jeblairnibalizer: the only thing you could do locally to work ahead of zuul would be to try to apply it to master + whatever else is in gate22:59
jeblairnibalizer: if you do that and it fails, it's worth cherry-picking it onto the tail of the gate queue22:59
* nibalizer nods23:00
* asselin_ is back23:04
jeblairrebasing 15092723:09
jheskethjeblair: okay, I'm going to reviews now.. any in particular you wanted me to look at?23:19
asselin_is metadata.json or Metadata.json correct? or either is fine?23:20
clarkbjhesketh: I have just been going through the main list of open reviews for that otpic and finding changes without +2's or approvals23:20
jeblairnibalizer: ^?23:20
jheskethclarkb: will do23:20
fungijhesketh: https://review.openstack.org/#/q/topic:module-split+status:open,n,z23:20
fungichurn through all the things23:20
jeblairjhesketh: and also watching out for failures that may need rebasing / reapproval23:20
asselin_nibalizer, is metadata.json or Metadata.json correct? or either is fine?23:21
jeblairgerritbot repo was just created, so i'm rechecking 150983 now23:21
jheskethjeblair: do we have automatic puppet updates turned off during this sprint?23:22
jeblairjhesketh: nope, everything is operating normally23:22
nibalizerasselin_: lower case please23:23
fungirebasing 15093523:23
asselin_ok23:23
jeblairjhesketh: all the changes should be noops23:23
jeblairjhesketh: and we've already completely finished gerrit (and many others) without breakage23:24
jheskethcool23:24
jeblair151000 is ready for aprv23:26
clarkblooking23:26
jheskethasselin_: 151039 any reason why you didn't put the rake file or the metadata in that change?23:28
asselin_jhesketh, just added them23:28
asselin_for to include them in the first patch23:29
asselin_forgot23:29
jeblairthe check queue graph is trending downward; we might speed up soon  (cross fingers)23:29
fungiyeah, the massive gate breakage is fixed, so now we just have the massive backlog it caused23:29
mmedvedeAdded bulk changes needed for remaining  5 modules https://review.openstack.org/#/c/151041/23:30
jeblairmmedvede: cool, thanks23:32
jeblairmmedvede: so i left comments on that that i thought we didn't want to split project_config, but then i realized i was probably wrong about that and it's fine...23:32
jeblairdoes that sound right to everyone?23:32
clarkbwait what is puppet-project_config?23:33
clarkboh the thing tha installs project-config23:33
jeblairclarkb: yep23:33
mmedvedeyes23:34
jeblairclarkb: so it should take "your project config repo git url" as a parameter and check it out for you23:34
clarkband define some parameters23:34
jeblairand it also provides puppet vars that other modules can use23:34
clarkbkk23:34
clarkbwait did puppet-subversion merge?23:35
clarkbI see it in the projects list23:35
clarkbnibalizer: ^23:35
jeblairclarkb: is it just in the base for that patch?23:35
jeblairclarkb: if so, you're probably looking at the pre-merge stuff that was added a long time ago23:36
jeblairclarkb: we'll want to clean that up, but it's not urgent23:36
clarkbya I think so23:36
jeblairas long as it's not in projects.yaml23:36
nibalizerclarkb: puppet-subversion just got refactored out23:38
nibalizerit was a whole class for package { 'subversion': }23:38
nibalizeri dont care if project_config splits or not23:39
nibalizercould go either way23:39
fungiclarkb: right, the removal patch for it merged23:41
fungithere was no split patch, just one that replaced it by the package resource in the one module using it23:41
fungii'm starting to wind down over here, but will check in a bit later on to see if things are getting stuck and need me to jump back in23:57
fungiamazing progress on the sprint so far23:57
nibalizerindeed!23:59
mmedvedefungi: I have 5 more modules coming in soon23:59
fungimmedvede: awesome!23:59
jeblairi have to run out for a bit but will be back soon23:59
jeblairping clarkb and jhesketh if approvals are needed :)23:59

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