Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-11-23

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

All times shown according to UTC.

Time Nick Message
00:04 otter768 joined #salt
00:20 GvJordan joined #salt
00:34 jimklo joined #salt
00:43 rockey joined #salt
00:58 ezheidtmann joined #salt
01:01 thedodd joined #salt
01:16 Brett_Swaim joined #salt
01:16 Brett_Swaim Hi all, I'm a complete n00b for Salt but have some experience with Puppet. I'm trying to use salt-cloud to create a node in a VPC
01:17 Brett_Swaim I can create nodes NOT in a vpc just great
01:17 Brett_Swaim when I try to create one in the VPC, it /kinda/ works...
01:17 Brett_Swaim the instance gets created in aws, it's in the right security group and subnet, but the name never sets, and I can salt-cloud can never access the node
01:18 Brett_Swaim basically, it looks like this
01:18 Brett_Swaim https://www.dropbox.com/s/8ec1r196569g21p/Screenshot%202014-11-22%2017.18.04.png?dl=0
01:18 Brett_Swaim you can see the ami.example.com one is NOT in my vpc
01:18 Brett_Swaim the blank on eis
01:18 Brett_Swaim one is
01:18 Brett_Swaim so, configs:
01:20 Brett_Swaim https://gist.github.com/BrettSwaim/dc0cc62a5c7ffaa4e66d
01:20 rap424 joined #salt
01:21 Brett_Swaim and I call it with
01:21 Brett_Swaim sudo salt-cloud -p base_ec2 Minion2
01:21 Brett_Swaim that's what creates that blank entry
01:21 Brett_Swaim anybody have any thoughts?
01:21 aparsons joined #salt
01:22 waygeekierthanu joined #salt
01:26 jonatas_oliveira joined #salt
01:29 waygeekierthanu switching to a different client, when I remove the securitygroup and subnetid lines, it seems to create nnormally but not in a vpc
01:30 Brett_Swaim it seems to be related to the subnetid, when I comment out the security group settings but leave in the subnet settings it doesn't take the name then either
01:34 jimklo joined #salt
01:38 funzo_ joined #salt
01:47 thedodd joined #salt
01:58 atbell joined #salt
02:07 crocket left #salt
02:08 alexr joined #salt
02:16 spielberg joined #salt
02:17 hunmonk_ joined #salt
02:20 spielberg joined #salt
02:31 glyf joined #salt
02:34 jimklo joined #salt
02:36 thedodd joined #salt
02:41 otter768 joined #salt
02:41 younqcass joined #salt
02:53 linjan joined #salt
02:55 elepfontius joined #salt
03:12 thedodd joined #salt
03:14 jonatas_oliveira joined #salt
03:28 CeBe1 joined #salt
03:35 kseifried joined #salt
03:37 rawkode_ joined #salt
03:40 rawkode_ joined #salt
03:45 hunmonk_ running into a weird problem with pkg module. running pkg.install from the master doesn't successfully install the package on the minion, but running pkg.install from the minion directly does successfully install it. same problem with pkg.upgrade. however, pkg.delete does work from the master. debug output from master/minion calls for pkg.install here: http://pastebin.com/guX1dMNx
03:53 hunmonk_ ok, figured out the problem. the server connects via a proxy, which is currently set via http_proxy environment variable. is there some way i can configure the minion to have that environment variable available when it executes commands from the master?
03:53 rawkode_ joined #salt
03:55 hunmonk_ best would be if i could load up the bash environment from the user that's got the http_proxy config, but i'll take what i can get :)
03:56 max_ joined #salt
04:22 jimklo joined #salt
04:38 thayne joined #salt
04:42 otter768 joined #salt
04:46 jonatas_oliveira joined #salt
04:48 druonysus joined #salt
04:48 druonysus joined #salt
05:07 aparsons joined #salt
05:10 otter768 joined #salt
05:13 TheThing joined #salt
05:21 Outlander joined #salt
05:34 jimklo joined #salt
05:48 Brett_Swaim joined #salt
06:15 catpigger joined #salt
06:22 monkey66 joined #salt
06:32 thayne joined #salt
06:33 hasues joined #salt
06:33 otter768 joined #salt
06:34 hasues left #salt
06:35 linjan joined #salt
07:00 snuffeluffegus joined #salt
07:01 thayne joined #salt
07:13 g3cko joined #salt
07:21 bhosmer_ joined #salt
07:26 jimklo joined #salt
07:28 ysiad joined #salt
07:34 jimklo joined #salt
08:05 jonatas_oliveira joined #salt
08:11 stooj joined #salt
08:22 linjan joined #salt
08:34 jimklo joined #salt
08:47 aparsons joined #salt
08:53 aparsons joined #salt
08:59 aparsons joined #salt
09:14 gildegoma joined #salt
09:34 jimklo joined #salt
09:51 agend joined #salt
09:55 jonatas_oliveira joined #salt
10:00 ysiad joined #salt
10:01 chiui joined #salt
10:09 Roee joined #salt
10:09 Roee hi all !
10:09 Roee Have a ques..
10:10 Roee i'm trying to configure the top.sls to run only on  a specific node group
10:10 Roee when i'm configuring the base with '*'
10:10 Roee everything is working well
10:11 agend joined #salt
10:12 Roee but when i'm changing the '*' to the name of the specific node group (e.g. 'lms') i'm receiving the following error :  No Top file or external nodes data matches found
10:15 viq Roee: http://docs.saltstack.com/en/latest/topics/targeting/nodegroups.html#targeting-nodegroups
10:15 viq have you added the - match: nodegroup part?
10:19 Roee hi viq
10:19 Roee sure I have created those nodegroup
10:20 viq Roee: I mean did you tell salt in your top.sls that you're trying to match on nodegroups, like the link says?
10:20 Roee btw when i'm executing a stae.sls on a specific node group everything is working as expected
10:23 Roee Great working !
10:23 Roee thanks Viq you saved me. again... :)
10:23 viq :P
10:25 Outlander joined #salt
10:30 otter768 joined #salt
10:34 jimklo joined #salt
10:34 ckao joined #salt
10:36 ysiad joined #salt
10:38 rawkode_ joined #salt
10:43 ingwaem joined #salt
10:49 bhosmer_ joined #salt
10:49 laderhiton joined #salt
10:55 ingwaem joined #salt
11:03 jasonrm joined #salt
11:07 xliiv joined #salt
11:22 xliiv hi
11:23 peters-tx joined #salt
11:24 xliiv i've got such file: https://github.com/xliiv/psf-salt/blob/master/salt/docs/init.sls
11:25 xliiv which should install e.g. git or mercurial.. so what am i doing is..
11:26 xliiv vagrant up docs according to vagrant file which is here: https://github.com/xliiv/psf-salt/blob/master/Vagrantfile
11:26 xliiv so machine is started, then i do 'vagrant ssh docs' ..
11:27 xliiv but i can't see git installed on the *docs* machine..
11:27 xliiv how can i debug it?
11:27 viq xliiv: salt-call state.highstate
11:27 xliiv im also manually run  "sudo salt-call state.highstate -l debug"
11:28 viq yeah, and what does that give?
11:28 viq Erm, also, what's your top.sls?
11:29 xliiv https://github.com/xliiv/psf-salt/blob/master/salt/top.sls
11:29 xliiv output of salt-call: http://pastebin.com/xBmxqWcG
11:29 xliiv should i have master working?
11:30 xliiv is it required?
11:30 xliiv because it's only suspecious message from debug :D
11:30 viq I've never really tried to use masterless
11:30 ingwaem joined #salt
11:30 xliiv anyway.. i also tried with uped salt-master
11:31 xliiv error is the same.. ok.. i'll check that track
11:32 viq you could try salt-call --local state.highstate if you don't want master and have states locally
11:32 xliiv thx
11:32 xliiv :)
11:33 jeddi joined #salt
11:33 viq Ah, also, if you're not preseeding minions' keys on master you would have to manually accept them before communication could happen
11:34 jimklo joined #salt
11:35 xliiv i forgot that, thx again :)
11:43 jonatas_oliveira joined #salt
12:01 alexr__ joined #salt
12:02 ecdhe joined #salt
12:09 glyf joined #salt
12:10 rawkode_ joined #salt
12:19 ysiad joined #salt
12:25 zamuz joined #salt
12:27 ysiad joined #salt
12:27 zamuz Hey guys, salt newbie here. You've probably read this a lot, but I'm quite confused. I've installed salt-master on a server, salt-minion on a client. Accepted the key and everything is fine. I've created /srv/salt/base/top.sls and named a sample name package with pkg: - installed...
12:27 zamuz Not really sure where I go from here.
12:31 otter768 joined #salt
12:32 zamuz (Oh and right, ping also works)
12:34 jimklo joined #salt
12:35 younqcass joined #salt
12:40 CeBe joined #salt
12:43 linjan_ joined #salt
12:45 bhosmer joined #salt
12:46 druonysus joined #salt
12:48 hasues joined #salt
12:56 viq zamuz: either add your state to top.sls assigning it to your minion, and "salt \* state.highstate", or apply state "one time" by "salt yourminion state.sls yourstate"
12:56 viq zamuz: also, that pkg.installed, you didn't put it in top.sls, did you?
12:58 zamuz afraid i did, viq
13:00 zamuz i already realized that's a mistake, but i'm still not sure how to achieve my initial goal; have x packages installed as a base case
13:03 viq zamuz: one more question - did you change your /etc/salt/master ?
13:04 zamuz yes, i uncommented file_roots
13:04 viq And did you change the value?
13:06 zamuz no, i just created the directory as it appeared in the file
13:06 viq which is /srv/salt - correct?
13:06 zamuz yeah
13:06 viq then your top.sls should be in there
13:06 zamuz then i created base dir
13:07 zamuz oh, not inside base?
13:07 viq No
13:07 viq That's for playing with environments, for which you need to adjust file_roots
13:08 viq So first step: your top file should be at /srv/salt/top.sls
13:08 zamuz oh, i get it
13:08 zamuz that makes sense
13:08 viq Second step: your state installing packages and such should be for example in /srv/salt/packages.sls
13:09 viq Third, your top.sls would look like this: https://www.refheap.com/93820
13:09 viq Then you can run commands I mentioned.
13:11 viq Note for future: you could for example put your state in /srv/salt/base/packages.sls in which case in your top you would refer to it as base.packages
13:11 viq If you named it base/init.sls then just base would work.
13:13 viq zamuz: have you seen http://docs.saltstack.com/en/latest/topics/tutorials/walkthrough.html ?
13:13 faust joined #salt
13:13 rawkode_ joined #salt
13:14 bmonty joined #salt
13:17 cads joined #salt
13:17 zamuz thanks a bunch, viq
13:17 max_ joined #salt
13:17 zamuz everything's clear now
13:17 faust joined #salt
13:17 zamuz and yes i have, but not carefully as i'm doing 10 things simultaneously
13:20 diegows joined #salt
13:25 johtso_ joined #salt
13:26 hunmonk_ joined #salt
13:26 faust joined #salt
13:29 faust joined #salt
13:32 jonatas_oliveira joined #salt
13:36 elfixit joined #salt
13:47 hcl2 joined #salt
13:51 hasues left #salt
13:53 bhosmer joined #salt
14:12 markm_ joined #salt
14:18 vbabiy joined #salt
14:21 pdayton joined #salt
14:23 vbabiy joined #salt
14:32 otter768 joined #salt
14:38 slav0nic joined #salt
14:38 slav0nic joined #salt
14:39 slav0nic i defined environment in top.sls but salt://files/ still try load from base env + got errors like "Detected conflicting IDs, SLS IDs need to be globally unique" (salt-ssh)
14:40 viq slav0nic: show your top.sls
14:41 slav0nic viq, http://dpaste.com/35RSGR9
14:42 slav0nic two env have same sls files
14:42 viq slav0nic: how many top.sls files do you have?
14:43 slav0nic 1 per env
14:43 slav0nic 2
14:43 viq Try having one global one, they get merged.
14:43 viq Or something to that effect, that I understood from comments here.
14:46 slav0nic viq, looks not useful. I have 2 project that uses salt and wont split it in 2 environments (based on project name for example)
14:55 spielberg joined #salt
15:01 viq joined #salt
15:02 babilen slav0nic: The general consensus is that you want to manage top files in their own repo/globally.
15:07 slav0nic okey, maybe i do not fully understand why IDs my be globally unique (not per environment)
15:12 hannesstruss joined #salt
15:21 jonatas_oliveira joined #salt
15:21 monkey66 left #salt
15:25 diegows joined #salt
15:28 borgstrom joined #salt
15:38 bhosmer joined #salt
15:39 hunmonk_ is there a way to point a salt minion to use an alternate version of zeromq?
16:10 SheetiS joined #salt
16:16 CeBe joined #salt
16:20 ysiad joined #salt
16:25 csstylish joined #salt
16:26 godber1 joined #salt
16:27 godber1 salt virt FYI ....
16:27 godber1 when bringin up a new hypervisor ...
16:27 spielberg joined #salt
16:27 godber1 if your salt minion starts up BEFORE you install python-libvirt ...
16:28 godber1 you must restart your salt minion for it to show up as having libvirt enabled
16:28 godber1 its obvious, but I did't think of it
16:28 godber1 TIA ... have a nice day everyone
16:28 tmmt joined #salt
16:33 otter768 joined #salt
16:37 g3cko Has anyone used the nagios module in 2014.7?
16:37 badon joined #salt
16:38 bhosmer joined #salt
16:39 g3cko Anyways, I noticed the docs as-is, don't actually work, so I made an issue, and a patch/PR to fix whats not working: https://github.com/saltstack/salt/pull/18405
16:40 ajolo joined #salt
16:41 ctrlrsf joined #salt
17:02 JlRd joined #salt
17:04 gildegoma joined #salt
17:10 jonatas_oliveira joined #salt
17:11 csstylish joined #salt
17:15 csstylish joined #salt
17:21 faust joined #salt
17:34 jimklo joined #salt
17:35 glyf joined #salt
17:37 TheThing joined #salt
17:38 CeBe joined #salt
17:52 jab416171 joined #salt
17:53 faust joined #salt
18:10 gildegoma joined #salt
18:12 jonatas_oliveira joined #salt
18:18 frex joined #salt
18:18 frex hey guys!
18:18 Rucknar_ joined #salt
18:18 frex i used to come here a while a go
18:18 pdayton1 joined #salt
18:18 MorbusIff joined #salt
18:19 wolfpackmars2 joined #salt
18:19 frex installed i2p again and salt is gone, and i dont remember the irc adress
18:19 frex did it move ?
18:19 dh__ joined #salt
18:19 Jellyfrog joined #salt
18:19 SheetiS joined #salt
18:20 giany joined #salt
18:21 frex hellooo0?
18:23 flebel joined #salt
18:30 linjan joined #salt
18:31 Bryanstein joined #salt
18:34 otter768 joined #salt
18:34 jimklo joined #salt
18:38 dh joined #salt
18:46 kseifried left #salt
18:54 ysiad joined #salt
19:05 toastedpenguin joined #salt
19:13 Kraln joined #salt
19:13 Kraln joined #salt
19:19 ShibMcNe Hi, is anyone using salt 2014.7 on ubuntu utopic ?
19:24 ShibMcNe salt 2014.1 is the last version vailable in utopic repos, and the official ppa only builds salt 2014.7 for trusty and precise.
19:25 bhosmer joined #salt
19:34 jimklo joined #salt
19:36 faust joined #salt
19:40 otter768 joined #salt
19:43 aquinas joined #salt
19:47 thayne joined #salt
19:51 chiui joined #salt
19:52 fr3x joined #salt
20:02 hannesstruss joined #salt
20:12 glyf joined #salt
20:15 faust joined #salt
20:16 faust joined #salt
20:18 faust joined #salt
20:24 dramagods joined #salt
20:26 hannesstruss joined #salt
20:27 withasmile joined #salt
20:30 __gotcha joined #salt
20:31 P0bailey joined #salt
20:31 P0bailey joined #salt
20:36 joehh ShibMcNe: I haven't built packages for it yet, will do so today
20:37 ssteinerX joined #salt
20:40 ShibMcNe joehh: thanks =] should I close issue #18421 ?
20:46 Kelly joined #salt
20:46 Kelly Hello All
20:46 dooshtuRabbit joined #salt
20:54 MugginsM joined #salt
20:59 LotR hmm. the gpus grain's value contains a dict (I hope that's the correct term in python). how do you match against one of its keys?
21:00 viq LotR: one thing I found was grain:*something*
21:01 viq so eg gpu:*nvidia*
21:01 bhosmer joined #salt
21:01 rawkode_ joined #salt
21:01 LotR so just globbing against the entire content as a string? that seems fragile
21:02 joehh ShibMcNe: don't close it till they are up...
21:02 viq I didn't say it was a good solution :P
21:06 Kelly Does anyone know how to monitor the restart of a service that occurs due to a config file change, and if the restart fails, replace the changed config file with the original file and restart again?
21:09 LotR viq: hmm. you can do grains.get 'ip_interfaces:eth0' to get the ip of that interface. but gpus is actually a list of dicts. so now to figure out how to get the first entry
21:12 asmaps joined #salt
21:12 douardda joined #salt
21:13 LotR viq: ooh, googling more found that 'gpus:model:*something*' should work too
21:15 LotR hmm, do you have to do all the matching of states to minions in top.sls, or can you do more fine-grained matching lower in the state tree?
21:16 CeBe joined #salt
21:18 spielberg joined #salt
21:18 thawes joined #salt
21:21 asmaps joined #salt
21:22 csstylish joined #salt
21:24 bhosmer joined #salt
21:24 noway_ joined #salt
21:27 ajolo joined #salt
21:27 snuffeluffegus joined #salt
21:34 jimklo joined #salt
21:40 ssteinerX is there a module etc. for running a command on the salt-master?
21:40 aurynn yes
21:41 aurynn I don't remember what it's called though
21:41 aurynn the reactor system uses it, though
21:47 bhosmer joined #salt
22:03 alexr joined #salt
22:03 Kelly Can I chain multiple steps in a state to watch a file, restart a service if that file changes, then if the restart fails (typo in file), rollback the file change and re-restart the service?
22:07 jY Kelly: i don't think there is anyway for service to notify on failure.. you could write your own state to do that though
22:07 mosen joined #salt
22:07 Kelly so would it be more appropriate after restarting a service to recheck its state, and if not running do a file restore and another restart?
22:08 aurynn that sounds more like orchestration and deployment than state management
22:09 Kelly Perhaps aurynn.  I just don't want to push a watched service config file out to my entire enterprise, and if it has a typo in it, have all servers fail to restart their service.
22:11 aurynn uh
22:11 aurynn it sounds like you have larger problems in your workflow
22:12 Kelly lol...well, in this case it's a tacacs user file that gets edited by hand when new users are added or old users removed.  Typos are certainly possible.
22:12 aurynn like "why are you pushing untested files into production?"
22:13 Kelly right..so the answer may just be that the file has to be tested against a local service instance prior to being pushed out.
22:15 aurynn like, having that kind of automated recovery orchestration is *good*, great even. But it's a fair amount of work to get it to play nicely, and get the right monitoring so you're not just pushing stuff out and never noticing that it's not upgrading because of a crash
22:17 aurynn so I'm not saying "don't" - I'd probably do it with the reactor system and a small shellscript that tells the master to deploy a "rollback" state in the event of a failure
22:17 aurynn I'm saying "is this the right solution?"
22:18 yani joined #salt
22:18 aurynn and maybe a nagios monitor that watches for what version of the file *is* running vs. what version of the file is in the repo, and alert on that
22:20 aurynn "fair amount" okay maybe that was lies. A day or two to hack something up. :)
22:21 aurynn If it's just you editing this file, I'd go with testing. If it's other, not-you people doing it, build orchestration.
22:21 aurynn :)
22:22 aurynn anything that results in Less Pager is good
22:25 yani http://pastebin.com/AveeT6sq called on 'salt/job/*/ret' but doesn't make it to the executable, am I doing something wrong?
22:25 Kelly I agree.  Thanks aurynn
22:25 Kelly and yeah, not always going to be me editing the file.
22:25 aurynn right.
22:26 aurynn Kelly, so, the reactor and orchestrate machinery would be good for this. Also, it depends on how the others will be uploading the new file
22:29 Kelly I'll have to look into reactor.  I'm about 2 days into using Salt, so it's all new to me.
22:30 ssteinerX aurynn: run command on salt-master -- "I don't remember what it's called though"  I've been searching for almost an hour, any clues?  I've googled 'till my fingers hurt and even tried searching in the salt source.  Seems such a simple and common thing to want to do...
22:31 Kelly ssteinerX, can a master not also be a minion?
22:32 ssteinerX Kelly: I thought of that, but it makes me itch not to just be able to run a command on the salt-master.
22:33 Kelly what command is it you want to run?
22:33 ssteinerX a pull from a git repo
22:33 ssteinerX I don't want the repo to be accessible from the target minion
22:34 ssteinerX (it's a private repo and I'd have to add an SSH key, etc.)
22:34 Kelly ah, so you're trying to pull a pkg down from a git repo and put it into the salt /srv/salt location for pull by a minion?
22:34 aurynn I use pull-only SSH keys for that
22:34 jimklo joined #salt
22:34 aurynn ssteinerX, I think you may have to make the master a minion as well, to do what you want to do
22:35 ssteinerX aurynn: that's only one use case
22:35 Kelly SCP to do the pull from the repo?
22:36 ssteinerX aurynn: seems upside down not to be able to control the local machine from a system that excells at controlling others
22:36 ssteinerX e.g. what if I want to add a git tag to identify what's being pushed to minions?
22:37 aurynn I'd still use a loopback state
22:37 aurynn or maybe a custom runner?
22:37 aurynn as http://serverfault.com/questions/588119/run-command-on-salt-master-before-minion-highstate suggests
22:38 ssteinerX far beyond my capabilities after 5 days with salt
22:38 ssteinerX I looked at the repo referenced and it's all clear as mud
22:38 ssteinerX if I want to run something manually, I can use a stupid shell script
22:39 ssteinerX it's the having to remember to do it that's giving me agita
22:39 aurynn not sure what's wrong with just setting up a minion on the master and doing stuff like that
22:40 ssteinerX two places to maintain code: one in the minion config and one in the master/minion
22:40 aurynn what? why?
22:41 ssteinerX I have to class the salt-master as one type of minion and the "minion-minions" as different ones
22:41 ssteinerX as far as I understand it, anyway
22:41 pentabular joined #salt
22:41 aurynn Yes, but you do that in the topfile in the main state tree
22:42 aurynn and then use orchestration to do master stuff, like updating git, before minion stuff
22:42 aurynn or just a shellscript which does all your git pulls before firing highstate
22:43 Outlander joined #salt
22:45 ssteinerX aurynn: it just seems convoluted.  Shouldn't operations on salt-master should be at least as powerful as operations on minions?
22:46 aurynn ssteinerX, it was build as a remote execution platform. the config management stuff came later.
22:46 ssteinerX or maybe (light bulb) adding all that crap is unnecessary since salt-master can also be a minion of itself
22:46 aurynn so, no
22:46 aurynn heh, yes, that's what I've been saying
22:46 ssteinerX what's the emoticon for "light bulb moment" ;-)
22:46 aurynn you can run minion on the master and associate it with itself
22:47 ssteinerX aurynn: thank you!
22:47 aurynn but!
22:47 ssteinerX oh crap.
22:47 aurynn heh
22:47 aurynn Not a big but
22:47 ssteinerX better with two t's
22:47 aurynn but if you need to do the git pulls first, you will need to look at the orchestration stuff, so you can have the minion-master stuff execute first
22:47 aurynn fortunately it's largely identical
22:48 glyf joined #salt
22:49 * ssteinerX uh oh, another black hole...
22:49 aurynn nah it's easy
22:49 ssteinerX everything's easy if you know what you're doing...
22:49 aurynn http://docs.saltstack.com/en/latest/topics/tutorials/states_pt5.html
22:50 ssteinerX for example, I find it easy to turn live chickens into food
22:50 ssteinerX try that from your keyboard...
22:50 aurynn so the 3.3.6.1.4 example can be pretty quickly modified to your needs
22:51 aurynn like, state.state: -tgt: is the same matching logic as the stuff in your top.sls
22:51 aurynn right?
22:52 aurynn and precedence happens with the same -require arg
22:52 CeBe joined #salt
22:53 aurynn so you'd have a minion-master: salt.state: -tgt: "minion-on-master", - highstate: True, and then minions: salt.state: -tgt: "real-minion-*", -require: salt: "minion-on-master"
22:54 aurynn and 'cos you're just using highstate directly, the pillar and grain stuff you've set up comes along
22:54 ssteinerX aurynn: understood-ish
22:54 ssteinerX I'm going to have to play with it for a little while
22:54 patrickcp joined #salt
22:55 ssteinerX interesting tidbit this:"Additionally, the states/functions will be executed in the order in which they are defined, unless prevented from doing so by any requisites, as is the default in SLS files since 0.17.0."
22:55 ssteinerX which I wasn't sure of
22:55 ssteinerX haven't looked at what kind of state machine is being built on the backend
22:56 aurynn ah neat
22:56 aurynn My puppet background makes me assume things will execute in arbitrary order, so I always set up explicit precedence
22:57 ssteinerX I have also used puppet and fabric (to which I contributed)
22:57 ssteinerX fabric is very explicit
22:57 ssteinerX I find "arbitrary" hard to deal with (in general in life)
23:02 aurynn I like that it forces explicit declarations
23:03 Outlander joined #salt
23:03 ssteinerX aurynn: agreed -- I need *less* fragility and *more* predictability, that's why I'm using a tool!
23:03 aurynn hehe
23:03 aurynn :)
23:05 ssteinerX aurynn: I'm feeling "the guilt" that I'm not writing this up in a blog post.  It seems an obvious and common problem, but I've been searching for a solution for three days.
23:05 ssteinerX Thing is, I've tried every logical search term and found zip.
23:06 ssteinerX And, I run an SEO company...
23:06 ssteinerX I could solve my own problem, the make sure it comes up in Google for when I forget!
23:06 ssteinerX then
23:09 spielberg joined #salt
23:31 Singularo joined #salt
23:34 jimklo joined #salt
23:42 alexr joined #salt
23:52 hcl2 joined #salt

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