Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-12-24

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

All times shown according to UTC.

Time Nick Message
00:00 UtahDave defunctzombie: you're welcome
00:00 bhosmer joined #salt
00:00 UtahDave jfzhu_us: You're in luck!  Salt provides most of that for you!
00:02 jfzhu_us UtahDave: I haven't been very clear on what utilities I would use in salt to accomplish some of those things. For example, I would want to log a case where I am unable to configure a user because they don't have a home directory but the only options I have seen are to log to a third party utility such as syslog
00:02 UtahDave You're going to want to set up your sls files like this for your vimrc  http://docs.saltstack.com/topics/tutorials/walkthrough.html#the-first-sls-formula
00:03 UtahDave You can use jinja to loop over the users you have in pillar to apply your states
00:03 elfixit joined #salt
00:03 N-Mi joined #salt
00:03 UtahDave jfzhu_us: if you run a state that has a failure, it will be recorded in the job return
00:05 anitak joined #salt
00:05 jfzhu_us UtahDave: Ah okay. I am thinking about it the wrong way. Instead of relying on myself to write the code to log/check for those error situations, I should just salt evaluation engine tell me that.
00:05 UtahDave Yes, exactly.
00:06 jfzhu_us No wonder this has been so hard...
00:07 quickdry21 joined #salt
00:07 UtahDave jfzhu_us: Yeah.  Technically, you can do what you're trying to do, but Salt is designed to handle most of those issues for you.
00:11 ajw0100 joined #salt
00:12 jfzhu_us UtahDave: I am so much more used to programming in declarative languages that I am confounded when I have to write something in something that isn't declarative like salt's state files are. It seems to me that salt follows the K.I.S.S. principal so I will stick to that and see how far that gets me.
00:17 UtahDave jfzhu_us: Actually, salt's state files ARE declarative.
00:18 eculver joined #salt
00:23 defunctzombie can I force a particular action in a statefile to run?
00:25 jfzhu_us UtahDave: That's confusing. Salt state files seem to say this is how I want the system to be rather than this is what I want the system to do
00:26 N-Mi joined #salt
00:27 UtahDave defunctzombie: No, you'd need to split it out into its own state file
00:28 defunctzombie gotcha
00:28 defunctzombie and if it is its own state file but contains stuff like waiting for a git version to change.. no way to force the deps of that to run?
00:29 UtahDave jfzhu_us: Yes, you "declare" what you want the state of your server to be.  That's what "declarative" means.  "Imperative" means "do this", then "do that".
00:30 UtahDave defunctzombie: you have to run   "state.sls  myslsfile"
00:30 kermit joined #salt
00:32 sfvivek1 reposting this - would be great if I can get some help with my issue
00:32 jfzhu_us UtahDave: You are correct. I have made a mistake in my understanding in the differences between the two styles.
00:33 sfvivek1 quick quesiton on the salt config.  we have a setup where salt master is configured to run as root, but the minion running on a different host is configured to run as non-root (let's say vivek) user.  when we invoke commands to the minion for example - salt 'minion.hostname' cmd.run 'id' the output is different from what we actually see by running 'id' on the minion host itself.
00:33 sfvivek1 I believe what was happening is when we invoke from the salt-master, it's running su vivek -c 'id' and returning the output to the master, where as it should run su - vivek -c 'id'
00:33 sfvivek1 is that the expected behavior?
00:33 bhosmer joined #salt
00:34 UtahDave sfvivek1: That might be the case.
00:35 sfvivek1 thanks @UtahDave
00:35 anitak joined #salt
00:36 sfvivek1 can you suggest any fix for this?  the reason is the minion is picking up the nofile descriptors for root which is by default 1024 instead for my user which is set to 65536
00:51 jslatts joined #salt
01:06 anitak joined #salt
01:13 UtahDave sfvivek1: I'm not sure.  I don't know if that was a design decision, or if that's a bug.
01:25 logix812 joined #salt
01:26 cachedout joined #salt
01:32 sfvivek1 thanks or responding @UtahDave
01:32 sfvivek1 for*
01:36 UtahDave sure, sorry. I've been in meetings
01:43 N-Mi joined #salt
01:52 ajw0100 joined #salt
02:07 anitak joined #salt
02:17 elithrar joined #salt
02:24 gazarsgo joined #salt
02:30 jmpdev joined #salt
02:31 jmpdev what is the preferred way to install salt-cloud now that it's incorporated into salt?
02:38 jmpdev ahh nevermind i see it's only in the dev branch
02:40 xl1 joined #salt
02:47 favadi joined #salt
02:48 anuvrat joined #salt
02:49 jmpdev left #salt
03:04 BenCoinanke joined #salt
03:08 anitak joined #salt
03:11 mgw joined #salt
03:16 ravibhure joined #salt
03:20 ravibhure1 joined #salt
03:22 quickdry21 joined #salt
03:28 N-Mi joined #salt
03:31 anitak joined #salt
03:31 ckao joined #salt
03:40 psyl0n joined #salt
03:45 ajw0100 joined #salt
04:13 BenCoinanke joined #salt
04:13 Chad joined #salt
04:15 Chad am I correct that my error is because of the cmd.run   ?   http://pastebin.com/VWV40Jcm
04:16 forresta Chad, yep
04:16 forresta you can't do "echo "
04:17 forresta it considers that the end of the string
04:17 forresta and messes things up
04:17 Chad oha
04:17 forresta try just "echo /etc/init.d/whateverelse"
04:17 forresta in the name section
04:19 Chad like this http://pastebin.com/bXSN4WcX >
04:19 Chad ?
04:19 forresta no
04:20 forresta https://gist.github.com/gravyboat/8108741
04:20 forresta but if you are gonna do that, I'd suggest something like this
04:21 forresta frefresh that gist
04:21 forresta it screwed up the formatting
04:21 forresta but you don't have to have the ID be the command if you're gonna use the name option
04:21 forresta so you could name it something that makes more sense to you
04:21 jslatts joined #salt
04:22 forresta Pretty sure you don't even need the quotes around the command
04:23 forresta for the name and unless section
04:23 forresta I added a second comment on that gist
04:24 forresta does that make more sense Chad?
04:24 Chad taking a look
04:25 Chad trying to take it all in
04:25 forresta ok
04:25 forresta I think you're overcomplicating it, did you look at the cmd.run docs?
04:27 Chad I was looking over   http://bencane.com/2013/09/23/remote-command-execution-with-saltstack/  and http://intothesaltmine.org/blog/html/2013/03/01/using_the_cmd_module_in_salt_states.html
04:27 Chad I am trying your example but it is still erroring out
04:28 forresta what's the error now?
04:28 Chad http://pastebin.com/ignPUfTJ
04:29 forresta can you paste what your state looks like now please?
04:30 Chad http://pastebin.com/iTNKTBCk
04:30 forresta oh sorry, cmd.run somehow dropped the :
04:31 forresta and those need to be indented properly
04:31 forresta commenting on my gist broke it :(
04:31 forresta does that make sense where the error is
04:31 forresta *?
04:33 ajw0100 joined #salt
04:33 Chad yes I found the missing :  after cmd.run:
04:33 Chad it ran better this ime
04:33 forresta cool
04:34 forresta and you don't have to use an ID like I did, you can put the command in there if you want, just depends on you.
04:34 jfzhu_us joined #salt
04:38 Chad either are nice
04:38 shennyg_ joined #salt
04:39 shennyg joined #salt
04:50 anuvrat joined #salt
04:50 techdragon joined #salt
04:55 sfvivek1 left #salt
05:04 fllr joined #salt
05:05 anuvrat joined #salt
05:06 fllr joined #salt
05:10 fllr joined #salt
05:11 thrashr888 joined #salt
05:14 sfvivek1 joined #salt
05:16 abc joined #salt
05:16 abcd joined #salt
05:23 defunctzombie I am trying to get packages to install on debian stable system from unstable repo
05:23 defunctzombie I added - fromrepo: unstable
05:23 defunctzombie but salt errors out with some apt error complaining about unstable not being a valid repo
05:23 defunctzombie I think I might need some require or something to update the repos before trying to install packages?
05:23 defunctzombie anyone run into such an issue?
05:26 cachedout joined #salt
05:36 forresta defunctzombie, did you make sure to add the unstable repo?
05:36 defunctzombie forresta: I added the unstable.list file to sources.d
05:36 defunctzombie but I think something isn't running apt-get update first
05:36 defunctzombie so it doesn't realize unstable is available or whatnot
05:37 defunctzombie oh damn.. just found the pkgrepo state
05:37 defunctzombie should probably use that!
05:38 forresta on your pkg.installed, did you set refresh to True?
05:41 defunctzombie nope, but I just added pkgrepo state instead of manually copying the file
05:41 defunctzombie I think that will fix it
05:41 forresta yea I think pkgrepo refreshes the database, but I can't remember.
05:42 defunctzombie yea, it seemed to
05:45 blarghmatey_ joined #salt
05:45 blarghmatey_ left #salt
06:00 mgw joined #salt
06:12 psyl0n joined #salt
06:17 ht left #salt
06:19 ht joined #salt
06:19 ht left #salt
06:22 aleszoulek joined #salt
06:26 crazysim joined #salt
06:39 vejdmn joined #salt
06:42 anuvrat joined #salt
06:49 xmltok joined #salt
06:52 jfzhu_us I ran list aliases and its returning its data in a weird format (http://pastebin.com/D6gSA4Hq). Notice the question mark at the top. I am not sure if it is bug or not or how to submit it if it is
06:55 crazysim joined #salt
07:00 pcurry_nomi joined #salt
07:02 aynik joined #salt
07:05 simonmcc_ joined #salt
07:05 cbloss joined #salt
07:05 sine_nitore joined #salt
07:16 quickdry21 joined #salt
07:20 mattmtl joined #salt
07:25 matanya joined #salt
07:26 Kraln joined #salt
07:28 cym3try joined #salt
07:28 anuvrat joined #salt
07:36 Shenril joined #salt
07:51 fllr joined #salt
07:53 _fllr_ joined #salt
08:05 fllr joined #salt
08:10 dangra joined #salt
08:32 Katafalkas joined #salt
08:42 giantlock_ joined #salt
09:05 fllr joined #salt
09:13 wonhunawks joined #salt
09:17 elithrar joined #salt
09:18 ajw0100 joined #salt
09:22 Shenril joined #salt
09:29 harobed joined #salt
09:31 simonmcc_ joined #salt
09:32 harobed joined #salt
09:44 techdragon joined #salt
10:05 fllr joined #salt
10:07 _fllr_ joined #salt
10:08 BenCoinanke joined #salt
11:05 fllr joined #salt
11:07 sine_nitore joined #salt
11:07 quickdry21 joined #salt
11:22 pkimber joined #salt
11:58 _ikke_ I've renamed a minion (changed the minion_id file), but along the new id, I still see key requests for the old id. Any clue where they come from? (I restarted the specific minion several times)
12:01 _ikke_ I see the requests in the logs for the master, but not where they come from
12:05 fllr joined #salt
12:10 bhosmer joined #salt
12:15 NV _ikke_: you might have to nuke the minions cached keys
12:16 NV (I assume you already deleted the key request with the old name from the master using salt-key)
12:16 dangra1 joined #salt
12:17 _ikke_ NV: OK, right
12:17 _ikke_ where are those keys cached?
12:17 NV err, /var/cache/salt/minion or something?
12:17 NV or /etc/salt/pki
12:17 NV can't recall
12:18 NV but something like that
12:18 _ikke_ the latter seems to only contain the ucrrent
12:42 pkimber joined #salt
12:46 joehh joined #salt
13:01 Shenril joined #salt
13:05 fllr joined #salt
13:05 ekristen joined #salt
13:06 ekristen so with salt you have to be logged into the master to do all the salt commands? or can I install salt on my local system and run salt commands that talk to the master and then to the minions?
13:17 bhosmer joined #salt
13:20 _ikke_ ekristen: the former
13:20 ekristen _ikke_: ok
13:21 ekristen _ikke_: just trying to get a handle on things ;)
13:23 _ikke_ ekristen: With syndic, you can have a master of masters
13:23 ekristen _ikke_: hrm, I’ll read up on it
13:30 Shenril joined #salt
13:34 gazarsgo joined #salt
13:35 wunki joined #salt
13:41 _ikke_ NV: Aparently there was still an old minion instance running
13:42 NV ah that'd do it!
13:42 pcurry_nomi joined #salt
13:43 _ikke_ I found out when I stopped the instance, an still saw key requests comming int
13:44 fllr joined #salt
13:46 _fllr_ joined #salt
13:49 EnTeQuAk joined #salt
13:51 elithrar joined #salt
13:55 simonmc| joined #salt
13:56 pcurry_nomi1 joined #salt
13:56 ange_ joined #salt
13:56 Anb_ joined #salt
13:56 Anb_ joined #salt
13:57 kiorky_ joined #salt
13:57 beardo_ joined #salt
13:58 jY- joined #salt
13:58 luminous_ joined #salt
13:58 tru_tru_ joined #salt
13:59 eskp_ joined #salt
13:59 bturner joined #salt
14:00 andyshin` joined #salt
14:00 scalability-junk joined #salt
14:00 pengunix joined #salt
14:01 oz_akan_ joined #salt
14:02 keekz_ joined #salt
14:03 oz_akan_ joined #salt
14:05 fllr joined #salt
14:06 ekristen anyone familiar with the salt-sandbox repo?
14:06 ekristen I’m getting some output I don’t think is normal, but I’m trying to learn the system
14:07 akitada joined #salt
14:07 benturner joined #salt
14:10 N-Mi joined #salt
14:10 majoh joined #salt
14:10 pkimber joined #salt
14:10 wunki joined #salt
14:10 giantlock_ joined #salt
14:10 lyska joined #salt
14:10 Chrisje joined #salt
14:10 xt joined #salt
14:10 MSeven joined #salt
14:10 faulkner joined #salt
14:10 g3cko joined #salt
14:13 EnTeQuAk joined #salt
14:17 luminous joined #salt
14:17 tru_tru joined #salt
14:23 MTecknology joined #salt
14:28 bastion2202 joined #salt
14:28 smccarthy joined #salt
14:37 TravisPaul joined #salt
14:40 mgw joined #salt
14:41 ravibhure joined #salt
14:41 bhosmer joined #salt
14:42 pengunix joined #salt
14:42 TravisPaul hey terminalmage just saw your message on github, I'll try to hang out on here today but will be in-and-out
14:50 TravisPaul Is there a recommended order for updating salt? Such as minions, then master or vice versa? Does it matter?
14:51 _ikke_ TravisPaul: What I've learned from here is that master should be at least the version of the minions
14:51 _ikke_ So, that would mean master first
14:51 TravisPaul _ikke_: Thanks, I'm glad you said that because I was thinking of doing it the other way around
14:54 toastedpenguin joined #salt
14:55 anuvrat joined #salt
14:55 dangra joined #salt
15:00 bastion2202 joined #salt
15:01 mattmtl joined #salt
15:05 fllr joined #salt
15:06 godog joined #salt
15:10 harobed_ joined #salt
15:15 pcurry_nomi joined #salt
15:18 bhosmer_ joined #salt
15:23 rojem joined #salt
15:24 mgw joined #salt
15:25 mgw joined #salt
15:27 forresta joined #salt
15:36 fllr joined #salt
15:43 rojem joined #salt
15:44 eclectic joined #salt
15:53 cyberbob joined #salt
15:54 cyberbob joined #salt
15:58 cyberbob joined #salt
15:59 cyberbob joined #salt
16:00 cyberbob joined #salt
16:02 cyberbob joined #salt
16:03 cyberbob joined #salt
16:04 cyberbob joined #salt
16:07 torrancew joined #salt
16:12 cyberbob joined #salt
16:14 cyberbob joined #salt
16:15 StDiluted joined #salt
16:16 rojem joined #salt
16:16 cyberbob joined #salt
16:16 rojem joined #salt
16:18 rojem joined #salt
16:19 diegows joined #salt
16:21 cyberbob joined #salt
16:25 cyberbob joined #salt
16:28 joehh joined #salt
16:28 pdayton joined #salt
16:28 jslatts joined #salt
16:28 cyberbob joined #salt
16:29 cyberbob joined #salt
16:30 cyberbob joined #salt
16:35 higgs001 joined #salt
16:36 Bosse joined #salt
16:38 cyberbob joined #salt
16:39 cyberbob joined #salt
16:40 cyberbob joined #salt
16:41 cyberbob joined #salt
16:41 danolj joined #salt
16:41 cyberbob joined #salt
16:42 cyberbob joined #salt
16:43 cyberbob joined #salt
16:45 cyberbob joined #salt
16:46 cyberbob joined #salt
16:46 cyberbob joined #salt
16:47 cyberbob joined #salt
16:47 opapo joined #salt
16:48 cyberbob joined #salt
16:48 cyberbob joined #salt
16:49 cyberbob joined #salt
16:50 cyberbob joined #salt
16:50 cyberbob joined #salt
16:51 cyberbob joined #salt
16:52 cyberbob joined #salt
16:52 cyberbob joined #salt
16:53 cyberbob joined #salt
16:53 cyberbob joined #salt
16:55 cyberbob joined #salt
16:55 cyberbob joined #salt
16:57 cyberbob joined #salt
16:58 cyberbob joined #salt
16:58 kolbe left #salt
16:58 cyberbob joined #salt
16:59 cyberbob joined #salt
17:00 cyberbob joined #salt
17:00 sfvivek1 joined #salt
17:00 cyberbob joined #salt
17:02 cyberbob joined #salt
17:02 sfvivek2 joined #salt
17:02 cyberbob joined #salt
17:03 cyberbob joined #salt
17:04 cyberbob joined #salt
17:05 cyberbob joined #salt
17:06 cyberbob joined #salt
17:06 bhosmer_ joined #salt
17:06 cyberbob joined #salt
17:07 cyberbob joined #salt
17:08 cyberbob joined #salt
17:09 cyberbob joined #salt
17:09 cyberbob joined #salt
17:10 cyberbob joined #salt
17:10 cyberbob joined #salt
17:11 cyberbob joined #salt
17:12 cyberbob joined #salt
17:12 cyberbob joined #salt
17:13 cyberbob joined #salt
17:14 cyberbob joined #salt
17:14 cyberbob joined #salt
17:15 cyberbob joined #salt
17:15 cyberbob joined #salt
17:16 cyberbob joined #salt
17:17 [M7] joined #salt
17:19 forresta cyberbob are you around?
17:19 pkimber Is it possible to view the pillar data for a server which hasn't yet been created?
17:20 forresta cyberbob, can you please turn off your reconnect, you're spamming pretty badly
17:20 forresta pkimber, not as far as I know.
17:20 forresta since you have to base pillar data off variables and such
17:20 pkimber Yes, I see.  OK, Thank you...
17:20 forresta np
17:34 thrashr888 joined #salt
17:36 thrashr888 joined #salt
17:47 Gifflen joined #salt
17:52 Katafalkas joined #salt
17:52 ravibhure joined #salt
17:58 berto- joined #salt
17:59 berto- It would be awesome for the release notes to have the release date.  http://docs.saltstack.com/topics/releases/0.17.4.html
18:02 pkimber joined #salt
18:06 harobed_ joined #salt
18:08 jalbretsen joined #salt
18:09 Gifflen joined #salt
18:17 pcurry_nomi joined #salt
18:27 forresta berto-, can you create an issue for that?
18:27 forresta or I can, doesn't really matter
18:27 matanya joined #salt
18:27 berto- forresta: of course, 1 sec.
18:27 forresta cool
18:27 forresta I don't know if the historical data will be available to go back to, but hopefully it can happen for more recent releases.
18:28 dangra joined #salt
18:28 forresta berto-, as a heads up https://github.com/saltstack/salt/issues/7526 has cropped back in 0.17.4, so if you have IDs that conflict, be careful
18:28 EugeneKay I'm sure `git tag` has the dates :-p
18:28 forresta EuguneKay, I don't know if those are the same as the release dates themselves though
18:28 [M7] joined #salt
18:28 EugeneKay Close enough for government work.
18:29 forresta psssh
18:29 berto- EugeneKay: I got the date from `git log v0.17.4`, from a user perspective i shouldn't have to dive in to dev tools to just get a release date.
18:29 EugeneKay I agree in full; I was speaking towards the "loss of historical data"
18:30 berto- forresta: I recall having issues with states that included others, for example if a state named `nginx` was included in more than one other state, that would blow up.  Is that #7526 ?
18:31 forresta pretty much
18:31 forresta if you included that one state, and also did nginx in your top, kablam
18:32 berto- forresta: ah, fffffff, ok, i can't use v0.17.4.
18:32 forresta yea figured I'd warn you, I know that it was discussed during yesterday's meeting and the guys are well aware of the issue
18:33 fllr joined #salt
18:33 berto- i don't want to sound overly critical here,  but every release breaks something.
18:34 forresta berto-, I know
18:34 forresta I've brought this up to UtahDave, and they know this is a major concern. cachedout has been working on a lot more integration testing style stuff lately. I believe one of the big things at the next sprint is going to be a focus on unit tests, but Tom needs to finish the 'how to write tests' documentation first.
18:37 forresta I actually proposed that the next sprint be ONLY unit tests, but I don't know if that will be the case since I believe it will be at saltconf
18:37 EugeneKay Features broken on <1.0.0 software? The horror!
18:38 forresta EugeneKay, it's the regression breaks that are bad
18:38 nahamu particularly regressions of previously identified bugs.
18:38 EugeneKay I agree. But it's not like this is production-ready; usage aside.
18:38 mgw joined #salt
18:39 forresta it's pretty production ready.
18:39 nahamu version numbers don't mean what they used to
18:39 nahamu also, bear in mind that post 0.17 they're moving to date-based version numbers.
18:39 forresta It's not as if this is only in small home grown shops, you've got legit companies using it. Most people just get annoyed (understandably), when a working feature they rely on is completey broken in the next release.
18:39 danolj anyone ever looked at saltstack? http://docs.saltstack.com/
18:39 danolj oops, wrong window, sorry guys & gals
18:40 forresta yes danolj, yes we have!
18:40 nahamu danolj: heh. no one in here has even heard of it... :-P
18:40 berto- danolj: haven't heard of that before.  ;)
18:40 danolj thanks for laughing with me!
18:40 EugeneKay I think it's /exactly/ the right window.
18:40 EugeneKay And oy, date-based? not thrilled about that.
18:41 EugeneKay Just because Ubuntu does it doesn't make it a good idea
18:41 forresta EugeneKay, it will be both date based, and there will be a codename
18:41 berto- EugeneKay: what does the current scheme mean to you?
18:41 forresta and I'll take dates over the outrageous Puppet style
18:42 EugeneKay I always assume Semantic Versioning.
18:42 _ikke_ danolj: Can you explain what it does? :P
18:42 danolj _ikke_: that's why I'm lurking here
18:42 forresta _ikke_, well these things called 'docs' right? You read them, and you learn things! :D
18:42 berto- forresta: glad the stability issue is being discussed.  version numbers, pre-1.0, whatever aside, having continual breakage eliminates any sort of confidence to upgrade.  i myself am usually reluctant.
18:43 forresta berto-, I don't blame you, and none of the devs would either.
18:43 EugeneKay I like the idea of unit tests, but I know writing them is horrifying.
18:43 forresta EuguneKay, integration AND unit tests :P
18:44 _ikke_ writing them after te fact is
18:44 EugeneKay And an unwavering commitment to the Pope
18:45 berto- forresta: https://github.com/saltstack/salt/issues/9426
18:45 forresta berto-, awesome
18:46 _ikke_ forresta: I hear often about 'Docs', still need to investigate them
18:46 forresta _ikke_, hey man, I work hard on those docs :(
18:47 _ikke_ It's appreciated
18:51 forresta I know, I'm just messing with you
18:52 forresta half the time I just write it for myself because I know I won't remember.
18:52 _ikke_ haha
18:52 danolj forresta: that is one of the best reasons for writing docs
18:52 forresta Yep
18:53 danolj so how did I configure that server two years ago?  Hmm... let's see what the wiki has on that subject.
18:53 forresta yep
18:53 danolj or Salt!
18:53 forresta I know I won't remember
18:53 forresta heh
18:54 bhosmer joined #salt
19:08 forresta I'll be back in a bit
19:13 druonysus joined #salt
19:14 druonysus joined #salt
19:14 ggoZ joined #salt
19:17 fllr joined #salt
19:21 _ikke_ I thought bits would exhaust after one second :P
19:24 pcurry_nomi joined #salt
19:30 cachedout joined #salt
19:31 forresta joined #salt
19:32 joehh joined #salt
19:33 pdayton joined #salt
19:40 ajw0100 joined #salt
19:40 pcurry_nomi joined #salt
19:48 jacksontj joined #salt
20:01 nahamu aside from the regression mentioned earlier, are people generally running 0.17.4 without issue?
20:01 * nahamu built and published the SmartOS esky a minute ago...
20:04 pengunix joined #salt
20:04 blarghmatey joined #salt
20:05 blarghmatey What is the best way to handle an SSH key for accessing a git repository? Should I include it as a pillar item?
20:05 blarghmatey What is the best way for securing sensitive data in pillars, particularly inside of version control?
20:06 blarghmatey Also, Hello Everyone!
20:08 bhosmer joined #salt
20:09 rojem joined #salt
20:11 rojem joined #salt
20:13 capricorn_1 joined #salt
20:14 mgw joined #salt
20:17 BenCoinanke joined #salt
20:18 troyready joined #salt
20:21 forresta blarghmatey, yea inside of pillar is best. Take a look at https://gist.github.com/UtahDave/3785738
20:21 forresta nahamu, generally 0.17.4 is pretty good from what I've seen so far.
20:21 forresta lots of bug fixes
20:22 Corey Happy Christmas, y'all.
20:23 forresta You mean 'happy day off from work' Corey? :P
20:24 forresta gonna be a good day, sleep in, work on my presentation and some other stuff, and relax.
20:25 Corey forresta: Yeah, lot of that going on.
20:25 Corey I plan to celebrate via drinking.
20:25 forresta heh
20:25 forresta There's no yoga tomorrow which is a bummer
20:25 forresta so I'll have to do that on my own
20:25 forresta damn holidays
20:26 Corey Then pull requesting.
20:26 forresta make sure you're at the top of the curve
20:26 nahamu forresta: good to know.
20:27 forresta nahamu, yea, other than that one damned regression issue, it's been very solid, a lot fewer problems in the IRC
20:27 forresta might be due to the holiday too
20:34 blarghmatey__ joined #salt
20:37 berto- joined #salt
20:48 pcurry_nomi joined #salt
20:49 gadams999 joined #salt
21:02 gadams999 with the merger of salt-cloud into saltstack, who is managing the combined documentation, or is it still referenced separately?
21:03 forresta gadams999, all of the docs have been transitioned to the main repo. I believe that part of read the docs still references salt-cloud specifically, however they live in the main repo.
21:04 gadams999 forresta: thanks, just found it under saltstack.com. Stoopid ol' Google keeps returning salt-cloud.com references. I've created New And Improved bookmarks to the docs
21:05 forresta hah yea that happens to me once in a while too, I don't know if there are plans to take that down yet...
21:22 martoss joined #salt
21:34 jacksontj joined #salt
21:35 kermit joined #salt
21:42 pcurry_nomi joined #salt
21:47 sfvivek1 joined #salt
21:52 elfixit joined #salt
21:52 fllr joined #salt
21:53 ajw0100 joined #salt
21:54 pcurry_nomi joined #salt
21:57 pcurry_nomi joined #salt
22:00 pdayton joined #salt
22:07 Katafalkas joined #salt
22:31 pdayton joined #salt
22:31 bhosmer joined #salt
22:43 fllr joined #salt
22:47 danolj left #salt
23:50 michelle_ joined #salt
23:53 fllr joined #salt
23:59 pdayton joined #salt

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