Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2015-08-15

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

All times shown according to UTC.

Time Nick Message
00:01 VR-Jack my theory is that if it hasn't processed the states in the 2nd include, it probably hasn't done jinja render either.
00:01 whytewolf VR-Jack: couldn't do a reload_modules in the pkg.installed?
00:01 scoates VR-Jack: you mean like this, right? http://paste.roguecoders.com/p/4b5681f7552095951fc408cab01f01f6.txt
00:01 scoates the jinja is definitely rendered before the aws.vpc.ops states are run
00:01 VR-Jack whytewolf: the error was because salt read in the state and couldn't find the module key
00:02 VR-Jack scoates: yes
00:03 Ryan_Lane scoates: what do you mean when you say cloud stuff? :)
00:03 Ryan_Lane are you using salt-cloud?
00:03 Ryan_Lane or is this some other custom thing?
00:04 VR-Jack looks custom
00:04 scoates using cloud.profile
00:04 Ryan_Lane but not using salt-cloud?
00:04 scoates right
00:04 Ryan_Lane heh. why use cloud.profile rather than just using pillars, then?
00:05 VR-Jack scoates: you could always break them up into separate sls, send an event to reactor and push the second sls.
00:05 VR-Jack presuming you aren't doing orchestrate to start with.
00:06 scoates VR-Jack: I suppose that's possible. Feels like already too many levels of indirection. Hoping to avoid more. /-:
00:06 scoates Ryan_Lane: I don't know. I should probably just stop.
00:07 VR-Jack well, the include trick was my best option.
00:07 duendecat joined #salt
00:08 scoates Ryan_Lane: is there a good example doc for using pillars like you describe? this feels like trailblazing for the most part. keep running into "I can't believe this hasn't happened to everyone else" moments. /-:
00:08 scoates s/describe/mention/
00:08 VR-Jack any reason you aren't using cloud?
00:08 Ryan_Lane scoates: I think most of the heavy users right now are also contributors
00:08 Ryan_Lane cloud is... not very useful in AWS
00:09 VR-Jack ahh
00:09 jeadr joined #salt
00:09 Ryan_Lane the boto_* modules, on the other hand are probably some of the best orchestration code around
00:09 scoates salt-cloud requires a lot of logic glue because of name+id mismatches, from what I can tell
00:09 solidsnack joined #salt
00:09 Ryan_Lane (I wrote most of the boto_* stuff, so I'm a bit biased)
00:10 kuromagi^ joined #salt
00:10 Ryan_Lane scoates: let me find some examples
00:10 murrdoc i need a test.ping retry
00:10 murrdoc test.ping, retry x times
00:10 Ryan_Lane scoates: most of the state modules have examples for pillars, I think
00:10 Ryan_Lane scoates: you're using the state modules, right?
00:10 scoates trying to (-:
00:10 Ryan_Lane cool
00:11 scoates also, I always feel very limited by pillar because you can't refer to pillar
00:11 Ryan_Lane scoates: http://ryandlane.com/blog/2015/01/06/saltstack-automated-cloudwatch-alarm-management-for-aws-resources/
00:11 VR-Jack scoates: actually you can
00:11 VR-Jack 2 ways
00:11 Ryan_Lane what do you mean you can't refer to it?
00:11 VR-Jack Ryan_Lane: self referencing
00:11 VR-Jack pillar in pillar is my guess
00:12 Ryan_Lane oh. it's possible, but I never recommend it
00:12 VR-Jack Well, there's the evil way, which I use
00:12 scoates yeah. and yeah.
00:12 VR-Jack or you can use StackPillar
00:12 scoates too much evil already
00:12 Ryan_Lane I reference grains in pilalrs
00:12 VR-Jack which is a good way
00:12 Ryan_Lane since I'm using masterless, that's fine :)
00:12 Ryan_Lane I also have a custom grain module that turns some environment variables into grains
00:13 Ryan_Lane so that I can use the same grains in my orchestration code and my config management code
00:14 Ryan_Lane scoates: http://ryandlane.com/blog/2015/04/02/saltconf15-sequentially-ordered-execution-in-saltstack-talk-and-slides/
00:14 Ryan_Lane check out the slides
00:14 VR-Jack https://github.com/bbinet/pillarstack
00:14 Ryan_Lane or the talk ;)
00:14 Ryan_Lane scoates: I have examples of how we do things in that
00:15 Ryan_Lane wait
00:15 Ryan_Lane wrong talk
00:15 Ryan_Lane sorry
00:15 Ryan_Lane scoates: this one http://ryandlane.com/blog/2015/04/02/saltconf15-masterless-saltstack-at-scale-talk-and-slides/
00:15 VR-Jack I'm glad you're not the only one that gets lost on your blog, Ryan.
00:15 VR-Jack err, I'm not the only one
00:15 Ryan_Lane :D
00:16 cliluw Does anyone here use Salt Cloud? I'm wondering if I should use Salt Cloud or use Amazon's CloudFormation.
00:16 scoates cool. pillarstack looks much better than the merging hackery I've had to do post-pillar…
00:16 scoates can't possibly rework that in time for the end-of-month deadline, though.
00:20 VR-Jack scoates: yes, and it's now in dev
00:20 scoates cool
00:20 VR-Jack was merged not long ago
00:21 Ryan_Lane scoates: so, in those slides, see slides 17-28
00:21 VR-Jack scoates: you mean this hackery? https://gist.github.com/vr-jack/d53733b554fb15b12bfd
00:22 Ryan_Lane scoates: a lot of the modules have "policies from pillars"
00:22 VR-Jack my first salt bugfix was to fix jinja import in pillar top.sls. lol
00:22 scoates VR-Jack: similar, but I at least had the sense to do it in Python (-;
00:22 Ryan_Lane also, every module has a "profile" argument, which by default takes a pillar key
00:22 scoates yep, I've been using the profile stuff, Ryan_Lane
00:22 Ryan_Lane which lets you setup region, key, keyid, etc
00:23 VR-Jack scoates: I don't know python. lol
00:23 baweaver joined #salt
00:24 VR-Jack I can bug fix, but not write from scratch
00:25 Ryan_Lane scoates: the "from_pillars" things are pretty magical for a lot of the state modules
00:25 scoates http://paste.roguecoders.com/p/30f0c2d44ff8132867d691dbad9e4f1d.txt
00:26 Ryan_Lane for instance, for autoscale groups you can have cloudwatch alarms and scaling policies come from pillars
00:26 Ryan_Lane which have a default pillar key
00:26 scoates I see
00:26 Ryan_Lane so you can define an autoscale group with no info about alarms or scaling policies, but have it have the "default" alarms and policies
00:26 scoates Ryan_Lane: is that specific to the boto states, or does it work everywhere? I haven't run into it before.
00:26 Ryan_Lane so that every ASG in your infra automatically scales by default
00:26 scoates (the attributes_from_pillars stuff)
00:27 Ryan_Lane specific to these states
00:27 * scoates nods
00:27 scoates too bad (-:
00:28 VR-Jack but when you have time, you can steal the code and throw it in others.
00:30 scoates "when I have time" might be the funniest thing I've read today. Thanks! (-;
00:33 VR-Jack To be fair, I don't think pillarstack will be better in my use case
00:35 VR-Jack The whole purpose of my jinja is to read in hgroup hosts files and build node lists to automatically generate top.sls
00:36 VR-Jack basically dynamic nodegroups
00:38 duendecat joined #salt
00:39 claytron_ joined #salt
00:40 scoates because Friday: http://paste.roguecoders.com/p/c60b1d80303df6c29cf5b3b7cc7d384a.txt
00:40 funzo joined #salt
00:45 jgelens joined #salt
00:45 Ryan_Lane scoates: heh. eww
00:45 scoates yep.
00:45 Ryan_Lane yeah, I can see why you want the vpc stuff to be in there correctly
00:46 Ryan_Lane we don't create vpcs often, so it's never been a major issue for us
00:46 scoates I want all of my stuff to be states so I can transport between aws accts.
00:46 scoates ideally. I'll probably fail (-:
00:46 scoates anyway, mixing IDs and names in there is a pain.
00:46 Ryan_Lane I haven't even tried multiple accounts yet
00:47 Ryan_Lane I'm relatively positive multi-region works correctly
00:47 Ryan_Lane I know we need to properly support assuming roles
00:47 Ryan_Lane that's on our agenda at some point
00:47 Ryan_Lane everything works perfectly with IAM roles, though
00:47 scoates oh, I didn't mean concurrently
00:48 scoates just meant changing the profile info from one acct to another
00:48 Ryan_Lane I think being able to assume roles will be needed for managing multiple accounts from one location and one run
00:48 scoates so I can have a true test account
00:48 Ryan_Lane ah. ok
00:48 Ryan_Lane scoates: so... fun fact :)
00:48 Ryan_Lane you don't even need to provide profile into
00:48 scoates uh-oh
00:48 Ryan_Lane info*
00:48 scoates if you use an IAM role, yeah
00:48 edrocks joined #salt
00:48 Ryan_Lane if you're calling this via salt-call and not runing a daemon you can just use boto config
00:49 scoates ah. heh.
00:49 Ryan_Lane when I run on my laptop that's what I do
00:49 Ryan_Lane then I can change profiles via environment vars
00:49 scoates didn't know that, but interesting.
00:49 scoates when this goes to production, we'll be calling the aws provisioning states from the saltmaster directly, and it will have an IAM role
00:49 scoates so no credentials needed
00:50 Ryan_Lane yep
00:50 Ryan_Lane that's the best situation :)
00:50 Ryan_Lane scoates: I really want this for salt master/minion: http://ryandlane.com/blog/2015/06/16/custom-service-to-service-authentication-using-iamkms/
00:51 Ryan_Lane to replace the key system currently in place
00:51 scoates I'll leave that open. Too many TLAs for fridaybrain to understand.
00:51 Ryan_Lane :D
00:52 Ryan_Lane KMS = key management system. it's an encryption service in amazon
00:52 pm90_ joined #salt
00:52 scoates … friday brain can't even seem to figure out how to `cloud.profile` and request a public IP…
00:52 scoates oh, right. I forgot KMS exists. (-:
00:52 Ryan_Lane can do encrypt/decrypt actions and can generate data keys that you can use for things
00:52 Ryan_Lane KMS is one of AWS's best services
00:52 Ryan_Lane no one seems to know about it though :D
00:53 Ryan_Lane it makes my inner security engineer giddy
00:53 * scoates nods
00:53 scoates future-me will be very interested in this (-;
00:54 Ryan_Lane here's a fun thing I haven't published yet, because I didn't do a full proof of concept: https://gist.github.com/ryan-lane/ecf49c1b39f6e6ba2e66
00:55 scoates I'm jealous of your "spare" time to do things like this. (-:
00:56 Ryan_Lane all I do is write tooling. it's wonderful
00:56 VR-Jack *sigh* Somehow I started my own company and I'm still not doing what I want. lol
00:57 scoates I'm theoretically doing what I want… just so tired.
00:58 VR-Jack same. Problem is I like to help people and it wears me out.
00:59 scoates I've found myself really down on software in the last couple months. None of it ever works.
00:59 scoates (including mine)
01:01 scoates Ryan_Lane: am I just missing it, or is there no way to tell subnets to auto-assign public IPs here? https://github.com/saltstack/salt/blob/develop/salt/modules/boto_vpc.py#L747
01:07 VR-Jack lol, reading through salt code has been depressing this month
01:08 hasues joined #salt
01:08 hasues left #salt
01:09 duendecat joined #salt
01:23 claytron_ joined #salt
01:40 duendecat joined #salt
01:40 hvn joined #salt
01:41 funzo joined #salt
01:45 zircote joined #salt
01:47 yomilk joined #salt
02:01 bfoxwell joined #salt
02:10 duendecat joined #salt
02:12 jeadr1 joined #salt
02:20 jeadr joined #salt
02:20 jeadr1 joined #salt
02:29 dthom91 joined #salt
02:32 dthom91 joined #salt
02:32 rabbitheart joined #salt
02:37 pm90_ joined #salt
02:39 fxhp joined #salt
02:41 duendecat joined #salt
02:42 funzo joined #salt
02:43 dthom91 joined #salt
02:45 dthom91 joined #salt
02:48 viq joined #salt
02:48 viq joined #salt
02:58 writtenoff joined #salt
03:00 dthom911 joined #salt
03:09 claytron_ joined #salt
03:12 duendecat joined #salt
03:12 dthom91 joined #salt
03:25 writtenoff joined #salt
03:26 hvn joined #salt
03:30 arthoo joined #salt
03:36 baweaver_ joined #salt
03:43 duendecat joined #salt
03:43 funzo joined #salt
03:45 kukacz joined #salt
03:48 arthoo Hi, I had a question about service.running on Debian.  I have a state that verifies the sshd service is running and it works on RH based systems since its initscript is 'sshd' but in Debian, it's 'ssh'.  Is there a smarter way to determine the proper service name other than checking the distro and doing an if on 'os_family:Debian'?
03:56 jeadr joined #salt
03:56 jeadr1 joined #salt
04:07 pcn arthoo: That's probably the smartest way to do it: KISS
04:08 arthoo pcn: just do the 'if' you mean?
04:08 pcn Yeah
04:08 pm90_ joined #salt
04:09 arthoo ok, sounds good.  just didn't know if there was another, better way that I just wasn't aware of.
04:09 arthoo but thanks!
04:09 pcn Trying to identify the service is full of sharp edges and corners.  If you know what you're targeting, layout the matrix for just that, and only deal with something more complex if you find out that it's a really good match for what you've got.
04:13 duendecat joined #salt
04:14 yomilk joined #salt
04:19 otter768_ joined #salt
04:27 hvn joined #salt
04:30 kuromagi joined #salt
04:31 honestly joined #salt
04:43 funzo joined #salt
04:44 duendecat joined #salt
04:48 stanchan joined #salt
04:48 jalbretsen joined #salt
05:00 markm_ joined #salt
05:06 AndreasLutro joined #salt
05:06 Jahkeup joined #salt
05:08 holyzhou joined #salt
05:08 claytron_ joined #salt
05:12 catpiggest joined #salt
05:14 hardwire joined #salt
05:40 Fiber^ joined #salt
05:42 ITChap joined #salt
05:43 duendecat joined #salt
05:44 funzo joined #salt
05:57 hvn joined #salt
06:14 duendecat joined #salt
06:32 otter768 joined #salt
06:33 claytron_ joined #salt
06:45 duendecat joined #salt
06:45 funzo joined #salt
06:55 pm90_ joined #salt
07:00 otter768 joined #salt
07:13 hvn joined #salt
07:13 hvn joined #salt
07:17 ITChap Hi everyone
07:17 ITChap is there a way to check which minions are currently running a highstate ?
07:26 hvn joined #salt
07:29 edrocks joined #salt
07:29 DanyC joined #salt
07:32 DanyC hi all, i've been going through all Salt doc and got to the modules reference sectino where i'm trying to understand one thing. When the doc says " salt.modules.redismod.info(host=None, port=None, db=None, password=None)" and the example is only a cli which can be run from salt master only "salt '*' redis.info",  can i assume this can be turned into a state ?
07:33 DanyC if yes, can anyone help me with a quick, short example ?
07:33 ITChap you can use the state: module.run
07:33 ITChap to run a module from a state
07:34 ITChap http://docs.saltstack.com/en/latest/ref/states/all/salt.states.module.html#salt.states.module.run
07:35 ITChap if you want to run the module only based on other state changes you need to use module.wait
07:35 ITChap with a watch for example
07:38 claytron_ joined #salt
07:39 ITChap DanyC: is it what you are looking for ?
07:39 DanyC ITChap: cool, that is what i needed it.
07:40 dopesong joined #salt
07:41 jeddi joined #salt
07:42 DanyC ITChap: i started to love more and more Salt but one thing i whish to have. The documentation should be improved asap.... it has tons of stuff in it but the basic things like what i asked is hard to get your head around. wouldn't have been easier if at the start of each module will be a link/ note saying "shoudl you wish to run it from a state/ formula do this - with a minor example"
07:42 yomilk joined #salt
07:43 ITChap yeah I discover stuff in the doc all the time that I missed and would have made my life easier :D
07:43 ITChap but in the end I spend most of my time in the 2 following pages:
07:43 ITChap http://docs.saltstack.com/en/latest/ref/states/all/
07:43 ITChap http://docs.saltstack.com/en/latest/salt-modindex.html
07:44 ITChap This one is pretty useful too http://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html
07:45 funzo joined #salt
07:46 ITChap There is so much stuff around Salt that a page with what each part is doing would be great
07:46 babilen DanyC: Generally speaking: States are implemented on top of modules and essentially add the logic/tests for deciding if a state has been achieved already and what must be done to achieve it. The state module typically just calls functions in the corresponding execution module.
07:46 DanyC ITChap: indeed those links are the best BUT before that people (those how just get started with Salt) need to understand how to use it the documentation, needs basic convetion and maping from modules to states, formula to states (like the link you provided)
07:48 DanyC ITChap: fully agree. And i know from SaltConf 15 that they might make improvments in doc layout but guess what... only for the Enterprise version
07:49 DanyC babilen: great, i get that one but wouldn't be simplier if what you said will be  someone in the Get starting wiht Salt doc and wiht minor example which will be always referenced from each module page section - like a note ?
07:50 babilen Yeah a short "modules are $FOO, states are $BAR and they relate like $BAR" with a good and simple example would be great
07:51 DanyC babilen: happy to go via documentation as long as i have known tips to go around and find the stuff. Is like man pages, always stay on it but then right at the end of each man pages says - check x,y,z
07:51 babilen It is actually *really* easy if you think about it, but it is not well explained in the docs and the documentation that is there is *way* too detailed and specific to make this relation obvious.
07:52 babilen Salt is in the unfortunate position to both have too little and too much documentation. More links and restructuring would be great ...
07:54 DanyC babilen: you got it!!!  if i can make an analogy i'd say: Salt is like a big posh dish but i don't know how to start eating it nor i have fork ... just 1 stick
07:56 DanyC babilen: do you know whom from Corporation might be on this channel so i can ping him/ her Monday on this topic ? i understand things are getting improved on Enterprise but then if the Corporation wants to gain more popularity the Doc is a must asap
07:57 DanyC babilen: and it must be on Community side first otherwise they can't attract more people and their business model won't get more cash flow ...simple equation :)
07:59 DanyC Ansible is all over the place on OpenStack, docker etc etc, they even have Comunity VPS ... so we from Salt side need to do more on that ...my £ 0.02
08:00 zhoujl joined #salt
08:00 zhoujl hello
08:00 zhoujl when i use salt.client.ssh.client.SSHClient
08:01 zhoujl how can i change the roster file
08:01 zhoujl just like salt-ssh '*' test.ping --roster-file='xxx'
08:01 hvn joined #salt
08:06 agj joined #salt
08:09 zhoujl help
08:11 babilen DanyC: No, i don't really know who to contact, but UtahDave or basepi might be a good candidates
08:12 duendecat joined #salt
08:12 DanyC babilen: thanks, will nundge them on Monday. Have a great weekend ..
08:13 DanyC *nudge
08:18 zhoujl ok . thanks
08:29 mschiff joined #salt
08:41 CeBe joined #salt
08:41 evle1 joined #salt
08:42 duendecat joined #salt
08:45 cb_ joined #salt
08:46 funzo joined #salt
08:56 pm90_ joined #salt
09:02 otter768 joined #salt
09:03 claytron_ joined #salt
09:05 X67r joined #salt
09:21 Fiber^ joined #salt
09:37 ijamgroot joined #salt
09:38 ijamgroot How can I get thh current os family by running salt-call --local ?
09:39 ijamgroot (Or any other way)
09:41 Mate grains.get os_family
09:41 duendecat joined #salt
09:47 ijamgroot Thanks! I'm trying to override it by setting it in /etc/salt/grains but it doesn't seem to work, is it possible to override somehow?
09:47 funzo joined #salt
09:48 Mate why would you override it?
09:49 ijamgroot it lists my family as antiX but I want to set it to Debian
09:49 ijamgroot so I don't have to add extra conditions in the map files
09:49 claytron_ joined #salt
09:51 AndreasLutro ijamgroot: you should open an issue or PR to add that os to the list that's included in the debian os family
09:51 AndreasLutro https://github.com/saltstack/salt/blob/develop/salt/grains/core.py#L935-L939
09:59 CeBe joined #salt
10:01 ijamgroot Thanks, will do :)
10:04 pjs joined #salt
10:05 dopesong joined #salt
10:13 linjan_ joined #salt
10:24 daemonkeeper joined #salt
10:27 pm90_ joined #salt
10:33 jeadr joined #salt
10:33 jeadr1 joined #salt
10:35 claytron_ joined #salt
10:40 linjan_ joined #salt
10:42 ijamgroot left #salt
10:44 hvn joined #salt
10:48 funzo joined #salt
10:58 duendecat joined #salt
10:59 jespada joined #salt
11:03 otter768 joined #salt
11:48 AndreasLutro joined #salt
11:49 funzo joined #salt
11:51 duendecat joined #salt
12:12 markm joined #salt
12:17 claytron_ joined #salt
12:25 SheetiS joined #salt
12:26 duendecat joined #salt
12:36 dthom91 joined #salt
12:38 dijit hey guys, I'm trying to have different "paths" for different OS's
12:39 dijit the way I _think_ I should do this is having a pillar for each OS (linux/BSD) and setting the path there.
12:39 dijit but can I match "not freebsd" in the topfile
12:39 dijit I suppose I can, but I'm scared to test.
12:39 dijit I guess it would be like:
12:40 dijit "not G@os:FreeBSD"
12:43 duendecat joined #salt
12:49 AndreasLutro dijit: not necessarily - look at how some of these setups use map.jinja https://github.com/saltstack-formulas
12:50 funzo joined #salt
12:52 arthoo joined #salt
12:54 dthom91 joined #salt
12:56 quasiben joined #salt
13:03 dijit hm
13:03 dijit god that looks complex.
13:04 otter768 joined #salt
13:04 claytron_ joined #salt
13:06 AndreasLutro dijit: as complex as you need it to be
13:07 dijit yeah
13:07 dijit someone had the fantastic idea of supporting debian as well as freebsd.
13:07 dijit so now I need to figure out how to integrate it in the cleanest way
13:32 duendecat joined #salt
13:35 dthom91 joined #salt
13:38 dthom91 joined #salt
13:43 pm90_ joined #salt
13:45 favadi joined #salt
13:47 claytron_ joined #salt
13:50 funzo joined #salt
14:20 ranomore The compound matcher doc page says you can't do a not match at the beginning of the matcher, so instead you do '* and not G@os:FreeBSD'
14:25 edrocks joined #salt
14:30 quasiben joined #salt
14:32 edrocks joined #salt
14:38 duendecat joined #salt
14:46 dijit ranomore: thanks
14:46 dijit I didn't know that.
14:50 favadi joined #salt
14:51 funzo joined #salt
14:53 claytron_ joined #salt
15:05 otter768 joined #salt
15:05 crabmartian joined #salt
15:09 duendecat joined #salt
15:39 claytron_ joined #salt
15:40 duendecat joined #salt
15:44 pm90_ joined #salt
15:52 funzo joined #salt
15:58 favadi joined #salt
16:00 malinoff joined #salt
16:00 pm90_ joined #salt
16:06 pfallenop joined #salt
16:11 duendecat joined #salt
16:24 revjim joined #salt
16:25 revjim I'm really new to salt and I'm having what is probably a really simple problem that I just can't figure out.
16:25 revjim No matching sls found for 'nginx.deploy' in env 'base'
16:25 revjim [DEBUG   ] Could not find file from saltenv 'base', u'salt://nginx/deploy.sls'
16:25 revjim but I have /srv/salt/nginx/deploy.sls in place.
16:26 otter768 joined #salt
16:27 scoates joined #salt
16:30 revjim this is my deploy.sls https://gist.github.com/dlashua/49084b3ea14a34e81c5b
16:31 bfoxwell joined #salt
16:36 rideh joined #salt
16:41 duendecat joined #salt
16:43 claytron_ joined #salt
16:44 sunkist joined #salt
16:44 dthom91 joined #salt
16:53 funzo joined #salt
16:55 jeadr joined #salt
16:56 jeadr1 joined #salt
17:02 ajw0100 joined #salt
17:22 revjim joined #salt
17:23 revjim having an issue matching grains in the pillar. it seems pretty straightforward, but it isn't working.
17:29 scoates I don't suppose any of you happen to have a cloud.profile[s] config that does something similar to this (binds a public IP address to an AWS instance in a subnet that doesn't auto-assign) ? http://paste.roguecoders.com/p/d6baaa5e00c6972f913e03ccc14394af.txt
17:30 Ryan_Lane joined #salt
17:42 riftman joined #salt
17:49 claytron_ joined #salt
17:49 gladiatr joined #salt
17:53 funzo joined #salt
17:55 DjDeaf joined #salt
17:56 jeadr joined #salt
17:56 jeadr1 joined #salt
17:59 Nazca joined #salt
18:01 DjDeaf joined #salt
18:38 TyrfingMjolnir joined #salt
18:54 funzo joined #salt
18:54 otter768 joined #salt
18:57 scoates where does it look for this `script`? https://github.com/saltstack/salt/blob/fd70187176bca85b6afd73e8086b5cb56404b9bf/doc/topics/cloud/deploy.rst#deploy-script-arguments
19:00 duendecat joined #salt
19:08 riftman joined #salt
19:09 claytron_ joined #salt
19:09 dopesong joined #salt
19:18 jeadr joined #salt
19:22 dijit hey guys, I think I found a bug/inconsistency
19:22 dijit localhost and host do different things on different platforms.
19:22 dijit localhost is fqdn on freebsd but the "short" hostname on debian
19:23 dijit host is fqdn on debian but "short" hostname on freebsd
19:23 dijit (grains, this is).
19:24 dijit actually, on debian "host" returns no value.
19:24 AndreasLutro odd, host and localhost are the short names on my debian
19:24 dijit https://pastebin.com/C8d7mgYH
19:25 dijit ah!
19:25 dijit you're right
19:25 dijit one of my deb machines works as expected.
19:26 AndreasLutro https://github.com/saltstack/salt/blob/2015.8/salt/grains/core.py#L1376-L1394
19:30 tedski joined #salt
19:30 dijit nice
19:31 dijit yeah, this looks the same on my target machine
19:31 dijit weird.
19:33 duendecat joined #salt
19:34 scoates FWIW, I found my earlier answer: /etc/salt/cloud.deploy.d/
19:44 boargod2 joined #salt
19:55 funzo joined #salt
19:55 subsignal joined #salt
19:58 murrdoc joined #salt
19:59 murrdoc how tough is a salt retry state
19:59 murrdoc we need a retry flag in all states
20:04 jvv joined #salt
20:10 dopesong joined #salt
20:13 claytron_ joined #salt
20:19 jeadr joined #salt
20:23 bhosmer joined #salt
20:34 cheus joined #salt
20:36 darix joined #salt
20:46 bhosmer_ joined #salt
20:46 bhosmer joined #salt
20:55 funzo joined #salt
20:56 claytron_ joined #salt
20:56 midacts joined #salt
20:56 midacts anyone else had this issue on Debian Jessie?  'Failed to start salt.service: Unit salt.service failed to load: No such file or directory.'
21:04 otter768 joined #salt
21:21 kukacz joined #salt
21:30 quasiben joined #salt
21:35 jeadr joined #salt
21:36 subsignal joined #salt
21:39 claytron_ joined #salt
21:45 roock joined #salt
21:47 markm joined #salt
21:54 duendecat joined #salt
21:56 funzo joined #salt
22:05 kaiyou joined #salt
22:08 dopesong joined #salt
22:13 dopesong_ joined #salt
22:18 dijit midacts: nope, mine has the unit file in the right place.
22:18 dijit /lib/systemd/system/salt-minion.service
22:24 duendecat joined #salt
22:43 markm joined #salt
22:54 jngd joined #salt
22:55 duendecat joined #salt
22:57 funzo joined #salt
23:01 jeadr joined #salt
23:04 dthorman joined #salt
23:08 SubOracle joined #salt
23:16 evilrob joined #salt
23:20 SubOracle joined #salt
23:23 markm joined #salt
23:25 claytron_ joined #salt
23:51 saltnooby joined #salt
23:52 saltnooby hi
23:52 dijit hello
23:52 saltnooby is there a way to also pass in pillar data in a remote (minion) file, similar to http://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.state.html#salt.modules.state.template ?
23:53 dijit remote minion? not sure what that means.
23:53 dijit but you can pull it in via jinja.
23:53 dijit https://github.com/darkscience/ds-salt/blob/master/states/inspircd/inspircd/inspircd.conf
23:53 dijit https://github.com/darkscience/ds-salt/blob/master/states/inspircd/inspircd/inspircd.conf
23:53 saltnooby see the link, from the master I'm able to execute a state sls file on the minion
23:54 dijit line4
23:54 dijit yeah
23:54 saltnooby just wondering if I can do this and also read a remote pillar file?
23:54 dijit I doubt it, sounds very unorthogonal
23:54 saltnooby it's so I can version control web projects along with state files and hopefully pillar data
23:55 saltnooby so I can allow development team to edit the state files (which would be a git submodule) that get's pulled in on their project, sub project so I can approve merge requests
23:57 saltnooby want to make it like formula's, have main conf's like apache and php templated with sane defaults, but overridable with pillar data
23:58 funzo joined #salt

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