Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-11-30

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

All times shown according to UTC.

Time Nick Message
00:11 TK_ joined #salt
00:16 pppingme joined #salt
00:19 viq joined #salt
00:23 TyrfingMjolnir joined #salt
00:25 viq joined #salt
00:42 CoolCold joined #salt
00:45 ananda left #salt
00:49 ingwaem joined #salt
00:49 glyf joined #salt
00:56 markm__ joined #salt
00:56 atbell joined #salt
00:58 CoolCold left #salt
01:02 TK_ joined #salt
01:02 atbell joined #salt
01:04 bahadir joined #salt
01:06 atbell joined #salt
01:12 otter768 joined #salt
01:16 diegows joined #salt
01:19 bhosmer joined #salt
01:22 TK_ joined #salt
01:42 markm_ joined #salt
01:45 wolfpackmars2 joined #salt
01:47 wolfpackmars2 when setting up a salt minion that acts as a git server, what are some recommended actions to take.  Obviously, the git server and its dependencies need to be installed.  Where I get fuzzy though is how to manage the git repos.  Should these be defined in the SLS files ?
01:49 TK_ joined #salt
01:59 bhosmer joined #salt
02:01 TK_ joined #salt
02:04 atbell joined #salt
02:14 markm_ joined #salt
02:14 ingwaem joined #salt
02:30 TK_ joined #salt
02:34 markm_ joined #salt
02:39 TK_ joined #salt
02:50 hintss joined #salt
02:53 TK_ joined #salt
02:58 markm_ joined #salt
02:59 tristianc joined #salt
03:00 mpanetta joined #salt
03:02 beado_ joined #salt
03:04 TK_ joined #salt
03:13 kormoc joined #salt
03:13 otter768 joined #salt
03:14 TK_ joined #salt
03:32 markm_ joined #salt
03:32 ecdhe joined #salt
04:10 marv__ joined #salt
04:13 wolfpackmars2 how would you create a git repo on a managed git remote server
04:13 wolfpackmars2 using state files
04:23 aqua^mac joined #salt
04:26 otter768 joined #salt
04:32 hunmonk_ joined #salt
04:35 tkharju joined #salt
05:01 mpanetta joined #salt
05:10 gildegoma joined #salt
05:12 chayak joined #salt
05:14 g3cko I'm having issues with network.traceroute on a brand new clean install, on a new debian vps
05:14 g3cko Traceback at : https://p.6core.net/p/OBqcMAtogTs2XiBSeSgsq3Rk
05:15 g3cko traceroute works on the system itself
05:15 TK_ joined #salt
05:25 g3cko ignore that, rebooted the system and its working now...
05:25 g3cko ahh wtf, no its back, same traceback
05:25 g3cko it worked once tho
05:31 jalbretsen joined #salt
05:37 TK_ joined #salt
05:57 TK_ joined #salt
05:59 TK___ joined #salt
06:00 markm_ joined #salt
06:02 g3cko so it seems I'm only having this problem on vultr debian VPS's, it popped up on a second system
06:05 aparsons joined #salt
06:07 catpigger joined #salt
06:08 nethershaw joined #salt
06:11 aparsons joined #salt
06:11 TK_ joined #salt
06:19 tristianc joined #salt
06:25 stooj joined #salt
06:30 TK_ joined #salt
06:57 linjan joined #salt
07:02 TK_ joined #salt
07:02 mpanetta joined #salt
07:07 Mso150_p_l_w joined #salt
07:12 monkey66 joined #salt
07:31 genediazjr joined #salt
07:38 jasonrm joined #salt
07:43 TK_ joined #salt
07:45 saravanans joined #salt
08:02 Ryan_Lane joined #salt
08:02 mpanetta joined #salt
08:11 TK_ joined #salt
08:20 genediazjr joined #salt
08:24 oyvjel joined #salt
08:26 hintss joined #salt
08:37 saravanans joined #salt
08:37 drxg joined #salt
08:46 JlRd joined #salt
09:03 dRiN joined #salt
09:10 glyf joined #salt
09:11 TK_ joined #salt
09:23 Nazca__ joined #salt
09:24 aqua^mac joined #salt
09:24 Roee joined #salt
09:24 Roee Hi all !
09:25 Roee Have a problem when running this : salt['pillar.get']('rsp:source', 'test')
09:25 Roee it takes only the test var...]
09:26 Roee how can i fix the formula to work without the default var
09:26 Roee like this : salt['pillar.get']('rsp:source')
09:27 Roee but the above isn't working
09:30 genediazjr joined #salt
09:31 NaPs joined #salt
09:32 otter768 joined #salt
10:09 linjan joined #salt
10:11 TK_ joined #salt
10:13 aqua^mac joined #salt
10:14 glyf joined #salt
10:32 mayak joined #salt
10:32 mayak left #salt
10:35 linjan joined #salt
10:41 ckao joined #salt
11:11 TK_ joined #salt
11:13 TyrfingMjolnir joined #salt
11:14 saravanans joined #salt
11:19 TyrfingMjolnir joined #salt
11:28 jamesog joined #salt
11:33 otter768 joined #salt
11:34 jamesog What's the difference between using grains['foo'] and salt['grains.get']('foo')? I think I've seen both in the examples, and we have both in our state files but it doesn't seem clear when to use which
11:42 saravanans joined #salt
11:42 bhosmer joined #salt
11:44 linjan joined #salt
11:46 saravanans joined #salt
11:58 agend joined #salt
12:03 jasonrm joined #salt
12:04 jasonrm joined #salt
12:10 sarlalia1 joined #salt
12:11 TK_ joined #salt
12:19 agend joined #salt
12:25 jasonrm joined #salt
12:38 mpanetta joined #salt
12:39 cads joined #salt
12:45 JlRd joined #salt
12:51 cads joined #salt
12:55 cads joined #salt
13:03 bhosmer joined #salt
13:07 saravanans joined #salt
13:11 TK_ joined #salt
13:21 Jimlad joined #salt
13:23 TheThing joined #salt
13:34 otter768 joined #salt
13:35 cads joined #salt
13:39 mpanetta joined #salt
13:46 elfixit joined #salt
13:56 sarlalia1 joined #salt
13:56 Roee joined #salt
13:57 Roee Hi all,
13:58 Roee I would like to start targeting my master
13:58 Roee can someone explain me what is the best practice to to so
13:58 Roee e.g. the top file - I know that I need to use 2 top files
13:59 CeBe joined #salt
13:59 Roee (one for states, and one in general per each env' - base,prod, staging
14:00 viq Roee: actually it's less confusing to use a single top file. And, uhm, a minion is a minion is a minion, doesn't matter whether it's running on same machine as master or not
14:01 viq You need to have two top files, but not the way you think: one for states, one for pillars
14:01 Roee sorry you are right...
14:01 Roee states and pillars
14:01 Roee so... every file roots have it's own top files ?
14:02 viq can, but they all get merged, so it's less confusing to have a single one
14:04 Roee this is my file roots dir : https://gist.github.com/roeera/07121bd2cb0a76bd4913
14:04 karimb joined #salt
14:05 Roee and let's say that i would like to completelty separate each of my env's
14:06 genediazjr joined #salt
14:08 viq define "completely separate"
14:08 Roee that each env' (or file root) will have it's own top files... and states
14:09 viq Why subdirs in there? You can reference subdirs in states easily
14:09 viq top files will get merged
14:09 Roee what do you mean get merged ?
14:10 Roee the subdirs are not true ?
14:10 Roee I would like a folder of states
14:10 Roee per each env'
14:11 Roee fix me if i'm wrong... what is the best way to arrange everything ?
14:11 linjan joined #salt
14:11 TheThing joined #salt
14:11 TK_ joined #salt
14:18 viq Roee: https://pbot.rmdir.de/OLWdAXXsDaIhEvf1UtouZQ would give you same result, I would say
14:20 Roee yes this is the basic config
14:20 Roee i know
14:20 Roee but if you could maybe send the base tree
14:20 Roee that maybe could help
14:20 Roee how to arrange the top states and pillars files
14:21 viq Roee: i mean having there /srv/salt/staging/services doesn't give you much if you already have /srv/salt/staging
14:21 Roee per each file root
14:21 Roee ok leave the services
14:21 Roee but states ?
14:21 viq same thing
14:22 oyvjel1 joined #salt
14:23 viq say you have /srv/salt/staging/states/mysql.sls. With file_roots of /srv/salt/staging you simply refer to it as states.mysql
14:23 fxhp joined #salt
14:24 viq So I don't see any advantage to it
14:26 viq Roee: one example I have is https://github.com/viq/cm-lab-salt/tree/master/salt/roots
14:28 Roee trying to understand this
14:29 viq Roee: maybe you could show some example of how you envision it. Some example states and top files
14:30 Roee i will try to explain... i have 2 env' (Prod and Staging)
14:31 Roee each env' have built from few servers per customer
14:32 Roee lets say that i have a customer called "nokia" , so nokia has it's staging and prod env's that each env' is built from few servers that holds different components
14:32 hcl2 joined #salt
14:32 Roee then i built different states to install each component
14:33 viq Can you mock up some state tree for that, to have a clear image and something to refer to?
14:34 Roee Now after i have all of the states i would like to start to arrange salt master by our env'.. (prod/staging/ customer/ servers/ components
14:34 tkharju joined #salt
14:40 gadams999 joined #salt
14:46 aqua^mac joined #salt
14:50 hcl2 joined #salt
15:11 TK_ joined #salt
15:21 davet joined #salt
15:27 cjohn_ joined #salt
15:27 intellix joined #salt
15:31 cjohn joined #salt
15:35 otter768 joined #salt
15:35 oarmstrong joined #salt
15:37 oarmstrong Using salt-cloud to create a master (with `make_master: True` in map) and a few minions.  All the minions are configured to connect to the master using it's public IP, I was wondering if I can get it to configure it with the private IP instead?  Using DigitalOcean provider and the standard salt-bootstrap script with no args currenty.
15:47 viq joined #salt
15:52 monkey66 left #salt
16:00 Hazelesque joined #salt
16:11 TK_ joined #salt
16:21 jasonrm joined #salt
16:28 atbell joined #salt
16:34 dude051 joined #salt
16:36 mordonez joined #salt
16:38 jasonrm joined #salt
16:42 CatPlusPlus joined #salt
16:44 jasonrm joined #salt
16:46 saravanans joined #salt
16:52 jasonrm joined #salt
17:00 linjan joined #salt
17:00 ggoZ joined #salt
17:08 genediazjr joined #salt
17:10 mpanetta joined #salt
17:11 TK_ joined #salt
17:17 zlhgo joined #salt
17:18 xenoxaos joined #salt
17:25 zlhgo joined #salt
17:29 saravanans joined #salt
17:32 TK_ joined #salt
17:36 otter768 joined #salt
17:44 NaPs joined #salt
17:46 TheThing joined #salt
18:11 TK_ joined #salt
18:15 bfoxwell joined #salt
18:25 bmonty joined #salt
18:27 TheThing_ joined #salt
18:28 cjohn joined #salt
18:35 saravanans joined #salt
18:43 NaPs joined #salt
18:43 Mso150 joined #salt
19:07 anotherZero joined #salt
19:11 mpanetta joined #salt
19:11 TK_ joined #salt
19:21 Ryan_Lane joined #salt
19:24 Mso150_s joined #salt
19:33 rubenb joined #salt
19:36 NaPs joined #salt
19:36 otter768 joined #salt
19:43 jeffg_ joined #salt
19:57 homelinen left #salt
20:11 TK_ joined #salt
20:27 Ryan_Lane joined #salt
20:29 bluenemo joined #salt
20:31 bluenemo I'm a bit puzzled by grains with jinja. I have a pillar file containing:  local: {{ salt['grains.get']('ip_interfaces:eth0')[0] }}  when I do  salt 'util*' pillar.get openvpn-server:server-conf:local  I get the resolved hostname for the ip. When I use it in a state to template a file it writes the ip address correctly.
20:32 saravanans joined #salt
20:32 bluenemo example: http://paste.debian.net/134342/
20:33 bluenemo are ips resolved automatically in the output of   salt '*' grains.items ?
20:34 ello_govna joined #salt
20:36 eliasp bluenemo: no, grains are not typed… they just return any plaintext they're provided with
20:36 bluenemo hm. then I'm very puzzled by the behaviour in my pastebin. do you have any idea what might cause that?
20:37 bluenemo when using the grain in the pillar file, the method pillar.get returnes a resolved fqdn. but if I use just that pillar to template a file, it works out just as expected and places the ip.
20:37 TheThing joined #salt
20:38 bluenemo ah sry, eliasp
20:43 Mso150_s joined #salt
20:45 TheThing_ joined #salt
21:05 Mso150_s joined #salt
21:06 bhosmer joined #salt
21:09 manytrees hi, what's the recommended way to manage firewall rules on centos7?  disable firewalld and use the iptables module?
21:11 TK_ joined #salt
21:12 mpanetta joined #salt
21:15 jp_ joined #salt
21:16 n8n joined #salt
21:17 beado_ joined #salt
21:18 snuffeluffegus joined #salt
21:24 tkharju joined #salt
21:34 gildegoma joined #salt
21:37 otter768 joined #salt
21:37 jp_ joined #salt
21:44 voltage_ joined #salt
21:46 voltage_ left #salt
21:47 archrs joined #salt
22:10 bluenemo is there a way to get the default gateway network interface, may it be eth0, eth1 or br0 somehow?
22:12 mpanetta joined #salt
22:15 linjan joined #salt
22:19 jp_ joined #salt
22:29 gladiatr joined #salt
22:30 gladiatr hey all.  Can anyone direct me towards a mailing list thread or some such that describes the listen/listen_in requisites?  I find the blurb at the bottom of the requisites doc to be somewhat... obtuse...
22:32 Ryan_Lane gladiatr: sure
22:32 Ryan_Lane I wrote the docs. sorry if they're not clear
22:32 Ryan_Lane gladiatr: here's a blog post about it: http://ryandlane.com/blog/2014/07/14/truly-ordered-execution-using-saltstack/
22:33 gladiatr Ryan_Lane, tyvm.  I've just been trying to wrap my head around the smart use of the req terms--I saw a list post w/ re: to someone who converted their entire system over to listen/listen_in--oh-so-worth-it but he didn't share any details :)
22:33 Ryan_Lane the gist is that a full state run will occur, then any state that was triggered by listen/listen_in will run in order
22:34 gladiatr and that is in lieu of using watch/watch_in then?
22:34 Ryan_Lane it lets you define your states in sequential order, and not use require/require_in and watch/watch_in, which can (and will) reorder your states
22:34 Ryan_Lane well, note in the blog post that I still recommend the use of watch for one particular use case
22:35 Ryan_Lane it should be used with care
22:36 gladiatr interesting.  ok.  I'll read your blog page about it before littering the channel further :)  I'm not sure if it is what I'm looking for, but I wanted to find out more.
22:36 Ryan_Lane it's mostly just a different way to use salt
22:37 Ryan_Lane completely sequentially ordered state runs, rather than dependency graphs
22:38 aurynn ... which is a subset of a dependency graph
22:41 Ryan_Lane sure. "all of these triggered states depend on all of the states run before it"
22:41 gladiatr aurynn, lol.  indeed.  I just need to spend a bit more time actually automating things (what I need to do) and less staring at source code trying to map out precisely what makes it tick (what I prefer doing but shouldn't be spending time on atm)
22:42 Ryan_Lane it's a graph with a single dependency :D
22:42 aurynn so learning puppet first helped me a lot, I feel; I assume by default that anything I declare will run out of order, and if I need specific ordering I add require/require_in/watch
22:43 linjan joined #salt
22:44 Ryan_Lane I assume the opposite. if I write things in order, I assume they'll run in that order
22:44 Ryan_Lane unless I use order, require, or watch
22:45 Ryan_Lane things running out of order are chaos inducing. a minor change can make an initial run fail
22:45 jab416171 joined #salt
22:45 Ryan_Lane I learned that really well from puppet :)
22:45 cads joined #salt
22:45 aurynn puppet taught me to *always* add the dependencies, because of that chaos
22:47 Ryan_Lane it's only necessary because things run out of order, though :)
22:47 Ryan_Lane ordered runs + global failhard = win
22:47 aurynn yes, which makes sense because it's not imperative programming
22:47 Ryan_Lane you can know when something runs in docker/vagrant that it will work exactly the same everywhere
22:47 jab416171 joined #salt
22:48 Ryan_Lane it's imperative programming for me
22:48 Ryan_Lane and why not? why does config management need to be unordered declarative, instead of imperative declarative?
22:48 aurynn performing imperative programming in declarative environments is a source of considerable suffering
22:49 Ryan_Lane I've found the opposite to be true
22:49 Ryan_Lane it's so much easier to modify an imperative system
22:49 aurynn it's just different
22:49 Ryan_Lane only because config management systems have historically been that way
22:49 __number5__ anyone has a simple custom state/module template I can copy?
22:50 aurynn chef isn't that way
22:50 Ryan_Lane __number5__: this may not be the best example: http://ryandlane.com/blog/2014/09/08/saltstack-development-behavior-of-exceptions-in-modules/
22:50 Ryan_Lane true. I don't have a lot of experience with chef
22:51 aurynn I'm not fond of it
22:51 Ryan_Lane people aren't leaving chef in droves as much as they are with puppet, though
22:51 aurynn it's very much what you get when you let a bunch of ruby programmers reimplement things
22:51 Ryan_Lane heh
22:51 aurynn like active record!
22:51 Ryan_Lane puppet uses (or used) active record :)
22:52 aurynn AR started out clownshoes and, I'm told, has evolved into something useful
22:52 jab416171 joined #salt
22:52 __number5__ Ryan_Lane: thanks, that will do.
22:52 Ryan_Lane anyway, running things imperative means that someone who's not familiar with the entire dependency graphs can jump in, and add something, knowing how things will run
22:53 aurynn I'm not sure I want someone modifying things in that case
22:54 Ryan_Lane our developers maintain their own config management and orchestration
22:54 aquinas joined #salt
22:54 Ryan_Lane it's easier for them to grok imperative, than unordered, since it's what everything else is
22:54 aurynn it turns out I'm more conservative than I thought, because that fills me with dread.
22:54 Ryan_Lane hahaha
22:54 Ryan_Lane it's wonderful
22:54 aurynn who gets paged?
22:54 Ryan_Lane they also are the ones on call
22:55 aurynn okay that's better.
22:55 Ryan_Lane they manage their own services, hence giving them config management and orchestration
22:56 gladiatr Ryan_Lane, great blog post.  A good chunk of that should be included in the doc section for listen/listen_in :)
22:56 Ryan_Lane yeah. I didn't put enough effort into that doc :D
22:56 Ryan_Lane I wrote up the basics, since no one else had added any docs
22:59 cjohn_ joined #salt
22:59 gladiatr Ryan_Lane, so, if I understand correctly, without requisites, a state does run sequentially if it uses no requisites. I'm working on a reactor chain to verify/unbugger a minion whose salt version is out of phase with the master--each stage needs to fire an event upon completion except for the stage where a service restart is run against the salt-minion itself.
22:59 gladiatr s/without requisites//
23:00 gladiatr joyjoyjoy.  Thanks for the information and the link
23:00 Ryan_Lane yw :)
23:00 atbell joined #salt
23:06 atbell joined #salt
23:11 hasues joined #salt
23:11 TK_ joined #salt
23:18 Outlander joined #salt
23:29 dude051 joined #salt
23:35 TyrfingMjolnir joined #salt
23:38 otter768 joined #salt
23:40 hasues left #salt
23:40 atbell joined #salt
23:41 rubenb joined #salt
23:48 gladiatr joined #salt
23:49 glyf joined #salt
23:53 jeffrubic joined #salt
23:54 atbell joined #salt

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