Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-09-02

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

All times shown according to UTC.

Time Nick Message
00:00 cmoberg joined #salt
00:06 __number5__ is there any states tree template I can start with?
00:12 ada left #salt
00:13 chrisgilmerproj joined #salt
00:14 forrest __number5__, are you talking specifically about the directory structure?
00:16 __number5__ forrest: yep, more like that, conventions to put what to where, how to organize stuff shared between envs, etc.
00:16 kvt joined #salt
00:16 forrest I assume you want something more complex than the states tutorial?
00:17 __number5__ yep and smaller than the QA states :)
00:17 forrest how about this
00:18 forrest https://github.com/terminalmage/djangocon2013-sls
00:18 forrest terminalmage put that together for djangocon, it's got a few different/new things than other repos with how it does the jinja mapping, but otherwise it has a good directory structure.
00:18 __number5__ forrest: cool, that's what I'm looking for. Thanks
00:19 forrest yea np, the top.sls is kinda simple for that one, but it's easy to expand.
00:24 letterj- joined #salt
00:26 lemao joined #salt
00:30 krissaxton joined #salt
00:32 wolfpack joined #salt
00:35 aat joined #salt
00:51 williamthekid joined #salt
00:55 felixhummel joined #salt
01:08 malinoff joined #salt
01:09 [diecast] joined #salt
01:12 cmoberg joined #salt
01:18 lazyguru joined #salt
01:20 liuyq joined #salt
01:30 krissaxton joined #salt
01:38 oz_akan_ joined #salt
01:48 msheiny joined #salt
02:02 m_george left #salt
02:07 forrest_ joined #salt
02:26 xl joined #salt
02:28 mgw joined #salt
02:31 krissaxton joined #salt
02:38 oz_akan_ joined #salt
02:39 dthom91 joined #salt
02:45 mafrosis joined #salt
02:50 Jack joined #salt
02:53 mafrosis hello! does any one know if there's a global option in salt-cloud to disable parallel execution?
02:53 mafrosis there's many places in there where stuff is run in parallel now, that makes my normal pdb.set_trace() debugging impossible
02:55 forrest_ No idea mafrosis, I haven't touched salt-cloud enough to test that.
02:57 mafrosis thanks for the reply! I can find/replace a few *_parallel calls for their non-parallel sibling, but I was hoping for something.. a little tidier
02:58 forrest_ Yea np, you could try to ping s0undt3ch since he has a ton of commits on salt-cloud, he might know a more elegant way.
02:59 s0undt3ch mafrosis: yep, initial query of the running VMs is done in parallel
03:00 s0undt3ch mafrosis: and no, there's no clean way to disable though right now :|
03:00 mafrosis s0undt3ch: no probs, my hacky find/replace seems to have it sorted
03:01 mafrosis I'm debugging a mutli-region config issue loading the location
03:01 mafrosis I'm trying to setup config to support multiple regions from one setup, and something weird is happening :)
03:01 mafrosis anyway, i'll be back later with a fix!
03:01 s0undt3ch mafrosis: you have to providers in the same file?
03:01 mafrosis thanks for the replies
03:01 s0undt3ch s/to/two/
03:02 mafrosis yes
03:02 s0undt3ch mafrosis: know bug
03:02 mafrosis in cloud.providers
03:02 s0undt3ch mafrosis: but if you fix it! ;)
03:02 mafrosis s0undtech: aha
03:02 mafrosis s0undtech: you mean, you know there's a bug? but not what the bug is?
03:02 s0undt3ch mafrosis: and I've created thaat bug ;)
03:02 s0undt3ch it's my fault!
03:03 s0undt3ch I know what it is, I still haven't found the time to fix it
03:03 mafrosis s0undtech: cos that's what's happening. get_location() will return either one of the locations from the two provider configs
03:03 mafrosis no worries! let me take this one
03:03 s0undt3ch either one?
03:03 s0undt3ch not just the first one?
03:04 mafrosis check it out: http://pastebin.com/PSZR27bW
03:04 forrest_ ahhh Singapore
03:04 mafrosis There are two providers, and running destroy I see prints mixing the locations.
03:05 forrest are you in a colo out there mafrosis?
03:05 mafrosis the machine I'm destroying is in ap-southeast-1
03:06 luminous hello! does either saltstack or another community member host .debs for the last release?
03:06 mafrosis forrest: no colo, but based in australia at present
03:06 forrest mafrosis, ahh ok, that's good, Singapore was the worst DC I ever had to deal with.
03:06 s0undt3ch luminous: yes
03:06 s0undt3ch debian.saltstack.com
03:06 luminous nice
03:07 luminous s0undt3ch: same with ppa?
03:07 s0undt3ch mafrosis: well, I think that you see that because, in order to know where your VM is(which cloud driver, etc), it loads the information from all configured providers looking for it
03:07 s0undt3ch luminous: nah, the ppa is hosted by ubuntu
03:07 mafrosis luminous: http://ppa.launchpad.net/saltstack/salt/ubuntu/pool/main/s/salt/
03:08 luminous interesting, that has 0.15.1 but not .3
03:09 s0undt3ch mafrosis: now, the issue(know bug) is, with which provider is the VM destroyed ;)
03:09 mafrosis s0undt3ch: exactly :)
03:09 s0undt3ch luminous: should have 0.16.3 there
03:10 luminous indeed
03:10 s0undt3ch mafrosis: but the iteration between the providers is normal, though, you have quite a few, I'd expect one per configured provider
03:10 luminous I was looking for last release, but I can work araound this
03:10 luminous thanks :)
03:10 s0undt3ch luminous: 0.16.3 is the last release
03:10 luminous latest stable
03:10 luminous not the last
03:10 luminous s/last/previous
03:11 * luminous shrugs
03:11 lazyguru joined #salt
03:11 s0undt3ch luminous: latest stable is 0.16.3, previous stable was 0.16.2
03:11 s0undt3ch and by latest, I mean the most up to date
03:11 luminous we just think about this differently, it's ok
03:11 luminous 0.15.x versus 0.16.x
03:11 s0undt3ch luminous: :) glad I could help
03:11 s0undt3ch ah!
03:12 s0undt3ch major
03:12 luminous apologies for my lack of clarity
03:12 luminous but those links are still helpful :)
03:12 forrest luminous, I'm checking the version I can install onto my ubuntu machine now, when I installed last night it installed 0.12 for some reason
03:12 s0undt3ch luminous: no worries, we understood each other in the end
03:12 s0undt3ch forrest: you have the ppa setup?
03:13 forrest Yea that's where I pulled from, just updated to 0.16.3
03:13 forrest not sure why it installed 0.12 yesterday *shrug*
03:13 luminous sounds like an apt update would help
03:13 forrest yea I did so
03:13 forrest it installed 0.16.3 just fine, might have been a deps issue or something, not extremely familiar with Ubuntu and how apt works yet, still getting used to it.
03:14 s0undt3ch mafrosis: let me know if I can be of additional help :)
03:14 mafrosis s0undt3ch: thanks dude
03:14 forrest but using the official PPA I'm pulling down 0.16.3 luminous so you should be good
03:14 dthom91 joined #salt
03:14 s0undt3ch mafrosis: nah, Thank You for looking into that one ;)
03:15 UtahDave joined #salt
03:16 forrest Hey UtahDave
03:16 UtahDave hey, forrest!
03:16 forrest Did you already push your family to go to bed? :P
03:18 UtahDave :)  Yep!  my girls are in bed finally
03:20 forrest oh I forgot you guys are an hour ahead
03:21 forrest I thought salt.states.iptables wasn't in untl 0.17?
03:21 forrest *until
03:22 UtahDave forrest: I think it's already in there, it's just not really fine tuned  yet.
03:22 forrest Ahh ok
03:29 littleidea joined #salt
03:31 jinrou joined #salt
03:32 krissaxton joined #salt
03:43 Koma joined #salt
03:46 mwillhite joined #salt
03:54 wolfpack_ joined #salt
03:59 jinrou joined #salt
04:00 xl joined #salt
04:12 aat joined #salt
04:14 baniir joined #salt
04:18 joehh luminous: the 0.15.3 packages are still at debian.saltstack.com, just not hooked into apt
04:19 joehh ie packages back to 0.14.1 under http://debian.saltstack.com/debian/pool/main/s/salt/
04:20 joshe if you're going to realistically manage a nontrivial salt deployment then you're going to have to do your own packaging
04:20 joshe especially if you have multiple distributions
04:22 joehh joshe: interesting point - are you referring to package hosting, because you want to ensure that your "stable" release stays or
04:23 joehh the lack of/delays with packages for some platforms
04:23 joshe there are several reasons to host your own salt packages
04:24 joshe minions and masters are not always compatible across version bumps, so you need to control when those bumps happen
04:25 joshe also, you may need to deploy local fixes for bugs you've encountered which may or may not have been fixed upstream yet
04:30 jinrou joined #salt
04:31 joehh I sort of agree with you, although those skills are probably reasonably rare
04:31 joehh I think the real "fix" is to have better tested releases
04:32 joehh I see it as a downside that any significant deployment needs those skills, but I think you are right
04:32 krissaxton joined #salt
04:33 joehh especially regarding the minion/master compatibility
04:33 joshe sure
04:33 joehh I wonder if the packagers (including me) shouldn't host them in series repositories - ie 0.15.x vs 0.16.x
04:34 joehh so people can chose where they want to sit
04:34 joehh difficulty from my perspective is it blows out the number of repos to manage
04:34 joshe you may be able to get away with it for a while, but eventually you'll have to handle local fixes and/or minion/master incompatibilities
04:35 efixit joined #salt
04:35 joehh true, I see the issue if you are following debian packages - do your initial install at 0.15.2 time and then install a new set of minions a fewmonths later at
04:35 joehh 0.16.3
04:36 joehh I don't know if that is bad from a master/minion comm perspective, but it is definitely not recommended
04:37 joehh I suspect that some documentation on managing this in salt (ie using reprepro in debian/ubuntu) to stabilise through time is worthwhile
04:40 joshe I think that to handle all cases, you're going to need some sort of independent supervisor agent which manages the salt minion, and is able to roll back to an old version if the new version is unable to communicate with the master
04:40 joshe however in practice, this may be unnecessary
04:41 joshe I'm running a very old version of salt, so I may not be the best test case
04:42 aleszoulek joined #salt
04:43 littleidea joined #salt
04:47 joehh yes - most people (except a few vocal ones) seem to be happy enough to move to the newest version on a regular basis (so far)
04:48 dthom91 joined #salt
04:55 Eugene While it's still <1.0 I would stick with the single package
04:56 Eugene Past that, incompatible versions should have a diff package name to prevent break-on-upgrade; see python2 and python3 for a good basis
04:57 Eugene Another good example is gitolite: 1.x --> 2.x upgraded fine, but 3.0 was a total rewrite. So now there's gitolite and gitolite3 in most OS repos
04:57 joshe that would be nice
04:58 Eugene This is largely compatible with Semantic Versioning, in that the X should only change when a backwards-incompatible change occurs. Otherwise, .Y or .Y.Z gets incremented.
04:58 Eugene Which is pretty sane
04:59 joehh I think that is what they try and achieve (except for security issues)
04:59 linjan_ joined #salt
05:00 joehh though some pullrequests/issues are pretty borderline as to wherther they are a feature or a bug
05:00 Eugene Bugture?
05:07 mafrosis left #salt
05:07 joehh yep :)
05:15 jinrou joined #salt
05:17 druonysuse joined #salt
05:17 druonysuse joined #salt
05:19 lemao joined #salt
05:23 malinoff joined #salt
05:26 pcarrier joined #salt
05:26 druonysuse joined #salt
05:28 xmj Could I use the salt master to run on itself?
05:29 xmj As in, set states that configure the master-hosting [jail/server] ?
05:29 aat joined #salt
05:30 middleman_ joined #salt
05:33 krissaxton joined #salt
05:33 Eugene You can run a minion on the same machine as the master, yes.
05:37 gildegoma joined #salt
05:39 xmj isn't that considered *bad* security-wise?
05:44 forrest why would it be xmj?
05:45 Eugene Not that I'm aware of
05:45 xmj forrest: imagine I misconfigure the minion running on master, to fuck up with the master-service and its config.
05:45 forrest but your master lives in it's own section in the top.sls
05:46 forrest lol
05:46 forrest whoops wrong irc window
05:46 littleidea joined #salt
05:47 xmj ok, let's try this.
05:52 mike25ro joined #salt
06:08 dthom91 joined #salt
06:13 xmj ha, i've got a trivial configuration problem
06:13 xmj FreeBSD calls salt's pkg py-salt, but once you install it it inserts 27 [py27-salt]
06:13 xmj how do you account for that in states?
06:16 xmj ^ never mind
06:17 forrest what was the resolution xmj?
06:23 xmj forrest: freebsd ports are called py-salt. once they're compiled, the pkgng system inserts the version-prefix (27)
06:23 xmj so, calling them py27-salt will work fine
06:23 forrest oh so you just renamed the required package
06:24 xmj basically
06:24 vbabiy joined #salt
06:24 dthom91 joined #salt
06:31 xmj now to find out how I can run uwsgi --ini /usr/local/etc/uwsgi.ini ... from the sls
06:34 krissaxton joined #salt
06:37 krissaxton1 joined #salt
06:39 TheCodeAssassin joined #salt
06:40 TheCodeA_ joined #salt
06:48 krissaxton joined #salt
06:53 balboah_ joined #salt
06:56 ronc joined #salt
07:01 Bosse joined #salt
07:08 ml_1 joined #salt
07:08 dthom91 joined #salt
07:10 malinoff_ joined #salt
07:13 Koma joined #salt
07:14 matanya joined #salt
07:15 xmj can I assume that state.highstate will be run after some time?
07:23 krissaxton joined #salt
07:25 Nazca joined #salt
07:25 linjan_ joined #salt
07:30 aleszoulek joined #salt
07:36 Katafalkas joined #salt
07:40 forrest yea it should be picked up
07:43 scott_w joined #salt
07:44 xmj how can I delay the master from /etc/rc.conf ?
07:45 xmj so that it basically only runs state.highstate after, say, 120 seconds?
07:45 forrest I'm not sure.
07:57 yota joined #salt
08:06 ggoZ joined #salt
08:08 ronc joined #salt
08:08 felixhummel joined #salt
08:12 carlos joined #salt
08:13 forrest did you figure that out xmj?
08:17 lemao joined #salt
08:26 zooz joined #salt
08:26 zooz joined #salt
08:27 p3rror joined #salt
08:30 darrend joined #salt
08:34 whiskybar joined #salt
08:36 xmj no, can't try over the next few h
08:40 lemao joined #salt
08:51 MrTango joined #salt
08:53 Nexpro joined #salt
08:57 matanya joined #salt
09:00 jinrou joined #salt
09:05 bhosmer joined #salt
09:09 ProT-0-TypE joined #salt
09:10 ProT-0-TypE joined #salt
09:10 ProT-0-TypE joined #salt
09:11 yota joined #salt
09:11 ProT-0-TypE joined #salt
09:12 ProT-0-TypE joined #salt
09:13 ProT-0-TypE joined #salt
09:17 hazzadous joined #salt
09:21 arapaho joined #salt
09:28 vaxholm_ joined #salt
09:29 liwen joined #salt
09:30 ninkotech joined #salt
09:30 Jason-AVST joined #salt
09:34 ktenney joined #salt
09:37 fredvd joined #salt
10:02 liwen joined #salt
10:07 bogdanbu joined #salt
10:10 bogdanbu hi ! i want to use salt to load a mysql database initial data. any advice ?
10:21 Sypher joined #salt
10:33 jinrou joined #salt
10:35 unicoletti_ joined #salt
10:43 Jason-AVST left #salt
10:43 Jason-AVST joined #salt
10:47 giantlock joined #salt
10:51 Katafalkas joined #salt
10:57 alunduil joined #salt
11:02 tomtomtom joined #salt
11:09 xl left #salt
11:15 jinrou joined #salt
11:16 Katafalkas joined #salt
11:30 abele joined #salt
11:34 stuah joined #salt
11:35 stuah left #salt
11:39 malinoff_ bogdanbu: How would you do that without salt?
11:40 xmj hint: it involves reading the manual ;)
11:40 bogdanbu thanks !
11:54 jinrou joined #salt
12:06 derelm joined #salt
12:08 ninkotech joined #salt
12:13 mgw joined #salt
12:15 Furao joined #salt
12:25 copelco joined #salt
12:28 backjlack joined #salt
12:40 unicoletti left #salt
12:58 Katafalkas joined #salt
12:59 Katafalkas joined #salt
12:59 Katafalkas joined #salt
13:06 racooper joined #salt
13:13 mike25ro left #salt
13:13 welby hey folks, having a few issues with external_pillars. in my master config i've got pillar_roots: base: - /srv/pillar ext_pillar: - cmd_json: "echo {'arg':'value'}" at the moment (obviously with correct yaml syntax), as soon as I add anything in ext_pillar i get a 'dict' object has no attribute 'endswith' error, and the (pillar) top file fails to render, any one have any ideas on this ?
13:13 vaxholm_ joined #salt
13:18 [diecast] joined #salt
13:21 TheCodeAssassin has anybody used quotes ? https://salt.readthedocs.org/en/latest/ref/states/all/salt.states.quota.html
13:25 blee_ joined #salt
13:31 tomeff joined #salt
13:37 felixhummel joined #salt
13:38 Pate_ joined #salt
13:47 Katafalkas joined #salt
13:48 Katafalkas If I would like to write a script, that combines salt and salt-cloud, is it possible to do it in just plain python ? as in import salt, import saltcloud and do stuff there ? is it recommended ?
13:49 p3rror joined #salt
13:51 Pate_ When using salty vagrant to install my base pip requirements, I get the following error from salt with Result=True: "There was no error installing package '' although it does not show when calling 'pip.freeze'"
13:53 xmj Pate_: you installed an empty package?
13:53 xmj magic!
13:57 Pate_ I checked for a blank trailing line in my requirements.txt, but there is none.
14:00 Katafalkas Is salt-cloud API centric just as salt ? I cant seem to find any guides.
14:03 anteaya joined #salt
14:08 vaxholm_ joined #salt
14:13 jinrou joined #salt
14:28 Striki joined #salt
14:28 backjlack joined #salt
14:29 Striki is there a way, when using the virtualenv module, to upgrade pip packages installed by using the requirements argument of the virtualenv.managed method? Doesn't seem like it does give you that options according to this code https://github.com/saltstack/salt/blob/develop/salt/states/virtualenv_mod.py#L143 - however I was wondering if there was another easy way to do it.
14:29 baniir joined #salt
14:38 deepakmd_ joined #salt
14:40 waverider joined #salt
14:44 HaxCore joined #salt
14:46 p3rror joined #salt
14:53 javix_ joined #salt
14:55 javix_ Hi, new to salt here. Is it possible with salt to create a minion (ct) inside another minion (hn) and start the ct and install salt-minion in it/add to available minions with a state? I am using OpenVZ. Or is salt not intended for this sort of tasks? Thanks
14:59 waverider left #salt
14:59 dave_den javix_:  yes, i also use openvz and run minions on HN and inside CTs
14:59 mgw joined #salt
15:01 javix_ @dave_den thanks for answering. How could I learn how to do that? I have been reading the getting started and I don't get how to execute scripts on minions
15:01 javix_ dave_den: thanks for answering. How could I learn how to do that? I have been reading the getting started and I don't get how to execute scripts on minions
15:01 ckao joined #salt
15:02 xmj javix_: you've probably overread it. create a top.sls with some commands in it and run salt '*' state.highstate :)
15:02 hughsaunders javix_: this may be useful: http://docs.saltstack.com/topics/virt/index.html?highlight=salt%20virt
15:03 javix_ ok, thank you. I will read it slowly again. Thanks for the link, too
15:04 mwillhite joined #salt
15:05 logix812 joined #salt
15:07 bkonkle joined #salt
15:10 tuxIO joined #salt
15:14 javix_ dave_den: Could you please guide me a little bit more into Openvz? Should I use libvirt with openvz?
15:15 robertkeizer joined #salt
15:16 dave_den i use custom setup scripts to start my cts
15:16 dave_den i am not sure if salt's virt handles openvz. i think it's only xen/kvm
15:27 jalbretsen joined #salt
15:28 javix_ dave_den: ok, I will dig on custom scripts then. I have some experience using bash for all this, but can't find how to translate the scripts or how to say salt "run this bash script inside that minion"
15:29 javix_ Another issue: I can't install the minion on centos6 because of Requires: kernel-firmware >= 2.6.32-358.18.1.el6            Installed: vzkernel-firmware-2.6.32-042stab079.6.noarch (@openvz-kernel-rhel6)
15:30 javix_ I am using "wget -O - http://bootstrap.saltstack.org | sudo sh"
15:31 dave_den javix_:  the kernel-firmware conflict is a common openvz issue. you can google it
15:31 dave_den javix_: running a script inside a ct from the hn is done with vzctl exec CTID command
15:33 chrisgilmerproj joined #salt
15:36 aat joined #salt
15:37 Jahkeup_ joined #salt
15:40 Katafalkas Is salt-cloud API centric just as salt ? I cant seem to find any guides. Anyone got any examples in github ?
15:41 deepakmd_oc joined #salt
15:42 xmj what about the little documentation here -> http://salt-api.readthedocs.org/en/latest/ ?
15:44 javix_ dave_den: thank you, that is what I was doing before salt  (vzctl exec CTID command), so I stick with this. I'll try to fix the kernel-firmware conflict, thanks.
15:46 Katafalkas This is not exactly what I am looking for. xmj . I would like to write a script combining salt and salt-cloud. I can import salt using salt's python API. I wonder if I can do the same with salt-cloud.
15:47 Katafalkas I assume I am looking for python-api for salt-cloud.
15:47 chrism hrm is there a good way to update salt-minion that doesnt' result in zombie processes everywhere?
15:48 felskrone joined #salt
15:48 dthom91 joined #salt
15:50 binko joined #salt
15:54 littleidea joined #salt
15:54 wolfpack joined #salt
16:10 vaxholm_ joined #salt
16:23 carlos joined #salt
16:26 anteaya joined #salt
16:26 vbabiy joined #salt
16:29 aat joined #salt
16:30 TheCodeAssassin joined #salt
16:32 az87c joined #salt
16:32 az87c_ joined #salt
16:34 vbabiy How can one list all states that the master knows about?
16:34 UtahDave joined #salt
16:36 tuxIO joined #salt
16:39 zonk1024 left #salt
16:40 carmony joined #salt
16:47 bhosmer joined #salt
16:47 ipmb joined #salt
17:01 bdf joined #salt
17:03 binko left #salt
17:06 Katafalkas joined #salt
17:07 jinrou joined #salt
17:08 cmoberg joined #salt
17:08 carmony joined #salt
17:14 juicer2 joined #salt
17:21 eightyeight joined #salt
17:23 kenbolton joined #salt
17:36 baniir when are keys generated
17:36 kenbolton joined #salt
17:38 UtahDave when the minion starts up if will create it's keys if the keys don't exist
17:49 chrisgilmerproj joined #salt
17:50 baniir ok. in a script, i'm attempting to run highstate following an install of salt-minion from ppa but the auth with master is failing
17:55 UtahDave have you accepted the minion's keys on the master?
17:55 baniir they auto accept
17:55 UtahDave what version of Salt?
17:55 TheCodeAssassin joined #salt
17:56 baniir 0.16.3-1precise
17:57 Eugene Yay, 16.3 hit epel.
17:58 UtahDave just in time for 0.16.4 to be released!  :)
17:58 Eugene Heh.
18:00 UtahDave baniir: Have you searched the issue tracker?  I think I remember seeing an open issue with auto_accept
18:01 baniir UtahDave: i have not. looking now...
18:01 UtahDave k
18:03 bhosmer joined #salt
18:08 Dimeetrees joined #salt
18:11 logix812 joined #salt
18:12 baniir UtahDave: of the issues related to auto_accept, this seems most relevant: https://github.com/saltstack/salt/issues/2978 though i'm not using wget | sh install method
18:13 UtahDave baniir: so maybe your script needs to wait a few seconds?
18:17 jinrou joined #salt
18:17 baniir UtahDave: sounds good. i was wondering if the keys should be generated by the end of the apt install, but it looks like i may need to wait. thank you
18:20 matanya joined #salt
18:21 giantlock joined #salt
18:21 UtahDave yeah, once you start up the minion it does take a few seconds for everything to be ready
18:28 Pate_ joined #salt
18:48 LarsN joined #salt
18:53 hazzadous joined #salt
18:55 chrisgilmerproj left #salt
18:57 mafrosis joined #salt
18:57 mwillhite joined #salt
19:01 p3rror joined #salt
19:01 felixhummel joined #salt
19:06 bkonkle joined #salt
19:11 dthom91 joined #salt
19:18 kenbolton joined #salt
19:21 UtahDave joined #salt
19:22 forrest joined #salt
19:24 forrest joined #salt
19:24 xmj right, so let's try this once more
19:25 xmj what do I have to do to make my master tell the minions only after 120 to state.highstate ?
19:27 whiteinge joined #salt
19:29 forrest you never figured that out xmj?
19:30 xmj forrest: uh, i do salt for fun and work in between
19:30 forrest gotcha
19:30 xmj forrest: what i did figure out is ... how to get where I don't need state.highstate to be run after *n seconds
19:31 xmj >don't be a lazy ass and setup wsgi in /etc/rc.conf
19:32 forrest heh
19:32 whiteinge joined #salt
19:32 xmj (i really liked the cmd.run - name: /usr/local/bin/uwsgi -d --ini /usr/local/etc/uwsgi.ini approach)
19:32 xmj :/
19:33 ipmb joined #salt
19:35 whiteinge joined #salt
19:37 UtahDave xmj: I don't quite understand what you're trying to accomplish
19:38 whiskybar joined #salt
19:39 xmj I was going down the shortcut which turned out to take much longer. That's what :)
19:40 kenbolton joined #salt
19:45 UtahDave ok.  :)
19:49 littleidea joined #salt
19:50 whiteinge joined #salt
19:50 hjubal joined #salt
19:50 hjubal joined #salt
19:50 xmj UtahDave: I was looking through sys.doc and couldn't find a uwsgi default config. The FreeBSD rc.d/uwsgi config looked a bit over the top ... soo .. NIH rolled my own.
19:53 ronc joined #salt
19:57 Lue_4911 joined #salt
20:01 kenbolton joined #salt
20:02 whiteinge joined #salt
20:03 xmj are there any ipfw modules?
20:10 kiorky hi, is there an easy way to restart a minion after a configuration change
20:10 kiorky or better, to make it reload it's configuration
20:10 kiorky the use case is to read newly added mysql configuration bits
20:11 kiorky maybe an easier way would be to add pillar based infos mangling for the mysql* module along the config and per-state
20:11 kiorky (_connect_ function)
20:11 kiorky is someone is inspired to answer me ...
20:12 kiorky UtahDave: i saw you participating on some bugs where reading a per-state configuration on github
20:12 kiorky maybe you have an opinion on this
20:12 UtahDave kiorky: you can manage the salt-minion package and the salt-minion config, then have the salt-minion package watch the salt-minion config
20:12 dthom91 joined #salt
20:13 kiorky UtahDave: but restarting it in the middle of a run would make weird thing append isnt it
20:13 kiorky idea is to do that in one state of an hightstate run
20:14 UtahDave maybe set order: last?
20:14 kiorky UtahDave: nope, its not relevant as the idea is: install mysql: set root password: configure databases with the mysql state which need this root password which wasnt there at the minion start
20:15 UtahDave kiorky: Ah, ok. it's a chicken and egg problem!
20:15 UtahDave what os are you using, kiorky?
20:15 kiorky UtahDave: is there a reason not to try to get the info from pillar in the mysql module ?
20:16 UtahDave I think you can.  Isn't the mysql module using config.get?
20:16 kiorky UtahDave: because in the cnnect_ function, it is trivial to add the mysql bits
20:16 kiorky UtahDave: yep it is
20:16 kiorky uhm no
20:16 kiorky wait, i dont remember well
20:16 kiorky was yesterday night ^
20:16 * kiorky looking
20:17 Lue_4911 joined #salt
20:17 robertkeizer joined #salt
20:18 xmj hm
20:18 kiorky sashka_ua:  124             val = __salt__['config.option']('mysql.{0}'.format(name), None)
20:18 kiorky oups, UtahDave sry.
20:19 kiorky UtahDave: but not sure config.option looks in pillar
20:19 UtahDave same as in the minion config
20:19 kiorky it looks in
20:19 UtahDave just make sure that your minion is targeted in the pillar top.sls
20:19 xmj UtahDave: is there any way to add files to rc.conf through salt?
20:20 kiorky UtahDave: will verify, thx !
20:20 UtahDave np, kiorky!
20:20 UtahDave xmj: not sure, is that for services?
20:20 xmj UtahDave: yes
20:20 xmj but, for arbitrary flags
20:20 UtahDave I've only used the service module and state.
20:21 xmj I'd need to set a few of those in lines 11-25 -- http://svnweb.freebsd.org/ports/head/www/uwsgi/files/uwsgi.in?view=markup
20:21 UtahDave I guess you could use a file.managed to put specific files in there.
20:21 xmj Ha. is there a way I can append a file to it?
20:22 matanya joined #salt
20:22 cedwards xmj: what about file.managed and place it in rc.d/uwsgi.conf?
20:23 xmj or that
20:23 xmj wait, isn't that bad style?
20:24 cedwards bad style according to whom? freebsd?
20:24 xmj yes :]
20:25 kiorky UtahDave: grrrr typo
20:25 kiorky UtahDave: was using passord instead of passwd ..
20:26 kiorky *pasword
20:26 kiorky event *password
20:26 cedwards xmj: is /etc/rc.conf.d/uwsgi.conf bad practice?
20:27 * xmj shudders
20:28 xmj /usr/local/etc/uwsgi.conf would be okay practice, but I don't think I can easily source it from rc.conf without appending it there
20:29 cedwards hmm. i generally just use rc.conf.local, and that's simple enough when you just need to enable the service
20:30 cedwards but needing to define multiple options isn't quite as simple with salt i guess
20:31 cedwards file.append might be the best solution..
20:31 Outlander joined #salt
20:35 cedwards that or a prepopulated rc.conf{.local} with everything you need in it
20:36 xmj i'm still configuring things, so that'd be a tad bit impractical
20:37 xmj (plus, I want to have the config as generic and reproducible as possible...
20:39 xmj http://apaste.info/1eKo works like a charm. thanks cedwards :)
20:39 jpadilla joined #salt
20:41 cedwards awesome :)
20:45 matanya_ joined #salt
21:00 littleidea joined #salt
21:18 rachbelaid joined #salt
21:19 robertkeizer joined #salt
21:19 zooz joined #salt
21:20 bkonkle_ joined #salt
21:23 bkonkle joined #salt
21:26 JoAkKiNeN joined #salt
21:32 CheKoLyN joined #salt
21:43 Cubber68 joined #salt
21:43 Cubber68 left #salt
21:54 xmj hmh, wondering: what's the best setup for getting ipfw onto three jails, with all having slightly different ipfw.rules files that need to be deployed?
21:55 forrest You could use the salt mine
21:55 xmj something like creating a common ipfw/init.sls, then ipfw/host1.sls ipfw/host2.sls ?
21:55 forrest yea that could work, jinja templating based on hostname could work as well
21:56 xmj yikes
21:56 forrest you could also base values off the grain data
21:56 xmj I'd be happy with a static one ? :-)
21:56 xmj forrest: mind you, i'm new to all this. templating would be way over the top right now
21:56 forrest it's pretty easy
21:57 forrest but if you wanted it to be static, yea just three different templates for your file or whatever.
21:58 xmj hmh, doesn't have to be
21:58 xmj the general principles what to allow, from which address, to which port, should be the same mostly
21:58 forrest oh yea
21:59 forrest You could use http://docs.saltstack.com/topics/tutorials/states_pt3.html#extend-declaration
22:00 xmj uh, well, i guess i'll do that tomorrow.
22:00 xmj once more i've successfully locked myself out of my ssh =/
22:00 forrest hah
22:01 xmj oh
22:01 xmj it's still working
22:01 xmj surprising.
22:06 Eugene What's the best vim syntax-highlighting language to use for sls? Seems like YAML?
22:06 forrest that's what I use since the sls files are usually yaml.
22:10 bkonkle I use YAML in Sublime, but whenever I do a salt['pillar.get']('key:subkey') the coloring blows up.
22:10 forrest yea I do the same bkonkle
22:10 bkonkle The colon trips up the highlighter.
22:13 littleidea joined #salt
22:14 dthom91 joined #salt
22:18 TheCodeAssassin joined #salt
22:32 _chjohnsthome joined #salt
22:42 xmj forrest: remind me to ask you how to do those templates, to get them minion IPs into sshd_config
22:42 lazyguru joined #salt
22:42 xmj gn8
22:42 forrest bye, check out https://github.com/terminalmage/djangocon2013-sls
22:42 forrest terminalmage made that for a presentation today, it's got some great stuff.
22:43 Eugene It still blows my mind that the apocalypse was last year
22:50 littleidea joined #salt
22:59 hazzadous joined #salt
23:02 littleidea joined #salt
23:17 logix812 joined #salt
23:37 manfred joined #salt
23:38 manfred is there a salt equivalent to chefs knife bootstrap -x root <ip> <bootstrapscript> ? all i can seem to find is makeing it work with vagrant
23:39 manfred so that it would automagically setup the minion to connect to the correct ip addr?
23:39 Eugene That sounds like a command which will connect to a host via SSH, and install / setup chef ?
23:39 manfred Eugene: correct
23:39 aat joined #salt
23:40 manfred and then once it has that, it knows how to connect back to the master server
23:40 Eugene https://github.com/saltstack/salt-bootstrap
23:41 s0undt3ch manfred: salt-cloud using the saltify driver -> http://salt-cloud.readthedocs.org/en/latest/topics/config.html#saltify <- which uses the bootstrap script to setup salt on the remote machine
23:42 s0undt3ch manfred: ie, for existing hosts, saltify
23:42 s0undt3ch or, as Eugene said, ssh to the machine and use the bootstrap script directly
23:42 Eugene I'm sure you can piece together a one-liner to do it
23:42 s0undt3ch in that case you would sill need to configure your monion
23:42 s0undt3ch yes
23:42 Eugene But there isn't one with the salt packages, no.
23:43 manfred ok cool, i think i just missunderstood what exactly saltify did then
23:43 Eugene I'm also not seeing any master= option o nthe bootstrap script; surprising, that.
23:43 s0undt3ch you have several one liners here https://github.com/saltstack/salt-bootstrap
23:43 Eugene So you'll have to sed /etc/salt/minion && service salt-minion restart. ;-)
23:43 s0undt3ch https://github.com/saltstack/salt-bootstrap/blob/develop/bootstrap-salt.sh#L146
23:43 s0undt3ch ah
23:44 Eugene That's to install, not to specify
23:44 s0undt3ch Eugene: yes for that you need to provide your own configuration file
23:44 s0undt3ch and pass -c to the script
23:44 Eugene That works too
23:44 NV is there any way to force refresh gitfs from git?
23:44 s0undt3ch -c /path/to/dir/containing/{master,minion,grains}
23:46 s0undt3ch NV: I know a master restart does that, but that was not what you asked ;)
23:47 NV that should work well enough for my needs
23:47 manfred s0undt3ch: ahh, so saltify does essentially what I want, i just need to manually make a profile file on the master and it will set it up?
23:47 NV if there's no cleaner way anyway
23:47 manfred i think that is what I read...
23:47 s0undt3ch manfred: yes
23:47 manfred awesome
23:47 NV just want to be able to refresh the gitfs after pushing it so i can test my changes go figure
23:47 s0undt3ch manfred: you can also provide partial configuration and the remote minion config will be pre-populated for you
23:48 manfred cool
23:48 manfred ok, i am going to give it a try now
23:48 s0undt3ch NV: if salt does not support it, it deserves a feature ticket
23:48 manfred thanks
23:48 s0undt3ch manfred: Anytime!
23:48 NV mhmm
23:50 NV ugh am i the only one who preferred the old github layout?
23:50 NV where the hell is search on the issues page nowadays
23:52 Katafalkas joined #salt
23:52 forrest I don't think it exists NV
23:53 forrest or at least, I can't find it
23:53 NV turns out it's combined in the search bar at the top now
23:53 NV took longer than i'd like to admit to figure that out...
23:53 forrest Oh I see, that's odd
23:53 NV indeed

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