Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-10-01

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

All times shown according to UTC.

Time Nick Message
00:02 brotatochip joined #salt
00:17 armonge joined #salt
00:18 xnavy joined #salt
00:38 jas02 joined #salt
00:42 pipps joined #salt
00:43 jdipierro joined #salt
00:57 jdipierro joined #salt
01:00 jdipierro joined #salt
01:03 edrocks joined #salt
01:20 XenophonF joined #salt
01:20 catpigger joined #salt
01:30 munhitsu_ joined #salt
01:34 jdipierro joined #salt
01:39 jas02 joined #salt
01:41 sebastian-w joined #salt
01:46 jdipierro joined #salt
01:46 amontalban joined #salt
01:46 amontalban joined #salt
01:46 hemebond joined #salt
01:48 ilbot3 joined #salt
01:48 Topic for #salt is now Welcome to #salt! | Latest Versions: 2015.8.12, 2016.3.3 | 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:49 promorphus joined #salt
01:54 Nahual joined #salt
02:09 takeda joined #salt
02:10 takeda Can't easily find answer to this in documentation. Is there a way that one minion can send a message to another minion?
02:16 hemebond takeda: Peer communication
02:16 hemebond https://docs.saltstack.com/en/develop/ref/peer.html
02:16 hemebond Have a long think about it though.
02:18 takeda how so?
02:19 hemebond Just think long about whether having your minions talk to each other directly (even through a proxy) is the best way; a lot of the time people seem to use it to work around something or because they want a specific workflow rather than adapt.
02:22 edrocks joined #salt
02:25 takeda We have CMDB that is independedn of salt and on separate host (it's running minion though), some of the data we make available to individual node through grains. We want to have a way for that host to notify other minion when something has changed.
02:25 takeda Does that sound reasonable to use it?
02:26 takeda the alternative seems to involve salt master, and it gets too complex
02:28 takeda the peer seems like is to allow commands, is there a way just to implant messages on event bus?
02:36 M-liberdiko joined #salt
02:40 jas02 joined #salt
02:41 takeda joined #salt
02:54 promorphus joined #salt
03:01 hoonetorg joined #salt
03:05 edrocks_ joined #salt
03:11 hemebond takeda: Oh you're still here.
03:12 hemebond takeda: Yes, minions can put events into the system.
03:24 mavhq joined #salt
03:28 takeda hemebond: how do they do that? the peer: example appears to list modules, or do you mean I should fire event module?
03:29 hemebond via a state: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.event.html
03:29 hemebond or something else: https://docs.saltstack.com/en/latest/topics/event/events.html
03:30 takeda hmm I'm confused now; how is the one you listed different from this? https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.event.html#module-salt.modules.event
03:31 hemebond So that's the execution module.
03:31 hemebond My first link is a state module.
03:31 hemebond Do you understand the difference between execution and state modules?
03:33 takeda actually no, well I know what state modules are (they are used in states; the sls files)
03:33 hemebond So an execution module is basically used for remote management.
03:33 hemebond For doing something on the minion right now.
03:33 takeda oh for salt-call command
03:33 takeda ?
03:33 hemebond salt-call is done on the minion.
03:34 hemebond Execution modules are used from the master to do things on the minion.
03:34 hemebond State modules are used for enforcing a state on the minion.
03:35 hemebond So if a highstate changed something you could use the event state module to send out an event for the master to react to.
03:35 takeda ok
03:35 hemebond The execution module could be used to immediately fire events from a set of minions.
03:36 takeda do you meant "to" instead of "from"
03:36 hemebond I mean from. Because you are telling the minions to fire out an event.
03:37 takeda ok
03:37 hemebond So master says "oi you lot, send out this event"
03:37 hemebond Then the master (via a reactor) reacts to those events and does something.
03:40 jas02 joined #salt
03:41 takeda hmm ... so how would I make even from specific minion arrive on another minion? I was thinking of configuring peer on salt master to allow event module to send an event to another minion, am I thinking about it correctly?
03:41 hemebond Well what is it you need to do?
03:42 hemebond Why does minionA need to talk to minionB?
03:43 dnull[m] joined #salt
03:43 M-MadsRC joined #salt
03:43 freelock[m] joined #salt
03:44 takeda ok minion A is very specific snowflake, it runs CMDB which has information about other machines etc. Part of that information is made available locally by injecting extra grains. We want allow Minion A to notify Minion B that information change and make Minion B fetch new data. Or maybe even provide that info in the event.
03:44 barmaley joined #salt
03:44 hemebond So CMDB is almost like a pillar?
03:45 takeda not really, the info is only specific for that single minion B, it contains info like which roles are used, rack etc
03:45 hemebond Sounds like pillar data to me.
03:46 hemebond But okay, so...
03:46 takeda well I suppose it could be like a pillar, but it has sensitive info
03:46 hemebond How does minion A know the data has been updated?
03:47 takeda the node only needs very small subset of it
03:47 hemebond That's what Pillars are for :-)
03:47 takeda yes, but that node existed way before we used salt
03:47 hemebond I'm talking more about CMDB :-)
03:47 takeda and has many information outside of salt
03:48 hemebond Did you know you can use anything as a Pillar source?
03:48 hemebond e.g., database
03:48 takeda well it's software to manage the infrastructure, provisioning machines etc it also has its database
03:48 hemebond Sounds good. But anyway, how does minion A know the data has been updated?
03:49 hemebond And can/does it run a script when the data has been updated?
03:49 takeda yes, it's has own api and tools to communicate with it
03:49 takeda it's the source of truth in our situation
03:50 takeda yes, currently is set up to send event to master that there was change
03:50 takeda but it would probably be simpler if it could notify the minion directly
03:50 hemebond Oh it's already notifying the master of the change?
03:51 takeda yes
03:51 hemebond And this only applies to a single minion?
03:51 takeda yes
03:51 hemebond easy peasy
03:51 hemebond https://docs.saltstack.com/en/latest/topics/reactor/index.html
03:52 hemebond Create a reactor to listen for the event and apply a state or whetever the minion uses to update the data.
03:52 hemebond e.g., state.apply to just run a highstate
03:53 takeda well that's how it's currently planned to be done, things are getting more complex because we have multiple masters, and the events will be duplicated etc
03:53 hemebond mmm
03:53 sagerdearia joined #salt
03:53 takeda it would be way simpler if that minion could just send event directly to the other minion
03:54 hemebond Well, you could already do that without Salt.
03:54 hemebond The reactor is very simple.
03:54 hemebond Not sure how you're using multiple masters.
03:55 takeda they're just there to handle load they are not independent of each other
03:55 takeda I meant they are independent
03:56 hemebond Then why would it result in duplicate events?
03:57 takeda hmm good question
03:57 hemebond Also, the state that applies should/will be idempotent
03:57 hemebond So even if it does run twice it shouldn't break anything.
03:58 takeda well if there would be duplicates it is still a bit ugly :)
03:58 hemebond That's true. I'm not familiar with multimaster setups so I don't know how they behave.
04:00 takeda when we send event it arrives to all masters
04:23 wangofett joined #salt
04:26 MajObviousman joined #salt
04:41 jas02 joined #salt
04:56 Ashald joined #salt
04:58 oida joined #salt
05:06 jaybocc2 joined #salt
05:07 edrocks_ joined #salt
05:42 jas02 joined #salt
05:44 systo joined #salt
05:45 DanyC joined #salt
05:55 jaybocc2 joined #salt
05:56 DanyC joined #salt
05:57 onlyanegg joined #salt
06:07 DanyC_ joined #salt
06:33 mpanetta joined #salt
06:43 jas02 joined #salt
06:50 keimlink joined #salt
07:09 edrocks_ joined #salt
07:15 DanyC joined #salt
07:25 mavhq joined #salt
07:34 DanyC joined #salt
07:41 haam3r joined #salt
07:43 jas02 joined #salt
07:51 Trauma joined #salt
07:53 mavhq joined #salt
08:06 jaybocc2 joined #salt
08:16 DarkKnightCZ joined #salt
08:22 jaybocc2 joined #salt
08:33 hemebond Before I dive into the code, anyone know of a way to register an instance with Salt-Cloud outside the normal process so it can be managed with Salt-Cloud?
08:42 bocaneri joined #salt
08:44 jas02 joined #salt
08:45 mavhq joined #salt
09:11 edrocks_ joined #salt
09:18 sgo_ joined #salt
09:22 bocaneri joined #salt
09:45 jas02 joined #salt
09:53 armyriad joined #salt
09:53 catpig joined #salt
09:58 pkoch joined #salt
10:10 ozux joined #salt
10:22 LostSoul joined #salt
10:23 lero joined #salt
10:33 jaybocc2 joined #salt
10:46 jas02 joined #salt
10:49 jaybocc2 joined #salt
11:02 lero joined #salt
11:04 v__ joined #salt
11:04 v__ ...
11:04 v__ https://www.youtube.com/watch?v=IBmC5RiIg9E
11:04 v__ I actually find this pretty interesting.
11:13 edrocks_ joined #salt
11:13 mrueg joined #salt
11:29 GreatSnoopy joined #salt
11:31 zulutango joined #salt
11:33 Edgan joined #salt
11:36 haam3r joined #salt
11:40 jaybocc2 joined #salt
11:40 jas02 joined #salt
11:41 amcorreia joined #salt
11:49 Trauma joined #salt
11:55 jaybocc2 joined #salt
12:10 _aeris_ joined #salt
12:16 cmek joined #salt
12:28 lilvim joined #salt
12:30 Deliant joined #salt
12:34 Patafke joined #salt
12:35 jdipierro joined #salt
12:58 glyf joined #salt
12:59 glyf just wanted to drop a quick note to say how awesome the new documentation layout is! thank you. https://docs.saltstack.com/en/latest/
13:11 mohae_ joined #salt
13:14 jdipierro joined #salt
13:14 edrocks_ joined #salt
13:15 lero joined #salt
13:18 jdipierro joined #salt
13:25 jdipierro joined #salt
13:30 jdipierro joined #salt
13:48 Lionel_Debroux joined #salt
13:52 aidin joined #salt
13:53 glyf_ joined #salt
14:06 catpig joined #salt
14:07 jaybocc2 joined #salt
14:16 XenophonF hemebond: you could always create a profile for a given instance, and then add the instance's name with that profile to the cloud map
14:17 XenophonF but that's really just used for instance deployment
14:18 XenophonF unless you're using salt-cloud to prune instances that it hasn't deployed, that doesn't really do anything (other than add documentation, which I'll admit is valuable in and of itself)
14:19 tiwula joined #salt
14:20 mattp_ is pepper up to date?
14:20 mattp_ was seeing some compatibility issues with the latest release
14:21 haam3r joined #salt
14:23 jaybocc2 joined #salt
14:30 sjorge joined #salt
14:37 scoates joined #salt
15:05 bluenemo joined #salt
15:06 scoates joined #salt
15:07 glyf joined #salt
15:17 edrocks joined #salt
15:18 sjorge joined #salt
15:21 jdipierro joined #salt
15:22 jdipierro joined #salt
15:24 jdipierr_ joined #salt
15:26 chamunks joined #salt
15:28 subsignal joined #salt
15:37 sjorge joined #salt
15:40 sgo_ joined #salt
15:46 sandro_ joined #salt
15:46 amcorreia https://docs.saltstack.com/en/latest/ref/states/all/salt.states.redismod.html  This kind of change is in running process or this will change redis.conf file?
15:48 jas02 joined #salt
16:08 sandro_ joined #salt
16:12 DarkKnightCZ joined #salt
16:14 takeda joined #salt
16:15 pcdummy joined #salt
16:43 om joined #salt
16:49 jas02 joined #salt
17:10 patrek joined #salt
17:19 edrocks joined #salt
17:19 sandro_ joined #salt
17:42 rubenb joined #salt
17:44 armonge joined #salt
17:50 jas02 joined #salt
17:53 RandyT joined #salt
18:13 mTeK joined #salt
18:20 nicksloan joined #salt
18:20 armyriad joined #salt
18:30 scoates joined #salt
18:32 jnials_ joined #salt
18:32 justanotheruser joined #salt
18:40 ozux joined #salt
18:48 scoates joined #salt
18:49 Rumbles joined #salt
18:51 jas02 joined #salt
18:51 krymzon joined #salt
19:01 ozux joined #salt
19:14 jdipierro joined #salt
19:21 edrocks joined #salt
19:22 Nahual joined #salt
19:27 jdipierro joined #salt
19:28 fxdgear joined #salt
19:30 jdipierr_ joined #salt
19:30 Bryson joined #salt
19:39 RandyT joined #salt
19:43 RandyT joined #salt
19:51 jas02 joined #salt
20:19 lilvim joined #salt
20:19 dober joined #salt
20:20 sgo_ joined #salt
20:22 jdipierro joined #salt
20:22 joe joined #salt
20:22 nixjdm joined #salt
20:26 ozux joined #salt
20:31 Vaelatern joined #salt
20:35 amontalban joined #salt
20:39 viq joined #salt
20:39 west575_ joined #salt
20:46 glyf joined #salt
20:49 catpig joined #salt
20:52 jas02 joined #salt
20:53 ZachLanich joined #salt
21:00 ozux joined #salt
21:15 CampusD joined #salt
21:17 CampusD question, is this format correct for an scheduled job? - function: state.apply  users.admins
21:18 CampusD I am getting an invalid function
21:19 CampusD I noticed that there is some job_args and job_kwargs options in https://docs.saltstack.com/en/latest/ref/states/all/salt.states.schedule.html
21:19 CampusD should I split the function and the arguments perhaps?
21:20 CampusD - function: state.apply , - job_args:       - users.admins
21:20 CampusD any help appreciated
21:23 edrocks joined #salt
21:34 hemebond XenophonF: Unfortunately Salt-Cloud uses a cache file on the master to track the instances it has created. If your instance isn't in there it won't be able to manage it.
21:46 CampusD can schedule files be in the base states structure? or do they need to be in pillar or somewhere else?
21:46 Satyajit joined #salt
21:47 hemebond CampusD: I haven't used that module before but it should just go into your states directory.
21:48 hemebond er
21:48 hemebond In a regular state file.
21:50 CampusD i've setup a schedules.sls which includes other files like this https://gist.github.com/anonymous/c8045fc20807f43b38059e48182d124f
21:50 CampusD didn't know if it would valid
21:50 hemebond Yeah, just including other files should be fine.
21:50 hemebond They're just regular state files.
21:53 jas02 joined #salt
21:53 CampusD thanks
21:59 systo joined #salt
22:01 ZachLanich joined #salt
22:04 stooj joined #salt
22:05 DarkKnightCZ joined #salt
22:24 nicksloan joined #salt
22:47 glyf joined #salt
22:52 voxpop_ joined #salt
22:54 jas02 joined #salt
22:54 amontalban joined #salt
23:00 Bryson joined #salt
23:05 west575 joined #salt
23:05 nethershaw joined #salt
23:23 rpb joined #salt
23:25 edrocks joined #salt
23:30 amontalban joined #salt
23:30 amontalban joined #salt
23:34 jdipierro joined #salt
23:54 jas02 joined #salt

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