Thursday, 2014-12-04

« Wednesday, 2014-12-03 Index Friday, 2014-12-05 »
libsysguyw00t ^^00:01
j^2:D00:01
libsysguyfinally I can kill off my fork00:01
*** erictian has quit IRC00:01
*** emagana has quit IRC00:10
*** malfaitc1 has quit IRC00:10
*** emagana has joined #openstack-chef00:11
*** os-chef-bot has quit IRC00:14
*** os-chef-bot has joined #openstack-chef00:14
*** emagana has quit IRC00:15
*** emagana has joined #openstack-chef00:18
*** otter768 has joined #openstack-chef00:31
libsysguyj^2 I don't know if you can do it with chef-provisioning00:31
j^2ah does it need to be a vagrant thing?00:32
libsysguyyeah00:32
libsysguyI am using chef-dk and it ships with 11.18 as the client00:32
j^2https://github.com/jjasghar/chef-openstack-testing-stack/blob/master/aio-neutron.rb#L3-L1700:32
j^2that’s a vagrant file00:32
libsysguyI am pretty sure if you update the client locally, it would use that one00:32
libsysguyhmm00:33
libsysguylet me give that a try without it bombing out00:33
j^2kk00:33
*** zsais has quit IRC00:34
libsysguydo you use bundle with chef-dk?00:36
j^2not exactly00:36
libsysguyor do you just roll with it locally ?00:36
*** otter768 has quit IRC00:36
j^2on me?00:36
j^2or chefdk in general?00:36
libsysguywell I was just running into berks issues with this repo and chef-dk00:37
libsysguyand I didn't know if you used it00:37
j^2ahh00:37
libsysguyto manage gems and such00:37
j^2yeah with chef-dk you’ll need to use chef exec blah00:37
j^2so it’s built in, cheeseplus testing chefdk for me recently00:37
cheeseplusso far it all checks out under ChefDK 0.3.500:38
libsysguyhmm, maybe I am just missing that gem00:38
libsysguyyup00:38
libsysguybundle didn't install berkshelf00:38
libsysguyor not00:39
libsysguywtf00:39
libsysguyanyway, I'll figure it out00:39
*** kobtea has joined #openstack-chef00:45
*** malfaitc has joined #openstack-chef00:46
*** kobtea has quit IRC00:50
*** dyjau has joined #openstack-chef00:56
*** erictian has joined #openstack-chef00:57
*** erictian has quit IRC01:01
dyjauhello, I have a chef-server install on a centos machine. Everything is working as expected except that I cannot access the chef-server Web interface from outside. I try to find a way to configure nginx but I keep failing. Is some one can help me with this problem ?01:03
dyjau"telnet mychefserver.local 4000" works on the centos machine where the chef-server is installed but failed from my machine01:12
dyjauI can ping mychefserver.local from my machine01:12
*** zhiwei has joined #openstack-chef01:16
dyjauI have just created a stackoverflow question for this issue http://stackoverflow.com/questions/27284738/cannot-access-chef-server-web-interface-no-route-to-host01:34
*** malfaitc has left #openstack-chef01:37
*** erictian has joined #openstack-chef01:46
*** nosnos has joined #openstack-chef01:52
*** neelashah has joined #openstack-chef02:04
*** neelashah has quit IRC02:04
*** neelashah has joined #openstack-chef02:07
*** neelashah has quit IRC02:11
*** galstrom_zzz is now known as galstrom02:12
*** dyjau has quit IRC02:18
*** libsysguy has quit IRC02:22
*** otter768 has joined #openstack-chef02:32
*** emagana has quit IRC02:36
*** otter768 has quit IRC02:37
j^2Dyjau what version of chef server? 4000 was chef 10 right?02:48
*** erictian has quit IRC02:59
*** nosnos has quit IRC03:23
*** erictian has joined #openstack-chef03:28
*** erictian_ has joined #openstack-chef03:31
*** erictian has quit IRC03:31
*** galstrom is now known as galstrom_zzz03:35
*** erictian_ has quit IRC03:41
*** erictian has joined #openstack-chef03:42
*** erictian has quit IRC03:46
*** nosnos has joined #openstack-chef04:16
*** MrMonkey has quit IRC04:18
*** GonZo2K has quit IRC04:21
*** otter768 has joined #openstack-chef04:33
*** galstrom_zzz is now known as galstrom04:34
*** otter768 has quit IRC04:38
*** malfaitc has joined #openstack-chef04:45
*** erictian has joined #openstack-chef04:51
*** tmichael has quit IRC04:53
*** swartwulf has quit IRC04:53
*** erictian has quit IRC04:56
*** swartwulf has joined #openstack-chef05:00
*** zsais has joined #openstack-chef05:26
*** galstrom is now known as galstrom_zzz05:29
*** zsais has quit IRC05:31
*** erictian has joined #openstack-chef05:33
*** malfaitc has left #openstack-chef05:36
*** erictian_ has joined #openstack-chef05:37
*** erictian has quit IRC05:37
*** kobtea has joined #openstack-chef06:11
*** kobtea has quit IRC06:16
*** harlowja_ is now known as harlowja_away06:19
*** otter768 has joined #openstack-chef06:34
*** otter768 has quit IRC06:39
*** k4n0 has joined #openstack-chef06:54
*** wenchma has joined #openstack-chef06:58
*** opscode-logger has quit IRC07:00
*** opscode-logger has joined #openstack-chef07:00
*** erictian_ has quit IRC07:29
*** nkrinner has joined #openstack-chef07:29
*** pradipta_away is now known as pradipta08:05
*** stannie has joined #openstack-chef08:28
*** otter768 has joined #openstack-chef08:35
*** otter768 has quit IRC08:40
*** pradipta is now known as pradipta_away08:46
*** PierreRambaud has quit IRC09:20
*** PierreRambaud has joined #openstack-chef09:20
*** lizk_ has joined #openstack-chef09:36
lizk_Can any +2 member give a review on https://review.openstack.org/#/c/136089/ ? or if it's belong to this channel, pls tell me09:37
lizk_if not09:37
*** kobtea has joined #openstack-chef09:49
lizk_Can any +2 member give a review on https://review.openstack.org/#/c/136089/ ? if I'm in wrong channel, pls tell me09:53
*** kobtea has quit IRC09:54
*** lizk_ has quit IRC10:02
*** zhiwei has quit IRC10:07
*** aspiers has joined #openstack-chef10:11
*** fayablazer has joined #openstack-chef10:13
*** iartarisi has joined #openstack-chef10:17
*** lizk has joined #openstack-chef10:24
*** lizk has left #openstack-chef10:25
*** lizk has joined #openstack-chef10:25
*** lizk has left #openstack-chef10:25
*** otter768 has joined #openstack-chef10:36
*** otter768 has quit IRC10:40
*** stannie has quit IRC10:50
*** fayablazer has quit IRC11:04
*** fayablazer has joined #openstack-chef11:23
*** kitch_ has joined #openstack-chef11:55
*** rtheis has joined #openstack-chef12:12
*** otter768 has joined #openstack-chef12:37
*** otter768 has quit IRC12:41
*** libsysguy has joined #openstack-chef12:50
libsysguyos-chef-bot: !meeting12:50
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-openstack and our IRC status meeting/office hours are at 15:30 GMT 10:30 EST 07:30 PST on Thursdays we try to have as many core members here so we can discuss topics or issues users are having12:50
*** libsysguy has quit IRC12:58
*** libsysguy has joined #openstack-chef13:00
*** galstrom_zzz is now known as galstrom13:18
*** kitch_ has quit IRC13:22
*** kitch_ has joined #openstack-chef13:22
*** kobtea has joined #openstack-chef13:27
*** nosnos has quit IRC13:27
*** neelashah has joined #openstack-chef13:27
*** kobtea has quit IRC13:32
*** GonZo2K has joined #openstack-chef13:52
*** galstrom is now known as galstrom_zzz14:01
*** galstrom_zzz is now known as galstrom14:05
*** galstrom is now known as galstrom_zzz14:23
*** ncerny has joined #openstack-chef14:26
*** galstrom_zzz is now known as galstrom14:30
*** k4n0 has quit IRC14:33
*** otter768 has joined #openstack-chef14:38
*** otter768 has quit IRC14:42
*** neelashah has quit IRC14:42
*** malfaitc has joined #openstack-chef14:48
*** galstrom is now known as galstrom_zzz14:48
*** GonZo2K has quit IRC14:57
*** neelashah has joined #openstack-chef14:57
*** kobtea has joined #openstack-chef15:00
*** kbringard has joined #openstack-chef15:20
j^2#meeting openstack-chef15:30
j^2#startmeeting openstack-chef15:30
openstackMeeting started Thu Dec  4 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
libsysguyhey hey15:31
markvanHowdy15:31
openstackgerritJan Klare proposed stackforge/cookbook-openstack-network: Handle nil and empty string for cafile  https://review.openstack.org/13608915:31
j^2I only have one thing i’d like to specificly talk about, is there anything you’d like to discuss? (open to everyone)15:32
libsysguyyeah, I'd like to talk about ssl in the dashboard cookbook15:32
j^2cool, any other topics?15:32
jklarehey15:32
j^2going once….15:33
jklareis it allowed to +2 a change when i rebased it?15:33
j^2the rule is “never +2” anything you have commited/changed or something like that15:34
j^2in that spirt no i don’t think so15:34
j^2ok, cool15:34
j^2#topic ssl in the dashboard cookbook15:35
libsysguyoh right to it then15:35
j^2libsysguy: the floor is yours15:35
libsysguyawesome.  Well I have been spending some time with the apache2 cookbook recently.  I noticed that we handle ssl in a strange way in that cookbook (assuming some paths, file names, etc)15:36
libsysguyI was wondering if there would be a problem re-implementing ssl with something like: https://supermarket.chef.io/cookbooks/ssl_certificate15:36
libsysguywe seem to be doing a lot of logic that seems to be implemented (more completely) in that cookbook15:37
j^2leveraging it as a dependancy?15:37
libsysguyyes15:37
j^2is there an LWRP in there? I haven’t looked15:37
libsysguyyes, ssl_certificate15:38
j^2this sounds like a blueprint ;)15:38
libsysguydefinitely15:38
libsysguyI was just unclear on what the policy was for deps, etc15:38
j^2leveraging an LWRP to make our life easier seems like a good idea in general15:38
libsysguybut I'd be happy to get in a spec15:39
markvanLooks like a good way to go.15:39
j^2traditionally? I have no idea, but i’m in the camp that this seems like a great idea15:39
markvanNote that we have SSL in many places, like for MQ, and potentially each service15:39
libsysguyI'l definitely like to leverage this everywhere15:40
markvanso, starting with something like dashboard sounds reasonable, and then we can expand from that integration kionledge15:40
libsysguys/I'l/I'd/15:40
j^2markvan: starting with the dashboard then we could move out to the rest of the cookbooks right?15:40
markvanyup15:40
j^2wow, it sounds like we are in agreement we should make this happen :P15:40
libsysguyexcellent15:41
markvanThe next obvious question:  is this a big enough change that we might consider it for kilo and not in juno?15:41
libsysguyah yes, I think we are close enough to the cut that it should get pushed to Kilo15:41
jklare+115:41
markvanyes, I was thinking kilo here as well15:42
j^2markvan: kilo15:42
j^2we can do a vote :P15:42
libsysguydo eet15:42
j^2libsysguy: can you take the action item to make the blueprint? to start mapping this out?15:42
libsysguyfor sure15:42
libsysguyaction on all cookbooks or just the dashboard?15:43
j^2#action libsysguy will start a blueprint for the inital mapping of gettting the ssl_cert cookbook in dashboard15:43
markvanimo the bp/spec can cover dashboard in detail and maybe just point out that it can be done in the other cookbooks like for MQ.15:43
j^2markvan: great idea15:44
j^2:)15:45
libsysguyit's added to my notebook as a todo :)15:45
j^2cool, next topic?15:46
markvanhow about that infra change?15:46
j^2#topic infra change15:46
j^2markvan: floor is yours15:47
markvanhttps://review.openstack.org/#/c/137134/15:47
markvanLooks like Sean has stepped in here...and that usually means we need to change to make any more progress.15:47
j^2:-/15:48
markvanusing "experiemental"   in job name is not going to fly, as it's the queue name and jobs can be placed in any queue.15:48
markvanso if we call this just 'gate' job  is that good enough for now?15:49
j^2i’m looking for the inline comments15:49
libsysguydidn't the name have some significance as to how it was processed?15:50
j^2The experimental in the name is intentional (also not syntactically needed) because as soon as this works smoothly we will just add another gate-{name}-chef-rake job (and delete the other three [lint,style,unit]) so we can run the gate job on the testes distros and use the experimental for the new distro releases.15:50
jklare^^15:50
jklarei guess we can change the name if it hurts somebody15:50
j^2i don’t really have an opinion here honestly15:50
j^2any other thoughts?15:52
libsysguynone from me - The Infra Newb15:52
j^2maybe jklare can you add a note explaining (again) why you chose experimental?15:53
j^2maybe that’ll suffice15:53
jklarei am currently talking to sdague15:53
j^2awesome15:54
jklarei will figure out if we have to rename it or not15:54
jklare:)15:54
markvanhumm, I think we should go with another name and stay away from experiemental.   maybe draft-gate-rake....  and then the gate-rake  ?15:54
j^2oh, i like that15:55
j^2draft is a great naming scheme15:55
j^2cool, anyother thoughts on this?15:56
j^2#topic client-cookbook15:57
j^2this is the only thing i wanted to bring up :)15:57
j^2we need another +2 from a core on it15:58
j^2sorry15:58
j^2+1 on the workflow15:58
j^2https://review.openstack.org/#/c/126365/15:58
j^2so we can have the begining of our client-cookook15:58
j^2i also started on the neutron portion, and i wanted to get it on peoples radar15:59
j^2neutron: https://review.openstack.org/#/c/138845/15:59
j^2it semes i’ve never really wrapped my head around creating LWRPs, so this is a great learning experience for me, and anyone else who wants to learn them15:59
*** iartaris` has joined #openstack-chef15:59
j^2challenge is…I don’t know if i’m going off the rails here16:00
j^2can i get some eyes on it to see if it’s at all in line on what it needs to be?16:00
j^2thoughts comments?16:00
markvanYeah for neutron lwrp, I thought Fog handled this:  https://github.com/fog/fog/blob/master/lib/fog/openstack/network.rb  and you just need some simple wrappers here.16:00
*** iartarisi has quit IRC16:01
j^2markvan: yep that seems like the correct path16:01
*** kbringard has quit IRC16:01
j^2i was starting with just shelling out to neutron, then going to try to create the wrappers16:02
libsysguyso the client is just a lwrp wrapping fog?16:02
j^2that’s the gist yeah16:02
j^2that whole cookbook’ll be lwrps for things you want to do with your openstack cluster leveraging fog basicly16:02
markvannot sure if there's a lighter way to use Fog directly16:02
libsysguyyeah that is my thought16:03
libsysguybut I am generally against wrappers :p16:03
j^2yeah same here, but this gives resources to do “normal” openstack configurations16:03
j^2make a network, make a vm, upload a object etc etc16:04
markvanI just don't know if there's a way to avoid the basic lwrp definition16:04
j^2and as mattray mentioned this is gains for two camps, users and builders of openstack16:04
markvanso the lwrp "wrapper" should be pretty thin and leave the logic in the Fog library16:04
j^2markvan: yep, basicly we tie the attributes to the options that the fog object would want16:05
j^2then we converge :)16:05
j^2example: https://review.openstack.org/#/c/138845/1/resources/neutron_network.rb16:05
j^2the network creation only needs a name for the network, but the shared and external options are flipable16:06
markvanI guess I don't mind the basic idea, but really want to keep the logic and guts in Fog such that it can change under us without have to fix lwrp all the time16:06
j^2markvan: agreed, leverage fog to do the heavy lifting, i’m totally with you on this16:07
markvanhumm, one thing I noticed was the need for passing in all the user creds/url stuff, is there a way to push that into a common lwrp that can be used within this one?  such that each wrapp focuses on just the arrts they need?16:07
j^2the challange as stated before though, is i’m not great at writing LWRPs, so any coding suggestions, eyes, would be helpful16:08
j^2markvan: totally, i’me just trying to get the framework though16:08
j^2markvan: i feel like that’s bikeshedding it ATM16:08
j^2i just want something that works16:08
j^2red green refactor ftw16:08
j^2anyone have any suggestions on LWRPs that leverage a gem as the backend like fog?16:09
j^2i havent done the research, that was something taht popped in my head this morning16:10
libsysguynothing from me16:10
j^2there has to be something out there16:11
j^2i’ll do some research and come back16:11
j^2this is a dependancy to the testing-framework as i mentioned in the hangout, so i’m focusing hard on it16:11
markvanyeah, should be someting out there.  also would like to understand if lwrp's can be subclassed, so you could put all the cred stuff up a level and leverage that by all the component specific ones16:12
jklareOT: so i talked to sdague and clarkb and they suggested to name the job gate-{}-chef-rake, place it in the experimental queue and test the rake change on precise first. If we wanna also test on trusty later, we should create something like trusty-{}-chef-rake and place it in the experimental again.16:12
j^2markvan: yeah theres no reason why you couldn’t do that, i just havent yet16:13
j^2jklare: interesting16:13
markvanjklare: interesting putting platform in the name16:14
*** MrMonkey has joined #openstack-chef16:14
j^2cool, last topic, our catch all16:15
j^2#topic General Discussion16:15
j^215 mins, then i’ll bring this to a close, floor is open16:16
*** mattray has joined #openstack-chef16:16
*** ChanServ sets mode: +o mattray16:16
*** Nakato_ has joined #openstack-chef16:16
markvanjklare: I guess I really prefer not to put trusty in the name, but maybe that's a discussion for later.   We can get the initial rake get in and working on precise, and then maybe clone that as the precise-gate-{}-chef-rake16:17
markvanso we keep the generic for working with latest, like trusty or whatever?16:17
j^2i think that’s a good idea16:18
jklarei was thinking about reducing my change to basically adding a gate-{}-chef-rake job which runs also on precise and in the experimental queue16:18
*** Nakato has quit IRC16:18
markvanor do even want to play with precise here?  goal is to get to trusty, why not just start there in first place?16:19
j^2generic names are our generic tests16:19
jklareafter we get that in and running we can push it to trusty16:19
jklareand discuss how to name it :)16:19
j^2os-chef-bot: ping16:20
os-chef-botPONG16:20
markvanhumm, but do we need to waste the time getting precise working if it's not going to be used?    we want trusty for stable juno branch right?16:20
j^2generic names are our generic tests16:20
j^2i like that idea16:20
jklarei think we should not go the other way around and add all the jobs to trusty in experimental queue, since thats a lot of code which we need to delete later16:20
*** galstrom_zzz is now known as galstrom16:21
jklarei am not sure if my initial patch is a good idea, since it will basically try to address 2 different issues at once16:21
jklareand we know how agile one can work in the infra project..16:21
j^2heh16:21
markvanjklare: I don't follow, why need to delete later.  we want trusty support as the goal, precise is just what were using now to make basic merges work.16:22
jklaremarkvan: so we wanna solve 2 things: using rake; testing on trusty16:22
j^2jklare: and that's feeling like two patches16:22
markvanyup, and have that as default for juno16:23
jklaremarkvan: if we do both at once we might run into more errors than we want to have and are able to solve in juno16:23
jklaremarkvan: if we try to push for trusty first, then we need to add 3 additional jobs (since we dont have rake) for each cookbook16:24
markvanyeah, that's a possibility, but I think it's worth trying that route first.16:24
*** libsysguy has quit IRC16:24
jklareso you would go for just renaming the job and sticking to solving 2 things at once?16:24
*** libsysguy has joined #openstack-chef16:25
markvanyup, that was my idea here.  trusty should not be that bad to get working with rake.16:25
j^25 mins16:25
*** kgerman has joined #openstack-chef16:26
*** iartaris` is now known as iartarisi16:27
j^2chaching! guys16:27
j^2#link https://github.com/stevendanna/cookbook-r/blob/master/providers/package.rb16:27
j^2^^^ a "simple" example for the LWRP16:27
j^2i'll be updating my code here soon16:27
*** mikedillion has joined #openstack-chef16:28
jklaremarkvan: ok, but i will remind you on this 'should not be that bad' ;)16:28
jklareany other thoughts?16:28
markvanlet the fireworks begin...16:28
j^2:)16:29
j^2unless there is anything else anyone would like to bring up, i'd like to welcome libsysguy as a core reviewer again; and thanks for everyones time16:29
j^2#endmeeting16:30
openstackMeeting ended Thu Dec  4 16:30:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_chef/2014/openstack_chef.2014-12-04-15.30.html16:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_chef/2014/openstack_chef.2014-12-04-15.30.txt16:30
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_chef/2014/openstack_chef.2014-12-04-15.30.log.html16:30
jklare^^ cool16:30
j^2:)16:30
j^2irccloud too a shit all over itself in the middle of the meeting16:31
j^2:(16:31
j^2maybe it’s working now?16:31
j^2os-chef-bot: ping16:31
os-chef-botPONG16:31
j^2yay!16:31
j^2i’ll send out the notes with monday’s notes too16:32
j^2next monday that is16:33
markvanj^2: I'll miss Monday...16:36
j^2ok :)16:36
j^2thanks for the heads up16:36
*** otter768 has joined #openstack-chef16:38
*** otter768 has quit IRC16:43
*** MrMonkey has quit IRC16:45
*** kbringard has joined #openstack-chef16:45
*** MrMonkey has joined #openstack-chef16:46
*** kobtea has quit IRC16:47
*** iartarisi has quit IRC16:49
*** nkrinner has quit IRC16:51
openstackgerritMerged stackforge/cookbook-openstack-client: Initial Commit of the cookbook-openstack-client  https://review.openstack.org/12636516:52
*** mattray1 has joined #openstack-chef16:59
*** ncerny_ has joined #openstack-chef16:59
*** kobtea has joined #openstack-chef17:03
*** kobtea has quit IRC17:03
j^2libsysguy: got time to pair today?17:09
libsysguyany chance I can push till tomorrow? I'd really like to get this OVS issue resolved17:10
j^2sure that’s fine. it’l around OVS too :P17:10
j^2i just need someone who knows this stuff at some level also so we can debug this damn thing17:11
libsysguyheh yeah I think I can help at *some* level17:11
j^2that’s better than me reading things that i have no idea are remotely close to fixing this17:12
libsysguyheh (truestory)17:12
*** mattray has quit IRC17:12
*** ncerny has quit IRC17:12
j^2AgentNotFoundByTypeHost: Agent with agent_type=L3 agent and host=controller could not be found —> i think that’s the genisus error17:13
libsysguyso neutron agent-list gives you a :-(17:14
j^2nope17:15
j^2it’s :-)17:15
j^2and that’s the rub17:15
libsysguywth17:15
j^2exactly17:15
libsysguyI think they just hard coded the :-)17:15
j^2ha!17:15
*** fayablazer has quit IRC17:16
*** MrMonkey has quit IRC17:19
openstackgerritMark Vanderwiel proposed stackforge/cookbook-ceph: Add rake support  https://review.openstack.org/13912117:20
j^2awwwwww shit17:21
j^2libsysguy: https://gist.github.com/jjasghar/022c56a09ea9ca0b43a917:21
libsysguyumm17:22
libsysguywhat OS is that?17:22
j^2centos17:22
libsysguyactually17:22
libsysguythat one is totally not mine17:22
j^2https://www.irccloud.com/pastebin/bQO1qzxd17:23
j^2that’s the command it’s trying to run17:23
markvanjklare: Looks like I spoke to soon, fireworks were a dud....added comments to the infra patch accordingly, thx.17:23
markvanj^2: on that infra patch for rake tests.....they will not run on trusty until Berkshelf and/or ChefDK is support on trusty...any timeframe for that you would like to share?17:24
libsysguyj^2: that is in core neutron right?17:25
libsysguynothing to do with the cookbook17:25
libsysguyunless netns is a package you can install in centos17:25
j^2libsysguy: i dont think netns is a packgae17:27
j^2and yeah it’s core17:27
*** MrMonkey has joined #openstack-chef17:27
libsysguywell ip netns would normally give you all the named tables17:27
*** MrMonkey has quit IRC17:27
*** MrMonkey has joined #openstack-chef17:28
j^2interesting17:37
j^2so that means i’m running an old version of ip maybe?17:37
j^2wow17:38
j^2that mean jack to me17:39
j^2ip utility, iproute2-ss09122617:39
j^2ooohhh17:39
j^2it’s called ss17:40
*** mikedillion has quit IRC17:40
j^2lovely17:40
j^2http://howproblemsolution.com/fix/linux-update-ss-utility-on-centos.12461/17:40
j^2<— venting17:40
libsysguyoh centos17:41
libsysguythis…this is why we can't have nice things17:41
j^2oh!17:41
j^2i think i found it17:41
j^2iproute-2.6.32-33.el6_6.x86_6417:41
j^2grrrr17:42
markvanjklare: I found this that might help with getting rake gates on trusty, https://github.com/berkshelf/berkshelf/issues/1138  near the bottom for workaround.  but it's still very hackish18:01
markvanwe really need chefdk/berkshelf on trusty to make this happen cleanly18:01
*** harlowja_away is now known as harlowja_18:10
*** emagana has joined #openstack-chef18:13
*** emagana has quit IRC18:14
*** shakamunyi has joined #openstack-chef18:18
*** kbringard has quit IRC18:26
*** mikedillion has joined #openstack-chef18:33
*** otter768 has joined #openstack-chef18:39
*** otter768 has quit IRC18:44
*** openstackgerrit has quit IRC18:50
*** openstackgerrit has joined #openstack-chef18:50
*** MrMonkey has quit IRC18:57
*** MrMonkey has joined #openstack-chef19:06
*** GonZo2K has joined #openstack-chef19:13
j^2libsysguy: did you ever figure out how to update the chef-client12 in vagrant?19:37
*** emagana has joined #openstack-chef19:43
libsysguyyou have to update it locally on whatever you're running provisioning on19:46
*** MrMonkey has quit IRC19:50
j^2oh, so update the Gemfile then?19:50
*** MrMonkey has joined #openstack-chef19:51
j^2i hate days with my backup headphones :(19:51
*** emagana has quit IRC19:51
*** emagana has joined #openstack-chef19:52
libsysguyyeah the headphone on my bose headset went out19:53
libsysguyso I am monophoning it until the new set gets here19:53
j^2my back up ear buds one size is perfect for my ear, the other is a tad bit big and it feels like it’ll fall out constanly19:54
j^2drives me up the wall19:54
j^2my good set at home fits perfectly, i completely forgot to put it in my bag this morning :(19:54
j^2first world problems19:54
libsysguyand tbh j^2 I'm not sure how to tell the client to update.  I just ran the shell script on my mac and set the version to 1219:55
j^2hmm19:55
j^2ok19:55
*** emagana has quit IRC19:56
j^2yay i’m about to get commit to neutron!19:58
j^2https://review.openstack.org/#/c/137920/19:58
libsysguyw00t readme changes19:59
j^2hey man, that’s how you help out opensource, however you can!20:00
j^2:P20:00
*** openstackgerrit has quit IRC20:04
*** openstackgerrit has joined #openstack-chef20:04
j^2and that makes me a core commiter to opentsack too :P20:05
libsysguydamn, now I need to get on that20:06
j^2ha!20:06
*** emagana has joined #openstack-chef20:07
openstackgerritJJ Asghar proposed stackforge/cookbook-openstack-network: Update iproute because Centos 6.5 hates us  https://review.openstack.org/13917520:19
j^2libsysguy: ^^^20:19
j^2and markvan ^^^20:19
libsysguylol20:20
j^2i should have put i Bugreport in, but that just seems like overhead for this fix20:20
markvanlooking...20:20
libsysguyalso looking20:20
j^2yeah it’s gross20:20
j^2but it’s a legit problem :)20:20
libsysguycan I beat markvan to it and say "changelog"20:20
j^2hahahahah20:20
j^2*facepalm*20:21
j^2that’s why i didnt create the icehouse patch yet20:21
markvank then I'll pile on with a spec request...20:21
j^2i learned my lesson last time20:21
j^2i hate and love you both20:21
markvanhumm netns...that's name space support right.  I thought that was not part of 6.5  only a special rdo repo version was available (kernel patches)20:22
markvanis that what your going after here?20:22
j^2zoom?20:22
j^2http://bit.ly/jj-zoom20:23
os-chef-bothttp://bit.ly/jj-zoom is https://chef.zoom.us/j/599676742120:23
j^2libsysguy: if you want to too20:23
j^2i can show you what’s going on20:23
j^2i can hear you libsysguy20:24
j^2you can’t hear me?20:24
*** kbringard has joined #openstack-chef20:26
j^2https://github.com/stackforge/cookbook-openstack-network/blob/master/attributes/default.rb#L104720:29
*** shakamunyi has quit IRC20:30
*** shakamunyi has joined #openstack-chef20:32
j^2https://github.com/stackforge/cookbook-openstack-network/blob/master/attributes/default.rb#L1039-L106820:32
*** otter768 has joined #openstack-chef20:40
*** otter768 has quit IRC20:45
*** libsysguy has quit IRC20:53
*** emagana has quit IRC21:03
openstackgerritJJ Asghar proposed stackforge/cookbook-openstack-network: Update iproute because Centos 6.5 hates us  https://review.openstack.org/13917521:04
*** mikedillion has quit IRC21:08
j^2markvan: perfect, works21:12
markvancool21:12
j^2now to the next stack trace...21:13
*** neelashah has quit IRC21:48
*** neelashah has joined #openstack-chef22:23
*** otter768 has joined #openstack-chef22:41
*** otter768 has quit IRC22:46
*** kbringard has quit IRC22:59
*** rtheis has quit IRC23:01
*** malfaitc has quit IRC23:06
*** malfaitc has joined #openstack-chef23:06
*** kitch_ has quit IRC23:15
*** kitch_ has joined #openstack-chef23:17
*** shakamunyi has quit IRC23:19
*** shakamunyi has joined #openstack-chef23:20
*** kitch_ has quit IRC23:20
*** kitch_ has joined #openstack-chef23:23
*** ncerny_ has quit IRC23:23
*** neelashah has quit IRC23:36
*** kobtea has joined #openstack-chef23:41
*** kobtea has quit IRC23:45
*** galstrom is now known as galstrom_zzz23:45
« Wednesday, 2014-12-03 Index Friday, 2014-12-05 »

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