Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-01-19

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

All times shown according to UTC.

Time Nick Message
00:06 hemebond Can't you have TCP listen on a different port until they're all switched over?
00:06 evidence you could configure it, and it would listen, but it didn't work properly
00:07 hemebond It didn't? That's odd.
00:07 evidence there was a ticket acknowledging such, the options made it sound like you could, but it didn't work in practice.  i believe it was cache and hatch discussing it.. but can't find it now
00:11 wendall911 joined #salt
00:14 wangofett evidence: what's a large minion count look like?
00:15 evidence certainly not the biggest install, but 12k
00:17 pipps joined #salt
00:18 evidence running it mostly across 2 beefy masters, with some cache/buffer tweaking, reserved use of the pillar, and the pillar cache it does pretty well.  the bulk of the boxes have ~400 states though, so it's starting to creep up.  zmq has high overhead and known memory leaks, so try to get to raw tcp
00:18 nanert left #salt
00:20 evidence we are still dealing with the but from < 2016.3.2 where it downloads the file over the salt:// source before checking the source_hash though also, so that should free up some resources
00:20 evidence s/but/bug/
00:20 hemebond You have 12k minions?
00:21 evidence somewhere around there.. we did a pretty big server consolidation when we switched to a new arch recently
00:21 hemebond Wooooow. I wonder if I'll ever have that many minions.
00:22 eThaD joined #salt
00:26 fyb3r joined #salt
00:27 fyb3r Is it possible to have two salt-minion daemons running on a single machine connect to a single machine running two syndic/master/minion daemons that connect to two totally separate master_of_masters?
00:28 Klas joined #salt
00:28 hemebond fyb3r: Possibly. You'd have to configure everything like the pid paths and such.
00:29 fyb3r because currently I have them all connecting to the point where I can see two totally separate sets of presence events coming into the master_masters, but when I go to test.ping the minion attached to the syndic, it gives me back true from the syndic, but the minion gives no response
00:29 fyb3r the weird part is that i see the job event come in on the minion
00:30 hemebond That's a really confusing setup that I don't really understand and will hopefully never need ☺
00:30 onlyanegg joined #salt
00:30 jaybocc2 joined #salt
00:30 fyb3r Lol. I could show a visio of it but I was worried if I linked it here no one would actually look
00:31 fyb3r and yeah, the problem is that we have two totally separate departments using salt now, and each needs their own daemons running on every machine -.- so me being the saltstack guy, I get to figure out how to run side by side daemons for my side
00:32 fyb3r I guess when I figure it out ill do a documentation write up for it lol, since there is nothing ont he site for it
00:33 spuder joined #salt
00:34 teclator_ joined #salt
00:36 djgerm1 joined #salt
00:50 fyb3r Ah I think I missed a few config settings.
00:51 Illusioneer joined #salt
00:59 nickabbey joined #salt
01:01 Illusioneer joined #salt
01:13 druonysus joined #salt
01:13 jaybocc2 joined #salt
01:22 jaybocc2 joined #salt
01:24 aw110f joined #salt
01:26 aw110f joined #salt
01:26 druonysus joined #salt
01:27 wangofett joined #salt
01:27 aw110f joined #salt
01:28 whytewolf fyb3r: so as the saltstack guy is you ass on the line when these two different departments are controlling the same file in different ways and break each others settings?
01:32 nZac_ joined #salt
01:33 rem5 joined #salt
01:35 wangofett joined #salt
01:38 markizano joined #salt
01:38 markizano huzzah!
01:38 markizano I finally found it!
01:38 markizano Now I need to create a POC so I can file a proper ticket about it...
01:39 djgerm1 this is weird https://github.com/saltstack/salt/issues/38719 and just found? is a for loop to apply states the best workaround so far?
01:39 saltstackbot [#38719][OPEN] No Top file or external nodes data matches found | Description of Issue/Question...
01:40 markizano The gist: define a state that manages a file. include that state in another state and make it run first. The derived state that runs first will pillar.get() as the template is processed the first time. When it comes to process the parent state, pillar.get() is called again, and you end up with duplicate data in the resulting file.
01:43 steve___ joined #salt
01:44 avalarion joined #salt
01:50 fyb3r whytewolf: Kind of. Less of the ass being on the line, more of the breaking my stuff. Im the DevOps engineer (which I know, buzzwords are fun arent they), so its me vs the systems admins who use salt but have no real idea how it works. They just come bother me to help them look at a memory leak here, or is it possible to do this with state files there.
01:52 druonysus joined #salt
01:54 whytewolf i feel sorry for you. if you get it working. i see pain and suffering in your future. not because of technical issues. but because of political snafus
01:56 jeet joined #salt
01:56 cainn joined #salt
01:57 raju joined #salt
01:57 cainn Hi, maybe i've missed a few explanatory words from the docs, but if i am using the orchestration runner, and my salt.state tgts multiple nodes, will the state be updated on each node in parallel?
01:57 cainn or one after the other?
01:59 hemebond cainn: I believe it's parallel
02:00 cainn is there a way to make it run the satte on one node, and then the next?
02:00 cainn or is that wrong
02:01 cainn wrong = unsalty :)
02:01 hemebond Not wrong, but seems silly. You can use "batch" maybe.
02:01 cainn ill look into that, thanks
02:01 cainn ooh, ill try setting up a bootstrap task that sets up an initial node
02:02 cainn ok, this will be fine, thanks!
02:05 upb joined #salt
02:09 gableroux joined #salt
02:24 eThaD joined #salt
02:27 wangofett joined #salt
02:29 tercenya joined #salt
02:31 Nahual joined #salt
02:31 fyb3r joined #salt
02:34 druonysus_ joined #salt
02:34 samkottler_ joined #salt
02:35 dem joined #salt
02:36 yetanotherzero joined #salt
02:36 iggy_ joined #salt
02:36 ventris joined #salt
02:36 bd joined #salt
02:36 spuder_ joined #salt
02:36 MikaT joined #salt
02:36 capn-mor1an joined #salt
02:37 goal_ joined #salt
02:37 kiorky_ joined #salt
02:37 iter_ joined #salt
02:37 Laogeodritt| joined #salt
02:37 MightyJoe joined #salt
02:37 Rkp_ joined #salt
02:37 eichiro_ joined #salt
02:37 aw110f joined #salt
02:38 Aikar_ joined #salt
02:38 Aikar_ joined #salt
02:40 Morrolan_ joined #salt
02:40 devnull joined #salt
02:40 notsetkeh joined #salt
02:40 tvinson_ joined #salt
02:40 v0rtex_ joined #salt
02:40 JPau1 joined #salt
02:40 themacproguy joined #salt
02:41 dober- joined #salt
02:41 scc joined #salt
02:41 shakalaka joined #salt
02:46 saltstackbot joined #salt
02:46 AbyssOne joined #salt
02:46 esc\ joined #salt
02:46 dijit joined #salt
02:46 fyb3r left #salt
02:46 sarlalian joined #salt
02:46 pocketprotector joined #salt
02:48 ilbot3 joined #salt
02:48 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.3.4, 2016.11.1 <+> 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
02:48 sh123124213 joined #salt
02:48 CeBe joined #salt
02:48 schinken joined #salt
02:49 andi- joined #salt
02:49 catpigger joined #salt
02:49 coredumb joined #salt
02:49 markizano joined #salt
02:50 jesusaur joined #salt
02:51 jav joined #salt
02:51 Horgix joined #salt
02:51 hemebond joined #salt
02:52 avalarion joined #salt
02:58 druonysus_ joined #salt
02:58 tom29739 joined #salt
03:00 berto- joined #salt
03:00 shalkie joined #salt
03:01 lazybear joined #salt
03:03 frew joined #salt
03:04 vaelen joined #salt
03:04 nethope joined #salt
03:05 evilrob joined #salt
03:13 alexanderilyin joined #salt
03:14 pipps joined #salt
03:19 druonysus__ joined #salt
03:27 evle joined #salt
03:32 debian112 joined #salt
03:44 q1x joined #salt
03:48 spuder joined #salt
03:56 hardyfresh joined #salt
04:11 jaybocc2 joined #salt
04:17 bowhunter joined #salt
04:22 bfritz joined #salt
04:25 eThaD joined #salt
04:40 onlyanegg joined #salt
05:01 spuder joined #salt
05:05 nickabbey joined #salt
05:09 yetanotherzero joined #salt
05:17 preludedrew joined #salt
05:27 eThaD joined #salt
05:31 nethershaw joined #salt
05:42 MTecknology frick... I always have issues running salt-call on salt-master containers
05:43 MTecknology can't figure out why either
05:51 yetanotherzero joined #salt
05:55 bocaneri joined #salt
05:58 jagguli hi, im trying to update a aoute53 mx record using the boto_rout53 state, but i cant get multiline records to work
06:00 spuder joined #salt
06:04 spuder_ joined #salt
06:08 mfilotto joined #salt
06:08 mfilotto hi
06:08 bocaneri joined #salt
06:09 mfilotto What would be the best way to reduce code duplication ?
06:09 mfilotto I always use a bunch of states to install ou purge de systemd unit
06:10 mfilotto So I wonder how to factorize this redundant code of states
06:10 mfilotto Would it be macros, or _states, or other ?
06:10 mfilotto thanks for your help
06:43 alssi joined #salt
06:49 impi joined #salt
06:50 sh123124213 joined #salt
06:51 stduolc joined #salt
07:00 nickabbey joined #salt
07:00 stduolc joined #salt
07:02 borgstrom joined #salt
07:03 brokensyntax joined #salt
07:19 aidin joined #salt
07:23 secrgb joined #salt
07:26 nidr0x joined #salt
07:28 eThaD joined #salt
07:31 ivanjaros joined #salt
07:36 hemebond mfilotto: Maybe a generic state that uses pillar data (like a formula does)
07:36 teclator joined #salt
07:38 andi^ joined #salt
07:39 MTecknology mfilotto: why don't you share an example of what you have? That suggestion about pillar data is usually a prtty solid one
07:41 MTecknology WOOHOO! Finally back to "salt '*' state.highstate" running cleanly again and deployed an "endpoint salt master" for my laptop 'n such. Next up, gotta write a preseed that installs salt and points it at that system so salt can set up my system for me.
07:41 MTecknology it'll feel weird not spending days realizing I forgot things.
07:47 MTecknology plug laptop into network, pxe boot, select option, feed in encryption keys, select hostname, wait until I accept a key in the endpoint master, wait a bit longer, restore data from backup, done
07:47 MTecknology still not stupidly trivial, but I can at least guarantee consistency and stop making myself angry with me
08:00 jaybocc2 joined #salt
08:11 eThaD joined #salt
08:16 samodid joined #salt
08:28 ronnix joined #salt
08:34 masber joined #salt
08:47 hvn joined #salt
08:47 hvn joined #salt
08:48 hvn joined #salt
08:48 hvn joined #salt
08:50 ravenx joined #salt
08:50 ravenx for git pillars, is it possible to have different repositories for each project?
08:50 ravenx like, i have project A, and want to populate templates with its own data
08:50 ravenx and project B should only be populating templates with its own data
08:51 ravenx so far i haven't found a way to do that.
08:51 hemebond ravenx: Depends how you're defining and organising "projects".
08:51 ronnix joined #salt
08:51 hemebond Sounds like something I would use environments for.
08:51 hemebond Environments are supported in pillars.
08:51 ravenx ah i see
08:51 hemebond And gitfs maps branches to environments.
08:51 ravenx basically i have app-1, and app2, two are completely different things, with their own branches.
08:52 ravenx ah i see. so branches to environments.  which make sense.
08:52 ravenx but can i do something like "salt 'server' state.sls app-1"
08:52 ravenx and have the app-1 be mapped to a git repo?
08:52 ravenx and app-2 would be it's own?
08:52 JohnnyRun joined #salt
08:53 hemebond No, that's not how environments are applied to minions.
08:53 ravenx hm..
08:53 ravenx then what is this thread about:
08:53 ravenx https://github.com/saltstack/salt/issues/30869
08:53 saltstackbot [#30869][MERGED] git pillar: do not see all pillar data with multiple repos in 2015.8.4 | Here is my master configuration file:...
08:53 hemebond You're using a top.sls for your pillars. yes?
08:53 ravenx cuz i see this user use "pillars_test2.git"   "pillars-test.git"
08:53 ravenx correct
08:54 hemebond Do you have a diagram or something on how you're trying to structure your apps and projects?
08:54 hemebond It sounds like you're trying to do something complex for something simple.
08:54 hemebond Like... if you apply state app-1, then it will read the pillar data for the minion you're applying to.
08:55 hemebond Now, are you trying to apply state app-2 to the same minion and have it read the same pillar keys but wanting different values?
08:56 ravenx i don't have a diagram per-se.  so i will try my best to describe:
08:56 ravenx i have two apps, which need their configs to be loaded.
08:56 ravenx right now i have a /srv/pillar/app-1/init.sls and a /srv/pillar/app-2/init.sls   (both contain the key value pairs)
08:56 ravenx which is cool, and a /srv/salt/app-1/  and a /srv/salt/app-2
08:56 ravenx their config templates get populated.  but my problem is:
08:57 ravenx everytime i want to update the key-value pairs, i gotta update the /srv/pillar/app-1/init.sls file, or the app-2's pillar init.sls file.
08:57 hemebond That sounds entirely reasonable.
08:57 ravenx it would be great if it could just place the init.sls containing the K:V pairs, in app-1 repository where the code is. and have salt populate it from there.
08:58 ravenx so, i did get it to work with one repo!     so that i don't need /srv/pillars/app-1 anymore
08:58 hemebond You want the app-1 config in the state?
08:58 ravenx but things get weird when i add a second git repo in my /etc/salt/master
08:59 nickabbey joined #salt
08:59 canci joined #salt
08:59 hemebond I'll be honest with you: that sounds like a weird setup you've got there.
09:00 hemebond It almost sounds like you're trying to do something similar to formulas.
09:00 hemebond You could "add another repo" by using mountpoints https://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html#mountpoints
09:00 hemebond Or do what I do with my formulas.
09:00 hemebond Clone the repo to /srv/salt/formulas/blah
09:00 hemebond Then symlink from /srv/salt/states/base/blah -> /srv/salt/formulas/blah
09:01 ravenx ah that's what i do too
09:01 mariusv joined #salt
09:01 mariusv joined #salt
09:01 ravenx i am using formulas
09:01 ravenx ah i could symlink....yeah, true.
09:02 candyman88 joined #salt
09:03 eThaD joined #salt
09:04 angel_dark joined #salt
09:04 aberdine joined #salt
09:05 keimlink joined #salt
09:10 bookwar joined #salt
09:16 jaybocc2 joined #salt
09:21 s_kunk joined #salt
09:23 madboxs joined #salt
09:25 teclator joined #salt
09:27 moeyebus9_ joined #salt
09:30 antpa joined #salt
09:30 madboxs hello all
09:30 madboxs When i get pillar data on jinja template.
09:30 madboxs How can i prevent  sorting or ordering
09:30 madboxs I want get output like a my write seq.
09:31 jaybocc2 joined #salt
09:36 saltnewbie joined #salt
09:38 hemebond madboxs: What kind of pillar data?
09:38 hemebond It should come through in the same order.
09:38 madboxs iptables .
09:38 madboxs my version 2015.8
09:38 eThaD joined #salt
09:39 hemebond Dicts are stored as OrderedDicts and lists are always ordered in Python.
09:39 madboxs I see.
09:39 hemebond So I'm not sure what issue you are having with your data.
09:40 AndreasLutro in reality they rarely do
09:40 AndreasLutro I use the "dictsort" filter if I want the order to be the same consistently
09:40 madboxs Yep. anyway. I will be use dictsort or sort . If i cant it.
09:41 madboxs like a ID{numbmer}
09:43 sfxandy joined #salt
09:43 madboxs THanks all :)
09:44 madboxs It was helpful for me.
09:44 madboxs joined #salt
09:46 cxtud joined #salt
09:51 sh123124213 joined #salt
09:54 moeyebus9_ joined #salt
09:55 cxtud Hello, can grains list the installed programs on windows?
09:56 Hybrid joined #salt
09:58 hemebond cxtud: I don't think there is a default grain to do that but a custom grain could.
09:58 hemebond (or use WSUS)
10:08 JohnnyRun joined #salt
10:10 necronian joined #salt
10:15 saltnewbie joined #salt
10:18 antpa For some reason I'm unable to install the package php.ng.memcached and php.ng.imagick when using the php formula. Has anyone else experienced this?
10:19 jhauser joined #salt
10:19 antpa https://gist.github.com/anthonyscolaro/aeb2c6c56ebf526f4509c55acfb9b57e
10:20 antpa Though I'm able to install other php.ng packages
10:21 aidin joined #salt
10:24 sh123124213 joined #salt
10:24 daxroc Can you use list comprehensions in salt-jinja ?
10:24 AndreasLutro no
10:24 daxroc * on a set myvar = [....]
10:25 evle joined #salt
10:25 cxtud hemebond: thanks, will use salt '*' cmd.run "wmic product get name" in a grain
10:28 saltnewbie joined #salt
10:29 xet7 joined #salt
10:38 vifon I've got 2 minions attached to my master, one of which is on the master server itself. When I perform test.ping, the remote minion returns almost immediately but the local minion usually timeouts and returns only on 2nd-3rd try. What may cause it?
10:41 masber joined #salt
10:43 dober joined #salt
10:45 babilen vifon: Do you see that behaviour after the initial ping or are they returning immediately once you've "woken" them?
10:45 mavhq joined #salt
10:46 vifon They are returning immediately afterwards.
10:47 babilen vifon: Try setting ping_on_rotate to True in the master configuration
10:47 DanyC joined #salt
10:48 babilen (the documented configuration files discusses the issue)
10:48 vifon I don't see it in my /etc/salt/master. Is that a new-ish option?
10:48 babilen Not really .. but that depends on what you consider to be "new" :)
10:48 babilen Which version are you using?
10:48 babilen https://docs.saltstack.com/en/latest/ref/configuration/examples.html
10:48 vifon salt 2014.1.13 (Hydrogen)
10:48 babilen That's ancient
10:49 vifon Debian Jessie FWIW.
10:49 babilen Well, jessie was released a long time ago and is stable (i.e. "not changing")
10:49 babilen Why don't you install a newer version from jessie-backports ?
10:50 rylnd joined #salt
10:50 vifon I didn't need it before. I'll do it in a few hours.
10:50 babilen We've (Debian Salt Team) packaged 2016.3.4+ds-2~bpo8+1 and we'll probably upload 2016.11.1+ds-1 soon
10:51 babilen Alternatively you can grab 2016.11 from the third party Saltstack repositories -- http://repo.saltstack.com/#debian
10:52 babilen There were some problems with 2016.11 still, so 2016.3 might not be a bad idea
10:52 babilen Personally I'd go with the backport, but it's entirely up to you
10:52 babilen Stretch will be released with 2016.11 (freeze is 5th of February)
10:53 vifon Installing from the backports right now. It's not a critical server as you might have guessed by the minion count so I'll just do it. :)
10:53 babilen Sure
10:58 vifon Seems to be working. I'll check if the minions will be responsive tomorrow.
10:58 vifon What might be the reason the other minion didn't have this issue?
11:00 nickabbey joined #salt
11:00 babilen There were all sorts of bugs in 2014.1 -- Determining what exactly caused this would probably take quite some time. It could very well be due to the key rotation, but that should have affected both minions
11:01 vifon The other minion is running Ubuntu 14.04 with salt-minion 0.17.5.
11:01 vifon I guess I should update it too.
11:04 cxtud the resposne time of test.ping or a cmd.run for windows is slow than unix. Is this normal?
11:09 amontalban joined #salt
11:09 amontalban joined #salt
11:11 eThaD joined #salt
11:12 Rumbles joined #salt
11:12 sh123124213 joined #salt
11:16 eThaD joined #salt
11:19 teclator joined #salt
11:24 secrgb joined #salt
11:25 babilen vifon: Yes, 0.17.5 is a case for the archeology department :)
11:25 secrgb hi
11:41 eThaD joined #salt
11:43 jaybocc2 joined #salt
11:52 ashmckenzie joined #salt
11:58 jaybocc2 joined #salt
11:59 manji babilen, lol
12:00 manji babilen, we have a frontend dev who holds a bachelor in archeology, for real
12:00 manji he can be useful for cases like this one
12:05 amcorreia joined #salt
12:08 aidin joined #salt
12:09 dariusjs joined #salt
12:13 EvaSDK is github @gravyboat hanging in there ?
12:15 ashmckenzie joined #salt
12:18 jwghvfwlrvn3e joined #salt
12:18 hvn joined #salt
12:18 hvn joined #salt
12:20 masber joined #salt
12:49 antpa joined #salt
12:59 EvaSDK damn, he stepped down from maintaining formulas :/
13:00 EvaSDK anyone I can poke for formulas PR review/merge ?
13:00 jhauser joined #salt
13:01 nickabbey joined #salt
13:03 honestly EvaSDK, I'm a contributor on saltstack-formulas, and apparently that gives me write permissions :)
13:03 honestly which formula?
13:05 EvaSDK postfix-formula
13:05 ssplatt joined #salt
13:05 EvaSDK has 2 open PR, one is mine and should solve a problem reported in bug #50, second I reviewed and should be fine to go in
13:09 honestly I'm going to test them and find someone from the saltstack team to merge them or tell me to go ahead and do it myself :)
13:10 EvaSDK thanks
13:13 honestly I wish I knew which of my salt formulas are actually in salt-formulas... github doesn't seem to give me an easy way to find out :D
13:21 numkem joined #salt
13:22 darioleidi joined #salt
13:27 zer0def joined #salt
13:31 dariusjs joined #salt
13:33 Triple_ joined #salt
13:34 ronnix joined #salt
13:35 moeyebus9__ joined #salt
13:37 EvaSDK github lacks some kind of group notion for your own repos
13:37 EvaSDK like it does for forks, source, private, etc
13:38 AndreasLutro not really... if your repos move to an organization, they're not yours anymore
13:39 EvaSDK true
13:39 EvaSDK I would still like to organize them somehow :)
13:39 EvaSDK like I don't fork all formulas I use like documentation suggests because it would just be super annoying to manage
13:45 numkem joined #salt
13:46 evle1 joined #salt
13:55 Brew joined #salt
13:57 AndreasLutro at least you can see where your forked formula was forked from, so it's fairly easy to add the original repo as an upstream if you want to merge upstream changes in
13:58 mikecmpbll joined #salt
14:03 sh123124213 joined #salt
14:06 cxtud I have 6 syndics and 3 masters
14:07 orion left #salt
14:08 cxtud ignore, fixed it
14:08 gableroux joined #salt
14:10 jaybocc2 joined #salt
14:11 Tanta joined #salt
14:13 mikecmpbll joined #salt
14:17 rylnd today i upgrade my salt master from 2016.3.3 to 2016.11.1. since then i am having trouble with my slack engine. it logs now "has an invalid type of dict, a list is required for this value". even though the file is the same before the update. has something changed?
14:18 rylnd anyone else experienced this?
14:18 dyasny joined #salt
14:21 Ish_ joined #salt
14:21 Ish_ Hi people.
14:25 jaybocc2 joined #salt
14:26 Rumbles I managed to break a few of my salt minions (I created a pillar called proxy - which was a bad idea) I have changed this on my master, but some of my minions are complaining about None not being iterable still... is it possible to remove the cache on a salt minion so they can forget the bad confirm and reconnect?
14:26 Rumbles currently all the salt minions are constantly restarting :/
14:27 Rumbles https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.saltutil.html <<< this says the safetst way is to delete the cache files, but is there a list of files I should delete?
14:30 ehjax joined #salt
14:37 Dan_1776 Rumbles:  I creatd pillars called "network:proxy:http_proxy, network:proxy:https_proxy, network:proxy:ftp_proxy, and network:proxy:no_proxy" and have not run into any issues yet.
14:37 SaucyElf joined #salt
14:37 Rumbles i created a pillar called proxy
14:37 Rumbles it's used by salt as a default for proxying traffic
14:37 Dan_1776 Not sure if you used this nested pillar format or not.  Hopefully your issues are not with that format but if it is let me know so I can undo it.
14:38 Rumbles it's not a good idea
14:38 Dan_1776 Just "proxy" is not a good idea, right?
14:38 Rumbles yeah
14:38 Rumbles don't do that
14:38 Rumbles anyone know the "right" way to clear the cached info on a moinion? struggling to find an answer :/
14:38 Rumbles minion*
14:39 AndreasLutro what cached info?
14:39 Dan_1776 Ok, thanks.  I didn't even think about the issue you ran into.  My nested format was for a different reason.
14:39 AndreasLutro everything?
14:39 ravi____ joined #salt
14:39 Rumbles minions can't connect to my master at the moment
14:39 Rumbles I think it has cached my badly named pillar on the minion
14:39 Rumbles which needs clearing out
14:40 AndreasLutro stop the minion, rm -rf /var/cache/salt/*, start it again
14:40 Rumbles I don't mind clearing everything if that's easier
14:40 Rumbles ok, simple, nice
14:40 Rumbles thanks AndreasLutro
14:40 Rumbles damn
14:40 Dan_1776 I thought there was a refresh command you can use via 'salt-call'.
14:40 Rumbles that didn't help
14:41 netcho joined #salt
14:41 AndreasLutro there is, but if your minion can't connect to the master you're not going to be able to run it
14:41 Dan_1776 restarting the minion should do it too since it gets the pillars from the master.
14:41 ssplatt salt-call saltutil.refresh_pillar
14:41 Dan_1776 Yeah, you will have to do hands on keyboard.
14:42 Dan_1776 RDP,SSH depending on OS.
14:42 Rumbles minion is just doing this over and over: http://paste.fedoraproject.org/530846/83691814/
14:42 Dan_1776 Maybe try setting the "proxy" pillar to ""
14:43 Dan_1776 Force it to clear what was previously there.  Not sure if that would work but it might.
14:43 Rumbles I'v deleted the folder on the master
14:44 AndreasLutro what version are you running Rumbles?
14:44 Dan_1776 Do you still have the 'proxy' pillar set in /srv/pillar/ though?
14:45 Rumbles Lithium (still)
14:45 Rumbles salt 2015.5.3 (Lithium)
14:45 Rumbles there is no proxy folder in /srv/pillar/ nothing in the top file either
14:46 AndreasLutro `grep -r proxy /srv/pillar` maybe
14:47 AndreasLutro also open salt/scripts.py on the minion and change line 86 to log.error('Proxy Minion failed to start: ', exc_info=True)
14:50 Rumbles so, I have a file pillar/nginx-proxy/init.sls which had the first line: proxy: so would that pillar be detected as nginx-proxy or proxy?
14:51 Rumbles does salt care about the name of the pillar folder, or the first line in the pillar?
14:51 Rumbles oh, clearly the first line matters
14:51 Rumbles hosts that were broken are no longer broken
14:52 dxiri joined #salt
14:52 * Rumbles gets back to breaking things
14:52 Rumbles thanks for the help (again) AndreasLutro !
14:53 AndreasLutro Rumbles: in terms of SLS files, the filename doesn't matter at all except for matching in top.sls, includes etc. - pillar data is all merged at the root level
14:53 mpanetta joined #salt
14:54 SaucyElf joined #salt
14:56 mpanetta joined #salt
14:57 Ish_ I'm having an issue with http file storage and multiple sources, I raised the issue in the salt-users google group but would appreciate it if someone here could have a look and make any suggestions...
14:57 Ish_ https://groups.google.com/forum/?hl=en#!topic/salt-users/7aKPi6rX0r4
14:58 AndreasLutro Ish_: I'd open a github issue as that seems like a bug
14:59 nickabbey joined #salt
14:59 Ish_ It seemed that way to me too but I wanted a second opinion before raising an issue
15:03 spuder joined #salt
15:05 dxiri joined #salt
15:06 dariusjs joined #salt
15:08 irctc741 joined #salt
15:09 _Cyclone_ joined #salt
15:10 snc joined #salt
15:15 beardedeagle joined #salt
15:17 PatrolDoom joined #salt
15:19 mpanetta joined #salt
15:20 racooper joined #salt
15:20 dyasny joined #salt
15:25 nickabbey joined #salt
15:27 ravenx can someone help me with my gpg decryption of my pillar data?
15:27 ravenx it isn't decrypting
15:27 ravenx despite added the #!jinja|yaml|gpg header in my init.sls
15:27 ravenx could it be that my gpgkeys/ folder's permission is too relaxed?
15:28 ssplatt gpg should be first iirc
15:28 ravenx ssplatt: i was followign this:
15:28 ravenx https://docs.saltstack.com/en/latest/ref/renderers/all/salt.renderers.gpg.html
15:28 ravenx it had the #!yaml|gpg in their example
15:28 AndreasLutro last is correct
15:29 ssplatt hmm yeah ok i couldn’t remember how our line setup
15:29 ravenx :(
15:29 ravenx the last?
15:29 AndreasLutro unless you gpg encrypt the whole yaml contents I guess
15:29 ravenx wait, i have to encrypt the entire yaml?
15:29 ssplatt no
15:29 ravenx can't i just select certain key value pairs
15:29 ravenx and leave some unecrypted
15:29 ssplatt 1: check your indents
15:29 ravenx ?
15:30 ssplatt and the |
15:30 AndreasLutro I said "unless you gpg encrypt the whole yaml contents", you don't have to do it
15:30 ravenx AndreasLutro: i can do it per key right?
15:30 ssplatt got an example you can put in gist/pastie?
15:31 ssplatt so we can see your code
15:31 ravenx sure i can do that:
15:32 ravenx https://paste.debian.net/909549/
15:32 ravenx so basically, saltutil.refresh_pillar is okay
15:33 ssplatt looks ok there
15:33 ravenx and pillar.items shows it
15:33 ravenx but shows the LITERAL gpg message
15:33 ravenx the actual thing instead of the decrypted result.
15:33 ravenx so i also have my /etc/salt/gpgkeys symlinked to my ~/.gnupg
15:33 ssplatt symlink may not be good
15:34 ravenx :o
15:34 ravenx uh oh
15:34 ssplatt not sure, never tried
15:34 ravenx i do not know how to duplicate my current one.
15:34 ssplatt but, the salt user needs it
15:34 ravenx do i simply copy it's contents?
15:34 ssplatt probably can’t see in your home dir
15:34 dxiri joined #salt
15:34 ssplatt that’s my guess
15:34 ravenx wait, what can't s'ee in my hom edir?
15:34 ssplatt salt isn’t root
15:35 ssplatt salt shouldn’t be looking in your homedir as basic cecurity
15:35 ravenx correct
15:35 ravenx so you're saying that
15:35 ravenx because i symlinked /etc/salt/gpgkeys -> /home/ravenx/.gnupg
15:35 ravenx it chokes while resolving the link?
15:35 ssplatt probably.
15:35 ssplatt is your dir owned by you and chowned to 700?
15:36 ravenx ~/.gnupg is owned by me, yes.  and is 0700
15:36 ssplatt # mkdir -p /etc/salt/gpgkeys
15:36 ssplatt # chmod 0700 /etc/salt/gpgkeys
15:36 ssplatt # gpg --gen-key --homedir /etc/salt/gpgkeys
15:36 ravenx i did that....but there was a conflict.
15:36 ssplatt https://docs.saltstack.com/en/latest/ref/renderers/all/salt.renderers.gpg.html
15:36 ravenx let me delete that /etc/salt/gpgpkeys and try again, hang on.
15:36 ravenx yeah i was following that guide until poop hit the fan.
15:37 ravenx also:   salt-master isn't running as root
15:37 yetanotherzero joined #salt
15:37 ravenx does that play a role?
15:37 ravenx it is run my ravenx. a normal user.
15:37 ssplatt runs as the salt user, right?
15:38 ravenx nope, it runs as myself.
15:38 ravenx whcih, is the salt user.
15:40 ssplatt double checked my perms.  gpgkeys/ is root:root 700
15:40 ssplatt all files inside are 600, root:root
15:40 ravenx i see
15:40 ravenx yeah
15:40 ravenx that may be why mine is fucking up.
15:40 ravenx i wonder if i can simply cop the contents of .gnupg/ into /etc/salt/gpgkeys and tweak the perms
15:41 ssplatt probably.
15:42 dxiri joined #salt
15:43 keltim joined #salt
15:43 ravenx alright
15:43 ravenx let' stry this again.
15:44 ravenx hm, my gpgkeys/ is root:root and 0700
15:44 anotherzero joined #salt
15:44 ravenx gpg: WARNING: unsafe ownership on homedir '/etc/salt/gpgkeys'
15:44 ravenx but i got this.
15:44 ravenx weird as heck.
15:48 Hydrosine joined #salt
15:49 jhauser joined #salt
15:51 dyasny joined #salt
15:53 aidin joined #salt
15:54 fredvd joined #salt
16:02 sarcasticadmin joined #salt
16:02 cyborg-one joined #salt
16:08 debian112 joined #salt
16:09 hackel joined #salt
16:11 Illusioneer joined #salt
16:16 spuder joined #salt
16:17 eThaD joined #salt
16:17 yuhl___ joined #salt
16:23 sp0097 joined #salt
16:24 sp0097 left #salt
16:32 _JZ_ joined #salt
16:36 bluenemo joined #salt
16:37 jaybocc2 joined #salt
16:51 nickabbey joined #salt
16:52 jaybocc2 joined #salt
16:55 Trauma joined #salt
17:00 numkem joined #salt
17:02 onlyanegg joined #salt
17:05 tiwula joined #salt
17:13 maxnstuff joined #salt
17:13 rallytime joined #salt
17:15 pipps joined #salt
17:19 nixjdm joined #salt
17:20 bowhunter joined #salt
17:27 eThaD joined #salt
17:27 woodtablet joined #salt
17:41 markizano joined #salt
17:41 morissette joined #salt
17:44 Lionel_Debroux joined #salt
17:47 anotherzero joined #salt
17:48 writtenoff joined #salt
17:56 nickabbey joined #salt
17:59 tercenya joined #salt
18:00 woodtablet left #salt
18:04 pipps joined #salt
18:06 promorphus joined #salt
18:08 pin joined #salt
18:08 promorphus Hey guys, I've got a state that builds docker containers (using dockerng), I was wondering if you're able to pass it arguments at build time? There doesn't seem to be anything in the docs about it, but it's a pretty commonly used thing in docker builds.
18:08 * pin DROP!
18:08 _JZ_ joined #salt
18:08 pin left #salt
18:10 tercenya joined #salt
18:11 MTecknology promorphus: that stuff isn't part of dockerfile?
18:12 MTecknology I see there's a "CONTAINER CONFIGURATION PARAMETERS" about here -> https://docs.saltstack.com/en/latest/ref/states/all/salt.states.dockerng.html
18:12 promorphus it is, but that's the exact point. You can set up a default build arg, and use it as part of the file, and on the commandline you can offer a new value for the arg as part of the build process
18:12 promorphus rightl, those are after the build, and are part of running the container
18:15 ronnix joined #salt
18:16 promorphus As an example, if you click to the docker docs, https://docs.docker.com/engine/reference/commandline/build/, and search for 'build-arg', you can see what im referring to
18:19 MTecknology I'd have to look at the source code for the module to make any guesses. I'm happily avoiding docker for as long as possible. :P
18:19 promorphus *interested* why's that?
18:20 MTecknology It seems like a disorganized mess of broken features and bugs that only aids to generate large-scale clusterfucks... but that's just my opinion
18:21 * whytewolf agrees with MTecknology opinion
18:21 MTecknology I'm too tired, too hungry, too un-caffeinated at the moment to dive into that off-topic conversation, but maybe over lunch
18:22 whytewolf and unforchantly i HAVE used docker for working in a production enviroment. it was a pain in the ass
18:22 whytewolf and really doesn't offer that much seperation
18:22 ivanjaros joined #salt
18:23 whytewolf it is a solaris zones wanna be
18:24 promorphus lol, im currently using it in a few production environments, and not really having any issues with it
18:24 promorphus think it might be a tool-for-the-job thing
18:24 higuita joined #salt
18:24 Eugene My mental picture of Docker is the "boat docking fail" section of Youtube
18:25 MTecknology I didn't know that was a section but really wanna look after work now
18:25 MTecknology promorphus: I don't see "build-arg" in either docker module. Might need a PR.
18:25 MTecknology https://github.com/saltstack/salt/blob/develop/salt/modules/dockerng.py
18:26 Trauma joined #salt
18:26 swills joined #salt
18:26 whytewolf honestly looking at the example of build_arg it looks like what the enviroment setting is for
18:26 promorphus It's got a different use, but yeah, it's similar
18:27 higuita I'm trying to use vault with salt-ssh and i use this info: https://docs.saltstack.com/en/latest/ref/pillar/all/salt.pillar.vault.html
18:27 promorphus in any case, i can't set either one as part of the build, and that's what i need. any ideas other then just running it the command line via cmd.run?
18:27 higuita i add both first block and the ext_pillar to master
18:27 higuita running salt-ssh host pillar.items i get this:
18:27 higuita [DEBUG   ] Requesting URL https://None:None/v1/secret/salt using GET method
18:27 Eugene https://youtu.be/RrrDLdeL2HQ
18:28 higuita looks like it is not loading the settings
18:29 higuita i already tried to rename both the config and the ext_pilar vault:  to the same name, still fails
18:29 higuita i'm doing something wrong or this is broken?
18:29 higuita salt-ssh 2016.11.1 (Carbon)
18:29 whytewolf higuita: salt-ssh is a speciel snow flake. i wouldn't doubt it is broken.
18:30 higuita that is what i suspect... i just come here to check before open a bug report
18:33 samodid joined #salt
18:36 MTecknology Eugene: How the crap is this possible?! https://youtu.be/-J6TTeL-wNs?t=1m15s
18:37 * MTecknology stopped getting anything that resembles work does...
18:37 MTecknology done*
18:38 tercenya joined #salt
18:39 SaucyElf joined #salt
18:40 s_kunk joined #salt
18:40 s_kunk joined #salt
18:41 stooj joined #salt
18:43 bowhunter joined #salt
18:45 johnkeates joined #salt
18:46 one joined #salt
18:48 spuder_ joined #salt
18:55 nZac joined #salt
18:55 spuder joined #salt
18:58 nickabbey joined #salt
18:59 beardedeagle joined #salt
19:01 nickabbey joined #salt
19:13 Sketch so i have a script that installs a package which causes osrelease to be updated.  i need salt to pick up that it's been updated, but this doesn't happen until i do a service salt-minion restart.
19:13 Sketch salt-call grains.get osrelease on the minion does show the grain as being updated, but salt minion grains.get osrelease on the master doesn't show it updated
19:14 Sketch and when i run the state, it doesn't seem to get updated...even if i do a module.run saltutil.sync_grains in it
19:14 Sketch even subsequent runs from the master still don't see the grain as being updated
19:14 Sketch unless i restart the minion (2016.3.4)
19:14 Sketch suggestions? :)
19:23 pipps joined #salt
19:23 aidin joined #salt
19:24 pipps99 joined #salt
19:27 nidr0x joined #salt
19:30 Praematura joined #salt
19:33 AvengerMoJo joined #salt
19:33 woodtablet joined #salt
19:34 raspado joined #salt
19:37 tercenya joined #salt
19:40 toastedpenguin joined #salt
19:40 mikecmpbll joined #salt
19:43 keimlink joined #salt
19:44 necronian joined #salt
19:46 nZac joined #salt
19:46 fyb3r joined #salt
19:47 toastedpenguin joined #salt
19:53 nickabbey joined #salt
19:53 nickabbey joined #salt
19:54 dxiri joined #salt
19:57 netcho joined #salt
20:00 om2 joined #salt
20:01 beardedeagle joined #salt
20:10 om2 joined #salt
20:16 iggy thanks MTecknology
20:17 Edgan joined #salt
20:20 pipps joined #salt
20:23 tapoxi hey guys I'm getting a "TypeError: must be convertible to a buffer, not OrderedDict" when trying to provision with salt-cloud
20:24 iggy MTecknology: and about your monitoring idea, we basically have unit tests written as validate states
20:24 Eugene MTecknology - the intersection of poor seamanship and momentum is a hell of a surprise
20:24 pipps joined #salt
20:25 Eugene The one at 1:36 is a famous favorite of mine
20:26 sjorge joined #salt
20:28 hackel joined #salt
20:31 nickabbey joined #salt
20:36 xet7 joined #salt
20:37 nickabbey joined #salt
20:37 mvensky joined #salt
20:37 UtahDave joined #salt
20:39 tercenya joined #salt
20:40 tapoxi this is really weird, apparently there is a bug in salt-cloud but I seem to be hitting it with a very simple userdatascript
20:40 hemebond tapoxi: Using 2016.11?
20:40 tapoxi hemebond: yes
20:41 hemebond AWS?
20:41 tapoxi yup
20:41 hemebond Yeah, probably want to downgrade :-)
20:41 tapoxi ruh roh
20:41 tapoxi what happened
20:41 UtahDave tapoxi: can you pastebin what you're attempting and the output you're getting?
20:41 tapoxi there an open bug for it I can follow?
20:42 tapoxi UtahDave: http://pastebin.com/UVRDQ1LP
20:42 hemebond https://github.com/saltstack/salt/issues/33194 ?
20:42 saltstackbot [#33194][OPEN] salt-cloud: EC2 userdata template error | Description of Issue/Question...
20:46 sfxandy joined #salt
20:46 UtahDave Hm. yeah, that looks like the same or similar error, hemebond.
20:47 tapoxi yeah that looks like the bug
20:47 tapoxi but my userdata is really simple and worked with the last release of salt-cloud
20:47 tapoxi http://pastebin.com/kjvPxGtA
20:48 hemebond I think it will affect you even if you're not using any templating.
20:48 mvensky joined #salt
20:48 hemebond I have a custom runner to do templating ion 2016.3.4 and was still affected.
20:49 hemebond Even though salt-cloud was getting a regular YAML file.
20:50 druonysus__ joined #salt
20:50 tapoxi threw a comment on the bug. hemebond did you downgrade?
20:51 hemebond I did. I upgraded to 2016.11rc2 to test it and found it all broken so went back to 2016.3.4.
20:51 hemebond Unfortunately it wasn't fixed before the full 2016.11 release.
20:52 tapoxi can you just downgrade salt-cloud or does that have deps on master and salt?
20:52 hemebond Uh, I think the issue is in the salt-master modules.
20:52 fyb3r Still cannot figure out why syndic refuses to pass up the job results from the minions to master_master -.-
20:52 hemebond You could try just downgrading salt-cloud. My master was installed using PIP so I just downgraded the whole thing.
20:53 tercenya joined #salt
20:54 hemebond tapoxi:  Might want to use ``` blah ```to format your code.
20:54 debian112 joined #salt
20:54 tapoxi I updated the comment
20:54 SaucyElf_ joined #salt
20:55 tapoxi stupid markdown
20:56 fyb3r crap now I see
20:56 fyb3r apparently my master_master does not have the keys for the minions listed....
20:58 pipps joined #salt
21:11 squishypebble joined #salt
21:11 orianbsilva_ joined #salt
21:12 gableroux hey there, quick question concerning salt-cloud, How can I get the image id from this: https://aws.amazon.com/marketplace/pp/B00WUNJIEE ?
21:13 gableroux Oh sorry I have to go :(
21:14 woodtablet left #salt
21:15 SaucyElf joined #salt
21:15 tapoxi gableroux: click continue then 'manual launch'
21:22 tercenya joined #salt
21:25 kbaikov joined #salt
21:28 debian112 joined #salt
21:29 pipps joined #salt
21:32 MTecknology iggy: how do failures trickle up to a notification system? I was considering something with beacons. My problem with most systems is that they're very heavy weight for a job that I would say should be pretty light and easy.
21:32 MTecknology and how do things get cleared?
21:37 spuder joined #salt
21:38 nZac joined #salt
21:39 vladr joined #salt
21:42 tapoxi MTecknology: you using salt for monitoring?
21:43 MTecknology thinking about it
21:44 tapoxi I've been thinking about Thorium to manage critical thresholds/clearing
21:44 tapoxi then for alerting just the pagerduty exec module
21:46 MTecknology oh?
21:46 dendazen joined #salt
21:46 MTecknology pagerduty is looking more and more sexy
21:47 teclator joined #salt
21:48 MTecknology eh, but $10/mo is a bit spendy for me
21:49 whytewolf eh, i use pushover. and setup rules in ifttt if something doesn't support it directly
21:52 UtahDave left #salt
21:52 teclator joined #salt
21:56 nickabbey joined #salt
21:56 smcquay joined #salt
21:57 dxiri joined #salt
21:57 MTecknology pushover looks nice
22:02 pipps99 joined #salt
22:03 tercenya joined #salt
22:04 iggy MTecknology: the validate failures get sent to our slack I think (or they go to the NOC... not super uptodate on that side of it since my shit always works...)
22:07 pipps joined #salt
22:07 MTecknology lol.. that's part of my problem. Most the stuff never has issues so monitoring has never been much of a thought
22:07 vodik Edgan: find help with base64 encoding files inside yaml? sorry, i haven't been around
22:08 tercenya joined #salt
22:10 Edgan vodik: I got it working, but then ran into a bug in salt-ssh. It doesn't deal with binary pillar data. It uses json for transport of pillar data to remote systems.
22:11 vodik ooh right
22:11 vodik isn't that pluggable? maybe i misundestood. i never dove that deep into how salt works
22:12 nZac joined #salt
22:13 Edgan vodik: there is an open issue, needs to be changed to using something like msgpack instead of json. It will require waiting or writing a PR.
22:14 Edgan vodik: I use salt-ssh for testing. So it is annoying any time they aren't equivalent, but I technically don't need this binary data in salt-ssh, yet.
22:14 woodtablet joined #salt
22:17 necronian joined #salt
22:18 vodik Edgan: i guess another option is to always host is somewhere outside of salt and curl it in - but i guess that defeats the pillars being secret bit
22:22 fyb3r So I finally got everything communicating properly, I believe, and now I see that I get this error on the master_of_masters --->   https://gist.github.com/fyb3r/0867e20c4dcb93af8e3abb56ffb6e814
22:24 ronnix joined #salt
22:33 Edgan vodik: that sounds something like Vault
22:34 bakins joined #salt
22:35 debian112 joined #salt
22:36 a_v joined #salt
22:38 bowhunter joined #salt
22:39 austin_ joined #salt
22:40 austin_ i have a really dumb question but how do i copy dirs on the minion?
22:40 iggy cmd.run
22:40 austin_ really
22:41 iggy salt has functionality to copy from the master, but not so much from one place to another on the minion
22:41 a_v Hey salters! I'm just getting started with salt-cloud trying to use it against my vmware cluster.  When I provision a machine it goes through the motions but when it never seems to push or give the box an ip.  It starts the tools and just sits there and waits for an ip.  I have a feeling it's the customization portion of this but not sure. Anyone been through this?
22:41 austin_ iggy: right. that is what was hanging me up
22:42 austin_ so... i know its stupid but cmd.run seems like... not the _expected_ way
22:42 austin_ im not saying its right/wrong
22:42 austin_ its just strange especially coming from chef
22:42 iggy where I work, we made our own file state module that wraps the normal one for master->minion stuff and just does cmd.run for local stuff
22:42 austin_ yea.
22:43 austin_ are you hosting all of that on say an internal github ?
22:44 austin_ i still havent figured out a good way to structure my git repos for all of these things
22:44 vodik austin_: well you could write your own module
22:44 vodik i guess
22:44 austin_ vodik: yes i could. again just found it...odd
22:44 iggy the specifics don't really matter so much
22:45 iggy our file state module is in salt://_states/
22:45 dxiri joined #salt
22:45 austin_ are all of your states in a single repo ?
22:45 austin_ if using gitfs
22:45 iggy yes
22:45 iggy not using gitfs
22:45 austin_ o ok
22:45 iggy I steer clear of gitfs if I can
22:46 austin_ i'm kinda in the same boat with that right now
22:46 austin_ i haven't found a good way to handle it
22:46 Tanta I have branches in one git repo, ie staging testing production
22:46 sjorge joined #salt
22:46 austin_ i've been putting a ./pillar, ./states ./reactor setup in a single repo and just manually cloning
22:46 austin_ and symlinkings /srv/salt
22:46 Tanta I just mange it all with salt and pillar
22:46 vodik austin_: https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.cp.html#salt.modules.cp.get_url
22:46 amontalban joined #salt
22:47 vodik austin_: does file:// work actually?
22:47 iggy we have a system that creates a deb pkg from our git repo which basically just drops the entire repo in /srv
22:47 vodik i mean, i get that's documentation around salt-cp integration, but i wonder
22:47 vodik austin_: if they support it, i wonder if they'll take pr to make file module accept file:// uris
22:47 iggy it works for some things (and it's a bit different across versions)
22:47 austin_ vodik: i was looking at that. didnt try it just yet and also, i tried file:// with file.manage and it wasnt exactly working right fo rme
22:48 austin_ iggy: that seems like hte ideal setup. i like that a lot better
22:48 vodik well there goes my ideas
22:48 writtenoff joined #salt
22:48 austin_ it could be that i didnt do it right
22:48 austin_ alwasy possible
22:48 austin_ but i'll hack on that for a few mins
22:48 austin_ thanks for the ideas
22:49 austin_ if cmd.run gets me through what i need to do... its good enough :shrugs:
22:49 iggy I've been working on a HOWTO doc to do a similar setup in AWS using codecommit/codebuild
22:49 tercenya joined #salt
22:50 austin_ yea. i need to figure out the best way to host code... becuase in the end i'm offering "salt as a service" for my other internal teams
22:50 nidr0x joined #salt
22:50 austin_ i mange the infrastructure, they manage their code
22:51 austin_ i just need repeatable ways to get their code to my masters and syndics :D
22:51 promorphus joined #salt
22:51 austin_ something tells me i'll be using a lot of jenkins, artifactory and my own "pull" code. cp.get_url looks interesting for that
22:52 whytewolf there is a file.copy that is supposed to work for moving files locally on a system.
22:52 whytewolf https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.copy
22:53 whytewolf although i have heard of people having all sorts of problems with it working with directories. not sure if it has been fixed since then
22:53 austin_ yea i need to copy dirs and recursively
22:53 ronnix joined #salt
22:54 promorphus anyone know of a quick way to set a grain or pillar variable as a result of another state? i.e., when i cmd.run something, i want the output stored in a grain?
22:55 debian112 joined #salt
22:56 rakila joined #salt
22:57 overyander I'm working on writing a module. i'm needing to get a value from a grain item. can anybody tell me or link me to docs showing how to that? thanks
22:58 nZac joined #salt
22:58 austin_ grains.present ?
22:58 austin_ just use a require on that
22:58 austin_ or are you looking for output ?
22:58 overyander no, i'm needing the value returned
22:58 austin_ to set that grain
22:58 austin_ o yea. not sure sorry
22:58 whytewolf overyander: you just use grains.get from with in your module
22:58 whytewolf [unless it is a grain modules, then you just don't]
22:59 overyander lol
22:59 rpb joined #salt
22:59 overyander do i need to include anything to use that or is available when i include salt.utils?
22:59 overyander i'm a complete beginner at this and my python skills aren't that great either.
23:00 cainn if i am accessing grains, and i'm not getting what i expect, what's the process for debugging? (i.e. the output seems wrong) - what's the process for debugging? (seems like the nodes are missing grains or something, but /etc/salt/grains seems fine)
23:01 whytewolf nope as long as you are within a function you can call salt modules with just __salt__['module.function']
23:01 overyander whytewolf ok, thanks.
23:01 whytewolf cainn: salt 'minion' grains.get or grains.items
23:01 cainn grains.items
23:02 whytewolf no i am saying thats how you tell what grains the minions get. if it isn't showing up in grains.items then something is off in your grains file
23:02 cainn oh ha
23:03 whytewolf you can turn up your log file level and check your minion log
23:03 cainn got it, thanks
23:03 seanz joined #salt
23:04 cainn okay, if i am running a salt state with 'test=True' is there a way to make it print out the a file from file.managed after being jinja'd?
23:07 whytewolf no, but you CAN use cp.get_template to actually gernate a file. then look on the minion to where the file is rendered.
23:07 woodtablet left #salt
23:07 cainn aha, i'll do that
23:07 cainn thanks
23:07 whytewolf OR https://github.com/whytewolf/salt-debug
23:07 whytewolf which does the same thing but returns the results to you with out having to log into the minion
23:08 cainn awesome, thanks man
23:10 dxiri joined #salt
23:14 a_v Anyone pretty good with salt-cloud and vmware? Having a weird problem with it just waiting for an ip.
23:15 nZac joined #salt
23:18 hemebond What's the problem?
23:22 irated joined #salt
23:31 k4kvm @a_v Are you using the vmware tools from ISO?  Or one of the packaged variants
23:31 a_v I'm using open-vm-tools
23:31 debian112 joined #salt
23:33 a_v I tried on another template also using open-vm-tools and that one seemed to work fine.
23:36 k4kvm Oh, interesting.  are the templates the same os flavour?
23:39 a_v yup both centos7
23:41 k4kvm if you console to the cloned vm that's waiting for ip, does it have a nic/only one MAC addr assigned?
23:41 k4kvm that's what happened in my cases so far.  if not, might need to scour logs...
23:49 amontalban joined #salt
23:49 amontalban joined #salt
23:49 a_v Yup it looks like 1  nic and 1 mac
23:53 ronnix joined #salt
23:56 iggy cainn: salt-call -l debug will show the rendered sls file
23:56 cainn is salt-call == salt-run ?
23:56 cainn or is it a minion vs master hing
23:56 iggy no, it's something you run on the minion
23:56 cainn got it
23:56 cainn thanks
23:59 debian112 joined #salt
23:59 iggy state.show_highstate --out=yaml <-- also useful

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