Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2015-11-19

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

All times shown according to UTC.

Time Nick Message
00:00 mdupont joined #salt
00:00 kevin-wk no, i'm back where i started.  state.show_sls renders, state.sls says failed to render.  the pillar item no longer has a - in the name.
00:00 alibama joined #salt
00:01 hemebond Can you paste errors and code?
00:01 kevin-wk hemebond: i tested these states successfully on multiple machines earlier today, then found this behavior only on CentOS 7/Salt 2015.5.5
00:01 kevin-wk hemebond: https://gist.github.com/kevins9/4cc0460a3e4b4590f163
00:02 hemebond So 2015.5.3 works but 2015.5.5 fails.
00:02 kevin-wk that's what it looks like so far
00:02 hemebond You have hyphens in your filenames too?
00:02 hemebond Oh, maybe not...
00:03 kevin-wk maybe in the pillar sls filenames - but they are working just fine on all systems
00:03 hemebond The working state could have been a bug :-)
00:03 * kevin-wk cries
00:04 kevin-wk ha
00:05 hemebond Just FYI: https://github.com/saltstack/salt/issues/28161
00:05 saltstackbot [#28161]title: Problems with having a hyphen in a pillar name | I had a pillar with a hyphen in the name that would fail to resolve in a state. ...
00:05 kevin-wk seems highly peculiar to me that state.show_sls would work but state.sls says it can't render.  I've made plenty of mistakes today that I knew were my fault (and I was right because I fixed them!)
00:06 kevin-wk OK, I'm going to try changing the filenames in the pillar and the pillar top.sls
00:07 kevin-wk though i use dashes a lot and never had problems
00:08 kevin-wk no luck :(
00:08 hemebond Where is config/sssd.sls?
00:08 kevin-wk on this system, /srv/salt/dev/config/sssd/init.sls
00:08 kevin-wk you can see i call saltenv=dev in every invocation
00:08 hemebond Yeah. "Could not find file from saltenv 'dev', 'salt://config/sssd.sls'"
00:09 hemebond Wondering if that's actually an error.
00:09 kevin-wk and the dev environment is configured for /srv/salt/dev
00:09 kevin-wk it normally searches that first
00:09 kevin-wk then it searches for salt://config/sssd/init.sls
00:09 kevin-wk that's just a warning
00:10 hemebond But why?
00:10 hemebond Oh
00:10 hemebond I see what you mean.
00:10 kevin-wk it says that in the output on the systems that work also
00:12 kanguru_au joined #salt
00:15 Val_ joined #salt
00:16 Val_ hey !
00:16 Val_ I have a small problem with my Jinja syntax
00:16 hemebond kevin-wk: But quoting the key in the pillar file didn't work?
00:17 hemebond Wait...
00:17 hemebond What is that contents_pillar...
00:17 hemebond oh
00:17 asco1aro Ch3LL: I replied to your comments.
00:18 asco1aro whytewolf: I replied to your comments.  Thank you both!  Still trying to find a solution though.
00:18 Val_ if someone can take a look : http://pastebin.com/6aNEiaCE
00:19 Val_ this diswork =>   {{ salt['pillar.get']['vm_eth0'](jinja_variable) }}
00:20 iggy {{ salt['pillar.get']('vm_eth0:' ~ host_server) }}
00:20 hemebond or [host_server]
00:20 hemebond Wait...
00:21 hemebond {{ salt['pillar.get']('vm_eth0')[host_server]
00:21 hemebond Got your brackets around the wrong way.
00:21 hemebond iggy's syntax is probably better though.
00:21 iggy mine won't fail if the key doesn't exist
00:21 iggy that could be a good thing or a bad thing
00:21 packeteer joined #salt
00:26 kevin-wk hemebond: sorry, got pulled away for a bit.  I tried putting quotes in the state, like - contents_pillar: 'sssdcacerts:{{ cert }}'
00:27 Waggott14 joined #salt
00:27 hemebond kevin-wk: What about in the pillar itself? that didn't help either?
00:27 kevin-wk i didn't edit my pillars, except to rename sssd-cacert to sssdcacert, and the file references similarly
00:27 hemebond And that didn't help either?
00:27 kevin-wk no
00:28 kevin-wk and i can salt-call pillar.get sssdcacert successfully on the minion
00:29 hemebond All I can think of doing is what I would do; disable everything and build up a test config, testing as I go.
00:30 Val_ Thanks for u answer
00:30 kevin-wk this works 100% on other minions, and state.show_sls works on the bad minions.  I'm getting a hunch this is a bug of some sort.
00:30 Val_ but     {{ salt['pillar.get']('vm_eth0')[host_server] }} have outage all my servers network config ^^
00:30 Val_ {{ salt['pillar.get']('vm_eth0')[host_server] }} look better
00:31 hemebond kevin-wk: Probably, but you need to find the trigger.
00:32 kevin-wk hemebond: true.  thanks for your help.  I am frustrated since I spent a long time getting it all working exactly the way I wanted, only to find it fail in unusual ways on other minions.
00:32 hemebond kevin-wk: Are you minions all running the same version?
00:32 kevin-wk I'll tear it down and see what I can figure out
00:32 hemebond (you might have answered me earlier but I missed it)
00:33 kevin-wk No.  I get salt from EPEL.  It looks like my EPEL repos have 2015.5.3 for 6 and 2015.5.5 for 7.
00:33 hemebond I see.
00:33 hemebond So an older OS and an older version of Salt.
00:34 kevin-wk correct - the older OS/Salt combo is working
00:36 Val_ https://github.com/valentin2105/Salt-Network My Network configuration using Salt
00:39 asco1aro whytewolf: for some reason I'm receiving an error, "expected the node content, but found '}'" for {% if salt["pillar.get"]('sites:'~grains['fqdn']~':nginx-redirect') == 'True' %} in my nginx state.
00:39 kitplummer joined #salt
00:39 asco1aro whytewolf: I posted an update here: https://gist.github.com/anthonyscolaro/126f8847b6186399505e
00:39 whytewolf asco1aro: so did I, you have an extra } on your endif
00:40 packeteer joined #salt
00:45 kevin-wk hemebond: I pulled out all of the pillar references in the sssd states I wrote, and the same problem lept over to the yum repo state.  I'm going to come up with a simple "hello world" style example that fails and file a bug
00:45 hemebond kevin-wk: Sounds good.
00:46 RandyT anyone have a clue as to why this ec2 provision is failing with the following error: https://gist.github.com/rterbush/4fa0fbc9d74cfcc6369a
00:46 RandyT I have a staging environment nearly identical to that that works...
00:46 asco1aro whytewolf: Amazing! It's working! Thanks!  Now I just need to figure out why the server_name: line in the nginx.conf file is completely removed instead of being either or.
00:48 kitplummer joined #salt
00:50 RandyT attempting to connect on the command line with the proper ssh key gives the following error: Received disconnect from 10.1.2.210: 2: Too many authentication failures for centos
00:50 quix joined #salt
00:51 aurynn anyone used salt-formula with salt-ssh?
00:53 aurynn I'm hitting an issue where it's telling me it can't find one of the jinja templates... which is clearly there.
00:53 aurynn and I'm probably doing something wrong
00:55 bhosmer joined #salt
00:55 iggy aurynn: yes
00:55 iggy uhh... one sec, there are a few tickets open about it
00:55 aurynn oh, I should've checked that
00:56 otter768 joined #salt
00:56 RandyT nevermind.. too many keys in my keychain...  never considered that the salt master would be using from those keys..
00:56 aurynn iggy, I found an issue for it
00:57 aurynn with a workaround
00:57 iggy good
00:57 iggy I was trying to find it
00:57 iggy guess your search-fu is better than mine
00:57 aurynn in fact you commented on this issue!
00:57 baweaver joined #salt
00:57 iggy not surprised
00:58 iggy I used to be pretty active in salt stuff
00:58 zmalone joined #salt
01:00 lorengordon joined #salt
01:02 zmalone joined #salt
01:04 intel joined #salt
01:04 asco1aro Could someone take a look at my file called nginx.files.prod.var.www.nginx.nginx.conf on https://gist.github.com/anthonyscolaro/126f8847b6186399505e?  I think that the other brackets in the file are preventing jinja from pulling pillar/grain data but I'm not getting any errors.  Instead, when the file renders on the minion, there's an empty lines where "server_name example.com;" should be.
01:06 RobertChen joined #salt
01:06 fsteinel_ joined #salt
01:06 aurynn iggy, thanks!
01:07 iggy asco1aro: my nginx file is templated with jinja and doesn't seem to have any problems
01:07 RobertChen hi
01:08 RobertChen for file.managed, source: http://xxxx,  is the hash mandatory or ?
01:08 iggy yes
01:08 aurynn if it's not it should be
01:09 iggy asco1aro: why do you have the join filter in there?
01:10 whytewolf iggy: I think that was something i usggested earlyer. when i compleatly forgot about ~
01:12 whytewolf altho. since you are testing true or false. the second test could be turned into an {% else &}
01:13 wryfi what is the proper way to make a command run only if a managed file has changed?
01:13 wryfi do i need a watcu_in statement in the file definition?
01:13 wryfi or a watch statement in the cmd.wait definition?
01:14 hemebond wryfi: if the file itself has changed or if a state was applied?
01:14 minghsieh joined #salt
01:14 wryfi if the file itself has changed
01:14 wryfi (e.g. i only want to restart networking if /etc/network/interfaces, which is managed by salt, has been changed)
01:15 minghsieh hello, everyone. just wonder if i cmd.run something, is it possible to return minion's fqdn_ip4 instead of the minion_id?
01:15 whytewolf wryfi: https://docs.saltstack.com/en/latest/ref/states/requisites.html#onchanges
01:15 jimklo_ joined #salt
01:16 wryfi ah whytewolf, ty. those little one-liners get lost in the docs. ;)
01:17 subsignal joined #salt
01:18 minghsieh for example, if i issued: salt '*' cmd.run 'ls -la /tmp'; then it would return like: minion_1:\n    <content of /tmp>\nminion_2:\n        <content of /tmp>;
01:18 wryfi whytewolf: cmd.wait or cmd.run with onchanges?
01:18 minghsieh i wonder if it could return like: 192.168.1.100:\n    <content of /tmp>\n192.168.1.101:\n        <content of /tmp>
01:19 whytewolf wryfi: I was thinking service.running. I have never used it with cmd.run or cmd.wait
01:19 wryfi ok, i'll experiment
01:20 otter768 joined #salt
01:20 asco1aro whytewolf: I tried updating the version to include the one with the ~ but it performs the same.  Further, when I swap out the elif with just {% endif %}, it only generates the second line (the line outside of the if statement.
01:21 whytewolf asco1aro: {% else %} not {% endif %}
01:22 asco1aro whytewolf: Ok great.  And I think I just realized why it wasn't changing the file. Testing now.
01:23 wryfi cmd.wait and onchanges seem to work nicely together, thanks again whytewolf
01:23 whytewolf wryfi: cool
01:24 whytewolf I think my brain is friend
01:24 whytewolf fried
01:24 whytewolf fryed
01:24 whytewolf ... dead
01:25 asco1aro whytewolf: you need a donate button. I'm doing backflips over here.  All is working properly now.
01:27 whytewolf asco1aro: nice. glad i could help
01:30 kitplumm_ joined #salt
01:30 RobertChen why for file download, hash is mandatory?
01:30 RobertChen my files are hosted by internal sites.
01:34 iggy RobertChen: the state can't know that, it errs on the safe side
01:34 kevin-wk left #salt
01:37 p404 joined #salt
01:39 p404 joined #salt
01:39 zmalone joined #salt
01:41 otter768 joined #salt
01:45 jacksontj joined #salt
01:46 RobertChen if I develop a module myself, will watch, require keyword are already available?
01:48 ahayes joined #salt
01:49 mosen I think require will be, i think watch requires an extra function
01:50 mosen mod_watch
01:58 RobertChen if a file is changed, then do something first? and then do something after?  How to implement this pre-event, or post event handlers in salt?
02:00 malinoff joined #salt
02:02 wryfi left #salt
02:06 kitplummer joined #salt
02:11 larsfronius joined #salt
02:14 qman__ joined #salt
02:20 Xevian_ joined #salt
02:23 londo__ joined #salt
02:23 rubenb joined #salt
02:23 Ludo__ joined #salt
02:24 Rkp joined #salt
02:24 freelock joined #salt
02:24 stickmack joined #salt
02:24 kbyrne joined #salt
02:24 MK_FG joined #salt
02:24 jasondotstar joined #salt
02:24 colttt joined #salt
02:24 ropes joined #salt
02:24 CSa_ joined #salt
02:24 apejens joined #salt
02:24 Heartsbane joined #salt
02:24 Riz joined #salt
02:24 blueyed joined #salt
02:24 jfred joined #salt
02:24 cswang_ joined #salt
02:25 B1nny joined #salt
02:25 oznah joined #salt
02:25 InAnimaTe joined #salt
02:25 cb joined #salt
02:25 tzero joined #salt
02:26 APLU joined #salt
02:27 fusionx8_ joined #salt
02:31 Muchoz joined #salt
02:32 Muchoz I've been trying out Ansible because my current deployment with Fabric is a pain. Ansible seems to be an even bigger pain because it can't even handle multiple python versions and virtualenvs properly. How easy is it to have a project setup with its owner user, database, python virtualenv with a specific version and server stuff (uwsgi, nginx, ufw...) installed on Salt?
02:33 murrdoc joined #salt
02:33 murrdoc sup
02:35 forrest Muchoz, I think it's easy
02:35 Muchoz Cause I see a pyenv 'module' (or state?) available in the docs forrest
02:35 forrest Muchoz, Check out this app I have running: https://github.com/gravyboat/hungryadmin-sls/blob/master/salt/hungryadmin/app.sls
02:35 forrest pyenv?
02:35 forrest you mean for a virtualenv?
02:36 Muchoz virtualenv and pyenv
02:36 favadi joined #salt
02:36 ahammond Muchoz, I've build salt formulae to install venv, code, etc. There's a few ways to do it. If the code has simple requirements, hardcoding them works fine. Otherwise, I find that dropping a requirements.txt onto the server somewhere works nicely.
02:37 forrest ahammond, Nooooob, store the requirements.txt in the repo, then do the git checkout first, then run the requirements.
02:37 forrest come on man
02:37 forrest ;)
02:37 forrest DID YOU EVEN READ THE BLOG POST I WROTE ON THIS, JEEZ SO RUDE
02:37 murrdoc no one did
02:37 forrest Ouch
02:37 murrdoc when did u start blogging
02:37 murrdoc :D
02:37 forrest That was a good burn
02:37 forrest also why are you still here murrdoc
02:37 murrdoc send links
02:37 murrdoc no reason
02:37 murrdoc came on to get some trolls in
02:37 forrest murrdoc, https://hungryadmin.com/building-a-static-blog-and-deploying-it-with-saltstack.html
02:37 murrdoc then bounce
02:38 forrest it's the one I wrote from 2013
02:38 forrest I updated it a few months ago
02:38 Muchoz Salt's server-only means SSH only and nothing needs to be preinstalled on the remote server, right?
02:38 murrdoc well
02:38 murrdoc ssh keys
02:38 catpiggest joined #salt
02:39 murrdoc blog is actually legit forrest
02:39 Muchoz Ya besides that of course
02:39 forrest Muchoz, Yeah, when you run it like that you have two options. A: Translate everything to bash via flags, B: Install a tmp salt minion into tmp (which will get trashed, again with flags)
02:39 murrdoc minimum python 2.6
02:39 forrest Muchoz, Keep in mind that this means runs are kind of slow (though they do work in parallel) because it's gotta translate/dump everything on. And by 'slow' I mean compared to normal salt
02:39 forrest I'd still take that any day over ansible
02:39 Muchoz https://docs.saltstack.com/en/getstarted/fundamentals/index.html
02:39 RobertChen joined #salt
02:39 Muchoz This get started guide is glorious compared to Ansible
02:40 Muchoz Oh damn
02:40 Muchoz forrest, meh. I'm used to long compile or deploy times
02:40 forrest Muchoz, I'm glad you like it, the Salt guys worked pretty hard on it, jfindlay let Jacob know someone likes the getting started guide!
02:40 Muchoz I don't really care about long deploy times really
02:40 forrest Muchoz, Yeah it's not even THAT slow
02:41 Muchoz I'll start tomorrow
02:41 Muchoz 3:41AM atm
02:41 forrest it's just slower than normal salt, so for those of us who usually use normal salt it's brutal
02:41 forrest Muchoz, lol
02:41 forrest Muchoz, oh before you go
02:41 Muchoz I generally work till pretty late
02:41 forrest Muchoz, https://github.com/gravyboat/salt-ssh-example I created an example salt-ssh repo
02:42 Muchoz Quick questioj
02:45 Muchoz n
02:45 forrest So you should be able to just git pull that, dump your servers in there (that have keys obviously) and start working. It expects a venv
02:45 Muchoz So can I completely start from a bare server besides ssh keys
02:45 Muchoz Disable root, create sudo account and then go from there?
02:45 forrest Yeah
02:45 Muchoz Create a new user for the project and then always use that one...
02:45 Muchoz Oh thank god
02:45 forrest Muchoz, Well, you want to usually run the commands as root, I haven't tried salt-ssh with a non-privilege user.
02:45 forrest I don't see how it would work, but maybe.
02:45 Muchoz Well I generally stay away from root
02:45 forrest Muchoz, How would the ssh user install packages then if the server is just blank?
02:45 Muchoz forrest, quote on quote "blank"
02:45 forrest hah okay
02:45 Muchoz Most of the linux distros come with ssh installed
02:45 forrest Muchoz, well, I mean python/pip and such
02:45 forrest to virtualenv a local dir like you want
02:45 forrest or create system users, etc.
02:46 ilbot3 joined #salt
02:46 Topic for #salt is now Welcome to #salt | 2015.8.1 is the latest | Please use https://gist.github.com for code, don't paste directly into the channel | Please be patient when asking questions as we are volunteers and may not have immediate answers | Channel logs are available at http://irclog.perlgeek.de/salt/
02:46 Muchoz Sweet
02:47 forrest Muchoz, https://docs.saltstack.com/en/latest/topics/ssh/#salt-ssh-roster
02:47 forrest Just make sure you set the sudo flag for the associated server, and use that repo I linked you so you don't have to waste time on your local system setting up all the stupid config files/dirs.
02:47 forrest I wasted time so no one else had to DAMMIT!
02:48 writtenoff joined #salt
02:49 Muchoz forrest, bookmarked it for "tomorrow" thank you
02:49 forrest Muchoz, You got it, I'm out of here, any last questions before I bounce?
02:50 favadi joined #salt
02:50 Muchoz I'll be here tomorrow most probably
02:50 forrest Alright later.
02:50 Muchoz But I've got some other shit to do first
02:55 aidalgol left #salt
02:55 bhosmer joined #salt
03:00 quix joined #salt
03:07 Muchoz Read through the getting started
03:08 Muchoz Goodnight for now
03:15 ageorgop joined #salt
03:19 hasues joined #salt
03:19 kitplummer joined #salt
03:25 hal58th joined #salt
03:25 hal58th_ joined #salt
03:26 hasues left #salt
03:28 mik__R joined #salt
03:31 bernieke joined #salt
03:33 sunkist joined #salt
03:34 RobertChen if a file is changed, then do something first? and then do something after?  How to implement this pre-event, or post event handlers in salt?
03:34 jaybocc2_ joined #salt
03:39 timoguin joined #salt
03:40 nickermire joined #salt
03:41 hemebond RobertChen: You might need to rethink your process.
03:41 timoguin_ joined #salt
03:41 hemebond Or put together a better explanation.
03:41 RobertChen probabaly use onchanges ?
03:43 timogui__ joined #salt
03:45 mik__R joined #salt
03:46 PeterO_ joined #salt
03:48 cpattonj joined #salt
03:52 armyriad joined #salt
04:01 nafg_ joined #salt
04:03 sunkist joined #salt
04:09 racooper joined #salt
04:21 otter768 joined #salt
04:56 anonymous joined #salt
04:56 bhosmer joined #salt
05:11 clintberry joined #salt
05:17 RobertChen joined #salt
05:22 cyborg-one joined #salt
05:22 kitplummer joined #salt
05:34 rdas joined #salt
05:45 jimklo joined #salt
05:51 evle joined #salt
05:54 gora joined #salt
05:58 favadi joined #salt
05:58 impi joined #salt
06:02 calvinh joined #salt
06:02 nidr0x joined #salt
06:06 xDamox joined #salt
06:10 armguy joined #salt
06:13 jalbretsen joined #salt
06:13 larsfronius joined #salt
06:22 otter768 joined #salt
07:05 RobertChen joined #salt
07:21 Andre-B joined #salt
07:22 AndreasLutro joined #salt
07:24 kitplummer joined #salt
07:28 DanyC joined #salt
07:39 KermitTheFragger joined #salt
07:43 impi joined #salt
07:49 Bryson joined #salt
07:51 elsmo joined #salt
07:51 Waggott14 Hi does anyone have decent config for Jekyll?
07:54 Pixionus joined #salt
07:56 linjan joined #salt
08:02 eseyman joined #salt
08:12 denys joined #salt
08:20 peppers joined #salt
08:23 otter768 joined #salt
08:27 GreatSnoopy joined #salt
08:27 ageorgop joined #salt
08:32 Guest71482 joined #salt
08:36 imanc joined #salt
08:37 Grokzen joined #salt
08:42 MK_FG joined #salt
08:43 RobertChen joined #salt
08:46 informant1 joined #salt
08:47 kawa2014 joined #salt
08:50 Rumbles joined #salt
08:54 s_kunk joined #salt
08:57 malinoff joined #salt
08:58 bhosmer joined #salt
09:00 thefish joined #salt
09:02 zerthimon joined #salt
09:03 tkharju joined #salt
09:06 antpa joined #salt
09:06 liskl joined #salt
09:07 Waggott14 Hi does anyone know how to setup jekyll succesfully in a state file?
09:08 claque2000 joined #salt
09:08 claque2000 hello
09:09 claque2000 I got an issue with orchestration : an sls has been created with require between each step and when I deploy it, each step is returned to be completed after 10 seconds
09:10 slav0nic joined #salt
09:10 claque2000 but it's not the case because the deployment on each server continues
09:10 Norrland Waggott14: ask your question and hang around. No need to repeat yourself.
09:10 claque2000 is this case known ?
09:11 Norrland Waggott14: maybe provide more information in a hastebin about what you're having problem with
09:11 Waggott14 sorry Norrland i assumed it would drop off somewhere
09:11 asco1oar joined #salt
09:12 rotbeard joined #salt
09:13 antpa Is there any way to check a jinja template prior to applying a stae?
09:14 antpa like a built in validation tool from salt?
09:14 claque2000 using test=True no ?
09:14 antpa I wish there were a tool that allowed me to specify the template to validate instead of having to run through the entire process.
09:15 antpa like something similar to composer validate
09:18 Andre-B joined #salt
09:18 thalleralexander joined #salt
09:19 antpa In any case, this is the error message I'm receiving.  I think the syntax is correct but it keeps throwing the same error no matter the edits I make:  https://gist.github.com/anthonyscolaro/153e6d0c3537d9d29430
09:21 AndreasLutro you're missing an endif
09:21 claque2000 you got 2 if but only 1 endif
09:22 AirOnSkin joined #salt
09:24 antpa Too easy :)  I'm officially tired...
09:25 babilen Waggott14: You would just automate with salt what you would do manually .. You might want to work on installing it first, maybe? Take a look at pkg.installed and, if applicable, pkgrepo.managed for that. Configuration files might also be needed so look into file.managed. I'd investigate formulas for inspiration on how to do this in a nice way (e.g. salt-formula)
09:26 kitplummer joined #salt
09:29 felskrone joined #salt
09:30 MadHatter42 joined #salt
09:31 RobertChen joined #salt
09:31 elsmo joined #salt
09:35 keimlink joined #salt
09:48 RobertChen joined #salt
09:50 N-Mi_ joined #salt
09:52 bluenemo joined #salt
09:56 evanlivingston joined #salt
09:56 evanlivingston Hey all
09:57 evanlivingston I'm wondering how to cause salt to render jinja files
10:02 larsfronius joined #salt
10:05 denys joined #salt
10:06 hemebond evanlivingston: template: jinja
10:07 hemebond It's usually automatic though.
10:07 larsfronius joined #salt
10:08 mohae joined #salt
10:11 kawa2014 joined #salt
10:14 AlberTUX1 joined #salt
10:20 huddy joined #salt
10:20 losh joined #salt
10:22 slav0nic joined #salt
10:22 krak3n` joined #salt
10:23 krak3n` Morning guys :) was wondering if it's possible to target just 1 minion from a group, say I have 3 web servers (I don;t know their id's since they are auto scaled) and I want to run an sls on just one of the three, whats the best way to target?
10:24 otter768 joined #salt
10:24 giantlock joined #salt
10:27 DanyC joined #salt
10:29 AndreasLutro krak3n`: specify the exact minion name
10:31 krak3n` i won't know their names, they will be part of auto scale groups so their names come and go dynamically, i'll only be able to target them by role (a grain), i guess i'll just have to get a list of minions that match the role and pick one at random
10:32 Azid joined #salt
10:36 bougie joined #salt
10:36 bougie hi
10:39 bluenemo joined #salt
10:40 krak3n` answered my own question :) sudo salt '*' --subset 1 test.ping
10:41 MadHatter42 joined #salt
10:41 CeBe joined #salt
10:45 antpa What is the proper way to require a user to be present before a state may run for a managed file?
10:45 babilen antpa: Require the user.present state for that user
10:45 rubenb Hi, is there a salt variable you can use in states that return the current state name?
10:46 rubenb like {{ sls }}, but then for the statename  _in_ the sls.
10:46 antpa babilen: I'm getting different errors when I try to do that...  Invalid requisite type 'user.present' in state. Requisite types must not contain dots, did you mean 'user'?
10:47 antpa babilen: And when I tried a different way, I received: State 'nginx.packages' in SLS 'nginx.extraswp' is not formed as a list for a pkg install state.
10:47 babilen antpa: Yeah, you would use "require: - user: $NAME_OR_ID_OF_USER_PRESENT_STATE
10:47 babilen So, "require: - user: babilen" for example
10:48 giantlock joined #salt
10:48 fredvd joined #salt
10:49 RobertChen joined #salt
10:50 antpa babilen: I thought that was the first thing I tried.  I'll try again.
10:52 shiriru joined #salt
10:53 rubenb Otherwise, is there a complete list of salt variables available you can use in states?
10:54 bougie how can I run a runner from salt api ? I don't unterstand how to use /run (and I think it's realy for this use case) and there is no url to launch a command
10:54 antpa babilen: thanks a lot.  it's working now
10:54 bougie Do I have to use reactor system ?
10:58 malinoff_ joined #salt
10:58 bhosmer joined #salt
10:59 babilen bougie: salt.saltutil.runner(runner_name, ...)
11:00 babilen https://github.com/saltstack/salt/pull/27096/files exemplifies that for mine.get (cf. https://docs.saltstack.com/en/develop/ref/runners/all/salt.runners.mine.html )
11:00 saltstackbot [#27096]title: Add note about retrieving Mine data from Pillar & Orchestrate | Closes #11509
11:01 marcinkuzminski joined #salt
11:01 sinonick joined #salt
11:02 mohae joined #salt
11:02 Jimlad joined #salt
11:02 daemonkeeper joined #salt
11:03 slav0nic joined #salt
11:07 felskrone1 joined #salt
11:08 amcorreia joined #salt
11:08 markm joined #salt
11:09 vape left #salt
11:14 tuxx hey guys.. how can i use modules in sls files?
11:14 tuxx i can do "salt '*' mysql.db_create 'bla'"
11:14 AndreasLutro tuxx: first look to see if there are states that do what you want
11:14 tuxx but i cant use the same module in sls
11:15 Waggott14 babilen: Thanks i will give it a try, i am very new to salt so still have much to learn
11:15 tuxx AndreasLutro: well i want to provision mysql... i only found states that support mysql_database.present
11:15 tuxx but i need stuff like user creation etc.. how can i do that?
11:15 tuxx i cld maybe run commands.. but it seems ugly
11:15 AndreasLutro https://www.google.com/search?q=salt+mysql+state
11:15 AndreasLutro leads to https://docs.saltstack.com/en/latest/ref/states/all/salt.states.mysql_user.html
11:15 AndreasLutro and others
11:15 tuxx oh damn.. yea
11:16 tuxx okay thanks... i only just noticed that modules cant be used in state files so easily
11:16 AndreasLutro they can, with module.run, but you normally should avoid it
11:16 tuxx i see
11:19 the_drow joined #salt
11:19 the_drow Is there a public API for loading an sls file into a dictionary?
11:27 viq joined #salt
11:28 _Cyclone_ joined #salt
11:30 kitplummer joined #salt
11:31 bezaban joined #salt
11:39 Xevian joined #salt
11:54 joshin joined #salt
11:54 joshin joined #salt
11:55 Waggott14 joined #salt
12:00 daemonkeeper joined #salt
12:07 permalac joined #salt
12:13 fredvd joined #salt
12:22 favadi joined #salt
12:25 otter768 joined #salt
12:28 Rumbles joined #salt
12:30 giantlock joined #salt
12:48 N-Mi_ joined #salt
12:49 alibama joined #salt
12:52 felskrone joined #salt
12:55 rotbeard joined #salt
12:56 RandyT good day, can anyone tell me if it is possible to specify a single state file to execute on the command line?
12:56 RandyT so execute everything in a specific file.
12:56 AndreasLutro RandyT: state.apply name.of.sls
12:56 RandyT AndreasLutro: excellent, thank you
12:58 lloesche joined #salt
12:58 giantlock joined #salt
13:08 Azid joined #salt
13:08 beardedeagle joined #salt
13:11 _JZ_ joined #salt
13:13 antpa I would like to automatically generate SSH keys for a use when I run the initial highstate but not on future highstates...  How could I use the onchanges requisite to prevent it from regenerating keys in the future by accident?  Or should I use another state for the initial highstate to generate ssh keys??
13:13 mage_ what's the difference between state.apply and state.sls ?
13:13 hoonetorg_ joined #salt
13:14 AndreasLutro mage_: none - state.apply is a shortcut to both .highstate and .sls
13:14 mage_ ok :)
13:14 AndreasLutro antpa: you could use - unless: test -f /path/to/ssh_key
13:19 mik__R joined #salt
13:19 alibama joined #salt
13:24 antpa AndreasLutro: I'm testing this out now but I'm receiving an error.
13:24 antpa https://gist.github.com/anthonyscolaro/9b868a941e6005feaa74
13:24 antpa AndreasLutro: state 'deploy' in SLS 'users.deploy' is not formed as a list
13:27 higuita hi! on debian, pkg.install some-package will ask to replace config files... is there any way to say N
13:28 higuita right now it leaves the dpkg in a broken state, with a incomplete instalation
13:30 tristianc joined #salt
13:31 calvinh joined #salt
13:32 kitplummer joined #salt
13:32 Segfault_ is it possible to add a line to top.sls that say "Every minion EXCEPT <something>*" ?
13:33 scoates joined #salt
13:36 Norrland Segfault_: like 'prod.* and not prod.foo': ?
13:36 Norrland Segfault_: even possible with 'foo.* and not G@roles:bar'
13:37 Segfault_ Ah, thanks. I assumed it was possible, but I couldn't figure out how
13:38 kshlm joined #salt
13:38 Norrland np
13:38 Segfault_ G@, that's the same as doing "- match: grain" ?
13:39 Norrland yes. G@roles matches the roles grain for example.
13:39 Norrland using both minion_id and grains in the top.sls, you have to use "match: compound"
13:39 RandyT How would I apply a specific state ID from a state file at the command line?
13:40 cpattonj joined #salt
13:40 TooLmaN joined #salt
13:42 cpattonj_ joined #salt
13:44 rubenb RandyT: salt hostname state.sls state ?
13:46 babilen state.apply or state.sls_id
13:47 babilen RandyT: You *really* might want to take a look at the docs! https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.state.html
13:49 alibama joined #salt
13:50 subsignal joined #salt
13:51 RandyT babilen: thanks, I have looked at the docs... was struggling with state.apply. and state.sls but missed state.sls_id...
13:51 RandyT something new every day...
13:52 ssplatt joined #salt
13:53 felskrone joined #salt
13:53 nemzes joined #salt
13:56 ITChap joined #salt
13:57 jeddi joined #salt
13:58 darix if you run with syndic. do you host the syndic process on another machine as the master?
14:00 brianfeister joined #salt
14:02 mpanetta joined #salt
14:07 zzzirk joined #salt
14:09 xmj joined #salt
14:09 xmj moin
14:09 xmj does salt these days batch pkg.installed states together?
14:09 xmj viq: you might know that
14:10 danielcb hi, does anyone know if theres a state/module for manage the windows certificate store? for example to add client certificates for a user
14:13 RandyT xmj: it is my understanding that if you provide the package names in a - pkgs: list, it batches the install
14:13 xmj oh derp
14:16 bougie i cannot launch a runner from rest api with cherrypy. i always have a 401 unauthorized error (even on a jobs.active)
14:17 scubahubby joined #salt
14:17 xmj RandyT that'd do it
14:17 xmj thanks
14:18 irctc845 joined #salt
14:22 claque2000 got a strange problem with orchestrate : sometimes the orchestrate recipe is played correctly, sometimes I got state completed in logs 10 seconds after job launch
14:22 claque2000 and the job is still running on the minion
14:23 claque2000 could it be a reason for this to happen on recipes not changed for 2 weeks with a behavior totally different each day ?
14:26 otter768 joined #salt
14:31 fusionx86 joined #salt
14:32 ekristen joined #salt
14:34 morissette joined #salt
14:35 bhosmer joined #salt
14:36 masterkorp hello
14:36 masterkorp So what do you guys use to test salt states?
14:36 masterkorp i used to use kitchen-salt but its all broken
14:39 mapu joined #salt
14:39 hasues joined #salt
14:40 calvinh joined #salt
14:43 ssplatt masterkorp: kitchen-salt is what i use
14:44 masterkorp mee too, looking for alternatives
14:44 ssplatt with -P on the boostrap options
14:44 winsalt joined #salt
14:46 masterkorp yeah, i've discovered that
14:47 masterkorp but ubuntu 15.04 were broken for me until recently
14:47 perfectsine joined #salt
14:48 LtLefse joined #salt
14:50 ITChap joined #salt
14:50 ssplatt yeah, all of the debian repos broke for a while too
14:50 ssplatt i could only get salt cloud working by cloning the repo and then doing salt-cloud -U
14:52 ssplatt they’re doing a bunch of refactoring it seems
14:52 hasues left #salt
14:53 thalleralexander joined #salt
14:54 nemzes joined #salt
14:54 tristianc_ joined #salt
14:55 Ryan_Lane joined #salt
14:56 johtso joined #salt
15:00 clintber_ joined #salt
15:00 calvinh_ joined #salt
15:00 zmalone joined #salt
15:01 kaptk2 joined #salt
15:04 claque2000 left #salt
15:05 cpowell joined #salt
15:05 nemzes joined #salt
15:06 Songohan joined #salt
15:06 toastedpenguin joined #salt
15:08 Songohan Hello, with salt can i authorize a group of persons to manage a few minions and not all minions ?
15:09 andrew_v joined #salt
15:09 Enquier joined #salt
15:10 Enquier Anyone had any luck creating a reactor from /salt/cloud/*/created? It looks like its configured correctly but... https://gist.github.com/cgaley/fca0f351f8094988506e
15:12 mik__R joined #salt
15:19 RandyT I asked earlier about how to apply an entire state file to a specific minion. I've tried state.sls and state.apply with no love.
15:20 RandyT Do I need to specify path to this state file?
15:20 RandyT path.to.state.file
15:22 numkem joined #salt
15:23 cpowell joined #salt
15:24 sk_0 joined #salt
15:24 jacksontj joined #salt
15:24 winsalt if example.sls is in /srv/salt then "salt minion state.sls example" should be how you do it
15:25 ssplatt enquier: i got one working yesterday.
15:25 stooj joined #salt
15:26 tehsu-- joined #salt
15:28 ssplatt enquier: where do you have {{ name }} in created.sls?
15:30 tehsu-- enterprise version of salt, where can I change the password for a user for the webgui
15:30 tehsu-- i dont have access to the webgui as the person who set it up didnt leave it for me
15:32 racooper joined #salt
15:32 asco1aro joined #salt
15:32 Sketch RandyT: yes, you have to specify the path (using the . notation you would use within a state file)
15:34 kitplummer joined #salt
15:34 cwyse_ joined #salt
15:39 antpa joined #salt
15:42 scubahubby joined #salt
15:43 scubahubby Is it possible to debug salt-master with pudb?  I added "import pudb; pudb.set_trace()" but am getting "ValueError: signal only works in main thread"
15:44 StolenToast is pkg.installed supposed to raise an error if the package is already installed?  It does but I'd like it not to
15:44 StolenToast in this case I am installing from a local rpm
15:45 StolenToast I also tried pkg_verify but I guess it doesn't do what I expect
15:46 techblaze joined #salt
15:49 brianfeister joined #salt
15:49 Songohan nobody knows ?
15:49 malinoff joined #salt
15:49 Azid joined #salt
15:51 zsoftich2 joined #salt
15:51 timoguin joined #salt
15:51 Norrland Songohan: did you check the documentation for client_acl?
15:52 Songohan thx.i've found it at the moment. I'm reading it
15:53 Brew joined #salt
15:58 Songohan Norrland: It's exactly what i'm looking for :).
16:02 scoates joined #salt
16:02 tuxx hey guys
16:03 tuxx i want to have a template to generate my pkg.installed dependencies from a jinja list
16:03 tuxx http://pastebin.com/qxgi58q3
16:04 tuxx does that make sense?
16:05 winsalt That looks fine to me tuxx, although I think you can do a list of pkgs in the pkg.installed without jinja
16:06 Norrland tuxx: why not "{{ name }}: pkg.installed" ?
16:07 ssplatt install_deps:  pkg.install: -pkgs: {{ packages }}
16:07 ssplatt s/install/installed
16:07 ssplatt no loop needed
16:07 ssplatt just a list
16:07 emostar joined #salt
16:08 ssplatt so in your pillar data, just make packages: - one - two - three
16:09 illern_ joined #salt
16:15 techblaze joined #salt
16:16 kshlm joined #salt
16:20 antpa I'd like to create an if statement for a jinja template that looks at pillar data which is either True or False.  If the pillar data is True then insert 'www' into the file.  How would I go about do that?
16:20 tuxx Norrland: good point
16:23 tuxx Norrland: i'm worried that it could conflict
16:23 tuxx Norrland: e.g. if i have a service-ssh and package-ssh
16:24 tuxx antpa: the file itself could be a jinja template
16:25 tuxx antpa: and you add file.managed: - template: jinja
16:26 antpa tuxx: I've good to go on that part.  I'm just confused about how to set up the statement.  I made a gist to illustrate where I'm having difficulty.  https://gist.github.com/anthonyscolaro/0d3fe1596944dc214b4a
16:27 otter768 joined #salt
16:28 subsignal joined #salt
16:36 kitplummer joined #salt
16:36 cipher_ joined #salt
16:37 dfinn joined #salt
16:37 tehsu-- joined #salt
16:42 jalbretsen joined #salt
16:43 Xevian_ joined #salt
16:48 PeterO_ joined #salt
16:49 jimklo joined #salt
16:49 cipher_ Is there not a way to specify a specific private ip address in the profile for ec2 salt cloud for version salt-cloud 5.5.6?
16:52 ecerulm joined #salt
16:57 beardedeagle If you are using salt-cloud with openstack and you have several availability zones, how would you make it so that you could use all of them in one provider file? Can you feed availability_zone a list?
16:58 ecerulm joined #salt
16:59 ecerulm Is it a good practice to setup a master in the cloud and manage that master from another master in my laptop?
16:59 mik__R joined #salt
16:59 ecerulm I mean a master in the cloud to manage  minions that are also in the cloud
17:00 impi joined #salt
17:03 conan_the_destro joined #salt
17:03 sdm24 joined #salt
17:03 Bryson joined #salt
17:08 bluenemo joined #salt
17:08 buMPnet joined #salt
17:09 mrosedale joined #salt
17:11 mrosedale Hey everyone. I'm working with salt-api and having an issue with Jobs that seem to never end? I'm targeting about 10 machines via salt to run puppet on those machines. Total time using salt command is 2 minutes. On salt-api it just hangs until it is killed by salt-api.
17:11 mrosedale Anyone have any thoughts on that?
17:17 Norrland mrosedale: using salt to run puppet?
17:19 mrosedale Don't judge. Gotta keep my legacy code moving forward ;-)
17:23 the_drow_ joined #salt
17:23 the_drow_ Hi guys, does anyone know where can I find the entry point in salt's source code for loading sls files and parsing them?
17:28 brianfeister joined #salt
17:28 the_drow_ all I want is to compile and render state files
17:28 ajw0100 joined #salt
17:32 clintberry joined #salt
17:33 hackel joined #salt
17:34 writtenoff joined #salt
17:39 nafg joined #salt
17:39 ageorgop joined #salt
17:40 Fiber^ joined #salt
17:43 jaybocc2 joined #salt
17:44 Lionel_Debroux_ joined #salt
17:48 bhosmer_ joined #salt
17:49 foundatron joined #salt
17:49 alibama joined #salt
17:50 cpowell joined #salt
17:59 tristianc_ joined #salt
18:00 bbbryson joined #salt
18:00 baweaver joined #salt
18:00 tristianc_ joined #salt
18:02 baweaver joined #salt
18:03 spiette joined #salt
18:04 tanta_g joined #salt
18:16 ssplatt joined #salt
18:17 thalleralexander joined #salt
18:20 holler joined #salt
18:20 holler hello, how can i install a specific version of node and npm? http://dpaste.com/0GVG35X
18:22 basepi joined #salt
18:22 hal58th joined #salt
18:24 tehsu joined #salt
18:24 tehsu anyway to change the password for admin user on salt enterprise webgui in postgresql
18:25 hal58th_ joined #salt
18:28 otter768 joined #salt
18:29 antpa Does anyone have experience with salt-cloud and digitalocean?  I'm setting it up for the first time and having difficulties deploying my first minion.  I can list data from my digitalocean account via api and have created a profile but I'm not sure what command to type to actually create the minion... salt cloud.create do-debian-512 my-new-instance?
18:29 tiadobatima1 left #salt
18:32 Muchoz joined #salt
18:32 Cyisl antpa: yes
18:33 Cyisl antpa: I use salt-cloud with DO... I assume you followed the docs on the website?
18:33 antpa Cyisl: Sure, I can send to you what I have so far in gist
18:35 stanchan joined #salt
18:37 Brew1 joined #salt
18:38 antpa Cyisl: Here are my two configuration files https://gist.github.com/anthonyscolaro/f1737b1ce1b40feec75d
18:39 antpa Cyisl: I used a . instead of / when showing the filename and location
18:40 basepi joined #salt
18:41 Ryan_Lane joined #salt
18:42 mapu joined #salt
18:42 Cyisl antpa: the ssh_key_names: should be ssh_key_name: and should match the name of the key as it is listed in your DO control panel ... I assume the ssh_key_file you're pointing to is the private SSH key ... driver: should be provider:
18:42 shaggy_surfer joined #salt
18:43 Cyisl antpa: that's just looking at the cloud.providers.d/do.conf you listed... you did read the docs right?
18:43 antpa Cyisl: I had driver per the documentation but changed it when I got a warning that it was depreciated when I tried to runa  cloud command via terminal.
18:44 Cyisl antpa: otherwise your profile is called digitalocean-debian when you try to launch
18:44 antpa Cyisl: I read through the offical documentation and hunted for other documentation but it was all pretty dated
18:45 antpa Cyisl: I'll make the changes now.  Thanks!
18:46 antpa Cyisl: and yes, it's a private key
18:46 Cyisl antpa: take your pick... https://www.digitalocean.com/community/tutorials/automated-provisioning-of-digitalocean-cloud-servers-with-salt-cloud-on-ubuntu-12-04 , https://www.digitalocean.com/community/tutorials/how-to-use-salt-cloud-map-files-to-deploy-app-servers-and-an-nginx-reverse-proxy or https://docs.saltstack.com/en/2015.5/topics/cloud/digitalocean.html those are what I read and it works fine
18:47 antpa Cyisl: somewhere I saw ssh_key_names and then mentioned that you could list more than one and it was written as plural
18:47 shaggy_surfer I noticed when using pillar and having quite a few modules and just running one simple update to a file that it can take up to 3 minutes.  I also sometimes get "minion no response" sometimes.  I followed the faq's and added more threads and also am using the salt -t 60 flag to tell the server to wait 60 seconds for the response.  This seems to make the issue less problematic, but if I am pushing a lot of changes or highstates to let's say 30 servers at a
18:47 antpa Cyisl: I've read all of those. :)
18:48 antpa Cyisl: I didn't install with python as I've already installed salt-master on debian 8 using the apt repo
18:48 Cyisl antpa: maybe it accepts ssh_key_names and ssh_key_name ... I just know what I have works
18:49 Cyisl I have a single map file that launches everything I have running in DO and Linode
18:52 antpa Cyisl: Nice, I love Linode as well. Used them for years for DO.  Again, I'm able to pull data from DO.  It's the creation part that I'm hitting a wall with.
18:52 Muchoz joined #salt
18:57 antpa Cyisl: I think I'm making progress :)  Im not hiiting an error and see a "[INFO    ] Rendering deploy script: /etc/salt/cloud.deploy.d/bootstrap-salt.sh "
18:57 antpa Cyisl: thanks for the bump in the right direction... I was calling to the profile my filename before...
18:58 mik__R joined #salt
19:00 antpa Cyisl: just deployed my first minon from salt-cloud... Does it automatically run highstate on deployment?
19:03 iggy ecerulm: in my former cloudy days, I just had a minimal script for the masters that did it's bootstrap (shoved into GCE's equivalent of cloud-init)... then go from there
19:04 jaybocc2 joined #salt
19:04 ecerulm GCE?
19:04 numkem is it possible to send events from a minion without having that process being ran by root?
19:04 iggy tehsu: you should probably file a ticket with the salt guys... this is more of a community support channel (in fact the SSE employees don't come here often for fear of being mobbed)
19:05 iggy ecerulm: google compute engine
19:05 iggy numkem: if you go through all the steps to allow the minion to be run by a user... sure
19:05 iggy I think there's a page in the docs for that
19:06 numkem I meant if the minion would have some kind of auth system like the master does
19:06 numkem Or the process should talk to the master directly instead
19:07 boargod joined #salt
19:07 iggy there are a lot of master features in minions (for masterless), but I'm not sure eauth is one of those
19:07 iggy either way, your user is going to need to be able to call salt-call
19:08 iggy so, start there
19:08 ecerulm but is this something that people do, I mean is a sensible setup?. To have a master  and the minions in the cloud and then having a minion in the master machine that is controlled by a master in my laptop. Or should I just ssh into the master and do everything there. I'm looking for best practices.
19:08 numkem Alright, thanks iggy.
19:08 conan_the_destro joined #salt
19:09 iggy ecerulm: a master running on a laptop isn't going to work well
19:09 forrest joined #salt
19:09 iggy when the cloud-master-minion loses the connection because someone closed their laptop, the minion process is going to die
19:09 ecerulm : So the master has to be "on" all the time
19:10 iggy yes
19:10 metalseargolid joined #salt
19:11 ecerulm how people develop and test the states then... the just rsync the files to the master and ssh into the master to sudo salt "*" state.highstate ?
19:12 iggy well, we used git... check in to git, the master pulls that down, then manually run a highstate (or if you have it scheduled, just wait)
19:12 iggy but yeah, at some point, you are going to have to login to the master to do stuff
19:13 Muchoz Salt allows the deployment to run from Travis for example, right?
19:14 iggy salt is flexible enough, I'm fairly certain you could make it do just about anything you want
19:16 ecerulm thanks iggy
19:16 Ahlee Muchoz: yes.
19:18 denys joined #salt
19:22 iggy antpa: you can tell it to (startup_states, start_action, etc)
19:25 iggy shaggy_surfer: that's why pillar is supposed to be small, fairly light pieces of info... not huge hulking swaths of code cobbled together from 29742 stackexchange articles
19:25 * iggy work jaded
19:27 giantlock joined #salt
19:27 tawm04 joined #salt
19:29 alibama joined #salt
19:33 bhosmer__ joined #salt
19:37 forrest lol
19:39 kitplummer joined #salt
19:40 nemzes joined #salt
19:43 nemzes joined #salt
19:45 Muchoz Is there a beginner example out there explaining how to make it so the deployment is run from any computer whenever I want?
19:45 antpa Cyisl: do you know how I can add set the ID and host of the minion and the time of profile creation?
19:45 Muchoz So no constant master connection, but masterless is a bit vague to me
19:45 nemzes left #salt
19:46 antpa iggy: not sure if you just saw my question.  I've been searching for a solution on this.  I currently have it deploying high state but it would be great if I could set the id to be something different than the hostname on creation.
19:46 moeyebus Hi
19:47 moeyebus I'm having a problem using https as a source scheme for this site : https://www.zulip.com/dist/releases/
19:47 moeyebus It seems the certificate is not faulty, bu I get this error:
19:47 moeyebus Unable to manage file: [Errno 185090050] _ssl.c:344: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib
19:48 antpa salt-cloud id -p profile hostname ?
19:48 moeyebus Is there an option to ignore certificate validity?
19:49 kitplummer joined #salt
19:49 alibama joined #salt
19:55 numkem I got salt-api working with tornado but when I query it with curl I get this error in the logs: SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca
19:56 numkem it makes sens as the certificate is self generated but is there a way to bypass that
19:58 Destreyf joined #salt
20:01 baweaver joined #salt
20:03 baweaver joined #salt
20:04 Guest71482 joined #salt
20:04 ubikite joined #salt
20:04 charli joined #salt
20:06 DanyC joined #salt
20:07 DanyC hi all, i'm getting this jinja error when i apply the state. Anyone can spot anything wrong as i've run out of ideas http://hastebin.com/bofeporifi.vbs
20:08 Vynce joined #salt
20:08 DanyC_ joined #salt
20:08 DanyC_ left #salt
20:09 DanyC_ joined #salt
20:10 DanyC_ i initially thought is missing an endif block but i think is s'thing else
20:10 forrest Muchoz, Masterless would be a daemon still running on the server, for the salt-ssh stuff you'd need to have the associated key to run commands (and your salt-ssh env stuff) on ever machine you want to run it on.
20:11 forrest *every
20:11 Muchoz forrest, is there a place where it would explain how I would add salt to a python so it deploys it every time from travis or something? Or just from my local machine?
20:12 forrest Muchoz, There isn't any documentation on that as far as I know, you'd just be setting up the salt-ssh stuff on the associated machine, then setting up the jenkins 'on success' options for each build.
20:12 shaggy_surfer joined #salt
20:14 forrest DanyC_, I'd start with the endif block
20:15 forrest also, hastebin blows for formatting, what is this nonsense where it doesn't understand single quotes?
20:15 forrest DanyC_, You can see right in the error it expects the end of the block, but isn't getting that, so put that in.
20:16 Muchoz forrest, thanks. I forgot about the salt-ssh page you sent me yesterday.
20:16 forrest Muchoz, np
20:16 shaggy_surfer iggy, my pillar is small.  It's a just key value pairs for parameters that change between environments.
20:22 MTeck joined #salt
20:23 s_kunk joined #salt
20:25 mik__R_ joined #salt
20:29 otter768 joined #salt
20:31 MindDrive Seriously, Salt?  I just cleared out /var/cache/salt and you've already recreated 200,000 files in just an hour and I've barely done anything??  *sigh*
20:32 hemebond MindDrive: How big is your Salt config?
20:32 MindDrive hemebond: Very small; we currently only use Salt for remote execution.
20:32 MindDrive And it's only this one server.
20:32 hemebond Interesting.
20:32 hemebond Oh.
20:33 MindDrive We have five other Salt masters and this is the only one that has unbounded growth.
20:33 MindDrive (Two masters for each of our three environments)
20:37 MindDrive (Two masters for each of our three environments)
20:37 MindDrive *sigh* I hate OSX at times... accidental resend.
20:38 forrest MindDrive, Is it all job run info?
20:39 MindDrive forrest: Don't know how to check that.
20:39 MindDrive Restarting all the salt-minions seems to have helped.
20:40 larsfronius joined #salt
20:40 forrest well I mean inside of /var/cache/salt it should be split up so you can see what is creating so many files, the master conf supports options to limit how long jobs are stored, as wel as cached minion data, etc.
20:42 boargod2 joined #salt
20:43 ipmb joined #salt
20:44 thalleralexander joined #salt
20:47 numkem ok, I've tried again with cherrypi for salt-api and I get the same ca error... I might have to open an issue with this
20:48 numkem the doc mentions using a execution module with salt-call and while it creates some certificates, it doesn't look like its taken into account by ca-certificates as the error is still happening (I'm on ubuntu 14.04 LTS)
20:50 DanyC_ forrest: so you saying hastebin is not good for sharing the gist? i didn't see any loss of the formatting. as for the endif block (if that is the case) i just don't see where to add it as i've tried all the options i could think of
20:50 forrest DanyC_, Nah it's fine, it just annoys me that it marks part of the line as a comment
20:51 forrest DanyC_, Put the {% endif %} on line 15
20:51 DanyC_ forrest: when you say "doesn't get the block, put that in" - put it where? as imo i do have endif blocks
20:51 baweaver joined #salt
20:51 DanyC_ forrest: 2 ticks, will try and see
20:52 forrest DanyC_, I'm saying put it on line 15 after the {% elif %} to see if that causes the error to go away, also remove the secondary one from 29 or 30, then you can see if it still pops up.
20:52 DanyC_ forrest: understood, giving a try now
20:55 Muchoz The pillar walkthrough doesn't seem to explain how I have 'variables' that every host has, but with different values.
20:59 iggy MindDrive: what version of salt?
20:59 forrest Muchoz, because of your usage of salt-ssh and not a version of salt where you can set custom variables to base stuff on you're going to have to create multiple states that use different pillars
21:00 * Muchoz screams in his pillow
21:00 * forrest shrugs, downside of using salt-ssh
21:01 forrest it's not even that hard.
21:01 Muchoz Not everyone has the money to have a server for every single project and a master on top of that
21:01 forrest just either use multiple pillar files for different environments or whatever, then have states for each environment.
21:01 grumm_servire joined #salt
21:01 forrest I guess? That's always been an excuse to me, servers are cheap.
21:02 forrest If you're running mulitple projects on a single box, either the projects don't get that much traffic, or it's a beefy system. I mean there are hosting companies with 5 dollar cloud instances.
21:02 MindDrive Iggy: salt 2015.5.0 - I was planning on upgrading to 2015.8.1 though hadn't been able to finish a few things to be able to push the button.
21:02 forrest 2015.2.0 is screwed MindDrive
21:02 forrest upgrade to at least the 5.3 release I think it is now
21:02 forrest *2015.5
21:03 Muchoz forrest, I run multiple versions on a single box
21:03 MindDrive I just sync'd over the Salt RedHat repos a short while ago, just need to find time to get our configuration management system to push out the latest release.
21:04 forrest yeah inside of venvs, which is fine. But since you're not interested in using a minion you lose some functionality, which includes certain options of being able to set variables on a per server basis and base other items off of those variables.
21:04 forrest MindDrive, Cool, just saying if you run into any other issues, good chance that is why
21:04 forrest I had real problems with 2015.5.0
21:05 Aleks3Y joined #salt
21:05 MindDrive I've been wanting to upgrade for some time now, but good 'ol work has kept me way too busy.
21:06 forrest Fair enough
21:06 mik__R joined #salt
21:06 forrest Muchoz, I'm not trying to give you shit here, just being straight up with you that some functionality is going to be lost, yeah it sucks, but it's the price you pay unfortunately
21:07 Muchoz forrest, how would having a master-minion setup allow me to have per minion settings?
21:08 Muchoz I don't see the difference with salt-ssh
21:08 forrest Even if you just went masterless you can set grains: https://docs.saltstack.com/en/latest/topics/targeting/grains.html
21:08 virusuy left #salt
21:08 forrest grains are values set ON the minion in the minion conf where you can say env: \n   - test
21:09 forrest and so forth, then in your states you can base items off that, so you could do choose between different postgresql hostnames based on a grain value
21:09 forrest in salt-ssh you can do similar, but it requires you to do a bit more work, and apply states in a more granular manner.
21:10 pfallenop joined #salt
21:11 Muchoz forrest, let's say I go with masterless then. How do I make it so it stays up to date with the branch on Github and runs tests before deploying or whatever?
21:12 Muchoz I also don't see why grains aren't possible for salt-ssh
21:12 forrest Muchoz, Unfortunately right now you have to use some workarounds (google ryan lane's blog and he has some suggestions) because the reactor doesn't work on masterless.
21:12 Muchoz It's basically exactly the same but everything is on one machine
21:12 forrest Muchoz, grains are set ON the minion, in the minion conf. No minion = no minion conf = no local grains to base data on
21:12 * Muchoz cries
21:12 forrest jfindlay, On this note, do you know if Tom is going to work on the masterless reactor soon? I really want that
21:12 Muchoz Why isn't there a single decent config management thing that can do what I want?
21:13 forrest Muchoz, Because what you want is full config management without anything sitting on the system, which is hard to do
21:13 forrest how would you propose grains be set on the server without actually being set on the server?
21:13 jfindlay forrest: not that I know of
21:13 forrest jfindlay, Booo
21:13 forrest BOOOoo
21:13 Muchoz Defined like playbooks? I don't get the problem?
21:13 Muchoz Like pillars*
21:14 ajw0100 joined #salt
21:14 DanyC_ forrest: i did what you suggested (http://hastebin.com/dologekuga.vbs ) and no longer get any error however that destroyed the logic because the code from lines 10 - 14 is applied as well as 28-30.
21:14 forrest Muchoz, Yeah sure, it just doesn't exist, that could be set in the https://docs.saltstack.com/en/latest/topics/ssh/roster.html but right now it isn't, maybe an issue exists to add it.
21:15 RedundancyD joined #salt
21:15 forrest DanyC_, That's good at least that we know that's where the issue is.
21:15 DanyC_ forrest: the expected output should have been: if cloud-provider is aws then if node_type is not lon-consul then do apply lines 21-24 else 28-30
21:15 DanyC_ forrest: it sounds like elif followed by if is not supported in jinja ?
21:16 Muchoz forrest, it's like basic functionality in my book
21:16 DanyC_ forrest: all the examples i've seen on jinja doc (including nested ones) is : if ... elif ...else ...endif
21:16 DanyC_ but not if ..elif ..if ...endif ..else ..endif
21:17 forrest DanyC_, http://stackoverflow.com/questions/20134651/does-jinja2-support-nested-if-statements says it should.
21:17 hemebond A nested if should definitely be supported.
21:17 forrest which leads me to believe there is some other issue in the logic
21:17 forrest that the endif fixed.
21:17 forrest by breaking the chain
21:17 Muchoz Well fuck it, I'll stay with Fabric for now. Let it all be clunky
21:19 kitplummer joined #salt
21:19 antpa joined #salt
21:19 DanyC_ forrest: right, hmm (if i could enable more jinja debug :) )
21:22 forrest DanyC_, You and me both
21:24 ajw0100_ joined #salt
21:25 ajw0100_ joined #salt
21:28 alibama joined #salt
21:31 big_area does "salt-run --hard-crash  ..."  work the same as adding "failhard: true" to a state?
21:31 DanyC_ forrest: it seems you can add Context is: {{ show_full_context() }} into sls but then what you get out is s'thing not v useful
21:32 big_area i'm looking to run some orchestration states and need then to fail hard in certain situations
21:33 tristianc_ joined #salt
21:33 perfectsine joined #salt
21:42 michael__ joined #salt
21:42 michael__ tada
21:42 michael__ howdy
21:42 michael__ question on orchestrator
21:42 michael__ can I call mine.get?
21:42 Guest9275 keeps returning an empty
21:42 Guest9275 list
21:43 Guest9275 when searching for minions. I have tested the same function logic on a regular state and it works properly
21:43 Guest9275 but when I run it against an orchestrator state it returns null
21:43 Guest9275 any ideas
21:43 Guest9275 :/
21:45 kitplummer joined #salt
21:47 sunkist joined #salt
21:47 Vynce OK, so the top.sls applies more sls files — in /srv/salt it applies other state files, in /srv/pillar it applies other pillar files.  is there a way for other files to do that? e.g., for other state files to apply other state files, and for other pillar files to include other pillars?
21:50 Brew joined #salt
21:55 tanta_g yes, include:\n  - statename
21:55 DanyC joined #salt
21:55 tanta_g or the same for pillar
21:57 Vynce ah, cool, thanks tanta_g … who left… hm.  anybody happen to know where int eh salt docs to find more on that?
21:59 Vynce does top get re-evaluated for each minion?  e.g., does it work to have {% for val in grains.get('somelistgrain') %} ?
21:59 alibama joined #salt
22:01 Andre_ks Hi all
22:01 edrocks joined #salt
22:01 Andre_ks quick question. is the glusterfs.create salt state built into salt-master?
22:01 Andre_ks I get this error:            ID: gv_gfs0     Function: glusterfs.create       Result: False      Comment: State glusterfs.create found in sls gfs is unavailable
22:02 Andre_ks salt.modules.glusterfs.create
22:02 Andre_ks here https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.glusterfs.html
22:02 Andre_ks or do I have to install the modules?
22:03 forrest Andre_ks, Looks like it is in main line salt, did you make sure to install gluster?
22:03 Andre_ks yea, I installed glusterfs from ppa
22:03 forrest did you rerun the state to see if it works after doing the install?
22:03 Andre_ks that was successful
22:03 Andre_ks yea
22:03 Andre_ks it doesn't
22:03 RandyT is there a way to create a swapfile image in salt beyond cmd.run dd?
22:03 forrest what version of salt are you using
22:04 RandyT I've looked through the docs and am not seeing it
22:04 RandyT I have an mix of module.run, cmd.run to get there but seems this should be a more common requirement
22:04 forrest RandyT, Are you using https://docs.saltstack.com/en/latest/ref/states/all/salt.states.mount.html#salt.states.mount.swap
22:05 SubOracle joined #salt
22:05 Andre_ks forrest:  salt --version salt 2015.8.1 (Beryllium)
22:05 RandyT forrest: that is the last of 5 state ids that I have put together.
22:06 forrest RandyT, Gotcha, yeah as far as I know there's no way to do an 'all in one' creation like that
22:06 RandyT forrest: I need to create a file to swap to, mkswap, chmod, edit fstab and mount...
22:06 forrest yeah
22:06 RandyT allrighty then..
22:06 ubikite joined #salt
22:07 RandyT seems I should next learn how to develop a state. :-)
22:07 forrest Andre_ks, The state is definitely in 2015.8.1 , does glusterfs have a service that needs to be running before you can use it? My gluster knowledge is minimal
22:07 forrest RandyT, hah
22:12 nafg joined #salt
22:12 GreatSnoopy joined #salt
22:12 gimpy2938 How can you use salt to put a VLAN tag on an interface?  salt.states.network has a vlan option but only takes true/false so no idea what that is meant to do
22:13 bhosmer_ joined #salt
22:16 Andre_ks forrest: the service only runs when the volume is started.  the volume is only started after it is created...
22:17 forrest Andre_ks, Ahh, not sure then, I'd run the minion in debug mode to see if there is any additional output from that state.
22:17 Andre_ks ok
22:21 sdm24 my coworker is using salt develop version and service.running, but gets errors that the service is not found. If he manually does systemctl for his service, it works. Does anyone else have this issue?
22:24 ubikite joined #salt
22:24 brianfeister joined #salt
22:25 ubikite joined #salt
22:25 forrest sdm24, "my coworker is using salt develop version"
22:25 forrest Assume all the things are broken
22:25 forrest Did he already start it in debug log mode?
22:25 eliasp if one's using "develop", he should also be able to debug + fix it…
22:25 eliasp otherwise, stick to a release
22:25 sdm24 yeah he should. instead he wants me to ask on here
22:26 forrest Well tell him to stop being a noob and start debugging.
22:26 sdm24 I'm trying to humor him until he posts a issue
22:26 forrest did he even start the service with debug logging?
22:26 forrest That should give the trace.
22:26 sdm24 but no one else has experienced this issue?
22:26 eliasp sdm24: point him to "salt-call -l debug […]" and https://github.com/saltstack/salt/issues/new
22:26 forrest eliasp, sdm24 knows, he's just trolling
22:26 sdm24 yeah the issue is with  systemctl --full --no-legend --no-pager list-units mariadb.service
22:26 eliasp kk
22:27 forrest sdm24, I'm not running dev right now, but no one else has reported such an issue.
22:27 sdm24 ok thanks, I'll tell him that
22:27 forrest sdm24, I assume it's multiple services it fails on, and not just this one
22:27 eliasp I have a box with develop and systemd, let me check
22:27 sdm24 ok thanks
22:27 forrest Just to note, eliasp is (again) working past 11 PM his time
22:28 sdm24 dang, dont go too far out of your way for this. Thanks, though
22:28 eliasp forrest: pff! ;)
22:28 eliasp sdm24: looks good here with Salt develop from ~6h ago
22:28 kitplumm_ joined #salt
22:28 forrest sdm24, I'm just messing with him, he works this late every night it seems.
22:29 eliasp sdm24: 83e50d2
22:29 eliasp forrest is my personal watchguard to make sure I get at least 3h of sleep ;)
22:29 sdm24 haha always important. Thanks for checking
22:29 otter768 joined #salt
22:29 forrest eliasp, more sleep than work train, granted I can't say much since I'm still here and working on shit and I don't even have a job.
22:30 sdm24 He will debug and then post an issue if it isn't a problem on his end
22:30 hemebond When pillars are processed by Salt, are they all merged before being run through the YAML renderer?
22:30 hemebond Or is each file processed separately?
22:32 kitplummer joined #salt
22:32 dkrae joined #salt
22:34 forrest hemebond, https://docs.saltstack.com/en/latest/topics/pillar/#pillar-namespace-merges
22:34 hemebond forrest: Hi, it's more about the underlying process.
22:35 Vynce i felt liek that doc was very vague about wha tactually happens, personally.
22:35 forrest Yeah it's a doc for a basic explanation/example.
22:35 hemebond Is each file separately run through the Jinja processor, then the YAML processor?
22:35 Vynce it seems to take a wild guess at what you are trying to do and talk abotu that instead of actually talking about what happens, as is standard for the salt docs.
22:35 forrest Vynce, 99% of people just want to know if pillars can be merged, very few care about the underlying process.
22:36 forrest hemebond, Yeah I don't know, I've never reviewed that section of the code.
22:36 Vynce this is why 99% of projects have documentation that is completely useless to me.  i'm terrible at guessing what the docs think they should be talking about.
22:36 forrest Vynce, Then read the source.
22:36 hemebond forrest: I've never bothered to think about it until now :-)
22:36 Vynce sadly, salt's source is complex enough that so far reading source has always led to more questions than answers for me.
22:37 Vynce (part of this is because so far i haven't found a guide to where to find what i'm looking for in the source, so most of my time has been search-and-spelunk)
22:38 forrest hemebond, Yeah, I always assumed it was just compiled into a dict of values (thus why the overwrite is non-determininstic) then pumped into yaml, then jinja, but I don't know.
22:39 forrest Vynce, Yeah you have to get familiar with it enough to know where to look. I just know I don't care quite enough about how the pillars are compiled to dive in myself, then write the docs since it would all be freebie work.
22:40 hemebond forrest: I think each file is probably run through the renderers individually then the resulting dicts are merged.
22:40 aqua^c joined #salt
22:40 hemebond Someone's comment on a Github issue suggested that wasn't the process.
22:40 forrest hemebond, Hmm, that seems like more work and thus a slower render, but who am I to disagree since I don't know :)
22:41 hemebond I can't see it working any other way.
22:41 baweaver joined #salt
22:43 kitplummer joined #salt
22:44 mosen joined #salt
22:45 eliasp yes, the order is definitely renderer first, then creating a datastructure out of the file, then merging different files based on include, extend and whatever statements…
22:45 forrest Good to know, thanks eliasp
22:47 asoc Anybody know where I can find the logic that is used to choose a module file to use. For example using win_service.py or rh_service.py instead of service.py?
22:47 eliasp asoc: this happens based on the "virtual" announced by each module
22:47 eliasp asoc: look at the "def virtual" block of those modules…
22:49 asoc eliasp: I saw that block. But how does windows know that it needs to check win_service.py next?
22:49 asoc or does it somehow know to go there first..?
22:52 asoc What I am trying to do is create a aix_service.py so that I can use service.running in one of my states on an AIX box.
22:53 eliasp asoc: the magic is in salt/loader.py:1203 ("if self.virtual_enable:")
22:53 eliasp asoc: and "process_virtual()"
22:55 eliasp asoc: sure, then just use a "def virtual" which returns False unless "__grains__['os'] == 'AIX'" or whatever grain matches best
22:55 Vynce is there a doc that explains the differences between top.sls and other .sls es?
22:55 eliasp Vynce: https://docs.saltstack.com/en/latest/ref/states/top.html
22:56 justanotheruser joined #salt
22:58 _JZ__ joined #salt
22:59 baweaver joined #salt
22:59 gimpy2938 Is there a common way to have all states applied to a minion when it starts/boots?  I assume something nicer than `salt-call state.highstate` in rc.local exists.
22:59 Vynce eliasp: again, that *explains* almost nothing, and certainly doesn't talk about how top.sls are *different from* other sls.  it's an intro-level doc, and talks about basics.
23:01 eliasp Vynce: well, `top.sls` files are rendered by the SLS renderer just as any other SLS file (so you can also use Jinja or whatever you like), but the major difference is: a top.sls doesn't contain individual states, but only environment → targeting → SLS assignments
23:01 Vynce i want to know detailed things, like, whether i can use minions' grains in the top file. (e.g.. {% for gvalue in salt['grains.get']('listgrain', []) %} … )
23:02 eliasp Vynce: you can… the only exception: you can't use Pillar data in the top.sls for Pillar assignments
23:02 Vynce cool, good, thanks.
23:03 gimpy2938 Vynce: The best way to know how software works is to try it and see.  Documentation can only go so far.
23:03 Vynce gimpy: i disagree, but i don't have time to get into a debate about it.
23:03 forrest as a note, the top file docs do explain you can match against grains.
23:04 asoc eliasp: That is exactly what I was looking for. Thanks!
23:04 sdm24 gimpy2938: check startup_states in the minion conf
23:04 Vynce forrest: only in the sense that they can have -match: grain mathcing.  doesn't imply at all that i can use {% salt['grains.get'](…) %}
23:05 forrest sure
23:05 ajw0100 joined #salt
23:05 sdm24 gimpy2938: here's the doc: https://docs.saltstack.com/en/latest/ref/states/startup.html
23:05 Vynce the primary thign missing from salt, IMO, is the big-picture, hwo does it work explanation.
23:06 forrest I don't really have anything to add, it's a free piece of software, if you don't like the docs, don't want to read the source, and don't want to contribute, then I can't help you out there.
23:06 forrest like an architecture overview but detailed for every component?
23:06 gimpy2938 sdm24: Yea, found it and testing now, thanks
23:06 Vynce gimpy2938: for one thing, i don't have and can't afford a farm of machines that i can afford to make mistakes with. \ :
23:06 Vynce forrest: well, i *have* contributed, actually.
23:06 forrest Vynce, Sorry, contribute to the improvement of the docs
23:07 Vynce … again, well, i *have8 actually
23:07 eliasp Vynce: as long as you don't have to run another Kernel than Linux, systemd-nspawn is your friend for disposable test-/devel-environments…
23:07 forrest also, you know there are cloud providers with 5 dollar servers right? Or virtualbox where you can test stuff?
23:07 forrest Vynce, That's great, I wish more people would.
23:07 Vynce but i don't like to add comments to docs that i'm not sure are right, and i only have so much time to dedicate to the improvement of a product that makes money for someone but not for me.
23:07 forrest But I personally am not going to spend my limited time that I work on contributing to add doc details about using grains.get in the top file and whether it's supported, much more pressing items.
23:08 forrest Fair enough, I don't make money from Salt either.
23:08 indispeq joined #salt
23:08 Vynce *shrug* sure. i'm just asking questions and trying to elain why the "that was in the docs" wasn't actually in the docs
23:08 forrest Yep fair enough
23:08 * eliasp put countless hours into SaltStack contributions… but then again, I've used it for 90% of the stuff I was doing within the last 2.5 years ;)
23:08 forrest We all know you're a slacker eliasp
23:08 Vynce forrest: if i had $5 right now it would go toward my rent.
23:09 thehaven_ joined #salt
23:09 eliasp forrest: sshhh ;)
23:09 geekatcmu I make money by using Salt, does that count?
23:09 forrest eliasp, I was going to make a joke about your rank, but you're 3 higher than I am
23:09 forrest so I can't
23:10 eliasp hehe, eat that
23:10 forrest ONLY IN NUMBER OF COMMITS
23:10 forrest rude
23:10 DanyC_ joined #salt
23:11 eliasp well, now those kind of commits pay off: https://github.com/saltstack/salt/commit/ab1b84545be18a59974684f1396a1c430b07edf9
23:11 eliasp :)
23:11 forrest lol
23:11 eliasp but then again, those kind of one-liners take ~8h of debugging: https://github.com/saltstack/salt/commit/05782aa78f6dcb377b203ac3378ea3fdeae72601
23:12 Vynce as for my "big picture" — point … forrest, i dunno, i don't knwo what you mean by that. but i mean, like, i don't really get why there are different "execution" modules and other modules, or what a runner is, or what data is available where because i don't know what gets run when / where (does a state get built on the master and then shipped to the minion wholesale?  or do minions get a copy of the relevant templates and expected to ru
23:12 lahwran joined #salt
23:13 Vynce there's a whole lot of salt where the docs maybe make sense if you already understand them, but there are 'examples" like "you can do a or b or even c" but no explanation of what doing a or b or even c will do.
23:14 forrest Vynce, I can see that in some instances, there are also instances where the questions you just proposed are answered in the docs though
23:14 mlanner joined #salt
23:15 forrest The only reason the docs are as comprehensive as they even are is because people asked those questions, and either made issues, or made PRs to explain it.
23:16 Vynce but where in the docs? i have been reading salt docs for a significant fraction of the last year and am still lost.
23:16 forrest for which one specifically? There's google, and there's a custom google search on the docs site.
23:17 forrest 99% of what I link in here and look for I find via google search.
23:17 gimpy2938 forrest: ...and there's this IRC thing where you ask a question and a human translates that into a URL
23:17 mosen hi salties
23:17 eliasp :)
23:18 forrest gimpy2938, Yeah I considered doing let me google that for you links for a while, but didn't want to be a dick ;)
23:18 Vynce yeah, because you know what to search. that's what i mean; salt is missing the "here's how to understand enough to know how to ask questions" aka "zero-to-self-sufficient" guide
23:18 forrest for your module question I literally searched 'difference between modules saltstack' and had both module pages as results 1 and 2. Maybe I do know how to search, I don't know.
23:19 Vynce I promise that every question i ask in her ei ask because i tried to research it myself and either couldn't find an answer, or couldn't understand the answer i got.
23:19 Vynce "both moduel pages" meaning what?
23:19 forrest And that's fine. That happens for a lot of people
23:19 Vynce well, so telling me tha ti should be googling more is not a useful thing
23:19 forrest Vynce, https://docs.saltstack.com/en/latest/ref/modules/ and https://docs.saltstack.com/en/latest/ref/states/writing.html
23:20 Vynce both of which start with how to make them, not what they are or how they are different from each other or why they both need to exist.
23:21 eliasp Vynce: so you're asking about the difference between execution and state modules?
23:21 Vynce also, ISTR there are other kinds of modules
23:21 forrest Vynce, Yeah and I can agree with that, execution module docs could be better.
23:22 Vynce at the moment, i'm not asking that, no.  it came up as an example of what i think salt docs are terrible at explaining, but atm i am not attempting to understand it
23:23 Vynce i don't think i've ever seen anything explaining the difference between `salt` `salt-call` and `salt-run` either, and i feel like if i understood that i would be much better at using salt.
23:24 forrest Vynce, https://docs.saltstack.com/en/latest/ref/cli/salt.html#description, https://docs.saltstack.com/en/latest/ref/cli/salt-call.html#description, https://docs.saltstack.com/en/latest/ref/cli/salt-run.html#description
23:24 forrest Are you looking for more in-depth details?
23:25 mosen I'm happy to explain stuff Vynce :)
23:25 mosen with my limited knowledge
23:25 forrest I think most of us are mosen
23:25 forrest I'm just trying to understand where the shortcoming in the docs are so I can make an issue to try and address it ;)
23:25 mosen forrest: fair enough.. docs have sometimes been a sore point
23:26 forrest mosen, Yep, that's why almost all of my ~115 issues related ot the docs
23:27 forrest if it's 'the docs are not explaining the components in enough detail' that's something we can fix, if the issue is 'searching for these things is hard' I'm not sure how to fix that.
23:27 Vynce forrest: if those three sentences were on one page, and didn't require clicking through to understand what a salt-runner was first, that would be the beginning. keep in mind that my core theme here is "pverview" … if you r answer for one overview-type distinction is a sentence each from three different pages, that's far from an overview.
23:27 mosen forrest: They are much better now.. but maybe there are too many choices for a newbie
23:27 Ryan_Lane Vynce: the difference between them is pretty simple and I'm not sure why it's not documented better
23:27 forrest Ryan_Lane, Yep
23:27 Ryan_Lane execution modules do actions, but they aren't necessarily idempotent
23:27 forrest mosen, Yeah I don't know, which is what makes it hard.
23:28 forrest Vynce, Maybe we should just make a big ass page where each item is explained? Like a nice big compilation of terms and such
23:28 Ryan_Lane state modules are always idempotent
23:28 Ryan_Lane they generally utilize execution modules to do so
23:29 Vynce (the fact that execution moduels are sometiems called jsut modules doesn't help)
23:29 Ryan_Lane I really like that salt actually makes these separate concepts.
23:29 Ryan_Lane yep. that's unfortunately due to historical reasons
23:29 forrest Yeah
23:29 Vynce forrest: like, an overview? ( :
23:29 Ryan_Lane because originally salt was just for remote execution
23:29 iggy my irc stats would be even higher than they are now if I wrote out "execution modules" and "state modules" all the time
23:29 Ryan_Lane salt <-- used on the master. runs execution module commands on minions
23:30 mosen Ryan_Lane: yeah I was surprised it had a puppet module :)
23:30 Ryan_Lane salt-call <-- used in masterless, or directly on minions. calls execution modules
23:30 forrest Vynce, An overview of terms is completely different than an overview of the entire system.
23:30 forrest Vynce, https://docs.saltstack.com/en/getstarted/overview.html
23:30 forrest This is actually the first time I've seen this page
23:30 Ryan_Lane salt-run <-- calls runners on the master. can only be used on a master
23:30 iggy catch up forrest
23:30 Vynce Ryan_Lane: then i'd argue that either (a) the other things chouldn't be called modules (b) execution moduels should not be filed under salt.modules or (c) this should at least be explained in the overview or somewhere easy to otice early on.
23:30 forrest There's also this one: https://docs.saltstack.com/en/latest/topics/development/architecture.html
23:30 Ryan_Lane runners are special modules that execute directly on the master
23:31 forrest iggy, Sorry, I don't usually watch the docs for new additions.
23:31 Ryan_Lane Vynce: agreed. terminology has been difficult in salt since forever
23:31 iggy Vynce: it also helps if you understand that there's a lot of python creep in salt (i.e. everything is called modules because they are... python modules)
23:32 mosen forrest: I was envisioning a tutorial in like a multi part series that covered some part of salt without the choice of which component to cover. There are already getting started guides though.. I dunno
23:32 Vynce that overview is amazing. i wonder how new it is.
23:32 Ryan_Lane it's pretty new
23:32 Vynce the getting started and tutorials are.. not great, IMO
23:32 Ryan_Lane maybe 3 months?
23:32 forrest mosen, You mean like this that I didn't finish? https://github.com/gravyboat/salt-book/tree/master/en ;)
23:32 mosen forrest: yeah like that! hehe
23:34 sdm24 for me, one of the things I still have trouble explaining/understanding sometimes, is that top.sls and highstate can be completely different
23:34 iggy here's the deal, SSE has a dedicated docs guy now, open tickets and they'll get looked at
23:34 forrest Yeah Jacob is doing a great job of improving the docs.
23:34 Vynce Ryan_Lane:, forrest: thanks for the overview doc.  i wish that had been there when i started with salt.
23:34 iggy nobody here sat down and wrote the docs
23:34 iggy (nobody anywhere did tbh)
23:34 forrest Vynce, For sure, that is my first time seeing the 'graphic' version as well.
23:35 Vynce sdm24: yeah, i still don't get what "highstate" and "high data" and "low data" refer to.
23:35 iggy we know the docs have shortcomings, SSE knows the docs have shortcomings
23:35 sdm24 speaking of updating docs, did anyone get their Digital Ocean Hacktoberfest shirt yet? I haven't
23:35 iggy but once you've been working on stuff for so long, it's hard to see what the shortcomings are
23:35 forrest sdm24, Not yet, they said within 3 weeks after Nov. 10th
23:35 sdm24 oh ok
23:35 forrest sdm24, I only know this because I looked at the email yesterday since I was wondering as well :D
23:35 iggy so we actually like when new people come and say "this isn't clear" or "it's hard to piece all these different things together"
23:35 Vynce OK, i need to go apply some of this new knowledgenow.  thanks, everybody.
23:35 forrest Yep, we ask for that a lot, or I create issues for people who don't want to do so if they're new.
23:36 forrest Everyone wants it to be better, but very few of us are paid to make it better, so there's only so much we can/are willing to do.
23:36 Vynce iggy: once again demonstrating why you are one of my favorite examples of irc-for-opensource ever. ( :
23:36 forrest I feel like you caught iggy on a nice day
23:36 forrest he's so kind today
23:36 iggy my amazon box just came
23:36 Vynce heh
23:37 Vynce forrest: yeah, and i've made issues but often feel like i don't know enough to make a good clear issue.
23:37 mosen hehe
23:37 forrest Vynce, Just do your best, worst case they ask for clarification.
23:37 iggy Vynce: they have people that are tasked to get more info out of users too, so don't worry about that... just give as much detail as you can think of
23:38 sdm24 I also wonder if its just me who is unsure if the docs aren't explaining something well, or if other people have this issue. I don't want to change a big chunk of the docs for just my needs
23:38 iggy I've filed an issue that was 4 words long
23:38 sdm24 igigy
23:38 sdm24 oops
23:38 forrest Trust me, it's more frustrating for us than it is for you when the docs are bad. I have almost 3k lines added to salt, and it's mostly in the docs, so I care.
23:38 sdm24 iggy: U R Teh Dum /send
23:38 iggy (8 if you count the comment after that said I was sending a PR later)
23:38 forrest I just can't fix it all.
23:39 pdayton joined #salt
23:39 Vynce is it just me, or should github have an actionable button to go with the "your fork is 14k commits behind saltstack/develop" line?
23:39 Vynce (my problems with "getting started" docs do not only apply to saltstack)
23:40 forrest Yeah that is definitely a problem, did you add the salt upstream? You can get up to speed pretty quick doing that
23:40 Vynce forrest: well, sicne i don't understand the uestion, i'm guessing my answer is no.
23:41 forrest My branch says I'm 1268 commits behind
23:41 forrest Vynce, do this: https://docs.saltstack.com/en/develop/topics/development/contributing.html#sending-a-github-pull-request
23:41 forrest but just the remote add upstream, and git fetch upstream
23:41 forrest then do a git merge upstream/develop
23:41 forrest and you should be caught up
23:41 forrest and you can push back to your fork and be up to date again
23:45 Vynce ah, i don't have a CLI option, because my fork exists only on github
23:46 forrest You can just pull your fork onto your local work station, via git clone, then add the upstream, fetch it, and merge, then push back
23:46 forrest No way to do it through the interface.
23:48 Vynce ah.  then i'll have to deal with it later.
23:50 shaggy_surfer joined #salt
23:52 iggy I think you can just go back to the upstream file and click the edit button and it'll create a new branch based off of whatever branch you were viewing on the upstream
23:52 bfoxwell joined #salt
23:53 kitplummer joined #salt

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