Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-11-19

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:01 oz_akan_ joined #salt
00:01 xmltok joined #salt
00:04 Cidan that's it
00:04 Cidan I'm done
00:05 Cidan I just spent 5 hours debugging salt, and I keep hitting wall after wall, I'll come back to salt when it's 1.0
00:05 Cidan and has unit testing
00:05 Cidan undocumented changes, regressions, so, much sadness.
00:05 Corey Cidan: 1.0 is somewhat arbitrary, but I take your point.
00:06 dwyerj does it matter if im using openvz on a vps for running salt-master?
00:06 Corey Nope.
00:06 Corey I am as well.
00:07 dwyerj if __grains__['os_family'] != 'Debian':
00:07 dwyerj KeyError: 'os_family'
00:07 dwyerj i get that error, when starting the service
00:08 pdayton joined #salt
00:08 Corey Oh!
00:08 Corey I've worked on that.
00:08 Corey It works properly here, so let's see what's different. What OS are you running in that container?
00:08 dwyerj centos
00:09 Corey dwyerj: Same here.
00:09 dwyerj i added epel-testing, and just yum installed salt-master
00:09 Corey rpm -qa |grep salt says what for versions of the three packages?
00:09 dwyerj [dwyerj@se15 ~]$ sudo rpm -qa | grep salt
00:09 dwyerj salt-0.17.1-1.el6.noarch
00:09 dwyerj salt-master-0.17.1-1.el6.noarch
00:09 dwyerj only 2 packages
00:10 Corey I'm also at salt-0.17.1-1.el6.noarch
00:10 cdcalef joined #salt
00:10 Corey Restarts cleanly.
00:11 dwyerj mine doesn't restart cleanly, still same error
00:11 Corey dwyerj: Does sudo salt-call --local grains.items
00:11 Corey error?
00:11 robawt joined #salt
00:11 dwyerj no salt-call
00:11 robawt joined #salt
00:11 Corey dwyerj: Grab the salt-minion package, retry.
00:12 dwyerj [dwyerj@se15 ~]$ FATAL ERROR: OUT OF MEMORY (epoll.cpp:57)
00:12 dwyerj FATAL ERROR: OUT OF MEMORY (session_base.cpp:453)
00:12 dwyerj if __grains__['os_family'] != 'Debian':
00:12 dwyerj KeyError: 'os_family'
00:12 dwyerj after installing salt-minion
00:12 dwyerj and then restarting salt-master
00:12 Corey Hey-o!
00:13 Corey dwyerj: Firstly: USE A PASTEBIN!
00:13 Corey dwyerj: Secondly, there's your problem.
00:13 dwyerj yeah sorry, ill use pastebin next time.
00:14 Corey dwyerj: If you examine /proc/user_beancounters you'll see what limit you're hitting. Talk to your provider.
00:14 dwyerj hmm alright, this is above my knowledge
00:15 Corey You're running out of memory. This causes all manner of things to pee themselves.
00:16 dwyerj yeah i think its the privvmpages limit
00:16 oz_akan_ joined #salt
00:17 jimallman joined #salt
00:21 dwyerj I don't think that privvmpages limit is what is causing the KeyError in salt-master
00:22 dwyerj i only got that error after restarting salt-master multiple times
00:22 dwyerj and there would have still be salt daemons running
00:24 dvogt joined #salt
00:27 indymike joined #salt
00:27 dwyerj http://pastebin.com/2AYBPcAi
00:29 lemao joined #salt
00:31 dwyerj actually, I think you are right Corey sorry.  I printed out the __grains__ dict, and it seems that most of the threads have the os_family key. while a few don't
00:31 dwyerj so i presume i cant burst enough ram to generate all the objects
00:32 jacksontj joined #salt
00:32 cdcalef how much ram are you working with? what does `free -m` say?
00:37 dwyerj http://pastebin.com/ZbDgA3Jy output of free-m
00:39 bemehow joined #salt
00:40 xt joined #salt
00:41 jacksontj joined #salt
00:44 cdcalef you might want to think about putting on some swap...
00:46 dwyerj yeah ill put some swap on, though there machines are only meant to be minions so i might just run the master on my main machine while testing
00:47 Ryan_Lane joined #salt
00:48 diegows joined #salt
00:49 cdcalef i don't know what you're using the boxes for but you're going to be hamstrung doing practically anything with that little RAM free and no swap.
00:49 dwyerj yeah they are not mine, i didnt even check the specs before this.
00:50 dwyerj and it has a clean centos install, with only salt/nginx/php being installed
00:51 bhosmer joined #salt
00:53 zandy joined #salt
00:55 pipps__ joined #salt
00:55 diegows documentation isn't very clear, is it possible to use syndic to control minion connected to a child master, but having some recipes in the child master too?
01:06 morganfainberg left #salt
01:09 mwmnj joined #salt
01:12 zandy joined #salt
01:15 shinylasers joined #salt
01:17 brianhicks joined #salt
01:18 Corey dwyerj: You're also hitting privvmpages, which is sort of like free ram but not really.
01:19 dwyerj yeah ive always had real machines to work on, so i didnt really know what i was going on. but ive read up and understand
01:19 dwyerj i have 2 vps, with 2gb ram
01:19 dwyerj starts salt-master no worries
01:21 halfss__ joined #salt
01:30 bemehow joined #salt
01:33 Furao joined #salt
01:35 zz_cro joined #salt
01:39 vipul joined #salt
01:41 bt joined #salt
01:42 bemehow joined #salt
01:45 bemehow_ joined #salt
01:47 ipmb joined #salt
01:49 NotreDev joined #salt
01:49 jalbretsen joined #salt
01:49 bhosmer joined #salt
01:53 foxx[cleeming] joined #salt
01:53 foxx[cleeming] joined #salt
01:55 xt joined #salt
02:03 oz_akan_ joined #salt
02:06 pipps joined #salt
02:08 bhosmer joined #salt
02:08 zz_cro joined #salt
02:11 bhosmer_ joined #salt
02:14 favadi joined #salt
02:14 favadi hi
02:15 favadi I have a problem with salt stack on centos 5
02:15 favadi I want to use gitfs_remotes, but the master log said:
02:15 favadi Git fileserver backend is enabled in configuration but could not be loaded, is GitPython installed
02:15 favadi But I'm very sure that GitPython is installed.
02:15 favadi What did I do wrong?
02:23 franky_ joined #salt
02:27 bemehow joined #salt
02:27 dvogt joined #salt
02:27 jcockhren favadi: gist your configuraiton
02:28 jcockhren also, does the user that's running salt hace read access to the repo?
02:29 xl1 joined #salt
02:33 favadi jcockhren, http://pastebin.com/gaNWVihm
02:33 favadi jcockhren, it's a github salt-formula
02:33 favadi so, yes
02:34 jcockhren favadi: what's the version GitPython you have installed?
02:35 favadi jcockhren, GitPython-0.2.0-0.3.beta1.el5
02:36 jcockhren favadi: get GitPython==0.3.2.RC1
02:37 jcockhren favadi: grab it from pip
02:38 favadi jcockhren, I will try it
02:39 bemehow_ joined #salt
02:40 sfz joined #salt
02:42 bemehow joined #salt
02:44 favadi jcockhren, seem that it works
02:44 jcockhren cool
02:44 favadi but salt-master complains about /var/cache/salt/master/gitfs
02:44 favadi I mkdir this folder
02:44 jcockhren delete that folder and restart the master
02:44 jcockhren it should repopulate it properly
02:46 _ilbot joined #salt
02:46 Topic for #salt is now Welcome to #salt - SaltConf in January!! http://saltconf.com | 0.17.1 is the latest | Please be patient when asking questions as we are volunteers and may not have immediate answers - Channel logs are available at http://irclog.perlgeek.de/salt/
02:47 favadi so, something is wrong with my config?
02:47 favadi or my salt package?
02:47 jcockhren make sure the gitfs folder has the same mode and ownership as it's sibling folders
02:47 jcockhren running 0.17.1?
02:48 favadi version: salt-master-0.17.1-1.el5
02:50 oz_akan_ joined #salt
02:50 favadi jcockhren, I mkdir this folder, and salt stop complains a bout missing folder
02:51 favadi salt create a folder with name 40a2bd331eb61da87260ca1318ed74fa inside it
02:51 jcockhren favadi: that's good
02:51 favadi jcockhren, is this normal?
02:52 jcockhren favadi: it should work now
02:52 jcockhren that is normal
02:52 favadi jcockhren, I will run state.sls now and see if thing work
02:52 favadi :)
02:53 favadi jcockhren,  No matching sls found for 'apache'
02:53 anuvrat joined #salt
02:53 favadi in folder 40a2bd331eb61da87260ca1318ed74fa, I get fatal: bad default revision 'HEAD' when run git log
02:54 jcockhren http://salt.readthedocs.org/en/latest/topics/conventions/formulas.html?highlight=formula#including-a-formula-from-a-top-file
02:55 jcockhren favadi: the actual code isn't held there
02:58 favadi this is my salt top.sls
02:58 favadi http://pastebin.com/mWe3A1XG
02:58 favadi I run sudo salt 'sysadmin-u12-t01' state.highstate test=True env=dieppv
02:58 favadi and still got a sls not found
02:59 jcockhren could you try changing your config to use:
03:00 jcockhren git@github.com:saltstack-formulas/apache-formula.git
03:04 ravibhure joined #salt
03:06 davet joined #salt
03:07 favadi jcockhren, 2013-11-19 10:06:18,698 [salt.loaded.int.fileserver.gitfs            ][WARNING ] GitPython exception caught while fetching: len([]) != len(['Permission denied (publickey).', ''])
03:08 jcockhren change it back to git:// or https://
03:09 bemehow joined #salt
03:09 ravibhure1 joined #salt
03:09 bemehow joined #salt
03:09 jcockhren as for your top file, I *think* there's a requirement to have a 'base' environment
03:10 jcockhren favadi: ^
03:10 jcockhren someone else here should confirm
03:10 favadi jcockhren, I have a base environment
03:11 jcockhren I mean calling it 'base'
03:11 jcockhren other than all that your config should work just fine
03:16 jcockhren oh
03:16 jcockhren favadi: I know
03:16 jcockhren favadi: your config is missing the roots location
03:16 jcockhren favadi: salt can't find your top.sls file
03:17 jcockhren favadi: nm. I see file_roots
03:18 jcockhren but try to put the formula usage in the top file of your base env location
03:22 anitak joined #salt
03:23 favadi jcockhren, I will try it
03:30 stefanmonkey joined #salt
03:31 Cidan moos3: when you're around, let me know
03:31 Cidan moos3: I got the pillar working
03:32 forrest joined #salt
03:40 redondos joined #salt
03:49 terminalmage 0.17.2 packages for EPEL5 and EPEL6 are submitted for epel-testing. packages should hit the mirrors in 48-72 hours
03:49 Baribal_ joined #salt
03:49 favadi jcockhren, after 2 hours, I finally know how
03:50 favadi apache.vhost.standard  should be apache.vhosts.standard
03:50 favadi the README.rst is wrong
03:50 favadi :|
03:50 NotreDev i need to download and build a library. i can do it in either cmd.run states or a BASH script. i can see an argument for either one. what method would you all choose?
03:59 bhosmer joined #salt
04:00 forrest terminalmage, nice!
04:01 forrest favadi, which file are you seeing that on?
04:01 forrest favadi, or did you open an issue already
04:03 favadi forrest, I talk about https://github.com/saltstack-formulas/apache-formula
04:04 Ryan_Lane joined #salt
04:05 forrest favadi, ahh ok
04:06 forrest still either file an issue or make a pull request so it can get updated if you have time though.
04:07 malinoff joined #salt
04:08 ckao joined #salt
04:08 favadi forrest, I've alreay done that
04:09 forrest awesome
04:09 KyleG joined #salt
04:09 KyleG joined #salt
04:11 junedm joined #salt
04:13 middleman_ joined #salt
04:14 joehh forrest: raring (and saucy) issue essentially sorted
04:14 forrest joehh, nice
04:14 forrest I don't even use 'em
04:14 forrest but I like seeing it fixed!
04:14 joehh me too
04:14 terminalmage fedora 20 is submitted and 19 is building on koji right now
04:16 forrest http://i.imgur.com/YCSSmiq.gif
04:16 terminalmage lol
04:21 MTecknology forrest: http://politicalhumor.about.com/library/jokes/bljokecompany.htm
04:22 forrest heh
04:22 forrest I just like that gif
04:22 forrest no political nature intended
04:22 MTecknology I just found it really funny
04:22 forrest yea
04:23 MTecknology who would win between puppet and cfengine?
04:24 forrest I don't know, is the participant a sysadmin or a developer?
04:24 MTecknology yes
04:24 MTecknology my bets are on cfengine... hands down
04:24 forrest in regards to functionality, I'm not familiar enough with cfengine to provide a valid argument
04:26 terminalmage I've only used cfengine 2, and it was horrible
04:26 terminalmage but 3 is much better from what I have been told, and the config syntax was completely changed
04:27 MTecknology cfengine is a pain, but at least it's not ruby
04:27 terminalmage true
04:28 forrest s0undt3ch are you around?
04:30 cro joined #salt
04:32 MTecknology HAHAHA!!! http://i.imgur.com/oVxgq.jpg
04:35 forrest I feel like you must be drinking hard cider again MTecknology
04:35 UtahDave joined #salt
04:36 jimallman joined #salt
04:36 MTecknology forrest: nope- 4 margaritas and a large bourbon
04:36 MTecknology UtahDave: HI!
04:36 forrest oh my bad
04:36 UtahDave hey!
04:37 UtahDave MTecknology: drunk coding again?  lol
04:37 MTecknology Unfortunately, I'm not coding. I'm getting ready for a day of documentation tomorrow unless something nasty breaks.
04:38 malinoff Hi guys!
04:38 morganfainberg joined #salt
04:38 forrest hey malinoff
04:39 ipmb joined #salt
04:39 UtahDave hey!
04:39 MTecknology I need to get a hotel and transportation lined up for saltconf
04:40 forrest plenty of time
04:40 MTecknology UtahDave: Will I need any transportation other than to/from the event center?
04:40 UtahDave nope!
04:40 malinoff Just blew the minds of our admins talking about Salt :)
04:40 forrest nice malinoff
04:40 forrest did you end up just building a demo?
04:41 UtahDave MTecknology: We'll be right down town salt lake city. Lots of stuff right within walking distance
04:41 UtahDave MTecknology: If you want to go skiiing or something you can even take public transportation up to the ski slopes
04:42 malinoff forrest,  That was the second time we met to dive into salt. Yeah, this time we have a lot of typing :)
04:42 MTecknology super duper- thanks :)
04:42 forrest malinoff, nice
04:42 forrest malinoff, so did the senior guy agree?
04:43 forrest UtahDave, to get to the conference, I assume you take the trax train thing, then the bus if you're just doing public transportation?
04:43 forrest unless there are additional trax routes that aren't on this map
04:44 malinoff forrest, I think I'm that guy :D I'm the one who chosen salt, so our admins actually have no choice
04:44 forrest lol
04:44 forrest How do I find that position at my job?
04:44 forrest UtahDave, oh nevermind, I was looking at the wrong section of the 80
04:44 forrest sweet
04:44 malinoff To be a chief guy, you mean?
04:45 forrest 'yeaaaaa, so this tech looks cool, we are using it now, bye'
04:45 forrest :P
04:45 forrest I already tried facts and figures, and examples
04:45 forrest no dice
04:45 UtahDave lol
04:45 UtahDave forrest: I haven't taken the trax train myself yet.  It's pretty new
04:46 malinoff forrest, ah. That was like 'goddamn this uses ruby, that uses ruby, fuck ruby i love python'
04:46 UtahDave I would be surprised if the hotel doesn't have a shuttle
04:46 Cidan sigh, I'm sorry baby
04:46 Cidan I didn't mean to snap at you salt
04:46 forrest UtahDave, yea I only ever take public transportation when I go to conferences unless there is absolutely no other option. Looks like trax goes almost all the way there: http://goo.gl/maps/Z6TqH
04:46 forrest malinoff, hah yea
04:47 zz_cro joined #salt
04:47 UtahDave forrest: Yeah, the trax comes right downtown. I would imagine that it wouldn't stop more than a few blocks from the hotel
04:47 forrest 0.3 mile walk
04:47 forrest no biggie
04:48 forrest it will be a cold walk though
04:51 JulianGindi joined #salt
04:51 UtahDave forrest: check with the hotel to see if they have a shuttle directly to the hotel
04:52 forrest Yea I will, public transportation doesn't bother me, I like talking to random people
04:52 JulianGindi joined #salt
04:53 terminalmage All fedora/epel packages are built and pending acceptance into testing
04:54 forrest nice
04:54 UtahDave terminalmage: nice!
04:54 malinoff Finally :)
04:54 terminalmage yeah... slow process, I think I'm going to create a cloud VM to build these
04:54 terminalmage for the next release
04:54 terminalmage see if that speeds up the mockbuilds
04:55 forrest what sort of resources do you have available on your laptop?
04:55 malinoff terminalmage, do you have any thoughts on your own rpm repository, just like debian.saltstack.com ?
04:55 forrest I got a lot better performance when I did mock builds on an 8 core box.
04:56 terminalmage malinoff: it's in the plans
04:56 forrest malinoff, terminalmage loves waiting for fedora packages :P
04:56 terminalmage just need to make time to get it done
04:56 malinoff terminalmage, nice
05:00 malinoff UtahDave, what's up with pyyaml? Have you tried to dive?
05:02 linjan joined #salt
05:03 UtahDave malinoff: no, I've been slammed with work. I worked  all day today, and now I'm back at the office after dinner with the family
05:03 forrest :\
05:03 forrest working too much is bad mm'kay?
05:03 [diecast] joined #salt
05:06 UtahDave yeah, for sure
05:09 Linz joined #salt
05:09 zz_cro joined #salt
05:11 favadi joined #salt
05:12 malinoff forrest, It's hard not to work when the work is very rewarding
05:12 forrest malinoff, I know
05:15 cocoy joined #salt
05:17 EugeneKay That's the same excuse used by druggies :v
05:18 forrest malinoff are you actually in Russia or are you just connecting through a russian VPN?
05:19 zz_cro joined #salt
05:29 zandy joined #salt
05:29 malinoff forrest, Actually :)
05:29 malinoff In Siberia
05:30 Corey In the salt mines?
05:30 forrest Really? That shows my ignorance of that area, I didn't know they ran many tech shops out of Siberia
05:30 malinoff lol
05:33 shadowsun :136
05:33 shadowsun Gah, this isn't vim O.o sorry
05:35 Cidan does anyone know when the salt ppa is going to be updated?
05:36 rawzone joined #salt
05:36 anuvrat joined #salt
05:39 malinoff forrest, http://goo.gl/maps/vGguB
05:42 forrest for some reason I stereotyped Siberia as the frozen north
05:42 forrest lol
05:43 joehh Cidan: we're holding off for the announcement, the packages are sitting in the salt-depends ppa ready to be copied over
05:43 joehh you can access them from there if you want
05:43 Cidan ah
05:43 Cidan okie
05:43 malinoff forrest, well, sometimes we have -40 in winter
05:43 forrest brr
05:44 malinoff http://www.omsk.aif.ru/pictures/201302/%D1%81%D1%83%D0%B3%D1%80%D0%BE%D0%B1.jpg
05:44 forrest hah
05:44 forrest looks like a pretty beautiful area though
05:45 malinoff Yes :)
05:45 malinoff forrest, https://www.google.ru/search?q=%D0%BE%D0%BC%D1%81%D0%BA&newwindow=1&hl=ru&authuser=0&source=lnms&tbm=isch&sa=X&ei=8_qKUubMJsST4ATelYDADw&ved=0CAcQ_AUoAQ&biw=1741&bih=887
05:45 forrest yea I'm google street viewing around, lol
05:46 joehh Cidan: not sure if you use it, but there is a minor issue with pkgrepo.managed on debian right now on 17.2
05:47 joehh debian=ubuntu in this context
05:47 bhosmer joined #salt
05:47 malinoff forrest, http://goo.gl/maps/0z1VJ
05:48 joehh Cidan: https://github.com/saltstack/salt/issues/8560
05:48 forrest malinoff, what is this thing? 54.98257,73.305779
05:48 forrest is that housing and the doors are garages?
05:49 Cidan you guys really
05:49 Cidan really really
05:49 Cidan really
05:49 Cidan really need unit tests
05:49 Cidan it's killing salt
05:49 forrest there's some sort of sign on the other side of the building
05:49 forrest lol they know Cidan
05:49 Linz joined #salt
05:49 forrest what am I looking at in that picture you linked malinoff?
05:50 forrest office buildings?
05:50 forrest or is that housing?
05:50 joehh Cidan: As a packager (and user), I agree
05:51 Cidan I lost ~6 hours of work today working around regressions, fyi
05:51 joehh I thought you'd want to know about the issue before you hit it yourself...
05:51 malinoff forrest, our embankment :)
05:51 Cidan now I need to pull an all nighter to catch up
05:51 forrest embankment? What do you mean
05:51 joehh in 0.17.2?
05:51 Cidan no, 0.17.1
05:52 Corey I'm completely with Cidan and joehh on this one.
05:52 forrest there's a bunch of doors in your embankment malinoff, lol
05:52 Corey I've lost count of the "oops, we'll have a fix for that out shortly" regressions we've seen.
05:52 forrest I think everyone is with you guys
05:52 malinoff forrest, I was talking about http://goo.gl/maps/0z1VJ
05:52 forrest yea that's what I'm looking at
05:53 EugeneKay Pre-1.0 software is like that :-p
05:53 joehh Cidan: which release were you coming from?
05:53 Cidan 0.17.0
05:53 malinoff About 54.98257,73.305779 - I don't know :) Something like garages, yes
05:53 forrest wait so what were you saying about the embankment?
05:53 forrest usually an embankment is a wall or something
05:54 Cidan Actually in 0.17.0 I had an issue, went to 0.17.1, had a different issue, which then made me have to go to develop
05:54 Cidan which then had another issue...
05:54 joehh yeah...
05:54 Cidan should have stayed on 16.4 at this rate
05:54 joehh I have been sticking with 0.16.4 till now
05:54 forrest lol Cidan
05:54 forrest I like your mood
05:54 forrest come in, chill -> excited for new release -> angry at new release
05:55 Cidan sorry if I'm shitty, I love salt, I really do, and I'll keep at it...
05:55 Cidan but 10 hours now
05:55 malinoff forrest, uhm. My English isn't very native, as you can see :) Probably the best word here is 'riverfront'
05:55 Cidan :(
05:55 forrest nah it's understandable man
05:55 forrest ahh I see I see, no you had it right malinoff
05:55 joehh I test each of the new releases and make sure any bugs I need are filed, but wait for about .2 before using in productin
05:55 forrest that is an embankment
05:55 forrest the street view was pointing me at a wall
05:55 malinoff forrest, I should say 'turn around' :( sorry
05:55 forrest and I was like 'this is the shittiest embankment I have ever seen, there are doors! And it is only a few hundred meters long'
05:55 forrest lol
05:56 malinoff :D
05:56 forrest that is a nice view though
05:56 NotreDev i see there is an open issue for file.accumulated documentation, does anyone have a working example? https://github.com/saltstack/salt/pull/2521
05:57 forrest NotreDev, nope
05:58 forrest NotreDev, looks like there is an example down here: http://docs.saltstack.com/ref/states/all/salt.states.file.html#salt.states.file.blockreplace
05:58 malinoff forrest, https://ssl.panoramio.com/photo/70464782
05:58 forrest nice malinoff
05:58 forrest oh damn it's already 11, I've gotta get to bed
05:58 forrest later
06:02 rmt joined #salt
06:06 bemehow joined #salt
06:14 NotreDev got it to work exactly as it was suggested in the error log
06:14 NotreDev sorry, issue tracker
06:18 sroegner_ joined #salt
06:18 Linz joined #salt
06:18 aserdp joined #salt
06:19 Cidan I tell you what though
06:19 Cidan when salt works, it fucking works
06:19 Cidan salt-cloud -p elastic-slave elastic-slave-01 elastic-slave-02 elastic-slave-03 elastic-slave-04
06:19 Cidan 4 elasticsearch nodes created in aws, EBS added, configured, and clustered
06:19 Cidan with one commant
06:19 Cidan *command
06:21 jalbretsen joined #salt
06:26 Furao joined #salt
06:32 Rudd-O joined #salt
06:33 Rudd-O hello gentlemen.  I am looking for a way to run salt-ssh but in a local chroot rather than SSHing into a box.  Can you help me?  Thanks.
06:33 Rudd-O does that make sense?
06:35 Cidan you mean running local salt?
06:36 Linz joined #salt
06:36 Cidan or do you mean running local salt in a folder that is a jail?
06:36 Cidan Rudd-O: ^
06:39 Furao joined #salt
06:43 isomorphic joined #salt
07:01 isomorphic joined #salt
07:05 NotreDev joined #salt
07:13 oz_akan_ joined #salt
07:16 juasiepo joined #salt
07:23 IJNX joined #salt
07:29 Katafalkas joined #salt
07:35 bhosmer joined #salt
07:40 Destro joined #salt
07:41 Furao joined #salt
07:53 Furao joined #salt
07:53 carlos joined #salt
07:55 isomorphic joined #salt
08:00 balboah joined #salt
08:03 slav0nic joined #salt
08:15 giantlock_ joined #salt
08:22 harobed joined #salt
08:32 bemehow joined #salt
08:35 matanya joined #salt
08:41 philipsd6 joined #salt
09:03 ajw0100 joined #salt
09:15 ravibhure joined #salt
09:16 linjan joined #salt
09:20 dangerousbeans joined #salt
09:23 favadi Why salt stack complie pillar top.sls in all environment?
09:24 bhosmer joined #salt
09:25 favadi If one dev mess up his pillar top.sls, all the other devs will get the errors about pillar fail to compile
09:35 zooz joined #salt
09:45 elsmorian joined #salt
09:52 AviMarcus joined #salt
10:02 bhosmer joined #salt
10:03 hhenkel Hi all, what is the best way to debug jinja errors? I got the following: https://www.refheap.com/21049
10:04 hhenkel These are my first steps with salt/jinja so it is quite possible that I'm doing stuff that is not supported.
10:11 aleszoulek joined #salt
10:12 pniederw joined #salt
10:12 pniederw hi guys. question: can I require a state from another sls file, or do I have to include that file first?
10:14 zooz joined #salt
10:28 linjan joined #salt
10:35 Cidan pniederw: I think you have to include it, afaik anyway, in the top file
10:35 Cidan I 100% could be wrong though
10:35 Cidan hhenkel: this might be the bug I hit earlier, it's insanely annoying
10:36 pniederw they are all included in the top file, but I'm not sure if that's enough.
10:36 Cidan pniederw: if they are in the top file, then they will be applied to the machines that match
10:36 Cidan pniederw: once they are in the top file, you can cross reference requirements too
10:37 pniederw sure: what I'm trying to do is to have a base config that I apply to '*' (to make absolutely sure I don't miss any servers), then build on top of that for selected servers. this means selected servers will sometimes have to depend on base config, and I wonder what's the right way to achieve this.
10:37 Cidan pniederw: ie: I have a "java.sls" that installs openjdk-7-jre, and "blah.sls", I can require pkg openjdk-7-jre in blah.sls somewhere, if java.sls is in the top for that machine too
10:37 Cidan pniederw: sure, yes, that works.
10:37 Cidan I do that all the time
10:37 Cidan :)
10:38 pniederw ok, thanks. didn't find that anywhere in the docs. from the docs it's just clear to me that it works within same file or when using include.
10:42 pniederw does this mean that id declarations have to be globally unique. or can I do something like "- require: - java.pkg openjdk-7-jre"?
10:42 Cidan it has to be unique
10:42 Cidan if it isn't, you will get a rendering error
10:43 Cidan That's why many states have a name param
10:43 Cidan so you can write out something like
10:44 Cidan something-important-title-blah: file.managed: - name: /etc/blah.conf - source:...
10:44 Cidan etc
10:45 pniederw I see. that smells like duplicate namespace maintenance, in addition to the file structure (e.g. I already have base/network/init.sls and xyz/network/init.sls).
10:47 pniederw hard to keep names unique across many files (without going overboard), but I'll try that for now
10:48 Cidan I find that it's not terribly hard
10:49 pniederw it shouldn't be necessary. unthinkable in programming. :-)
10:49 * Cidan shrugs
10:49 Cidan you're likely right
10:50 Cidan sls files should maybe be rendered as individual templates, requiring explicit includes
10:50 Cidan but I like the flat global name space
10:50 Cidan then again, I like C
10:51 vespakoen joined #salt
10:54 pniederw I'm new to this world, and I'm still trying to find a layout/design that's easy to understand/maintain/scale
10:56 xl1 Is there a way to have state.highstate report an error if not all minions returned a result?
10:57 xl1 I'm shocked to discover that 50% of the chance not all minions return a result, there're 11 of them in total.
11:01 hhenkel Cidan: Which bug?
11:12 bhosmer_ joined #salt
11:13 hazzadous joined #salt
11:15 hhenkel Anyone able to point out what's wrong here: https://www.refheap.com/21049
11:16 Cidan hhenkel: sorry!  I was afk
11:16 Cidan it's not you
11:16 Cidan it's a bug in jinja/salt
11:16 Cidan I just ran into this today
11:16 hhenkel Cidan: okay, can you point me to the report / workaround?
11:17 Cidan https://github.com/saltstack/salt/issues/7625
11:17 hhenkel Cidan: I'm not totally convinced that it is a bug, since it's the first time I'll try to use jinja with salt.
11:17 Cidan hhenkel: I was only able to use it by installing develop branch, I have not tried 17.2 packages
11:17 Cidan I'm almost certain it's a bug.
11:17 Cidan You just hit it at an unlucky time
11:19 hhenkel Cidan: hmm, okay seems like bad luck then... :( I'll give the dev branch a shot as I also need to give another fix a try.
11:20 baffle hhenkel: Yeah, I had similar problems as well. 17.2 packages worked fine.
11:20 Cidan baffle: that's good to know
11:21 hhenkel baffle: Ah, good info, then I'm able to use 0.17.2 with my playground machines and only need to do a short test in the dev branch. Thanks!
11:22 vespakoen joined #salt
11:29 foxx joined #salt
11:30 hhenkel baffle: On which os version are you using salt? Seems like epel (for rhel) still got 0.17.1 packages... :(
11:34 baffle hhenkel: Ubuntu Precise; Packages are not updated in the main repos yet, as it is not technically released.
11:35 baffle hhenkel: For Ubuntu there are packages in a staging repo. Myself, I created my own packages from develop.
11:35 baffle hhenkel: There might be a staging repo for RHEL/CentOS as well, but I have no idea where it is. :)
11:37 hhenkel baffle: Nope, there is nothing in epel "testing" repo, I guess I'll build them by myself then.
11:40 Cidan don't use the 17.2 packages
11:40 lemao joined #salt
11:40 Cidan in testing
11:40 Cidan there is a major bug with them
11:40 baffle Cidan: Oh? What?
11:40 pniederw there is a salt-daily ubuntu ppa, but my impression is that it's outdated
11:40 Cidan https://github.com/saltstack/salt/issues/8560
11:40 Cidan seriously
11:40 Cidan do not upgrade using those packages
11:41 sroegner_ joined #salt
11:44 baffle Good I am using develop then. :)
11:45 zandy joined #salt
11:47 joehh Cidan, baffle: I wouldn't completely avoid that release - if you don't use pkgrepo or are prepared to use the temporary workaround described in the bug
11:47 joehh then they are fine
11:48 Cidan absolutely not
11:48 joehh There are many bugs fixed and on the whole they will be a big improvement over 0.17.1
11:48 Cidan literally, an entire state is broken in a mainline release, that's insane
11:48 Cidan also I very much use pkgrepo, all over
11:49 joehh in that case, wait a day or so and terminalmage and I will have an update out... :)
11:49 Cidan :D
11:49 Cidan btw I'm not being a dick to you, I totally realize it's not your fault
11:51 joehh I know - I also understand your frustration, I just think it is more subtle than "don't use"
11:51 Cidan nuke it from orbit!
11:51 joehh :)
12:01 cron0 joined #salt
12:13 anitak joined #salt
12:15 matanya joined #salt
12:18 brianhicks joined #salt
12:19 baffle joehh: I use package repos, and I had huge jinja issues. So my tmp packages with 0.17.2 code from develop works great. A bit hacky, tho'.
12:26 joehh baffle: have you got a bug for the jinja issues (or was that an older package)?
12:27 blee joined #salt
12:29 baffle joehh: Didn't get around to posting one, it was fixed in 0.17.2.
12:30 joehh thats good
12:40 ipmb joined #salt
12:43 hhenkel Cidan: building the packages of the 0.17.2 git branch should have this fixed I guess?
12:43 Cidan in theory, but I didn't test/do that
12:44 hhenkel Okay, I'll guess I give it a try, I only got 4 machines with salt currently, so it won't hurt that much... ^^
12:44 Cidan I've got 90, so, it sucked, D:
12:44 Cidan and moos3 over there has like, 300 now
12:46 Cidan off to bed, only at 5 am
12:46 Cidan woo woo
12:46 Cidan night night
12:48 bemehow joined #salt
12:49 xl1 left #salt
12:55 bhosmer joined #salt
12:56 bemehow joined #salt
13:00 bhosmer joined #salt
13:02 diegows joined #salt
13:14 jslatts joined #salt
13:19 dangerousbeans joined #salt
13:22 whiskybar joined #salt
13:22 natewalck joined #salt
13:23 mpanetta joined #salt
13:24 quantum-x joined #salt
13:25 quantum-x hey all
13:25 quantum-x I upgraded to .17 yesterday
13:25 quantum-x and noticed that file.recurse seems to break
13:25 quantum-x That is, my old sls files no longer work
13:25 quantum-x http://pastebin.com/S33cAqmr
13:34 vejdmn joined #salt
13:36 urtow joined #salt
13:37 urtow hello
13:44 MTecknology quantum-x: help write tests!!! :D
13:44 quantum-x MTecknology, let me know whwere to update / post my findings, and it'd be with pleaure
13:45 MTecknology quantum-x: I mean unit tests, https://github.com/saltstack/salt/tree/develop/tests
13:45 jslatts has anyone here done much with custom grain modules?
13:46 MTecknology jslatts: with ext_grains?
13:46 Teknix joined #salt
13:46 MTecknology quantum-x: Eventually, I'm going to have someone help me learn how and then I'm going to try to make documentation for it followed by actually making a bunch of them. The regression issues are a bit irritating.
13:47 jslatts MTecknology: hrm, not sure. I'm using the ec2_tags grain module from contrib
13:47 MTecknology ah.. know nothing about those
13:47 jslatts I just need to figure out something about ordering
13:48 jslatts as in, will the grains be available for matching against on the first run of state.highstate
13:51 toastedpenguin joined #salt
13:53 jeffasinger joined #salt
14:01 MTecknology jslatts: sure, as long as there's not a state that puts it there
14:01 sroegner_ joined #salt
14:01 jslatts MTecknology: it gets delivered during the grains sync
14:01 jslatts i think. its in the _grains folder
14:02 MTecknology it won't be available until the run after it's been put there (afaik)
14:03 quantum-x this is really not good
14:03 jslatts so the very first run won't match on those grains. that is what i was afraid of
14:03 quantum-x .17 doesn't like the file recurse at all
14:03 jslatts i am trying to get the machine to fully provision on boot
14:04 quantum-x it's just broken our deployment servers, ugh
14:05 MTecknology jslatts: how is a grain supposed to be available if what generates it doesn't exist?
14:05 MTecknology jslatts: see if a bug report exists for it already
14:05 MTecknology quantum-x: **
14:05 quantum-x ** ?
14:05 jslatts MTecknology: well, if the grain sync happens before the patterns are matched in the top file it could work in theory
14:05 MTecknology quantum-x: see if a bug report exists for it already
14:06 MTecknology jslatts: grains aren't calculated on call
14:06 MTecknology wait... are they?
14:07 MTecknology jslatts: find out if grains are calculated as requested or if they're all calculated at the beginning
14:07 jslatts MTecknology: i guess i'll have to read through the source
14:07 jslatts can't find any docs about it
14:07 jslatts i'm also about to run an experiment
14:08 MTecknology It looks like they're calculated from running and not on request, but trying will be the easiest way to know
14:09 juicer2 joined #salt
14:10 MTecknology https://github.com/saltstack/salt/blob/develop/salt/modules/grains.py#L148 <-- seems like this could be done a bit cleaner
14:13 Gifflen joined #salt
14:16 jergerber joined #salt
14:17 brianhicks joined #salt
14:18 racooper joined #salt
14:19 NotreDev joined #salt
14:21 baoboa joined #salt
14:21 nahamu joined #salt
14:22 tty-1 joined #salt
14:24 AdamSewell joined #salt
14:27 bhosmer joined #salt
14:30 jimallman joined #salt
14:31 anitak joined #salt
14:37 Brew joined #salt
14:41 danielbachhuber joined #salt
14:41 balboah is there some helper function to format state results for textual output in a returner? maybe I should dig down the default master output
14:48 zandy joined #salt
14:49 bhosmer_ joined #salt
14:49 [diecast] joined #salt
14:50 mannyt joined #salt
14:51 quickdry21 joined #salt
14:51 tyler-baker joined #salt
14:56 pdayton joined #salt
14:57 abe_music joined #salt
14:57 sroegner_ joined #salt
14:59 quantum-x anyone ever seen this with .17? http://pastebin.com/AG8tFLv2
15:00 quantum-x file.recurse no longer works
15:11 ze- hey. How would you do a file.replace, with append_if_not_found option ?
15:18 jrdx joined #salt
15:18 Chrisje joined #salt
15:21 Katafalk_ joined #salt
15:21 JasonSwindle joined #salt
15:25 BenBen joined #salt
15:27 kermit joined #salt
15:28 DredTiger joined #salt
15:29 JasonSwindle left #salt
15:30 alunduil joined #salt
15:31 terminalmage quantum-x: please file an issue, with an SLS example and the version of both the master and minion
15:31 JasonSwindle joined #salt
15:31 quantum-x terminalmage, done alreay sir!
15:31 quantum-x nasty way to find a bug
15:32 quantum-x upgrade and it killed all our production
15:32 quantum-x but hey
15:32 terminalmage quantum-x: thanks
15:33 forrest joined #salt
15:35 aleszoulek joined #salt
15:38 Sypher is the api still being worked on as a separate project/product (and is it still getting fixes) or is it waiting for it to be merged?
15:38 mannyt_ joined #salt
15:40 terminalmage api is not going away
15:40 Sypher its being merged to the core at some point, like salt-cloud right?
15:40 terminalmage I believe so, but I am not certain
15:41 Sypher i've found quite an annoying bug (reported it) which is blocking the development of the thing i'm working on :(
15:41 terminalmage what is the issue number?
15:41 terminalmage I'll ping some guys
15:41 terminalmage I don't work on the API unfortunately
15:42 Sypher https://github.com/saltstack/salt-api/issues/127
15:42 forrest s0undt3ch, thanks for the response on that ticket, I was trawling the ticket queue last night and was wondering why that was still open.
15:43 s0undt3ch forrest: well, Thank You!
15:43 s0undt3ch ;)
15:43 forrest lol
15:44 eculver_ joined #salt
15:45 forrest hey s0undt3ch that reminds me, do you think at some point you could do a small intro to writing tests for salt? There was a lot of interest in writing tests for salt in a discussion going last night, but people aren't quite sure how to get started.
15:46 forrest I mean they know how to write tests, but it's kinda hard to wrap your head around all the 'magic' happening in Salt to really understand how to write a proper test I think.
15:47 steveoliver_ joined #salt
15:47 imil_ joined #salt
15:47 zz___ joined #salt
15:48 elements joined #salt
15:48 s0undt3ch forrest: if all goes well, I'll be doin' a presentation @SaltConf about unit testing. I'd like to record that for these kind of things, but, at the bare minimum, I'll have to write something on how to code tests for salt, so, worst case scenario, 2 more months until proper documentation regarding unittests ;)
15:48 zandy joined #salt
15:48 bui_ joined #salt
15:48 forrest s0undt3ch, lol ok
15:48 Vivek_ joined #salt
15:48 EWDurbin_ joined #salt
15:48 AlcariTh1Mad joined #salt
15:48 forrest I'll tell people to aim their pitchforks at you until that time then :P
15:49 s0undt3ch forrest: sure ;)
15:49 thelorax123 joined #salt
15:50 Corey s0undt3ch: So you are making it out to saltconf? :-)
15:50 Baribal_ joined #salt
15:50 s0undt3ch Corey: fingers crossed, yes
15:50 Corey s0undt3ch: I'm speaking on best practices. I look forward to meeting you!
15:51 forrest be care s0undt3ch, the Salt team will let you walk in, then chain you to a computer
15:51 forrest *careful
15:51 zooz joined #salt
15:51 s0undt3ch Corey: awesome!
15:51 twinshadow_ joined #salt
15:51 bturner joined #salt
15:51 s0undt3ch forrest: he he he he
15:51 z3uS| joined #salt
15:51 keekz_ joined #salt
15:51 coolj_ joined #salt
15:51 marcel- joined #salt
15:52 vbabiy_ joined #salt
15:52 s0undt3ch I think I won't have enough time to attend all presentations
15:52 s0undt3ch ;)
15:52 forrest hah
15:53 defunctzombie_zz joined #salt
15:53 s0undt3ch I'm a version ppl
15:54 s0undt3ch heh
15:54 s0undt3ch virgin
15:54 jdenning joined #salt
15:54 s0undt3ch on computer related presentations
15:54 s0undt3ch I've never been to anything similar
15:54 s0undt3ch ever!
15:55 forrest s0undt3ch, it looks like your testing stuff is a lab, are you planning on doing a talk too?
15:55 zandy joined #salt
15:56 s0undt3ch forrest: yep, a lab, but I should talk about it too, if it's a "talk" or not, still haven't decided
15:57 s0undt3ch forrest: I'm already on the schedule?
15:57 forrest yea they have the schedule up
15:57 forrest http://www.cvent.com/events/saltconf-2014/custom-21-3aef0eba23dd49a1bd9ffcaaf83d657e.aspx
15:57 forrest talks
15:57 forrest http://www.cvent.com/events/saltconf-2014/custom-22-3aef0eba23dd49a1bd9ffcaaf83d657e.aspx
15:57 forrest labs
15:58 s0undt3ch yep
15:58 s0undt3ch I'm there
15:58 forrest and like UtahDave said, no worries about it being your first presentation, you'll only be presenting alongside guys from Nasa and other major IT shops, no big deal :P
15:58 Ixan joined #salt
15:59 JasonSwindle forrest:  It looks like my team did not make the cut.
15:59 forrest What was your talk on?
15:59 JasonSwindle Django and the Cloud
15:59 forrest ahh ok
15:59 mordred joined #salt
15:59 ConceitedCode joined #salt
15:59 forrest I wish you had been around last night, I had a question, but can't remember what it is.
16:00 JasonSwindle Our stack is NGINX -> uWSGI -> Postgres on linux
16:00 JasonSwindle with Kibana / Logstash and New Relic monitoring
16:00 JasonSwindle We were going to give a talk on it and open source the stack.
16:00 ClausA joined #salt
16:02 forrest I'd still be interested in seeing it, you should just tweet it out at the conference.
16:03 cnelsonsic joined #salt
16:03 JasonSwindle I am working on getting it ready to the public.  A lot of stuff to re-write to make it general
16:03 JasonSwindle Right now it is too much to one app.
16:03 forrest you've got time!
16:04 JasonSwindle BTW, uWSGI is amazing
16:05 * EugeneKay calls BINGO!
16:05 forrest yea, BenBen was talking about it yesterday
16:05 NotreDev joined #salt
16:06 JasonSwindle The power and little overhead it needs is great.  NGINX <—> uWSGI <—> App
16:07 jdenning Does anyone know if SaltConf is going to be recorded?  I'd like to share my talk w/ some people who aren't going to be able to attend..
16:07 forrest jdenning, I'm not sure. I asked this a month or two ago, whether it would be streamed/recorded
16:07 forrest UtahDave said they were gonna try to I believe, but nothing was set in stone
16:07 forrest I just asked if they stream it they don't use the same potato quality company that puppetconf has used two years in a row
16:07 BenBen Yeap, uwsgi is great. It's still a little more cumbersome to use than things like apache, because you've got to manage both nginx , uwsgi and the nginx-uwsgi link
16:07 jdenning forrest: Cool..fingers crossed :)
16:08 forrest jdenning, indeed, I haven't asked lately though so I don't know
16:08 BenBen But it's probably faster in terms of performances
16:08 JasonSwindle The over-head and performance is why I moved onto it
16:08 JasonSwindle I have the config for uWSGI setup pretty guy
16:08 forrest Woah woah woah, are you guys saying you'd rather use uwsgi and nginx, than apache with fastcgi??
16:08 JasonSwindle *DRY
16:08 forrest :P
16:09 forrest I'm knocking fastcgi if that wasn't clear.
16:10 KyleG joined #salt
16:10 KyleG joined #salt
16:10 defunctzombie joined #salt
16:10 BenBen JasonSwindle: one things that bugged me a little, was that everytime i restarted uwsgi, i had to restart nginx as well.. For example, on first install, i tell salt to install both, but for some reason i couldn't have the nginx-uwsgi link work right away. I had to manually call highstate once after the install
16:11 BenBen But i'm a total admin noob, so my opinion doesn't matter much :)
16:12 forrest BenBen, *gasp* multiple runs??? NOOOOOOOooooooooooo
16:13 sashka_ua joined #salt
16:13 BenBen forrest: not multiple highstate run. Just that when the VM is provisionned using vagrant, it installs everything, but since i've probably left some order unconstrained, it doesn't install & run the nginx and uwsgi service in the right order.
16:13 forrest ahhh ok
16:13 forrest that makes me feel a bit better
16:14 BenBen (well, it does probably call highstate, so that's a bit equivalent, but that's a very special case)
16:15 BenBen So i've probably forgot to put some require & watch somewhere.. The point was, it's two services to configure and synchronize. Which may be a bit more cumbersome that one.
16:15 BenBen than one
16:22 _jslatts joined #salt
16:23 JasonSwindle BenBen:  That is odd
16:24 JasonSwindle I only have to reload the app that uWSGI is spawning with a touch
16:24 micah_chatt joined #salt
16:25 teskew joined #salt
16:26 iMil joined #salt
16:26 BenBen JasonSwindle: hm, well, maybe i remember incorrectly then.
16:26 JasonSwindle BenBen:  https://gist.github.com/JasonSwindle/7f6f897186fef95a3075
16:26 ccase joined #salt
16:27 amckinley joined #salt
16:28 BenBen JasonSwindle: My uwsgi configuration is in a .ini file
16:28 JasonSwindle Ah ok
16:28 JasonSwindle Mine was, but I really like YAML
16:30 JasonSwindle I guess I also need to give you my uwsgi config as well
16:31 JasonSwindle BenBen:  Updated.  uWSGI is scoped to non-root and then spawns the app as a different user.
16:32 BenBen JasonSwindle: i'm a bit confused by what you've sent. Is this salt tls files ? or just uwsgi configuration files ?
16:32 JasonSwindle uWSGI configs with Pillar data in them
16:33 BenBen JasonSwindle: ok. The uwsgi: at the start of the file gave me a doubt..
16:33 BenBen JasonSwindle: i thought maybe there was some secret salt module i didn't know :))
16:33 JasonSwindle Sadly, no.  I wish…..but uWSGI is a beast.
16:34 JasonSwindle It took me some time to get uWSGI to where it is, and I am still a little lost on it
16:34 BenBen JasonSwindle: well, you've clearly spent a lot more time than i did on uwsgi configuration..
16:35 BenBen JasonSwindle: they really should layer those configuration options rather than just list them all in their documentation. It's really confusing.
16:35 JasonSwindle I agree, the docs on uWSGI are a real issue for me as first.
16:35 JasonSwindle and some options are totally hidden
16:35 balboah What's left for 0.17.2 to be released officially?
16:36 wkf joined #salt
16:36 BenBen JasonSwindle: as for the nginx-uwsgi link i suppose i got used to restart everything when i was still messing around with the linking and continues to do it without thinking
16:37 * Gareth waves
16:37 bhosmer_ joined #salt
16:37 pdayton joined #salt
16:37 BenBen JasonSwindle: thx for the gist anyway. It'll probably be very helpful to me very soon
16:37 JasonSwindle BenBen:  no problem.  The touch reload is really neat
16:37 JasonSwindle and scoping the app is really awesome
16:38 xinkeT joined #salt
16:38 jrdx joined #salt
16:39 oz_akan_ joined #salt
16:39 Katafalkas joined #salt
16:39 BenBen scoping the app ?
16:40 BenBen oh ok
16:40 JasonSwindle The app no longer runs as root, but as a user with limited permissions
16:40 JasonSwindle cap: setgid,setuid
16:41 JasonSwindle uWSGI has a cove of options that are really confusing but keep at it
16:42 cachedout joined #salt
16:43 BenBen Yeap. i'm learning a bit everything at the same time right now. Both salt, the OS subtleties, and service configuration options... So for now, my first concern is just to have something that works :))) But i'll probably spend more time later on tweaking things and options...
16:44 jacob_s joined #salt
16:44 KyleG joined #salt
16:44 KyleG joined #salt
16:44 [ilin] joined #salt
16:46 pdayton joined #salt
16:47 apergos fi we have firewalls in the way between the salt maser and minion, what ports do I need to worry about?  and sorry if this is a faq
16:47 apergos *master
16:48 apergos nm found
16:51 jacob_s Did installation from a .deb file break in salt 17.1?
16:52 wilywonka joined #salt
16:52 wilywonka ic
16:53 pipps_ joined #salt
16:55 jalbretsen joined #salt
16:55 zandy joined #salt
16:56 jacob_s To be more specific I have a state http://pastebin.com/VgNq26VA
16:56 jacob_s Which used to work, but doesn't anymore.
16:57 oz_akan_ joined #salt
17:05 KyleG joined #salt
17:05 KyleG joined #salt
17:06 troyready joined #salt
17:06 pdayton joined #salt
17:08 xmltok joined #salt
17:09 mannyt_ joined #salt
17:11 druonysus joined #salt
17:11 druonysus joined #salt
17:16 tty-1 joined #salt
17:20 redondos joined #salt
17:21 dave_den jacob_s: there was a bug when specifying version: in pkg, but i don't recall anything about sources:
17:21 tty-1 joined #salt
17:21 dave_den your gist looks fine. if you enable debug logging on the minion, do you see anything during that state run?
17:24 amahon joined #salt
17:26 dvogt joined #salt
17:26 pdayton joined #salt
17:27 tty-1_ joined #salt
17:32 sfz joined #salt
17:33 davet1 joined #salt
17:35 mgw joined #salt
17:36 mgw anybody here using debian/ubuntu preseeds? I'm wanting to brainstorm on how to use salt to configure an install server
17:39 bemehow joined #salt
17:40 dave_den mgw: yeah, i do
17:41 mgw dave_den: how do you currently manage your preseeds?
17:41 mgw I've been using cobbler, but am migrating away in favor of managing everything with salt
17:42 dave_den mgw: right now i just use packer.io to build my images, and i start with my salt-master first by doing a masterless "salt-call state.sls bootstrap" where my salt state tree and salt source code is shared to my guest via vmware shared dirs.
17:43 dave_den packer.io also has a salt-masterles provisioner, but i prefer to just do a simple shell script provisioner so i can have full control
17:43 mgw I'll have to look at packer.io
17:43 * timoguin has been aching to try out packer
17:43 dave_den mgw: that's what i am doing. all salt from bootstrap to deploy and infrastructure lifecycle
17:43 mgw does it build images for pxe booting hardware?
17:44 mgw does packer.io use preseeds?
17:44 dave_den packer is ok. it does the job of starting the ISO and serving the preseed files and running commands over ssh
17:45 dave_den all packer does is start the guest and provide a built-in HTTP server to serve the preseed files. then it waits for SSH to be available from your guest to send your provisioning scripts into the guest
17:46 dave_den i've got a packer build going now for a centos minion. i can show you the transcript when it finishes.
17:47 mgw dave_den, thanks
17:48 mgw so docker.io is a daemon that runs on a boot server?
17:48 dave_den i have the beginning of making my own PXE boot server.
17:48 dave_den docker or packer?
17:48 mgw packer, sorry
17:48 mgw lol
17:49 dave_den packer is just an app written in Go
17:49 troyready joined #salt
17:49 mgw I'm trying to understand what your overall process is like.
17:50 mgw are you using packer.io for provisioning bare metal?
17:50 mgw or just guest systems?
17:50 JasonSwindle joined #salt
17:50 mgw dave_den ^
17:51 dave_den all it does is attach an ISO (like the ubuntu or centos install isos) to vmware or virtualbox guest (you define a template to use for CPU, RAM, etc of the guest), then it boots the guest and starts an HTTP server. When the guest boots from the ISO, packer.io can send keyboard commands to the guest, like 'text ks=http://PACKER_IP/my_kickstart.ks'
17:51 mgw i see, ok
17:52 dave_den then the ISO starts the kickstart process and packer waits for SSH to be available from your host, then it sends any files you want and executes scripts
17:52 mgw I see, so it's for virutal guests
17:52 dave_den so you would use packer.io to build a PXE boot server, then you could not need packer.io
17:52 dave_den right.
17:52 dave_den well, sort of.
17:53 mgw My immediate issue is with managing the preseeds for the bare metal install
17:53 JasonSwindle left #salt
17:53 dave_den it creates images, which are built within vm guests, but they could be used as images to install to bare metal, too.
17:53 linuxnewbie joined #salt
17:54 Pikachu320 joined #salt
17:54 smccarthy joined #salt
17:54 bhosmer joined #salt
17:55 zandy joined #salt
17:58 jrdx joined #salt
17:59 xcbt joined #salt
18:00 bhosmer joined #salt
18:02 thelorax123 joined #salt
18:04 jimallman joined #salt
18:05 quickdry21 joined #salt
18:07 amahon joined #salt
18:07 Corey Well, it's not Salt related, but http://blog.taos.com/2013/11/19/dns-resolution-a-primer/
18:08 grep_away joined #salt
18:08 matanya joined #salt
18:09 jacksontj joined #salt
18:10 dave_den short and sweet and correct
18:10 dave_den :)
18:10 cdcalef joined #salt
18:11 mannyt_ joined #salt
18:11 Corey dave_den: Needs moar ipv6 I think.
18:11 dave_den and dnssec
18:13 elfixit joined #salt
18:14 druonysus joined #salt
18:14 druonysus joined #salt
18:15 jslatts joined #salt
18:19 jacksontj joined #salt
18:20 UtahDave joined #salt
18:20 Psi-Jack Is it possible, in jinja templating, to comment out a jinja variable, like {% if ... %}, and it's ending {% endif %} ?
18:21 _ikke_ put them between {# #}
18:21 _ikke_ ?
18:22 cachedout That's right, but beware that only comments out the conditional logic, and not the enclosed lines.
18:22 cachedout So be aware of that.
18:22 Psi-Jack Oh? That's it? Append {# {% if ... %} #} around the statements? Nice.
18:23 Psi-Jack cachedout: All I needed. I have additional condition blocks inside this one, multi-tiered if. :)
18:23 cachedout Aye, I figured. Just a gotcha to watch for is all. :]
18:23 Psi-Jack Hehe
18:24 matanya joined #salt
18:25 bhosmer_ joined #salt
18:27 xmltok joined #salt
18:28 ipmb joined #salt
18:30 whiteinge Sypher: thanks for reporting that salt-api bug. I'll drop a reply on that ticket this afternoon.
18:30 Sypher thanks whiteinge!
18:30 whiteinge sure thing. sorry for the slow reply though. my travel schedule is a little tight
18:31 whiteinge the project is still very much active, but you're right that it will be merged into salt proper soonish
18:31 Sypher would be nice to have it merged :) had to jump trough some hoops to get it working
18:32 Sypher the ubuntu packages are not working, a git pull works a lot better but now this weird issue
18:32 Sypher whats strange is that iirc it did work at some point, but that may have been an older revision
18:32 whiteinge definitely. having to manually mix and match package versions is crap
18:34 whiteinge i haven't seen this bug before, so you're right it's probably new. i'll know for sure shortly
18:35 quickdry21 joined #salt
18:35 Sypher always great to be the first, hehe
18:36 matanya joined #salt
18:38 druonysus joined #salt
18:38 druonysus joined #salt
18:40 dpippenger joined #salt
18:41 Sypher hmm the old one was on a different git commit, the only change - other than comments/spec/manpages/releasenotes is 03fbaf55367441b2f45a76c3066eff6be0a6c873 where you updated rest_cherrypy for __virtualname__
18:41 dpippenger Should the 0.17.2 tag work? I installed it and the minion won't even start up... not sure if this is just a bad release or if something else is going on.
18:42 Ryan_Lane joined #salt
18:42 _ikke_ have you tried to start it in debug mode?
18:42 dpippenger yeah, it bails when it's trying to load built-in grains
18:42 _ikke_ There do seem to be problems with this release, but I haven't heard about minions not starting
18:42 matanya joined #salt
18:42 dpippenger sec I can pastebin a log
18:43 xcbt joined #salt
18:44 dpippenger http://pastebin.com/uteGAYS7
18:44 dpippenger this was on a clean install, I purged the old package version entirely
18:45 NotreDev joined #salt
18:45 japage joined #salt
18:45 abe_music joined #salt
18:45 jaustinpage joined #salt
18:46 zooz joined #salt
18:47 pdayton joined #salt
18:48 dave_den dpippenger: looks like you were/are using custom modules as extension modules?
18:48 dpippenger well on my master I'm using the git support for the salt data
18:49 dpippenger but I don't have anything loaded on this minion yet, I can't even get it to start
18:49 dave_den you can rm -rf /var/cache/salt/minion/extmods and restart your minoin
18:49 dpippenger tried that yesterday
18:49 dpippenger but I can do it again
18:50 dpippenger there is something there, is it getting sucked down from the master before the minion commits suicide?
18:50 dave_den yeah
18:50 dpippenger I see... ok, thank you
18:50 dpippenger I'll see if I can figure out who put that grain in place and what's wrong with it
18:51 zooz joined #salt
18:52 matanya joined #salt
18:54 dangerousbeans joined #salt
18:54 dave_den no prob
18:55 zandy joined #salt
18:57 dangerousbeans left #salt
18:58 dave_den dpippenger: https://github.com/saltstack/salt/pull/8578
18:58 jcsp left #salt
18:58 jcsp joined #salt
18:59 dpippenger ahh awesome
18:59 dpippenger yeah I was going to say it's a pretty confusing error as it stands :)
18:59 Psi-Jack Now, is it possible to get jinja templates to not put in blank lines where if statements exist, because it can be really frustrating seeing the actual generated content filled with blank lines.
19:00 dave_den Psi-Jack: use {%-  instead of {%
19:00 Psi-Jack Oh. :)
19:00 forrest I like seeing heewa's merges, because that funny face he has always makes me laugh
19:00 Psi-Jack Thanks! :D
19:00 cro Psi-Jack: There is now a configuration parameter that will turn it off globally
19:00 dave_den forrest: heh, it is definitely a feel-good avatar.
19:00 cro I put it in but I can't remember what I called it :-)  Let me go see.
19:00 forrest I just imagine him going 'YEA, GO CODE!'
19:00 Psi-Jack {%- if ... %} and {%- endif %} appropriately?
19:00 mpanetta Quick question, is there any way to get a salt-minion to update its pillar and grains without a hard restart (IE service salt-minion restart or equiv)?
19:01 dave_den Psi-Jack: yep
19:01 dave_den mpanetta: saltutil module.
19:01 Psi-Jack cro: Yeah, don't /need/ it globally. :)
19:01 dave_den mpanetta: http://docs.saltstack.com/ref/modules/all/salt.modules.saltutil.html
19:01 forrest Psi-Jack, here's more on whitespace control if you're interested http://jinja.pocoo.org/docs/templates/#whitespace-control
19:01 mpanetta dave_den: Thanks!
19:01 cro jinja_trim_blocks and jinja_lstrip_blocks in /etc/salt/master
19:02 mpanetta dave_den: That exists in 0.16.4 correct?
19:02 dave_den mpanetta: yes, it should
19:02 mpanetta dave_den: awesome.
19:02 brianhicks joined #salt
19:03 dave_den cro: since you're here, just checking to see if you got a ping from git on my maxrunning comment: https://github.com/saltstack/salt/commit/f6b7ae4e10491a1db910f5068155268ce51cfa47
19:03 dave_den i know you're probably pretty busy
19:04 cro dave_den: Thanks, I missed that.  I went back and forth on that--but you are probably right
19:05 dave_den i figure the purpose of maxrunning is to prevent fork bombs as discussed on the salt-users list, so we should make it enforcing by default.
19:06 matanya joined #salt
19:06 cro That was kind of a side-effect--I was actually fixing a bug whereby a dead master could cause 100s of minion processes to pile up
19:06 cro But it needed to be done anyway
19:07 cro Yes, I'll switch the default.  Thanks again for bringing it to my attn.
19:07 morganfainberg left #salt
19:08 dave_den cool. thanks for doing it :)
19:08 bhosmer joined #salt
19:08 druonysus joined #salt
19:08 druonysus joined #salt
19:08 micah_chatt joined #salt
19:09 mpanetta dave_den: Is there a way to call the saltutil salt module from a state file?
19:09 dave_den mpanetta: http://docs.saltstack.com/ref/states/all/salt.states.module.html
19:10 jrdx joined #salt
19:10 dave_den mpanetta: although beware that you probably won't have access to the new grains/pillar data in the same state run.
19:10 jrlorence joined #salt
19:11 mpanetta dave_den: Thank you for the link!
19:11 dave_den the pillar/grains/salt dicts are compiled before the state run is actually executed.
19:11 mpanetta Ok good to know.
19:11 mpanetta I don;t think that matters for what I want to do.
19:11 dave_den cool, then yeah saltutil from module.run/wait should work.
19:14 th3reverend joined #salt
19:18 matanya joined #salt
19:23 jacksontj joined #salt
19:27 ksalman_ can i do smething like this? salt-ssh --grain 'os:Debian' cmd.run 'cat /etc/issue'
19:28 ksalman_ it just returns without any output
19:31 NotreDev i want to compile source unless a bin exists: easy enough. however, i don't want another state to execute unless that same bin exists. so a require on the first state wouldn't work - it would only execute the first time when the bin is compiled. how can I order this?
19:33 jaustinpage_ joined #salt
19:34 oz_akan_ joined #salt
19:35 mpanetta dave_den: Ok, I found out why we are restarting salt-minion instead of using the saltutil module...  We are putting grains/pillar data in to the minion config file.  Is this necessary?
19:36 jlorence joined #salt
19:36 dave_den mpanetta: is what necessary?
19:36 dave_den NotreDev: you can use if/unless.
19:37 dave_den for cmd.run states.. i think global if/unless is still in the works.
19:37 bemehow joined #salt
19:37 mpanetta dave_den: For the grains/pillar data to be in the minion config.  In other words, can we move it somewhere else?
19:37 bemehow joined #salt
19:38 dave_den mpanetta: yeah the pillar data should be on the salt master, and you can write custom grains modules that reside on the master that are synced to the minions on startup or with saltutil
19:40 mpanetta dave_den: Are there any docs you can point me to that describes how to do this?
19:41 dave_den mpanetta: http://docs.saltstack.com/topics/targeting/grains.html#writing-grains
19:41 NotreDev dave_den: yeah, i can build a bin unless it already exists, that's fine. but if i want to execute another state afterwards, regardless of whether the build needed to happen, I don't understand how to do that
19:42 NotreDev except {'order': 'last'}
19:42 mpanetta dave_den: Thank you!
19:42 dwyerj is this the correct way ? http://pastebin.com/VuxQWKpk
19:42 dwyerj for what i am trying to do with ntp ?
19:43 dave_den NotreDev: if you have if/unless in state x, and state y requires state x, then if state x's 'unless' is satisfied, it is still considered successful and state y will will run
19:44 NotreDev dave_den: oh ok. thanks
19:45 dave_den dwyerj: what are you trying to do?
19:45 dwyerj yum install ntpd, force ntpd to update, then enable it
19:45 dwyerj sorry the package, is ntp not ntpd
19:47 dwyerj .
19:48 tty-1 joined #salt
19:49 dave_den dwyerj: try this: https://gist.github.com/dlanderson/fb48f295e2e8a60c2bba
19:49 dwyerj thanks dave_den, is there anywhere that just has a bunch of examples of different states?
19:49 dave_den dwyerj: i just updated the gist to add a require for service.running.
19:50 dwyerj is that the require: -pkg: ntpd ?
19:50 dave_den dwyerj: https://github.com/saltstack-formulas
19:50 dave_den yes
19:50 dwyerj thanks
19:51 mannyt joined #salt
19:53 dave_den ksalman_: i haven't tried tergating with salt-ssh except by using id globbing, sorry
19:53 dave_den targeting
19:53 ksalman_ alrighty
19:53 ajw0100 joined #salt
19:55 zandy joined #salt
19:57 pentabular joined #salt
19:57 pentabular left #salt
19:59 quickdry21_ joined #salt
20:01 xmltok joined #salt
20:04 fishpen0 joined #salt
20:04 cro dave_den: That fix is in develop now.
20:04 NotreDev `unless: stat /usr/local/sbin/mybin` doesn't seem to be proper usage on file.run?
20:04 dave_den cro: sweet, thanks!
20:05 dave_den NotreDev: if/unless is for cmd
20:07 fishpen0 joined #salt
20:08 troyready joined #salt
20:09 d0ugal left #salt
20:11 JulianGindi joined #salt
20:11 fishpen01 joined #salt
20:13 rgarcia_ joined #salt
20:13 NotreDev dave_den: sorry, that's what i meant. post-lunch food coma over here
20:13 bhosmer joined #salt
20:14 NotreDev my states are still executing. i'm wondering if while `stat...` doesn't return "false" if it's response is interpreted as untrue
20:14 dave_den if/unless goes by retcode
20:15 reuss joined #salt
20:15 modafinil Are there any existing alternate backends to pillar? (Git or a DB, for example)
20:15 dave_den so to check to see if /tmp/blah exists:   - unless:  "[ -e /tmp/blah ]"
20:16 dave_den modafinil: yes, look for external pillars (ext_pillar)
20:16 modafinil cheers, thanks
20:18 modafinil i should write a zookeeper one... :)
20:19 NotreDev dave_den: and 0 is typically a success and 1 is typically an error. is 0 interpreted as false?
20:19 EugeneKay Ugh, I hate regressions.
20:20 EugeneKay I'm getting a PyYaml syntax error when using Pillar data with a "-quoted key name.
20:21 dave_den NotreDev: 0 is true.
20:21 NotreDev dave_den: thanks agin :)
20:21 dave_den NotreDev: no prob. :)
20:22 dave_den EugeneKay: have you tried using '<' ?
20:22 EugeneKay I have not
20:23 dave_den e.g.  some_pillar_data: <"this will not be interpreted by yaml"
20:23 EugeneKay It's the key I'm trying to quote, not the data
20:23 mannyt joined #salt
20:23 EugeneKay the key has a : in it(it's a network interface alias name)
20:23 dave_den same thing.
20:24 dave_den - <"my_key":
20:24 EugeneKay iNope, same error.
20:25 * EugeneKay fiddles
20:26 EugeneKay oooh, new error. I'll chase this
20:26 dangerousbeans joined #salt
20:26 dangerousbeans left #salt
20:26 druonysus joined #salt
20:27 jacksontj joined #salt
20:28 EugeneKay New approach: put the name bit as a property, and assign a friendly name to the interface
20:29 dzen joined #salt
20:29 dzen hello
20:31 zwevans joined #salt
20:32 dzen Is it possible to define the help required for a module using the CLI
20:32 dzen I mean
20:32 dzen salt --help pkg
20:32 dzen salt --help pkg.install
20:32 zwevans left #salt
20:32 dzen oh, -d
20:33 [diecast] joined #salt
20:34 EugeneKay Annnnd of course I was barking up the wrong tree. Sigh.
20:36 dave_den EugeneKay: what was it?
20:36 EugeneKay Still trying to sort it out. Looks like I'm using a syntax wrong somewhere, and that is NOW being caught - wasn't before.
20:37 jaustinpage_ joined #salt
20:37 dave_den ah
20:41 EugeneKay And the error message was showing me the wrong bit :-|
20:41 opapo joined #salt
20:42 NotreDev joined #salt
20:45 EugeneKay So here's the problematic pillar. https://gist.github.com/EugeneKay/91b294366cb690021056
20:45 _ikke_ Ah, nothing as fun as a misleading error message
20:45 EugeneKay Uncommenting lines 21&22 lead to an error: expected ',' or '}', but got '<scalar>'
20:45 EugeneKay (or either of them)
20:45 d0ugal joined #salt
20:46 _ikke_ does line 21 miss a ,?
20:46 EugeneKay It does now because I'm angrily editing it.
20:46 _ikke_ ok
20:48 EugeneKay Same results with that fixed
20:48 EugeneKay And no clue why 22 is failing at all
20:49 _ikke_ Seems like a yaml error?
20:49 EugeneKay That's what it smells like, but AFAIK that's valid YAML, and it worked pre-0.17.1
20:49 mannyt joined #salt
20:50 oz_akan_ joined #salt
20:51 EugeneKay And now I'm tearing out my hair. Kicked over salt-minion, and it's working with #21... but #22 gives problem.
20:51 EugeneKay (yes, I've been refreshing my pillar data to the minion)
20:51 _ikke_ YAMLLint says it's valid
20:52 dave_den EugeneKay: setting log_level to garbage might help. it will show all rendering being done
20:52 oz_akan_ joined #salt
20:52 EugeneKay Setting that where?
20:52 dave_den EugeneKay: log_level in minion config
20:53 Linz joined #salt
20:54 Gareth this looks interesting https://github.com/davidhalter/jedi-vim
20:55 zandy joined #salt
20:56 NotreDev here is a very simple test state that doesn't function as i'd expect (cmd.run's unless) http://pastebin.com/Wt7PSze4
20:56 EugeneKay And now I scream.
20:56 _ikke_ EugeneKay: Do tell
20:56 _ikke_ Gareth: Seems nice
20:56 EugeneKay I was doing something stupid in a different place.
20:56 _ikke_ Gareth: (curiosity, were you interviewed on FLOSS Weekly?)
20:57 EugeneKay calling network.items() somewhere that didn't really need it
20:57 EugeneKay No idea what changed still
20:58 _ikke_ Gareth: n/m, was someone else
20:58 cdcalef joined #salt
21:00 d0ugal left #salt
21:00 Gareth _ikke_: I was a few years ago, now I'm an occasional co-host.
21:00 Gareth brb.
21:00 elsmorian joined #salt
21:01 _ikke_ Gareth: Ah, that's why the name sounded familiar
21:01 Ryan_Lane1 joined #salt
21:01 dave_den NotreDev: if/unless is only implemented in cmdmod.
21:02 NotreDev yep, fixed it
21:02 NotreDev thanks
21:02 NotreDev i don't know why i keep mixing up file and cmd
21:03 dave_den heh
21:04 jimallman joined #salt
21:09 Ryan_Lane joined #salt
21:10 joehoyle joined #salt
21:12 sroegner_ hi there: how do i use the pkg state on the cmd line?
21:12 sroegner_ can't seem to figure it out
21:13 sroegner_ it always asks a third argument
21:15 ajw0100 joined #salt
21:15 forrest sroegner_, use salt 'minionName' pkg.install pkg_name
21:16 dzen sroegner_: # salt --doc "target"  pkg
21:19 ipmb joined #salt
21:19 cewood joined #salt
21:20 berto- joined #salt
21:21 sroegner_ thanks
21:21 berto- Does salt's event system fire an event for minions that connect and disconnect?
21:22 forrest I'm really gonna have to stop submitting issues while I'm at work that I intend to fix when I get home, Tom keeps fixing them.
21:23 berto- forrest: fyi, i added the --pillar-root command line arg last week.
21:23 forrest berto-, ahh nice! Yea I totally spaced it.
21:26 dave_den berto-: a minion fires a 'minion_start' event on the master at startup. there is no event for shutting down yet
21:26 dave_den that i know of.
21:27 _ikke_ There would need to be some kind of timeout on the master in case the minion got disconnected somehow
21:29 berto- dave_den: ok, thanks.  I would love to have an event for minion_stop as well.  i'll see if there's an issue for that.
21:30 druonysus joined #salt
21:31 Katafalkas joined #salt
21:33 berto- dave_den: it's an existing issue: https://github.com/saltstack/salt/issues/6794
21:34 joehoyle joined #salt
21:49 Damoun joined #salt
21:52 pmrowla joined #salt
21:53 vitaliyf joined #salt
21:55 KFDM joined #salt
21:55 zandy joined #salt
21:57 th3reverend hey guys; i'm trying to start salt-master on a macbook without su, and i get a permission denied error trying to create path /etc/salt/pki/master even though i'm passing salt-master -d -c ~/salt.  is that a known issue or am i trying to do something that is not intended to be supported?
21:58 mag_ joined #salt
21:58 th3reverend i don't have a master config file... nor can i find any documentation online as to what should be in a master config file.
21:58 xmltok joined #salt
21:59 dwyerj http://docs.saltstack.com/ref/configuration/master.html
21:59 dwyerj but you only really need interface:
21:59 dwyerj there is an example of a master config there also
22:01 th3reverend yeah i found that... and i actually got salt-master to read the config file, but it still says failed to create the etc/salt folder... wierd
22:01 th3reverend seems like it tries to create etc/salt/pki/master no matter what
22:02 bhosmer joined #salt
22:02 Pikachu320 left #salt
22:03 teskew salt-cloud .8.10 is still not compatible with .17.2 ...i thought the .8.10 release of salt-cloud was supposed to fix that after the update of salt core to .17.2
22:03 xmltok joined #salt
22:04 bemehow joined #salt
22:06 dwyerj you wont have permissions to create anything in /etc if you are just running it as a regular user. have you tried setting the file
22:06 dwyerj the file_roots
22:07 forrest file_roots is where it looks for stuff like your top file, the /etc/salt/pki/master has to be created for key auth.
22:12 th3reverend so you can't run salt-master without permissions on /etc/salt/*
22:13 dwyerj why cant you chown /etc/salt to the user you are trying to run as ?
22:13 forrest Correct: http://docs.saltstack.com/topics/nonroot.html
22:13 jslatts joined #salt
22:13 forrest dwyerj, you totally could, that is what the docs suggest.
22:14 th3reverend dwyerj: i can, but i don't want to. i thought passing -c ~/salt i could change the default salt root
22:14 Ahlee th3reverend: For clarification, are you specifying ~/ or /path/to/home
22:14 th3reverend Ahlee: i've tried both
22:15 forrest that -c option might be specifically for the configuration file itself, and not the pki dir, as minion keys will need a place to go when they are created. I'm not familiar enough with that option to say 100% though
22:15 th3reverend it seems to work as far as finding the master config file, but it still wants to go to /etc/salt for some other reason, probably for storing keys?
22:16 dwyerj have you chowned /var/cache/salt and /var/log/salt ?
22:16 terminalmage th3reverend: if you're running your conf dir outside of /etc/salt, set root_dir
22:16 th3reverend so is there something i can put in the config file to change the salt root?
22:16 terminalmage th3reverend: ^^^^^
22:17 th3reverend terminalmage: hehe yeah
22:17 terminalmage root_dir will then be prepended to things like the cachedir, pki dir, etc
22:17 dwyerj yeah root_dir
22:17 terminalmage that's how I run salt in a virtualenv
22:17 dwyerj is it worth explicitly stating the user, with either -u or in the config ?
22:18 Brew1 joined #salt
22:18 bemehow_ joined #salt
22:19 th3reverend ok i got the master to start without errors, but i can't find it in PS
22:19 melinath akoumjian (or anyone) have advice on this error message? "Specified SLS deploy in environment base is not available on the salt master"
22:19 melinath using salt-call --local with the latest git.
22:19 melinath latest commit, rather.
22:19 Ahlee For anybody curious, it doesn't appear you can limit root's ability to run commands via client_acl :(
22:19 forrest does the sls you're trying to use exist on the server?
22:20 melinath forrest: yes, and salt seems to be compiling it, when I look at the debug
22:20 forrest th3reverend, https://github.com/saltstack/salt/issues/8649 created to get the documentation updated.
22:20 dwyerj are you running salt-master in teh foreground ?
22:20 melinath salt setup I'm using is here: https://github.com/pculture/mirocommunity-salt
22:21 melinath dwyerj: yes.
22:21 th3reverend dwyerj: no i used daemon
22:21 melinath ... you were both not talking to me, were you... :-p
22:22 dwyerj haha sorry, i need to learn irc commands. was to th3reverend
22:22 forrest heh
22:22 forrest melinath, do you have any weird requires in there that might not exist?
22:22 forrest as in, can you run a single state and that works?
22:22 dwyerj reverend, set the log level to all, and run in foreground
22:22 forrest or can you create a new very simple state and that works?
22:22 forrest that won't hit him dwyerj
22:23 forrest or at least 'ping' him
22:23 th3reverend dwyerj: thanks for the help... i need to setup some more stuff tomorrow... as for now i'm being dragged to happy hour.  such is the life of a developer.  sigh.
22:23 forrest developer?? are you on macosx?
22:23 dwyerj hahahaha
22:24 th3reverend yeah i'm on macos, but i dev the underarmour.com ecommerce site.
22:24 forrest th3reverend, are you trying to set up a local instance of salt to play with?
22:24 forrest or on a server?
22:24 th3reverend forrest: local play; need to evaluate it for possible use in our cloud deployments
22:25 melinath forrest: run a single state? could you clarify? I don't know how I'd do that, unless you just mean replacing my state tree with a simple do-nothing file.
22:25 forrest th3reverend, if you have time, can you try this tutorial?
22:25 forrest http://docs.saltstack.com/topics/tutorials/walkthrough_macosx.html
22:25 forrest BenBen pushed that, so I'm curious regarding how it works for others, or if there are issues that could be cleared up. Granted you might want to modify some of it to run as an unprivileged user
22:25 th3reverend forrest: yeah i found that grepping the git repo.  looks good.  i already broke from that script by installing stalkstack with brew instead of pip
22:26 th3reverend forrest: but either way there is nothing in there about SU or SUDO in fact it says don't use SU/SUDO
22:26 druonysus joined #salt
22:26 druonysus joined #salt
22:26 Corey th3reverend: YES!
22:26 Corey SOMEBODY IS USING IT!
22:26 forrest Corey, ?
22:26 Corey (Sorry, I spent a week shoehorning saltstack into homebrew)
22:26 th3reverend ok guys i'll peek back in here tomorrow and i'll give feedback on the macos walkthrough
22:26 th3reverend gotta  go
22:27 forrest thanks, let me know and I'll work on updating it
22:27 forrest Corey, can you create an issue/pull request to installing Salt with brew on that doc and I'll get it updated? Unless it's just brew install, I just need to know if there is anything after that which is different (a non-priv section would be good to add)
22:28 forrest melinath, so you're doing salt-call --local state.highstate right now?
22:28 carmony Corey: wait, saltstack is in homebrew now?
22:28 Corey forrest: Yeah, that just gets it installed. Getting it actually *working* is probably still accurate.
22:28 melinath forrest: yes.
22:28 Corey carmony: Yes indeed.
22:28 * carmony goes to test
22:28 Corey carmony: See my email earlier today in reply to the release announcement.
22:28 * carmony is a big homebrew fan
22:28 forrest carmony, http://docs.saltstack.com/topics/tutorials/walkthrough_macosx.html
22:28 Corey carmony: Note that it's saltstack, not salt.
22:28 forrest go through that after installing with homebrew :P
22:28 Corey carmony: And --HEAD does what you'd expect.
22:28 forrest and let me know what needs to be updated so I can modify the section
22:29 forrest melinath, so you have a single simple state, you can just call salt-call --local state.sls nameOfState
22:29 forrest so if you want, make something super simple, like echo 'test' > /tmp/testfile:\n  cmd.run
22:29 forrest then run that state to see if it works
22:30 melinath forrest: Okay, yes. I can run a simple state.
22:30 forrest carmony, or better yet make a pull request since you actually have a mac
22:30 forrest melinath, cool
22:30 forrest I just want to see if states in general are working
22:31 forrest Corey, why did you name it saltstack?
22:31 forrest and does that install both the minion and master?
22:31 forrest my brew knowledge is very limited
22:31 Corey forrest: Yes, and "because salt was taken"
22:31 Corey Not in that order.
22:31 forrest yea I figured
22:31 Corey forrest: Find and kill the guy who runs http://supernovae.in2p3.fr/~guy/salt/ and we're good.
22:31 forrest so you didn't want to create salt-master, and salt-minion, and salt-common?
22:32 Corey forrest: I wasn't entirely sure it'd be accepted as it is.
22:32 Corey I can modify it, but it's not going to be separate formula. It would instead take arguments.
22:32 forrest ahh ok
22:32 forrest and this guy has a contact link on his page :P
22:32 forrest did you email him?
22:32 Corey So we'd need to come to some form of agreement on which "brew install saltstack" installs. And what the flags would look like. :)
22:33 Corey Remember we've also got a syndic.
22:33 forrest yea
22:33 forrest I'm not disagreeing with what you named it, just curious
22:33 forrest julien.guy@lpnhe.in2p3.fr is the dude's email
22:33 forrest I don't like that domain name :(
22:33 Corey I'm not even sure what I'd ask him. :-)
22:34 Corey "HEY YOU. I'D LIKE YOU TO INTRODUCE A NAMING CHANGE TO YOUR PROJECT BEFORE I INTRODUCE A BAT TO YOUR FACE."
22:34 forrest Dear sir, it appears that you have not worked on this brew package in 3 years, could you please rename it? do the needful.
22:34 Corey "And if you have a problem with that, my name is UtahDave and I can be reached at..."
22:35 Corey He's also not the guy who wrote the package I suspect.
22:35 Corey It's... politics.
22:35 forrest lol
22:35 forrest that would be funny if he emailed UtahDave
22:37 Corey Sure. Unless you're utahdave.
22:38 KFDM left #salt
22:41 forrest I'm sure he'd think it's funny
22:41 forrest maybe
22:44 BenBen joined #salt
22:45 alunduil joined #salt
22:46 forrest BenBen, someone was already using the macosx tutorial, but they installed saltstack straight from brew now that it's supported, figured you'd want to know :D
22:47 BenBen Hi there, i've got a quick question regarding environments such as "base" , "qa", "prod", in sls files : This tutorial http://salt.readthedocs.org/en/latest/topics/tutorials/states_pt4.html , shows an example of promoting a serving in each environment (from dev to qa to prod). But my queston is this : in that case, does it suppose that the machine on which the salt-master daemon is installed has access to the three enviroments (dev, qa
22:47 BenBen forrest: great !
22:47 forrest and Tom also updated that command combo that you brought up earlier
22:47 BenBen forrest: yeap, that was a typo, but it's a really handy shortcut and it's not very well known.
22:48 forrest yea I know, when I was modifying the docs the first time I remember you saying the command was wrong but couldn't remember what it was, google was not helping me find it
22:48 forrest everyone was modifying settings
22:49 BenBen forrest: actually that's what i did before, but since maverick it has become a little bit more cumbersome
22:49 BenBen forrest: .. i think.. I'm not even sure. Or maybe i stumbled accross this shortcut when i was looking for the line to modify settings
22:50 forrest seems dumb people would be saying how to do it via settings, but not the shortcut itself
22:50 BenBen To continue my question : i would have thought that in a typical production environment, the salt-master daemon was in production as well, but in a complete isolation from the QA and DEV environment.
22:51 foxx[cleeming] joined #salt
22:51 foxx[cleeming] joined #salt
22:51 heewa forrest: Hmm, I guess that's better than a face that makes you puke, so I'll take the compliment!
22:52 forrest Haha, no I mean it is odd people would provide all the command changes, but not the simple command as well for a quick fix.
22:52 forrest BenBen, it depends how you run the environment, since you can easily segment out different file_roots in salt for different environments, you don't really have to do that.
22:53 BenBen forrest: ok. I guess my case is a bit different, since i basically only have two environments : dev is on my local machine, and prod is on EC2
22:53 Linz joined #salt
22:53 forrest Yea for you it makes sense to have two different masters
22:53 BenBen i don't think it would be wise to use my mac for both the local VM and my EC 2 servers
22:54 forrest most people when running in a private cloud or something don't need to do so, because they are on the same network
22:54 forrest no I don't think it would be either
22:54 BenBen hmm
22:55 zandy joined #salt
22:55 forrest One master per environment like you are doing is a good plan, the only thing I might consider is pushing to a central git repo for your states, then you can easily push and pull them between environments, as well as easily run branches of stable versus unstable code for testing in your EC2 instance.
22:55 BenBen I tried to keep my dev environment very close to my production, in order to be able to reuse all my sls files. I only need to change a few settings on pillars. But then i'm stuck with how I should split those files between enviornments
22:56 kermit joined #salt
22:56 BenBen forrest: ok... Maybe a separate git just for the tls files would be wise indeed..
22:56 BenBen i mean split those settings, not files..
22:56 forrest Yea you could always keep the pillars on one branch, but the sls files in a main branch, or use multiple repos, there are a lot of ways around it.
22:57 BenBen hmm
22:57 forrest the way I have it configured is that my whole repo starts at /etc/, and then the pillar, and salt dirs are checked in to git
22:57 Ahlee cro: I'm sitting here with terminalmage and I hear you are who I should be pestering for info regarding switch _runner's
22:57 BenBen actually, i was thinking about using environment withing my pillar sls files
22:57 forrest so I just pull them down into etc, and get my updates, probably not the best plan (they should be apart more probably), but it works for the small project it is on.
22:57 BenBen pillar/tops.sls => dev : and prod:
22:58 forrest BenBen, environments are a great idea
22:58 BenBen Yeap, but then i don't know how to use them :)
22:58 forrest Hah, you've gotten this far I'm sure you can figure out one more slice!
22:58 BenBen I mean, what rule should i set
22:58 forrest ahh gotcha
22:59 BenBen relying on minion names seems a bit too light
22:59 BenBen such as 'dev_*':
22:59 BenBen that's dangerous..
22:59 BenBen i don't know why, but i don't feel like it's safe..
22:59 forrest yea, I'd probably create node groups: http://docs.saltstack.com/topics/targeting/nodegroups.html
23:00 BenBen forrest: interesting..
23:01 BenBen forrest: looks much better indeed..
23:01 forrest yea, you can use the compound matchers there, so you can specifically match on subnet/IP etc.
23:01 BenBen forrest: ok, nice
23:02 BenBen Well, it seems like i know have no excuse to postpone deployment on EC2 anymore :))
23:02 forrest lol
23:02 BenBen i now have
23:02 forrest carmony, any luck with the brew install?
23:02 BenBen oh, one more thing : do you know if killing the VM that will be my "production master" will have any impact on the production minions ?
23:03 rawzone joined #salt
23:03 forrest BenBen, in what sense? Obviously they will be unable to contact the master, but for the running of other services? Not as far as I know
23:03 BenBen should i keep it alive, or can i stop it / resume it and will the minions be able to reconnect automatically ?
23:04 BenBen i don't want to pay for that VM when i don't have any command to issue
23:04 hazzadous joined #salt
23:05 forrest oh, well, the minions will probably be trying to poll, the master, so I don't know how that would work security wise. It might be one of those things where you want to modify the minion config in some sense to reduce that, but I'm not sure what you'd change exactly. I assume you'd simply turn the VM off, but not delete it right? I'd be scared if someone else got my IP, and saw that some minions were polling that server.
23:05 BenBen I've tried it localy, and killing the master and restarting it seem to work, but i want to make sure it's a feature..
23:05 alunduil joined #salt
23:05 BenBen forrest: sure, stopping it only.
23:05 BenBen i want to keep the ip
23:06 forrest Yea, it should work then, like I said though the polling might be a concern. Maybe it's one of those things to consider salt-ssh for?
23:06 BenBen forrest: i was wondering about salt-ssh indeed
23:06 forrest yea all your existing salt states will work with it just fine
23:06 forrest so if you're planning on doing it that way, salt-ssh might be a better option
23:06 BenBen in which case i would use my mac to issue the commands..
23:07 forrest Yep you could do that.
23:07 BenBen and have no master at all nor minions in production, right ?
23:07 forrest right, your laptop would be the master, and all the salt stuff is taken care of over ssh, so no salt service installed on the minion
23:07 BenBen hmm
23:07 forrest only concern there is speed, but I'm sure a few seconds is no big deal
23:07 BenBen no, indeed
23:07 forrest it would be worth testing for sure, just to try and keep things as tight as possible.
23:07 carmony so I did a brew install saltstack
23:07 BenBen yeap
23:08 carmony and I don't have any of the files in place in my /usr/local/bin
23:08 BenBen carmony: : does brew doctor gives you any info ?
23:09 BenBen sometimes the linking phase conflicts
23:09 BenBen and it's rolled back completely
23:10 carmony BenBen: https://gist.github.com/JustinCarmony/b1ea4420b2eb3483a6a9
23:10 BenBen forrest: which doc is the most accurate : readthedocs or doc.saltstack ?
23:10 forrest BenBen, they are identical
23:10 forrest use docs.saltstack.com though so the SEO data pushes it further up, lol
23:11 BenBen carmony: you do have a lot of conlicts indeed
23:11 carmony I think it is from an old pip install
23:11 BenBen carmony: yeap
23:11 __number5__ forrest: I've made docs.saltstack.org one of my startup pages :)
23:11 forrest hah
23:12 BenBen carmony: once you're using brew, you need to use it for everything python related as well
23:12 jkyle joined #salt
23:12 forrest yea I always hate when read the docs is the first link, while the CSS is better, I still like the simplicity of the docs.saltstack site better.
23:12 BenBen carmony: doesn't mean you can't pip install, but you need to make sure you're pip-installing from the pip that was installed by brew
23:12 BenBen forrest: honnestly, kill one. it's extremely confusing
23:13 carmony BenBen: should I brew install python first?
23:13 BenBen carmony: i suppose brew install saltstack installs python as a dependency
23:13 carmony BenBen: it actually didn't for me
23:13 jkyle carmony: you can use system python. . . I'd say virtualenvwrapper will keep you saner than a brew instal of python
23:13 BenBen carmony: yeap, i just saw that in the logs
23:14 forrest BenBen, Yea that isn't up to me. I don't know what the salt guys plan honestly.
23:14 BenBen carmony: you do seem to have a saltstack installed from pip
23:14 mgw I'm thinking about an execution function that would download a remote (http) iso, md5 it, and mount it.
23:14 jkyle brew installs of python can get a bit kludgy and even cause breakage in the system tools. mostly because they're library paths overlap with system paths (an oddity of the osx python default compile options)
23:14 BenBen carmony: i would pip uninstall it first
23:15 mgw should there be a file.get_http function?
23:15 Corey carmony: Disclaimer: "brew install saltstack" works under the /usr/local tree; it may get very, very angry if you've already mucked about with salt manually in that environment.
23:15 BenBen carmony: from what i see in your log, that should be enough
23:15 carmony Corey: yup, I think you're right
23:18 Corey Oh hey, there's a log?
23:19 BenBen Corey:  in the gist carmony send above
23:19 BenBen Corey:  in the gist carmony sent above
23:19 carmony I had tried a pip install before
23:19 carmony based off of a brew python
23:20 carmony but I've done a ton of stuff in there before, so I actually just nuked that directory and re-installed the few brews I use regularly
23:21 alunduil joined #salt
23:21 carmony but having the saltstack forumla will make it easy to do a demo of salt-ssh
23:22 Corey carmony: Ah, there we go.
23:22 Ryan_Lane1 joined #salt
23:23 Corey carmony: rm -rf /usr/local/lib/python2.7/site-packages/salt
23:23 carmony yup
23:23 Corey carmony: rm -rf /usr/local/share/man/man1/salt*
23:23 carmony the brew link --overwrite worked
23:23 Corey carmony: Trust me on this.
23:23 Corey :-)
23:23 Corey There may be things in there that didn't get overwritten.
23:23 Corey This could mean tears before bedtime.
23:23 Corey rm /usr/local/share/man/man7/salt.7
23:24 Corey *THEN* brew link saltstack
23:25 carmony Corey: that worked :)
23:25 Corey Yay.
23:25 Ahlee Corey: you got a link to that blog post you wrote a while back?
23:25 carmony k, I'm out
23:25 carmony later :)
23:25 Corey Ahlee: Sure. http://blog.taos.com/2013/11/19/dns-resolution-a-primer/
23:25 Ahlee was going after the salt vs puppet one
23:26 Corey Ahlee: Ah, you mean http://blog.smartbear.com/devops/a-taste-of-salt-like-puppet-except-it-doesnt-suck/
23:26 forrest later carmony
23:26 Corey Sorry, I kinda write a bit.
23:26 danielbachhuber joined #salt
23:26 Ahlee dar she be
23:28 forrest It just looks like a lot of text because of the commandline formatting Corey :P
23:29 mgw is there a current state module that can download and md5 a file from an http server? I'm not finding one...
23:29 forrest mgw, will file.managed not work?
23:29 forrest http://docs.saltstack.com/ref/states/all/salt.states.file.html#salt.states.file.managed set the source, set the source_hash. ?
23:30 mgw forrest, I didn't realize it took an http scheme
23:30 mgw but I guess it would, since it takes file: and salt:
23:30 forrest oh ok cool
23:30 mgw which is why I asked, before I went reinventing the wheel :-)
23:30 mgw thanks
23:31 forrest np
23:31 bemehow joined #salt
23:32 micah_chatt joined #salt
23:34 Thiggy joined #salt
23:37 Ryan_Lane joined #salt
23:45 bemehow_ joined #salt
23:47 [diecast] joined #salt
23:50 bhosmer joined #salt
23:52 dwyerj for adding something like rpmforge to yum on centos, should i use salt.states.pkgrepe? or just roll my own with cmd.run etc
23:54 joehoyle joined #salt
23:54 dwyerj example of rolling my own would be something like : http://pastebin.com/qKEXPUjXhttp://pastebin.com/qKEXPUjX
23:55 dwyerj im trying to do it with pkgrepo, but so far no luck
23:55 zandy joined #salt

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary