Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-07-18

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

All times shown according to UTC.

Time Nick Message
00:12 TheoSLC joined #salt
00:18 rpburkholder joined #salt
00:18 nixjdm_ joined #salt
00:27 rebbdohr joined #salt
00:31 om2_ joined #salt
00:38 debian112 joined #salt
00:38 manji joined #salt
00:59 sh123124213 joined #salt
01:00 onlyanegg joined #salt
01:07 jeffspeff joined #salt
01:18 nixjdm_ joined #salt
01:27 miruoy joined #salt
01:50 beardedeagle joined #salt
01:59 felskrone joined #salt
02:06 m0nky_ joined #salt
02:06 nahkiss_ joined #salt
02:06 shanesveller_ joined #salt
02:06 djinni`_ joined #salt
02:07 supermike__ joined #salt
02:07 guerby_ joined #salt
02:07 futuredale_ joined #salt
02:07 Nightcinder_ joined #salt
02:08 dragon788_ joined #salt
02:08 djural_ joined #salt
02:08 wonko21_ joined #salt
02:08 Laogeodritt| joined #salt
02:09 Hipikat_ joined #salt
02:09 MasterNayru joined #salt
02:09 mugsie_ joined #salt
02:11 Armadill0 joined #salt
02:11 k1ltzman joined #salt
02:11 zerocoolback joined #salt
02:11 Hipikat_ left #salt
02:12 druonysus__ joined #salt
02:12 Hipikat joined #salt
02:12 ropes_ joined #salt
02:12 v12aml_ joined #salt
02:12 elkektetet joined #salt
02:12 druonysuse joined #salt
02:12 druonysuse joined #salt
02:14 armyriad joined #salt
02:14 Vaelater1 joined #salt
02:14 wendall911 joined #salt
02:14 evle joined #salt
02:14 feliks joined #salt
02:15 magnuss joined #salt
02:15 kshlm joined #salt
02:15 Ryan_Lane joined #salt
02:15 edrocks joined #salt
02:16 TRManderson joined #salt
02:17 tellendil joined #salt
02:18 benjiale[m] joined #salt
02:18 nixjdm_ joined #salt
02:18 twiedenbein joined #salt
02:18 ekkelett joined #salt
02:18 DoomPatrol joined #salt
02:19 nledez joined #salt
02:19 nledez joined #salt
02:19 alexlist joined #salt
02:21 DammitJim joined #salt
02:23 tellendil joined #salt
02:43 gmacon joined #salt
02:43 emid joined #salt
02:46 felskrone joined #salt
02:51 evle2 joined #salt
02:55 iggy joined #salt
02:58 gtmanfred joined #salt
02:59 asoc joined #salt
02:59 gadams joined #salt
02:59 druonysus joined #salt
02:59 whiteinge joined #salt
02:59 whiteinge joined #salt
03:00 guerby__ joined #salt
03:03 justanotheruser joined #salt
03:03 druonysuse joined #salt
03:03 druonysuse joined #salt
03:06 emid joined #salt
03:08 andrei joined #salt
03:08 justanotheruser joined #salt
03:08 jab416171 joined #salt
03:13 donmichelangelo joined #salt
03:16 sh123124213 joined #salt
03:18 nixjdm_ joined #salt
03:27 TheoSLC joined #salt
03:33 justan0theruser joined #salt
03:37 justan0theruser joined #salt
03:37 onlyanegg joined #salt
03:38 om2_ joined #salt
03:42 high_fiver joined #salt
04:02 sh123124213 joined #salt
04:04 alkyl joined #salt
04:07 _JZ_ joined #salt
04:17 edrocks joined #salt
04:18 nixjdm_ joined #salt
04:19 Ni3mm4nd joined #salt
04:20 mavhq joined #salt
04:38 kerrick_ joined #salt
04:40 swills joined #salt
04:40 swills joined #salt
04:41 swills joined #salt
04:41 swills joined #salt
04:50 mavhq joined #salt
04:53 onlyanegg joined #salt
05:03 kerrick_ joined #salt
05:04 preludedrew joined #salt
05:06 vishvendra joined #salt
05:07 swills joined #salt
05:09 noraatepernos joined #salt
05:16 Bock joined #salt
05:18 nixjdm_ joined #salt
05:21 v3x joined #salt
05:24 mbuf joined #salt
05:33 guerby__ joined #salt
05:37 Armadill0 left #salt
05:37 Armadillo joined #salt
05:37 fritz09 joined #salt
05:44 sh123124213 joined #salt
05:45 ahrs joined #salt
05:51 vishvendra1 joined #salt
05:57 vishvendra joined #salt
05:57 pualj joined #salt
05:58 _KaszpiR_ joined #salt
06:14 aldevar joined #salt
06:18 nixjdm_ joined #salt
06:20 xet7 joined #salt
06:25 vishvendra1 joined #salt
06:27 impi joined #salt
06:30 vishvendra1 joined #salt
06:34 vishvendra1 joined #salt
06:39 vishvendra1 joined #salt
06:41 onlyanegg joined #salt
06:47 syst0m joined #salt
07:03 do3meli joined #salt
07:03 do3meli left #salt
07:14 mbrgm joined #salt
07:15 mbrgm hey! what is the common approach to separate a salt master (inside an internal network) from minions in a DMZ? can this be setup so only the master needs to initiate connections? or do the minions have to be able to connect to the master?
07:17 whytewolf the minions need to be able to connect to "a" master. you could setup a master that lives in the dmz that connects back to the main master.
07:17 whytewolf using syndic
07:18 nixjdm_ joined #salt
07:18 whytewolf or, you could just go masterrless
07:19 mbrgm whytewolf: you said 'connect _back_' to the main master. this would then again be a connection from DMZ->INTERNAL. is it possible the other way around? and: can syndic be configured to only sync part of the pillar data?
07:20 whytewolf no. it is not possable the other way around. minions connect to masters. and syndic masters connect to main masters. as for pillar. split your pillar data up. so that it can.
07:21 whytewolf use multiple repos and git_pillar
07:22 patrek_ joined #salt
07:23 whytewolf there is a work around. a way to go ther other way. but it is a little more ... of a pain sometimes. useing salt-ssh the master creates an ssh connection to the minion and runs scripts on it then disconnects
07:24 mbrgm ok, ty very much!
07:31 Ricardo1000 joined #salt
07:33 vishvendra joined #salt
07:43 Rumbles joined #salt
07:50 mikecmpbll joined #salt
07:50 mavhq joined #salt
07:59 pbandark joined #salt
08:02 miruoy joined #salt
08:07 usernkey1 joined #salt
08:14 vishvendra1 joined #salt
08:18 nixjdm_ joined #salt
08:22 felskrone joined #salt
08:23 miruoy joined #salt
08:34 zerocoolback joined #salt
08:38 Mattch joined #salt
08:38 coredumb For those that don't backlog, I'd be happy if anyone would be willing to beta test my pillar/master_tops module https://github.com/saltstack/salt/pull/42349 let me know if you test it :)
08:39 XenophonF joined #salt
08:42 onlyanegg joined #salt
08:42 zerocoolback joined #salt
08:44 Bernard__ joined #salt
08:44 zerocool_ joined #salt
08:45 impi joined #salt
08:46 k1412 joined #salt
08:47 k1412 Hello everyone, I'm a little stuck. I try to find a method to replace a bock of text with another. I thought about file.blockreplace first but it look that it not replace the text that already exist/
08:47 joe_n joined #salt
08:54 xet7 joined #salt
08:55 rebbdohr joined #salt
09:06 vishvendra joined #salt
09:09 zulutango joined #salt
09:18 nixjdm_ joined #salt
09:19 Naresh joined #salt
09:30 arif-ali joined #salt
09:32 zerocoolback joined #salt
09:33 zerocool_ joined #salt
09:37 noraatepernos joined #salt
09:37 joe_n joined #salt
09:38 zerocoolback joined #salt
09:42 zerocool_ joined #salt
09:47 coredumb joined #salt
09:48 Rumbles k1412 file.replace should be able to do that
09:48 Rumbles https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.replace
09:49 k1412 Rumbles: Thanks, I find that out after multiple try for the regex, is there a reason that blockreplace don't have an option to replace the block directly ?
09:50 c06 joined #salt
09:52 Rumbles I believe that's the point, blockreplace is designed so you can leave some text intact, replace isn't designed to do that
09:54 lorengordon joined #salt
09:54 k1412 Ok, it's because when I saw the name I thought directly about replace a complete block ^^, but thanks I have found a way with replace
10:02 Heartsbane joined #salt
10:03 sturla joined #salt
10:14 eightyeight joined #salt
10:15 Ricardo1000 joined #salt
10:16 Ricardo1000 joined #salt
10:16 sturla joined #salt
10:17 nixjdm_ joined #salt
10:20 mavhq joined #salt
10:23 N-Mi_ joined #salt
10:23 edrocks joined #salt
10:29 sturlik joined #salt
10:30 sturlik Can someone help with problem. Created custom salt state which invoke file state by __salt__. But invocation aren't showing in low_state and can't use require on file state invocation. Is there posibility to add invocation to low state?
10:30 sturlik So other states can depend on invocations? For ex. state invokes file.manage and would like to depend file.directory on file.manage
10:31 joe_n joined #salt
10:36 cyteen_ joined #salt
10:39 joe_n joined #salt
10:39 Rumbles sturlik, I find your question difficult to understand, I think you need to look at the require documentation, or perhaps onlyif
10:41 Rumbles or perhaps onchanges: https://docs.saltstack.com/en/latest/ref/states/requisites.html#onchanges
10:41 smartalek joined #salt
10:42 smartalek joined #salt
10:42 onlyanegg joined #salt
10:42 mbuf Can Salt do what Bosh can do for cloud foundary?
10:43 smartalek joined #salt
10:43 Rumbles want to give specific examples?
10:45 sturlik Rumbles, thanks for info! But unfortunately on changes wouldn't help as I have many invocation of custom state
10:45 sturlik In detail I would like to do following custom state prepare content and invokes file.manage
10:46 sturlik and then file.directory requires all file.manage and cleanup of old files not managed by salt
10:50 sturlik But unfortunately can do this, because when passing list of file to require argument of file.directory with 'clean: True' checks if they present in low state
10:52 sturlik and falls with error:
10:52 sturlik File "/usr/lib/python2.7/dist-packages/salt/states/file.py", line 404, in _gen_keep_files
10:52 sturlik if low['name'] == comp['file'] or low['__id__'] == comp['file']:
10:53 Rumbles I'm sturggling to udnerstand what your issue is, sorry
10:59 sturlik Will try rephrasing I invoking from my custom state python __states__['file.managed']
11:00 sturlik And then would like to invoke __states__['file.directory'] with args clean=True and require=files, where files are list of list create by __states__['file.managed']
11:00 Rumbles can you just pastebin the state files?
11:01 sturlik Yes, here https://pastebin.com/BxUe03cu
11:02 mbuf Terraform and SaltStack are a good combination, I guess
11:02 Rumbles that's not your state file sturlik
11:04 sturlik sorry seams that I'm not correct in phrase it's custom state module
11:04 Rumbles custom module
11:04 Rumbles a state is a salt config file (.sls) that stores the configuration that may then call modules
11:05 Rumbles :)
11:07 sturlik thanks for pointing
11:08 wonko21 joined #salt
11:10 vishvendra joined #salt
11:10 Rumbles np, I'm not an expert either, but it's easier to ask for help if you use the right terminology :)
11:10 wonko21 joined #salt
11:14 wonko21 joined #salt
11:15 wonko21 joined #salt
11:15 vishvendra1 joined #salt
11:18 nixjdm_ joined #salt
11:20 muep left #salt
11:25 felskrone joined #salt
11:33 c06 joined #salt
11:38 thinkt4nk joined #salt
11:45 vishvendra1 joined #salt
11:45 stduolc can I use state file with #!py header and use it like a python extend module?
11:45 stduolc now I have some code in sls
11:47 kyuuri joined #salt
11:50 stduolc and it works, but the return value is not available. I delve into the source code of salt. the code like this "https://github.com/saltstack/salt/blob/develop/salt/utils/templates.py#L482". who can I return the data to the master?
11:52 CrummyGummy joined #salt
11:53 skorpy2009 joined #salt
11:56 zerocool_ joined #salt
12:00 swills joined #salt
12:00 dev_tea joined #salt
12:03 ecdhe joined #salt
12:07 jessexoc joined #salt
12:12 dev_tea joined #salt
12:13 syst0m joined #salt
12:17 nixjdm_ joined #salt
12:29 Rumbles joined #salt
12:31 DammitJim joined #salt
12:38 DammitJim joined #salt
12:38 high_fiver joined #salt
12:38 syst0m yesterday I asked about crating a reactor that would activate if a log file hasn't been changed in the last 1h. was thinking of adding the if condition in the beacon, so that it would send to the event bus, only if the mtime hasn't been changed, not sure exactly how to do it, after studying the docs
12:38 syst0m found this on writing beacon plugins:
12:38 syst0m https://docs.saltstack.com/en/latest/topics/beacons/#writing-beacon-plugins
12:38 syst0m anyone have experience with this?
12:43 onlyanegg joined #salt
12:43 syst0m not sure if a better place for the if condition would be on the beacon
12:44 cgiroua joined #salt
12:48 DammitJim1 joined #salt
12:56 edrocks joined #salt
13:07 numkem joined #salt
13:07 permalac joined #salt
13:07 joe_n joined #salt
13:08 jdipierro joined #salt
13:14 DammitJim1 joined #salt
13:16 ssplatt joined #salt
13:17 nixjdm_ joined #salt
13:19 smartalek joined #salt
13:21 losh joined #salt
13:22 ashmckenzie joined #salt
13:23 wiggy joined #salt
13:24 wiggy anyone know what might be wrong of "salt-call state.highstate" aborts with "Passed invalid arguments: expected string or buffer" ?
13:25 smartalek joined #salt
13:25 wiggy master and minion are both running 2016.11.4
13:29 smartalek wiggy: are you looking for general info on writing beacons?
13:30 wiggy smartalek: no
13:30 wiggy I'm trying to figure out why state.highstate broke
13:30 noobiedubie joined #salt
13:30 wiggy on a system that shouldn't have changed in many months
13:33 syst0m smartalek: I was inquiring about beacons. I am not sure if in this particular use-case it would make more sense to write a custom beacon plugin or create a reactor that fires up a runner with a python renderer that would have the if conditional statement
13:34 jdipierro joined #salt
13:38 wiggy chunk['name'] = None
13:38 wiggy which makes check_requisites blow up
13:39 tobstone joined #salt
13:40 sturlik joined #salt
13:41 mikecmpb_ joined #salt
13:43 smartalek wiggy: my bad, had your question confused with syst0m
13:44 racooper joined #salt
13:44 onlyanegg joined #salt
13:44 salt-noob joined #salt
13:48 smartalek syst0m: I'd prob put it in the beacon and append to the tag when you do/don't detect the change you're looking for. In this way you can create a flag for a reactor to look for.
13:49 zerocool_ joined #salt
13:56 defswork joined #salt
13:57 zerocoolback joined #salt
14:02 _JZ_ joined #salt
14:10 tobstone i managed restarting some minions one after another if reboot-required, https://gitlab.dwbn.org/snippets/42 and https://gitlab.dwbn.org/snippets/43, would be nice if this wont fail if one of the minions is not required to start and skip the wait for start event.
14:10 gmoro_ joined #salt
14:11 gmoro_ joined #salt
14:18 cyborg-one joined #salt
14:18 nixjdm_ joined #salt
14:18 gmoro_ joined #salt
14:19 Teemo joined #salt
14:19 Ricardo1000 joined #salt
14:21 xet7 joined #salt
14:26 sarcasticadmin joined #salt
14:27 Ricardo1000 joined #salt
14:29 Ni3mm4nd joined #salt
14:30 high_fiver joined #salt
14:32 mbrgm left #salt
14:33 mikecmpbll joined #salt
14:39 lakewoodweb joined #salt
14:49 ecdhe_ joined #salt
14:49 DammitJim joined #salt
14:50 donmichelangelo joined #salt
14:51 thinkt4nk joined #salt
14:52 fatal_exception joined #salt
14:54 lompik joined #salt
14:58 fritz09 joined #salt
15:00 onlyanegg joined #salt
15:01 noobiedubie i'm running salt-cloud on centos 7 using the latest repo and I started getting these error messages when I try to launch a new instance. remote: okTraceback (most recent call last):
15:03 bowhunter joined #salt
15:04 Ricardo1000 joined #salt
15:04 noobiedubie https://paste.debian.net/977065
15:05 noobiedubie can i just remove the 0rc2 portion it's complaining about
15:06 lordcirth_work noobiedubie, as always, check that master and minion are the same version
15:06 lordcirth_work 0rc2 looks like the end of a version number
15:07 zerocoolback joined #salt
15:07 lordcirth_work I don't know why it's trying to read it as an int
15:07 noobiedubie it is but there is only a master in this case right minion hasn't even been created never mind launched yet
15:07 noobiedubie using git to launch a new ec2 instance
15:08 Teemo left #salt
15:08 noobiedubie system was working before i guess i just hadn't ran it since last upgrade till now didn't know if anyone else ran into this
15:12 syst0m joined #salt
15:14 tgog joined #salt
15:17 tgog_ joined #salt
15:17 nixjdm_ joined #salt
15:19 tgog_ hi
15:19 tgog_ has anyone encountered this before:
15:19 tgog_ 2017-07-18 15:10:01,427 [salt.pillar      ][CRITICAL][127876] Specified ext_pillar interface consul is unavailable
15:21 noobiedubie where is the version located in salt-cloud?
15:24 mikecmpbll joined #salt
15:24 ecdhe joined #salt
15:24 ecdhe joined #salt
15:25 dfinn joined #salt
15:27 fatal_exception joined #salt
15:29 noobiedubie I can't even find where it's parsing 0rc2 from
15:35 thinkt4n_ joined #salt
15:35 lakewoodweb joined #salt
15:37 lakewoodweb joined #salt
15:43 zerocoolback joined #salt
15:44 onlyanegg joined #salt
15:46 high_fiver joined #salt
15:48 devoper joined #salt
15:50 devoper Hey Peoples, awesome job at OpenWest
15:51 devoper I have a jenkins server that has some binaries that need to be transfered to the salt server, but I can't use SSH, I was looking at the salt-api, but it appears that it can't handle file uploads. Is there another module I could look at?
15:52 noobiedubie so turned out to be outdated pip package that it was complaining about pip install -U fixed it
15:54 vishvendra joined #salt
15:56 woodtablet joined #salt
16:03 mpanetta joined #salt
16:03 ahrs joined #salt
16:06 zerocool_ joined #salt
16:10 tgog_ any ideas :
16:10 tgog_ 2017-07-18 16:06:47,662 [salt.pillar      ][CRITICAL][78577] Pillar render error: Failed to load ext_pillar consul: incomplete format
16:17 nixjdm_ joined #salt
16:20 debian112 joined #salt
16:22 beardedeagle joined #salt
16:23 noobiedubie spaces or back syntax check for hidden characters if nothing looks obvious
16:29 TheoSLC joined #salt
16:29 andrei joined #salt
16:39 ASalted joined #salt
16:46 censorshipwreck joined #salt
16:46 AvengerMoJo joined #salt
16:47 leonkatz joined #salt
16:48 leonkatz Any one getting this error Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) from salt cloud
16:48 TheoSLC joined #salt
16:49 wendall911 joined #salt
16:56 vishvendra joined #salt
16:56 impi joined #salt
16:59 onlyanegg joined #salt
17:02 dendazen joined #salt
17:12 leonkatz W: GPG error: https://repo.saltstack.com/apt/ubuntu/16.04/amd64/latest xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E08A149DE57BFBE looks like that is cause the lock
17:12 leonkatz *causing
17:14 AvengerMoJo joined #salt
17:14 ahrs joined #salt
17:18 nixjdm_ joined #salt
17:20 ChubYann joined #salt
17:22 wangofett joined #salt
17:25 zerocoolback joined #salt
17:26 zerocoolback joined #salt
17:26 kerrick joined #salt
17:27 Inveracity joined #salt
17:29 devoper joined #salt
17:43 edrocks joined #salt
17:45 high_fiver joined #salt
17:46 leonkatz In case anyone runs into this, it looks like dpkg locks in the salt-cloud logs the work around is to add the gpg key to the aws ami and use that ami
17:46 leonkatz wget http://repo.saltstack.com/apt/ubuntu/16.04/amd64/latest/SALTSTACK-GPG-KEY.pub
17:46 leonkatz sudo apt-key add SALTSTACK-GPG-KEY.pub
17:54 mugsie_ left #salt
17:54 mugsie joined #salt
17:54 DoomPatrol hrm could have sworn there was a openstack salt formula or something "official" for openstack & salt
17:55 DoomPatrol founnd it
17:56 btorch is this something new as of 2016.11.3 ? while calling "sudo salt -l warning  --state-output=changes 'data1*' state.highstate test=true" I get back a bunch of stuff like "Result: Clean Started: - 17:53:42.265667 Duration: 0.674 ms"
17:56 btorch I have two clusters with the same salt versions and this only actually happens on one of the clusters , everything isthe same version and config log levels
18:03 deep-book-gk_ joined #salt
18:03 deep-book-gk_ left #salt
18:03 cyborg-one joined #salt
18:12 major joined #salt
18:14 nixjdm joined #salt
18:16 Trauma joined #salt
18:19 druonysuse joined #salt
18:19 druonysus joined #salt
18:19 druonysuse joined #salt
18:35 ecdhe joined #salt
18:38 noraatepernos joined #salt
18:42 lahdekorpi joined #salt
18:44 woodtablet joined #salt
18:47 watersoul joined #salt
18:47 lahdekorpi Any suggestions on running a node.js as a service with salt? What process manager to use (pm2, strongloop, etc) if any and how to start / configure them?
18:49 lahdekorpi I've currently just hacked pm2 to start, dump and save it's state and then use a service state to start the process manager, and that doesn't seem very practical or clean...
18:49 astronouth7303 salt is pretty agnostic about it. Although saltstack does have modules for supervisord
18:50 astronouth7303 just tell salt to spit out the necessary config files and then poke at the init system when needed
18:51 GMAzrael joined #salt
18:54 lahdekorpi having a module for some node process manager directly would be pretty neat, and using a process manager in itself is nice to be able to handle the clustering, etc
18:55 lahdekorpi but I guess why fix something that ain't broken, I'll just keep using what I have :)
18:58 astronouth7303 of course. I'm using supervisord but not the supervisord states.
18:59 eykd joined #salt
19:01 astronouth7303 (i do use the supervisord execution module, though, from time to time)
19:09 MTecknology nooo! let supervisord die!!
19:10 MTecknology actually, it's passenger that I strongly dislike, but supervisord is up there.
19:10 astronouth7303 AWS's elastic beanstalk (python) uses it, and I've been successful with it in the past
19:14 kerrick joined #salt
19:14 MTecknology %quit
19:15 XenophonF joined #salt
19:15 XenophonF left #salt
19:16 Renich joined #salt
19:19 nixjdm joined #salt
19:23 astronouth7303 i'm fairly tempted to use salt as the data-gathering layer for some monitoring system. Since I already have a scatter/gather infrastructure set up and installed on all my infra.
19:25 major isn't that how salt sort of started?
19:26 astronouth7303 i always assumed it started as a command execution layer, and then someone figured out you could define a state command on top of that, but i'm too new to know the actual history.
19:26 swills joined #salt
19:26 aldevar joined #salt
19:27 major I believe it started as a data collection/monitoring solution combined with remote command execution.  The configuration management sort of emerged from those components.
19:27 astronouth7303 i'm not aware of any monitoring/alerting packages that support a salt backend, though
19:27 spiette joined #salt
19:28 major agreed
19:28 major though I can't fathom why not
19:29 major well .. SaltEnterprise effectively acts as a monitoring solution
19:29 astronouth7303 all the major ones use their own agents, because a dependency like salt would be too much to swallow?
19:29 astronouth7303 oh, that might be it
19:29 ecdhe joined #salt
19:29 ecdhe joined #salt
19:29 major honestly, I suspect you could use the salt engine to make a transparent agent for something like Zabbix to reach into data collected by salt
19:29 nixjdm_ joined #salt
19:30 astronouth7303 yeah; I was looking at prometheus earlier today (because gitlab), and I'm pretty sure it'd be easy to proxy the data across
19:30 major or maybe store everything into consul and then use a monitoring solution that watches consul
19:31 major which might be a more robust solution in the end
19:31 ecdhe joined #salt
19:31 astronouth7303 i'm honestly a devops newbie. Last time I did this, I was on AWS so it was CloudWatch all the way.
19:32 eykd left #salt
19:33 ecdhe joined #salt
19:34 astronouth7303 if there was something that combined the collection, storage, and interface into a single package (especially if it also did logs), i would be extremely interested.
19:34 kerrick joined #salt
19:34 smartalek joined #salt
19:34 major https://www.datadoghq.com/blog/monitor-consul-health-and-performance-with-datadog/
19:34 major consul is basically a fault tolerant HA distributed key=value database which spans the network (and optionally data centers)
19:34 ecdhe joined #salt
19:35 major you can basically use it for storing any data and then querying that data from anywhere else
19:35 major and .. salt plays well with consul
19:36 major so you can store random data in consul (including pillar data) and you can develop custom scripts and such which query the system and do various health checks that also end up in consul
19:36 major https://docs.saltstack.com/en/latest/ref/pillar/all/salt.pillar.consul_pillar.html
19:37 drawsmcgraw joined #salt
19:37 astronouth7303 that seems like a pretty big, complex thing for my needs right now
19:37 astronouth7303 and honestly, i'm not sure we'll ever scale that large
19:38 karlthane joined #salt
19:38 major I dunno if it is that "large" so much is that it can be made to go that route
19:38 astronouth7303 large == requiring large, complex systems for "simple" stuff
19:38 tgog joined #salt
19:39 major consul has a few interesting "tricks" it can do though .. like .. if you use a consul agent to be the parent of a process tree (like .. init for example) .. then the agent can automatically register all the ports/services/resources that all its children are consuming and report them to the network w/out any special configs
19:39 major a particularly neat feature for spinning up containers and automatically monitoring them on the network
19:40 astronouth7303 yeah.... we're not on containers
19:41 major and .. for me at least .. consul is lighter weight than say .. an sql database
19:41 major which is kinda funny in a cry cry kinda way
19:41 astronouth7303 idk, i already know SQL and i got postgres setup and configured (through salt, even) in about a day and a half
19:42 astronouth7303 and even if i have a place the data sits in, i'd still need a tool to do something useful with it, wouldn't i?
19:43 major consul's query interface uses the DNS protocol
19:43 tgog joined #salt
19:43 major and is slightly less complicated to settup than bind
19:43 astronouth7303 querying for service discovery
19:43 astronouth7303 (which i'm just using salt mine for)
19:44 major soo .. anything with the 'host' command, or 'dig' or 'nslookup' can query consul
19:44 major or any resolver library really
19:44 astronouth7303 i'm looking at monitoring and metrics and alerts
19:45 astronouth7303 (although yes, monitoring -> health checks -> good SD)
19:45 tgog joined #salt
19:45 major right, and any data can be stored in consul as a key=value pair
19:45 major someone just up and realized that you can store any data into DNS .. not just "services"
19:45 major consul is generally built around that idea I guess
19:45 astronouth7303 sounds like a poor fit for time-series
19:46 major https://conferences.oreilly.com/velocity/devops-web-performance-2015/public/schedule/detail/40306
19:46 tgog so like
19:46 major I dunno .. it seems to be the new norm
19:46 tgog when using consul as an external pillar
19:46 karlthane joined #salt
19:46 tgog if there's ever a state where consul is not up and running, salt will just fail to run any states whatsover
19:46 major tgog, interesting
19:46 tgog is there a way to disable that behaviour or is that not something that can be changed
19:47 tgog it'll just fail to render the pillar and quit
19:47 major like .. no consul servers are available anywhere on the network?
19:47 astronouth7303 well, apparently you could just run a DNS caching resolver in front of consul
19:47 tgog well I think the external pillar renders seperately on each node for whatever reason
19:48 tgog actually that's a good point i'll test that
19:49 astronouth7303 the right solution is probably to set up a consul cluster, though
19:49 astronouth7303 ok, the right solution is probably both
19:54 noraatepernos joined #salt
19:54 sturlik joined #salt
19:56 leonkatz joined #salt
19:56 ecdhe joined #salt
20:01 MTecknology joined #salt
20:02 druonysus__ joined #salt
20:02 druonysus joined #salt
20:14 eykd joined #salt
20:19 edrocks joined #salt
20:19 eykd joined #salt
20:29 nixjdm_ joined #salt
20:33 aldevar left #salt
20:34 aldevar joined #salt
20:36 whytewolf wtf.
20:36 whytewolf 2017.7.0 just showed up on my laptop
20:37 whytewolf didn't know it was that close. skipping extra rc's this time?
20:37 kerrick joined #salt
20:38 astronouth7303 apparently one was enough
20:38 astronouth7303 i told you, they already tagged it in git
20:38 astronouth7303 i'm just waiting for the official announcement
20:39 whytewolf ...
20:39 * whytewolf waits for the roll in of issues this release is going to cause
20:41 stomith Help! I can't do the needful!
20:41 stomith ^
20:42 druonysuse joined #salt
20:42 druonysuse joined #salt
20:42 drawsmcgraw left #salt
20:42 druonysus__ joined #salt
20:43 druonysus__ joined #salt
20:45 Ni3mm4nd joined #salt
20:50 astronouth7303 ... why doesn't the salt blog discuss new versions? that seems like one of the most important, basic things for a software company?
20:52 zie joined #salt
20:54 whytewolf you actually read the saltstack blog?
20:54 gmoro joined #salt
20:54 major they have a blog?
20:54 onlyanegg joined #salt
20:55 whytewolf yeah. https://saltstack.com/blog/ though no one i know reads it
20:55 major bah .. the channel failed
20:55 major really .. the next question should have been "what's a blog?"
20:55 astronouth7303 no, i don'
20:55 astronouth7303 t
20:56 astronouth7303 i do read the gitlab blog, because that actually talks about versions and security notices and new features
20:56 astronouth7303 (ie, stuff i actually care about as a user)
20:56 major whats the blogs latency vs the channel?
20:57 Trauma joined #salt
20:57 major oh .. gitlab blog
20:57 major my bad
20:57 whytewolf the blogs last post was about saltconf17 ... so i would say really bad latency
20:57 major ...
20:58 whytewolf mostly they just do posts about employees
20:58 xet7 joined #salt
20:58 major ...
20:58 astronouth7303 compare https://saltstack.com/blog/ to https://about.gitlab.com/blog/
20:58 major employees?
20:58 whytewolf i would rather not as a blog is the last place i go for any kind of info ever
20:59 astronouth7303 i like it because RSS feed
21:00 whytewolf rss feeds. so 2010 of you
21:00 whytewolf as i watch my mail lists ....
21:00 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.11.6, 2017.7.0 <+> Support: https://www.saltstack.com/support/ <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ <+> See also: #salt-devel, #salt-offtopic <+> We are volunteers and may not have immediate answers <+> The call for speakers for SaltConf17 is now open: http://tinyurl.com/SaltConf17
21:00 astronouth7303 is the salt announce list better?
21:00 gtmanfred i am better than mailing lists :P
21:00 major ++
21:01 major there is a certain irony in that my systems where all running 2017.7.0 before the topic was changed...
21:01 major s/where/were/
21:01 astronouth7303 is 2017.7.0 actually out?
21:01 gtmanfred yes
21:01 Trauma joined #salt
21:01 major salt-ssh --version
21:01 major salt-ssh 2017.7.0 (Nitrogen)
21:01 gtmanfred i am about to go to the gym, but assuming all the downloads tests pass
21:02 gtmanfred salt-announce should have an announcement within the hour
21:02 astronouth7303 ok
21:02 lorengordon hey, and it _is_ july, nice! :p
21:02 gtmanfred but i will be at the gym, plus i have been working since 5am today, so i am all done an can go drive my new car
21:02 upb mainly been reading comp.internet.services.management.salt
21:02 gtmanfred lorengordon: second one in a row that has been released in the version month
21:02 gtmanfred 2016.11 was released in november
21:02 lorengordon woot!
21:05 gtmanfred py3 packages will be released later
21:05 preludedrew joined #salt
21:05 whytewolf so, are we going to get a second major release before the end of the year? seems to be cutting it close this year
21:05 gtmanfred that is a good question, to which i do not have an answer
21:05 astronouth7303 oh! There is a salt-announce feed! https://groups.google.com/forum/#!aboutgroup/salt-announce
21:05 gtmanfred I have a bunch of work to do on the oxygen release still, for features that have to get in
21:06 gtmanfred https://groups.google.com/forum/#!forum/salt-announce
21:06 whytewolf astronouth7303: yes, it is a google group so it would have an rss feed. as well as a mailing list
21:06 gtmanfred maybe in 6 months I will have time to hang out on irc again :/
21:06 whytewolf :(
21:07 whytewolf well see you at saltconf?
21:07 major is there a particular order in the periodic table you guys are following?
21:07 gtmanfred atomic number
21:07 gtmanfred left to right, the usual way that it is ordered?
21:07 major ...
21:08 major bummer ..
21:08 astronouth7303 as opposed to...?
21:08 major left-step perodic table
21:08 major like .. the one that actually makes sense :(
21:09 astronouth7303 the elements would still have the same order
21:09 whytewolf the janet form?
21:09 major well .. when using the atomic number yes
21:09 major whytewolf, correct
21:10 * gtmanfred can't wait until we get to Uuu release
21:10 major heh
21:10 major whytewolf, was hoping someone would actually order stuff based on orbital filling
21:10 major which makes more sense to me
21:11 astronouth7303 gtmanfred: bad news, it's Roentgenium (Rg) now
21:11 gtmanfred those bastards
21:13 whytewolf was 2004 that was decided. little late to put in changes
21:14 major never to late to build a time machine and fix it ;)
21:14 major ...
21:14 major damn .. software bugs are an emperical proof that time travel doesn't exist :(
21:14 whytewolf I just don't understand the gravity of time travel
21:15 v3x is the "cloud" client not available in salt-api?
21:15 gtmanfred it is
21:15 gtmanfred just not available as a client
21:15 v3x and if not, how am I supposed to access salt-cloud functions from the API, assuming I don't want to hard-code the salt-master's ID into it?
21:15 gtmanfred you have to use the cloud runner or cloud module
21:15 astronouth7303 v3x: the cloud runner? it is, but it's a runner module
21:15 gtmanfred use the cloud runner to build profiles
21:16 gtmanfred salt cloud is still somewhat of an afterthought in salt, I have plans of fixing this.
21:16 astronouth7303 iirc, there's local (minion), runner, and wheels
21:16 astronouth7303 gtmanfred: oooo
21:16 gtmanfred also caller
21:16 gtmanfred i think it can do caller client
21:16 gtmanfred maybe not
21:16 gtmanfred astronouth7303: https://groups.google.com/forum/#!forum/salt-cloud
21:16 v3x Yeah, but then I have to target the master, which means I have to write the master's ID into the calls before hand rather than allowing salt to pass arguments directly to the master by default
21:16 gtmanfred that will be picked up again soon
21:16 gtmanfred v3x: you do not have to target the master with the runner
21:16 whytewolf v3x: if you use the runner that happens on the master.
21:16 gtmanfred the runner runs on the master
21:17 * astronouth7303 goes to lurk
21:17 v3x i'm not familiar with what salt-cloud functions are available in "salt-run" ...
21:17 gtmanfred https://docs.saltstack.com/en/latest/ref/runners/all/salt.runners.cloud.html
21:17 major whytewolf, that was good...
21:17 major whytewolf, just sayin..
21:17 v3x ok, thx
21:17 gtmanfred ok, i am headed to the gym
21:17 gtmanfred o/
21:17 whytewolf major: thanks, I try
21:18 astronouth7303 execution modules run on minions. state modules are run by state.apply. runner/wheel modules are run by the runner/wheel clients
21:18 whytewolf gtmanfred: have fun storming the gym
21:18 astronouth7303 note that "run on the master" is distinct from "run by the minion you just happened to install on the master"
21:19 major totally made me go back and revisit gravity time dilation
21:19 astronouth7303 so for example, to create a new instance through the pepper library would be `pepper --client runner cloud.profile ....`
21:20 v3x so... if I pass " client = runner / fun = cloud.full_query " through salt-api, it just gives me an empty json array
21:21 Mogget joined #salt
21:21 astronouth7303 you've configured providers and profiles, right?
21:22 Mogget joined #salt
21:22 v3x yes. salt-cloud -Q (and everything else) works fine from CLI
21:22 v3x i have profiles, maps, providers, etc etc
21:22 sp0097 joined #salt
21:23 v3x ho ho nevermind
21:23 v3x i was pointing it at the wrong master. ignore me.
21:23 v3x thanks
21:24 Trauma joined #salt
21:28 Rumbles joined #salt
21:29 Trauma joined #salt
21:30 nixjdm_ joined #salt
21:35 kerrick joined #salt
21:46 astronouth7303 ... why isn't there a salt time series/alerting tool? Like, "store the results of these executions against these minions" and "execute these orchestration/fire these events under these conditions"
21:48 astronouth7303 oh! https://speakerdeck.com/ipmb/monitoring-infrastructure-with-saltstack
22:10 edrocks joined #salt
22:22 ssplatt joined #salt
22:30 nixjdm_ joined #salt
22:41 kerrick joined #salt
22:43 ssplatt joined #salt
22:44 leonkatz joined #salt
22:47 om2 joined #salt
22:47 Edgan astronouth7303: salt reactors are fire on events
22:48 Edgan astronouth7303: something like foreman can store the results of executions, with the salt plugin
22:50 major I am going to come clean .. I toggled to this window and read "salt reactors" and for a second my brain thought there was a discussion regarding sodium-cooled nuclear reactors...
22:51 Edgan major: haha
22:51 nethershaw joined #salt
22:51 Edgan major: Part of reactors is called thorium, they knew what they were doing.
22:51 leonkatz joined #salt
23:09 deuscapturus joined #salt
23:11 edrocks joined #salt
23:22 major the Saltfile makes me cry
23:27 dendazen joined #salt
23:29 Edgan major: salt-ssh?
23:30 nixjdm_ joined #salt
23:30 Edgan major: The only thing I don't like about it is extra-refs, and I have something on my TODO list for that
23:31 major I am failing to stop salt-ssh's attempts to role its own identity files and just use whatever I have configured in .ssh/config
23:33 Edgan major: you can set that in the master or per host in the roster
23:35 major at times I wish the Saltfile was ALSO the roster file and I just had a stack of "defaults" at the top and a stack of per-host configs below that
23:35 major okay .. pretty muhc all the time
23:35 Edgan major: examples, https://paste.fedoraproject.org/paste/K03WjwxFTGYo-W-iNEe~kg
23:36 Edgan major: The only time I have to touch the Saltfile is when I add a new map.jinja
23:36 Edgan major: or if I want to play with ssh_wipe: True or not
23:37 Edgan major: I keep want Saltfile, and symlink it into multiple directories with separate roster files
23:38 Edgan I mean keep one
23:38 major I have 1 ~/.salt/Saltfile that works for everything I do
23:38 major or .. seems to
23:38 Edgan major: I keep Saltfile in formula/_ssh
23:39 Edgan major: and I put rosters in things like formulas/_ssh_dev
23:39 major yah .. I have other developers using the same tree and they override their own stuff via their own personal Saltfile
23:39 major and they have their own dev saltmasters .. and minions .. and test targets .. and clusters .. and stuff
23:39 major and whiskey for the end of the day
23:40 Edgan Their own rosters makes sense, but they shouldn't really need their own Saltfile if you are all working on the same Salt code over time
23:40 major so I supply a sort of generic bootstrapping environment and all, and examples for how to get their own private thing configured
23:40 major well .. they have their own repos, keys, etc
23:41 major its torture
23:41 major they even get to choose which editor they want to use.. wtf
23:41 * major sighs.
23:41 Edgan major: sumblime, vim, atom, etc?
23:41 major even emacs
23:41 * major whimpers.
23:41 Edgan major: what does it matter?
23:42 major it doesn't
23:42 major mostly joking while I try to work through all this
23:42 major well .. half joking
23:43 major the thing that is nice is that ~/.salt/Saltfile is now something looked for by default, so no special CLI or settings or any of that
23:43 Edgan major: own repos, as in own formula/pillar repos?
23:43 major their own forks of the production repo, their changes come back up to production via Pull Requests
23:44 major good ol triangular workflows
23:44 Edgan major: . is also looked for by default, so I just require you to be in the right directory, where your roster will also be
23:44 Edgan major: They could just be branches that become pull requests, no need for separate repos
23:45 major ...
23:45 major that would get ugly real fast
23:45 major 500 branches in GitHub Enterprise on 1 repo..
23:45 major no thanks
23:45 Edgan major: Are these branches long lived?
23:45 major some of them
23:45 Edgan I think 500 git repo is a bigger shit show
23:46 Edgan how many developers?
23:46 major ...
23:46 major on this floor?
23:46 Edgan using salt-ssh
23:47 major well .. that would be mostly this floor .. and maybe a few other sites..
23:47 Edgan major: Are they using salt-ssh for deploys of applications?
23:47 major you could say that..
23:47 major deploying their own salt masters for controlling their own clusters of systems for testing production code
23:47 major and or for deploying QA infrastructures
23:48 Edgan major: Have you written a template for different language based service types, and created standardization? nodejs? java? ruby? python? etc?
23:48 major I think we have over 20,000 VM's at 1 site
23:48 major well .. that 1 QA group spins up that many for their testing
23:48 Edgan major: If it is just testing, do you really even need salt masters?
23:49 major that is just testing...
23:49 major there is also infrastructure
23:49 major and the some
23:49 major and dev
23:50 Edgan I previously used salt masters for infrastructure and production. I tested in dev with salt-ssh.
23:50 major well .. dev does their own testing, and qa does their own testing
23:50 major and infrastructure tries to keep it all from falling apart
23:50 major and sometimes we just spin up stuff in order to try to reproduce stuff on the customer side
23:50 Edgan I also used salt-ssh for deploys in all environments
23:51 Edgan I would also bootstrap a new account with salt-ssh
23:51 major and yah .. for the developes .. they may not actively need much more than salt-ssh for the majority of stuff .. but I know of a handful who will end up doing their own salt-masters with entire infrastructures attached to that
23:53 major histerically^H^H^H^H^H^H^H^H^H^H^H^Hhistorically they used puppet, there has been a sort of recent decision to start doing future work in salt, as well as eventually migrate all the past infrastructure off puppet onto salt
23:54 Edgan major: My current employer, till tomorrow, is also going from puppet to salt. They are recreating how they did puppet in salt :\
23:54 major that said .. many of them haven't .. they need their starting point custom made for them, but to be capable of being whatever they want to mold it into while still being able to push non-destructive changes up to the central repo
23:54 major Edgan, fun
23:55 major we can swap horror stories ;)
23:55 Edgan major: how about three puppet hiera git repositories that get "merged" together?
23:55 major ...
23:55 major how about no
23:56 Edgan major: haha
23:56 major thats just not right
23:56 Edgan major: and each puppet module is it's own git repo
23:56 Edgan major: Which I know is fairly common, but gets out of hand
23:57 major note: this pastebin would have been just a weeeee more legible if the filename had been prefixed w/ a # or something .. my eyes keep reading them as yaml stanza's :(
23:57 kerrick joined #salt
23:57 Edgan major: The first foo: of each section is the filename, but I will do # next time :)
23:58 major but can only tell the sections based on the 2 newlines...
23:58 major I am slightly confused ..
23:59 Edgan major: ?
23:59 major how do you disable the whole key creation?
23:59 Edgan key creation?
23:59 major just want salt-ssh to stop trying to role its own
23:59 major every time I run it it tries to create new keys, even prompts to overwrite the existing key files
23:59 major wonder what it is looking for
23:59 Edgan Never had that problem
23:59 Edgan What version of salt?

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