Friday, 2014-11-21

*** emagana has quit IRC00:02
*** emagana has joined #openstack-chef00:02
*** Viswanath has joined #openstack-chef00:04
*** emagana has quit IRC00:07
*** emagana has joined #openstack-chef00:08
*** Viswanath has quit IRC00:09
*** dmowrer has joined #openstack-chef00:09
*** emagana has quit IRC00:10
*** dmowrer has quit IRC00:10
*** dmowrer has joined #openstack-chef00:10
*** emagana has joined #openstack-chef00:10
*** ChrissKO_ has joined #openstack-chef00:21
*** ChrissKO_ has quit IRC00:26
*** emagana has quit IRC00:47
*** emagana has joined #openstack-chef00:48
*** emagana has quit IRC00:52
*** zhiwei has joined #openstack-chef01:03
*** jmickle has quit IRC01:23
*** jmickle has joined #openstack-chef01:23
*** jmickle has quit IRC01:24
*** wenchma has quit IRC01:24
*** jaypipes has quit IRC01:24
*** jaypipes has joined #openstack-chef01:38
*** MrMonkey has quit IRC01:50
*** ChrissKO_ has joined #openstack-chef02:10
*** nosnos has joined #openstack-chef02:12
*** ChrissKO_ has quit IRC02:15
*** galstrom_zzz is now known as galstrom02:17
*** erictian has joined #openstack-chef02:35
openstackgerritZhiwei Chen proposed stackforge/cookbook-openstack-compute: Add nova-docker configuration to nova.conf  https://review.openstack.org/13551003:03
*** GonZo2K has quit IRC03:07
*** erictian has quit IRC03:15
*** nosnos has quit IRC03:24
*** erictian has joined #openstack-chef03:27
*** erictian has quit IRC03:30
*** ncerny has joined #openstack-chef03:33
*** ncerny has quit IRC03:36
*** harlowja is now known as harlowja_away03:39
*** os-chef-bot has quit IRC03:43
*** os-chef-bot has joined #openstack-chef03:43
*** galstrom is now known as galstrom_zzz03:58
*** ChrissKO has joined #openstack-chef03:59
*** ChrissKO has quit IRC04:03
*** Viswanath has joined #openstack-chef04:09
*** Viswanath has quit IRC04:13
*** nosnos has joined #openstack-chef04:29
*** erictian has joined #openstack-chef04:30
*** neelashah has joined #openstack-chef04:53
*** neelashah has quit IRC05:02
*** erictian has quit IRC05:04
*** nosnos has quit IRC05:14
*** nosnos has joined #openstack-chef05:16
*** ChrissKO_ has joined #openstack-chef05:47
*** ChrissKO_ has quit IRC05:52
*** nosnos has quit IRC05:59
*** nosnos has joined #openstack-chef06:00
*** jmickle has joined #openstack-chef06:07
*** tryggvil has quit IRC06:07
*** erictian has joined #openstack-chef06:15
*** ehaselwanter has joined #openstack-chef06:16
*** k4n0 has joined #openstack-chef06:17
*** erictian has quit IRC06:19
*** jmickle has quit IRC06:21
*** ehaselwanter has quit IRC06:54
*** nkrinner has joined #openstack-chef06:59
*** opscode-logger has quit IRC07:00
*** opscode-logger has joined #openstack-chef07:00
openstackgerritZhiwei Chen proposed stackforge/cookbook-openstack-image: Add upload docker image logic to image provider  https://review.openstack.org/13625007:12
*** ehaselwanter has joined #openstack-chef07:15
openstackgerritJürgen Brüder proposed stackforge/openstack-chef-repo: Replaced references to Opscode  https://review.openstack.org/13605007:19
*** otter768 has quit IRC08:20
*** nosnos has quit IRC08:24
*** nosnos has joined #openstack-chef08:24
*** nosnos has quit IRC08:51
*** nosnos has joined #openstack-chef08:51
*** nosnos has quit IRC09:06
*** nosnos has joined #openstack-chef09:34
*** GonZo2K has joined #openstack-chef09:43
*** GonZo2K has quit IRC09:49
openstackgerritMerged stackforge/cookbook-openstack-block-storage: The default has a capital s  https://review.openstack.org/13607009:51
*** k4n0 has quit IRC09:53
*** tryggvil has joined #openstack-chef09:58
*** tryggvil has quit IRC10:01
*** zhiwei has quit IRC10:03
*** otter768 has joined #openstack-chef10:21
*** otter768 has quit IRC10:25
*** tryggvil has joined #openstack-chef10:37
*** tryggvil has quit IRC10:37
*** tryggvil has joined #openstack-chef10:40
*** ehaselwanter has quit IRC11:31
*** ehaselwanter has joined #openstack-chef11:55
*** otter768 has joined #openstack-chef12:22
*** otter768 has quit IRC12:27
*** ehaselwanter has quit IRC12:27
*** zhiwei has joined #openstack-chef12:36
*** ChrissKO has joined #openstack-chef12:41
*** ChrissKO has quit IRC12:44
*** zhiwei has quit IRC12:57
*** galstrom_zzz is now known as galstrom13:02
*** ehaselwanter has joined #openstack-chef13:02
*** ChrissKO has joined #openstack-chef13:08
*** ChrissKO has quit IRC13:11
*** nosnos has quit IRC13:16
*** ChrissKO_ has joined #openstack-chef13:20
*** ChrissKO_ has quit IRC13:22
*** judd7 has quit IRC13:26
*** rtheis has joined #openstack-chef13:42
*** galstrom is now known as galstrom_zzz13:43
*** ctracey has quit IRC14:15
*** ctracey has joined #openstack-chef14:18
*** libsysguy has joined #openstack-chef14:18
*** otter768 has joined #openstack-chef14:23
libsysguyos-chef-bot: irc meeting?14:24
libsysguyos-chef-bot: !irc-meeting14:25
os-chef-botOur IRC status meeting/office hours are at 15:30 GMT 10:30 EST 07:30 PST on Fridays we try to have as many core members here so we can discuss topics or issues users are having14:25
*** ncerny has joined #openstack-chef14:27
*** otter768 has quit IRC14:27
*** malfaitc has left #openstack-chef14:35
*** malfaitc has joined #openstack-chef14:37
*** neelashah has joined #openstack-chef14:38
*** nkrinner has quit IRC14:43
j^2Yeah that was supposed to be thrusday14:44
j^2I screwed it up. Ill announce it via ML and the meeting today14:45
libsysguyoh did I miss it14:45
j^2Nope14:48
j^2I forgot to announce the move14:48
libsysguygotcha14:49
j^2And man neutron makes me sad inside14:49
libsysguyhaha it is pretty challenging14:49
j^2I hacked on my system till like 1am14:50
j^2I'm sleep ATM14:50
j^2Sleepy*14:50
libsysguygood, then maybe I can get you to sleep approve my patches :p14:50
libsysguywhat is on the agenda for today?14:51
*** GonZo2K has joined #openstack-chef15:00
*** judd7 has joined #openstack-chef15:12
*** galstrom_zzz is now known as galstrom15:18
openstackgerritMark Vanderwiel proposed stackforge/cookbook-openstack-object-storage: Use Common bind endpoint  https://review.openstack.org/13613415:21
j^2a couple things15:28
j^2is there anything you’d like to add to it?15:29
j^2#startmeeting openstack-chef15:30
openstackMeeting started Fri Nov 21 15:30:14 2014 UTC and is due to finish in 60 minutes.  The chair is j^2. Information about MeetBot at http://wiki.debian.org/MeetBot.15:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:30
openstackThe meeting name has been set to 'openstack_chef'15:30
j^2Hey everyone!15:30
libsysguyo/15:30
j^2There were a couple topics that we have on the agenda, libsysguy is there anything you’d like to add?15:31
libsysguynah, not really15:32
j^2ok15:32
j^2well i’ll jump right in then15:32
j^2#topic Spitballing on a testing idea15:32
j^2over this week i had a community member show up and ask some questions15:33
j^2#link https://botbot.me/freenode/openstack-chef/2014-11-20/?msg=25847921&page=115:33
j^2he was setting up his cluster with our cookbooks and he had an issue that i don’t think we’ve thought about15:33
j^2we’ve though about breaking out the network node, the compute nodes, but his issue was that he had a shared db that someone else used15:34
j^2I think we should try to figure out a way to do remote testing with remote dbs15:34
j^2but i have no idea how we could15:34
j^2any thoughts on this?15:34
libsysguyso mysql was already set up on a remote node?15:35
j^2yeah15:35
j^2he had another box that was owned by someone else15:35
j^2and he was leveraging it for the db for his cluster15:35
j^2i’m thinking this “would be pretty common?"15:35
j^2right?15:35
libsysguyyeah that is what I do15:35
libsysguywell15:35
libsysguyexcept I own the box15:36
libsysguybut I keep mysql and rabbit on one box15:36
j^2ah15:36
libsysguyand the other controller fucntions on a different box15:36
j^2i think i might be over thinking this though15:36
j^2i think we should stay simple first?15:36
j^2i’m not sure though15:36
j^2this is where i’d hope markvan would pop up and start talking :)15:37
fricklerif we get a proper bug report for this, we should certainly fix it15:37
libsysguywell as far as testing goes I am fairly useless15:37
fricklerbut I wouldn't invest much into debugging this myself15:37
j^2frickler: yeah but i’m not sure it’s a “bug” per-se it seems like another test case15:37
markvansorry, late to this show15:38
j^2no worries :)15:38
frickleronce your multi-neutron is running, you could easily do another setup with a split-mysql15:38
fricklerif you want to build a testing environment for that case15:38
j^2frickler: that seems like the path, but is that over engineering something though15:38
j^2i mean then we could have no split on the mysql but with the rabbitmq box15:39
j^2and then all the different databases15:39
j^2i mean it could open up a HUGE can of worms15:39
frickleryes, that why I would put it rather low on priority15:39
markvanit's very common to have the DB on a dedicated or remote node, but not something we need to focus on for our integration testing15:39
j^2i’m looking for feedback here, i’m leaning towards the “KISS” idea with the testing framework and maybe just mention this in the refarchs?15:40
j^2ok cool15:40
j^2i just wanted to bring it up to the group to make sure it was at  least talked about15:40
j^2:)15:40
j^2next topic?15:41
libsysguyyeah I would agree (as an outsider) that it would be nice in a ref arch, but not so much in the integration tests15:41
j^2libsysguy: :D awesoem tahnks, and no you’re an insider now, one of us one of us15:41
j^2#topic Moving of this meeting15:41
*** junhongl has quit IRC15:41
j^2frickler: mentioned this morning that we were supposed to have this yesterday….15:42
j^2I take full responsibility for this not happening15:42
j^2I’m proposing that we move this to thursdays as of two weeks from today15:42
j^2Being next thursday is Thanksgiving in the US15:42
*** GonZo2K has quit IRC15:42
j^2any objections?15:42
fricklerso next week no meeting at all?15:43
j^2I’ll have the hangout though15:43
j^2os-chef-bot: !status-meeting15:43
os-chef-botOur hangout (live) status meeting are at 15:30 GMT 10:30 EST 07:30 PST on Mondays and we post the links to the Google Group: https://groups.google.com/forum/#!forum/opscode-chef-openstack15:43
*** GonZo2K has joined #openstack-chef15:43
fricklerno IRC meeting I wanted to say15:43
frickleror IRC on Friday next week?15:43
j^2yep, i dont think we’d have a very good turn out and i’ll be….cooking most if not all of the day ;)15:43
fricklerk15:44
j^2and friday is a huge shopping day in the US and i’ll be…..shopping15:44
j^2:’(15:44
j^2i hate shopping15:44
j^2anyway i digree15:44
j^2digress15:44
j^2any objections to offically moving this meeting to thrusdays after the thanksgiving break?15:44
j^2k, i’ll post something to the ML today to make this happen15:45
j^2frickler: you have a few things you’d like to talk about; so i’ll let you have the floor from now on i’ll take some notes on the dicussion points if taht’s cool15:46
j^2#topic frickler’s show15:46
j^2could we start with: How do we properly handle blueprints? There is a specs-repo, but as long as on can create them directly via launchpad, this seems to mostly get ignored15:46
frickleryes, this occured to me after I had created mine15:47
j^2markvan: thoughts? :)15:47
j^2libsysguy: you too ;)15:47
j^2this also can go into the “storyboard” conversation, but that’s a different topic15:48
fricklerso my proposal would be to either make the specs-repo mandatory, or drop it again15:48
libsysguywell I don't really like the blueprints process15:48
libsysguybut either way it needs to be standard15:49
libsysguyso I'm with frickler15:49
j^2the challange with the blueprints is we have no discussion and/or history around it15:49
j^2it’s just basicly a text box15:50
*** junhongl has joined #openstack-chef15:50
markvanI guess I like the spec reviews, we just need to get used to using them.15:50
j^2there really is no way to mandate this either, we can have an agreement, but anyone can still put in the blueprint and circumvent the process15:51
j^2like frickler did15:51
fricklerhow do other projects solve this?15:51
j^2which highlights this15:51
j^2nova-specs have a big enough team that they can enforce this15:51
fricklerI did this accidentally, read the mail about the repo only later15:52
j^2we’re only a rag-tag group of devs trying to make this stuff work15:52
markvanI think the other projects keep a mich tigher watch on the blueprints....and enforce the process from there.15:52
libsysguywell if we are going full tote with the openstack process we should probably use the specs repo15:52
j^2frickler: i’m not blaming you, i’m just restating the issue i guess in “my words?"15:52
j^2libsysguy: there’s a flip side to this though15:52
j^2the storyboard thing, openstack-infra offically moved to it15:53
markvanIs there a blueprint template we could update to point to the spec repo, thus helping the process along15:53
j^2i think there are parts and processes in it that can inforce the issues we’ve been having15:53
markvanlike we did with the Bugs15:53
j^2markvan: not a horrible idea15:53
libsysguyI am all for automatic enforcement15:53
j^2have another page on the wiki for a “templatized blueprint” page?15:54
markvanand yeah, storyboard is coming, but I think we can wait for the base projects to shake that tree first.15:54
libsysguylink for storyboard?15:54
libsysguyI think I missed that announcement from openstack-infra15:55
j^2#link https://storyboard.openstack.org/15:55
j^2libsysguy: yeah it was a tweet that i found out about the move15:55
j^2i’m still trynig to figure out how to filter the emails that get blasted out15:55
libsysguyso is this mimicking agile style storyboards?15:55
j^2“yes?"15:55
*** emagana has joined #openstack-chef15:55
j^2but i guess this brings up the topic, would we want to start the process of moving to it?15:56
j^2or like markvan says wait for the other groups to adopt15:56
markvanand/or maybe we can set the Specification URL to required instead of optional?   Not sure what is configurable in the lanuchpad blueprint register page.15:56
libsysguyif it is an official move on the part of openstack, I wouldn't be opposed15:56
libsysguybut then again I like the bleeding edge15:56
fricklerso how about sticking with launchpad until we either go directly to storyboard or decide it takes too long to become useable?15:56
libsysguy^^15:56
j^2markvan: yeah we can’t configure anything on launchpad iirc15:57
j^2frickler: that’s the challange though, how do we know when that is, and how do we know about the migration process?15:57
j^2i’ve got a feeling it might be a lot of work15:57
*** judd7 has quit IRC15:58
*** judd7 has joined #openstack-chef15:58
j^2i mean we don’t have to have the desicion here right now, but i wanted to bring it up for people to think about15:59
markvansince most of the base projects are still using spec/blueprint process for kilo, I thnk we should continue down that road as well and learn more about storyboard16:00
j^2anyway, sorry, i kinda diverted the conversation, frickler would a templatized blueprint for specs help? would that fullfill your issue?16:00
j^2markvan: sounds good16:00
markvanhumm, we already have a template for the specs, it just that we can't configure launchpad blueprints to enforce anything.16:01
fricklermainly I want to clarify whether the specs-repo is optional16:01
markvanis has to be done by the cores16:01
frickleror whether thats the standard way for doing blueprints16:01
j^2frickler: offically no it’s not optional per our decisions a couple months ago16:01
j^2but it’s not enforced it seems16:01
fricklero.k., so I'll try that next time16:02
j^2:D16:02
j^2your next topic was: There is an issue with "rake unit" if run twice in a row, because "berks vendor" will refuse to install the cookbooks into an existing directory.16:02
j^2have you opened a bug on this?16:02
fricklerno, not yet16:03
j^2markvan, libsysguy have you seen this also?16:03
j^2yeah whenever i run the tests, i don’t use the rake file honestly, i run rspec spec16:03
libsysguyI didn't have a problem running rake *test* twice yesterday on the neutron cookbook16:03
markvanyup, I have seen that.  Seems like a bug to me as old berks did not do that.16:04
fricklerwell it's a feature of the new berks, they say16:04
libsysguyI also didn't let it run to completion16:04
j^2interesting16:04
fricklernot to accidentally overwrite stuff16:04
markvanhumm, not sure on their intent here...it just makes dev slower if I have to grab cookbooks each time16:04
j^2yeah frickler can you open the bug for it, and we can start championing this, hell maybe even send it upstream?16:05
j^2frickler: agreed, i think this is so you don’t overwrite stuff16:05
markvanIs there an option on verdor that would allow it?16:05
markvanvendor16:05
j^2markvan: i dont think so16:05
j^2at least not that i know off the top of my head16:05
fricklerno, one has to rm_rf to berks_cookbook directory16:06
j^2yeah there is no option in berks vendor for this16:06
j^2this seems like a upstream bug then16:07
markvanor we could wrapper this with our own check to just skip it if we think the cookbooks are up to date16:07
j^2markvan: i thnk thats over engineering this, i’m betting others have seen this16:07
markvanwow, they missed open source rule #1, everything needs an option.16:07
j^2markvan: ha!16:07
j^2but how about this, lets start small, frickler can you take the Action Item to write the bug report then we can start floating it around?16:08
j^2please put in a good description of teh usecase too, so i can poke the berks devs about it16:08
fricklero.k., will do16:08
j^2iirc most/all of them work for chef now?16:08
j^2:)16:09
j^2thanks!16:09
j^2so your last topic was: Can we do some cleanup regarding CHEF-3694 being done? Most of the warnings seem to come from upstream cookbooks, but I think there is some room for improvement here on our side16:09
j^2i have idea what that CHEF-3694 is, can you tell us about it and i’ll look for the link?16:09
j^2#link https://tickets.opscode.com/browse/CHEF-369416:10
*** GonZo2K has quit IRC16:10
markvan#link http://scottwb.com/blog/2014/01/24/defeating-the-infamous-chef-3694-warning/16:10
fricklerit is about cloning resources16:10
j^2oh wow16:10
markvanThis is a great topic and it usually shows that a design needs some improvement.16:10
j^2i completely gloss over this now-a-days16:10
fricklerwhen I do a chef-client run, the log gets spilled with these warnings16:11
j^2yep16:11
markvanAnd yes, we have quite a few in our own cookbooks to deal with16:11
fricklerand I want to get rid of them, because they may hide interesting stuff16:11
markvan^ +116:11
j^2nice16:11
*** Viswanath has joined #openstack-chef16:11
j^2ok, so we can start the process of cleaning this up?16:12
*** GonZo2K has joined #openstack-chef16:12
j^2i’ll need to read that link that markvan just linked to, and i think we should all look to help out here16:12
j^2no?16:12
fricklerso I would say do a blueprint where we can collect the places where this happens16:12
j^2heh, don’t you mean a spec? :P16:13
* j^2 runs16:13
markvanhumm, yeah I guess this is really not a bug, but a poor design somewhere, so a spec/bp would be right path.16:13
j^2in this case yeah identifing this issue in a centralized location is a great idea16:13
markvanBut the spec/bp and be fairly generic16:14
fricklerand it will be tedious16:14
j^2i’m seeing a list of the effected cookbooks and the general line numbers of the effected areas16:14
*** Viswanath has quit IRC16:14
j^2and just update it when you see it16:14
j^2and someone takes ownership of fixing that mess?16:14
fricklerbut once we have some progress in our own cookbooks, it will be easier to nag the upstream cookbooks about it16:14
j^2frickler: agreede16:15
markvanI was think more high level then even that, just here's the issue with the links above, and maybe one example of it, and then cover the rest as we go.16:15
frickleryes, just have something consistent to reference from the patchsets16:15
markvanI think the network cookbook will be a challange for this type of change...16:16
j^2and have “partial fix” in the commit message so it hooks back to the issue?16:16
j^2so when we fix it it’s tracke?16:16
j^2tracked*16:16
markvanfor blueprint, I think you use "Implememets"16:16
markvan(wow can't speel or tpye today)16:17
j^2so maybe then we should have it as a bug?16:17
j^2it would be faster that way right?16:17
j^2it’s been a while since i’ve looked through the bugs to be honest16:17
j^2oh nice only 30 open :)16:18
j^2yeah the more i thnk about it a bp isn’t the correct answer here16:18
j^2it’s not a design, it’s a refactor16:18
j^2and you refactor to reduce bugs right?16:18
markvanYeah, we could go the Bug route and use the "Partial-Bug: #"16:18
j^2granted this is a very symantic conversation, as long as it gets done right?16:19
markvanI try to go thru bug list once a week to see what's new and what's getting way old16:19
j^2frickler: has this covered what you’d like to dicuss? I’d like to make sure that we’ve hit all the major points?16:20
j^210 mins btw :)16:20
frickleryep, fine for me and I'm also through with my collection now :)16:20
j^2awesome16:21
markvanI had one other small topic16:21
j^2#topic General Discussion16:21
j^2markvan: go ahead16:21
markvan#topic supermarket cookbooks16:21
j^2i’m a piseces, i do sometimes like long walks…oh you’re not asking that...16:21
j^2markvan: oooohhh mark you’re killing me16:21
j^2yeah we cant upload ours to the supermarked16:22
libsysguyoh?16:22
libsysguywhy not?16:22
j^2it requries ownership of the repo, and because stackforge does we cant16:22
j^2and there are someother little things16:22
j^2i’ve discussed this also with a couple people, including puppet people asking why we hadn’t and we just don’t have the ability16:23
markvanI have seen some pull requests that look valid, but are going no where fast.  And these are fixes that impact our cookbooks.  Ref: https://github.com/kennonkwok/rabbitmq/pull/15416:23
j^2oh ouch16:23
*** otter768 has joined #openstack-chef16:24
j^2oh shit, this is Kennon from chef?16:24
markvanWhat can be done to get those moved along....without the gerrit review process, seems like pull requests are very slow at times16:24
j^2i’ll ping him asap16:24
j^2no need, i’ll get on this16:24
markvanis there a "recommend" way to help move these along....besides having inside contacts?16:25
j^2just ping’d him :P16:25
j^2markvan: that’s a great question, and i think that’s the downfall of OS software, it’s about people as much as code16:25
j^2sometimes you just need to pester16:25
markvanwas hoping the supermarket would have some better oversight on these...16:26
j^2that’s a great point16:26
*** MrMonkey has joined #openstack-chef16:26
markvan(and since your chatting with him, I'll pile on: https://github.com/kennonkwok/rabbitmq/pull/148)16:27
j^2done16:27
j^2if he dosent get back to me today, i’ll start pestering :)16:27
j^2it’s still early in PST16:28
markvanSince we rely on these dependent cookbooks through out our openstack cookbooks, folks are seeing the great activity on our side, but become very frustrated on the supermarket side.16:28
j^2that’s a great point16:28
j^2it really is16:28
* markvan step down from soap box16:28
j^2i’m not sure on who/or what we can do about this16:28
*** otter768 has quit IRC16:28
j^2i can hook you up with teh supermarket guys and maybe they have an answer? i dunno16:29
markvanYeah, getting them some direct feedback would be great, thx.16:29
j^2cool, i’ll see what i can make happen16:29
markvanbtw, i think the switch from the internal opscode bug tracking to github issues has really slowed down some of the response times16:30
markvannot sure why, maybe just to many projects out there...16:30
j^2that’s interesting feedback, i actaully thought it was the opposite for my interactions16:31
markvanthat is for me, nice discussion today.16:31
openstackgerritFederico Gimenez Nieto proposed stackforge/cookbook-openstack-object-storage: Use cookbook_file resource for drive-audit.conf  https://review.openstack.org/13641016:31
j^2ok, any last topics taht want to be discussed?16:31
j^2going once?16:32
libsysguynone from me16:32
j^2going twice?16:32
fricklernot here either16:32
j^2Thanks everyone!16:32
j^2#endmeeting16:32
openstackMeeting ended Fri Nov 21 16:32:27 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_chef/2014/openstack_chef.2014-11-21-15.30.html16:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_chef/2014/openstack_chef.2014-11-21-15.30.txt16:32
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_chef/2014/openstack_chef.2014-11-21-15.30.log.html16:32
libsysguymarkvan: did you see my comment reply?16:32
libsysguyit apparently is still marked as draft?16:32
j^2I’ll send out the notes with the Hangout notes like i did early this week16:32
libsysguyso I didn't know if it went through16:33
markvanlibsysguy: which review again?16:33
libsysguyhttps://review.openstack.org/#/c/136128/116:33
fricklerlibsysguy: you need to click on "review" to publish the drafted comments16:35
libsysguyah,16:35
libsysguygerrit newb16:36
markvanyeah, did not see the reply yet.16:36
fricklerI'm just a week ahead, then ;)16:36
libsysguyit's weird coming from Jira/BitBucket to Launchpad/Gerrit16:36
markvanlibsysguy: did my questions about gating this make sense?16:37
*** emagana has quit IRC16:37
libsysguywell…no actually16:37
libsysguyI assumed the upstream gate16:37
*** judd7 has quit IRC16:37
libsysguybut I figured that was wrong16:37
*** emagana has joined #openstack-chef16:37
libsysguyand maybe you meant wrap it in a conditional16:37
fricklerha, markvan beat me to 136410 :'(16:38
markvanyeah, I was more thinking about the conditional around the resource itself.  Does this need to be done if that external_network_bridge_interface is nil?  or that's invalid config.16:39
markvanlibsysguy: if that's the case, you only need a spec test here, then this is ready to go16:40
libsysguyyeah about a spec test16:40
libsysguyI thought about how to test that the interface came up16:40
libsysguyand, maybe somebody else can point me in the right direction, but I can't for the life of me figure out how to test for success16:41
libsysguylike…ip link ls dev <interface> would give you more than up/down16:41
markvanhumm, I don't think that is necessary for a spec test.  It's job is to verify the basic logic, not the functional integration16:41
libsysguyah16:42
*** emagana has quit IRC16:42
markvanso basicaly you expect that resource to always get converged with that value, that's what the spec can verify.16:42
*** jaypipes is now known as leakypipes16:43
markvanlibsysguy: something like this: expect(chef_run).to add_route('10.0.0.10/32').with(device: 'eth0')16:45
markvansee: http://www.rubydoc.info/github/sethvargo/chefspec/ChefSpec/API/RouteMatchers for list of matchers16:45
libsysguyah nice16:46
libsysguyI was looking for that doc yesterday16:46
*** kbringard has joined #openstack-chef16:48
markvanyeah, it seems I'm always digging around in the ChefSpec source to figure out better ways to test things16:49
libsysguyheh just ran into the same problem with rake as frickler16:56
j^2markvan: merged16:59
*** galstrom is now known as galstrom_zzz17:00
markvanthx!17:00
j^2i’m a collab in it now too17:00
j^2i can take ownership of it if i want17:00
*** jmickle has joined #openstack-chef17:01
*** GonZo2K has quit IRC17:01
*** emagana has joined #openstack-chef17:05
j^2markvan: can you send me a link to the Berksfile link for this cookbook?17:06
j^2rabbitmq17:08
markvanIt's pulled in here: https://github.com/stackforge/cookbook-openstack-ops-messaging/blob/master/metadata.rb   not sure what your asking17:08
j^2perfect taht’s what i was looking for17:08
*** galstrom_zzz is now known as galstrom17:09
j^2btw, we can upload our cookbooks to supermarket if we want17:10
*** grothendieck has joined #openstack-chef17:10
libsysguyo rly?17:12
libsysguyj^2 you know some people on the inside of chef or something?17:13
libsysguy:P17:13
j^2ha!17:15
openstackgerritElliott Davis proposed stackforge/cookbook-openstack-network: Enable physical external interface  https://review.openstack.org/13612817:15
libsysguythats right…unit tests in baby!17:15
j^2i wish openstackgerrit would post bugs too17:16
libsysguywhat kind of bot is it?17:17
j^2it’s on the opentack sight17:17
j^2site17:17
j^2(in a call atm) :P17:17
libsysguymust be its weekly Turing test17:18
markvanj^2: Need to understand what being in supermarket would mean?  no more gerrit reviews?   Would like to stay somewhat consistent with base openstack with stackforge.17:21
j^2btw, i’ve updated the readme for the testing framework if yall would take a look17:21
markvanj^2: how about the title?  Maybe "Testing Framework for OpenStack and Chef"    it's implemented with a cluster and chef-provisiioning, but those are details17:22
*** GonZo2K has joined #openstack-chef17:23
j^2sorry i’m back, just got off the phone17:28
j^2ah, ok markvan so yeah the supermarket, that would give us more exposure to the community17:29
j^2we’d still leverage our openstack process, but it would just be part of another index if you will17:29
markvanyou don't feel exposed enough already ;)17:29
j^2i suggest we’d only do like stable/icehouse and stable/juno not master17:29
markvanif we could keep the same processes, then yeah, sounds like little to no impact, but has gains in community.17:30
j^2yep, we’d ideally get more involvement17:30
j^2and that title, good, i’ll update it17:30
markvanhumm, so your thinking just the stable branches, with little dev on them.  but keep master in stackforge?   not sure I understand that17:32
j^2zoom?17:32
j^2http://bit.ly/jj-zoom17:32
os-chef-bothttp://bit.ly/jj-zoom is https://chef.zoom.us/j/599676742117:32
j^2libsysguy: if you want to join you’re more than welcome17:32
libsysguyactually I have to do an interview in 1517:34
j^2xx17:34
j^2kk17:34
*** GonZo2K has quit IRC17:34
libsysguybut fwiw +1 on supermarket17:34
j^2markvan: i think i lost you17:36
*** GonZo2K has joined #openstack-chef17:48
*** tmichael has joined #openstack-chef17:49
*** libsysguy has quit IRC17:51
*** libsysguy has joined #openstack-chef17:51
*** harlowja_away is now known as harlowja17:52
*** libsysguy has quit IRC17:52
*** jmickle has quit IRC17:52
*** kbringard has quit IRC17:53
*** GonZo2K has quit IRC17:55
*** libsysguy has joined #openstack-chef17:55
*** GonZo2K has joined #openstack-chef17:56
*** GonZo2K has quit IRC18:02
*** emagana has quit IRC18:02
*** emagana has joined #openstack-chef18:03
*** GonZo2K has joined #openstack-chef18:03
*** jmickle has joined #openstack-chef18:05
*** GonZo2K has quit IRC18:06
*** emagana has quit IRC18:07
*** emagana has joined #openstack-chef18:08
openstackgerritMark Vanderwiel proposed stackforge/cookbook-openstack-compute: Make compute dbsync command timeout to be an optional parameter  https://review.openstack.org/13644418:19
*** emagana has quit IRC18:22
*** emagana has joined #openstack-chef18:23
*** otter768 has joined #openstack-chef18:25
*** GonZo2K has joined #openstack-chef18:25
*** emagana has quit IRC18:27
*** GonZo2K has quit IRC18:27
*** libsysguy has quit IRC18:28
openstackgerritMark Vanderwiel proposed stackforge/cookbook-openstack-network: Make network dbsync command timeout to be an optional parameter  https://review.openstack.org/13644918:29
*** otter768 has quit IRC18:29
*** emagana has joined #openstack-chef18:30
*** emagana has quit IRC18:42
*** emagana has joined #openstack-chef18:43
*** GonZo2K has joined #openstack-chef18:45
*** emagana has quit IRC18:47
*** libsysguy has joined #openstack-chef18:52
*** galstrom is now known as galstrom_zzz18:56
*** emagana has joined #openstack-chef18:56
*** libsysguy has quit IRC18:59
*** GonZo2K has quit IRC18:59
*** libsysguy has joined #openstack-chef18:59
*** GonZo2K has joined #openstack-chef19:01
*** emagana has quit IRC19:02
*** emagana has joined #openstack-chef19:02
*** GonZo2K has quit IRC19:03
*** tmichael has quit IRC19:18
*** tmichael has joined #openstack-chef19:19
*** otter768 has joined #openstack-chef19:19
*** emagana has quit IRC19:19
*** emagana has joined #openstack-chef19:19
*** emagana has quit IRC19:24
*** emagana has joined #openstack-chef19:26
*** galstrom_zzz is now known as galstrom19:39
*** markvan has quit IRC19:47
*** markvan_ has joined #openstack-chef19:47
openstackgerritMerged stackforge/openstack-chef-repo: Replaced references to Opscode  https://review.openstack.org/13605019:49
*** emagana has quit IRC20:06
*** emagana has joined #openstack-chef20:06
openstackgerritMark Vanderwiel proposed stackforge/cookbook-openstack-identity: Fix incorrect default for token expiration  https://review.openstack.org/13647820:08
*** junhongl has quit IRC20:08
*** tryggvil has quit IRC20:10
*** emagana has quit IRC20:11
*** junhongl has joined #openstack-chef20:11
*** emagana has joined #openstack-chef20:15
j^2anyone around?20:22
j^2can i get a +1 on this? https://github.com/kennonkwok/rabbitmq/pull/16220:23
*** emagana has quit IRC20:24
*** neelashah has quit IRC20:24
*** emagana has joined #openstack-chef20:24
libsysguydone20:27
j^2thanks :)20:28
libsysguynot that my +1 means anything20:29
j^2i just wanted to make sure someone else saw the change i wanted to make20:29
libsysguyyeah it looks sane20:29
markvan_j^2: humm, the gemfile still shows: gem 'rubocop', '~> 0.18'   show this is for 0.23?20:30
j^2i’m thinking i should update that too20:30
j^2but the CameCase issue you can’t run rake without it20:30
j^2one step at a time ;)20:30
markvan_humm, bumpinhg rubocop, could bring in many other changes20:30
j^2sounds like a “good?” idea :)20:32
libsysguymerged20:35
j^2:D20:35
j^2so when i run rspec spec it should run chefspec….but it’s not20:35
j^2that’s…odd20:35
*** emagana has quit IRC20:46
j^2holy shit this rabbitmq cookbook is out-of-date20:47
j^2i think i may have made a mistake picking this up20:47
j^2ok, updating foodcritic, only one offence is there now20:50
j^2ok, i’m getting someplace20:50
j^2now to figure out getting chefspec to play nice20:50
*** libsysguy has quit IRC21:00
*** emagana has joined #openstack-chef21:00
*** tryggvil has joined #openstack-chef21:11
*** emagana has quit IRC21:14
*** emagana has joined #openstack-chef21:14
*** emagana has quit IRC21:19
j^2markvan_: i own the rabbitmq cookbook now21:38
-openstackstatus- NOTICE: gating is going offline while we deal with a broken block device, eta unknown21:43
*** ChanServ changes topic to "gating is going offline while we deal with a broken block device, eta unknown"21:43
*** petercd has left #openstack-chef21:44
*** emagana has joined #openstack-chef21:57
*** emagana has quit IRC22:02
*** tryggvil has quit IRC22:07
openstackgerritJJ Asghar proposed stackforge/cookbook-openstack-common: Ensure apt runs before packages are updated.  https://review.openstack.org/12485422:07
*** emagana has joined #openstack-chef22:07
*** galstrom is now known as galstrom_zzz22:07
*** emagana has quit IRC22:18
*** emagana has joined #openstack-chef22:19
*** galstrom_zzz is now known as galstrom22:20
*** emagana has quit IRC22:24
*** tmichael has quit IRC22:26
*** tmichael has joined #openstack-chef22:35
*** rtheis has quit IRC22:55
*** emagana has joined #openstack-chef22:57
*** ncerny has quit IRC22:57
*** emagana has quit IRC23:03
*** kbringard has joined #openstack-chef23:03
*** emagana has joined #openstack-chef23:03
*** emagana_ has joined #openstack-chef23:04
*** emagana has quit IRC23:04
*** tryggvil has joined #openstack-chef23:06
*** galstrom is now known as galstrom_zzz23:08
*** jmickle has quit IRC23:14
*** malfaitc has quit IRC23:17
*** tmichael has quit IRC23:22
*** kbringard has quit IRC23:30
*** tmichael has joined #openstack-chef23:34

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