Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2015-11-08

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

All times shown according to UTC.

Time Nick Message
00:02 dthom91 joined #salt
00:10 dthom911 joined #salt
00:12 viq joined #salt
00:21 maduro joined #salt
00:22 zsoftich1 joined #salt
00:23 itisme joined #salt
00:23 maduro joined #salt
00:24 subsignal joined #salt
00:29 dthom911 joined #salt
00:31 otter768 joined #salt
00:32 maduro joined #salt
00:32 otter768 joined #salt
00:36 dthom91 joined #salt
00:40 hightekvagabond joined #salt
00:44 maduro joined #salt
00:51 hightekvagabond joined #salt
00:51 hightekvagabond joined #salt
00:52 hightekvagabond joined #salt
01:02 subsignal joined #salt
01:20 dthom91 joined #salt
01:24 lpmulligan joined #salt
01:30 JDiPierro joined #salt
01:36 timoguin joined #salt
01:37 hightekvagabond joined #salt
01:41 fsteinel joined #salt
02:04 NV joined #salt
02:05 quasiben joined #salt
02:28 dthom91 joined #salt
02:40 hasues joined #salt
02:41 hasues left #salt
02:42 larsfronius joined #salt
02:47 ilbot3 joined #salt
02:47 Topic for #salt is now Welcome to #salt | 2015.8.1 is the latest | Please use https://gist.github.com for code, don't paste directly into the channel | Please be patient when asking questions as we are volunteers and may not have immediate answers | Channel logs are available at http://irclog.perlgeek.de/salt/
02:50 NrsV joined #salt
02:50 Vaelater1 joined #salt
02:50 NrsV hi
02:50 catpigger joined #salt
02:55 bhosmer_ joined #salt
03:05 stanchan joined #salt
03:07 yidhra joined #salt
03:24 dthom91 joined #salt
03:25 otter768 joined #salt
03:36 racooper joined #salt
03:40 dthom91 joined #salt
03:41 furrowedbrow joined #salt
03:46 aphor way past beer-o-clock here in #salt
03:46 NrsV salt-call beer.give who=me
03:46 aphor If CM can't give you back work/life balance what good is it?
03:48 HappySlappy joined #salt
03:49 dthom91 joined #salt
03:50 moogyver joined #salt
03:51 Hazelesque heheheh
03:51 * Hazelesque could do with a drink...
03:51 Hazelesque spent an hour troubleshooting a "problem" with pillars...
03:51 Hazelesque turns out I'd checked it out as /srv/pillars (with an s) but the path in /etc/salt/master was /srv/pillar (no s)
03:51 Hazelesque :/
03:53 Hazelesque and now it is [almost] 4am... so I probably shouldn't attempt to finish what I started with the iptables states at this hour...
04:13 cedwards joined #salt
04:14 cedwards I'm wondering if it's possible to reference pillar data on the command line
04:15 cedwards I see that I can define pillar data with pillar={'foo': 'bar'}, but I want to reference existing data
04:15 PeterO joined #salt
04:20 FreeSpencer joined #salt
04:20 FreeSpencer joined #salt
04:21 nobrak joined #salt
04:21 nobrak joined #salt
04:22 dthom91 joined #salt
04:27 nobrak joined #salt
04:27 nobrak joined #salt
04:27 FreeSpencer joined #salt
04:27 FreeSpencer joined #salt
04:36 whytewolf cedwards: the answer is it depends. some cli modules can do jinja direcly such as cmd.run: salt '*' cmd.run 'echo {{salt.pillar.get("taco_tuesday")}}' template=jinja
04:38 cedwards i will try that. thanks
04:43 larsfronius joined #salt
04:56 sunkist joined #salt
04:58 meanieotter left #salt
04:58 meanieotter joined #salt
04:59 dthom91 joined #salt
05:02 JDiPierro joined #salt
05:15 dthom91 joined #salt
05:26 otter768 joined #salt
05:38 otter768 joined #salt
05:39 okfine joined #salt
06:14 llua for some reason, i can't use the pkg.* modules: http://sprunge.us/Ndei is a trace of a run. how should a go further troubleshooting this issue?
06:28 whytewolf huh, SuSE, one of the few distros i havn't touched in ten years. however I'm not sure what pkg manager that salt supports lines up with SuSE. SuSE is rpm based. but doens't use yum IIRC.
06:28 whytewolf ahh zypper
06:28 markm joined #salt
06:30 whytewolf llua: looks like you need to see if A. the os_family is listed as Suse "salt 'minion' grains.get os_family" and that zypper is avalible.
06:32 llua the family is: openSUSE Leap and zypper is available.
06:34 whytewolf llua: thats the problem then. as you can see here https://github.com/saltstack/salt/blob/01490387d714256191b3017fe488175b55231bbf/salt/modules/zypper.py#L40-L49 the code is looking for Suse. not openSUSE Leap
06:37 llua whytewolf: heh. thanks for that.
06:38 geomyidae_ left #salt
06:38 jaybocc2 joined #salt
06:40 whytewolf llua: https://github.com/saltstack/salt/issues/27744 looks like zypper is getting a bit of love. SuSE isn't exactly a widely used distro around here.
06:44 llua yea, i saw that and decided to build develop to see if it was related.
06:49 s_kunk joined #salt
06:56 jaybocc2 joined #salt
07:03 jaybocc2_ joined #salt
07:09 subsignal joined #salt
07:15 jaybocc2 joined #salt
07:29 armyriad joined #salt
07:33 okfine joined #salt
07:37 Vaelatern joined #salt
07:39 llua heh, and service.get_all doesn't return any systemd units in leap.
07:45 Lionel_Debroux joined #salt
07:46 jaybocc2 joined #salt
07:49 otter768 joined #salt
07:51 jaybocc2_ joined #salt
07:52 mehakkahlon joined #salt
07:57 jaybocc2 joined #salt
08:13 subsignal joined #salt
08:14 scarcry joined #salt
08:23 scarcry joined #salt
08:33 elsmo joined #salt
08:41 Knuta uh, salt-run pillar.show_top saltenv=dev gives me the content of the pillar topfile for the dev environment. If I omit saltenv or use saltenv=base, I get the topfile for the salt states, not pillar. That can't be right?
08:41 szhem joined #salt
08:43 mehakkah_ joined #salt
08:48 whytewolf Knuta: ... that really does not sound right. I do not see the same thing when i try it
08:49 hightekvagabond joined #salt
08:54 rocket_ joined #salt
08:56 evle1 joined #salt
09:17 Knuta whytewolf: never mind, I'm stupid. Guess what happens if you set /srv/salt as your pillar root instead of /srv/pillar? :-P
09:17 whytewolf Knuta: lol, that would do it
09:18 Knuta that took waay too long to figure out :-P
09:21 thefish joined #salt
09:25 subsignal joined #salt
09:30 mbrgm joined #salt
09:30 mbrgm is there a way to make reactor work when using salt-ssh?
09:31 whytewolf mbrgm: I doubt it. unless salt-ssh can fire off events which is how reactor knows to do it's magic.
09:33 Fiber^ joined #salt
09:36 whytewolf mbrgm: there is a way to test though. watch the event bus. and fire off a salt-ssh command
09:36 whytewolf https://docs.saltstack.com/en/latest/topics/event/index.html#listening-for-events
09:37 mbrgm whytewolf: ty
09:45 larsfronius joined #salt
09:50 otter768 joined #salt
09:59 whytewolf ahh fun, rebuilding openstack. and starting from scratch on my openstack salt setup to make it more robust as well as as using more generic configs.
10:04 anmolb joined #salt
10:08 jaybocc2 joined #salt
10:13 Guest55101 joined #salt
10:14 edulix joined #salt
10:18 cyborg-one joined #salt
10:22 MK_FG joined #salt
10:26 subsignal joined #salt
10:40 MK_FG joined #salt
10:48 rotbeard joined #salt
10:52 Hazelesque out of interest... if "salting the salt master"... and you:re using the "salt.master" state from salt-formula, and you've added the git repo for salt-formula to salt:master:gitfs_remotes in pillars...
10:53 Hazelesque how do you solve the chicken and egg problem to bootstrap the salt master initially?
10:54 Hazelesque or do you cheat, and put the salt-formula into /srv/formulas, and then have /srv/formulas/salt-formulas as a hard-coded file root in your initial /etc/salt/master?
10:55 whytewolf I wouldn't know i don't use the formula. but i would assume that you would work with a checked out copy
10:56 Hazelesque and not with gitfs_remotes, then?
10:56 whytewolf yeah. honestly you should almost never point directly at the upstream formulas anyway. even when using gitfs_remote.
10:57 whytewolf you end up at the whim of other developers that may break things from time to time
10:57 Hazelesque whytewolf: I see. was trying to work out whether I should just drop on or more of my own files in /etc/salt/{minion,master}[.d], or use a formula...
10:57 Hazelesque whytewolf: yeah, I saw that... which is why I forked them first
10:57 jaybocc2 joined #salt
10:59 Hazelesque any idea if the iptables-formula is any good?
11:00 whytewolf I have no idea. I don't do a lot with any of the formulas.
11:00 Hazelesque ah, okay... was mostly trying to see whether this was better than rolling my own for everything
11:01 Hazelesque I guess it's a tradeoff, along the lines of "do these people know better than me how Salt should be done" vs "but is my situation more specific"
11:01 Hazelesque and the built in iptables state stuff looked very verbose and to involve a lot of boilerplate and repeated stuff
11:01 whytewolf typically yeah. I fall into the my situation is more specific. and
11:02 favadi joined #salt
11:02 whytewolf honestly since i only work with ubuntu in my home lab i don't need to build out the bloated map.jinja stuff
11:02 Hazelesque (right now, I just want to have a consistent firewall policy, so I can actually put the apps on these machines without worrying about them being exposed~
11:02 Hazelesque whytewolf: oh?
11:03 mbrgm joined #salt
11:03 whytewolf map.jinja works great for building a a system that can be in any distro. which is why formulas work so well across the board. but they also tend to bloat the code with a lot of jinja
11:04 Hazelesque (at work, we hava Cisco ASA 5510 between us and the internet... and some Rackspace proprietary crap to manage iptables... but this is just some linode boxes for the hackspace, so I have to DIY it...)
11:04 Hazelesque ahh
11:04 Hazelesque I see
11:04 whytewolf you might want to spin the iptables stuff up in a test system. see if it works for you. might be simpler then learning the iptables module cause i heard that thing can be a pain.
11:05 Hazelesque I guess part of me is less worried about bloat for this project, and more worried about idiot-proofing...
11:06 whytewolf that is always a good thing to look for.
11:06 Hazelesque or, rather, I have very limited time to work on it, and it could well be someone else who touches it next... so it should ideally be as close to the "beaten path" of Salt as possible
11:06 whytewolf I used to use the vim formula.
11:07 Hazelesque I have to admit I do like what I've seen of the Salt Formulas stuff so far... when working with CFEngine3, I looked at the CFEngine Design Center "sketch" stuff and it just seemed horribly ass-backwards and weird...
11:07 mbrgm left #salt
11:07 Hazelesque but that was back when I was new to CFEngine, so maybe if I looked at it again now I'd see the light
11:08 whytewolf hummm the iptables formula doens't look to bad. how ever it does look like it is strictly iptables. no firewalld or ufw
11:09 Hazelesque mm, yeah
11:10 whytewolf they also skipped map.jinja and just put it at the top of the init.sls file
11:10 Hazelesque ah
11:11 Hazelesque it looks from the docs like the interface might be generic enough that it could be made to talk to other firewall systems?
11:11 Hazelesque in terms of how you declare what you want?
11:11 Hazelesque it doesn't seem particularly iptables-flavoured to me
11:12 whytewolf it is straight up using the iptables module
11:12 Hazelesque well, yes
11:12 Hazelesque but
11:12 Hazelesque I mean
11:12 Hazelesque the format you write your declarations in
11:12 Hazelesque /someone/ could write another implementation that uses that data?
11:12 whytewolf oh defintly
11:12 Hazelesque in that it's not full of "-j THIS"
11:13 Hazelesque "-A OUTPUT" etc
11:14 * Hazelesque wonders where the valid friendly service names are declared, whether the formula has them hard coded, whether it gets them from /etc/services, or whether iptables itself has a set of known symbolic names (or itself looks them up in /etc/services~
11:14 whytewolf yeah. humm, strange. all of the chains are set to INPUT
11:14 Hazelesque whytewolf: as in, this supports ingress filtering only?
11:14 Hazelesque no egress filtering?
11:15 whytewolf yeah
11:15 Hazelesque I wonder if it DTRT with ICMP and ICMPv6
11:15 * Hazelesque may have to pull up her cisco ios firewall config and crib the list of stuff that she allows from there...
11:15 whytewolf the only chain that isn't INPUT is a call to the nat table for NAT rules
11:16 denys joined #salt
11:16 whytewolf well proto is a pillar setup so it can do ICMP
11:16 Hazelesque tbh, ingress filtering would still be a buttload better than nothing...
11:17 Hazelesque the next thing is to set up Flynn, and that basically assumes it has a private network to talk over for its internal comms
11:17 whytewolf humm. except they all have a dport and IIRC iptables doesn't like dport and proto icmp
11:17 Hazelesque hence Firewall Time(TM)
11:17 Hazelesque whytewolf: oh goodie
11:18 whytewolf i don't know if the iptables module is smart enough to ignore dport if proto is icmp
11:18 Hazelesque someone should write a firewall tool for Linux that reads Cisco IOS format access-list and access-class definitions... >:3
11:19 Hazelesque (and, no, Cisco's internal IOS-on-Unix that they use for testing doesn't count ;))
11:20 whytewolf lol.
11:22 whytewolf humm, all you would really need is something that can take cisco logic and translate it into dumb.... i mean linux logic
11:27 subsignal joined #salt
11:28 evle joined #salt
11:38 Fiber^ joined #salt
11:38 openfly joined #salt
11:51 mdupont joined #salt
11:51 otter768 joined #salt
11:54 cyborg-one joined #salt
12:12 Striki joined #salt
12:20 favadi joined #salt
12:25 Bryson joined #salt
12:29 quasiben joined #salt
12:33 markm joined #salt
12:33 antonw joined #salt
12:37 munhitsu joined #salt
12:42 mattl joined #salt
12:42 copelco joined #salt
12:46 akoumjian joined #salt
12:46 malinoff joined #salt
12:47 larsfronius joined #salt
12:49 bstaz joined #salt
12:50 JonGretar joined #salt
12:52 mihait joined #salt
12:54 davedash joined #salt
12:56 ramblinpeck joined #salt
13:05 LinuxHorn joined #salt
13:08 m0nky joined #salt
13:09 jaybocc2 joined #salt
13:14 pcdummy joined #salt
13:14 pcdummy joined #salt
13:19 bVectr joined #salt
13:24 jaybocc2 joined #salt
13:30 subsignal joined #salt
13:34 Guest55101 Hi there! Is there a way to rebuid yum cache via salt? I mean without using cmd.run? May be salt has some built-in function?
13:37 whytewolf Guest55101: salt 'yumminion' pkg.clean_metadata
13:37 mitsuhiko joined #salt
13:37 whytewolf Guest55101: https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.yumpkg.html#salt.modules.yumpkg.clean_metadata
13:39 Guest55101 whytewolf: Thanks for the quick reply! I've seen this, but how can I use it from .sls?
13:40 whytewolf by calling it with module.run state
13:40 ggoZ joined #salt
13:40 whytewolf https://docs.saltstack.com/en/latest/ref/states/all/salt.states.module.html#salt.states.module.run
13:42 Guest55101 whytewolf: Oh, I see... Thank you!
13:43 whytewolf no problem
13:52 otter768 joined #salt
13:57 babilen Guest55101: Why is that necessary? (just curious)
13:59 Vaelatern joined #salt
14:10 Guest55101 babilen: I do this after changing repositories.
14:14 babilen For apt based systems pkg.install would update repositories (so would pkgrepo.managed). Are you sure that you have to do it yourself?
14:23 Guest55101 babilen: After switching to another repos yum fails with 404 error on some packages. If I rebuild cache, everythings works fine.
14:31 subsignal joined #salt
14:36 Erik_____ joined #salt
14:36 Erik_____ Hi all need help with salt-cloud
14:37 Erik_____ i setup a provider and can run salt-cloud --query ec2
14:37 Erik_____ i created a profile windows-server-2012 but when i try to lounch i get
14:38 Erik_____ Profile windows-server-2012 is not defined
14:38 Erik_____ who can assit me?
14:43 saltman joined #salt
14:43 saltman I wrote a module, that use __pillar__ (DUNDER DICTIONARIES)
14:44 saltman So I wrote the following: __pillar__['rm']['keystore']
14:44 saltman It gives the following error: __pillar__['rm']['keystore'])\nKeyError: 'rm'\n",
14:45 saltman But when I do: salt-call pillar.get rm
14:45 saltman I get the result: local:  keystore: 1456
14:47 catpig joined #salt
14:48 saltman Why it doesn't return the result with DUNDER DICTIONARIES?
14:57 timoguin joined #salt
14:57 voxxit joined #salt
15:02 RandyT Erik_____: can you show me your provider and profile configuration in a gist?
15:02 RandyT Erik_____: you might also try adding -l debug to that command to see what is happening.
15:03 malinoff joined #salt
15:04 quasiben joined #salt
15:16 Erik_____ Missing configuration file: /etc/salt/cloud.profiles
15:16 Erik_____ but i set it on cloud.profiles.d/windows-server-2012
15:23 Erik_____ https://gist.github.com/erikpar/223c9a9f6260810df5f5
15:23 RandyT Erik_____: try renaming the config file to have .conf extension. I've seen discrepancy in the docs that suggest that any file in that directory will be parsed, but behavior is different.
15:24 RandyT if you confirm that, should probably file an issue in github
15:26 RandyT Erik_____: in profile, your provider is actually us-west-2-ec2:
15:26 Erik_____ ok i set it to conf gile now its reading it but
15:27 Erik_____ still Profile windows-server-2012_private is not defined
15:27 RandyT not sure what version of salt you are running, but newer versions have also changed to use the term "driver:" to avoid confusion.
15:27 RandyT so in provider, you are driver: ec2
15:28 RandyT in profiles, you point to provider us-west-2-ec2:
15:28 RandyT driver: is available to you in 2015.8.x
15:30 Erik_____ so to change proviler in profile to driver?
15:31 RandyT Erik_____: no, in your provider definitiion, you set driver: ec2
15:31 RandyT in your profiles, you reference the defined provider: us-west-2-ec2
15:31 Erik_____ ok let me check
15:32 subsignal joined #salt
15:32 Erik_____ bravo
15:32 Erik_____ its working thanks alot
15:33 CeBe joined #salt
15:33 RandyT np
15:33 amcorreia joined #salt
15:36 jaybocc2 joined #salt
15:36 sunkist joined #salt
15:39 ldelossa joined #salt
15:40 favadi joined #salt
15:44 rmnuvg joined #salt
15:51 jaybocc2 joined #salt
15:53 otter768 joined #salt
15:59 Guest55101 What's the point to install yum's groups with repoquery like salt does instead of using 'yum groupinstall'? In this case salt's pkg.group_installed fails while yum groupinstall works fine.
16:00 Guest55101 BTW, salt-2015.8.1-1.el7
16:14 totte joined #salt
16:14 aphor Guest55101: search GitHub for related issues. Maybe you could write up a new one and that will be fixed?
16:15 dthom91 joined #salt
16:32 subsignal joined #salt
16:42 larsfronius joined #salt
16:49 mehakkahlon joined #salt
16:58 ubikite1 joined #salt
17:00 bhosmer joined #salt
17:02 saltman Is there any known issue in DUNDER DICTIONARIES with salt 2015.5.2?
17:03 saltman I try to use __pillar__ dictonary, and it doesn't find the key (but with pillar.get it works well)
17:06 mdupont joined #salt
17:07 opensource_ninja joined #salt
17:08 ageorgop joined #salt
17:08 viq joined #salt
17:12 dthom91 joined #salt
17:27 o1l3r joined #salt
17:28 o1l3r hey guys, trying to set up salt on centOS and when running #salt-master &, returns a processid.
17:30 o1l3r when I run #salt-master on &, returns a processID, and then "[WARNING]Unable to bind socket, error: [Errno 98] Address already in use The ports are not available to bind"
17:30 okfine joined #salt
17:30 o1l3r any ideas on where I may have messed up? This is right after the initial install. This is also my first time working with centOS/salt.
17:33 o1l3r #netstat -anp | grep 4505, returns "tcp 0 0 0.0.0.0:4505 0.0.0.0:* LISTEN 12626/python"--this is the pid I received for salt-master start
17:46 itisme joined #salt
17:46 karee joined #salt
17:52 o1l3r appears it may not be an issue, I was under the impression I needed to be able to ping salt from the terminal, but I believe I need to set up the salt-master location in the minion
17:54 otter768 joined #salt
18:02 subsignal joined #salt
18:03 jaybocc2 joined #salt
18:03 clintberry joined #salt
18:09 anmolb joined #salt
18:11 const_ joined #salt
18:11 const_ Hi all, is there some way to pass variable to state include?
18:13 clintberry joined #salt
18:18 jaybocc2 joined #salt
18:21 clintber_ joined #salt
18:25 clintberry joined #salt
18:26 clintbe__ joined #salt
18:29 clintber_ joined #salt
18:30 dthom91 joined #salt
18:43 larsfronius joined #salt
19:05 moeyebus Morning
19:05 moeyebus I seem to be having a problem now
19:06 moeyebus I'm using the lxc.container_profile configuration option, and I can't seem to reach it from config.get
19:06 mbrgm joined #salt
19:08 mbrgm hey! is there a way to mirror only part of a state tree to a second master or syndic? I'd really like to avoid exposing our internal salt master to the DMZ but still want to be able to manage the DMZ hosts without buildin a separate state tree. how can such a problem be dealt with?
19:08 moeyebus My mistake: I can get it via config.get but lxc.present results in a key error.
19:10 moeyebus KeyError: 'lxc.get_container_profile'
19:13 moeyebus Here's the pillar file I've written: http://ix.io/m1j
19:14 moeyebus and how I try to import these:
19:14 moeyebus http://ix.io/m1k
19:16 otter768 joined #salt
19:18 whytewolf moeyebus: what version are you on, cause KeyError typically means it can not load the module. or the module doesn't exist
19:18 moeyebus 2015.8.1
19:19 whytewolf humm, that doesn't sound right, cause KeyError was fixed by then.
19:21 whytewolf actually check your minions version with test.version
19:21 moeyebus left #salt
19:21 moeyebus joined #salt
19:21 moeyebus ok
19:22 moeyebus salt minions are 2015.8.1
19:23 moeyebus I sure hope I didn't find a bug, again...
19:23 moeyebus I seem to be doing only that these days. It's so frustrating. ^^
19:24 whytewolf humm. okay. strange. you are calling lxc.present. but it is complaining about get_container_profile?
19:26 moeyebus yup
19:26 whytewolf ohhhh, I see. the lxc state doesn't have a __virtual__ function so it lazy loads fine. however the exacution module that it calls does have a virtual and must not be able to load
19:27 whytewolf looks like the execution module is looking for lxc-start in the path.
19:27 moeyebus whytewolf: I have no idea what you just said means.
19:27 moeyebus whytewolf: That's it. I didn't install lxc
19:27 moeyebus ... --'
19:28 whytewolf basicly __virtual__ is a function in the modules that uses logic to determine if the module will load or not. saves a bit of mem when dealing with lots of modules.
19:28 moeyebus Oh, I get it.
19:28 whytewolf there is a minor bug. the lxc state shouldn't have loaded if the exacution bug didn't load. but that is a minor bug. I would put that one in
19:31 whytewolf but yeah. once you install lxc [greater then 1.0 according to the docs] you should be golden
19:31 kermit joined #salt
19:33 whytewolf mbrgm: mirror part of the state tree? well. you could look at using enviroments for that. or split your state tree up into diffrent repos and point each master at different repos
19:41 mehakkahlon joined #salt
19:46 zzzirk joined #salt
19:48 moogyver joined #salt
20:08 mapu joined #salt
20:17 nethershaw joined #salt
20:20 otter768 joined #salt
20:20 okfine joined #salt
20:29 Lionel_Debroux joined #salt
20:32 hasues joined #salt
20:32 hasues left #salt
20:49 ziro` joined #salt
20:53 Bryson joined #salt
20:55 blast_hardcheese joined #salt
21:01 bhosmer joined #salt
21:05 ziro` joined #salt
21:16 ziro` joined #salt
21:21 clintberry joined #salt
21:25 clintber_ joined #salt
21:26 clintberry joined #salt
21:29 MadHatter42 joined #salt
21:33 ziro` joined #salt
21:36 dthom91 joined #salt
21:38 edrocks joined #salt
21:44 moeyebus Anyone has a nice way to file.managed with the output from a command line? :)
21:48 nkuttler moeyebus: where do you run that command?
21:49 moeyebus on the minion
21:49 nkuttler hmr, just redirect the output?
21:49 keimlink joined #salt
21:50 moeyebus nkuttler: Yeah, I know. I want to be able to use file.watch after this.
21:51 nkuttler i wasn't sure if you can you use file.managed without a source
21:52 moeyebus nkuttler: I've thought of a solution now.
21:53 moeyebus running command > /tmp/stuff then file.managed source=/tmp/stuff name=/my/file.txt would work
21:54 moeyebus That'd be an extra step, but heh...
22:04 iggy saltman: gist some code
22:07 opensource_ninja joined #salt
22:08 ajw0100 joined #salt
22:09 Dev0n hey, am I right in saying that setting state_events to true would allow me to see the progress of a highstate?
22:14 NotBobDole joined #salt
22:16 enigma99a joined #salt
22:18 enigma99a I have been trying to get ext pillar working with git. I defined:
22:18 enigma99a git_pillar_provider: pygit2 git_pillar_pubkey: /root/.ssh/id_rsa.pub git_pillar_privkey: /root/.ssh/id_rsa git_pillar_passphrase: mypasswd   ext_pillar:   - git:      - production git@gitlabhost.net:salt/prod-pillar.git
22:18 dthom91 joined #salt
22:18 enigma99a looks correct to me and my files are in /var/cache/salt/master/git_pillar/7a3dd906d436e1bb19ea215a8fe04b88
22:19 enigma99a but when I do a salt '*' pillar.items
22:19 enigma99a the list is empty
22:19 enigma99a any ideas on how to troubleshoot?
22:19 enigma99a I don't see any errors
22:28 enigma99a https://gist.githubusercontent.com/anonymous/40d7497306d124052de3/raw/0035386210d711b3eea8feabea44d6c9515ceceb/gistfile1.txt
22:28 enigma99a should have pasted the config there :)
22:29 moogyver joined #salt
22:30 otter768 joined #salt
22:37 sunkist joined #salt
22:50 ziro` joined #salt
22:57 dthom91 joined #salt
23:04 otter768 joined #salt
23:15 iggy salt --versions
23:26 blast_hardcheese joined #salt
23:31 dthom91 joined #salt
23:33 blast_hardcheese moeyebus: Are you trying to set changed when the output of a command changes, or do you actually _need_ the file around?
23:34 moeyebus blast_hardcheese: I need the file around.
23:35 blast_hardcheese moeyebus: I was just curious-- thanks
23:36 NotBobDole joined #salt
23:36 blast_hardcheese enigma99a: What version of salt are you running? iirc they changed how ext_pillar works in 2015.8
23:37 falenn joined #salt
23:37 blast_hardcheese but I can't find anything about that, I must be mistaken
23:38 blast_hardcheese oh wait, no
23:38 blast_hardcheese here it is
23:40 blast_hardcheese enigma99a: I just set this up yesterday with 2015.8, https://docs.saltstack.com/en/latest/ref/pillar/all/salt.pillar.git_pillar.html#git-pillar-2015-8-0-and-later was reasonably straightforward
23:40 blast_hardcheese only real confusion was realizing I had to put a top.sls in the git repo as well, which is different from how salt/top.sls works with gitfs
23:41 Knuta moeyebus: just do a python template and run the command using python :-)
23:41 Knuta moeyebus: you could probably even do a generic one and just pass the command as parameters.
23:43 falenn joined #salt
23:44 sunkist joined #salt
23:48 Knuta moeyebus: just do a file.managed with "source: salt://whatever/command.py" and "template: py". Then have implement a run() in command.py which returns the output of the command.
23:49 Knuta moeyebus: the command will be executed each time, and the output compared. So you can even set up other states to watch for changes.
23:50 stupidnic Would it not be easier to just make a module?
23:50 stupidnic I mean you are already in python at that point
23:51 Knuta this way you get all the features of file.managed for free
23:51 Knuta and it should only require like five lines of python in the template.
23:52 falenn joined #salt
23:52 Vaelatern joined #salt
23:53 Knuta I've never made a module, but I'm pretty sure it'd both be more work and less intuitive. Everyone's seen a file.managed with a template before, and can reason about the flow. They have no clue what a custom module does.
23:55 falenn_ joined #salt
23:57 JDiPierro joined #salt
23:58 jondonas joined #salt

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