Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-02-05

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

All times shown according to UTC.

Time Nick Message
00:03 warmwaffles anyone know why the `python2-msgpack` is failing to install for Arch?
00:04 warmwaffles I keep getting "invalid or corrupted package (PGP signature)"
00:04 Gifflen joined #salt
00:05 bemehow it's work in progress but here you go: https://github.com/bemehow/salt/compare/saltstack:develop...develop
00:06 n8n joined #salt
00:06 forrest oh this is a module, gotcha
00:06 forrest that's cool
00:08 n8n joined #salt
00:11 n8n joined #salt
00:14 n8n joined #salt
00:32 BenCoinanke joined #salt
00:33 gnu-man1 joined #salt
00:34 mgw joined #salt
00:35 rojem joined #salt
00:45 KyleG joined #salt
00:45 KyleG joined #salt
00:46 Gifflen joined #salt
00:48 Poooogles joined #salt
00:52 Ryan_Lane1 joined #salt
00:53 steveoliver joined #salt
00:53 bhosmer joined #salt
00:58 d10n joined #salt
01:04 justBob joined #salt
01:05 iamveen joined #salt
01:07 iamveen Hi guys, does anyone know if there exists some instructions for setting up salt-ssh on OS/X? I'm having a hell of a time trying to get everything working. Basically I just have no idea where everything goes.
01:08 iamveen Doesn't even really need to be OS/X specific, any salt-ssh setup documentation would be really helpful
01:09 KyleG left #salt
01:18 clearclaw Has 15:54 | bemehow > if anyone is interested in extfs states I will try to contribute  them after some cleanup
01:19 clearclaw Sorry
01:19 clearclaw has delete_sshkeys moved away from /etc/salt/cloud?
01:41 dave_den joined #salt
01:42 AdamSewell joined #salt
01:42 [diecast] joined #salt
01:42 gnu-man1_ joined #salt
01:44 xmltok joined #salt
01:46 mbarrien joined #salt
01:59 mgw joined #salt
02:02 mgw joined #salt
02:14 ravibhure joined #salt
02:17 joehh joined #salt
02:20 iamveen joined #salt
02:21 iamveen Hello. Do you guys know where salt-ssh looks for states by default? I'm having a difficult time getting it to do anything :\
02:23 forrest iamveen, standard /srv/salt/
02:31 iamveen joined #salt
02:32 iamveen Sorry, got disconnected... that web client sorta sucks.
02:33 forrest states are stored in the same location as always iamveen, /srv/salt/
02:33 iamveen So ya, I basically put top.sls and apache.sls in /srv/salt, but they seem to be ignored.
02:33 iamveen test.ping works and I can run commands
02:34 Ahlee salt-ssh requires local states, right?
02:34 Ahlee i have no idea, I used it once to restart salt-minions then promptly forgot about it as pssh was faster
02:35 forrest salt-ssh just relies on the states being on the master, try salt-ssh 'minion' state.sls state_name -l debug
02:35 forrest and see what happens
02:35 forrest could be that the timeout value is just getting reached, so the action completes but pushes you back to the console, in that case try -t 20
02:35 cedwards I've been playing with salt-ssh recently, but haven't tried using states yet.
02:36 iamveen k, one sec.
02:36 Ahlee good call forrest
02:36 forrest this is why I get paid those big internet dollars
02:37 Ahlee dollar dollar bill, ya'll
02:37 salt-noob joined #salt
02:37 sroegner joined #salt
02:38 iamveen hrmm, Function srv/top.sls is not available
02:39 forrest your top is in /srv/salt right?
02:39 iamveen When I run 'salt-ssh 'bhs01' srv/top.sls state.highstate -l debug'
02:39 cedwards drop the srv/top.sls
02:39 Ahlee that should jsut be salt-ssh 'bhs01' state.highstate -l debug
02:39 iamveen Well /srv/salt is a symlink to ./srv
02:39 iamveen so that I can keep everything in one dir
02:40 Ahlee the call to state.highstate is going to look into your top file and execute the states matched for bhs01
02:40 iamveen Ahlee: Ya, that's what I was expecting, but it doesn't do anything
02:41 iamveen I get a row of "------------" and then nothing
02:42 forrest that's why I'm suggesting to just target a minion, then use one state
02:44 bhosmer joined #salt
02:44 Ahlee i'd have to set up a salt-ssh config and poke, and i have a mere 6 minutes of battery left
02:44 carmony joined #salt
02:44 Ahlee as such, i shall be bowing out as you're in forrest's capable hands
02:44 carmony there we go, ZNC fixed
02:44 iamveen forrest sorry, I don't even know how to do that... I'm a total newb to salt... this is my attempt to learn it
02:46 ilbot3 joined #salt
02:46 Topic for #salt is now Welcome to #salt | Thanks to everyone who made SaltConf 2014 amazing! | 0.17.5 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/
02:47 seb` joined #salt
02:47 iamveen top.sls and apache.sls
02:47 forrest so the state name would be apache
02:49 iamveen salt-ssh 'bhs01' apache.sls apache  ->  Function apache.sls is not available
02:49 forrest no, salt-ssh 'bhs01' state.sls apache -l debug
02:49 forrest state.sls says "I want to use a state"
02:49 forrest and then you provide it the name of a state
02:50 iamveen oh!
02:51 cedwards grumble. trying to use states over salt-ssh on freebsd gives a Traceback
02:51 Ahlee ok, charger aquired
02:51 iamveen bam. that worked.
02:51 forrest iamveen, ok so if you got data back that time, you might want to try salt-ssh 'bhs01' state.highstate -l debug -t 20
02:52 forrest to increase the timeout
02:52 forrest or you can omit the debug logging
02:52 Ahlee i see my work here is done
02:52 Ahlee ;)
02:52 forrest but if state works, and highstate errors, then there might be a problem with your top file
02:52 forrest This is why we keep you around Ahlee
02:52 iamveen no such option: -t
02:53 forrest does salt-ssh not use the timeout option? I never remember.
02:53 cedwards i don't think it does
02:53 cedwards it's not in the man page
02:53 jdenning joined #salt
02:53 forrest gotcha, then just run it with debug and see what happens to confirm whether there is an error or not
02:54 iamveen I don't see any errors :\
02:54 forrest with -l debug?
02:54 forrest yet the output is just --------- ?
02:54 forrest what's in your top.sls
02:56 iamveen what the f
02:56 iamveen base:
02:56 iamveen 'bhs01':
02:56 iamveen - apache
02:57 iamveen I changed bhs01 to * and now it works :\
02:57 MTecknology so... templated files are built client side, so I can't really be querying for a list of accepted minion keys; so... what I really want is mine so that this template file can be aware of all other minions, right?
02:58 forrest could be an issue with how the hostname is being interpreted perhaps? As in on your network it treats bhs01.my.domain and respond to bhs01, but targeting that in the top might not work.
03:00 manfred joined #salt
03:00 iamveen do you know if that refers to the id in the roster or the hostname?
03:00 MTecknology iamveen: well... use nginx
03:00 forrest I thought it was the roster file, but I'm not familiar enough with the salt-ssh targeting to be 100% sure
03:00 MTecknology whatevery your issue, it'll be solved!
03:00 MTecknology (only 15% serious)
03:01 18WAFPFSX joined #salt
03:01 iamveen nginx must be pretty magical to fix this :)
03:01 jeter_ joined #salt
03:02 iamveen fyi, you CAN set a timeout in the roster file per host
03:02 forrest good to know
03:03 jeter_ can you request gpgkey for salt.states.pkgrepo remotely like ( - gpgkey: salt://nginx/nginx_signing.key )
03:06 forrest jeter_, that's a good question and I'm not sure, if you try and test it and it works, can you create an issue, or a pull request to update that in the docs?
03:07 jeter_ how do i update the docs? git?
03:07 forrest on github yea
03:07 jeter_ im testing it nwo
03:07 forrest ok
03:07 forrest if you don't wanna update it create an issue and someone will get around to it
03:08 felixhummel joined #salt
03:09 jeter_ never done it but heres to learning
03:09 forrest did it work?
03:10 Ahlee I can not reproduce this stupid issue that bit me in prod today with grains.setval not being immediately available
03:10 forrest are you still at work?
03:10 Ahlee kind of.
03:11 Ahlee I'm still working, but not at the office
03:11 forrest gotcha
03:12 Ahlee oh. would probably help if i tested on same version in prod
03:12 forrest lol
03:17 rgbkrk joined #salt
03:20 jeter_ and no, it doesn't work
03:20 forrest bummer
03:20 jeter_ im going to add it as a feature request
03:21 forrest sounds good, they might suggest putting it on there via file.managed, but we'll see.
03:21 jeter_ yah, thats my way around it
03:23 Ahlee well, salt minion grains.setval vanilla ice; salt minion grains.item vanilla
03:23 Ahlee that failed, but subsequent calls worked
03:24 forrest Ahlee, are you sure the grain was synced to the minion that first time when it ran?
03:24 Ahlee forrest: it was all done via setval, which should be immediate
03:24 forrest gotcha
03:24 Ahlee i have logged calls of saltutil.sync_grains
03:24 Ahlee well, "immediate"
03:24 Ahlee while we tried to figure it out
03:25 Ahlee but, without being able to reproduce
03:25 fridiculous joined #salt
03:25 Ahlee i don't want to report since we're still on 0.17.2 with no reproduction step
03:25 forrest yea
03:25 forrest I assume you can't dup it on 0.17.4/5
03:25 Ahlee nope
03:25 fridiculous is there a good way to download tar files from source, configure, make and install them without 6 cmds?
03:25 Ahlee can't dupe on 0.17.4 or develop from Friday
03:25 forrest fridiculous, obviously, cmd.run one big command! :D
03:25 Ahlee fridiculous: cmd.script
03:26 Ahlee can you package them in your OS's package of choice?
03:27 fridiculous nah, i'm going to probably script it
03:28 Ryan_Lane1 joined #salt
03:36 tvle joined #salt
03:37 lahwran joined #salt
03:41 fejjerai joined #salt
03:51 yomilk joined #salt
03:57 pdayton joined #salt
04:00 warmwaffles joined #salt
04:01 warmwaffles Had to turn off package signing on Arch in order for me to get it working with salt and vagrant =/
04:01 warmwaffles womp womp
04:06 oz_akan_ joined #salt
04:08 jeremyfelt joined #salt
04:09 AdamSewell joined #salt
04:14 jdenning joined #salt
04:22 seb` joined #salt
04:23 analogbyte joined #salt
04:24 robthoms joined #salt
04:28 [M7] joined #salt
04:30 bhosmer joined #salt
04:44 Gifflen joined #salt
04:45 wolfpackmars2 joined #salt
04:50 joshe joined #salt
04:58 anitak joined #salt
05:01 tvle joined #salt
05:10 [diecast] joined #salt
05:16 ravibhure joined #salt
05:22 chitown i was thkning about adding a simple bash script for bootstrapping a virtualenv
05:22 chitown does that mke sense in "salt-bootstrap"?
05:22 chitown that seems to be more for real deployment, not localhost
05:22 chitown thoughts?
05:22 chitown (yes, it's late... i'll try to ping this again during normal time: PST :)
05:23 forrest chitown, I'd suggest to open an issue on the bootstrap script
05:24 forrest I know that in the past s0undt3ch has wanted to keep it pretty lean, but if it could be worked in and retain the 'clean' layout it has now, I don't see why he'd be against it
05:29 middleman_ joined #salt
05:32 jalbretsen joined #salt
05:42 jdenning joined #salt
05:44 MK_FG joined #salt
05:52 Gifflen joined #salt
06:01 apergos basepi: pong (it was after midnight here, I was sleepnig)
06:01 forrest apergos, he's probably on his mobile so he might not see it
06:01 apergos ah
06:02 apergos ah I see, comments on the bug
06:02 apergos I'll check it out once I'm properly awake. sweet
06:03 forrest cool
06:04 rojem joined #salt
06:06 kermit joined #salt
06:08 anuvrat joined #salt
06:10 jdenning joined #salt
06:15 Psyke joined #salt
06:17 zz_Cidan joined #salt
06:18 bhosmer joined #salt
06:23 sroegner joined #salt
06:24 conf joined #salt
06:24 conf what is salt sls? what for it it used?
06:26 forrest sls's are SaLt States
06:26 forrest so they're just state files
06:27 shadowsun They're used in the control of configuration on remote machines
06:27 shadowsun I wrote one today to manage the state of /etc/yum.conf so that all the machines have the same !#$%!#R$5ing one
06:27 * shadowsun passes out now
06:29 shadowsun conf: http://docs.saltstack.com/topics/tutorials/starting_states.html
06:30 conf thanks all
06:38 salt_ joined #salt
06:41 joehillen joined #salt
06:42 new_to_salt joined #salt
06:43 new_to_salt hello all
06:43 new_to_salt i am trying to use salt to look up process table of windows machines
06:48 pydanny joined #salt
06:49 new_to_salt left #salt
07:19 JordanRi1ke joined #salt
07:24 jimallman joined #salt
07:31 [diecast] joined #salt
07:57 Ryan_Lane joined #salt
07:58 rojem joined #salt
07:59 balboah joined #salt
08:06 Franz__ joined #salt
08:07 gammalget joined #salt
08:09 ndrei joined #salt
08:11 martoss joined #salt
08:12 sroegner joined #salt
08:13 ravibhure joined #salt
08:14 mike25ro joined #salt
08:16 mike25ro hi guys ... i have manually deleted /etc/salt/pki/master/minions/minion.test.com  - and i was expecting .. that i see that minion in the list of pending keys ... since its key is no longer there... should i do smth else in order to be able to re-accept that minion ?
08:16 harobed_ joined #salt
08:18 giantlock_ joined #salt
08:20 gnu-man1 joined #salt
08:20 _Flusher joined #salt
08:21 ndrei joined #salt
08:23 che-arne joined #salt
08:24 miguitas joined #salt
08:27 lessismore joined #salt
08:27 juso joined #salt
08:27 martoss1 joined #salt
08:31 Tanoti joined #salt
08:31 che-arne joined #salt
08:32 hotbox joined #salt
08:34 wendall911 left #salt
08:34 yomilk joined #salt
08:36 Ryan_Lane joined #salt
08:37 Poooogles joined #salt
08:39 tomspur joined #salt
08:39 tomspur joined #salt
08:49 mike25ro hey guys anyone around?
08:52 zooz joined #salt
08:53 Ryan_Lane joined #salt
08:56 Franz__ joined #salt
08:56 balboah mike25ro: did you restart the minion?
08:56 mike25ro balboah: no need.. it came up after 2 minutes or so
08:56 Franz__ joined #salt
08:57 mike25ro balboah:  i have a small issue.. maybe you have an idea... is it possible to have a file.append depending on the EXIT status of a bash script?
08:58 mike25ro the idea .. .is to append 1 line at the end of /etc/fstab .. but in some cases on some servers... there is something to mount... so i was thinking of creating a bash script to remove that last line and then only append from the state.... am i making any sense?
08:59 wahbaduck joined #salt
09:00 wahbaduck left #salt
09:00 mbarrien joined #salt
09:01 mbarrien Should a pull request for something that is broken in the 2014.1.0RC3 go against the 2014.1 branch, or just against develop?
09:03 balboah mike25ro: you can use http://docs.saltstack.com/ref/states/all/salt.states.cmd.html#salt.states.cmd.script and let the script say if it "changed" or not, which you watch in the file.append. Or something like that
09:07 mike25ro balboah: hmm ... not sure i understand ... how should i do it  .. how do i .. let the script know it has changed anything? via the exit? how can the file.append watch that? i know i am an ass to ask so many questions...
09:08 balboah you have to modify the script to tell salt if it "changed" or not. which will replace the exit code check. but maybe theres a way to only care about exit code as well
09:09 mike25ro i mean ... how to check in the state for the output of a shell script?
09:09 balboah if cmd.script stateful=true then the script can print changed=yes
09:09 ndrei joined #salt
09:09 balboah and then all states that have a watch requisite on it will trigger
09:09 mike25ro ah.. i have to check the stateful
09:11 mike25ro thanks balboah
09:12 mbarrien Reasking my earlier question… if I have a pull request to fix a bug in 2014.1.0RC3, should I make the pull request against the 2014.1 branch or the develop branch? Specifically, do I need to close https://github.com/saltstack/salt/pull/10197 and re-open it so that it is merging to develop or do I leave it alone and have it merge into 2014.1?
09:22 n8n joined #salt
09:40 yomilk joined #salt
09:42 MrTango joined #salt
09:43 ajw0100 joined #salt
09:47 zooz joined #salt
09:49 Poooogles joined #salt
09:49 slav0nic joined #salt
09:50 salt_new joined #salt
09:51 salt_new this is my mypackage.sls file top.sls: ========    base:     '*':     - mypackages       mypackages.sls:      =================    svn:    pkg.installed      - fromrepo: http://mirror.cogentco.com/pub/apache/subversion/      - skip_verify: True
09:51 salt_new my result is  sudo salt '*' mypackage.sls paris:     "mypackage.sls" is not available.
09:54 y0j joined #salt
09:55 bhosmer joined #salt
09:55 jpihl_ joined #salt
09:55 jpihl joined #salt
10:01 Flusher joined #salt
10:01 sroegner joined #salt
10:02 Psyke joined #salt
10:13 cyrusdavid joined #salt
10:17 JordanRinke_ Morning
10:17 ckao joined #salt
10:18 x5257 joined #salt
10:30 yomilk joined #salt
10:30 viq basepi: I was told to poke you about this. Say I have a StateA, pkg.install postgresql and some related tasks, StateB which is git.latest, and StateC being cmd.wait which watches StateB but also depends on StateA. Say StateA failed, but StateB succeeded, is there a way to make StateC run besides, say, removing the git checkout?
10:31 viq Also, I seem to be seeing a... bug, maybe? CentOS 6.5, salt 0.17.4, pkg.install(ed) postgresql-server does not run the post-install scripts of the rpm
10:33 viq (please highlight me with answers, I'm not able to watch the channel all the time)
10:41 Franz__ joined #salt
10:47 kiorky joined #salt
10:55 balboah how was it that you compiled all the states and requisites  and show the final result in how it will be ran after all includes and extends etc?
11:12 ndrei joined #salt
11:15 anuvrat joined #salt
11:21 iri joined #salt
11:22 iri Hi All. I have salt://myservice/id_rsa.pub and I want to make a file.managed state which creates an /home/myservice/.ssh/authorized_keys, where the authorized keys has lots of text prepended to the pubkey
11:22 iri What's the best way to achieve that?
11:22 iri Can I template in the contents of a salt:// file?
11:22 jbirdman joined #salt
11:23 honestly yes.
11:24 honestly http://docs.saltstack.com/ref/states/all/salt.states.file.html
11:25 honestly unless you mean using a file as the template content...
11:27 iri Yes, that's what I mean
11:27 iri I have a file with PUBKEY in it, and I want to create a new file with "FOO PUBKEY" in it
11:27 iri based in salt://se
11:27 iri myservice/key.pub
11:28 iri maybe it can be achieved with file.accumulated?
11:29 honestly you could probably do that with some jinja hackery
11:30 honestly if you find out how to query the salt:// "filesystem" via direct calls
11:30 qwer joined #salt
11:31 iri honestly: I think the answer might be https://salt.readthedocs.org/en/latest/ref/states/all/salt.states.ssh_auth.html :)
11:32 qwer 610 15:22 this is my mypackage.sls file top.sls:  ========   base:  '*':  - mypackages   mypackages.sls:  =================  svn:  pkg.installed  - fromrepo: mirror.cogentco.com/pub/…  - skip_verify: True this is my result @rome:~$ sudo salt '*' state.highstate test=True  paris:  ----------  State: - no  Name: states  Function: None  Result: False  Comment: No Top file or external nodes data matches found  Changes:   Summary  ------
11:33 qwer this is my mypackage.sls and result http://pastebin.com/gdqQ2YxM
11:33 qwer let me know the changes to be done in the mypackage.sls
11:34 sroegner joined #salt
11:44 vejdmn joined #salt
11:45 Shenril joined #salt
11:47 iri is there a way with jinja to get the home directory for a user?
11:47 iri I want to have a file.managed directive for ~myuser/foo
11:48 nkuttler iri: just pass the username as a var?
11:48 iri nkuttler: the home directory might not be at /home
11:49 nkuttler iri: is ~/name/ not recognized?
11:49 iri Do you mean ~name?
11:49 nkuttler bah, yeah
11:50 iri nkuttler: apparently not. It complains "it is not an absolute path"
11:51 nkuttler iri: i see. personally i have the home dir stored in a pillar
11:52 iri well in this case I just want to copy a pub/private key. I used user.present to create the (system) user which happened to put the home directory in /var/lib/{user}
11:52 iri so I wanted to know a portable way to write ~userdirectory/
11:52 iri (because for the next user it might not be at /var/lib)
11:54 nkuttler yeah, odd, i'm just looking through the modules and don't see anything obvious
11:55 vejdmn joined #salt
12:00 iri ugh, just ran a salt command and got no output whatsoever, nothing in the logs to indicate what went wrong, either
12:01 iri second time it succeeded, but whatever changed the first time is now lost :(
12:01 munhitsu hi all is there any good example of pydsl used to create library of reusable code (stuff that one would normally put as ninja macros)?
12:05 iri I'm using file.recurse to copy a directory with lots of symlinks
12:05 iri I've set keep_symlinks, force_symlinks and sym_mode but when it updates the target directory it copies through the symlink, wth?
12:06 vejdmn joined #salt
12:06 drawsmcgraw joined #salt
12:09 ndrei joined #salt
12:10 Poooogles joined #salt
12:10 babilen Hmm, it appears as if includes aren't working for pillars. I've tried different variations (started out with foo/init.sls that includes .bar, then foo/init.sls that includes foo.bar, then foo.sls that includes foo-bar.sls) -- The only time it seems to work is if I list *everything* directly in top.sls
12:11 babilen Anything I can do to mititagate that as it really isn't beautiful to have to have a huge collection of files and having to list everything in top.sls
12:11 babilen ?
12:12 Poooogle_ joined #salt
12:13 Poooogle_ Always reassuring to see the leased line drop out :o
12:14 diegows joined #salt
12:16 brianhicks joined #salt
12:20 kedo39 joined #salt
12:22 munhitsu why singleton magic works only within an sls file it would have been more natural for it to also work on included states
12:23 munhitsu w/o a need to extend a state to create a new function on it
12:23 munhitsu re: pydsl
12:24 x5257 joined #salt
12:30 testit joined #salt
12:37 Whissi joined #salt
12:38 babilen Can I somehow reference whatever matched in the glob? I am trying to say "foo-bar-1:\n  - foo.bar.1" and don't necessarily want to enumerate all numbers (i.e. hosts) Can I somehow define a regular expression with groups and the reference to that? (e.g. "foo-bar-(\d+):\n - foo.bar.\1" (or so))
12:39 helminthe joined #salt
12:43 qwer @rome:~$ sudo salt '*' pkg.install mypackage.sls paris:     ----------
12:43 babilen qwer: Doesn't pkg.install take the package name?
12:43 qwer no
12:44 qwer @rome:~$ sudo salt '*' pkg.install paris:     ----------
12:44 babilen qwer: Which package are you trying to install?
12:44 drawsmcgraw joined #salt
12:45 qwer mypackage.sls
12:45 babilen That's not the actual package name now, is it?
12:45 qwer no it is mypackage name
12:46 babilen qwer: So, which actual package are you trying to install and what happens if you run "salt '*' pkg.install $ACTUAL_NAME_OF_THAT_PACKAGE" ?
12:46 qwer http://pastebin.com/GirK4JHF
12:46 qwer this is my content
12:47 qwer @rome:~$ sudo salt '*' pkg.install paris:     ----------
12:47 mike25ro can i use a salt.module in a state or jinja? like salt '*' file.get_uid /etc/passwd ... but use that in a jinja or state
12:47 qwer this is the result
12:47 drawsmcgraw joined #salt
12:48 babilen qwer: I think you either want to run "salt '*' state.sls mypackage.sls" or "salt '*' state.highstate" or "salt '*' pkg.install pkgs='["svn", "apache"]'"
12:48 babilen qwer: highstate naturally requires a suitable top.sls
12:48 kedo39 joined #salt
12:48 jrdx joined #salt
12:49 qwer ok thanks, i will let you know the result once i try. i wil try now
12:50 zzzirk joined #salt
12:51 danielbachhuber joined #salt
12:51 qwer i have all those things and pasted the results in this link http://pastebin.com/5sDM0By7
12:52 qwer please do let me know what needs to be done
12:52 qwer babilen: i have all those things and pasted the results in this link http://pastebin.com/5sDM0By7
12:53 zooz joined #salt
12:53 drawsmcgraw1 joined #salt
12:53 zooz joined #salt
12:54 babilen qwer: What about "sudo salt '*' state.sls mypackage" ?
12:54 babilen qwer: You also don't seem to have a top.sls
12:55 qwer let me know what should be in top.sls
12:56 qwer babilen: let me know what should be in top.sls
12:57 drawsmcgraw joined #salt
12:59 vejdmn joined #salt
13:00 Shenril joined #salt
13:07 Franz__ joined #salt
13:09 babilen patience!
13:10 blee joined #salt
13:14 arthurlutz joined #salt
13:14 arthurlutz #minibugreport : end of http://docs.saltstack.com/topics/releases/2014.1.0.html isn't properly converted to HTML
13:15 arthurlutz and https://github.com/cro/salt-proxy-rest ends up on a 404
13:18 ndrei joined #salt
13:19 AdamSewell joined #salt
13:20 harobed_ joined #salt
13:21 harobed_ joined #salt
13:21 harobed_ joined #salt
13:22 che-arne joined #salt
13:22 harobed_ joined #salt
13:23 harobed_ joined #salt
13:33 elfixit1 joined #salt
13:38 elithrar joined #salt
13:39 ipmb joined #salt
13:42 Vivi-Idle joined #salt
13:44 ndrei joined #salt
13:45 logix812 joined #salt
13:46 jdenning joined #salt
13:47 mike25ro left #salt
13:51 BogdanR Can I run commands with salt-ssh on a machine which doesn't have the minion installed?
13:51 njpatel joined #salt
13:52 Poooogles joined #salt
13:52 BogdanR I am pretty sure I can but I can't figure out how to specify that I want to run the "ps aux" command on the 10.0.0.5 machine
13:53 oz_akan_ joined #salt
13:54 Poooogles joined #salt
13:58 jslatts joined #salt
14:03 ay_ joined #salt
14:03 ay_ Hi. Just a quick question. Is it possible in salt to search for node based by grains by something else than globs? For example I want to search for boxes with uptime higher than 300 days.
14:04 ay_ So searching with "less than" or "greater than"
14:04 ay_ On grains
14:04 Ahlee BogdanR: salt-ssh -S 10.0.0.5/32 cmd.run 'ps aux'
14:04 tessellare joined #salt
14:05 Gifflen joined #salt
14:06 Ahlee ay_: hm.
14:08 vejdmn joined #salt
14:08 juicer2 joined #salt
14:10 Ahlee ay_: doesn't look like grains.filter_by has a comparator
14:10 Ahlee i can't think of a way to do it, not that that's saying much
14:10 Ahlee might be worth putting in a feature request for it on github
14:10 ndrei joined #salt
14:12 hany joined #salt
14:12 pydanny joined #salt
14:12 ipmb joined #salt
14:13 dirjax joined #salt
14:13 racooper joined #salt
14:15 lessismore Is it possible to use extend in a loop?  No: I get the error failed: Conflicting ID "extend"!  Are there known workaround?  To give more contest I want the web server to watch a list of sites coming from pillars.
14:15 BogdanR Ahlee: The -S parameter is not available for me in version 0.17.4
14:15 BogdanR Was it introduced later or it was somehting else?
14:16 ay_ Ahlee: Ok. Thanks. The chef version looks like this knife search node 'uptime_seconds:[6213490 TO *]' -a uptime
14:16 Ahlee ay_: it's likely possible with the salt mine, i'm just not placing how to do it
14:17 dirjax /j ansible
14:18 Ahlee BogdanR: appears salt-ssh doesn't have it, salt does.  My apologies
14:18 iri I'm using file.symlink and it fails because it complains that the target is not an abspath: http://hastebin.com/tiqofotaco.vhdl
14:18 Gifflen joined #salt
14:19 iri except that state.show_sls shows that it *is* an abspath! wth?
14:23 Gifflen joined #salt
14:24 ndrei joined #salt
14:30 favadi joined #salt
14:33 lessismo` joined #salt
14:35 jcsp joined #salt
14:37 Franz__ joined #salt
14:37 yomilk joined #salt
14:39 Franz___ joined #salt
14:41 ipmb_ joined #salt
14:44 ndrei joined #salt
14:47 bhosmer joined #salt
14:48 bhosmer_ joined #salt
14:49 GradysGhost joined #salt
14:50 anitak joined #salt
14:54 BogdanR Starting with 0.17.5 is salt-cloud also included?
14:55 kaptk2 joined #salt
15:02 mattmtl joined #salt
15:06 GradysGhost joined #salt
15:09 jergerber joined #salt
15:15 fxhp joined #salt
15:16 Gordonz joined #salt
15:17 Gordonz joined #salt
15:20 rojem joined #salt
15:21 rojem joined #salt
15:23 elfixit1 joined #salt
15:24 cedwards Mornin'
15:24 balboah evening
15:25 dlloyd joined #salt
15:28 dlloyd is there any way to have a file.comment not return false, thus being an error condition when the regex is not found in the file?
15:29 quickdry21 joined #salt
15:30 ndrei joined #salt
15:34 jimallman joined #salt
15:34 mgw joined #salt
15:38 cnelsonsic joined #salt
15:39 Poooogles Has anyone actually got any further with decent VMWare integration RE: https://github.com/saltstack/salt-cloud/issues/503
15:40 Damoun joined #salt
15:41 mikkn_ Any quick suggestions on how to execute a command only if a certain process is not running?
15:43 Poooogles make a bash one liner and use cmd.run?
15:44 cedwards mikkn_: have you looked at the 'unless' or 'onlyif' options?
15:44 ndrei joined #salt
15:45 rgbkrk joined #salt
15:46 mikkn_ cedwards: Yeah, I looked a bit at it, but "true" and "false" is vague. Is it if a python method returns true or false? Is it if a shell command returns with a non-zero exit code?
15:46 mikkn_ Is it if the shell command returns output or not? :)
15:47 mikkn_ Wasn't very clear, at least. :)
15:48 kalloc joined #salt
15:48 guest23543 joined #salt
15:48 cedwards mikkn_: you can provide the command to run, and based on that return it'll run your other command.
15:49 alunduil joined #salt
15:51 whiskybar joined #salt
15:51 tessellare joined #salt
15:52 forrest joined #salt
15:55 dave_den mikkn_: it's based on the exit code from the command used in unless/ony_if
15:57 tyler-baker joined #salt
16:05 mpanetta joined #salt
16:07 pdayton joined #salt
16:09 mpanetta_ joined #salt
16:10 kalloc_ joined #salt
16:11 mpanetta joined #salt
16:12 tvle joined #salt
16:12 bhosmer joined #salt
16:13 sbdelisle joined #salt
16:13 kalloc_ joined #salt
16:13 bhosmer_ joined #salt
16:16 sbdelisle Hello.  I'm working with state files that generate some fairly complex java properties files for an in-house application. There are five separate config files that need to use what are essentially transformations and combinations of data that is in pillar.  My first approach was to switch to mako and add a block of about 50 lines of python code to do the transformations but I can't figure out how to reuse that.
16:17 kalloc joined #salt
16:17 sbdelisle So I have five files with the same 50 lines cut-and-pasted at the top of each.
16:18 sbdelisle If I try to move the logic into pillar I can't really figure out how to access other pillar data from a pillar sls file.
16:19 sbdelisle Anyone familiar with this kind of problem?
16:19 rgbkrk joined #salt
16:21 MTecknology IT sucks
16:21 MTecknology If you do your job correctly, nobody knows you exist and you get recognized for nothing. If you make a mess of things and blame it on others and then fix your mess, you did well and get emails sent out about how great you are.
16:22 Egya_Koo joined #salt
16:22 Egya_Koo Morning/Afternoon Gurus
16:23 Gordonz joined #salt
16:23 dave_den sbdelisle: doesn't mako have inheritance so you can just include the transformation mako code from other templates?
16:23 Egya_Koo Trying to bond 10G on rhel 6 using the dev branch from github.  In my /usr/lib/python2.7/dist-packages/salt/modules/rh_ip.py I see 10000
16:23 Gordonz joined #salt
16:24 dlloyd left #salt
16:24 Egya_Koo But when I run salt, it seems to complain with this error :      Comment: Invalid option -- Interface: eth1, Option: 10000, Expected: [10|100|1000]
16:24 Egya_Koo dave_den: I think you tried helping us the last time but the option wasn't available in rhel
16:24 forrest sbdelisle, can you not create templatized managed files?
16:25 Egya_Koo are we missing something ?
16:25 forrest Egya_Koo, Were you here a couple weeks ago with this error?
16:25 forrest someone else brought it up
16:25 Egya_Koo forrest: yeah
16:25 forrest did you try and go in and add 10000?
16:25 dave_den forrest: yeah and i made the commit to add 10000. let me look again, egya
16:26 Egya_Koo Thanks Guys
16:26 forrest dave_den, cool, I thought I remember someone fixing it in dev, Egya_Koo I assume you aren't running off the dev branch though
16:26 forrest oh you are
16:26 forrest nevermind
16:26 jeremyfelt joined #salt
16:26 dave_den Egya_Koo: how are you calling the rh_ip module?
16:27 Egya_Koo dave_den: using this http://docs.saltstack.com/ref/states/all/salt.states.network.html
16:28 sbdelisle @dave_den mako has inheritence, but 1. it doesn't inherit python functions so there is a lot of rework that would be needed anyway. 2. mako functions etc. are more about reusing text that logic 3. I can't even figure out what's on the path for mako inheritance.
16:30 dave_den Egya_Koo: can i see your bond state?
16:30 Gareth forrest: someone fixed it in the debian_ip module but I don't believe it got added to the rh_ip one.
16:31 yota Uh?! It's the same version "Master pub message signing is disabled but we received a signature for this message"
16:31 jalbretsen joined #salt
16:31 dave_den Gareth: it's there. https://github.com/saltstack/salt/blob/develop/salt/modules/rh_ip.py#L160
16:31 Egya_Koo dave_den: Happy for me to paste it here ?
16:31 Gareth dave_den: ah okay.
16:31 dave_den Egya_Koo: use a pastebin or gist, please
16:31 Egya_Koo ok
16:32 Egya_Koo dave_den: http://fpaste.org/74697/13916179/
16:32 zach dave_den: have you ever seen this before? https://p.6core.net/p/tLiDJVz9ocjgoDBBsh7tfJPb
16:33 forrest zach, did you talk to techhat about that one yet?
16:33 zach was working flawlessly up until yesterday, nothing has changed
16:33 forrest I'm curious as to what the answer is
16:33 zach forrest: hasnt come online yet
16:33 forrest ahh
16:33 carlos joined #salt
16:33 dwiden joined #salt
16:34 zach Just weird, it was all working just fine, then randomly wizards appear and that error happened
16:35 dwiden Can you use salt states to have minions download and install programming language packages, for example M2Crypto in Python?
16:35 zach sure
16:35 zach pkg.manage
16:36 zach There also is a python one too if I'm not mistaken
16:36 forrest zach, you mean pkg.installed?
16:36 sbdelisle there's a state for pip
16:36 dave_den Egya_Koo: are you sure the minion is running the dev branch? can you run 'salt-call —versions-report' on the minion?
16:36 gadams999 joined #salt
16:37 zach http://docs.saltstack.com/ref/states/all/salt.states.pip_state.html#module-salt.states.pip_state
16:37 forrest oh you're looking at the pip state
16:37 zach forrest: yeah I meant pkg.installed
16:37 forrest gotcha
16:37 zach I use file.managed way too much
16:37 dwiden zach: that looks great, thank you!
16:37 Egya_Koo dave_den: You might be right - minion was kickstarted and installed via yum. I will change and test
16:37 Egya_Koo brb
16:37 jeremyBass1 joined #salt
16:40 gnu-man1_ joined #salt
16:44 bhosmer joined #salt
16:44 GradysGhost joined #salt
16:45 bhosmer_ joined #salt
16:46 Thiggy joined #salt
16:46 drawsmcgraw Any common issues I should look for when a new minion connects to a salt master but won't respond to test.ping ?
16:46 drawsmcgraw After accepting the key, of course
16:46 krak3n` joined #salt
16:48 zach run it with -l debug
16:53 forrest also try test.ping -t 20
16:53 forrest to increase the timeout
16:53 forrest the job might be created, but it's taking a while
16:54 zach also salt-run manage.down
16:54 krak3n` joined #salt
16:56 toastedpenguin joined #salt
16:56 vejdmn joined #salt
16:58 faldridge joined #salt
16:59 Ahlee ok, this is wierd.  Trying to bring up a minion is attempting to connexct to redis, neither master has a default returner configured
16:59 rojem joined #salt
16:59 17WAA0PM2 joined #salt
17:07 krak3n` joined #salt
17:08 mgw joined #salt
17:08 Ryan_Lane joined #salt
17:08 krak3n` joined #salt
17:09 krak3n` joined #salt
17:10 harobed_ joined #salt
17:10 synfin joined #salt
17:10 felixhummel joined #salt
17:10 harobed_ joined #salt
17:11 harobed_ joined #salt
17:13 gadams9991 joined #salt
17:14 KyleG joined #salt
17:14 KyleG joined #salt
17:15 Egya_Koo dave_den: I'm not sure how to thank you man ...
17:15 Egya_Koo dave_den: Thanks so Much
17:15 troyready joined #salt
17:15 Egya_Koo :)
17:15 dave_den Egya_Koo: you're welcome. the minion was not running the develop branch?
17:16 Egya_Koo dave_den::)
17:16 Egya_Koo dave_den: yeah
17:16 dave_den that happens :)
17:17 Egya_Koo Thanks for your patience
17:19 robawt carmony: I liked your salt speaker deck.  Not just because I like legos and Marvel heroes.  Question about the dev/prod salt masters/minions.  Are you limiting the dev salt capabilities?
17:19 carmony robawt: yeah, we basically limit the user that salt is running as
17:19 carmony the dev salt-minion
17:20 robawt carmony: what limitations are set?  limiting certain executable modules or access of the minion itself?
17:20 carmony so we run that minion under the user "bob"
17:20 carmony it basically a dummy minion
17:21 zooz joined #salt
17:21 carmony so it could try to rm -rf something
17:21 robawt ah ok, and 'bob' is limited.  can you still get things like system grains?
17:21 maxleonca joined #salt
17:21 carmony I think so
17:21 jstadler joined #salt
17:21 carmony I think we had to make some changes to our sudoer files to make it work
17:21 robawt i liked your presentation slides, and I look forward to a video (I hope)
17:21 carmony I should do a blog post on it
17:21 robawt yeah it's an interesting approach carmony
17:22 carmony it was one that our Systems team felt comfortable
17:22 carmony with
17:22 carmony they know how the system users permissions work isntead of worrying about messing up the ACLs on a salt-master
17:23 n8n joined #salt
17:23 robawt it's a smart approach
17:24 robawt especially since it doesn't get modified with updates to salt
17:24 kalloc_ joined #salt
17:24 Ahlee it's certainly interesting
17:24 Ahlee how long have you been using that setup carmony?
17:25 carmony its relatively new, we're still working some kinks out but its showing some serious promise
17:25 Ahlee lack of group support in ACLs and auth in general is making me seriously question my pull-from-ad-and-write-out-a-file method
17:25 sASas joined #salt
17:26 tvle joined #salt
17:26 hany joined #salt
17:27 drawsmcgraw so... I used salt-cloud to create a master. I passed it my own deploy script, which just curls salt-bootstrap and passes it -M to also install a master
17:28 drawsmcgraw Then I use salt-cloud + a mapfile to create several minions. The minions connect just fine.
17:28 drawsmcgraw The master accepts their key. But then the minions won't respond to test.pings
17:28 drawsmcgraw This is what's in the minion logs: http://pastebin.com/cu5RXKwk
17:28 drawsmcgraw I'm really confused, since all of these machines are no more than an hour old
17:29 tl-ml joined #salt
17:29 hunter joined #salt
17:29 hunter Re: the topic, have any of the saltconf videos made it to the web yet?
17:29 ekristen joined #salt
17:30 ekristen how do I bootstrap just the minion?
17:30 KyleG left #salt
17:30 cedwards ekristen: using the bootstrap script?
17:31 ekristen cedwards: I just don’t want it to install the master, or do I have to set a flag for that
17:32 cedwards ekristen: you need a special flag to install a master, so for just a minion you can use: curl -L | http://bootstrap.saltstack.org | sh
17:32 davet joined #salt
17:33 funzo joined #salt
17:33 Katafalkas forrest: Are you here ?
17:34 drawsmcgraw AH... nevermind... I'm running salt-cloud from my laptop and connecting the minions to a master in AWs
17:34 thayne joined #salt
17:34 drawsmcgraw salt-cloud is preseeding the minions with my laptops fingerprint. So they don't trust the master I direct them to. Bugger...
17:34 bemehow joined #salt
17:36 toofer joined #salt
17:37 * thayne acknowledges that he made SaltConf 2014 amazing.
17:38 krak3n` joined #salt
17:39 mpanetta joined #salt
17:39 krak3n` joined #salt
17:40 Ahlee hunter: They'll make it known when the videos are up.  They need to do the editing themselves, so it will take time, as video editing doesn't pay the bills
17:40 mpanetta joined #salt
17:42 hunter fair enough
17:42 krak3n` joined #salt
17:43 longdays anyone have further documenation for using cloud-init to spinup a salt-minion using #cloud-config data? All I have found is this https://github.com/number5/cloud-init/blob/master/doc/examples/cloud-config-salt-minion.txt
17:44 longdays I know we can do it with bash. We are using that now. Just seeing if using cloud-config data is an easier option
17:45 longdays looking at code now https://github.com/number5/cloud-init/blob/8a5e01d7484307a846430ecfe18873627e4b18d1/cloudinit/config/cc_salt_minion.py
17:45 Led_Zeppelin joined #salt
17:45 bhosmer joined #salt
17:47 kalloc joined #salt
17:50 Poooogle_ joined #salt
17:51 Poooogles joined #salt
17:51 wendall911 joined #salt
17:52 BrendanGilmore joined #salt
17:53 diegows joined #salt
17:54 Poooogle_ joined #salt
17:56 mgw joined #salt
17:57 Ryan_Lane joined #salt
17:57 tvle joined #salt
18:01 funzo_ joined #salt
18:02 kalloc joined #salt
18:05 Led_Zeppelin is there a tar.gz file for salt ?
18:07 dave_den you mean containing the salt source code?
18:07 Led_Zeppelin eh, nevermind.
18:07 Led_Zeppelin yes, I got it now.
18:07 dave_den k
18:07 Led_Zeppelin nice to see such a quick response :p
18:07 Led_Zeppelin so far I am impressed
18:10 logix812 joined #salt
18:23 saurabhs joined #salt
18:27 Katafalkas Any ideas when the video recordings of Saltconf will be posted online ?
18:28 tessellare joined #salt
18:29 krak3n` joined #salt
18:38 thayne joined #salt
18:38 xfactor973 joined #salt
18:39 xfactor973 morning everyone!  I'm having an issue where the salt master is rejecting a minion's pub key.  when i do a salt-key -d 'minion-name' and restart the minion it just rejects it again
18:39 xfactor973 i also tried restarting the master in open mode and it doesn't help
18:42 ekristen can I do - require: - user.present: username?
18:44 [vaelen] joined #salt
18:45 cedwards ekristen: you should just be able to require the user id
18:45 AdamSewell joined #salt
18:45 AdamSewell joined #salt
18:45 Poooogles joined #salt
18:47 AdamSewell joehh, are you around?
18:47 alexthegraham joined #salt
18:48 Led_Zeppelin i am trying to start up salt-master as non-root user. So I am doing salt-master -c salt/etc (which I have permission for) but its seems its trying to create a directory in /etc/salt/pki/master how can I fix this also ?
18:48 ekristen how do I clear my pillar cached data
18:49 ekristen I had a yaml error in a pillar, I’ve fixed it, but salt is still reporting the error
18:49 Voziv Is there a way to have salt only refresh the package list (apt-get update) only once? Even better if it can be only once per day or something like that
18:50 cedwards Led_Zeppelin: sounds like you need to update the pki_dir value in the master config
18:51 lynxman_ joined #salt
18:51 lynxman joined #salt
18:51 cedwards Voziv: I believe the pkg state supports refresh: True/False for that.
18:51 Led_Zeppelin cedwards, this is a brand new install. Do I just create a dummy master config file and point to it?
18:52 Voziv cedwards: But if I have 10 packages being installed, all with refresh: true, does it only do the refresh once?
18:53 Voziv Right now if I set them all to false, highstate only takes 3-4 seconds to complete. If they are set to true it takes a few minutes (it seems like it does apt-get update for each package)
18:53 cedwards Led_Zeppelin: are you using a copy of the default config in your salt/etc/ setup?
18:54 xfactor973 i think my salt master is broken.  i purged the salt minion package, reinstalled it, it generated a new key and the salt master rejects it
18:54 schristensen joined #salt
18:54 Led_Zeppelin there is no configuration files for me cedwards. I did a source install. I don't have root access and I just wanted to play around with salt to evulate it.
18:54 Led_Zeppelin cedwards, is there a sample file I can download and use? or a way to generate this file?
18:55 cedwards Led_Zeppelin: all the config files: https://github.com/saltstack/salt/tree/develop/conf
18:55 Led_Zeppelin ok, let me get one
18:55 cedwards Voziv: You should be able to provide a list of all the packages you need in one pkg.installed declaration and provide refresh: True/False once.
18:56 cedwards Voziv: trying to find an example..
18:56 Led_Zeppelin does the file have to be named a certain way?
18:56 cedwards Led_Zeppelin: just 'master'
18:56 Shish joined #salt
18:57 Voziv cedwards: That's not really an option as not all the packages are installed on all servers
18:57 echos joined #salt
18:57 drawsmcgraw ekristen: you're looking for a 'saltutil.refresh_pillar' I think.
18:58 Led_Zeppelin cedwards, nice. Got a little further.
18:58 vejdmn joined #salt
18:58 dave_den Voziv: you don't need to specify refresh: true unless you are modifying your apt repo configuration in the same state run
18:58 hany good morning folks, i've got a question regarding the use of the Salt Mine. I'm looking to manage several customers using a single master+minion setup, and I'm interested in the functionality that the Salt Mine provides. My question is, is there some way to add some security to prevent minion A from querying data in the Salt Mine for minion B?
18:58 Voziv dave_den: Does it run once at the beginning?
18:58 martoss joined #salt
18:58 dave_den Voziv: yes, it will refresh once per state run
18:59 Voziv awesome
18:59 Voziv thanks for the help
18:59 dave_den hany: no, the salt mine data is visible to all minions
19:00 drawsmcgraw So I install salt 2014.1 from Git. Works great. But I need salt-cloud, which complains about libcloud
19:00 drawsmcgraw So I pip install apache-libcloud
19:01 drawsmcgraw and now I'm getting the nasty warning: _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability."
19:01 derelm joined #salt
19:01 drawsmcgraw This is on Amazon Linux.  Any nice way of getting around this warning?
19:01 hany dave_den: gotcha. i'm looking for a way to have a special minion have access to (preferably cached) data from all other minions, but restrict this ability for others. is the peer communication system the only way?
19:01 drawsmcgraw All I see is 'rebuild libgmp' with no clear instructions on it...
19:03 ajw0100 joined #salt
19:03 dave_den hany: I wrote MasterPillarUtil for exaclty that purpose. you can use it in a custom runner module that you give access to the specific minion in the 'peer_run' configuraiton https://github.com/saltstack/salt/blob/develop/salt/utils/master.py
19:04 hany dave_den: aha! thank you very much. i will look into it. thanks for the quick response
19:05 Led_Zeppelin cedwards, yah! got master up :p
19:07 dave_den welcome
19:07 ausmarton joined #salt
19:09 cedwards Led_Zeppelin: great :)
19:10 dlam joined #salt
19:11 dlam hey whats the "best" salt way to change say the default mysql log path?  maybe put it in a pillar variable or something?
19:12 vejdmn joined #salt
19:14 clearclaw Anybody know how to specify an EBS volume/mount by ID in a statefile?
19:15 * clearclaw wan'ts to re-use the volumes he already has.
19:15 amckinley joined #salt
19:15 Franz__ joined #salt
19:16 rojem joined #salt
19:16 iri left #salt
19:17 druonysus joined #salt
19:17 druonysus joined #salt
19:17 clearclaw Ahh: volume_id
19:22 Ryan_Lane joined #salt
19:23 brendangilmor joined #salt
19:25 vejdmn joined #salt
19:25 kalloc joined #salt
19:29 xfactor973 anyone have a min to help me fix this master minion key accepting problem?
19:30 cedwards xfactor973: have you tried deleting the offending key off of the master?
19:30 m87carlson joined #salt
19:30 xfactor973 i have
19:30 aptiko left #salt
19:30 xfactor973 i restart the minion, the master accepts the key and then the minion service dies saying the master rejected the key
19:30 xfactor973 i'm a bit confused what is going on
19:31 xfactor973 the logs say try restarting the master in open mode to clear out the key but that didn't solve it either
19:35 xfactor973 crap i know what is wrong.  i'm using multimaster and another master has rejected the key.  if i blow that away i think it'll solve it
19:39 jcsp joined #salt
19:39 yomilk joined #salt
19:40 cedwards that might do it
19:44 Led_Zeppelin now, I keep getting No cuh file or directory '/etc/salt/minion_id'. I would like to change this location. how can I do that?
19:46 xfactor973 cedwards: yeah that fixed it. i'm all set
19:46 dfisklements joined #salt
19:47 cedwards xfactor973: i would never have thought to ask about multi-master. glad you figured it out.
19:48 xfactor973 i put the minion in debug mode and then it made sense :)
19:48 ipmb joined #salt
19:48 Led_Zeppelin is there an alternative to minion_id location?
19:49 * clearclaw sings: I can see clearly now-that-I-have-all-this-information-in-this-logfile-that-is-scrolling-faster-than-I-can-read
19:50 xfactor973 haha
19:51 mgw clearclaw: I'm curious as to whether you got the s3 versioning figured out
19:53 gnu-man1 joined #salt
19:53 zach Oh man, new error with salt-cloud now
19:53 Led_Zeppelin anyone? about minion_id?
19:53 zach https://p.6core.net/p/PkN8wwOQbHveTHLJA9LaqCSr
19:54 Led_Zeppelin Could not cache minion ID...
19:54 zach Led_Zeppelin: you can set it within the /etc/salt/minion too if not mistaken
19:55 bhosmer joined #salt
19:55 Led_Zeppelin i don't have access to /etc/salt. I don't have root
19:55 zach I see
19:55 zach Why are you doing this as a non-root user?
19:55 zach mind blown
19:55 zach Why not use salt-ssh vs salt-minion if non-root?
19:55 scoates asked yesterday, but no luck. Anyone know why __grains__ (and the other supers) might not be available in the #!py renderer? Pillar complains.
19:56 zach salt works best as a super user
19:56 Led_Zeppelin zach, don't have root access and I want to test minion before I submit a formal request to my team.
19:56 Led_Zeppelin yes, I know. But I want to see how it works beforehand.
19:56 zach Setup a sandbox environment?
19:56 zach do a few virtual machines on your local machine
19:56 Led_Zeppelin yes, I can do that too
19:56 Led_Zeppelin but really, non-root should also work
19:56 zach You won't be able to demo it to it's fullest as non-superuser
19:56 Led_Zeppelin i think this maybe a bug
19:56 Led_Zeppelin thats ok.
19:57 Led_Zeppelin i want to atleast get minion up
19:57 Led_Zeppelin i have the master up
19:57 ekristen anyone use salt to manage linux users? how do you control which server gets which users?
19:57 zach ekristen: I used grains
19:57 zach ekristen: you can set the if grainsblah = blah add these users
19:57 ekristen right, now do you organize your pillar data?
19:58 scoates ekristen: I use an ugly hack. /-: {% for name, user in salt['fkutil.filter_host_groups'](grains['id'], pillar['users'], pillar['users_host_group_patterns']).items() %}
19:58 derelm joined #salt
19:58 Led_Zeppelin cedwards, any thoughts about my problem? ;p
19:58 zach Led_Zeppelin: I am quite sure salt is not QA'd against a non-privileged environment
19:58 scalability-junk ekristen: depends on what I would wanna do. For finegrained controlle an not per project, but per host basis I would have one pillar per user and then embed this users pillar/state via the top sls file.
19:59 Led_Zeppelin zach, i doubt that. There is a document about this after all, http://docs.saltstack.com/topics/nonroot.html
19:59 felixhummel joined #salt
19:59 ekristen scalability-junk: if you do one user per pillar file, how do you reference them via a state to add them?
19:59 cedwards Led_Zeppelin: honestly I've never tried to run as non-root either. I've not seen that error before.
20:01 Led_Zeppelin it seems minion_id is hard coded to /etc/salt. https://github.com/saltstack/salt/pull/7678
20:01 scalability-junk ekristen: can't find the actual example right now. but I think it was looping through user_xxx pillars in the states and then supply different user_xxx pillars (one per user) in the pillar top file.
20:02 scalability-junk But that was a really small environment, wouldn't do that when bigger.
20:02 jcsp Led_Zeppelin if you're not running as root you probably want to set CONFIG_DIR to something in your home
20:03 Led_Zeppelin oh..
20:03 Led_Zeppelin where exactly do I set CONFIG_DIR? as an environment variable?
20:03 jcsp there's an environment variable, there's also -c on the command line
20:03 jcsp you will also need to craft config files that have appropriate paths for all the other things
20:03 Led_Zeppelin well, I am running salt-minon -c /localuser/minion
20:04 Led_Zeppelin i already modified the config file to have it point to local entries.
20:04 jcsp annoyingly, if salt can't find config in the file you specify, it will fall back to /etc instead of giving you an error
20:05 jcsp if you have a config file in e.g. ~/etc/salt/minion then you would use "-c ~/etc/salt"
20:05 Led_Zeppelin right, so what option in the config file must I change for this?
20:05 jcsp I'm suggesting that your -c might be wrong
20:05 Led_Zeppelin oh
20:08 Led_Zeppelin hang in there
20:10 seanz Dumb question: I can include an sls file from any other sls file, right?
20:10 oz_akan_ joined #salt
20:11 Led_Zeppelin jcsp, what should the minion configuration file be named? can I speciify a name instead of a directory?
20:12 lzhang joined #salt
20:12 jcsp I believe -c always expects a directory
20:13 lzhang I'm getting "The Salt Master has rejected this minion's public key!" when installing a new salt minion... what triggers the regeneration of the /etc/salt/pki/minion keys?
20:14 lzhang It looks like it registers under a public key, then regenerates the key failing to auth
20:14 Led_Zeppelin jcsp, got it running!!
20:15 seanz Would someone please look at this sls file and give me a hint as to why I'm getting an error: http://pastebin.com/cViNvhRA
20:15 seanz The error is that the following requisites were not found: curl, debconf-utils
20:16 seanz Yet those packages are already marked as installed further down the highstate output.
20:16 Mua_ joined #salt
20:17 bemehow joined #salt
20:19 scoates trying to debug a renderer. I added `fkpy.py` to `_renderers/` but my templates with `#!fkpy` at the start are trying to get rendered as YAML. Is there something else I need to do to register the renderer?
20:19 mapu joined #salt
20:22 zooz joined #salt
20:22 scoates -> [ERROR   ] The renderer "fkpy" is not available
20:22 scoates hmm
20:25 dave_den scoates: you're putting it on the master at /srv/salt/base/_renderers ?
20:27 felixhummel joined #salt
20:27 maxleonca Hello, anyone with extra documentation of managing windows?  Is a necesary evil, but I'll love to address those with salt as well.
20:27 pydanny joined #salt
20:29 scoates dave_den: I'm putting it in /path/to/roots/_renderers/
20:30 m87carlson hey maxleonca, I manage windows and *nix systems with Salt
20:30 scoates where master's config has: `file_roots: base: - /path/to/roots`
20:31 scoates maybe it's because I'm using pillar?
20:32 maxleonca hey m87carlson, do you have any documentation besides that is on the docs?
20:32 dave_den scoates: yeah, the _renderers direcotry just needs to be in your file_roots path
20:33 m87carlson maxleonca: I can help answer specific questions, or give you a general overview, but I don't have a lot of formal documentation on windows
20:33 scoates it is, yeah, dave_den
20:33 dave_den scoates: so you;re following these instructions? http://docs.saltstack.com/ref/renderers/index.html#writing-renderers
20:33 m87carlson basically, we installed salt on our base image for xp and windows 7, and we manage software and files just like we would with a *nix system
20:34 scoates dave_den: I am. roots/_renderers/fkpy.py is a copy of py.py from git
20:34 m87carlson the most diffcult part was getting the win repo to work
20:34 scoates dave_den: possible custom renderers aren't hooked up for pillar sls?
20:34 bhosmer joined #salt
20:35 dave_den scoates: oh, for pillars you need to put it in your master extension directory
20:35 scoates ah… ok
20:35 scoates let me see
20:36 scoates potentially dumb question: how do I determine the extension directory?
20:37 Franz__ joined #salt
20:39 scoates [DEBUG   ] Skipping /var/cache/salt/master/extmods/renderers, it is not a directory
20:39 scoates I guess that?
20:40 scoates related, is there more documentation on runner_dirs ?
20:40 maxleonca Thanks m87carlson, I just need to find the bases for managing windows boxes and then I'll pile up with experimentation.
20:41 jstadler joined #salt
20:41 maxleonca what do you mean by a base image for xp and windows 7?
20:42 m87carlson We use FOG to create and image desktops at work, so the "golden" image we have already has salt installed
20:42 hunter FOG?
20:42 m87carlson http://fogproject.org/
20:43 dave_den scoates: just set 'extension_modules: /etc/salt/extmods' in your master config
20:43 m87carlson its a free imaging tool based on linux
20:43 scoates dave_den: thanks.
20:43 dave_den and make /etc/salt/extmods/_renderers
20:43 scoates yep
20:43 xmltok joined #salt
20:43 dfinn joined #salt
20:44 dfinn probably a stupid question but any reason why the salt master can't also run the salt minion process and the minion can pull basic config stuff from the master?
20:44 maxleonca OK, so you create a "master" image, you deploy it on your work stations.  Then how do you work it out?,  I mean how do you fix the minion key problem from the image?
20:44 m87carlson anyway, we use the saltstack provided salt installers, run it with the /S flag for an unattended install, and then I accept its key on the master. After that, its just a matter of building states
20:44 maxleonca I figure just one registers...
20:44 m87carlson oh, thats easy :)
20:45 m87carlson when we update the FOG base image, we make sure that all the pki stuff is deleted, and the minion_id file is removed. Once a system is imaged and deployed, salt-minion starts up again, and this time it has the correct hostname / minion_id
20:46 mbarrien joined #salt
20:47 m87carlson but if a system does not already have salt on it, I'll usually use psexec:
20:47 maxleonca hmmm, ok dhcp reservations I figure
20:47 m87carlson psexec.exe \\client "\\fileserver\insatlls\salt\salt-minion-amd64-0.17.2.exe /S"
20:47 maxleonca OK and from there is mostly regular formulas, states and pillars?
20:48 m87carlson we use dhcp but most desktops don;t have a reservation, we do use active directory for DHCP and DNS, so they auto-update their records whne they are on the domain
20:48 m87carlson yup
20:48 scoates dave_den: `_renderers` or `renderers` ?
20:49 maxleonca hmm interesting, just figure a way to bootstrap salt onto the clients and next!
20:49 maxleonca thank you, I'll start playing with it to see how it works out.
20:51 scoates seems to be `renderers`
20:52 zooz joined #salt
20:53 Led_Zeppelin since i have salt setup, I want to do something very simple. I want to make sure '/etc/motd' exists. What is the best way to do this?
20:54 thayne Anyone see a failure in the test suite in unit.modules.cron_test.PsTestCase line 55 ?
20:54 Linuturk file.managed
20:56 cedwards Led_Zeppelin: if your minion isn't running as root you're not going to be able to create that file though
20:57 Gifflen_ joined #salt
20:57 Led_Zeppelin cedwards, thats fine.  I just want to verify
20:57 Ryan_Lane joined #salt
20:58 felixhummel joined #salt
20:58 rojem joined #salt
20:58 dave_den scoates: sorry, yes 'renderers'
20:59 scoates ty
21:00 dave_den Led_Zeppelin: if you just want to make sure the file already exists, use file.exists. http://docs.saltstack.com/ref/states/all/salt.states.file.html#salt.states.file.exists
21:02 Led_Zeppelin ok, so I created the sls file with file managed
21:02 Led_Zeppelin now, not sure what I need to run to verify
21:02 Gifflen joined #salt
21:03 cedwards Led_Zeppelin: have you created a top.sls too?
21:03 Led_Zeppelin yes, I did
21:03 cedwards then you should be able to try and apply it with 'salt $minion state.highstate'
21:05 Led_Zeppelin nice
21:05 Led_Zeppelin that works :p
21:05 Led_Zeppelin nothing showed up
21:05 babilen Hi, can I somehow reference match groups later in states/pillars? I think of something like "foo-([a-z]+)-(\d+): - somestate.\1.\2" so that, say, foo-bar-1234 would lead to somestate.bar.1234
21:06 babilen So essentially: Are match groups made available later in a specific scope?
21:06 Led_Zeppelin ok. now I am getting the hang of it :p
21:07 dave_den babilen: it depends on which renderer you use. the default is yaml + jinja.
21:07 cedwards Led_Zeppelin: glad to hear it
21:07 Led_Zeppelin this is very cool, btw :p
21:07 babilen dave_den: Please elaborate, would that necessitate writing this in pure Python?
21:07 dave_den babilen: and jinja is not able to do that, afaik.
21:07 cedwards Led_Zeppelin: remember to keep in mind that a "normal" setup usually only takes about 5 min.
21:07 Led_Zeppelin yes, it took me 1 hour but wasn't bad as I though
21:08 pydanny joined #salt
21:08 babilen dave_den: It's simply that I am writing pillars/states for pretty well formed minion-ids and being able to do the above would mean that I wouldn't have to enumerate every single minion
21:09 synfin salt-ssh, what dependencies are required on the "minion host"?  The docs say you need ssh, but no minion.  But what else is required, Python version 2.7.x?
21:09 Led_Zeppelin instead of running all sls files, how can I run only the one I chooise?
21:09 Led_Zeppelin *choose
21:09 babilen dave_den: Right now I want to use it for automatic assignment of roles, all of which follow the form: $FOO-$FUNCTION-$NUMBER and I want to assign roles $FOO, $FOO.$FUNCTION and $FOO.$FUNCTION.$NUMBER to it
21:09 cedwards synfin: i believe the only requirement is a recent python, yes.
21:10 tvle joined #salt
21:10 cedwards Led_Zeppelin: to use a specific state (sls) instead of all of them you can use 'salt $minion state.sls $state'
21:10 cedwards Led_Zeppelin: you'll also decide what state files run on which minions inside the top.sls. they'll only run where they are targetted.
21:12 Led_Zeppelin so if I had a file called, issue.sls, I would do, salt state.sls issue ?
21:12 dave_den babilen: i'm not sure the built-in state tops and pillar tops render functions know the minion id during render, but i know you can do that with master_tops and ext_pillars.
21:12 Franz__ joined #salt
21:12 cedwards don't forget the minion(s) after the salt command, but yes.
21:13 Thiggy joined #salt
21:13 dave_den babilen: i've just never tried to do that in the tops renderers, only in external master_tops and ext_pillars
21:15 babilen dave_den: Okay, I'll have a look - I am used to making copious amounts of regular expressions in Python and therefore used to having the actual match objects around, wasn't sure if *something* like that exists in Salt.
21:15 Led_Zeppelin don't bash be but is there a GUI for saltstack :p
21:17 felixhummel_ joined #salt
21:18 cedwards Led_Zeppelin: web interface, called Halite
21:18 dave_den babilen: for the states tops, that is rendered on the minion, so it's just like using yaml in state files
21:18 Led_Zeppelin cedwards, good enough :p
21:18 Led_Zeppelin cedwards, thanks for your help btw
21:19 dave_den babilen: e.g.:   base:\n  '*":\n    - per_host.{{ grains['fqdn'] }}
21:20 dave_den although that wouldn't work since the tops system thinks dots are path separators.
21:20 dave_den but it's an example of how top.sls for states is just a template
21:23 harobed joined #salt
21:24 Led_Zeppelin this is more of an efficiencty question. Lets say I have 1000 nodes running minions. I want to do a query, does it do it each one by one or does in parallel?
21:26 babilen dave_den: Okay, thanks for that example ... it's just that I have "base: '*': - global \n 'foo-*': - foo \n 'foo-mdb-*': - foo.mdb ... " now and am just looking for ways to *not* have to enumerate all foo-mdb-1-999...999 if all I do is to assign roles foo.mdb.1 - foo.mdb.999...999 to them :)
21:26 dave_den Led_Zeppelin: parallel, unless you use a batch options
21:26 babilen dave_den: It's the kind of thing that simply screams "use a regular expression with groups and refer to that!"
21:26 Led_Zeppelin nice
21:28 dave_den babilen: you can do that with jinja
21:29 Gifflen_ joined #salt
21:29 felixhummel joined #salt
21:29 Led_Zeppelin so, what does jinja have to do with saltstack?
21:29 babilen dave_den: What would be the general idea?
21:30 bemehow joined #salt
21:32 bemehow joined #salt
21:39 patrek joined #salt
21:42 martoss joined #salt
21:44 dave_den babilen: sorry. well you could do
21:44 [diecast] joined #salt
21:45 dave_den {{ grains['id']|replace("foo-mdb-", "") }}  i think
21:45 lzhang left #salt
21:47 stewpot joined #salt
21:48 bretep Okay... Ubuntu-ites. How do you deploy salt-minions? Do you use the pre-built .deb? Do you build your own? Or do you use the bootstrap script? I need to know because of a fix that went out to the 0.17 branch on Feb. 3rd.
21:49 stewpot hello.. I have a state file powerdns in /srv/salt/dev/powerdns/init.sls . I then have in that file require: sls: mysql-server . The mysql-server sls is in /srv/salt/dev/mysql/server.sls it does not seem to work. what have I got wrong?
21:49 stewpot bretep: I use the packages provided by ppa
21:51 EntropyWorks bretep: we like to use .deb's when able. since without that your left to pull via git SHA1 or release branch to keep all systems the same
21:55 bretep The bootstrap script should make it easy to update a release vs. having to go delete all the files manually then bootstrapping again. Maybe I'm doing something wrong?
21:55 felixhummel_ joined #salt
21:56 forrest bretep, I thought there was an option to avoid deleting your files
21:56 forrest but I can't remember
21:58 felixhummel joined #salt
21:59 Ahlee I roll my own RPM, as I'm old and feel nothing should be installed to a system that isn't installed through your OS's package manager
21:59 Ahlee If I used ubuntu, I'd create a .deb
22:00 forrest Ahlee, I'm the exact opposite, I roll my own RPMs because I'm super lazy, and don't want to deal with managing all that crap.
22:00 Ahlee once the .spec is wrote it's easy :)
22:01 Ahlee and they've already handled that
22:01 bretep Back in my last company I also rolled my own RPMs. Just updated the has in the Makefile and koji did the rest
22:01 bretep It was awesome!
22:02 bretep Now, I'm at a new company and on ubuntu, meh..
22:02 SEJeff_work bretep, You had an internal koji?
22:02 bretep Yep
22:02 SEJeff_work Did you use pulp?
22:02 bretep Nope
22:02 tvle joined #salt
22:02 SEJeff_work And did you have koji tied into ldap or anything?
22:02 SEJeff_work Thats interesting
22:02 forrest I really want to mess with the suse buidl service
22:02 forrest *build
22:02 thayne joined #salt
22:02 bretep Koji was all digital certificates
22:03 zzzirk joined #salt
22:03 EntropyWorks Q: looking at "salt-cloud" and "salt virt" which is the recommend method for setting up some vm's using OpenStack theses days?
22:03 bretep After the 3rd time of building koji, I can build a koji infrastrucutre in less than a day. :D I don't know if that is something I should make public. ;)
22:04 forrest EntropyWorks, for that you'd want salt-cloud
22:04 forrest bretep, that is impressive
22:04 bretep I hosted our internal koji server from 2008-2013 when I left. They still use it
22:04 forrest usually setting that up is a bit of a process
22:04 bretep That's an understatement
22:04 bretep :)
22:04 bretep The first time took almost 3 weeks
22:05 forrest I'm not surprised
22:05 bretep The second time took ~4 days. When I built the latest one in ec2 took about 4 hours
22:05 EntropyWorks forrest: thx
22:05 herzi I'm getting “[salt.crypt][WARNING] SaltReqTimeoutError: Waited 60 seconds” every 70s in my minion log; where should I look for more information about that?
22:05 forrest EntropyWorks, yea np
22:05 herzi (as in, how to I look for more detail on my system)
22:06 forrest herzi, someone else was complaining about that yesterday as well, I thought I saw an issue for it
22:06 Ahlee interesting
22:06 Ahlee an internal koji system looks tempting
22:06 herzi yesterday, thanks, I'll have a look
22:07 forrest herzi, yea np
22:07 forrest Ahlee, koji is awesome, but as bretep said, it SUCKS to set up the first time
22:08 forrest you'll want to punch a baby, especially when previous RPM builds start failing because they weren't built with mock.
22:08 bretep Ahlee: It's nice if you build a lot of packages. We had over 900 propiatarty packages. and +1 to forrest, sucks
22:08 Ahlee https://fedoraproject.org/wiki/Koji/ServerHowTo
22:08 Ahlee yeah
22:08 Ahlee so much that can go wrong
22:08 Ahlee bretep: yeah, we don't use mock, so that'd be an interesting first step
22:08 Ahlee oh well
22:08 Ahlee current system works for now
22:09 forrest non-mock -> mock is huge
22:09 forrest and painful
22:09 bretep I actually had to edit a lot of the python koji stuff to get everything to work smoothly. We used mock, which, after figuring out all the nuances, is pretty awesome.
22:10 forrest yea mock is incredible
22:10 forrest just sucks to fix all your RPMs
22:10 forrest 900 packages man, that is insane
22:10 bretep That was config management before salt
22:10 bretep :)
22:11 forrest ahh gotcha
22:11 bretep yum clean all; yum update; reboot
22:11 forrest we do that where I'm at now
22:11 forrest not quite that cleanly
22:11 bretep yum clean all; yum update -y; reboot
22:11 forrest ll
22:11 forrest *lol
22:12 dave_den babilen: you have python in [% … %} blocks, so you could just do something like https://gist.github.com/dlanderson/c8ec06d2203cfcd58bdc
22:12 bretep We actually wrote a grain to tie in with our config server and moving to salt was super simple.
22:12 felixhummel joined #salt
22:15 krak3n` joined #salt
22:15 krak3n` joined #salt
22:15 yomilk joined #salt
22:16 felixhummel_ joined #salt
22:16 stewpot hello.. I have a state file powerdns in /srv/salt/dev/powerdns/init.sls . I then have in that file require: sls: mysql-server . The mysql-server sls is in /srv/salt/dev/mysql/server.sls it does not seem to work. what have I got wrong?
22:17 maxleonca stewpot, have you set mysql-server as a requirement for powerdns?
22:18 forrest stewpot, Did you make sure to include the appropriate state? you'd need to include the powerdns state at the top.
22:18 dave_den stewpot: you probably want '- include: mysql.server'
22:19 forrest dave_den ++
22:19 stewpot maxleonca: http://pastebin.com/Z7rkRAE9
22:20 maxleonca well stewpot as deve_den says it should go not as required but as an include, just set at the top of the file the include: - mysql-server
22:20 maxleonca instead of the require sls.mysql.mysql-server
22:20 maxleonca and give it a try
22:20 stewpot okay, i will try that now..
22:21 bretep I know it's a sad story... but .debs does anyone build their own? I've added a lot of fixes and a feature this last month and I need to get them deployed. It's really stifling this move from chef to salt.
22:21 stewpot bretep: building packages for debian is not  very hard.
22:21 dave_den building .debs of salt?
22:22 bretep stewpot: really?
22:22 stewpot bretep: : https://github.com/jordansissel/fpm/wiki makes it easy
22:23 bretep Have you done it or have you just read about it?
22:23 krak3n` joined #salt
22:23 bretep because I've "done" it
22:23 stewpot bretep: i manage about 40 custom packages.. however I don't do custom salt packages yet
22:24 bretep If you get a chance, try with salt. I also maintain many .debs that we build with jenkins just fine. Salt... I lost 3 days trying to get that to build
22:25 jergerber joined #salt
22:25 bretep I have not used fpm
22:25 felixhummel joined #salt
22:25 forrest fpm is dirty
22:25 forrest but it gets the job done
22:25 carmony you guys see the GitHub 2013 stats were released? :P
22:25 scoates I see what's going on with the python renderer, fwiw.
22:25 forrest were they carmony?
22:25 carmony http://octoverse.github.com/
22:25 forrest carmony, you have the link?
22:26 stewpot maxleonca: is the include under the service or under the package?
22:26 scoates https://github.com/saltstack/salt/blob/develop/salt/utils/templates.py#L343 <-- this is bailing if the file it's loading contains __grains__ because it's not defined until the next stanza.
22:26 forrest we're we #1 carmony?
22:27 carmony #3 for most issued closed, #3 in pull requests
22:27 carmony pull requests merged
22:27 carmony they only show top 5
22:27 forrest damn
22:27 carmony didn't make top 5 of most contributors
22:28 carmony best of all
22:28 carmony #3 person on github for pull reqs...
22:28 carmony s0undt3ch
22:28 forrest lol
22:28 stewpot bretep: what fixes or modules are you trying to deploy?
22:28 maxleonca try it at the top of the powerdns.sls
22:28 forrest wtf is cocoapods
22:28 forrest we beat rails
22:29 forrest always a happy day
22:30 forrest We need to kick it up for this year with more contributors
22:31 scoates does salt monkeypatch imp or something?
22:32 scoates here's why I ask: http://paste.roguecoders.com/p/ad75d7637c5559ca04b749ea853b0e81.txt
22:33 scoates unless imp doesn't raise an exception?
22:33 frosty996 joined #salt
22:33 frosty996 Any idea when 2014.1 is going to ship?
22:34 carmony scoates: whats imp? </newb_question>
22:34 scoates carmony: http://docs.python.org/2/library/imp.html I guess
22:34 Linuturk has any work been done to tie in Openstack Heat with SaltStack to handle the orchistration?
22:34 scoates this: https://github.com/saltstack/salt/blob/develop/salt/utils/templates.py#L11
22:34 elfixit1 joined #salt
22:34 Linuturk or, is salt-cloud the only supported method?
22:35 dave_den scoates: what are you trying to do
22:35 maxleonca stewpot, any luck:?
22:35 scoates dave_den: what I'm actually trying to do is use __grains__ in a #!py sls in pillar
22:35 scoates but what that's become is source diving to find out why my sls won't load
22:35 forrest scoates, oh yea. You haven't figured that out yet huh?
22:36 scoates I've figured out *why* just not a solution (-:
22:36 forrest scoates, what a slacker..
22:36 scoates I know. I spent most of the day getting fanned with palm leaves or something.
22:36 dave_den scoates: have you tried just 'grains'?
22:36 scoates dave_den: yeah; same problem
22:37 scoates looking at the source, it seems that the variables aren't attached to the module until after load_source(…)
22:37 forrest that seems weird, I don't get how that would break all of a sudden
22:38 scoates "all of a sudden" = for me? or for everyone?
22:38 scoates this is my first dive into #!py
22:38 scoates so it's not "all of a sudden" for me.
22:39 scoates do #!py templates work for anyone else, in pillar?
22:39 forrest scoates, I'm just curious if it's broken in a specific release
22:39 forrest no idea
22:39 forrest but you're the first to complain
22:39 rgbkrk joined #salt
22:40 scoates achievement unlocked
22:40 carmony I didn't know you could use a #!py template :P
22:43 babilen dave_den: Thanks, I'll probably end up with slightly different code, but that is a nice example to work with.
22:43 babilen dave_den++
22:43 scoates anyone willing to try? put this into a file in your pillar, and link it from top.sls: #!py\nfoo=__grains__
22:43 scoates (where \n is a newline)
22:45 whiteinge joined #salt
22:45 gwmngilfen joined #salt
22:46 bemehow joined #salt
22:46 scoates straight python spits out a NameError there, fwiw
22:47 scoates http://paste.roguecoders.com/p/99f9456a1cbca78de0bb33453b8e402b.txt
22:47 racooper joined #salt
22:47 bemehow joined #salt
22:48 joehh AdamSewell: I am now - but I guess you are gone :(
22:48 dave_den scoates: __grains__ is loaded by salt code, so that's expected
22:48 scoates dave_den: what do you mean, expected?
22:48 dave_den scoates: #!py renderered sls files need a run(): function that reurn the proper data
22:48 scoates dave_den: that's not the problem
22:48 dave_den i mean it's expected that __grains__ is not in your python console
22:49 scoates oh. I bet if I guard my reference to __grains__ within a function, it will "work".
22:53 Linuturk what's the best way to partition, format, and mount a disk using salt?
22:53 forrest Linuturk, http://docs.saltstack.com/ref/states/all/salt.states.lvm.html
22:53 forrest http://docs.saltstack.com/ref/modules/all/salt.modules.parted.html via module.run as well
22:54 Linuturk nice
22:54 Linuturk thanks forrest
22:54 forrest np
22:55 joehh bretep: what are the problems you are having trying to build salt debs?
22:55 scoates got it.
22:55 scoates thanks for the help, dave_den
22:55 dave_den scoates: np
22:55 dave_den missing run() ?
22:55 bretep the debian directory only works with the ppa
22:56 scoates dave_den: no, not exactly.
22:56 joehh yes
22:56 joehh unfortunate, but that is the case right now
22:56 bretep That would be the problem
22:56 joehh are you building for debian or ubuntu?
22:56 forrest scoates, so what was the resolution? I thought you tried all that stuff before
22:56 scoates forrest: dave_den: short version is: __grains__ is not defined at load time, but only by the time run() is called, so you can't reference __grains__ outside of the scope of run() (or a function that is called by run())
22:56 forrest scoates, ahh gotcha that makes sense.
22:56 scoates makes sense in the source, once it clicked, but SUPER confusing until then (-:
22:57 blee joined #salt
22:57 bhosmer joined #salt
22:57 forrest yea for sure
22:57 joehh if debian, best to use the debian directory from the debian packages on debian.saltstack.com or the debian archive
22:57 forrest I will have to remember that
22:57 bretep joehh: ubuntu
22:57 joehh which version?
22:58 bretep Ubuntu precise (12.04.4 LTS)
22:58 joehh do you remember what errors you get/got?
22:59 bretep I can't. It was back in december when I was trying to build it
22:59 joehh were they related to a missing pkg dir?
22:59 bretep I think so, and sources and the change log generation was taking hours!
22:59 joehh If I was doing what I think you were doing, then I would start with getting the source dir
23:00 joehh not sure about the last one (taking hours)
23:00 bretep I kept fixing different problems once I'd fix say the source dir problem another one problem would come up
23:00 bretep This was early december, It's now feb. maybe I should give it another go.
23:00 joehh dget -ux http://ppa.launchpad.net/saltstack/salt/ubuntu/pool/main/s/salt/salt_0.17.5-1precise1.dsc
23:01 joehh then make your changes
23:01 bretep I'm just shocked it's so difficult.
23:01 joehh update the changelog file
23:01 scoates what a relief (-:
23:01 joehh then debuild -us -uc
23:01 joehh if you want binary packages
23:01 bretep 0.17.5 does not have the back ported fixes I need
23:01 bretep specifically I need https://github.com/saltstack/salt/commit/113adcd36d3a2f86111c5bcd678184203f1dd41f
23:02 joehh shouldn't be so difficult - I'll add some docs to the debian/ubuntu installation pages on building with custom fixes
23:02 bretep It's in the 0.17 branch but not 0.17.5
23:03 joehh if you do the steps above with that fix on a precise system, it should work
23:03 babilen joehh: I could compile just fine against wheezy + wheezy-backports with cowbuilder
23:04 bretep joehh: thanks I'll give it a go
23:04 joehh babilen: that is how I build the official packages :)
23:04 bretep It's be nice to have a jenkins job that did this?
23:04 babilen joehh: (am using a local fork as I had to backport https://github.com/saltstack/salt/pull/9184) -- btw, a README.source would be nice or some build instructions. Where do you keep the backports btw?
23:05 joehh babilen: got to go to meeting - answer shortly
23:05 babilen joehh: I mean: Where do I find the git branch for backports?
23:05 scoates additional annoyance: .slsc file (-:
23:05 babilen nooo!
23:06 jimallman left #salt
23:06 scoates doc for import_source "Note that if a properly matching byte-compiled file (with suffix .pyc or .pyo) exists, it will be used instead of parsing the given source file."
23:07 babilen bretep: oh, that is a pretty bad one. i am happy that I saw that before continuing my work .. Yet another patch for my local fork then. ;-/
23:09 bretep babilen: you might be interested in https://github.com/saltstack/salt/pull/10013
23:09 forrest bretep that's cool
23:10 forrest so you have boxes called prodwebserverfront and prodwebserverback?
23:10 bretep No I made all that up
23:10 forrest oh ok
23:10 bretep I don't post real stuff
23:10 forrest I was like 'man these naming schemes make me feel bad for you'
23:11 babilen bretep: I've seen that before and yes, I am *very* interested in it, but it is apparently not likely to make it into a release soon. IIRC 2014.6 was mentioned which is too far in the future to use that in production right now with a local backport. (I try not to rely on code that won't make it into an official release withing, say, four weeks)
23:11 bretep :)
23:11 bretep Makes sense
23:11 forrest babilen, are you just unable to upgrade to more recent releases?
23:12 forrest if it's due to an outstanding bug you should +1 it, or mention your issue so it can get more visibility
23:12 babilen bretep: That, together with https://github.com/saltstack/salt/issues/2466 would make me a very happy person
23:12 babilen forrest: I cannot upgrade to a release that has not been released yet
23:12 forrest oh you're using stuff from develop
23:12 seanz whiteinge: ping
23:13 whiteinge seanz: hi
23:13 seanz Greetings!
23:13 seanz I was wondering about requiring an entire sls file.
23:13 babilen forrest: I've backported https://github.com/saltstack/salt/pull/9184 am pondering bretep's one, but simply don't want to maintain a local version myself that is too out-of-sync with what is being scheduled for the next release
23:13 bretep Yeah, one snag with that. the includes only works at the top level, not in-line. Ugh... I want to tackle that soon, but it's not an easy one
23:13 forrest babilen, fair enough
23:14 whiteinge seanz: it can be done! sec...
23:14 seanz whiteinge: I have a case where I'm requiring that curl be installed. The sls file is just basically pkg.installed. However, it seems to run later than the block where the require is.
23:14 forrest seanz, is it an include at the top of the file?
23:14 forrest I thought auto ordering was supposed to address that to ensure that included states ran before the state they are included in...
23:15 seanz forrest: It is. I have a pastebin entry - looking for the link.
23:15 seanz http://pastebin.com/cViNvhRA
23:16 forrest that's already using the require logic for an sls
23:16 forrest it's not working?
23:16 seanz forrest: It isn't. I get an error: Requisites not found: curl"
23:16 seanz That's a paraphrase.
23:16 forrest odd
23:16 forrest your indenting bothers me :(
23:17 seanz 2 spaces, right?
23:17 seanz I shall fix.
23:17 forrest it's the extra between include for curl, and postfi
23:17 seanz However, when I do pkg.installed: curl in the require, that works.
23:17 forrest *fix
23:17 forrest that's like, 4 then 5 it looks like
23:17 seanz Oh, that's a pastebin rendering issue.
23:17 forrest oh cool good to know
23:17 seanz The raw paste shows it correctly.
23:18 dave_den 'sls' isn't a state module
23:19 forrest http://docs.saltstack.com/ref/states/requisites.html#require-an-entire-sls-file should work though
23:20 seanz forrest: I referenced that file.
23:20 seanz That page.
23:20 forrest yea, dave_den were you talking to someone else? Or am I missing something
23:20 dave_den no, disregard that
23:20 dave_den :)
23:21 forrest ok
23:21 forrest seanz, is there anything weird going on in the init you have for curl?
23:22 forrest and have you confirmed that the other items that are part of your include work when required?
23:22 seanz http://pastebin.com/bJvZGQzM
23:22 seanz debconf-utils was failing, too.
23:22 forrest that's all your init is right?
23:22 seanz Once I changed curl to pkg.installed and removed debconf-utils (it was being included elsewhere, I realized), the whole thing worked.
23:23 forrest yea that's lame though, you should be able to require the state.
23:23 forrest what release is this?
23:23 seanz 0.16.4
23:24 scoates is there a way to tell pillar not to cache?
23:24 scoates I have stale entries. even after a salt-run cache.clear_pillar \*
23:24 dave_den seanz: what's the exact error?
23:25 dave_den scoates: the cache.clear_pillar only clears the cache on the master
23:25 seanz dave_den: http://pastebin.com/rJkuExHW
23:25 stewpot maxleonca: fixed, thankyou.
23:25 ajw0100 joined #salt
23:26 maxleonca excellent
23:26 scoates dave_den: yeah. and then I highstated the minion, and it seems to still have the old pillar. I'm confused.
23:27 dave_den seanz: does curl live in the root of the file_roots path?
23:27 seanz dave_den: Yes, same as postfix is.
23:27 seanz And java.oracle-java7.
23:29 scoates refresh_pillar also returns None for me, for that minion
23:29 rgbkrk joined #salt
23:29 scoates a minion restart gives me fresh pillar data.
23:29 scoates but even a highstate doesn't give me fresh data
23:29 scoates at least not for pillar.get
23:30 seanz dave_den: forrest, whiteinge: I'll catch up with you tomorrow. I've got to head out now, but I'm curious if you will be able to figure out what's happening with my state up in here.
23:30 seanz See you later, and thanks for trying to help.
23:31 scoates welp. I'm going to go drink some beers instead. (-: thanks for the help today, dave_den
23:32 felixhummel joined #salt
23:39 forrest later
23:47 jrdx joined #salt
23:50 clintonius joined #salt
23:51 clintonius any salt-virt pros in the house?
23:52 clintonius dang it. Pacific time is killing me. Salt guys are probably home already in Utah :-)
23:52 scoates mission slightly delayed.
23:53 scoates is there a way to tell my minions to just never cache pillar data?
23:53 clintonius scoates: that would be nice... force a refresh each command
23:53 clintonius might be slow though
23:54 scoates this one won't even refresh when asked. data stays stale until the minion restarts. driving me crazy.
23:54 clintonius ouch. that is no good. Latest version?
23:55 clintonius and are you using Git by chance?
23:55 kermit joined #salt
23:56 scoates 0.17.5
23:56 clintonius that is indeed the latest
23:56 scoates minion is 0.17.2
23:57 clintonius upgrade might be worth a shot
23:57 clintonius freaking Salt upgrades faster than Node.js. It is awesome, but hard to keep my systems up to date

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