Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-08-16

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

All times shown according to UTC.

Time Nick Message
00:04 whit joined #salt
00:07 cxz can someone tell me why my salt module isn't loading?
00:07 cxz i have it in /srv/salt/myenv/_modules/mynetwork.py
00:08 cxz then i get this: "mynetwork.dig" is not available.
00:08 UtahDave cxz: did you run salt \* saltutil.sync_modules?
00:08 cxz yeh
00:09 cxz i did
00:09 cxz it's odd cos i can see it in the minion cache
00:09 cxz and if i put in a syntax error python clearly returns it with salt
00:09 cxz but when it obviously runs fine, it's being 'not loaded'
00:09 cxz or 'not available'
00:09 cxz i also have the __virtual__ function returning the proper name
00:10 UtahDave what's the virtual function look like
00:11 cxz http://pastebin.com/mtq5LHqp
00:11 cxz my main issue is that i'm basically using this module to do network.dig but using +short passed to dig
00:11 cxz the problem with the salt provided network module shows up when u dont have dig installed
00:11 cxz and even if u did
00:11 cxz i just want to resolve some addr to an A record
00:11 cxz i don't need all the ridiculous dig outpu
00:11 hazzadous joined #salt
00:11 cxz output*
00:13 juanlittledevil joined #salt
00:15 UtahDave gotcha
00:15 UtahDave try using  salt.utils.is_windows()  to test for Windows
00:16 cxz can i just remove everything
00:16 cxz i'll never use a windows system
00:16 cxz with salt anyway
00:16 cxz it also doesn't work without the virtual function
00:17 UtahDave cxz: OK, startup your minion in the foreground in debug mode.      salt-minion -l debug
00:17 UtahDave you should see if your module got loaded or not
00:17 cxz ok cool
00:19 MaxK joined #salt
00:21 cxz import salt.utils.socket_util
00:21 cxz ImportError: No module named socket_util
00:21 cxz so it looks like i can't use that
00:21 cxz let me see
00:22 cxz think i copied over an old file ;)
00:22 UtahDave there you go.
00:22 UtahDave That's a great way to troubleshoot that kind of thing
00:25 cxz cool
00:25 cxz i have one question though
00:25 cxz why do some network modules actually just call to commands
00:25 cxz some of which clearly wont exist
00:25 cxz like dig for instance
00:26 cxz if u use it in a jinja template you then need a state that needs require dnsutils for example
00:26 cxz that's not obvious IMO
00:26 cxz someone would need to drill down into the source to know that
00:26 dthom91 joined #salt
00:27 UtahDave Salt tries to be explicit about what it's going to install and not just install things automatically for you
00:27 cxz i recognize that
00:27 cxz that's not my question/statement
00:28 cxz i'm saying why doesn't it implement dig functionality natively
00:28 cxz or some kind of resolve-host natively
00:28 cxz it's not entirely obvious that network.dig is going to require dig installed
00:28 jacksontj joined #salt
00:28 cxz maybe if it was redis.somefunc
00:28 cxz you would know that redis needs installing
00:29 cxz but network implies system wide functionality
00:29 UtahDave that's true.
00:29 kstaken joined #salt
00:33 Ryan_Lane joined #salt
00:35 oz_akan_ joined #salt
00:36 dave_den cxz: yeah, network.dig should test for the dig command, or even better should be removed and replaced with a python native dns query function
00:37 baniir joined #salt
00:37 cxz yeh
00:38 cxz or just have another function called network.dnsq
00:38 dave_den right
00:41 Politoed joined #salt
00:45 oz_akan_ joined #salt
00:51 intchanter joined #salt
01:01 mannyt joined #salt
01:04 Jahkeup joined #salt
01:06 joehoyle Is it possible to only allow certain minions to be accessed with client_acl ?
01:15 Nexpro1 joined #salt
01:16 dthom91 joined #salt
01:17 oz_akan_ joined #salt
01:18 andrew__ joined #salt
01:18 zonk1024 joined #salt
01:22 m_george|away joined #salt
01:22 m_george left #salt
01:22 bdf hmm, so is user.present state working for anyone else in 0.16.3 in freebsd?
01:22 bdf I keep getting TypeError: Invalid keyword argument(s): {'createhome': True}
01:30 bdf pwd
01:30 bdf ls
01:30 bdf oops
01:35 jaequery joined #salt
01:45 Lue_4911 joined #salt
01:45 bdf hmm. so the sha256 of https://pypi.python.org/packages/source/s/salt/salt-0.16.3.tar.gz and the tarball of what is tagged in github as v0.16.3 differ
01:49 kermit joined #salt
01:58 mgw joined #salt
02:05 malinoff joined #salt
02:06 lemao joined #salt
02:13 xl1 joined #salt
02:14 oz_akan_ joined #salt
02:15 mannyt joined #salt
02:15 jaequery joined #salt
02:27 aat joined #salt
02:28 Lue_4911 joined #salt
02:33 oz_akan_ joined #salt
02:36 liuyq joined #salt
02:37 liuyq joined #salt
02:44 aat joined #salt
02:45 liuyq joined #salt
02:51 robertkeizer joined #salt
02:54 redbeard2 joined #salt
03:04 jaequery joined #salt
03:10 Nexpro1 joined #salt
03:11 whit joined #salt
03:11 Jahkeup joined #salt
03:13 dthom91 joined #salt
03:14 nonuby joined #salt
03:17 rberger joined #salt
03:17 nonuby when using   pkg.installed in an sls does pkg.installed always refer to the root key?
03:17 cewood joined #salt
03:26 saurabhs joined #salt
03:30 suodla joined #salt
03:44 Corey nonuby: "root key?"
03:45 nonuby just adapting to it, makes sense now, was expecting like meta-name:\npkg.installed:\n- vim\n -nano etc..
03:49 mgw joined #salt
03:51 backjlack joined #salt
03:54 malinoff Hi all. Can i somehow use pkgrepo module to install yum repository from an rpm file?
04:08 stevetodd joined #salt
04:10 UtahDave joined #salt
04:17 Jahkeup joined #salt
04:19 mwillhite joined #salt
04:29 alunduil joined #salt
04:31 waverider joined #salt
04:38 carmony joined #salt
04:43 jaequery joined #salt
04:50 renothing joined #salt
04:51 oz_akan_ joined #salt
05:01 z3uS I'm looking for a linux sysadmin in the Bay Area... SaltStack experience is a MAJOR plus!
05:01 z3uS http://hire.jobvite.com/Jobvite/Job.aspx?b=nFEM1lwW&j=owWKXfwT
05:01 z3uS drop me a /msg if you're seriously interested
05:01 z3uS need me a semi-experienced PFY
05:01 z3uS ;)
05:02 Corey *snicker*
05:02 Corey z3uS: By which you mean "junior admin."
05:03 z3uS we'll take a senior if the experience is right
05:03 z3uS need a damn good linux admin when it comes down to it
05:03 z3uS they're my direct report
05:04 z3uS and I have no problem hiring someone smarter then me but I'm an old linux fogey with a recent background in hadoop and cassandra and big data, I'm just building a team out now at this new place :)
05:04 z3uS and fuck running shit like ruby as root (al la chef/puppet "yeah yeah I know they're DSL's but thats even worse)
05:04 z3uS found saltstack and we're a python shop
05:04 z3uS so even better
05:04 alunduil joined #salt
05:04 z3uS alas I digress
05:06 jkleckner joined #salt
05:07 malinoff z3uS: in my company, we are looking for linux admins too. 9 of 10 guys can't even answer the question: "What does the command 'uname [some_option]'?"
05:08 z3uS oh god
05:08 z3uS hah
05:08 malinoff yep
05:08 z3uS being in the bay I have to compete with Google/Apple and all the other big players
05:08 z3uS but at least there are a lot of candidates out here
05:09 evilNirvana yo z3uS ;)
05:10 z3uS sup evilNirvana
05:10 z3uS :D
05:11 middleman_ joined #salt
05:15 stevetodd joined #salt
05:15 mgw joined #salt
05:17 jkleckner joined #salt
05:18 jY z3uS: you guys using headhunters?
05:19 z3uS yes
05:19 Jahkeup joined #salt
05:19 z3uS we do
05:19 z3uS :)
05:19 jY i think i got contacted via linkedin about that
05:19 jY small world
05:19 z3uS hahaha, nice! :D
05:19 z3uS I didn't know our HR had turned over this role to HH yet
05:19 z3uS I had just got it posted recently
05:19 z3uS thats good shit though
05:20 z3uS and yeah small world
05:20 Corey Sounds like it'd be fun.
05:20 EugeneKay I'm not Bay Area currently, but I've been there before. I probably charge way too much though :-p
05:20 jY i've almost given up trying to find people in SF.. trying to convince my boss to let people work remote
05:20 jY EugeneKay: ahh i doubt it.. you'd be surprised
05:21 Corey My company is based out of San Jose.
05:21 Corey I'm based out of anywhere United flies. :-p
05:21 Gifflen joined #salt
05:22 EugeneKay I currently charge $5k/week to fly out, plus expenses, and that's a discount. So no, I wouldn't be.
05:22 jY you think $5k is a lot?
05:22 EugeneKay For 6-hour days, yeah. :-p
05:22 jY i wont tell you what we paid an ex paypal guy to help us architect
05:22 jY hardly a lot
05:23 EugeneKay It's more than "an sysadmin"
05:23 z3uS we pay market rates, its easy to live in SF if you work here in the tech industry
05:23 EugeneKay I know what $ARCHITECT positions cost; the work is annoying.
05:23 jY ya that's not a lot for contract work
05:23 z3uS contract is diff then staff for sure
05:23 z3uS esp. around the bay
05:23 z3uS in pay rates
05:24 Corey I kinda get to play the best of all worlds; I'm an employee of a company that hires me out as a consultant to their clients.
05:24 EugeneKay Yup.
05:24 EugeneKay I run my own company. Good fun.
05:24 z3uS Corey: I usually use those kind of companies for IT
05:24 EugeneKay I like the travel currently, but I know I'll hate it within ay ear.
05:24 Corey z3uS: Yeah, we're Taos.
05:24 z3uS EugeneKay: did that years ago, sold it, moved to new zealand, had a blast... I'm done with the company running stuff
05:24 z3uS put me on an exec. team and I'll be happy
05:25 EugeneKay Fun!
05:25 z3uS for sure! .nz rocks
05:25 EugeneKay Never been, but everything I've seen on the internet is beautiful.
05:25 EugeneKay I'm sure I'll be there eventually.
05:25 EugeneKay Anyway..... bedtimeish
05:25 z3uS yeah me too
05:25 EugeneKay Hope you find somebody good
05:25 z3uS last day of cassandra training tomorrow
05:26 z3uS thanks man!
05:26 Corey Might email the list, z3uS
05:26 z3uS have a good night
05:26 z3uS corey: great!
05:26 Corey z3uS: As in, "you should email the list." :-)
05:26 z3uS yeah
05:27 z3uS will do early next week, gotta wrap a few things up tomorrow and this weekend
05:30 xl joined #salt
05:30 jkleckner joined #salt
05:37 xl joined #salt
06:02 oz_akan_ joined #salt
06:03 mechanicalduck joined #salt
06:06 xl joined #salt
06:25 waverider joined #salt
06:28 y0j joined #salt
06:31 jkleckner1 joined #salt
06:34 jkleckner joined #salt
06:42 jkleckner1 joined #salt
06:54 BbT0n joined #salt
06:55 balboah joined #salt
07:03 mechanicalduck_ joined #salt
07:06 vaxholm joined #salt
07:21 malinoff How can i clear mine content?
07:22 scott_w joined #salt
07:22 Furao malinoff: http://docs.saltstack.com/ref/modules/all/salt.modules.mine.html#salt.modules.mine.update
07:22 Furao clear=True
07:23 * goodwill slaps whiteinge
07:24 malinoff Furao: thanks. Am i right, there's no abitily to exclude one piece of the data?
07:24 ml_1 joined #salt
07:26 Furao malinoff: I don't think, but I didn't looked deeply into mine code
07:27 ramesh joined #salt
07:28 malinoff Furao, ok, thanks. Anyway mine is awesome :)
07:30 mechanicalduck joined #salt
07:31 xl1 joined #salt
07:32 malinoff joined #salt
07:32 Furao yeah it's great, more helpful than publish.publish + grains || pillars
07:35 malinoff You know, this is the first time i see such fast, obvious and simple module to statically distribute dynamic content, such as ip of newly created node (in words of deployment tools, ofc)
07:38 Ryan_Lane joined #salt
07:41 Furao and as you it's so easy to write module, it's great to perform custom tasks, such as cluster nodes auto-discovery
07:45 ml_1 joined #salt
07:47 malinoff Yeah, that's awesome! :)
07:48 malinoff I have no words to say how i like salt
07:48 malinoff every task i want to do is there already, i just need to specify a small yaml
07:52 Ixan hi, has anyone worked on support for aix?
07:52 dthom91 joined #salt
07:52 Furao Ixan: search the google groups, there was a discussion on that a few days ago.
07:52 Furao short answer: not much
07:53 subway joined #salt
07:58 stevetodd joined #salt
07:59 krak3n` joined #salt
08:01 faldridge joined #salt
08:01 ml_1 joined #salt
08:12 ml_1 joined #salt
08:13 Ixan Furao: found it, thanks for the pointer
08:14 Xeago joined #salt
08:18 felixhummel joined #salt
08:20 UtahDave Ixan: have you tried running salt on aix yet?
08:20 Ixan yes, i got it working
08:21 xl2 joined #salt
08:21 Ixan grains.items at least works. have worked a bit on getting reasonable information into grains for aix
08:22 dthom91 joined #salt
08:23 UtahDave cool.
08:24 UtahDave yeah, I imagine there would be a fair amount of work in grains/core.py for aix
08:24 UtahDave would you mind adding your experience and any problems you've run into to that email thread?
08:26 Ixan yeah, will do. i'll write up something about how to get it running.
08:26 malinoff UtahDave, could you please say something about salt-0.16.3 in CentOS repos? Or at least 0.16.2. We really need this, since pkgrepo (yum) is not works correctly on 0.16.0
08:26 UtahDave that would be awesome, Ixan. Thanks!
08:26 Ixan np
08:27 UtahDave malinoff: have you looked in epel-testing?  I think our backup packager got it uploaded there today. maybe yesterday
08:28 malinoff UtahDave, every day i'm looking for it. There's 0.16.0 right how
08:28 malinoff Why don't you make your own repository?
08:29 ml_1 joined #salt
08:29 zooz joined #salt
08:31 UtahDave malinoff: I'm sorry about that. Our epel packager has been really busy lately. We're working to get 2 more packagers involved to pick up the slack
08:31 UtahDave We're working on our own repository, too
08:32 morganfainberg UtahDave: Extra people is good, +1 ;)
08:32 UtahDave Yeah, having just one person is obviously a problem when they go on vacation!  :)
08:33 morganfainberg Vay-cay-shun? whats that?
08:34 Furao I almost never ask question, mostly just answer. but here is a non salt-specific question: as salt-api pam auth requires local user in /etc/passwd. you guys know a way to set a non-encrypted password trough salt? such as echo 'mypass'  | set_password myuser
08:34 malinoff UtahDave, its awesome, thanks.
08:35 Furao I'm about to hack /usr/sbin/passwd source code to turn it into a separate bin that just do that
08:35 UtahDave Furao: http://docs.saltstack.com/ref/modules/all/salt.modules.shadow.html#salt.modules.shadow.set_password
08:36 Furao woah
08:36 Furao thanks!
08:36 Furao I looked like a few months ago and I don't remember it was there
08:36 * Furao need to write a crypt module
08:37 Furao I already got that module that generate password
08:39 UtahDave Furao: that would be cool to have1
08:41 Furao UtahDave: https://gist.github.com/bclermont/dbee003f4fde0124c834
08:42 UtahDave that's sweet
08:47 malinoff I want to add mine_functions to a minion config from the master. What's the best way to do that? One thing i see is to check at first whether /etc/salt/minion contains mine_functions line, and if it's not append this block
08:48 kallek_ joined #salt
08:49 malinoff But it seems that soon i will have a very complex state with many {% if %} blocks...
08:51 Furao malinoff: if you manage it from a single state, put that in /etc/salt/minion.d/$file or use file.accumulated
08:55 malinoff Furao, thanks :)
08:57 gildegoma joined #salt
09:10 wimbo joined #salt
09:10 wimbo hello all
09:11 wimbo can somebody help with state.cmd ?
09:11 wimbo how i can wait for complete execution?
09:12 mike25ro cmd.wait
09:12 mike25ro i think there is a cmd.wait :)
09:13 krak3n` joined #salt
09:14 wimbo i can get require for cmd.run/wait?
09:19 Jahkeup joined #salt
09:20 Nexpro joined #salt
09:24 p3rror joined #salt
09:32 ggoZ joined #salt
09:32 bhosmer joined #salt
09:33 jkleckner joined #salt
09:34 MrTango joined #salt
09:52 xl2 Can overstate.sls itself be in gitfs? Seems that "salt-call state.over" cannot find it, but all the other sls files called by it are in gitfs and work fine. I'm using 0.16.0
09:56 vaxholm joined #salt
10:01 malinoff I am really missing something. I have many environments (e.g. /srv/salt/base, /srv/salt/project1, /srv/salt/project2), and i want to have separate top.sls files in all environments.
10:02 malinoff Im doing that, and when i run state.highstate - salt returns 'there is no top file'
10:05 mike25ro malinoff: there is only one top.sls in /srv/salt/top.sls
10:05 mike25ro that's it
10:07 whiskybar joined #salt
10:09 az87c joined #salt
10:19 kiorky uhm, we ask a while ago that: https://github.com/saltstack-formulas/salt-formula/pull/5
10:19 kiorky which was then removed back to a subdirectory
10:20 kiorky but then, how can we easily include formulas in a top directory without having to touch to the configuration.
10:21 kiorky What we want is to drop a formula in our states directory without having to declare it
10:23 kiorky basepi: ^
10:25 scalability-junk kiorky: why can't it be used as submodule?
10:25 scalability-junk salt/init.sls = salt.sls which sort of defeats the purpose to put everything in root
10:26 kiorky scalability-junk: because you have to do salt.salt
10:26 kiorky which does not work
10:26 kiorky read the bug
10:27 kiorky (let me find it)
10:27 scalability-junk yeah reading it already
10:27 kiorky scalability-junk: that was our  first idea, to use submodules
10:27 kiorky (and what we want to do)
10:28 kiorky scalability-junk: https://github.com/saltstack-formulas/salt-formula/issues/4
10:28 scalability-junk yeah I already read that.
10:28 kiorky scalability-junk: ok !
10:28 giantlock joined #salt
10:29 scalability-junk but it would be unorganized to have them in the root. this is the best practice structure...
10:29 scalability-junk thinking about your problem so...
10:30 kiorky scalability-junk: yoju mean when you use those formulas as a gitfs remote ?
10:30 kiorky scalability-junk: the only workaround i see is an ugly symlinker script
10:30 scalability-junk kiorky: primarily for better understanding and structure
10:31 scalability-junk kiorky: yeah would be my first idea too.
10:31 scalability-junk kiorky: have them all in submodules and then use a bash to link the real folders within your root dir.
10:32 scalability-junk not perfect, but having everything in the root directory is ugly especially when formulas grow bigger.
10:33 kiorky scalability-junk: well, just the documentation is a bit broken then
10:33 scalability-junk for the formulas?
10:33 kiorky scalability-junk: https://salt.readthedocs.org/en/latest/topics/conventions/formulas.html#adding-a-formula-directory-manually
10:34 kiorky this thing doest work unless you add the inner dir to your master file_roots
10:34 scalability-junk nope it does work ;)
10:34 scalability-junk if you git clone ..formula.git .
10:35 scalability-junk you have root/salt/init.sls which in turn results in calling salt just fine
10:35 scalability-junk the problem is that you have them as submodules, where you need additional subdirectories here salt
10:35 kiorky scalability-junk: but then you can execute only this formula
10:36 scalability-junk kiorky: true, the docs are misleading or old... I'll try to ping someone about it when I'm back later tonight.
10:38 kiorky scalability-junk: imo subdirectories whith a formula structure should have been picken up with the same behavior as it would have been with a gitfs_remote
10:38 kiorky (so stripping the toplevel directory eg "salt-formula")
10:40 brianhicks joined #salt
10:40 scalability-junk yeah with gitfs it seems to work. then I would almost consider it a bug... perhaps create an issue within the core code that subdirectories should be stripped, but then gitfs could be used with submodules...
10:40 scalability-junk tricky :D
10:41 kiorky scalability-junk: its normal that it works with gitfs as then the topdir is considered as another root
10:41 kiorky that's then not a bug but a feature for local formulas checkouts to be considered as new roots, isnt it ?
10:41 scalability-junk depends on the viewpoint :)
10:42 scalability-junk as the new formula structure was already done I think it's more a bug than a feature :) but for features create an issue too :D
10:42 scalability-junk I'll bug someone about the misleading documentation and point them to the issue. so probably gitfs or bash symlink workaround for now :(
10:43 kiorky scalability-junk: in our case i wold justg use buildout + mr.developer + a recipe.command to symlinks
10:44 kiorky but that's odd
10:44 kiorky scalability-junk: https://github.com/saltstack/salt/issues?state=open issue there ?
10:47 scalability-junk y
10:48 scalability-junk kiorky: hehe I talk about bash scripts within a config automation channel... schame on me
10:50 it_dude joined #salt
10:51 malinoff mike25ro, there is definitely NOT the only top file http://docs.saltstack.com/ref/states/top.html#how-top-files-are-compiled
10:54 kiorky scalability-junk: https://github.com/saltstack/salt/issues/6739
10:56 scalability-junk kiorky thanks will comment on it
10:58 mikedawson joined #salt
10:59 felixhummel_ joined #salt
11:00 it_dude joined #salt
11:04 felixhummel joined #salt
11:07 suodla_ joined #salt
11:07 felixhummel_ joined #salt
11:08 wimbo how i can execute command only if another command complete?
11:08 scalability-junk wimbo: doesn't require do that?
11:09 wimbo some command with cmd.run and another command with cmd.wait (watch first cmd) ?
11:09 wimbo in first command i checkout svn and after that need do chown all files that checkout
11:09 suodla__ joined #salt
11:10 suodla joined #salt
11:13 felixhummel joined #salt
11:18 blee joined #salt
11:20 Jahkeup joined #salt
11:28 oz_akan_ joined #salt
11:29 it_dude joined #salt
11:30 hazzadous joined #salt
11:31 lemao joined #salt
11:33 Jarus Is it possible that the state mount doesn't work very well with tmpfs: https://gist.github.com/jarus/1a468eb7cedf5fc011f3
11:36 fredvd joined #salt
11:37 baniir joined #salt
11:38 felixhummel_ joined #salt
11:41 xl2 left #salt
11:52 baniir joined #salt
12:04 mechanicalduck joined #salt
12:07 it_dude joined #salt
12:16 intchanter joined #salt
12:18 bhosmer joined #salt
12:20 intchanter-swapp left #salt
12:20 LucasCozy joined #salt
12:21 bhosmer_ joined #salt
12:22 logix812 joined #salt
12:42 aleszoulek joined #salt
12:46 waverider joined #salt
12:47 brianhicks joined #salt
12:56 juicer2 joined #salt
12:57 dstanek joined #salt
12:59 mikedawson joined #salt
13:02 anteaya joined #salt
13:04 aat joined #salt
13:04 TJ1980 joined #salt
13:05 oz_akan_ joined #salt
13:05 baniir joined #salt
13:09 jslatts joined #salt
13:11 mikedawson_ joined #salt
13:14 jeffasinger joined #salt
13:21 redbeard2 joined #salt
13:23 pdayton joined #salt
13:27 it_dude joined #salt
13:28 Jahkeup joined #salt
13:31 jaequery joined #salt
13:33 oz_akan_ joined #salt
13:36 aat joined #salt
13:39 ipmb joined #salt
13:40 mechanicalduck_ joined #salt
13:42 joehoyle joined #salt
13:44 aat joined #salt
13:46 mmilano joined #salt
14:00 mwillhite joined #salt
14:03 mannyt joined #salt
14:04 kermit joined #salt
14:05 opapo joined #salt
14:09 napperjabber joined #salt
14:13 faldridge joined #salt
14:17 LotusBleu joined #salt
14:17 LotusBleu hi
14:18 LotusBleu can Salt manage the conformity of switches/firewalls configurations ? (thru ssh comandlines ?)
14:26 tqrst joined #salt
14:26 bhosmer joined #salt
14:27 tqrst whenever I run a command using salt '*' {test.ping, cmd.run, etc.}, the output for every minion gets displayed immediately, but the actual salt command seems to hang there for another 5-10 seconds before exiting. Is this normal?
14:28 xt tqrst: unless every node return it will wait for the defined timeout in master config
14:29 tqrst xt: but there is no more output after hanging, which leads me to believe that no timeout occured (wouldn't there be an error message otherwise?)
14:29 xt check output for salt-run manage.down
14:30 LotusBleu is it possible to get an ssh output command with salt ?
14:30 hazzadous joined #salt
14:32 xt yes!
14:32 xt if I understand your question, not sure
14:32 m_george|away joined #salt
14:33 tqrst xt: ah, some are down. Why is salt not warning me about these, though?
14:33 xt that's not salt's job
14:34 LotusBleu I want to connect to a component via ssh to parse the results of a command, or execute some configs commands
14:34 jaequery joined #salt
14:35 andredublin joined #salt
14:37 m_george left #salt
14:37 gamingrobot tqrst: thats test.ping's job
14:39 xt tqrst: you can monitor nodes through salt, but salt cant know which nodes you meant to be down, etc.
14:41 tqrst joined #salt
14:41 LotusBleu https://salt.readthedocs.org/en/latest/ref/cli/salt-ssh.html <3
14:43 gamingrobot LotusBleu: Pretty sure thats just using ssh for transport to a salt minion instead of zmq
14:43 jpaetzel joined #salt
14:44 LotusBleu gamingrobot, I need that for firewalls & switches :)
14:44 LotusBleu for others zmq !
14:46 ckao joined #salt
14:46 kgarland joined #salt
14:46 tqrst joined #salt
14:47 KennethWilke joined #salt
15:02 andrew_ joined #salt
15:02 faldridge joined #salt
15:03 dkubb joined #salt
15:04 forrest joined #salt
15:08 lazyguru joined #salt
15:09 napperjabber joined #salt
15:19 devinus joined #salt
15:22 Xeago joined #salt
15:27 kaptk2 joined #salt
15:28 elfixit joined #salt
15:29 troyready joined #salt
15:30 cron0 joined #salt
15:34 StDiluted joined #salt
15:35 DerekRBN left #salt
15:40 JasonSwindle joined #salt
15:41 chrisgilmerproj joined #salt
15:46 jschadlick joined #salt
15:52 kstaken joined #salt
15:55 ml_1 joined #salt
16:07 kermit joined #salt
16:07 drawsmcgraw joined #salt
16:08 drawsmcgraw I've got Minions with outdated cached topfiles and they insist on trying to run with those old topfiles. Any sanctioned way of making them update it?
16:08 drawsmcgraw I've tried state.clear_cache to no avail...
16:14 tqrst left #salt
16:15 SEJeff_work https://gocardless.com/blog/building-a-large-angular-application for Samuel to checkout as he writes halite
16:16 KyleG joined #salt
16:16 KyleG joined #salt
16:20 dthom91 joined #salt
16:22 devinus joined #salt
16:32 devinus joined #salt
16:37 psilo joined #salt
16:39 Lue_4911 joined #salt
16:42 gordonm joined #salt
16:44 whit joined #salt
16:53 kermit joined #salt
17:01 TJ1980 joined #salt
17:09 jschadlick joined #salt
17:09 luminous when you set fileserver_backend to git, and then a repo for gitfs_remotes, can file_roots be empty (provided you have top.sls in repo)?
17:12 devinus joined #salt
17:16 napperjabber joined #salt
17:17 jschadlick joined #salt
17:18 gildegoma joined #salt
17:21 drawsmcgraw luminous: yes
17:21 drawsmcgraw I just learned this by troubleshooting a problem of my own
17:21 drawsmcgraw I have a top.sls in my Git repo. I've been modifying my local Topfile (in /srv/salt) and wondering why I wasn't seeing the changes.
17:21 drawsmcgraw rather
17:22 drawsmcgraw Yes. I just tested by commenting out the file_roots in my Master config. Ran with no problem (or in my case, threw the same error because it's fetching the Topfile from Git)
17:23 robertkeizer joined #salt
17:35 jkleckner joined #salt
17:35 dthom91 joined #salt
17:38 UtahDave joined #salt
17:43 druonysus joined #salt
17:44 druonysus joined #salt
17:44 psilo joined #salt
17:47 brianhicks joined #salt
17:48 chrisgilmerproj joined #salt
17:50 PhoenixSTF joined #salt
17:50 nkuttler joined #salt
17:52 zonk1024 joined #salt
17:52 PhoenixSTF hey guys, sorry to ask this but any recomendations for naming servers, vm's, desktops, and why? This is for a collage student laboratory run by students.
17:52 djn joined #salt
17:53 forrest depends on what software you're using PhoenixSTF
17:53 forrest Generally you want to stay away from using something like web1.domain.com
17:54 PhoenixSTF yes that is true
17:54 forrest depending on the software you can have problems if you use app1.web1.domain.com, in stuff like vmware it will cut off part after the dot, so now app1.web1, is just app1
17:54 PhoenixSTF I was hopping for a more relaxed and funny
17:54 forrest Ehh, relaxed and funny = naming drift
17:55 drawsmcgraw PhoenixSTF: oh. If you're going for casual, my favorite theme is random pantheons
17:55 PhoenixSTF drawsmcgraw, what?
17:55 drawsmcgraw I was going to suggest a service-to-name mapping, like an Apache server would be 'http-001', and subsequent servers 'http-002'.....
17:55 PhoenixSTF it's mroe like getting a name for vm and name it, minions-I
17:55 StDiluted are pillars always one key, one value?
17:55 forrest that works as well drawsmcgraw
17:56 forrest http001, or http-001.domain.com
17:56 drawsmcgraw Yeah. Random pantheons. For example, I have a home server named Vishnu from the Indian pantheon
17:56 djn joined #salt
17:56 drawsmcgraw forrest: Yeah I like the dashes for readability
17:56 forrest well, the dashes are a requirement for stuff like vmware
17:56 forrest they don't accept dots
17:56 drawsmcgraw interesting
17:56 forrest so you can screw yourself hard
17:56 drawsmcgraw I can believe that
17:56 luminous drawsmcgraw: thanks for confirming!
17:57 forrest as an admin it's not as big a deal, but when I'm trying to show someone a list of servers, and they all say 'web1' because the rest of the name got chopped, it's problematic
17:57 PhoenixSTF ok we got hosts, desktops, thi/fat clients and a future rendering cluster type servers
17:57 UtahDave StDiluted: pillars can be dicts and lists as well
17:57 chjohnst_work joined #salt
17:58 drawsmcgraw luminous: Sure thing. That cost me about 2 hours of troubleshooting this morning, that Topfile hidden in my Git repo :P
17:58 luminous :(
17:58 forrest yea then do something like host1.domain.com (if you can ensure that later down the road there won't be different standards), pc1/mac1.domain.com, thi1.domain.com, etc.
17:58 forrest whatever you do, make sure that everything before the domain uses dashes
17:58 luminous I'm caught in a similar limbo trying to figure out why some of my states aren't being seen
17:59 StDiluted UtahDave: that's what I thought. If I want to assign a dict to a pillar, would I do something like: pillar['virt_dom'] = ['value1','value2','value3'] in my external pillar?
17:59 drawsmcgraw luminous: Yeah I just trashed my deployment and re-deployed my servers. My targeting seems to be off... All of the minions say there are no states for them in the Topfile
17:59 luminous :(
18:00 drawsmcgraw We have an openstack deployment. It took five seconds to start a script that just makes some VMs. No real time lost
18:00 PhoenixSTF so nobody uses like star wars names and that sort of geek stuff
18:00 luminous is there a module/cmd to sync gitfs?
18:00 UtahDave StDiluted: I haven't looked at the external pillar doc in a while, but yes, whatever the var is that's passed in to the external pillar you can modify however you want
18:00 forrest You run out of names PhoenixSTF
18:00 luminous drawsmcgraw:  :D
18:00 forrest what happens when you have 50 nodes in that rendering cluster?
18:00 PhoenixSTF not if you use numbering
18:00 luminous are you using salt-cloud?
18:00 forrest how do you keep track?
18:00 drawsmcgraw PhoenixSTF: Negatory. My geekiness is in using those random diety names
18:00 luminous hah
18:00 forrest I guess you could do that PhoenixSTF
18:00 KennethWilke left #salt
18:00 forrest I just like it when anyone can look at a server name, and get an idea of what it does
18:00 forrest or where it is, etc.
18:01 PhoenixSTF viper-I, Viper-II, Viper-VI
18:01 drawsmcgraw luminous: negative on salt-cloud. Bunch of Nova commands. But I may eventually play with salt-cloud
18:01 forrest don't use roman numerals
18:01 luminous forrest: that's the purpose of CNAMEs :)
18:01 forrest *shrug*
18:01 PhoenixSTF forrest, no roman?
18:01 luminous drawsmcgraw: I would encourage you to do so
18:01 forrest why waste time with that when you can just name it easily the first time
18:01 StDiluted the Vindow Viper?
18:01 forrest Too easy to screw up Phoenix
18:01 PhoenixSTF cylon-7
18:01 PhoenixSTF lol
18:01 drawsmcgraw I agree with forrest . Anything even remotely 'official', I stay away from the fun stuff and make meaningful server names
18:02 forrest Even at home on my own VMs, everything has an official name
18:02 luminous because how will that name suggest what additional services you load up on it, or what about when you migrate services and your meaningful name is not longer relevant
18:02 luminous forrest: ^^
18:02 forrest agreed luminous
18:02 forrest this isn't a lab you're blowing away tomorrow, this is an infrastructure you have to maintain, bring people on board to maintain, etc.
18:02 forrest the more official, and clear things are, the easier that maintenance will be
18:02 StDiluted at $prevjob there was a file server called 'my-balls'
18:02 dthom91 joined #salt
18:02 PhoenixSTF it is not official since most of the hardware is donated by myself and some friends, Collage don't give that much of a crap to IT students
18:02 luminous forrest: this is the point of pillars
18:03 luminous :)
18:03 StDiluted made for some fun conversations
18:03 luminous at least in my setup, pillars.data will tell you the roles associated with that system
18:03 druonysuse joined #salt
18:03 druonysuse joined #salt
18:03 StDiluted 'The file is on my-balls' or.. "Just slap it in the shared directory on my-balls'
18:03 luminous so it doesn't matter that I have isis, osiris, or aten for VM names
18:03 forrest Yea that works, I just don't find the geek names 'fun' just annoying I guess.
18:03 forrest Let me know when you run out of names luminous :D
18:04 luminous oh there are a lot of options
18:04 luminous let me know when you run out of meaningful ways to name db-server
18:04 forrest 0-infiniti?
18:04 luminous hmm... is that db on db-01 or db02? or web-db-memcache?
18:04 luminous :P
18:05 forrest wait wait was our primary DB on Thor? Or was it on Odin?
18:05 drawsmcgraw In my Topfile, I'm targeting some minions with -->  'N@software-hosts'
18:05 luminous forrest: pillars.data will tell you!
18:05 drawsmcgraw Where 'software-hosts' is a nodeGroup as defined in my Master config file
18:05 forrest lol
18:05 luminous :D
18:05 drawsmcgraw ...is that right?
18:05 forrest lame excuse is lame
18:05 luminous use pillar effectively and you will save yourself having to think
18:05 forrest same could be said for the numbering scheme ;D
18:05 StDiluted thinking is bad, mmkay
18:06 luminous hah
18:06 berto- joined #salt
18:06 forrest Just avoid dots
18:06 forrest seriously, name it anything
18:06 forrest whatever you want
18:06 forrest but don't do web1.asdf.domain.com
18:07 StDiluted I will name my server dot.dotdot….dotty.dot.dot.domain.com
18:07 PhoenixSTF i'll just find comparative name for the job of the machine, thanks guys
18:07 luminous :P
18:07 forrest StDiluted, I hope you're never going virtual then
18:07 luminous PhoenixSTF: you could also ask about vim and emacs if you haven't chosen one
18:07 luminous :P
18:08 StDiluted forrest: ha, I hope you realize I'm kidding ;)
18:08 StDiluted hahaha
18:08 forrest I know StDiluted
18:08 StDiluted luminous, holy-war-baiting!
18:08 UtahDave In case this hasn't been linked to in here: http://developer.rackspace.com/blog/why-i-use-saltstack.html
18:08 luminous is there a module/cmd to request your master sync gitfs?
18:08 StDiluted emacs is awesome if you like running an OS instead of an editor ;)
18:08 forrest Ugh that reminds me I need to migrate my VM off rackspace
18:09 luminous StDiluted: have youseen that pycon 2013 talk using dragon and emacs?
18:09 StDiluted no
18:10 luminous it's hawt
18:10 drawsmcgraw UtahDave: I think my targeting in my Topfile is off... What's the 'best' way of targeting via NodeGroups in the Topfile ?
18:10 luminous StDiluted: Using Python to Code by Voice-8SkdfdXWYaI << name on youtube
18:10 drawsmcgraw When I target 'all' (that is, with '*'), then my Minions get their states
18:11 drawsmcgraw But if I try to use a NodeGroup, they get none...
18:11 luminous StDiluted: works with both editors though :)
18:11 UtahDave drawsmcgraw: do you have an  - match: nodegroup    underneath your matching line?
18:11 drawsmcgraw I do. Just now tried that
18:11 drawsmcgraw And I confirmed it's a valid node group via a Salt command from the master
18:12 drawsmcgraw salt -N awesome-hosts test.ping
18:12 drawsmcgraw I keep getting -> "No hosts found for this minion" from all of them
18:12 StDiluted draws: can you pastebin your top.sls?
18:12 drawsmcgraw StDiluted: Sure. One second
18:13 UtahDave drawsmcgraw: what version of Salt?
18:13 drawsmcgraw UtahDave: 16.3
18:13 jpeach joined #salt
18:13 drawsmcgraw though... I used Yum to install Salt (master | minion) 16.0. Then used the included setup.py to install Salt 16.3 on top of that
18:14 drawsmcgraw salt --version returns 0.16.3 on the master and all minions
18:15 drawsmcgraw StDiluted: http://pastebin.com/a6ESBi4n
18:16 StDiluted draws: https://salt.readthedocs.org/en/latest/topics/targeting/nodegroups.html
18:17 jpeach I just ran into an 0.16.0 issue where the minions seems to go deaf to the salt master .. is that known?
18:17 StDiluted I think maybe you just need awesome-hosts: as your matcher line
18:17 drawsmcgraw StDiluted: Ah, I see. One second....
18:17 StDiluted jpeach: I had that happen with vagrant sometimes
18:17 jpeach this is bare metal
18:18 drawsmcgraw StDiluted: That did it! Thanks! Now I just need to fix the individual host names and I can move on....
18:18 drawsmcgraw Thanks again
18:18 StDiluted sure
18:19 JasonSwindle Just got an "AttributeError: LooseVersion instance has no attribute 'version'" error on 0.16.3
18:19 JasonSwindle https://gist.github.com/JasonSwindle/7e4692bf5123b9111734
18:19 JasonSwindle This was on a second Highstate
18:19 drawsmcgraw Ah. If I put just the id in, I have to specify --> match: id.
18:19 drawsmcgraw I'm okay with that
18:20 jpeach sounds like https://github.com/saltstack/salt/issues/6231
18:22 luminous when the master is set up to use gitfs, where are the repos cached?
18:23 drawsmcgraw luminous: /var/cache/salt/(master|minion)
18:24 drawsmcgraw I find I have to occasionally destroy the Master's GitFS cache when I have new files pushed to the repo
18:24 luminous ah, well the master is not syncing my repos
18:24 drawsmcgraw Try deleting the contents of 'gitfs' under /var/cache/salt/master
18:24 drawsmcgraw Then restarting the master
18:25 StDiluted draws: you can always put the id in with '' around it
18:25 drawsmcgraw It seems a bit stubborn about hanging onto cached files
18:25 drawsmcgraw StDiluted:  Yeah I tried that (without the 'match' parameter) and it wasn't working
18:25 luminous yea, not seeing anything pulled
18:25 luminous oh, there we go
18:26 drawsmcgraw I set the Master log output to debug and look for some Git-type messages
18:26 drawsmcgraw but it sounds like you're good now
18:27 luminous nope, I think the problem is that I need the ssh/git syntax and I haven't got that correct in the master config
18:27 drawsmcgraw ah
18:28 drawsmcgraw luminous: We use an internal GitLab install. The line in my Master config looks like --> git@internal.gitlab.server:groupname/project.git
18:29 drawsmcgraw And I have a deploy key that lives in /root/.ssh/(id_rsa | id_rsa.pub)
18:29 drawsmcgraw For my dev place, Salt runs as root
18:29 luminous you're not using  - git+ssh://git@github.com/example/salt-states.git
18:29 luminous https://salt.readthedocs.org/en/v0.16/topics/tutorials/gitfs.html#gitfs-remotes-over-ssh
18:30 rberger joined #salt
18:30 luminous fatal: bad default revision 'HEAD' <<< :(
18:30 drawsmcgraw luminous: No. I read that howto and I ran into issues that may be the same as what you're having
18:30 drawsmcgraw now that, I don't know what it is
18:30 napperjabber joined #salt
18:30 luminous that's me trying git log from inside /var/cache/salt/master/gitfs/0
18:31 drawsmcgraw ah
18:32 drawsmcgraw Yeah. I tried *exactly* what that doc says. I was (still am) new to Git, so I just started hacking different interpretations until I ran into what I have now
18:32 luminous no errors in the master log
18:33 drawsmcgraw luminous: even with the log_level at debug, huh?
18:34 djn joined #salt
18:34 drawsmcgraw Unrelated (for anyone else) --> Can I have the Salt Master greet a new minion with its States? Or do I have to pull the trigger manually or wait for a routine Salt run ?
18:35 UtahDave drawsmcgraw: you can set the following config in your /etc/salt/minion     startup_states: highstate
18:37 drawsmcgraw UtahDave: Oh cool! Thanks!
18:39 Tekni joined #salt
18:48 mechanicalduck joined #salt
18:49 Linz joined #salt
18:51 Linz joined #salt
18:54 djn joined #salt
18:56 bhosmer joined #salt
19:01 dthom91 joined #salt
19:05 djn joined #salt
19:08 jimallman joined #salt
19:11 dstanek joined #salt
19:14 djn joined #salt
19:18 ggoZ joined #salt
19:19 djn joined #salt
19:21 djn joined #salt
19:26 djn joined #salt
19:29 felixhummel joined #salt
19:33 devinus joined #salt
19:35 napperjabber joined #salt
19:35 gordonm joined #salt
19:37 fxhp hi guys
19:37 fxhp had a key pending in salt-key
19:38 napperjabber joined #salt
19:38 fxhp and ended up filling var (4G) with this type of message:
19:38 fxhp [ERROR   ] The Salt Master has cached the public key for this node, this salt minion will wait for 10 seconds before attempting to re-authenticate
19:39 MrTango joined #salt
19:39 salty-sailor joined #salt
19:39 fxhp /var/log/upstart/salt-minion.log and /var/log/salt/minion
19:39 fxhp both nearly 2G
19:39 salty-sailor Hey all, I'm a little confused about environments
19:39 fxhp version 15.1
19:39 salty-sailor The documentation says to set them via the top file, but I don't understand how one goes about doing that
19:40 fxhp salty-sailor: ok
19:40 fxhp salty-sailor: so I don't use different evn, so I use the env 'base':
19:40 fxhp everything falls into that
19:40 fxhp by default
19:41 salty-sailor sorry fxhp I was asking a question :-P
19:41 salty-sailor not answering yours :-[
19:41 fxhp I was answering yours
19:41 fxhp : )
19:41 salty-sailor oh
19:41 bhosmer joined #salt
19:41 salty-sailor I know everything falls into base by default, but Im curious how one would target a different environment
19:42 fxhp I think it looks like this: http://pad.yohdah.com/161/c3f6dae0-3e90-452b-b94f-49cb33c7bb58
19:43 fxhp http://docs.saltstack.com/ref/states/top.html
19:43 fxhp ^ salty-sailor
19:44 gordonm joined #salt
19:44 fxhp I do things a tad differently, all my envs are part of base
19:44 salty-sailor so if your file_roots had /srv/salt/dev then *.dev.example.com would pull from there?
19:44 fxhp simplifies our repos
19:44 zach joined #salt
19:45 fxhp salty-sailor: thats how I think it works, but I've never tested it
19:50 juicer2 joined #salt
19:50 cameron__ joined #salt
19:52 isomorphic joined #salt
19:54 felixhummel joined #salt
19:55 dthom91 joined #salt
19:56 cedwards s0undt3ch: ping re: bootstrap
19:56 s0undt3ch cedwards: Thanks!
19:56 s0undt3ch cedwards: working perfectly now
19:56 cedwards s0undt3ch: glad to hear it
19:57 cedwards s0undt3ch: that fix this morning got me thinking about the FreeBSD bootstrap
19:57 s0undt3ch cedwards: saw that mail I sent to the packagers mailing list?
19:57 s0undt3ch cedwards: oh?
19:57 cedwards s0undt3ch: as I understand it the FreeBSD bootstrap doesn't work because packages aren't available.
19:58 cedwards s0undt3ch: ...but if we're using my repo for Arch, we may as well use it for FreeBSD too.
19:58 druonysus joined #salt
19:58 s0undt3ch cedwards: well, the only thing there is, for Arch we pull one package, right? For FreeBSD we'd need a bunch of them
19:59 s0undt3ch cedwards: also, we're using a public PACKAGESITE, let me get it
19:59 cedwards s0undt3ch: Arch pulls two packages technically. I also maintain python2-msgpack in AUR and my repo
19:59 devinus joined #salt
19:59 s0undt3ch ah :)
20:00 cedwards I also updated my repo this morning to provide all the depends for salt-cloud, which are like a half-dozen packages.
20:00 s0undt3ch cedwards: PACKAGESITE: ftp://ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64
20:03 ksalman when I include a state file, does salt ensures and satisfies everything in that state first?
20:03 s0undt3ch cedwards: we could use your repo, but I think Thomas was trying to avoid user repositories so they don't get smashed with requests
20:04 s0undt3ch cedwards: we need to bring that discussion up again :)
20:04 ksalman or would i need to be explicit and use require: for the packages and things in the included state?
20:04 cedwards s0undt3ch: yeah, that was the understanding I had before as well.
20:04 cedwards s0undt3ch: I figured though, if we're already using me for one..
20:04 s0undt3ch cedwards: you were supposed to get a VM to build and serve pacakges right?
20:05 cedwards s0undt3ch: plus, my pipe just got upgraded from 50M to 100M :)
20:05 s0undt3ch cedwards: dam!
20:05 s0undt3ch cedwards: that's what you have at home?
20:05 cedwards s0undt3ch: yes. 100M/100M fiber
20:06 s0undt3ch F*c*!
20:06 s0undt3ch :)
20:06 cedwards s0undt3ch: I'd be happy to help you guys setup the a server to host these on your end
20:06 s0undt3ch I have 20 down / 1 up cable
20:06 cedwards s0undt3ch: a single VM would be adequate I'm sure
20:06 s0undt3ch cedwards: I think Herlo was taking care of setting that up
20:07 s0undt3ch cedwards: though here's either in vacation, or extremely busy at the moment
20:07 felixhummel hey guys! what do you use for logging? we are currently using a central rsyslogd, but maybe you know something better...
20:07 s0undt3ch *he's
20:08 cedwards s0undt3ch: well i'm happy to help when he gets back
20:08 s0undt3ch cedwards: Awesome!
20:08 s0undt3ch cedwards: you have access to the packagers mailing list?
20:09 cedwards s0undt3ch: yes, I'm on the packagers list
20:09 s0undt3ch cedwards: saw that salt-testing mail I sent yesterday?
20:09 cedwards s0undt3ch: Yeah. I don't think it applies to my packages..?
20:09 UtahDave cedwards: Let's get on that right now.  What do you need to get that set up?  I can build you a vm and get you a dns entry
20:10 s0undt3ch UtahDave: Awesome!
20:10 cedwards UtahDave: are we talking hosting FreeBSD packages?
20:10 UtahDave cedwards: sure, whatever you want to help with
20:10 s0undt3ch cedwards: ah, so, there's no unittesting going on for both Arch and FreeBSD, then, cool, you don't have to do anything else ;)
20:11 s0undt3ch UtahDave: would be cool to have both, maybe a single VM handles both Arch and FreeBSD? That way we aliviate the workload on cedwards 100M pipe ;)
20:11 UtahDave lol
20:12 jschadlick joined #salt
20:12 cedwards s0undt3ch: I haven't been doing any unittesting.. maybe I should. *shrug*
20:12 s0undt3ch cedwards: I think ppl are only doin' unittesting because the pacakges release process requires it
20:12 cedwards UtahDave: mainly I just need a FreeBSD VM, but I realize the build-tool I use requires ZFS
20:13 s0undt3ch cedwards: I've been helping Thomas setup a Jenkins server which is running the tests suite on multiple platforms
20:13 cedwards UtahDave: the main FreeBSd installer doesn't support that in 9.1, but the PCBSD installer does
20:14 cedwards UtahDave: are you talking an AWS VM or something in-house?
20:14 UtahDave cedwards: OK. If I set you up a FreeBSD 9.1 vm, can you handle it from there?
20:14 UtahDave cedwards: Rackspace
20:14 cedwards UtahDave: I just wonder about the ZFS support in a Rackspace VM. Never spun one up.
20:15 UtahDave I have no idea.  I'll spin one up and let you check it out.  Is that cool?
20:15 KyleG cedwards: http://www.rackspace.com/blog/rackspace-cloud-servers-to-support-centos-6-3-freebsd-9/
20:15 KyleG " To make FreeBSD support possible, we needed to make a couple of fundamental enhancements to Cloud Servers. One such change is support for non-ext3 and NTFS file systems (FreeBSD runs ZFS)."
20:15 KyleG looks like you're good
20:16 * KyleG pokes JordanRinke for comment
20:16 cedwards awesome
20:16 cedwards KyleG: just found the same article :)
20:16 KyleG ^_^
20:17 chrisgilmerproj joined #salt
20:17 jschadlick joined #salt
20:17 druonysus joined #salt
20:18 cameron__ hey guys! first: i love salt. thank you thank you thank you. i would love it if someone could help me diagnose a salt-cloud config error: https://gist.github.com/cameronboehmer/445777e19de89026a219. this feels like it could be a) silly user error or b) salt-cloud providers/profiles config is pretty broken
20:18 forrest joined #salt
20:18 druonysus joined #salt
20:19 druonysus joined #salt
20:20 luminous I'm using the git repo formated noted here https://salt.readthedocs.org/en/v0.16/topics/tutorials/gitfs.html#simple-configuration, but still seeing this error in master's debug log:  salt.master: Exception len([]) != len(['ssh: Could not resolve hostname github.com:Username
20:20 luminous eg, I have this in master's config: - git@github.com/Username/salt.git
20:21 luminous and ssh key in /root/.ssh/id_rsa
20:21 luminous am I overlooking a key detail here?
20:21 KyleG 'ssh: Could not resolve hostname github.com:Username'
20:22 derelm joined #salt
20:22 KyleG Sounds like you didn't format the config right or something
20:22 KyleG maybe you have to add the protocol like
20:22 KyleG git://
20:22 KyleG or http://
20:22 KyleG Because SSH is trying to resolve github.com + :Username which obviously isn't valid
20:22 mgw joined #salt
20:22 luminous right, I'm mixing ssh and non ssh
20:22 luminous bah!
20:23 luminous git@ but no git+ssh
20:23 * luminous retries
20:26 luminous hrm, same thing
20:28 forrest you're able to make a normal request to github without using salt right?
20:28 nielsbusch joined #salt
20:28 luminous I was earlier, I can retest..
20:29 forrest no just confirming
20:29 forrest gotta start at the easiest one
20:30 luminous most definitely :)
20:31 luminous i'm hoping i had to correct the url, THEN remove the old (failed) cached directories, THEN restart..
20:32 luminous Exception 'Error when fetching: fatal: remote error:' returned exit status 2: None occurred in file server update <<< is this gitfs?
20:32 luminous if so, I've at least progressed to a new error ;)
20:34 luminous woot, two steps closer
20:34 luminous note that you do need to correct the url, clear cache, then restart
20:34 luminous current error has "\tnot-for-merge\tbranch 'master' of <repo> "
20:35 berto- joined #salt
20:41 mwillhite joined #salt
20:42 craig_ how do i get a list of jobs currently in the queue?
20:42 craig_ sudo salt-run jobs.active
20:42 craig_ ...
20:43 craig_ File "/usr/lib/python2.6/site-packages/salt/runners/jobs.py", line 32, in active
20:43 craig_ 'Arguments': list(job['arg']),
20:43 craig_ 0.15.3
20:43 JasonSwindle left #salt
20:43 JasonSwindle joined #salt
20:45 ksalman doing a file.recurse, is it not possible to replicate the execute bits, like they are on the master?
20:45 dthom91 joined #salt
20:47 UtahDave do you mean setting   +x  ?
20:47 ksalman or just copy the file_mode like they are on the server?
20:49 UtahDave I'm not sure if there's an option to keep the same file mode.  Have you looked at the docs?  I know you can set the file mode under your file.recurse
20:49 luminous ["ff6a88a\tnot-for-merge\tbranch 'master' of git+ssh://github.com/user/salt\n"]) <<< what does 'not for merge' translate to when you are talking about a clean clone?
20:50 ksalman Yea, there doesn't seem to be an option to keep the file mode
20:50 dthom91 +1 would be nice feature
20:50 ksalman yarr
20:51 luminous +1
20:52 forrest there's options for file_mode in file.recurse
20:53 luminous i think it's a blanket
20:53 ksalman yea
20:53 forrest oh you need a unique configuration on a specific file?
20:53 luminous when you want to retain the permissions of the files as they are on the master, you are sol
20:53 ksalman coping file_mode as they are on the server would be nice
20:53 dthom91 yep. consider a trivial case where you have /bin and /docs… do you really want to set them all to +x?
20:54 forrest why not just set all of the files one way, then use the basic file options to set the specific files you need with executables to exeutable?
20:55 forrest *executable
20:55 dthom91 I don't think it's a great practice to manage the same file in multiple places if you can avoid it… likely to get pretty confusing
20:55 forrest I don't disagree
20:55 forrest but if you have 1000 files and only one of them needs executable permissions
20:55 forrest it would suck to define all 1000 files
20:56 UtahDave ksalman: would you mind opening a feature request on that?
20:56 dthom91 so, to be clear, there are workarounds, but probably not as elegant as just maintaining the permissions as they're defined in the repo
20:56 forrest yea
20:56 ksalman UtahDave: I'll gladly open it :P
20:57 luminous speaking of repos
20:57 luminous ["ff6a88a\tnot-for-merge\tbranch 'master' of git+ssh://github.com/user/salt\n"]) <<< what does 'not for merge' translate to when you are talking about a clean clone?
20:58 luminous I've rm -rf'd everything in /var/cache/master/gitfs/ got the url correct, and restarted the master, this comes out of debug log
21:02 ksalman okay, i ahve never really submitted a feature request. I see a "new issue" link but I can't classify as "feature"?
21:03 ksalman i am guess the author does that?
21:03 ksalman guessing
21:03 UtahDave yeah, just mention it's a feature and we'll categorize it if you can't.
21:04 ksalman okay cool
21:04 it_dude joined #salt
21:06 mwillhite can anyone tell me where I can find an example of multiple applications setup with salt and vagrant? I'm brand new to this and having a little trouble figuring out how to put it together
21:06 mwillhite I have maybe a dozen or so separate apps, some of them being shared dependencies of other apps
21:08 UtahDave mwillhite: can you pastebin what you've tried so far?
21:08 mwillhite sure…though its not much
21:11 mwillhite UtahDave: here you go: http://pastebin.com/tRytH570
21:11 mwillhite there is really nothing there, I don't even know how to get started with this
21:11 hazzadous joined #salt
21:11 mwillhite most of the modules build…with the exception of nginx, mysql, rvm
21:12 UtahDave what error are you getting with those?
21:12 mwillhite nginx is missing passenger, I haven't looked into the others
21:12 mwillhite wanted to wrap my head around how this all works before I dig too deep into those things
21:13 mwillhite I don't even know if I'm approaching this the right way…
21:13 UtahDave well, I think you're on the right path.  You just need to make sure that any deps are handled.  You probably need to "require" some things.
21:13 mwillhite if I have separate apps…do they all live in the same space? or am I switching context somehow?
21:13 mwillhite with vagrant I get one box, but I don't know how things are managed beyond that
21:14 UtahDave well, are you familiar with how the top.sls works in conjunction with a highstate?
21:16 mwillhite not really…this is my second day into this stuff
21:17 UtahDave OK, so when you call a highstate the minion reads through your top.sls to determine which sls files it should apply to itself.
21:18 UtahDave So your top.sls is saying that all minions that match the glob '*' get that list of sls files applied to them.   So basically ALL minions.
21:18 Lue_4911 joined #salt
21:18 mwillhite Would I want different minions for my different applications?
21:18 UtahDave because you have them all split out nicely you can easily match different types of minions and give each separate applications if you wanted
21:19 UtahDave mwillhite: That's entirely up to you.
21:19 mwillhite for example, one of the apps follows this structure…there is a database that everything needs, then an api layer to pull the data out. the top level app is a javascript app that depends on the api
21:19 UtahDave One common scenario is that development boxes get ALL the applications
21:19 luminous mwillhite: depending on what you are trying to do, it may be easier to start with writing states and applying them with salt-call, rather than using the master/minion setup
21:19 UtahDave But then in staging and production they get split out among various servers for performance/security reasons
21:19 mwillhite ok
21:20 mwillhite so thats another thing, I keep seeing file_roots referenced for adding different states
21:20 mwillhite but I don't really understand how that fits into vagrant
21:21 mwillhite it seems maybe I need to setup a master configuration, whereas now I just have masterless
21:23 luminous again, it depends on what you are going for, and how much you want to bite off at once
21:23 luminous if you are going for the master/minion setup, and want to figure that out to start, that is a good place to start
21:24 luminous if you just want to write states for automating parts of your deployment, or app setup, etc, you might be fine focusing first on writing states and applying locally
21:24 luminous there are different flow
21:24 luminous *flows
21:25 mwillhite i want to bite off very little because I have no idea what I'm doing :P
21:26 luminous :)
21:26 mwillhite I'm really just trying to setup a dev environment that can be passed around
21:26 mwillhite because the setup for developing in this infrastructure is super annoying…and there are a lot of moving parts
21:26 luminous starting with salt-call and a masterless setup may be best
21:26 luminous have you seen the 'masterless' doc?
21:26 mwillhite ok…I'm looking at the masterless example in salty-vagrant
21:26 luminous yea, that makes sense
21:26 mwillhite looks like I can setup the file_roots there
21:26 luminous yep
21:26 mwillhite which will give me different states…
21:27 luminous usually something like /srv/salt
21:27 luminous you may prefer /etc/salt/states/
21:27 mwillhite ok
21:27 mwillhite I'm still a little confused on states vs environments
21:27 luminous environments are more of a thing for master/minino setup, least I don't think they apply to masterless setups
21:27 mwillhite for example…these different apps…are they different states, environments? or somethin else?
21:28 mwillhite ok
21:28 luminous states are files you write
21:28 luminous you can use different 'renderers'
21:28 luminous jinja2 (python templating engine) is the default
21:28 devinus joined #salt
21:29 mwillhite well say I build out everything for this api app, then I have the javascript/rails app that runs on top of it
21:29 luminous basically, this lets you express something like "manage the file /etc/hosts, its owner is root and mode is 0744, and source it from here"
21:29 mwillhite ok
21:29 luminous in short, the states are data that "map" to modules/functions that are called with various attributes you define
21:30 luminous so, continuing with the example, there's a file.managed function
21:30 luminous and a state for that would set the source, mode, user, group
21:30 luminous there are many state 'functions', for all sorts of things like databases, services, and users
21:30 luminous and you can write your own custom states
21:31 opapo_ joined #salt
21:34 luminous mwillhite: make sense so far?
21:34 mwillhite mmm, still trying to figure out how I can build up these apps using this system
21:34 mwillhite it makes sense a the level of permissions, etc
21:34 mwillhite but if I want to for example, build rails apps, run migrations
21:35 mwillhite I don't get where that fits in
21:35 auser joined #salt
21:35 KyleG1 joined #salt
21:35 mwillhite would I use the state functions to perform those actions?
21:35 luminous mwillhite: if you want to run arbitrary commands, there is cmd.run state
21:35 luminous you can then 'hook' everything together in various ways
21:35 mwillhite and that is a "state function"?
21:36 luminous for example you could have a state require another, so it must have the requirement fulfilled before being applied
21:36 luminous or you could use 'watch' which will rerun a state when the 'watched' state changes
21:36 luminous so maybe you run a migration when the repo changes
21:36 luminous or something
21:36 mwillhite so essentially for each app I could put together a series of these states
21:36 luminous yep
21:37 mwillhite and maybe my top level javascript app requires the other apps that require other states
21:37 mwillhite or something like that :P
21:37 luminous I usually have common / base services, stuff for admin / user management, and then apps
21:37 luminous exactly
21:37 luminous it might help to look at some states in github
21:37 luminous have you seen the salt-formulas repos?
21:37 mwillhite ok, the fog is clearing a little bit
21:37 mwillhite yes
21:37 luminous https://github.com/saltstack-formulas/
21:38 mwillhite I'm using that for git, ack and a few other things
21:38 mwillhite I added them as submodules and reference them in my top.sls
21:38 mwillhite as part of the base: '*
21:38 luminous https://github.com/saltstack-formulas/nginx-formula/blob/master/nginx/init.sls <<< pretty good example
21:38 mwillhite yes
21:38 luminous note 'pillar' in there
21:38 mwillhite okay, this is starting to come together for me
21:39 mwillhite so that .sls is really just comprised of "states"
21:39 mwillhite then those states have several state functions
21:39 luminous yep
21:39 mwillhite what about pillar?
21:39 luminous internally, somethign like file.managed is a managed() in states/file.py
21:39 luminous so pillar is wonderful
21:39 luminous it's how you 'abstract out' the details
21:40 mwillhite so its like a data mapper?
21:40 luminous so, if you see here https://github.com/saltstack-formulas/nginx-formula/blob/master/nginx/files/upstart-logger.jinja
21:40 luminous that's a simple example, the others in that repo are messy and difficult to follow
21:40 oz_akan_ joined #salt
21:40 mwillhite heh
21:41 luminous pillar is a giant dictionary of key/value pairs
21:41 luminous where each value can be a string, list, or dictionary
21:41 luminous so you can have a 'users' state, then say, "for each user in my users list, apply this state, pull the username, shell, password, and all that other stuff like a dotfiles git repo from pillar"
21:42 mike25ro luminous: nice explained!
21:42 luminous I don't know if you can use pillar with masterless, I would assume so, but check on that
21:42 devinus joined #salt
21:42 luminous mike25ro: thanks :)
21:42 mwillhite i haven't seen an example of a pillar file
21:42 gatoralli joined #salt
21:43 mwillhite looks like they are sls so I assume its the same format…and are you always building your own?
21:43 mike25ro mwillhite: there are a lot
21:43 mwillhite is it just to have shared data?
21:43 luminous https://github.com/saltstack-formulas/openstack-standalone-formula/blob/master/pillar.example
21:43 gatoralli Is there a way for me to see all loaded states on my salt-master instance
21:43 mike25ro mwillhite: you can have a pillar SLS for each minion - this is how i started my tests
21:43 luminous mwillhite: actually, it lets you tie specific data to specific minions
21:44 luminous so not shared amongst all minions
21:44 luminous whereas "grains" are, this is another dictionary that has stuff like system type, cpu, ram, etc
21:44 mike25ro mwillhite:  usually one designs a pillar for a specific minion / group of minions that share the same logic
21:44 mwillhite ok
21:45 luminous you could, for example, create a generic nginx vhost config, and then populate a bunch of vhosts using details pulled from pillar
21:45 mike25ro mwillhite:  you can even target ... which pillar goes to which minion based on the minion's grains
21:45 mwillhite so back to the minions…if I do a masterless setup, am I just using one minion? or whats the pattern with those guys?
21:45 luminous masterless just uses the salt-call utility, there's no concept of a master/minion
21:45 mwillhite hm ok that makes sense
21:46 luminous so you could apply states with something like: salt-call --local state.highstate
21:46 mike25ro mwillhite:  i haven't used a masterless setup ... for me the master... is really useful
21:46 mwillhite so my minion wouldnt do antyhing
21:46 luminous as opposed to salt 'some_minion' state.highstate
21:46 mwillhite ok
21:46 luminous the 'some_minion' is my target
21:46 mike25ro mwillhite:  from the master you can run salt 'some minion' state.sls  myStateFile.sls
21:47 luminous no .sls there
21:47 mwillhite so what does it mean that "salt-call was not found"
21:47 mwillhite where do I get that?
21:47 luminous just myStateFile
21:47 mike25ro luminous: indeed .. sorry my bad... salt 'some minion' state.sls  myStateFile  this one is correct
21:47 luminous mwillhite: do you ahve salt-minion installed? I think it's in that packatge
21:47 mike25ro i am also a newbie
21:47 luminous mike25ro: I still consider myself a newb :P more like an advanced newb
21:48 luminous considering all the stuff you can do with events, the salt-mine, etc, etc
21:48 mwillhite well I have a minion…
21:48 mwillhite haha I don't know if I have it installed
21:48 mike25ro luminous:  :) salt is so flexible... that i think i am going to be a newb.. for the next 1-2 years
21:48 mwillhite I just setup vagrant and salty-vagrant
21:48 mwillhite so I'm assuming no
21:49 mwillhite ah according to salty-vagrant docs
21:49 mwillhite they permit me a standalone minion
21:49 ipmb joined #salt
21:50 mike25ro mwillhite:  ... i am not an expert... but you can easily install in virtualbox 2 vms : one to be master and the second minion ... and only this setup will let you realize the FULL potentian of SALT....
21:51 mwillhite ha…I'm trying to keep it as simple as possible for now
21:51 luminous :)
21:51 mwillhite even I can just get some apps up and running I'll be ecstatic
21:51 mwillhite thanks luminous, this helps a lot
21:51 mwillhite I'll sure I'll have more questions moving forward, but the state thing is huge
21:51 luminous yw, I need to focus on some other stuff but will try to check back in a bit
21:52 luminous yea, there's a lot to wrap your mind around
21:52 mwillhite tons…really cool stuff though
21:52 luminous this salt stuff is a game changer though :) you've made a good choice to come this far
21:53 mike25ro luminous:  is right ...  i just came here 2 weeks ago... and since then ... everyday salt lets me do something awesome
21:54 luminous and it only gets better
21:54 luminous this is going to play a big part in revolutionizing how we do things
21:54 luminous so long as we keep it up and don't get stuck like puppet
21:54 luminous :P
21:55 george_torwell joined #salt
21:56 mike25ro luminous: yea... puppet seemed to me a bit scary
21:56 mike25ro i might be wrong... but i definitely like salt better
21:56 luminous I spent more than a year working on stuff that I reimplemented in ~2 weeks in salt
21:56 luminous well, the big difference is that salt is other stuff, AND a configuration management tool
21:56 luminous puppet is a config management tool
21:57 luminous and it's written in ruby, so that kinda limits it
21:57 luminous not that ruby is flawed, but python has a much stronger community
21:57 luminous the yaml security holes of earlier this year are a good example of that
21:58 mike25ro luminous:  i am not a py dev... so this is what i am doing ... now.. learning a bit of py .. to help me out with salt
21:59 luminous you'll appreciate that as you get more into custom states and stuff
21:59 luminous but you certainly can get really far without too much python exp
21:59 mike25ro yes indeed, but i like to get as close to perfection as possible.. to know as many...
21:59 mike25ro that's why i am asking a lot of Qs here
22:00 luminous :)
22:01 Rorgo joined #salt
22:04 gatoralli Is there a way to view all loaded configuration/states for salt-master?
22:05 luminous gatoralli: there's grains.ls and pillar.data
22:05 luminous but I don't know about /loaded states
22:05 dthom91 joined #salt
22:06 Rorgo is there any easy way to get a python list of the accepted salt keys?
22:07 Rorgo short of like running 'salt-key --out=json' through subprocess anyway..
22:08 gatoralli it looks like pillar.data does what i'm looking for. thanks
22:08 luminous Rorgo: the mailing list might have some thoughts to share in history
22:08 Jahkeup joined #salt
22:10 UtahDave Rorgo: The python api has a the ability to give you a list of accepted keys, I believe
22:11 UtahDave Rorgo: also, you could just ls the /etc/salt/pki/master/minions  directory
22:13 baniir joined #salt
22:14 gatoralli joined #salt
22:41 berto- joined #salt
22:48 aat joined #salt
22:49 troyready joined #salt
22:51 oz_akan_ joined #salt
22:52 kermit joined #salt
22:53 lemao joined #salt
22:59 mwillhite I added the ruby-formula as a submodule from saltstack-formulas…the same way I added git, vim and others. but when it tries to build I get this error: Specified SLS base: ruby-formula is not available on the salt master in environment(s): base
22:59 mwillhite does that mean that its not finding it?
22:59 mwillhite what exactly does that mean?
23:00 UtahDave yeah, it's not finding your formula.
23:01 mwillhite does it just drill down directories until it finds an init.sls?
23:02 mwillhite because the git one is structred as ./git-formula/git/init.sls
23:02 UtahDave no, it doesn't
23:02 mwillhite hm
23:03 UtahDave so if you have   - ruby-formula    in your top.sls, then by default it's going to look for  /srv/salt/ruby-formula.sls  or /srv/salt/ruby-formula/init.sls
23:03 mwillhite thats how all of the https://github.com/saltstack-formulas/ formulas are structured
23:03 mwillhite I'm missing something here…
23:05 UtahDave you probably need to copy the contents of ruby-formula to your file_roots, not the top level directory
23:05 mwillhite thats where I'm confused though, because I didn't do that for git or vim and those are just fine
23:06 mwillhite actually…I think there something special about those two
23:07 UtahDave are you putting   - git-formula.git  in your top.sls?
23:07 mwillhite I don't understand it, but looking at other submodules that I have, they have the init in the top directory
23:07 mwillhite yeah
23:07 mwillhite and vim-formula.vim
23:08 mwillhite oh
23:08 mwillhite haha
23:08 mwillhite its the dot indicates a new directory right?
23:08 mwillhite derp
23:08 mwillhite thanks
23:08 mwillhite so I could just do ruby-formula.ruby
23:08 jschadlick left #salt
23:08 jslatts joined #salt
23:17 UtahDave yep!
23:32 mwillhite how do I use the built-in salt.state modules? for example if I want to include rvm…
23:33 berto- joined #salt
23:40 jslatts joined #salt
23:53 cnelsonsic joined #salt

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