Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-06-02

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

All times shown according to UTC.

Time Nick Message
00:00 bhosmer joined #salt
00:19 bemehow joined #salt
00:46 ogrisel joined #salt
00:47 aat joined #salt
01:29 favadi joined #salt
01:37 taotetek joined #salt
01:41 bhosmer joined #salt
01:44 omgparticle joined #salt
01:47 bemehow joined #salt
01:50 ogrisel joined #salt
02:04 baniir joined #salt
02:06 Divining joined #salt
02:28 bemehow joined #salt
02:31 nrub joined #salt
02:32 aat joined #salt
02:50 ogrisel joined #salt
02:58 sgviking joined #salt
03:01 kmwhite joined #salt
03:09 sgviking joined #salt
03:14 raydeo joined #salt
03:21 UtahDave joined #salt
03:31 jrgifford_ joined #salt
03:35 KyleG joined #salt
03:42 baniir joined #salt
03:51 ogrisel joined #salt
03:54 kmwhite joined #salt
03:59 melinath joined #salt
04:03 bemehow joined #salt
04:09 lvicks joined #salt
04:11 opapo joined #salt
04:13 auser joined #salt
04:16 auser hey all
04:23 koolhead17 joined #salt
04:23 koolhead17 joined #salt
04:26 spudbook joined #salt
04:29 nrub_ joined #salt
04:29 nrub__ joined #salt
04:35 efixit joined #salt
04:37 axisys joined #salt
04:43 bemehow joined #salt
04:51 ogrisel joined #salt
04:54 benspaulding joined #salt
05:47 yumike joined #salt
05:47 yumike joined #salt
05:48 yumike joined #salt
05:52 ogrisel joined #salt
06:07 SpX joined #salt
06:08 xinkeT joined #salt
06:10 lvicks joined #salt
06:10 balltongu joined #salt
06:11 mjmac joined #salt
06:11 __number5__ joined #salt
06:13 Gareth joined #salt
06:16 zloidemon joined #salt
06:16 jasonrm joined #salt
06:17 tamentis joined #salt
06:17 ogrisel joined #salt
06:17 Damianz joined #salt
06:18 lineman60 joined #salt
06:18 ahammond joined #salt
06:18 seubert joined #salt
06:18 entil joined #salt
06:19 [ilin] joined #salt
06:19 brutasse joined #salt
06:20 echohead joined #salt
06:20 anteaya joined #salt
06:21 copec joined #salt
06:21 FreeSpencer joined #salt
06:21 crashmag joined #salt
06:21 chuffpdx joined #salt
06:21 greghaynes joined #salt
06:30 [ilin] joined #salt
06:31 gadams_ joined #salt
06:32 [ilin] joined #salt
06:49 FreeSpencer joined #salt
06:49 chuffpdx joined #salt
06:49 greghaynes joined #salt
07:11 lvicks joined #salt
07:22 nrub_ joined #salt
07:36 s0undt3ch joined #salt
07:51 tharkun joined #salt
07:51 tharkun joined #salt
08:00 axisys joined #salt
08:01 copec joined #salt
08:06 favadi joined #salt
08:08 crashmag joined #salt
08:10 SpX joined #salt
08:19 copec joined #salt
08:19 ogrisel joined #salt
08:21 sgviking joined #salt
08:30 aboe joined #salt
08:46 entil found a new (though slight) issue with salt-master. if ~/.ssh/config defines LogLevel DEBUG for Host github.com the gitfs backend will fail
08:49 entil it checks for len() on the output pretty blindly, that'll fail because debug has more output
08:49 entil and there's a bug in the documentation. the key does not have to be called id_rsa if ~/.ssh/config defines a custom keyfile for github (which I always do, with the debug)
08:56 ggoZ joined #salt
08:58 jts` left #salt
09:04 tharkun joined #salt
09:04 tharkun joined #salt
09:04 Furao joined #salt
09:39 ogrisel joined #salt
09:57 favadi joined #salt
10:07 auser joined #salt
10:28 bhosmer joined #salt
10:39 ogrisel joined #salt
10:52 Ivo joined #salt
10:53 entil this is crazy.. I do saltutil.sync_all on a new ec2 instance and registering the grain tells me I'm not authorized (with aws) but when I restart the minion, it starts working
11:12 lvicks joined #salt
11:18 azbarcea joined #salt
11:20 zooz joined #salt
11:25 Ivo joined #salt
11:25 koolhead17 joined #salt
11:25 koolhead17 joined #salt
11:30 taotetek joined #salt
11:38 jeddi entil: the loglevel debug stuff for ssh - could you file an issue?
11:40 ogrisel joined #salt
11:44 entil umm, sure, in a moment, I'm still fighting with the ec2 issue, that aws is allegedly not authenticated
11:45 entil I think maybe I can hack it with service.restart salt-minion and if it's that easy, then I can look into an issue
11:52 entil jeddi: are you like a salt developer or something btw?
11:53 entil because now I got even more issues. grains.ls lists me the custom grains, even the previously failing one with ec2 (both grains .py files are about ec2) - and running salt says "ec2_tags" is not available
11:53 entil oh lol sorry, that was my bad
11:54 entil stare at problems for long enough and go blind :P
12:05 ronc joined #salt
12:10 backjlack joined #salt
12:11 entil jeddi: https://github.com/saltstack/salt/issues/5372 there ya go
12:32 Furao_ joined #salt
12:33 z3uS joined #salt
12:38 jeddi entil: i'm in the 'something' category.  :)   no, a bit of a salt newbie myself.
12:38 entil hehe
12:38 jeddi on the weekend i fill in for the official people that say 'could you please file a bug report of that'
12:39 jeddi the pay's a bit crap.
12:39 entil well, I'm just happy that despite the obstacles (half of which are code blindness caused by not taking enough breaks) I got my own grain going
12:39 jeddi i guess the theory is that no one runs debug level ssh logging.  :)
12:40 entil gonna take a longer break (or maybe until tomorrow) and see how I can map those something concrete, like doing virtualenv pip installs
12:40 jeddi i ended up pushing grains out semi-manually, but haven't worked out how to do that nicely (for my stuff) with salt cloud to rackspace boxes.
12:40 entil I do for programmatical stuff, it's kinda useless for shells
12:40 ogrisel joined #salt
12:40 jeddi certainly i can empathise with the stare at something long enough and eventually it will make even less sense phenomenon.
12:41 entil but I need to do states (or pillars?) that do some sort of includes based on what the ec2 tags have, and they switch users and virtualenvs and do installs and configure postfix and do all the stuff salt is supposed to be good for
12:42 entil after that I need to figure out where to store the requirements.txt files :P the one thing that would be harder than anything is to use salt for desktops etc where the need is not the same as in production. so I may have to solve that totally separately (s3, mounted at the office?) and have salt talk to those
12:43 entil but now I need food, just thinking out loud on irc makes me faint, cya ->
12:49 zooz how do I target minions based on puppet fact value?
12:54 mgw joined #salt
13:02 felixhummel joined #salt
13:08 efixit1 joined #salt
13:10 SpX joined #salt
13:13 alekibango joined #salt
13:24 bhosmer joined #salt
13:27 koolhead17 joined #salt
13:27 koolhead17 joined #salt
13:35 avn joined #salt
13:39 ronc joined #salt
13:40 ogrisel joined #salt
13:49 SpX joined #salt
13:51 faust joined #salt
13:58 milind joined #salt
14:01 faust joined #salt
14:10 mgw joined #salt
14:20 bhosmer joined #salt
14:28 aat joined #salt
14:32 SpX joined #salt
14:40 Newt[cz] joined #salt
14:41 ogrisel joined #salt
14:46 aat joined #salt
15:03 jkleckner joined #salt
15:07 baniir joined #salt
15:10 ronc joined #salt
15:17 johnny joined #salt
15:20 Guest91064 New to salt and configuration managment in general, and have a quick question. I currently have one server which I would like to use salt to configure, but I know that down the line I would also like to use that server as a salt master. What is the best way for me to configure this server? Is it to set it up as a headless minon for config, then manually switch it to a server, or is there a way to run a master and minion safely on th
15:22 Guest91064 *masterless minion, not headless
15:22 carlos joined #salt
15:22 danielbachhuber joined #salt
15:24 ska joined #salt
15:24 ska joined #salt
15:36 aat joined #salt
15:41 ogrisel joined #salt
15:50 Furao Guest91064: salt-call
15:51 Guest91064 I can just setup a master with salt-call, no need for a minion on the same server?
15:52 badmeischter joined #salt
15:52 favadi joined #salt
15:54 joshe why would you not want to have a minion running on the master?
15:54 Furao joined #salt
15:56 Guest91064 I don't have a preference, I am just asking what the approach is, given my current and future needs. My question was more for clarification than preference.
15:57 avn joshe: salt-call --local 'master' salt.highstate to bootstrap master?
15:58 Guest91064 If setting up and master and minion on the same server is the way to go, then I can do that. That seems like the most straightforward approach, but I wasn't sure if that was appropriate, as the documention talks about the minion being a different machine.
15:59 raz Guest91064: master/minion on same host is perfectly fine and even desirable (that way you can easily salt-up a new master if you ever want one)
16:01 entil I'm considering having a minion on the master to manage some of the other stuff running on the same box. at least maybe.
16:02 avn as I understand -- one 'pro' for master/minion on same host at least allow "document" master configuration as state
16:02 Guest91064 raz: Thanks! So for configuring the server initially, I would need to install salt master and minion, then copy my config to the master and have it push to the minion (same machine) or would it be better to use salt-call on the minion for the initial deployment?
16:03 raz Guest91064: not sure what you're getting at. you can just install master/minion on the same host in the same way as if it was two different hosts. :)
16:04 entil do the minions get all the default modules? because (if I'm getting this correctly) salt-call is useless unless it's got the modules from the master first
16:04 badmeischter left #salt
16:04 sashka_u1 hehehhe. 0.15.3. is out
16:06 badmeischter joined #salt
16:08 Guest91064 raz: I know I can install them both on the same machine (thanks to you!). My question is whether it is better to push my initial configuration of the server using salt-call as Furao suggested, or it if would be better to push the changes from the master to the minion as I would if there were different machines. I'm leaning toward that latter, but just want to confirm as I am very green.
16:08 abe_music joined #salt
16:08 raz Guest91064: shouldn't make a difference imho
16:09 avn guys, I planning to manage few groups of hosts (each group bound to specific project, with custom built software). I have few question -- what the best way to keep project specific state in their own gits, and how to deploy custom built software with salt (if it possible of course)
16:14 dthom91 joined #salt
16:15 bemehow joined #salt
16:15 entil avn: I have something slightly similar. I keep my grains in gitfs, along with two shell scripts for bootstrapping.
16:16 entil the setup is obviously far from complete and I started doing other stuff :P
16:23 Chucky_ joined #salt
16:24 avn entil: own gitfs for each project?
16:24 ZenoTasedro joined #salt
16:25 entil avn: so far it's one gitfs for the salt setup itself. I haven't solved specific project requirements yet, though I know I'll use ec2 tags for them
16:25 entil we use a ton of different django apps in different combinations and so far have been keeping the requirements in regular trad. requirements.txt files *per django project or app* and that's a huge mess (everyone who's done it knows it)
16:26 spudbook joined #salt
16:26 entil one of the things I want to get done is uncouple requirements from packages because it's obvious nothing is up for the task (pip or distribute or anything, they all suck)
16:26 abe_music left #salt
16:26 avn entil: I should build in-house solution. I plan to have global /srv/salt (maybe on gitfs), and per-project pillars
16:27 entil I could call them like foo_production or bar_staging and have them mapped to (like you say) pillars that provide per-environment requirements.txt files
16:27 entil pip can work with those
16:27 avn entil: I want to utilize heroku builder for custom software (it opensource)
16:27 entil then any dev can just clone the salt stuff and use pip on the files provided in the gitfs repo, and update them if necessary
16:28 entil dunno if that'll work out but it's the best I got so far. the other option is to uncouple the requirements from the conf manager by having two gitfs remotes
16:28 avn heh, not all our software are pythonic (sadness ;)
16:29 entil dunno how other environments deal with this. but I'd expect the abstract case to be the same for a lot of web apps. the one we see is having an app (call it foo) and its db (call it foodb) and a slightly tweaked django admin interface (call it fooadmin) and we need different reqs for the web app and the admin
16:29 entil I can't believe a case like that is dependant on the language or framework itself, as long as it provides that architecture
16:41 ogrisel joined #salt
16:52 jeddi joined #salt
17:06 auser joined #salt
17:08 mgw joined #salt
17:19 entil so pillar cannot be had in gitfs, https://github.com/saltstack/salt/issues/3745
17:19 entil :(
17:21 ogrisel joined #salt
17:44 badmeischter left #salt
17:50 axisys joined #salt
17:52 bemehow joined #salt
17:55 Lionel_Debroux joined #salt
17:57 aleszoulek joined #salt
18:02 dthom91 joined #salt
18:15 robertkeizer joined #salt
18:17 s2r2 hmm gitfs. interesting.
18:18 m_george left #salt
18:24 milind joined #salt
18:27 bemehow joined #salt
18:32 druonysus joined #salt
18:32 druonysus joined #salt
18:34 aorist joined #salt
18:35 aat joined #salt
18:52 druonysuse joined #salt
18:59 koolhead17 joined #salt
18:59 koolhead17 joined #salt
19:09 baniir joined #salt
19:11 jeddi joined #salt
19:16 nrub joined #salt
19:20 ggoZ joined #salt
19:34 dthom91 joined #salt
19:37 ogrisel joined #salt
19:40 nobody_ joined #salt
19:42 Crazybus joined #salt
19:43 nobody_ Is there a possibility to implement a custom python module accessible when rendering jinja templates? (e.g. something along having foobar.py in _modules and accesssing it with {{ foobar.baz }} from a template)
19:44 aleszoulek nobody_:  {{ salt['cmd.run']('date') }} ?
19:44 aleszoulek nobody_: state jinja templates have access to pillar, grains, salt (=modules) in a context
19:45 mnemonikk joined #salt
19:50 keith4 joined #salt
19:52 nobody_ aleszoulek: can I get data from that module that way?
20:07 jeddi joined #salt
20:13 Newt[cz] joined #salt
20:18 it_dude joined #salt
20:28 mgw joined #salt
20:32 mnemonikk joined #salt
20:35 robertkeizer left #salt
20:37 nkuttler oh wow i really don't like the docs template :( the old look was much more readable for me
20:41 Charatna joined #salt
20:43 Charatna left #salt
20:50 ronc joined #salt
20:51 it_dude joined #salt
21:13 krissaxton joined #salt
21:15 bemehow joined #salt
21:17 auser joined #salt
21:19 LarsN when installing salt-master on ubuntu using apt & the ppa, where does salt actually get installed?
21:20 mgw joined #salt
21:21 LarsN /usr/share/pyshared/salt it looks like.
21:38 ogrisel joined #salt
21:45 raydeo joined #salt
21:54 bensix joined #salt
21:55 maxleonca joined #salt
21:55 maxleonca Hello
21:55 maxleonca Anyone can spare a couple of minutes to clear out a doubt?
21:56 maxleonca I'm having trouble with the file.recurse state, the odd part is that when it fails it does list the files on the master and then says not found. the only odd thing is that is showing a pipe character before the actual folder.
21:58 mgw joined #salt
22:00 dthom91 This was a known defect, I think in the 0.15. release. Not sure what the fix status is
22:00 dthom91 Ran into it myself, which caused me to roll back to 0.14
22:01 maxleonca Hmmm, thanks a lot.  It was driving me crazy
22:02 Gareth joined #salt
22:02 dthom91 me too, I messed with it for several hours before I asked on here and got confirmation that it's a bug
22:02 tharkun joined #salt
22:02 tharkun joined #salt
22:04 maxleonca damn, I just checked and I'm running master at 0.11
22:05 maxleonca hmm and the problematic host is at 0.15.1
22:05 maxleonca I need to check versions
22:05 maxleonca I'll post if the problem is caused by the mistmatch of versions
22:15 Ryan_Lane joined #salt
22:34 aleszoulek nobody_: Sure.. it's jinja call, so you can assign them with {% set %} or cycle them
22:37 abe_music joined #salt
22:37 valberg joined #salt
22:38 krissaxton joined #salt
22:38 ogrisel joined #salt
22:40 waldo323 joined #salt
22:41 [ilin] joined #salt
22:43 mgw joined #salt
22:47 efixit joined #salt
22:49 lvicks joined #salt
22:56 Heartsbane joined #salt
22:56 Heartsbane joined #salt
23:01 aat joined #salt
23:09 adotbrown joined #salt
23:11 tamentis joined #salt
23:16 alexl joined #salt
23:17 napperjabber joined #salt
23:24 cxz joined #salt
23:25 cxz joined #salt
23:36 nrub joined #salt
23:39 ogrisel joined #salt
23:43 krissaxton joined #salt
23:54 adotbrown joined #salt
23:56 Kzim joined #salt
23:56 Kzim hi
23:58 Kzim i have a file, say /etc/myvalue that contain data about the minion so i assume i can include them in Salt with Grains. but those values can change. but i still need to have them localy. do i have to refresh grains in some way ? is there some sort of local pillar ? thx

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