Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-02-05

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

All times shown according to UTC.

Time Nick Message
00:00 shaggy_surfer joined #salt
00:00 berserk joined #salt
00:06 bhosmer joined #salt
00:09 joe_n joined #salt
00:10 subsignal joined #salt
00:11 Guest12597 joined #salt
00:12 PredatorVI jfindlay (and anyone else):  I sent an email to rallytime as suggested, but in thinking about it more, I think the issue is with processing the command response via orchestrate.  All indications from the log suggest the state.highstate succeeded since all components were installed and running correctly, including rabbitmq...
00:12 calculon joined #salt
00:12 PredatorVI The gist is at https://gist.github.com/PredatorVI/3e7ea91595607d89943e
00:13 PredatorVI Guessing it is specifically related to serializing some portion of the state.highstate result
00:17 xnly joined #salt
00:18 rem5 joined #salt
00:18 nahamu stevei101: Solaris or illumos?
00:18 xnly Hello, I see salt minion/master config examples with "- consul: consul_config root=salt/minion/%(minion_id)s" (from ext_pillar), the `minion_id` that is a string here, what is the list of other variables available for use like this in the config?
00:19 nahamu stevei101: I run it on SmartOS pretty happily and sjorge has been doing a bunch of additional work on it lately too.
00:20 stevei101 yes i meant solaris
00:28 lompik joined #salt
00:29 Guest12597 joined #salt
00:29 brianfeister joined #salt
00:31 dendazen joined #salt
00:33 baweaver joined #salt
00:38 MadsRC_ joined #salt
00:38 mrbobbytables_ joined #salt
00:40 rawzone joined #salt
00:42 dober joined #salt
00:42 dober joined #salt
00:42 joe_n joined #salt
00:46 Guest12597 joined #salt
00:55 rem5 joined #salt
00:56 ninjada joined #salt
01:01 bhosmer joined #salt
01:01 Guest12597 joined #salt
01:10 grumm_servire joined #salt
01:17 rem5 joined #salt
01:17 nahamu Cool. I don't know of anyone using it on Solaris, but lately I haven't been following things very closely, so who knows...
01:22 rem5 joined #salt
01:24 antpa joined #salt
01:25 pfallenop joined #salt
01:32 ageorgop joined #salt
01:38 brianfeister joined #salt
01:40 ageorgop joined #salt
01:41 ageorgop joined #salt
01:41 shaggy_surfer joined #salt
01:43 grumm_servire joined #salt
01:50 ageorgop joined #salt
01:50 cybacolt joined #salt
01:51 totzky joined #salt
01:51 pfallenop joined #salt
01:52 grumm_servire joined #salt
01:52 ageorgop joined #salt
01:55 bhosmer_ joined #salt
01:57 scoates joined #salt
02:00 lorengordon joined #salt
02:04 pfallenop joined #salt
02:10 darix joined #salt
02:10 JDiPierro joined #salt
02:16 jack__ joined #salt
02:21 pfallenop joined #salt
02:23 ageorgop joined #salt
02:25 ageorgop joined #salt
02:27 trent joined #salt
02:30 ninjada joined #salt
02:34 wych joined #salt
02:39 Pie_Mage joined #salt
02:46 jack__ joined #salt
02:47 ilbot3 joined #salt
02:47 Topic for #salt is now Welcome to #salt! | Latest Version: 2015.8.4 | Register for SaltConf16: http://saltconf.com/register/ | Paid support available for open source Salt! https://www.saltstack.com/support/ | Logs: http://irclog.perlgeek.de/salt/ | Paste: https://gist.github.com/ (please don't multiline paste into channel) | Ask with patience as we are volunteers and may not have immediate answers
02:48 hightekvagabond joined #salt
02:50 bhosmer joined #salt
02:54 antpa joined #salt
02:56 evle joined #salt
02:56 grumm_servire joined #salt
02:57 donmichelangelo joined #salt
03:02 anthpa joined #salt
03:09 antpa joined #salt
03:12 jack__ joined #salt
03:14 berserk joined #salt
03:18 Ashald joined #salt
03:22 writtenoff joined #salt
03:24 _beardedeagle joined #salt
03:31 evle joined #salt
03:33 ageorgop joined #salt
03:38 jack__ joined #salt
03:38 berserk joined #salt
03:39 quasiben joined #salt
03:44 bhosmer_ joined #salt
03:48 digitalhero joined #salt
03:48 rem5 joined #salt
03:52 jack__ joined #salt
04:07 xenly joined #salt
04:08 xenly https://github.com/saltstack/salt/blob/develop/salt/pillar/consul_pillar.py#L102 - rather than using the "minion_id" here, could grains be used?
04:10 anmolb joined #salt
04:11 racooper joined #salt
04:12 jack__ joined #salt
04:13 aw110f joined #salt
04:14 treaki_ joined #salt
04:20 jack__ joined #salt
04:20 hasues joined #salt
04:21 hasues left #salt
04:33 brianfeister joined #salt
04:38 bhosmer_ joined #salt
04:57 anmolb joined #salt
05:06 voidspacexyz joined #salt
05:06 ViciousLove joined #salt
05:14 MeltedLux joined #salt
05:18 jfindlay stevei101: we have enterprise support for solaris
05:32 bhosmer_ joined #salt
05:39 joe_n joined #salt
05:41 quasiben joined #salt
05:59 MTecknology What the crap is novaclient and why do I keep getting errors about it?
06:00 calvinh joined #salt
06:00 GreatSnoopy joined #salt
06:03 MTecknology looks like the issues have been opened for it
06:04 ecdhe joined #salt
06:05 atmosx joined #salt
06:06 mapu joined #salt
06:07 ninjada_ joined #salt
06:12 nidr0x joined #salt
06:17 pfallenop joined #salt
06:22 hightekvagabond joined #salt
06:22 brianfeister joined #salt
06:28 pfallenop joined #salt
06:44 av_ joined #salt
06:44 pfallenop joined #salt
06:45 brianfeister joined #salt
06:47 jack__ joined #salt
06:56 krymzon joined #salt
06:58 hojgaard joined #salt
06:59 anmolb joined #salt
07:00 anmolb joined #salt
07:02 giantlock joined #salt
07:20 bhosmer_ joined #salt
07:34 dariusjs joined #salt
07:38 cztanu joined #salt
07:39 jack__ joined #salt
07:43 Brayheim joined #salt
07:44 Brayheim left #salt
07:47 KermitTheFragger joined #salt
07:49 GreatSnoopy joined #salt
07:49 viq joined #salt
07:51 anthpa joined #salt
08:00 linjan joined #salt
08:11 malinoff joined #salt
08:15 bhosmer joined #salt
08:15 rominf joined #salt
08:18 slav0nic joined #salt
08:19 jhauser joined #salt
08:23 PurpleTree joined #salt
08:24 PeterO_ joined #salt
08:25 PurpleTree hello
08:26 PurpleTree I was wondering if somebody could help me with my salt problem
08:27 PurpleTree I have VM with debian 8
08:27 kawa2014 joined #salt
08:27 PurpleTree installed version 2015.8.5 from the repo
08:28 PurpleTree and it fails to run
08:28 PurpleTree it throws "AttributeError: 'module' object has no attribute 'BASE_THORIUM_ROOTS_DIR' "
08:29 aqua^c joined #salt
08:29 PurpleTree it throws the same error if I try to run salt-minion or salt-master
08:32 auzty joined #salt
08:33 babilen That string doesn't appear at all in the salt codebase. Could you paste the *entire* error to one of http://refheap.com, http://paste.debian.net, https://gist.github.com, http://sprunge.us, … and elaborate on any customisation you've done on the setup?
08:34 PurpleTree sure
08:34 babilen That string is on develop though ..
08:34 babilen (it wasn't in the 2015.8 branch)
08:35 PurpleTree The full error code:
08:35 PurpleTree http://pastebin.com/4v4F2Tai
08:35 babilen Please don't use pastebin.com .. it is horrible
08:36 PurpleTree ok
08:36 babilen No need to repaste it now, but there are simply many better paste sites
08:36 babilen Lets see what happened there now ..
08:37 PurpleTree There shouldn't be any customisations on the setup
08:37 PurpleTree it's a generated VM instance from Azure
08:37 atmosx joined #salt
08:38 babilen PurpleTree: Yeah, its fine. Let me investigate what happened there ..
08:41 jack__ joined #salt
08:43 XenophonF joined #salt
08:44 krymzon joined #salt
08:44 babilen PurpleTree: What does "dpkg -S /usr/lib/python2.7/dist-packages/salt/config/__init__.py" give you?
08:45 PurpleTree dpkg-query: no path found matching pattern /usr/lib/python2.7/dist-packages/salt/config/__init__.py
08:45 babilen How about "dpkg -l 'salt*'" ?
08:46 PurpleTree https://gist.github.com/anonymous/a21eccae2530ef5447a9
08:46 babilen Let me try to reproduce that in a VM
08:47 babilen config/__init__.py shouldn't exist in 2015.8 and I can't find it in the packages. How did you install salt?
08:47 babilen What does "dpkg -a --configure" give you?
08:48 cswang joined #salt
08:48 linjan joined #salt
08:48 PurpleTree https://gist.github.com/anonymous/000e647925a5bce3cc15
08:49 babilen Thanks, how did you install salt?
08:49 PurpleTree I followed these steps:
08:49 PurpleTree https://docs.saltstack.com/en/latest/topics/installation/debian.html
08:49 losh joined #salt
08:49 babilen And the initial installation failed similar to what you've just shown me?
08:50 PurpleTree yep
08:54 babilen Let me reproduce that locally
08:55 PurpleTree I have a local VM with debian and there it works with no problems
08:55 babilen Also jessie and you are referring to jessie?
08:56 babilen err
08:56 PurpleTree yes
08:56 babilen "referring to the installation" :)
08:58 PurpleTree I tried also the development branch
08:58 babilen Just now?
08:58 PurpleTree Installed it with one of these methods
08:58 PurpleTree https://docs.saltstack.com/en/latest/topics/tutorials/salt_bootstrap.html
08:59 PurpleTree before
08:59 babilen well ...
08:59 babilen That would explain why you have development branch files there
08:59 babilen I couldn't come up with a sensible explanation why installing the packages would have left them on the filesystem (also given that they do *not* belong to a package)
09:00 PurpleTree but removed it because it gave a weird error while running the salt files
09:00 babilen You obviously didn't remove all of it
09:00 geomacy joined #salt
09:00 babilen Could you delete that instance and start fresh again?
09:00 babilen Installing the packages worked perfectly on a VM here
09:02 PurpleTree yeah I can
09:02 PurpleTree I'll see if that helps
09:02 mr-op5 joined #salt
09:03 PurpleTree I removed the installed versions with "apt-get remove" and then "apt-get autoremove"
09:03 PurpleTree Is there a better method?
09:05 jack__ joined #salt
09:05 s_kunk joined #salt
09:06 babilen PurpleTree: I meant: "Delete your Azure instance and reinstall it"
09:06 PurpleTree sure sure, I'm doing it :)
09:07 PurpleTree but I was asking for the future
09:07 babilen We could alternatively investigate how to really get rid of the salt version you installed by bootstrapping it, but that might take a while.
09:08 PurpleTree The instance is deploying
09:09 bhosmer joined #salt
09:15 colttt_ joined #salt
09:26 sfxandy joined #salt
09:27 PurpleTree On the new instance the install seems to be working
09:28 babilen Well, who knows what went wrong
09:30 CeBe joined #salt
09:31 nicolas joined #salt
09:31 nicolas joined #salt
09:32 nicolas joined #salt
09:34 PurpleTree everything seems to be working now
09:34 PurpleTree thanks for your help!
09:34 N-Mi joined #salt
09:36 malinoff joined #salt
09:40 jack__ joined #salt
09:40 ruxu joined #salt
09:48 lyh joined #salt
09:49 Azid joined #salt
09:49 jack__ joined #salt
09:50 onovy joined #salt
09:50 rotbeard joined #salt
09:50 onovy hi all. is there any way to have !!omap working in salt pillar yaml files?
09:53 keimlink joined #salt
09:55 babilen onovy: What have you tried, what happened and what did you expect to happen?
09:55 onovy original: http://paste.openstack.org/show/486059/
09:56 cyteen joined #salt
09:56 onovy http://paste.openstack.org/show/486060/
09:56 onovy and order is not preserved
09:56 giannello joined #salt
09:57 babilen How do you know?
09:57 onovy running salt state.higstate
09:58 babilen go on
09:59 babilen What does "salt 'someminion' pillar.get rw-acls" give you?
10:02 geomacy joined #salt
10:02 onovy i think i got it
10:02 onovy http://paste.openstack.org/show/486063/
10:02 onovy added - at begging of line
10:03 bhosmer joined #salt
10:09 babilen yes, that would turn it into a list
10:09 lyh cli target by hostname(default minionid) works, but by -S <IP> ,“No minions matched the target”, what's the possible reason?  salt 2015.8.3 (Beryllium)
10:10 jack__ joined #salt
10:16 ninjada joined #salt
10:22 antpa joined #salt
10:23 amcorreia joined #salt
10:26 fredvd joined #salt
10:28 losh hello, I'm having trouble finding any documentation that explains the meaning of the whitelist option when calling state.highstate.  Could someone here give me a brief overview of it's purpose and how it's mean to be used?  The example from the docs is the following: salt '*' state.highstate whitelist=sls1_to_run,sls2_to_run
10:28 jack__ joined #salt
10:29 mattiasr joined #salt
10:30 SunPowered joined #salt
10:33 denys joined #salt
10:37 yuhlw joined #salt
10:37 yuhlw Is it possible to use a pillar within a pillar
10:37 saltsa joined #salt
10:39 yuhlw The usage, I'd like to have is that the first pillar is somehow a definition, when the second one does use this definition with jinja to make it a bit more smart
10:41 giantlock joined #salt
10:42 babilen yuhlw: Look into pillarstack
10:43 babilen https://github.com/saltstack/salt/issues/6955 is the (very old) issue concerning this
10:43 saltstackbot [#6955]title: Ability for pillar to read other pillar values | Hi, I have a number of states that could be greatly simplified if pillar could read other pillar values.  One use case example is I have a "walt_warning" pillar value which i populate in all managed files.  I have several pillar values that declare the entire contents of files which are referenced by jinja templates, and instead of having to populate each instances of this with the
10:46 jack__ joined #salt
10:49 antpa joined #salt
10:52 aidenir joined #salt
10:58 jack__ joined #salt
10:58 bhosmer joined #salt
11:06 kbaikov joined #salt
11:09 voidspacexyz joined #salt
11:09 giantlock joined #salt
11:11 dstokes_ joined #salt
11:11 tristianc_ joined #salt
11:13 honestly joined #salt
11:13 admgre joined #salt
11:13 admgre joined #salt
11:13 tru_tru joined #salt
11:14 eofs joined #salt
11:15 justanotheruser joined #salt
11:16 scc joined #salt
11:17 wych joined #salt
11:17 LondonAppDev joined #salt
11:17 xMopxShell joined #salt
11:17 Heartsbane joined #salt
11:17 jack__ joined #salt
11:17 gnord joined #salt
11:20 cswang_ joined #salt
11:21 Rumbles joined #salt
11:24 rubendv joined #salt
11:24 rubendv joined #salt
11:24 GreatSnoopy joined #salt
11:25 eightyeight joined #salt
11:26 N-Mi joined #salt
11:27 jrklein joined #salt
11:29 wm-bot443 joined #salt
11:32 jack__ joined #salt
11:33 zeltron joined #salt
11:34 zeltron left #salt
11:35 Rumbles joined #salt
11:43 djinni` joined #salt
11:43 ggoZ joined #salt
11:45 aqua^c joined #salt
11:48 Fabbe joined #salt
11:51 antpa joined #salt
11:52 bhosmer joined #salt
11:55 anthpa joined #salt
12:14 jack__ joined #salt
12:21 yidhra joined #salt
12:26 yidhra joined #salt
12:26 kshlm joined #salt
12:30 multiscan joined #salt
12:33 cangiani joined #salt
12:41 jack__ joined #salt
12:42 morissette joined #salt
12:45 ninjada joined #salt
12:46 Lionel_Debroux_ joined #salt
12:46 bhosmer joined #salt
12:47 DammitJim joined #salt
12:50 lompik joined #salt
12:51 jack__ joined #salt
12:53 ninjada joined #salt
12:55 kawa2014 joined #salt
12:56 PeterO_ joined #salt
12:57 quasiben joined #salt
12:58 onovy babilen: i forgot to say thank you! sorry and thanks for help
12:58 babilen Oh .. what did I help you with again? :)
12:58 giantlock joined #salt
13:01 sfz- joined #salt
13:01 rem5 joined #salt
13:03 dendazen joined #salt
13:03 dendazen on nj school
13:06 mattiasr left #salt
13:06 onovy babilen: remind me grains.get so i can better debug it :)
13:06 onovy and you know, sometimes you just need to ask someone and just few second after asking you figure it out :)
13:08 catpig joined #salt
13:08 scarcry joined #salt
13:13 AndreasLutro this is so weird - I can reproduce not being able to pkg.install to upgrade salt-minion from 2015.8.3 to 2015.8.5, but if I run the exact same apt-get command salt runs (based on the debug log), it works fine
13:15 babilen What happens if you run pkg.install ?
13:15 AndreasLutro same as I described to you the other day - dpkg complains about misconfiguration
13:16 giannello AndreasLutro, how much memory do you have on that machine? I've had a similar problem months ago on a very small dev vm, where the same command was failing when executed via salt due to the memory overhead
13:17 AndreasLutro it's definitely not that
13:17 babilen Yeah, that bug still hasn't been reported.
13:17 babilen (or I've missed it)
13:17 egil_ joined #salt
13:18 babilen Our suspicion was that the minion can't handle with files being upgraded "under the hood" while it is running.
13:18 babilen It is strange though as I haven't had that issue in the past and we've upgraded quite some a number of times
13:19 AndreasLutro babilen: https://bpaste.net/show/7c8d533ec9d4
13:19 AndreasLutro I can reproduce it reliably right now by switching between archive/2015.8.3 and 2015.8 in the apt source list
13:20 babilen And "dpkg -l 'salt*'" shows it in iFR ?
13:20 AndreasLutro only salt-minion
13:20 AndreasLutro salt-common was ii
13:20 babilen AndreasLutro: I'm done with my packages for jessie btw
13:20 AndreasLutro neat, I'll have to try it out
13:21 babilen Currently waiting for information on how to push to the testing repositories
13:22 AndreasLutro we'll be setting up mirrors of the salt minor version packages so we can always have a "stable" repo url point  to whatever has actually been tested
13:22 babilen Sounds like a plan
13:22 babilen I'll probably stick to the "community" repositories and personally ensure that proper packages are being uploaded
13:23 babilen AndreasLutro: Could you report that bug so that we can start gathering information on it?
13:24 babilen It looks as if the "apt-get upgrade" process isn't properly forked anymore and dies when the minion is being restarted or something along those lines
13:26 malinoff joined #salt
13:26 AndreasLutro I can't see any references to upgrade in the minon log, just apt-get update and apt-get install salt-minion
13:26 AndreasLutro plus a whole bunch of options of course
13:28 AndreasLutro https://github.com/saltstack/salt/issues/30937
13:28 saltstackbot [#30937]title: Debian: upgrading from 2015.8.3 with pkg.install fails | ```...
13:28 jack__ joined #salt
13:30 jraby joined #salt
13:30 KennethWilke joined #salt
13:31 sjorge joined #salt
13:32 sjorge joined #salt
13:34 AndreasLutro https://github.com/saltstack/salt/blob/v2015.8.3/salt/modules/aptpkg.py#L665-L669
13:34 AndreasLutro this seems a bit silly.. env never gets used
13:41 bhosmer joined #salt
13:42 linjan joined #salt
13:43 babilen AndreasLutro: Yeah, the "upgrade" was assuming that you run "pkg.upgrade" / "pkg.upgrade dist_upgrade=True" rather than "pkg.install". Naturally "pkg.install" is being used in the latter case
13:43 denys joined #salt
13:44 AndreasLutro apt/term.log ends at Preparing to unpack .../salt-minion_2015.8.5+ds-1_all.deb ...
13:45 bhosmer joined #salt
13:45 sjorge joined #salt
13:45 sjorge joined #salt
13:45 babilen Yeah, that's when the files are being overwritten
13:45 quasiben joined #salt
13:46 babilen sry, meeting now
13:46 egil joined #salt
13:47 geomacy joined #salt
13:49 sfxandy hi everyboduy
13:49 sfxandy everybody even
13:49 sfxandy i have a question about Salt mine usage.
13:49 ninjada joined #salt
13:49 sfxandy so, from Salts own documentation pages .......
13:50 sfxandy given this statement to obtain network.ip_addrs from the salt mine....
13:50 sfxandy {% for server, addrs in salt['mine.get']('roles:web', 'network.ip_addrs', expr_form='pillar').items() %}
13:51 sfxandy is there any way I can make it so that the pillar match was based on a variable? rather than being 'roles"web'
13:51 tpaul joined #salt
13:51 AndreasLutro what variable
13:51 sfxandy well whatever I want
13:51 AndreasLutro 'roles:' ~ my_var
13:51 AndreasLutro like this?
13:51 sfxandy does that work?
13:52 AndreasLutro ~ is the string concatenation character in jinja
13:52 sfxandy i knew that, just never thought to use it
13:52 AndreasLutro well, feel free to try it
13:52 AndreasLutro I don't know if it solves your use case
13:56 sfxandy well it didnt baulk at that ... but didn;t give me quite what i expected
13:56 subsignal joined #salt
14:03 jack__ joined #salt
14:04 akhter joined #salt
14:08 egil joined #salt
14:10 JDiPierro joined #salt
14:11 FeatherKing joined #salt
14:14 quasiben joined #salt
14:15 numkem joined #salt
14:16 quasiben joined #salt
14:20 stedaniels joined #salt
14:20 alvinstarr joined #salt
14:24 cpowell joined #salt
14:25 antpa joined #salt
14:25 jardoin 2016.3.0rc1 is the current RC right?
14:25 jardoin like, most current
14:26 AndreasLutro that seems to be the case
14:26 FeatherKing has anyone seen problems using grains.setval and the grain value not refreshing? this is 2015.5.2
14:27 FeatherKing the minion shows the new value, but not the master
14:27 favadi joined #salt
14:30 mpanetta joined #salt
14:30 quasiben joined #salt
14:32 rm_jorge joined #salt
14:34 * AndreasLutro writes custom module to install new minion safely
14:37 pcdummy joined #salt
14:39 giantlock joined #salt
14:39 jraby joined #salt
14:39 malinoff joined #salt
14:42 favadi joined #salt
14:45 teryx510 joined #salt
14:48 racooper joined #salt
14:50 kshlm joined #salt
14:52 favadi joined #salt
14:56 Tyrm joined #salt
14:57 geomacy joined #salt
14:58 DammitJim joined #salt
14:59 zmalone joined #salt
14:59 kaptk2 joined #salt
15:00 edrocks joined #salt
15:01 joshin joined #salt
15:01 joshin joined #salt
15:02 ahosking joined #salt
15:03 human01d joined #salt
15:03 dendazen joined #salt
15:03 human01d babilen: are you here ? =)
15:04 human01d babilen: wish you good weekend, here is ticket, which you asked #30939
15:04 jack__ joined #salt
15:06 tracphil joined #salt
15:07 pcdummy joined #salt
15:07 mrbob joined #salt
15:07 mrbob Hey guys
15:08 andrew_v joined #salt
15:08 mrbob Can anyone toss me some good salt resources?
15:08 onlyanegg joined #salt
15:09 saltsa joined #salt
15:10 akhter mrbob: What exactly are you looking for?
15:10 mrbob starting a devops salt job
15:10 akhter Anyone here use the #!py or the #!pyobjects renderers?
15:10 mrbob i know python and i'm a full stack dev
15:10 mrbob I just don't know salt
15:11 akhter mrbob: I recommend starting with state docs.
15:11 akhter One sec.
15:11 akhter https://docs.saltstack.com/en/latest/topics/tutorials/starting_states.html
15:11 zmalone mrbob: https://docs.saltstack.com/en/latest/ and https://github.com/saltstack/salt/issues
15:13 akhter Anyone here use the #!py or the #!pyobjects renderers?
15:14 akhter I'd like to know how to use file.managed source and specify a salt environment.  Or does this not matter?
15:14 pcn joined #salt
15:14 mrbobbytables hey folks, bit of an odd issue...when setting sysctl, system is ubuntu 14.04, and setting some fails the first time, but rerunning -- it succeeds.
15:15 akhter mrbobbytables: No idea what setting you're talking about.
15:15 akhter Is this in  a state?
15:15 mrbobbytables yeah, sorry
15:16 akhter Could you provide a gist for the error and the state?
15:16 mrbobbytables net.ipv4.max_syn_backlog, net.netfilter.nf_conntrack_max, few others
15:16 mrbobbytables sure 1 sec
15:16 mrbobbytables let me nuke vm and rerun
15:16 akhter Sure.
15:21 jack__ joined #salt
15:24 digitalhero joined #salt
15:26 mrbobbytables https://github.com/mrbobbytables/mygrid/tree/master/salt/salt/sysctl
15:27 mrbobbytables theres the state, pulls in info from pillars here: https://github.com/mrbobbytables/mygrid/tree/master/salt/pillar
15:28 mrbobbytables https://gist.github.com/mrbobbytables/fffbe6c04a8934399c05
15:28 mrbobbytables some info from the run
15:30 mapu joined #salt
15:31 mrbobbytables the values are present in the /etc/sysctl.conf, but it does error out
15:31 elsmo joined #salt
15:33 mrwboilers left #salt
15:36 Brew joined #salt
15:42 akhter joined #salt
15:43 human01d left #salt
15:44 scoates joined #salt
15:50 _JZ_ joined #salt
15:50 jraby joined #salt
15:53 jack__ joined #salt
15:54 snicers-work joined #salt
15:56 spuder joined #salt
15:58 snicers-work With git.latest I am getting 'Your local changes to the following files would be overwritten by merge:' when I attempt to apply my state to the minion
15:59 snicers-work I have
15:59 snicers-work - force_reset: True
15:59 snicers-work - force_checkout: True
15:59 berserk joined #salt
15:59 VSpike_ joined #salt
15:59 jordanpwalsh joined #salt
15:59 VSpike_ I know I knew how to do this once, but I can't remember at all. https://bpaste.net/show/19bd94d511f8 ... how can I merge the contents of that pillar into the "env" for the command?
16:00 berserk joined #salt
16:03 tmmt_ joined #salt
16:03 nicksloan- joined #salt
16:04 dgutu_ joined #salt
16:04 v0rtex_ joined #salt
16:04 karlthane joined #salt
16:05 Ashald joined #salt
16:06 yidhra_ joined #salt
16:06 zsoftich1 joined #salt
16:06 Yoda-BZH` joined #salt
16:06 jack__ joined #salt
16:07 jhauser_ joined #salt
16:07 tooth_ joined #salt
16:08 VSpike Ah, never mind. https://docs.saltstack.com/en/latest/ref/states/all/salt.states.cmd.html#how-do-i-create-an-environment-from-a-pillar-map
16:08 VSpike Knew I'd seen it somewhere
16:09 admgre_ joined #salt
16:12 tligda joined #salt
16:14 nicksloan joined #salt
16:15 jraby left #salt
16:16 aqua^c joined #salt
16:18 favadi joined #salt
16:18 onlyanegg joined #salt
16:18 wm-bot4 joined #salt
16:18 ekristen joined #salt
16:18 hasues joined #salt
16:19 etw joined #salt
16:21 hasues left #salt
16:21 malinoff joined #salt
16:23 jack__ joined #salt
16:25 daemonkeeper joined #salt
16:26 Qwazerty joined #salt
16:29 yuhlw babilen: thanks for your information
16:30 Bryson joined #salt
16:30 TooLmaN joined #salt
16:32 daemonkeeper joined #salt
16:32 winsalt joined #salt
16:33 eichiro joined #salt
16:35 kermit joined #salt
16:37 cpowell joined #salt
16:39 scarcry joined #salt
16:39 KennethWilke joined #salt
16:39 daemonkeeper joined #salt
16:40 PeterO joined #salt
16:44 wych joined #salt
16:48 MTecknology I MIGHT BE GOING TO SALTCONF!!!! :D
16:49 MTecknology iggy: It would be rather funny if the next drink we get is there instead of here...
16:49 malinoff joined #salt
16:51 djgerm Woo! is there a big banner at saltconf that has "#salt" so we know "this is the room for heroes who solve problems"?
16:52 jfindlay MTecknology: be sure to register today as today is the last day for discounted registration
16:52 jfindlay djgerm: we should have that :)
16:54 MTecknology jfindlay: I'm trying to get my old employer (where I'm still technically sort of employed) to buy support and then I'll grab that ticket since they already paid for my replacement to go. Then I'll have my current employer cover everything else from my "education allowance"
16:54 MTecknology otherwise I'm not able to afford it this year
16:56 digitalhero joined #salt
16:57 N-Mi joined #salt
16:59 PeterO joined #salt
16:59 jack__ joined #salt
17:04 winsalt Im noticing a performance hit on windows minions when upgrading to 2015.8.4 from 8.3, even with simple commands like test.ping the minion will not respond quick enough
17:05 giantlock joined #salt
17:07 winsalt If i increase the timeout to 20 seconds they will respond eventually,  does anyone know what changed in the last release?
17:07 heaje joined #salt
17:07 sfxandy joined #salt
17:10 scarcry joined #salt
17:10 Tyrm joined #salt
17:10 MTecknology winsalt: I don't know for sure, but I heard rumors that the last update had a whole lotta windows fixes in it
17:11 kshlm joined #salt
17:12 Tyrm_ joined #salt
17:12 MTecknology jfindlay: also, thanks for making sure I knew this was the last day to save $400! :D
17:13 jfindlay winsalt: that is strange you are noticing it between 8.3 and 8.4.  I think the switch to multiprocessing came in 8.0
17:15 winsalt to test, I have 4 servers here.  3 are on 8.4, 1 i reverted to 8.3.  without setting a timeout, only the 8.3 minion returns
17:15 writtenoff joined #salt
17:16 quasiben joined #salt
17:16 winsalt I think it has to do "Minion return retry timer set to 9 seconds (randomized)"
17:16 MTecknology can you run them with '-l debug' and see where that long timeout happens?
17:17 jfindlay winsalt: I know that there was a performance regression with the switch to multithreading on windows that corresponds to your experience.  I'm not sure that has been completely resolved or not
17:19 Tyrm joined #salt
17:19 jfindlay s/multithreading/multiprocessing/
17:20 cangiani joined #salt
17:20 winsalt would setting multiprocessing: False   help?
17:20 jfindlay winsalt: https://github.com/saltstack/salt/issues/27866
17:20 saltstackbot [#27866]title: Slow response from Windows minions on 2015.8 | Sending a test.ping to a Windows minion seems to take on average nearly 6 seconds, compared to less than 1 seconds for a Linux minion....
17:20 jfindlay winsalt: it is likely
17:21 tracphil_ joined #salt
17:24 gimpy927 left #salt
17:26 hasues joined #salt
17:26 gordonm joined #salt
17:27 antpa joined #salt
17:27 tkeith I have a state that enables ufw and blocks all except port 22 ("ufw default reject; ufw allow 22; ufw enable"). This seems to (sometimes) cause the minion to stop responding until it reboots. It appears ufw may be blocking connections from the master on port 4505/6. My understanding is that the minion connects to the master but not the other way around. Why might this be happening?
17:28 Tyrm joined #salt
17:29 MTecknology tkeith: totally unrelated, but consider poking at ferm..  https://gist.github.com/MTecknology/ebd746dc9d7cc7d351f0
17:30 jfindlay tkeith: on the zmq transport that is right.  Could your firewall also be intercepting outbound traffic as well?
17:30 winsalt multiprocessing: False, works.  Thanks guys.
17:31 onlyanegg joined #salt
17:31 winsalt I thought multiprocess was default False, did that change, or am i imagining things?
17:31 jfindlay winsalt: nice.  That is definitely a bad bug, but there are things that can't be done on windows without multiprocessing.  I am not aware of the details, though.  Dave and Shane are working it out
17:31 jab416171 joined #salt
17:32 DammitJim joined #salt
17:33 tkeith jfindlay: I don't believe it should (I've never experienced that with any other applications, and syslog shows incoming requests to those ports)
17:33 hasues left #salt
17:34 tkeith jfindlay: Also, this time it eventually (after 5-10 mins) started working again without even rebooting
17:34 jab416171 joined #salt
17:35 akhter joined #salt
17:38 jfindlay winsalt: the change to multiprocessing helps with job management
17:39 shaggy_surfer joined #salt
17:39 jfindlay tkeith: that is interesting.  It seems like you may have to start doing some network debugging
17:42 akhter_1 joined #salt
17:42 fxhp joined #salt
17:55 shoemonkey joined #salt
18:01 shoemonk_ joined #salt
18:02 jack joined #salt
18:07 hightekvagabond joined #salt
18:10 djgerm left #salt
18:11 digitalhero joined #salt
18:11 bbbryson joined #salt
18:12 trent ok if I have two state files ... one includes the other ... the one that is included sets grains.  how can I make those grains accessable in jinja logic? or is the answer you can't
18:12 jab416171 I'm having a lot of issues with timeouts, can someone take a look and tell me what's going on here? running the same exact command 3 times in a row, and different minions respond each time. https://gist.githubusercontent.com/jab416171/6d51bd9f0fa8f75ebc4d/raw/gistfile1.txt
18:13 jab416171 we have a dual master setup (only one is active) with a set of syndics below them, one per geo, and then all of the minions below that.
18:13 jab416171 I've tried playing with and tweaking timeout, gather_job_timeout, and syndic_wait but no combination seems to work well.
18:14 AndreasLutro anything interesting in your master/minion logs?
18:14 AndreasLutro consider increasing the log level
18:15 jab416171 I'm seeing Could not write job cache file for minions: []
18:16 jab416171 and An extra return was detected from minion someotherminion.example.com, please verify the minion, this could be a replay attack
18:16 jab416171 there's 22k instances of "Could not write job cache" since Sunday
18:17 jfindlay trent: jinja is rendered at the beginning of a state run, so it is not going to contain any updates made in the state run itself
18:21 Guest36793 joined #salt
18:23 impi joined #salt
18:23 SunPowered joined #salt
18:24 trent jfindlay: ok thanks ... is there a better way to do that?
18:29 Crazy67 joined #salt
18:29 grumm_servire joined #salt
18:30 hosttor joined #salt
18:31 aw110f joined #salt
18:33 Fiber^ joined #salt
18:33 babilen trent: Do you really have to do this via grains? What kind of data are you modelling there?
18:35 trent babilen: nope I'm open to ideas ... really its just a role that I'm setting
18:35 trent I would like it set in a grain ... but if I can set it somewhere else as well to facilitate the machine creation I'm OK with that
18:36 trent just a if roll is database install postgres
18:36 babilen Why don't you keep roles in pillars or do you *really* have to maintain them in a distributed and insecure manner?
18:36 babilen (insecure in the sense that minions can lie about their grains)
18:36 trent babilen: sure not a bad idea ...  but don't I have the same problem there
18:37 trent i.e. jinja renders first
18:38 babilen You no longer have to set pillars in that case as they are already available. There is no way to get them to the minions beforehand as that has already been done.
18:38 babilen well s/pillars/that data/ is probably better
18:38 trent but thats the thing .. where would I put that data into a pillar?
18:38 babilen So the second state that requires that data can use it right away
18:39 babilen trent: Where is the data coming from now?
18:39 trent right so machine is created via salt-cloud ... based on hostname etc etc a role is assigned .. a reactor is called to finish bringing up the machine
18:40 trent right now I'm assigning the role in a state run by the reactor
18:40 trent but to assign a pillar or something else I need to run code somewhere
18:40 babilen Okay, so you could simply target pillars based on hostname in that case.
18:40 babilen '*database*: - roles.database
18:40 trent that makes sense ... set pillars based on hostname or other initial grain data
18:41 trent I'll have to look at which things I can target in a pillar ... but that makes sense to me
18:41 trent babilen: thanks for the help
18:42 cliluw joined #salt
18:42 babilen I mean you could match on something else .. another common approach would be to keep that assignment of host <-> role(s) in an external datasource that you access as external pillar. Look into https://docs.saltstack.com/en/latest/ref/pillar/all/ for a list of suitable datasources.
18:43 trent awesome! I'll dig in
18:43 babilen trent: Using pillars also has the advantage that you don't have to care about "local state" on the minion anymore and that you can trust them ..
18:43 Crazy67 joined #salt
18:44 berserk joined #salt
18:45 Guest36793 joined #salt
18:46 Ryan_Lane_ wow. what in the world is going on with all the regressions?
18:48 baweaver joined #salt
18:48 babilen Ryan_Lane_: You really wonder how that managed to slip throughk, don't you?
18:48 snarfy joined #salt
18:48 Ryan_Lane_ well, two point releases in a row with regressions
18:48 Ryan_Lane_ there should really be a strict no-features policy to point releases
18:49 Ryan_Lane_ bug and security fixes only
18:49 Ryan_Lane_ 2015.8 has had what 3 major regressions now?
18:49 AndreasLutro yes please
18:50 babilen We've mentioned a "only miniomal bug fixes" policy in point releases ... I would be 100% behind that.
18:52 babilen Bring Debian's idea of "stable" to salt so that one can be sure that a point release doesn't change anything. Allow users to track 20XX.Y branches/repos without fear of breaking anything.
18:52 Ryan_Lane_ yep
18:52 Ryan_Lane_ that would be ideal
18:53 zmalone There are a lot of broken things that need to be fixed, so I'm not sure fully stable releases are a possibility.
18:55 AndreasLutro I'd be happy with more stability, full stability is an impossibility
18:56 GreatSnoopy joined #salt
18:56 Ryan_Lane_ sure, but from what I can tell all three regressions wouldn't have happened if features weren't added
18:56 jab416171 anyone know why my logs are being flooded with "Could not write job cache file for minions: []"?
18:56 jfindlay babilen: we've started to be more limited in accepting fixes for release branches
18:56 AndreasLutro indeed
18:56 Ryan_Lane_ @jab416171 is your master filesystem full?
18:56 jfindlay mainly because Mike took over pull requests :)
18:57 jab416171 Ryan_Lane_, no, it's at 17%
18:57 Ryan_Lane_ @jab416171 inodes?
18:57 Ryan_Lane_ stupid slack is ruining me
18:57 jab416171 inodes is at 22%
18:57 Ryan_Lane_ hm. no idea then. sorry :)
18:58 jab416171 and why is it an empty list?
18:58 Ryan_Lane_ the limit of my knowledge on that
18:58 Crazy67 joined #salt
18:58 jab416171 there's no minions that it's not writing the job cache for
18:58 aqua^c joined #salt
18:58 jfindlay I used to be more open to backporting fixes, but I think the new process is better.  The problem is that new code does continue to come in and this shifts the testing burden to release time, whereas we still have limited resources test things
19:01 Ryan_Lane_ make a release branch for the new version. all new changes go into develop. no new changes in release branch :)
19:01 Ryan_Lane_ only bug fixes and security fixes in release branch
19:01 Ryan_Lane_ just like it was released
19:01 Ryan_Lane_ "if you don't have a feature in by x, it waits 3 months"
19:02 Ryan_Lane_ the openstack projects do this and they basically always meet their release deadlines
19:02 lompik joined #salt
19:03 Ryan_Lane_ I know it's easier to say these things than to do them, but on my side getting a stable release is really important
19:04 denys joined #salt
19:04 AndreasLutro I'm more than ok with delayed releases - but I've been waiting almost 2 weeks for a critical security update because pillar merging behaviour keeps changing in 2015.8.x
19:05 jfindlay Ryan_Lane_: right, and part of the challenge is that many 'bug fixes' end up having bonus effects
19:05 * Ryan_Lane_ nods
19:05 catpig joined #salt
19:06 XenophonF Ryan_Lane_: +1
19:06 jfindlay the real problem is that we need more resources on QA development
19:06 * jfindlay points at self :-/
19:07 babilen We can help!
19:07 AndreasLutro I dunno, I hate to point at specific issues but look at something like this https://github.com/saltstack/salt/pull/30686
19:07 babilen But for that additional repositories are needed that *we* can target in our QA infrastructure.
19:07 saltstackbot [#30686]title: Master-side pillar caching | An experimental master-side pillar cache. This can greatly improve master load in cases where the pillar is relied upon heavily, as well obvious improvements for the case of slow external pillars....
19:07 winsalt speaking of which.  Do you know anything about file.line being unavailable on win minions
19:07 XenophonF yeah, same here, jfindlay
19:07 AndreasLutro it even has "experimental" in the first sentence of the issue description, why is it against a stable release
19:08 jfindlay AndreasLutro: good point
19:09 AndreasLutro most of the bugs I find I track back to a PR which adds some feature, or a PR that fixes another added feature... though that's just anecdotal I guess
19:09 jfindlay babilen: I'm working on writing a new integration test infrastructure that uses salt to test salt, with the goal being that tests will be much easier to write and run than our current programmatic unit and integration tests
19:10 babilen That sounds good, but there are many arcane deployments out in the wild. In the end a number of bugs will only be caught if a new version has been tested by actual users. Naturally bugs such as the one that caused .5 should be dealt with earlier, but right now a lot of the "RC" work is being done internally by salt.
19:10 babilen I still wonder how that managed to slip through.
19:11 AndreasLutro if there were nightly debian packages I'd test them all the time... just saying ;)
19:11 babilen I *really* do .. requisites are such an integral part of saltstack that I can't really explain it to myself :)
19:12 babilen AndreasLutro: exactly .. *that's* that strength of having an automatic build process such as what is being tried with salt-pack
19:13 baweaver joined #salt
19:13 jfindlay I think nightly packages would be better than having RCs for minor releases, but then new features shouldn't be happening in minor releases
19:14 zmalone AndreasLutro: https://github.com/saltstack/salt/pull/30686 is a wild ticket, although I think those features were mostly feature flagged off
19:14 saltstackbot [#30686]title: Master-side pillar caching | An experimental master-side pillar cache. This can greatly improve master load in cases where the pillar is relied upon heavily, as well obvious improvements for the case of slow external pillars....
19:14 zmalone especially because I can imagine a lot of possible security concerns
19:14 AndreasLutro I'd like nightly packages for every actively maintained minor version
19:16 Guest36793 joined #salt
19:16 AndreasLutro I'd run 2015.8 nightlies in my test VMs and live test environment to spot bugs, if I can report/fix them that just means they won't bother me in production when the next bugfix release happens
19:16 murrdoc joined #salt
19:18 gordonm_ joined #salt
19:19 subsignal joined #salt
19:19 iggy MTecknology: I'm not going to saltconf
19:20 shoemonkey joined #salt
19:22 Crazy67 joined #salt
19:22 MTecknology iggy: nooooooooo!!!!!
19:24 subsignal joined #salt
19:26 zmalone AndreasLutro: https://github.com/saltstack/salt-pack is supposed to generate identical packages to the ones on repo.saltstack.com, you could probably turn that into a nightly build
19:26 zmalone I didn't have much luck with it though when I tried it
19:27 zmalone I emailed a few people at Saltstack offering to document it if they sent me their internal process for making it work, but that didn't happen
19:27 rmnuvg joined #salt
19:27 digitalhero joined #salt
19:27 AndreasLutro it seems incomplete, but then again I've yet to find a single git repo containing full instructions on how to build a debian package - I left some comments here https://github.com/saltstack/salt/issues/30735
19:27 saltstackbot [#30735]title: Make packaging/build processes for repo.saltstack.com more transparent | Right now, it's completely intransparent to the consumers of `repo.saltstack.com` what's happening with the packaging and builds behind the scenes:...
19:27 zmalone At this point though, there are quite a few "bug fixes" which would break something else, like that cron.present issue I created a week or two back
19:28 zmalone That was what I thought when I used it, plus it is a 500mb repo full of embedded tarballs and stuff
19:28 AndreasLutro haha yeah I "fixed" that initially
19:28 shoemonk_ joined #salt
19:28 zmalone your fix was better then what existed before
19:29 zmalone but fixing it to match the docs would mean we could end up with three cron jobs for one definition over the same 2015.8.x branch of salt
19:29 AndreasLutro oh I dunno
19:29 onovy left #salt
19:30 zmalone I've had a few issues though where I've just orphaned them, working around a  weird behavior is better then coming up with a fix that will break pre-existing stuff.
19:30 zmalone I figure having it documented as an issue will help the next person who hits it though
19:30 hightekvagabond joined #salt
19:31 AndreasLutro I support that
19:32 seblu joined #salt
19:32 Guest36793 joined #salt
19:32 hasues joined #salt
19:32 hasues left #salt
19:32 akhter joined #salt
19:35 babilen AndreasLutro: pm okay?
19:36 AndreasLutro absolutely
19:36 bhosmer joined #salt
19:36 ajw0100 joined #salt
19:37 gordonm_ joined #salt
19:42 akhter joined #salt
19:43 akhter joined #salt
19:43 GreatSnoopy joined #salt
19:46 garphy joined #salt
19:48 winsalt I think file.line is broken in 8.4, does anyone else use this function?
19:48 Guest36793 joined #salt
19:50 zmalone Are you using watch_in?
19:50 zmalone https://github.com/saltstack/salt/issues/30820
19:50 saltstackbot [#30820]title: State runs involving watch_in or extending break on 2015.8.4 | Environment: rackspace, Ubuntu 14.04, salt packages from `http://repo.saltstack.com/apt/ubuntu/14.04/amd64/latest`...
19:50 zmalone 2015.8.5 was just announced today
19:51 winsalt no, this is just for windows.  it works on the linux side, but for windows I get "file.line is not available".  I can find the file.py on the server
19:51 jfindlay windows uses the win_file.py module
19:53 winsalt well i guess thats it.  I see no file function in win_file.py
19:53 jfindlay winsalt: here's an example of something not working because of threading rather than processing: https://github.com/saltstack/salt/issues/14691
19:53 saltstackbot [#14691]title: custom grains disappearing on Windows | On Windows salt-minion does not have the osarch grain so I wrote a custom grain for it, and synced the new grains to the minion...
19:53 winsalt i mean line function
19:59 quasiben joined #salt
20:00 Guest36793 joined #salt
20:01 Tyrm joined #salt
20:01 jardoin so the instructions here: https://docs.saltstack.com/en/develop/topics/releases/releasecandidate.html <--I'm trying to use these to install on OS X, as I was told native support for OS X should be improved. The bootstrap options flat out say Darwin isn't supported, which is kind of ironic, and the tarball asks to remove "salt paths configuration setting" from the install command. Looking at the script, I'm guessing we're discussing t
20:02 Tyrm_ joined #salt
20:03 zmalone jardoin: you were cut off by line limits after "discussing"
20:03 jardoin ah
20:03 jardoin the install class
20:04 jardoin setup.py script
20:04 murrdoc joined #salt
20:04 jardoin or maybe I'm misreading it entirely
20:05 viq joined #salt
20:05 krymzon joined #salt
20:06 fredvd joined #salt
20:07 onlyanegg joined #salt
20:07 berserk joined #salt
20:11 berserk joined #salt
20:11 Guest36793 joined #salt
20:13 akhter_1 joined #salt
20:13 mohae oh, hai edrocks
20:13 edrocks mohae: lol hey
20:13 shoemonkey joined #salt
20:14 edrocks bringing salt and go together :)
20:14 mohae never noticed you in this channel
20:14 edrocks same with you. I've been here for over a year too
20:15 mohae same, but I rarely say anything
20:16 mohae last was a burst of frustration
20:16 mohae I think
20:16 edrocks I lurk to see if anyone is doing cool stuff. my setup has been mostly stable with salt for the past few months
20:17 Tyrm joined #salt
20:17 edrocks I'd like to get better deployment integrated with my load balancer though. but thats a job for another day
20:17 mohae ya, I need to check my salt stuff
20:18 cpowell_ joined #salt
20:19 geomacy joined #salt
20:20 Tyrm_ joined #salt
20:23 rem5 joined #salt
20:24 baweaver joined #salt
20:24 FeatherKing joined #salt
20:26 fxhp https://twitter.com/RussellBal/status/695693929661001728 | how to stand up a new fleet of servers and have them auto provision
20:27 fxhp gave up on salt-cloud
20:28 akhter_1 Anyone here use the Py renderer?
20:28 fxhp Never found a need akhter_1
20:28 fxhp I'd either figure things out with YAML or write my own state/execution modules
20:28 akhter_1 Jinja is cool, I just think it looks a bit ugly.
20:28 akhter_1 I do the same now
20:29 akhter_1 I was hoping a different renderer would help so I wouldn't have to write my own modules.
20:29 catpigger joined #salt
20:30 fxhp You can use other renderer, not sure I would drop down to using python
20:30 fxhp have a look a mako
20:30 bhosmer joined #salt
20:31 fxhp in the end though, less jinja / mako magic they better
20:31 fxhp the*
20:32 hightekvagabond joined #salt
20:34 akhter_1 fxhp: I guess I'll stick to jinja.  By the way, what issues are you having with salt-cloud?
20:35 quasiben joined #salt
20:35 fxhp akhter_1: straight up doesn't work with Joyent anymore
20:36 akhter_1 Ahh, I don't actually use Joyent so I wouldn't be able to help there.
20:36 atmosx joined #salt
20:36 shoemonkey joined #salt
20:36 fxhp I was going to fix the codebase but decided to expand myself outside of how salt does things
20:36 fxhp actually think I have a better solution now.
20:37 akhter_1 What's that?
20:37 fxhp https://github.com/russellballestrini/remarkbox-states/blob/master/sdc/sdc-createmachine-salted
20:37 fxhp https://github.com/russellballestrini/remarkbox-states/blob/master/sdc/bootstrap-salt-minion.sh
20:37 igorwidl joined #salt
20:37 fxhp https://github.com/russellballestrini/remarkbox-states/blob/master/salt-master/auto-accept-minion-keys.sh
20:38 fxhp I just used that auto-accept-minion-keys.sh to unlock the doors on my salt msater
20:38 fxhp then sdc-createmachine-salted to launch 8 nodes (4 different rolls)
20:39 fxhp that script passes bootstrap-salt-minion.sh as a user-script metadata such that the instances come into existance and are automatically provisioned for the particular role
20:39 shoemonk_ joined #salt
20:40 fxhp I'm building my new bootstrapped started in the complete open.
20:40 fxhp started/startup
20:40 fxhp when I launch all the code will likely be opensource
20:42 shoemonkey joined #salt
20:43 Guest36793 joined #salt
20:43 tpaul Is it possible to add custom beacons? Preferably in the same way customer grains can be added...
20:44 tpaul nvm found it in the docs :)
20:52 mapu joined #salt
20:53 karlthane joined #salt
20:53 lazybear joined #salt
20:58 antpa joined #salt
21:00 shoemonkey joined #salt
21:01 jardoin ..so for anybody wondering I pulled 2016.3 from Git and it kind of works.. except for the new SIP stuff put in to El Capitan. Stops modification of some folders that salt wants to modify.
21:03 cliluw joined #salt
21:04 Guest36793 joined #salt
21:06 cliluw joined #salt
21:10 shoemonkey joined #salt
21:10 keimlink joined #salt
21:11 Guest36793 joined #salt
21:15 baweaver joined #salt
21:19 DammitJim joined #salt
21:21 giantlock joined #salt
21:22 andrew_v joined #salt
21:25 bhosmer joined #salt
21:25 Guest36793 joined #salt
21:30 hightekvagabond joined #salt
21:33 FeatherKing joined #salt
21:36 digitalhero joined #salt
21:38 jdubski joined #salt
21:39 jxm_ joined #salt
21:41 aqua^c joined #salt
21:48 murrdoc joined #salt
21:49 joe_n joined #salt
21:54 shaggy_surfer joined #salt
21:59 antpa joined #salt
22:03 beardedeagle joined #salt
22:04 dabb joined #salt
22:11 Guest36793 joined #salt
22:13 Rumbles joined #salt
22:13 akhter joined #salt
22:14 chadhs joined #salt
22:16 hosttor joined #salt
22:19 bhosmer_ joined #salt
22:23 Guest36793 joined #salt
22:24 beardedeagle wth, I like how when I am trying to do non-ssl pywinrm salt-cloud calls it still tries to provision on port 5986.
22:26 nikogonzo69 joined #salt
22:28 rem5 joined #salt
22:34 Guest36793 joined #salt
22:35 teryx510 joined #salt
22:36 dober joined #salt
22:36 dober joined #salt
22:43 zenlot1 joined #salt
23:00 Guest36793 joined #salt
23:02 baweaver joined #salt
23:07 s_kunk joined #salt
23:13 bhosmer_ joined #salt
23:19 joe__n joined #salt
23:20 krymzon joined #salt
23:30 hightekvagabond joined #salt
23:31 antpa joined #salt
23:33 hosttor joined #salt
23:38 oida_ joined #salt
23:39 Guest36793 joined #salt
23:46 krymzon joined #salt
23:48 jtylers joined #salt
23:54 subsignal joined #salt
23:57 Guest36793 joined #salt
23:57 lompik joined #salt

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