Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-08-26

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

All times shown according to UTC.

Time Nick Message
00:00 aparsons_ joined #salt
00:00 gzcwnk Ive added a comment to that, I have asked in here, first time I got a reply that made sense.
00:00 gzcwnk thanks
00:02 Ryan_Lane yw
00:04 rojem joined #salt
00:06 dstokes has anyone setup a routine to periodically clean ephemeral minion keys out of the master key list?
00:07 ajolo joined #salt
00:07 aparsons joined #salt
00:07 Ryan_Lane dstokes: I think the ec2 autoscale reactor will do that for you, if you're using that
00:10 dstokes alas, i am not using salt-cloud. really just need to periodically remove old keys. may just use the scheduler
00:10 DrQuest how do you decide the key is no longer in use?
00:11 melinath joined #salt
00:11 Ryan_Lane if you're using cloud services, you can query the cloud to see if the host is no longer running
00:11 Ryan_Lane if it's dead, you can purge its key
00:12 aparsons joined #salt
00:14 aparsons joined #salt
00:15 ndrei joined #salt
00:16 ckao joined #salt
00:16 bhosmer joined #salt
00:17 aparsons joined #salt
00:18 skullone wow, the salt network state is so much easier to use than puppet's
00:18 ckao joined #salt
00:19 mosen yeah im pretty happy with salt states migrating over, skullone :)
00:20 DrQuest I dunno, bash is pretty darn handy ;)
00:20 logix812 joined #salt
00:26 pentabular joined #salt
00:27 dvestal joined #salt
00:34 Gareth skullone: what distributions are you using the network state on?
00:39 aparsons joined #salt
00:39 oz_akan joined #salt
00:41 shalkie joined #salt
00:41 gaker joined #salt
00:47 skullone centos
00:50 Gareth ah okay.  just curious, the centos/redhat stuff works well.  I wrote a good portion of the debian network management module, always curious how it's working for people :)
00:52 n8n joined #salt
00:54 melinath joined #salt
00:56 forrest it works well Gareth
00:58 Gareth forrest: thanks :)  a few bugs remain I suspect, mostly scenarios that haven't been tried yet.
00:59 diegows joined #salt
00:59 * Gareth heads home
01:00 forrest later
01:00 * Gareth waves
01:01 * forrest shakes fist
01:02 aparsons_ joined #salt
01:09 bhosmer joined #salt
01:10 jhauser_ joined #salt
01:11 skullone i think itd be nice to keep tops out of the base environment path
01:12 jchen joined #salt
01:25 jensnockert joined #salt
01:26 scoates joined #salt
01:29 daniel2 joined #salt
01:30 pled76 joined #salt
01:31 vbabiy joined #salt
01:32 ml_1 joined #salt
01:47 pled76 joined #salt
01:48 Outlander joined #salt
01:55 kingel joined #salt
02:03 pled76 joined #salt
02:06 homebody_rlarkin I want to autoscale in ec2 and not use ec2 autoscale groups, and, I have an idea.  I have several applications to deploy in a vpc, each app in it's own defined environment.  Create /srv/salt/$application/_scale <--contains a simple integer index .  Use a script to loop and write a map file , call the script with a cmd.yaml reactor file (and a cmd.yml that updates _scale on events).  Is it a stupid idea?
02:07 manfred why not just use the autoscale groups, and then use the ec2-cloud-reactor with the sns webhooks?
02:08 homebody_rlarkin because one of my (assigned-by-mgmt) directives is to be 'independent' of ec2-only services.
02:08 DrQuest same at my org too homebody_rlarkin
02:08 DrQuest for what it's worth
02:09 homebody_rlarkin Ha.
02:09 manfred homebody_rlarkin: you could use https://github.com/saltstack-formulas/salt-cloud-reactor
02:09 Ryan_Lane homebody_rlarkin: if you were to switch away from amazon to openstack, for instance, you'd be able to use heat to scale
02:09 manfred homebody_rlarkin: and use the salt cloud cache from 2014.7, and scale off of those
02:09 pled76 joined #salt
02:09 homebody_rlarkin hrm
02:09 manfred homebody_rlarkin: yeah, what Ryan_Lane said, heat is completely compatible with cloud formations
02:10 manfred homebody_rlarkin: then you just schedule a salt-cloud -F, every 10 minutes...
02:10 manfred then just build servers with whatever you want
02:10 manfred https://wiki.openstack.org/wiki/Heat
02:10 manfred A native Heat template format is evolving, but Heat also endeavours to provide compatibility with the AWS CloudFormation template format,
02:11 manfred \o/
02:11 manfred available at rackspace
02:12 Ryan_Lane meh cloudformation. I prefer using salt for my infrastructure definitions over cloud formation :)
02:12 Ryan_Lane but I definitely use autoscaling
02:13 manfred Ryan_Lane: we are putting heat between otter (our autoscale group stuff) and nova (the stuff that builds the servers)
02:13 manfred Ryan_Lane: there is a blueprint for it somewhere
02:13 DrQuest the scale of work that needed to be done, and still needs to be done to manage a single web application on aws with salt is a little daunting
02:13 manfred to add callbacks in the heat formation stuff, so that you can do a call back like you do with amazon's sns messages
02:13 Ryan_Lane DrQuest: it's not so bad
02:13 DrQuest though that may be because of architectural decisions having to do with the application
02:14 Ryan_Lane I have a blog post that I may post tomorrow that shows how
02:14 DrQuest I've been working on it fairly regularly since april
02:14 homebody_rlarkin do you have an opinion on 'starting from 0' , the idea I mentioned above vs. ramping up on scalinggroups? Basically the only thing left to write is the scaling.
02:14 DrQuest and we aren't even at the point where we can incorporate scaling
02:15 aparsons joined #salt
02:15 rawzone joined #salt
02:15 toddnni joined #salt
02:15 aberdine joined #salt
02:15 jab416171 joined #salt
02:15 homelinen joined #salt
02:15 kalessin joined #salt
02:15 Ryan_Lane 207 lines of salt code will: create 2 security groups, 2 sqs queues, an ELB, a launch config with cloud-init scripts, an autoscaling group (with scaling policies) and two cloudwatch alarms (for scaling policies)
02:16 DrQuest that's not the hard part
02:16 * Ryan_Lane just counted the lines used in his blog post :)
02:16 DrQuest ^_^ 100 lines of python will do that ;)
02:16 Ryan_Lane 100 lines of python won't do that in an idempotent way
02:17 Ryan_Lane oh, it's another 15 lines for VPC support
02:17 Ryan_Lane heh
02:17 DrQuest I'm pulling your leg a little on that.  The hard part is communicating to the developers, I need clear, concise definitions of what each of your servers do, and what you require for them to do
02:17 Ryan_Lane ah, yeah, that's what we're using this for
02:17 Ryan_Lane devs can maintain their own definitions in their own repos
02:18 DrQuest mm, I'm slowly leading them to writing their own formulas.
02:18 DrQuest and one day I'll just quietly hand it off
02:18 Ryan_Lane heh
02:19 Ryan_Lane we have something that'll take a heroku procfile and spit out salt definitions for aws resources and config management
02:19 slashdot joined #salt
02:19 DrQuest we're not even close to that kind of nifty ness
02:19 DrQuest but it sounds nice
02:20 Ryan_Lane that's actually pretty simple, assuming you're using the boto_* states, since heroku services are pretty easy to replicate (sec group, elb, launch config, autoscale group per app in procfile)
02:20 homebody_rlarkin we have several apps to deploy and everything is abstracted so that devs can create new apps without cooperation from ops and everything 'just works' by following convention.  all devs work in a VM managed by the same salt stack as production.  the idea I was thinking of supports that convention, so 'new applications' get scaling support out of the gate.  been the plan for months, and now, just as I'm about to write it, I wa
02:21 DrQuest mm, let me rephrase, before I joined the team, every single environment was being built one server at a time, by hand in AWS
02:21 homebody_rlarkin 'Stedder! I have a doubt.'
02:22 DrQuest you'd ssh into the box, list out all the requirements, install them, hand it to the dev for multiple days of testing and then move onto the next box
02:23 homebody_rlarkin ugh.
02:23 DrQuest multiply by 6, as they wanted a dev/qa/prod environment and redundancy within each ;)
02:23 aparsons joined #salt
02:23 DrQuest we're working it out, slowly but surely
02:26 pled76_ joined #salt
02:26 Ryan_Lane heh, indeed
02:26 homebody_rlarkin https://github.com/saltstack-formulas/salt-cloud-reactor  <- I don't see a reference to ec2 scaling groups.  intrigued and confused.
02:26 manfred you don't need them for that
02:26 manfred instead you use the salt-cloud cache for that
02:27 homebody_rlarkin I see.  No, I don't.  I will see.
02:27 manfred http://docs.saltstack.com/en/latest/topics/cloud/misc.html#salt-cloud-cache
02:27 aparsons joined #salt
02:27 manfred the salt cloud cache fires off events on new nodes, and when nodes change
02:29 sroegner__ joined #salt
02:29 homebody_rlarkin DrQuest: what I did was make a convention : app_env-app_name-app_branch , we built conventions around those three dimensions as abstract as possible.  it looks like it's going to scale (number of apps and environments) very well.
02:30 * homebody_rlarkin gets his read on...
02:30 DrQuest often times the biggest challenges are not technical in nature ^_^
02:30 DrQuest enjoy
02:30 homebody_rlarkin yep
02:37 jab416171 joined #salt
02:38 mordonez_ joined #salt
02:39 malinoff joined #salt
02:42 aparsons_ joined #salt
02:44 schimmy joined #salt
02:48 schimmy1 joined #salt
02:51 jab416171 joined #salt
02:51 ramishra joined #salt
02:53 csa joined #salt
02:55 pclermont joined #salt
02:56 kelseelynn joined #salt
02:56 kelseelynn left #salt
02:58 bhosmer joined #salt
02:58 pled76 joined #salt
03:05 pled76 joined #salt
03:11 ramishra joined #salt
03:14 ajolo joined #salt
03:18 xcbt joined #salt
03:22 KyleG joined #salt
03:22 KyleG joined #salt
03:26 jensnockert joined #salt
03:28 pled76_ joined #salt
03:33 ml_1 joined #salt
03:35 ramishra joined #salt
03:37 jab416171 joined #salt
03:40 kelseelynn joined #salt
03:43 kingel joined #salt
03:53 tac joined #salt
04:01 xcbt joined #salt
04:04 dvestal joined #salt
04:05 mosen joined #salt
04:11 aquinas_ joined #salt
04:11 pentabular joined #salt
04:12 pentabular1 joined #salt
04:21 thayne joined #salt
04:22 pled76 joined #salt
04:28 wigit joined #salt
04:29 sroegner__ joined #salt
04:33 icebourg joined #salt
04:43 bezeee joined #salt
04:44 xcbt joined #salt
04:46 msciciel joined #salt
04:47 bhosmer joined #salt
04:50 rojem joined #salt
04:50 ramishra joined #salt
04:52 felskrone joined #salt
04:54 pled76 joined #salt
05:04 pled76 joined #salt
05:11 pled76 joined #salt
05:16 n8n joined #salt
05:16 bhosmer joined #salt
05:22 Sauvin joined #salt
05:23 kelseelynn joined #salt
05:27 jensnockert joined #salt
05:29 calvinh joined #salt
05:30 pled76 joined #salt
05:32 kingel joined #salt
05:33 papabalyo joined #salt
05:35 alicesmith2013 joined #salt
05:35 alicesmith2013 hello
05:37 papabalyo hi there. Just started with Salt, absorbing information :)
05:38 mosen hiya
05:38 papabalyo I was breaking my Salt setup several times while going through tutorial, so I've created a simple Vagrant setup to experiment: https://github.com/kishanov/salt-playground
05:38 mosen me too
05:39 papabalyo if somebody has done something similar, I would appreciate suggestions/corrections on how to run Salt inside VMs (not through Vagrant provisioning mechanism, don't want to involve host machine)
05:40 mosen not using pillars from vagrant?
05:41 dccc__ joined #salt
05:42 DrQuest salty vagrant seems to be a thing
05:42 DrQuest but that's all I know
05:42 DrQuest ciao
05:42 DrQuest left #salt
05:42 mosen as far as i can see, that was merged into vagrant
05:43 mosen similar to the puppet provisioning
05:43 ramishra joined #salt
05:45 calvinh joined #salt
05:45 martoss joined #salt
05:45 papabalyo yes, I saw that but I wanted something different. I don't want to pollute my host OS with Salt Master stuff while I'm learning so I want to have a completely isolated env with Salt Master also in a VM
05:46 calvinh_ joined #salt
05:46 papabalyo I'm looking for best practices for this setup, if any. otherwise I'll just continue digging through docs and breaking/reinstantiating my VMs :)
05:48 mosen oh right
05:48 mosen other than manually starting a master vm and minion vm
05:48 mosen I don't know
05:48 mosen even kitchen-salt calls salt-call
05:49 mosen most of the testing stuff seems to be masterless
05:59 tcotav fwiw -- I do most of my dev masterless on a vm
06:00 and joined #salt
06:03 pled76 joined #salt
06:05 tcotav papabalyo: one thing you could add would be vm.synced_folders for both your srv/salt and srv/pillar
06:07 cym3try joined #salt
06:11 ngo joined #salt
06:13 roolo joined #salt
06:23 jensnockert joined #salt
06:23 mechanicalduck joined #salt
06:30 ramishra joined #salt
06:30 sroegner__ joined #salt
06:34 bmcorser joined #salt
06:35 bhosmer joined #salt
06:38 catpigger joined #salt
06:44 Daemonik joined #salt
06:48 Katafalkas joined #salt
06:48 TyrfingMjolnir joined #salt
06:48 MK_FG joined #salt
06:51 pled76 joined #salt
06:51 Ryan_Lane joined #salt
06:57 jdmf joined #salt
06:58 felskrone joined #salt
07:03 felskrone joined #salt
07:04 ml_1 joined #salt
07:05 lcavassa joined #salt
07:08 aw110f joined #salt
07:11 aw110f_ joined #salt
07:11 dbanck joined #salt
07:16 kelseelynn joined #salt
07:21 kingel joined #salt
07:21 pled76 joined #salt
07:23 slav0nic joined #salt
07:23 slav0nic joined #salt
07:34 mechanicalduck joined #salt
07:37 intellix joined #salt
07:41 malinoff joined #salt
07:46 Daviey joined #salt
07:46 qq1378005101 joined #salt
07:50 darkelda joined #salt
07:56 chiui joined #salt
08:06 linjan joined #salt
08:07 mechanicalduck joined #salt
08:08 pled76 joined #salt
08:13 jhauser joined #salt
08:13 ngo ping
08:16 Jin__ joined #salt
08:17 pled76 joined #salt
08:22 kingel joined #salt
08:24 bhosmer joined #salt
08:26 chiui joined #salt
08:26 Katafalkas joined #salt
08:27 Ossoleil joined #salt
08:31 sroegner__ joined #salt
08:33 intellix joined #salt
08:36 deepz88 joined #salt
08:38 deepz88 joined #salt
08:42 t0ku joined #salt
08:43 albertid joined #salt
08:44 albertid Hi, would something like "- identity: salt://identities/my_id_rsa" make sense in git state? I think it would be useful, should I open an issue for that?
08:45 albertid Currently, you have to provide a path on the fs
08:46 deepz88 joined #salt
08:55 pressureman joined #salt
08:59 MrTango joined #salt
09:00 pled76 joined #salt
09:06 blackhelmethacke joined #salt
09:08 ndrei joined #salt
09:08 kingel joined #salt
09:17 TheThing joined #salt
09:19 che-arne joined #salt
09:19 TheThing_ joined #salt
09:26 Eliz joined #salt
09:27 intellix joined #salt
09:27 chiui joined #salt
09:30 calvinh joined #salt
09:31 calvinh_ joined #salt
09:42 yomilk joined #salt
09:48 dudaros joined #salt
09:48 dudaros hi guys
09:48 dudaros greetings from Greece
09:48 dudaros quick question:
09:48 dudaros file.managed:
09:48 dudaros - source:
09:48 malinoff dudaros, http://pastie.org
09:49 dudaros could the source on file.managed be from the minion or does it has to be on the salt-master folder?
09:50 malinoff dudaros, you can't specify a minion there, but you can pull file from minion at first to the master and then specify master folder
09:51 dudaros malinoff  thanks for the reply
09:52 dudaros so this   http://pastie.org/9503730
09:52 dudaros is not possible
09:53 dudaros ?
09:53 malinoff Is 'source' a remote directory?
09:54 dudaros yes, its a specific location on the minion
09:55 malinoff dudaros, nope, it's not possible
09:56 dudaros thing is, i am downloading a daemon service from source, install it and then want to use the config sample which comes from the package
09:56 dudaros ok i can do that with run.cmd
09:56 dudaros but then i have to add an extra file.managed
09:56 dudaros so i can be able to restart the service whenever there is a change on that file
09:57 malinoff dudaros, you can't manage unmanaged content. You should put the sample to the master and configure your daemon with it
09:57 dudaros roger
09:57 dudaros thanks
09:57 dudaros :-)
09:59 Eliz joined #salt
10:01 calvinh joined #salt
10:01 Daemonik joined #salt
10:03 dudaros one more thing
10:03 dudaros what happens when i cmd.run and the process after a while requires a user input in order to complete?
10:04 malinoff dudaros, the process hangs :)
10:05 malinoff dudaros, for now you can wrap your commands to expect scripts
10:06 dudaros kk
10:06 dudaros noted
10:06 pled76 joined #salt
10:06 wedgie joined #salt
10:06 wedgie joined #salt
10:07 snuffeluffegus joined #salt
10:12 lyddonb joined #salt
10:13 bhosmer joined #salt
10:14 Katafalkas joined #salt
10:14 yomilk joined #salt
10:14 CeBe joined #salt
10:14 Nexpro joined #salt
10:25 ndrei joined #salt
10:32 sroegner__ joined #salt
10:34 bhosmer joined #salt
10:40 Skos joined #salt
10:41 Skos Hi all
10:41 Skos how can I use static pillars in ext_pillar function ?
10:41 Skos in 'pillar' func param there is an empty dict
10:43 floWenoL Rendering SLS "base:haproxy" failed: Unknown yaml render error; line 17
10:43 floWenoL - name: /etc/default/haproxy    <=====================
10:43 floWenoL any clue
10:43 floWenoL looks ok to me
10:46 Outlander joined #salt
10:46 floWenoL nvm
10:46 floWenoL just rewrote it
10:50 iMil joined #salt
10:53 ramishra joined #salt
10:55 calvinh_ joined #salt
10:59 babilen Skos: Could you provide a bit more context?
11:05 vbabiy joined #salt
11:08 masterkorp hello
11:08 ndrei joined #salt
11:09 jeddi joined #salt
11:11 Skos ok, actually I want to use pillars provided from command line to determine behaviour in ext_pillar function
11:12 mechanicalduck_ joined #salt
11:12 Skos now I can see that I finally have an access to static pillars in external pillars (ext_pillar func), but have no access to pillars provided from command line during state.sls execution
11:13 Skos example: when I run:    salt '*' state.sls _myproject.deploy PROD pillar='{"environment": "PROD", "project": "my_project"}'
11:13 Skos ...I wanted to have access in ext_pillar() function to those two additional pillars ('environment' and 'project')
11:14 Ganesan joined #salt
11:14 TyrfingMjolnir joined #salt
11:19 Outlander joined #salt
11:22 sectionme joined #salt
11:26 ramteid joined #salt
11:36 intellix joined #salt
11:37 floWenoL how can I import an sls, and then require some of the ids on that sls
11:37 floWenoL i tried include but then i cant require those ids
11:37 floWenoL and the included file does not seem to be run
11:42 pled76 joined #salt
11:48 Katafalkas joined #salt
11:48 diegows joined #salt
11:48 albertid floWenoL, did you use -include or {% include %} ? Try {% include %}
11:55 pdayton joined #salt
12:01 omio joined #salt
12:02 floWenoL i was doing
12:02 floWenoL include: - wildfly.wildfly
12:02 floWenoL with line break after :
12:02 mechanicalduck joined #salt
12:02 bhosmer joined #salt
12:07 mechanicalduck_ joined #salt
12:11 nyx_ joined #salt
12:12 totte joined #salt
12:13 Skos ohhh.. it seems that pillars provided from command line are added after calculation of static+ext pillars
12:13 midacts joined #salt
12:14 jslatts joined #salt
12:16 pclermont joined #salt
12:16 albertid floWenoL, maybe try to {% include %} it via jinja2 ?
12:23 AlecTaylor joined #salt
12:23 AlecTaylor hi
12:23 AlecTaylor Which SaaS solution would you recommend for agile team+project management? :)
12:25 mechanicalduck joined #salt
12:26 17SAAZ5I0 joined #salt
12:29 dccc__ joined #salt
12:29 www joined #salt
12:33 sroegner__ joined #salt
12:35 hobakill joined #salt
12:40 systmp joined #salt
12:41 mordonez_ joined #salt
12:41 freeminds joined #salt
12:41 bhosmer joined #salt
12:41 systmp Hi, what's the best way to have my minions automatically run commands when connected to the salt master? Or the other way around. I have a base-sls which I want to always apply when minions are connected.
12:42 systmp like.. if minion == connected then run salt 'host'
12:42 systmp sls
12:42 vmdsch joined #salt
12:45 oz_akan joined #salt
12:46 ekristen joined #salt
12:46 mechanicalduck joined #salt
12:47 ndrei joined #salt
12:49 adilroot joined #salt
12:54 xmj AlecTaylor: let me know once you find something out.
12:55 vbabiy joined #salt
12:56 pdayton1 joined #salt
12:56 TheThing joined #salt
12:57 istram joined #salt
12:57 adilroot Hi Salt community
12:57 sroegner__ joined #salt
12:57 adilroot does salt-cloud support creating an amazon rds instance for postgresql?
12:58 miqui joined #salt
12:59 systmp I want to automate the salt minion to execute a state.highstate call once it's connected to the master server. Any idea on how to do this?
12:59 manfred systmp: yes, startup_states: highstate
12:59 manfred http://docs.saltstack.com/en/latest/ref/states/startup.html
12:59 cpowell joined #salt
13:00 pclermont joined #salt
13:01 ndrei joined #salt
13:03 6A4AAF7XN joined #salt
13:03 racooper joined #salt
13:03 systmp manfred: perfect, thanks!
13:03 blarghmatey joined #salt
13:03 thayne joined #salt
13:04 racooper joined #salt
13:05 ipmb joined #salt
13:05 blarghmatey joined #salt
13:06 albertid_ joined #salt
13:07 mhubbard joined #salt
13:08 FeatherKing joined #salt
13:08 intellix joined #salt
13:11 pdayton joined #salt
13:14 ndrei joined #salt
13:21 mpanetta joined #salt
13:24 nyx joined #salt
13:24 t0ku how do you usually debug salt states? I mean, if you have a jinja for loop or if condition, how do you verify that it jumped in there or to see a variable currently processed by the for loop? placing an echo "jumped in" or echo variable would be the way i do this in bash or python (print) …
13:25 pled76 joined #salt
13:26 mapu joined #salt
13:28 dude051 joined #salt
13:39 manfred t0ku: states.show_highstate
13:39 manfred states.show_sls
13:40 manfred and states.show_low_state
13:40 manfred those show states help you see that jinja gets  rendered
13:40 manfred http://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.state.html
13:40 PI-Lloyd joined #salt
13:41 toastedpenguin joined #salt
13:41 bezeee joined #salt
13:42 ndrei joined #salt
13:42 calvinh joined #salt
13:43 PI-Lloyd Hi, I'm trying to setup gitfs on a new master, however I only want it to use the master branch of the repo as the repo is not setup in the conventional way with environments. For example there is a branch for creating the states, which is pulled by jenkins, tested, then jenkins pushes to master. Is there a way around this without rebuilding the repo?
13:45 manfred PI-Lloyd: salt could use any branch in gitfs by setting the saltenv, by default the base environment maps to the master branch though
13:46 PI-Lloyd hmm, i gave that a go however it's still trying to pull the pre-testing branch and serving that up as another env. Maybe I'm just having a massive brain fart and not seeing the mistake, I will play around some more then.
13:47 t0ku @manfred: thanks a ton!
13:47 manfred PI-Lloyd: it might do that, and try to render every branch into salt data... that part i do not know
13:48 istram PI-Lloyd: there are some problems with gitfs, be sure to check all the logs in debug
13:49 manfred ^^
13:49 PI-Lloyd all I know is, it's driving me flippin loopy trying to figure it out! :p
13:50 istram PI-Lloyd: enjoy that :) my colleague have actually tried to make a multi-repo multi-branch setup working for us.
13:51 PI-Lloyd istram: they get it working or end up beating their head against a wall and giving up?
13:52 t0ku @manfred: I get 'states.show_state' is not available for each of these - any hints?
13:52 t0ku ah wait, … state.xxxx (remove the s….)
13:52 t0ku works
13:52 manfred t0ku: check the docs page.
13:52 manfred yeah
13:53 t0ku was not obvious at first sight ;)
13:53 istram PI-Lloyd: he rewrote some parts of the module, spent few weeks debugging it and in the end we rather decided  to ditch it.
13:54 dvestal joined #salt
13:55 midacts Has anyone here had problems where salt-minions are unresponsive until you restart the salt-minion service? (it seems to happen on a daily basis, but the salt-minion service is running)
13:56 calvinh_ joined #salt
13:56 berserk joined #salt
13:57 kermit joined #salt
13:58 ndrei joined #salt
13:58 dvestal joined #salt
13:59 yidhra joined #salt
14:01 quickdry21 joined #salt
14:02 penguin_dan joined #salt
14:03 kingel_ joined #salt
14:04 wendall911 joined #salt
14:08 j-saturne joined #salt
14:09 intellix joined #salt
14:10 kingel_ joined #salt
14:14 bhosmer_ joined #salt
14:17 pled76 joined #salt
14:19 aquinas_ joined #salt
14:22 PI-Lloyd ugh, starting to getting really narked off with this gitfs nonsense :/ There has to be an easier way of doing this surely....
14:22 sectionme joined #salt
14:23 mapu_ joined #salt
14:30 dude051 joined #salt
14:30 rojem joined #salt
14:30 SheetiS joined #salt
14:31 dude051 joined #salt
14:31 Katafalkas joined #salt
14:33 rojem joined #salt
14:34 SheetiS1 joined #salt
14:35 t0ku left #salt
14:37 Ozack1 joined #salt
14:37 mechanicalduck_ joined #salt
14:38 gokr joined #salt
14:38 jeffrubic joined #salt
14:39 TheThing joined #salt
14:43 smcquay joined #salt
14:45 tmh1999 joined #salt
14:46 gokr I am getting so sick of chef. Anyone here made the switch?
14:46 gokr Juts curious about pros/cons. One thing that I guess salt does better is larger files.
14:49 istram gokr: you get pros/cons everywhere
14:49 conan_the_destro joined #salt
14:50 istram gokr: haven't made the "switch" so just general things: salt is really young and there are loads of bugs, sometimes regressions, multimaster (HA) had problems...
14:51 ipmb joined #salt
14:52 CheKoLyN joined #salt
14:53 giannello joined #salt
14:55 gokr Chef is pushed by a company to a fairly large extent it seems - is salt slightly more community driven or is that just something I imagined?
14:56 Kakwa joined #salt
14:57 babilen istram: It is incredibly active with all the positive and negative things that are associated with that :)
14:58 istram babilen: just sayin' :) I like it more this way too... I even have the opportunity to test my rpmbuild-fu skills
14:59 felskrone joined #salt
15:00 calvinh joined #salt
15:00 istram gokr: you can check the github. as more or less every FOS project nowadays it has it's company but the community is active with salt.
15:01 schimmy joined #salt
15:01 icebourg joined #salt
15:02 icebourg joined #salt
15:03 luminous joined #salt
15:03 schimmy1 joined #salt
15:03 icebourg joined #salt
15:04 luminous gokr: even with the bugs and regressions, I highly recommend salt over puppet/chef - you'll be far more productive. This is especially true if you know python. But in the end, this is all dependent on what you want to do really
15:04 luminous gokr: you'll get better answers if you are more clear about what your needs and usecases are
15:05 rallytime joined #salt
15:05 rojem joined #salt
15:05 luminous gokr: full disclosure: I've never really used chef, I could not get past all the ruby everywhere. I did use puppet for a few years before throwing that all in the garbage for salt instead. It only took me 2 weeks to recreate (in salt) what I had in puppet
15:07 dude051 joined #salt
15:07 luminous gokr: if you want pros/cons, overall pro: Salt is flexible in ways that matter. Overall con: salt development likes features before code quality, and new releases often include regressions. I generally stick with a release that I know works (I'm still on v0.17.x) before moving to the latest and greatest.
15:08 geekmush joined #salt
15:08 luminous another con is that salt likes to experiment, so sometimes concepts and implementations are confusing.. modules/states, and grains/pillar are good examples
15:09 luminous but it still puts the rest to shame, honestly
15:09 * luminous end "salt is awesome" lecture
15:09 mechanicalduck joined #salt
15:12 aparsons joined #salt
15:13 abe_music joined #salt
15:14 delinquentme joined #salt
15:17 istram yeah, based on what luminous said - python really was a big + for salt when we were deciding.
15:18 nlb joined #salt
15:18 pled76 joined #salt
15:19 luminous if you know and work with python, you can make salt do pretty much anything
15:19 * istram thinks ruby is meh and sysadmins are more likely to know python from my experience
15:20 gokr luminous: Sorry, was out getting pizzas :)
15:20 wangofett joined #salt
15:20 gokr Thanks for the info
15:20 gokr We have used chef now for ... some time, and it seems to me to be over engineered, at least for us.
15:21 wangofett Documentation about windows minions is pretty sparse... naturally :) I do have a question though - does package management work, or do I need to roll my own?
15:21 gokr What I have read so far on salt would fit us much better. Python or Ruby doesn't matter much for us, although Python is a better fit since we have it in our product.
15:21 wangofett e.g. use Choclatey or otherwise use cmd.run
15:21 foxx joined #salt
15:21 luminous wangofett: it works, not sure how, but there's a bunch that can be done
15:21 foxx anyone have any idea what this means in salt?? TypeError encountered executing state.highstate: object of type 'ConstructorError
15:21 foxx uhh: 2014-08-26 15:21:18,364 [salt.minion      ][WARNING ] TypeError encountered executing state.highstate: object of type 'ConstructorError' has no len(). See debug log for more info.  Possibly a missing arguments issue:  ArgSpec(args=['test', 'queue'], varargs=None, keywords='kwargs', defaults=(None, False))
15:21 luminous gokr: what do you actually want salt to do for you?
15:22 luminous foxx: --log-level=debug tell you anything helpful?
15:22 wangofett luminous: any clue where I'd look for more info - mainly to get the names of packages
15:22 luminous wangofett: no idea, I refuse to touch windows ever again
15:22 foxx luminous: silly question but, where would i put --log-level=debug - on the salt sync?
15:22 luminous sorry
15:22 gokr luminous: Well, we have a fairly complicated system so basically its the installation process of all that on Linux boxes (one or more).
15:23 gokr And also cloud control in general.
15:23 luminous foxx: salt-call foo.bar --log-level=debug
15:23 luminous foxx: it's a command line argument
15:23 foxx ohh, lets see
15:23 foxx Passed invalid arguments: can't serialize ConstructorError()
15:23 luminous gokr: clound control in salt is pretty awesome. it's got deficiencies, but you can work around them pretty easily
15:23 foxx nothing else shown
15:23 gokr One thing I wonder about is shell scripts - you seem to maintain them separately from sls files, and... well, I kinda liked inlining them in the chef recipes.
15:23 luminous foxx: what are you running?
15:23 foxx seems to be something to do with the serialization
15:23 foxx File "/usr/lib/pymodules/python2.7/salt/payload.py", line 149, in dumps
15:23 foxx return msgpack.dumps(odict_encoder(msg))
15:24 foxx luminous: salt-minion 2014.1.10 (Hydrogen)
15:24 * gokr off to eat
15:24 luminous gokr: you can inline stuff in salt, see the file.managed state and contents (and pillar_contents?) args
15:24 mechanicalduck_ joined #salt
15:24 foxx both minion and master are running the same ver
15:24 luminous gokr: you'd need to be more clear about what your install process is like if you want more input, but overall it sounds like you'll be happier
15:24 Ahlee anybody noticed (or know if it's by design) that only the first listed file_root for an environment is checked for _returners, _states, _modules etc?
15:24 luminous foxx: what are you doing?
15:25 foxx luminous: jsut running state.highstate :X
15:25 luminous Ahlee: that would be interesting
15:25 luminous Ahlee: can you reproduce that on a clean host?
15:25 luminous foxx: can you run state.sls with something or simplify top.sls to get somewhere?
15:25 Ahlee eventually, sure.
15:25 foxx sure sec
15:26 Ahlee I'll spin up a fresh 0.17.5, 2014.1.10, and develop when possible
15:27 ajolo joined #salt
15:30 kingel joined #salt
15:32 foxx luminous: wow, okay yeah so it seems to be if i structure my top.sls in a specific way
15:32 foxx id need to reproduce this in a clean env to report
15:32 luminous you might be goofing up tops.sls
15:32 foxx well, this works:
15:32 foxx 'sa1,web10,web11':
15:32 foxx but this doesnt:
15:32 foxx 'web10,web11':
15:32 foxx lol
15:33 foxx the latter results in that error i pasted earlier
15:33 luminous weird
15:33 foxx the former results in success :X
15:33 luminous try web[10-11] or other variants?
15:33 luminous I don't do that type of thing in top.sls
15:33 foxx lemme try now, whats the match type for that?
15:33 luminous I'm making it up, look at the docs :)
15:33 foxx ahahah, ksec
15:33 dude051 joined #salt
15:35 foxx k this works fine:
15:35 foxx '^web(10|11)':
15:35 foxx - match: pcre
15:35 wangofett for anyone curious about salt pkg on windows https://github.com/saltstack/salt/blob/2014.7/salt/modules/win_pkg.py looks like the relevant file
15:36 UtahDave joined #salt
15:37 wangofett ah. http://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.win_repo.html Looks like there is a salt winrepo that has packages
15:39 aberdine joined #salt
15:40 wangofett http://docs.saltstack.com/en/latest/topics/windows/windows-package-manager.html I think that's what I was looking for
15:41 wangofett Yep, exactly it.
15:42 dvestal joined #salt
15:42 pled76 joined #salt
15:45 yomilk joined #salt
15:48 luminous wangofett: awesome! good luck
15:48 t0rrant joined #salt
15:48 luminous foxx: looks good!
15:49 t0rrant joined #salt
15:49 wangofett luminous: thanks! Now that I found the right document it looks surprisingly straight forward. Has salt managed to *gasp* make installing softwares on Windows less than painful??? ;)
15:49 thayne joined #salt
15:49 luminous it has, though it doesn't make windows all that much less painful
15:49 * Sp00n rolls his eyes
15:49 luminous at least you can automate all the basics
15:50 omio joined #salt
15:50 wangofett quite so. And maybe as important - it's repeatable.
15:50 luminous :)
15:52 j-saturne joined #salt
15:52 smcquay joined #salt
15:55 babilen luminous: [10-11] doesn't work, you'd want 1[0-1]
15:55 xcbt joined #salt
15:55 luminous and match: pcre I assume
15:55 KyleG joined #salt
15:55 KyleG joined #salt
15:55 luminous I referred foxx to docs for that reason - I don't use pcre/match in top.sls
15:58 ndrei joined #salt
15:58 KyleG joined #salt
15:58 KyleG joined #salt
15:59 UtahDave wangofett: Let me know if you have any issues with the Windows stuff!
15:59 beneggett joined #salt
16:00 FeatherKing UtahDave: i did a little more digging on running from a UNC path
16:01 UtahDave FeatherKing: what did you figure out?
16:01 wangofett UtahDave: sure will, thanks. Looks pretty straight forward now that I found the documentation. Not sure, but might be an opportunity to improve the documentation for the less persistent individuals ;)
16:02 UtahDave wangofett: Yeah, please let me know if there are any doc improvements you'd suggest as you go through
16:02 UtahDave all the docs are in the salt repo and we can update them with just a pull request
16:02 FeatherKing UtahDave: if i run salt in debug mode salt will actually run correctly from a unc path, however the minion as a service will always fail on the unc path. i set the service to "allow service to interact with desktop" and still it wont find the path
16:03 FeatherKing however salt as a service running the file from the desktop works
16:03 FeatherKing salt as a service and unc path no worky
16:03 FeatherKing unless debug mode?
16:03 FeatherKing weird
16:05 t0rrant joined #salt
16:05 ekristen is there a way to have a state on server A trigger an event so that a state on server B will run after it is done?
16:06 armonge joined #salt
16:06 UtahDave FeatherKing: That is weird.  If you want to open an issue for that, I'll take a look at it as soon as I get a chance.  please include any info I'd need to reproduce it.
16:06 Ssquidly joined #salt
16:06 UtahDave ekristen: I'd probably have the state send an event to the master, then use a Reactor to execute the state on server B
16:07 jaimed joined #salt
16:07 FeatherKing UtahDave: i only hesitate to call it a bug because it might be how our setup needs a graphical window for a moment and the service having no graphical environment. but i thought the interact with desktop could solve that but it didnt. i feel like its more a windows thing than a salt thing :/
16:08 FeatherKing in debug mode you can see the correct command
16:08 wangofett FeatherKing: there are a lot of those Windows things ;)
16:08 FeatherKing but in debug mode it also works
16:08 FeatherKing lol yeah
16:08 FeatherKing i will make a bug report
16:08 UtahDave yeah
16:08 UtahDave There might be a way to work around that somehow.
16:08 FeatherKing ok
16:09 FeatherKing for now i may try to map the drive and see
16:10 ekristen UtahDave: that was my thought to , I just wasn’t finding the state to use?
16:11 UtahDave ekristen: what version of salt are you on/
16:12 UtahDave ?
16:12 ekristen my master is at 2014.1.0rc3 (need to update that) most of my minions are 2014.1.4/5
16:12 UtahDave joined #salt
16:12 ekristen I tried upgrading to 2014.1.7 on master and minions and it broke everything, pillar data stopped working, etc I put a ticket in on it
16:12 ekristen my master is at 2014.1.0rc3 (need to update that) most of my minions are 2014.1.4/5
16:13 ksalman_ whats wrong with this sls? http://pastebin.com/raw.php?i=nGQbhCD3 I get the error "requisite declaration in sls is not formed as a single key dictionary"
16:13 bezeee joined #salt
16:13 UtahDave ekristen: Ok, so on 2014.7 there's the event state http://docs.saltstack.com/en/latest/ref/states/all/salt.states.event.html#module-salt.states.event
16:13 UtahDave ekristen: otherwise you can use the module.run with the event execution module to send an event with event.fire_master
16:14 ekristen ok 2014.1.7 has the event state?
16:14 UtahDave yeah.
16:14 ekristen I’m super gunshy about upgrading now, because I tried it once and I had to downgrade everything to get it working again, when I upgraded all my gitfs pillars stopped working
16:14 DaveQB joined #salt
16:14 tligda joined #salt
16:14 Ssquidly joined #salt
16:14 ekristen I like the new states though :)
16:15 UtahDave yeah, there's a lot of great stuff there.  I do recommend testing before upgrading everything.  :)
16:15 pled76 joined #salt
16:16 ekristen UtahDave: agreed there is an outstanding bug with docker/salt and docker registry authentication too that I have been trying to solve cause I rely on it
16:16 hobakill is there a way test to to see if gitfs is 'working' ? i've configured it per the documentation but i'm getting python errors on a state.highstate test=True
16:17 pled76_ joined #salt
16:17 melinath joined #salt
16:18 UtahDave hobakill: there's a function to force it to update.  It checks for updates every 60 seconds, by default
16:18 hobakill specifically: https://www.hobapolis.com/paste/?728f178a393cb9d5#oIw36eOlOyfZb01PPVCLzqH4eR68DPdPM29UMK/A1Ag=
16:18 hobakill UtahDave: for sure. i think i waited the 60 seconds before i tested the highstate.
16:18 UtahDave hobakill: is it a large repository?
16:19 hobakill nope. very small
16:19 hobakill UtahDave: you can see the error on the link i provided.
16:20 Eugene Something something pillar really needs a better solution for storing arbitrary files rabble rabble etc.
16:22 ekristen UtahDave: any recommendations on how to test upgrades with salt? Just setup a second master and slave and test the states and pillars, etc out? o
16:22 UtahDave hobakill: can you pastebin your sanitizez gitfs configuration?
16:22 UtahDave Eugene: :) yes, very true
16:24 hobakill UtahDave: pretty basic: https://www.hobapolis.com/paste/?3bac0c56ea06f4ca#H8lyIQVg2t6uOZ3ORW4E1FCUNgA+gWdHL5G/5oHMF1c=
16:25 hobakill UtahDave: i'm not entirely sure that -pubkey and -privkey are needed but it bombs with or without them
16:25 Eugene I also keep hoping #12301 will happen. But I'm just selfish.
16:25 berserk joined #salt
16:25 UtahDave hobakill: looks like you need to set up an ssh/config file:   http://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html#id5
16:26 j-saturne joined #salt
16:27 Ryan_Lane joined #salt
16:28 joehillen joined #salt
16:29 babilen EVENT states! \o/
16:29 rallytime joined #salt
16:29 thayne joined #salt
16:29 babilen Can we *please* have a 2014.7 release?
16:29 Ahlee Tips for troubleshooting a returner saying The specified returner used for the external job cache "custom_return" does not have a save_load function! when it does in fact have a safe_load method?
16:29 hobakill UtahDave: that blurb is confusing. do i HAVE to use a different rsa file or can i use the .pub file? the .pub is what my stash server has to authenticate the salt-master with
16:30 babilen I mean I don't really care about RAET for now, but I am writing so much boilerplate these days only because I cannot use 2014.7 already ... (also holding off on a massive restructuring of my git repositories as I can finally include pillars in a subdirectory)
16:31 UtahDave babilen: I know. We're working feverishly squashing bugs and working on the RC's.
16:31 hobakill UtahDave: my old work flow was that would write salt states, push it up to the stash server, and then salt-master would do a crontab'd "git pull" into a certain directory. so i know the salt-master can authenticate fine against the stash server.
16:31 aparsons joined #salt
16:32 aberdine joined #salt
16:32 UtahDave hobakill: i believe it needs to be the private key used to connect to the git server
16:33 armonge joined #salt
16:33 babilen UtahDave: I can imagine. Sorry, I don't mean to put you guys under more pressure or anything and a stable release would be appreciated. It's just that it happens so often that I do something and there would be a better solution if .7 had been released already (mine function aliases wa something I ran into yesterday, ...)
16:33 troyready joined #salt
16:33 ramishra joined #salt
16:33 babilen UtahDave: Is there anything that can be done to help? (e.g. run tests/...)
16:34 UtahDave babilen: Yeah, I know what you mean. We're anxious, too.  :)
16:34 babilen UtahDave: Or event states. I had to write my own execution module for two legitimate things, but mostly to just raise two different events :)
16:34 hobakill UtahDave: no dice even with the ~/.ssh/config file
16:35 babilen UtahDave: Let me know if there is something I could do. I could probably fire up some docker containers I use for testing our infrastructure and states and run it against .7 ...)
16:35 spookah joined #salt
16:35 * babilen heads off (yay, end of $WORK)
16:36 hobakill UtahDave: one sec... i stumbled on something.
16:37 UtahDave babilen: OK, I'll do that.  Thanks for being willing to help!
16:37 SpeeR joined #salt
16:38 ericof joined #salt
16:38 hobakill UtahDave: if i am only using gitpython do i have to specify that in the config?
16:38 hobakill eg: gitfs_provider:
16:38 hobakill - gitpython
16:39 UtahDave are you using 2014.7?
16:39 hobakill 2014.1.7
16:39 UtahDave then that option isn't supported yet.
16:40 UtahDave http://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html#installing-dependencies
16:40 robawt truth!
16:40 robawt it is backported to the future 2014.1.11
16:40 * robawt highfives UtahDave
16:41 Ahlee oh poop.  You have to restart the master/minion for new _returners to show up
16:42 Ahlee Well, kind of.  It's still throws the 'does not have a save_load', but the host returns but not the jid result
16:42 * UtahDave highfives robawt
16:43 hobakill UtahDave: so i should be using git+ssh as my gitfs_remotes?
16:43 pled76 joined #salt
16:44 armonge joined #salt
16:45 forrest joined #salt
16:45 UtahDave you might try that.  I haven't used all the different ways of configuring gitfs.
16:45 ramishra joined #salt
16:47 hobakill UtahDave: yeah no love. i really struggle with how tricky basic things can be.
16:47 ramteid joined #salt
16:49 Ahlee Using gitpython, hte user salt's running as should have a public key registered with your git remote
16:49 hobakill Ahlee: it does.
16:49 tyler-baker joined #salt
16:50 Ahlee ok, and git clone works outside of salt?
16:50 pled76 joined #salt
16:50 hobakill Ahlee: it does yes.
16:50 Ahlee We formally were using gitpython, now we run a state to locally clone
16:50 Ahlee let me pull up my config
16:51 Ahlee apologies, i'm coming in late
16:51 Ahlee you're having issues getting salt talking to stash?
16:52 ramishra joined #salt
16:52 hobakill Ahlee: gimme one second. i may have stumbled on something.
16:53 Ahlee https://gist.github.com/jalons/eea1e241283dc7fa5c32
16:55 pentabular joined #salt
16:56 FeatherKing UtahDave: Looks like i get similar UNC behavior trying to map a network drive
16:56 FeatherKing running in debug mounts it, running through service fails
16:56 hobakill Ahlee: i tried cloning a repo and it failed... i've regenerated the keys and added it to stash... gonna try again... gimme a few minutes to sort this out. :)
16:56 UtahDave FeatherKing: What happens if you change the user the service is running as?
16:57 Gareth morning
16:57 berserk joined #salt
16:57 robawt mornin' Gareth
16:58 Gareth robawt: hey. :) hows things?
16:58 FeatherKing UtahDave: that worked with the service logon as administrator
16:58 cpowell joined #salt
16:58 hobakill Ahlee: yeah i'm totally befuddled. now i know the key is working ... config seems "right" .... but it still is failing.
16:59 UtahDave FeatherKing: must be a security restriction on the system user
16:59 UtahDave hobakill: what user is the salt-minion running as?
16:59 hobakill root
16:59 robawt Gareth: not bad.  hopefully digging into some states today
16:59 chrisjones joined #salt
17:00 Ahlee hobakill: ok.  Let's take a step back. You can clone the repo you're trying to get salt working with now locally, so we know the underlying ssh auth is good.  Now let's fire up the saltmaster with -l debug (/usr/bin/salt-master -l debug or similar to launch it into the foreground with debug logging)
17:01 hobakill Ahlee: sure. thanks for the dedication to my stupidity. :)
17:02 Ahlee hobakill: just paying back all the patience shown me when I went down this path ;)
17:02 forrest lol
17:02 jhauser joined #salt
17:02 Ahlee FeatherKing: what version of salt?  We actually had to enable logging for service accounts to be able to mount before it would
17:02 FeatherKing 2014.1.7
17:02 Ahlee ok.  we're on 0.17.5-something
17:02 forrest Gareth, how goes the on-call?
17:03 FeatherKing where did you enable logging
17:03 hobakill ok debug is on
17:03 hobakill sorry - Ahlee - debug is running
17:03 Ahlee alright, it should yell at you now with why it can't clone
17:03 Gareth forrest: so far...quiet :)
17:03 Ahlee your repo in stash, it has a master branch at least?
17:03 forrest Gareth, Nice
17:03 j-saturne joined #salt
17:04 FeatherKing Ahlee: do you remember where you enabled logging for service accounts>?
17:05 Ahlee FeatherKing: C:\salt\conf\minion; make sure log_file is set (log_file: /var/log/salt/minion) and log_level_logfile: <level>
17:05 pled76_ joined #salt
17:05 FeatherKing oh salt logging
17:05 FeatherKing i will try ty
17:05 Ahlee yeah. strange thing.  We assumed (but never investigated) it was due to salt trying to print something to a log and failing
17:05 hobakill ok Ahlee gotz me a TON of logging. a lot of it looks very familiar to what gets kicked back in the standard test=Tur
17:05 FeatherKing that would make sense that debug works though
17:05 Ahlee we were about to roll out a new version of nssm
17:05 hobakill true
17:05 FeatherKing because it does log
17:06 FeatherKing brb
17:07 hobakill Ahlee: UtahDave https://www.hobapolis.com/paste/?4288885537d2c22a#iwwWTuH5mRR/63syAMP94pwYhaysZwIidL8X+HBnW6s=
17:08 Ahlee hobakill: well, those exceptions aren't good
17:09 Ahlee hobakill: sorry, what version of salt is this?
17:09 chiui joined #salt
17:09 Ahlee i want to make sure i'm looking at write gitfs.py
17:09 Ahlee right, even
17:09 UtahDave hobakill: could you open an issue on this? please include that paste and all the details of your systems.  including the output of   salt 'minion-id' test.versions_report
17:10 UtahDave I'll point the main gitfs dev to that.
17:10 Ahlee as I know terminalmage does a lot of tinkering with gitfs
17:10 Ahlee whoops, shouldn't have named him :(
17:10 ml_1 joined #salt
17:11 possibilities joined #salt
17:11 hobakill Ahlee: i'm on 2014.1.7
17:11 forrest hobakill, any chance you can try a more recent release?
17:11 forrest 2014.1.10?
17:12 hobakill forrest: if it would go into EPEL stable i'd be happy to
17:12 forrest hobakill, lol
17:12 forrest hobakill, the 'joys' of EPEL
17:14 Ahlee That's why I pull from koji ;)
17:14 Ahlee and rebuild
17:14 elfixit joined #salt
17:15 intellix joined #salt
17:15 Ahlee yeah, sadly i'm going to have to agree with UtahDave and point you to an issue with this.  I unfortunately need to get back to not making any progress at all on custom _returners
17:15 hobakill i appreciate it all!
17:15 pled76 joined #salt
17:15 forrest Ahlee, jeez, what a slacker :P
17:15 Ahlee I know right?!
17:16 forrest Ahlee, you could always hire me to consult, for the low low price of 9999 per hour
17:16 forrest minimum 40 hours
17:16 Ahlee heh
17:16 beneggett joined #salt
17:19 kermit joined #salt
17:19 hobakill UtahDave: https://github.com/saltstack/salt/issues/15285
17:21 kingel joined #salt
17:22 UtahDave thanks, hobakill!
17:22 Ryan_Lane joined #salt
17:23 vmdsch joined #salt
17:24 ndrei joined #salt
17:24 hobakill thank you UtahDave for the help
17:24 UtahDave you're very welcome. Sorry me or ahlee couldn't fix it right away. We'll get it sorted out.
17:25 vmdsch left #salt
17:26 forrest UtahDave, That reminds me, did you ever get around to throwing something together for https://github.com/saltstack/salt/issues/9066 ?
17:28 UtahDave forrest: I haven't had the time yet.  I'm glad you pointed that out to me. I do want to get that put together.
17:29 forrest UtahDave, ok cool, I wasn't sure if I had just missed it somewhere and could close the issue!
17:29 forrest UtahDave, it's like you have bugs that are negatively impacting people to fix, and clients to help or something, sheesh!
17:30 UtahDave :)  Yeah, it's a flood!  :)
17:35 jeremyBass1 joined #salt
17:35 nmadhok joined #salt
17:35 nmadhok hey
17:36 nmadhok i'm having problem setting up external authentication with ldap
17:36 tac joined #salt
17:37 cyberhawk777 joined #salt
17:38 pled76 joined #salt
17:38 dvestal joined #salt
17:39 forrest nmadhok, look who it is, that guy stealing all the damn formula merge requests *grumble*
17:40 nmadhok haha
17:40 forrest nmadhok, is your ldap hooked up to AD?
17:40 nmadhok sorry about that forest :p
17:40 nmadhok yes
17:40 forrest nmadhok, I really don't care, it's less work for so I appreciate it
17:40 forrest nmadhok, https://github.com/saltstack/salt/issues/13177 ?
17:41 forrest nmadhok, there's a good note there from cachedout
17:41 nmadhok i'm free after work so i look at the pull requests
17:41 nmadhok don't want them to pile up for anyone ;)
17:42 nmadhok ahhh no support for AD :\
17:42 forrest nmadhok, yeah
17:42 forrest nmadhok, he does say you could try to modify the group stuff though
17:42 forrest it might be worth investigating
17:42 forrest because that would be good to have
17:42 smcquay joined #salt
17:43 nmadhok i'll try
17:43 forrest nmadhok, cool
17:47 pled76 joined #salt
17:48 jalbretsen joined #salt
17:48 nmadhok it's not authenticating for me
17:48 nmadhok [root@ccitmgt2 ~]# salt -a ldap '*' test.ping username: nmadhok password:  Failed to authenticate, is this user permitted to execute commands?
17:49 hobakill UtahDave: ok i might be closer now. half of my centos boxes are half aren't on gitfs. i'm not entirely sure why.
17:49 icebourg joined #salt
17:49 forrest nmadhok, whomp whomp
17:51 lz-dylan Hey guys, I've been fighting Salt trying to target minions based on a grain that I'm setting on provisioning, and having a lot of difficulty figuring out how to do so.
17:51 hobakill UtahDave: as in - any minion doing something outside the "base:" config... doesn't work.
17:51 forrest lz-dylan, ok, what have you done so far, and where are you encountering issues?
17:51 nmadhok the configuration seems correct
17:51 ndrei joined #salt
17:51 lz-dylan I'm setting the grain as a list of properties, and they come through in grains.items, and I can select the _name_ of the grain with grains.has_value, but none of the values...
17:52 nmadhok i don't know what's stopping it from authentication
17:52 lz-dylan relevant configuration and comparative runs of grains.get, grains.has_value: https://gist.github.com/arubis/0d065b9e10f9e69c83d2
17:53 lz-dylan the minions were provisioned using salt-cloud -m /etc/salt/logstash-staging-only, which works just fine
17:53 forrest lz-dylan, interesting...
17:54 lz-dylan I first started picking up on this because running highstate wouldn't target the servers in my topfile.
17:54 hobakill so - yeah - that's exactly my problem. anything not in the "base:" environment isn't working. i have base: win: foo: bar: test: etc.... if the minion matches anything other than base: it doesn't work.
17:55 forrest lz-dylan, what does the actual role structure look like on the minion?
17:56 lz-dylan forrest: I'm not sure what you're asking. You mean from a file in /etc/salt on the minion, or the results of a grains.items, or something else entirely?
17:56 forrest lz-dylan, I mean the actual structure of the file for that grain item where you have it defined
17:56 lz-dylan hobakill: can I see your topfile?
17:58 berserk joined #salt
17:58 hobakill lz-dylan: you can. one second.
17:58 ndrei joined #salt
17:59 lz-dylan forrest: I'm defining it in /etc/salt/cloud.profiles. https://gist.github.com/arubis/0d065b9e10f9e69c83d2#file-_etc_salt_cloud-profiles
17:59 lz-dylan as 'staging_ec2_elk'
17:59 brent1 I am setting up some salt, and I environment is completely locked down, no pip, repos, nothing... Lame... So I am bulding from scratch... Has anyone ever document such an endeavor or can give me some useful tips.
17:59 rojem joined #salt
18:00 hobakill lz-dylan: https://www.hobapolis.com/paste/?505654081b635c4e#i63UFvXqDbrYgdwhMy43iHaylEwCtxkUFXCZ3ALA7ck=
18:00 lynxman joined #salt
18:00 lz-dylan brent1: you mean on the target minions?
18:01 forrest lz-dylan, ahh ok, I'm thinking that's the problem then, because it's a list. It needs to be a dictionary
18:01 econnell joined #salt
18:01 aparsons joined #salt
18:01 lz-dylan brent1: if you're provisioning using salt-cloud you can include quite a bit in the bootstrap
18:02 aparsons joined #salt
18:03 forrest lz-dylan, I've added a comment to your gist, could you please try it?
18:03 forrest I don't know if it will work for sure
18:04 lz-dylan forrest: I was just going to ask for suggestions, and that seems like a good next step. I'll give it a shot.
18:04 forrest lz-dylan, awesome, let me know if it works
18:05 hobakill lz-dylan: and i get errors like this on a high-state test: https://www.hobapolis.com/paste/?50e48f003c0cd51c#sdeLUEdZG54pQqiUkB2VwnNX0CFJjGuzDle+IBrgCls=
18:08 lz-dylan hobakill: is it just the PENTAHO-series that cause that error or anything?
18:08 brent1 lz-dylan: no saltcloud, I am stuck with rhel image that I can get admin rights, but no external networking, no pip, no epel, just manually downloading the libs and setting up on the server
18:09 hobakill lz-dylan: that's just an example. any box outside of the base: file root has errors.
18:09 lynxman joined #salt
18:09 hobakill lz-dylan: here's a windows example: https://www.hobapolis.com/paste/?2da5feabf675f0c9#g+b+S3lKPUw01o1PpsFAighhZ3r22ataLdzDjrdQCkg=
18:09 lz-dylan hobakill: haha, good! because I don't want to stare at that compound match too long ;)
18:10 lz-dylan forrest: just waiting on reprovisioning servers. I want a clean run from scratch so I'm not modifying the grains in-place.
18:10 forrest lz-dylan, sounds good
18:10 hobakill lz-dylan: :)
18:11 to_json joined #salt
18:12 lz-dylan hobakill: can you try it with that compound match and its subsections commented out, just to remove that from Things To Think About?
18:13 kballou joined #salt
18:14 hobakill lz-dylan: i can - but i have a feeling this is more a environments issue than pcre... but give me a few minutes.
18:14 dvestal joined #salt
18:14 lz-dylan forrest: no dice :( updated the gist with a comment response.
18:15 lz-dylan hobakill: you're almost certainly right, but it'd suck to tear out hair while going down the wrong path.
18:15 pled76 joined #salt
18:15 n8n joined #salt
18:16 hobakill lz-dylan: contextually this may make more sense. as you can see BDAPPTEST1 is in the same environment but has the same error: https://www.hobapolis.com/paste/?3b6d3e98470c4fb1#HDyZnorUWaHSzhxOG9enszGRvbuz/CyRbBjNz2ugBG0=
18:17 forrest lz-dylan, hmm, it's definitely formed as a dictionary now at least. I wonder if using a value of true was the wrong way to do it and it needs an actual value?
18:17 hobakill lz-dylan: and BDAPPTEST1 doesn't have that insane compound pcre
18:17 forrest lz-dylan, maybe just try present or something
18:18 lz-dylan brent1: oof, that's rough! I'm not sure what the best way to do that would be. Best I can tell, Salt really expects to be able to use some sort of package management. Anyone here used SaltStack without external networking?  ...
18:19 forrest lz-dylan, yeah, should mirror external repos
18:20 lz-dylan forrest: re-provisioning... And yeah, it'd definitely a dict now. I just don't know how to get it back out.
18:20 forrest lz-dylan, haha. When we find out there should be an update to the docs :P
18:21 brent1 forrest: interesting, can you point me to the repo ?
18:21 kingel joined #salt
18:21 forrest brent1, ? I mean setting up a copy of the official repos
18:22 lz-dylan forrest: indeed. it's _crazy frustrating_ that http://docs.saltstack.com/en/latest/topics/targeting/grains.html actually sets up a grain called 'roles' with the same syntax I used, then proceeds to talk about pulling grain matches...against an elsewhere-undefined grain called 'node_type'.
18:22 forrest a lot of companies do that to save bandwidth outside the network
18:22 lz-dylan forrest: I'd be happy to help out.
18:22 hobakill lz-dylan: do you think i need to change my File Server settings file_roots?
18:22 forrest lz-dylan, yeah that's problematic, someone is using it here too: https://developer.rackspace.com/blog/why-i-use-saltstack/
18:23 lz-dylan hobakill: I don't *think* so. You could try using an alternative syntax like in http://docs.saltstack.com/en/latest/ref/states/top.html#other-ways-of-targeting-minions
18:23 forrest lz-dylan, I feel like node_type is just a custom grain
18:23 PsionTheory joined #salt
18:23 lz-dylan which puts everything under base and then selects separately anyway
18:23 forrest but the way that role versus node_type is used is incorrect :\
18:24 lz-dylan forrest: agreed, but it's not defined so you can't see what's going in compared to how roles is defined...yeah.
18:24 forrest lz-dylan, I absolutely agree
18:24 n8n joined #salt
18:24 SheetiS This is how I used 'roles' in my grains:  http://devop.ninja/configuration%20management/2014/08/25/the-grains-conundrum/.  I liked targeting roles and whatnot, but I needed a way to do groupings as well.  That also shows what I do in my top.sls to apply the roles.
18:24 hobakill lz-dylan: i meant more like changing it from /srv/salt/win to /salt/win
18:25 hobakill lz-dylan: (in /etc/salt/master)
18:26 hobakill lz-dylan: never mind. it didn't work.
18:26 lz-dylan hobakill: ....y'know, that might be worth a shot. looks like convention involves moving base to /srv/salt/base and the rest to /srv/salt/other-directory. if so you should adjust your directory structure in /srv accordingly. I don't know if that will fix your problem; the only reason I can think that it would is removing potential confligts.
18:26 lz-dylan conflicts. and sadface.
18:27 brent1 forrest: makes sense, can you point me to the repo enpoint?
18:28 lz-dylan forrest: results of setting 'present' are about the same as setting True. updated Gist comment.
18:29 hobakill lz-dylan: wait a second... does /srv/salt /srv/salt/win /srv/salt/foo /srv/salt/bar actually need to exist?
18:29 chrisjones joined #salt
18:29 lz-dylan hobakill: whatever you've got defined in file_roots definitely needs to exist
18:29 hobakill lz-dylan: even in gitfs huh?... weird...
18:30 lz-dylan hobakill: oh I would _definitely_ try this on filesystem first to have one less thing to think about :P
18:31 hobakill filesystem works totally fine. i'm trying to convert this mess from filesystem to gitfs
18:31 bezeee joined #salt
18:31 forrest lz-dylan, bleh, that's dumb. it has a value though!
18:32 forrest hey UtahDave are you around?
18:32 pled76 joined #salt
18:32 UtahDave forrest: kinda sorta.  :)  what's up?
18:32 forrest UtahDave, is Mike there today?
18:33 UtahDave he's working from home today.  Want me to pass on a question for you?
18:33 lz-dylan hobakill: so this works completely okay on filesystem?
18:33 forrest UtahDave, please, could you ask him to take a look at: https://gist.github.com/arubis/0d065b9e10f9e69c83d2#file-_etc_salt_cloud-profiles ?
18:33 hobakill lz-dylan: yessir
18:33 forrest UtahDave, he added: https://github.com/saltstack/salt/issues/7829
18:33 n8n joined #salt
18:34 UtahDave yeah, I'll pass that one
18:34 forrest UtahDave, or the functionality that resolves it, but it's either not working, or we aren't using it correctly.
18:34 forrest UtahDave, thanks a ton
18:34 lz-dylan hobakill: Can I see your /etc/salt/master, or at least the relevant bits to select your file_roots? If that's proprietary, I can work with obfuscated/pseudocode versions.
18:36 hobakill lz-dylan: i just want to understand something. file_root directories matter even if using gitfs?
18:36 delinquentme joined #salt
18:36 aparsons joined #salt
18:37 TheThing joined #salt
18:38 hobakill lz-dylan: FWIW: https://www.hobapolis.com/paste/?553a693d8a19c726#XC2IW3zRgugnsfWE5Fc1uc2lT7fX2aF84J72XRSo2nQ=
18:39 lz-dylan hobakill: one sec
18:39 hobakill lz-dylan: also - even with the file_roots defined i still get the same errors. anything outside of "base:" doesn't work.
18:39 lz-dylan forrest UtahDave thanks for passing that along :)
18:40 forrest lz-dylan, yep, honestly I just want to know what the format should be
18:40 ronc joined #salt
18:41 berserk joined #salt
18:42 lz-dylan hobakill: if (1) that worked on filesystem and (2) you've moved all the non-base states to gitfs, I think you want to comment out the stuff you don't have on filesystem out completely from file_roots. though I'm not sure that it matters if the files just aren't there.
18:42 peters-tx joined #salt
18:42 lz-dylan hobakill: you've got git in your fileserver_backend?
18:43 deepz88 joined #salt
18:44 lz-dylan hobakill: from the top of http://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html :: "Branches and tags become Salt fileserver environments."
18:44 lz-dylan (which I did not know!)
18:44 lz-dylan (nifty!)
18:45 hobakill lz-dylan: oh F me running..... that could be it
18:45 pled76 joined #salt
18:47 TheThing joined #salt
18:47 hobakill lz-dylan: so it wants me to make a 'win' and 'bdapp' branch and that's how it gets addressed in a highstate.
18:47 hobakill ?
18:47 FeatherKing Ahlee: well the unc path still fails even with logging disabled. its weird i can see the debug log in there but the command never returns or fails or anything
18:48 FeatherKing Ahlee: reading more in windows the localSystem account has no network credential so it really shouldnt work i guess
18:48 TheoSLC joined #salt
18:49 jhauser joined #salt
18:49 FeatherKing so i appeal back to group for ideas: i have a salt master here and several windows minions over a WAN link. i need to run a setup that is local to the minions but i cant use UNC paths
18:49 TheoSLC Greeting KuberNots ;-)
18:49 lz-dylan hobakill: that's how it appears to me
18:49 TheThing_ joined #salt
18:49 FeatherKing what is a good way through salt to run that file local to the minions?
18:50 hobakill lz-dylan: i have a company meeting now but i'll test this tomorrow and let y'all know.
18:50 lz-dylan hobakill: seems like a reasonable way to keep from either needing a ton of repos or keeping everything in one big lump in one repo. too bad that line wasn't in boldface a dozen times ;)
18:50 lz-dylan hobakill: good deal and good luck!
18:51 kermit joined #salt
18:51 Ahlee FeatherKing: ah, interesting.  Very sorry to lead you astray
18:51 hobakill lz-dylan: agreed on all points. thanks a ton!
18:51 FeatherKing Ahlee: np
18:51 gwmngilfen joined #salt
18:51 UtahDave FeatherKing: can you mount those unc paths to a letter drive?
18:51 Ahlee FeatherKing: well, fileserver would work right?  Not ideal, but you could file.managed: to C:\tmp\file and then run it?
18:52 FeatherKing Ahlee: wouldnt it then copy the whole setup over the WAN?
18:52 Ahlee Yes, sadly
18:52 FeatherKing UtahDave: that fails as well through teh system account
18:52 Daemonik joined #salt
18:52 FeatherKing UtahDave: if i change the service to a real user, all of this works
18:52 lz-dylan forrest: in the interest of Science And Experimenting, I'm re-provisioning with "roles: {'logstash-reciever': True, 'logstash': True, 'elasticsearch': True', 'kibana': True}" in my cloud profile
18:52 forrest haha ok
18:55 thayne joined #salt
18:56 lz-dylan oh man typos are super frustrating when the test step is decommissioning and recommissioning a minion
18:56 forrest lz-dylan, :\
18:56 lz-dylan forrest: but I suspect this is going to work! which is nice.
18:56 forrest lz-dylan, are you going to wrap all those trues in quotes?
18:56 lz-dylan will know in a few minutes
18:57 forrest lz-dylan, the other way should work too, it's still a dictionary :\
18:57 lz-dylan do I need to? that's the typo earlier
18:57 forrest lz-dylan, I don't know for True if you need to or not
18:57 lz-dylan note the one True with the single-quote after elasticsearch
18:57 forrest I'm just looking at the examples
18:57 lz-dylan trying without
18:57 forrest ok
18:58 lz-dylan one of these days I'll throw together an AMI that's already got all the bootstrap-required packages installed. or, presumably, finding one that someone else has already done.
18:58 forrest lz-dylan, that would be cool
18:58 cwright hi. i'm writing a custom grain and would like to access variables defined in my pillar data. is it documented somewhere how to do this?
18:59 patarr does anyone here use salt for deployment of applications? Do you integrate it with your load balancers and such/
18:59 Ryan_Lane I've used it for deployment extensively
18:59 Ryan_Lane and currently use it as an integrated step for deploy + config management
19:00 Ryan_Lane where config management is run on every deploy
19:00 Ryan_Lane we only somewhat integrate it with out load balancers
19:00 Ahlee My continuous integration is also based on salt providing the backend, but all my applications are compiled c++ apps so no load balancers/web configs
19:00 Ryan_Lane basically we just use it on instance creation to add a node to an ELB
19:01 Ahlee if you can script manipulation of your LB, there's no reason not to be able to run that as a prereq for whatever state(s) you use for deployment
19:01 Ryan_Lane otherwise we rely on atomic deployment mechanisms
19:01 TheoSLC Could somebody that knows how the salt mine works look at this http://paste.ubuntu.com/8152399/
19:02 aparsons joined #salt
19:02 TheoSLC The mine.get returns values for all minions, not just the ones I've selected for .
19:03 skyler What is the best way to make sure that a script is shutdown before you execute a command and then restarted afterwards?
19:06 jalaziz joined #salt
19:08 aparsons_ joined #salt
19:09 lz-dylan forrest: hey, that worked!
19:09 forrest lz-dylan, that's good
19:09 forrest I don't see why it didn't work the other way
19:09 forrest but ok
19:09 forrest lol
19:10 lz-dylan I want elegant but will settle for functional
19:10 Ahlee oh what the... self.mminion = salt.minion.MasterMinion(  what the heck is this MasterMinion concept?
19:11 forrest lz-dylan, yeah if it works it works, I'll still be interested to see if Mike has any suggestions though
19:11 forrest Ahlee, it's a minion of masters who have minions, duh! :P
19:11 Ahlee heh.
19:12 Ahlee It appears you can't just arbitrarily define a new returner type as previously believed, as MasterMinion must already know about it
19:12 ekristen joined #salt
19:12 lz-dylan forrest: agreed. I do want a fuller understanding of what's happening here.
19:12 Ahlee otherwise the self.mminion doesn't know how to lookup the functions like save_load
19:13 forrest Ahlee, lame
19:13 mway joined #salt
19:15 Ahlee incredibly
19:15 pled76 joined #salt
19:15 lz-dylan forrest: gist updated if you want a go/no-go reference
19:15 Ahlee guess i steal an existing and overwrite the functions
19:16 forrest lz-dylan, great thanks
19:18 melinath joined #salt
19:18 forrest lz-dylan, lame, forks don't preserve comments.
19:19 TheThing joined #salt
19:20 possibilities joined #salt
19:21 wackycaptain joined #salt
19:22 lz-dylan forrest: well that's no bueño.
19:22 ndrei joined #salt
19:23 lz-dylan forrest: also my final target goal still isn't achieved. :P "salt '*' grains.has_value roles:elasticsearch" returns True, which is _wonderful_, but the section of my topfile under "'roles:elasticsearch': - match: grain" still doesn't fire.
19:26 skullone forrest: how goes it
19:33 dvestal I’m brand new to salt and trying to learn it. If anyone uses vagrant do you know if there is a secret to get the provisioner to print the output?  If I ssh into the vm and run “sudo salt-call —local state.highstate” manually I see the print out like I expect.
19:37 aparsons joined #salt
19:37 kingel joined #salt
19:37 thayne joined #salt
19:38 Katafalkas joined #salt
19:39 bhosmer joined #salt
19:41 aparsons joined #salt
19:44 FeatherKing UtahDave: Ahlee: i ended up doing this cmd.run 'sc \\localhost config salt-minion obj= .\Administrator password= pass' to reconfigure the service to start as a real user account and now all the unc path commands work
19:45 UtahDave I'm glad you found a workaround, FeatherKing!
19:45 Ahlee FeatherKing: Great to hear
19:46 Ahlee UtahDave: mailing list best place to ask for clarification around the MasterMinion loader methods?
19:46 FeatherKing UtahDave: Ahlee: seems more like a windows thing than a salt thing here, but you could create a salt user in the administrators group and have that user run the service in your windows installer, just a thought
19:46 rojem joined #salt
19:46 kingel joined #salt
19:47 pled76 joined #salt
19:47 UtahDave Ahlee: Yeah, I'll make sure tom or cachedout or whiteinge see it.  One those is probably your best bet for details on that.
19:47 Ahlee UtahDave: figured it'd be one of those three :) Thanks.  I'll get it composed and pushed up here shortly
19:49 Ahlee Suppose I should test on latest stable before getting too carried away
19:50 UtahDave thanks, Ahlee!
19:51 marco_en_voyage joined #salt
19:52 rojem joined #salt
19:52 aparsons_ joined #salt
19:58 ipmb joined #salt
20:04 aparsons joined #salt
20:04 forrest lz-dylan, that's a bummer..
20:04 felskrone joined #salt
20:04 forrest skullone, another day, short week and long weekend, so pretty good, you?
20:05 omio joined #salt
20:05 dvestal joined #salt
20:09 Ryan_Lane joined #salt
20:09 felskrone joined #salt
20:10 SheetiS joined #salt
20:10 cpowell joined #salt
20:13 MatthewsFace joined #salt
20:14 mpanetta joined #salt
20:15 Ryan_Lane http://ryandlane.com/blog/2014/08/26/saltstack-masterless-bootstrapping/ <-- finally posted that blog post I was working on
20:16 pled76 joined #salt
20:16 whiteinge Ryan_Lane: nice!
20:17 Corey Ryan_Lane: Threw it into Instapaper.
20:17 forrest Ryan_Lane, nice
20:17 Corey Will read it on the plane.
20:18 Ryan_Lane this one isn't nearly as long as the last :)
20:19 TheThing joined #salt
20:19 kingel joined #salt
20:19 * UtahDave starts reading.
20:20 mway joined #salt
20:21 perfectsine joined #salt
20:21 ipmb joined #salt
20:21 sectionme joined #salt
20:22 Sylphid|home joined #salt
20:27 Sylphid|home Hey all, ive been working on a syslog-ng formula that I would like to transfer over to the saltstack-formulas org
20:27 Sylphid|home anyone available to help atm?
20:29 bhosmer joined #salt
20:30 forrest Sylphid|home, yeah sure, looks like there isn't currently a syslog formula
20:30 forrest Sylphid|home, is it strictly in the ng format, or does it support the more simplified format as well?
20:31 Sylphid|home forrest, strictly ng
20:32 Sylphid|home forrest, https://github.com/sylphid8/syslog_ng-formula
20:32 forrest Sylphid|home, oh this is actually for a package called syslog ng
20:33 Sylphid|home forrest, correct
20:33 forrest Sylphid|home, I was not aware of that, I was talking about the NG style for formulas, lol. hang on a second.
20:33 Sylphid|home forrest, np
20:34 forrest Sylphid|home, https://github.com/saltstack-formulas/syslog-ng-formula
20:34 forrest Sylphid|home, if you'll just make a fork and then set that as a remote for your existing repo, then push there and make a PR via the interface, I'll merge it in right away!
20:35 Sylphid|home forrest, coolies, 2 shakes
20:35 forrest Sylphid|home, great
20:36 Sylphid|home forrest, well thats odd.. wont let me fork the empty repo
20:36 forrest ugh that's dumb
20:36 forrest hang on a sec
20:36 Sylphid|home np
20:37 floWenoL is it possible to dynamically write config files?
20:37 manfred forrest: should have clicked the button that put a default readme in it
20:37 floWenoL having a template and setting some variables
20:37 forrest Sylphid|home, https://github.com/gravyboat/syslog-ng-formula
20:37 floWenoL mostly interface addresses and hostname
20:37 forrest Sylphid|home, don't use that one
20:37 forrest it's on the wrong repo anyways
20:37 Sylphid|home forrest, LOL
20:37 forrest Sylphid|home, https://github.com/saltstack-formulas/syslog-ng-formula
20:37 forrest there we go
20:38 forrest fork that sucker, trash the readme, and do all the fun stuff to push and make a PR :P
20:38 forrest the joys of doing 5 things at once
20:38 forrest manfred, I should have
20:38 forrest manfred, I forgot that you can't fork an empty repo *shrug*
20:39 Katafalkas joined #salt
20:40 roolo joined #salt
20:41 floWenoL more important question than my first one
20:41 floWenoL if a managed file is externally changed salt will overwrite it right?
20:41 forrest floWenoL, absolutely
20:41 floWenoL damn it
20:41 forrest floWenoL, it will tell you the changes, and trash the file
20:42 forrest floWenoL, when you run the state/highstate
20:42 floWenoL shit
20:42 floWenoL im screwed
20:42 aparsons joined #salt
20:42 floWenoL wildfly rewrites its own config file
20:43 Sylphid|home forrest, PR en route
20:43 TheoSLC What are the valid resource locators for salt?? examples: salt:// file:// git://
20:44 floWenoL forrest: this may seem against what salt does but can I tell it to ignore a section of a file?
20:44 forrest Sylphid|home, cool
20:45 longdays joined #salt
20:45 aparsons joined #salt
20:45 longdays When is /etc/salt/minion_id generated and how can I reset it?
20:46 longdays just delete it?
20:46 pentabular1 joined #salt
20:46 pled76 joined #salt
20:46 forrest floWenoL, there's file.append, and file.blockreplace
20:47 forrest floWenoL, there's also file.prepend
20:47 forrest so yeah it's possible with some work aroundish stuff
20:47 longdays This is on bootstrap of a system
20:47 longdays coming out of vmware without cloud-init
20:47 forrest longdays, https://gist.github.com/gravyboat/e6b93a6c1e6f9a776062
20:47 floWenoL forrest thanks i will check that
20:47 forrest longdays, do that on the minion
20:48 forrest floWenoL, np
20:48 longdays looks like the ticket
20:48 longdays thanks
20:48 forrest np
20:48 floWenoL forrest: also how about a managed file and replace some stuff on it based on ip hostname etc
20:48 floWenoL can i have a template for the config file?
20:48 TheoSLC I answer my own questions.  looks like Salt will accept file locations using urlparse from salt://  http:// https:// ftp:// and swift://
20:48 forrest Sylphid|home, that's merged in, thanks!
20:48 Sylphid|home forrest, ty much
20:49 forrest floWenoL, yes you can template the config file using jinja!
20:49 floWenoL good
20:49 floWenoL ty once again
20:49 forrest floWenoL, np, there are some docs on doing that as well for templating files and such
20:49 floWenoL btw jinja in my country is an alcoholic drink :P
20:49 forrest haha
20:49 tempspace What country is that?
20:49 forrest Sylphid|home, np
20:50 floWenoL Portugal, well its Ginja but it is read the same way at least here
20:50 floWenoL basically its a sort of cherry liquor
20:51 tempspace nice
20:52 bezeee joined #salt
20:54 basepi Ryan_Lane: once https://github.com/saltstack/salt/pull/15295 is merged all your marked backports should be in 2014.7.  Sorry for how long it took, Jenkins had some issues yesterday, so it took us awhile to get the tests run on the backports.
20:55 Ryan_Lane yay!
20:55 Ryan_Lane no worries. thanks for the help!
20:55 Ryan_Lane I'll probably have some followups in the next few days
20:57 floWenoL in my test environment the host and localhost grains have the same value, wich one has the hostname only all the time
20:58 active8 joined #salt
21:00 kermit joined #salt
21:00 UtahDave TheoSLC: salt:// http:// https:// ftp:// s3://
21:02 UtahDave longdays: /etc/salt/minion_id is created by the minion the first time it starts up if the id is not defined in the minion config. It attempts to determine its fqdn and caches it in /etc/salt/minion_id
21:02 UtahDave longdays: you can safely just delete /etc/salt/minion_id if you want
21:03 longdays forrest and UtahDave I am using the gist sent over by forrest looks like it will do the trick. Thanks for both of your help
21:04 forrest longdays, great!
21:04 forrest longdays, tcotav originally provided those instructions, I just stole them from him, so all credit to him!
21:09 rap424 joined #salt
21:13 ekristen joined #salt
21:13 mpanetta_ joined #salt
21:14 kelseelynn joined #salt
21:15 aparsons joined #salt
21:16 pled76 joined #salt
21:16 kelseelynn left #salt
21:18 kingel joined #salt
21:18 KyleG1 joined #salt
21:20 KyleG2 joined #salt
21:21 aparsons joined #salt
21:22 sectionme joined #salt
21:22 lz-dylan forrest: soooo I kept on keeping on with this targeting-by-grains debacle. and it turns out that the way I _started_ doing it (looking like a bulleted list in markdown) is closer to working than defining a dict
21:24 chrisjones joined #salt
21:25 forrest lz-dylan, ahh ok
21:26 lz-dylan have a look: https://gist.github.com/arubis/798fe28ebd89c5f349e0
21:26 lz-dylan I can target minions correctly from the CLI
21:26 lz-dylan so, yay?
21:26 KyleG joined #salt
21:26 KyleG joined #salt
21:26 lz-dylan but topfile/highstate still doesn't make the connection and target minions by role
21:27 pclermont joined #salt
21:28 possibilities joined #salt
21:30 FL1SK joined #salt
21:33 n8n joined #salt
21:34 Ryan_Lane1 joined #salt
21:36 FeatherKing joined #salt
21:38 lz-dylan ...unless that's affected by salt-master not having been restarted........I'll know in ~15m.
21:40 floWenoL is it possible to use grain data from multiple minions
21:41 floWenoL lets say all of them have a grain called abc, and then use the aggregate of all of them for a loop
21:48 lz-dylan well boy howdy lookit that. forrest: I needed to restart my salt-master for it to be Smart about selecting minions by grain. *facepalm* and with that I am done for the day. ciao, folks.
21:48 aparsons joined #salt
21:49 kingel joined #salt
21:52 forrest lz-dylan, wait so you just used the original structure and it worked?
21:52 forrest you didn't use has_value though right?
21:52 kermit joined #salt
21:54 lz-dylan forrest: let me test has_value
21:54 forrest lz-dylan, ok cool, I doubt it will work since it expects a dict, but I'm glad the 'standard' way worked.
21:55 bhosmer joined #salt
21:56 lz-dylan forrest: and yeah, I just used the original structure. got a clue from https://github.com/saltstack/salt/issues/752
21:56 forrest nice
21:58 lz-dylan forrest: this is probably a decent summary: https://gist.github.com/arubis/95adeb756943164217bb
22:00 drowe joined #salt
22:00 aparsons joined #salt
22:03 lz-dylan in any case, i'm out for now. will check in manaña.
22:05 rojem joined #salt
22:07 davet joined #salt
22:09 rypeck Is there a preferred method for having the salt-minion start on boot?
22:09 rypeck I'm on ubuntu 12.04
22:11 davet1 joined #salt
22:11 manfred rypeck: if you have the upstart script on there, it starts by default
22:11 wt joined #salt
22:11 manfred you have to do crazy stuff to disable upstart scripts
22:11 wt hey, do the config item on http://salt.readthedocs.org/en/latest/topics/tutorials/intro_scale.html go i the minion config?
22:11 wt I am assuming, but it's kind unclear.
22:11 manfred rypeck: echo manual | sudo tee /etc/init/salt-master.override
22:12 manfred rypeck: that is how you disable it...
22:12 manfred if you just have /etc/init/salt-minion.conf from the salt repository, it will start on boot
22:12 manfred wt: which config?
22:13 wt random_reauth_delay and recon_*
22:13 manfred wt: first, use this one http://docs.saltstack.com/en/latest/topics/tutorials/intro_scale.html
22:13 manfred second
22:14 manfred random_reauth_delay says 'in the minions configuration file'
22:14 manfred and the recon ones should go in the minino config as well
22:17 intellix joined #salt
22:18 wt well, it does say that after the config option, but you're right it is there
22:18 wt Are the recon_* options also for the minion?
22:18 rypeck manfred: so if I want salt-minion to automatically start on boot I should remove that file?
22:18 rojem joined #salt
22:18 floWenoL for some reason one of my minions does ñot respond
22:18 floWenoL and he is online
22:19 manfred rypeck:
22:19 manfred rypeck: just don't have a /etc/init/salt-minion.override
22:19 rypeck Yup - thanks.
22:19 manfred it just needs to have /etc/init/salt-minion.conf
22:50 ilbot3 joined #salt
22:50 Topic for #salt is now Welcome to #salt | 2014.1.10 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/
22:50 kingel joined #salt
22:50 lude1 joined #salt
22:51 joehoyle joined #salt
22:54 possibilities joined #salt
22:54 Ryan_LAne joined #salt
22:54 yomilk joined #salt
22:55 hillna_ joined #salt
22:55 bmcorser joined #salt
22:56 natewalck joined #salt
22:56 rypeck joined #salt
22:57 whytewolf joined #salt
22:58 aparsons joined #salt
23:02 Outlander joined #salt
23:03 aparsons joined #salt
23:04 andrej Heh ... "(Quit: My MacBook Pro has gone to sleep. ZZZzzz�)" .... finally something a mac's good at :}
23:04 Alan_S joined #salt
23:05 sctsang joined #salt
23:06 KyleG joined #salt
23:06 KyleG joined #salt
23:08 Outlander joined #salt
23:13 aparsons joined #salt
23:14 troyready joined #salt
23:17 davi_____ joined #salt
23:18 freemania joined #salt
23:22 wendall911 joined #salt
23:23 possibilities joined #salt
23:31 dccc__ joined #salt
23:33 blarghmatey joined #salt
23:34 joehoyle to use require_in, does that required thing need to be in the same sls file?
23:34 blarghmatey joehoyle: No, it can be in a different state file. It just needs to be accessible.
23:35 TOoSmOotH joined #salt
23:35 blarghmatey Salt will scan through all of the states when it begins the run so that it can compile the dependency graph.
23:35 joehoyle blarghmatey: hm I thought so, but I'm getting: "No function declared in state "watch_in" in sls newrelic"
23:36 joehoyle which seems a bit cryptic!
23:36 blarghmatey Can you post your sls to pastebin?
23:36 joehoyle yeah https://gist.github.com/joehoyle/1dd57c46147d5bfaa2f7
23:37 joehoyle )hope gist is ok)
23:37 TheThing joined #salt
23:37 joehoyle this is the required file https://gist.github.com/joehoyle/f41fa076c6d9938c5d33
23:37 joehoyle perhaps should I be using "php_stack" as the service?
23:39 blarghmatey Yes, it matches against what you named the state
23:39 blarghmatey In this case, php_stack
23:39 joehoyle ah ok, cool
23:40 blarghmatey Does anyone know if there is a way to list the files located in the configured file roots? I'm trying to debug an issue I'm having when trying to use gitfs.
23:40 mosen joined #salt
23:40 joehoyle did I see somewhere that it would be added so you can do "watch_in: service - nginx" for example, and it would also just reload that service on the system without it needing to be in your SLS files?
23:40 blarghmatey joehoyle: That would be nice. I haven't seen it, but that doesn't mean much.
23:41 forrest joehoyle, I don't think that would work, since without knowing about the service, salt can't do anything with it
23:41 joehoyle blarghmatey: no worries! thanks for you help, just trying it now :)
23:41 forrest joehoyle, right now you just need to include: \n  - nginx.service or whatever
23:41 forrest and that will work
23:41 forrest assuming you have a /srv/salt/nginx/service.sls state that handles that
23:41 blarghmatey Also, it might be better to use pkgs:\n- packagename\n- otherpackage as it will then pull all of them together and run it at once, making for faster execution
23:41 joehoyle forrest: right
23:41 joehoyle oh nice
23:42 joehoyle blarghmatey: on that note, I feel like I've observed salt to a new "apt-get update" for every pkg.installed it encounters, is tha the case?
23:42 blarghmatey Yes, I believe so
23:42 mosen hi saltines
23:43 blarghmatey I think you can pass a param that tells it whether or not to do a refresh.
23:43 joehoyle ah ok, intersting - I guess realy I want to say "the first one can do it, then don't do it any more"
23:43 blarghmatey Yes it does. - refresh: False
23:44 patrickcp joined #salt
23:45 joehoyle does pkg.installed install an update if one is avialable, as I see this "hold" parameter "Force the package to be held at the current installed version. Currently works with YUM & APT based systems." this makes me think salt is going to be upgrading my packages on a highstate?
23:47 schimmy joined #salt
23:49 schimmy1 joined #salt
23:51 davi_____ left #salt
23:52 blarghmatey joined #salt
23:52 TheThing joined #salt

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