Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-10-30

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

All times shown according to UTC.

Time Nick Message
00:01 justan0theruser joined #salt
00:02 jas02 joined #salt
00:22 edrocks_ joined #salt
00:36 hemebond joined #salt
00:42 mikecmpbll joined #salt
00:46 onlyanegg joined #salt
00:47 jas02 joined #salt
01:11 akhter joined #salt
01:25 zulutango joined #salt
01:28 spuder joined #salt
01:39 spuder joined #salt
01:42 sebastian-w joined #salt
01:45 mavhq joined #salt
01:46 fracklen joined #salt
02:08 promorphus joined #salt
02:24 amontalban joined #salt
02:24 edrocks_ joined #salt
02:40 fracklen joined #salt
02:41 sebastian-w joined #salt
02:41 justanotheruser joined #salt
02:44 catpigger joined #salt
02:58 m4rx joined #salt
03:01 subsignal joined #salt
03:02 subsignal joined #salt
03:03 jas02 joined #salt
03:11 subsignal joined #salt
03:20 prg3 joined #salt
03:21 wangofett joined #salt
03:34 fracklen joined #salt
03:36 DEger joined #salt
03:37 hemebond joined #salt
03:38 DEger_ joined #salt
03:40 DEger joined #salt
03:41 DEger joined #salt
03:56 karlthane joined #salt
04:01 sjmh joined #salt
04:17 mikea- joined #salt
04:26 justan0theruser joined #salt
04:26 amontalban joined #salt
04:26 amontalban joined #salt
04:28 fracklen joined #salt
04:32 mikea Is there any way to get the output of a orchestration state item for use in the next step in the orchestration?
04:32 mikea i.e. I want to parse the list of installed packages and figure out if I need to reboot or not
04:34 hemebond mikea: Isn't there an option on the pkg module to reboot when required?
04:34 mikea that would be useful
04:35 mikea the word reboot is not listed at all in the yumpkg module
04:36 lompik joined #salt
04:36 jeddi joined #salt
04:37 mikea there's a list of redhat packages that redhat says require a reboot, I would just like to check if those were installed and reboot if they were
04:38 hemebond It doesn't look like there is a way to, at least via pkg, tell if the system needs to be rebooted.
04:39 hemebond Does YUM tell you a reboot is required somehow?
04:39 mikea no, but pkg.upgrade does tell you what packages were installed
04:39 mikea if the package is in this list: https://access.redhat.com/solutions/27943 you should reboot
04:39 hemebond Oh, well if you know what packages need a reboot then you can just reboot when they change.
04:40 mikea got an example?
04:42 hemebond https://docs.saltstack.com/en/latest/ref/states/requisites.html#onchanges
04:45 hemebond Schedule a reboot https://docs.saltstack.com/en/latest/faq.html#linux-unix
04:45 hemebond Make that reboot state run last https://docs.saltstack.com/en/latest/ref/states/ordering.html#the-order-option
04:47 mikea so would I do onchanges:
04:47 hemebond I believe so.
04:47 mikea then a list of - pkg: kernel, - pkg: firmware, etc
04:48 mikea or would i have to watch the files in those packages?
04:48 hemebond You would watch the states that install those packages.
04:48 mikea so the way it works now is that I'm running pkg.upgrade
04:49 mikea doing a few walls
04:49 mikea then rebooting
04:49 mikea I would just like to make the reboot optional
04:50 mikea so you're saying I should write individual states for the reboot-requiring packages, then pkg.upgrade after that, then reboot at the end if required?
04:50 hemebond The reboot would only be triggered if your package install states change.
04:50 hemebond i.e., they upgrade or install a package.
04:51 hemebond There is no pkg.upgrade state function.
04:52 mikea but if I'm just calling pkg.upgrade or pkg.uptodate there are no states for those packages
04:52 jas02 joined #salt
04:52 hemebond Oh.
04:53 hemebond Then why don't you just reboot it?
04:53 mikea I don't want to reboot unless I have to, and I only have to when certain packages are installed
04:53 hemebond Write a state that does that and apply it.
04:54 mikea the problem with that is I don't want to install them unless they are present
04:54 mikea pkg.upgrade does that
04:54 mikea if I put a state with pkg.latest, it'll install it if its missing
04:54 mikea i.e. kernel and kernel-PAE
04:55 hemebond I see.
04:57 hemebond So maybe if you change the highstate output to JSON and then parse it and check it.
04:57 hemebond There's nothing in-built to do that for you as far as I know. It seems a very specific requirement.
04:58 DrunkSignal joined #salt
04:58 DrunkSignal joined #salt
05:11 iggy mikea: https://docs.saltstack.com/en/latest/ref/beacons/all/salt.beacons.pkg.html#module-salt.beacons.pkg maybe?
05:12 mikea hmm
05:12 mikea so like that beacon could set a grain or pillar to needs_reboot=True
05:13 mikea and then in my orchestration I could G@needs_reboot:True
05:13 mikea and reset the grain/pillar to False
05:14 mikea @iggy I'm also submitting a github issue so that yumpkg can do something to prompt or inform you of a required reboot
05:14 iggy something like that
05:18 DEger joined #salt
05:22 fracklen joined #salt
05:25 hemebond I found an issue earlier about adding a reboot notification in the pkg module return data.
05:25 hemebond It was still open.
05:26 edrocks joined #salt
05:34 akhter joined #salt
05:46 Klas joined #salt
05:48 Klas joined #salt
05:51 alexanderilyin joined #salt
06:03 cosming joined #salt
06:13 stanchan joined #salt
06:17 fracklen joined #salt
06:19 Ni3mm4nd joined #salt
06:28 amontalban joined #salt
06:30 samodid joined #salt
06:49 cosming joined #salt
06:54 jas02 joined #salt
06:56 jeddi joined #salt
07:04 akhter joined #salt
07:04 jas02 joined #salt
07:09 vodik joined #salt
07:11 fracklen joined #salt
07:14 cosming joined #salt
07:18 cosming joined #salt
07:23 jeddi joined #salt
07:28 edrocks joined #salt
07:31 jeddi joined #salt
07:42 jas02 joined #salt
07:47 zer0def joined #salt
07:50 komputes joined #salt
07:51 jas02_ joined #salt
07:55 jas02 joined #salt
08:05 fracklen joined #salt
08:07 CEH joined #salt
08:17 mohae joined #salt
08:18 Trauma joined #salt
08:25 IdoKaplan joined #salt
08:25 IdoKaplan Hi, Is it possible to target grains and not server name when using SaltAPI?
08:26 DrunkSignal joined #salt
08:26 akhter joined #salt
08:30 amontalban joined #salt
08:36 ivanjaros joined #salt
08:59 fracklen joined #salt
09:02 hemebond IdoKaplan: Have you tried the regular targeting syntax?
09:05 nidr0x joined #salt
09:07 IdoKaplan hemebond: curl -sSk https://rg-cm01:8000 -H 'Accept: application/x-yaml' -H 'X-Auth-Token: d9ff421d9793321c75192303105299bdb3a70b0b' -d client=local -d tgt='env:test' -d fun=test.ping
09:08 hemebond IdoKaplan: http://stackoverflow.com/questions/28064098/salt-api-use-other-matching-method-other-then-glob
09:08 IdoKaplan hemebond: env is the grain. how can I say that the "env:test" is grain?
09:10 IdoKaplan hemebond: curl -sSk https://XXXX:8000 -H 'Accept: application/x-yaml' -H 'X-Auth-Token: d9ff421d9793321c75192303105299bdb3a70b0b' -d client=local -d tgt='env:analytics-dev' expr_form='grain' -d fun=test.ping
09:11 IdoKaplan hemebond: Is this the command? I get an error - curl: (6) Couldn't resolve host 'expr_form=grain'
09:11 bocaneri joined #salt
09:11 hemebond You need -d
09:13 IdoKaplan hemebond: Thanks!! is it's possbile to use compound in tgt?
09:13 hemebond Yes https://docs.saltstack.com/en/develop/ref/clients/index.html#salt.client.LocalClient.cmd
09:14 hemebond I believe that's what salt-api ends up calling, that function/method.
09:15 nidr0x joined #salt
09:16 IdoKaplan hemebond: tgt should be "env:analytics-dev and env2:ido"?
09:16 hemebond Not sure.
09:17 hemebond Whatever works from the master.
09:17 IdoKaplan hemebond: Thank you very much!! I will check it.
09:19 DEger joined #salt
09:30 promorphus joined #salt
09:40 fracklen joined #salt
09:46 xet7 joined #salt
09:49 ivanjaros3916 joined #salt
09:50 fracklen joined #salt
09:57 jas02 joined #salt
09:59 DrunkSignal joined #salt
10:12 Trauma joined #salt
10:15 cryptolukas joined #salt
10:17 cryptolukas How Can I substitute the ipv4 address with the grain from the clienthost? bind_socket = inet:3456@10.100.123.1;
10:19 lionel joined #salt
10:20 mavhq joined #salt
10:26 cryptolukas The problem is i get the localhost address too. salt 'mx1.test.de' grains.get ipv4
10:28 akhter joined #salt
10:32 amontalban joined #salt
11:02 DrunkSignal joined #salt
11:16 abednarik joined #salt
11:20 CEH joined #salt
11:31 promorphus joined #salt
11:31 edrocks joined #salt
11:58 jas02 joined #salt
12:01 ivanjaros joined #salt
12:02 DrunkSignal joined #salt
12:06 CEH joined #salt
12:22 CEH joined #salt
12:29 jas02 joined #salt
12:34 amontalban joined #salt
12:42 zer0def joined #salt
12:44 abednarik joined #salt
12:48 bastiandg joined #salt
13:03 DrunkSignal joined #salt
13:04 Electron^- joined #salt
13:07 west575 joined #salt
13:21 DEger joined #salt
13:31 akhter joined #salt
13:32 promorphus joined #salt
13:34 edrocks joined #salt
13:52 mavhq joined #salt
14:00 jas02 joined #salt
14:01 fracklen joined #salt
14:03 jeddi joined #salt
14:04 DrunkSignal joined #salt
14:10 fracklen joined #salt
14:25 akhter joined #salt
14:26 tercenya_ joined #salt
14:27 mavhq joined #salt
14:29 mavhq joined #salt
14:36 amontalban joined #salt
14:39 spuder joined #salt
14:40 saltsupernoob joined #salt
14:40 saltsupernoob Hi guys is there anyway to do a package.install accepting any vendor changes which may occure
14:40 saltsupernoob Hi guys is there anyway to do a package.install accepting any vendor changes which may occur
14:40 jas02 joined #salt
14:41 honestly what do you mean by vendor changes? config file conflicts?
14:42 mavhq joined #salt
14:43 saltsupernoob so running on suse currently the vendor for python.backports.ssl is suse however when doing an  python-docker-py install it wants to change the vendor to our obs repo which is fine wondering if theres anyway to accept this rather than having to manually do it on all the machines
14:44 saltsupernoob its basically needs to swap out the binary
14:44 saltsupernoob to ours over theres
14:45 honestly does "vendor" mean "repository"?
14:45 mavhq joined #salt
14:45 saltsupernoob no its who owns the repo
14:45 saltsupernoob and who is responsable for the package
14:46 honestly you'd have to check the implementation module for your package system to see if it supports that
14:46 honestly tbqf it sounds pretty weird
14:46 honestly are you using yum or rpm or what?
14:46 saltsupernoob zypper
14:47 honestly then look at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.zypper.html
14:48 mavhq joined #salt
14:51 xet7 joined #salt
14:51 mavhq joined #salt
14:53 jas02 joined #salt
14:56 mavhq joined #salt
14:58 tercenya joined #salt
14:59 Hybrid joined #salt
15:01 jas02_ joined #salt
15:05 DrunkSignal joined #salt
15:09 mavhq joined #salt
15:14 mavhq joined #salt
15:16 CEH joined #salt
15:25 mavhq joined #salt
15:29 mavhq joined #salt
15:31 samodid joined #salt
15:33 promorphus joined #salt
15:46 mavhq joined #salt
15:55 saltsupernoob and another silly question am i going crazy or is the : actully here in the correct place ?     Data failed to compile: ----------     Rendering SLS 'base:docker.build' failed: could not found expected ':'; line 4  --- include:  docker.config  docker/nba:latest:    <======================  dockerng.image_present:   - build: /workspace/nba/
15:55 saltsupernoob if i restart the master i can run the build once however the minion times out
15:55 saltsupernoob then i get the syntax error on subsquent runs
15:59 saltsupernoob pastebin for ease of readabilty http://pastebin.com/wjtCffp1
16:00 DEger joined #salt
16:01 mavhq joined #salt
16:02 jas02_ joined #salt
16:04 mavhq joined #salt
16:05 CEH joined #salt
16:06 rem5_ joined #salt
16:07 xet7 joined #salt
16:11 fracklen joined #salt
16:13 samodid joined #salt
16:15 spuder joined #salt
16:20 mavhq joined #salt
16:33 besideyou-SP-Bra joined #salt
16:35 edrocks joined #salt
16:48 akhter joined #salt
16:57 theblazehen_ joined #salt
17:25 promorphus joined #salt
17:43 andi- joined #salt
17:48 nawwmz joined #salt
18:00 alexanderilyin joined #salt
18:02 DrunkSignal joined #salt
18:02 PerilousApricot joined #salt
18:03 jas02 joined #salt
18:04 XenophonF saltsupernoob: you have syntax errors on lines 1 and 2
18:04 XenophonF add a colon to the end of line 1
18:04 XenophonF add two spaces, a dash, and a space to the beginning of line 2
18:04 snc joined #salt
18:04 XenophonF oh strike that - you don't need an extra colon on line 1
18:04 jas02_ joined #salt
18:06 rem5 joined #salt
18:08 jas02 joined #salt
18:09 jas02_ joined #salt
18:12 fracklen joined #salt
18:16 haam3r joined #salt
18:19 rem5 joined #salt
18:25 DEger joined #salt
18:26 saltsupernoob ahh cheers thanks though i was going crazy and couldnt spot it for the life of me
18:28 ivanjaros joined #salt
18:28 nawwmz joined #salt
18:33 DEger joined #salt
18:35 juanito joined #salt
18:37 DEger joined #salt
18:48 sgo_ joined #salt
18:50 akhter joined #salt
18:52 fracklen joined #salt
18:53 IdoKaplan joined #salt
18:55 IdoKaplan Hi, I'm trying to refresh gitfs Upon Push. Git is a docker machine inside salt-master server. I'm getting this error "[WARNING ] Although 'dmidecode' was found in path, the current user cannot execute it. Grains output might not be accurate" when running "sudo -u root salt-call event.fire_master update salt/fileserver/gitfs/update" in the Git server. Can you please help?
18:57 sh123124213 the difference between using tornado vs cherrypy in salt-api is that tornado is event driven and cherrypy is multithreaded right ?
18:58 stanchan joined #salt
18:59 cyteen joined #salt
19:04 juanito_ joined #salt
19:08 sh123124213 is there anyway I can enable salt-api for xmlrpc ?
19:08 alexanderilyin joined #salt
19:09 jas02 joined #salt
19:11 fracklen_ joined #salt
19:17 haam3r joined #salt
19:33 smcquay joined #salt
19:53 DEger joined #salt
19:59 Klas joined #salt
20:01 jas02 joined #salt
20:01 Sarphram joined #salt
20:04 Klas joined #salt
20:07 SuBsIgNaL joined #salt
20:12 f4 joined #salt
20:24 cyteen joined #salt
20:26 jas02 joined #salt
20:31 mavhq joined #salt
20:31 keltim joined #salt
20:32 mikecmpbll joined #salt
20:34 spuder joined #salt
20:34 mavhq joined #salt
20:39 edrocks joined #salt
20:44 garphy`aw joined #salt
20:47 hasues joined #salt
20:47 hasues left #salt
20:50 fannet joined #salt
20:53 akhter joined #salt
20:54 jas02 joined #salt
20:56 sgo_ joined #salt
21:10 DEger_ joined #salt
21:12 SuBsIgNaL joined #salt
21:22 mohae_ joined #salt
21:25 preludedrew joined #salt
21:30 amcorreia joined #salt
21:37 cyteen joined #salt
21:37 jacksontj joined #salt
21:39 jas02 joined #salt
21:49 promorphus Hey guys, I'm running a bunch of containers, and want to be able to make sure they're using the 'latest' tag to denote which version of the containers to have running. I'd like salt to pull / compare the version of the container running vs the actual latest version before running it, can anyone give me a way to do this? In particular, Im wondering if there's a way to do this using dockerng.image_running as an argument
21:49 promorphus im sorry, dockerng.running
21:54 DEger joined #salt
21:54 nidr0x joined #salt
22:00 DEger_ joined #salt
22:09 ivanjaros joined #salt
22:10 ivanjaros3916 joined #salt
22:14 amontalban joined #salt
22:17 cyteen_ joined #salt
22:19 nidr0x joined #salt
22:24 jeddi joined #salt
22:26 fracklen joined #salt
22:26 cyteen_ joined #salt
22:26 jas02 joined #salt
22:27 cyteen_ joined #salt
22:28 hopthrisC joined #salt
22:29 akhter joined #salt
22:31 cyteen joined #salt
22:33 fannet joined #salt
22:35 Zaunei joined #salt
22:45 nidr0x joined #salt
22:46 Zaunei joined #salt
22:47 jas02 joined #salt
22:52 whytewolf joined #salt
23:02 spuder joined #salt
23:13 JonGretar joined #salt
23:38 SuBsIgNaL joined #salt
23:38 mavhq joined #salt
23:42 mrueg joined #salt
23:48 jas02 joined #salt
23:50 subsignal joined #salt
23:51 amontalb1n joined #salt

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