Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-06-30

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

All times shown according to UTC.

Time Nick Message
00:02 bruce-one joined #salt
00:04 whit joined #salt
00:05 EugeneKay I use a default pillar with global users/groups(and other data), and then(if need be) override it in a machine-specific one.
00:11 jeddi EugeneKay: you can override it such that some users won't be included?  do you override it by doing a jinja for loop for a given set of users? that's kind of what i thought i might end up doing .. only a handful of my servers have actual users on them.   and i have one sftp-only server, so users need to be known (ssh keys etc) but configured in an entirely different way.
00:11 EugeneKay No, I just override the entire users: block
00:11 jeddi i'm probably going to try to adopt the new stuff defined at https://github.com/saltstack-formulas/users
00:11 jeddi ah, okay.  using a pillar for that host?
00:11 EugeneKay Yah
00:11 jeddi (still getting into pillar layouts)
00:11 EugeneKay I just copypasta the section from the default pillar and modify as needed
00:12 EugeneKay If I ever need to change the defaults I'll have to go through all my hosts and modify.... there's probably a better way
00:12 EugeneKay Probably something involving a for loop, yeah
00:13 jeddi hmm .. yeah.  i'm paralized by the fear of having to rework bits of this.  i should get over that.
00:14 EugeneKay I figure it'll evolve.
00:14 carmony joined #salt
00:17 rglauser joined #salt
00:40 kleinishere joined #salt
00:42 Jahkeup_ joined #salt
00:55 bemehow joined #salt
00:59 raydeo joined #salt
01:09 bluemoon joined #salt
01:12 jkleckner joined #salt
01:26 jbunting joined #salt
01:29 diegows joined #salt
01:34 oz_akan_ joined #salt
01:40 rhormaza joined #salt
01:50 UForgotten_ joined #salt
02:04 jaequery joined #salt
02:10 tpe11etier joined #salt
03:18 bemehow joined #salt
03:21 jessep joined #salt
03:29 raydeo joined #salt
03:30 alazylearner joined #salt
03:46 oz_akan_ joined #salt
03:50 oz_akan__ joined #salt
03:55 Gifflen joined #salt
03:56 UForgotten joined #salt
03:58 LyndsySimon joined #salt
04:00 Ivo joined #salt
04:10 blakearnold joined #salt
04:20 auser joined #salt
04:22 Gifflen joined #salt
04:24 rfgarcia joined #salt
04:29 dthom91 joined #salt
04:48 rglauser joined #salt
05:08 jaequery joined #salt
05:13 tomeff joined #salt
05:26 whit joined #salt
05:30 alazylearner joined #salt
05:32 mchype joined #salt
05:39 kmwhite joined #salt
05:54 kleinishere joined #salt
06:24 fllr joined #salt
06:32 kleinishere joined #salt
06:35 Newt[cz] joined #salt
06:36 jkleckner joined #salt
06:38 dthom91 joined #salt
06:39 Newt[cz]1 joined #salt
07:05 oz_akan_ joined #salt
07:11 Katafalkas joined #salt
07:13 upsidedwn joined #salt
07:25 faust joined #salt
07:45 jkleckner joined #salt
07:50 Xeago joined #salt
07:55 dthom91 joined #salt
08:09 fllr joined #salt
08:20 bemehow joined #salt
08:20 jkleckner joined #salt
08:23 Ivo joined #salt
08:37 berto- joined #salt
08:51 madduck defunctzombie_zz, __number5__: it would be great if you could stop your clients from nick-changing on away. It's noise in the channel(s), not terrible, but also not necessary. Thanks.
08:53 bemehow joined #salt
09:00 jkleckner joined #salt
09:04 Newt[cz] joined #salt
09:04 kleinishere joined #salt
09:47 hazzadous joined #salt
09:56 drdran joined #salt
10:08 bluemoon joined #salt
10:16 dthom91 joined #salt
10:21 ronc joined #salt
10:22 carmony joined #salt
10:27 __number5__ madduck: sorry
10:27 __number5__ will fix it
10:27 madduck __number5__: no worries, thank you for understanding!
10:36 jkleckner joined #salt
10:55 drdran joined #salt
11:10 p3rror joined #salt
11:12 ronc joined #salt
11:14 jkleckner joined #salt
11:29 bhosmer joined #salt
11:32 Lancy joined #salt
11:32 azbarcea joined #salt
11:33 az87c joined #salt
11:34 Lancy left #salt
11:46 jbunting joined #salt
11:50 mikedawson joined #salt
11:55 aranhoide joined #salt
12:05 diegows joined #salt
12:24 Jahkeup_ joined #salt
12:28 _ilbot joined #salt
12:28 Topic for #salt is now Welcome to #salt - http://saltstack.org | 0.15.3 is the latest | Please be patient when asking questions as we are volunteers and may not have immediate answers - Channel logs are available at http://irclog.perlgeek.de/salt/
12:36 bhosmer joined #salt
12:50 oz_akan_ joined #salt
13:17 diegows joined #salt
13:19 p3rror joined #salt
13:24 mikedawson joined #salt
13:27 oz_akan_ joined #salt
13:35 pewpewarrows joined #salt
13:35 jeddi joined #salt
13:40 pewpewarrows joined #salt
13:44 pewpewarrows joined #salt
13:49 pewpewarrows if I wanted to have a single salt master box handle deployment for multiple projects, using separate salt tree bases per project, how isolated/secure would they be from one another?
13:50 pewpewarrows that is, if my top file only has "*.foo.com" referencing states in the foo tree, and "*.bar.com" referencing states in the bar tree, is that adequate?
13:51 pewpewarrows could a minion matching "*.foo.com" ever possibly request/obtain a file from the bar state tree without it explicitly listed in the top file?
14:01 joshe sure, some state which it does match could include the bar state
14:03 kmwhite joined #salt
14:03 pewpewarrows ugh, damn
14:09 UtahDave joined #salt
14:13 jeddi pewpewarrows: i believe the recommended practice there is to put all sensitiev data into pillar.
14:13 jeddi pewpewarrows: alternatively keep them as separate projects entirely.  that'd make it easier if you ever hand over ownership of the config management for one of those projects to someone else.
14:14 pewpewarrows jeddi: that was the idea, I wanted a single salt-master server to handle deployment for several projects. each project has its own salt state tree config repo.
14:15 pewpewarrows jeddi: we're using pillars for most sensitive data, but there are some that have to be files (private keys)
14:15 jeddi pewpewarrows:  oh -y ou mean that they have /srv/salt1 , /srv/salt2, etc - and each set is accessible by running a different master?
14:16 jeddi yeah - private files .. i've yet to work out an elegant approach to.  private keys *can* go into pillar, but it's a bit messier.  i've considered (as have a few others) using git repos to pull these out on the fly.
14:16 jeddi but it's a bit of a pain, and obviously it's working around a limitation in a pretty inelegant way.
14:16 pewpewarrows jeddi: I don't know if it's possible to do that, haven't tried. was going with /srv/salt/foo and /srv/salt/bar
14:16 pewpewarrows if you can have entirely separate salt-masters running on the same system, that'd be perfect
14:17 jeddi pewpewarrows: fairy nuff.  i may have a similar problem in the future with some clients needing to peel off and look after their own configuration - at the moment i'm just resolved to having to split the repo up and hand over the bits relevant to them.
14:17 jeddi pewpewarrows: lxc may be a cheap way of virtualising multiple salt-masters on a single vps / machine.
14:17 pewpewarrows well we have separate repos
14:17 jeddi but, again, it's quite a messy arrangement.
14:18 pewpewarrows yeah, there's not an easy solution here, thanks for the advice jeddi
14:40 fllr joined #salt
14:41 faust joined #salt
14:42 wahahajun joined #salt
14:42 wahahajun hello  everyone
14:43 wahahajun is there anyone hear me? i met one question hope someone can help me
14:45 wahahajun i write one sls like:     jdk:   cmd run: -name setx path “%PATH%;c:\test” /M
14:47 wahahajun but  got one error:  the state 'jdk' in sls is not formed as a list..
14:48 wahahajun is someone met the similar problem?
14:48 wahahajun hello hi .....
14:49 wahahajun this is the first sls i wrote. met such kind of error. make me crazy...
14:50 pewpewarrows wahahajun: it should be "cmd.run"
14:50 jkleckner joined #salt
14:51 wahahajun o, sorry .i made a mistake here.
14:52 wahahajun sls file is :   jdk:   cmd.run:   -name: setx path “%PATH%;c:\test” /M
14:54 jkleckner joined #salt
14:54 jeddi wahahajun: can you put the file into a pastebin - it's easier to spot syntax and spelling mistakes .. try http://rn0.ru/ if you don't have a preference.
14:56 wahahajun ok
14:59 fllr joined #salt
14:59 dthom91 joined #salt
14:59 fllr How can I make salt create a passwordless user?
15:00 wahahajun this is my sls content http://rn0.ru/show/nsOSR8XtEQf5aTcqDZ2d/
15:03 pewpewarrows wahahajun: try indenting the third line another level
15:04 tpe11etier joined #salt
15:05 wahahajun ?? sorry
15:05 jeddi http://rn0.ru/show/m5FK2mjUMpHaB99ZQhGp/
15:06 jeddi though this doesn't look like the best way to do what you're trying to do.  have you run this successfully from the command line?   remember that state files define the 'state' of a machine or set of machines, and using them to run commands (without any qualifiers) may not be what you want.
15:06 wahahajun o, add one blank
15:07 jeddi you also usually have a space between the list (-) indicator and the string 'name'  .. that might be more aesthetics.
15:07 wahahajun yes. i have try the in command line:    salt '*' cmd.run "setx Path \"%PATH%\";\"%ProgramFiles%\"/java/jdk1.5.0_22/jre/bin; /M"
15:08 wahahajun it's ok in command line
15:12 wahahajun i added one blank to try but got same error:     data  failed to compile: ----------     The state "JDK" in sls win.repo.jdk.jdk is not formed as a list
15:12 tpe11etier joined #salt
15:16 pewpewarrows wahahajun: is the third line indented twice?
15:18 wahahajun yes. does it matter?
15:21 dthom91 joined #salt
15:22 wahahajun here is the source code of salt. https://bitbucket.org/ericsnowcurrently/salt/src/c5fa6893d0c2e3cf3553b85356aa8e90c5ea8711/salt/state.py
15:23 wahahajun please see line 221.  it seem to check the type list. Then throw this error
15:26 dahunter3 joined #salt
15:27 jeddi I'd try wrapping that thing in quotes.  change internal quotes to apostrophes.   it looks very windowsish.
15:27 jeddi and jdk 1.5 is quite the retro little beast, isn't it?
15:30 wahahajun yea. what do you mean "windowsish"
15:33 wahahajun you can use some simple cmd. like http://rn0.ru/show/VA5iebkenPKpdia6rKYk/
15:33 wahahajun got same error
15:34 santagada joined #salt
15:35 jeddi wahahajun: simle commands are unlikely to get parsed weirdly.  things with /m's and quotes (") in them .. are less guaranteed, I would imagine.
15:36 jeddi anyway, just saying that's what I'd try next :)
15:38 wahahajun Success. haha
15:39 wahahajun <jeddi> you also usually have a space between the list (-) indicator and the string 'name'  .. that it not just aesthetics.......
15:39 UtahDave joined #salt
15:40 wahahajun it does really  matter to do add a space  between the list (-) indicator and the string 'name'
15:40 joshe joined #salt
15:41 wahahajun Thanks very much.  it go on well to add the system variable PATH  in windows after install the JDK
15:42 wahahajun @<jeddi> @<pewpewarrows>   Thanks!!!!!!!!!
15:42 jkleckner @whahajun:  You may find this useful: http://www.yaml.org/spec/1.2/spec.html
15:47 joshe joined #salt
15:50 tpe11etier joined #salt
16:03 Shish joined #salt
16:04 Shish anyone got an example of a file with multiple lines of content in the .sls? I'm sure I saw something in one of the tutorials, but can't find it again, and no example on the file.managed reference page :(
16:08 akoumjian Shish: What do you mean multiple lines of content? You mean using the contents keyword?
16:09 Shish yeah
16:10 akoumjian Shish: Is there a particular reason you don't want to use the source attribute?
16:12 Shish there's several related two-line files, having them all on screen is more pleasant to edit; source works, it's just more fiddly
16:15 akoumjian Shish: I haven't used it personally, but do regular return characters '\n' work?
16:18 Shish seems those get put in the file as literal "\n"s v.v
16:19 Shish googling for yaml in general, the response is "use '>'", with no example of *how* to use it :|
16:22 Nazca joined #salt
16:22 akoumjian Shish: Do you need to double escape them? "\\n"
16:23 akoumjian And are you using double quotes?
16:24 Shish I was not using double quotes - doing so appears to be getting me somewhere...
16:29 akoumjian Cool. good luck
16:30 Shish thanks :3
16:34 rfgarcia joined #salt
16:36 jessep joined #salt
16:36 fllr Anyone with experience using salty-vagrant here?
16:36 rglauser joined #salt
16:36 akoumjian fllr: yep
16:41 wahahajun_ joined #salt
16:42 wahahajun_ now i wrote a new sls file and compile well http://rn0.ru/show/2PkiRa634ILfaMWhMUaM/
16:43 fllr akoumjian: I'm a beginner at both vagrant and salt. I wanted my vm to have a default user other than vagrant, and defined by me, and which I could login without a password since this is only my local dev environment. Could you help me out with that?
16:43 wahahajun_ but it seem only execute the JDK state and don't execute the Set_path .   no error infomation get..
16:44 mikedawson joined #salt
16:44 akoumjian fllr: Perhaps, yes. Perhaps you can tell me how you're trying to tackle that problem and where you're running into trouble.
16:44 akoumjian fllr: It sounds more like a *nix problem than a vagrant or salt problem.
16:46 wahahajun_ can anyone see my sls file. do me a favor..
16:47 tpe11etier joined #salt
16:48 fllr akoumjian: Well... I just don't know where to start. I started using salty-vagrant yesterday. I tried creating a users.sls file that creates a user for me. But it still requires me to login with a password. Is there anyway to upload my ssh key into my vm as soon as I run vagrant up?
16:48 akoumjian fllr: This is one of those cases where you first need to figure out how to do it manually, then figure out how to have salt automate it.
16:49 akoumjian fllr: Yes, inside a Vagrantfile you can use something like "@machine.communicate.upload(bootstrap_path.to_s, bootstrap_destination)" to upload a file to the VM
16:50 akoumjian fllr: But getting salt to do it would be easy too.
16:50 jaequery joined #salt
16:50 fllr akoumjian: How would I make salt do it?
16:51 akoumjian fllr: Let's start with how you would do it by hand. You need to add the key to the user's authorized_keys, have you done that part?
16:52 fllr akoumjian: Right. I usually just scp my key there, then cat the key >> authorized_keys
16:53 Shish (ssh-copy-id automates copy and append to authorized_keys, and does some other things like checking permissions)
16:53 akoumjian fllr: Okay, so what happens when you try to ssh in after placing the pubkey in authorized_keys?
16:54 niki joined #salt
16:55 fllr akoumjian: it just works.
16:59 fllr akoumjian: I think...?
16:59 akoumjian fllr: You tell me. :-)
16:59 baniir joined #salt
17:00 akoumjian fllr: If it is working properly, then all we need to do is use salt to describe the same process you used. I'm guessing first you created the user, then you placed the key in authorized_keys.
17:01 akoumjian fllr: That would mean probably one user.present state and one ssh_auth state
17:07 dahunter3 I'm was just about to select Chef for our environment when I bumped into Salt by accident. I'm really attracted to the idea that it uses Python instead of Ruby. I'm browsing the docs now, but perhaps someone could answer a few basic questions for me? Like, is Salt a push or pull technology?
17:09 dahunter3 Plus, it seems less Linux centric. The docs seem to reference FreeBSD more, which we utilize.
17:12 fllr akoumjian: Maybe what I'm trying to do is way too complicated? See... I wanna create this dev environment. But I also wanna deploy at aws. The default user at vagrant is vagrant, and at aws it's ubuntu. I figured if I just created one default user account for both, it'd be less of a headache =p
17:12 akoumjian fllr: No, that makes perfect sense. Is it not working to create the user and seed the key?
17:13 dahunter3 I'm also very curious about versioning. That is, how does Salt handle versions of salt states? If I make a new version of a state table do all minions automatically get that state table or is there a way to specify, these minions go ahead and use the new state table but everyone else keep on the old version.
17:15 fllr akoumjian: it creates the user fine. It's the seeding the key part that's confusing me... I guess I'll just leave things like this for now and come back to it later when I'm familiar with both tools
17:15 copelco joined #salt
17:15 akoumjian fllr: Have you seen this? http://docs.saltstack.com/ref/states/all/salt.states.ssh_auth.html#module-salt.states.ssh_auth
17:16 akoumjian fllr: If you use that and make sure to requrie the user.present state first, it should work fine
17:17 fllr akoumjian: I hadn't... Lemme take a look...
17:17 akoumjian dahunter3: Salt only alters minions when either the master or the minion decide to run a job (such as state.highstate, which puts a minion in compliance with the specified state tree)
17:18 dahunter3 akoumjian: Okay. That helps. But does the master specify the exact version the minion should run a specific version or just the latest?
17:19 akoumjian dahunter3: A version of the global state tree? No, and I'm not sure I would recommend doing it that way. You are probably better off figuring out why some minions should be running different configurations and splitting them out in your state tree.
17:20 akoumjian dahunter3: If what you want it rolling deployment, you can definitely do that though by running batch style commands from the salt master
17:22 fllr akoumjian: from that link you gave me: - source: salt://ssh_keys/thatch.id_rsa.pub how does salt:/ work?
17:23 alazylearner joined #salt
17:23 dahunter3 akoumjian: Right, the idea being sort of a trial or rolling deployment where it is sent out to a subset of all minions for final ascertainment of correctness.
17:23 hari_ joined #salt
17:24 akoumjian fllr: Salt has a built in file server (this is how it distributes salt state files, modules, etc to all the minions). Some state modules take advantage of though (like file.managed or ssh_auth) by letting you point to a source for a file
17:24 akoumjian fllr: on the salt file server. That file will exist relative to your salt file root (which is /srv/salt by default)
17:25 akoumjian So salt://myuser/id_rsa.pub will point to the file at /srv/salt/myuser/id_rsa.pub
17:26 akoumjian fllr: In the case of vagrant, you can see the example mounts a local folder to the guest os here: https://github.com/saltstack/salty-vagrant/blob/develop/example/masterless/Vagrantfile#L6
17:27 bemehow joined #salt
17:28 kenbolton joined #salt
17:28 akoumjian dahunter3: What you can do is version your salt directories using git. You can run state.highstate on a subset of minions using --batch or by targetting based on some other minion attribute. If you like what you see, you can use batch to continue the rolling deployment. if you don't like it, roll back the git version on your salt directories and rerun state.highstate on the minions you experimented with
17:30 akoumjian dahunter3: Actually I misspoke. The command option is not batch, but I know there is a command which will let you do that.
17:30 akoumjian dahunter3: It might be --number, not sure
17:32 fllr akoumjian: So, I could technically sync_folder my own .ssh folder into the vm, and then pass in my id_rsa.pub file into it. I think that'd work, right?
17:33 akoumjian fllr: You could, but that it wouldn't be reproducable on aws. Plus if you're syncing your .ssh folder you shouldn't need to pass in the pub key
17:34 akoumjian fllr: Take a look at some example salt setups http://saltstarters.org/
17:36 rfgarcia_ joined #salt
17:43 dahunter3 Completely unrelated poll type question: How are you guys aggregating your log files from amongst all your servers and is there a salt module for it?
17:56 rfgarcia joined #salt
17:57 efixit joined #salt
18:10 jaequery joined #salt
18:13 luminous dahunter3: logstash / graylog are pretty awesome
18:16 Nitron joined #salt
18:18 mikedawson joined #salt
18:20 baniir joined #salt
18:21 adfasdfasdf joined #salt
18:24 m0hit joined #salt
18:38 mikedawson joined #salt
18:43 baniir joined #salt
18:57 jkleckner joined #salt
18:59 lemao joined #salt
19:07 baniir joined #salt
19:15 bemehow joined #salt
19:17 fllr joined #salt
19:22 fllr joined #salt
19:22 oz_akan_ joined #salt
19:24 kleinishere joined #salt
19:31 rfgarcia joined #salt
19:36 jbunting joined #salt
19:39 robbyt joined #salt
19:57 berto- joined #salt
19:58 mikedawson joined #salt
20:05 fllr Hey guys, salt is telling me that this file cannot be found: /etc/postgresql/9.1/main/pg_hba.conf but I went down that folder, and the file is there. What's happening?
20:11 copec joined #salt
20:12 copec joined #salt
20:14 whit joined #salt
20:21 lemao joined #salt
20:25 drdran joined #salt
20:32 fllr joined #salt
20:34 quantumsummers|c joined #salt
20:36 mgw joined #salt
20:36 fllr Hey guys, I asked salt to watch this file for me, but it's is telling me that the file cannot be found: /etc/postgresql/9.1/main/pg_hba.conf I went to that folder, and the file is there. What's happening?
20:38 nrub joined #salt
20:43 fllr joined #salt
20:44 mgw joined #salt
20:45 niki joined #salt
20:45 mgw joined #salt
20:47 mgw joined #salt
20:48 mgw joined #salt
20:49 mgw joined #salt
20:55 jbunting joined #salt
20:56 mgw joined #salt
20:57 mgw joined #salt
21:04 baniir joined #salt
21:09 luminous fllr: it sounds like you are a little confused with the details
21:09 oliv_mc joined #salt
21:09 luminous first, is this config file managed in salt? do you have a file.managed state defined for it?
21:10 luminous maybe you can post the related offending snippets to dpaste or another pastebin?
21:15 jessep joined #salt
21:20 henk AFAICT salt simply continues when it cannot find an included module without a warning or an error. Is that correct? If so, does anyone know why that is? It basically means that I have to double-check every module manually because I’ll never know if salt found it and applied it, does it not?
21:21 Jarus Hi, is it possible to get pillar data for the host over a python api?
21:23 niki joined #salt
21:27 luminous Jarus: retrieve pillar data for a given host, as seen by salt?
21:28 luminous henk: more specifically, what are you concerned about missing, could you give an example?
21:28 Jarus luminous, yes
21:28 Jarus I want to run a script on a host which get some config vars from pillar
21:29 luminous Jarus: as I understand the details, if you had a salt module that ran on the minion (or master), yes.. but not from another node
21:29 luminous Jarus: you would probably be better to put pillar in another datastore, giving salt access through ext_pillar, and have your script access it as needed that way
21:30 luminous pillar is seen as containing somewhat sensitive, minion-only data, so it's not likely to do what you want directly via an api
21:32 Jarus yes but maybe I want to run a cron job on a salt minion host which need some sensitive config values it would be nice to get this values
21:32 jessep joined #salt
21:32 luminous Jarus: if you are talking about a minion accessing its own data, then yes, and that should be relatively easy
21:33 luminous but you would do so (at least I believe so) with a salt module that runs on the minion
21:33 luminous you could likely then run that module with salt's built-in cron support even..
21:33 luminous that should work quite nicely
21:34 Jarus yes this could solve my problem
21:34 luminous salt modules are really simple to
21:34 luminous *too
21:34 Vekz joined #salt
21:34 Jarus is there a api which I can ask give me the value of key xyz for my current host?
21:35 Vekz @akoumjian: I'm trying to do vagrant up with salty-vagrant and getting: Calling state.highstate... (this may take a while) The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!  salt-call saltutil.sync_all
21:35 Vekz akoumjian: any ideas?
21:35 luminous Jarus: yea, modules have access to the dataa structure directly, I believe. your best bet is to crack open some modules in github to see
21:36 luminous Vekz: can you ssh to that vm?
21:36 Vekz luminous: yes
21:36 luminous or otherwise run that command manually
21:37 Jarus luminous, okay but only modules have this access or is there also something like: import salt.pillar, salt.pillar.get('my_key') outside of the salt module context?
21:37 dthom91 joined #salt
21:37 kleinishere joined #salt
21:37 luminous Jarus: no, I do not believe so. how would salt validate the request?
21:38 luminous you've got to be in a _salt_ module on the minion, to get access to all the salt goodies - like authentication and integrity of communications
21:38 Jarus luminous, the salt minion could create a local socket and the python api connect to this socket and request the data
21:38 kleinishere joined #salt
21:38 Vekz luminous: I sshed into the box and got vagrant@precise64:~$ sudo salt-call saltutil.sync_all [INFO    ] Configuration file path: /etc/salt/minion Minion failed to authenticate with the master, has the minion key been accepted?
21:38 luminous Jarus: just create a module that uses your code as a library or some such, way simpler and cleanrer
21:39 henk luminous: http://pastie.org/8097976 There is no module 'bar' but salt will not give any warning about that AFAICT.
21:39 luminous Jarus: again, you want to use salt's internal cron, which would "call" that module
21:39 Vekz The configuration file path is suspicious because thats not what I specified in my Vagrantfile
21:39 Jarus luminous okay =)
21:39 luminous Vekz: so there you go
21:39 Jarus luminous, thanks for you help
21:40 luminous ;)
21:40 niki joined #salt
21:40 Vekz luminous: That dosen't help me.
21:41 Vekz The paths are different but the files content is the same
21:41 luminous what's salt-key got to say?
21:42 luminous what's the minion log say?
21:42 luminous restart the minion service annd watch the log
21:42 luminous that should provide you with some info
21:43 luminous in other words, it seems like your problem is (at least at this stage of debugging) notvagrant-specific, you're in normal "minion can't communicate with master" land
21:46 luminous henk: I forget, specifically, but salt is not the best with these types of error/warnings. I think you get something, but maybe not enough. there are a few tickets for variations on this topic
21:47 kleinishere joined #salt
21:48 Vekz ok looks like I forgoet the file_client:local
21:48 henk luminous: oh ok, thanks
21:48 Vekz derp
21:50 luminous :)
21:51 copelco joined #salt
21:57 kcb joined #salt
22:01 henk luminous: hm, can’t really find any …
22:06 Jahkeup_ joined #salt
22:09 luminous henk: there are various tickets related to crappy error/warning reporting coming from salt. take your pick.. maybe not this worded in the way you would.. but then you are free to submit your own
22:09 luminous either way..  saltstack has been slow to address/fix this type of issue, so submit a pull request if you want it now, else write up a ticket and wait
22:12 henk ah, got you, thanks
22:15 kleinishere joined #salt
22:16 rglauser joined #salt
22:18 akoumjian Vekz: Your minion config needs to set file_client: local
22:18 akoumjian Vekz: Ah, I see you found that :-)
22:19 Vekz yeah had client spelled cilent
22:19 Vekz raged for awhile
22:19 akoumjian Yep, that'll happen
22:21 Xeago joined #salt
22:22 Vekz If i'm using salt to install apt-get packages and i'm getting prompted for input from apt-get like `press enter` how do I handle that in my sls files?
22:25 Vekz looks like theres a -y flag to pass to answer yes
22:26 Vekz has anyone installed Docker.io with salt and has a sls file for me?
22:27 rjc joined #salt
22:29 fllr Hey guys, I asked salt to watch this file for me, but it's is telling me that the file cannot be found: /etc/postgresql/9.1/main/pg_hba.conf I went to that folder, and the file is there. What's happening?
22:31 fllr luminous: I just got your comments about your issues. Can you still help me out?
22:35 akoumjian fllr: watch is a "requisite statement". When you watch something, you are watching another state. ie: you can watch a file.managed state, and if when executed, the file.managed state reports changes, whatever is watching it will know about it and be able to react to it.
22:35 akoumjian fllr: ie; a service.running state watching a file.managed state will restart is file.managed changed the file being managed
22:37 akoumjian fllr: So in order to watch a file for changes, you need to set up a file.managed state for that file, then the state is what you are watching. But to be clear, it won't watch the file all the time, like a service. It will only watch the state, to see if any changes are made when the state is applied
22:37 adotbrown joined #salt
22:37 renoirb joined #salt
22:38 alazylearner joined #salt
22:52 fllr akoumjian: I was following a tutorial, though. https://gist.github.com/anonymous/5897323 here's a gist of what I have with the error message included
22:53 akoumjian fllr: It should be "watch: file" not "watch: files" (plural)
22:53 renoirb_ joined #salt
22:53 akoumjian fllr: "file" is the name of the state module
22:56 fllr Oooooh! Worked! :) Thanks, bro!
22:57 koolhead17 joined #salt
22:58 inso joined #salt
22:58 bemehow joined #salt
22:59 bemehow_ joined #salt
23:02 taotetek joined #salt
23:08 ajw0100 joined #salt
23:13 akoumjian fllr: sweet!
23:18 javl joined #salt
23:22 kleinishere joined #salt
23:23 sciyoshi1 joined #salt
23:23 robbyt joined #salt
23:25 shiznit joined #salt
23:29 adotbrown joined #salt
23:39 cxz joined #salt
23:42 ferai joined #salt
23:51 renoirb_ joined #salt
23:56 efixit joined #salt
23:58 rfgarcia joined #salt

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