Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-10-18

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

All times shown according to UTC.

Time Nick Message
00:01 cshuman joined #salt
00:07 dranger joined #salt
00:08 __number5__ vespakoen: sorry, I'm wrong. the file.managed only support source from salt master or gitfs/hgfs/etc.
00:08 vespakoen do you see what I try to achieve? is there an alternative way to get it done?
00:08 m0hit_ joined #salt
00:09 __number5__ vespakoen: you can use file.cp or file.symlink deal with it, but not exactly like managed does
00:09 vespakoen yeh that is too bad, would wish to use the template language
00:10 __number5__ the other way around is to checkout your git repos at salt master under file_roots, then use salt:// to get them through
00:10 vespakoen yeh
00:10 vespakoen think i'll go that route
00:10 __number5__ it's actually faster than git checkout at minions
00:11 vespakoen well the code has to be there anyways
00:11 vespakoen but that will work too i guess
00:13 m_george|away joined #salt
00:13 mgw joined #salt
00:13 __number5__ imho, the nginx configs templates should live at salt master
00:14 m_george left #salt
00:15 justlooks joined #salt
00:17 vespakoen thanks I will explore that approach a bit more
00:17 vkurup joined #salt
00:20 mgw joined #salt
00:23 darrend joined #salt
00:27 oz_akan_ joined #salt
00:27 pdayton joined #salt
00:30 pdayton1 joined #salt
00:31 mofomikes joined #salt
00:33 redondos joined #salt
00:33 redondos joined #salt
00:34 t13 joined #salt
00:40 NetworkN3rd joined #salt
00:49 krissaxton joined #salt
00:57 akasto joined #salt
00:58 vespakoen joined #salt
01:04 Drawsmcgraw joined #salt
01:04 pdayton joined #salt
01:11 m0hit joined #salt
01:12 KyleG joined #salt
01:12 KyleG joined #salt
01:14 brianhicks joined #salt
01:14 ajw0100 can gitfs be used with a masterless minion? if so, should fileserver_backend and gitfs_remotes be added to /etc/salt/minion?
01:16 m0hit joined #salt
01:17 toofer joined #salt
01:18 rgbkrk joined #salt
01:21 Gifflen joined #salt
01:22 cachedou_ ajw0100: I have not tested it but my guess is that won't work correctly. I don't see minion code that interfaces with the Fileserver class. But again, I haven't tested it so it's worth investigating further.
01:23 cachedou_ (Apologies for the non-specific answer. It's more of a best-guess.)
01:24 ajw0100 cachedou_ doesn't seem to work for me. plus I don't see fileserver_backend and gitfs_remotes documented here: http://docs.saltstack.com/ref/configuration/minion.html#file-directory-settings
01:24 ajw0100 so I guess that probably means gitfs is a no go with a masterless minion
01:27 cachedou_ ajw0100: If you want to ping me tomorrow, I'll check with the guys in the office and we'll come to a consensus.
01:27 ajw0100 cachedou_ awesome will do. thanks.
01:27 cachedou_ You're welcome.
01:33 UtahDave joined #salt
01:34 Teknix joined #salt
01:35 elbaschid joined #salt
01:36 ingwaem joined #salt
01:38 KyleG joined #salt
01:38 KyleG joined #salt
01:38 elbaschid Hi guys
01:38 Nexpro joined #salt
01:39 elbaschid I've got a quick question about specifying files in pillar
01:39 elbaschid I'm trying to provide SSL certs via salt and would like the entire .key/.crt file to be in pillar
01:39 ingwaem Greetings Salty friends!   Hey quick question about states. I have some pretty fancy state files setup now, that combine file recursion with cmd.waits and watches. With the watches, I know that when a file or folder that's being watched has it's state change, these commands will fire off. I also know that the state will only check the changes and execute when the overall state is called (for example, my state file is called
01:39 ingwaem ios-directories.sls and has perhaps 10 folders and commands that run in sequence of each other). what I'm interested to know though … is there a way to automate the execution of states watching something?
01:40 elbaschid a similar thing was discussed in https://github.com/saltstack/salt/issues/1543 but the refrenced commit doesn't make it clear to me how this is supposed to work
01:40 elbaschid does anyone know more about this?
01:41 elbaschid can I actually reference a file within one of my pillar_roots dirs? Or do I still have to have the file content in a SLS file?
01:45 ingwaem elbaschid, you could assign it to a variable I guess, then o execution of your state/pillar, write the cert to disk on the target minion from the variable. Although i am not entirely sure…I hack such things with php, and the salt api.
01:45 pdayton joined #salt
01:45 fxhp http://russell.ballestrini.net/postfix-salt-state-formula/
01:45 redondos joined #salt
01:45 redondos joined #salt
01:45 fxhp Hadoken!
01:45 elbaschid ingwaem: that's exactly what I am trying to avoid
01:45 m0hit joined #salt
01:45 ingwaem Hmm, thanks fxhp, I'll give that a try.
01:47 _ilbot joined #salt
01:47 Topic for #salt is now Welcome to #salt - SaltConf in January!! http://saltconf.com | 0.17.1 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/
01:49 krissaxton joined #salt
01:49 fxhp ingwaem - thats how I control postfix on all my servers
01:51 fxhp elbaschid - we ended up placing the key/crt into pillar multiline yaml ... at some point we plan to write a jinja filter/function to read in values from relative files (.key/.crt)
01:52 Gifflen joined #salt
01:52 ingwaem fxhp: cool. Yea, it would be an interesting solution because I have a bunch of minions that update files from the master. The master updates from git. IT's a way of ensuring my minions don't have to have external access, or security keys etc. What would be cool is if a repo has updated and I've fired off the repo sync state, to have other states watching that state and they would automatically push to the minions accordingly. I'll h
01:52 ingwaem to give it some good thought too as it would automate on the master, but have to cascade through to the minions…that way I can keep internal code as up to date as the git files, without having to run a state every time I do it.
01:53 fxhp elbaschid: but in the end, pillar doesn't serve files, it serves generated pillar data specified in yaml schema and interpreted as python dict datastructures
01:54 fxhp ingwaem: are you talking about postfix?
01:54 ingwaem elbaschid: i've been using php, mysql in combination with salt to drive state file generation for some things as well as organizing and triggering internal events…the route I had in my head was have the cert in a field in the db, pull that out, and target a minion and write the value into a file there. or have the files in a central location on the salt master and push accordingly using the salt:// address
01:55 ingwaem fxhp: yes, in reference to your postfix example. Mine isn't specifically related to postfix but I like the logic. makes sense
01:56 fxhp elbaschid: the generated pillar schema happens _only_ on the master, which is unlike the salt file_roots which are compiled by each minion individually
01:57 fxhp ingwaem - cool yeah, are you talking about how the cmd.wait states are watching related files and performing updates?
01:57 ingwaem yes
01:58 ajw0100 joined #salt
01:58 fxhp yes, we make great use of cmd.wait, you can think about it like this; cmd.wait will never happen _unless_ the states it watches change
01:58 nmistry joined #salt
01:58 melinath joined #salt
01:58 fxhp (super powerful)
01:58 ingwaem Can you watch a directory?
01:58 fxhp You can watch _any_ state
01:59 Lue_4911 joined #salt
01:59 teebes joined #salt
01:59 fxhp and then run _any_ cmd
01:59 fxhp Its my fav pattern in all of salt
01:59 ingwaem wow cool..I'm only touching the surface then :)
02:00 ingwaem I've been working with salt roughly 7 months now, ask UtahDave…and I've been doing some pretty amazing stuff but always learning and discovering new cool things with it :) LIke diving into a real salt mine :) haha
02:00 fxhp ingwaem - yeah salt isn't watching the directory, its watching the file.directory state
02:01 fxhp if that state it watches "Changed" (which is a response it provides) it will trigger and thine that is "waiting" and "watching"
02:02 fxhp thine/any state/
02:02 fxhp *** it will trigger any state that is "waiting" and "watching" ***
02:04 Gifflen joined #salt
02:05 ingwaem Ahh! Penny drops further and things get clearer. I'll change some of my logic because I've been watching the wrong things. I think with the state I have, with them all chained together, they're not actually watching a physical state change, but just an execution state within the state file. I'm lucky, I could have had a whole bunch of syncing and moving going on in the backend…nice though…I like :)
02:06 ingwaem can states on the master affect minions too? or can the minions watch the salt://blabla directory and if it changes do something?
02:07 ingwaem i've done minion specific things with the salt 'minionname' globs up to now
02:07 ingwaem and commandline only
02:09 Lue_4911 joined #salt
02:09 ingwaem Perhaps I'm just being dumb…forgot about the base params in the top.sls file.
02:13 Gifflen joined #salt
02:15 elfixit joined #salt
02:16 mofomikes joined #salt
02:17 xl1 joined #salt
02:17 ingwaem I'll be back later. Thanks for all your help fxhp :)
02:20 juicer2 joined #salt
02:23 pabelanger joined #salt
02:23 djn joined #salt
02:26 mgw2 joined #salt
02:27 cachedout joined #salt
02:50 krissaxton joined #salt
02:54 cachedout joined #salt
02:56 cachedout joined #salt
03:01 mwillhite joined #salt
03:04 cmthornton joined #salt
03:04 shadowsun In 0.17.0 I ran salt -G 'node:group' -b 2 state.highstate, and it would batch starting highstate - without waiting for it to finish (as far as I could tell). The end effect of this is that it ran a state.highstate on all of them within about a minute, which (in reality) meant that all the jobs started by the highstates were running *at the same time*, completely negating the entire purpose of having a batch command. Is there an easy
03:07 brianhicks joined #salt
03:15 mwillhite joined #salt
03:17 pentabular joined #salt
03:20 pentabular1 joined #salt
03:20 cachedout joined #salt
03:21 Gifflen joined #salt
03:28 mgw joined #salt
03:32 ajw0100 joined #salt
03:51 krissaxton joined #salt
03:52 pipps joined #salt
03:53 pipps3 joined #salt
03:55 pentabular joined #salt
03:57 pentabular joined #salt
03:57 donatello joined #salt
03:59 pipps joined #salt
04:01 pipps2 joined #salt
04:01 rgbkrk joined #salt
04:03 TheSojourner joined #salt
04:03 TheSojourner joined #salt
04:05 donatello hi all
04:05 shinylasers joined #salt
04:06 donatello i am looking to generate salt keys through a python script to achieve preseeded minions. i am not able to find key generations functions in the api though. please help
04:08 donatello i see the --gen-keys option for salt-key, but there seems to be no API way to do the same thing
04:10 jdenning joined #salt
04:11 pdayton joined #salt
04:13 oz_akan_ joined #salt
04:15 pentabular joined #salt
04:18 __number5__ Use the source, donatello https://github.com/saltstack/salt/blob/develop/salt/cli/__init__.py#L251
04:23 donatello ah here it is - https://github.com/saltstack/salt/blob/develop/salt/crypt.py#L59 - thanks __number5__ !
04:25 __number5__ np
04:33 jdenning joined #salt
04:36 pdayton joined #salt
04:37 druonysus joined #salt
04:37 pentabular joined #salt
04:43 vipul joined #salt
04:51 krissaxton joined #salt
04:55 zz__ joined #salt
05:02 m0hit joined #salt
05:02 ramteid joined #salt
05:06 shadowsun Does salt actually require the old version of msgpack?
05:11 linjan joined #salt
05:22 pmrowla joined #salt
05:24 [ilin] joined #salt
05:29 oz_akan_ joined #salt
05:36 matanya joined #salt
05:37 pdayton joined #salt
05:40 jdenning joined #salt
05:40 jumperswitch joined #salt
05:44 pdayton joined #salt
05:45 TheCodeAssassin joined #salt
05:52 krissaxton joined #salt
05:58 jefimenko joined #salt
06:30 UtahDave joined #salt
06:41 pipps joined #salt
06:53 krissaxton joined #salt
06:54 sebgoa joined #salt
07:00 balboah joined #salt
07:02 bud joined #salt
07:03 jasiek joined #salt
07:05 jefferai_gone joined #salt
07:08 keee joined #salt
07:09 pentabular joined #salt
07:09 tomspur joined #salt
07:13 krissaxton joined #salt
07:19 dranger joined #salt
07:22 ckao joined #salt
07:26 druonysuse joined #salt
07:26 druonysuse joined #salt
07:37 pentabular joined #salt
07:40 networkpadawan joined #salt
07:47 tomeff joined #salt
07:52 [M7] joined #salt
07:53 pentabular joined #salt
08:01 scott_w joined #salt
08:02 whiskybar joined #salt
08:09 vespakoen joined #salt
08:25 malinoff joined #salt
08:25 malinoff Hi all
08:28 vespakoen Is there a way I can get the minion id in a template?
08:30 malinoff vespakoen, {{ grains['id'] }}
08:30 vespakoen great, thanks
08:31 vespakoen hmmz, Undefined jinja variable; line 21 in template (          fastcgi_param LARAVEL_ENV {{ grains['id'] }};    <======================)
08:32 shomodj joined #salt
08:32 shomodj then ghost_url = "http://ghost/download/ {{ pillar['ghost_version"] }}.zip
08:33 rawzone joined #salt
08:34 vespakoen nvm, seems to work now
08:39 pentabular joined #salt
08:41 [M7] joined #salt
08:43 dranger anyone here using states.iptables in 0.17?
08:44 dranger I need some help on where to look for my issue... I'm getting the following when trying to apply a simple state
08:44 dranger 2013-10-18 10:25:51,596 [salt.loaded.int.module.cmdmod][INFO    ] Executing command 'iptables -t filter -A INPUT --in-interface lo --jump ACCEPT --__env__ base --__sls__ iptables --order 10001 ' in directory '/root'
08:45 dranger 2013-10-18 10:25:51,594 [salt.loaded.int.module.cmdmod][DEBUG   ] output: iptables v1.4.12: unknown option "--__env__"
08:47 zooz joined #salt
08:53 rawzone joined #salt
08:55 Lue_4911 joined #salt
09:05 felixhummel joined #salt
09:07 rawzone joined #salt
09:12 az87c joined #salt
09:34 goki joined #salt
09:35 bhosmer joined #salt
09:36 backjlack joined #salt
09:42 shomodj pillar complex assignements http://pastebin.com/QEdGUHwE
09:49 vespakoen joined #salt
09:50 vespakoen I am trying to join(" ") values in an array, but it seems when using file.managed's context option, it does not allow for it (http://hastebin.com/hemonahuku.yaml) does anyone know how I can get this to work?
09:57 jumperswitch joined #salt
09:59 Furao vespakoen: there is a join jinja2 filter
10:01 vespakoen ahh
10:01 vespakoen so I am using the wrong template language =P
10:02 vespakoen pecified template format jinja2 is not supported
10:02 vespakoen should I download it or something?
10:03 vespakoen actually, in "args.domains|join(" ")" the join seems to be working, but the args.domains seems to be a string in stead of an array
10:03 anuvrat joined #salt
10:04 felixhummel joined #salt
10:10 elfixit joined #salt
10:10 vengeance joined #salt
10:18 oz_akan_ joined #salt
10:22 pnl joined #salt
10:25 krissaxton joined #salt
10:25 felixhummel joined #salt
10:25 krissaxton1 joined #salt
10:28 scalability-junk joined #salt
10:30 akitada joined #salt
10:31 modafinil joined #salt
10:32 octarine joined #salt
10:33 malinoff Hello, Furao
10:35 dranger joined #salt
10:40 ninkotech joined #salt
10:42 giantlock joined #salt
10:46 ebodine4 joined #salt
10:51 ebodine joined #salt
11:00 krissaxton joined #salt
11:01 mwillhite joined #salt
11:08 matanya joined #salt
11:21 matanya joined #salt
11:25 brianhicks joined #salt
11:28 jbunting joined #salt
11:29 matanya joined #salt
11:30 blee joined #salt
11:37 srage joined #salt
11:39 oz_akan_ joined #salt
11:43 felixhummel joined #salt
11:47 reinsle joined #salt
11:48 matanya joined #salt
11:54 tomeff joined #salt
12:02 zz_Cidan joined #salt
12:03 vkurup left #salt
12:07 jbunting joined #salt
12:12 teebes joined #salt
12:12 gldnspud joined #salt
12:14 xl1 left #salt
12:16 g3cko joined #salt
12:18 jbub joined #salt
12:18 mfournier joined #salt
12:18 Niichan joined #salt
12:18 EnTeQuAk joined #salt
12:19 Gareth joined #salt
12:32 Destro joined #salt
12:40 bhosmer joined #salt
12:42 Drawsmcgraw joined #salt
12:42 linjan joined #salt
12:43 Drawsmcgraw Anyone ever seen some oddness when using gitfs and roots?
12:43 Drawsmcgraw Specifically, I list gitfs as the first location for the fileserver to search. The second location is 'roots'.
12:44 Drawsmcgraw If I make a new state file on the file system (say, /srv/salt/foo), then try to run a salt comand with  'state.sls foo', the minion comes back saying that there's no such state.
12:44 gldnspud joined #salt
12:44 Drawsmcgraw This persists even if I run a saltutil.sync_states
12:46 NetworkN3rd joined #salt
12:55 rgbkrk joined #salt
12:56 xinkeT joined #salt
13:00 racooper joined #salt
13:00 Kholloway joined #salt
13:01 ss_ joined #salt
13:01 ss_ hi all
13:03 jslatts joined #salt
13:03 ss_ we have 4 different environments. deploying packages through salt. how to change IP based on respective environments
13:03 ss_ through salt
13:04 ss_ because .rpm package has different IP
13:05 vespakoen ss_ you can use {{ grains['id'] }} to get the minion_id / hostname (learned that today)
13:06 Jahkeup joined #salt
13:07 Gifflen joined #salt
13:07 diegows_ joined #salt
13:07 ss_ can u plzbrief me
13:09 timoguin joined #salt
13:12 ipmb joined #salt
13:16 oz_akan_ joined #salt
13:16 shomodj anybody here from Croatia that uses salt?
13:17 juicer2 joined #salt
13:17 bhosmer joined #salt
13:20 toastedpenguin joined #salt
13:23 jrdx joined #salt
13:23 AdamSewell joined #salt
13:23 ddv joined #salt
13:23 brianhicks joined #salt
13:26 NetworkN3rd_ joined #salt
13:27 c0bra joined #salt
13:29 Destro I have a quick question, busy looking at a central configuration management engine. Thus would like to know if Salt is opensource and free ?
13:29 mofomikes joined #salt
13:29 Destro Might be a n00b question however got it seems to be free till I gone to http://saltstack.com/products
13:30 xt Destro: it's opensource and free
13:30 xt it's also gratis
13:30 Destro Dutch: gratis ?
13:30 abe_music joined #salt
13:30 xt dutch?
13:30 tempspace Destro: https://github.com/saltstack/salt is the repo
13:31 xt gratis is an english word, also used in many other languages
13:31 xt it means free of chrage
13:31 xt *charge
13:31 Destro Thanks :-)
13:32 Destro Would be great, and will watch this space for more (y) Till next time
13:33 pnl xt: actually, it's a latin word
13:33 xt pnl: it can be both latin and english, you mean
13:33 xt english word just means that it's in the english dictionary :-)
13:34 xt english doesn't have their own words, just imported everything
13:36 c0bra "internet" is an English word
13:36 sebgoa joined #salt
13:36 mwillhite joined #salt
13:37 xt inter is latin
13:39 oz_akan_ joined #salt
13:39 tempspace xt: You going to SaltConf?
13:39 xt I would like to, but I doub't I can manage
13:40 Destro My spell checker doesn't recognize internet as a word :o
13:40 tempspace Destro: how about interwebs?
13:40 Destro interwebs :-( unfortunately not
13:41 Destro Maybe I need to update my Ubuntu with a latin dictionary :-)
13:44 Destro internet -> Right click -> Spelling Suggestions -> Add 'internet' to English Dictionary
13:44 Destro problem resolved
13:44 Destro Have a great weekend (y)
13:49 racooper what about Internet? some dictionaries seem to think it Must Be Capitalized
13:51 noxeor laser is an original English word.
13:51 tyler-baker joined #salt
13:52 pnl acronym
13:53 racooper was going to say...LASER is an acronym, not a word, technically
13:53 noxeor initially, yes, but it is actually a word.
13:53 noxeor la·ser  [ley-zer]  Show IPA noun Physics. a device that produces a nearly parallel, nearly monochromatic, and coherent beam of light by exciting atoms to a higher energy level and causing them to radiate their energy in phase.
13:54 noxeor It was *created* as an acronym, but it is a word nonetheless.
13:54 pnl acronym is a subclass of word
13:55 noxeor but I appreciate the immediate pounce on that. lol
13:55 noxeor so you admit it's a word. lol
13:55 pnl never said it wasn't
13:58 amahon joined #salt
13:59 noxeor true
13:59 noxeor quark, maybe? quark (n.) Look up quark at Dictionary.com 1964, applied by U.S. physicist Murray Gell-Mann (b.1929), who said in correspondence with the editors of the OED in 1978 that he took it from a word in James Joyce's "Finnegans Wake" (1939), but also that the sound of the word was in his head before he encountered the printed form in Joyce.
13:59 noxeor this is fun. :]
13:59 noxeor I really should be working...
14:00 noxeor jedi   Use Jedi in a sentence Ads "Ender's Game" - Nov 1 www.endersgamemovie.com/ Harrison Ford & Ben Kingsley Star In This Sci-Fi Epic. Watch Trailer! S. www.mulhollandbooks.com/S. One book. Two readers. A world of mystery by J.J. Abrams & Doug Dorst World English Dictionary jedi or Jedi  (ˈdʒɛdaɪ)    — n a person who claims to live according to a philosophy based on that of the fictional Jedi, a caste of wizards in the Star Wars
14:01 noxeor ;)
14:01 mua joined #salt
14:02 racooper alright...Salt Conf registration, hotel and airfare...complete!
14:06 alunduil joined #salt
14:09 jergerber joined #salt
14:12 Brew joined #salt
14:14 cachedout joined #salt
14:14 NetworkN3rd joined #salt
14:14 kaptk2 joined #salt
14:18 noxeor Sooo.. Salt gods.  I am still [very] new to this.  How would I go about (generally) implementing a conditional modification.... for example, I run [ ifconfig lo|grep MTU| awk '{print $4}'| sed 's/[^0-9]//g' ]; if the result is NOT "1500", then I want to run a command to set it to 1500...
14:19 lineman60 joined #salt
14:22 cwright noxeor: look at `cmd.run` with an `unless`
14:22 noxeor awesome -- thank you!
14:22 teskew joined #salt
14:23 tempspace noxeor: I use a bash if/else in my unless for stuff like this. ex: unless: "if [ \"$(pear list-channels | grep pear.phpunit.de | cut -d\" \" -f1)\" = \"pear.phpunit.de\" ]; then true; else false; fi"
14:23 tempspace return true if the condition you want is met
14:24 berto- joined #salt
14:26 dray3 joined #salt
14:27 deedubs joined #salt
14:27 jalbretsen joined #salt
14:27 deedubs is saltmine what I would use to let minion's locate other minions?
14:27 deedubs f.e. locate a db server,
14:28 Furao deedubs: I use mine for such kind of thing
14:29 Furao mostly autodetection for monitoring
14:30 deedubs yeah, there is no TTL on mine data correct?
14:30 Furao it's refresh each hours
14:30 deedubs oic
14:30 Furao you can refresh more frequently or manually
14:31 deedubs so it seems like it would be good for the initial locating of minions for cluster setup etc, but maybe not for locating machines that are 'online' at this point in time
14:31 deedubs unless you forced a refresh
14:32 akio left #salt
14:35 adepasquale joined #salt
14:35 cro joined #salt
14:36 adepasquale left #salt
14:37 NetworkN3rd joined #salt
14:38 Rick1 joined #salt
14:38 bhosmer joined #salt
14:41 vespakoen joined #salt
14:52 cro joined #salt
14:58 mgw joined #salt
14:58 noxeor tempspace: thanks, this worked well for me: - unless: ifconfig lo|grep MTU| awk '{print $4}'| sed 's/[^0-9]//g'|grep ^1500$
14:59 Jahkeup joined #salt
15:00 mgw bud: did you see https://github.com/saltstack/salt/pull/7920 ?
15:00 noxeor every time I do something with Salt, I like it more...
15:00 bud Hi mgw, seen it, awesome!
15:00 bud Hadn't had time to test the new code yet.
15:01 mua joined #salt
15:02 bud Had a nice time reading the code, I have learned a little out of it.
15:02 swa joined #salt
15:02 swa joined #salt
15:03 bud It'a shame it didn't make it in 0.17.1 though.
15:04 swa Is it me, or it doesn't look like the doc makes it clear master and minion must run the same exact config, or you are expected to encounter pretty bad bugs ?
15:05 pdayton joined #salt
15:05 swa same exact *version*
15:06 mgw bud: it wouldn't have made it anyway, it's a feature not a bug
15:07 emil joined #salt
15:07 bud I was just thinking now about how salt is developed and thought that it didn't make it because of this. I will test it and get back to you.
15:08 StDiluted joined #salt
15:10 mgw bud: also, https://github.com/saltstack/salt/issues/7844#issuecomment-26525006
15:10 abe_music joined #salt
15:10 bud I have seen that also. That's much better than my sleep right?
15:11 mgw not sure it's much better
15:11 mgw and it's not tested
15:11 mgw I'd rather figure out why the chroot exec is keeping the mount busy
15:12 jefferai joined #salt
15:12 cro joined #salt
15:12 bud I agree.
15:12 krissaxton joined #salt
15:13 bud I have also chroot inside the mount and ps aux. Did not see any running services...
15:13 mgw it's possibly the way I kill pids, maybe they don't die instantly
15:14 SunSparc joined #salt
15:14 cro joined #salt
15:20 forrest joined #salt
15:20 cachedout joined #salt
15:21 NetworkN3rd joined #salt
15:21 brimpa joined #salt
15:22 ddsstt joined #salt
15:22 ddsstt Hi!
15:23 forrest hey
15:23 ddsstt Of course, I have a question about SaltStack
15:23 forrest what's up
15:24 ddsstt Is there any option to specifically order states in top.sls? E.g. I have a local mirror of custom APT packages, and this state should be executed first
15:24 ddsstt - order: 10 works, but doesn't seem to be really elegant
15:24 forrest The way I usually do that is through the states themselves ddsstt
15:24 forrest you can require an sls file
15:25 forrest http://docs.saltstack.com/ref/states/requisites.html#require-an-entire-sls-file
15:26 forrest so usually what I'd do is create a repo.sls, then in my package/init.sls, you would include repo.sls, and then put a require of that sls file when the package is installed
15:26 ddsstt Thank you forrest
15:26 ddsstt Still, looks like a boilerplate code a little bit
15:27 forrest Yep, and I'm sure with 0.17 since it now runs content of states in order there are more elegant ways to do this, I just don't know what it is.
15:27 ddsstt E.g. if you install like 10 packages
15:27 ddsstt You'll have to require repo.sls in each definition, which doesn't look lille a clean way to solve the problem
15:27 ddsstt So, 0.17 is evaluating states in order they're listed?
15:28 forrest it evalutes the content of states in the order they are listed.
15:28 cachedout Evaluating and executing, yes. That's the state auto order system which is on by default in 0.17
15:28 forrest cachedout, does that occur in the top file?
15:29 cachedout AFAIK, any sls file including the top file.
15:29 cachedout I will double-check though.
15:29 forrest cachedout, nice, I haven't tested that yet
15:30 forrest ddsstt, it really isn't that boilerplate, because you're ensuring each item is a singular entity, so if you only need one package, you don't have to rewrite the state. It's much easier on 0.17 if the top file gets interpreted like cachedout is saying
15:30 rgbkrk joined #salt
15:30 forrest cuts out a LOT of work, and gives it one more advantage over puppet
15:30 ddsstt Okay, thank you a lot
15:31 ddsstt That really helped, guys
15:31 krissaxton joined #salt
15:32 cachedout Auto-ordering is a huge deal. Back in a former life a CFM engine that shall-not-be-named made me tear my hair out for the lack of it.
15:32 cachedout Heh
15:32 forrest I almost can't work without requires I'm so used to them cachedout :\
15:32 forrest feels weird not to write them
15:32 cachedout Whatever gets the job done. :]
15:38 mwillhite joined #salt
15:39 UnwashedMeme left #salt
15:41 forrest cachedout, can you let me know once you've confirmed the top file order?
15:42 cachedout Yes. I want to ask some people in the office a question about that but they're not in yet. I'll let you know once I have a solid answer for you.
15:42 forrest awesome
15:43 sebgoa joined #salt
15:44 cshuman joined #salt
15:47 UtahDave joined #salt
15:50 ubercore joined #salt
15:54 carmony does salt-cloud work with DigitalOcean?
15:55 carmony ping UtahDave
15:55 mgw joined #salt
15:55 UtahDave yep!
15:56 pabelanger left #salt
15:56 carmony UtahDave: care if I bug you for a little bit while I try and get salt-cloud up and running? :P
15:57 UtahDave carmony: yeah, that would be totally fine
15:58 carmony should I do it in here or PM you? :P
15:59 timoguin share with the wooooorld!
15:59 timoguin never underestimate the power of the lurkers
15:59 krak3n` joined #salt
15:59 forrest better yet carmony, document it and do a pull request :P
15:59 timoguin now that's just too far!
15:59 forrest Picking UtahDave's brain: Chapter 1 -
16:00 carmony seriously, I should document it out :) since I am an excellent "dumb user" so I ask all the right dumb questions. :P
16:00 forrest Yea I see this already https://salt-cloud.readthedocs.org/en/latest/topics/config.html#digital-ocean
16:00 UtahDave lol
16:01 UtahDave carmony: let's talk about it in here.  First, what's your DigitalOcean username and password?
16:01 carmony ah, cool, it wasn't listed on http://salt-cloud.readthedocs.org/en/latest/ (from what I saw)
16:01 UtahDave :)  j/k
16:01 forrest lol
16:01 carmony LOL
16:01 berto- joined #salt
16:01 timoguin yea examples are sparse on stuff like specifying an ssh key etc.
16:01 timoguin took me a day or so of confusion to get working
16:01 StDiluted is there documentation for the VPN feature in salt-cloud yet?
16:01 carmony Ok, so let me talk about my "goal" of what I'm trying to accomplish
16:01 StDiluted I would love that to exist
16:02 timoguin StDiluted, DO's private network in NY2, you mean?
16:02 StDiluted no, AWS VPC
16:02 timoguin ah
16:02 StDiluted as in, launching AWS instances directly into a VPC
16:02 UtahDave StDiluted: I think we have initial support for that, but I'm not sure how polished it is yet.
16:02 StDiluted someone added the code but it wasn't doc'd yet
16:03 pass_by_value joined #salt
16:03 TJ1980 joined #salt
16:03 carmony so I was thinking of doign this with Vagrant somehow, but I want to be able to spin up a Master and configurable number of minions on demand, test and try some things out, and then tear everything down a few hours later
16:03 KyleG joined #salt
16:03 KyleG joined #salt
16:05 UtahDave OK, so salt-cloud can build a server that is a master, but in order for salt-cloud to automatically configure and pre-authorized the new minions to connect into your master salt-cloud has to be running on the master
16:06 StDiluted carmony: vagrant has the ability to bring up multiple computers as well
16:06 jdenning joined #salt
16:06 carmony StDiluted: yeah, so I kinda have it kinda working on my fun-with-redis project
16:07 druonysuse joined #salt
16:07 druonysuse joined #salt
16:07 carmony So my thought was is I could have vagrant go out and setup one salt-cloud server
16:07 dranger joined #salt
16:08 carmony and then let salt-cloud take over from there
16:09 cachedout forrest, can I PM you?
16:09 forrest sure
16:09 TJ1980 I have an AMI that I would like to bring up with salt-cloud.  How do I specify additional user_data that other programs on the AMI expect to find?
16:10 UtahDave carmony: that sounds great.
16:11 carmony https://github.com/JustinCarmony/fun-with-redis-2 -- this is what I have with Vagrant doing all the provisioning of setting up a master and a minion
16:13 ricicle joined #salt
16:13 Jahkeup joined #salt
16:15 ricicle Hi all, let' say I have a custom.repo file that is dropped and the repo server is the source for all packages. Can I do a require_in for pkg: * to avoid having to require custom.repo every time I use pkg?
16:15 forrest ricicle, you should be able to include the state at the top, I believe with the ordering in 0.17 it should run that first, can anyone confirm/deny that?
16:16 drewbert joined #salt
16:16 Linz joined #salt
16:16 carmony so salt-cloud is just an extension on top of a salt-master?
16:18 ricicle forrest: I've argued for ordering but have been asked to be explicit. The rationale being there may be optimisations in the future that allow for some salt states to be run after its required packages to have been installed.
16:19 forrest ricicle? I guess I'm confused, states now do ordering by default in 0.17
16:19 forrest oh you're saying specifically at your organization?
16:19 UtahDave carmony: yeah, pretty much.  In fact it's going to be merged in to salt proper soon
16:20 carmony cool
16:20 ricicle forrest: yes, we have a custom repo. Every package will require the repo file to be in place
16:20 forrest right, but you can't just include the sls at the top?
16:21 forrest the repo sls
16:21 ricicle including doesn't add require: file: custom.repo though?
16:22 ricicle sorry, that came out badly. I mean I will still need to have require: file: custom.repo every time I use pkg?
16:23 forrest That's what I'm not sure about
16:24 forrest because if you're using 0.17, state ordering is on by default
16:24 forrest so if you include repo.sls, it should run that first right?
16:24 TheCodeAssassin joined #salt
16:26 pipps1 joined #salt
16:27 forrest UtahDave, does the state ordering in 0.17 apply to states that you include? So an included state will be applied before content within the sls itself is run?
16:28 amahon joined #salt
16:30 bhosmer joined #salt
16:30 DredTiger joined #salt
16:30 ricicle Ah, we're on 0.16.4 at the moment, time to upgrade :)
16:31 forrest 0.17.1 should be out soon ricicle
16:31 forrest might want to wait
16:31 forrest it's got a lot of fixes.
16:32 cshuman joined #salt
16:34 UtahDave forrest: OK. I just cleared this up with Tom
16:35 UtahDave Yes, an included state is applied "above" the including state
16:35 redondos joined #salt
16:35 redondos joined #salt
16:36 TheCodeAssassin2 joined #salt
16:36 fxhp Wrote this post for a friend in another channel last night, I shared it last night but I thought I would share this morning too
16:36 fxhp http://russell.ballestrini.net/postfix-salt-state-formula/
16:41 mwillhite joined #salt
16:42 forrest UtahDave, awesome thanks for double checking, that makes sense with the state ordering present in 0.17, but it's nice to have it confirmed, that's a great feature.
16:43 UtahDave yeah.  Also, if an sls file has already been include, it won't be included a second time.  It gets built into a big dictionary
16:43 UtahDave So if it is already there it doesn't get added back in
16:43 forrest fxhp, are you gonna add a map file and such to support multiple distros? If so you could get that replace: https://github.com/saltstack-formulas/postfix-formula
16:44 forrest UtahDave, nice, that's really really awesome functionality wise, especially since that's how you'd 'feel' it should work.
16:44 forrest so ricicle, upgrade to 0.17, or 0.17.1 when it comes out, and things get even more awesome
16:45 forrest err could replace, not could get that replace, jeez.
16:45 fxhp forrest - at this point I have no urge to support other distros, maybe solaris because I'm messing with smartos zones recently
16:45 fxhp forrest - although I don't see it being a very difficult task to support other distros
16:46 forrest fxhp, nah, if you use the jinja map it should be trivial.
16:46 fxhp UtahDave - watched salt-ssh salt air 16 last night, it was refreshing to see another member of salt company!
16:46 forrest lol
16:47 fxhp UtahDave - I could tell a couple hours before you guys got that to work and were on a high from it
16:47 VSpike left #salt
16:47 fxhp I feel the same way when salt does something magical for me
16:47 UtahDave :)  Marc was embarrassed  about the toaster oven and toaster in the background. :)
16:47 forrest why?
16:47 UtahDave yeah, seriously. It's way fun when that happens
16:47 forrest You should include corn dogs in all future videos
16:48 forrest as a testament to the toaster oven
16:48 UtahDave lol
16:49 forrest Really though, no one who gives two shits about tech cares about a toaster oven in the background, if anything it's something fun to show that the team is a bunch of human beings, and not robots.
16:49 troyready joined #salt
16:50 UtahDave Yeah, I agree. He just likes us to use the nice pretty SaltStack background that we have.
16:50 forrest Hah
16:50 forrest yea that was missing from the last vidoe as well, you guys only have one of those right
16:50 forrest *?
16:51 UtahDave Just the one big one
16:53 forrest Should draw a toaster on it
16:53 ajw0100 joined #salt
16:53 forrest because you can run salt on a toaster
16:53 forrest hoho
16:53 pdayton left #salt
16:57 TJ1980 joined #salt
17:02 akoumjian Hm, I'm trying to use pkgrepo to add newrelic monitoring to an ubuntu system. On 0.16.x my state works fine, but on 0.17.x it fails with "Failed to confirm config of repo deb http://apt.newrelic.com/debian/ newrelic non-free: repo "deb http://apt.newrelic.com/debian/ newrelic non-free" was not found
17:02 NetworkN3rd joined #salt
17:03 cwright akoumjian: remove the trailing slash from the end of the repo, it was a known issue
17:03 amckinley joined #salt
17:03 UtahDave cwright: have we fixed it yet?
17:03 vespakoen joined #salt
17:04 akoumjian cwright: Thank you, workaround appears to have worked
17:04 cwright UtahDave: I don't think so
17:04 cwright https://github.com/saltstack/salt/issues/7696
17:05 ajw0100 I have a state tree here: https://github.com/ajw0100/dev_vm_saltfs.git . If I clone it locally to /srv/salt/ and use the default master config everything works fine. If I change the master config to search the git fileserver_backend first and add the repo as a gitfs_remote I get "Data failed to compile". https://gist.github.com/ajw0100/7044464
17:05 ajw0100 can anyone spot what I'm doing wrong?
17:05 UtahDave ok, thanks, cwright
17:05 mgw I've got a #!py state that is causing me a lot of headaches
17:06 mgw it seems some minions expect pillar to be in __pillar__ and others in pillar.
17:06 mgw the two I'm coparing right now are both running 0.17.0.1-1precise
17:07 Brew joined #salt
17:07 UtahDave that's really odd, mgw.  can you pastebin what you've got?
17:08 mgw actually, it's the __grains__ it's choking on, but I suspect it would choke on pillar next
17:09 mgw https://gist.github.com/mgwilliams/9b48ba2bc5f5f6292de0
17:09 UtahDave mgw: I'm pretty sure that it should be __grains__ and __pillar__
17:10 UtahDave in that context
17:10 mgw I thought so too
17:11 mgw https://gist.github.com/mgwilliams/9b48ba2bc5f5f6292de0#comment-931790
17:11 jefimenko joined #salt
17:11 UtahDave mgw: Are you getting a stacktrace somewhere that is causing the creation of __grains__ to fail?
17:12 UtahDave You might try running the minion in debug mode to see
17:12 abe_music joined #salt
17:14 mgw no stack trace prior to that one
17:15 Lue_4911 joined #salt
17:15 mgw UtahDave: I can run grains.get environment just fine
17:17 jimallman joined #salt
17:20 UtahDave what version of salt are you on?
17:20 mgw UtahDave: I think I figured  it out
17:20 mgw I'll let you know in a second
17:20 UtahDave cool
17:20 pentabular joined #salt
17:21 mgw one of those minions may not be running from the package at all
17:23 mgw i'm removing what was installed from source
17:24 dave_den mgw: https://github.com/saltstack/salt/commit/d660b5f8c9862928ea2d56de8516d9b65c874e9e
17:24 mgw dave_den: thanks
17:25 mgw that seems to be the issue
17:25 UtahDave Ah, I didn't know about that one. Thanks, dave_den
17:25 dave_den yeah, pretty recent change. no prob :)
17:28 ddv joined #salt
17:28 UtahDave ah, apparently this was fixed in 0.17.1, mgw and dave_den.
17:29 UtahDave __grains__ and grains both work now, for backwards compatibility
17:30 dave_den ah, cool
17:30 jimallman joined #salt
17:30 UtahDave Yeah, that slipped through. Normally we don't break api's like that without some deprecation notification time
17:33 berto- joined #salt
17:33 amahon joined #salt
17:34 dave_den i'd love to help write more tests for salt when I can find some spare time. need moar tests!
17:35 UtahDave dave_den: yes, for sure.
17:36 mgw is there a script for eradicating salt installed from source?
17:37 forrest rm -rf /* mgw :P
17:37 mgw I have four minions that I installed from source at some point
17:37 mgw forrest: thanks I'll try that
17:37 mgw Do I need sudo?
17:37 forrest I'm joking
17:37 forrest don't do that
17:37 mgw lol
17:37 mgw I know ;-)
17:37 forrest jeez
17:37 forrest ok good
17:37 forrest was concerned there for a second
17:37 mgw lol
17:38 dave_den mgw: you should be able to just delete the salt directory in your python's site-modules dir, and delete the entry points scripts in /usr/local/ - salt, salt-minion, salt-master, salt-call, salt-run, etc.
17:38 dranger joined #salt
17:38 mgw dave_den: thanks, that's basically what I'm doing, but want to be sure I'm not missing anything
17:38 vespakoen joined #salt
17:38 mgw I wonder if I can pull this off from the master
17:39 dave_den if you can, i strongly recommend using virtualenvs for source installs
17:39 mgw If I install the packages first, then remove those entry points/dirs, then restart salt-minion
17:39 mgw dave_den: yeah… I had some issues with the init scripts and virtualenvs
17:39 mgw I'll give it another shot next time I need to install from source
17:40 danielbachhuber joined #salt
17:40 dave_den perhaps it would be nice to have support for defining a virtualenv to use in /etc/defaults/salt-xxx that the init scripts could check
17:41 dave_den then you could switch versions with a simple var change if you had multiple versions installed by virtualenvs
17:42 forrest has anyone tried running salt off a raspberry pi yet?
17:42 dave_den i just init my virtualenv in my upstrat scripts https://gist.github.com/dlanderson/6bea68e69f02c94e3cf1
17:43 Ryan_Lane joined #salt
17:45 timoguin forrest, There have been reports on the list of getting it working successfully on Raspian, using the debian wheezy instructions
17:45 timoguin back in August: https://groups.google.com/forum/#!topic/salt-users/H0_QS2HXIvY
17:45 forrest timoguin, yea I'm looking at those now, wasn't sure if anyone in here had tested it with a large env or anything
17:46 mgw dave_den: this worked: cmd.run "rm -rf  /usr/local/lib/python2.7/dist-packages/salt/; rm /usr/local/bin/salt-*; service salt-minion restart"
17:46 mgw Not sure I'd try that in production though
17:46 timoguin what could go wrong. ;-)
17:47 nocturn joined #salt
17:48 ajw0100 joined #salt
17:49 UtahDave yeah, lots of people have it running on  raspberry pi
17:49 mgw dave_den: thanks for the upstart script
17:49 forrest I'm more curious about performance UtahDave.
17:50 bhosmer joined #salt
17:51 UtahDave forrest: The minion runs pretty well.  Running a master is pretty slow at startup because of all the crypto it has to do
17:51 forrest yea
17:54 jrdx joined #salt
17:56 dranger joined #salt
17:57 josephholsten joined #salt
17:58 zakm_ joined #salt
17:59 dave_den mgw: no prob. just opened this, too https://github.com/saltstack/salt/pull/7950
18:00 ajw0100 joined #salt
18:00 forrest nice dave_den
18:03 Gareth forrest: I installed it the other day.  Pretty straight forward and seems snappy.  I'm using a Model B with the 512MB of ram though.
18:04 forrest yea I've got a model B as wel from pycon earlier this year, what distro did you throw on it?
18:04 Gareth Raspbian iirc.
18:04 forrest gotcha
18:06 Gareth took a bit to install it from pip.
18:07 vespakoen joined #salt
18:08 forrest yea I saw in the issue there were some workarounds that people were doing
18:10 Gareth yeah. mostly just installing most of the requirements via apt then pip install salt.
18:11 forrest gotcha
18:12 jon_____ joined #salt
18:17 ajw0100 joined #salt
18:25 jbunting joined #salt
18:30 dranger joined #salt
18:32 Teknix joined #salt
18:40 mwillhite joined #salt
18:42 mgw 0.17 seems to be creating pyc files in the _modules dir, and then trying to sync them (when running sync_modules)
18:43 pentabular joined #salt
18:48 dranger joined #salt
18:55 ajw0100 joined #salt
19:00 lemao joined #salt
19:08 NetworkN3rd_ joined #salt
19:09 Rick1 left #salt
19:11 felixhummel joined #salt
19:13 foxx joined #salt
19:13 lemao_ joined #salt
19:16 ricicle joined #salt
19:26 giantlock joined #salt
19:28 vespakoen joined #salt
19:29 Lue_4911 joined #salt
19:34 Gifflen joined #salt
19:35 druonysus joined #salt
19:39 hjubal joined #salt
19:39 hjubal joined #salt
19:40 lineman60 has salt-call been depreated?
19:42 Lue_4911 joined #salt
19:43 rawzone joined #salt
19:43 TheCodeAssassin joined #salt
19:46 ubercore lineman60: I don't think so?
19:47 dranger joined #salt
19:47 lineman60 i just installed salt  on ubntu 13.04 and it's not there
19:47 lineman60 hrm
19:47 ubercore you installed the minion?
19:48 ubercore also double check your paths
19:48 lineman60 I am writing my first complex sls file and it's not working
19:48 ubercore I've used it on 13.04, so I'm pretty sure it's there
19:48 lineman60 i was trying to run it off the server
19:48 lineman60 master*
19:48 lineman60 will try on minion
19:48 troyready joined #salt
19:49 ubercore salt-call is used to run locally on the minion
19:49 godber1 joined #salt
19:49 ubercore I don't know if it would be installed as part of a master-only install
19:50 godber1 joined #salt
19:50 lineman60 it's not
19:50 lineman60 aperntlay
19:50 lineman60 apperntly
19:50 godber1 left #salt
19:51 srage joined #salt
19:56 pdayton joined #salt
19:58 xet7 joined #salt
19:58 berto- joined #salt
20:02 pipps joined #salt
20:03 dray3 joined #salt
20:06 dray31 joined #salt
20:06 TheCodeAssassin2 joined #salt
20:09 dray3 joined #salt
20:10 LarsN Quote from a co-worker "Wow.....Salt Stack is pretty powerful"
20:10 LarsN :)
20:10 backjlack joined #salt
20:10 forrest LarsN, awww yea!
20:11 UtahDave :)  love it, LarsN!
20:12 dray3 joined #salt
20:15 forrest LarsN, are you guys building your states with mappings and such?
20:15 forrest If not, you should show your co-worker that, it's REALLY cool
20:15 LarsN we should be, but we're not yet.
20:15 forrest gotcha
20:15 forrest single distro environment?
20:15 dray3 joined #salt
20:15 adepasquale joined #salt
20:15 UtahDave forrest: HUGE cloud environment.  :)
20:16 forrest Ahh
20:16 LarsN We're currently using it in smaller segments of that environment, but....
20:16 forrest Racker?
20:16 LarsN not a Racker.
20:16 forrest oh I see HP
20:16 LarsN :)
20:16 forrest internet ftw
20:16 forrest Woah woah woah, NetOps? I don't know if you're allowed in here...
20:17 LarsN I work with a bunch of former rackers.
20:17 LarsN I haven't updated my linked in
20:17 LarsN I'm afraid of what will happen to my inbox.
20:17 LarsN I work for the Operations Automation team now....  ;)
20:17 forrest niiiiiiice
20:17 LarsN because...  "DevOps @ HP Cloud"
20:17 LarsN plus linked in....
20:17 LarsN *shudder*
20:18 redondos joined #salt
20:18 forrest You should try to hit a devopsdays thing if you can, it's a breath of fresh air to not have to explain how devops isn't a tool to exploit, but a mentality, lol.
20:19 LarsN forrest: I'm going to need to start looking for those.
20:19 forrest http://devopsdays.org/
20:19 LarsN there had been one in Austin last year I believe.
20:19 forrest yea
20:19 LarsN hopefully they'll come back.
20:19 mwillhite joined #salt
20:20 LarsN My co-worker Amos is doing an intro to salt for Lopsa-Austin on the 28th
20:20 forrest I hope so as well, the events are really cool, open spaces are an aewsome idea.
20:20 forrest nice!
20:20 LarsN I was supposed to be doing it, but I'm flying out to Fort Collins sunday, returning on Nov. 2
20:21 forrest sunday to saturday? Ouch
20:21 LarsN I just set up Vagrant-KVM with a bootstrap.sh that installs docker
20:21 dray3 joined #salt
20:21 LarsN two weeks, sunday-sat
20:21 LarsN and part of that is I'm flying into Denver, and have to drive an hour and a half to get to the Ft. Collins office.
20:21 pdayton left #salt
20:21 LarsN <--- not a morning person ;)
20:21 jslatts joined #salt
20:21 forrest Neither am I :\
20:21 jefimenko /join #twisted
20:22 qba73 joined #salt
20:22 * LarsN wonders why he should /join #twisted
20:23 dranger joined #salt
20:25 forrest the weather should be really nice in ft. collins at least
20:25 defunctzombie are there any good docs/examples of creating roles?
20:26 defunctzombie like I want to assign ips to specific names and then put names in "categories" or "roles"
20:26 forrest system roles defunctzombie?
20:26 defunctzombie whatever it might be called
20:26 defunctzombie if by system you mean, "web" "db" "web-different" then yea
20:26 defunctzombie higher level organization roles if that makes sense
20:27 defunctzombie I can't quite get the grasp of how it is suppose to happen or look like in the salt config files
20:27 forrest defunctzombie, so you could use node groups: http://docs.saltstack.com/topics/targeting/nodegroups.html
20:27 forrest Or simply base that data off globbing in the top.sls http://docs.saltstack.com/ref/states/top.html
20:28 forrest This is a good example of using grains: http://docs.saltstack.com/ref/states/top.html#other-ways-of-targeting-minions
20:28 defunctzombie forrest: ah.. ok…
20:28 forrest Also check out http://docs.saltstack.com/ref/states/top.html#how-top-files-are-compiled
20:28 adepasquale left #salt
20:28 forrest I've gotta run to a meeting, I'll be back in a bit
20:28 defunctzombie forrest: thanks for the groups info
20:28 defunctzombie that should get me where I need
20:29 cron0 joined #salt
20:30 LarsN wonder if I can fit two weeks of clothes, and my laptop into my timbuk2 messenger :)
20:30 vimalloc joined #salt
20:31 abe_music joined #salt
20:34 dray3 joined #salt
20:36 EugeneKay Probably. But will that fit into the overhead?
20:38 dray3 joined #salt
20:38 amckinley joined #salt
20:39 ajw0100 anyone know a thing or two about gitfs? I have no problem using https://github.com/ajw0100/dev_vm_saltfs as a state tree when cloned locally. When I try to enable git as a fileserver_backend and add the repo as a gitfs_remote I get "Data failed to compile". https://gist.github.com/ajw0100/7044464
20:40 dray3 joined #salt
20:41 socks__ joined #salt
20:41 dray3 joined #salt
20:42 pdayton joined #salt
20:43 pentabular joined #salt
20:44 berto- joined #salt
20:45 ipmb joined #salt
20:45 dray31 joined #salt
20:46 socks__ hi, could someone explain to me the difference between  "module.get('...')"  and regular ol' "module['...']" operations?   eg pillar.get('some_var')  vs pillar['some_var'].  i understand that get ops enables you to specify a default if it isn't already defined.  but are there  reasons to use one verses the other?
20:49 dray3 joined #salt
20:49 redondos joined #salt
20:50 m0hit joined #salt
20:52 dray3 joined #salt
20:52 rawzone joined #salt
20:52 ajw0100 socks__ another benefit is it's easier to specify nested dicts using the : delimiter
20:53 cwright ajw0100: not with pillar['some_var'], only with salt['pillar.get']('some_var')
20:54 cwright in both pillar[] and pillar.get() the pillar object is a dictionary
20:54 ubercore pillar['key']|default('my default') also works, thanks to jinja
20:56 forrest LarsN, I think it depends if you want to waste water or not, if so, then you could just pack two-three pairs of everything, and do laundry a few times
20:57 forrest or, you could flat rate ship your clean clothes to the office, then flat rate ship them back once you were done
20:57 jesusaurus i prefer .get() because i tend to have multiple levels in my data structure
20:57 ajw0100 cwright i was referring to pillar.get not pillar['some_var']
20:57 jesusaurus and i think that pillar[foo][bar]|default('foobar') barfs if pillar[foo] doesnt exist
20:58 dray3 joined #salt
21:00 dray3 joined #salt
21:02 berto- joined #salt
21:03 socks__ thanks all
21:03 gildegoma joined #salt
21:05 ajw0100 cachedou_ hey did you get a chance to look further into using gitfs with a masterless minion?
21:06 forrest ajw0100, I think cachedout is the actual user.
21:06 forrest unless he disconnected and reconnected.
21:06 cachedout Sorry, that's an IRC client connected on a machine at home.
21:07 ajw0100 np
21:07 dray3 joined #salt
21:08 cachedout ajw0100: I just asked Tom about that. He said that we don't currently have that functionality right now but that he would certainly like to build it in at some point.
21:10 rgbkrk joined #salt
21:12 EugeneKay cachedout - ZNC ftw ;-)
21:13 cachedout Heh. Yeah.
21:13 ajw0100 cachedout Cool. I'll keep an eye out for it. Based on the docs I figured it wasn't possible at the moment so I just set up a master on the machine. Still having trouble with gitfs though.
21:13 cachedout ajw0100: Go ahead and toss your current gitfs troubles in here and we'll take a swing at 'em
21:14 rgbkrk ajw0100 - Just joined -- what issues are you having with gitfs?
21:15 ajw0100 Well it seems super easy to set up based on the docs so I must be doing something wrong. But anyways I have no problem using https://github.com/ajw0100/dev_vm_saltfs as a state tree when I clone it locally to /srv/salt. When I try to enable git as a fileserver_backend and add the repo as a gitfs_remote I get "Data failed to compile". https://gist.github.com/ajw0100/7044464
21:16 ajw0100 I've found a few notes online about that error basically meaning my YAML is incorrect but I can't spot it.
21:17 amckinley joined #salt
21:18 Lue_4911 joined #salt
21:19 hjubal joined #salt
21:20 lineman60__ joined #salt
21:21 rgbkrk I've had issues in the past (ahem in the last week)
21:21 rgbkrk Where I needed to make sure the right version of gitpython was installed
21:21 rgbkrk As well as git itself
21:21 rgbkrk Otherwise it kind of failed silently or awkwardly
21:22 rgbkrk Do you pip install gitpython?
21:22 forrest the version of gitpython has been an issue for a loooong while rgbkrk.
21:22 forrest I still don't get how old releases get installed sometimes
21:23 rgbkrk I'm new, so my "in the past" means in the last couple weeks
21:23 forrest ajw0100, once you've confirmed the git python version, if that isn't the problem, could you please run the comand again with -l debug?
21:23 forrest rgbkrk, gotcha
21:23 forrest I just meant it was a unique problem, happens to tons of people it seems :)
21:23 ajw0100 yea I found out about gitpython by running salt-master -l debug. the salt-master wasn't starting but once i added gitpython it was fine. this "Data failed to compile" error comes up when I run salt '*' state.highstate test=true
21:23 forrest err wasn't*
21:24 forrest can you do run salt '*' state.highstate -l debug test=true?
21:24 ajw0100 sure hold on
21:24 rgbkrk For Rackspace's SaltStack deployment, I made an explicit pip install gitpython==0.3.2.RC1
21:24 forrest hah nice
21:25 c0bra joined #salt
21:26 mgw1 joined #salt
21:27 rgbkrk I just added your repo as my gitfs_remote to /etc/salt/master on a working master, ran `service salt-master restart`, and ran `salt 'qa01*' state.highstate`.
21:27 rgbkrk Waiting on it to come back with something
21:28 rgbkrk - ajw0100
21:28 dranger joined #salt
21:28 dray3 joined #salt
21:28 rgbkrk Success!
21:29 defunctzombie I have put a top.sls into /srv/salt/base/
21:29 rgbkrk All 13 steps were succesfful.
21:29 rgbkrk *successful
21:29 defunctzombie but when I run state.highstate I get: "No Top file or external nodes data matches found"
21:30 defunctzombie salt -N www state.highstate (is what I run)
21:30 defunctzombie and the www nodegroup is setup
21:30 rgbkrk Your top.sls should be in /srv/salt
21:30 ajw0100 rgbkrk nice. now if i could just get the same result haha
21:30 forrest beat me to it rgbkrk
21:30 ajw0100 i just added the results of sudo salt '*' state.highstate -l debug test=true to the gist
21:30 rgbkrk Unless you have your base set differently
21:30 ajw0100 https://gist.github.com/ajw0100/7044464
21:30 forrest defunctzombie, you're treating the location of the top file, like the file_roots: section of the config perhaps?
21:30 rgbkrk Don't worry forrest, I'll be heading out to get food with my family shorly
21:30 forrest :( I wish I was leaving work shortly
21:30 defunctzombie forrest: I think so
21:31 defunctzombie forrest: did did setup a base file_roots in config
21:31 forrest the file_roots value is where your file lives, your top is an overarching item.
21:31 rgbkrk ajw0100 - Do you mean to have both fileserver_backends?
21:31 forrest so for dev, you have /srv/salt/dev, and then you might have /srv/salt/dev/apache
21:32 forrest your top file itself doesn't go into those subdirectories unless you've modified the default location like rgbkrk was saying.
21:32 defunctzombie gotcha
21:32 defunctzombie ok… but I would put other sls files in those locations?
21:32 forrest yes
21:32 defunctzombie k
21:32 rgbkrk ajw0100 - Can you do me a favor and restart your salt-master?
21:32 ajw0100 rgbkrk it's not necessary but I've tried it with only git as a fileserver_backend and i still get the same result
21:32 rgbkrk service salt-master stop
21:32 ajw0100 rgbkrk sure
21:32 rgbkrk service salt-master start
21:32 defunctzombie ok.. yes putting the top file back to /srv/salt does change the error
21:32 rgbkrk (instead of restart, just to be sure)
21:32 forrest cool
21:32 defunctzombie to "no states found for this minion"
21:33 defunctzombie which is progress :)
21:33 forrest yea,
21:33 forrest If you look at the error (try adding the -l debug option) and still can't figure it out, paste your top.sls onto pastebin or whatever and we can try to help out
21:33 ajw0100 rgbkrk same result
21:33 rgbkrk :(
21:33 rgbkrk salt --version ?
21:34 ajw0100 salt 0.17.0
21:34 rgbkrk I find it crazy I was able to deploy yours
21:34 rgbkrk Oh
21:34 rgbkrk I'm on the dev branch
21:34 abe_music joined #salt
21:34 forrest the dev branch and 0.17 shouldn't be that far out though, unless you know of an error relating to git_fs that was resolved on dev?
21:34 ajw0100 if it helps, the way i'm setting this machine up is by having a masterless minions salt the machine with a master. which kind of makes my head hurt haha
21:34 rgbkrk I've been bootstrapping using the -- git develop
21:35 rgbkrk Oh ha
21:35 forrest ajw0100, you have gitpython installed on the machine you plan to put the master on right?
21:35 forrest not just the masterless minion?
21:36 rgbkrk Good point. It's the master that needs it.
21:36 rgbkrk Along with installing git
21:36 rgbkrk The only issue that develop addressed was the conflicting IDs problem http://stackoverflow.com/questions/19327272/what-order-do-states-in-top-sls-get-executed
21:36 rgbkrk *The only issue I faced
21:37 rgbkrk Made me feel dumb, but I didn't know those had to be unique
21:37 forrest yea we were talking about that earlier rgbkrk
21:37 rgbkrk Alright, over and out for me. Catch you all later.
21:37 forrest but that was the conflict with items, not issues with the state itself
21:37 forrest later
21:38 defunctzombie forrest: http://pastebin.com/Q92sqAxt
21:38 defunctzombie that is the top.sls
21:38 ajw0100 i'm basically just using this formula to set the machine up with a master https://github.com/saltstack-formulas/salt-formula. but I've changed the master.sls to require gitpython.sls. i've included both of those in the gist: https://gist.github.com/ajw0100/7044464
21:38 defunctzombie and I have a www.sls in /srv/salt/base/
21:38 defunctzombie which based on my limited understanding is that it should be finding that
21:38 forrest your server is just named www?
21:39 defunctzombie forrest: I have a www nodegroup configured
21:39 ajw0100 I only have one vm that I'm setting up. so I'm basically firing it up as a masterless minion that salts itself into a machine with a master and a minion
21:40 ajw0100 the only reason i want a master to begin with on this lone vm is to use gitfs haha
21:41 forrest wait so you're trying to salt a master onto a masterless minion when they're both the same machine?
21:41 forrest Why don't you just bootstrap a master, then install git/gitpython?
21:41 forrest defunctzombie, gotcha. Ok let's start here then, try salt -N www test.ping
21:41 forrest does that return anything?
21:42 defunctzombie forrest: yea, ive done that one returns true for both (I have two machines in the group)
21:42 forrest ok cool,
21:43 ajw0100 forrest haha i told you it made my head hurt. that sounds like a much better approach
21:43 forrest ajw0100, Yea I would do that instead, you could always bootstrap, then have a state that installs git/gitfs, and just ensure it gets executed first.
21:44 forrest I don't have a solution to the problem you're currently encountering though, I've never tried to salt the same machine with a master from a masterless minion, lol
21:44 hjubal joined #salt
21:44 forrest ok, defunctzombie, can you try salt -N state.highstate?
21:45 forrest sorry salt -N www state.highstate
21:45 forrest brain is not working this afternoon
21:45 troyready joined #salt
21:45 defunctzombie forrest: yea, it errors out with "No states found for this minion" for each minion
21:45 ajw0100 forrest haha yea I'll try that approach out. originally I wasn't planning on having a master at all since it's just one machine. but when i wanted to use gitfs i found out i needed a master. should have taken a step back at that point.
21:46 forrest ok cool, so let's try this now, salt 'name_of_minion_in_www_group' state.highstate, what does that return?
21:46 forrest ajw0100, ahh I gotcha, yea I'd just bootstrap the master, and drop git/gitfs on, way easier :P
21:46 ajw0100 forrest cool thanks.
21:46 forrest yup yup
21:46 forrest That's why they pay me those big IRC dollars
21:47 defunctzombie forrest: No minions matched the target. No command was sent, no jid was assigned.
21:47 ajw0100 haha
21:47 defunctzombie forrest: oh sorry
21:47 forrest defuntzombie, you joined the minions to the master right?
21:47 defunctzombie forrest: same No state error than before
21:47 forrest *defunctzombie
21:47 defunctzombie forrest: I mistyped
21:47 forrest oh ok
21:47 defunctzombie the minions are connected because I can run commands on them manually
21:48 forrest right duh we tested that already, fridays man...
21:48 berto- joined #salt
21:49 forrest So let's try this now, salt 'name_of_minion_in_www_group' state.sls www, what does that return?
21:49 Lue_4911 joined #salt
21:50 defunctzombie it ran, total of 0
21:50 forrest what's in www.sls?
21:50 Lue_4911 joined #salt
21:50 defunctzombie a git repo clone
21:50 defunctzombie is there something simpler I can put in it?
21:51 defunctzombie to just test?
21:51 defunctzombie and www.sls in in /srv/salt/base/ btw
21:51 forrest yea it/s just /srv/salt/base/www.sls right?
21:52 defunctzombie yep
21:53 forrest and you set the base as a file_root in your master.conf?
21:53 defunctzombie forrest: forrest ok.. so one issue was I had no restarted the salt-master after updating it
21:53 forrest ahh ok
21:53 defunctzombie forrest: and yes, I have base
21:54 forrest ok cool, so it should pick up that file in the base then, are you still getting an error?
21:55 defunctzombie yes and no
21:55 defunctzombie I can do state.sls manually
21:55 defunctzombie but I can't to state.highstate
21:55 defunctzombie when I do -N www that is
21:56 defunctzombie ok.. I fixed that too
21:56 defunctzombie top.sls does need to be in /srv/salt/base
21:56 defunctzombie so this is progress
21:57 defunctzombie but it still doesn't detect that the www group needs the www state
21:57 defunctzombie but at least the core state is applied
21:57 defunctzombie probably because of the '*'
21:57 forrest right
21:58 forrest oh I think we're being dumb here
21:58 forrest change line 5
21:58 forrest http://pastebin.com/Q92sqAxt
21:58 forrest to be - match: nodegroup
21:59 defunctzombie forrest: hm… I tried that.. same
21:59 defunctzombie only core state seems to be detected
21:59 forrest and the base thing makes sense since you modified the base location, if you had added another location (such as /srv/salt/dev) then the top file could live in /srv/salt/
21:59 forrest really? That's odd.
21:59 jumperswitch_ joined #salt
21:59 forrest take out... 'www' and do www ?
22:00 forrest for line 4, the example doesn't have the group in quotes
22:00 defunctzombie forrest: yep, tried that too
22:01 forrest huh
22:03 forrest can you run it with -l debug defunctzombie? Maybe we'll get something more
22:03 forrest right now I'm stumped
22:03 forrest I'm sure it's simple
22:03 forrest but I'm not seeing it for some reaosn
22:06 jumperswitch_ joined #salt
22:06 defunctzombie forrest: I am sure it is simple too
22:06 defunctzombie just need to find it
22:07 forrest yea
22:11 aboe joined #salt
22:13 defunctzombie does salt run automatically on the minion boxes or do I have to trigger it?
22:13 jacksontj joined #salt
22:14 kermit joined #salt
22:14 defunctzombie forrest: figured it out
22:15 defunctzombie the '*' in base was intercepting the www that followed it
22:15 defunctzombie the box is only matched once
22:15 defunctzombie not stacked like I thought
22:17 forrest Really?
22:17 aboe cedwards, are you there?
22:17 forrest I didn't know that, it makes sense though that it would match that first, very cool defunctzombie, thanks for letting me know!
22:18 jumperswitch__ joined #salt
22:19 forrest defunctzombie, I emailed myself to try and remember to write a documentation note on that.
22:20 jumperswitch_ joined #salt
22:25 forrest defunctzombie, did you just swap the www nodegroup matcher, and the '*' item in top.sls, and it worked?
22:25 defunctzombie forrest: I moved - core into www
22:25 defunctzombie and removed the '*' for now
22:25 defunctzombie but yea, I think swapping would be good too
22:26 forrest I just don't get it
22:26 forrest there is an example on the top file page, that has it matching '*' to get global, then groups below that to apply
22:26 forrest so how you were doing it SHOULD work :\
22:26 forrest there's gotta be something else we're missing.
22:26 forrest something about how the group is being matched or something
22:27 forrest what does your nodegroups section look like in the master.conf?
22:27 sarnold joined #salt
22:28 sarnold CVE-2013-4438 appears to be listed twice in http://docs.saltstack.com/topics/releases/0.17.1.html
22:28 sarnold but CVE-2013-4437 isn't listed at all in that same URL
22:28 redondos joined #salt
22:29 jbunting joined #salt
22:36 cshuman joined #salt
22:39 UtahDave sarnold: does it appear that the repeated CVE number should be replaced with CVE*4437?
22:39 defunctzombie any good guides on creating a service with salt?
22:39 Jahkeup joined #salt
22:40 defunctzombie forrest: www: 'L@www1,www2'
22:40 sarnold UtahDave: probably
22:41 sarnold UtahDave: if you've got write access to the thing, this posting might be useful: http://www.openwall.com/lists/oss-security/2013/10/18/3
22:41 sarnold but those five-word descriptions leave a little to be desired :)
22:43 jbunting joined #salt
22:45 rgbkrk joined #salt
22:47 UtahDave Yeah, these have all been dealt with in 0.17.1
22:49 mwillhite joined #salt
22:51 defunctzombie forrest: I think it may be a bug
22:51 forrest is there already an issue filed?
22:51 defunctzombie forrest: cause I would also expect it to work by merging the two
22:51 defunctzombie since both "match"
22:51 forrest yea
22:51 forrest I'm gonna head home defunctzombie, I will probably be back on later tonight, let me know if you figure it out
22:57 cshuman joined #salt
23:00 seanz Is there a way to capture highstate output with the ansi color codes in place? I only see a way to disable colors.
23:00 rgbkrk When using environments, can you only set up states?
23:00 pentabular joined #salt
23:00 rgbkrk Are you able to set things in pillar?
23:04 Thiggy joined #salt
23:05 xmltok joined #salt
23:07 fllr joined #salt
23:08 fllr Hey guys. Salt is changing the ownership of files to root. I tried running salt-call without sudo, but then it won't run. What can I do to avoid that?
23:09 Corey fllr: Which files?
23:10 fllr Corey: well, for example, I asked salt to create a user for me, and add a home folder for the user. the home folder, and all files I uploaded there using file.managed, they're all owned by root
23:11 Corey That's default unless you stipulate otherwise.
23:11 cachedout You want the user argument for file.managed
23:13 fllr What about the home folder?
23:15 rgbkrk Does anyone here use gitfs along with several branches?
23:15 rgbkrk I'd love to see some good sample code that I can learn from.
23:15 rgbkrk The examples aren't giving me enough.
23:16 fllr Corey: cachedout: The home folder I created with the user state: http://docs.saltstack.com/ref/states/all/salt.states.user.html#module-salt.states.user
23:17 m0hit joined #salt
23:18 m0hit_ joined #salt
23:19 sarnold left #salt
23:21 Gareth rgbkrk: Look at the Salt States repo in github.
23:22 Gareth rgbkrk: https://github.com/saltstack/salt-states
23:22 rgbkrk I'm looking that one, but it only has one usage of pillar and no branches.
23:23 vespakoen joined #salt
23:24 kula rgbkrk: i'm using gitfs with two branches currently. master only contains top.sls, and i have a production branch. but i'm still not doing much complicated with it.
23:24 rgbkrk kula - Do you have anything in a public repo?
23:25 kula no, i don't. i don't have much in that project right now anyways.
23:26 kula i'm just starting out with salt for that gig. my other use of salt is still the conventional fileserver backend with my hacked together git usage
23:27 rgbkrk Oh ok, thanks jula
23:27 rgbkrk Also, thanks Gareth
23:27 rgbkrk *kula
23:28 kula but the mapping of git branches to environments works well for me.
23:28 rgbkrk I may be trying to pigeonhole this inappropriately'
23:28 kula and git pillar also works well for me, ince you get to the git pillar in 0.17
23:28 kula what are you trying to do?
23:28 rgbkrk What I'm hoping to do is setup qa servers that can deploy particular branches, etc. of a git repo
23:29 rgbkrk All the setup is the same across prod and qa
23:29 rgbkrk Just need the ability to configure where I pull from a bit more easily.
23:29 rgbkrk https://github.com/rgbkrk/salt-nbviewer is the repo
23:30 kula that should work with the git fileserver. have a prod branch, a qa branch, and those become the prod and qa environments.
23:30 rgbkrk Only two lines change in nbviewer/init.sls
23:30 rgbkrk https://github.com/rgbkrk/salt-nbviewer/blob/master/nbviewer/init.sls#L16-L17
23:30 rgbkrk Yeah, so I have the prod branch and qa branch now.
23:31 rgbkrk All you can do is set which states run right?
23:31 kula yeah, that's what top.sls sets for you, which states are ran for which matches
23:32 rgbkrk Guess I was hoping I could set up some pillar settings based on environment too
23:33 rgbkrk Perhaps I need to wrap my head around the fact that I won't be using the salt states like a typical repo.
23:33 rgbkrk It's more like having a parallel file system
23:35 DredTiger joined #salt
23:35 kula you can set up pillar settings based on environment, it's just that the environment is the one defined in the pillar top.sls file
23:35 rgbkrk Just awkward amongst a file that's slightly different. Guess I need to figure out a better way to break this up.
23:35 rgbkrk The pillar top.sls
23:36 rgbkrk Just now looking at that...
23:36 rgbkrk That won't be backed by gitfs though right?
23:36 backjlack joined #salt
23:36 rgbkrk I feel like I need another repo that contains my pillar top.sls, /etc/salt/master, etc.
23:36 kula you can use the git external_pillar
23:36 rgbkrk When bootstrapping a master
23:36 rgbkrk ah-wha?!
23:37 rgbkrk Checking that out now
23:37 jacksontj joined #salt
23:37 kula it works kinda like the gitfs backend, just ... broken in special ways in my opinion.
23:37 rgbkrk lol
23:37 druonysus joined #salt
23:37 kula you definitely want the version from 0.17 or later, though.
23:37 rgbkrk Yeah, I'm on the dev branch right now
23:38 rgbkrk Fine with risky for the moment while learning and tinkering with this.
23:38 cshuman joined #salt
23:38 kula i haven't quite figured out how you configure the pillar_git backend to do different pillar environments, although i really don't use different pillar environments much. although i can see use for them in the future.
23:39 kula i've stared at that code way too much recently.
23:40 kula but yeah, with the gitfs backend, the pillar_git backend, and stashing /etc/salt/master somewhere, i've got a pretty good bootstrap a master plan going.
23:40 rgbkrk What I'm hoping to set up is an *easy* way for us to go from pull request to deploy to qa in automation
23:40 rgbkrk (first kick off manually so we're not deploying a malicious server)
23:42 rgbkrk Creating the bootstrap now
23:43 linjan joined #salt
23:43 kula i do have to say that there's this interesting effort curve with salt: i spent 20 solid hours a couple weeks ago to get a kickstart+salt (salty kick? kicksalted?) blade VM host set up. the second time i used it it was about 10 minutes of effort during a boring meeting i was sitting in....
23:43 alunduil joined #salt
23:44 rgbkrk lol
23:45 rgbkrk I feel like I keep trying to twist salt into the wrong thing
23:45 rgbkrk My initial deploys are much faster now with my fabric script (shhh… don't tell anyone I'm not using salt-cloud yet)
23:45 kula i'm rather proud of 'kicksalted', btw
23:45 rgbkrk (https://gist.github.com/rgbkrk/7008699)
23:46 rgbkrk kicksalted
23:46 cshuman joined #salt
23:46 kula eh, whatever works. if fabric does some chunk for you, use it.
23:47 rgbkrk Just kickstart+salt bootstrap?
23:47 rgbkrk Yeah, it was just easy to throw that together when tearing machines up and down
23:48 rgbkrk The weird part to me about salt-cloud was that I need a master set up already to deploy my infra.
23:48 kula yes. all of my systems (well, the ones i secretly really care about) are centos, so i can use a kickstart file to deploy a system with salt on it, and after it boots for the first time i run salt on it.
23:49 kula the key point being i've got git tracking for *everything* to build a system.
23:50 pentabular joined #salt

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