Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-10-13

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

All times shown according to UTC.

Time Nick Message
00:02 Mso150 joined #salt
00:06 bhosmer joined #salt
00:12 invsblduck joined #salt
00:14 badon_ joined #salt
00:16 TheThing joined #salt
00:23 invsblduck left #salt
00:30 UForgotten joined #salt
00:36 mechanicalduck joined #salt
00:44 deeprave joined #salt
00:46 kingel joined #salt
00:53 scoates joined #salt
00:58 diegows joined #salt
01:08 hardwire joined #salt
01:10 elfixit joined #salt
01:11 malinoff joined #salt
01:11 borgstrom joined #salt
01:17 jalaziz_ joined #salt
01:33 sysdoc joined #salt
01:52 acabrera_ joined #salt
01:55 sroegner_ joined #salt
01:55 bhosmer joined #salt
02:03 jeddi joined #salt
02:13 badon_ joined #salt
02:14 otter768 joined #salt
02:19 ramishra joined #salt
02:26 schristensen joined #salt
02:35 kingel joined #salt
02:55 Nexpro1 joined #salt
02:57 Saravanan joined #salt
03:02 mosen joined #salt
03:09 balltongu_ joined #salt
03:16 n8n joined #salt
03:21 UForgotten joined #salt
03:21 balltongu joined #salt
03:40 pipps joined #salt
03:44 bhosmer joined #salt
03:56 sroegner_ joined #salt
03:56 n8n joined #salt
04:07 pipps joined #salt
04:15 pipps joined #salt
04:23 floWenoL_ joined #salt
04:27 dccc_ joined #salt
04:42 felskrone joined #salt
04:51 ramteid joined #salt
05:01 Outlander joined #salt
05:20 Katafalkas joined #salt
05:24 kingel joined #salt
05:32 bhosmer joined #salt
05:34 stephanbuys joined #salt
05:36 calvinh joined #salt
05:39 desposo joined #salt
05:39 linjan joined #salt
05:40 hardwire joined #salt
05:49 oyvjel joined #salt
05:56 sroegner_ joined #salt
06:03 colttt joined #salt
06:05 swah joined #salt
06:17 lopez joined #salt
06:18 ramishra joined #salt
06:41 cberndt joined #salt
06:46 rattmuff joined #salt
06:48 lcavassa joined #salt
06:48 kingel joined #salt
06:53 desposo joined #salt
06:54 trikke joined #salt
07:01 FreddyFlatFoot joined #salt
07:02 tomspur joined #salt
07:02 tomspur joined #salt
07:02 duncanmv joined #salt
07:05 flyboy joined #salt
07:14 linjan joined #salt
07:18 TyrfingMjolnir joined #salt
07:19 cberndt joined #salt
07:21 bhosmer joined #salt
07:22 oyvjel joined #salt
07:35 intellix joined #salt
07:39 CycloHex joined #salt
07:40 CycloHex Hello guys! I have a server I deploy with salt, this runs a service, But I actually only want the service to be in running state after git completed cloning. I have tried requires on the .sls file and all, but the service starts running before the git lcone has been done. I'm really not sure how to rearrange these sls files in order to have my git cloned first
07:44 aquinas joined #salt
07:44 Katafalkas joined #salt
07:45 aquinas_ joined #salt
07:46 CycloHex When my minion gets deployed through the cloud it runs an initial highstate. Is it possible for me to get the output of the state afterwards??
07:47 trikke joined #salt
07:53 CycloHex Say I have the following states to be executed: core, git, nginx, odoo, postgres .. I would like the order of these states to be core, postgres, git, odoo, nginx. I am not familiar with the watch or required functions, I just cannot seem to get these requisites to work :(
07:57 sroegner_ joined #salt
07:58 oyvjel joined #salt
07:59 wr3nch joined #salt
08:00 oyvjel joined #salt
08:02 wnkz joined #salt
08:04 PI-Lloyd joined #salt
08:08 babilen CycloHex: You either want a require: on the git.latest state that does the cloning in your service.running state or a require_in on the service.running state in your git.latest
08:16 bhi joined #salt
08:18 briner joined #salt
08:18 CycloHex Ok, thanks.. it's not working yet, but I'll keep trying... Is there a difference between the require and the requireD requisite?
08:18 CycloHex if so, what is the difference.. As I'm unable to find the big difference
08:22 TheThing joined #salt
08:25 damaex joined #salt
08:27 akafred joined #salt
08:27 Mso150 joined #salt
08:30 kingel left #salt
08:40 CeBe joined #salt
08:43 N-Mi joined #salt
08:52 TheThing joined #salt
09:02 ze- the documentation states that jobs cache should by default only be kept 1 day. Anyone able to explain where/how cleaning works, so i can try to check why it doesn't on our server?
09:07 astol joined #salt
09:09 zemm joined #salt
09:10 bhosmer joined #salt
09:11 AxelFooley joined #salt
09:11 AxelFooley hey guys
09:12 salted_ joined #salt
09:12 AxelFooley someone experienced with "salt-ssh" that could explain me why, when i launch "salt-ssh 'dev-sql-test' state.sls salt-install test=True" i get Unable to fetch the latest changes from remote ssh://git@gitlab.farm/sistemi/saltstack-pillars.git: 'git fetch' returned exit status 255: error: cannot open .git/FETCH_HEAD: Permission denied
09:12 AxelFooley obviously file permissions are ok
09:13 AxelFooley -rw-r--r-- 1 salt-master salt-master 123 Oct 13 11:08 ./master/pillar_gitfs/0/.git/FETCH_HEAD
09:13 AxelFooley -rw-r--r-- 1 salt-master salt-master 115 Oct 13 11:08 ./master/gitfs/c5ae1d8deae1cee8ca6f58a9f9a23998/.git/FETCH_HEAD
09:14 AxelFooley the gitfs backend works fine, because if i install manually a minion, and the use simply the salt command toward it, the states are applied correctly
09:15 salted_ hi guys, does anyone know if inside a sls I can obtain the value of a custome CLI argument? e.g. 'salt-call state.highstate --customArg=val'
09:15 AxelFooley if the "val" argument has to be applied to the minion, i guess you can use pillars
09:17 agend joined #salt
09:19 salted_ I actually do use Pillar. I have a  default value to this argument but I want the caller to be able to specify it when they run salt-call. a typical scenario for that would be, say, Salt fetches a file from me and there are two locations that this file can be found at. One of them is the default location (i.e. a remote) and the other one is a local one, which can be activated by passing the custom argument
09:20 colttt joined #salt
09:20 salted_ I'm fairly new to Salt so am sorry if I'm totally missing the point.
09:21 xmj one idea is that salt states are automatically applicable
09:21 xmj so, requiring a CLI argument is ... sort of not ok
09:21 xmj you de-automate.
09:22 babilen salted_: You typically don't want to use states in that case, but execution modules. States should, IMHO, be self-contained in the entirety of /srv/{salt/pillar} and not rely on arguments that have been passed on the command line.
09:22 babilen In fact I would strongly recommend to not do that (and that is British understatement)
09:23 babilen You can, however, pass a pillar on the command line if you insist on doing this. If you could tell us what you are trying to achieve here we might be able to suggest alternatives or better approaches though.
09:23 salted_ I see.
09:25 xmj babilen: can you actually override a pillar (provided in /srv/pillar or whatevs) with a command ?
09:25 babilen But to elaborate a bit more: There are, actually, two sides to this. The first is that you typically target a number of states to your minions via the top.sls and it are these states that should not rely on any command line switches.
09:25 chiui joined #salt
09:25 flyboy82 hey guys, dows mine.get support grains based targeting in the 'tgt' argument?  eg. salt '*' mine.get 'G@fqdn:minion' 'network.ip_addrs'
09:26 salted_ babilen: Basically I have a binary file which I fetch from S3 and that works fine. However in case of, say you don't have internet access, I'd like Salt to look for it in a local folder instead since this binary can be built locally too. Does this make sense?
09:26 babilen xmj: Pillars are merged with a simple "some_dictionary.update(some_other_dictionary)" in Python and the pillars that you pass on the command line are, presumably, merged in last. That would mean that the values for keys defined in the manually passed one would override the ones defined in /srv/pillar
09:28 babilen xmj: I am not using this often (ever?) so I'd test the behaviour yourself before you rely on this.
09:29 babilen salted_: That makes perfect sense.
09:31 babilen salted_: I might approach the problem a bit differently. You could have a state that downloads the file and then trigger the build if that fails. You would, probably, would use the onfail requisite (http://docs.saltstack.com/en/latest/ref/states/requisites.html#onfail) that will be introduced in the next salt version that is scheduled for release soon™.
09:31 fredvd joined #salt
09:32 babilen That doesn't help you right now though ...
09:33 salted_ babilen: That sounds great however I would also like to have the ability to maunally specifcy which location Salt should use to fetch this file.
09:33 babilen I mean you could, in this case, pass a pillar with "{'offline': True}" manually and include/target different states based on the value of that minion.
09:34 babilen How come your servers aren't online and why can you talk to them from your master if they aren't? (just asking, trying to understand what you are actually trying to do here)
09:34 giantlock joined #salt
09:34 gfa can i do math on a state file? i want to set a variable on config file according to to host ram
09:34 salted_ Luckily these are not my servers :) It's just the local development envorinment that runs in vagrant VMs
09:35 babilen gfa: You can write states in pure Python and you can do some maths with jinja2 http://jinja.pocoo.org/docs/dev/templates/#math
09:35 salted_ I want developers to be able to test their changes luckily without pushing a lot of snapshot binariers to S3 and then fetching them.
09:36 istram joined #salt
09:37 agend joined #salt
09:37 gfa babilen: cool, that is what i want :) the jinja2 i already have a lot of states in jinja i don't want to rewrite them in python
09:37 zemm joined #salt
09:37 gfa babilen: thanks
09:37 babilen salted_: Okay, in that case I would start by setting a local grain in the minion config used by vagrant so that you can differentiate between production servers and dev environments. That allows you to target different states (were applicable) and pillars based on that. Secondly it is, IMHO, perfectly fine to pass pillars manually.
09:39 babilen salted_: You might also want to write "interactive" states and "non-interactive" states and run the former *only* via salt 'sometarget' state.sls  ...
09:39 salted_ Thanks a lot babilen. I think passing pillars manually would perfectly do it. I'll look into doing that.
09:40 salted_ I see.
09:40 salted_ you have been very helpful - thanks very much again.
09:40 babilen It really depends on the particulars in this case and I wouldn't be happy to rely on manually given information. You can (and will soon) be able to model depedencies like this perfectly in salt without your developers ever having to care about it.
09:41 babilen I can, however, not think of a way to require two alternative states in such a way that the success of one of them would allow the requisite to be satisfied.
09:41 babilen ...
09:41 babilen That would actually be a neat feature.
09:42 babilen Which is why I mentioned the onfail requisite that you will be able to use soon.
09:42 salted_ well yeah that was the idea behind having a custom argument rather than passing pillars manually so that all they had to do was to tell salt which location it should look for the binary in
09:42 viq SOON....
09:42 salted_ :)
09:44 salted_ let's also see how soon we can upgrade to the lastest version. but for now, I'll rely on passing pillars
09:44 babilen salted_: It is, IMHO, fine to do it in this case. People will use it interactively anyway, but states defined in top.sls should be able to run without *any* human interaction and be, preferably, also be a no-op if you didn't change their definition. (e.g. no automatic package upgrades)
09:45 babilen I mean that isn't a hard rule as well (e.g. checkout HEAD in git states, ...), but it is something that I try to ensure in my states.
09:45 zemm joined #salt
09:46 salted_ I totally agree with you and that's precisely what I'm trying to achieve.
09:49 student__ joined #salt
09:52 Outlander joined #salt
09:55 student__ Hi all, Could you help me please. I am using salt on gentoo and I want to install some packages in different slots through the salt. I tried to write states, but option slot was ignored
09:58 sroegner_ joined #salt
09:58 smcquay joined #salt
09:58 martoss joined #salt
09:59 student__ but when I set version - package is installed to the according slot
10:00 student__ media-libs/tiff:   pkg.latest: - slot: 3
10:01 student__ doesn't work
10:01 calvinh joined #salt
10:01 student__ (this state is installed in 0 slot)
10:03 viq joined #salt
10:09 astol joined #salt
10:10 tmh1999 joined #salt
10:12 tmh1999 joined #salt
10:12 astol1 joined #salt
10:22 flyboy82 hey guys, dows mine.get support grain-like based targeting in the 'tgt' argument?  eg. salt '*' mine.get 'G@fqdn:minion' 'network.ip_addrs'
10:23 flyboy82 I know targeting by grains in mine.get shouldn't work since mine resides on the master
10:23 workingcats joined #salt
10:24 flyboy82 I want to get the network.ip_addrs function results only for minions that also send a certain other key th the mine
10:27 bhosmer joined #salt
10:28 babilen Hmm, what should happen if I pass a pillar on the command line as list: http://docs.saltstack.com/en/latest/topics/tutorials/pillar.html#setting-pillar-data-on-the-command-line
10:29 babilen IMHO a pillar has to be a dictionary and salt, rightfully IMHO, complains about "ERROR executing 'state.highstate': Pillar data must be formatted as a dictionary" if that example is executed.
10:34 babilen Could an op "+b *!~juuso@vonk.iki.fi$##fix_your_connection" ? The constant nick-cycling is starting to be quite annoying.
10:37 wnkz_ joined #salt
10:38 linjan joined #salt
10:47 calvinh_ joined #salt
10:50 calvinh joined #salt
10:54 calvinh_ joined #salt
10:56 giannello joined #salt
10:59 bhosmer_ joined #salt
10:59 ramishra joined #salt
11:01 salted_ joined #salt
11:02 salted_ left #salt
11:03 bigl0af joined #salt
11:07 _ale_ joined #salt
11:14 johtso joined #salt
11:14 johtso shouldn't ps.pkill be available on 2014.7.0rc3-58-gf12e594 ?
11:14 Nazca joined #salt
11:14 johtso I'm getting "'ps.pkill' is not available."
11:17 johtso oh oops, didn't notice it had a dependancy
11:18 dccc_ joined #salt
11:21 bmcorser joined #salt
11:23 astol joined #salt
11:29 bhosmer joined #salt
11:32 stephanbuys joined #salt
11:38 diegows joined #salt
11:43 httpdss joined #salt
11:45 rattmuff I'm trying to find a small example of parsing the state result as JSON using python but can't find the resources I knwo I've seen before /
11:45 rattmuff :/
11:45 stephanbuys joined #salt
11:52 VSpike Is there an equivalent of an assert in salt? I want to write a state that will only work on a 64-bit OS, and fail with a warning if someone tries to use it on a 32-bit one
11:58 tinuva joined #salt
11:59 sroegner_ joined #salt
11:59 intellix joined #salt
12:02 hasues joined #salt
12:02 micah_chatt joined #salt
12:04 damaex cpuarch: x86_64
12:06 flyboy82 is there any other way to target mine data besides minion_id?
12:06 babilen VSpike: You should simply conditionally run that state based on the architecture .. why do you want it to fail?
12:11 kbyrne joined #salt
12:12 CycloHex Is it possible to find the output of a highstate that runs immediatly after the deployment? (I'd like th eoutput that a salt-call state.highstate gives, but for the job that started on deployment)
12:19 linjan joined #salt
12:20 flyboy82 left #salt
12:21 jpl1079 joined #salt
12:21 londo joined #salt
12:23 sirtaj joined #salt
12:23 Ironhand joined #salt
12:23 sgate1 joined #salt
12:24 zemm joined #salt
12:24 baffle joined #salt
12:24 nihe joined #salt
12:24 eofs joined #salt
12:24 hellerbarde joined #salt
12:25 the_lalelu joined #salt
12:25 jagardaniel joined #salt
12:27 ntropy joined #salt
12:30 ericof joined #salt
12:33 gildegoma joined #salt
12:37 puddingMe joined #salt
12:39 vbabiy joined #salt
12:47 micah_chatt joined #salt
12:48 bhosmer joined #salt
12:51 iamsam joined #salt
12:51 iamsam left #salt
12:51 flyboy82 joined #salt
12:55 vejdmn joined #salt
12:56 cpowell joined #salt
12:57 csa__ 'mn
12:58 ze- arg. I have trouble when restarting the salt-master. some 1k+ minions, 10 threads. but the master is using alot of CPU, and minions get "Waiting for minion key to be accepted by the master.", though they are already accepted.
13:00 workingcats ze-, normal, i get that error, too, e.g. when a network error prevents contact between minion and master. should work next time the minion tries
13:01 ze- i had it for over half an hour.
13:01 ze- and right now, getting "SaltReqTimeoutError: Waited 3 seconds" (not sure when it changed)
13:01 bhosmer joined #salt
13:05 johtso What option do I need to specify to hide all unchanged state results?
13:07 racooper joined #salt
13:08 VSpike babilen: I could try to handle the 32-bit case, but it's complicated and difficult to do so, and also pointless because I'm dealing with Windows Server which is 64-bit only since Svr 2008. So, the state will only work for 64 bit and I have no version to cover 32 bit
13:10 kusams joined #salt
13:11 AxelFooley i get "AttributeError: 'str' object has no attribute 'get'" every time i try to use the pkg.installed function
13:11 AxelFooley anyone experienced this?
13:12 nitti joined #salt
13:12 vejdmn1 joined #salt
13:13 VSpike babilen: so basically I'm making a "this will never happen" assumption and that leaves me slightly uncomfortable, so I wanted a way to abort early if any fool ever tries it on a Windows 32-bit desktop :)
13:14 astol joined #salt
13:14 sgate1 joined #salt
13:16 istram joined #salt
13:16 micah_chatt joined #salt
13:16 babilen VSpike: You don't have to define an else to every if. It is perfectly fine to be blank/not applied if the state doesn't, well, apply to that platform
13:17 nitti joined #salt
13:17 martoss1 joined #salt
13:17 vejdmn joined #salt
13:17 martoss2 joined #salt
13:19 CycloHex AxelFooley, can you pastebin your statrfile in which you get the error?
13:20 Deevolution joined #salt
13:20 CycloHex statefile*
13:21 AxelFooley CycloHex, thanks, the problem was related to the "python-apt" package missing on the minion, debian guys didn't compiled the salt-minion package with that dependancy
13:22 CycloHex (y)
13:22 anotherZero joined #salt
13:22 kermit joined #salt
13:26 anotherZero joined #salt
13:30 vejdmn1 joined #salt
13:31 vejdmn joined #salt
13:31 jpl1079 joined #salt
13:34 kusams joined #salt
13:34 Twiglet_ joined #salt
13:38 spo0nman joined #salt
13:38 vejdmn joined #salt
13:40 spo0nman I'm trying to use salt-cp to distribute a 5mb file, but it never gets copied, smaller files 10-100KB get distributed fine. I'm using large --timeout values too, is there a config variable i'm missing?
13:41 eliasp spo0nman: deploying +300MB files just fine here…
13:42 eliasp spo0nman: running 2014.1.x
13:42 spo0nman eliasp: yeah! 2014.1.11
13:42 jeddi joined #salt
13:43 perfectsine joined #salt
13:43 spo0nman eliasp: any clues how to debug further? small files distribute fine. large ones don't
13:44 eliasp spo0nman: well, you could run "salt-call -l debug state.highstate your.state" directly on a affected minion to get more details ("-l debug" or for even more "-l trace")
13:44 eunuchsocket joined #salt
13:44 spo0nman eliasp: let me give it a shot
13:44 eliasp spo0nman: you can also execute this remotely on the minion using "salt --timeout=2000 your-minion cmd.run 'command from previous line'"
13:49 glyf joined #salt
13:49 ramishra joined #salt
13:51 saltnoob joined #salt
13:52 saltnoob hi, is anyone using the gpg renderer from 2014.7 with 2014.1 ?
13:52 AxelFooley seems that "salt-ssh" doesn't use the gifs backend, i created a state file and pushed it to the repo, but when i call "salt-ssh -l debug 'test-minion' state.sls kickstart" it says "No matching sls found for 'kickstart' in env 'base'"
13:53 AxelFooley i have to use only local file backend with salt-ssh?
13:53 AxelFooley using gitfs backend with normal salt command works just fine
13:54 dude051 joined #salt
13:55 CeBe1 joined #salt
13:55 spo0nman eliasp: the command never reaches the minion, it just times out.
13:56 spo0nman for large files. but for small i see the job on the minion
13:58 spo0nman eliasp: what version of zero mq do you have?
13:59 eliasp spo0nman: http://pastebin.kde.org/pgl7pv87a
14:00 sroegner_ joined #salt
14:00 spo0nman eliasp: thanks
14:01 AirOnSkin joined #salt
14:01 slav0nic joined #salt
14:01 kusams joined #salt
14:01 AirOnSkin Hey guys, question: If I define multiple environments via file_roots, does that mean I also have multiple top.sls files (one per environment), or is it still just one top.sls?
14:02 micah_chatt joined #salt
14:03 eliasp AirOnSkin: multiple top.sls will be merged before they're evaluated…
14:03 spo0nman eliasp: http://pastebin.com/raw.php?i=GyT8Fyfn
14:04 hobakill joined #salt
14:05 salted_ joined #salt
14:06 stephanbuys joined #salt
14:06 AirOnSkin eliasp: that means it doesn't really matter if i have multiple ones or only one...
14:08 vejdmn joined #salt
14:08 eliasp having a single one makes your life usually easier, as you won't run into situations where you forgot about something in another environment's top.sls…
14:09 AirOnSkin eliasp: ok, great. thank you :)
14:09 eliasp AirOnSkin: so if you're using GitFS, place your top.sls in a separate repo with only a "master" branch
14:13 miqui joined #salt
14:18 ekristen joined #salt
14:19 kaptk2 joined #salt
14:19 linjan joined #salt
14:20 felskrone joined #salt
14:20 thedodd joined #salt
14:21 pdayton joined #salt
14:22 spo0nman eliasp: a strange thing is going on
14:23 spo0nman salt '*' cp.get_file salt://a /tmp/a works well with large files
14:23 spo0nman salt-cp croaks
14:23 spo0nman just times out, no matter how big is the timeout
14:24 eliasp spo0nman: that's weird… but you might have to wait for one of the devs or so… I don't know much about the internals of 'cp'
14:24 spo0nman sure. i can hang around
14:24 bernieke joined #salt
14:26 iggy I think someone else was saying something similar the other day
14:26 iggy didn't catch if they got it fixed
14:27 spo0nman iggy: you're referring to salt-cp?
14:27 iggy si
14:28 spo0nman ok. will it help if i filed a bug?
14:28 Zedman9991 joined #salt
14:29 iggy it never hurts (assuming you make sure one doesn't already exist, etc.)
14:29 spo0nman iggy: i'll search github and if it's not there. i'll create one
14:30 eliasp I'd love if the saltstack issues where tagged with the affected state/module where possible…
14:30 eliasp would make looking for such things way easier
14:30 spo0nman eliasp: oh! that would be awesome.
14:30 iggy eliasp: file a bug ;p
14:30 eliasp iggy: ha! got me! ;)
14:30 mpanetta joined #salt
14:30 eliasp iggy: will talk to one of the saltstack guys later today when they're online
14:32 mpanetta joined #salt
14:32 timoguin eliasp: a version_affected tag would be nice too
14:33 eliasp timoguin: +1
14:36 KennethWilke joined #salt
14:40 ze- I'm trying to use "master_job_cache: redis", but it doesn't seem to have any effect.
14:40 spo0nman https://github.com/saltstack/salt/issues/16592
14:41 flyboy82 you fellas know if there is a way for me to print some variables I'm generating from mine data to debug output while running an sls?
14:41 smcquay joined #salt
14:41 iggy if you find something, do share
14:41 elfixit joined #salt
14:42 kusams joined #salt
14:44 eliasp comment on https://github.com/saltstack/salt/issues/16593 regarding labeling improvements if you want…
14:44 manfred flyboy82:  i just dump them to a file.managed
14:49 wnkz joined #salt
14:56 thedodd joined #salt
14:58 vejdmn joined #salt
15:01 ggoZ joined #salt
15:02 conan_the_destro joined #salt
15:05 thedodd joined #salt
15:05 StDiluted joined #salt
15:09 eriko joined #salt
15:12 ze- any idea when 2014.7 might be stable?
15:12 mechanicalduck joined #salt
15:12 ze- more likely within a few weeks, or several monthes ?
15:16 iggy well... several months would be 2015
15:16 iggy so at the very least it would be annoyingly named
15:16 ze- yeah, still it's not considered "stable" yet... so, when is Helium going stable :)
15:17 iggy there's a chemistry joke there somewhere
15:19 ze- ... but not intended :)
15:19 iggy I've been hearing 2 weeks for 4 weeks, so...
15:21 SheetiS joined #salt
15:23 Gareth ze-: there were two blocker bugs as of Friday, sounded like one of those got fixed.  Haven't heard about the other one.
15:26 jhulten joined #salt
15:27 thedodd joined #salt
15:27 thedodd joined #salt
15:28 jalbretsen joined #salt
15:29 ajolo joined #salt
15:29 rypeck joined #salt
15:29 pdayton joined #salt
15:29 mpanetta_ joined #salt
15:32 jmdcal joined #salt
15:32 jmdcal howdy
15:34 mpanetta joined #salt
15:35 jmdcal i am having a problem that salt is trying to deploy my emacs temp files from the state directory
15:36 eliasp jmdcal: is your state directory from GitFS?
15:36 eliasp jmdcal: if so, add appropriate entries to your .gitignore
15:36 pipps joined #salt
15:36 jmdcal i am just doing a local test, had a foo~ and .#foo
15:36 jmdcal i was editing in the state dir
15:37 jmdcal /srv/salt/_states
15:37 jmdcal it is not a big problem, but was confusing, i fixed it, removing the temp files.
15:38 eliasp jmdcal: yeah, I don't think the plain-FS fileserver supports any 'exclude' statements… you could use an exclude_pat in your file state
15:39 eliasp jmdcal: see the 'exclude_pat' option: http://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.recurse
15:39 wnkz___ joined #salt
15:40 ckao joined #salt
15:40 jmdcal ok thanks
15:41 student__ I am using salt on gentoo and I want to install some packages in different slots through the salt. I tried to write states, but option slot was ignored
15:42 student__ I'm using pkg.latest
15:43 kickerdog joined #salt
15:43 student__ May be who knows, what should I do
15:43 eliasp student__: did you try to simply use the slot in the package atom, like foo/bar:3 vs foo/bar:5?
15:43 kickerdog Started seeing this, this morning, anyone else, when running "salt '*' state.highstate"
15:43 kickerdog TypeError encountered executing state.highstate: Cannot serialize ConstructorError(). See debug log for more info.  Possibly a missing arguments issue:  ArgSpec(args=['test', 'queue'], varargs=None, keywords='kwargs', defaults=(None, False))
15:45 student__ The following package(s) were not found, and no possible matches were found in the package db: media-libs/tiff:3
15:45 wnkz joined #salt
15:45 eliasp student__: let me have a look
15:45 student__ when I wroute media-libs/tiff:3
15:47 StDiluted joined #salt
15:47 kickerdog nevermind
15:47 eliasp student__: ah, I see… salt.modules.ebuild (which is used as backend for the 'pkg' state) has a slot=':X' param…
15:48 eliasp student__: you tried to use that and it didn't work as expected?
15:48 eliasp student__: what was the result when you tried to install media-libs/tiff with slot='3'?got 4.0.3-r6 from SLOT=0?
15:49 student__ <eliasp> yes, I can' install into custom slot
15:49 student__ yes, got 4.0...
15:50 eliasp ok… let's see if I can find something obviously wrong with the slot handling
15:50 eliasp student__: which salt version do you have running on your affected minion?
15:51 kwmiebach______ joined #salt
15:51 student__ pkg.latest:     - name: media-libs/tiff     - slot: 3
15:51 student__ salt 2014.1.11 (Hydrogen)
15:51 eliasp ok
15:53 pipps joined #salt
15:53 student__ thank you
15:54 eliasp student__: ok, I can confirm this even on 'develop', where "slot: 3" is simply ignored… let me see whether I can come up with a fix
15:54 kwmiebach joined #salt
15:55 ggoZ joined #salt
15:55 pipps_ joined #salt
15:56 troyready joined #salt
15:56 wendall911 joined #salt
15:56 student__ <eliasp>Thank you a lot
15:58 pipps joined #salt
16:00 sroegner_ joined #salt
16:02 jhulten joined #salt
16:03 toastedpenguin joined #salt
16:04 eliasp student__: might be a bit tricky, as the generic pkg handling doesn't know about a single package which could be installed multiple times… let's see if I can find a proper solution here
16:04 forrest joined #salt
16:06 schimmy joined #salt
16:07 stan_k joined #salt
16:07 ramishra_ joined #salt
16:10 KyleG joined #salt
16:10 KyleG joined #salt
16:10 sroegner_ joined #salt
16:12 sroegner joined #salt
16:13 iondrip joined #salt
16:13 student__ I think - write k
16:14 student__ write issue on github
16:15 eliasp student__: I'll open an issue in case I can't resolve it, otherwise there'll be a PR
16:15 eliasp student__: might have a solution now… need to do some tests
16:16 student__ how can I help You?
16:16 TheThing joined #salt
16:16 eliasp student__: not yet… will ping you once you can give it a try
16:18 Katafalkas joined #salt
16:18 n8n joined #salt
16:18 OS14261 joined #salt
16:19 krak3n` joined #salt
16:22 wnkz joined #salt
16:24 tligda joined #salt
16:28 aparsons joined #salt
16:29 aparsons joined #salt
16:30 jtrenholm joined #salt
16:31 jtrenholm hi, on http://docs.saltstack.com/en/latest/index.html, the link to the pdf is just a pdf with the salt logo :/
16:31 KennethWilke hey
16:31 KennethWilke minor details
16:32 KennethWilke within that logo contains all the stuff you need to know
16:33 jtrenholm haha. GOod to know
16:33 KennethWilke how's reddit :p
16:33 jtrenholm add box to another box and puppet is replaced. :p
16:34 jtrenholm good...
16:34 forrest jtrenholm, yeah it's been that way for a bit, whiteinge did you ever create time like a wizard to fix that pdf issue?
16:34 KennethWilke sites be changing going the salt route too
16:34 KennethWilke no more of that puppet business if it can be helped
16:34 jtrenholm Yea Fritts was jabbering on and on about that before he left austin. Very cool though.
16:35 KennethWilke it's certainly made life easier
16:36 wnkz joined #salt
16:36 timoguin jtrenholm: are you at reddit?
16:36 desposo joined #salt
16:37 jtrenholm i r
16:37 timoguin sweet, replacing puppet with salt?
16:38 eliasp jtrenholm: nice move! ;)
16:39 jtrenholm timoguin: I'm exploring some new software. I'm going to play around with it for some of my own stuff. eliasp Thanks!
16:40 eliasp oh, and for everyone who's not subscribed yet: http://www.reddit.com/r/saltstack/
16:40 timoguin would always love to see more activity there. :)
16:40 jtrenholm Yup! I've been subscribed for a while.
16:41 timoguin it's getting between 400 and 600 uniques per month
16:41 iggy subscribed... now let's just hope nobody in my nerd subs can see all the porn I look at on reddit
16:42 timoguin lrn2throwaway. ;-)
16:42 reikoshea joined #salt
16:42 eliasp ;)
16:42 iggy but I'm too lazy to remember more than one username:pass
16:42 eliasp iggy: I think you're on jtrenholm's watchlist now
16:42 jtrenholm timoguin: Nice, I've noticed most of the config management subs don't get much traffic.
16:42 reikoshea jtrenholm's a panzy
16:42 cpowell joined #salt
16:43 timoguin iggy: RES supports multi-user switching. :)
16:43 reikoshea he aint got nothing....nothing...but a dog...
16:43 eliasp timoguin: living without RES since ~2 weeks since it sucks a lot on FF ;(
16:43 jtrenholm i have bigger fish to fry than look at your subscribed subs...
16:43 eliasp jtrenholm: looking at /u/BarackObama's subs? ;)
16:43 babilen Could an op "+b *!~juuso@vonk.iki.fi$##fix_your_connection" ? The constant nick-cycling is starting to be quite annoying. (The GuestXXXX → help → GuestYYYY)
16:44 timoguin jtrenholm: nope, they don't. r/devops has a lot of subscriber, but the content seems to be pretty meh
16:44 KennethWilke you can't trust those devops people
16:44 reikoshea they're all a bunch of hacky hackers :P
16:44 Mso150 joined #salt
16:44 eliasp babilen: that's why I "hide" all joins/quits/parts in Quassel here
16:45 jtrenholm timoguin:  yea I'm not too impressed with that content, it's just links to devop theory and various circle jerks. Would rather read some good tech content with people solving real problems with real solutions.
16:45 rap424 joined #salt
16:45 iggy ^
16:46 KennethWilke those people are busy working
16:46 reikoshea should come to my team then jtrenholm...you could have been a great
16:46 reikoshea instead...you've wasted your potential
16:46 funzo_ joined #salt
16:46 eliasp reikoshea: another Reddit-employee?
16:46 babilen eliasp: I am an op in too many channels to do that globally, but could naturally make an exception for this channel. I just like to actually be aware of this normally, but that juuso person has been at it for days/weeks now.
16:46 reikoshea and given KennethWilke the opportunity to fill in the gap that you left
16:46 timoguin jtrenholm: yea, lots of "What is devops?" article churn
16:46 iggy I'm probably going to do a saltstack reddit post about our "backup" solution that I'm hacking together with mostly salt
16:46 eliasp babilen: well, you're right… hiding is not really solving here ;)
16:46 reikoshea my team funded reddit's engineering team...mwahahhaha
16:47 KennethWilke trained*
16:47 reikoshea what ev
16:47 astol joined #salt
16:47 babilen reikoshea: Would you like to fund me? I can't promise anything, but I'd be grateful and would name a deployment after you.
16:47 eliasp ;)
16:47 reikoshea trained = underpaid for multiple years for slave like labor hours
16:47 KennethWilke lol
16:48 KennethWilke it's called inspiration
16:48 KennethWilke lol
16:48 schimmy joined #salt
16:51 babilen Okay, I need some opinions. I'm currently investigating introducing new monitoring infrastructure and need, in particular, ways to classify/react to streams of events and *also* render those events so that we can be aware of problems/developments/... and can react/spot those more easily.
16:52 KennethWilke yeah i'd like to hear and answer to that too!
16:52 KennethWilke some guy was just telling me about this sensu thing, and i don't trust it
16:52 babilen I am looking at riemann, graphite and, naturally, the ELK (logstash, elasticsearch, kibana) stack to realise that, but need some opinions on the choice and also have the feeling that they aren't necessarily doing exactly the same thing.
16:52 schimmy joined #salt
16:52 timoguin babilen: i'm working on implementing a logstash / elasticsearch / kibana setup.
16:53 KennethWilke of them i've only dabbled with graphite
16:53 timoguin i'd also like to setup salt-eventsd for better forwarding and reacting for salt events
16:53 wnkz joined #salt
16:53 pipps joined #salt
16:53 babilen I quite like what I've seen of riemann so far and would like to trigger certain salt events from it and have the impression that it would be wonderful to *react* to events, whereas ELK is rather a visually pleasing solution.
16:54 babilen I know that, for example, The Guardian uses both tools/stacks and I just like to get an idea what the exact areas are in which I'd use them.
16:54 timoguin i've seen graphite implemented along with an ELK setup too, so metrics get shipped straight to that and the full logs still go to ELK
16:54 babilen (unfortunately I cannot get hold of my contacts at the guardian right now)
16:54 funzo_ joined #salt
16:55 reikoshea when it comes to monitoring ive never found a be-all-end-all solution for it. I've always had to cobble together different pieces of stuff i like in order to get a halfway functional dashboard that gives me the information i want. Then it comes down to BI data...that i just throw all the collectors i can at something and hope ill eventually want the data that ive collected so that my work wasnt all for nothing
16:55 timoguin logstash can react also to log patterns
16:55 babilen timoguin: Yeah, I've seen lots of cross-pollination and just try to get a better feeling for the areas in which these tools excel.
16:55 sroegner joined #salt
16:55 babilen (not to mention kafka, ...)
16:56 babilen As a person who is quite fond of Clojure I *do* like the idea of using riemann and it seems to be a powerful solution, but I also have the feeling as if I end up with an ELK setup in the next few weeks anyway (in particular if Kibana 4 hits stable).
16:57 iggy babilen: the author of riemann is very responsive and all around cool (fwiw)
16:57 babilen My most pressing problem is that I'd like to monitor CPU utilisation in a better way and 1. React to spikes/... by autoscaling (via salt) and 2. Visualize that in an accessible and beautiful way.
16:58 babilen iggy: Do you use riemann in production?
16:58 iggy fsvo production
16:58 iggy our product isn't actually live yet (Oct 23rd!)
16:59 babilen heh
16:59 floWenoL joined #salt
16:59 timoguin babilen: Using AWS?
16:59 spookah joined #salt
16:59 kusams joined #salt
16:59 babilen No, not AWS (something in-house)
17:00 timoguin grafana looks interesting too. http://grafana.org
17:01 timoguin looks like kibana for graphite
17:01 babilen I am aware of the EC2 autoscaler, but that was just an example. We use a variety of tools (nagios, munin, test scheduled with salt that feed some databases, salt-mine, ...) and I'd love to unify a little of that and riemann + graphite + ELK looked most useful.
17:01 iggy another thing I need to submit to salt-contrib probably... our riemann and graphite event signalers
17:01 babilen ooooh
17:01 eliasp oh all these things look so pretty… stop tempting me
17:01 babilen iggy: Please do *now* -- I was about to start writing those in the next 14 days, but would be happy if I don't have to do that.
17:01 babilen timoguin: Oh, that's lovely.
17:02 iggy maybe Wednesday, I'm looking pretty busy today/tomorrow
17:02 babilen yeah, no rush, but it will be nice to have
17:03 kermit joined #salt
17:03 timoguin iggy: yea i'd be interested in that too. i'm also evaluating monitoring solutions
17:03 babilen Reminds me that I wanted to open-source my easy-rsa based CA reactor system
17:03 aparsons joined #salt
17:05 babilen Okay, I guess I won't get around evaluating those approaches myself. Thanks for the input guys and poke me later (or let me know if you find nice things) -- I try to hunt down the Guardian people and ask them about their usage of ELK vs riemann/graphite
17:08 luminous joined #salt
17:08 iggy I wonder if I could convert my crazy white board picture to ascii art
17:09 iggy it's funny to look at
17:10 luminous babilen: fwiw, I believe logstash would give you the simplest/most direct access to doing stuff with streams
17:10 luminous babilen: you could rather easily write a filter, or an input/output handler to do some crazy stuff
17:11 luminous babilen: and what's this CA reactor system do?
17:13 babilen luminous: We use it to generate certificates for minions from central CAs. It is based on reactors so that a minion can sent a cert request to the master. The master then triggers the geenration of a new cert on the minion hosting the CA and the certificate is then delivered back to the minion via the master.
17:13 babilen I need to clean up a few shortcuts, but I really like it.
17:14 murrdoc joined #salt
17:15 aw110f joined #salt
17:15 babilen You do, however, have to define locations to which each CA will "deliver" its certificates (that is needed for the "write_cert" function in that module that will be triggered by the master to deliver the certificate)
17:18 luminous babilen: that sounds awesome!
17:18 jhulten joined #salt
17:18 luminous I would be interested in that, for sure
17:18 iggy I wouldn't say no to more real world examples of reactors
17:18 babilen We've been using that in production for a while so I am happy with the way it works. Please continue kicking me as I'd love to make it available, but ENOTIME
17:19 murrdoc oh man reactors
17:19 murrdoc so yummy
17:20 reikoshea left #salt
17:22 floWenoL_ joined #salt
17:25 bhosmer_ joined #salt
17:30 vlcn can anyone point me in the right dirrection for using something like the mount module to collect data which is used in a state?
17:30 Katafalkas joined #salt
17:31 vlcn for example, I want to use mount.active to grab information about a particular mount so that I can then add a new otpion using mount.mounted in a state
17:32 murrdoc salt.mine is supposed to be the goto way to get info from minions
17:32 murrdoc but that might not help here
17:32 murrdoc you want to do this all within one state ?
17:33 httpdss joined #salt
17:34 vlcn murrdoc, I suppose it doesn't have to be
17:34 vlcn essentially I'm juts trying to add the discard mount option to three mounts on about 400 VMs
17:37 aparsons joined #salt
17:37 chrisjones joined #salt
17:39 ramishra joined #salt
17:39 pltrent joined #salt
17:39 skyler joined #salt
17:41 jhulten joined #salt
17:44 httpdss joined #salt
17:44 e7_hb joined #salt
17:44 e7_hb hello all
17:45 Gareth morning morning
17:45 e7_hb i'm having some trouble getting the saltmaster to produce a terse output for users
17:45 mechanicalduck joined #salt
17:46 e7_hb the root (user running salt master) has correct output, but all the users have the verbose output
17:47 toastedpenguin joined #salt
17:47 e7_hb any insight would be much appreciated
17:48 ipmb joined #salt
17:50 badon joined #salt
17:51 druonysus joined #salt
17:51 druonysus joined #salt
17:51 jroof joined #salt
17:54 skyler I have been wondering how I should manage backups for a while. The current approach is to have a state that runs a shell script that uses rsync to backup the data, and then have a cron job that salt-calls that state. I am looking for a more elegant solution if anyone has one.
17:54 eliasp skyler: are you talking about "file" states or states in general?
17:55 skyler I have a .sls file that runs the script and the script dumps mysql data copies it over. There is also a script for taring a folder and copying it over.
17:56 skyler eliasp: Does that answer your question? I am not sure I follow you.
17:57 eliasp skyler: well, I was wondering whether you're just missing the "backup" option provided by many "file.*" states…
17:57 eliasp skyler: but it seems you're doing more complex stuff than simply file.recurse of file.managed
17:58 eliasp skyler: see also: http://docs.saltstack.com/en/latest/ref/states/backup_mode.html
17:58 thedodd joined #salt
17:59 pipps joined #salt
17:59 eliasp skyler: so regarding what you describe, I follow a completely different infrastructure philosophy and can't really give you a proper advice…
18:00 skyler eliasp: Yes, I am trying to put nightly backups on a backup server. Do you think you could give me a short overview of how you manage it? I am looking at ideas, because what I have right now sucks.
18:00 pipps_ joined #salt
18:03 Ryan_Lane joined #salt
18:04 obimod joined #salt
18:04 martoss joined #salt
18:05 dccc joined #salt
18:05 martoss1 joined #salt
18:06 aparsons_ joined #salt
18:07 aparson__ joined #salt
18:07 dude051 joined #salt
18:07 eliasp skyler: for me, there are only 2 entities in my infrastructure:
18:07 eliasp 1# "disposable runtime environments", which are hosts/containers/applications deployed by Salt…
18:07 eliasp 2# "data", such as SQL DB binary files/logs, user-data on network shares, code repositories (also containing all my Saltstack stuff)
18:07 eliasp stuff in the "disposable runtime environments" entity is basically worthless… no need to backup anything here, as it can be rebuilt anytime from Salt
18:07 eliasp only stuff from the "data entity" is worth being backed up… this is done externally via rsync and DB-specific backup solutions (which are also deployed as part of '1#')
18:08 higgs001 joined #salt
18:09 nitti_ joined #salt
18:10 eliasp skyler: for DB backups, you might want to have a look at http://www.hollandbackup.org/
18:13 vejdmn1 joined #salt
18:14 aparsons joined #salt
18:14 skyler eliasp: Thanks, that is helpful!
18:15 pipps joined #salt
18:19 kickerdog1 joined #salt
18:20 jjb joined #salt
18:20 schimmy joined #salt
18:20 rojem joined #salt
18:21 perfectsine joined #salt
18:21 kermit joined #salt
18:22 iggy I'll be detailing our setup on the saltstack subreddit in the coming weeks hopefully... keep your eyes peeled
18:22 scarcry joined #salt
18:23 n8n joined #salt
18:23 schimmy1 joined #salt
18:24 eliasp iggy: yeehaw! ;)
18:26 teepark in the file.managed state, if I use the 'makedirs' option will it set the ownership of the dir(s) to the user and group as well? or will they be root/root?
18:26 iggy our setup uses snapshots and cloud object storage to store the backups (hopefully with the object version being in a different cloud provider)
18:26 teepark there's dir_mode but no dir_user/dir_group
18:27 iggy teepark: I was just looking at that code the other day... and I don't remember
18:27 teepark guess I'm about to find out anyway, may have been a silly question :)
18:29 _mel_ joined #salt
18:29 pipps joined #salt
18:30 iggy it uses the user/group you specify (or defaults to user running salt command)
18:30 teepark yep, at least the user gets used on the dir
18:30 teepark beat me to it :)
18:31 capricorn_1 joined #salt
18:32 FreddyFlatFoot joined #salt
18:35 utahcon how could I grab an arbitrary list of files on a minion and symlink them... basically want to dynamically enable all vhosts on a minion
18:35 skyler iggy: What are you using for object storage?
18:37 skyler I have to keep everything local, so S3 is not really an option. I am looking at ceph, but I only have a single storage server atm, so I am not sure if it would be worth it.
18:37 eliasp utahcon: you mean like vhosts in /etc/apache2/hosts.available/?
18:37 smcquaid joined #salt
18:37 utahcon eliasp: more or less, yeah
18:37 eliasp utahcon: I'd probably write a custom grain which returns me the available hosts, then loop over them and Jinja a file.symlink for each of them
18:38 eliasp utahcon: a custom grain to return the available hosts should be roughly 3-5 lines ;)
18:38 eliasp import os, for node in os.listdir(/foo/bar): … etc
18:39 utahcon nice
18:39 utahcon good idea, I will head that direction
18:39 httpdss joined #salt
18:39 duncanmv joined #salt
18:40 eliasp utahcon: then on the other hand, I wonder why the available vhosts on a host aren't provided by your pillars already… where are they coming from?
18:40 iggy skyler: we are currently in gce... don't know about where we'd do "offsite" backups to yet (I probably won't have any say in the matter)
18:41 scbunn joined #salt
18:43 teepark I've never had this problem before, but I can't get pillar data to work. I think I've set everything up correctly: https://gist.githubusercontent.com/teepark/e0d7d61c86d1a7378df0/raw/600e9a3365094d50eb1b725dcb6ef559d13d8830/gistfile1.sh-session
18:43 eliasp teepark: pillars for masterless setups are broken in 2014.1.11
18:43 teepark oh, the missing piece there, file_client is set to "local" in /etc/salt/minion
18:43 teepark eliasp: oh
18:43 iggy eliasp beat me to it
18:43 eliasp teepark: downgrade to 2014.1.10 or wait for 2014.1.12
18:44 eliasp ;)
18:44 teepark eliasp: thanks. any workarounds?
18:44 teepark ok
18:44 teepark hmm, using the vagrant salt provisioner ATM. it seems pretty opaque
18:44 teepark any downgrading instructions around?
18:44 eliasp teepark: you could simply replace a single file fixing this
18:45 eliasp teepark: let me look for the PR fixing this
18:45 teepark eliasp: oh awesome I'll do that
18:45 vejdmn joined #salt
18:46 eliasp teepark: https://github.com/saltstack/salt/pull/16212
18:47 eliasp teepark: https://raw.githubusercontent.com/semarie/salt/edbe6f9d4f454442e09dbdc7bc406a0f2157c68e/salt/pillar/__init__.py
18:47 teepark these date-based releases, does that indicate that it won't get fixed until a december 1 release?
18:47 eliasp no… these are just increasing patchlevel numbers…
18:48 teepark ok
18:48 teepark oh right we're on 1.11
18:50 cberndt joined #salt
18:50 iggy it's year.month.point where year.month is when the release was branched (hence we _might_ get 2014.7.0 in 2014.10 or maybe 2014.11)
18:50 viii joined #salt
18:50 toastedpenguin joined #salt
18:52 cberndt joined #salt
18:52 toastedpenguin joined #salt
18:53 jpeach joined #salt
18:53 jpeach is it possible to reference a grain from another custom grain? if so, what's the right syntax for that?
18:54 viii hi, hope everyone is well! Wondering if anybody can shed some light on how sls files are processed in a directory; i've got a conf.sls which doesn't seem to be processed
18:54 Ryan_Lane jpeach: not really
18:54 Ryan_Lane they're all being loaded at the same time
18:54 teepark viii: you have to point to your sls in top.sls
18:54 viii this is based on the best practices conf.sls in the docs
18:54 teepark viii: or include your conf.sls in something else which is pointed at by top.sls
18:55 jpeach hmm, my use case is to publish a grain that is derived from the installed memory size, so I wanted to avoid rewriting the "mem_total" grain
18:59 kickerdog1 left #salt
19:00 viii teepark: thanks, going to try right now
19:01 teepark viii: good luck. more details: http://docs.saltstack.com/en/latest/ref/states/top.html
19:02 mechanicalduck joined #salt
19:05 Mso150_1 joined #salt
19:05 scbunn joined #salt
19:08 kusams joined #salt
19:08 viii teepark: thanks! one step closer, i thought it was odd that the conf.sls wasn't references so now it renders it... anyway to troubleshoot a jinja template, i've got salt-call -l all but it doesn't seem to show jinja processing, my source: isn't pulled from the pillars
19:09 teepark viii: you didn't by any chance recently install salt and are trying to run your states without a master?
19:15 viii teepark: it is running on a master, i am using salt-call from the minion but this is on a windows minion
19:16 teepark you also need a top.sls in your pillar_root
19:16 teepark is that maybe missing?
19:16 murrdoc unrelated but salt totally needs something liek http://kitchen.ci/
19:18 viii teepark: that was just, was just reading the storing static data in the pillars doc and copied the top.sls from /srv/salt and modified it and boom, rendered!  i was banging my head against the table for a day already!
19:18 httpdss joined #salt
19:18 pipps joined #salt
19:19 viii teepark: so basically saltstack doesn't automagically import sls files from the roots, if it isn't references it doesn't get loaded
19:19 teepark viii: exactly. this also frees you up to have lots of states in there not *turned on*
19:20 teepark viii: or selectively turned on, but the host or whatever other matcher you want to use. read that whole documentation page on top files
19:20 teepark *based on
19:21 viii teepark: will do re: top; i usually read based on the issue i run into but it seems like top.sls ought to be my first trip to the doc
19:27 viii teepark: thanks again, greatly appreciate your help - you saved me countless hours, just ran the highstate and my test for nxlog with the conf file deployment worked like a charm - template rendered beautifully based on cpuarch. just what i needed, now i can go and read up on top.sls and also further refine the config
19:27 vlcn odd.  mount.mounted seems to be generating invalid commands
19:27 vlcn eaxmple: mount -o remount,defaults,discard -t ext4 /dev/sdb1 configure /vz
19:27 vlcn I have no idea where configure is coming from
19:27 teepark viii: no problem
19:29 vejdmn joined #salt
19:30 trevorj Hi everyone
19:30 trevorj Salt-cloud is broken for me with 2014.1 git
19:30 aw110f joined #salt
19:30 trevorj I cannot provision VMs, it fails @ sftp'ing minion.pem
19:31 trevorj The funny part is, it uploads just fine, it's just detecting an error where there isn't one.
19:33 iggy trevorj: did you check issues? This sounds vaguely familiar
19:33 rlarkin|2 is 2014.1.12 actually released?
19:33 iggy not yet
19:34 trevorj iggy: I'm currently searching issues, didn't find anything yet
19:34 eliasp murrdoc: https://github.com/simonmcc/kitchen-salt
19:34 vlcn hey trevorj :)
19:35 trevorj iggy: I updated to fix a bug with salt-cloud, which led me to this other issue. Lol.
19:35 iggy yeah, we ended up dumping salt-cloud for now because it was unsowrkable for us
19:35 trevorj Hey vlcn!
19:35 MTecknology Can I match pillar data in top.sls?
19:36 * dstufft is idling considering packaging up 2014.7rc3 and deploying it into prod
19:36 thedodd joined #salt
19:36 MTecknology dstufft: I got bit in the bum for that.
19:36 rypeck Anyone know why SaltStack doesn't use the milestones feature on GitHub anymore?
19:36 dstufft MTecknology: what happened? :| I keep finding new features I want to use
19:37 MTecknology yay, I can match on pillar
19:37 MTecknology dstufft: mostly just compatibility from using current distros
19:38 dstufft MTecknology: I'm not sure I can parse that sentence... compatability how?
19:38 MTecknology package versions
19:38 aparsons joined #salt
19:38 MTecknology go for it, but do it in dev first
19:38 * MTecknology wanders off for a walk
19:39 vlcn https://gist.github.com/kelchm/b533ba46caf3fc3c7bf5
19:39 trevorj vlcn: Long time no talk
19:39 vlcn trevorj: indeed, it has been a long time
19:40 cpowell holas everyone
19:40 schristensen joined #salt
19:41 bhosmer_ joined #salt
19:50 to_json joined #salt
19:51 elfixit joined #salt
19:53 ggoZ joined #salt
19:56 scbunn joined #salt
19:57 toastedpenguin joined #salt
19:57 phblj_ joined #salt
19:57 ericof joined #salt
19:58 phblj_ hey all, still new to salt and I've come upon a logical problem in configuring minions.  I've got an execution module I use in top.sls to assign SLS to systems.  When a new minion comes up, it needs the module, so I "salt new_minion saltutil.sync_modules".  This gives me a jinja error in top.sls when it tries to resolve the missing module.  Should I just code around the missing module in the template?
19:58 phblj_ does it make sense that sync_modules is trying to parse top.sls?
20:00 FreddyFlatFoot left #salt
20:00 Cidan joined #salt
20:01 phblj_ looks like that worked.  Just want to make sure I'm not doing something awkwardly wrong
20:01 vejdmn joined #salt
20:03 schimmy joined #salt
20:04 glyf_ joined #salt
20:04 beneggett joined #salt
20:05 Heartsbane to many Trevor's on the dancefloor
20:07 phblj_ ok, so now I have a strange setup that I'm sure i'm doing wrong.  Said execution module relies on a python package to run.  So it takes two state.highstates to set up my minion-- the first installs the requirement (matching a 'common' SLS) then on the second the module actually runs correctly and matches the minion to a specific SLS.
20:07 phblj_ any way to do them both in the same update, without pre-installing the python package on machines?
20:07 glyf joined #salt
20:12 tpaul joined #salt
20:14 tpaul Is it possible to match minions that are using a particular state? I updated a certificate and want to make sure that all servers using that state have been updated, but I don't necessarily want to run highstate on all my minions...
20:15 eightyeight salt stack mentioned: https://www.youtube.com/watch?v=mXdFHNJ6srY
20:15 nledez joined #salt
20:16 eightyeight not a good discussion either
20:18 honestly phblj_: add the package install as a requirement to the state that uses the package
20:18 phblj_ no state uses that package, though-- it's an execution module
20:19 trevorj Heartsbane: lol
20:19 ramishra joined #salt
20:19 phblj_ used in top.sls
20:19 tpaul eightyeight: where abouts what salt mentioned?
20:19 trevorj Ok guys, in cloud.py, line 1079
20:19 tpaul where abouts was*
20:19 eightyeight tpaul: first couple minutes
20:19 tpaul thanks
20:19 trevorj Is it just me, or is it impossible to not error out
20:19 eightyeight using salt as an example how _not_ to do rsa
20:20 tpaul ouch... interested to see what they say
20:20 tpaul didn't they fix that issue a LONG time ago though?
20:21 bhosmer_ joined #salt
20:21 ndrei joined #salt
20:21 viq tpaul: yeah. People still make fun of debian though, so... ;)
20:24 Ozack1 joined #salt
20:25 pipps joined #salt
20:26 perfectsine joined #salt
20:27 linjan joined #salt
20:27 nledez joined #salt
20:29 vejdmn1 joined #salt
20:32 druonysuse joined #salt
20:33 beneggett joined #salt
20:35 kermit joined #salt
20:36 eightyeight https://github.com/saltstack/salt/commit/5dd304276ba5745ec21fc1e6686a0b28da29e6fc
20:36 eightyeight ^ the commit it's referencing
20:36 jmdcal joined #salt
20:37 druonysus joined #salt
20:37 druonysus joined #salt
20:39 dstufft Question, do entries in the salt mine expire? Or how long are they valid for.
20:41 utahcon can you add a watch for a service on a directory?
20:42 utahcon or just files?
20:42 babilen utahcon: You can add a watch on any state
20:42 spookah eightyeight: that is quite the discussion
20:42 babilen (if that state has changes it will trigger the requisite - as directories will seldom have changes this is not what you want)
20:44 murrdoc joined #salt
20:44 babilen utahcon: But the question here really is: What kind of changes do you want to trigger on?
20:44 bhosmer_ joined #salt
20:46 utahcon babilen: really I only need to do it once, after I have symlinked all the vhosts for a server (they are created dynamically on the hosts)
20:47 utahcon but service.running doesn't restart, unless there is a watch set... if I am reading things properly
20:47 utahcon so basically I have written a horrible state that does ls on a dir, and then creates symlinks, and then I need it to restart apache... which I figure worse case scenario I can do by cmd.run
20:48 utahcon state that makes symlinks http://pastie.org/9645441
20:48 utahcon but was hoping for something a little more... flexible
20:54 robawt is it possible to "listen" on the bus for a new key being accepted?
20:54 robawt i'd like to react to it if possible
20:57 nitti joined #salt
20:57 glyf joined #salt
20:58 Guest63401 left #salt
20:58 TheThing joined #salt
20:59 timoguin robawt: yea there's an event tag for keys being accepted.
20:59 timoguin can't remember what it is off the top of my head
21:00 robawt ok but i'd want to lookup "event tag" timoguin ?
21:02 timoguin robawt: try the eventlisten.py script in the salt source, under tests/eventlisten.py
21:02 pipps_ joined #salt
21:02 timoguin accept a key and see what pops up
21:03 SheetiS http://docs.saltstack.com/en/latest/topics/reactor/ has an example that runs when a key is accepted {% if data['act'] == 'accept' ...
21:04 rubenb joined #salt
21:04 SheetiS on an event of 'salt/key'
21:08 ndrei joined #salt
21:08 nledez hi all. I search a way to "manage many hosts".
21:09 StDiluted you have found a good place for that.
21:09 nledez When a highstate fail on some node, I would like to have a report
21:09 murrdoc failHard !
21:09 nledez @StDiluted I allready use salt :)
21:10 aw110f joined #salt
21:10 StDiluted @niedez: it’s all good, I’m just joking.
21:11 kballou joined #salt
21:11 n8n joined #salt
21:11 nledez A solution can be a dashbord, I try to deploy halite.
21:12 nledez But I'm not sure it can be a real solution in my case
21:12 iggy you could use json or yaml output and stuff that into some other tool
21:12 nledez I have ~400 hosts
21:13 baconbeckons joined #salt
21:14 nledez @iggy fine I think about that in the past bu never try it. Thanks to reminder :)
21:14 iggy I have yet to find anything that makes for pretty output of that many hosts
21:15 iggy I usually use --batch to limit the size
21:15 murrdoc well
21:15 murrdoc you could foreman it up
21:15 baconbeckons i have a package that i have to download to install. right now, i download it on each minion, but i want to make the saltmaster download it (as opposed to putting it into the repo that stores my salt states) and serve it via salt://. is there a place that is usually used for downloaded files like this?
21:15 m1crofarmer joined #salt
21:15 murrdoc its a little bit of work
21:15 nledez One thing what I like to have is when I launch a "salt '*' run.cmd node --version"
21:16 murrdoc you could use the json output and jq
21:16 murrdoc nledez:  ^
21:16 baconbeckons hey iggy! you helped me a lot getting saltstack up and running over the past couple of weeks and i wanted to thank you again! thanks to everyone else that helped out too of course :)
21:16 murrdoc oh i see how it is
21:16 murrdoc iggy gets all the love
21:16 nledez A big job is launch. But I would like to have a way to export this big job such as jobs.lookup_jid
21:16 iggy another option that I've toyed with a bit is writing a logstash outputter that would dump all that to my ES cluster
21:16 pravka joined #salt
21:17 nledez But jobs.lookup_jid is for one host
21:17 baconbeckons murrdoc gets love too!
21:17 iggy suck it murrdoc! ;)
21:17 murrdoc chyeah
21:17 murrdoc i got left over love
21:17 murrdoc what!
21:17 murrdoc anyhow iggy why you no http://docs.saltstack.com/en/latest/ref/returners/all/salt.returners.elasticsearch_return.html
21:17 baconbeckons many people helped me, but iggy was here day after day answering stupid questions
21:17 murrdoc i am totally kidding baconbeckons
21:18 iggy there are a lot of people more helpful than I am... I just have a short memorable name
21:18 baconbeckons i don’t think that iggy was kidding when he told you to suck it :-p
21:18 murrdoc i think he was
21:18 baconbeckons that might be it iggy
21:18 baconbeckons murrdoc: no, he wasn’t. he hates you /s
21:19 eliasp student__: https://github.com/saltstack/salt/issues/16600
21:19 murrdoc iggy best have those pull requests out this year
21:19 iggy murrdoc: yeah... I didn't know you could do returners with highstate and orchestrate
21:19 iggy I got one done the other day!
21:19 iggy that's like .1% of my full list
21:20 timoguin nledez: iggy: there is an elasticsearch returner as well
21:20 murrdoc nledez:  try out  http://docs.saltstack.com/en/latest/ref/returners/all/index.html
21:20 murrdoc the local one works best with bash
21:20 timoguin oh hey murrdoc, there's an elasticsearch returner as well
21:20 murrdoc yup
21:20 timoguin what is scrollback?
21:20 murrdoc its the past
21:21 murrdoc forget that noise
21:21 trevorj iggy: https://github.com/saltstack/salt/pull/16599 fixed with this PR
21:21 Victor joined #salt
21:21 Victor hi
21:21 iggy I could swear there was some reason I didn't think returners would work for me
21:22 murrdoc skills ?
21:22 timoguin the gauntlet has been thrown
21:22 murrdoc :D
21:22 iggy touche :(
21:22 murrdoc i keed ma
21:22 murrdoc man*
21:22 murrdoc my fav is the smtp_returner btw
21:22 murrdoc i cant wait to put that in somewhere
21:23 Victor I'm starting to play with salt and I'm having some problems with pillars. Seems that when I run salt-call --local pillar.items I can't get any of the newly added pillars, but when I execute it with -l debug I don't see any errors and the actual debug messages shows OrderedDict([('info', 'some data')])
21:23 Victor any ideas?
21:23 iggy yeah, right after I aim it at somebody else's mailbox
21:23 Victor i'm running in masterless mode (in case it matters)
21:23 iggy Victor: 2014.1.11
21:23 iggy ?
21:23 iggy let's just assume yes... downgrade
21:24 murrdoc or
21:24 Victor iggy: yep, 2014.1.11, freebsd's version
21:24 murrdoc salt —local '*' saltutil.refresh_pillar
21:24 Ahlee iggy: returners firing from the minions bothers me, and i sometimes wish returners brokered back to the master for storage
21:24 Victor murrdoc: tried with salt-call --local salutil.refresh_pillar, but same result
21:24 murrdoc nothing in the logs ?
21:24 timoguin Ahlee: yea every minion returner can be shitty. that's why i'm interested in salt-eventsd
21:24 timoguin so everything will aggregate on the master and return
21:24 Ahlee timoguin: news to me
21:25 Victor iggy: i guess there is a known issue with this version, is there any bug to track it and get more context?
21:25 Victor murrdoc: no error, just what I pasted in debug, which looks weird
21:25 timoguin Ahlee: I mean every minion returnING can be annoying
21:25 Ahlee ah.  heh.
21:25 Ahlee My issue is with them not returning ;)
21:25 murrdoc also iggy you could just use logstash forwarder
21:26 murrdoc and take the salt logs and make them json
21:26 eliasp Victor:  https://github.com/saltstack/salt/pull/16212
21:26 eliasp Victor: https://raw.githubusercontent.com/semarie/salt/edbe6f9d4f454442e09dbdc7bc406a0f2157c68e/salt/pillar/__init__.py
21:26 murrdoc keep returners out if
21:26 gothix_ joined #salt
21:26 Victor thx a lot eliasp && iggy && murrdoc
21:27 timoguin I wrote a really basic Slack returner, and every minion will post back to the Slack channel, but a single aggregate would be better
21:27 timoguin working on that
21:28 baconbeckons timoguin: i would be interested in seeing your slack returner
21:28 Ahlee slack? something akin to thrift?
21:28 iggy yeah, doesn't look like returners work with salt-run which is why I decided against that route
21:28 baconbeckons ahale: slack is a group messaging service
21:29 iggy but now that I'm looking at the docs, I don't see --out for salt-run either
21:29 Ahlee I'm officially to the point in my career I can no longer keep all this straight.
21:29 Ahlee Time to move to management
21:29 iggy ^
21:29 murrdoc i want to downgrade
21:29 pipps joined #salt
21:29 murrdoc digital janitor is over rated
21:29 murrdoc i am thinking real janitor
21:29 Ahlee indeed.
21:30 skyler I am getting 'State 'debconf.set' found in SLS 'ldap.server' is unavailable' when I try to run a state on an ubuntu vm. I am confused. It works on what I am pretty sure is the exact same issue in another place.
21:30 Victor nice, according to https://github.com/saltstack/salt/issues/16428 seems that in one or two weeks a new release will fix the issue
21:30 ndrei joined #salt
21:30 murrdoc Victor:  are u starting a new implementaiton of salt
21:30 murrdoc or are u already deployed
21:30 timoguin baconbeckons: cool. i have an execution module as well as a returner. i'll contribute them before too long
21:30 murrdoc if its the latter i d say work with rc3
21:30 iggy I used to tell women I met at bars that I was a custodial engineer at a higher learning institution
21:30 murrdoc its got tooo much good stuff
21:30 iggy sadly, most of them were impressed
21:30 Ahlee skyler: Do you have the debconf-utils package?
21:31 murrdoc iggy:  smooth
21:31 Victor murrdoc: I'm playing with it ATM. I've used in the past cfengine and tried different things so I thought it might be fun to try it and see it's good, bad and ugly sides
21:31 baconbeckons timoguin: are they on github now so that i can start playing with them?
21:31 Victor :)
21:31 skyler Ahlee: That may very well be it!
21:31 Ahlee skyler: http://docs.saltstack.com/en/latest/ref/states/all/salt.states.debconfmod.html
21:31 Ahlee If salt can't find a required package for a state it disables the state
21:31 murrdoc Victor:  then for sure use the salt-bootstrap and use the rc4
21:31 murrdoc or rc3
21:31 Victor will salt-bootstrap work well on FreeBSD?
21:31 timoguin baconbeckons: not yet. i can probably throw up a gist soon, but it'll probably be a few weeks before i get them contributed properly
21:32 murrdoc only one way to find out
21:32 Victor :)
21:32 murrdoc https://github.com/saltstack/salt-bootstrap/blob/develop/bootstrap-salt.sh read code
21:32 murrdoc also deploy in prod
21:32 murrdoc :D
21:32 Victor I think I'm going to look into merging the change manually in my local install just for fun
21:33 Ahlee slippery slope.
21:33 nledez Thanks iggy: timoguin: murrdoc: I try json output and it can be a goot start :)
21:34 murrdoc no need to thank me
21:34 murrdoc but yay :)
21:34 murrdoc do the ryan and write a blog post
21:34 iggy my cat has been laying on my keyboard for the last 2 hours... what happened?
21:34 murrdoc so other people can find the solution when they goog
21:35 higgs001 joined #salt
21:35 murrdoc u shipped stuff
21:35 skyler Ahlee: Thanks! That appears to have been the issue. I guess the image I am working off of is not the image I thought it was...
21:35 peters-tx joined #salt
21:35 Ahlee skyler: awesome!
21:36 Victor eliasp: overwriting the __init__.py with your referenced file fixes the issue, thanks a lot!
21:36 skyler I just asked the guy who loaded this image into our cloud where he got the image from. Turns out I gave it to him...
21:37 dstokes i'm getting an error on file.directory not being able to recursively set mode, but increasing output verbosity doesn't give me any additional info about the error. has anyone run into this?
21:38 iggy dstokes: apparmor/selinux?
21:39 dstokes iggy: nope
21:40 dstokes at least not anything that would affect this dir
21:41 jhujhiti joined #salt
21:41 iggy famous last words...
21:43 dccc joined #salt
21:46 skullone anyone making use of reclass over standard pillars, with lots of nodes?
21:47 aw110f Does globbing or regex work when targetting grains?
21:48 murrdoc skullone:  no, but i d like to hear what you are running into
21:48 murrdoc i am testing it out for 10
21:48 babilen aw110f: yes
21:48 babilen aw110f: http://docs.saltstack.com/en/latest/topics/targeting/compound.html
21:48 timoguin baconbeckons: here you go: https://gist.github.com/timoguin/8cc68cac25848c95ac61
21:48 timoguin still very basic, but that's what i'm currently working with
21:49 baconbeckons timoguin: cool! thanks for posting it!
21:49 baconbeckons are you going to put it in a github repo?
21:49 aw110f babilen: globbing and regex seems to work around minionid only but doesn't seem to work around grains
21:49 iggy all the cool kids are
21:50 babilen aw110f: You can glob and use PCRE on grains too (G@ and P@ respectively)
21:50 timoguin baconbeckons: i'll contribute it to salt or salt-contrib once it's ready. it's in a private repo for now
21:50 baconbeckons timoguin: can you throw a license on it so that we can use it? :)
21:50 skullone murrdoc: ive got about 50 so far, no problems yet, but just wondering how people are going about it
21:51 murrdoc ah
21:51 aw110f http://pastebin.com/CVWiyKrA
21:52 aw110f babilen: http://pastebin.com/CVWiyKrA
21:52 babilen aw110f: That's the most horrible pastebin of them all
21:54 aw110f Sorry but how so? it clearly shows that either globbing or PCRE isn't working
21:54 babilen aw110f: [qa,dev] is not a glob expression that would match qa or dev
21:54 babilen And you want P@ for PCRE on grains (as mentioned earlier)
21:55 JonGretar_ joined #salt
21:55 eliasp and even for PCRE [qa,dev] would be wrong… you probably mean (qa|dev)
21:55 babilen In globs [..] defines character ranges (e.g. [0-9] matched 0,2,3,4,5,6,7,8 and 9)
21:56 eliasp aw110f: if you're unsure whether your regex is correct… all you need is: http://regex101.com/
21:56 babilen eliasp: There is "salt -C 'G@NODEGROUPS:ypca-web_(dev|qa)' test.ping" in there which should have been "salt -C 'P@NODEGROUPS:ypca-web_(dev|qa)' test.ping"
21:56 timoguin baconbeckons: just stuck apache 2 in the comments.
21:57 aw110f yea P@NODEGROUPS:ypca-web_(dev|qa) worked thanks, i thought PCRE only worked around minionid
21:57 baconbeckons thank you timoguin :)
21:58 babilen No, that is why I linked the documentation on compound matchers earlier and mentioned G@ and P@ ... Glad that I could help. Does that do what you want?
21:58 aw110f thanks babilen:
21:58 aw110f yep it does
21:58 mihait joined #salt
21:58 babilen Wonderful! http://xkcd.com/208/
21:59 akitada__ joined #salt
21:59 Ahlee is it possible to specify a timeout within a state?  I.e. if i know it's going to take 300+ seconds to run git.latest, can i add timeout: under?
21:59 MrThrax joined #salt
21:59 eliasp babilen: yeah… one of the absolute XKCD classics + one of my favourites ;)
22:00 babilen Indeed, couldn't resist
22:00 eliasp babilen: I used to write a looot of regex as Perl dev ;)
22:03 httpdss joined #salt
22:04 schimmy joined #salt
22:04 babilen timoguin: Okay, I read a bit more and decided to give two setups a spin. For the first I'll try riemann, influxdb (graphite maybe) and grafana for tracking of values that you would track in grains in salt and other metrics. The second is the ELK stack for logs. I don't think that I want to track, say, time series of CPU utilisation or bandwith measurements with ELK nor do I want to track logs (and aggregated metrics on top of that) with ...
22:04 babilen ... graphite/influxdb/grafana/riemann
22:04 eliasp babilen: please please please blog about the outcome of all this! ;)
22:05 timoguin yes, for we all share the journey!
22:06 timoguin onward and outward?
22:06 borgstrom joined #salt
22:06 iggy babilen: don't forget statsd, logstash, logster, etc...
22:06 timoguin logstash is the L in ELK. ;-)
22:07 mosen joined #salt
22:07 iggy and bucky, rocksteady, esper, beaver, flume, fluentd-logging, cabot, etc...
22:07 iggy I've got a very convoluted drawing with all these names on it
22:10 ajolo_ joined #salt
22:10 Ahlee is key for meetings with C levels
22:12 ipmanx joined #salt
22:12 babilen iggy: yeah, statsd has a place in there. I guess i have to add logster too.
22:12 pipps joined #salt
22:12 iggy I think logstash can actually do quite a bit of what logster does
22:12 ipmanx hi - any tips on how to approve a minion salt-key automatically when setting up to test VMs (e.g. using vagrant) ?
22:12 Ahlee my memory vaguely recalls a performance problem with file.directory, recurse: and speed, anybody else recall this and/or have direct experience with it?
22:13 Ahlee iggy: It can.
22:13 iggy Ahlee: directory -> recurse is fine here with a 600M tree
22:13 iggy but it's more big files than a ton of files
22:14 Ahlee yeah this is a ~400M git clone with a couple million files
22:14 httpdss joined #salt
22:14 Ahlee somebody on team likes to git clone as root
22:15 Ahlee er, git pull
22:15 jmdcal joined #salt
22:15 Ahlee *shrug* cmd.run here we come
22:16 timoguin ipmanx: I use auto-accept with vagrant. You can also pre-seed them with generated keys
22:17 ipmanx timoguin: thanks, good idea :)
22:17 Ahlee I couldn't imagine running salt not in open mode
22:17 timoguin I only use open mode for disposable vagrant environments.
22:17 saltnoob joined #salt
22:17 timoguin Otherwise salt-cloud handles seeding
22:19 saltnoob any idea when 2014.7 stable will be ready?
22:20 murrdoc sooon
22:20 iggy 2 weeks
22:20 iggy ... is what I've been hearing for the last 4 weeks
22:20 saltnoob lol
22:21 saltnoob looking forward to the gpg feature
22:22 murrdoc its easy to add
22:22 murrdoc to your existing deploy
22:22 murrdoc look at salt-contrib repo for examples
22:22 kermit joined #salt
22:22 saltnoob cool, thx murrdoc
22:22 murrdoc nooo problem
22:23 murrdoc imma get more thanks then iggy today
22:23 murrdoc muhahahahaha
22:23 murrdoc thats just sad
22:23 n8n joined #salt
22:23 vxitch joined #salt
22:24 iggy damn, better stop wa^Wslacking off
22:24 saltnoob I don't see it anywhere @ https://github.com/saltstack/salt-contrib
22:24 murrdoc hah
22:24 vxitch i have to run a state/highstate multiple times until the job will return output either right away or when i query it using salt-run jobs.lookup_jid
22:24 vxitch any ideas why?
22:24 vxitch the job also doesnt appear in jobs.active
22:25 iggy vxitch: I've never been bothered enough to track it down, but we see the same thing here
22:25 vxitch iggy: alright. sucks because usually i just rerun the state, though now my state is refusing to run at all
22:26 vxitch and as always, master is silent about the whole ordeal
22:26 iggy -l debug?
22:26 vxitch yeah, doing that now
22:26 murrdoc saltnoob:  add https://github.com/saltstack/salt/blob/develop/salt/renderers/gpg.py to the renderers dir
22:26 murrdoc as shown in the contrib repo
22:26 Ahlee vxitch: might be worth connecting to the event bus and watching it
22:27 Ahlee vxitch: any returner specified taht might be slow?
22:27 vxitch how would i do that?
22:27 vxitch Ahlee: no returner
22:28 seanz joined #salt
22:28 seanz Greetings. Is it possible to pass in a custom function into jinja?
22:28 seanz A template helper or the like/
22:28 seanz ?
22:29 saltnoob thx murrdoc, to clarify, add salt-contrib and add gpg.py to the renderers folder (from salt-contrib)?
22:30 murrdoc nope
22:30 murrdoc make the renderers folder and add gpg.py to it
22:31 kusams joined #salt
22:31 saltnoob I did that a few days ago and whilst I was able to decrypt data in pillar, I couldn't run state.highstate, any step I'm missing?
22:32 saltnoob (also amended renderers line in master to add | gpg
22:32 saltnoob )
22:33 saltnoob it would complain about the rendering line
22:34 vxitch salt-master is waiting to return execution from salt '...' state.highstate, minion is currently stuck with this being the last line of output [DEBUG   ] Fetching file from saltenv 'base', ** attempting ** 'salt://auth/keys/vxitch.id_rsa.pub'
22:34 vxitch any idea why it would be stuck there? or where to look next?
22:34 saltnoob but if I copy the gpg file to the /var/cache/salt.... renderers (of the top of my head) I can decrypt but not run highstate
22:40 bashcoder joined #salt
22:41 vxitch yup, salt-minion says it is returning info for job, but nothing gets displayed when i do a lookup_jid on the master
22:42 ndrei joined #salt
22:43 pipps joined #salt
22:44 saltnoob after creating renderers/gpg.py in file root and adding renderer: jinja | yaml | gpg to master config:
22:44 saltnoob [CRITICAL] The renderer jinja | yaml | gpg is unavailable, this error is often because the needed software is unavailable
22:45 iggy not _renderers?
22:45 iggy modules/grains/etc all have an _
22:48 pipps_ joined #salt
22:48 vxitch holy shit why the fuck won't salt run
22:49 n8n joined #salt
22:50 Outlander joined #salt
22:54 Corey vxitch: What're you seeing?
22:55 cads joined #salt
22:56 vxitch Corey: one of my hosts is not running salt states. i can target it directly via hostname and after a while the salt command on the master returns with no output, no jobs in jobs.active, and if i do a lookup_jid on the jid from list_jobs i get nothing as well, not even the hostname and --- line separator
22:56 vxitch if i target a grain it has, other hosts with that grain get the module/state i'm running and i can see the output by doing a lookup_jid, but this host isn't in there once again
22:57 Corey vxitch: From the node itself, can you salt-call state.highstate?
22:57 vxitch test.ping works just fine for the host, though. the salt-key is valid. nothing in the logs.
22:57 vxitch Corey: let me give that a shot
22:57 Corey vxitch: Also, what makes this node unique?
22:58 vxitch Corey: nothing, it's built by cobbler and salt like my other nodes. it has a small handful of specific states, but they build on top of other states that exist on other nodes (things like dropping a specific /etc/exports in place for nfs, for example)
22:58 vxitch that's what's so confusing about it all
22:58 pravka joined #salt
22:58 nitti joined #salt
22:58 vxitch Usage: salt-call [options]
22:58 vxitch salt-call: error: --checksum-fill option requires an argument
22:58 vxitch those are the last two lines after calling salt-call from the minion
22:59 vxitch right after it tries to do some iptables things (doesn't look like my iptables states)
23:01 vxitch other than jinja2, minion's --versions match the master
23:03 n8n joined #salt
23:05 seanz joined #salt
23:07 jnials joined #salt
23:08 DaveQB joined #salt
23:09 aparsons joined #salt
23:11 blackjid joined #salt
23:14 jnials joined #salt
23:14 bhosmer joined #salt
23:14 iggy show_top show_low_sls show_lowstate pillar.items grains.items
23:16 techdragon joined #salt
23:21 Air joined #salt
23:22 vxitch iggy: those all return almost instantly
23:24 higgs001 joined #salt
23:25 iggy and don't show anything?
23:25 iggy vxitch: if not, you need to start stripping out state files until it unbreaks
23:26 vxitch iggy: no errors, no
23:26 vxitch i'm suspecting this
23:26 vxitch salt-call: error: --checksum-fill option requires an argument
23:27 vxitch which i see if i debug the minion or salt-call from the minion
23:28 spookah joined #salt
23:28 iggy I don't even see that option anywhere
23:29 iggy do you have the iptables module enabled for anything?
23:29 iggy if so, disable it or the state that is using it
23:30 vxitch i dont have it disabled, though let me check again. i push out a minion config to disable a bunch of modules i dont use in my env, iptables is used all around though
23:33 iggy that's what's causing your problems
23:34 iggy so... it's not "salt" failing, it's something with your iptables setup/binary/etc.
23:35 KyleG joined #salt
23:35 KyleG joined #salt
23:36 vxitch checking /etc/salt/minion on the minion, my own minion config hasnt been applied yet, its still the default (which still works in my env)
23:36 vxitch no modules are disabled
23:38 iggy quick test, rename the iptables binary and see what happens
23:38 vxitch ok
23:40 murrdoc joined #salt
23:40 pipps joined #salt
23:40 vxitch state runs, all the iptables and dependent states fail as eexpected, but the state runs and returns
23:40 vxitch so iptables is the issue here?
23:44 iggy nah, I think it's salt
23:44 iggy 19:34 < iggy> so... it's not "salt" failing, it's something with your iptables setup/binary/etc.
23:44 MatthewsFace joined #salt
23:44 aquinas joined #salt
23:44 vxitch sarcasm? :)
23:44 pipps_ joined #salt
23:45 iggy it's my favorite form of public criticism
23:45 vxitch haha, i'll take it
23:46 vxitch well, no idea how iptables is doing this, since it's from a vanialla rhel6.5 install, but i will poke at it until it gives me answers
23:46 vxitch thanks for your help
23:46 murrdoc iptables -F
23:46 murrdoc for the win
23:46 murrdoc yes i am late to the party
23:47 MatthewsFace joined #salt
23:48 manfred iptables -F; iptables -P INPUT ACCEPT; iptables -P FORWARD ACCEPT; iptables -P OUTPUT ACCEPT
23:48 manfred just to make sure
23:48 vxitch yup, i have default accept policies and no rules, salt is supposed to populate
23:48 vxitch that was the first thing i checked :)
23:49 vxitch looks like iptables and i are going to have a little talk
23:49 manfred vxitch:  don't use the iptables module with salt if you are using rhel 6.5, just fyi, it doesn't work
23:49 manfred because we are regex matching against iptables-save and that is not reliable
23:49 vxitch manfred: ah.
23:49 vxitch alternatives?
23:49 manfred vxitch:  https://github.com/saltstack/salt/issues/12455
23:49 murrdoc oh u are on rhel 6 ?
23:49 manfred vxitch:  do a file.managed on /etc/sysconfig/iptables, and then a watch on that file.managed that restarts iptables if the configuration changes
23:50 manfred rhel 6 does not have iptables —check, so there is no internal checking for if a rule exists in a chain or not
23:50 murrdoc yeah i think rhel is recommending something else instead of iptables
23:50 manfred which really sucks, beacuse iptables sometimes puts the arguments in weird orders, making it so that what we generate doesn't 100% match it
23:50 murrdoc the service name escapes me
23:50 vxitch manfred: i have a need for a base set of rules then additional rules on top of that depending on which services or apps are running on a minion, so the file.managed route would get very messy
23:51 manfred vxitch:  well, then you need to switch to rhel 7, or ubuntu 12/14
23:51 vxitch alright, looks like even more incentive to move to el7
23:51 manfred bcause doing it with the iptables module is not reliable
23:51 vxitch how supported is el7 by salt?
23:51 manfred it is fine
23:51 n8n joined #salt
23:52 to_json joined #salt
23:54 Eugene It's in EPEL and it works
23:54 skyler When I run 'salt-key -L' it takes a long time to return. On the order of 1 to 3 minutes. Has anyone else had this?
23:54 manfred and the tests currently run against cent 7
23:55 vxitch manfred: oh thats great to know
23:55 vxitch are there tests for each module as well? i remember before the 2014 releases i ran into awful issues with testable bugs in modules, namely iptables (hah)
23:57 manfred not all modules have tests
23:58 Outlander joined #salt

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