Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-02-24

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

All times shown according to UTC.

Time Nick Message
00:00 ajw0100 joined #salt
00:00 sgviking joined #salt
00:03 davet1 joined #salt
00:03 davet1 joined #salt
00:07 krow joined #salt
00:11 helderco joined #salt
00:18 ewong_ joined #salt
00:20 dpn` joined #salt
00:22 mgw joined #salt
00:35 hunter joined #salt
00:38 fllr joined #salt
00:43 gnugnu6 joined #salt
00:43 DanGarthwaite joined #salt
00:45 nineteen1ightd joined #salt
00:48 Linuturk joined #salt
00:48 Linuturk joined #salt
00:49 juice- joined #salt
00:49 goodwill_ joined #salt
00:49 hvn joined #salt
00:50 giantlock joined #salt
00:50 psyl0n joined #salt
00:50 seblu joined #salt
00:50 Damoun joined #salt
00:50 jeff joined #salt
00:50 rmnuvg joined #salt
00:50 bdf_ joined #salt
00:50 vipuls joined #salt
00:50 clearclaw joined #salt
00:50 ch0psti23 joined #salt
00:50 gamingrobot joined #salt
00:50 dave4925 joined #salt
00:50 backjlack joined #salt
00:50 beardo joined #salt
00:50 codysoyland joined #salt
00:50 homelinen joined #salt
00:50 pexio_ joined #salt
00:50 SEJeff_work joined #salt
00:50 anuvrat joined #salt
00:50 fr0 joined #salt
00:50 cofeineSunshine joined #salt
00:51 andersb joined #salt
00:52 goodwill joined #salt
00:52 eculver joined #salt
00:52 eculver joined #salt
00:52 Corey joined #salt
00:52 jcockhren hey. is there's a way to restart the salt-minion service across many minions
00:52 goodwill joined #salt
00:54 mrchrisadams joined #salt
00:55 kossy joined #salt
00:56 psyl0n joined #salt
00:58 fllr joined #salt
01:02 lude joined #salt
01:03 scoates joined #salt
01:03 krow joined #salt
01:05 Furao jcockhren: run service.restart salt-minion
01:06 DanGarthwaite Beware of dragons here.
01:07 jcockhren Furao: thanks. I tried it out and it worked without hitch
01:07 DanGarthwaite Usually it works for me without a hitch.
01:07 jcockhren yeah. I remember it being broken a while back. glad that's no longer an issue
01:08 jcockhren "broken" or something
01:08 jcockhren so...
01:08 jcockhren the elasticsearch returner is nearly done
01:08 jcockhren ;)
01:15 mgw joined #salt
01:15 faldridge joined #salt
01:27 xzarth joined #salt
01:28 cachedout joined #salt
01:36 n8n joined #salt
01:39 bhosmer joined #salt
01:40 mgw joined #salt
02:11 kedo39 joined #salt
02:12 qybl joined #salt
02:16 elfixit joined #salt
02:18 AdamSewell joined #salt
02:20 helderco joined #salt
02:21 ravibhure joined #salt
02:24 ravibhure left #salt
02:27 ravibhure1 joined #salt
02:27 ravibhure1 left #salt
02:28 oz_akan joined #salt
02:30 Ryan_Lane joined #salt
02:30 Ryan_Lane1 joined #salt
02:32 monokrome joined #salt
02:38 jeffro_ joined #salt
02:43 xl joined #salt
02:50 returner joined #salt
03:17 yomilk joined #salt
03:17 AdamSewell joined #salt
03:19 robawt joined #salt
03:21 oz_akan joined #salt
03:22 rostam joined #salt
03:25 Gifflen joined #salt
03:26 favadi joined #salt
03:26 krow joined #salt
03:29 krow1 joined #salt
03:32 elithrar joined #salt
03:32 mgw joined #salt
03:39 faldridge joined #salt
03:40 dstanek joined #salt
03:49 yomilk joined #salt
03:57 Nexpro1 joined #salt
04:01 Networkn3rd joined #salt
04:08 returner joined #salt
04:09 AdamSewell joined #salt
04:25 krow joined #salt
04:39 acabrera joined #salt
04:57 oz_akan joined #salt
04:58 ipalreadytaken joined #salt
05:18 Furao joined #salt
05:18 dpn` left #salt
05:27 oz_akan joined #salt
05:29 n8n joined #salt
05:32 xDamox joined #salt
05:42 fllr joined #salt
05:46 cym3try joined #salt
05:53 robawt bueno yawls
05:59 ipalreadytaken joined #salt
06:04 kermit joined #salt
06:04 ajw0100 joined #salt
06:05 l0x3py joined #salt
06:24 krow joined #salt
06:28 oz_akan joined #salt
06:32 ajw0100 joined #salt
06:41 mephx joined #salt
06:43 rojem_ joined #salt
06:44 fllr joined #salt
06:45 fllr joined #salt
06:56 leonardinius joined #salt
06:58 Katafalkas joined #salt
06:59 mephx joined #salt
07:01 cachedout joined #salt
07:02 gammalget joined #salt
07:16 stephanbuys joined #salt
07:29 oz_akan joined #salt
07:37 liwen joined #salt
07:44 lessismore joined #salt
07:51 Kenzor joined #salt
07:54 robinsmidsrod joined #salt
07:55 dstanek_afk joined #salt
07:55 dave4925_l joined #salt
07:56 gamingrobot_ joined #salt
07:56 backjlack_ joined #salt
07:56 mephx joined #salt
07:57 Katafalk_ joined #salt
07:58 clearcla1 joined #salt
07:58 rmnuvg_ joined #salt
07:58 pexio joined #salt
07:58 fr0_ joined #salt
07:58 bdf joined #salt
07:59 jeff_ joined #salt
07:59 jeff_ joined #salt
08:00 n8n_ joined #salt
08:01 seblu42 joined #salt
08:02 vipul joined #salt
08:04 cofeineSunshine joined #salt
08:04 codysoyland joined #salt
08:04 homelinen joined #salt
08:04 giantlock joined #salt
08:05 homelinen joined #salt
08:07 backjlack joined #salt
08:09 anuvrat joined #salt
08:10 SEJeff_work joined #salt
08:10 beardo joined #salt
08:10 ml_1 joined #salt
08:11 balboah joined #salt
08:15 cofeineSunshine joined #salt
08:15 codysoyland joined #salt
08:15 homelinen joined #salt
08:15 giantlock joined #salt
08:17 cym3try joined #salt
08:18 harobed joined #salt
08:20 kadel joined #salt
08:24 krow joined #salt
08:27 zooz joined #salt
08:29 slav0nic joined #salt
08:30 oz_akan joined #salt
08:32 mike25ro joined #salt
08:32 linjan joined #salt
08:33 giantlock_ joined #salt
08:43 jeffro joined #salt
08:50 jeffro_ joined #salt
08:57 CeBe joined #salt
09:03 seblu joined #salt
09:04 yomilk joined #salt
09:07 sfello joined #salt
09:08 slav0nic joined #salt
09:11 Valdo joined #salt
09:14 aleszoulek joined #salt
09:20 krow joined #salt
09:22 ahtik joined #salt
09:23 echos How can I preview the output of salts renderers on a state file?
09:32 oz_akan_ joined #salt
09:34 slav0nic joined #salt
09:41 ajw0100 joined #salt
09:42 bhosmer joined #salt
09:54 rojem joined #salt
09:59 MrTango joined #salt
10:03 millz0r joined #salt
10:06 Furao joined #salt
10:08 Flusher joined #salt
10:16 colttt joined #salt
10:16 colttt hello!
10:17 colttt what are the defference between saltstack enterprise and saltstack community?
10:17 zooz joined #salt
10:20 millz0r money
10:21 colttt and nothing more (features or somthing else)
10:22 mike25ro support maybe..?
10:24 sfello_ joined #salt
10:25 krow joined #salt
10:25 Iwirada joined #salt
10:27 colttt ok..
10:27 colttt also it dosnt exist a paid version with more features.. thanks for this informatioN!
10:29 Iwirada :q
10:29 Iwirada sry...
10:29 Iwirada hi
10:30 Iwirada i have the following problem: when i call state.highstate i get the  comment: No Top file of external nodes data matches found
10:30 Iwirada but there is a top.sls in /srv/salt
10:31 Iwirada with the '*' wildcard. is there a possibility to debug that? i already tried -l debug when calling salt.
10:32 helderco joined #salt
10:32 liwen joined #salt
10:33 scarcry Iwirada: what is file_roots set to in your master config? did you change it or using defaults (which IIRC is indeed /srv/salt)
10:34 Iwirada scarcry:  i didnt touch /etc/salt/master at all - this is what confuses me
10:35 scarcry what does salt '*' state.highstate test=true return ?
10:36 scarcry pastebin it
10:36 Iwirada scarcry: wait a minute
10:36 scarcry sorry I meant salt '*' state.show_highstate
10:37 scarcry Iwirada: has calling salt
10:38 scarcry Iwirada: has calling salt '*' state.highstate worked before for you at all or 1st attempt ?
10:38 Iwirada scarcry: i dont think so
10:38 Iwirada scarcry: i would have more files on that machine, if it worked at all
10:39 carlos joined #salt
10:40 scarcry show contents of top.sls ?
10:41 scarcry did you create it yourself?
10:41 Iwirada http://slexy.org/view/s20RS7aR33
10:41 Iwirada yes
10:42 scarcry so does /srv/salt/repositories exist and if so, does it contain an init.sls ?
10:43 Iwirada yes
10:43 scarcry I'm also new on salt so I don't think I can help you out further sorry to say
10:43 scarcry have you googled the error salt is returning?
10:44 Iwirada scarcry: no worries
10:45 Iwirada what confuses me is that simmilar setups worked before, but this one just bugs me
10:45 scarcry Iwirada: fresh install?
10:45 scarcry how? which OS are you on ?
10:46 scarcry using packages or using latest git stuff?
10:46 scarcry anything in the logs?
10:46 scarcry tried starting salt-master in debug mode?
10:46 Iwirada yes. currently i try to autoprovision suse
10:46 Iwirada and yes, i have to use suse
10:47 scarcry so you're trying to bootstrap suse minions? I haven't used the bootstrap script myself yet so can't comment
10:47 Iwirada nothing in the logs i don't already know
10:47 scarcry kk
10:47 John__ joined #salt
10:48 scarcry Iwirada: hope someone else can help you out mate
10:48 Iwirada ah, i will just provision the machine again and take away some automations
10:48 Iwirada bootstaping isnt difficult
10:48 Iwirada just write a script to add the salt repository, install salt, set the master, and start teh service
10:49 scarcry like I said, I haven't tried bootstrapping a minion yet. I take it you've read http://salt.readthedocs.org/en/latest/topics/tutorials/salt_bootstrap.html ?
10:49 Iwirada scarcry: http://slexy.org/view/s20doMAiYT
10:50 scarcry Iwirada: thanks for that. I'm on SmartOS myself so not linux but that script might help me to brainstorm off from it a bit
10:51 Iwirada damn i totally forgot about that script :/
10:51 scarcry kk, perhaps I *have* helped you at a bit at least then
10:52 Iwirada i'm just reading teh source of the script
10:52 scarcry kk, well gotta do something else so all the best with it
10:52 astol joined #salt
10:52 Iwirada the problem is that under suse you shouldn't use the original repository, because there is only salt 0.16, which doesn't work with 0-17 masters
10:53 scarcry i'm running 0.16.3 myself so wouldn't know what 0.17 brought
10:53 scarcry haven't looked into that yet
10:53 scarcry but yeah, I am aware as of 0.17 that both master and minions *must* be on same version
10:54 scarcry no longer compatible
10:54 Iwirada on debian it defaults to 0.17, so i stick with the version of my distro of choice ;)
10:54 scarcry Iwirada: ditto mate
10:54 scarcry hopefully us SmartOS users will see 0.17 soon in pkgsrc
10:55 scarcry kk, gl with it
10:55 Iwirada scarcry: what is smartos, btw?
10:56 Iwirada some kind of linux? or more bsd?
10:56 Iwirada ah, kvm -> linux with fuse-zfs i guess.
10:56 scarcry smartos is an illumos distribution (hypervisor). illumos is what was once known as opensolaris
10:56 scarcry neither
10:57 scarcry it's the platform where actual ZFS was designed and built on but in open source form
10:57 scarcry smartos.org
10:57 Iwirada didn't know illumos had many users.
10:57 debaser joined #salt
10:57 scarcry you'd be surprised but one can't compare to the linux user base obviously
10:57 Iwirada i know zfs ;)
10:57 scarcry cool
10:58 Iwirada the zfs and kvm combo confused me
10:58 Iwirada ^^
10:58 scarcry ack
10:58 scarcry so yeah, os VMs (zones) + kvm + zfs + dtrace == awesome
10:58 Iwirada na, my idea was, when i would like to use zfs i would default to freebsd, which also only imported it from illumos
10:59 scarcry but enough of that, don't have to force you to drink the kool-aid :P
10:59 scarcry yup
10:59 Iwirada i might give it a shot, once i have time
10:59 scarcry I've run freebsd myself for many years
11:00 scarcry but at the core I've always been a solaris guy although us illumos users don't like to use that name anymore (solaris that is) since horacle
11:00 Iwirada hehe, oracle screwd a view projects when they took sun
11:01 Iwirada s/view/few/
11:01 scarcry just a view ^^
11:01 scarcry few lol yeah
11:01 scarcry not a native english speaker
11:01 Iwirada me neither
11:01 scarcry dutchie
11:01 _Flusher joined #salt
11:02 Iwirada austrian
11:02 scarcry nice to meet ya
11:02 Iwirada you, too
11:02 Iwirada i tell you, this suse creeps me out
11:03 scarcry i've never been a linux fan of any distro..always solaris/freebsd . have only worked with debian and rhel at work
11:03 scarcry because I was forced to, would defintely not have been my choice
11:04 zain joined #salt
11:04 scarcry netsplit?
11:04 vipul joined #salt
11:04 d10n_ joined #salt
11:04 nobody_314 joined #salt
11:05 goki joined #salt
11:05 scalability-junk joined #salt
11:05 herzi_ joined #salt
11:05 Iwirada i use mostly debian, but privately i try to switch to free/open bsd
11:05 mrchrisadams joined #salt
11:05 copelco____ joined #salt
11:05 rcsheets_ joined #salt
11:05 abele_ joined #salt
11:05 jgelens joined #salt
11:05 octarine joined #salt
11:06 pcarrier__ joined #salt
11:06 munhitsu_ joined #salt
11:06 munhitsu_ joined #salt
11:06 pkimber joined #salt
11:06 scarcry Iwirada: kk, don't know what current status of freebsd 10 is in regard to zfs and jails
11:06 scarcry illumos zones are so much more clean comparing it to freebsd jails a year back
11:07 scarcry don't track freebsd anylonger tbh
11:07 Chrisje joined #salt
11:07 scarcry Iwirada: gotta go mate, ttyl perhaps
11:08 debaser is it possible to avoid double returns on higher master from minions under lower master in syndic setup?
11:09 EvaSDK_ joined #salt
11:09 EvaSDK_ joined #salt
11:09 erjohnso joined #salt
11:09 Corey_ joined #salt
11:09 arthurlutz joined #salt
11:09 luminous joined #salt
11:10 debaser also, can i use multi-master setup to simulate different command topologies like in syndic setup?
11:10 debaser or is that only for redundancy_
11:11 debaser ?
11:14 Iwirada scarcry: i just found the location of the suse salt installation in the bootstrap script. it basically does what my script does, too
11:14 honestly_ joined #salt
11:14 Iwirada na, i checked, whether they were using the right repository
11:14 eculver_ joined #salt
11:14 bigmston1 joined #salt
11:15 oc joined #salt
11:16 mikkn_ joined #salt
11:17 Guest29587 joined #salt
11:17 hvn_ joined #salt
11:18 luminous joined #salt
11:18 n8n joined #salt
11:18 jeremyBass joined #salt
11:19 Zuru_ joined #salt
11:19 tempspace joined #salt
11:19 MTecknology joined #salt
11:20 robinsmidsrod joined #salt
11:20 Kenzor joined #salt
11:21 philipsd6 joined #salt
11:21 gammalget joined #salt
11:22 Katafalkas joined #salt
11:28 bhosmer joined #salt
11:29 Flusher joined #salt
11:32 abele_ joined #salt
11:34 abele joined #salt
11:35 srfwii joined #salt
11:35 derelm joined #salt
11:36 debaser can anyone give me some feedback on syndic use_
11:48 elfixit joined #salt
11:50 ckao joined #salt
11:56 whiskybar joined #salt
12:01 n8n_ joined #salt
12:06 Guest72558 joined #salt
12:09 honestly_ joined #salt
12:18 viq debaser: probably someone can.
12:19 viq oh, you did ask questions, let me see
12:22 Iwirada joined #salt
12:24 favadi joined #salt
12:29 rojem joined #salt
12:37 colttt does exist a dashboard (like puppet dashboard) for saltstack?
12:41 viq colttt: not really, though have a look at halite
12:42 rojem joined #salt
12:42 colttt viq: ok thanks..
12:42 viq colttt: depends what you want from a dashboard
12:42 Rojematic joined #salt
12:44 colttt only see some things (something like are all server does have the right config etc)
12:46 ajw0100 joined #salt
12:47 viq colttt: that's reports, and for that I'm afraid not really
12:48 DaveQB joined #salt
12:49 colttt viq: and what do halite?
12:50 logix812 joined #salt
12:51 Nazzy salt test-node pillar.items  24.81s user 9.18s system 95% cpu 35.743 total
12:51 Nazzy urg
12:51 bhosmer joined #salt
12:52 pnl gotofail.com
12:54 che-arne joined #salt
12:55 CeBe joined #salt
12:55 TamCore joined #salt
12:55 viq colttt: kind of a gui on top of normal salt. See which machines are responding, execute commands and see output
12:56 colttt but  the management like GUIs with colors, and pie with color ;)
12:56 viq colttt: https://github.com/saltstack/halite
12:56 Nazzy pnl, yes, I spotted that on G+ ... very fail
13:03 nicksloan joined #salt
13:04 nicksloan joined #salt
13:04 nicksloan left #salt
13:08 viq colttt: there's also salmon, but it plays a somewhat different role https://github.com/lincolnloop/salmon
13:12 hvn joined #salt
13:16 rjc joined #salt
13:23 brianhicks joined #salt
13:24 blee joined #salt
13:26 jcsp joined #salt
13:30 phyde_ joined #salt
13:32 jpaetzel_ joined #salt
13:33 eclectic joined #salt
13:33 aurigus joined #salt
13:33 aurigus joined #salt
13:33 fejjerai joined #salt
13:33 londo joined #salt
13:35 Ahlee joined #salt
13:35 svx_ joined #salt
13:35 utahcon_ joined #salt
13:35 Valda joined #salt
13:35 babilen_ joined #salt
13:35 mackstick joined #salt
13:35 rogst_ joined #salt
13:35 yongkang joined #salt
13:35 feth_ joined #salt
13:35 kvbik_ joined #salt
13:35 arnoldB_ joined #salt
13:35 kloplop321_ joined #salt
13:36 insatsu_ joined #salt
13:36 zach_ joined #salt
13:37 flebel_ joined #salt
13:38 fejjerai joined #salt
13:38 Gifflen joined #salt
13:38 crashmag_ joined #salt
13:38 SaveTheR0btz joined #salt
13:39 marcinkuzminski_ joined #salt
13:39 keekz_ joined #salt
13:39 melinath_ joined #salt
13:40 brucewang joined #salt
13:40 jeff joined #salt
13:40 jeff joined #salt
13:40 \ask_ joined #salt
13:40 terminalmage_ joined #salt
13:41 debaser viq: managed to pinpoint the problem, it was the debian init scirpt for syndic
13:42 debaser it seems it doesnt clean processes properly on restarts so i winded up with multiple syndics running which resulted in multiple minion calls/returns
13:42 EntropyWorks joined #salt
13:43 vbabiy joined #salt
13:43 rojem joined #salt
13:43 marcinkuzminski joined #salt
13:43 jaimed joined #salt
13:43 oc_ joined #salt
13:43 mephx_ joined #salt
13:44 mikkn joined #salt
13:44 hardwire joined #salt
13:44 kamal_ joined #salt
13:45 SEJeff_work joined #salt
13:45 dimeshake_ joined #salt
13:45 andersb_ joined #salt
13:45 ecdhe_ joined #salt
13:46 Marion joined #salt
13:46 ahtik joined #salt
13:46 dwfreed joined #salt
13:46 vegardx_ joined #salt
13:46 yano joined #salt
13:46 APLU joined #salt
13:46 Eugene joined #salt
13:46 arapaho joined #salt
13:47 goncalo joined #salt
13:48 kedo39 joined #salt
13:48 yml joined #salt
13:48 chitown joined #salt
13:48 trevorj joined #salt
13:48 che-arne joined #salt
13:48 jgelens joined #salt
13:48 nobody_314 joined #salt
13:48 Nazzy joined #salt
13:48 Nazzy joined #salt
13:49 scarcry joined #salt
13:49 Xe joined #salt
13:49 krak3n` joined #salt
13:50 jero joined #salt
13:50 razor joined #salt
13:52 sgviking joined #salt
13:52 alienresidents joined #salt
13:53 CeBe joined #salt
13:54 miguitas joined #salt
13:56 godog joined #salt
13:58 nineteen1ightd joined #salt
13:58 nineteeneightd joined #salt
13:59 viq debaser: ah, good to know. I had some problems with halite when syndic entered picture
13:59 snuffeluffegus joined #salt
14:00 erjohnso joined #salt
14:03 bhosmer joined #salt
14:05 debaser viq: yeah same here with our in-house web interface, some issues with higher master timing out a response from lower master
14:05 debaser syndic_wait on higher master helped some, but slowed down things considerably
14:05 bryano_ joined #salt
14:07 bhosmer joined #salt
14:07 racooper joined #salt
14:08 ipmb joined #salt
14:09 bhosmer joined #salt
14:09 bhosmer joined #salt
14:13 SEJeff_work When is the 2014.x release going to be released?
14:13 SEJeff_work Any rough timeline?
14:16 R_Shackleford joined #salt
14:17 krak3n` @SEJeff_work - today: http://docs.saltstack.com/topics/releases/2014.1.0.html
14:18 juicer2 joined #salt
14:20 sfello joined #salt
14:20 faldridge joined #salt
14:21 debaser is it possible to push new state modules from master to minions in a similar way to pushing custom execution modules (via /srv/salt/_modules)?
14:22 jrdx joined #salt
14:25 ajw0100 joined #salt
14:36 arnoldB_ how do you guys collect the public ssh rsa key of your users?
14:37 viq arnoldB: ask them to email them? Unless that's not what you're asking ;)
14:38 arnoldB viq: we have salt and we have Linux :) with users I mean system users I created myself with salt
14:39 GradysGhost joined #salt
14:39 alice|wl copy their keys to pillarf and maintain their keys with salt
14:40 arnoldB hmm. I've planned to collect the pubkeys via mine instead of managing them on the master
14:40 bezaban managing them centrally is useful
14:40 bezaban they're only public keys after all :)
14:41 yano joined #salt
14:41 arnoldB Example: I deploy a new OS, create users and install+configure software. the (system) users get ssh keys generated via ssh-keygen.
14:41 arnoldB the keys aren't known before deployment
14:42 arnoldB and I _do not want_ to define them manually
14:42 rojem joined #salt
14:42 Rojematic joined #salt
14:43 arnoldB think of a cluster where the cluster controller need to be able to ssh into the nodes.
14:43 sroegner joined #salt
14:43 Vivi-1 joined #salt
14:44 Troic joined #salt
14:45 zzzirk joined #salt
14:46 arnoldB cmd.run 'cat /var/lib/one/.ssh/id_rsa.pub'   could be working. but thats ugly
14:47 Gifflen joined #salt
14:48 viq arnoldB: http://docs.saltstack.com/ref/modules/all/salt.modules.ssh.html#salt.modules.ssh.auth_keys ?
14:48 viq and combine with saltmod
14:49 harobed joined #salt
14:49 rlarkin joined #salt
14:51 faldridge joined #salt
14:51 kaptk2 joined #salt
14:54 jeremyBass1 joined #salt
14:54 AdamSewell joined #salt
14:58 arnoldB ssh.auth_keys returns the authorized key, not the public rsa key
15:00 arnoldB hm
15:01 arnoldB I'll try to the hack it with cmd.run
15:03 mr_chris joined #salt
15:04 zooz joined #salt
15:04 mpanetta joined #salt
15:06 SEJeff_work krak3n`, Thanks!
15:10 SEJeff_work krak3n`, When is someone going to update /topic?
15:11 krak3n` i dunno, i guess its not out out yet, the package on PyPi hasn't been updated: https://pypi.python.org/pypi/salt
15:14 viq arnoldB: well, you need to generate the key somehow, you could at the same time copy it over to ~/.ssh/authorized_keys and have it available via that. Just a thought
15:14 Ztyx joined #salt
15:16 arnoldB viq: true
15:16 xerxas joined #salt
15:17 Ztyx Looking to provision a firewall on Ubuntu. With "ufw" being the recommended firewall on Ubuntu, but I can't find a state module for it. Are you guys provisioning firewall with ufw or iptables straight? Any recommended way? Example?
15:18 Ztyx I'm currently thinking about executing a managed script the sets up ufw the way I want it.
15:18 Ztyx s/the/that
15:19 cweisel joined #salt
15:23 rostam joined #salt
15:25 pdayton joined #salt
15:30 opapo joined #salt
15:30 dstanek is it possible to access grains in a reactor run sls?
15:31 dstanek i basically want to check for a given role and then run a script on the master to add the node to a load balancer
15:31 pdayton1 joined #salt
15:31 fllr joined #salt
15:34 Ztyx dstanek: I think these slides will give you an example of how this can be done: http://www.slideshare.net/SaltStack/real-time-cloud-management-with-salt-stack
15:35 Ztyx dstanek: (start from slide 29 and onwards)
15:38 dstanek Ztyx: i tried using salt mine, but had rendering issues...maybe i need to try again now that i've added logging
15:38 dstanek Ztyx: thanks for the pointer
15:38 keekz joined #salt
15:39 Ztyx dstanek: I see. I'm still learning salt and I haven't done orchestration (yet) myself. That said, I made sure it was possible before starting to work with salt.
15:39 Guest34564 joined #salt
15:42 forrest joined #salt
15:42 bhosmer_ joined #salt
15:42 schristensen joined #salt
15:43 quickdry21 joined #salt
15:47 tyler-baker joined #salt
15:48 jcockhren there are many many companies that currently use salt and are looking to use salt
15:48 jcockhren it was nice to see the interestr
15:49 forrest jcockhren, nice!
15:49 forrest you were at scale?
15:50 jcockhren It was at pyTennessee this weekend
15:50 jcockhren timoguin was there and gave a salt talk
15:50 jcockhren I lead a saltstack print
15:50 jcockhren sprint*
15:50 jcockhren I was telling tim, Emma uses salt exclusively
15:51 forrest ahh nice
15:55 sfello folks, sorry if this is a daft question - how can i get the IP of the minion to which I'm rendering files in the template?
15:55 abe_music joined #salt
15:55 sfello seems like it should be a common thing… but its quite hard to search for!
15:56 viq sfello: use grains for that
15:56 viq either grains, or saltcmd I guess
15:57 Ztyx sfello: see http://docs.saltstack.com/ref/states/vars.html#grains
15:57 rgbkrk joined #salt
15:57 sfello oh right, so {% for ip in grains['ipv4'] %}...
15:57 Ztyx sfello: yes
15:57 sfello cool, ta!
15:57 timoguin joined #salt
16:00 zwevans joined #salt
16:01 tharkun joined #salt
16:01 forrest jcockhren, what did you guys focus on for the sprint?
16:04 Heartsbane joined #salt
16:04 jeblair joined #salt
16:04 frasergraham joined #salt
16:05 zain joined #salt
16:05 fuser joined #salt
16:06 testing joined #salt
16:07 dstanek jcockhren: i didn't realize that there would be so much salt content or i would have gone
16:08 cachedout joined #salt
16:09 budrose joined #salt
16:12 sgviking joined #salt
16:13 nkuttler joined #salt
16:14 forrest dstanek, are you out in TN?
16:14 Nazzy urg ... file.manage's context arg is really dangerous
16:14 dstanek forrest: no, i'm a Clevelander
16:15 forrest oh
16:15 forrest Nazzy, with great power comes great responsibility :P
16:16 Kraln joined #salt
16:16 Nazzy forrest: I use a loop to generate states, each file.manage state has a non-trivial context passed ... so for every state it does a deepcopy of all the chunks, which includes all the context dicts
16:17 forrest ahh
16:17 Saint-N joined #salt
16:18 Nazzy when you have 800+ of these states, the scaling is scary
16:19 teskew joined #salt
16:19 forrest yea
16:19 Ztyx Nazzy: test=True on first call perhaps?
16:20 Ztyx ;)
16:21 forrest timoguin, how did the talk go>?
16:21 jcockhren forrest: I defined the core vocab (states, modules, pillar, master, minion, grains). gave them the spill about the problems salt can solve.
16:22 jcockhren forrest: basically distilled it all and then we 'together' wrote a salt module
16:22 forrest ahh nice
16:22 jcockhren gave them a salt master+minion vagrant setup
16:22 Nazzy Ztyx, doesn't help
16:23 nebuchadnezzar joined #salt
16:23 jcockhren forrest: after timoguin's talk signficantly wetted their appetite
16:23 jcockhren s/after//
16:23 kballou joined #salt
16:23 forrest jcockhren, That's great, hopefully we'll get some more contributors. We came close to being in the top 5 this year, but had some inactivity fom past users in 2013 :\
16:23 forrest jcockhren, yea I'm not surprised by that at all, when I did a talk locally here people were blown away
16:23 Saint-N is there a way to make salt behave sequential to it's minions like ansible?
16:24 Saint-N or would i have to forloop it in bash with a call to salt that way?
16:24 Nazzy 64.9% of function time spent on `'__lowstate__': copy.deepcopy(chunks) if chunks else {}`
16:25 jalbretsen joined #salt
16:26 Dinde joined #salt
16:26 opapo joined #salt
16:26 kiorky joined #salt
16:28 viq Saint-N: you mean one minion at once, or?
16:29 Saint-N kind of yeah
16:29 Saint-N like lets say i wanted to restart 50 apache servers
16:29 viq Saint-N: http://docs.saltstack.com/topics/targeting/batch.html
16:29 Saint-N but i want them to do so in order and not do another til the previous finishes
16:31 Saint-N nice thanks
16:31 Saint-N thats exactly what i wanted
16:32 forrest Saint-N, which release of salt are you on?
16:32 forrest batch is broken in 0.17.4
16:32 pdayton1 left #salt
16:32 Saint-N oh
16:32 Saint-N i think master is like 15 or something and minions are 17
16:32 Saint-N really need to get around to updating heh
16:33 viq Saint-N: master should be at least as new as minions
16:33 viq Saint-N: also 0.17.1 was a "flag day" - older than that won't talk with newer than that
16:34 Saint-N correction master is 0.14.0 minions randong from 10.2 - 17.2
16:34 viq Saint-N: because earlier than that there was a nasty bug with minion keys
16:34 Saint-N duplicate key causing?
16:34 viq no, poor quality encryption keys
16:34 Saint-N ahh
16:35 Ztyx left #salt
16:35 viq Saint-N: http://docs.saltstack.com/topics/releases/0.17.1.html
16:36 Saint-N yeah im gonna be updating all of them in th next week or so
16:36 forrest https://github.com/saltstack/salt/issues/8597 is still open...
16:36 Saint-N once we get rid of our arch boxes heh
16:36 Saint-N thanks for the headsup though now i have a justification to speed up the process
16:37 forrest salt works on arch! :P
16:37 Saint-N oh i know
16:37 forrest Saint-N, yea just be aware of that batch mode bug
16:37 Saint-N i just hate arch heh
16:37 forrest I wouldn't want you to bring down a bunch of machines like the guy who found the issue did
16:37 viq Saint-N: arch has now in commutnity 2014.1.0 ;) no need to build from aur :P
16:37 Saint-N they started a roll to ubu12.04lts
16:37 Saint-N so its like a 80/20 split rightnow ubu/arch
16:37 ChrisF_ joined #salt
16:38 Saint-N for some reason arch keeps forgetting its ldap server and making it irritating so it's going away
16:39 viq out of curiousity, will you be moving to next LTC, 14.04 once that comes out?
16:39 Saint-N prolly not for a while
16:39 liwen joined #salt
16:39 Saint-N might depend if its a stark change from 12.04 (ie more beneficial because of core updates)
16:40 Saint-N i tend to base os updates on the fbsd style
16:40 viq oh?
16:40 Saint-N in that each version is so retardedly better than the previous you're a fool not to
16:40 viq haha
16:40 alice|wl left #salt
16:40 Saint-N as opposed to the debian rolling updates style
16:40 Saint-N for servers anyways
16:40 Saint-N home machine im always bleeding edge
16:41 viq hm?
16:41 Saint-N cuz thats where the fun is
16:41 viq yeah, my boxes are usually either arch or openbsd-current ;)
16:41 Saint-N apt-get upgrade WOOO now i get to rebuild flash and java!
16:41 Saint-N heh
16:41 viq with the exception of NAS box which has freebsd for zfs ;)
16:41 Saint-N im morally opposed to obsd
16:41 Saint-N cuz theo is a dick
16:42 viq why so?
16:42 Saint-N used to hangout with him in calgary
16:42 Saint-N he makes stallman look humble
16:42 Saint-N and sane
16:42 ajw0100 joined #salt
16:42 Saint-N fbsd i love though
16:42 viq hah
16:43 Saint-N we actually had a discussion recently of shifting the whole infra to fbsd
16:43 timoguin forrest, yea it went well. i did try to pack in a bit too much for a 45min talk, but not too bad from what i've been told
16:43 Saint-N cuz its not like we buy new hardware heh
16:43 viq I don't know about Theo, but I love the sanity of OpenBSD config. And their package management tools. FreeBSD package management tools suck.
16:43 Saint-N lies!
16:43 Saint-N usr/ports rocks
16:43 timoguin i found another guy in nashville using salt to manage AWS stuff. we triaged the issues with autoscaling salt-minions in AWS
16:43 Ryan_Lane joined #salt
16:43 forrest timoguin, nice
16:44 timoguin and a buddy of mine that works at a django shop said they'll most likely start using it
16:44 forrest timoguin, what's the PR number?
16:44 Nazzy at a django shop? poor guy/girl
16:44 ipalreadytaken joined #salt
16:44 jacksontj_ joined #salt
16:44 timoguin none yet, but he's looking at it
16:44 Nazzy though it could be worse ... could be joomla *snerk*
16:45 Saint-N im mosty an ansible kid
16:45 timoguin as someone who's just started learning Django, it seems pretty damn nice
16:45 kiorky joined #salt
16:45 Saint-N but thats because i hate client/server things
16:45 Saint-N nrpe is the spawn of the debil
16:45 cachedout joined #salt
16:45 forrest timoguin, django is cool, I don't use it for internal tools most of the time though, too much work
16:45 forrest way easier to go with flask/bottle.
16:46 timoguin yea i've been playing with flask a bit too. i'm new the python web dev.
16:46 Nazzy django is an assortment of yuck, it's not massively bad, just probably the worst of the current
16:46 timoguin and actually still pretty new to python
16:46 Nazzy I actually really like tornado
16:46 forrest django has good docs though that's for sure
16:47 forrest Nazzy, I haven't messed with tornado much
16:47 forrest timoguin, I just like flask because I can get an app up and running in a day or less with it.
16:47 forrest slap some bootstrap on there, and it looks prettt good, while not being a hassle to get setup
16:47 Nazzy async web reactor ... doesn't require messing around with wsgi servers
16:48 Nazzy (also, if you ever plan to used websockets, avoid wsgi like the plague)
16:48 forrest Nazzy, I'm already sold on trying it now
16:48 forrest Nazzy, does it hook into apache/nginx easily?
16:48 TheRealBill_here joined #salt
16:49 Nazzy I put a reverse proxy mode nginx in front of it
16:49 forrest nice
16:49 forrest I'll have to try it out.
16:49 forrest I like that it supports python3
16:50 cweisel1 joined #salt
16:50 Nazzy the trick is getting your head round futures.concurrent ... you instantiate a thread pool, then when you have something you want to run outside the main thread you have your page handler return a future instead of a page result
16:50 forrest Nazzy, woah
16:51 forrest that's interesting
16:51 backjlack joined #salt
16:51 Nazzy *nod* it's actually useful, you can choose what you want to thread out and what you want to keep in the main thread
16:53 zach joined #salt
16:53 forrest Nazzy, I really wish there was a better standard for all these frameworks :\
16:54 bryano__ joined #salt
16:55 Nazzy it also hooks in to twisted, so you can have it internally do anything in the twisted.internet.protocols library
16:55 forrest cool
16:56 * Saint-N styabs the moosefs people
16:56 Saint-N there has to be a better in dev dfs that isnt moose
16:57 nobody_314 joined #salt
16:57 Nazzy joined #salt
16:57 Nazzy joined #salt
16:57 Heartsbane_ joined #salt
16:57 Nazzy wow, server not happy lol
16:57 gfa_ when i launch an event from a minion master run the state file according to tags, that's ok. but if i launch the same event master won't run the state file. i have to restart master to get it running again
16:57 Saint-N so are there any major hazards in 17.1 updates of all salt minions and master? master is 14.0 minions(about 80 or so) are primarily 10.5 13.1 and 17.5
16:57 ml_1 joined #salt
16:57 Saint-N mostly ubuntu 12.04lts
16:58 gfa_ it's annoying when you are developing the reactor formula
16:58 Nazzy though, funny thing, I noticed where the ssl for this server originates from: /C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware
16:59 gammalget_ joined #salt
16:59 mephx joined #salt
17:02 jrdx joined #salt
17:02 Valdo joined #salt
17:04 schristensen joined #salt
17:04 mr_chris joined #salt
17:04 hunter joined #salt
17:04 EntropyWorks joined #salt
17:04 bigmston1 joined #salt
17:04 tharkun joined #salt
17:04 dave4925 joined #salt
17:04 viq Saint-N: no, they don't. Installed a machine, with a bunch of stuff installed from ports. Installed poudriere, fed it list of ports and their options. And of course it did not build them with preper options/dependencies
17:05 TheRealBill_he-1 joined #salt
17:05 _Dinde joined #salt
17:06 jmccree joined #salt
17:06 jasonrm joined #salt
17:06 opapo_ joined #salt
17:06 ravibhure joined #salt
17:06 andersb joined #salt
17:06 cachedout joined #salt
17:06 zain joined #salt
17:06 jeblair joined #salt
17:06 zwevans joined #salt
17:06 timoguin joined #salt
17:06 keekz joined #salt
17:06 fllr joined #salt
17:06 xerxas joined #salt
17:06 kaptk2 joined #salt
17:06 faldridge joined #salt
17:06 harobed joined #salt
17:06 Gifflen joined #salt
17:06 ipmb joined #salt
17:06 racooper joined #salt
17:06 erjohnso joined #salt
17:06 jero joined #salt
17:06 scarcry joined #salt
17:06 ecdhe_ joined #salt
17:06 dimeshake_ joined #salt
17:06 SEJeff_work joined #salt
17:06 hardwire joined #salt
17:06 oc_ joined #salt
17:06 jeff joined #salt
17:06 __number5__ joined #salt
17:06 melinath joined #salt
17:06 fejjerai joined #salt
17:06 flebel joined #salt
17:06 kloplop321 joined #salt
17:06 feth_ joined #salt
17:06 utahcon_ joined #salt
17:06 aurigus joined #salt
17:06 TamCore joined #salt
17:06 Guest72558 joined #salt
17:06 ckao joined #salt
17:06 abele joined #salt
17:06 Zuru_ joined #salt
17:06 eculver_ joined #salt
17:06 munhitsu_ joined #salt
17:06 pcarrier__ joined #salt
17:06 goki joined #salt
17:06 d10n_ joined #salt
17:06 linjan joined #salt
17:06 beardo joined #salt
17:06 rmnuvg_ joined #salt
17:06 xzarth joined #salt
17:06 kossy joined #salt
17:06 rogst joined #salt
17:06 mackstick joined #salt
17:06 londo joined #salt
17:06 jcsp joined #salt
17:06 blee joined #salt
17:06 rjc joined #salt
17:06 hvn joined #salt
17:06 Iwirada joined #salt
17:06 srfwii joined #salt
17:06 tempspace joined #salt
17:06 honestly joined #salt
17:06 rcsheets joined #salt
17:06 copelco___ joined #salt
17:06 mrchrisadams joined #salt
17:06 herzi joined #salt
17:06 aleszoulek joined #salt
17:06 seblu joined #salt
17:06 fr0_ joined #salt
17:06 pexio joined #salt
17:06 clearcla1 joined #salt
17:06 gamingrobot joined #salt
17:06 elithrar joined #salt
17:06 scoates joined #salt
17:06 Guest7079 joined #salt
17:06 juice joined #salt
17:06 Linuturk joined #salt
17:06 markm joined #salt
17:06 Hefeweizen joined #salt
17:06 pnl joined #salt
17:06 simonmcc joined #salt
17:06 gldnspud__ joined #salt
17:06 modafinil_ joined #salt
17:06 z3uS joined #salt
17:06 darrend joined #salt
17:06 seb` joined #salt
17:06 dpac|away joined #salt
17:06 echos joined #salt
17:06 nliadm joined #salt
17:06 Kyle joined #salt
17:06 dirjax joined #salt
17:06 bretep` joined #salt
17:06 carmony joined #salt
17:06 vlcn_ joined #salt
17:06 cyrusdavid joined #salt
17:06 btorch_ joined #salt
17:06 BogdanR_ joined #salt
17:06 micko__ joined #salt
17:06 renoirb joined #salt
17:06 ahammond joined #salt
17:06 Guest24242 joined #salt
17:06 codekoala joined #salt
17:06 Jahkeup joined #salt
17:06 [vaelen] joined #salt
17:06 bezaban joined #salt
17:06 crane joined #salt
17:06 trevorjay joined #salt
17:06 jab416171_ joined #salt
17:06 jab416171_ joined #salt
17:06 marcinkuzminski joined #salt
17:06 marcinkuzminski joined #salt
17:07 dcolish joined #salt
17:07 gnugnu6 joined #salt
17:08 SaveTheRbtz joined #salt
17:11 ravibhure joined #salt
17:11 ravibhure left #salt
17:11 gammalget joined #salt
17:11 KyleG1 joined #salt
17:11 nineteeneightd joined #salt
17:11 KyleG joined #salt
17:12 nobody_314 joined #salt
17:12 KyleG joined #salt
17:14 funzo joined #salt
17:14 CaptTofu joined #salt
17:16 CaptTofu hi all!
17:16 CaptTofu anyone here who works with salt-cloud?
17:16 Vivi-Idle joined #salt
17:16 n8n joined #salt
17:17 kermit joined #salt
17:18 jeremyfelt joined #salt
17:19 jdenning joined #salt
17:19 blast_hardcheese joined #salt
17:19 Ryan_Lane joined #salt
17:19 Linz joined #salt
17:20 Ryan_Lane1 joined #salt
17:21 jcsp1 joined #salt
17:23 alekibango joined #salt
17:24 joehillen joined #salt
17:26 Mr_N Hrm.  Today's conundrum, pillar problems.
17:26 basepi joined #salt
17:27 Mr_N I have a /srv/pillar/users/ folder, which is set as a pillar_roots option in master
17:27 Mr_N and in that folder a root.sls pillar
17:27 Mr_N if I put - root under pillar top, I can see the proper data in pillar.items
17:27 Topic for #salt is now Welcome to #salt | 2014.1.0 is the latest | Please be patient when asking questions as we are volunteers and may not have immediate answers | Channel logs are available at http://irclog.perlgeek.de/salt/
17:27 Mr_N but if I make one level of abstraction, putting - users under pillar top, and then having an include: - root in users, I can no longer access the root pillar
17:28 viq Mr_N: users.root
17:29 Mr_N as the argument to pillar.get?
17:29 Mr_N Already tried that, no such luck.
17:29 viq Mr_N: no, as include
17:29 Mr_N Oh
17:29 arnoldB YAML question: what's the difference between `foo: bar` and `:foo: bar`?
17:29 davet joined #salt
17:30 Mr_N Hm.  Unless I'm doing this wrong, it doesn't appear to be working any differently.
17:30 Mr_N my include now reads like:  users: include: -users.root
17:31 viq Mr_N: what does your /srv/pillars/top.sls say?
17:31 Mr_N base: '*': - users
17:32 viq and do you have users/init.sls ?
17:32 Mr_N I have a users.sls.  I wonder how, if I have both a /srv/pillar/users and a /srv/pillar/users.sls, will it disambiguate properly?
17:33 Mr_N wondering if my terribly ambiguous naming caused this mess.
17:33 Mr_N I wonder now*
17:33 viq good question, and I don't know the answer.
17:33 Mr_N Thanks for your help thus far, I can poke at that.
17:33 viq Mr_N: though if you don't have users/init.sls, then just refering to users will not match anything in the users/ dir
17:33 Mr_N Yeah, that's what I'd _hope_ would happen
17:34 Mr_N my /users/ dir is exclusively for logical organization
17:34 Mr_N it has no init.sls and I wouldn't expect it to register and thus cause a naming conflict, but... ???
17:34 viq Mr_N: you could move users.sls to users/init.sls
17:34 viq It would remove ambiguity, you could still refer to as 'users', and would be able to call things like 'users.root'
17:35 Mr_N Indeed.  That seems way more sane.
17:35 Mr_N I'm still rather new to salt; and I've been battling on how I want to structure my state/pillar tree
17:35 ravibhure1 joined #salt
17:35 Mr_N and as such have been half and half between using <explicitename>.sls versus <explicitename>/init.sls
17:36 viq Mr_N: I'm using both depending on complexity ;)
17:36 Mr_N (can come up with "reasonable justifications" for both, and haven't built up an intuition as to where one is better yet)
17:36 Mr_N Heh; good to know I'm not _too_ far off then XD
17:37 viq If it's a single simple file then I see no need to make a folder just for a couple of lines. If it's a larger thing, splitting it into multiple files makes sense (or it has supporting files), and for that you need a dir
17:37 Mr_N Sure.  I guess what makes me hesitate is that MANY of peoples's githubbed state trees utilize the init.sls model ubiquitously
17:37 Mr_N so part of me is like, "am I comitting some style faux pas"
17:38 viq Mr_N: salt is too new to have best practices yet
17:38 ch0pstick joined #salt
17:38 Mr_N My main issue is that salt has SO MANY WAYS to solve any given problem
17:38 viq Aye
17:39 viq https://github.com/viq/cm-lab-salt/tree/master/salt/roots/salt - my example scenario I was testing things with. Here you see both ;)
17:40 Ryan_Lane joined #salt
17:40 Mr_N Hmm... I have something _very_ similar, but it's still not behaving quite right
17:40 Mr_N I think we may have even modeled our user sls off of the same example, though XD
17:40 Mr_N (the {{ user}}_key.pub section is quite familiar :P)
17:40 viq UtahDave's ? ;)
17:40 Mr_N Yep!
17:41 robawt joined #salt
17:41 viq Though mine's a merge of some ideas from other places too
17:41 Mr_N Yeah, I'm just not getting that final level of user exansion for some reason or another... It registers that I'm trying to include a state called users.root
17:41 Mr_N but then when I try to expand that through a pillar.get it returns nil
17:41 viq As I'm making a bit more complicated thing of "I want host1 and host2 to have groupA and groupB, and host3 to have groupB and groupC"
17:42 mgw joined #salt
17:42 Mr_N My pipe dream is to basically have a "users" folder, and you essentially get pillar variable level control over what of those users gets pushed to a given host.
17:42 Mr_N Mostly in order to create a clean point of contact between salt and kickstart.
17:43 Mr_N rather; between salt and our user lifecycle management workflow.
17:43 Mr_N (in that it's very easy to programmatically create and retire users, and individually set role variables that determine what machines they get pushed to.)
17:43 ravibhure joined #salt
17:43 Mr_N Which is why I'm trying to get this "flatten folder of users into a "users" pillar" functionality.
17:44 scoates is there a reasonable way to do something like "next time {{mininionname}} connects to master, ask it to highstate" ?
17:44 ravibhure left #salt
17:44 Saint-N joined #salt
17:44 MTecknology joined #salt
17:44 nebuchadnezzar joined #salt
17:44 teskew joined #salt
17:44 budrose joined #salt
17:44 frasergraham joined #salt
17:44 tyler-baker joined #salt
17:44 mpanetta joined #salt
17:44 jeremyBass1 joined #salt
17:44 juicer2 joined #salt
17:44 R_Shackleford joined #salt
17:44 CeBe joined #salt
17:44 alienresidents joined #salt
17:44 jaimed joined #salt
17:44 brianhicks joined #salt
17:44 monokrome joined #salt
17:44 ewong_ joined #salt
17:44 dren_ joined #salt
17:44 justBob joined #salt
17:44 xmltok joined #salt
17:44 Teknix joined #salt
17:44 jcockhren joined #salt
17:44 rhand joined #salt
17:44 twiedenbein joined #salt
17:44 zloidemon joined #salt
17:44 Topic for #salt is now Welcome to #salt | Thanks to everyone who made SaltConf 2014 amazing! | 0.17.5 is the latest | Please be patient when asking questions as we are volunteers and may not have immediate answers | Channel logs are available at http://irclog.perlgeek.de/salt/
17:44 viq Mr_N: if you can show what you have I could try and spot what's causing issues
17:44 Mr_N cron it on the minion scoates? ><
17:44 viq scoates: "next time"? or could it be "Every time" ?
17:44 Mr_N viq: Sure.  I can pastebin the relevent parts.  It's all rather compact and proof-of-concepty, right now, so that makes it easy.
17:45 viq scoates: either way, reactor system
17:45 scoates I only want "next time". I have machines that aren't always online, and it's a pain to get stuff synced.
17:45 scoates viq: oh yeah? cool. I'll read up on that… it's been on my "stuff I should know about" list for a while.
17:46 Mr_N ... I've been hacking on salt for like, 2 months now, and haven't had time to dive into reactors yet.
17:46 viq scoates: I still didn't get around to it, but I read a bit about that
17:46 Mr_N Goddamnit, every time I think I've wrapped my mind aroud all that this system can do ><
17:47 viq Mr_N: it evolves so fast that even if you knew _everything_ about it today it wouldn't be everything a week from now :P
17:47 ch0psti57 joined #salt
17:48 neilf_ joined #salt
17:49 eculver joined #salt
17:49 Mr_N Oh interesting... viq in pastebinning this to you, I found some behavior I hadn't noticed before.
17:49 Mr_N I'll make a note of it and link you.
17:50 hillna joined #salt
17:50 scoates viq: thanks
17:50 viq cool
17:52 schimmy joined #salt
17:53 Ryan_Lane joined #salt
17:53 Mr_N Here we go.  http://pastebin.com/zPzcN9tB
17:53 Mr_N The relevent parts should all be there.
17:54 Mr_N I'm clearly doing something wrong in how I do nested pillar stuff in that it's not resolving properly when the include isn't at the top level
17:54 Mr_N but IDFK
17:58 MTecknol1gy joined #salt
17:58 xmltok_ joined #salt
17:58 smcquay joined #salt
17:59 jnials joined #salt
18:00 jnials_laptop joined #salt
18:01 viq Mr_N: I don't believe that's the proper syntax for include
18:01 jnials joined #salt
18:02 viq try - include
18:03 Mr_N The behavior is in fact, identical :P  (as far as I can tell)
18:03 viq OK, i think include needs to be top level, not as a sub-key of users
18:04 Mr_N It works in that fasion
18:04 Mr_N But that's rather obnoxious.
18:04 nobody_314 joined #salt
18:04 viq oh?
18:04 Mr_N since then I don't get good hierarchy
18:04 gammalget joined #salt
18:04 thayne joined #salt
18:04 Mr_N as I said, when I remove the users: above include, it works appropriately
18:05 Mr_N but then I believe it basically just dumps the root pillar right at the bottom.
18:05 zain joined #salt
18:05 Mr_N Yeah; I just have a top level pillar variable of "root:"
18:05 Mr_N rather than users.root
18:06 Mr_N (when I do pillar.items)
18:06 viq yeah
18:06 Mr_N That's why initially I was trying to do it without an include, to have users: root:
18:06 Mr_N but then I don't get the root state either.
18:06 Mr_N rather; users: -root
18:07 nineteeneightd joined #salt
18:08 joehillen joined #salt
18:08 viq Mr_N: my take on this: https://github.com/viq/cm-lab-salt/tree/master/salt/roots/pillar/users
18:08 Mr_N Yeah, I saw
18:08 Mr_N you do user groups
18:08 Mr_N I had just really been trying to avoid putting all my users in a single file.
18:08 viq But yeah, pillar includes are right now a bit tricky/ugly
18:08 Mr_N since that makes my job _way_ harder in a lot of other ways
18:08 Vivi-Idle joined #salt
18:09 Mr_N What confuses me is that salt has ways to deal with this
18:09 Mr_N vi cp.list_master
18:09 Mr_N via*
18:09 Mr_N I have no idea why pillar can't offer similar functionality.
18:09 Mr_N Some of the design choices do seem a bit "all over the place"
18:09 viq http://docs.saltstack.com/ref/pillar/all/salt.pillar.pillar_ldap.html  ?
18:10 Mr_N Hmm.
18:10 Mr_N I must admit the documentation on that command is a wee bit lacking
18:12 Mr_N It lets you merge a given config file with a given pillar...
18:12 Mr_N Guess I need to play around with it a bit
18:12 Mr_N thanks for the tip
18:13 jacksontj_ joined #salt
18:14 Iwirada left #salt
18:15 Mr_N (FWIW; this functionality I'm "aiming for", I already have a working version implemented completely within states; but it relies on an absolute mess of template code, and I'd rather just rely on pillar since it seems more "appropriate")
18:15 Mr_N I guess that's why I'm surprised that making it work in pillar has ended up being a bit harder.
18:15 viq yeah
18:16 viq Mr_N: also have a look at reclass as another option
18:16 Ryan_Lane joined #salt
18:16 Mr_N I have some magical salt code that automatically looks for states matching some various grain variables and syncs them as requested if they exist (regardless of depth away from the salt file_root)
18:16 Mr_N but it is _ugly_
18:17 Mr_N (I need to learn about what reclass _is_ beforehand XD)
18:17 viq haha
18:17 Mr_N (so much to learn, so little time...)
18:18 CaptTofu is there anyone here using salt-cloud with: 1. hpcs ae1 2. stock devstack ?
18:18 arnoldB can I force Salt to restart a service instead of reloading it?
18:18 CaptTofu s/devstack/openstack\/devstack/
18:19 arnoldB CaptTofu: opennebula here
18:19 arnoldB without salt-cloud (sorry)
18:19 CaptTofu arnoldB: sure.
18:19 viq arnoldB: IIRC reload: false
18:20 Mr_N Thanks for all the pointers viq, I'll be attacking this again after lunch :)
18:20 arnoldB viq: I've already tried it. reload: False is AFAIR default
18:20 forrest arnoldB, service.running supports kwargs, so you could try passing something through like - restart: True
18:20 srage joined #salt
18:21 mgw joined #salt
18:23 arnoldB service hasn't a status command. had to define a sig to look for in process list. thank you anyway :)
18:24 jcsp joined #salt
18:25 iben joined #salt
18:26 iben Hello Salt gurus!  Is anyone around from the Austin Texas area? #ATX? we have a contract position open there in the area.
18:26 synfin joined #salt
18:36 jeffro joined #salt
18:38 arnoldB a state.highstate needs ~ 10 minutes to execute. can I tell the salt CLI tool to do the job in the background without appending a &?
18:39 forrest arnoldB, are you setting the timeout?
18:39 oz_akan joined #salt
18:39 arnoldB forrest: yes
18:40 forrest arnoldB, have you tried setting it really low? Like 2 seconds?
18:40 viq arnoldB: --async
18:40 arnoldB viq: great"
18:40 akoumjian joined #salt
18:40 arnoldB !
18:40 forrest viq, duh! Nice catch.
18:40 viq :P
18:41 ml_1 joined #salt
18:41 Kraln- joined #salt
18:42 synfin_ joined #salt
18:42 Linz joined #salt
18:43 HeadAIX joined #salt
18:45 nobody_314 joined #salt
18:45 nineteeneightd joined #salt
18:46 Vivi-Idle joined #salt
18:46 octarine joined #salt
18:46 basepi joined #salt
18:51 austin987 joined #salt
18:52 psyl0n joined #salt
18:53 iben Do any of you take contract jobs to help companies get started with salt? CentOS 6.5 64 bit shop.
18:54 kolaman joined #salt
18:54 Corey iben: Sure, many of us are consultants in that space.
18:55 Corey I must say though, you're probably the first person who's asked here. :-)
18:55 forrest Corey, actually a few people have asked about jerbs in here
18:56 Corey forrest: Sure, but I've seen the "hire me for Salt work" type, not "can I hire anyone here to work on Salt projects."
18:56 forrest Corey, were you able to get one of the puppet shirts?
18:56 Corey Sadly no.
18:56 forrest Corey, ahh, yea that is fair.
18:56 forrest lame
18:56 Corey The Puppet booth was surprisingly reluctant to engage anyone in conversation.
18:56 forrest I am sad
18:56 forrest from Salt? Or just in general?
18:56 Corey ANYONE!
18:56 forrest that's weird
18:56 forrest why?
18:56 Corey I was wearing nothing that looked even vaguely Salt-like!
18:56 forrest they're usually nice guys when I've met them before
18:56 forrest yea I saw your stupid suit picture
18:56 forrest too many suits :P
18:56 ajw0100 joined #salt
18:57 Corey It's about all I wear during the wee.
18:57 forrest man, you're lucky to find me in a button up
18:57 iben Corey - are the salt guys here too busy to work contracts?
18:57 Corey iben: Hardly; in fact, that's kinda what Saltstack (the company) does.
18:57 iben i was told there might be some interest in contract work from you guys.
18:58 Corey iben: Taking a step back for a second, what're you trying to do?
18:58 iben well - we're looking for a full time 3 months person
18:58 oz_akan joined #salt
18:58 iben hopefully also more than just salt - flume, elastic search, splunk, mysql
18:58 iben salt is just a means to an end - right?
18:58 iben it's a way to get things done
18:59 Corey iben: Just so. :-)
18:59 nineteeneightd joined #salt
18:59 forrest iben, some of the guys in here take contracts, just have to find them, sometimes they're pretty busy so they won't respond.
18:59 hunter_ joined #salt
19:00 MTecknol1gy I'd consider it, but I wouldn't be on-site and I wouldn't quit my current job for it.
19:00 iben so - we could do a remote work deal
19:01 Corey Not for nothing, but my employer kinda specializes in dropping people into places for short periods of time. It's kinda how I spend my weeks. :-)
19:01 Corey <-- traveling consultant
19:01 iben short = ?
19:01 iben weeks? months?
19:02 Corey It varies, but "yes."
19:02 danielbachhuber joined #salt
19:02 Corey I believe our typical projects run anywhere between 1-8 months, it really just depends.
19:02 nineteeneightd joined #salt
19:02 srage joined #salt
19:02 jcsp left #salt
19:02 ravibhure1 joined #salt
19:02 jcsp joined #salt
19:04 iben i see - you work for salt?
19:05 Corey No, no.
19:05 Corey They have hiring standards there. ;-)
19:05 forrest lol
19:05 iben i was hoping to go direct with someone who was independent.
19:05 Corey I'm just a mouthy community member.
19:05 iben 3 month contract to help with centos setup, operation, and log collection. Familiar with Saltstack, MySQL, Flume, Splunk, Logstash. email me: salt@ibenit.com
19:05 iben you say "our" - so who are "we"?
19:05 Corey Hey, I've contributed to two of those projects! :-)
19:05 Corey <-- Taos
19:06 iben ahh - of course.  cool.
19:06 forrest COREY, THE ALMIGHTY TAOS, MASTER OF THE LLAMAS, WEARER OF SUITS AT IT CONFERENCES.
19:07 Corey forrest: I also collect whisky. DOn't forget the important bits.
19:07 iben alright guys - I'll check back in here later to see if there are any more bodies available.  If you know anyone looking for work let me know.  Thanks!
19:07 psyl0n joined #salt
19:07 * scoates pops champagne and stuff
19:08 whiskybar joined #salt
19:09 troyready joined #salt
19:09 VONION joined #salt
19:12 christopherl joined #salt
19:13 vlcn_ https://gist.github.com/kelchm/bfb16b2863cd7c1ec54d
19:13 vlcn_ this doesn't seem to be working how I would have exected
19:13 ipalreadytaken joined #salt
19:13 vlcn_ IE, /usr/local/solusvm/data/solusvm.conf does exist but the script gets executed anyway
19:13 vlcn_ any ideas?
19:14 mohamed_ joined #salt
19:14 forrest vlcn_, give it a shot with -l debug and see if that returns anything more.
19:14 dave_den vlcn_: - creates is new in 2014.1. it will not work (but won't give an error) in 0.17
19:15 vlcn_ agh, that explains it dave_den!
19:15 dave_den you need to use unless:  in 0.17
19:16 forrest dave_den, are you gonna file the versionadd issue or should I?
19:17 renoirb Hey guys, I have a question about nvm and state.npm module
19:17 dave_den if there;s not one then yeah, hit it forrest.
19:17 Nazzy joined #salt
19:17 dave_den didn't check
19:17 renoirb How could I use nvm and npm.installed in my states
19:17 forrest renoirb, do you mean npm? Not nvm?
19:18 forrest there is an npm state
19:18 Nazzy forrest, you don't happen to know what the sfn param for file.manage_file is supposed to be?
19:19 christopherl joined #salt
19:19 forrest dave_den, looks like someone added it, but it doesn't show that in the example.
19:19 renoirb forrest, i really meant nvm.
19:20 kainswor joined #salt
19:20 Nazzy forrest, it looks like it's supposed to be the source file name in the local cache, but it's completely absent from the example
19:20 forrest Nazzy, maybe the short filename?
19:20 MTecknol1gy iben: actually... I'm just catching up, but I would highly recommend taos; a little spendier than their competition, but experts of all things anything.
19:20 forrest incase it's on winderp
19:21 forrest Nazzy, but I'm not sure
19:21 dave_den renoirb: i don't think there is nvm support in the npm module
19:22 Nazzy forrest, oooh, yeah, it's the local cache'd name: sfn = __salt__['cp.cache_file'](source, saltenv)
19:22 iben I've used them in the past - thanks for the recommendation.
19:22 forrest Nazzy, gotcha
19:22 Nazzy that needs fixing in the docs
19:22 renoirb yeah, that's what I was thinking. It would be then better for me to stick to import a pkgrepo.managed instaed.
19:22 renoirb thanks dave_den, forrest.
19:22 Nazzy bleh, brb
19:23 forrest renoirb, you should write it :P
19:23 renoirb hahaha
19:23 renoirb I have a few things to write before that one
19:23 renoirb In my queue, salt recipes for: OpenSSL certificates management, Piwik,  MediaWiki
19:24 forrest get to it!
19:24 renoirb forrest: ^
19:24 dave_den renoirb: i wrote the environ modules that will allow you do change your environment variables to act as a shim for node versions.  they aren't in 2014.1 but you could manually add them
19:24 forrest Nazzy, I'm creating an issue now to have that notated.
19:24 renoirb oh, that's clever dave_den
19:24 renoirb BTW, forrest, dave_den, i'm going to meet up with redbeard2 at Montreal PyCon
19:25 forrest renoirb, I will be there as well.
19:25 renoirb cool!
19:25 forrest dropping some cash to fly to pycon this year that's for sure
19:25 SEJeff_work joined #salt
19:25 renoirb I'm learning python because of you guys.
19:25 forrest sweet!
19:25 forrest renoirb, do you live in Montreal?
19:26 renoirb yup
19:26 forrest Nice
19:27 dave_den renoirb: speaking of, tom just merged them 2 minutes ago.  https://github.com/saltstack/salt/pull/10653/files
19:27 DanGarthwaite joined #salt
19:27 DanGarthwaite Congratulations!
19:27 DanGarthwaite We can update the IRC banner.
19:27 forrest for 2014?
19:27 forrest .1
19:28 timoguin joined #salt
19:28 renoirb yaay!
19:28 forrest renoirb, are you staying at the hotel for the conference? I'm still trying to find someone to split the room cost with
19:29 DanGarthwaite I just got an email announcing it.
19:30 forrest on the mailing list DanGarthwaite?
19:30 DanGarthwaite salt-announce
19:30 forrest oh yea I'm not on that one
19:30 renoirb are you from Salt Lake City too forrest ?
19:30 psyl0n joined #salt
19:30 forrest renoirb, no I live in Arizona
19:32 bt joined #salt
19:32 valgrind joined #salt
19:32 bt joined #salt
19:33 forrest back in a bit
19:34 carlos_ joined #salt
19:36 Saint-N joined #salt
19:36 pmcg joined #salt
19:38 cym3try joined #salt
19:38 abe_music joined #salt
19:38 ml_1 joined #salt
19:41 dstanek_afk joined #salt
19:43 christopherl joined #salt
19:43 cheus__ Howdy. Does anyone have a best-practice recommendation for setting up recurring events in a multi-master (ha) scenario? Cron on one node isn't HA and cron on two could cause the same events to fire. I'd usually use a rabbitmq work queue for this but hoping something's baked in.
19:46 oz_akan joined #salt
19:46 n8n joined #salt
19:47 oz_akan joined #salt
19:48 schimmy1 joined #salt
19:48 yano joined #salt
19:49 forrest joined #salt
19:53 R_Shackleford joined #salt
19:54 nextdoorwarren joined #salt
19:56 kermit joined #salt
19:56 kermit joined #salt
19:57 n8n joined #salt
19:58 Katafalkas joined #salt
20:01 Ahlee cheus__: salt's scheduling isn't flexible.  I use a third party utility to schedule runs through the master
20:02 yano joined #salt
20:03 ipalread_ joined #salt
20:03 ipalread_ joined #salt
20:05 ajw0100 joined #salt
20:06 bhosmer joined #salt
20:09 cheus__ Ahlee, Thanks. Wasn't certain if I was missing something.
20:13 Ahlee cheus__: Yeah, so far all attempts at discussing fleshing out scheduling gets met with 'lol use cron'
20:13 Ahlee well
20:13 Ahlee fleshing out in the community, the devs see the need
20:14 ndrei joined #salt
20:14 budrose joined #salt
20:15 dstanek_afk joined #salt
20:15 cheus__ Ahlee, indeed, Can't exactly schedule say a cluster-wide apt-get dist-upgrade with cron on every master node and putting it on minions could cause waay too many to fire at once. Salt has such an awesome batch system it's a shame it can't be used for scheduled management like that
20:15 rallytime joined #salt
20:21 Ahlee i played with marrying salt with celery's scheduling, my python wasn't up to it
20:21 Rasathus joined #salt
20:21 brianhicks left #salt
20:23 Rasathus Has anyone got a moment for a question about Salts architecture, and how some functionality would be achieved ?
20:23 Rasathus Im only just starting out, so its probably easy enough
20:23 jcockhren Ahlee: I use ironMQ and ironWrokers to call salt-api
20:24 jcockhren you can schedule workers
20:24 cheus__ Ahlee, We might yet do that here; the only thing keeping me from committing to it is how it adds another set of moving parts that could fail. In my theoretical solution we'd use a rabbitmq cluster to fire salt events to the reactor.
20:24 zooz joined #salt
20:24 cheus__ ^^ Like jcockhren's implementation with ironmq
20:24 Rasathus Ive been reading through the various getting started guides, and had a few questions about how grain information could be dynamically gathered.
20:25 Rasathus I wanted to make the version number of a few applications available as parameters for selection, and node grouping
20:26 Rasathus I started to look at pillars, but this seemed to serve up key value data based on checks upon grains.
20:26 Rasathus How would I architect something more dynamic ?
20:27 Ahlee yeah, i already have a celery decorator for manipulating salt, i just haven't pulled hte trigger as I do'nt want to add rabbitmq thus erlang into hte environment
20:27 dave_den Rasathus: pillar data is data that the master tells the minions - it can be dynamic based on grains, but it can also be as simple as defining static data.
20:28 Rasathus is there an equivalent for data provided by the minions ?
20:28 dave_den Rasathus: grains are information about the minion that don't really change
20:28 renoirb forrest: i'm not staying at the hotel.
20:28 Rasathus or would i have to use remote calls from the master to gather the data from the pillar ?
20:28 renoirb forrest: I'm living at ~30min with public transit from the conference site. My previous company had an office at walking distance to the Palais des Congrès
20:29 Ahlee I think the worst thing salt did was allow grains to get set with setval.
20:29 Ahlee It's really muddied the waters.
20:29 dave_den Rasathus: can you explain a bit more about exaclty what you are trying to achieve? i might be able to suggest the easiest way once i understand exactly what you need.
20:30 jcockhren fwiw Ahlee, cheus__: I think if there was a simple way to introduce a delay between sending minions their jobs, it'll cover the use case
20:31 faldridge joined #salt
20:31 Ahlee jcockhren: you mean delay on the secondary since salt prevents two states from executing at once, and just allowing the slower to fail?
20:31 Gifflen_ joined #salt
20:32 srage joined #salt
20:32 Rasathus We have some jboss applications that run on various machines.  I would like the version numbers of these applications to be available to salt to allow us to target nodes based on that information.  So that we could upgrade them, or push out certain configuration files etc.
20:32 jcockhren Ahlee: yeah something like that
20:33 chrisjones joined #salt
20:33 jcockhren I may be oversimplifying it all, but... I don't think salt should really turn into a MQ+worker thingy
20:33 jcockhren maybe, have the two master communicate via the peer system
20:33 Ahlee jcockhren: I agree, but salt also needs real scheduling
20:34 Ahlee not "run this 5 minutes past whenever i started"
20:34 forrest renoirb, oh nice
20:34 Ahlee to combine celery and salt is trivial, to yank celery's scheduling out of celery and bolt it into salt is tough
20:35 Ahlee all i mean is all the trickery around edge cases when it comes to scheduling
20:35 Ahlee for now I'll continue to use and be upset with the third party utility we use for scheduling other tasks
20:36 ndrei joined #salt
20:36 dave_den Rasathus: it would make more sense to have your master tell the minions which versions they should have installed, that way you already know that infromation
20:37 Gifflen joined #salt
20:37 ndrei joined #salt
20:37 dave_den Rasathus: but if you wanted to do it the other way around then yes, you could have the minion set a grain with the version number
20:38 dave_den Rasathus: you can use http://docs.saltstack.com/ref/modules/all/salt.modules.grains.html#salt.modules.grains.setval to set a grain
20:38 Nazzy I should really open a issue for this "flaw", but I'm not really sure how it could be fixed :/
20:38 jcockhren Ahlee: what if the salt state system could use an external MQ as a backend?
20:38 dave_den Rasathus: and you can use the state module to set a grain from a state file: http://docs.saltstack.com/ref/states/all/salt.states.grains.html#salt.states.grains.present
20:39 Rasathus dave_den: ok thanks, Im probably still thinking about the problem the wrong way around.
20:39 Ahlee jcockhren: hrm. And then make it up to the chosen message queue or some other task to insert timing notifications into the state?
20:40 Rasathus dave_den: That might be more along the lines of what I was thinking
20:40 Rasathus dave_den: Thank you for your help.  I'll do some more reading.
20:41 dave_den Rasathus: ideally the master knows everything and tells the minions what they should do
20:41 ndrei joined #salt
20:42 Rasathus dave_den: Yep.  I was just rather confused about grains being static data.
20:42 dave_den the state files are templates (jinja by default) which can contain logic conditions that will help the minion know what to do as well
20:42 jcockhren Ahlee: basically, I'm thinking having a MQ as a shared resource for stste execution for the multi master setup
20:42 Rasathus dave_den: yeah, so it can include basic logic, but not go off and run a version command
20:43 Nazzy description of flaw: it seems that every state that is called gets a copy of the state chunks, thus every call triggers a deep copy of the chunks dict... this is geometric scaling and very bad
20:43 Ahlee jcockhren: it's an interesting thought
20:43 dave_den Rasathus: well, the nice thing is that you have access to some special dicts within your template files. the 'salt' dict actually gives you access to every single execution module loaded into the minion.
20:43 ndrei joined #salt
20:44 Rasathus dave_den: ahh ok.  That makes a bit more sense
20:44 Networkn3rd joined #salt
20:45 Rasathus dave_den: I've been evaluating mesos and looking at making our infrastructure more dynamic.  As such I was expecting that a minions role might change, so the roles listed for it might be appended to or removed.
20:46 Rasathus dave_den: so I suppose my confusion was around just how 'static' the grain data is intended to be.
20:46 Nazzy I'll figure out how to open an issue for that in a bit *sigh*
20:47 Rasathus dave_den: but it sounds like I need to go and read up on the 'salt' dict.  Once again, thank you very much for your help
20:47 jcockhren https://github.com/saltstack/salt/issues/5946
20:47 jcockhren Ahlee, Nazzy ^
20:47 dave_den Rasathus: you're welcome. good luck and ask any questions here. someone is usually able to help
20:48 dave_den or the salt-users mailing list
20:49 jcockhren OH
20:49 jcockhren can states use returners?
20:50 Ahlee jcockhren: heh, yeah, my issuee is the linked 8122
20:50 Ahlee man, 4 months already.
20:52 n8n joined #salt
20:52 Mr_N dave: so, funny thing, talking about static grains vs dynamic pillar
20:53 nextdoorwarren joined #salt
20:53 Mr_N It seems that pillar is being a bit more difficult to actually implement dynamic content than shoving it in core states
20:53 schimmy joined #salt
20:54 dave_den well, it's not that pillar is dynamic. in fact, if you're only using file based pillars then it is hardly dynamic
20:55 Mr_N Indeed, that's the problem I found.
20:55 christopherl joined #salt
20:55 Mr_N That raw states are rather "ok" at being able to dynamically detect each others's existence
20:56 Mr_N but doing pillar stuff without going into like, pure python, i've yet to find a way to properly include other hierarchical pillars the way I want, or do any sort of autodetection.
20:57 Mr_N (better put, I've not found an equivilent functionality to the cp list_master module you showed me; but for pillars instead)
20:57 hunter_ joined #salt
20:58 Mr_N Also, I'm totally butchering the intended usage I'm sure; but I found that it's quite easy to use states to maintain a minions own grain file dynamically.
20:59 cewood joined #salt
20:59 hunter_ joined #salt
21:01 Gifflen joined #salt
21:01 Gifflen joined #salt
21:01 ipalreadytaken joined #salt
21:02 dave_den Mr_N: yeah, i am not sure i would try to force the file based pillar to do that.
21:02 Topic for #salt is now Welcome to #salt | Thanks to everyone who made SaltConf 2014 amazing! | 2014.1.0 is the latest | Please be patient when asking questions as we are volunteers and may not have immediate answers | Channel logs are available at http://irclog.perlgeek.de/salt/
21:02 dave_den i would use reclass or custom ext_pillar
21:02 Mr_N I'm looking at what ReClass offers right now
21:02 Mr_N yeah :P
21:02 Mr_N I explored the grains/pillar/pure state based solutions to try and get understandings for the "many ways I can solve this problem"
21:04 zain joined #salt
21:06 jbub joined #salt
21:07 Ryan_Lane joined #salt
21:08 thayne joined #salt
21:08 Mr_N There's a bit of chicken and egg problem where I'm deploying this, in that it has to dovetail with pieces of existing infrastructure lest I try and reinvent it all in one go (hah.)
21:08 Mr_N and the existing infrastructure is often not a solution that elegently fits well
21:09 ipalreadytaken joined #salt
21:09 Rasathus Mr_N: That sounds like a rather similair problem to the one im trying to understand at the moment.
21:09 rojem joined #salt
21:09 Rasathus Mr_N: we've got some rather awkward legacy decisions to try and work around
21:09 Mr_N Rasathus: If it's anything similar to mine, yeah, I could believe it, it seems like a common "use case" for which there are many many solutions given how broad salt is.
21:10 dwiden joined #salt
21:10 Mr_N In our environment it's mostly a deployment system almost entirely consisting of an ANCIENT kickstart/pxe system + two terribly maintained and distinct dhcp/DNS setups
21:10 Rasathus Mr_N: I've done a bit of evaluation with Puppet, Chef and Salt so far.  I Really like salt, but im finding it harder to understand its structure through all its flexibility.
21:11 dwiden I'm trying to install a python package using the pip.installed state, but I get the error: "state pip.installed found in pythondependencies.sls is not available."  However, when I run the python shell, I can successfully perform "import pip"
21:11 Rasathus Mr_N: Im still trying to understand the intended way of implementing some of the things I forsee us having to do
21:11 Mr_N I looked at puppet chef ansible and salt.  Found this one to be BY FAR the easiest to use/set up and most intuitive
21:11 Mr_N Oh yeah, don't worry, I'm in your same shoes.
21:11 Mr_N So so so many ways to potentially solve any problem, and no real "best practices" at this point.
21:12 dave_den dwiden: what's your path to pip?
21:12 hunter_ first pillar template isn't going well
21:12 dwiden I'm using ActivePython, give me a second let me check (also using a windows minion)
21:12 dave_den dwiden: the PATH environment of the salt-minion may not be the same as your shell
21:13 Rasathus Mr_N: well good luck with the research.
21:13 Mr_N You too.  IMHO salt is a great choice :)
21:14 dwiden dave_den: My pip is located in C:\Python27\Scripts\pip
21:14 Mr_N what sort of problem are you currently exploring, if I may pick your brain just to get a glimpse into some other environment? :P
21:15 dave_den dwiden: run this to see your minion's path:   salt-call cmd.run 'echo $PATH'
21:15 mgw joined #salt
21:16 schimmy joined #salt
21:16 nextdoorwarren joined #salt
21:17 dwiden dave_den: I should run that on my salt-minion?  It fails with the following error: specified kwd '$PATH' is not absolute or does not exist
21:19 dave_den dwiden: did you use the single quotes?  also, try:   salt-call pip.version
21:19 hunter I'm trying to templatize my first sls state.
21:19 dave_den need to determine if it's your pip executable that is not found or the pip lib
21:19 hunter I'm following http://docs.saltstack.com/topics/tutorials/pillar.html but instead of users I'm attempting this with yum repos.
21:19 dwiden dave_den: just to make sure, this should work on a windows minion, right?
21:20 hunter My pillar data is:  http://pastebin.com/ANjjE7x1
21:20 hunter but pillar.items says "[ERROR   ] Got a bad pillar from master, type str, expecting dict:"
21:21 hunter Do I need dashes at the head of the yaml elements?
21:21 dave_den dwiden: yes, i think. i don't use windows myself
21:22 terminalmage hunter: is that top line in your file?
21:22 dave_den hunter: what does your pillar top.sls look like
21:23 terminalmage the "pillar/dev/yum.sls"
21:23 dwiden okay, when I ran: salt-call pip.version, I get the following output: <-[0;36mlocal]<-[0m: and then the line beneath it is indented, with the following text <-[0;32m1.4.1<-[0m
21:23 hunter terminalmage: no, that was just me saying what file the following lines were from.
21:23 terminalmage ok... the rest of it looks like a valid dict
21:24 mlen left #salt
21:24 dave_den dwiden: sorry, i forgot to ask: are you seeing the 'pip not found in state' when you execute a call from the master?
21:24 hunter dave_den found it - I was looking at hte data file and I'm missing a line in the top.sls
21:24 hunter Damnit,
21:24 terminalmage oh
21:24 dave_den doh
21:25 krow joined #salt
21:25 gfa_ can i use file.mkdir in a reactor formula?
21:25 hunter damn
21:25 hunter And now it works.
21:26 hunter well, the uber simple version does. I need something more complicated.
21:26 hunter So I need to take that pillar data file I posted and have more fields than just the description for each repo. Each one will have a sane default, but I need to be able to override the defaults in the pillar data.
21:27 hunter How do I do that? None of the examples in the pillar docs show anything but one ... item per pillar nuggest.
21:27 hunter (user: userid) and whatnot.
21:27 dave_den hunter: it just needs to be valid yaml
21:27 fragamus joined #salt
21:27 whiteinge gfa_: no. you don't have access to {{ salt }} in reactor sls files
21:28 hunter ok. Let me work up what I think it should be
21:28 gfa_ whiteinge: what do i have access? docs are not very clear
21:28 dwiden dave_den: yes, when I execute the master, I get the following output: ...Comment: State pip.installed found in sls pythondependencies is not available
21:28 whiteinge only {{ data }}
21:28 gfa_ i don't get it, sorry
21:29 dave_den dwiden: ok, can you instead do:  salt 'yourminion' pip.version
21:29 zain joined #salt
21:30 dwiden dave_den: the result is: command required for 'pip.version' not found: Could not find a 'pip' binary
21:30 juice- joined #salt
21:30 thayne Hey, jphall, look over here!
21:31 dave_den dwiden: that means the salt-minion cannot see your pip install.  run:   salt 'yourminion' 'echo $PATH'
21:32 dwiden salt '*' cmd.run 'echo $PATH' yields 'dev-1: $PATH'
21:32 bhosmer joined #salt
21:33 conan_the_destro joined #salt
21:33 hunter Can you have an empty dict - for an entry that I want to _exist_ but all its fields/keys are defaulted?
21:33 dave_den man, i haven't used windows since 2003… is it %PATH% ?
21:33 whiteinge gfa_: the only jinja variable in that context is the event data. have you run the eventlisten.py script before and seen that?
21:34 dwiden dave_den: good idea, that worked.  The output is...
21:34 conan_the_destro hello, I am running 0.17.5 on freebsd and I am gettign the following error: http://pastebin.com/nEVYyxnA
21:34 dwiden dave_den: C:\salt\salt-0.17.2.win-amd64; C:\Windows\System32; C:\Windows; C:\Windows\System32\Wbem; C:\Windows\System32\WindowsPowerShell\v1.0\
21:35 dave_den dwiden: you will need to add C:\Python-2.7 (or whatever it was that had pip.exe in it) to your path for salt-minion
21:36 dwiden dave_den: I'm guessing there is something in the minion configuration that I can add it to?
21:36 analogbyte is there a simple way to convert a jid back to a timestamp? I guess its some python builtin generating the jids, so it should be easy to reverse the process?
21:36 hunter I'm totally lost writing this.
21:36 gfa_ whiteinge: i'm running eventlisten.py in the next console. how can i use the data as parameter to cmd.cmd.run ?
21:36 dave_den i don;t think so. i think you have to open up the properties of the salt-minion exe and configure an extra path… but honestly it has been 11 years since i've used windows so i don't know for sure
21:37 rojem joined #salt
21:37 dwiden dave_den: okay cool, thank you for the help!
21:38 analogbyte found it:     return '{0:%Y%m%d%H%M%S%f}'.format(datetime.datetime.now())
21:39 juice- joined #salt
21:39 dave_den '{0:%Y%m%d%H%M%S%f}'.format(datetime.datetime.now())
21:39 dave_den herp
21:39 dave_den yep
21:39 gfa_ i launch the event like this salt-call event.fire_master '{"hostname": "monotono"}' 'newbackup'. but it fails to render this, in the formula, cp /var/cache/salt/master/minions/{{ data['hostname'] }}/files/root/.ssh/id_backup.pub /var/www/salt/minion/{{ data['hostname'] }}/id_backup.pub
21:39 ipalreadytaken joined #salt
21:40 hunter http://pastebin.com/78y2wmQD
21:40 hunter Thats a rough idea of what I'm attemping.
21:41 jrdx joined #salt
21:41 analogbyte dave_den: thanks ;)
21:42 dave_den hunter: try something like this: http://pastebin.com/Fs99CyA5
21:42 whiteinge gfa_: for custom events you want {{ data['data']['hostname'] }}
21:42 dave_den hunter: although if you don't have all of the args defined for every repo, that will blow up
21:43 hunter Yes - whats the best way to do defaults? 99% of the time, the defaults will be fine.
21:43 jergerber joined #salt
21:44 hunter dave_den: IE, I need a .... pillar.get(args.humanname, "blahblahblah) ?
21:44 dave_den args.get('humanname', 'a default string')
21:44 dave_den yaeh
21:44 hunter I was close.
21:44 dave_den or you can make a default dict in pillar and use that instead of hardcoding it in the state files
21:44 hunter Where close doesn't work and doesn't count, but I was close.
21:44 hunter oooh
21:44 hunter dave_den: what would THAT look like pray tell?
21:45 dave_den in that case you could do args.get('humanname', def_args.get('humanname', 'last_attempt'))
21:45 gfa_ whiteinge: thanks, it works, unordered but it works
21:45 gfa_ i owe you a $BEVERAGE
21:46 gfa_ can i use require: on reactor?
21:46 dave_den hunter: of course, you could leave off the 'last_attempt'
21:46 hunter Let me try that. dave_den: thank you so much.
21:46 dave_den no prob
21:47 hunter I know pillar is the right way to do this, it just isn't obvious the very first time you sit down to debug an empty file.
21:47 dave_den just take a bit of practice
21:47 dave_den takes
21:48 whiteinge gfa_: also no. reactor sls files are pretty simple. generally you should just use them to kick off an cmd.state.sls and pass {{ data }} along. then you can put the real logic in the sls file that actually gets run on the minion (since reactor sls files run on the master)
21:50 schimmy1 joined #salt
21:51 juice- joined #salt
21:52 srage joined #salt
21:58 dwiden dave_den: I modified the path environment variable on my windows minion, but I still get the same issue as before
21:59 dave_den dwiden: can you successfully run:  salt 'yourminion' pip.version ?
21:59 FarrisG joined #salt
22:00 dwiden dave_den: yeah it reports 1.4.1
22:01 dave_den dwiden: this is the library and bin path check for the pip state: https://github.com/saltstack/salt/blob/develop/salt/states/pip_state.py#L31
22:02 dave_den lines 31-50
22:03 dwiden dave_den: do you know what 'pip.list' in __salt__ means?  Its on line 48 of that file
22:04 dave_den if the salt minion can't 'import pip' and 'import pip.req', or if there is no 'pip.list' in the salt modules then it won't load.  the check for salt in the pip execution module is the salt.list line. that is here https://github.com/saltstack/salt/blob/develop/salt/modules/pip.py#L31
22:05 dave_den so i would suspect it can't find the libs, since you are able to do salt pip.version
22:06 dwiden do you know what would cause salt to not be able to find the libs?  Does the salt-minion run from a "weird" user?  I ran the python shell and manually ran import pip and import pip.req to check
22:06 dwiden (does it happen to be randomly "bad" that the username on my minion machine is salt?)
22:07 dave_den dwiden: UtahDave is the salt on windows expert. you might try asking the salt-users mailing list as well
22:07 dave_den i have no windows-fu
22:08 dave_den dwiden: https://github.com/saltstack/salt/issues/8405
22:08 thayne joined #salt
22:09 ajw0100 joined #salt
22:10 Ryan_Lane joined #salt
22:10 hunter dave_den: is there a way to have "lazy" jinja variable evaluation?
22:10 dwiden dave_den: thanks for showing me that, it doesn't look good for me I guess.  Perhaps I could ask my minion to install it manually, such as "salt '*' cmd.run 'pip install etc'
22:11 dave_den hunter: what are you wanting to do
22:11 hunter dave_den: http://pastebin.com/p6PVdje1
22:11 schimmy joined #salt
22:12 hunter I cut-n-pasted that from the original state sls file and didn't notice the variable - but if I could _have_ that variable there, it would be wonderful
22:14 hunter dave_den: I'd love for that that jinja variable /pillar var to be evaluated at state.sls time, not pillar.sls time.
22:14 hunter Does that make any sense?
22:15 dave_den well
22:15 dave_den in your state file, you'd have
22:16 dave_den repo.managed:
22:16 dave_den
22:16 csa2 joined #salt
22:17 yomilk joined #salt
22:17 dave_den {% if repo.get('baseurl') %}
22:17 dave_den {{ repo.baseurl }}
22:17 dave_den {% else %}
22:18 dave_den {{ defaults['baseurl'] }}{{ repo }}
22:18 dave_den {% endif %}
22:18 hunter So you have to attack it programmatically, not strictly thorugh templating?
22:19 dave_den well, jinja won't interpolate into variables
22:19 dave_den so if you have var: 'hello my name is {{ blah }}' in pillar, then jinja won't look at it when you do {{ var }}
22:19 millz0r joined #salt
22:20 psyl0n joined #salt
22:20 dave_den it will just be 'hi my name is {{ blah }}'
22:20 hunter I didn't know if there was a sequence like \{\{ blah \}\} (or whatever) that would allow that to pass through the pillar jinja step and then be eval'd at the state jinja step.
22:21 dave_den i suppose you could try to do #! jinja | jinja | yaml
22:21 dave_den but i have not tried that
22:26 djaykay joined #salt
22:28 mwmnj joined #salt
22:28 MTecknol1gy dave_den: this issue is making me cry and I don't have any idea what to do :(
22:28 xmj joined #salt
22:28 dave_den there's no crying in saltstack
22:29 * Heartsbane_ mumbles something about documentation.
22:29 dave_den MTecknol1gy: what's the problem
22:30 forrest Heartsbane, Feel free to make a pull request on the docs, or open an issue if you see something missing and we'll try to get it added.
22:30 mgw hunter: Why do you want to avoid evaluating at compile time? There was a discussion some time ago on lazy pillars, but it had more to do with recursive evaluation, similar to reclass
22:30 MTecknol1gy dave_den: https://github.com/saltstack/salt/issues/9743
22:30 Heartsbane forrest: I have ... and I have reading
22:31 forrest Heartsbane, awesome!
22:31 Heartsbane Somehow this is all terminalmage's fault.
22:31 Networkn3rd joined #salt
22:31 * Heartsbane blames terminalmage.
22:31 forrest that's usually how it goes
22:31 terminalmage Heartsbane: just because you're a slacker, doesn't mean you have to blame everything on me :P
22:32 MTecknol1gy terminalmage: You have a cinnamon roll hat! Fix my issue!
22:32 MTecknol1gy please?
22:33 ajw0100 joined #salt
22:34 terminalmage MTecknol1gy: yeah, I'll drop everything else I'm working on
22:34 terminalmage just for you!
22:34 torrancew whiteinge: terminalmage: good meeting and chatting with you both re: salt, puppet, gitfs and pillar at-rest-encryption this weekend!
22:34 MTecknol1gy :D YAY!
22:34 terminalmage torrancew: yes I remember the topic, not so much the face. So many people!
22:34 Math` joined #salt
22:35 lynxman joined #salt
22:35 MTecknol1gy You guys are making me both sad that I missed but also happy that I w*will* be there next year.
22:35 dave_den MTecknol1gy: if you'd like to sponsor me for a fix, i'd be happy to spend the time on it. from what i can see we know what the problem is (getgrall and looping over every group)
22:36 hunter dave_den: I think I'm close -but http://pastebin.com/p6PVdje1
22:36 torrancew terminalmage: too many!
22:36 toastedpenguin joined #salt
22:36 hunter mgw: in this case I was hoping to include in the pillar data variables that would not be known until state.sls jinja time.
22:38 mgw hunter: is that pillar data in that case?
22:38 hunter yes
22:38 dave_den hunter: add .items() to your for loop line
22:38 mgw are you trying to use pillar data recursively?
22:38 hunter well, sort of - it was  a loop
22:38 MTecknol1gy wow... uploading a 100GB file w/o throttle does a great job of making ssh impossible
22:38 Math` I want to get logging enabled when using SSHClient from python code, I've tried settings opts['log_level'] to all but it doesn't seem to have any effect, what am I missing?
22:38 dave_den you need to unpack the dict key and the dict args into repo, args
22:38 psyl0n joined #salt
22:39 torrancew terminalmage: if you're ever up in the bay area, I hope you'll let me buy you a beer as a thank you for the half hour or so I stole from your life on Sat ;)
22:39 MTecknol1gy dave_den: I don't think the issue is even the loop, it seems to just be '''groups = [g.gr_gid for g in grp.getgrall() if user in g.gr_mem]'''
22:39 hunter dave_den: {% for repo, args in pillar.get('repos', {}).items() %}   ??
22:39 MTecknol1gy dave_den: What kinda penny are you looking for?
22:39 hunter dave_den: I just tried that version and it fails as well
22:40 MTecknol1gy I fully suspect that I'm in about the only environment in the world that would ever experience this.
22:40 MTecknol1gy Really, what we should be doing is having local read-only domain controllers, but the cost of that would be way more than we could afford.
22:41 terminalmage torrancew: I'm always up for free beer :)
22:42 forrest lol
22:42 hunter I hate not knowning what I'm doing.
22:42 hunter I like the jinja error messages - they aren't bad at all.
22:44 dave_den MTecknol1gy: indeed, anywhere you see getgrall you have potential for the 3 hour wait while ldap retrieves the list of groups, unless the cache is still warm
22:45 terminalmage hunter: in line 40, use items() or iteritems()
22:46 kloplop321 joined #salt
22:46 terminalmage hunter: oh, someone else already mentioned it I guess
22:46 hunter OH - instead of git
22:46 hunter get
22:46 terminalmage no you can use get
22:47 terminalmage but you should consider using the salt['pillar.get'] function
22:47 terminalmage in your jinja
22:47 hunter Then I totally don't understand
22:47 terminalmage hunter: one moment
22:47 terminalmage I'll pastebin it
22:47 dave_den {% for repo, args in pillar.get('repos', {}).items() %}   you said you tried this?
22:48 hunter yes
22:48 hunter let me cut-n-paste directly from IRC to avoid my typos
22:49 hunter Now I get an end_for error
22:49 terminalmage hunter: http://pastebin.com/kSF1vQ0U
22:50 terminalmage the latter is a salt function that can parse down multiple levels of nested dicts
22:50 terminalmage using : as a delmiter for dict levels
22:50 terminalmage good for deeply nested pillar data
22:51 hunter http://pastebin.com/MxxS6Rak
22:51 hunter terminalmage: I see the advantage of it - Let me get this version working for learning purposes and then I'll switch to that.
22:52 terminalmage cool
22:52 terminalmage hunter: is that the entire file?
22:52 hunter Yes
22:53 hunter Other than the pillar data which lives in a different file - I assume thats not what you meant.
22:54 dave_den hunter: you have syntax errors there
22:54 dave_den {{args.get('enabled'), repos_defaults.get('enabled')}}
22:54 terminalmage hunter: where does repos_defaults come from then?
22:54 hunter dave_den: I don't doubt it - but I'm too new at jinja templates to see them.
22:54 dave_den those lines have to be {{args.get('enabled', repos_defaults.get('enabled'))}}
22:54 hunter Let me paste the pillar data again.
22:54 dave_den see the paranthesis placement
22:54 hunter let me try dave_den's fix and then I'll paste the pillar again.
22:55 utahcon isn't there a way to pass a new pillar value with a command?
22:55 terminalmage ok, but repos_defaults doesn't seem to be defined
22:55 terminalmage that would seem to be a problem
22:55 utahcon salt * state.single pillarDatas etc?
22:55 hunter OH - Its a nested function wihtout the secondary closing paran.
22:55 hunter terminalmage: its in the pillar data file elsewhere.
22:55 dave_den bbiab
22:56 terminalmage hunter: ???
22:56 terminalmage hunter: if it's a pillar variable, then it'd need to be referenced using: pillar['repos_defaults']
22:56 terminalmage otherwise it's an undefined jinja variable
22:58 hunter terminalmage: hold on one please - you've got a partial view of something while I'm trying to see the dave_den pointed out syntax error
22:58 terminalmage hunter: ok... you did say that it was the entire file though
22:58 terminalmage so, sorry for the confusion
22:58 hunter Thats the entire _state_ file - I didn't include any of the pillar data file - let me do that now.
22:58 ndrei joined #salt
22:59 ipalreadytaken joined #salt
22:59 zain joined #salt
23:00 hunter terminalmage: http://pastebin.com/MxxS6Rak
23:00 terminalmage hunter: I think you're misunderstanding how this all works
23:00 hunter terminalmage: The pillar data file is at the top of that.
23:00 terminalmage pillar data is compiled and made available in a dictionary
23:00 terminalmage so it can be referenced using: {{ pillar['variable_name'] }}
23:01 hunter Yes- I've made sure that the pillar data I expect is seen by the client wiht "salt-call pillar.items"
23:01 terminalmage it doesn't get merged with the state file, at all
23:01 terminalmage hunter: OK... but ^^^
23:01 terminalmage {{ repos_defaults['baseurl'] }} is not going to work
23:01 terminalmage ever
23:02 terminalmage {{ pillar['repos_defaults']['baseurl'] }} is what is needed
23:02 hunter That was what dave_den sent me in irc above.
23:02 Guest72558 joined #salt
23:02 hunter at around 16:17
23:03 whiteinge torrancew: nice chatting with you as well
23:03 terminalmage hunter: please read http://docs.saltstack.com/topics/pillar/index.html?highlight=pillar#pillar-get-function
23:03 terminalmage that shows how pillar is referenced in jinja
23:03 terminalmage and also demonstrates pillar.get
23:04 whiteinge torrancew: i don't think we have a issue to get that added (although it has been discussed). care to do the honors?
23:04 terminalmage hunter: I wasn't part of your earlier conversation, sorry
23:04 ipalreadytaken joined #salt
23:04 terminalmage I'm just telling you how it works
23:04 hunter You are certainly trying, and I very much appreciate that.
23:05 hunter And I don't doubt I mistunderstand how this works. But without an example of the base loop working, that if statement and its contents doesn't have to be correct or incorrect - I can't get there.
23:06 terminalmage well, dave_den pointed out a problem with one of your get calls
23:06 hunter He did and I thought I had fixed it correctly - but I am mistaken.
23:06 hunter Rendering SLS "dev:yum.base" failed: Jinja variable 'list' object has no attribute 'items'; line 10
23:06 hunter for the line:
23:07 hunter {% for repo, args in pillar.get('repos', {}).items() %}
23:08 terminalmage hunter: what do you think that might mean?
23:08 terminalmage "'list' object"
23:08 hunter I _think_ thats telling me the result of the .get() is just the list of repo names
23:10 zain joined #salt
23:10 terminalmage http://dpaste.com/1655081/
23:10 terminalmage it's telling you that repos_defaults is a list
23:10 terminalmage it needs to be a dict for what you're trying to do
23:11 terminalmage lists entries are prepended with a dash
23:11 terminalmage so... get rid of that
23:11 hunter But that line doesn't refer to repos_defaults - its only referring to the repos.
23:12 terminalmage yeah, I used the wrong example... but if you look at "repos", it has the same issue
23:12 hunter Ok. Let me try
23:12 terminalmage remove all those dashes
23:12 terminalmage from both
23:14 bhosmer joined #salt
23:15 hunter done. Now it errors out further down-  and I think I understand the probelem down there.
23:15 hunter terminalmage: i need to review how yaml formatted pillar data is specified - I thought those dashes were necessary
23:16 terminalmage hunter: pillar data can be any data structure you want it to be
23:16 terminalmage you told it to be lists
23:16 hunter I see that now. But that wasn't my intent and my mistake was not obvious to me.
23:16 torrancew whiteinge: will do!
23:17 terminalmage hunter: http://www.yaml.org/spec/1.2/spec.html
23:18 hunter As I said, I need to review how yaml formatted .....
23:18 hunter But that url will be handy for the base spec.
23:19 hunter Now I'm hitting what you alluded to earlier, which is that I'm attempting to use a naked pillar data chunk without requesting it first.
23:19 terminalmage hunter: yeah I know... my point is that pillar data has no specific formatting
23:19 hunter Lets see if i can figure this out on my own
23:19 hunter prove that I'm not a complete moron
23:19 terminalmage hunter: it is user-specified
23:20 hunter indeed - and thats useful - later. Right now a little more rigidity might make learning easier. :)
23:21 hunter In jinja, what is the difference between {% and {%-
23:21 hunter ?
23:21 christopherl joined #salt
23:21 forrest hunter, http://jinja.pocoo.org/docs/templates/#whitespace-control
23:22 terminalmage hunter: http://dpaste.com/1655127/
23:22 terminalmage hunter: I don't know what you mean by "rigidity" here, sorry
23:22 hunter terminalmage: that dpaste is what i needed - I'm saving that.
23:23 hunter forrest: AH.
23:23 terminalmage hunter: better download it, that site drops pastes after a week
23:24 hunter http://pastebin.com/MxxS6Rak
23:24 hunter Final version, and that one is working.
23:24 terminalmage hunter: anything with a colon is a dictionary key
23:24 krow joined #salt
23:24 terminalmage and what comes after it is the value for that key
23:24 hunter terminalmage: I got it - I have a notes dir in my /srv/salt for such nuggets.
23:25 hunter terminalmage: thank you (and forrest and dave_den) kindly for the help.
23:25 terminalmage np
23:25 xmltok_ ive built a second salt master and copied over the master keys, yet my minions are not connecting to it. they just keep cycling trying to reconnect
23:25 hunter terminalmage: thinking back I think I had gotten into the habit of everything (or nearly everything) having a dash from teh state files
23:26 ahammond O
23:26 hunter 1
23:26 ahammond god, I _hate_ this new keyboard.
23:26 ahammond ok. trying again.
23:26 ahammond I'm having issues using git.latest to clone a repo. The error I get is "fatal: I don't handle protocol '/root/https' "
23:26 ahammond anyone seen that before?
23:27 hunter terminalmage: at least I understand more of what was going on in the very complicated https://github.com/saltstack-formulas/sudoers-formula/blob/master/sudoers/files/sudoers
23:27 hunter that I was using as a learning example.
23:27 Math` anyone familiar with the source of client/ssl/__init__.py, Im not sure if what I'm seeing is a bug or intended behavior. SSHClient.cmd_iter calls SSH.run_iter, but SSHClient.cmd also calls run_iter (instread of run). Is this intended or is it a bug?
23:27 xmltok_ bah. iptables
23:27 hunter terminalmage: not easy teaching the village idiot of jinja/pillar is it. :)
23:27 Math` Im guessing it's a bug since cmd shouldnt be a generator
23:28 Math` and by ssl I mean ssh
23:28 terminalmage hunter: once you grok yaml better, this makes more sense
23:28 terminalmage no worries
23:29 hunter terminalmage: actually for me the aha moment was that loop
23:29 hunter I'm still chewing on it
23:29 terminalmage the difference between state files and pillar data is that state files are designed with a specific structure in mind, and pillar data is just whatever you want it to be
23:29 terminalmage so, you need to understand YAML if you're going to use complex pillar data structures
23:30 EHLOha joined #salt
23:30 terminalmage fwiw, you can also use pure python :D
23:31 nextdoorwarren joined #salt
23:31 hunter terminalmage: I've seen a puppet setup driven by the ruby lang instead of the puppet DSL. I hesitate to go down the same path with salt/python.
23:32 hunter Though at least i'm a bit of a python programmer.
23:32 terminalmage hunter: yeah but we like to provide options
23:32 terminalmage pure python lets you have your pillar data be more dynamic in the cases where that is desirable
23:32 hunter terminalmage: and for advanced users, options = the awesome. For me right now and other users starting out options aren't always so hot
23:33 hunter terminalmage: so far........ What I'm seeing and making notes against suggests salt/pillar is just about right dynamic-wise. I might need reclass later on driving some stuff but not right now.
23:33 * hunter does a git commit of the working template I have before experimenting.
23:35 MTecknology joined #salt
23:38 snuffeluffegus joined #salt
23:41 liwen joined #salt
23:42 rojem joined #salt
23:43 mgw joined #salt
23:44 z3uS joined #salt
23:47 hunter using {{'{{repo}}'}} in the pillar data successfully gets {{repo}} paste the pillar jinja render stage, but doesn't do the right thing in the state one.
23:48 hunter Interesting.
23:48 leonardinius joined #salt
23:49 ahammond does file.managed store a backup file anywhere?
23:51 dave_den hunter: put this at the top of the state file:   #! jinja | jinja | yaml
23:55 Linz joined #salt
23:55 hunter Rendering SLS "dev:yum.base" failed: Jinja variable 'repo' is undefined; line 31
23:56 liwen joined #salt
23:56 hunter dave_den: I'm ok with this not working - you and terminalmage have got me to a good starting point. but now that I had somethng that worked I'm trying to circle back and explore the crannies I skipped over earlier.
23:57 nextdoorwarren joined #salt
23:58 terminalmage hunter: without seeing your SLS and pillar data, that error is meaningless to me
23:58 hunter Hold on then - i can paste it.

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