Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-11-16

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

All times shown according to UTC.

Time Nick Message
00:01 dooshtuRabbit joined #salt
00:13 thayne joined #salt
00:15 MTecknology gitlab ... a pain in the arse every single time I try to install it
00:15 MTecknology even via working salt states
00:17 MTecknology maybe ugrading to debian testing will help...
00:18 yomilk joined #salt
00:23 slafs left #salt
00:31 MTecknology k... fuckit... not using gitlab at home
00:32 Eugene I've had good luck with Gitblit. Stick it in a tomcat server, and it Just Works
00:33 Eugene There was an env var I had to set to make it use /srv/gitblit/ for data storage, and a bit of fiddling to auth against LDAP.... but nothing terribly out of the ordinary pains for that
00:35 alanpearce joined #salt
00:43 seydu joined #salt
00:59 alexr joined #salt
01:07 jagardaniel Hmm, I think i have come across a bug and i'm trying to change the source to see if it is working (in python2.7/site-packages/salt...etc) but the changes there doesn't seem to take effect at all - are they cached or something?
01:24 yomilk joined #salt
01:35 aparsons joined #salt
01:35 srage_ joined #salt
01:46 ajolo joined #salt
01:56 mrlesmithjr joined #salt
02:03 n8n joined #salt
02:07 moos3 anyone use reclass with jinja tempaltes
02:23 n8n joined #salt
02:31 MTecknology How far off am I with this?  http://dpaste.com/106ASD2
02:31 n8n joined #salt
02:32 MTecknology seems like I'm copying the syntax for gitfs_remotes from the docs
02:34 jhauser_ joined #salt
02:36 alanpearce joined #salt
02:39 MTecknology another attempt that seems closer... http://dpaste.com/3JV2PT9
02:45 MTecknology as root, I can run 'git clone <url>' without issues...
02:45 StDiluted joined #salt
02:45 asyncsrc joined #salt
02:47 ilbot3 joined #salt
02:47 Topic for #salt is now Welcome to #salt | SaltConf 2015 Call for Speakers is open! http://saltconf.com/call-for-speakers/ | 2014.1.13 is the latest | Help us test the 2014.7 RC! http://bit.ly/salt-rc | Please be patient when asking questions as we are volunteers and may not have immediate answers | Channel logs are available at http://irclog.perlgeek.de/salt/
02:59 Nexus_x1 joined #salt
03:06 wolfpackmars2 joined #salt
03:18 cleme1mp joined #salt
03:25 tmh1999 joined #salt
03:31 mosen joined #salt
03:32 n8n_ joined #salt
04:45 Ryan_Lane joined #salt
04:47 ramishra joined #salt
05:07 cads joined #salt
05:08 ajolo joined #salt
05:09 ysiad joined #salt
05:23 Reiner0318 joined #salt
05:23 igorw_ joined #salt
05:39 TTimo joined #salt
05:53 n8n joined #salt
06:05 davelupt joined #salt
06:06 otter768 joined #salt
06:09 genediazjr joined #salt
06:11 davelupt left #salt
06:14 ramishra joined #salt
06:15 davelupt joined #salt
06:38 alanpearce joined #salt
06:40 n8n joined #salt
06:50 catpiggest joined #salt
06:50 thayne joined #salt
07:19 ghanima joined #salt
07:24 ndrei joined #salt
07:35 JlRd joined #salt
07:38 alanpearce joined #salt
07:52 ramishra joined #salt
07:52 esharpmajor joined #salt
08:41 TTimo joined #salt
08:45 gildegoma joined #salt
09:07 ckao joined #salt
09:08 CeBe joined #salt
09:11 genediazjr joined #salt
09:24 alanpearce joined #salt
09:30 __gotcha joined #salt
09:32 JlRd joined #salt
09:42 TTimo joined #salt
09:45 intellix joined #salt
09:46 scarcry joined #salt
10:24 alanpearce joined #salt
10:34 LotR joined #salt
10:34 chiui joined #salt
10:41 CeBe1 joined #salt
10:42 favadi joined #salt
10:43 thehaven joined #salt
10:49 paha joined #salt
10:49 cpowell joined #salt
10:54 alexr joined #salt
10:56 alexr joined #salt
11:06 paha joined #salt
11:12 CeBe joined #salt
11:22 peters-tx joined #salt
11:33 CeBe joined #salt
11:43 TTimo joined #salt
11:49 bhosmer joined #salt
11:50 CeBe2 joined #salt
11:51 CeBe joined #salt
12:21 yomilk joined #salt
12:29 yomilk joined #salt
12:34 akafred joined #salt
12:34 JlRd joined #salt
12:36 __gotcha joined #salt
13:01 yomilk joined #salt
13:06 arnoldB MTecknology: https://np.adm.sx/view/5cd9b5ba
13:14 thayne joined #salt
13:15 agend joined #salt
13:28 alanpearce joined #salt
13:31 jonatas_oliveira joined #salt
13:43 bhosmer joined #salt
13:45 TTimo joined #salt
13:47 __gotcha joined #salt
13:50 rawkode joined #salt
13:53 Roee joined #salt
13:53 __gotcha joined #salt
13:54 rjc joined #salt
13:55 Roee Hi all
13:55 Roee i'm new in salt and looking for good and basic states examples
13:58 Roee and one more question, let's say that i'm writing new state that using file.recurse, is there a way to find all the arguments options and how to use them correctly ?
13:58 Roee Many thanks !
14:11 \ask joined #salt
14:19 asmaps joined #salt
14:34 bmonty joined #salt
14:38 TTimo joined #salt
14:56 jagardaniel Roee: yes, you can find all that information in the documentation :) here is file.recurse as an example http://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.recurse
15:00 viq joined #salt
15:02 alanpearce joined #salt
15:08 bhosmer joined #salt
15:08 Roee hi thank you very much !
15:13 Roee I have another question please , i created a state that includes from file.recurse. and 3 *  cmd.run
15:14 Roee how can i decide the order execution per each function ?
15:17 jagardaniel another person can probably fill in with some more information, but they should be executed in the order that you have placed them in the state file - however, you can use - order: 1 as an example to change that
15:17 jagardaniel http://docs.saltstack.com/en/latest/ref/states/ordering.html#the-order-option
15:23 ndrei joined #salt
15:27 johtso_ joined #salt
15:29 bhosmer joined #salt
15:40 babilen Roee: Please don't use order, but requisites. Why does the order matter?
15:40 babilen (also: states in SLS are run top to bottom)
15:47 stbenjam is there any built-in way to schedule state.highstate from the master?
15:47 stbenjam if you do the scheduling in /etc/salt/minion, the job results don't get uploaded back to the master...
15:50 thayne joined #salt
15:52 cads joined #salt
15:57 babilen stbenjam: Something like http://docs.saltstack.com/en/latest/topics/jobs/schedule.html ?
16:00 stbenjam yes, that doesn't upload back to the master, there's an open issue for it i guess
16:00 stbenjam https://github.com/saltstack/salt/issues/12653
16:02 babilen there you go then
16:03 cetex left #salt
16:07 aqua^mac joined #salt
16:08 glyf joined #salt
16:15 CeBe joined #salt
16:20 glyf joined #salt
16:32 bhosmer joined #salt
16:46 felskrone joined #salt
16:51 jhauser joined #salt
16:53 jp___ joined #salt
16:56 MTecknology arnoldB: so then my syntax is right... making this particular error much more irritating.. http://dpaste.com/3YJWYZD
16:56 davidone joined #salt
16:59 MTecknology I can see on the git server that salt is authenticating to the git server perfectly fine
17:04 MTecknology I wonder if my git server just isn't set up right for the way salt wants to pull repos. It's only a server with openssh, git, and users. Nothing like gitlab running on it.
17:08 MTecknology kablam! got it!
17:10 MTecknology I needed this format:  git+ssh://salt@git.lustfield.net/states.git
17:15 ajolo joined #salt
17:16 zlhgo joined #salt
17:25 MTecknology Isn't the python-git package in Debian 7 supposed to provide all of the git stuff I need?
17:34 ndrei joined #salt
17:39 horace_ joined #salt
17:41 patrek joined #salt
17:43 gildegoma joined #salt
17:45 mapu joined #salt
17:48 arthabaska joined #salt
17:52 TTimo joined #salt
17:58 snuffeluffegus joined #salt
17:59 TTimo joined #salt
18:04 MTecknology I should just re-roll my salt master from scratch. I've done a lot of stuff with it to try to make things work and it seems I obviously screwed something up.
18:15 favadi joined #salt
18:19 jhauser joined #salt
18:20 teebes joined #salt
18:26 Eugene Just use Salt to manage it :v
18:27 MTecknology Eugene: that's my goal
18:33 alexr__ joined #salt
18:34 MTecknology Wow! That helped a lot!!!
18:34 MTecknology holy crappers did redoing that box from scratch help a lot!
18:35 MTecknology My only error now is "2014-11-16 12:34:01,697 [salt.loaded.int.fileserver.gitfs         ][ERROR   ] Git fileserver backend is enabled in master config file, but could not be loaded, are pygit2 and libgit2 installed?" Interesting because it seems to actually be pulling teh git repos
18:40 MTecknology It doesn't seem to pull the git repos, it most definitely does. It seems that the error message is a bit incorrect.
18:40 MTecknology Eugene: Do you use salt to manage the salt-master configs?
18:46 Leonw joined #salt
18:46 calve joined #salt
18:48 superted666 Hey guys, newbie python question. I'm working on adding a new function to an existing module, a good way for me to learn python but i have a basic question first.. within a module i want to call another function of the same module but with a fixed parameter, how do i write that in python?
18:48 superted666 Trying to set '    installed_kernels = pkg.version kernel'  but clearly i'll need something smarter than that!
18:54 b1nar1_ joined #salt
19:01 Eugene Yes, but I have a very basic master. No gitfs or such
19:02 dnai23 joined #salt
19:02 babilen MTecknology: Is that 2014.7 ?
19:03 MTecknology yessir
19:03 MTecknology v2014.7.0
19:03 babilen MTecknology: Set "gitfs_provider: gitpython" in your master config. It is a little superfluous, but helps with these error messages.
19:03 babilen "error" messages that is
19:04 b1nar1 joined #salt
19:04 babilen I haven't had time to look into this in detail, but it appears that some codepaths don't trust/propagate the "git provider autodiscovery (i.e. "try pygit2, try gitpython, try dulwich, ...))
19:05 dnai23 hi, I just started using salt, and I have some values I need in a pillar organized with hostnames: hostname -> value_1. Now I want to use them in a file template, but since I need to access them via hostnames I need some way to use a hostname in the {{ salt['pillar.get'].. }} call
19:05 MTecknology babilen: yup, that took care of it
19:05 dnai23 is there some way to access grains in there?
19:05 dnai23 or another way to do this
19:08 CeBe joined #salt
19:14 ndrei joined #salt
19:15 glyf joined #salt
19:16 tristianc joined #salt
19:19 TTimo joined #salt
19:19 TheThing joined #salt
19:25 cads joined #salt
19:29 b1nar1_ joined #salt
19:34 MTecknology I wonder if I should roll my salt server at work from scratch as well... I've done a lot of mucking on that box as well.
19:36 TTimo joined #salt
19:42 CeBe joined #salt
19:43 tomtomtomtom joined #salt
19:45 LotR can you somehow insert the value of a grain into a value in the pillar? so you instead of having literal foo: example.com, you do foo: <grain:domain>
19:52 teebes joined #salt
19:54 miqui_ joined #salt
19:55 MTecknology I imagine that's possible. Grains are available in pillars afaik.
19:57 LotR yes, I figured it out. foo: {{ grain['domain'] }}
20:01 b1nar1 joined #salt
20:04 babilen LotR: Why would you want that (you could just refer to the grain directory in the file or state) ?
20:04 * babilen is too nosy
20:05 gildegoma joined #salt
20:09 LotR babilen: maybe I'm doing things suboptimally, it's my first day playing with saltstack. the saltstack-nginx-formula has vhost definitions in the pillar. if I have a generic vhost that just serves stuff out of /var/www, I can make that one reusable for all hosts if I don't hardcode the domain name
20:13 babilen LotR: Ah, yeah. That makes sense. I was simply saying that you could have used "{{ grains['domain'] }}" directly in the file you want to manage (i.e. the vhost definition), if it weren't for the fact that you are using a formula which states/files you cannot change.
20:13 babilen (or might not want to)
20:16 LotR babilen: the vhost definition isn't in a plain file, it's in a dictionary of vhosts in the pillar
20:17 LotR or maybe I misunderstood what you're saying. like I said, it's my first day :)
20:17 gngsk joined #salt
20:18 CeBe joined #salt
20:19 babilen Yes, but that will be used by https://github.com/saltstack-formulas/nginx-formula/blob/master/nginx/ng/files/vhost.conf
20:19 babilen fwiw, I consider the nginx formula to be horribly complex and the whole mixture of "ng" and "old style" in one formula to be quite suboptimal.
20:20 LotR babilen: oh, I found this one: https://github.com/bechtoldt/saltstack-nginx-formula.git
20:20 laderhiton joined #salt
20:21 CeBe2 joined #salt
20:21 babilen LotR: I can't say that the formula is not working or anything, just that it is impossible to understand it. I also strongly dislike the mixture of "ng" into the mix. If one wants to work on the formula it should be be done in place and if one wants to write a new formula then, well, so be it.
20:22 LotR babilen: I was trying to say I'm not using that one, but the one I linked
20:23 babilen Ah, that one
20:25 babilen bechtold's formulas are quite alright most of the time, but the official ones are hosted on saltstack-formulas. Ah, so bechtold decided to have the plain text config that is being inserted into the file in the pillar. How very unusual.
20:25 babilen You would, typically, have a template file that is being managed and contains references to pillar/grains in there.
20:26 LotR I didn't know about the official ones, I just googled around :) I will take a look at the repo with official ones
20:33 babilen LotR: https://github.com/saltstack-formulas/
20:35 LotR saltstack seems really cool, but you still need to think very carefully about how you do things. like that gitlab vhost in bechtoldt's pillar example. that should really be part of a gitlab formula. which would ideally have config for every webserver you can run it on
20:37 babilen I won't comment on that formula as it is neither in any way official nor am I familiar with it
20:37 babilen But, judging from the information you provided, I would agree with you
20:38 dude051 joined #salt
20:38 TTimo joined #salt
20:40 alexr joined #salt
20:41 LotR babilen: well, the included pillar is just an example, so it's not really part of the formula. it was just an easy example of my thoughts on how salt requires a lot of careful planning
20:42 babilen Everything needs careful planning, but I don't quite follow or understand what you are trying to say.
20:43 babilen I'd just start using salt and figure things out as you go along.
20:43 LotR I am
20:43 babilen Read the tutorials, best practices and formula conventions documentation, play with salt for a week or two and take it from there.
20:46 otter768 joined #salt
20:51 Ryan_Lane joined #salt
20:51 LotR babilen: what I was trying to say is that it seems really hard to write really good formulas. for say a web-app you need to add support for lots of webservers, and if it supports multiple databases you need to add support for those too, etc. it's very easy to make assumptions based on the choices of webserver/database/whatever that you've already made before starting with salt
20:54 babilen Oh, very much so.
20:56 babilen We just started with an effort to "standardize" some of the formulas and hope to have a style guide for them. But then: If you want absolute flexibility you will end up with reasonably complex formulas. But then: You don't always have to support all databases in existence nor all webservers. Configure one well in a manner that is easy to extend and the rest will come.
21:00 thayne joined #salt
21:15 teebes joined #salt
21:15 TTimo joined #salt
21:27 aquinas joined #salt
21:32 gngsk_ joined #salt
21:32 aquinas_ joined #salt
21:33 CatPlusPlus joined #salt
21:33 smcquay joined #salt
21:35 hasues joined #salt
21:37 hasues left #salt
21:39 TheThing joined #salt
21:40 rogst joined #salt
21:43 cads joined #salt
21:47 mapu left #salt
21:51 dooshtuRabbit joined #salt
21:52 aurynn if I'm using salt-ssh to run states, that implies that salt-minion is running on the target, right?
21:52 aurynn (docs are unclear)
21:55 babilen it does not AFAIR
21:55 TTimo joined #salt
21:55 babilen Isn't that the point?
21:55 babilen (or one of them, at least)
21:55 aurynn ah yes
21:55 aurynn Apparently I just can't read
21:55 aurynn :)
21:56 babilen nobody uses SSH as transport just for the fun of it
21:56 aurynn it looks like it builds a tarball of everything it's going to do, then shoves it over, and then runs that
21:56 jhauser joined #salt
21:58 ajolo joined #salt
22:02 alexbst joined #salt
22:03 mosen joined #salt
22:05 thayne joined #salt
22:05 ajolo_ joined #salt
22:06 ajolo_ joined #salt
22:06 cpowell joined #salt
22:09 TyrfingMjolnir joined #salt
22:16 bhosmer joined #salt
22:19 Singularo joined #salt
22:33 alexbst joined #salt
22:42 elfixit joined #salt
22:43 alexr__ joined #salt
22:48 Nexus_x1 joined #salt
22:51 glyf joined #salt
22:57 dude051 joined #salt
23:01 drags 7/win 28
23:02 ndrei joined #salt
23:05 ramishra joined #salt
23:05 g4rlic_ basepi: apologies for late reply, when I was working on my spec, there was nothing in Git or in Fedora mainline.  I hadn't checked epel yet.
23:06 alexbst joined #salt
23:12 ajolo__ joined #salt
23:18 Outlander joined #salt
23:19 ajolo joined #salt
23:25 ssteinerX joined #salt
23:29 ssteinerX http://docs.saltstack.com/en/latest/topics/tutorials/walkthrough.html -- leaves me at the end, with a minion attached to the master, and the ability to manually call functions
23:29 ssteinerX then what?  Where do I set up the server to push things to the minions?
23:31 babilen "things" ? What do you want to do?
23:32 ssteinerX e.g. make sure my one minion has nginx installed and running
23:32 babilen Did you read the state tutorial already?
23:32 ssteinerX yes
23:32 ssteinerX but I don't want to run things manually, I want the minions to be kept up to date by the server
23:32 ssteinerX I've use puppet and chef
23:33 babilen So, when do you want that to happen?
23:33 ssteinerX any time the 'minion of type xyz' spec changes
23:34 babilen Well, that's not quite how salt works, but you can naturally trigger a highstate run from a git push or so.
23:34 ssteinerX what I'm not seeing is where to put the specification
23:35 babilen Well, you read http://docs.saltstack.com/en/latest/topics/tutorials/states_pt1.html#preparing-the-top-file haven't you?
23:35 mosen ssteinerX: in state files (.sls), they're similar to .pp manifests in puppet
23:35 ssteinerX i.e. in chef or puppet all "webservers" have a configuration and all "webservers" are kept up to date with that
23:35 babilen (that's what I was just asking about)
23:35 mosen I think the confusion arises because theres a walkthrough, and then there's other tutorials
23:35 babilen http://docs.saltstack.com/en/latest/topics/targeting/
23:35 ssteinerX mosen: but where's the part where the "webserver" desired state is specified?
23:35 snuffeluffegus joined #salt
23:36 babilen ssteinerX: In the top file. Did you read the states tutorial I just linked and asked you about?
23:36 ssteinerX babilen: I'm not having trouble with the command line, I want the server to push config changes out to the minions
23:36 * ssteinerX going back to docs
23:36 jbub joined #salt
23:36 ramishra joined #salt
23:36 mosen ssteinerX: like babilen said theres another tutorial for that. everything flows down from the top file (default /srv/salt/top.sls) which is similar to the default nodes thing in puppet
23:36 babilen ssteinerX: So, did you read that or not?
23:37 ssteinerX I think I did the walkthrough and kind of expected it to go to the next level, but it kind of dead-ends with links to mind-numbing detail docs
23:38 babilen So you did not read the states tutorial, I'd read that and then continue with the pillar walkthrough
23:39 ssteinerX babilen: I went through the walkthrough, then kind of dead-ended.  The walkthrough should link through to the States tutorial, IMO.
23:39 mosen ssteinerX: yeah I found some problems with the documentation structure because it stops explaining something, and then there will be a corresponding detailed section about that under a different heading
23:39 babilen You might want to take a look at http://docs.saltstack.com/en/latest/ref/states/top.html and the targeting info I linked earlier if you want to jump ahead, but I'd essentially work through http://docs.saltstack.com/en/latest/topics/tutorials/index.html first
23:39 babilen ssteinerX: It does link: http://docs.saltstack.com/en/latest/topics/tutorials/walkthrough.html#next-reading
23:40 ssteinerX babilen: "Getting deeper into states" does not convey "The next thing you need to know" to me
23:40 LotR I must admit, it felt kind of confusing to me too that there was more than one 'walk-through'
23:41 babilen Which is why I specifically asked you about "the states tutorial". Either way, read the tutorial chapter and, in particular, the documentation I highlighted so far.
23:41 ssteinerX babilen: will do
23:42 babilen The documentation is vast, but reading chapter 3 + best practices + formula conventions gets you pretty damn far. You will also want to refer to the targeting docs every now and then and you might find the scheduling system interesting if you want to run highstates on a regular basis.
23:43 ssteinerX babilen: And, coming from other tools, I felt like I hit a brick wall there…I know what I want to do, but how would I know where to go from the end of the walkthrough?  States Tutorial is clearly where I need to go, but that's not really clear from the walkthrough.
23:44 babilen ack, I agree. The transition could be better in the docs
23:44 ssteinerX babilen: How can I help?
23:45 glyf joined #salt
23:46 ssteinerX The walkthrough's awesome and got me right to the point where I wanted to start developing target states for my various minions, but there I was, stuck with no clue as to where to find the info I needed to make my "top."
23:46 babilen Well, for once it should be more obvious that people should just start reading http://docs.saltstack.com/en/latest/topics/tutorials/index.html in that order (probably skipping everything after 3.4, although I find GitFS to be an invaluable tool
23:46 babilen And on the other hand the "States tutorial 1,2,3..." should be linked directly from the walkthrough in the "read this next" bit
23:47 babilen So: Just read 3.2 and 3.3 and you should be set
23:47 ssteinerX babilen: Coming from other tools, I don't want to read "masterless" anything...
23:48 ssteinerX babilen: And maybe that's the impedance mismatch
23:48 babilen sure, skip that if it really doesn't interest you
23:48 babilen you might also be interested in https://github.com/saltstack-formulas/ + pillar documentation + best practices
23:48 LotR ssteinerX: the docs aren't written for you exclusively :)
23:48 ssteinerX LotR: WHAT!?
23:49 ssteinerX ;-)
23:49 ssteinerX I'm feeling a very, very bad urge to actually write the tutorial I need (so I don't forget how I got there, mostly)
23:50 mosen ssteinerX: hehe I thought the same, i should do a blog post
23:50 ssteinerX mosen: It's not easy being green ;-)
23:52 yomilk joined #salt
23:52 ssteinerX Now that I'm looking at 3. Tutorials, I can see how it got set up this way.  A real NOOB wouldn't want to do all the (incredibly tedious) shit to get a client/server set up with firewalls etc.
23:54 b1nar1 joined #salt
23:54 ssteinerX Damn software documentation is hard!
23:56 babilen http://shop.oreilly.com/product/0636920033240.do

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