Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-12-06

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

All times shown according to UTC.

Time Nick Message
00:00 hcl2 salt master: https://www.zerobin.net/?2ccdfbc7c1aaff6b#ktCAVj5/tB3pzjZh8XVBJHVjv73o+bL/hz3vq+9Q250=
00:00 hcl2 i should be able to just do state.sls users after that, assuming the pillar is setup right, right?
00:01 hcl2 if i just git clone it, and add the file path to the file roots it works perfectly
00:05 shaggy_surfer joined #salt
00:13 smcquay joined #salt
00:23 badon joined #salt
00:25 glyf joined #salt
00:28 Leonw joined #salt
00:29 Leonw Hi
00:30 Leonw I'm having a situation where a salt '*' test.ping doesn't return nothing but a salt-call state.highstate on the minion works
00:30 Leonw the master and the minion are running on docker
00:30 Leonw and the minion is also a syndic/master/minion
00:34 snave left #salt
00:34 Leonw Is there any chance that it's blocking on the network?
00:35 Leonw I'm mapping the 4505 and 4506 ports to another ports when starting the docker
00:35 Leonw but I'm also setting this up on the minion config and on the master it self
00:40 lempa joined #salt
00:42 cads joined #salt
00:43 wt I don't know if salt would know how to get back to a minion in a non-routable docker container.
00:45 Leonw wt: yes yes... this is what I was thinking...
00:45 Leonw wt: does any one have any documentation about how is the network architecture between maste/minions?
00:46 Leonw wt: I have it working from non-docker hosts against a dockered master
00:46 Leonw wt: It's failing against a dockerized minion agains a dockerized master
00:49 UtahDave Leonw: It's a zeromq pub/sub scenario.  The minions listen on a pub port on the master and execute commands that the match and then return the output of the commands to the master's receive port
00:51 collinanderson joined #salt
00:53 otter768 joined #salt
00:54 Leonw UtahDave: and from where the minions fetch the port number of the master's receive port?
00:55 Leonw UtahDave: does the master tell this to the minions or it's configured on the minions configs?
00:55 UtahDave Leonw: everything defaults to ports 4505 and 4506. So you don't have to do anything with the ports. Just make sure the minions can reach the master
00:56 UtahDave if you want to change the ports, then you have to set that in the master and minion configs
00:56 Leonw UtahDave: this is the Issue man... I *must* to change the defaut ports
00:56 Leonw but... not on the salt it self
00:56 Leonw but on the port mapping from inside the docker to the outside world
00:57 Leonw so... in this cenario... master-1 port 4505 will map to port 10000
00:57 Leonw master-2 port 4505 to port 10010
00:57 Leonw etc
00:57 UtahDave can you map it to port 4505 on the outside instead?
00:57 Leonw I'm running a multi-master, single server setup using docker :P
00:57 Leonw which one?
00:57 Leonw the master-1
00:57 UtahDave oh, ok.
00:57 Leonw :)
00:58 UtahDave Then the minions will need to be configured to point to the correct port
00:58 Leonw UtahDave: do you know which parameter?
00:58 Leonw i'm using the master_port: 10022
00:58 Leonw (what will map in the end to 4506)
00:59 UtahDave yeah, that should be correct.
00:59 Leonw on the host server... it doesn't ping
00:59 Leonw on the master server*
00:59 collinanderson left #salt
00:59 Leonw but a salt-call inside the dockered minion works... :S
00:59 UtahDave can the minion telnet to 10022?
01:00 Leonw yes
01:00 UtahDave Hm. I'm not seeing an option for the other port though.  Let me code dive for a sec
01:04 UtahDave Leonw: try having your master's publish_port match the external port
01:05 Leonw this is a problem also... because then I can't reuse the docker image
01:05 Leonw I would need to build diferent images EXPOSING this especific port
01:05 UtahDave gotcha.
01:05 Leonw but... if you tell me that this is a limitation... I can try to think on a workaround
01:05 Leonw :)
01:06 UtahDave I thought we used to configure both the pub and ret port on the minion also, but I'm only seeing 4506, not 4505.
01:06 UtahDave Let me ask here internally. Everyone's gone for the day, so it might not be until tomorrow.
01:07 UtahDave can you send me an email for me to respond to with the answer?
01:17 pdayton joined #salt
01:23 Leonw UtahDave: sure :)
01:27 bhosmer joined #salt
01:33 pdayton joined #salt
01:36 shaggy_surfer Hi.  I am noticing that even when running salt with the -v -t  30, that the minion returns "Minion did not return. [No response]"  even though the job and state are executed on the remote minion, as I can see it in the tailing of the log.  I also notice sometimes that when you first run salt to a node when it hasn't run in a while , i.e. a day… that the output and results don't spit back to the master console.  Anyone else experiencing similar behavior
01:37 shaggy_surfer I am running the latest matching versions of master and minion, helium
01:38 shaggy_surfer but I have seen this in previous versions too, basically since I started using it…. issue is now I am executing salt orchestration from jenkins and it doesn't always spit back the output to the console, which is needed for verification of deploy
01:39 Ryan_Lane joined #salt
01:41 nitti joined #salt
01:51 Outlander joined #salt
01:56 glyf joined #salt
02:02 yomilk joined #salt
02:10 pr_wilson joined #salt
02:11 shaggy_surfer FYI, just for anyone else, I tried this solution and will check back and see if it works:
02:11 shaggy_surfer https://github.com/saltstack/salt/issues/16518
02:11 shaggy_surfer enable the ping and restart the master
02:11 shaggy_surfer check back after 24 hours
02:18 Mso150 joined #salt
02:22 pr_wilson joined #salt
02:28 Ryan_Lane joined #salt
02:28 pr_wilson joined #salt
02:29 yomilk joined #salt
02:34 pr_wilson joined #salt
02:52 jimklo_ joined #salt
02:54 smcquay joined #salt
02:54 tmh1999 joined #salt
02:54 otter768 joined #salt
03:03 jasonrm joined #salt
03:06 luminous joined #salt
03:07 Mso150 joined #salt
03:08 monkey66 joined #salt
03:08 torment joined #salt
03:21 pacopablo joined #salt
03:23 Mso150 joined #salt
03:24 ckao joined #salt
03:31 CeBe1 joined #salt
03:51 otter768 joined #salt
04:02 catpig joined #salt
04:04 jeffrubic joined #salt
04:16 Mso150_e joined #salt
04:17 viq joined #salt
04:23 dude051 joined #salt
04:29 thedodd joined #salt
04:30 glyf joined #salt
04:32 brendanashworth joined #salt
04:34 schristensen joined #salt
04:45 claytron joined #salt
05:04 fishdust joined #salt
05:19 pdayton joined #salt
05:30 capricorn_1 joined #salt
05:37 Eugene joined #salt
05:43 pdayton joined #salt
05:45 nethershaw joined #salt
05:58 jalbretsen joined #salt
06:17 otter768 joined #salt
06:41 jeddi joined #salt
06:42 ndrei joined #salt
06:58 catpigger joined #salt
07:13 ajolo_ joined #salt
07:18 SGTItlog joined #salt
07:30 Luijk joined #salt
07:35 aqua^mac joined #salt
07:41 Luijk left #salt
07:56 TheThing joined #salt
08:01 yomilk joined #salt
08:01 jnials joined #salt
08:26 monkey66 joined #salt
08:29 otter768 joined #salt
08:36 Diaoul hi
08:36 Diaoul what's the best practice to store default values for pillars? using the default of dict.get just results in a lot of code duplication
08:46 babilen Diaoul: Take a look at the mysql formula for example
08:48 st_iron joined #salt
08:48 st_iron hello
08:49 babilen welcome
09:08 monkey66 joined #salt
09:23 viq joined #salt
09:51 JlRd joined #salt
10:05 rubenb joined #salt
10:24 viq joined #salt
10:30 otter768 joined #salt
10:35 alreece45 left #salt
10:40 bfoxwell_ joined #salt
10:44 erjohnso joined #salt
10:49 TyrfingMjolnir joined #salt
10:58 davet joined #salt
11:01 bhosmer joined #salt
11:06 agend joined #salt
11:28 jalaziz joined #salt
11:32 JPaul joined #salt
11:33 Hazelesque joined #salt
11:45 bhosmer joined #salt
11:57 ndrei joined #salt
11:58 joehh1 whiteinge: is the important part of packaging salt-api to package the salt-api script and systemd/upstart/sysvinit scripts to start it as appropriate?
12:07 herzi joined #salt
12:08 CeBe joined #salt
12:23 LittUp joined #salt
12:25 glyf joined #salt
12:30 otter768 joined #salt
12:33 JlRd joined #salt
12:34 linjan joined #salt
12:38 agend joined #salt
12:43 JayFK joined #salt
12:46 JayFK I have some machines missing the osfinger grain, why?
12:57 luminous joined #salt
13:03 glyf joined #salt
13:06 aquinas joined #salt
13:07 CeBe1 joined #salt
13:13 linjan joined #salt
13:19 jonatas_oliveira joined #salt
13:40 jonatas_oliveira joined #salt
13:44 jonatas_oliveira joined #salt
13:53 yomilk joined #salt
13:56 davet joined #salt
14:04 hcl2 joined #salt
14:09 davet joined #salt
14:10 Whissi Is is normal to have so many "KeyError: 'kernel'" in /tmp/salt-runtests.log after running the test suite? -> https://bpaste.net/show/a8497f9036af
14:23 favadi joined #salt
14:27 CeBe joined #salt
14:31 clinta joined #salt
14:31 otter768 joined #salt
14:40 rjc joined #salt
14:46 cads joined #salt
14:51 CeBe1 joined #salt
14:54 davet joined #salt
15:00 mapu joined #salt
15:01 davet joined #salt
15:15 cads joined #salt
15:19 Rockj joined #salt
15:23 whiteinge joehh1: yes, that's it.
15:23 whiteinge joehh1: You can even just put those in the salt-master package since it must be run on that same machine and because it doesn't start or do anything without the user adding stuff to the master config
15:33 SpX joined #salt
15:41 clinta Is anyone here successfully using proxyminions?
15:49 patrek joined #salt
16:08 CeBe1 joined #salt
16:32 otter768 joined #salt
16:35 linjan joined #salt
16:37 aqua^mac joined #salt
16:37 glyf joined #salt
16:45 LittUp joined #salt
16:56 jrluis joined #salt
16:56 st_iron joined #salt
16:57 pr_wilson joined #salt
17:02 nyx_ joined #salt
17:08 __gotcha joined #salt
17:12 pdayton joined #salt
17:16 zlhgo joined #salt
17:27 LittUp joined #salt
17:32 xliiv joined #salt
17:47 bhosmer_ joined #salt
17:55 _JZ_ joined #salt
17:56 karimb joined #salt
18:06 patrek joined #salt
18:13 douardda joined #salt
18:26 aqua^mac joined #salt
18:27 yomilk joined #salt
18:33 otter768 joined #salt
18:36 Mso150 joined #salt
18:38 ckao joined #salt
18:44 StDiluted joined #salt
18:45 dude051 joined #salt
18:58 intellix joined #salt
18:59 bhosmer_ joined #salt
18:59 jeffrubic1 joined #salt
19:01 faust joined #salt
19:04 superted666__ joined #salt
19:04 faust joined #salt
19:11 glyf joined #salt
19:40 balltongu joined #salt
19:54 glyf joined #salt
20:00 jalaziz_ joined #salt
20:01 otter768 joined #salt
20:14 aqua^mac joined #salt
20:33 jalaziz joined #salt
20:49 CeBe1 joined #salt
20:51 CeBe1 joined #salt
20:59 byronschaller joined #salt
21:07 Mso150 joined #salt
21:08 agend joined #salt
21:10 dude051 joined #salt
21:14 Renat joined #salt
21:29 jnials joined #salt
21:33 ckao joined #salt
21:40 borgstrom joined #salt
21:42 CeBe1 joined #salt
21:47 jnials joined #salt
21:52 bhosmer joined #salt
22:03 aqua^mac joined #salt
22:07 mapu_ joined #salt
22:11 jalaziz joined #salt
22:13 jnials joined #salt
22:18 decrypted hey if anyone is around does anyone know of compat issues on Salt: 2014.7.0 and Salt: 2014.1.13?
22:24 vectra joined #salt
22:24 jnials joined #salt
22:29 aparsons joined #salt
22:32 karimb joined #salt
22:34 aparsons joined #salt
22:38 Diaoul hi
22:40 Diaoul is it possible to use a pillar variable defined above in a pillar file? like to avoid redundancy "app_name: test" [...] later [...] "app_path: /var/www/{{ app_name }}"
22:44 CeBe joined #salt
22:45 nkuttler Diaoul: fwiw, you can set variable in jinja. use the var everywhere, in the pillar as well?
22:48 Hell_Fire joined #salt
22:52 glyf joined #salt
23:06 jnials joined #salt
23:09 Metin joined #salt
23:09 Metin Hi
23:10 Metin I have a noob question about contributing to salt-cloud dev
23:11 Metin I am trying to debug a specific case with ec2, but every code changes that I on salt/cloud files seems to be ignored
23:12 Metin Is there anything specific to salt-cloud that is not written in HACKING.rst ?
23:18 jnials joined #salt
23:52 aqua^mac joined #salt
23:53 Incognito78 joined #salt
23:54 otter768 joined #salt

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