Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-01-21

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

All times shown according to UTC.

Time Nick Message
00:05 alemeno22 joined #salt
00:06 alemeno22 joined #salt
00:10 cpowell joined #salt
00:10 GothAck joined #salt
00:10 paolo joined #salt
00:10 cpowell joined #salt
00:10 GothAck joined #salt
00:10 paolo joined #salt
00:11 dijit joined #salt
00:18 larsfronius joined #salt
00:23 keimlink_ joined #salt
00:25 onlyaneg1 joined #salt
00:25 tmclaugh[work] joined #salt
00:26 ekkelett joined #salt
00:26 ekkelett joined #salt
00:29 oida joined #salt
00:29 UtahDave left #salt
00:33 digitalhero joined #salt
00:36 otter768 joined #salt
00:39 onlyaneg1 joined #salt
00:40 onlyaneg1 joined #salt
00:40 nyx_ joined #salt
00:42 onlyaneg1 joined #salt
00:46 alexlist joined #salt
00:50 berto- joined #salt
00:50 cztanu joined #salt
00:50 lompik joined #salt
00:53 tvinson joined #salt
00:57 ablemann joined #salt
01:00 matt_____ joined #salt
01:03 larsfronius joined #salt
01:11 kevinquinnyo1 joined #salt
01:13 kevinquinnyo1 has anyone ever done some kind of 'functional testing' after highstate or individual state runs to ensure that the minions are properly configured?  I don't need anything fancy, i just think it would be nice if after say the highstate runs with no failures i could hit the minion on port 80 and check for a few things, etc
01:14 kevinquinnyo1 just wondering if there's a proper way to do this -- i notice there are some built in test classes in salt core that i could use, but they seem to be for unit testing modules and such, not testing achieved state
01:19 larsberg joined #salt
01:22 brianfeister joined #salt
01:23 ajw0100 joined #salt
01:24 capricorn_1 joined #salt
01:27 catpigger joined #salt
01:34 izrail joined #salt
01:46 baweaver joined #salt
01:51 nZac joined #salt
01:57 cpelon joined #salt
01:57 cpelon how do i upgrade my salt master from 2015.8.3 to develop?
02:01 malinoff joined #salt
02:04 alemeno22 joined #salt
02:16 donmichelangelo joined #salt
02:22 catpiggest joined #salt
02:37 synical joined #salt
02:37 racooper joined #salt
02:37 otter768 joined #salt
02:46 auzty joined #salt
02:48 ilbot3 joined #salt
02:48 Topic for #salt is now Welcome to #salt! | Latest Version: 2015.8.3 | Paid support available for open source Salt! www.saltstack.com/support | Logs: http://irclog.perlgeek.de/salt/ | Paste: https://gist.github.com/ (please don't multiline paste into channel) | Ask with patience as we are volunteers and may not have immediate answers
02:48 _ikke_ joined #salt
02:51 oida joined #salt
02:54 Bryson joined #salt
02:54 RandyT I'm hitting throttling issues using boto against cloudwatch api. What are my options to pace these api calls?
02:59 jimklo_ joined #salt
03:05 oida joined #salt
03:09 anmol joined #salt
03:10 otter768 joined #salt
03:11 _JZ_ joined #salt
03:11 brianfeister joined #salt
03:13 GrueMaster joined #salt
03:14 jalbretsen joined #salt
03:18 kevinquinnyo1 is there any way to have nested directories in a runners_dir and call them with "dot notation" or some other notation from the command line?
03:18 altu1nsf0llow3r joined #salt
03:18 kevinquinnyo1 for example: /srv/salt/runners/foo/bar/baz.py   <-- my runner.  # salt-run foo.bar.baz.function_name arg
03:22 wangofett joined #salt
03:23 AnalogLifestyle joined #salt
03:28 ashmckenzie joined #salt
03:29 RandyT kevinquinnyo1: not sure if there are any specifics around runners, but I would assume you can add /srv/salt/runners to file_roots: in master and that would work
03:34 brianfeister joined #salt
03:46 quasiben joined #salt
03:48 favadi joined #salt
03:50 kevinquinnyo1 RandyT: In order to write my custom runner, i have to define my runners_dir in my master salt configuration file to be: /srv/salt/runners/
03:51 kevinquinnyo1 there is no <file_roots>/_runners default by the way (at least not currently that I'm aware of) like there is for _modules and _states
03:53 RandyT just guessing but I would expect that any path you provide to the runner is going to use the salt filesystem. Which I would think maps to that path if foo is under your file_roots:
03:54 RandyT like I said, no idea if runners are unique somehow. Easy enough to try.
04:01 dimeshake joined #salt
04:01 dimeshake joined #salt
04:07 fleaz joined #salt
04:08 ageorgop joined #salt
04:12 writtenoff joined #salt
04:21 _JZ__ joined #salt
04:25 moogyver joined #salt
04:46 moogyver joined #salt
04:50 voidspacexyz joined #salt
05:09 Fiber^ joined #salt
05:17 digitalhero joined #salt
05:21 zmalone joined #salt
05:23 malinoff joined #salt
05:25 tmclaugh[work] joined #salt
05:25 ageorgop joined #salt
05:32 rdas joined #salt
05:48 anmol joined #salt
05:49 freelock joined #salt
05:57 calvinh joined #salt
05:57 favadi joined #salt
05:59 armyriad joined #salt
06:09 Vaelatern Hey, does salt-ssh support ed25519 keys?
06:09 Vaelatern My systems all do
06:11 MeltedLux joined #salt
06:12 impi joined #salt
06:13 ntropy check what the underlying ssh library supports
06:16 rominf joined #salt
06:25 lemur joined #salt
06:31 dlam joined #salt
06:32 otter768 joined #salt
06:41 voidspacexyz joined #salt
06:42 alemeno22 joined #salt
06:50 calvinh joined #salt
06:53 Vaelatern Does salt support multiple ways to disable a service?
06:55 malinoff Vaelatern: like what ways?
06:55 Vaelatern Working on void linux support. You can either $(touch /var/service/<service>/down) or $(rm /var/service/<service>)
06:56 Vaelatern There is an ideological disconnect between me and the other person working on this. I would rather rm, he'd rather touch. Is there an alternative where we both can have peace?
06:57 Vaelatern Touching feels more temporary than rming it
07:03 atmosx joined #salt
07:03 atmosx hello
07:03 atmosx is there a way to get the sate of the remote machine, like: salt 'minion2' state.info or something>
07:04 Pie_Mage like to see which states get applied?
07:05 atmosx yes, which states are applied in the remote machine
07:05 Pie_Mage salt state.show_top
07:05 Pie_Mage there are a few show_* functions to show highdata and lowdata
07:05 Pie_Mage if you need more detailed data
07:05 atmosx thanks
07:06 Pie_Mage https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.state.html
07:09 linjan joined #salt
07:10 davromaniak joined #salt
07:15 chutzpah joined #salt
07:19 kshlm joined #salt
07:26 anmol joined #salt
07:44 federicob joined #salt
07:48 impi joined #salt
07:49 rdas joined #salt
07:52 KingJ joined #salt
07:53 jhauser joined #salt
07:59 aqua^c joined #salt
08:00 otter768 joined #salt
08:01 yuhlw joined #salt
08:02 otter768_ joined #salt
08:02 elsmo joined #salt
08:04 otter76__ joined #salt
08:06 otter768 joined #salt
08:07 otter768 joined #salt
08:08 anmol joined #salt
08:09 otter768_ joined #salt
08:11 rdas joined #salt
08:11 otter768 joined #salt
08:12 rdas joined #salt
08:14 dgutu joined #salt
08:16 doody joined #salt
08:18 viq joined #salt
08:20 doody hello, i have been googleing round havent found answer to the question.. how i can place automatically some text from pillars to the top of the file.. i know that file.append puts end of the file, but how with top?
08:24 doody i have made right now these steps:
08:24 doody https://gist.github.com/asjalik/7a057bada764e507772d
08:27 dariusjs joined #salt
08:28 Rkp doody: not tested but what about file.prepend ?
08:28 Rkp https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html could need a recent salt version though
08:28 dayid joined #salt
08:29 dayid joined #salt
08:32 kawa2014 joined #salt
08:38 Rumbles joined #salt
08:42 doody thanks alot @Rkp file.prepend works for me :) https://gist.github.com/asjalik/157f17ecee2aa3c70ae7
08:46 Grokzen joined #salt
08:47 amcorreia joined #salt
08:52 geomacy joined #salt
08:58 LondonAppDev joined #salt
09:03 vim-zz joined #salt
09:05 vim-zz i have state decalred at main.sls, i want to have another state in another.sls to wait for the first, ow can i do that?
09:13 jhauser joined #salt
09:17 linjan joined #salt
09:21 Xevian joined #salt
09:25 slav0nic joined #salt
09:26 keimlink joined #salt
09:28 pwalsh joined #salt
09:33 Doody joined #salt
09:34 s_kunk joined #salt
09:34 s_kunk joined #salt
09:35 s_kunk joined #salt
09:46 N-Mi joined #salt
09:47 wm-bot4 joined #salt
09:48 ajw0100 joined #salt
09:52 rotbeard joined #salt
09:54 mekstrem joined #salt
09:55 kbyrne joined #salt
10:02 colttt joined #salt
10:10 amcorreia joined #salt
10:12 thebwt joined #salt
10:14 phx joined #salt
10:14 chiui joined #salt
10:16 onlyaneg1 joined #salt
10:18 GreatSnoopy joined #salt
10:22 _mel_ joined #salt
10:23 larsfronius joined #salt
10:25 larsfron_ joined #salt
10:25 Rumbles joined #salt
10:27 atmosx how can I enforce key-generation every time a change is made here: https://gist.github.com/atmosx/d3a0a56f67a5aaffed82 ?
10:30 basepi joined #salt
10:32 [vaelen] joined #salt
10:32 packeteer joined #salt
10:32 chutzpah joined #salt
10:32 esharpmajor joined #salt
10:37 Pie_Mage atmosx: are you sure you want to constantly re-key your ssh host keys/
10:38 atmosx Pie_Mage: hmm, not just once to turn the rsa to 4096
10:38 atmosx Pie_Mage: but it's better to do it thgouth another state maybe
10:38 atmosx just once
10:38 atmosx this state will regenerate keys on every sshd_config change
10:39 Pie_Mage you could set a grain saying it's run once?
10:39 atmosx anyway, I figured how to delete files absent, but can it accept a wildcard? like /etc/ssh/ssh_host* ?
10:39 Pie_Mage lemme check how I do it
10:40 Pie_Mage I think I just run Cmd.run('rm /etc/ssh/ssh_host*')
10:40 atmosx Pie_Mage: I had no idea that was possible. I can setup a grain saying 'sshd_keys_generation_date: $(date)' for example?
10:40 atmosx ah yes, I thought about this
10:40 Pie_Mage yes I believe so
10:40 Pie_Mage I haven't done it, but I recall it bein possible
10:41 atmosx okay, that is about right, so I'll ask the lead engineer if I have to rotate keys and I'll just: salt 'group' cmd.run '<cmd'
10:41 Pie_Mage https://github.com/alandrees/salt-secure-ssh/blob/master/sshd_config.sls
10:41 atmosx okay ty
10:41 Pie_Mage that's how I handle it
10:42 Pie_Mage i'll kill my keys every time though... so I guess I gotta fix that :P
10:42 atmosx tha 'name' tag is really confusing for a newcomer like me, calling it 'exec' would be more appropriate IMHO
10:42 Pie_Mage yeah, I agree
10:43 atmosx Pie_Mage: good!
10:43 atmosx that's a nice example btw
10:43 Pie_Mage ty
10:43 spaceSub Is there something like salt clouds profiles and maps for the salt virt module?
10:51 Rumbles joined #salt
10:53 giantlock joined #salt
11:06 permalac joined #salt
11:13 denys joined #salt
11:16 SN joined #salt
11:18 Guest47301 joined #salt
11:28 CeBe joined #salt
11:30 giantlock joined #salt
11:41 ajw0100 joined #salt
11:47 rmnuvg joined #salt
11:55 atmosx This line: https://gist.github.com/atmosx/d3a0a56f67a5aaffed82#file-config-sls-L25 waits for a: generate_rsa:\n -size: 4096 in pillar/openssh.sls or something else to get triggered?
11:57 dariusjs joined #salt
12:01 voidspacexyz_ joined #salt
12:03 Rumbles joined #salt
12:03 Pie_Mage hmm
12:05 atmosx Pie_Mage: I figured that doesn't create keys randomly, this must work like: salt 'grou1p' openssh.generate_rsa:4096 (or something similar)
12:06 Pie_Mage that looks correct, as far as I can tell
12:08 Pie_Mage and you say it's hanging?
12:09 atmosx it's not executing
12:10 atmosx I'm not sure how to call it
12:10 Pie_Mage oh!
12:10 Pie_Mage i see
12:10 Pie_Mage salt 'grou1p' salt.sls openssh.generate_rsa:4096
12:10 atmosx due to our previous discussion I figured that this might be called dynamically somehow
12:10 atmosx what is salt.sls ?
12:11 Pie_Mage erm sorry
12:11 Pie_Mage state.sls
12:11 atmosx ah
12:11 Pie_Mage you can add a test=true and it will go through the motions, and test everything
12:11 atmosx awesome
12:11 Pie_Mage before you actually execute the state
12:11 VSpike Has anyone seen the case where using the users formula and supplying the gitconfig data, it fails to set the git stuff on the first pass but another run of the states works fine?
12:12 atmosx I'm working on two testing droplets on DO anyway
12:12 atmosx but that's cool
12:12 Pie_Mage atmosx: https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.state.html
12:13 Pie_Mage those are all the module functions you can call at the commandline
12:13 Pie_Mage lots of really helpful debugging and introspection commands in there (especially like show_highdata, show_lowdata, etc.)
12:14 VSpike https://bpaste.net/show/2fbdf7348bbf is the output
12:15 VSpike The important bit being ... "[ERROR   ] State 'git.config_set' was not found in SLS 'users'\nReason: 'git' __virtual__ returned False"
12:17 atmosx Pie_Mage: it returns  'openssh.sls' is not available. when executing the cmd. I updated the gist to display dir tree https://gist.github.com/atmosx/d3a0a56f67a5aaffed82
12:17 atmosx I think it's relevant. I tried also replacing 'openssh.sls' with 'openssh' & 'config.sls'
12:23 Pie_Mage the pathing in salt is done the same way as in python
12:23 Pie_Mage so to refer to to openssh/config.sls you'd need to do openssh.config
12:24 Pie_Mage so your command would look like:
12:25 Pie_Mage salt 'grou1p' state.sls openssh.config test=true
12:26 atmosx this works fine
12:26 Pie_Mage woohoo!
12:27 atmosx but I want to generate the keys :-P
12:29 atmosx salt '*' state.sls openssh.generate_ed25519_keys test=true <-- this should run
12:30 atmosx hm, I think i tmight be easier to generate a new state and just call it
12:30 otter768 joined #salt
12:35 Pie_Mage remove the test=true
12:35 Pie_Mage and it will actually generate the keys
12:36 fas3r joined #salt
12:36 fas3r hello
12:37 evle joined #salt
12:37 Pie_Mage \o
12:40 quasiben joined #salt
12:42 fas3r can I use file.search ad file.sed i a sls file ?
12:43 Pie_Mage https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html
12:44 Pie_Mage doesn't look like it... but I recall their being a way to call module functions from inside states
12:46 Pie_Mage s/their/there
12:47 Pie_Mage fas3r: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.module.html
12:47 fas3r Pie_Mage: Thanks !!
12:51 ajw0100 joined #salt
12:54 tarunBansal joined #salt
12:55 AlberTUX1 joined #salt
12:56 Pie_Mage np! :D
12:56 tarunBansal Hi. Any salt experts here? Need to ask a complex doubt. Please help.
12:58 tarunBansal We have a installable product for *nix systems. Want to support bulk deployment using salt. I have read about salt states, pillars and grains. Now need to know how to execute a shell script with a custom argument.
12:58 Pie_Mage you used salt much?
12:59 tarunBansal No. Just set it up locally and playing around with different modules.I know we can use the cmd.run state module for this purpose but my doubt is how to pass a user defined argument to the command which we want to execute.
13:00 Pie_Mage there are a few ways to do that
13:00 Pie_Mage you can pass on the command line, you can use what are called 'salt grains' or you can use 'salt pillars'
13:01 Pie_Mage then you can build your cmd.run command with jinja templating
13:01 tarunBansal Thanks. Please let me know how to refer that inside state module. Its the API_key i want to input and the command actually looks like 'sudo ./XYZ -i -key=<API_Key>'
13:02 tarunBansal Oh okay. will look into jinja templating.
13:02 Pie_Mage https://docs.saltstack.com/en/latest/topics/tutorials/states_pt3.html
13:02 Pie_Mage unless you changed your renderer, that should do you for what you need to do
13:04 tarunBansal Please note i want the same API_Key to be used for all the minions.
13:04 Pie_Mage well then you can specify on the commandline, and use that varible inside the template
13:04 fas3r tarunBansal: like this : http://pastebin.com/nZa5Far8
13:04 Pie_Mage or you can specify a salt pillar
13:04 fas3r that's a stupid examle but you have the logic
13:05 Pie_Mage ^
13:06 Pie_Mage pillars are the way to go
13:08 tarunBansal Yes okay. Will go with pillars method.
13:09 fas3r tarunBansal: if not you can try mine.get but that's way too heavy.
13:09 kshlm joined #salt
13:12 tarunBansal Yes. can i use mine.get inside cmd.run ?
13:12 nyx_ joined #salt
13:14 tarunBansal in this way - salt '*' cmd.run ' sudo ./XYZ -i -key={mine.get _____ } '
13:16 Pie_Mage you don't need to use pillars or mines or grains if you just want to execute from the commandline
13:16 Pie_Mage by specifying your target as '*', the command you give the cmd.run module will be identical on all the systems
13:17 tarunBansal Yes that is my objective too. I guess i should use plain command line rather than salt states.
13:18 Pie_Mage states are great though!
13:18 Pie_Mage you can just put your command in there, and keep it in version control
13:19 tarunBansal Yeah i have also read that .. also i need to provide options to bulk uninstall and bulk status check.
13:20 geomacy joined #salt
13:20 anmol joined #salt
13:20 av_ joined #salt
13:27 Pie_Mage you can just write different state files, so you can just on the commandline do:
13:27 Pie_Mage salt '*' state.sls XYZ.status_check
13:32 Rumbles joined #salt
13:32 zerthimon joined #salt
13:33 jespada joined #salt
13:36 ingslovak joined #salt
13:36 fas3r Can I use file.replace to remove an entire line in a file ?
13:36 fas3r or I cshould prefer a cmd.run with grep and sed ?
13:39 cyborg-one joined #salt
13:42 pwalsh joined #salt
13:43 Pie_Mage i found file.replace to work nicely
13:44 Pie_Mage i'm pretty sure you can specify regex too
13:45 Tanta joined #salt
13:45 KennethWilke joined #salt
13:48 lompik joined #salt
13:49 DammitJim joined #salt
13:49 cyborg-one joined #salt
13:51 subsignal joined #salt
13:57 dendazen joined #salt
13:59 dendazen Hey guys i have this part of code in my state: https://gist.github.com/anonymous/793069593a3378a3b70a
14:00 dendazen and from master i can see that grain value [root@ops1 ~]# salt 'vialactea.sec1.example.com' grains.items | grep roles -A1
14:00 dendazen roles:
14:00 dendazen - mailserver
14:01 dendazen but when i run that state the line still gets appended to the main.cf.
14:01 dendazen What am i doing wrong?
14:08 erjohnso joined #salt
14:08 hasues joined #salt
14:08 hasues left #salt
14:08 zmalone joined #salt
14:11 drawsmcgraw dendazen: I think you're using salt('grains.get') wrong
14:11 drawsmcgraw one second
14:11 dendazen yeah, i mean i used this version as well and it did not work
14:12 dendazen https://gist.github.com/anonymous/b4480386995441288d43
14:12 dendazen and unfrotunately it did not work for me either.
14:13 drawsmcgraw dendazen: You want to append the line to the main.cnf *only if* it has the 'mailserver' role, correct?
14:13 impi joined #salt
14:13 fas3r Pie_Mage: I checked but no success :D
14:13 dendazen no, only if it doesn't.
14:13 drawsmcgraw ah, okay. Don't append the line if it has the 'mailserver' role.
14:14 dendazen yes.
14:15 dendazen oh then first state is completely wrong
14:15 dendazen even semantically.
14:15 dendazen it would append the line
14:16 drawsmcgraw Yeah, I'm thinking something like this: http://dpaste.com/1Y9HVBX
14:17 drawsmcgraw Also, if you want to get the 'mailserver' role in the 'roles' grains, it would look like this -> salt['grains.get']('roles:mailserver','')
14:17 drawsmcgraw The second argument is a default to be returned if what you're asking for is not found.
14:18 Pie_Mage fas3r: https://github.com/alandrees/salt-secure-ssh/blob/master/sshd_config.sls#L27-L30
14:18 dendazen oh, i see. Thank you.
14:19 fas3r Pie_Mage: ok but it will not replace by a empty line ?
14:19 drawsmcgraw yep! Good luck!
14:20 Pie_Mage if you wanted to replace it with a blank line, you can just set repl to \n
14:20 fas3r ok, no I want to remove it.
14:20 fas3r so it should be fine than.
14:20 fas3r thanks !
14:20 Pie_Mage no problem!
14:22 sterfield joined #salt
14:23 dendazen It worked, thanks much.
14:25 nyx_ joined #salt
14:25 lothiraldan joined #salt
14:31 otter768 joined #salt
14:33 impi joined #salt
14:35 racooper joined #salt
14:37 Tyrm joined #salt
14:38 numkem joined #salt
14:38 mapu joined #salt
14:41 akhter joined #salt
14:45 fas3r Pie_Mage: working, thanks !
14:48 fas3r can I list the content of a file with salt ?
14:49 blckbit10 joined #salt
14:50 izrail joined #salt
14:50 Sacro Yes
14:52 Pie_Mage fas3r: \o/
14:52 fas3r Pie_Mage: hahah I know :D
14:52 fas3r forget it hahah :D
14:52 fas3r cmd.run 'cat .... '
14:52 Pie_Mage lol
14:52 fas3r actually I found : cp.get_file_str
14:54 gh34 joined #salt
15:01 tmclaugh[work] joined #salt
15:03 winsalt joined #salt
15:06 wangofett so... I don't think I want to manage an entire xml file, just some sections of it
15:06 wangofett is that insanity?
15:06 nyx_ joined #salt
15:11 wangofett Aw, boo. Also wanted to file.recurse but apparently you can only do that with a salt:// uri and not s3://
15:12 VSpike wangofett: what about https://docs.saltstack.com/en/latest/ref/file_server/all/salt.fileserver.s3fs.html ?
15:12 andrew_v joined #salt
15:13 wangofett VSpike: yeah, that's what I'm doing... but file.recurse: source: s3://mybucket/ fails with
15:13 wangofett Invalid source: s3://mybucket/ (must be a salt:// URI)
15:14 ecdhe joined #salt
15:14 VSpike wangofett: oh, I imagined that would map S3 into your salt:// hierarchy
15:15 wangofett me too, heh
15:16 quasiben joined #salt
15:16 fas3r does unless can work with other states than cmd.run ?  (module.run for example)
15:16 fas3r ?
15:16 Brew joined #salt
15:17 wangofett I think that must be why my colleague created what looks like a state that puts hgfs in the salt dir :P
15:17 Pie_Mage i don't believe so
15:17 fas3r Pie_Mage: ok thanks.
15:18 Pie_Mage unless the module implements it themselves
15:18 wangofett Hm. I thought I was told differently - that unless/onlyif/onchanges/etc. work on all states
15:18 Pie_Mage I could be wrong, i'm still pretty new
15:19 Pie_Mage i'm just interpolating from the fact that it's a named param for cmd.run
15:19 VSpike This is wierd. I'm creating instances from an AMI where the AMI defines a root volume type as "gp2". In my salt-cloud profile I define a block device mapping for an additional disk. The resulting instance has a standard root disk.
15:21 morissette joined #salt
15:21 oida joined #salt
15:21 RandyT wangofett: if you setup the s3:// resources as and s3fs, I believe it will map that to the salt://
15:22 RandyT s/as and/as an/
15:22 Pie_Mage I know of ways to solve that problem using the pyobjects renderer... but i'm not sure if it's possible using jinja + yaml
15:26 digitalhero joined #salt
15:33 berserk joined #salt
15:35 berserk joined #salt
15:35 Tyrm joined #salt
15:36 ALLmightySPIFF joined #salt
15:37 ALLmightySPIFF joined #salt
15:37 rm_jorge joined #salt
15:39 ALLmightySPIFF joined #salt
15:46 zsoftich1 joined #salt
15:49 marcus_ joined #salt
15:50 bahdoosd joined #salt
15:51 nidr0x joined #salt
15:51 dmatson1 joined #salt
15:53 dmatson1 is there a state I could use to generate a keypair on a minion X and then deploy the public key to minion Y for passwordless ssh between X->Y?
15:53 murrdoc joined #salt
15:55 _JZ_ joined #salt
15:57 fas3r can I check the result of a state using beside using watch/onchanges/onfail ?
15:57 fas3r like {% if mystate %} ..... does it work like this too ?
15:57 cilkay joined #salt
16:00 baoboa joined #salt
16:01 digitalhero joined #salt
16:01 Ssquidly joined #salt
16:02 Rumbles joined #salt
16:03 berserk joined #salt
16:06 wangofett RandyT: it doesn't appear to work like that. At least they don't show up when I do `fileserver.file_list`
16:06 Pie_Mage does anyone know how to get a list of state modules?
16:06 wangofett dmatson1: why not generate the key on master and deploy the private key to X and public key to Y?
16:06 zmalone joined #salt
16:07 wangofett Pie_Mage: do you mean states or modules?
16:07 Pie_Mage states
16:07 wangofett huh, I guess they're called state modules in the docs
16:07 wangofett https://docs.saltstack.com/en/latest/ref/states/all/index.html
16:08 Pie_Mage is there a way for me to list them in salt?
16:09 Pie_Mage it's telling me Debconfmod isn't available or something
16:09 oida joined #salt
16:09 nyx_ joined #salt
16:10 wangofett `ls /usr/lib/python2.7/site-packages/salt/states/*.py` may be helpful
16:10 wangofett assuming that ours are installed in the same place
16:14 zsoftich1 joined #salt
16:15 Pie_Mage maybe it's a bug with pyobjects
16:16 cpowell joined #salt
16:17 CheKoLyN joined #salt
16:17 malinoff joined #salt
16:21 fas3r I'm looking for a template (if I can call it like this), to build a documentation for an API. Any to recommand ?
16:22 fas3r oups wrong chan :D
16:27 dfinn joined #salt
16:27 akhter joined #salt
16:28 tehsu anyone using saltpad here
16:32 otter768 joined #salt
16:37 scooby2 joined #salt
16:38 shoemonkey joined #salt
16:38 jimklo joined #salt
16:39 jhauser_ joined #salt
16:43 wangofett not I, but saltpad does look interesting
16:45 InsaneGeek joined #salt
16:46 Laserwhit joined #salt
16:50 SubOracle joined #salt
16:52 tehsu just wondering about the settings file
16:54 moogyver joined #salt
16:55 alemeno22 joined #salt
16:57 eriko_ joined #salt
16:58 L2SHO joined #salt
16:59 Tyrm joined #salt
17:00 neogenix joined #salt
17:02 onlyaneg1 joined #salt
17:03 mpanetta joined #salt
17:10 akhter joined #salt
17:11 totzky joined #salt
17:12 Bryson joined #salt
17:13 berserk joined #salt
17:14 Lionel_Debroux joined #salt
17:14 brianfeister joined #salt
17:19 pwalsh joined #salt
17:20 akhter_1 joined #salt
17:21 eriko_ joined #salt
17:22 shanemhansen joined #salt
17:25 wangofett If I have two states in one, e.g. somestate: file.directory:... cmd.run:...
17:26 wangofett if the cmd.run, runs
17:28 wryfi_ is it possible to call a jinja macro from an imported state?
17:29 wryfi_ i can't seem to get it to work
17:29 wryfi_ sorry, i mean an _included_ state
17:29 wangofett should another state with `onchange... okay never mind, I just wasn't doing `onchange: cmd: somestate` *facepalm*
17:29 jab416171 is there a salt module to manage the keys on a syndic?
17:29 fas3r wangofett: :D
17:29 jab416171 from a master
17:29 wangofett wryfi_: pretty sure - look at the users formula
17:31 fas3r can we make a && or || (AND / OR) in a if state ?
17:31 fas3r statement*
17:31 wryfi_ wangofett i don't see any macros in the users formula
17:36 AlberTUX1 joined #salt
17:37 chadhs joined #salt
17:38 berserk joined #salt
17:39 Rumbles joined #salt
17:39 linjan joined #salt
17:45 pwalsh joined #salt
17:46 rem5 joined #salt
17:46 dmatson1 left #salt
17:52 murrdoc its a terrible formula
17:59 murrdoc1 joined #salt
18:03 onlyaneg1 joined #salt
18:07 DanyC joined #salt
18:08 Rumbles joined #salt
18:09 giantlock joined #salt
18:10 denys joined #salt
18:10 onlyanegg joined #salt
18:12 nidr0x joined #salt
18:13 tmclaugh[work] joined #salt
18:14 wangofett wryfi_: the macro is defined in map.jinja, I believe
18:15 wryfi_ wangofett: no, i grepped through the whole repo for 'macro' and it doesn't appear once. but that's ok. i figured it out. i have to both import and include.
18:15 wryfi_ include brings in the rendered file, so it's too late to know about macros
18:15 wangofett Hm. Maybe it was the jenkins-forumla
18:15 wangofett formula
18:16 wangofett ah, yeah, there I go conflating the two again >_<
18:20 Brew joined #salt
18:21 akhter joined #salt
18:25 akhter_1 joined #salt
18:25 irctc775 joined #salt
18:25 impi joined #salt
18:32 elsmo joined #salt
18:33 otter768 joined #salt
18:34 akhter joined #salt
18:34 brianfeister joined #salt
18:37 shoemonkey joined #salt
18:38 Tyrm joined #salt
18:39 lompik joined #salt
18:39 Tyrm_ joined #salt
18:39 pwalsh joined #salt
18:41 larsfronius joined #salt
18:42 Bryson joined #salt
18:44 baweaver joined #salt
18:44 digitalhero joined #salt
18:45 digitalhero joined #salt
18:46 baweaver joined #salt
18:47 permalac joined #salt
18:48 shoemonkey joined #salt
18:56 cliluw joined #salt
18:56 Tyrm joined #salt
18:57 Tyrm joined #salt
18:57 virusuy joined #salt
19:00 shoemonkey joined #salt
19:02 nidr0x joined #salt
19:03 dyasny joined #salt
19:04 impi_ joined #salt
19:05 zmalone I'm considering moving to running branches directly from github.com/saltstack/salt, instead of relying on repo.saltstack.com, but github.com/saltstack/salt doesn't include bugfix versions.  For example, https://github.com/saltstack/salt/blob/2015.8/salt/version.py#L203
19:05 zmalone Can someone explain the work flow here to me?  Are those manually updated prior to rolling a repo.saltstack.com release?
19:06 zmalone Should they be updated in git for each point release?
19:06 impi__ joined #salt
19:06 alemeno22 joined #salt
19:07 impi___ joined #salt
19:07 mohae joined #salt
19:08 jfindlay zmalone: there is some logic in setup.py to try to avoid the version info paradox
19:09 jfindlay I'm not sure exactly how it works, but if you use setup.py to install (with pip, etc.) or create a 'release' archive, you should be fine
19:09 jfindlay see the note here, for example: https://github.com/saltstack/salt/releases/tag/v2015.8.3
19:10 pwalsh joined #salt
19:10 Tyrm_ joined #salt
19:11 zmalone I've got a coworker running "setup.py install" and ending up with 2015.8.0 as the "version", so I guess I'll dig in further.
19:11 jfindlay that's strange; were you running that from the HEAD of 2015.8?
19:12 zmalone Ah, got it.
19:12 zmalone His logs look like they are cloning without a branch specified, so he's getting develop
19:12 zmalone Which I'm guessing has "2015.8.0"
19:13 Tyrm__ joined #salt
19:13 jfindlay that must be the latest tag available on the develop branch
19:14 jfindlay although I thought the only tags on develop were supposed to be the tags created specifically to point to branch points 2015.5, 2015.8, etc.
19:15 jfindlay probably my fault because I'm the person who pushes release tags to saltstack/salt :-)
19:18 jimklo_ joined #salt
19:21 rem5 joined #salt
19:21 baweaver joined #salt
19:21 impi joined #salt
19:21 jimklo joined #salt
19:22 impi_ joined #salt
19:22 Bryson joined #salt
19:23 impi__ joined #salt
19:27 evle1 joined #salt
19:28 notnotpeter joined #salt
19:28 pwalsh joined #salt
19:32 babilen jfindlay: Apparently most tags are on develop also .. git branch --contains v2015.5.9 is interesting (only on 2015.8/develop and not on 2015.5)
19:33 jimklo_ joined #salt
19:34 kimball joined #salt
19:35 DammitJim joined #salt
19:36 kawa2014 joined #salt
19:36 DammitJim if I want to set up a mounted samba share from another server on a minion
19:36 DammitJim would I used mount.mounted
19:37 DammitJim or would I just create a state the updates fstab?
19:37 DammitJim that*
19:37 kimball joined #salt
19:37 DammitJim I mean, doing a state with mount.mounted doesn't make that mount automatically happen if it was disconnected and someone needed the resources, right?
19:38 jfindlay babilen: on my local repo v2015.5.9 is in the 2015.5 and 2015.8 branches
19:39 babilen jfindlay: Interesting, let me double check
19:40 jfindlay babilen: I wouldn't be surprised if I've done something wrong.  Git tags seem to always seem to beguile me, but at least I know v2015.5.9 points to the intended commit :-)
19:41 babilen jfindlay: Interesting, 54e031f is my HEAD right now and when I run "$ git branch --contains v2015.5.9" I get develop and 2015.8
19:41 babilen Looks as if you forgot a "git push --tags"
19:41 babilen I was just curious and ran through "git branch --contains $TAG" for all tags and that one was surprising
19:41 jfindlay also, I'm not quite sure what it means for a tag to be contained in a branch.  In my understanding, branches and tags are almost the same things, except that branches are different somehow
19:42 jfindlay babilen: was it only that one that was odd?
19:42 babilen Let me see
19:42 chiui joined #salt
19:43 jfindlay I'm loth to use `--tags` because I want to be careful push the single tag
19:44 berserk joined #salt
19:45 jfindlay DammitJim: mount.mounted also updates fstab, I think
19:45 DammitJim oh yeah!
19:45 DammitJim persist something
19:46 babilen jfindlay: I totally understand, let me paste some output ... I take it that releases earlier than two years ago aren't really that interesting anymore
19:49 babilen jfindlay: https://www.refheap.com/113924 -- Around 2014.7 tags appears on more branches than the one that pertains to that release, v2015.2 is not on the 2015.2 branch (not surprising), v2015.5.9 is missing on 2015.5 and the rest looks fine
19:50 babilen Looks as if 2015.9 is the odd one out
19:50 babilen 2015.5.9 that is
19:52 larsfronius joined #salt
19:53 akhter joined #salt
19:55 jfindlay interesting because I did a plain `git push upstream v2015.5.9` just as with previous tags
19:56 nyx_ joined #salt
19:56 linjan joined #salt
20:00 ageorgop joined #salt
20:01 job joined #salt
20:02 job why isnt PR 29587 in https://docs.saltstack.com/en/2015.5/topics/releases/2015.5.9.html
20:02 babilen jfindlay: *shrug* -- I was just curious and took a closer loos :)
20:02 job or #29585
20:06 digitalhero joined #salt
20:06 digitalhero joined #salt
20:07 babilen s/loos/look -- haha
20:08 Tyrm joined #salt
20:10 elsmo joined #salt
20:11 neogenix joined #salt
20:12 giantlock joined #salt
20:13 jfindlay job: that was merged into develop.  All release branches flow into develop rather than the other way around
20:13 jfindlay wait, sorry, it looks like it was backported
20:14 job yeah it was
20:14 iamtew joined #salt
20:15 keimlink joined #salt
20:15 jfindlay it was backported to 2015.8, and not further back to 2015.5
20:15 jfindlay it should come out with 2015.8.4
20:17 job ahh
20:17 job thanks!
20:17 RabidCicada joined #salt
20:18 alemeno22 joined #salt
20:19 jfindlay that should be coming out next week
20:19 jfindlay or the week after
20:20 jfindlay but next week is more likely
20:20 babilen jfindlay: Do you have a second (re: packaging) ?
20:20 ajw0100 joined #salt
20:21 jfindlay sure
20:21 job jfindlay, it wasnt immediately clear to me that the new 2015.5.9 is a maint release on an older series
20:22 jfindlay yeah, I was confused for a second too :-)
20:24 brianfeister joined #salt
20:26 lemur joined #salt
20:29 alemeno22 joined #salt
20:29 digitalhero joined #salt
20:30 digitalhero joined #salt
20:30 digitalhero joined #salt
20:30 dariusjs joined #salt
20:31 digitalhero joined #salt
20:32 digitalhero joined #salt
20:32 neogenix joined #salt
20:33 digitalhero joined #salt
20:34 otter768 joined #salt
20:34 teryx510 joined #salt
20:34 digitalhero joined #salt
20:34 alemeno22 joined #salt
20:35 digitalhero joined #salt
20:35 murrdoc joined #salt
20:36 digitalhero joined #salt
20:37 digitalhero joined #salt
20:37 digitalhero joined #salt
20:38 digitalhero joined #salt
20:39 berserk joined #salt
20:39 digitalhero joined #salt
20:39 akhter_1 joined #salt
20:39 berserk joined #salt
20:40 digitalhero joined #salt
20:41 shoemonkey joined #salt
20:41 digitalhero joined #salt
20:42 alemeno22 joined #salt
20:42 nidr0x joined #salt
20:48 akhter joined #salt
20:50 NightMonkey joined #salt
20:51 baweaver joined #salt
20:52 akhter_1 joined #salt
20:56 subsigna_ joined #salt
20:56 akhter joined #salt
20:56 mapu joined #salt
20:58 akhter_1 joined #salt
21:03 impi joined #salt
21:08 shoemonk_ joined #salt
21:08 slav0nic joined #salt
21:10 mpanetta joined #salt
21:11 digitalhero joined #salt
21:12 digitalhero joined #salt
21:12 digitalhero joined #salt
21:13 denys joined #salt
21:14 digitalhero joined #salt
21:14 digitalhero joined #salt
21:15 digitalhero joined #salt
21:16 digitalhero joined #salt
21:17 digitalhero joined #salt
21:18 digitalhero joined #salt
21:18 neogenix joined #salt
21:18 atmosx {% if openssh.server is defined %} <-- what does 'defined' mean? where is a service 'defined' ?
21:19 hightekvagabond joined #salt
21:19 digitalhero joined #salt
21:20 iggy it's a variable
21:20 gtmanfred if it is set to anything, None a string, a dictinoary, anything at all, will result as true
21:20 jfindlay atmosx: it's python-like code, think of it as `if openssh.server == defined`
21:20 hightekvagabond I have a piece of information that is generated on one of my minions, when that info changes I need to take it down to the master and add it to a config file for all the others. Is there a method to do this?
21:20 gtmanfred it is closer to hasattr(openssh, 'server') in python
21:20 gtmanfred jfindlay: ^^
21:21 digitalhero joined #salt
21:21 gtmanfred because it won't fail if it isn't defined, which it would in your example, assuming there isn't @property magic in teh background
21:21 digitalhero joined #salt
21:21 iggy hightekvagabond: salt mine maybe?
21:22 jfindlay gtmanfred: don't be afraid to assume I'm not as intelligent as I seem :)
21:22 gtmanfred <3
21:22 digitalhero joined #salt
21:23 digitalhero joined #salt
21:24 digitalhero joined #salt
21:25 digitalhero joined #salt
21:26 ALLmightySPIFF joined #salt
21:26 digitalhero joined #salt
21:27 digitalhero joined #salt
21:27 atmosx I want to comment out from sshd every lines containing the world 'dsa'. I see this as an example:  - regex: ^//10.10.20.5
21:27 atmosx - regex: ^//dsa   will do?
21:27 digitalhero joined #salt
21:27 atmosx under file.comment:
21:28 digitalhero joined #salt
21:29 digitalhero joined #salt
21:30 digitalhero joined #salt
21:31 digitalhero joined #salt
21:31 netcho_ joined #salt
21:32 digitalhero joined #salt
21:32 digitalhero joined #salt
21:33 grumm_servire joined #salt
21:33 jimklo joined #salt
21:34 shoemonkey joined #salt
21:50 Rumbles joined #salt
21:57 shoemonkey joined #salt
22:00 twork so... i'm about shin-deep into some bonehead shell scripts that run '[ minion ] state.highstate test=True', pipe that through txt2html (or whatever), and post the results for Them to look over at their leisure. and i'm starting to think, there has to be a better way.
22:00 twork or many, many better ways.
22:01 whytewolf twork: anything sounds beeter then that.
22:01 twork doesn't it?
22:02 twork there are always catches. for instance, i would like to subdivide minions, subdivide (maybe) the portions of the state that gets displayed [here] or [there]
22:02 whytewolf put the output to json and use some json formatting tools. change the state_output to changes so that only things that are being changed make any kind of waves
22:03 twork that sounds like a good clue
22:03 whytewolf buy the enterprise version and gets salts gui
22:03 geekatcmu Use a returner, ship the data to ES, PROFIT
22:03 whytewolf ^^^
22:03 geekatcmu Or Splunk
22:03 whytewolf dump it to a database
22:04 twork don't make me weep.
22:04 * geekatcmu pokes the bear some more
22:05 * twork turns pockets inside out
22:05 twork though, splunk...
22:05 tercenya joined #salt
22:07 whytewolf dump the raw data to a printer, and pay a homeless man to read the data back.
22:08 twork with a british accent?
22:08 whytewolf need scottish or welsh
22:08 twork scottish i'll take.
22:08 whytewolf but german with anything that says ERROR
22:09 twork naturlich
22:10 whytewolf oh, smtp returner and have everything CCed to the CEO
22:10 twork YES
22:10 twork ...to be printed out there
22:10 baweaver joined #salt
22:12 iggy CEOs love paper
22:12 whytewolf and they love being kept in the loop
22:12 twork don't laugh
22:12 twork have a story... but, not today
22:12 whytewolf i think we all have stories of "That" ceo
22:13 twork mine involves fire!
22:13 brianfeister joined #salt
22:13 geekatcmu Have your return ship the data to the NSA.  Ask them for a summary.
22:15 twork sysadmins adore fire.
22:15 berserk joined #salt
22:15 whytewolf so do printers
22:18 GreatSnoopy joined #salt
22:19 Pie_Mage geekatcmu: make sure you redact all the important stuff... don't do their job for them of course!
22:20 geekatcmu But if you do that you can't count it as your off-site backup when the auditors ask about that.
22:20 Pie_Mage the data is there... just highly encrypted
22:20 Pie_Mage of sorts
22:21 jfindlay that reminds me: @dnd filed an issue recently and replaced the secret info in his cloud config with hunter2, it was awesome
22:21 geekatcmu "What's your backup strategy?"  "Litter words like 'terrorist', 'WMD', and 'nuclear' throughout or code, data, and documentation and let the NSA manage it."
22:21 whytewolf geekatcmu: thats why send the redacted information to the FBI. while redacting the information that the NSA got was redacted in their copy
22:21 jfindlay https://github.com/saltstack/salt/issues/30432#issuecomment-172924353
22:21 saltstackbot [#30432]title: Cloning linode server with salt-cloud requires payment term | I'm using 2015.8.3, and when trying to clone a node, I get the error:...
22:21 geomacy joined #salt
22:21 jfindlay and https://web.archive.org/web/20150602093855/http://www.bash.org/?244321%29 if you don't know what hunter2 is (or should I say ******?)
22:22 jfindlay it was awesome
22:22 job oh, a classic
22:22 Pie_Mage i think a ticket should be opened to get an nsa:// file backend
22:23 jfindlay nice :)
22:26 atmosx hmmm to restart ssh after editing the file, the synatx with: ssh ?
22:28 twork whytewolf: (or whoever) speaking of state_output, i was meaning to ask: previously my poking has led me to believe that state_verbose and state_output only counted in the master config file, couldn't be specified at the command line. once again... that cannot be true, but config file is the only way i've been able to make them work.
22:30 berserk joined #salt
22:30 twork earlier i was scripting up a couple different calls to the salt master, where the only differences were config files that set those differently
22:31 twork was i on the right track with those, or had i missed something less convoluted?
22:33 nyx_ joined #salt
22:34 Tyrm_ joined #salt
22:34 wm-bot4 joined #salt
22:35 otter768 joined #salt
22:36 brianfeister joined #salt
22:36 bhosmer joined #salt
22:37 dreardon joined #salt
22:43 mosen joined #salt
22:43 zenlot1 joined #salt
22:55 dlam joined #salt
22:55 snarfy joined #salt
22:55 digitalh_ joined #salt
22:55 dlam hmm what do i google to find what you can put  under  - require:   thingys?   i cant find it
22:55 jfindlay requisites?
22:56 digitalh_ joined #salt
22:56 dlam yeah i wanna see what i can specify,  like -id or something
22:56 snarfy yo yo. is there some documentation on what variables i can use in a custom salt bootstrap script?
22:57 dlam like its here https://docs.saltstack.com/en/latest/ref/states/requisites.html  but i don't think it lists all the options, but mayb im noob
22:57 akhter joined #salt
22:58 dendazen joined #salt
22:59 baweaver joined #salt
23:00 iggy dlam: <module>: <ID>
23:00 iggy so any id anywhere in your states
23:02 tmkerr joined #salt
23:02 ajw0100 joined #salt
23:08 starman_ joined #salt
23:08 starman_ left #salt
23:10 ALLmightySPIFF joined #salt
23:14 digitalhero joined #salt
23:15 ronrib joined #salt
23:17 digitalh_ joined #salt
23:18 dlam ooo thanks thanks
23:21 digitalhero joined #salt
23:25 subsignal joined #salt
23:26 brianfeister joined #salt
23:26 digitalhero joined #salt
23:28 dlam hmm i get like "The following requisites were not found"  when i try it (https://gist.github.com/dlam26/90130f58face44068da6)  not sure hmm
23:29 dlam (if anyone be bored :D)
23:29 whytewolf pkg. not app
23:30 whytewolf the module is pkg
23:30 dlam !!!  thanks whytewolf that worked
23:30 whytewolf np
23:32 shoemonkey joined #salt
23:41 nyx_ joined #salt
23:45 Pie_Mage is it possible to use something different than yaml + jinja for building pillar data?
23:46 AlberTUX joined #salt
23:46 whytewolf Pie_Mage: https://docs.saltstack.com/en/latest/ref/renderers/ or you can even start using ext_pillars https://docs.saltstack.com/en/latest/topics/development/external_pillars.html
23:50 jtylers joined #salt
23:54 drawsmcgraw left #salt
23:56 adelcast joined #salt
23:57 digitalhero joined #salt

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