Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-06-17

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

All times shown according to UTC.

Time Nick Message
00:43 Brew joined #salt
00:49 zulutango joined #salt
00:51 mikea joined #salt
01:26 onlyanegg joined #salt
01:29 Valfor joined #salt
01:29 Valfor joined #salt
01:48 ilbot3 joined #salt
01:48 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.3.6, 2016.11.5 <+> Support: https://www.saltstack.com/support/ <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ <+> See also: #salt-devel, #salt-offtopic <+> We are volunteers and may not have immediate answers <+> The call for speakers for SaltConf17 is now open: http://tinyurl.com/SaltConf17
02:03 rem5 joined #salt
02:04 edrocks joined #salt
02:12 Awesomecase joined #salt
02:29 cliluw joined #salt
02:45 Roh joined #salt
03:06 ivanjaros joined #salt
03:31 donmichelangelo joined #salt
04:05 irated joined #salt
04:05 irated joined #salt
04:10 rideh joined #salt
04:13 irated joined #salt
04:32 evle1 joined #salt
04:43 kuromagi joined #salt
04:52 fracklen joined #salt
04:58 asyncsec joined #salt
05:07 edrocks joined #salt
05:11 mosen joined #salt
05:13 ivanjaros joined #salt
05:18 nocaberi joined #salt
05:21 onlyanegg joined #salt
05:21 nocaberi joined #salt
06:29 Inveracity joined #salt
06:39 mpanetta joined #salt
06:47 preludedrew joined #salt
07:04 bantone joined #salt
07:10 fritz09 joined #salt
07:28 XenophonF joined #salt
07:42 Trauma joined #salt
07:54 hemebond joined #salt
08:03 major joined #salt
08:09 edrocks joined #salt
08:18 oida_ joined #salt
08:26 samodid joined #salt
08:36 major joined #salt
08:38 darioleidi joined #salt
08:41 mt5225 joined #salt
08:46 pbandark joined #salt
09:09 major joined #salt
09:13 evle1 joined #salt
09:19 Praematura joined #salt
09:21 darioleidi joined #salt
09:30 absolutejam Hey guys, what's the state of requisites and failures in orchestration?
09:32 hemebond absolutejam: I thought they worked the same as in regular states. But I haven't done much orchestration. Are you hitting a problem?
09:33 cyborg-one joined #salt
09:44 mt5225 joined #salt
09:52 absolutejam Oh i haven't started yet!
09:53 absolutejam I'm getting well into salt and orchestrate is one of the parts I haven't touched yet
09:54 absolutejam Want to be able to replicate some of my Ansible play books in Salt as I like being able to have a complete product and tell
09:54 absolutejam Somebody else to just fire it off
10:12 edrocks joined #salt
10:26 Neighbour absolutejam: requisites work for any state declaration, whether they're orchestration states or minion states
10:31 keltim joined #salt
10:40 mt5225 joined #salt
10:52 viq You probably already have seen https://docs.saltstack.com/en/latest/topics/orchestrate/orchestrate_runner.html
10:58 tellendil joined #salt
11:00 Kelsar joined #salt
11:12 darioleidi joined #salt
11:23 Trauma joined #salt
11:40 absolutejam Sweet, thanks Neighbour hemebond
11:41 mt5225 joined #salt
11:41 absolutejam So, does a failure continue the state like in a regular state run?
11:43 absolutejam Also, is there any way to apply 'failhard:' on an entire state file?
11:43 absolutejam Or is it only per state/globally?
11:43 evle joined #salt
11:47 coredumb absolutejam: I think failhard is global so it will stop completely when an error is found
11:48 hemebond left #salt
11:48 cyteen joined #salt
11:49 absolutejam That might do to be honest, because i can't really see much point in applying to per state
11:49 coredumb and indeed without failhard, any failure continues like nothing happened :)
11:53 svolentin joined #salt
12:13 edrocks joined #salt
12:25 pbandark joined #salt
12:29 Neighbour You can specify failhard globally (in the config file) or per state
12:29 Neighbour And since you can call state files in orchestration (salt.state accepts an sls-parameter), you can (if not already globally) fail on a state file
12:36 ThomasJ joined #salt
12:38 Whissi joined #salt
12:42 Trauma joined #salt
12:51 mt5225 joined #salt
13:05 mpanetta joined #salt
13:21 johnkeates joined #salt
13:22 johnkeates i'm integrating a little bit of auto configuration and discovery into one of my formulas, but i'm not sure about the implementation details; i'm re-engineering prometheus and the exporters so that activating a node exporter auto-registers it on prometheus servers
13:23 johnkeates at first I thought about using a beacon to spit out events as soon as the node_exporter is running and have a reactor write the node's host to a file and have prometheus pick it up
13:23 johnkeates but that doesn't clean up after itself and doesn't allow for further configuration
13:24 johnkeates so next, i thought about making a mine function that gets configuration data on hosts and then have a periodic job update prometheus with it, but that might be a bit resource hungry
13:32 xet7 joined #salt
13:33 Praematura joined #salt
13:35 fracklen joined #salt
13:38 ThomasJ joined #salt
13:46 buhm joined #salt
13:53 darioleidi joined #salt
14:04 mt5225 joined #salt
14:08 pbandark1 joined #salt
14:29 aarontc joined #salt
14:30 heyimawesome joined #salt
14:52 johnkeates left #salt
14:53 Praematura joined #salt
14:58 ivanjaros joined #salt
15:04 mpanetta joined #salt
15:08 JPT joined #salt
15:15 mt5225 joined #salt
15:17 codeiter joined #salt
15:21 codeiter left #salt
15:21 JPT_ joined #salt
15:24 JPT_ left #salt
15:26 JPT joined #salt
15:35 morissette joined #salt
15:35 CheckYourSix joined #salt
15:36 iggy joined #salt
15:37 MTecknology joined #salt
15:37 gadams joined #salt
15:37 asoc joined #salt
15:37 Zachary_DuBois joined #salt
15:38 JPaul joined #salt
15:38 TooLmaN joined #salt
15:38 gtmanfred joined #salt
15:39 gmacon joined #salt
15:40 rome_390 joined #salt
15:42 Ch3LL joined #salt
15:45 robawt joined #salt
15:56 cgiroua joined #salt
16:05 cgiroua joined #salt
16:06 onlyanegg joined #salt
16:12 bdf joined #salt
16:14 nebuchadnezzar joined #salt
16:14 onlyanegg joined #salt
16:17 edrocks joined #salt
16:23 rihannon joined #salt
16:27 mt5225 joined #salt
16:31 extiberius joined #salt
16:32 extiberius left #salt
16:40 robawt joined #salt
16:47 evle joined #salt
16:48 rihannon joined #salt
16:57 ahrs joined #salt
17:15 onlyanegg joined #salt
17:22 buhm joined #salt
17:26 cyborg-one joined #salt
17:37 mt5225 joined #salt
17:59 gmoro joined #salt
18:01 amcorreia joined #salt
18:03 nledez joined #salt
18:03 Edur joined #salt
18:03 lstor joined #salt
18:03 ksa_ joined #salt
18:03 rofl____ joined #salt
18:08 gaborn joined #salt
18:13 relidy joined #salt
18:16 onlyanegg joined #salt
18:18 xet7 joined #salt
18:47 mt5225 joined #salt
18:52 evidence joined #salt
18:52 packeteer joined #salt
18:52 evilrob_ joined #salt
18:52 mihait joined #salt
18:52 czchen joined #salt
18:52 chutzpah joined #salt
18:52 mauli joined #salt
18:52 ople joined #salt
18:52 copelco joined #salt
18:52 simonmcc joined #salt
18:52 hacks_ joined #salt
18:52 J0hnSteel joined #salt
18:52 doriftoshoes_ joined #salt
18:52 carmony joined #salt
18:52 WKNiGHT joined #salt
18:52 tcolvin joined #salt
18:52 attente joined #salt
18:52 Bock joined #salt
18:54 nledez joined #salt
18:54 sjorge joined #salt
18:54 keldwud joined #salt
18:54 keldwud joined #salt
18:55 fracklen joined #salt
19:01 _KaszpiR_ joined #salt
19:01 Praematura joined #salt
19:03 tom29739 joined #salt
19:03 Inveracity joined #salt
19:19 edrocks joined #salt
19:27 bowhunter joined #salt
19:36 Sammichmaker joined #salt
19:36 Sammichmaker joined #salt
19:37 asyncsec joined #salt
19:37 Praematura joined #salt
19:43 absolutejam So, if I wanted to trigger a state on a remote host if a local file is changed
19:44 coredumb beacon + reactor
19:44 absolutejam Yeah, that's fine
19:44 absolutejam Beacon on master
19:44 absolutejam reactor fires off state on remote minion(s)
19:45 absolutejam But, is there a way I can achieve this with the logic 'if file is changed, wait 5 minutes to ensure there's no more changes'
19:45 absolutejam I guess I could use git(fs) and it'd be on commit, so it'd be more CI-like
19:47 absolutejam My other thought was to try and use the salt queue and make the beacon add to the queue
19:47 absolutejam and then have a schedule check it every 5 minutes, and uhm
19:47 absolutejam Hm.
19:48 bowhunter joined #salt
19:49 coredumb ok so
19:50 coredumb firing events from git hooks is perfectly fine
19:50 coredumb your need for wait could be easily implemented in your own beacon I guess
19:53 GnuLxUsr joined #salt
19:57 mt5225 joined #salt
20:03 absolutejam On another note - custom outputters
20:03 absolutejam can I do what is done with other modules and make /srv/salt/_output ?
20:04 absolutejam There's no obvious docs about custom output modules compared to custom grains, execution modules, etc.
20:07 coredumb no idea
20:07 coredumb :)
20:17 onlyanegg joined #salt
20:26 cgiroua joined #salt
20:35 rawzone joined #salt
20:40 absolutejam Ah, looks like the https://docs.saltstack.com/en/latest/ref/modules/ docs refer to execution, returner, beacon etc modules
20:49 donmichelangelo joined #salt
21:08 mt5225 joined #salt
21:40 lorengordon absolutejam: yes, https://docs.saltstack.com/en/latest/ref/file_server/dynamic-modules.html
21:50 ivanjaros joined #salt
22:01 swills joined #salt
22:09 swills joined #salt
22:10 swills joined #salt
22:10 swills joined #salt
22:10 swills joined #salt
22:18 onlyanegg joined #salt
22:19 mt5225 joined #salt
22:26 justanotheruser joined #salt
22:28 justanotheruser joined #salt
22:33 onlyanegg joined #salt
22:35 absolutejam lorengordon: beautiful!
22:35 absolutejam Thank you
22:46 absolutejam is there any way to sync python dependencies too?
22:46 absolutejam not really sure how it works for Windows as there's an embedded python
22:47 absolutejam unless I just run it as a state using that python
22:54 asyncsec joined #salt
23:23 edrocks joined #salt
23:27 mt5225 joined #salt
23:49 XenophonF joined #salt

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