Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-08-08

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

All times shown according to UTC.

Time Nick Message
00:01 flowstate joined #salt
00:13 mosen joined #salt
00:25 timoguin joined #salt
00:30 edrocks joined #salt
00:47 Vaelatern joined #salt
00:51 agentnoel joined #salt
00:52 Nahual joined #salt
00:54 agentnoel Hi there. I'm trying to use SaltStack formulas. They appear to download, but I cannot list them with "sys.list_functions", or "sys.list_state_functions".
00:54 agentnoel I am using the guide here https://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html
01:13 catpigger joined #salt
01:24 iggy rylnd: make sure you don't have an old version still installed somewhere else (i.e. /usr/lib vs /usr/local/lib)
01:24 cyborg-one joined #salt
01:24 rylnd iggy thx, checked. i deployed a new VM already with the new packages
01:25 rylnd iggy i forked my version (that i use to build) it from 2016.3.2 on Github. So I am really confused why it tells me that it's version is 2016.3.0
01:25 iggy agentnoel: formulas wouldn't generally provide extra modules (although a few do)
01:26 iggy rylnd: no clue then, that's just the first thing that popped into my head
01:26 rylnd iggy thx. i think ill head to bed and look further tomorrow. already 3am here
01:36 agentnoel iggy: How do you list the gitfs remote states?
01:42 subsignal joined #salt
01:47 ilbot3 joined #salt
01:47 Topic for #salt is now Welcome to #salt! | Latest Versions: 2015.5.11, 2015.8.11, 2016.3.2 | Support: https://www.saltstack.com/support/ | Logs: http://irclog.perlgeek.de/salt/ | Paste: https://gist.github.com/ (please don't multiline paste into channel) | See also: #salt-devel, #salt-offtopic | Ask with patience as we are volunteers and may not have immediate answers
01:56 k_sze[work] joined #salt
02:01 stotch joined #salt
02:02 stotch joined #salt
02:21 onlyanegg joined #salt
02:30 hasues joined #salt
02:30 hasues left #salt
02:33 edrocks joined #salt
02:34 bastiand1 joined #salt
02:40 evle joined #salt
02:52 flowstate joined #salt
02:53 badon joined #salt
03:04 mavhq joined #salt
03:11 subsignal joined #salt
03:12 ZachLanich joined #salt
03:14 badon joined #salt
03:19 iggy agentnoel: as I said, the formulas generally don't include modules/states
03:19 subsignal joined #salt
03:19 iggy if you are just trying to figure out how to use the formulas, the best place to start is the pillar.example for each one
03:21 agentnoel Thanks. I have been reading them, and the sls files in the formulas, but they all seem overly complicated, and don't show what is a default value, and what is a required value. Any tips?
03:21 nicksloan joined #salt
03:23 iggy they are overly complex
03:25 iggy they probably aren't for everyone
03:26 agentnoel Would you recommend a beginner keep away from them, and just build simple pillars/states first?
03:34 kshlm joined #salt
03:36 iggy yes
03:36 iggy a lot of them are just complete crap
03:38 iggy and I say that as one of the maintainers of them
03:52 flowstate joined #salt
03:58 jesusaur joined #salt
04:00 hamstah left #salt
04:01 onlyanegg joined #salt
04:18 antpa joined #salt
04:26 agentnoel Do you have any advice on how to manage configuration files, as a beginner?
04:27 agentnoel Should you copy the configuration files from a os package, and then do a brute overrite, or should you attempt to patch them?
04:36 edrocks joined #salt
04:37 iggy ehh, it kind of depends
04:37 iggy I use a mix of both
04:55 antpa joined #salt
04:58 west575_ joined #salt
05:09 ageorgop joined #salt
05:10 cyborg-one joined #salt
05:10 alexhayes joined #salt
05:11 rdas joined #salt
05:11 flowstate joined #salt
05:24 fracklen joined #salt
05:30 MTecknology iggy: Home office! :D  http://i.imgur.com/3f8VNsE.jpg
05:51 iggy seems like you'd probably run into the deer a lot
05:53 flowstate joined #salt
06:01 alexhayes joined #salt
06:06 infrmnt joined #salt
06:07 POJO joined #salt
06:09 felskrone joined #salt
06:22 CeBe joined #salt
06:25 Inver joined #salt
06:33 fracklen joined #salt
06:38 edrocks joined #salt
06:38 impi joined #salt
06:52 flowstate joined #salt
07:07 fracklen joined #salt
07:10 jhauser joined #salt
07:11 Electron^- joined #salt
07:15 JohnnyRun joined #salt
07:21 rdas joined #salt
07:24 permalac joined #salt
07:36 cyborg-one joined #salt
07:37 irctc903 joined #salt
07:39 sagerdearia joined #salt
07:42 Karthik427 joined #salt
07:51 vilitux joined #salt
07:51 Electron^- joined #salt
07:52 ivanjaros3916 joined #salt
07:52 flowstate joined #salt
07:56 amy_ joined #salt
07:57 gableroux joined #salt
07:57 antpa joined #salt
08:01 bdrung_work joined #salt
08:08 Miouge joined #salt
08:20 amy_ joined #salt
08:24 Sammichmaker joined #salt
08:25 joe1 joined #salt
08:26 joe1 Hi! The docs for Salt Virt say: "Salt Virt does not work with KVM that is running in a VM. KVM must be running on the base hardware."
08:26 ravenx joined #salt
08:26 joe1 Is there any particular reason for why that wouldn't work?
08:28 GreatSnoopy joined #salt
08:29 antpa joined #salt
08:30 s_kunk joined #salt
08:33 fredvd joined #salt
08:37 fannet joined #salt
08:41 edrocks joined #salt
08:42 jcalero joined #salt
08:43 keimlink joined #salt
08:44 Electron^- joined #salt
08:46 s_kunk joined #salt
08:51 flowstate joined #salt
09:09 jcalero_ joined #salt
09:15 garphy`aw joined #salt
09:24 DanyC joined #salt
09:28 antpa joined #salt
09:37 mikecmpbll joined #salt
09:37 giany what is the easiest way to change the salt master host/ip of minions from master? (and eventually restart salt-minion)
09:42 antpa joined #salt
09:43 jcalero would love to know that too ^
09:43 joe1 giany: What I personally would do is use salt-ssh for changing the config. Because if you mess things up and the minion doesn't see the master any more you can't fix things over the message bus.
09:43 Deliant joined #salt
09:44 joe1 You can use salt-ssh with states. So a simple state that manages your /etc/salt/minion file and restarts the minion service should do the job.
09:51 flowstate joined #salt
09:56 Electron^- joined #salt
09:56 lero joined #salt
10:13 fracklen joined #salt
10:16 AndreasLutro giany: I would add the new IP as a redundant master in the minions' config, that way when the old IP stops responding the minions should just fall back to the new IP. also you might want to use a DNS record instead of IP addresses
10:16 kbaikov joined #salt
10:39 impi joined #salt
10:40 guerby joined #salt
10:44 keekz joined #salt
10:44 edrocks joined #salt
10:48 tpaul joined #salt
10:50 flowstate joined #salt
11:00 amcorreia joined #salt
11:13 rdas joined #salt
11:19 subsignal joined #salt
11:22 johnkeates joined #salt
11:30 subsignal joined #salt
11:37 subsignal joined #salt
11:42 subsignal joined #salt
11:45 XenophonF joined #salt
11:46 rubenb joined #salt
11:47 rubenb Hi, I'm looking at more information about using the python libs for salt.
11:48 rubenb Anyone knows some good resources for that?
11:50 flowstate joined #salt
11:51 subsignal joined #salt
11:55 Inver joined #salt
11:55 goestin joined #salt
11:58 lovecraftian joined #salt
12:02 subsignal joined #salt
12:03 rylnd joined #salt
12:07 goestin Hi All, i'm having some trouble using environments for pillar data. Maybe someone wants to take a look at my master config: http://pastebin.com/m8aCbfTm and then demonstration of the issue: http://pastebin.com/bLUWFVJ6
12:09 goestin I would asume that the data "pillar_enviroment" for server1 would be "prod" and not "dev". However i fail to see why this is
12:10 goestin *pillar_environment
12:15 subsignal joined #salt
12:16 scoates joined #salt
12:17 numkem joined #salt
12:18 roock joined #salt
12:19 subsignal joined #salt
12:21 PerilousApricot joined #salt
12:22 west575 joined #salt
12:33 kneph joined #salt
12:35 subsignal joined #salt
12:35 edrocks joined #salt
12:37 squishypebble joined #salt
12:38 gh34 joined #salt
12:45 Electron^- joined #salt
12:50 flowstate joined #salt
13:00 pcdummy This is what Salstack will provision for me in the near future: https://rene.jochums.at/qooxdoo/
13:00 pcdummy Saltstack
13:01 pcdummy It will be drawstack an Open Source GUI to draw Clouds.
13:01 pcdummy With saltstack as backed to make it happen.
13:01 dyasny joined #salt
13:04 johnkeates no
13:04 johnkeates .
13:06 Vaelatern Well, good luck with that. If it works, that's awesome.
13:07 kneph Does the dockerng state module's "running" state function support specifying volume mount propagation modes?
13:07 kneph I need to do something equivalent to "docker run -v /mypath:/mypath:shared ... "
13:08 kneph The spec for the "binds" argument (<host_path>:<container_path>:<read_only>) seems to only allow for read modes
13:08 johnkeates no, docker only supports burning and failing
13:08 johnkeates sorry to break it to ya
13:09 kneph well, at least it supports both instead of just one or the other
13:10 AndreasLutro it's possible to both burn and fail while running
13:10 pcdummy AndreasLutro: always with cloud provisioning tools :)
13:10 pcdummy AndreasLutro: hopefully it wont :)
13:10 pcdummy Vaelatern: ta
13:12 pcdummy goestin: thats because you have the asterisk in both
13:13 subsignal joined #salt
13:13 pcdummy goestin: hmm looking again at your example, maybe saltenv helps instead enviornment?
13:14 goestin pcdummy: thanks! let me read into that...
13:14 pcdummy goestin: why do you target from grains? You have a special reason for that?
13:14 protoz joined #salt
13:15 subsigna_ joined #salt
13:15 * pcdummy needs to boot his local salt to check this "config.get environment" thing
13:16 goestin pcdummy: i'm not using grains
13:16 pcdummy goestin: ahh then its realy the asterisk
13:16 goestin (((accidental [enter]))) (at least not in that example ;))
13:17 pcdummy if you put dev:\n  'server2.somedomain.org':\n  - _global it will work.
13:18 goestin pcdummy: i know, but what is the point then in having different pillar_roots?
13:18 pcdummy goestin: different data per pillar?
13:18 pcdummy same keys put different output
13:19 goestin well not in my experience? (im obviously missing the point here, but i honestly see no logic in this behaviour)
13:20 dyasny joined #salt
13:20 pcdummy goestin: you can have a "users.my_user.sls" in both, one returns dev data the other returns prod data.
13:21 goestin ok, but how is that different from "_global.sls" in both, i would expect one to return prod-, and one to return dev-data
13:22 goestin and how, will something that says "dev:\n  '*':\n     -  just_an_example" ever be assigned to a  host that has it's environment set to "prod". That is my  biggest question, i think...
13:24 sm1ly[wrk] joined #salt
13:24 sm1ly[wrk] re2all
13:26 sm1ly[wrk] ppl, tell me please. I looking for https://github.com/saltstack/salt/blob/develop/salt/engines/slack.py I configured it. I cant find any docs about aliases and I can find any docs about rights separating.
13:31 debian112 joined #salt
13:33 goestin hi sm1ly[wrk] : create a file in the directory where your top.sls file is (eg: /srv/salt/slack.sls) with the following: http://pastebin.com/qUteNjmC
13:34 sm1ly[wrk] goestin, its slack-message. I talks about master configuration
13:34 timoguin joined #salt
13:34 goestin sm1ly[wrk]: whoopsie poopsie, please ignore my rambling then :)
13:36 ktosiek left #salt
13:37 DanyC joined #salt
13:40 timoguin joined #salt
13:41 dendazen joined #salt
13:41 sfxandy joined #salt
13:43 DanyC left #salt
13:44 wych joined #salt
13:44 racooper joined #salt
13:45 perfectsine joined #salt
13:50 flowstate joined #salt
13:53 ssplatt joined #salt
13:57 subsignal joined #salt
13:58 antpa joined #salt
13:58 nonades joined #salt
14:01 west575_ joined #salt
14:03 mpanetta joined #salt
14:04 timoguin joined #salt
14:04 bowhunter joined #salt
14:05 mpanetta joined #salt
14:06 jcalero Does anyone recognise this error: https://gist.github.com/jcalero/7dcc3f5476a7bc8e348ceb2c95c4841c? "Failed to import module dock, this is due most likely toa syntax error:"
14:07 jcalero I keep having it on my minons with various modules, 'dock' and 'db' mainly.
14:07 whytewolf do these external modules pass python lint tests?
14:09 jcalero ugh, I'm an idiot, I kept thinking it was complaining about a module as part of salt itself, but now I realise it's one of ours -.-, so the fault is in our code
14:10 jcalero thanks for the nudge whytewolf
14:11 whytewolf np
14:15 jason2 Hi, is there a documented way to download/upload files to remote windows machine over SMB session?
14:15 PerilousApricot joined #salt
14:15 jason2 I'm looking for a way to do it from a selected minion to another windows machine this minion has access to
14:15 jason2 or from the master itself if it possible
14:21 ZachLanich joined #salt
14:21 permalac joined #salt
14:22 perfectsine joined #salt
14:24 west575 joined #salt
14:25 scoates joined #salt
14:25 edrocks joined #salt
14:25 mapu joined #salt
14:27 TooLmaN joined #salt
14:29 gaffelzange joined #salt
14:36 flowstate joined #salt
14:38 Perilous_ joined #salt
14:38 west575 joined #salt
14:42 flowstate joined #salt
14:43 west575 joined #salt
14:43 ivanjaros joined #salt
14:44 Brew joined #salt
14:49 vincent_vdk joined #salt
14:51 POJO joined #salt
14:57 tiwula joined #salt
15:01 debian112 joined #salt
15:02 PerilousApricot joined #salt
15:03 Miouge joined #salt
15:05 hasues joined #salt
15:05 hasues left #salt
15:08 heaje joined #salt
15:08 hasues joined #salt
15:10 beardedeagle joined #salt
15:15 Ch3LL joined #salt
15:15 perfectsine joined #salt
15:15 amy_ joined #salt
15:18 fxhp joined #salt
15:23 jeddi joined #salt
15:25 Perilous_ joined #salt
15:26 Bryson joined #salt
15:37 bbbryson joined #salt
15:40 KingOfFools Hey guys. I have state file with pillar getting info from /srv/pillar files. It works when Im running state manually. But when I'm running this state with reactor and passing POST data in it with pillar, pillar from files /srv/pillar is not working.
15:41 KingOfFools Variables are different and shouldn't override each other
15:42 one joined #salt
15:42 DanyC joined #salt
15:44 johnkeates joined #salt
15:48 PerilousApricot joined #salt
15:49 iggy I've never tested to see if reactor pillar merges with other pillar data... I think I just always assumed that pillar data (other than what you pass it) was just a no go
15:50 iggy KingOfFools: one thing to keep in mind is reactors run in master context, so they really don't have pillar data to begin with
15:51 amcorreia joined #salt
15:51 onlyanegg joined #salt
15:55 POJO_ joined #salt
15:56 lorikcana joined #salt
15:56 sfxandy hi guys,  silly question here ...... but is it possible to call one orchestration from another?
15:56 lorikcana Hey all
15:56 hasues left #salt
15:56 lorikcana I am new here
15:57 iggy sfxandy: maybe? but why? Just be careful that one of them can't trigger the other one and send it into a recursive loop
15:57 sfxandy no danger of that iggy
15:57 lorikcana Where can I get the GUI version of saltstack?
15:58 sfxandy i have three calls to salt.state in my orchestration file .... but when i attempt to call runner.state.orchestrate as the last call, nothing seems to happen
15:59 rylnd lorikcana you need to be an enterprise customer to get saltstack enterprise 4.0 https://saltstack.com/enterprise/
16:00 lorikcana I need to buy?
16:00 Sylvain31 joined #salt
16:00 antpa joined #salt
16:01 Tanta joined #salt
16:01 rylnd lorikcana yes, if you want to have a UI and use all enterprise features
16:01 lorikcana Okay.
16:02 paant joined #salt
16:02 lorikcana rylnd so is the UI close sourced?
16:02 rylnd lorikcana as far as i know, yes
16:02 lorikcana rylnd Ohkay thanks
16:03 rylnd lorikcana contact them, talk to their reps and ask for a demo. they will be happy to demonstrate saltstack enterprise 4.0 and the UI. we had one a couple of weeks back
16:04 jason2 Hi , anyone has idea regarding my question? thank you :)
16:04 pipps joined #salt
16:04 jason2 "is there a documented way to download/upload files to remote windows machine over SMB session"
16:11 Perilous_ joined #salt
16:15 KingOfFools iggy: but it possible to run state on minion by reactor?
16:23 woodtablet joined #salt
16:24 Sarphram joined #salt
16:25 Brew joined #salt
16:26 colegatron_origi joined #salt
16:26 iggy KingOfFools: right, but then you're talking about something different (which shouldn't be different than saying `salt 'minion' state.sls foo`)
16:32 fyb3r joined #salt
16:33 onlyanegg joined #salt
16:34 PerilousApricot joined #salt
16:35 Edgan joined #salt
16:36 lero joined #salt
16:36 patrek_ joined #salt
16:40 pipps joined #salt
16:41 DanyC joined #salt
16:42 DanyC left #salt
16:44 KingOfFools iggy:  Im a bit confused when i should use orchestrate runners, state.apply and other things. Should read documentation again, i guess
16:46 ronnix joined #salt
16:46 buglessdr joined #salt
16:49 woodtablet joined #salt
16:56 freelock Hi,
16:56 freelock I'm getting an error on dockerng.image_present states all of a sudden
16:57 freelock File "/usr/lib/python2.7/dist-packages/salt/modules/dockerng.py", line 2253, in list_tags
16:57 freelock for repo_tag in item.get('RepoTags', []):
16:57 freelock TypeError: 'NoneType' object is not iterable
16:57 Perilous_ joined #salt
16:58 freelock I just tried adding image tags to the state "name" field, based on seeing the repo:tag syntax on https://docs.saltstack.com/en/latest/ref/states/all/salt.states.dockerng.html#module-salt.states.dockerng
16:58 freelock but still same error... I also tried updating docker.py...
16:58 freelock Is there some other new change necessary?
16:59 kus joined #salt
17:00 freelock ah ok just found https://github.com/saltstack/salt/issues/35139
17:00 saltstackbot [#35139][OPEN] dockerng: RepoTags not iterable with docker 1.12 on ubuntu 14.04 | Description of Issue/Question...
17:03 flowstate joined #salt
17:06 stanchan joined #salt
17:06 scoates joined #salt
17:12 davisj_ Anyone else find that scheduled minion jobs never appear on the event bus? It's makes my reporting setup pretty much useless.
17:17 _JZ_ joined #salt
17:18 Misfit joined #salt
17:19 Edgan davisj_: sounds somewhat like, https://github.com/saltstack/salt/issues/12653
17:19 saltstackbot [#12653][OPEN] salt schedule doesn't return jobs result info to master | salt schedule doesn't return jobs result info to master, and don't fire event to event bus.   It's inconvenient  for debugging or checking the schedule functions status.
17:20 west575_ joined #salt
17:21 PerilousApricot joined #salt
17:22 pipps joined #salt
17:22 lero joined #salt
17:23 ageorgop joined #salt
17:23 jenastar joined #salt
17:24 gableroux joined #salt
17:25 repl1cant joined #salt
17:26 autofsckk joined #salt
17:27 bowhunter joined #salt
17:27 repl1cant joined #salt
17:27 wendall911 joined #salt
17:28 repl1cant Is this still the most valid 'template' for new formulas? I just noticed this .. Basically seperating everything out of the init.sls and into config, service, and install?
17:28 repl1cant https://github.com/saltstack-formulas/template-formula/tree/master/template
17:28 DammitJim joined #salt
17:29 davisj_ Edgan: thanks for the link
17:31 cmarzullo repl1cant: I use a variation of that pattern. I like it.
17:31 cmarzullo install, config, service is a good pattern for most formulas.
17:32 repl1cant ya, was just thinking of renaming 'install' to 'package' but that's just me being ocd
17:32 cmarzullo yeah I'm used to package, file, service. but same diff.
17:32 repl1cant ;-)
17:33 cmarzullo If you are looking for something to generate scaffolding checkout saltscaffold
17:34 cmarzullo It'll drop in kitchen tests and stuff
17:35 LessSneaky joined #salt
17:37 racooper joined #salt
17:38 ronnix joined #salt
17:39 repl1cant ah cool, I'll check it out
17:39 repl1cant thanks
17:44 Perilous_ joined #salt
17:45 wendall911 joined #salt
17:56 gableroux joined #salt
17:57 mavhq joined #salt
17:57 edrocks joined #salt
17:59 mikecmpbll joined #salt
17:59 pipps joined #salt
18:02 pipps99 joined #salt
18:04 pipps99 joined #salt
18:05 pipps99 joined #salt
18:07 PerilousApricot joined #salt
18:12 lero joined #salt
18:14 GreatSnoopy joined #salt
18:14 antpa joined #salt
18:19 zer0def joined #salt
18:19 iggy KingOfFools: runners run stuff on the master (in the master context without reliable access to any pillar data... even what's targeted at the master)
18:20 iggy states/modules would operate the same as normal (you target them at a minion and they _should_ have access to a merge of their normal pillar data and whatever pillar data you are _passing_ to the state/module run... not every bit of pillar data that exists in the reactor)
18:22 ageorgop joined #salt
18:25 flowstate joined #salt
18:30 cyborg-one joined #salt
18:30 POJO joined #salt
18:31 btorch left #salt
18:32 Perilous_ joined #salt
18:33 fannet joined #salt
18:39 mavhq joined #salt
18:43 mapu joined #salt
18:43 DanyC joined #salt
18:45 mavhq joined #salt
18:49 Hipikat_ joined #salt
18:49 sinh_ joined #salt
18:50 goal_ joined #salt
18:50 tooth_ joined #salt
18:50 Miouge joined #salt
18:50 ze-_ joined #salt
18:50 rome_390 joined #salt
18:50 gadams_ joined #salt
18:50 v0rtex joined #salt
18:50 sjohnsen- joined #salt
18:50 VSpike_ joined #salt
18:50 euidzero joined #salt
18:50 emid_ joined #salt
18:50 Karunamon joined #salt
18:50 UForgotten joined #salt
18:50 quarcu joined #salt
18:50 Nebraskka joined #salt
18:50 flebel joined #salt
18:50 Patch joined #salt
18:50 nethershaw joined #salt
18:51 Nebraskka joined #salt
18:51 MaZ- joined #salt
18:51 fracklen joined #salt
18:51 DerCed joined #salt
18:52 mavhq joined #salt
18:52 jgarr joined #salt
18:52 guerby joined #salt
18:53 jgarr the salt-master service is eating ALL of my disk inodes. Anyone know a setting in the master to help with that outside of getting a bigger disk?
18:53 om joined #salt
18:55 PerilousApricot joined #salt
18:59 17WAAECCO joined #salt
19:09 perfectsine joined #salt
19:10 cmarzullo have more inodes?
19:11 cmarzullo probably too late for that though.
19:11 Edgan jgarr: how many minions and how often are you running a salt run per minion?
19:12 mavhq joined #salt
19:12 LessSneaky joined #salt
19:12 pipps joined #salt
19:12 jgarr ~5000 minions. I'm not running any highstates. It's just for one off module commands Edgan
19:13 Edgan jgarr: version?
19:13 pipps joined #salt
19:13 jgarr I set a file limit for the master and cleared the cache directory. That dropped the inodes back down to 2%. We'll see if it goes back up
19:13 jgarr version 2016.3.1-1
19:14 Edgan jgarr: is it really just /var/cache/salt/master/jobs?
19:14 pipps joined #salt
19:16 jgarr Edgan: yes looks like it's all in jobs
19:16 Edgan jgarr: I think you are seeing https://github.com/saltstack/salt/issues/3663 . Supposedly it is fixed in your version, but sounds like not well enough. If you aren't using a highstate, you might not be trigginer the code that does the clean up. You might be in a corner case. I would open a new issue(after searching for other issues), and reference this one.
19:17 saltstackbot [#3663][MERGED] salt-master leaves a mess in /var/cache/salt/master/jobs | Detailed Inode usage for: /var/cache/salt/master/jobs...
19:18 mavhq joined #salt
19:21 Perilous_ joined #salt
19:22 Ryan_Lane joined #salt
19:24 onlyanegg joined #salt
19:29 antpa joined #salt
19:31 mavhq joined #salt
19:32 timoguin joined #salt
19:33 mavhq joined #salt
19:34 Miouge joined #salt
19:35 Pulp joined #salt
19:36 mavhq joined #salt
19:36 jgarr Edgan: thanks for the tip. Interestingly I have keep_jobs: False in my master config
19:38 jgarr realized that should be a numerical hour (not false) I also have job_cache: False
19:38 g3cko joined #salt
19:39 Edgan jgarr: yeah, that is what the docks say
19:39 Edgan docs
19:39 Edgan jgarr: False might be treated like 0, which says never run the clean
19:40 DanyC joined #salt
19:40 lero joined #salt
19:40 Miouge_ joined #salt
19:40 jgarr I would assume with job_cache: False they wouldn't even be there
19:40 Edgan jgarr: they also say job_cache: False is not a 100% solution
19:40 jgarr but that's what I get for making assumptions. Still not sure what job_cache should be set to
19:41 Edgan "However, you can disable the job_cache by setting it to False in the Salt Master configuration file. Setting this value to False means that the Salt Master will no longer cache minion returns, but a JID directory and jid file for each job will still be created. This JID directory is necessary for checking for and preventing JID collisions."
19:41 jgarr ahh ok, well I'll just make keep_jobs: 1 and see if they get cleaned out
19:42 Edgan jgarr: and the 1 value is hours to keep
19:42 Edgan jgarr: So it should keep one hour of jid dirs instead of forever
19:42 jgarr right, so it should clean up the jobs older than 1 hour
19:42 nkuttler joined #salt
19:42 jgarr I'll try that and see what breaks
19:43 timoguin joined #salt
19:44 PerilousApricot joined #salt
19:44 edrocks joined #salt
19:44 mavhq joined #salt
19:45 nkuttler joined #salt
19:47 17WAAECCO joined #salt
19:48 mavhq joined #salt
19:51 mavhq joined #salt
19:55 iggy jgarr: the only time I've seen that before was when I had a recursive reactor setup (accidentally)
19:55 DanyC left #salt
19:55 iggy and I think the default for keep_jobs is 24 hours not inf
19:55 west575 joined #salt
19:56 jgarr iggy: how was it retursive? did it call itself?
19:56 iggy it called something, that called something, that ended up triggering the reactor
19:57 iggy under normal conditions, you really shouldn't run out of inodes
19:57 jgarr The only thing I have set up is 2 reactor jobs but one just deletes the minion keys and the other installs a package
19:58 jgarr This is the 3rd time I've run out of inodes. Once on an old server and then 2x on this system
19:58 jgarr hopefully that config change will help. Just odd when it happens and the server is mostly idle
19:58 iggy watch the event bus and see if you see anything weird
19:59 Edgan jgarr: how long does it take before you run out of inodes from a wipe?
20:00 Perilous_ joined #salt
20:00 jgarr Edgan: not sure. It doesn't get used very often. I use it maybe once a week or every other week. Usually when I get to it the disk is "full"
20:02 mavhq joined #salt
20:03 Perilou__ joined #salt
20:03 Edgan jgarr: I suspect it is just a matter of you had disabled the cleaner, and it caught up with you
20:03 rubenb Hi, I'm looking at more information about using the python libs for salt within scripts. (ie: not using os.system('salt-key -Ay'))
20:04 jgarr Edgan: that's my hope/guess too. We'll see the next time I need to use it
20:04 mavhq joined #salt
20:05 Edgan rubenb: one way would be the salt api
20:06 Edgan rubenb: then you are writing to a rest api
20:07 Edgan rubenb: I use it in EC2 to have a provisioning script request a minion key via the salt api, and then I put it in the instance's userdata. Then cloud-init reads userdata at boot and installs the key.
20:07 Edgan rubenb: Then you have secure key creation/deployment.
20:08 Edgan rubenb: or, https://docs.saltstack.com/en/latest/ref/clients/#salt.client.LocalClient.cmd
20:08 rubenb Edgan: That could work. I need minions to register at an API, get the (preseeded) keys and a minion_id.
20:09 rubenb I found the LocalClient(), but that class does not seem to have key-related stuff.
20:09 Edgan rubenb: It would be better if a third party was handling it. If you let the minion do it, then all minions have a key that can use the api. Though you can limit what a salt api user can do.
20:11 Edgan rubenb: I think the salt api is the intended way of dealing with keys.
20:11 mavhq joined #salt
20:11 rubenb Edgan: Thanks!
20:12 Edgan rubenb: or, https://github.com/saltstack/salt/issues/31112
20:12 saltstackbot [#31112][MERGED] Can't delete a minion key from the Python API | This doesn't work. No error, no return. Tested on 2015.8 and 2016.3....
20:12 Edgan rubenb: Looks like you are looking for the wheel.cmd function in the python api
20:12 PerilousApricot joined #salt
20:12 rubenb Will not let the minions communicate directly to the salt API, just to our own API which will generate the minion_id (don't trust the clients), and the keys.
20:13 antpa joined #salt
20:13 Edgan rubenb: and the salt api uses wheel too
20:13 Edgan rubenb: So sounds like you can do it either way
20:13 mikecmpbll joined #salt
20:13 scoates joined #salt
20:13 west575__ joined #salt
20:14 mavhq joined #salt
20:15 paant joined #salt
20:15 rubenb Edgan: What's a salt wheel thing?
20:16 Edgan rubenb: https://docs.saltstack.com/en/latest/ref/wheel/all/index.html
20:18 rubenb Edgan: Seen that, it just doesnt really tell me how to place 'wheels'
20:19 rubenb Sometimes, I could use like a salt dictionary :P
20:20 Edgan rubenb: I think wheel is a stand in word for admin functions. wheel is a linux group that can do things like su/sudo.
20:23 DanyC joined #salt
20:24 jcl_ joined #salt
20:25 jcl_ Hey all, is there a canonical way to do something only if another package is installed, e.g. only install php5-redis if redis-server is installed?
20:27 mavhq joined #salt
20:28 honestly onlyif
20:28 pipps joined #salt
20:28 PredatorVI joined #salt
20:29 rubenb jcl_: https://docs.saltstack.com/en/latest/ref/states/requisites.html#onlyif
20:29 mavhq joined #salt
20:30 jcl_ Ok, I thought a command may be the only way. I wasn't finding a native Salt way of querying whether a package exists in a recipe. Thanks!
20:31 fredrick joined #salt
20:32 mavhq joined #salt
20:33 pipps joined #salt
20:33 mikecmpbll joined #salt
20:34 fredrick Trying to run a state.apply on my master getting No Top file or external nodes data matches found top file looks like https://gist.github.com/anonymous/4822ab67788dbb023d7a936438d8f155
20:34 heaje Is it expected behavior that after a salt minion restart I have to re-run saltutil.sync_modules?
20:34 PredatorVI joined #salt
20:34 heaje Right now if I restart my minion, all custom grains/modules/states dissapear
20:35 mavhq joined #salt
20:35 Perilous_ joined #salt
20:36 heaje I've confirmed that if I restart my minion all directories under /var/cache/salt/minion/extmods get removed
20:37 antpa joined #salt
20:40 mavhq joined #salt
20:44 mikecmpbll joined #salt
20:44 heaje I should mention that I'm running hbase-hbase-regionserver-monds2.ut1.omniture.com.log
20:44 heaje oops
20:44 heaje I should mention that I'm running salt 2016.3.1 (Boron)
20:51 fredrick so if I set a grains.append it displays with a - before the key.  if I set the same when spinning up with salt-cloud it does not.  Could that be what is making my master not run against a grain?
20:52 mavhq joined #salt
20:53 fredrick https://gist.github.com/anonymous/524bdf4005c063070baad2d3e753975f
20:53 edrocks joined #salt
20:58 PerilousApricot joined #salt
20:59 wangofett joined #salt
21:04 pipps99 joined #salt
21:05 PerilousApricot joined #salt
21:07 ageorgop left #salt
21:13 subsignal joined #salt
21:18 flowstate joined #salt
21:18 mavhq joined #salt
21:21 mavhq joined #salt
21:24 mavhq joined #salt
21:25 mikecmpbll joined #salt
21:26 pipps joined #salt
21:27 mavhq joined #salt
21:28 fyb3r left #salt
21:30 Miouge joined #salt
21:42 mavhq joined #salt
21:45 jenastar joined #salt
21:45 fredrick If anyone cares it was the append.  I needed to grains.setval for it to be evaluated correctly in top.sls
21:45 mavhq joined #salt
21:50 flowstate joined #salt
21:53 aharvey joined #salt
21:56 woodtablet so, i see gravyboat has docka docka docka for user salt & docker-hub. Anyone know of other salt users using salt and AWS ECS ?
21:57 mavhq joined #salt
22:02 woodtablet found something from jacksoncage on the saltstack page from 2014; doest look like it is using aws ecs, but, i think i can transform it: http://jacksoncage.se/posts/2014/10/01/use-salt-to-manage-and-deploy-docker-containers/
22:07 mavhq joined #salt
22:12 jgarr why does the salt-minion start so many processes?
22:12 jgarr when it first starts it has 2 and some systems have 4+
22:12 jgarr not sure which each is doing
22:15 sagerdearia joined #salt
22:15 schemanic joined #salt
22:24 woodtablet left #salt
22:26 mavhq joined #salt
22:28 mavhq joined #salt
22:29 jenastar joined #salt
22:34 [dee] 5
22:34 [dee] left #salt
22:38 mavhq joined #salt
22:44 aea joined #salt
22:46 aea Is there a way to target the current minion using saltmine? I have an util function that returns the internal network ip via saltmine. I want to get that from saltmine and use it in a template.
22:48 pipps joined #salt
22:49 flowstate joined #salt
22:49 pipps joined #salt
22:58 pipps99 joined #salt
23:01 raiden joined #salt
23:04 aharvey joined #salt
23:10 alexhayes joined #salt
23:12 pipps joined #salt
23:13 pipps99 joined #salt
23:14 scsinutz joined #salt
23:17 bltmiller joined #salt
23:19 dendazen joined #salt
23:20 scsinutz we are bound to version 2015.5.10 and have found a bug (bug isnt important) - salt has given us a patch to fix it. I'm looking for opinions here, would you apply the patch to a running salt system using the patch command OR fork the salt code and apply the patch there and run through the build/unit test/rpm process to have a new salt rpm with the patch baked in?
23:20 Miouge joined #salt
23:21 scsinutz and let say there might be more patches in the future
23:22 woodtablet joined #salt
23:24 timoguin joined #salt
23:26 Miouge joined #salt
23:28 mavhq joined #salt
23:33 rylnd scsinutz did they give the fix only you because you are a business customer? would it make sense to send a PR to salt to add it to the the 2015.5.10 repo? did they already incorporate the fix?
23:33 mavhq joined #salt
23:35 rylnd scsinutz i would say it depends on how many machines you have. i would have environments with up to ~2000 workloads. i would want new VMs to be deployed with the patched version of salt and i would want to roll it out to all existing ones too (after extensive testing). so i would go with my own repo and my own packages. if you have 5 machines, you could patch it on every machine i guess
23:41 scsinutz yea the patch was rolled in 2015.8 but we can't upgrade just yet. I was thinking why double the efforts of building/testing and packaging since salt has taken care of that. I was thinking to put the patch in a rpm and have it run the patch command the %post section of the spec file and have a pkg.install state to install it. Looking at ~10k hosts
23:44 mavhq joined #salt
23:44 rylnd scsinutz depends how many resources you have and how much time you can spend. but doing that or your own version of the salt packages is the way i would go with that amount of hosts
23:45 nyx joined #salt
23:46 nyx_ joined #salt
23:48 scsinutz I'm not sold on rolling our own package versions with the patch baked in. My coworker wants to take that approach
23:50 flowstate joined #salt
23:51 pipps joined #salt
23:54 kiorky joined #salt
23:54 edrocks joined #salt
23:58 bltmiller joined #salt

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