Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-05-24

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

All times shown according to UTC.

Time Nick Message
00:02 krissaxton joined #salt
00:05 justhamade joined #salt
00:10 mahimahi joined #salt
00:14 jacksontj joined #salt
00:16 mahimahi1 joined #salt
00:17 m_george|away joined #salt
00:22 m_george left #salt
00:23 lex__ joined #salt
00:32 juicer2 joined #salt
00:33 aat joined #salt
00:33 cvrebert left #salt
00:37 oz_akan joined #salt
00:43 m_george|away joined #salt
00:44 Kzim_ joined #salt
00:44 Kzim_ Hi
00:47 Kzim_ i try to use Salt as orchestration. have a Web interface where you enter 3 host and salt build you the cluster. so i think i need OverState but from what i understand you can't pass arguments to OverStates and use pillar force my gui to write a flat file ... and i find this ugly. i don't understand the correct ay to do this
00:47 jafo joined #salt
00:48 eskp joined #salt
00:54 jafo joined #salt
01:09 Nexpro joined #salt
01:39 Bram joined #salt
01:45 mirko joined #salt
01:50 danielbachhuber joined #salt
01:50 jacksontj joined #salt
01:53 napperjabber joined #salt
02:05 druonysus joined #salt
02:05 druonysus joined #salt
02:24 cxz joined #salt
02:31 KyleG joined #salt
02:55 raydeo_ joined #salt
02:58 jgelb joined #salt
02:59 jgelb_ joined #salt
02:59 wilywonka joined #salt
03:00 cxz joined #salt
03:01 jdaggett joined #salt
03:09 novel1 joined #salt
03:14 knapper_tech joined #salt
03:15 dcrouch joined #salt
03:24 hvn joined #salt
03:30 oz_akan joined #salt
03:41 KyleG joined #salt
03:46 aat joined #salt
03:56 dthom91 joined #salt
04:06 Katafalkas joined #salt
04:07 mgw joined #salt
04:08 wilywonka joined #salt
04:16 danielbachhuber joined #salt
04:35 efixit joined #salt
04:44 kmrhb joined #salt
05:05 Katafalk_ joined #salt
05:16 raydeo_ joined #salt
05:18 robbyt joined #salt
05:27 krissaxton joined #salt
05:38 ktenney joined #salt
05:55 jacksontj joined #salt
05:58 jacksontj_ joined #salt
06:06 sebgoa joined #salt
06:28 oz_akan joined #salt
06:35 drdran joined #salt
06:36 smeagol joined #salt
06:43 druonysus joined #salt
06:43 druonysus joined #salt
06:47 tharkun joined #salt
06:47 tharkun joined #salt
07:05 Charatna joined #salt
07:06 Nexpro1 joined #salt
07:12 carlos joined #salt
07:13 arek_ joined #salt
07:15 agend joined #salt
07:16 agend joined #salt
07:16 Ivo joined #salt
07:20 lesnail joined #salt
07:22 oliv_mc joined #salt
07:24 sebgoa joined #salt
07:24 sebgoa_ joined #salt
07:25 sebgoa__ joined #salt
07:27 jhauser joined #salt
07:31 vaxholm joined #salt
07:32 balboah joined #salt
07:35 ronc joined #salt
07:47 JLG joined #salt
07:48 davidone joined #salt
07:49 ekarlso joined #salt
07:49 ekarlso ello
07:49 ekarlso is there any modules for salt to do gluster?
07:55 Lucas_ joined #salt
07:55 sebgoa_ joined #salt
07:57 scott_w joined #salt
08:15 unicoletti_ joined #salt
08:23 Gareth joined #salt
08:25 scott_w joined #salt
08:27 azbarcea joined #salt
08:29 Lucas_ Hello salt channel.
08:30 Lucas_ I'm a Devops, and do my homework for saltstack. We project to study saltstack for managing little simple openvz VM (about  100+/1000+ host)
08:31 Lucas_ 1) Seeing the doc.saltstack.org. Is exist other source of informations, tutorial about salt.
08:31 Lucas_ ?
08:32 Lucas_ 2) Is there a limit of Minion number attribuate to one Master?
08:34 Charatna left #salt
08:37 kadel joined #salt
08:38 krak3n` joined #salt
08:40 lesnail joined #salt
08:56 sebgoa_ joined #salt
09:35 whiteinge Lucas_: the only limit for minions on a single master are available system resources. you can bump up the worker_threads setting if you run into slow minion returns
09:36 whiteinge Lucas_: two good resources:
09:36 whiteinge http://intothesaltmine.org
09:36 whiteinge http://www.youtube.com/saltstack
09:44 krak3n` joined #salt
09:53 it_dude joined #salt
09:53 zloidemon Hello, how can I get data from custom grains in minion configuration inside external pillar? For example: minion_id = __opts__['id'] from https://github.com/saltstack/salt/blob/develop/salt/pillar/cobbler.py
09:54 Katafalkas joined #salt
09:56 sebgoa_ joined #salt
09:58 Lucas_ whiteinge: ok, a good point, thank's for links
10:06 zloidemon Found  I was need __grains__['xxx']
10:21 mikedawson joined #salt
10:23 tharkun joined #salt
10:27 it_dude joined #salt
10:32 sebgoa Hi, is there a way to deploy a master with salt-cloud, get it's IP and pass it to a minion profile, within a map file ?
10:33 Katafalkas joined #salt
10:49 ProT-0-TypE joined #salt
10:50 krissaxton joined #salt
10:52 ronc joined #salt
10:55 vaxholm joined #salt
11:01 oz_akan joined #salt
11:25 giantlock joined #salt
11:27 lesnail joined #salt
11:29 mirko joined #salt
11:32 tharkun joined #salt
11:48 napperjabber joined #salt
11:54 jureq joined #salt
11:59 sebgoa joined #salt
12:00 felixhummel joined #salt
12:01 felixhummel joined #salt
12:04 vaxholm joined #salt
12:16 wilywonka joined #salt
12:28 backjlack joined #salt
12:29 Ryan_Lane joined #salt
12:34 hackband joined #salt
12:39 emilis_info joined #salt
12:41 lesnail joined #salt
12:42 jgelb joined #salt
12:53 elan joined #salt
12:55 elan hi ... anybody here have some experience with gitfs?
12:58 elan i'm trying to set it up. so far salt has noticed that the top.sls has an env called master, which is also the master branch in git. however the minion log throws an error that ends with : "for sls in fnmatch.filter(self.avail[env], sls_match): KeyError: 'master'"
12:59 pcarrier_ joined #salt
13:00 elan i'm wondering if the structure in my git repo is wrong. i have the top.sls in the root, and the modules directories also start in the root.
13:00 oz_akan joined #salt
13:06 oz_akan joined #salt
13:07 juicer2 joined #salt
13:15 bhosmer joined #salt
13:16 jkleckner joined #salt
13:17 krissaxton joined #salt
13:20 Ryan_Lane joined #salt
13:25 wilkystyle joined #salt
13:25 wilkystyle left #salt
13:27 Ryan_Lane joined #salt
13:27 Kholloway joined #salt
13:30 Ryan_Lane joined #salt
13:33 dcrouch joined #salt
13:35 pcarrier_ joined #salt
13:37 oz_akan_ joined #salt
13:39 Ryan_Lane joined #salt
13:41 felskrone joined #salt
13:41 felskrone hey
13:46 _Lionel_Debroux joined #salt
13:47 wunki joined #salt
13:48 wunki salt-cloud also has a daemon, should I be running it and what does it do?
13:55 jkleckner joined #salt
14:02 premera joined #salt
14:04 Madkinder joined #salt
14:05 Madkinder hi, can I use shell pipes in onlyif/unless of a cmd.state module?
14:06 aat joined #salt
14:07 felixhummel Madkinder: yes
14:08 m_george left #salt
14:09 felixhummel Madkinder: see http://pastebin.com/YFM9rqDc
14:12 lesnail joined #salt
14:14 chapel joined #salt
14:17 oz_akan joined #salt
14:19 LyndsySimon joined #salt
14:20 jdaggett joined #salt
14:21 lex__ joined #salt
14:21 kaptk2 joined #salt
14:22 conan_the_destro joined #salt
14:24 santagada joined #salt
14:24 ronc joined #salt
14:25 pcarrier_ joined #salt
14:26 Madkinder felixhummel: thanks a lot :)
14:26 Madkinder I'm trying to manage salt on a bunch of FreeBSD servers
14:27 Madkinder from what I understood there is support for both package managers: the old one and the new one
14:27 Madkinder how can I force salt to use one or another?
14:28 ronc_ joined #salt
14:30 Valda joined #salt
14:32 mgw joined #salt
14:33 balboah joined #salt
14:34 mgw joined #salt
14:36 _chjohnstwork joined #salt
14:40 jkleckner joined #salt
14:45 JasonSwindle joined #salt
14:48 sarkis joined #salt
14:54 aleszoulek joined #salt
14:55 kho joined #salt
14:56 danielbachhuber joined #salt
14:56 jefferai joined #salt
14:58 teskew joined #salt
15:05 Heartsbane joined #salt
15:05 Heartsbane joined #salt
15:06 Madkinder left #salt
15:06 jslatts joined #salt
15:07 unicoletti left #salt
15:12 agend joined #salt
15:12 jgelb joined #salt
15:14 faldridge joined #salt
15:16 luminous hello! what's the proper way to write a state to deploy a db like mysql / postgres, to a new salt host, such that you can then manage the dbs, users/etc in that new service
15:17 probablyfine luminous: there are the mysql/postgres modules available for managing databases, users, permissions, etc.
15:17 probablyfine e.g. http://docs.saltstack.com/ref/states/all/salt.states.mysql_database.html#module-salt.states.mysql_database
15:17 chrism luminous: yulp lots of good stuff in salt for pgsql/mysql
15:18 luminous that's not what I mean to ask, sorry
15:18 luminous unless I am mistaken, there's a connundrum here, no?
15:18 chrism ?
15:18 luminous do add a db/user/etc, salt needs to know the root password
15:18 luminous if it's a new install, you need to set it
15:18 chrism nah
15:18 chrism it runs as root on the client machine
15:19 luminous oh, so I am mistaken
15:19 chrism so it just sudos to postgres to exec that
15:19 luminous any mysql is fine too?
15:19 chrism afaik, I haven't used it personally
15:19 luminous ok
15:19 chrism i've been doing everything with pgsql
15:19 luminous I'll check that detail
15:19 luminous yea, you would be sensible to do so :P
15:19 opapo joined #salt
15:19 chrism =)
15:19 luminous I have to support some mysql :*(
15:24 koolhead17 joined #salt
15:24 koolhead17 joined #salt
15:25 oz_akan hi all, I have started to use overstate and now it almost seems like there is no use case for top.sls. any comments?
15:25 luminous hrm, what is this supposed to mean? "Comment:   State mysql_database.present found in sls foobarc is unavailable"
15:26 luminous oz_akan: not having used overstate at all.. I would ask.. how so?
15:26 clintberry joined #salt
15:27 oz_akan luminous: while creating servers, I have to provide an order. like install database servers first then get their IPs and configure web servers
15:27 luminous chrism: does the minion, master, or both, need the pg/mysql python module?
15:27 oz_akan luminous: overstate provides this mechanism. once I have overstate config file, which seems like top.sls, I would never use top.sls
15:27 luminous oz_akan: sure, but how does that do away with top?
15:28 oz_akan luminous: you say use this overstate file to run my sls files in an order
15:28 jdaggett joined #salt
15:28 oz_akan luminous: top.sls has the same thing, just without a forced order
15:29 luminous oh, interesting, so it's like another top.sls completely
15:29 luminous that's a little silly..
15:29 oz_akan yes, like top.sls with ordering
15:29 oz_akan I agree, instead I would just change top.sls to provide ordering
15:29 oz_akan I might well be missing something though
15:29 luminous yea, that should be combined in some way, it would seem, no?
15:30 luminous what's funny is that you can setup ordering with top.sls in a more crude way
15:30 luminous redundant functionality >> code bloat
15:31 luminous chrism: https://salt.readthedocs.org/en/latest/ref/modules/all/salt.modules.mysql.html#module-salt.modules.mysql <<< this is what I was talking about
15:31 luminous you have to put all this config in the minion :(
15:31 spudbook joined #salt
15:33 dave_den oz_akan: you have a fair question. being new to salt i have been struggling with order
15:34 oz_akan dave_den: you just need to use overstate system
15:34 oz_akan dave_den: it works well. just I can't understand why it doesn't replicate top.sls at all
15:35 dave_den yeah, overstate makes more logical sense to me. right now i have everything working in highstate/top.sls and ordered well
15:35 oz_akan luminous: I need something like, instal mongodb on all servers, than set replica
15:35 dave_den overstate seems like what i will use for application deployment rollouts so it will abort or rollback if there is a failure
15:36 oz_akan dave_den: I think you can't solve setting a replica set by just using top.sls
15:36 dave_den similar to capistrano functionality that we use now
15:36 dave_den oz_akan: how do you mean, re: replica?
15:37 oz_akan dave_den: problem is not the order of servers to run sls, but the order of sls files to run on same servers. so like first install mongodb on all servers, then if it succeeds, configure mongodb replica set
15:37 Ivo joined #salt
15:37 oz_akan dave_den: ...then configure web servers etc.
15:38 dave_den yeah, overstate seems like the proper place for that.
15:39 oz_akan then, if I am using overstate, do I ever need top.sls... that I am trying to understand
15:39 dave_den yep. i would say ask the mailing list to get clarification
15:40 dave_den perhaps overstate has not been emphasized as much as it should be in the docs
15:41 dave_den the only difference i can see is that overstate does ordered execution and halts on failed states
15:43 dave_den i actually want the ability to specify 'order:' on 'include' directives in my state files for highstate
15:45 jalbretsen joined #salt
15:45 opapo joined #salt
15:46 oz_akan I would like overstate functionality on top.sls.
15:47 oz_akan top.sls defines in which environment to run for a match
15:47 oz_akan I think overstate doesn't do that.
15:47 oz_akan better let me read more about it
15:49 dave_den overstate.sls should let you match just like you do in top.sls
15:49 chrism so does anyone have a good way to apply an extension to a pgsql db via salt?
15:49 chrism seems to be the pgsql states lack that bit
15:50 probablyfine chrism: i don't think that functionality exists in salt, write it! :)
15:51 chrism if python were something I did, I absolutely would
15:51 oz_akan dave_den: right it does.
15:51 * chrism shells out to perl
15:51 chrism =P
15:51 lesnail joined #salt
15:52 probablyfine chrism: /o\ :P
15:52 chrism lol
15:56 dave_den oz_akan: will you be asking the mailing list about overstate vs highstate? i'd also like to hear a more educated answer
15:57 synotna joined #salt
15:57 oz_akan dave_den: yes I will
15:57 dave_den cool
15:58 synotna hi, is anyone familiar with using the tomcat module? I'm having trouble deploying a WAR with it, it seems the WAR isn't copied to the /tmp folder in the process of deploying
16:02 robertkeizer joined #salt
16:02 oz_akan dave_den: just sent the email subject: overstate vs highstate
16:03 robertkeizer joined #salt
16:05 ronc joined #salt
16:08 druonysus joined #salt
16:08 druonysus joined #salt
16:20 knapper_tech joined #salt
16:26 lesnail joined #salt
16:27 krissaxton joined #salt
16:28 juicer2 Hi, curious how folks are doing reporting with salt, wondering how I can get my state.highstate results into redis or mongo or something, then see it in via html somehow?
16:30 btanaka joined #salt
16:31 KyleG joined #salt
16:35 ZenoTasedro joined #salt
16:36 jslatts joined #salt
16:39 luminous juicer2: you might be better with a question to the ml about that
16:40 juicer2 luminous: k
16:40 luminous juicer2: it seems like most folks either don't, or roll their own
16:41 juicer2 luminous: I see
16:41 luminous but I could be wrong.. I've been trying to get the same answered
16:42 dave_den juicer2: have you read about returners? https://salt.readthedocs.org/en/latest/ref/returners/
16:43 juicer2 dave_den: yep, I knew returners had something to do with it, but wasn't sure if many folks had it set up
16:44 gordonm joined #salt
16:46 luminous I think a better question is what to do with the data in the db afterwards
16:46 luminous not what to do with it when salt returns
16:46 Katafalkas joined #salt
16:47 luminous eg, this is the "folks either don't, or roll their own" - we have no UI elements for that
16:47 luminous unless salt-ui is getting there?
16:52 UtahDave joined #salt
16:56 jdaggett joined #salt
16:57 ronc joined #salt
16:57 hotbox hi guys
16:57 hotbox just done https://github.com/saltstack/salt/pull/5248
16:57 robertkeizer Question for knowledgeable folks: I'm starting with salt states, and I'm setting up 'apache2' and 'trac'. Simple enough, and I've got trac depending on apache2. My question is thus: I want to split out the definition of apache2 into its own file so that it can be used by other things down the road. How do I get that to work?
16:58 probablyfine robertkeizer: It should just still work? Just include the apache2.sls (for example) and the original file in your top/whatever
16:59 robertkeizer probablyfine: Thanks! I was missing it where the states were being specified against the host.
17:00 robertkeizer Makes logical sense.. I just was trying to figure out a way to get sls A to reference sls B.. gah.
17:00 robertkeizer Makes sense to go through some higher-level sls :).
17:00 * robertkeizer is happy.
17:02 whiteinge hotbox: awesome!
17:03 hotbox wow already merged thx whiteinge
17:04 ZenoTasedro i just pip installed salt-api on my saltmaster, but when ran it silently fails, i think i added the right settings to my master config to use the cherrypy rest interface
17:06 ZenoTasedro with -l debug it reads the conf, makes pidfile, and then starts to load netapi stuff
17:06 ZenoTasedro anybody have any tips on this?
17:07 whiteinge ZenoTasedro: pip won't install cherrypy as a dep. did you install that too?
17:07 ZenoTasedro yeah i thought that may have been the problem, i have 3.2.4 installed
17:08 ZenoTasedro http://pastebin.com/ivCZ4irA
17:09 whiteinge hm. can you also pastebin your rest_cherrypy config?
17:09 Lucas_ Hello, I'm trying to install salt -minion via bootstrap.saltstack.org, but I got a error with 'No installation function found. Exiting'
17:09 Lucas_ The full log  : http://pastebin.com/9K8bj18Y
17:10 ZenoTasedro bah! it was my config
17:10 ZenoTasedro cherypy
17:10 Lucas_ I'm on a debian7. (openVZ container, but not matter here I think)
17:10 ZenoTasedro picky computers!
17:10 whiteinge heh
17:10 ZenoTasedro ty whiteinge
17:10 whiteinge np :)
17:11 all_the_fisch joined #salt
17:13 Lucas_ I found some old issue matching older versions it seems. Is a manual dependancies to add before lauching install script?
17:14 UtahDave robertkeizer: you can have sls A include sls B
17:15 druonysus joined #salt
17:15 druonysus joined #salt
17:15 robertkeizer UtahDave: In your opinion, is that a cleaner way than doing multiple states for each host.. ?
17:16 ggoZ joined #salt
17:18 jkleckner joined #salt
17:18 UtahDave robertkeizer: Well, if you're going to be requiring sls A from sls B, then if you only list sls B in the top file and include sls A, you won't have to worry about accidently removing sls A from the top file.
17:19 druonysuse joined #salt
17:19 druonysuse joined #salt
17:19 robertkeizer UtahDave: True, although if I ever make a change to sls A I then have to figure out what depends on it, which means going through all the sls's rather than just the top.. if I'm understanding this correctly that is.
17:20 robertkeizer Simple grep, but still not the most elegant solution.
17:20 UtahDave Yeah, in the end it really just depends on how you like to organize things.
17:20 robertkeizer Then again, states are mainly fire and forget correct? Some additions and such later on, but for the most part they can be considered fairly static?
17:21 robertkeizer UtahDave: hmm, okay. How would I get sls A to include sls B, if I wanted to go that route? So far I've only found using top to include in order.
17:22 UtahDave in your A sls file:    - include:\n  - B
17:22 robertkeizer Thanks :)
17:22 ZenoTasedro robertkeizer: also this tut touches on that: http://docs.saltstack.com/topics/tutorials/states_pt3.html
17:22 justhamade joined #salt
17:23 druonysus joined #salt
17:23 druonysus joined #salt
17:23 robertkeizer ZenoTasedro: Thanks! I had looked at it, but hadn't gotten past the templating section.. thats exactly what I was looking for!
17:23 ZenoTasedro You're welcome
17:24 ZenoTasedro I kinda tip-toed through the tut's myself taking breaks to implement what i've learned as I go
17:25 chrism i started doing that, and then like 3 days later I had a full deployment system going "woah"
17:25 chrism lol
17:25 druonysuse joined #salt
17:25 druonysuse joined #salt
17:25 * robertkeizer is going to have to write a CouchDB returner in the next few days.
17:26 UtahDave nice
17:26 ZenoTasedro yeah i want to hack on the source a bit, but everything i've needed so far has already been included
17:28 ZenoTasedro i want to make a module for blue/green deployments with nginx, but I don't think it'd be flexible enough to be added to the core functionality
17:33 ZenoTasedro oh, well maybe the ldap auth module will get hacked on a bit actually
17:45 karlp I'm got a simple state file that installs supervisord, but salt '*' service.stop supervisor doesn't always stop it,
17:45 karlp I presume that must be a bug in supervisor's init scripts?
17:46 Corey karlp: Maybe. What OS?
17:47 karlp ubu 12.04?
17:47 karlp might have tried to stop it too soon as well.
17:48 karlp the fact that there's a supervisord module doesn't save me from having to setup the actual _installation_ of supervisor ina  state file right?
17:48 karlp just that once I've installed I can use the module
17:48 krissaxton joined #salt
17:48 Corey karlp: Checking.
17:49 Corey karlp: Correct.
17:49 karlp I did salt '*' pkg.install supervisor,
17:49 karlp but I didnt get anything from sys.doc supervisord until I restarted the minions
17:49 Corey karlp: Generally I prefer to do that in state files rather than through active commands.
17:49 Corey Then just highstate it. :-)
17:49 karlp yeah, only just getting started with this :)
17:50 karlp seems to be working quite nicely so far.
17:50 karlp next though is setting up a .sls for a package that will pull from git...
17:50 karlp more docs to read :)
17:53 krissaxton1 joined #salt
17:54 krissaxton joined #salt
17:57 karlp if I'm runnign the 0.15.1 version form the ppa, is there any good reason why it still runs as root? (by default)
17:57 karlp https://salt.readthedocs.org/en/latest/topics/nonroot.html says it's been not required since 0.9.1?
17:57 sebgoa joined #salt
17:57 Corey karlp: Funny you should ask. :-)
17:58 Corey karlp: The idiot PPA maintainer hasn't updated the package to run as non-root.
17:58 karlp ah.
17:58 karlp it seemed like the ppa was the best/right way of getting reasonably recent versions from.
17:58 Corey Mainly because I didn't realize that was a thing now. :-)
17:58 Corey karlp: It is.
17:59 Corey karlp: But somehow that slipped off of my radar.
17:59 Corey karlp: Let me see if I can make it go, if so I'll push it to the PPA later.
17:59 karlp beautiful :)
17:59 Corey karlp: There's a slight problem in that it may cause issues for folks who upgrade from old root versions.
17:59 Corey karlp: So the migration may be hairy, and I don't want to break folks' production clusters.
18:00 Corey karlp: Let me talk with the rest of the packagers, see if we can get some clarity around this. Thanks for bringing it up-- can you open an issue on github so we don't lose sight of it, tag @kb1jwq in it?
18:02 karlp under just "salt" or salt-qa or somethwere else?
18:02 karlp while we're on issues, this one should really be closed, it's committed and shipped: https://github.com/saltstack/salt/issues/2026
18:04 mgw I'm working on some ideas of how to manage BIND and DHCP via Salt. Anybody care to share their solutions?
18:05 probablyfine Managed zone files/etc via managed files? Templating?
18:05 Ryan_Lane joined #salt
18:06 mgw I have a pillar module such that a minion that has need of it (e.g, the dns server) has access to everything it needs, so a template might be sufficient.
18:06 mgw There was previously some discussion of a dns module
18:08 kermit1 joined #salt
18:08 dave_den i am putting DNS info into pillar and pushing templates to my dns servers that compile the zones
18:09 mgw dave_den: thanks, does that work well?
18:09 mgw Are you using bind?
18:09 dave_den i'm using tinydns
18:09 dthom91 joined #salt
18:09 dave_den mgw: i'm still developing my layout, so it's only functional as a test
18:11 mgw dave_den are you using dhcp too?
18:11 dave_den mgw: no. all my minions have static IPs
18:11 [diecast] joined #salt
18:12 dave_den mgw: i was previously looking into using DHCP from mongodb with https://github.com/guillaumerose/dhcp-mongodb
18:12 [diecast] what does "_in" mean for "require_in" or "watch_in"
18:12 dave_den not sure if that will give you any ideas ;)
18:12 [diecast] the docs are not clear on the meaning
18:13 knapper_tech joined #salt
18:13 dave_den [diecast]: require_in and watch_in are reverse of require and watch. so instead of defining a 'require' in a dependent state, you define 'require_in' in the parent state so that the dependent state requires the parent
18:15 mgw dave_den: I have bind and isc-dhcp in production, I'll probably just template their configs
18:16 dave_den [diecast]: the naming of require_in is kind of confusing. You can think of it as "required_by" like this git issue says: https://github.com/saltstack/salt/issues/3046
18:16 [diecast] ah, yes.
18:17 [diecast] at the least the docs should be updated - "One of them required for sure we fill up accumulator before we manage the file. Probably the same as filename"
18:18 [diecast] that's not even a comprehensible sentence
18:18 [diecast] http://docs.saltstack.com/ref/states/all/salt.states.file.html
18:21 Lionel_Debroux joined #salt
18:23 m_george|away joined #salt
18:30 balboah joined #salt
18:31 SpX joined #salt
18:32 jdaggett joined #salt
18:33 felixhummel joined #salt
18:35 oz_akan hi
18:35 oz_akan I can't seem to make mine work, is there a sample ?
18:36 oz_akan the one one the documentation wasn't enough, I set mine_fcuntions on the minion but can't get data
18:36 dave_den [diecast]: the docs are generated directly from the source. you could edit that sentence and submit a pull request if you are able. see http://docs.saltstack.com/topics/community.html#editing-and-previewing-the-documention     the sentence you posted is located in the module itself at salt/states/file.py
18:36 justhamade joined #salt
18:37 dave_den oz_akan: what version of salt?
18:37 oz_akan 0.15.1
18:37 oz_akan salt-0.15.1-1
18:38 robertkeizer If I wanted to check to make sure a given vhost is actually defined via apache.vhost, how would I add it to a sls file?
18:38 ada__ joined #salt
18:39 fxhp Do we have a method of creating a "system/service" style user?
18:39 robertkeizer I can pull the value just fine, but I'm unsure how to do a comparison /  true false..
18:40 dave_den fxhp: yes, use system: True in the user function
18:41 dave_den robert: do you mean you want to set the vhost from a state function, then have another state function make sure it was really set?
18:42 dave_den oz_akan: you have the mine functions declared in the minion config?
18:42 oz_akan dave_den: yes I did, as show in the document
18:42 oz_akan http://docs.saltstack.com/topics/mine/index.html
18:43 dave_den oz_akan: does this return anything: salt '*' mine.update
18:43 dave_den and of course i have to ask: did you restart your minion after adding the mine funcs to the config?
18:43 Kzim joined #salt
18:43 oz_akan says : None
18:43 Kzim hi
18:43 oz_akan dave_den: sure I restared
18:44 robertkeizer dave_den: Make sure the vhost is set.
18:45 robertkeizer dave_den: A jinja if statement? But then how do I return a value still..
18:46 oz_akan dave_den: when I run salt '*' mine.update, I see job is executed on the minion, but doesn't seem to send data
18:47 [diecast] dave_den: thanks for your help.
18:47 dave_den oz_akan: on minion: salt-call -l debug mine.update
18:48 oz_akan dave_den: let me try
18:48 munhitsu joined #salt
18:49 dave_den robertkeizer: sorry i am not clear on exaclty what you want. do you want to make a test to see if the vhost is set so that you can use logic in another state or template?
18:49 oz_akan dave_den: http://paste.openstack.org/show/37744/
18:50 robertkeizer dave_den: Yes.. I think I've made some progress.. using jinja logic and salt['apache.vhosts']( ) ..
18:50 Kzim Hi When a mudole ask an external pillar for data, does the minion make the call directly or this go through the Master ?
18:53 dave_den oz_akan: sorry, i'm not much help with mine
18:53 abscond_ joined #salt
18:53 oz_akan dave_den: np, it seems like a bug to me. have you ever seen it working
18:54 dave_den i have not used it myself yet
18:54 oz_akan salt is great but every critical component has a bug
18:54 oz_akan map has a bug, mine has a bug, profiles has a bug...
18:55 fxhp dave_den: are you sure that makes the user a system/service account?
18:55 dave_den it's still very young. i've struggled with a lot of unexpected stuff like that
18:55 fxhp It seems like that just chooses the pool of uid/gids
18:57 dave_den fxhp: it should create the user with UID within the SYS_UID_MIN and SYS_UID_MAX
18:59 fxhp dave_den: does it harden the account?
18:59 fxhp like prevent it from logging in
19:00 [diecast] another quick question in the docs... http://docs.saltstack.com/ref/states/#sls-files
19:01 dave_den fxhp: the password field is set to '!' in /etc/shadow. you can also set the shell for the user in the salt function definition
19:01 [diecast] earlier it was said that 'watch' includes the function of require and require is not needed when watching
19:01 dave_den fxhp: for example: http://pastebin.com/VQPYVFxV
19:01 [diecast] so why in this example are both require and watch used on the same object
19:02 [diecast] "file: /etc/salt/minion"
19:02 LGSilva joined #salt
19:03 [diecast] http://docs.saltstack.com/ref/states/ordering.html#the-watch-requisite - "The watch requisite executes the same logic as require (therefore if something is watched it does not need to also be required)"
19:03 fxhp [diecast]: you want to watch the file, and only run if it changes, you want to order the dependency "tree" such that this state will not run before file state is run
19:03 [diecast] but it was also said in the docs that "Salt does not execute state declarations in the order they appear in the source."
19:04 Kzim i can find a good documentation on how do a external pillar module to get data from Chef
19:05 fxhp [diecast]: right, it is run in a seemly random order, unless you care, in which case you may specify the order using require:
19:08 pjs joined #salt
19:08 jdaggett joined #salt
19:11 [diecast] fxhp: so something like - a requires c, c requires b, b requires a
19:16 baniir joined #salt
19:20 Lionel_Debroux_ joined #salt
19:27 _Lionel_Debroux joined #salt
19:28 LGSilva hello guys. Is there a good documentation about external pillars?
19:31 unicoletti_ joined #salt
19:33 faldridge joined #salt
19:39 drdran joined #salt
19:41 UtahDave joined #salt
19:43 * robertkeizer just discovered the awesomeness of watch_in ..
19:44 LyndsySimon_ joined #salt
19:48 bhosmer joined #salt
19:55 fxhp [diecast]: that might cause a problem if you create a circular require
19:57 [diecast] that occured to me as well
19:58 fxhp [diecast]: let say you wanted a command to run, but not before a file is in place...
19:59 Lucas_ joined #salt
19:59 fxhp [diecast]: you may use "- require: - file: the-file-label-or-name" in the cmd
20:00 fxhp that means the file state will run before the cmd state
20:02 [diecast] then later if you want another method to run before one would you use watch_in or require_in
20:02 [diecast] it seems you are never really running everything in a linear way
20:02 fxhp [diecast]: require_in is basically the inverse
20:02 fxhp salt runs linearly
20:02 [diecast] ok
20:03 fxhp the order is seemingly random unless you configure it otherwise
20:03 [diecast] so from top to bottom each state respects order?
20:03 [diecast] ok, ok.. got it
20:03 fxhp no
20:03 [diecast] that's wrong
20:03 [diecast] ya, i understand now
20:03 fxhp [diecast]: do you know python?
20:03 [diecast] yes
20:04 [diecast] so is the top.sls much like a run() inside __main__ ?
20:04 fxhp [diecast]: salt is convering yaml into dicts of dicts
20:04 fxhp you know how python does not keep dict keys in order?
20:04 [diecast] right
20:04 fxhp same is true with salt
20:05 [diecast] but you can write a generator to sequentially read based on a key
20:05 fxhp top.sls is a place to have a very high level view of your environments
20:05 fxhp to quickly know what the state of your systems are
20:06 fxhp It is an entry point
20:06 fxhp minions will apply state according to the target's they match in the top.sls
20:06 fxhp '*' targets all
20:07 fxhp '*.example.com' targets all minion id's of the example.com domain
20:07 zloidemon UtahDave: What's tops and auth? Where and how can I use it?
20:07 [diecast] fxhp: right
20:07 [diecast] ive been using it for a few days now and have made some states and applied them
20:08 UtahDave zloidemon: what part of the docs are you looking at?
20:08 [diecast] was missing a general overview that made sense. thanks for that introduction. ;)
20:08 fxhp [diecast]: anytime
20:09 zloidemon UtahDave: I'm looking at logging info and I saw a few dirs which not found on my system
20:09 alekibango joined #salt
20:11 UtahDave well, you can use various external authentication mechanisms.
20:12 Lionel_Debroux joined #salt
20:14 zloidemon UtahDave: And I have question about removing packages. When I was installing new hosts I deleted many packges without salt because it's openvz servers from hostings. How will I fix it with salt?
20:18 unicoletti_ left #salt
20:24 Kzim hello, if i do a external pillar module can i have minion ask the pillar to the master to avoid having to install the python dependancies for the external pillar ?
20:24 dave_den zloidemon: this is how I purge a package. sendmail used in this example, and I have to use the 'sendmail stop' command because the package doesn't shut down sendmail properly on purge (but that is not salt's fault).  http://pastebin.com/MQQGb0Ls
20:24 aboe joined #salt
20:26 UtahDave Kzim: external pillar is ALWAYS queried on the master.  The master compiles the pillar and encrypts it and sends the data to the minion
20:26 UtahDave the minion never queries the external pillar
20:27 Lucas_ joined #salt
20:27 zloidemon dave_den: Thank you. It seems as I want.
20:27 Kzim UtahDave, i love salt :)
20:28 Kzim UtahDave, if i want create a ext pillar module i just put it in  /usr/lib/python2.7 ?
20:28 dave_den hey UtahDave: is there a salt dev mailing list? how do the devs coordinate efforts on features, etc?
20:28 krissaxton joined #salt
20:28 dave_den besides #salt-devel
20:29 UtahDave #salt-devel and the salt-users mailing list.
20:29 whiteinge also github milestones
20:29 UtahDave yes
20:32 justhamade joined #salt
20:34 Kzim i rename cmd_json.py in /usr/lib/python2.7/site-packages/salt/pillar and enabled it in master conf and this doesn't work do i miss something ?
20:34 [ilin] joined #salt
20:34 [ilin] joined #salt
20:35 Kzim nevermind it work :0
20:38 ronc joined #salt
20:38 knapper_tech joined #salt
20:40 druonysus joined #salt
20:40 druonysus joined #salt
20:44 Kholloway joined #salt
20:52 pcarrier_ joined #salt
20:53 sebgoa joined #salt
21:01 jesusaurus at what point during state compilation does grain data become available?
21:06 UtahDave grain data is available from the very beginning because grains are instantiated when the minion starts up
21:09 jesusaurus hmm... well I seem to be getting: UndefinedError: 'grains' is undefined
21:09 jesusaurus and I thought maybe it had to do with trying to access grains from within a jinja macro
21:10 jesusaurus and so I was wondering at what stage of the state compilation the grains dict becomes available to the internal compiler
21:11 jesusaurus actually, im accessing the grains dict as an argument to the jinja macro
21:12 jesusaurus maybe if i {% set %} the grain data first, then pass that in as the argument it'll work
21:16 jalbretsen ugh, I can't find this on google.  Mutliple conditions in jinja, what is the correct syntax....
21:17 dave_den jesusaurus: what data are you trying to access? perhaps you should be using pillar?
21:17 jalbretsen is it like.... {% if foo = 'bar' or foo = "baz" %} ?
21:17 jesusaurus i think i found where its barfing
21:17 jesusaurus dave_den: inside a jinja macro i have an id called 'foo_bar_{{ grains['host'] }}:'
21:18 jalbretsen er
21:18 jalbretsen {% if foo == 'bar' or foo == "baz" %}
21:19 jesusaurus jalbretsen: its just standard python syntax inside {% %}
21:19 jalbretsen good to know, thanks
21:26 mgw Is something missing from this page: http://docs.saltstack.com//topics/tutorials/cloud_controller.html#using-salt-virt ? It seems to end very abruptly.
21:27 jdaggett joined #salt
21:32 UtahDave mgw: :)  It does seem that way.
21:32 UtahDave Tom just recently wrote those docs. I'll ask if he has anything missing there.
21:32 mgw UtahDave, thanks
21:33 UtahDave np
21:37 luminous UtahDave: continuing with my returner question from yesterday - do you know of any UI elements that aim to act as a display interface to returner info stored inthe database?
21:38 baniir joined #salt
21:41 UtahDave luminous: I don't know of any.  You can just access the data from the database however you need
21:42 luminous of course, I'm just a wee bit surprised we have so many modules (clearly many people doing many different things) but everyone seems to roll their own
21:42 luminous I can live with rolling my own, just like to build off of other components if they exist and fit well
21:43 luminous totally different type of question, is it possible to define a dictionary in say pillar_defaults.sls, and then in another pillar_node.sls extend what exists? or are you overriding?
21:45 UtahDave I believe they are overriding.
21:48 luminous thanks UtahDave! I will confirm
21:48 luminous test/confirm
21:49 UtahDave cool, thanks
21:52 krissaxton joined #salt
21:55 mgw virt.init: image is a path to the image accessible via the filesystem on all hypers?
21:59 mgw also — what is the format/options for the 'nic' parameter?
21:59 robertkeizer left #salt
22:05 UtahDave mgw: You're going to have to ask on the mailing list.  I'll point it out to Tom. He's done all the work so far on salt-virt
22:05 jdaggett joined #salt
22:08 it_dude joined #salt
22:08 mgw UtahDave: thanks
22:08 UtahDave You're welcome.  I'm sorry, I wish I could be of more help with that.
22:09 mgw UtahDave: here it is: https://github.com/saltstack/salt/blob/develop/salt/modules/virt.py#L197
22:09 mgw :-)
22:10 jgelb joined #salt
22:10 mahimahi joined #salt
22:10 UtahDave ah, cool.
22:10 mgw the first question at least
22:10 faldridge joined #salt
22:10 UtahDave mgw: Hey, as you go through the docs it would be awesome if you'd make any improvements you see
22:11 mgw I'll try to find time for that :-)
22:11 UtahDave :) he he.
22:14 aat joined #salt
22:14 berto- joined #salt
22:15 justhamade joined #salt
22:16 kermit joined #salt
22:20 efixit joined #salt
22:21 pcarrier_ joined #salt
22:24 berto- I'm having trouble with the salt mine; i'm getting the master's data for all minions: https://gist.github.com/rca/5646896
22:25 berto- I may be misconfiguring or looping incorrectly, but I'm not sure and wasn't able to find extensive docs.
22:26 aat joined #salt
22:27 UtahDave berto-: what version of salt are you on?
22:28 herlo_ joined #salt
22:29 berto- UtahDave:
22:29 berto- UtahDave: the master and one of the minions is on 0.15.1, 1 of 3 minions is on 0.14.0
22:30 berto- i'm updating the old minion now.
22:30 UtahDave ok, so first of all the salt mine is new in 0.15.0
22:30 UtahDave but let me test here
22:32 berto- yeah, not sure why that one minion was not updated.
22:33 berto- still getting the same behavior on this end, even with all minions on the same version.
22:37 faldridge joined #salt
22:43 oz_akan joined #salt
22:44 efixit joined #salt
22:50 bfig joined #salt
22:53 berto- UtahDave: i added a debug line to mine.update to see what the minion is sending the master and that data looks correct.
22:53 berto- i'm also running a minion on the master; wonder if that has something to do with it.
22:54 jeddi joined #salt
23:09 salticus joined #salt
23:24 bfig joined #salt
23:28 melinath joined #salt
23:43 wilywonka joined #salt
23:44 jdaggett joined #salt
23:51 aat joined #salt
23:53 auser joined #salt

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