Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-10-23

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

All times shown according to UTC.

Time Nick Message
00:01 cshuman joined #salt
00:14 dthom91 joined #salt
00:15 andredublin joined #salt
00:15 jslatts joined #salt
00:15 pipps joined #salt
00:15 andredublin joined #salt
00:17 andredublin left #salt
00:18 Gifflen joined #salt
00:27 mannyt joined #salt
00:30 justlooks joined #salt
00:31 woebtz joined #salt
00:32 wkf joined #salt
00:40 juicer2 joined #salt
00:52 austin987 joined #salt
00:55 foxx joined #salt
00:55 foxx joined #salt
00:57 pentabular joined #salt
00:59 foxx[cleeming] joined #salt
00:59 foxx joined #salt
01:04 Snow-Man Gareth: thanks!
01:05 Snow-Man Gareth: and, yes, I imagine there would be.. :)
01:07 pabelanger left #salt
01:09 druonysus joined #salt
01:09 sfz joined #salt
01:10 redondos joined #salt
01:10 jslatts joined #salt
01:13 mafrosis joined #salt
01:13 dthom91 joined #salt
01:14 mafrosis any salt devs about?
01:14 mafrosis lo :)
01:17 mua joined #salt
01:17 dthom91 joined #salt
01:17 cshuman joined #salt
01:17 rgbkrk joined #salt
01:19 ctdawe joined #salt
01:21 mgw joined #salt
01:25 Lue_4911 joined #salt
01:33 Lue_4911 joined #salt
01:33 packeteer they're usually on at the other end of the day
01:34 ajw0100 joined #salt
01:39 drinking joined #salt
01:44 tyler-baker joined #salt
01:56 cshuman joined #salt
01:58 drinking joined #salt
01:58 Drawsmcgraw joined #salt
02:01 xinkeT joined #salt
02:02 pentabular joined #salt
02:05 Furao joined #salt
02:06 Tekni joined #salt
02:06 jslatts joined #salt
02:12 Furao joined #salt
02:14 JPmx joined #salt
02:14 xinkeT joined #salt
02:15 ajw0100 joined #salt
02:15 pentabular joined #salt
02:16 mafrosis packeteer: thanks
02:16 Furao joined #salt
02:16 mafrosis I'm not a regular on here, and I normally manage to miss everyone ;)
02:17 pentabular joined #salt
02:20 Furao joined #salt
02:25 vipul joined #salt
02:28 ajw0100 joined #salt
02:28 xl1 joined #salt
02:31 Furao joined #salt
02:35 dthom91 joined #salt
02:38 pentabular joined #salt
02:39 Furao joined #salt
02:41 nmistry joined #salt
02:43 Gifflen joined #salt
02:44 pentabular joined #salt
02:45 Furao joined #salt
02:47 Furao joined #salt
02:49 Furao joined #salt
02:52 taylorgumgum joined #salt
02:59 Marion joined #salt
03:00 Marion jcockhren?
03:00 Furao joined #salt
03:01 Gifflen joined #salt
03:03 Furao joined #salt
03:03 smccarthy joined #salt
03:03 UtahDave joined #salt
03:04 modafinil what does this mean? "No Top file or external nodes data matches found"
03:06 Furao joined #salt
03:06 cachedout joined #salt
03:06 modafinil err i think i'm just being dumb, maybe figured it out
03:07 Marion in case you didn't : http://docs.saltstack.com/topics/tutorials/starting_states.html#the-top-file
03:08 modafinil yeah, i just have bad master config :)
03:08 UtahDave modafinil: yeah, by default you need a top file here:    /srv/salt/top.sls
03:08 Marion :-)
03:09 modafinil yeah -- im actually setting up the saltmaster config in salt, so i forgot to, like, put it in the right place also and not just in the to-be-pushed-out-config :D
03:09 modafinil thanks :)
03:10 akio joined #salt
03:11 akio I couldn't find it, but is there a minionless mode?
03:11 Marion yes, there in minionless mode
03:11 akio Its new right?
03:12 dthom91 joined #salt
03:12 Marion I'm new to salt myself, so I don't have all the answers off the top of my head, but I could direct you to where I found answers for myself in the documentation.
03:13 Furao joined #salt
03:15 cshuman joined #salt
03:15 __number5__ akio: masterless mode has been there for a while http://docs.saltstack.com/topics/tutorials/quickstart.html
03:15 Marion akio: in minion, set file_client: local
03:17 akio actually i was looking from something that doesn't use an agent on the target
03:17 akio i know a lot of functionality would be lost
03:17 akio i know of masterless
03:18 akio master controlling targets without a minion was what i was looking for
03:18 akio i suppose i could build a minion for things that don't have it in the repos
03:19 UtahDave akio: Ah, you're looking for salt-ssh
03:20 Furao joined #salt
03:20 akio From the man himself...
03:20 akio Awesome stuff you are working on!
03:21 UtahDave Thanks!  Tom's the genius, though.  :)
03:21 Furao joined #salt
03:22 akio Has that always been there or is that new from a recent version?
03:22 UtahDave akio: no, salt-ssh was just barely released in 0.17.0 with some refinements in 0.17.1
03:23 UtahDave It's very usable right now, but it is still undergoing polishing
03:25 Corey And that's a new laptop ordered.
03:25 Corey That reminds me, I need to start using salt-ssh so I can complain about it.
03:25 pentabular joined #salt
03:25 akio I would figure you would lose some of the functionality such as grain data.
03:26 UtahDave akio: nope!  You still have grains
03:26 pentabular joined #salt
03:26 UtahDave You lose the peer interface, the Salt Mine, I believe
03:27 UtahDave There are a few things that still need to be implemented, but salt-ssh was designed in such a way that most sls files can be used across your entire infrastructure
03:27 UtahDave both salt-ssh minions and traditional minions
03:27 ctdawe joined #salt
03:28 taylorgumgum joined #salt
03:28 UtahDave Corey: I would feel sad if we didn't get some complaints from you about salt-ssh!  :)
03:29 Furao joined #salt
03:29 Corey UtahDave: It takes too much typing, so I aliased it.
03:29 Corey Tab complete stumbles over salt-syndic.
03:29 Gifflen joined #salt
03:31 UtahDave lol
03:32 Corey Works well when aliased to "ansible"
03:33 UtahDave smh
03:33 pdayton joined #salt
03:33 UtahDave Corey: lol
03:35 akio Yeah. Thats what I am trying to avoid using. This project feels a lot more warm and cozy. I get scared off when the main page tries to sell you something.
03:35 Gareth w 3
03:35 Gareth erm
03:35 Corey Gareth: GET BACK TO APPROVING TALKS!
03:35 Corey akio: That's the fun part of Salt. The enterprise offering sells itself.
03:36 Gareth Corey: Not until after December 15th :)
03:36 akio And I like the halite freebie.
03:36 Corey "Extended support, and a stable release with backported patches" is GREAT for enterprises, but is overkill for folks who're likely to be found here.
03:36 UtahDave akio: yeah, all our code is Apache 2.0   We're not open core
03:36 Marion I have a weird problem that appears to be salt related … I have a vagrant/salt ubuntu/nginx setup.  It works fine on my macbook and the originator's (of this setup) macbook.  It does not run on my older iMac.  It seems to be crashing on the apt-get update.  I have several vagrant/puppet VMs that don't have a problem running on the iMac.
03:36 Corey UtahDave: Define "Open Core" plz.
03:37 UtahDave Corey: here's some good code that's "open source".  Here's some more stuff that would make it especially useful, but we're going to make you pay for the extra stuff
03:38 Furao joined #salt
03:38 jY Corey: puppet would be open core
03:38 akio And that creates a rift that keeps getting bigger.
03:38 Raymii joined #salt
03:39 UtahDave Corey: Is that what you consider open core?
03:40 Corey UtahDave: I'd not heard the term aside from Salt using it, so I wanted the definition from the horse's mouth.
03:40 Furao joined #salt
03:40 akio I hear it, and I dismiss quickly when I do.
03:40 Gareth Did you just call UtahDave a horse?
03:40 Corey Gareth: More a pony.
03:40 ctdawe joined #salt
03:40 UtahDave lol
03:41 akio brony
03:41 UtahDave Dang, I just got downgraded to a pony
03:41 UtahDave dang, now to a brony!
03:41 UtahDave I think this just keeps getting worse!
03:41 akio Unicorn?
03:41 akio Narwhal? Thats going up!
03:42 UtahDave I'd prefer Pegasus
03:42 akio Even more magical.
03:42 carmony lol
03:42 Gareth maybe a hippogriff
03:43 carmony Mwuahahaha, its alive!
03:43 Corey Well crap. "codepony" is taken on github. Else I'd have released a utahdave parody account.
03:45 taylorgumgum joined #salt
03:46 carmony Sweet, I've now provisioned on digital ocean and aws
03:46 UtahDave lol
03:47 UtahDave nice, carmony.  the digital ocean api came back later in the afternoon today.  They were having networking issues
03:50 carmony UtahDave: so when you do a training, how do you setup everyone's envs?
03:51 UtahDave we typically do everything on aws. I've used digitalocean once.
03:52 carmony so do you provision a setup for each attendee
03:52 middleman_ joined #salt
03:53 Furao joined #salt
03:55 UtahDave yeah, each attendee gets credentials to spin up all the vms they need for the course materials
03:55 UtahDave So they get a lot of experience using Salt Cloud early on.
03:55 UtahDave And can get comfortable creating and destroying their vms as needed
03:57 taylorgumgum joined #salt
03:57 Furao joined #salt
04:06 carmony UtahDave: nice
04:06 carmony I'm doing a 3.5 hour tutorial
04:07 carmony not sure how many people will be there
04:12 UtahDave nice! where at?
04:12 carmony TrueNorthPHP, conference in Toronto
04:13 UtahDave Ah, that's right. I heard you mention that
04:14 carmony I was thinking of having them each spin up a 3-vm salt setup
04:14 carmony via vagrant
04:14 webben joined #salt
04:14 UtahDave yeah, that's cool
04:15 UtahDave carmony: so it's 3.5 hours on Salt?
04:15 carmony up
04:15 carmony yup
04:15 UtahDave :) dang, you're awesome.
04:16 carmony well, managing your servers with salt :P So we'll be approaching it from a LAMP perspective
04:17 jfalco joined #salt
04:20 UtahDave sweet
04:25 cachedout joined #salt
04:26 carmony UtahDave: for salt-cloud and Rackspace, how do you do your ssh keys for it?
04:26 carmony I'm failing to provision
04:28 packeteer please tell me there will be a stream of the Conf?
04:28 packeteer for those of us on the other side of the world
04:28 carmony Um, I don't know if there will be or not :P
04:32 UtahDave We're still not sure if there's going to be a live stream.  We do plan on recording as much as possible.
04:32 \ask joined #salt
04:34 jalbretsen joined #salt
04:34 UtahDave carmony: I just set up my cloud.providers file like the example here: http://salt-cloud.readthedocs.org/en/latest/topics/rackspace.html
04:35 pentabular joined #salt
04:35 carmony yeah, I get an error
04:35 elfixit joined #salt
04:36 carmony UtahDave: https://github.com/JustinCarmony/vagrant-cloud/tree/master/saltstack/salt/master/files/etc
04:37 puffrfish left #salt
04:37 jalbretsen left #salt
04:38 UtahDave Oh, can you jinja in Salt Cloud configs?  I don't think you can.
04:38 carmony Its been working for me
04:38 UtahDave s/jinja/use jinja
04:38 carmony oh
04:38 carmony its because I manage them through salt
04:39 carmony so salt passes them through jinja and they are written out with the values in place
04:39 carmony so when salt-cloud reads them they have the values
04:39 UtahDave ah, ok.  I see.  Nice setup!  I like that
04:40 pipps1 joined #salt
04:40 UtahDave what's the error you're getting?
04:41 UtahDave carmony: Oh, did you see that developer offer rackspace has going right now?
04:41 mafrosis lo
04:41 carmony Nope, what offer?
04:41 carmony UtahDave: https://gist.github.com/JustinCarmony/4710e15f25ba1d4a7249
04:41 UtahDave http://developer.rackspace.com/devtrial/
04:42 UtahDave hey, mafrosis!
04:42 forrest joined #salt
04:42 mafrosis yo!
04:42 forrest hi
04:42 mafrosis is anyone aware of a bug in 0.17.1 (which wasn't in 0.17.0) where some pkg.install states fail?
04:43 mafrosis "failed with return code: 100"
04:43 forrest mafrosis https://github.com/saltstack/salt/issues/7933
04:43 UtahDave carmony: I don't know if rackspace supports using keys for authentication
04:43 forrest looks like Terminalmage already has the fix in place.
04:44 UtahDave mafrosis: which os?
04:44 mafrosis forrest: thanks dude
04:44 carmony UtahDave: Well how does salt-cloud install salt on Rackspace servers?
04:44 forrest mafrosis, np
04:44 UtahDave through it's api keys
04:44 carmony I got this error before: Error: There was a profile error: Cannot deploy salt in a VM if the 'ssh_key_file' setting is not set and 'sshpass' binary is not present on the system for the password.
04:44 UtahDave try commenting out that ssh_key_file option
04:44 carmony so I set the ssh_key
04:45 forrest UtahDave, do you ever leave the IRC? It feels weird that you're in here so much after you were gone for a while, I feel like you've got google glass and you just walk around with the IRC up al the time :P
04:45 dthom91 joined #salt
04:45 UtahDave Hm.  that would be a nice setup, forrest!
04:45 UtahDave Nah, I was gone 2 weeks on a customer engagement. They had the most annoyingly locked down network. blocked irc among a million other things
04:46 forrest I'm just poking fun
04:46 forrest They blocked IRC at my old job, then I just used the web client, SUCK IT SECURITAH.
04:46 UtahDave :)
04:47 forrest Did you at least eat some good food wherever you were?
04:47 carmony I use ZNC to get around security :P
04:47 Gareth UtahDave: ssh tunnesl to the rescue :)
04:47 Gareth tunnels too
04:48 UtahDave Yeah, had some great seafood in Boston area
04:48 forrest ahh nice I am jealous, not much good seafood in the desert
04:48 UtahDave they even had weird http rules.
04:48 carmony ZNC is awesome for me since I switch between ethernet and wireless a lot at work
04:48 UtahDave github was almost useless because the css for github was blocked
04:49 luminous hello! question... can salt-run state.over accept pillar data from the cli/
04:49 carmony UtahDave: hey, I'm having that problem at work
04:49 luminous I can't find details about this in docs or code
04:49 carmony just recently
04:49 forrest I never get the blocking of http content
04:50 forrest carmony, is it the icons and such? Github plugs straight into gravatar, and I noticed it seems that some of the icons are getting ripped from there too, not just people's images.
04:50 carmony no ide
04:50 UtahDave luminous: I'm not sure if it does. I'll have to ask and find out.
04:51 UtahDave have you tried it?
04:51 carmony I just hop on the VPN and it fixes it
04:51 luminous UtahDave: I don't really have any over states setup yet :P
04:51 luminous I'm having a helluva time figuring out a good way to do what i need, and if I can pass pillar data to salt-run state.over I can work with that
04:51 UtahDave ok.  you might search the mailing list archives, I think that question may have been asked a few months ago
04:52 carmony UtahDave: https://gist.github.com/JustinCarmony/c62957c9b5f62a9e4f04 -- this is the error I get when I comment out the ssh_key stuff
04:52 luminous peer, mine, and the others are all lacking in one way or another for the use case
04:52 luminous UtahDave: ok, thanks!
04:52 UtahDave carmony: sudo apt-get install sshpass
04:52 carmony on the master?
04:52 Fandekasp joined #salt
04:53 UtahDave yeah
04:53 carmony ahhh
04:53 forrest Interesting, I like how gmail is now trying to translate my email from myself, to myself just because my last name is hispanic, thanks Google...
04:53 carmony let me add that to my salt states :)
04:53 UtahDave TRADUZCA TODAS LAS COSAS!!!!!!!!!!
04:53 luminous UtahDave: you might be thinking of me asking about pillar and the command line. but that was about state.highstate and the like, not salt-run
04:53 luminous but I guess a test is also in order
04:54 luminous let me know if you end up being able to confirm with someone
04:54 UtahDave luminous: I think there was someone else asking specifically about the overstate
04:54 forrest UtahDave, heh
04:54 UtahDave luminous: ok, I'll ask when I get into the office in the morning
04:54 Fandekasp hi there. I'm following the salt tutorial, and when I try to run the salt '*' state.sls vim  and salt '*' state.sls nginx  commands, it always fail: http://sprunge.us/efOQ (I thought it was normal for vim, as it's already installed (thought I tried salt '*' pkg.remove vim), but nginx is really not installed). Any idea why ?
04:54 luminous thanks!
04:54 luminous Fandekasp: without looking at the paste... do you have those states?
04:55 UtahDave Fandekasp: can you pastebin your sls file for nginx?
04:55 carmony UtahDave: does salt-cloud setup servers in parralel
04:55 carmony ?
04:55 UtahDave carmony: not by default. If you add -P it will
04:55 luminous carmony: I think it can? but questionable reliability
04:55 luminous test and see?
04:55 UtahDave Be forewarned, if you do -P when you try spinning up 100 vms with -P it might kill your master
04:56 luminous hah
04:56 UtahDave because it doesn't have batching ability yet
04:56 Fandekasp UtahDave: http://docs.saltstack.com/topics/tutorials/walkthrough.html#adding-some-depth
04:56 carmony Psssh, I ain't worried yet :P
04:56 UtahDave so it will attempt to spin up all 100 at once
04:56 luminous I need to create 200 VMs next week :P
04:56 UtahDave It would be good to have it batch 5 or 10 at a time
04:56 carmony With vagrant and aws, I'd actually run into AWS API limits
04:56 luminous that's the use case I'm working out the details now
04:56 carmony if I tried to parallel deploy more than 10 at a time
04:56 UtahDave Fandekasp: what OS are you using?  is nginx the package name on your os?
04:56 EugeneKay 100 would make it puke? Out of curiousity, what's the most minions that a Master has been tested with?
04:57 luminous EugeneKay: there's the swarm script for that.. so thousands
04:57 luminous EugeneKay: but spinning up VMs is different
04:57 Fandekasp hmm not sure, I'll investigate
04:57 luminous that's much more costly
04:57 EugeneKay Pffft, I have a pile of ESXi hosts. :-p
04:57 UtahDave EugeneKay: with a pretty beefy Salt master server one user manages upwards of 13,000 minions
04:58 luminous NICE
04:58 EugeneKay How many cores / RAMs?
04:58 luminous I image TCP queues start to become an issue there
04:58 * EugeneKay is genuinely curious
04:58 luminous mailing list?
04:58 UtahDave I believe that master had 16 cores, local ssd storage, and maybe 64 gigs of ram?  something like that.
04:59 EugeneKay Pfffft, I want synchronous info. Not coming back in the morning!
04:59 EugeneKay Nice. Sounds about right.
04:59 carmony man, I wish I had salt back in the day I did sysadmin stuff for DVD Kiosks
04:59 EugeneKay I think the most my puny 2-core/2GB master(on a ESXi VM) has seen is 50 minions.
04:59 carmony we did all of our deployments.... manually....
05:00 forrest carmony, yea? When you walked uphill in the snow both ways to work? :P
05:00 carmony yup
05:00 carmony over VNC...
05:00 luminous hah
05:00 carmony over a celnet
05:00 carmony cell-net
05:00 forrest :(
05:00 carmony so it was like being back in the dialup days
05:00 Gareth walking uphill in the snow over VNC?  Brutal.
05:00 EugeneKay Cell-net? Pah! I've done deployments from miles offshore!
05:00 luminous don't laugh, all I had available a few years ago was dialup
05:00 luminous :P
05:01 carmony Oh yeah! I have one master, and its spun up a server in aws, rackspace, and digital ocean
05:01 carmony via salt-cloud
05:01 luminous <3 salt-cloud
05:01 UtahDave cool, carmony!
05:01 EugeneKay The most EC2s I've spun up was 200 for 24 hours.
05:02 EugeneKay That wasn't salted, tho
05:02 UtahDave i have a demo I used to use that spins up an asterisk server on aws that logs into my google voice #
05:02 UtahDave then sets up a web server on rackspace
05:03 UtahDave The asterisk server records audio and scp's it over to the web server for display
05:03 EugeneKay Shiny.
05:03 * luminous would love an asterisk state
05:04 Gareth Then the asterisk server calls everyone in the audience and tells them to look under the chairs, because they've won a new car!  Its called the Oprah State.
05:04 cachedout joined #salt
05:04 luminous HAH
05:04 forrest that would be pretty funny
05:04 forrest hook it into a soundboard
05:05 forrest YOU WON A CAR AND YOU WON A CAR AND YOU WON A CAR! Then UtahDave just throwing hot wheels at people
05:05 forrest fantastic
05:06 forrest why is gevent such a terrible web server?
05:06 forrest It takes so much to get installed, I still haven't gotten it installed properly
05:07 forrest I mean requiring gcc? Come on
05:09 Gareth gcc is required to run the web server?
05:10 forrest to install it
05:10 forrest when you do the install it has to build
05:10 Gareth ahh.
05:10 forrest and you need python-dev/devel for it
05:10 forrest and probably a few other things, haven't figured them out yet, I ended up skipping it.
05:10 Fandekasp UtahDave: amazon linux AMI (red-hat based) OS, yes there are packages "vim" and "nginx" in yum.
05:11 Gareth well if you're building it :)  makes send that you would need gcc.
05:11 Fandekasp the minion is the server containing master (test)
05:12 forrest Gareth, yea I'd prefer not to build it, I'd prefer if installing it via pip just you know, made it available :P
05:12 forrest Hey UtahDave, I know I harass you about this all the time, but any update from the vmware guys?
05:13 forrest I'm fighting a losing battle at work
05:17 carmony I am soooo close....
05:17 carmony to having it auto-generate servers :P
05:17 UtahDave forrest: it might help if you asked on the mailing list. so they see some demand for it.
05:17 Ryan_Lane joined #salt
05:20 packeteer carmony: please share your recipes when done  <3
05:20 carmony Will do :)
05:20 forrest UtahDave, done https://groups.google.com/forum/#!topic/salt-users/_HVzfdU7lyw
05:20 UtahDave thanks, forrest!
05:21 forrest yea np
05:21 forrest anything I can do to avoid using puppet at work, I'm willing to try :P
05:22 taylorgumgum joined #salt
05:25 UtahDave :)
05:26 carmony oh man, salt-cloud for vmware would be awesome
05:26 carmony since we have a lot of vmware at work
05:26 luminous people still use VMware?
05:26 forrest luminous, some of us like paying out the nose :P
05:26 * luminous scratches his head
05:26 forrest what are you using?
05:26 luminous openstack?
05:26 forrest psssssssssh
05:27 forrest that's the present luminous
05:27 forrest come on
05:27 forrest that's free
05:27 luminous sure, but I'm not
05:27 luminous I like working for folks who value people more than ridiculous licenses
05:27 luminous :)
05:27 forrest let's not get crazy here
05:27 luminous Fandekasp: what's your state look like?
05:28 luminous forrest: crazy? nahhh
05:28 luminous :P
05:28 forrest :D
05:28 forrest I tried to convince my team we shouldn't pay for puppet or salt
05:28 forrest as terrible as that is to say
05:28 forrest lol
05:28 luminous if healthcare.gov is the norm.. we've got a ways to go before we get to crazy
05:29 forrest I don't think I'd want to be on that project
05:29 luminous I like the idea of publishing it so we can all hack on it
05:29 mafrosis hey it's kind of off-topic, but could anyone explain to me why sometimes salt gets installed here:
05:29 forrest I like that idea as well
05:29 luminous given that it was paid for by the people, they're supposed to have the code
05:29 mafrosis /usr/lib/python2.7/dist-packages
05:30 mafrosis and sometimes it goes here
05:30 luminous mafrosis: installed with boostrap?
05:30 mafrosis /usr/lib/pymodules/python2.7
05:30 luminous what OS?
05:30 luminous never seen /usr/lib/pymodules, myself
05:30 mafrosis always ubuntu 12
05:30 mafrosis always bootstrao
05:30 luminous O.o
05:30 * luminous looks to compare
05:30 mafrosis I could mess about to find out the *exact* difference
05:31 luminous 12.04?
05:31 luminous or 13.x?
05:31 luminous I've  never seen such non-sense
05:31 mafrosis haha
05:31 luminous if you are using bootstrap you're using PPA
05:31 mafrosis don't worry, I don't come here often
05:32 * luminous is not worried
05:32 luminous :)
05:32 * carmony twiddles his thumbs as he deploys 9 servers across 3 providers in parallel....
05:32 luminous and maybe you should come here more often?
05:32 UtahDave mafrosis: maybe if you install salt from pip?
05:32 luminous carmony: LOVE IT
05:32 mafrosis hah
05:32 forrest carmony, yea it's awesome huh?
05:32 carmony way awesome
05:32 luminous carmony: do you have state.highstate hooked up to that too?
05:32 carmony then once this works, I'll just need to document the README
05:32 anuvrat joined #salt
05:32 mafrosis okay so I got a production server here deployed with salt-cloud, running 12.04 and files are in /usr/lib/pymodules
05:33 luminous weird
05:33 carmony luminous: Not yet, though it would be easy to call highstate
05:33 carmony I think there is an option for that
05:33 luminous did you use git/develop/etc? when installing with bootstrap, mafrosis
05:33 luminous carmony: yea, there's an option, I forget it
05:34 mafrosis luminous: you got it.. one of our devs was testing old salt version and left some code in the Vagrantfile
05:35 mafrosis salty-vagrant installs now go to /usr/lib/python2.7/dist-packages
05:35 mafrosis because they're git branch installs
05:35 * luminous nods
05:35 luminous good to know
05:35 carmony lol, there is something goofy with the salt-cloud output as I do 9 servers
05:35 carmony the tab spacing is off
05:36 luminous 0.17.x?
05:36 mafrosis I'll run another test to verify this theory
05:36 mafrosis 0.16.4, 0.17.x
05:36 luminous UtahDave: oh, I've been meaning to ask.. why or why doesn't salt-stack core host packages for previous releases somewhere?
05:36 carmony when I was working with salty-vagrant earlier it was installing an older version of salt, like 0.13 or something like that
05:37 mafrosis carmony: that's weird, it uses bootstrap so you should get latest
05:37 carmony mafrosis: thats what I thought
05:37 carmony I should have tried to reproduce it and bugged it
05:38 UtahDave luminous: we're working on hosting packages for various distros.  we have debian.saltstack.com right now. Others are in the works
05:38 carmony its also unclear whether you should still use salty-vagrant or just the bundled version of vagrant-salt that comes with Vagrant 1.3.x
05:38 mafrosis hey carmony - you doing salt-cloud parallel deploys?
05:38 joehh luminous: not sure if you use debian or not, the most recent version of the previous release is hosted at debian.saltstack.com
05:38 carmony mafrosis: yup, right now in fact
05:38 mafrosis and seeing a mangled terminal?
05:38 carmony mafrosis: yup
05:38 mafrosis you'll need to reset after the run
05:38 carmony awww
05:38 mafrosis I can offer you a little fix
05:38 akoumjian Do not use salty-vagrant plugin if you are using 1.3. The separate plugin is being deprecated
05:38 joehh you just need to add -016 to the end of the distribution bit to stay on that release
05:38 UtahDave carmony: yeah, salt-cloud can do that.  What version of salt-cloudd are you on ?
05:39 joehh similarly with -017
05:39 luminous UtahDave: I will, quite literally, completely stop cursing at the devs when that is available for ubuntu/etc
05:39 mafrosis been meaning to get to the bottom of it with s0undt3ch for ages
05:39 carmony UtahDave: latest and greatest
05:40 joehh luminous: there is https://launchpad.net/~saltstack/+archive/salt16 for ubuntu
05:40 nmistry joined #salt
05:40 carmony yeah, looks like deploying lots of servers in parallel eats up memory
05:40 luminous joehh: hmm.. how come I haven't seen that?
05:40 luminous I went digging real deep when 0.17.0 came out
05:41 mafrosis carmony: https://github.com/mafrosis/salt-cloud/compare/ttyfalse
05:41 UtahDave luminous: that was kind of an unofficial workaround.
05:41 luminous yea, that's acceptable
05:42 mafrosis akoumjian: did you just say *not* to use salty-vagrant with Vagrant 1.3?
05:42 luminous joehh: and I assume that'll bump to 17.x when 18.x is released?
05:42 luminous mafrosis: the newer vagrant has salty-vagrant included
05:42 luminous I believe
05:42 luminous at least, they've been waiting for a while to have that completed
05:43 joehh I hope/think that will stay around and a 0.17 one will be setup
05:43 mafrosis luminous: i remember all that going on
05:43 akoumjian mafrosis luminous : Correct. Salty-vagrant is now bundled with Vagrant
05:43 akoumjian I need to update the docs.
05:43 mafrosis phew
05:43 luminous joehh: that would be nice
05:43 mafrosis so what will happen if I run both 1.3 and the plugin?
05:43 mafrosis cos that's what I've been doing for weeks!
05:43 luminous find out and let us know?
05:43 joehh ideally, a 0.17 one would be there now, so taht people can be "safe" against unexpected upgrads
05:43 mafrosis LOL
05:43 luminous joehh: agreed
05:43 akoumjian Not sure. It will probably break, or best case one package will overwrite the namespace of the other
05:44 akoumjian Good to know
05:44 luminous I have a bootstrap script that I had to scramble and get it installing a specific version of salt because 0.17.1 broke stuff over the weekend
05:44 luminous >.<
05:44 mafrosis akoumjian yeah it's all good - I even attempted to update the plugin yesterday and wondered why the version hadn't changed in a while ;)
05:46 mafrosis left #salt
05:46 mafrosis joined #salt
05:47 mafrosis luminous: FYI that test came back as we suspected - a git install ends up in /usr/lib/python2.7/dist-packages, a normal install in /usr/lib/pymodules
05:48 luminous pymodules must be a vagrant thing?
05:50 mafrosis nah
05:50 mafrosis I get that in prod as well when using bootstrap via salt-cloud
05:50 __number5__ centos/redhat stuff
05:50 mafrosis this is ubuntu 12.04
05:51 Fandekasp I created a new minion in another server, with /etc/salt/minion updated to the cname of the salt master server. Restarted both minion and master, but salt-key -L on master doesn't show the new minion key. Did I miss a step ?
05:52 __number5__ mafrosis: ubuntu system don't install anything into /usr/lib/pymodules, they use /usr/lib/pyshared
05:53 mafrosis __number5__ trust man, it's happening here
05:53 mafrosis I'm running salt code from /usr/lib/pymodules/python2.7/salt
05:54 jefimenko joined #salt
05:54 __number5__ yep, I'm wrong, it belongs to python-support pkg
05:54 carlos joined #salt
05:55 mafrosis my original query was about the difference between the two
05:55 mafrosis it's something I'd noticed but never looked into
05:56 UtahDave Fandekasp: when you're logged in to the minion, can you ping the cname of the salt master server?
05:58 linjan_ joined #salt
05:58 Fandekasp UtahDave: no. problem fixed, needed to open ports 4505-4506 on master
05:58 __number5__ looks like /usr/lib/pymodules is just for the *.pyc, all *.py is symlink to /usr/share/pyshared
05:58 UtahDave Fandekasp: ah, yeah. good catch!
05:59 Fandekasp Do you know if we can rename the keys listed in ssh-key -L ?
06:00 mafrosis __number5__ interesting idea - I checked though and they are files in both dirs
06:00 pipps joined #salt
06:01 __number5__ mafrosis: did you find any *.pyc in /usr/share/pyshared/salt/ ?
06:02 UtahDave Fandekasp: right now you have to change the minion's id manually in /etc/salt/config on the minion.  Then you have to reaccept the minion under the new name with salt-key
06:02 Fandekasp thank you
06:03 ctdawe joined #salt
06:03 UtahDave We have plans to add the ability to change a minion's ID from the master, but that hasn't been implemented yet
06:04 mafrosis __number5__ nope
06:04 mafrosis I'm not sure what that dir is about at all
06:05 mafrosis sometimes I get salt code installed into /usr/lib/pymodules/python2.7
06:05 mafrosis and sometimes /usr/lib/python2.7/dist-packages
06:05 mafrosis that's what we were talking about earlier - not sure about pyshared at all
06:06 __number5__ If salt goes to /usr/lib/python2.7/dist-packages, it has been installed by pip or easy_install
06:07 __number5__ if salt is installed using deb, it goes to /usr/share/pyshared and /usr/lib/pymodules
06:07 ausmarton joined #salt
06:08 mafrosis __number5__ thanks
06:10 __number5__ but some package like python-api will still install stuff into /usr/lib/python2.7/dist-packages/apt_pkg.so, that's really beyond me
06:10 __number5__ *python-apt
06:11 mafrosis huh yeah
06:12 redondos joined #salt
06:12 redondos joined #salt
06:20 hotbox joined #salt
06:20 berto- joined #salt
06:20 bud joined #salt
06:27 tumm joined #salt
06:29 redondos joined #salt
06:35 rawzone joined #salt
06:41 Lue_4911 joined #salt
06:49 hotbox joined #salt
06:56 hvn joined #salt
07:01 balboah joined #salt
07:11 Raymii joined #salt
07:15 Iwirada joined #salt
07:19 anuvrat joined #salt
07:25 Destro joined #salt
07:26 networkpadawan joined #salt
07:37 abishekk92 joined #salt
07:40 APLU joined #salt
07:41 deepakmd_oc joined #salt
07:50 alexheneveld joined #salt
07:57 tonthon Hi
07:58 tonthon Using the state.cmd module, I'd like to append some path to my PATH env var
07:58 aleszoulek joined #salt
07:59 tonthon I know the env param that allows to pass environment vars, but I want to append some stuff, any idea how I could do it cleanly ?
08:07 felixhummel joined #salt
08:08 hvn_ joined #salt
08:09 Ryan_Lane joined #salt
08:14 bhosmer joined #salt
08:16 xinkeT joined #salt
08:18 bud tonthon: prefix your command with PATH=/some/path:$PATH in name of cmd.run.
08:19 bud So for example you would like to run the command echo $PATH, name would be PATH=/some/path:$PATH echo $PATH.
08:19 bud Maybe there are cleaner solutions, have tried the above in the CLI and it works.
08:21 bud Anybody here running Salt 0.17.0 on Debian Wheezy? I have some strange problems with Jinja, it complains about undefined variable.
08:22 bud The thing is that the same state with the same pillar data works on another Debian Wheezy box the only difference being that on the box that works python-jinja2 is installed from unstable repository and the version is 2.7.1. On the box it crashes python-jinja2 is at 2.6.1.
08:37 tonthon bud: I know that one, I was looking for a cleaner one :)
08:37 tonthon thx for taking some time
08:38 tonthon bud: I use salt on debian wheezy without running any particular problem
08:39 tonthon bud: do you get the same pillar dats with pillar.items on both boxes ?
08:39 bud tonthon: the salt.states.cmd.run has env - Pass in a list or dict of environment variables to be applied to the command upon execution. Does that help you?
08:39 bud tonthon: exactly the same!
08:40 bud I use set var = pillar.get to load variables with data from pillar.
08:46 bud tonthon: the state in question works just fine on Debian Wheezy with python-jinja2 from unstable.
08:53 Ryan_Lane joined #salt
09:07 elfixit joined #salt
09:16 mua joined #salt
09:25 baoboa joined #salt
09:28 giantlock joined #salt
09:28 Ryan_Lane joined #salt
09:32 alexheneveld joined #salt
09:32 baffle joined #salt
09:33 zooz joined #salt
09:34 jslatts joined #salt
09:38 enertek joined #salt
09:39 mua joined #salt
09:41 scott_w joined #salt
09:41 networkpadawan joined #salt
09:43 enertek hi all (first time on IRC since #teenchat circa 1994)... i'm having a problem with salt not recognizing an upstart service on raspbian (based on debian wheezy)
09:44 enertek the issue stems from the upstart module 'excusing itself' except when __grains__['os'] in ('Ubuntu', 'Linaro', 'elementary OS')
09:44 joehh what is the result of grains.get os?
09:44 enertek 'Debian' on this raspian device
09:45 enertek if I edit upstart.py and add 'Debian' to the list, it's working fine
09:45 enertek i would suggest that other os's be included in this list, or a check for pkg upstart, or perhaps a custom grain to force-allow upstart... what is the best way to suggest these modifications? bug report, pull request, ?
09:47 giantlock joined #salt
09:52 gildegoma joined #salt
09:58 ajw0100 joined #salt
10:01 ajw0100 joined #salt
10:02 bud Anyone using git and roots together and working?
10:03 bud On 0.17.1 I mean.
10:03 jcristau enertek: fwiw /lib/lsb/init-functions has a init_is_upstart function that could be used at least as inspiration
10:03 jcristau instead of relying on distro name
10:04 ajw0100 joined #salt
10:05 jcsp joined #salt
10:05 matanya joined #salt
10:05 matanya joined #salt
10:06 jslatts joined #salt
10:06 ajw0100 joined #salt
10:07 summernguyen joined #salt
10:07 summernguyen Hello,
10:07 summernguyen I'm new to saltstack in few days
10:07 summernguyen I found that saltstack is fit to my company
10:08 summernguyen I'm finding out how to write a module
10:08 summernguyen I did a test module , but I don't know where to place my mytest.py module
10:09 enertek jcristau: thanks for that, maybe a more generic method of detecting upstart is just if pkg.version('upstart') is set... init_is_upstart checks initctl version for 'upstart' string, which hmm may not be universal for other distros
10:09 ajw0100 joined #salt
10:10 bud summernguyen: custom modules can be placed in _modules directory located in the base environment of file_roots. Run salt '*' saltutil.sync_modules to have it available on the minions.
10:12 ajw0100 joined #salt
10:12 jcristau enertek: just because upstart is installed doesn't mean it's used
10:12 summernguyen http://pastebin.com/mXUA2pu7
10:13 summernguyen ahh
10:13 summernguyen ok
10:13 summernguyen thank you bud
10:13 summernguyen I did in wrong way
10:13 summernguyen thank you very much
10:14 ajw0100 joined #salt
10:17 ajw0100 joined #salt
10:17 bud Setting fileserver
10:18 bud _backend to git and root, in this order, would tell salt to first look for states in gitfs_remotes and then in file_roots, isn't it?
10:19 ajw0100 joined #salt
10:22 ajw0100 joined #salt
10:23 enertek ok i added a check for debian/raspian in the os grain, and then call 'initctl version' and check for upstart... what's the best way to submit/offer this mod (total FOSS newbie here)
10:24 ajw0100 joined #salt
10:27 ajw0100 joined #salt
10:29 ajw0100 joined #salt
10:32 phab3k joined #salt
10:32 ajw0100 joined #salt
10:35 ajw0100 joined #salt
10:36 jcsp joined #salt
10:37 ajw0100 joined #salt
10:40 ajw0100 joined #salt
10:41 enertek i opened an issue 8039 and submitted a pull request 8040 -- hope i did it right
10:51 alexheneveld joined #salt
10:55 hazzadous joined #salt
11:11 joehh enertek: can't comment on the code directly (not familiar enough with that bit or upstart), but the pull request looks ok
11:11 joehh ok==good
11:12 joehh what you've done is a really good way to contribute - hopefully in a few hours/days one of the saltstack devs will apply your pull request
11:20 enertek ok thanks for that!
11:24 ajw0100 joined #salt
11:25 jslatts joined #salt
11:27 Iwirada joined #salt
11:28 joehh either that or they will suggest how it can be improved
11:30 networkpadawan joined #salt
11:35 jcsp joined #salt
11:44 enertek left #salt
11:47 elfixit joined #salt
11:52 ipmb joined #salt
11:53 ajw0100 joined #salt
11:55 Raymii joined #salt
11:57 srage joined #salt
12:01 whiskybar joined #salt
12:09 logix812 joined #salt
12:09 logix812 Is it possible to set env vars for a service: to run under?
12:10 Pierre joined #salt
12:10 Pierre hi!
12:10 Pierre FYI, your CI bot is accusing me of breaking the builds :)
12:10 Pierre I suppose it looks for the wrong Pierre
12:11 Pierre -salt-jenkins- Build Salt Rackspace Arch isSTILL FAILING: http://jenkins.saltstack.com/job/salt-rs-arch/501/
12:11 Pierre -salt-jenkins- Oh no! You're suspected of having broken Salt Rackspace FreeBSD: http://jenkins.saltstack.com/job/salt-rs-freebsd/481/
12:11 Pierre would be nice to change the link to the right user, as he surely has to be blamed!
12:13 Raymii joined #salt
12:16 Raymii joined #salt
12:17 Pierre hm, and here it goes again
12:17 Raymii joined #salt
12:17 Pierre basepi, as you seem to be an admin of this project, mind to take of it? I could simply block it but the gulty committer won't notice it
12:19 kyusan hi, what is the best way to pass a variable from top.sls to another module ? thank you in advance :)
12:21 anteaya joined #salt
12:23 xl1 left #salt
12:25 rr_ joined #salt
12:25 rr_ How to replace a second word in a file using saltstack
12:29 oz_akan_ joined #salt
12:30 bhosmer joined #salt
12:37 alexheneveld joined #salt
12:39 bud rr_: maybe http://docs.saltstack.com/ref/states/all/salt.states.file.html#salt.states.file.replace would fit your needs.
12:40 wkf joined #salt
12:48 jcsp joined #salt
12:51 brianhicks joined #salt
12:55 cron0 joined #salt
13:04 mua joined #salt
13:06 anuvrat joined #salt
13:10 Pierre left #salt
13:11 bhosmer_ joined #salt
13:12 juicer2 joined #salt
13:15 wkf joined #salt
13:16 baffle Hmm, is there any good way to set the mysql root password during salting of a db server on Ubuntu? I've seen one hack here: https://groups.google.com/forum/message/raw?msg=salt-users/MHATYLoG2js/OhpBPCvo5ZsJ
13:17 baffle But that is kinda ugly. I also saw a mention of a default_user and default_pass function going into 0.17.0, but I can't find it in the MySQL module at least..
13:19 racooper joined #salt
13:20 Kholloway joined #salt
13:21 mpanetta joined #salt
13:22 m_george|away joined #salt
13:22 mgw joined #salt
13:24 zz_polaco joined #salt
13:24 mapu joined #salt
13:31 jcsp joined #salt
13:33 jslatts joined #salt
13:35 mwm_ joined #salt
13:35 mwm_ howdy
13:35 toastedpenguin joined #salt
13:39 mwmnj joined #salt
13:39 Ryan_Lane joined #salt
13:41 amahon joined #salt
13:42 mwmnj joined #salt
13:42 mwmnj Hi
13:43 mwmnj Is salt just libcloud + puppet ?
13:43 akio no
13:44 mwmnj akio: there are additional functionalities of saltstack or?
13:44 xt yes
13:47 colinbits joined #salt
13:47 Furao best feature: not in ruby
13:48 jumperswitch joined #salt
13:48 mwmnj Furao: haha
13:48 mwmnj thanks guys I will keep diggin in the docs
13:51 Brew joined #salt
13:51 penguin_dan joined #salt
13:52 Linz joined #salt
13:53 Brew joined #salt
13:57 srage joined #salt
13:58 srage joined #salt
14:00 jcsp joined #salt
14:01 mgw joined #salt
14:08 acsir joined #salt
14:10 m_george left #salt
14:14 urtow joined #salt
14:15 baffle Hmm, does a minion really need mysql.pass etc in its minion configuration to use the mysql salt module? Can't it just use the values from pillar?
14:17 basepi Pierre: any idea why it chose you to bother? Did you submit a pull req recently?
14:17 kermit joined #salt
14:21 Ryan_Lane joined #salt
14:22 copelco joined #salt
14:23 aberant joined #salt
14:24 mwmnj joined #salt
14:25 srage joined #salt
14:26 srage joined #salt
14:26 jergerber joined #salt
14:26 pipps1 joined #salt
14:27 srage joined #salt
14:29 urtow Hi, sorry for my rude lang, i have some stupid question. I have salt master with open_mode and auto_accept enabled true, how i can automatically run "salt 'id' state.highstate" for new salt-minion with id, who had just connected to master?
14:29 urtow i know this not secure, but i need some thing like this
14:32 cnelsonsic joined #salt
14:35 Destro left #salt
14:36 urtow_ joined #salt
14:36 urtow_ sorry, if someone answer - please repeat, my internet falls down
14:37 tyler-baker joined #salt
14:38 jcsp joined #salt
14:40 acsir urtow: I expect that with such a behaviour it would work out of the box as soon as you start the minion server.
14:41 acsir try {salt-key -L} in order to check that the minion key has been accepted by master
14:41 acsir then, you could also try {salt 'new-minion-ID' test.ping} to get sure that it is connected
14:41 acsir let me know
14:42 acsir urtow_: just read the above
14:44 ausmarton joined #salt
14:44 bds joined #salt
14:44 urtow_ thsnks i`ll check
14:46 linjan_ joined #salt
14:47 foxx joined #salt
14:49 micah_chatt joined #salt
14:56 Ryan_Lane joined #salt
14:59 dthom91 joined #salt
14:59 whiskybar joined #salt
14:59 brimpa joined #salt
15:00 jslatts joined #salt
15:02 jalbretsen joined #salt
15:09 mgw I'm having an issue with ext_nodes:
15:09 mgw https://gist.github.com/mgwilliams/6f4fa9aead636a7fbf0a
15:09 mgw anybody seen that error?
15:14 brimpa joined #salt
15:15 mgw this seems to be a bug in 0.17.0
15:15 mgw I just upgraded to 0.17.1 on that minion and it works now
15:18 UtahDave joined #salt
15:19 forrest joined #salt
15:22 Khollowa_ joined #salt
15:23 redondos joined #salt
15:23 redondos joined #salt
15:24 phab3k joined #salt
15:27 cachedout joined #salt
15:28 Khollowa_ joined #salt
15:30 micah_chatt joined #salt
15:30 ctdawe joined #salt
15:34 GradysGhost joined #salt
15:35 mikko__ Anyone know what causes this error when starting the salt-master 0.17.1? https://dpaste.de/3yC9
15:35 mikko__ [ERROR   ] Error in function _mine:
15:36 mikko__ the old minions are using 0.15.3 version. Could this be a conflict with keys?
15:36 GradysGhost Hey guys, I set up a master and three minions, then realized that the minions' hostnames were invalid, so I changed them. salt no longer seems to do anything when I target these servers, and I can't get the minions to resend their keys to the master.
15:36 GradysGhost Any advice?
15:36 mikko__ Or has the key structure been revamped since 0.15.3?
15:37 UtahDave GradysGhost: Have you tried deleting the minion's keys from the master?
15:37 GradysGhost Would those be in /etc/salt/pki?
15:38 GradysGhost er, /etc/salt/pki/minion
15:39 ebodine \exit
15:40 bhosmer joined #salt
15:41 alexheneveld joined #salt
15:43 GradysGhost I've deleted all the keys that I can find there, but restarting the minion/master does not result in the master seeing any new keys.
15:43 mikko__ UtahDave: Is there any way to manually clean all old jobs that has been queued up? I know there is no jobs to run but the salt-master still uses 100% CPU and seems to hang up when executing a new command.
15:43 GradysGhost Do I need to force the minion to regenerate keys somehow?
15:44 c0bra joined #salt
15:44 ncjohnsto joined #salt
15:45 patrek gradysghost: did you restart the minion after deleting the keys?
15:45 alexheneveld_ joined #salt
15:45 GradysGhost Yes.
15:46 GradysGhost The keys got regenerated, but `salt-key -L` doesn't show anything.
15:47 forrest restart the master GradysGhost?
15:47 forrest oh you already did
15:47 forrest failure to read
15:48 GradysGhost Yeah, I restarted both. In all cases, the keys get regenerated, but salt-key doesn't have anything for me to accept.
15:48 forrest weird
15:48 GradysGhost It looks like the relevant directory on my system is /etc/salt/pki/master/minions
15:48 GradysGhost But that's an empty directory right now.
15:48 GradysGhost So are /etc/salt/pki/master/minions_pre
15:49 GradysGhost and /etc/salt/pki/master/minions_rejected
15:49 jcsp joined #salt
15:49 alexheneveld joined #salt
15:50 forrest the master is still listening on the right ports correct?
15:50 patrek anything in /var/log/salt/minion ?
15:51 GradysGhost I'll check. I'm trying one more thing real quick. Results to come shortly...
15:52 GradysGhost ok
15:52 GradysGhost I uninstalled both the salt-master and salt-minion packages
15:52 mapu joined #salt
15:52 GradysGhost I fully deleted /etc/salt
15:52 GradysGhost I reinstalled the packages
15:52 GradysGhost I started master and minion services (same box)
15:53 GradysGhost I think I may have some config issues that I'm going to try to work out now, but I have two unaccepted keys.
15:53 pentabular joined #salt
15:53 GradysGhost I'm not accepting them right now because they're highlighting the fact that I need to get those minions to regen their keys as well.
15:54 nahamu UtahDave: I think I've gotten the salt esky build working on SmartOS.
15:54 GradysGhost ok, this is looking much better now.
15:54 UtahDave GradysGhost: make sure the /etc/salt/minion has the master's ip or hostname set
15:54 nahamu I have some patches I need to send upstream to bbfreeze
15:54 GradysGhost They do. I just needed to also delete the minion keys from my other minions so the keys they present for themselves actually represent the correct hostname.
15:54 UtahDave mikko__: looks like you're running into a problem we've just learned about 0.17.1 master not being able to talk to an older minion.
15:55 UtahDave nahamu: nice!
15:57 mikko__ UtahDave: Well the minion says "Returning job bla bla bla " but then it hangs up and prints out a ZMQError: cannot continue in the current state~. This happens when ZMQ tries to execute some Socket.send(pkg)
15:57 mgw1 joined #salt
15:58 jcockhren UtahDave: got halite up. However, I'ev only actually seen the UI once. Any other time, just a blank page appears.
15:58 mgw1 mikko_: did you find your problem?
15:58 mikko__ mgw1: no i did not  :/
15:58 forrest jcockhren, is it logging your requests when you hit the page?
15:58 KyleG joined #salt
15:58 KyleG joined #salt
15:59 mgw1 what versions are the minion and the master?
15:59 MTecknology I was just asked to interview at a company for a position managing their salt infrastructure...
15:59 mikko__ mgw1: https://dpaste.de/9iEJ this happens on the master.
15:59 mikko__ mgw1: 17.1 master, 15.3 minion
15:59 jcockhren no errors and the favicon and doing a "view source" on the blank page shows the home page source just fine.
15:59 mikko__ happens on 17.1 minion also
15:59 GradysGhost Ok, new keys accepted. But running...
15:59 MTecknology Apparently they think I'm as smart as UtahDave dave. Funny...
15:59 GradysGhost salt '*' cmd.run 'hostname'
15:59 GradysGhost Produces zero output
15:59 kula i really need to write something complimentary to salt and call it 'pepper'
15:59 MTecknology GradysGhost: add -v
15:59 mgw1 mikko_: I was having a similar issue on 17.1 master, 17.0 minion
16:00 mgw1 upgraded minion and it went away
16:00 UtahDave mikko__: I think you're going to have to upgrade that minion to 0.17.1 or downgrade your master
16:00 MTecknology GradysGhost: salt -v '*' cmd.run 'hostname'
16:00 dthom91 joined #salt
16:00 jcockhren forrest: yes. It at least shows the access logs when running in debug mode at the terminal
16:00 forrest interesting, what web server are you running it through?
16:00 GradysGhost "Minion did not return"
16:00 forrest granted, I'm running it through salt-mater
16:00 GradysGhost For every node
16:00 forrest *master
16:01 jcockhren forrest: just regular ol' cherrypy
16:01 forrest hmm
16:01 forrest what OS?
16:01 jcockhren ubuntu 12.04
16:01 forrest I set it up on Debian, as well as centos and haven't encountered that yet. Can you try it in another browser?
16:01 jcockhren the thing is, it worked well once
16:01 forrest Yea, which is odd.
16:01 forrest did you log in?
16:01 jcockhren tried both chrome and firefox
16:02 jcockhren yes I did that once. it all worked as expected
16:02 GradysGhost Maybe a dumb question, but what ports on the minions need to be open?
16:02 forrest What user did you log in as ?
16:02 GradysGhost 450{5,6}?
16:02 forrest no port GradysGhost
16:02 GradysGhost ok
16:02 jcockhren forrest: a pam enabled user
16:02 jcockhren not root
16:02 GradysGhost I did notice no listening processes.
16:02 jcockhren it executed commands and pulls grains just fine
16:02 forrest jcockhren, ok. Can you try to stop/restart the server, and check your cookies to see if it stored one for the login itself, then clear that cookie?
16:02 mua joined #salt
16:03 jcockhren ok.
16:04 mua left #salt
16:04 jcockhren ok. same result
16:04 forrest weird, public facing IP or internal?
16:04 jdenning joined #salt
16:04 jcockhren it's out there in the world
16:05 GradysGhost Restarted all minions; still getting "Minion did not return". Nothing in the various minion logs.
16:06 pentabular joined #salt
16:06 pentabular left #salt
16:06 dave_den GradysGhost: stop master and minions and rm -rf /var/cache/salt on master and minions?
16:07 GradysGhost will try...
16:07 dave_den then start salt-master with salt-master -l debug, and start your minions with salt-minion -l debug
16:07 dave_den see what comes up
16:07 GradysGhost ok
16:08 pipps1 joined #salt
16:09 Gifflen joined #salt
16:11 avienu joined #salt
16:12 redondos joined #salt
16:13 GradysGhost All three minion throw up "Waiting for minion key to be accepted by the master." However, salt-key -L shows no unaccepted keys.
16:13 GradysGhost The three minion keys are listed as accepted.
16:13 dave_den rm the minion keys on the master from /etc/salt/pki/master/minions_accepted
16:14 GradysGhost Then restart the minions?
16:14 dave_den or rather /etc/salt/pki/master/minions
16:14 GradysGhost Or will they auto-attempt to get them accepted?
16:14 dave_den restart for good measuer
16:14 GradysGhost k
16:15 GradysGhost Now there are no keys at all, accepted or otherwise, in salt-key output
16:15 CheKoLyN joined #salt
16:16 dave_den on a minion
16:16 dave_den can you telnet to your master on port 4505?
16:17 dave_den and port 4506?
16:17 dave_den double check the hostname the minions are trying to connect to:   grep master: /etc/salt/minion
16:17 druonysus joined #salt
16:18 druonysus joined #salt
16:18 GradysGhost ah crap
16:18 GradysGhost I can't, but I'm not sure why.
16:18 pentabular joined #salt
16:18 GradysGhost The port's open in the firewall, and the service is listening.
16:19 dave_den ah, well that's definitely the problem
16:19 GradysGhost hang on, I think I found the issue. I think I'm doing port binding wrong...
16:20 wrale left #salt
16:22 tempspace I like the new summary at the end of the highstate
16:23 Linz joined #salt
16:23 pentabular1 joined #salt
16:23 ctdawe joined #salt
16:25 Ryan_Lane joined #salt
16:26 Lue_4911 joined #salt
16:27 bhosmer joined #salt
16:32 jefimenko joined #salt
16:32 GradysGhost Thanks, guys! I got the minions all worked out!
16:34 mwmnj I am trying to install salt on mac os but I am seeing this error: error: command 'swig' failed with exit status 1
16:34 danielbachhuber joined #salt
16:35 mwmnj Looks like it is known and a potential solution is to install M2Crypto first like so:
16:35 mwmnj env SWIG_FEATURES="-cpperraswarn -includeall -D__`uname -m`__ -I/usr/include/openssl" pip install M2Crypto
16:35 dave_den GradysGhost: cool
16:35 mwmnj But that shows that same error
16:37 taylorgumgum joined #salt
16:37 dave_den mwmnj: i've never installed salt on osx, but swig is available from homebrew
16:37 troyready joined #salt
16:38 morty_ joined #salt
16:38 dave_den oh, the osx instructions also say that. i'm redundant
16:39 Corey Hmm, can't import yaml after an upgrade to mavericks. Checking.
16:40 cro Corey: Me either, but I don't remember if I pip-intstalled it under ML or not.
16:42 Corey cro: Yeah, I suspect I did. Checking.
16:43 viq Sorry, I need some handholding - trying to figure out how to get data out of a pillar like here https://groups.google.com/forum/#!topic/salt-users/wgtIuYncrL0
16:45 mgw joined #salt
16:45 ipmb joined #salt
16:46 networkpadawan left #salt
16:52 Raymii joined #salt
16:53 linjan_ joined #salt
16:54 chrishoffman joined #salt
16:55 dthom91 joined #salt
16:57 Corey UtahDave: Yeah, there are issues around Salt under Mavericks.
16:57 Corey Researching.
16:58 UtahDave I'll be interested to hear what you figure out
16:58 xmltok joined #salt
16:59 micah_chatt joined #salt
17:00 Corey UtahDave: oldsalt has Mavericks now if anyone on your end wants to poke at it.
17:04 wkf joined #salt
17:04 pipps joined #salt
17:06 linuxnewbie joined #salt
17:06 linuxnewbie joined #salt
17:07 linuxnewbie hello, is there any way to convert puppet manifests to salt ?
17:07 linuxnewbie other than writing from scratch
17:08 jpcw joined #salt
17:13 bitz joined #salt
17:14 viq linuxnewbie: not really, completely different language
17:14 mspitz joined #salt
17:14 UtahDave linuxnewbie: Yeah, we don't have a converter or anything.
17:14 mspitz Hello!  I'm new to salt.
17:14 linuxnewbie ty guys i hoped to have luck :)
17:14 viq OK, so with pillar data in test.sls and state names.sls like https://gist.github.com/viq/7122665 I can get data out. How do I get it out if test.sls looks like this: https://gist.github.com/viq/7122699 ?
17:15 mspitz Is there a way to run 'highstate' without apt-get update'ing every single time?
17:15 UtahDave linuxnewbie: I have helped several customers switch and it's really pretty quick to read through the manifests and rewrite them in Salt formulas
17:15 mspitz As I'm figuring out how the package structure and stuff works, I find that really slow to iterate.
17:15 UtahDave mspitz: which version of Salt are you using?
17:15 linuxnewbie UtahDave, i'll try my best :)
17:15 viq mspitz: just a guess, but any 'pkg.latest' in your states?
17:16 bds joined #salt
17:16 mspitz viq: I do
17:16 mspitz UtahDave: whatever the bootstrap script just installed; I assume the latest
17:17 UtahDave mspitz: salt-minion --version   or salt \* test.version
17:17 UtahDave I think viq has a point. I believe that if you're using pkg.latest instead of pkg.installed it will cause apt to update to check for the latest available version of the software
17:18 akio salt noob here, what am i doing wrong, and is there a checker i could use that comes with salt? : http://sprunge.us/ahLX
17:18 mspitz UtahDave: 0.17.1
17:18 viq Or you could add refresh=False to the states
17:18 UtahDave akio: try  salt '<minion name> state.show_sls <sls name>
17:19 akio thanks
17:19 viq OK, so with pillar data in test.sls and state names.sls like https://gist.github.com/viq/7122665 I can get data out. How do I get it out if test.sls looks like this: https://gist.github.com/viq/7122699 ?
17:20 Gifflen joined #salt
17:20 mspitz UtahDave/viq: moving to pkg.installed fixed my woes
17:20 mspitz Though that's not quite what I want.
17:20 UtahDave viq: is that data coming from the same pillar data?
17:20 viq mspitz: cool, good to know
17:21 viq UtahDave: hm?
17:21 viq UtahDave: I just pasted test.sls pillar
17:21 viq Just trying to figure out how to do something more complicated, starting from something smaller
17:21 UtahDave Oh, I see. I didn't realize that. I was a bit confused.
17:22 steveoliver does it make sense to have salt-minion also running on salt-master?
17:22 viq test.sls is pillar data, names.sls is state where I am trying to use it
17:22 steveoliver alongside salt-master on a master, that is
17:22 UtahDave steveoliver: yeah, I almost always have a minion running on my saltmaster
17:22 viq steveoliver: sure does
17:22 kula i run a salt-minion on my master.
17:22 mspitz I'm just going to keep asking questions, sorry.  Does Salt support templates for files?  Can I parameterize my nginx.conf based on the node it's running on, for example?
17:22 steveoliver k. is there a grain (or other way) to identify if a master is also a minion?
17:22 viq mspitz: yes, in multiple languages even
17:23 akio UtahDave: The paste was about some syntax problems. I see I can see what is matching with the command you gave, that will be helpful.
17:23 UtahDave mspitz: yeah, you can template in jinja by default, and mako or wempy as well
17:23 mspitz viq: Thanks! I haven't found a good article on it yet.  Any suggestions?
17:23 mwmnj joined #salt
17:24 mwmnj dave_den: Yea, I have it installed w/ homebrew already
17:24 viq mspitz: http://docs.saltstack.com/ref/renderers/all/index.html
17:24 steveoliver well if it authenticates with itself, then… duh
17:24 UtahDave mspitz: look at this repo for some examples: https://github.com/saltstack-formulas/nginx-formula/blob/master/nginx/init.sls
17:24 steveoliver derp
17:24 viq steveoliver: 'if hostname == salt'  ?
17:25 steveoliver viq: yeah, something like that
17:25 steveoliver thx
17:25 steveoliver :)
17:25 steveoliver sls files are so fun to write
17:25 UtahDave steveoliver: I usually set my minion id to something that tells me it's the minion running on my master.
17:25 viq steveoliver: also you can hardcode custom grains in a file, IIRC /etc/salt/grains or something like that
17:25 mspitz viq/UtahDave: that's perfect; thank you.
17:25 steveoliver UtahDave: viq: yeah, i started defining a grain… then wondered if there were some flag...
17:26 steveoliver considered checking hostname as well, which i may do
17:26 steveoliver s/flag/existing grain/
17:26 UtahDave viq: {{ pillar['joe']['number'] }}
17:27 viq UtahDave: yeah, but how to iterate over the stuff...
17:29 ncjohnsto joined #salt
17:30 jesusaurus viq: heres an example of a somewhat complex iteration: https://github.com/jesusaurus/hpcs-salt-state/blob/master/apt/repo/distro
17:30 jesusaurus with this pillar: https://github.com/jesusaurus/hpcs-salt-state/blob/master/apt/sample.pillar
17:31 viq jesusaurus: thank you, lookijng
17:31 viq jesusaurus: what does -% do ?
17:32 jesusaurus the - means jinja ignores whitespace
17:32 jesusaurus so -%} ignores following whitespace and {%- ignores leading whitespace
17:32 jesusaurus that way i dont end up with a ton of blank lines in the generated file
17:33 viq Ah, nice, thanks
17:34 viq jesusaurus: seeing what other repos you have there, this might interest you ;) https://github.com/threatgrid/kiries
17:35 jesusaurus oh, interesting
17:35 * jesusaurus googles riemann
17:35 viq riemann.io
17:37 amckinley joined #salt
17:38 mspitz I think I understand how to set up different states/pillar-files for dev vs qa vs production, but how do I indicate which environment I'd like to run when calling highstate?
17:40 jesusaurus mspitz: you match minions to environments based on minion id in the top files
17:40 mspitz Boom, got it.
17:41 mspitz Thank you!
17:41 mspitz Can I see the environment with Pillar?
17:41 jesusaurus UtahDave: do you know if there is any discussion around separating environment matching away from state/pillar matching?
17:42 jesusaurus mspitz: what do you mean by 'see the environment with pillar'?
17:42 viq jesusaurus: the second line of your state file, what does the 'false' do there?
17:44 mspitz Say I'm configuring my application to point at a database.
17:44 mspitz In dev, the database lives at test_whatever
17:44 mspitz In production, the database lives at important_database.prod.myapp.com
17:45 mspitz When generating my config file, how do I differentiate those states?
17:45 viq mspitz: that sounds like stuff you put into pillar, or maybe 'context'
17:45 mspitz Ah, but when generating context, how do I know what value to put in there?
17:45 mspitz Is there something like:
17:45 UtahDave jesusaurus: I'm not sure.  do you have any ideas on how you would like that to work?
17:45 mspitz {% if pillar.get("is_dev") %}
17:45 mspitz - hostname: test_whatever
17:45 mspitz {% else %}
17:46 viq mspitz: http://docs.saltstack.com/topics/tutorials/pillar.html 'Paramaterizing States With Pillar'
17:46 mspitz - hostname: important_databse.prod.myapp.com
17:46 viq mspitz: no, you assign different pillar files depending on environment
17:46 mspitz Ah, brilliant.
17:46 mspitz So, for each state, I'd set up a different pillar file per-environment?
17:47 mspitz Doesn't that end up being a lot of files all edited in different places?
17:47 jesusaurus viq: that false is a default value. so if distro['origin'] doesnt exist the get yields the value False
17:47 viq jesusaurus: awesome, thanks
17:47 viq mspitz: number of pillar files is independent of number of state files
17:48 KyleG joined #salt
17:48 KyleG joined #salt
17:48 ccase_ joined #salt
17:48 viq mspitz: http://docs.saltstack.com/topics/pillar/index.html
17:49 ccase joined #salt
17:49 akio whats the right way to make sure epel-release is installed?
17:49 * Gareth waves
17:50 akio I saw this: https://github.com/saltstack-formulas/epel-formula/blob/master/epel/init.sls
17:50 * akio waves back
17:50 jesusaurus UtahDave: well, i think that the top file is doing two very different things: giving minions either their states or pillars, and also defining environments
17:51 akio love your name jesusaurus
17:51 jesusaurus i think it makes sense to do these separately, so that in one file, or stage of the process we give a minion its states / pillars
17:51 jesusaurus and in a separate file give minions their environments
17:52 jesusaurus then the master can look in the given environment for listed states / pillars
17:52 mwmnj At the mac os installation instructions: http://docs.saltstack.com/topics/installation/osx.html
17:52 mwmnj do I need to create the directory and file /etc/salt/master
17:52 jesusaurus this would make it easier to override the enviorment for testing
17:52 mwmnj to paste "max_open_files: 8192" as instructed
17:53 mwmnj ( /etc/salt/master doesn't exist)
17:53 viq jesusaurus: still deciphering how it works, but your example is very informative, thank you!
17:53 steveoliver seen auser?
17:54 jesusaurus viq: youre welcome :)
17:54 dave_den mwmnj: if you are installing the master on osx, that file will be created and then you can edit it to change max_open_files
17:54 forrest haven't seen auser today steveoliver.
17:54 steveoliver forrest: thx
17:54 forrest np
17:55 steveoliver i'm wondering if anybody can explain what's happening with the nginx-old-init stuff in this https://github.com/saltstack-formulas/nginx-formula/blob/master/nginx/package.sls
17:55 steveoliver ?
17:56 steveoliver maybe i need to learn more about dpkg-divert (I did read up on it quickly)
17:56 forrest what are you confused about steveoliver?
17:56 mwmnj dave_den: ah ok, when will is be create? Is there some kind of salt init command?
17:56 steveoliver let me see if i can form a real question :)
17:56 forrest That's for the old style runlevel stuff that isn't present on certain OS systems
17:56 forrest err OS's
17:56 josephholsten joined #salt
17:57 jcockhren forrest: lol
17:58 jcockhren OS Systems and PIN numbers
17:58 forrest yea
17:58 steveoliver :)
17:58 viq jcockhren: Personal PIN Number ? ;)
17:58 dave_den mwmnj: if you're installing from pip, it won't be created. sorry to confuse you. you may need to manually create it. You can use the config from git: https://github.com/saltstack/salt/tree/develop/conf
17:58 mspitz Sorry, I have another dumb question.  What's the relationship between salt.modules.* and the SLS files I'd write?
17:58 mspitz For example: http://docs.saltstack.com/ref/modules/all/salt.modules.pip.html#salt.modules.pip.install
17:58 mspitz How would I actually call that function from a module?
17:58 forrest I never remember what the name is for the runlevel replacement in ubuntu
17:59 forrest mspitz, imagine the module like the underlying layer
17:59 jcockhren forrest: upstart?
17:59 forrest there we go
17:59 forrest thanks jcockhren
17:59 forrest mspitz, sometimes you have access to all the functionality in the state (the state commands use the modules), and sometimes you don't, because they have to link to each other.
18:00 forrest that's why sometimes the module commands have more options than the states do (feel free to stop me if I'm talking out of my ass here)
18:00 steveoliver this looks like a real nice formula — https://github.com/saltstack-formulas/nginx-formula/tree/master/nginx
18:00 mspitz I see.  So is there a reference as to what the states provide?
18:00 forrest http://docs.saltstack.com/ref/states/all/salt.states.pip.html
18:01 mwmnj dave_den: acutally I am seeing: /etc/salt/pki
18:01 mwmnj thats where I should put the master config?
18:01 dave_den mwmnj: so you have probably started the minion, correct?
18:01 forrest steveoliver, that nginx formula needs to be updated with a map file :P
18:01 mspitz forrest: great, thank you!
18:01 mwmnj dave_den: i've ran: $ sudo salt-master
18:01 steveoliver forrest: oh yeah?
18:01 forrest mspitz, np, the doc layout will make sense to you after a bit longer
18:02 forrest steveoliver, yea that one hasn't been updated in a bit.
18:02 steveoliver so that's what i'm wondering — what needs to be done here for you to recommend using it, forrest?
18:02 dave_den mwmnj: just put https://github.com/saltstack/salt/blob/develop/conf/master  at  /etc/salt/master
18:02 forrest There's nothing wrong with it at all
18:02 Heartsbane joined #salt
18:02 Heartsbane joined #salt
18:02 steveoliver not that i necessarily want to do that, but if it'd help
18:02 forrest it works fine, but it could just be claner.
18:02 steveoliver ok
18:02 forrest *cleaner
18:02 steveoliver gotchya
18:02 viq jesusaurus: why "codename, distro" in the first line of your state? It seems like they both would have same value?
18:03 forrest steveoliver, take a look at: https://github.com/saltstack-formulas/nagios-formula
18:03 mwmnj dave_den: ok, ty
18:03 jesusaurus viq: thats the (key, value) pair from my pillar datastructure
18:03 steveoliver ok, cool - i'll be needing nagios, too :)
18:03 steveoliver forrest: thx
18:03 forrest it's a simpler example map file wise, but it sets data in there to reduce clutter elsewhere. This project: https://github.com/terminalmage/djangocon2013-sls also uses the newer style heavily, and is an awesome example
18:04 forrest yea np, and like I said, nothing is wrong with that nginx one, it just doesn't use the newest style, which is understandable.
18:05 steveoliver the use of pillar data in those templates is what i'm interested in, atm, as I develop my nginx .sls
18:07 forrest yea it's a really cool way to do things
18:07 forrest provides a central location for making changes. I use it as part of my static blog deployment, and it works really well
18:08 viq Hm, not quite able to replicate - salt is not happy with https://gist.github.com/viq/7123612
18:08 * steveoliver looks up maps — they look real clean in the nagios example
18:09 logix812 joined #salt
18:09 ckao joined #salt
18:09 forrest yea, take a look at that django example, they are used extensively there, and are awesome
18:09 brianhicks joined #salt
18:10 toofer joined #salt
18:10 mspitz Is there a more graceful way to specify dependencies in a salt state file rather than manually adding the require: line for every subsequent requirement?
18:11 steveoliver simple.  powerful.  #bad #ass  http://salt.readthedocs.org/en/v0.17.0/topics/conventions/formulas.html#map-jinja
18:11 steveoliver mspitz: guess: require_in ?
18:11 forrest agreed, require_in
18:11 viq oh, duh, it should be name['number'] and not name.['number']
18:11 UtahDave jesusaurus: I think Tom would be open to discussing improvements in that area.  If you want to open a discussion on that with an email to the mailing list, that would be cool.
18:11 steveoliver aka "required by"
18:11 mspitz But that means updating that list every time I add something new to that state, no?
18:12 forrest you could use a loop with pillar data or something mspitz, then just modify the list in pillar, but I don't have an example.
18:12 jesusaurus UtahDave: yeah, ive been planning on doing that, but im collecting my thoughts on the subject first. i just thought i would ask if there is already a discussion that i could join
18:12 mspitz Mmkay.
18:13 mspitz Puppet has this nice syntax (its only nice syntax) where you can specify arrows to chain dependencies, but I suppose you can't do that in YAML.
18:13 forrest well, in 0.17 now you don't need to use requires
18:13 forrest by default it will parse everythin in the order of the file
18:13 forrest *everything
18:14 ausmarton joined #salt
18:14 mspitz !
18:14 mgw joined #salt
18:14 mspitz That's awesome.
18:15 forrest http://docs.saltstack.com/topics/releases/0.17.0.html#state-auto-order
18:15 forrest yea it's pretty badass
18:15 forrest especially for people who haven't used config management before
18:15 mspitz That's fantastic.
18:16 NV arguably the most useful thing about it is you can make your changes to the salt minion happen last, and thus the salt minion restart happens last, so you don't have to run highstate twice :D
18:16 UtahDave jesusaurus: We have had some minor discussions around that. Tom has mentioned that he'd like to improve how that works, so yeah, we'd love to hear your thoughts on that.
18:17 jesusaurus cool, i'll draft something up
18:17 NV actually jesusaurus - just read what you're talking about
18:18 NV I actually managed to achieve exactly that already using a python pillar jigger if I understand what you're asking correctly
18:19 NV basically define in a top.sls-like format (with full glob matching etc) the ability to assign roles to hosts and pulls in pillar data automagically if it exists for that role
18:20 NV i then give hosts roles like 'web' 'webprod' and 'webtest' (web for common between test and prod, webprod/webtest for env-specific) which the top.sls can then match on as required
18:21 NV or have i misunderstood what you mean?
18:23 ajw0100 joined #salt
18:25 NV http://pastie.org/8424757 is the code
18:26 mua joined #salt
18:26 NV on the 'would-be-nice' list is for pcre matching to be able to assign a role that includes part of the matched regex
18:26 NV ie, when matching web(test|prod) being able to assign - web\1 and have it assign webprod/webtest depending on which side matched
18:27 forrest NV, I'm imagining that being abused.
18:27 forrest web(test|prod)(dc1|dc2)(rack1|rack2|rack3|rack4) :P
18:27 NV although atm im just stealing the salt top.sls matching so probably best to just change it in salt and then top.sls can take advantage of it too
18:28 NV forrest: ah but you see you could then define roles of "web" "dc1server" "webprod"
18:28 NV although for dc1server you'd be better off matching on say *.dc1.example.com
18:28 forrest I'm just joking
18:29 NV will probably get around to hacking up a patch for extending top.sls matching when using pcre at some point :P
18:29 NV actually, that code probably needs adjusting for 0.17
18:30 NV im on holidays atm go figure :P
18:30 jesusaurus NV: i actually use a single state environment with multiple pillar environments
18:31 NV https://github.com/saltstack/salt/pull/7176 would need updating to take into account that
18:31 NV just adding some __ decorating
18:31 Brew joined #salt
18:31 jesusaurus what i want is something like: nodes matching 'rabbit*' get the rabbitmq pillar; nodes matching 'prod.example.com' look for that pillar in the prod environment, nodes matching 'dev.example.com' look for it in the dev environment
18:31 jesusaurus err, i mean *prod and *dev
18:31 NV ahh i see what you mean
18:32 NV i do that with my roles stuff by assigning rabbit* to have the rabbit role, then rabbitdev to have rabbitdev role, rabbitprod to have rabbitprod
18:32 NV which automagically pulls in pillars by the same name if they are found, then match the states on the roles pillar
18:33 NV not using salt environments at all
18:33 NV just seemed simpler that way
18:34 abishekk92 joined #salt
18:34 jslatts joined #salt
18:34 mspitz Another one: is there a way to provide a default argument to be used each time a state is used?  That is, every time I call 'pip.installed', I'd like to use 'find_links: http://mycustomurl.com/repo'
18:34 jesusaurus mspitz: unfortunatey not
18:35 NV for pillar data i have a templated yaml for say rabbit called rabbittemplate, then have rabbitprod and rabbitdev include it setting defaults for the templated parameters
18:36 NV or if it doesn't need per-env pillar data just dump it in the main rabbit pillar
18:36 m0hit joined #salt
18:37 kermit joined #salt
18:40 amahon joined #salt
18:41 amahon joined #salt
18:50 bhosmer joined #salt
18:50 taylorgumgum joined #salt
18:51 wibberwock joined #salt
18:52 wibberwock joined #salt
18:53 wibberwock anyone know the typical way to use salt with rackspace cloud dns and cloud load balancers?
18:56 forrest wibberwock, there was this blog post
18:56 akio How to list sls modules?
18:56 forrest http://developer.rackspace.com/blog/why-i-use-saltstack.html
18:57 forrest and this onehttp://developer.rackspace.com/blog/marconi-and-salt.html
18:57 forrest but no actual sls files :\
18:57 wibberwock tbh I'm more struggling with salt-cloud
18:57 wibberwock doesn't support rackspace cloud dns or load balancers as far as i can see
18:57 wibberwock and map files don't support templating or extend
18:58 GradysGhost wibberwock: Probably because those aren't compute resources. What would you like to see in terms of cloud DNS and LBs?
18:59 wibberwock i'm using salt-cloud to bring up clusters at a time.  each cluster should have dns records and load balancers as well, and it seems like i'll have to script that separately
18:59 ubercore joined #salt
19:00 ubercore Salt 0.17, I'm having trouble with virtualenv.managed
19:00 ubercore I'm getting this odd "AttributeError: 'module' object has no attribute 'virtualenv_version'" error
19:00 crow23 joined #salt
19:00 ubercore has anyone seen that recently? this state hasn't been touched in a little while, so I think it's a bootstrap/salt version thing, but I'm not positive
19:02 UtahDave wibberwock: you are correct. salt cloud doesn't yet support cloud dns or load balancers.
19:04 josephho_ joined #salt
19:04 krandun joined #salt
19:04 forrest ubercore, are you trying to see that as an option?
19:04 ubercore Nope
19:05 ubercore I'm not setting any options on the virtualenv.managed call, actually
19:07 m0hit_ joined #salt
19:07 ubercore Oh, I am. Hold on, testing something...
19:07 foxx[cleeming] joined #salt
19:07 foxx[cleeming] joined #salt
19:09 ubercore Here's the state: http://pastebin.com/rLE0siUp
19:09 ubercore I can import virtualenv and check the version (either through virtualenv_version or __version__) like the module is trying to do, so I'm not sure where the disconnect is
19:14 hjubal joined #salt
19:14 ubercore Could it be a bug? I'm wondering if virtualenv_mod is clobbering the namespace
19:14 mgw joined #salt
19:15 ubercore Ahh, yup: https://github.com/saltstack/salt/commit/bd002f97da2d0819f732d8468f984b2b23740ee9
19:16 ubercore looks like it was fixed in 0.17.1
19:16 taylorgumgum joined #salt
19:18 ubercore ... or not. I'm still getting the same error.
19:20 wibberwock joined #salt
19:22 ubercore *sigh* bootstrapping from a git tag doesn't clean removed files
19:23 forrest can you add that as an issue on the bootstrap ubercore?
19:23 ubercore If anyone else runs into this issue after upgrading to 0.17, you'll need to remove salt/modules/virtualenv.py after updating to 0.17.1
19:23 ubercore Yup, no problem
19:23 m_george|away joined #salt
19:23 forrest thanks
19:23 backjlack joined #salt
19:25 mwmnj Are renderers used to define the data format returned from salt commands?
19:26 mwmnj for instance, could I use a renderer to get the following commands output in json:  salt '*' status.cpustats ?
19:27 NV no, renderers are used to interpret sls files etc to read pillar and state information
19:27 NV https://salt.readthedocs.org/en/v0.17.0/ref/renderers/index.html has some info
19:29 NV http://docs.saltstack.com/ref/returners/ might be what you're after?
19:29 mwmnj I think this is what I am after: http://docs.saltstack.com/ref/output/all/salt.output.json_out.html
19:30 ubercore Larger meta question: we've never been able to upgrade salt versions without critical things breaking and killing our setup. Is there a point where the project hopes to have more stable releases before 1.0?
19:30 mwmnj Not sure how I would run it with the command though
19:31 mwmnj salt --json_out '*' test.ping returns invalid option
19:32 GradysGhost Running simple salt command, getting the following: "Failed to authenticate, is this user permitted to execute commands?"
19:32 GradysGhost command is being run as root
19:32 shinylasers joined #salt
19:32 ubercore GradysGhost: check your client_acl
19:32 GradysGhost what is that?
19:32 ubercore In the docs, check for Client ACL
19:32 forrest http://docs.saltstack.com/ref/clientacl.html
19:33 aberant is there a way in salt where i could get a list of all the IP's of all the other minions in a nodegroup?   or from a compound match?  now sure how to implement this
19:33 elfixit joined #salt
19:33 ubercore It's likely it's a permissions error at the salt level, not the os level
19:33 shinylasers joined #salt
19:33 GradysGhost nm, i'm stupid
19:33 GradysGhost not acls, just me changing the master conf file and not restarting the master
19:34 forrest aberant, salt -N groupName grains.items
19:34 forrest that will show you all the grain items, then do salt -N groupName grains.item ip
19:34 forrest I don't know if IP will work though
19:35 forrest I think there's a grain for ip address? I can't remember.
19:35 aberant forrest: i would need this to be passed into a template.. hmm..
19:35 aberant forrest: but this gets me further along.. thanks..
19:35 forrest aberant, http://docs.saltstack.com/topics/tutorials/states_pt3.html#using-grains-in-sls-modules
19:35 forrest take a look at that
19:35 Gareth forrest: there is.  its a list of all IPs.
19:36 forrest Gareth, do you remember what the grain name is though?
19:36 forrest I don't have a salt box at work
19:36 Gareth ipv4
19:36 Gareth there is also ip_interfaces.
19:36 Gareth which is a dict.
19:36 forrest ahh right right, thanks Gareth!
19:36 aberant but i would want all the OTHER ips..
19:36 Gareth no worries :)
19:37 aberant i'll mess with this.. thanks for your help
19:37 mwmnj Anyone able to chime in on using the output module? salt --json_out '*' test.ping
19:37 Ryan_Lane hm. when I have a module that calls __salt__[cmd.run]('something', runas='user') and use salt-call, it works fine
19:37 Gareth aberant: so you want to see all the IPs of all the minions in a group>?
19:37 forrest aberant, yea np
19:37 Ryan_Lane if I call that module from the master, it doesn't use runas and just sets the user as root
19:38 wibberwock joined #salt
19:38 logix812 is it possible to use the output of a cmd.run in another state? I don't think it is at first glance I'm just double checking in case I missed it
19:40 aberant forrest: so that link helped me come up with a better question.. is there a way to get grains for other minions.. and put that in a template?
19:40 forrest aberant I don't know, I've never experimented with that or seen an example of it.
19:41 forrest I'm sure there's some work around to make it happen
19:41 hazzadous joined #salt
19:41 NV mwmnj: ah ok, so you probably want salt-call --out json status.cpustats i assume
19:41 NV or --out=json
19:41 NV http://docs.saltstack.com/ref/cli/salt-call.html
19:41 NV see there ^^
19:41 NV i assume it works for salt as well
19:41 mwmnj NV: yea, looks like the usage may have change? https://github.com/saltstack/salt/issues/1685
19:41 NV note the caveat about using --static with --out=json
19:42 Gareth aberant: what is it that you're trying to do?
19:42 NV yeah guessing they moved to --out=* notation to make it easier to add more output modules
19:43 aberant Gareth: i'm setting up graphite.. and for the web front end, it needs to know the OTHER web front end IP's.. and horrible things happen if it's own IP is on that list
19:44 Gareth aberant: sounds like putting that information in pillar might be the way to go.
19:44 aberant Gareth: just seeing if i can cheat my way out of typing out all that info..
19:45 aberant Gareth: cause as it stands, i think i'd need to put in every permutation for each pillar file..  but there's only 4 hosts right now so shouldn't be bad
19:45 Gareth You could probably pull it all n using salt and grains calls, then script it or something to generate the pillar files.
19:46 aberant Gareth: now that's an idea..
19:47 aberant Gareth: thanks..
19:47 mwmnj Can anyone provide any insight into reasons one might use salt-cloud over libclud ?
19:47 scooby2 stupid question. Is there a way to tell salt to put scripts for cmd.script/cmd.wait_script in a different directory? We have /tmp as noexec.
19:48 UtahDave Ryan_Lane: That's pretty weird. what version of salt are you on?
19:48 giantlock joined #salt
19:48 Ryan_Lane UtahDave: I'm seeing this in both 0.17 and 0.15.3
19:48 Gareth scooby2: the cwd option maybe?
19:49 scooby2 It says CWD defaults to /root
19:49 scooby2 I will give that a shot however
19:50 avienu_ joined #salt
19:50 Ryan_Lane UtahDave: this is when using a custom module and calling __salt__['cmd.retcode'] from within it
19:51 UtahDave have you tested using   user='user' instead?
19:51 mapu joined #salt
19:52 fllr joined #salt
19:53 fllr akoumjian: Hey, dude. You the guy who created salty vagrant, right? Could you help me out real quick?
19:54 forrest fllr, just say vagrant 3 times, and you will summon him.
19:54 forrest he's like the vagrant genie
19:54 forrest or beetlejuice, I don't know
19:56 Teknix joined #salt
20:00 m0hit joined #salt
20:00 jslatts joined #salt
20:02 az87c joined #salt
20:02 az87c_ joined #salt
20:04 bhosmer joined #salt
20:05 Gifflen joined #salt
20:06 rgbkrk joined #salt
20:08 redondos joined #salt
20:08 redondos joined #salt
20:10 ajw0100 joined #salt
20:11 elfixit joined #salt
20:12 JasonSwindle joined #salt
20:13 saurabhs joined #salt
20:17 taylorgumgum joined #salt
20:17 mua joined #salt
20:22 UtahDave Just got Salt installed on my Raspberry Pi.  pretty cool so far
20:22 amckinley joined #salt
20:23 HeadAIX joined #salt
20:25 krandun UtahDave: Which distro is it running?
20:25 baffle $1 it's Raspbian.
20:25 UtahDave raspian
20:25 krandun Nifty.
20:25 UtahDave baffle wins!
20:25 baffle \o/
20:25 UtahDave yeah, I just followed the debian wheezy install instructions and it worked great
20:26 mspitz Is there a nice example repo out there using dev/prod pillar environments?
20:26 mspitz I'm pretty confused.
20:27 m_george left #salt
20:30 dcrouch joined #salt
20:31 ctdawe joined #salt
20:37 Gareth UtahDave: Model B?
20:38 UtahDave Gareth: Uh, it's the pi they gave out at pycon
20:39 Gareth UtahDave: probably model b.
20:39 Gareth 512MB of ram.
20:39 Gareth two USB ports.
20:39 UtahDave yeah, 2 usb ports
20:39 redondos joined #salt
20:39 redondos joined #salt
20:40 ausmarton joined #salt
20:40 woebtz joined #salt
20:40 cachedout joined #salt
20:40 ubercore Yeah, pycon was model b
20:40 ubercore I used the pycon one to upgrade my xbmc :)
20:41 ubercore kind of neat just swapping out the sd card to the model b and it just working
20:41 krandun The "B" has an onboard Ethernet jack, but "A" doesn't.
20:41 xmltok is a grain just a python script with a function in it? im using saltversioninfo as an example but i do not see my new grain function as a grain. i have run sync_grains and i can see the script on my minion
20:41 UtahDave Ah, gotcha. I definitely have model b, then.   2 usb ports, ethernet.
20:41 Gareth There were two versions of the A...one had ethernet...the other did not.  iirc.
20:42 c0bra joined #salt
20:42 xmltok i found my problem in the dict it was returning
20:43 kickerdog joined #salt
20:44 josephholsten joined #salt
20:45 Gareth maybe not :)  two version of the B...one with 256MB...that makes more sense.
20:53 amckinley joined #salt
20:54 jumperswitch joined #salt
20:55 mspitz I think I'm missing something with salt/pillar.
20:56 mspitz As I understand it, I'm supposed to set the environment with salt/top.sls, yes?
20:56 mspitz Does that environment get used when evaluating my pillar/top.sls?
20:56 mspitz http://pastie.org/private/wwf1sjdcj59rur45ttegrq
20:56 cewood joined #salt
20:56 mspitz Here's my minion config: http://pastie.org/private/7z9tf7r9xnayjxrdrigta
20:58 mspitz Basically, I'd like to specify pillar data per environment.
20:58 mspitz But I don't want to have to duplicate specifying the hosts that belong in each environment both in salt/top.sls and pillar/top.sls
20:58 mspitz What am I missing?
21:00 taylorgumgum joined #salt
21:03 dthom91 joined #salt
21:06 jdenning joined #salt
21:06 sciyoshi joined #salt
21:07 akoumjian fllr: hey you still here?
21:07 * akoumjian is now known as the Salty Vagrant genie
21:09 Thiggy joined #salt
21:09 pipps1 joined #salt
21:10 logix812 in cmd.call, can you not construct more states you would like to run and execute?
21:10 logix812 in a pydsl based state
21:11 xet7 joined #salt
21:14 taylorgumgum joined #salt
21:15 jergerber joined #salt
21:18 nitin_ joined #salt
21:18 logix812 When trying to add states from within a cmd.call, I get an IndexError: list index out of range
21:19 Fandekasp joined #salt
21:19 dthom91 joined #salt
21:20 pentabular joined #salt
21:21 torandu joined #salt
21:22 logix812 Here's my use case: I need to move a postgres conf file into place on deb/ubuntu. the pkg is installed with the version of the database in the path, so I need to get that version to know the proper path
21:22 nliadm came up with a good name for a project that uses salt as its messaging layer: wound
21:23 logix812 So I need to require that postgres is installed before I can call out to get the version
21:24 logix812 pydsl seems like it's a good fit for this, but states don't seem to like being run from within the target of a cmd.call
21:25 jalbretsen joined #salt
21:25 Brew joined #salt
21:28 mgw joined #salt
21:30 saurabhs left #salt
21:30 Ryan_Lane :(
21:30 Ryan_Lane 0.17.1 isn't reporting pkg upgrades in its output
21:30 Ryan_Lane all I get back is:  ----------
21:30 Ryan_Lane though it is upgrading the packages
21:34 taylorgumgum joined #salt
21:35 Ryan_Lane hm. weird. some hosts are
21:37 Ahlee anybody got a prebaked salt module for accessing cisco/arrista switches via saltstack?
21:38 Narven joined #salt
21:41 mwmnj joined #salt
21:41 hazzadous joined #salt
21:42 mgw joined #salt
21:44 joehh joined #salt
21:48 druonysuse joined #salt
21:49 whiskybar how should I copy a file from the master to a minion, outside of salt:// and using a module?
21:50 Corey salt-cp!
21:51 KyleG joined #salt
21:51 KyleG joined #salt
21:52 whiskybar Corey: v. good thanks that's it!
21:52 brimpa joined #salt
21:53 jalbretsen left #salt
21:55 alexheneveld joined #salt
21:57 dthom91 joined #salt
22:00 mgw joined #salt
22:00 quantumsummers|c left #salt
22:02 mwmnj joined #salt
22:04 ubercore joined #salt
22:05 kermit joined #salt
22:07 cbloss has anything changed with 0.17.1 with how state files call pillar variables or how if statements are formatted? after upgrading to 0.17.1 some of my states broke and am not sure why
22:07 amahon joined #salt
22:07 forrest what does the error look like cbloss?
22:08 xmltok i am able to match a grain on the command line with -G item:val but i can't match that grain in the top.sls, i've tried iwth G@item:val and item:val with - match:grain, what could i be doing wrong?
22:08 forrest xmltok, http://docs.saltstack.com/ref/states/top.html#other-ways-of-targeting-minions
22:10 xmltok forrest: i believe I am doing that, check it out http://pastebin.com/Knipcy21
22:12 cbloss forrest: http://pastebin.com/dy0tq7BW
22:12 cbloss a lot of little things like this
22:12 forrest xmltok, are your machines defined as groups in a SerialNumber group?
22:13 xmltok not in the end, right now i am grouping them that way since i only have a single node in each environment and i want to be able to test the filtering
22:13 forrest cbloss, interesting, so the item seems to be broken up into a list, maybe try single quotes around the items?
22:13 cbloss forrest: in the pillar?
22:13 forrest well, each of those items is one letter or character in your path
22:14 forrest it seems odd that it would be breaking it up like that
22:14 forrest it's like when you do a a for loop
22:14 forrest but screw it up in python
22:14 forrest so it goes through each letter of the string, instead of the string itself.
22:15 xmltok yeah cbloss it looks like your list is being interpreted as a string
22:15 cbloss putting it in quotes in the pillar didn't help.
22:15 forrest hmm
22:16 Linz joined #salt
22:16 cbloss it is seeing the whole pillar this way i think
22:16 cbloss {% for site, args in pillar.get('sites', {}).items() %}
22:16 cbloss is the top level pillar.get
22:16 xmltok whats sites look like where its defined
22:17 mgw joined #salt
22:17 cbloss xmltok: http://pastebin.com/UYYsMyiD
22:18 cbloss the alias is messed up too... does the character issue
22:18 xmltok im by no means qualified to say, but id guess that is a bug
22:20 cbloss what is weird i don't think any of my other states are having a problem
22:26 m_george|away joined #salt
22:30 KyleG joined #salt
22:30 KyleG joined #salt
22:30 xmltok my top.sls works now that i ran salt-call state.highstate from my minions, i guess i need to sync the top.sls file over before i can run salt '*' state.highstate?
22:33 mgw joined #salt
22:38 mafrosis joined #salt
22:48 m0hit_ joined #salt
22:50 UtahDave xmltok: the highstate should sync everything over for you.
22:51 jcockhren x/quit
22:53 dthom91 joined #salt
22:54 bhosmer joined #salt
22:55 SEJeff_work joined #salt
22:56 mgw joined #salt
23:00 ncjohnsto joined #salt
23:00 NinjR joined #salt
23:00 NinjR left #salt
23:02 jumperswitch joined #salt
23:06 m0hit joined #salt
23:08 Ryan_Lane hm. weird. my runas issue went away too
23:08 Ryan_Lane I upgraded everything to 0.17.1
23:09 forrest before you had just upgraded the master Ryan_Lane?
23:09 Ryan_Lane well, no
23:09 Ryan_Lane I was running a test env with 0.17
23:09 Ryan_Lane and a prod environment with 0.15.3
23:12 amckinley joined #salt
23:12 pipps joined #salt
23:14 tallpaul joined #salt
23:15 toofer joined #salt
23:16 pentabular joined #salt
23:22 jslatts joined #salt
23:38 alunduil joined #salt
23:42 mwmnj joined #salt
23:45 mwmnj Does the salt-master persist which minion nodes it has a connection with?
23:50 cachedout joined #salt
23:52 __number5__ what do you mean by persist?
23:53 honestly salt-master doesn't have persistent connections with minions
23:54 dthom91 joined #salt
23:58 mwmnj _number5_: I am trying to figure out how the master knows who its minions are
23:58 mwmnj I see this: http://docs.saltstack.com/ref/configuration/master.html#minion-data-cache
23:59 mwmnj and i've read this:
23:59 mwmnj http://docs.saltstack.com/ref/topology.html
23:59 mwmnj But it is still unclear exactly how the master knows which server to connect to using what ssh credentials

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