Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-08-31

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

All times shown according to UTC.

Time Nick Message
00:00 mattp_ joined #salt
00:00 mattp_ hi guys
00:00 mattp_ I have a script I'm running that produces a file artifact that I need to act on (but is not the main output of the script)
00:01 mattp_ what is the correct way to glue this in via orchestrate
00:01 mattp_ create an external pillar?
00:01 mattp_ or create a module function that runs on the minion/
00:02 silicon_id joined #salt
00:04 pipps joined #salt
00:04 woodtablet left #salt
00:22 XenophonF omg templating xml files sucks
00:24 silicon_id joined #salt
00:29 amcorreia joined #salt
00:30 schemanic_ joined #salt
00:31 schemanic_ Hi
00:31 schemanic_ Is anyone willing to help me break down a salt formula? I'm feeling a bit lost with the sudoers one
00:31 ninjada_ joined #salt
00:37 Brijesh1 joined #salt
00:40 cmarzullo schemanic_: whats your q?
00:41 schemanic_ hi cmarzullo. I'm trying to understand the sample pillar. It doesn't seem to be commented insofar as what to place there, and I need help translating it.
00:41 cmarzullo link to sudoers formula?
00:42 schemanic_ sure: https://github.com/saltstack-formulas/sudoers-formula
00:43 cmarzullo you all set with pillar? Like you grok it and stuff?
00:43 schemanic_ Yes, I understand pillar at a high level - Its a data structure that holds sensitive data to pass into states
00:43 cmarzullo k.
00:44 cmarzullo so that formula basically makes one file. and uses the pillar to 'template' the file out.
00:44 schemanic_ Im just not following the logic of this formula - it seems like there's references to users all over the place, but I'm not sure which of them says 'these people are sudoers, and this is what settings they get'
00:44 cmarzullo yeah it's a poorly written formula.
00:44 cmarzullo (imo)
00:44 schemanic_ hmm
00:45 schemanic_ Is there a better one that you might recommend?
00:46 cmarzullo lemme look through that list there.
00:46 cmarzullo there's a nice blog about TDD with test kitchen for writing formulas.
00:47 schemanic_ test kitchen?
00:47 cmarzullo as your code base grows and you have lots of formulas you'll want a way to easily write them, and test them.
00:48 cmarzullo test kitchen will let you do that.
00:48 mattp_ cmarzullo: do you have any idea how to adress what I was asking about
00:49 cmarzullo so like I write formulas on my mac, then use test kitchen. which uses vagrnt to stand up a vm does all the states so I can see if it works like I want.
00:49 schemanic_ ah
00:50 cmarzullo mattp_: so you want to react to a file that gets created elswhere
00:50 cmarzullo schemanic_: it's gets kinda next level.
00:50 mattp_ cmarzullo: ah yes ok
00:50 mattp_ so wait_for_event
00:50 schemanic_ is this the github project?
00:50 cmarzullo mattp_: I'm not the best with reactors and beacons.
00:51 mattp_ cmarzullo: that part is fine, but how do I go from file contents -> data in jinja2 that gets turned into sls state?
00:51 cmarzullo schemanic_: checkout this dude bros blog http://unicolet.blogspot.com/2016/05/a-not-so-short-guide-to-tdd-saltstack.html
00:52 cmarzullo mattp_: I'm not really following your use case.
00:52 mattp_ cmarzullo: I have a script that does stuff, then writes state data to a file ( I cant change this script )
00:53 hasues joined #salt
00:53 mattp_ I need to act on the contents of whats written to this file
00:53 cmarzullo the script is non-salted? Like called from cron or something?
00:53 schemanic_ cmarzullo, I see, so this article describes setting up a pipeline for setting up my salt states
00:53 mattp_ the script itself is invoked via cmd.run, but its something that can be manually run outside of salt
00:54 schemanic_ and testing them on a dummy vm
00:54 cmarzullo yeah.
00:54 cmarzullo then in prod you can be reasonably certain you'll get the desired output.
00:54 nicksloan joined #salt
00:55 cmarzullo mattp_: Perhaps a beacon that watches the file then fires off events. Then you'd have reactors respond to that.
00:55 mattp_ cmarzullo: so the beacon owns the parsing of the file
00:55 mattp_ ok
00:56 schemanic_ how does test kitchen handle simulating the master?
00:56 cmarzullo no the beacon will look for the creation or changes to the file. It sends an event about that.
00:56 cmarzullo Then a reactor receives the event and 'does things'
00:56 schemanic_ come to think of it, how should I set up my repo for salt development
00:56 cmarzullo schemanic_: hehe got a couple of hours?
00:56 Brijesh1 joined #salt
00:56 schemanic_ lol
00:57 mattp_ cmarzullo: ah
00:57 schemanic_ yeah, the salt structure doesn't lend itself to just having a repo to blow out somewhere
00:58 cmarzullo it does and doesn't. If you just want to have a go it's pretty easy. But if you want full CI and testing with a multiperson team, you gotta put in a bunch of legwork.
00:58 debian112 joined #salt
00:58 cmarzullo Some folks just do monolithic state tree and are fine with it.
00:58 cmarzullo Works great if you have a limited application set to support.
00:59 cmarzullo But if you have dozens of services and want to not repeat yourself you have to do some more.
00:59 cmarzullo We have a repo per salt formula.
01:00 cmarzullo Then our saltstack formula configures all the different file roots to where all the formulas live on disk.
01:00 cmarzullo We have other glue that git clones all the salt formulas to the places on disk.
01:01 cmarzullo We develop locally. Then when a PR is made against the production formula, a VM is fired up on our cloud provider to ensure the formula has the same result.
01:02 cmarzullo And we write tests for our formulas to double check that, even though salt is doing what we tell it to, it's actally doing what we want.
01:02 fannet joined #salt
01:02 cmarzullo we've found some bugs in packaging and stuff like that
01:05 schemanic_ cmarzullo, but given that pillar and salt(states) have to live in separate places, how do you handle getting the pillar out to the right place if you're versioning the formula as a whole?
01:06 edrocks joined #salt
01:07 cmarzullo It's pretty imporant to separate your data about the thing you are configuring from the thing your are configuring.
01:07 cmarzullo So that's where you see those pillar.examples.
01:07 cmarzullo We bundle an exxample pillar with each formula. So if you just call the formula you get one result. But if you call with with a bunch of pillar you get another result.
01:08 cmarzullo Some of our more risky formulas has feature toggles. So it's not enough just to include the formula in your top file. you MUST have a pillar saying iptables.enabled = true
01:09 cmarzullo kinda like two keys to launch the missle.
01:10 xbglowx_ joined #salt
01:10 schemanic_ cmarzullo, that makes sense. But what I mean is that the pillar file itself can't live in the directory with the formula right? You have to move the pillar to /srv/pillar then configure it yes?
01:10 cmarzullo oh I see where you going.
01:10 cmarzullo yeah we have a differnt seperate repo for pillar data.
01:11 cmarzullo We like to think of that repo as our CMDB.
01:11 schemanic_ do you do all your pillars in one repo, or 1:1 with your formulas?
01:11 cmarzullo All pillar in one repo.
01:12 cmarzullo a nother nice thing is we gpg a lot of our pillar. But that's separate from the formula. So the formula just takes mysql.password = testpw
01:12 cmarzullo but in production pillar that password in gpg encrypted.
01:12 cmarzullo or not if peeps are being bad.
01:12 schemanic_ I see, so the password in the pillar itself is the gpg cypher
01:12 cmarzullo yeah
01:12 schemanic_ I havent gotten that working yet
01:13 schemanic_ So far, i've gotten salt cloud going
01:13 schemanic_ and some minor states with ssh keys
01:13 ninjada joined #salt
01:13 cmarzullo sweet. salt-cloud is really fun.
01:13 schemanic_ I'm teaching myself this stuff and our company really has no devops organization to speak of, so having a sense of what step 1 is, the step 2 etc is helpful
01:14 cmarzullo I hear you. We are the shepards in the valley of darkness
01:15 schemanic_ If I follow you correctly, whether I'm using canned formulas or not, I should use this test suite to work with my infrastructure code, because it decouples me from having to use actual cloud resources to do so, and tests the code before deployment
01:15 cmarzullo For me, it's about the path. It's not about getting the formula right the first time. But having someone else come back and slowly add features in a way we know won't break reverything
01:16 schemanic_ mmm
01:16 schemanic_ yeah. start small, get it working, then iterate
01:16 XenophonF cmarzullo: if you want a good description of that process, look at the commit history for https://github.com/irtnog/shibboleth-formula/tree/master/shibboleth/idp
01:17 XenophonF i started with a basic framework - an empty defaults.yaml, a map.jinja file for just one or two operating systems, and a simple init.sls file that installed some packages
01:17 XenophonF and then iterated
01:17 XenophonF i'm basically adding capabilities as i need them
01:18 John_Kang joined #salt
01:18 cmarzullo That's why I like the local development with test-kitchen. I can freely experiment try lots of things. Then combine a bunch of formulas into a vbox vagrant project. feel pretty good about it share it with the team. collab then got to prod.
01:18 XenophonF hm, maybe https://github.com/irtnog/tomcat-formula/tree/master/tomcat would be a better example
01:18 cmarzullo and jsut change the pillar in prod.
01:18 cmarzullo XenophonF: I'll take a look.
01:18 schemanic_ For me I'm charged with creating configuration management throughout the environment
01:18 XenophonF i'm following a github-flow like pattern but yeah, local development, rapid prototyping
01:19 cmarzullo XenophonF: have you worked with test-kitchen and kitchen-salt? it's pretty sweet.
01:19 hasues left #salt
01:20 XenophonF no i haven't
01:20 cmarzullo schemanic_: yeah takes a lot of head scrathing. People will hate you cause it's a lot of effort. Till later when everyone is on the same page.
01:20 schemanic_ mmm
01:20 XenophonF i have a dev master & small collection of VMs
01:20 cmarzullo I wrote a little salt-formula scaffold generator.
01:20 XenophonF do development on the master
01:21 schemanic_ Im working through setting up that environment
01:21 cmarzullo you do saltscaffold -p haveged and it'lls make a haveged-formula that you can kitchen test right away
01:21 XenophonF i keep meaning to play around with vagrant and docker and all that stuff
01:21 cmarzullo docker meh. but test-kitchen is nice
01:22 cmarzullo It basically uses vagrant. so you define some yaml and it'll do all the needful.
01:22 cmarzullo Like run the same formula against different platforms.
01:22 cmarzullo It's heavily used in the chef world.
01:22 schemanic_ cmarzullo, can you install saltscaffold with pip?
01:23 XenophonF hm, looks like there's a devel/py-kitchen port on freebsd
01:23 XenophonF doesn't look like the same thing though
01:23 cmarzullo schemanic_: not sure. I need to get back on it. I have a bunch of PRs I need to go through.
01:24 cmarzullo I'm a terrible developer.
01:24 schemanic_ you got me this far, don't knock yourself :)
01:24 cmarzullo fake it till you make it right?
01:25 schemanic_ of course! hey whats the bits page on the readme though? can I just point pip at the zipfile that gets downloaded from github?
01:25 cmarzullo yeah the bits page is one of the PRs I need to process. heh
01:26 schemanic_ hmm
01:26 schemanic_ okay. I'll do it from setup.py
01:27 schemanic_ oh cool
01:27 schemanic_ pip seems to get ahold of it if I pass the zip as an argument to it
01:28 * ssplatt hacks bits
01:29 * cmarzullo grumles
01:29 * ssplatt sees a bunch of 1s and 0s
01:30 schemanic_ hey cmarzullo thanks very much for the chat - it really helped get some eyes on the way forward.
01:30 cmarzullo happy to help.
01:33 brotatochip joined #salt
01:42 fracklen joined #salt
01:46 catpigger joined #salt
01:47 ilbot3 joined #salt
01:47 Topic for #salt is now Welcome to #salt! | Latest Versions: 2015.5.11, 2015.8.11, 2016.3.2 | Support: https://www.saltstack.com/support/ | Logs: http://irclog.perlgeek.de/salt/ | Paste: https://gist.github.com/ (please don't multiline paste into channel) | See also: #salt-devel, #salt-offtopic | Ask with patience as we are volunteers and may not have immediate answers
01:49 _JZ_ joined #salt
01:52 sp0097 joined #salt
02:03 M-liberdiko joined #salt
02:20 subsignal joined #salt
02:21 bastiandg joined #salt
02:27 subsignal joined #salt
02:34 hasues joined #salt
02:34 hasues left #salt
02:40 Sammichmaker joined #salt
02:40 Sammichmaker joined #salt
02:43 evle joined #salt
02:43 schemanic_ joined #salt
02:47 subsignal joined #salt
02:50 M-MadsRC joined #salt
02:50 freelock[m] joined #salt
02:50 hasues joined #salt
02:50 subsignal joined #salt
02:57 hasues left #salt
03:00 subsignal joined #salt
03:02 fannet joined #salt
03:04 jenastar joined #salt
03:05 dyasny joined #salt
03:05 jenastar joined #salt
03:15 alvinstarr joined #salt
03:20 subsignal joined #salt
03:21 subsigna_ joined #salt
03:24 subsignal joined #salt
03:43 jenastar joined #salt
03:59 brotatochip joined #salt
04:03 DEger joined #salt
04:07 cyborg-one joined #salt
04:10 jenastar left #salt
04:17 s0undt3ch_ joined #salt
04:25 subsignal joined #salt
04:27 armguy joined #salt
04:39 edrocks joined #salt
04:39 justanotheruser joined #salt
04:46 DEger joined #salt
05:03 fannet joined #salt
05:09 ninjada joined #salt
05:11 onlyanegg joined #salt
05:31 jaybocc2 joined #salt
05:31 subsignal joined #salt
05:40 eightyeight so, working through the salt documentation, and noticing that routable IPs and domain names are being used for examples
05:41 eightyeight there are actually RFCs set aside for this
05:41 eightyeight RFC 2606 defines reserved domain names example.com, example.org, and example.net specifically for documentation
05:42 eightyeight RFC 5737 defines three network ranges for docs, that are not routable (or shouldn't be)
05:42 eightyeight TEST_NET_1: 192.0.2.0/24
05:42 eightyeight TEST_NET_2: 198.51.100.0/24
05:43 eightyeight TEST_NET_3: 203.0.113.0/24
05:43 eightyeight there is also an analagous RFC for IPv6
05:43 eightyeight so, instead of exapmles like `10.0.0.1', `192.0.2.1' could be used
05:43 eightyeight etc.
05:43 eightyeight FYI
05:43 eightyeight jfindlay: ^
05:46 jaybocc2 joined #salt
05:52 impi joined #salt
06:05 ttrumm joined #salt
06:09 bocaneri joined #salt
06:20 yuhlw_ joined #salt
06:25 agentnoel joined #salt
06:25 ttrumm joined #salt
06:28 jxm_ joined #salt
06:29 Karthik427 joined #salt
06:30 Karthik427 Hi
06:30 Karthik427 i am getting the below error when trying to use git as fileserver backend
06:30 Karthik427 State 'kube-master' in SLS 'kube-master' is not formed as a list
06:31 Arjun_ joined #salt
06:31 Arjun_ Hi Salt Team
06:31 Arjun_ Is there anyone to help out fixing my issue
06:31 cro joined #salt
06:32 GreatSnoopy joined #salt
06:32 Arjun_ I have configured salt with git and i am trying to execute salt highstate command and it throws error
06:33 k_sze joined #salt
06:36 Karthik427 Hello All
06:36 Arjun_ Hello Karthik
06:36 Arjun_ Looks like no members are active now
06:40 amy_ joined #salt
06:43 CeBe joined #salt
06:47 kshlm joined #salt
06:47 babilen Arjun_: There is little people can do if you don't even tell them what error message you get
06:47 babilen Preferably create a pastebin on one of http://refheap.com, http://paste.debian.net, https://gist.github.com, http://sprunge.us, … with all information that pertains to the problem (e.g. your configuration, commands, their output, ...)
06:48 Arjun_ Sure @babilen thanks for you reply
06:48 babilen In your case the most important bits of information are probably your master configuration as it pertains to git, your top.sls and the commands you run
06:49 Arjun_ Shall i paste the master configuration
06:49 Arjun_ in the pastebin
06:49 ub joined #salt
06:51 Arjun_ https://gist.github.com/arjunm183/a2e66c6791f9e31c3a81adb5bc312454
06:51 Arjun_ @babilen you can see the details here
06:53 babilen Okay, I'll be afk for a while, but it would be good to know the error. As this might be related to the master not being able to clone your repositories you might also want to show the master debug log (run salt-master -ldebug after stopping the service) bits where it clones them and try to clone the repos manually as the user salt runs as.
06:53 babilen I am assuming that the actual error you see is about there being no top files or states for a potential minion
06:54 Arjun_ I am running the below command in my salt master " salt -G 'roles:kube-master' state.apply
06:54 scavara joined #salt
06:56 babilen And?
06:56 Brijesh1 joined #salt
06:57 Karthik427 joined #salt
06:57 babilen Okay, bbl
06:57 keimlink joined #salt
06:58 Arjun_ and it hangs
06:58 Arjun_ no output at the moment
06:58 Arjun_ I manually set the grains using  grains.setval for my kube-master and kube-node
06:59 Bryson joined #salt
07:00 AndreasLutro Arjun_: if you ssh to the minion and run `salt-call state.apply -l info` you'll get more information about what's actually going on
07:00 k_sze If I get "SaltReqTimeoutError: SaltReqTimeoutError: after 180 seconds, ran 3 tries", what does it actually mean?
07:01 k_sze Is the salt minion still running the job?
07:01 Brijesh2 joined #salt
07:01 Arjun_ @AndreasLutro looks like it worked, but how do i confirm that my salt master is talking to git to fetch the states and formulas
07:03 Arjun_ @AndreasLutro https://gist.github.com/arjunm183/a2e66c6791f9e31c3a81adb5bc312454
07:03 scavara Is there any way to prevent accidental rm/reboots on minion, when such commands are initiated via master "salt "someclient(s)*" cmd.run "rm -rf /etc". I was hopping that installing tools/wrappers on a minion such as safe-rm, molly-guard will do, but they don't.
07:04 fannet joined #salt
07:05 AndreasLutro Arjun_: increase the salt master log level and inspect the master log I guess, if you want to be 100% sure
07:05 AndreasLutro k_sze: where do you see that?
07:06 k_sze `salt-run jobs.lookup_jid <jid>`
07:07 ninjada joined #salt
07:07 AndreasLutro mm I think that means your salt-run can't talk to the salt master, are you running the command on the master?
07:07 k_sze yes
07:09 mavhq joined #salt
07:11 AndreasLutro dunno then, check that your master is running properly I suppose
07:15 fracklen joined #salt
07:16 fracklen joined #salt
07:19 tongpu joined #salt
07:19 IanV0rn2341 joined #salt
07:31 Brijesh1 joined #salt
07:31 tongpu joined #salt
07:31 Brijesh1 joined #salt
07:31 Brijesh1 left #salt
07:31 Brijesh1 joined #salt
07:32 sjorge joined #salt
07:35 keimlink joined #salt
07:39 pfc joined #salt
07:39 debian112 joined #salt
07:44 pfc joined #salt
07:48 impi joined #salt
07:58 jaybocc2 joined #salt
08:05 ixs XenophonF: nice suggestion, but salt even has a ipmi module for state and execution already. My issue is more: can I have salt-ssh execute _one_ thing locally?
08:07 ninjada joined #salt
08:13 pipps joined #salt
08:14 jaybocc2 joined #salt
08:14 dariusjs joined #salt
08:17 babilen ixs: Look into orchestrate -- https://docs.saltstack.com/en/latest/topics/orchestrate/orchestrate_runner.html#orchestrate-runner
08:17 babilen That's Salt's way of running states on different hosts/minions
08:21 babilen I guess you will then want to wait for the box to become available. You could kick off a highstate run via reactors or startup states or wait for a specific event with https://docs.saltstack.com/en/latest/ref/states/all/salt.states.saltmod.html#salt.states.saltmod.wait_for_event
08:21 babilen (all based on the salt/minion/$FOO/start event)
08:22 babilen Otherwise you might try to run the state while the box is still booting
08:23 ixs babilen: thanks, reading for now...
08:24 ixs but it sounds like it is what I am looking for. thanks already.
08:28 ixs babilen: do you if salt-run can be paired with salt-ssh or does it really need a running master?
08:38 Harmless_Sponge joined #salt
08:38 babilen ixs: I don't actually know. I am rarely using salt-ssh and if I do then for not very complicated setups. I found the cost of running a master to be negligible compared to the functionality and features it opens up
08:42 ixs babilen: fair enough. I will probably go for a master soonish, but as of right now I am still trying first steps with salt and there salt-ssh sounds neater.
08:43 edrocks joined #salt
08:43 babilen It certainly does appeal to your ansible mindset, I'm sure :)
08:45 rdas joined #salt
08:47 keimlink joined #salt
08:49 jgarr joined #salt
08:50 DEger joined #salt
08:50 ttrumm joined #salt
08:53 Rumbles joined #salt
08:54 keimlink joined #salt
08:56 jhauser joined #salt
09:05 fannet joined #salt
09:05 lero joined #salt
09:17 Brijesh1 joined #salt
09:20 lero_ joined #salt
09:23 JPT joined #salt
09:30 cliluw joined #salt
09:36 scavara i found the workaround wrt my question (@09:03). salt-minion, when run as root, has PATH variable set (by default) so it looks first in /bin or /sbin before their pandans in /usr/ dir. If you put something like PATH=/usr/sbin:/sbin:/usr/bin:/bin:/usr/local/bin in /etc/init.d/salt-minion (restart of course), it should work but i'm not quite sure how durty this is...
09:40 Rumbles joined #salt
09:42 richardl quick question for people here, what would be the best method to create a file on a salt run/ state and share it between two different minions?
09:43 N-Mi joined #salt
09:50 cmarzullo just create it on both minions.
09:52 richardl The issue is I wish to create a public and private key pair then share out the public key, however I want these to be fresh when the salt-state is run
09:53 cmarzullo push the public key into the mine.
09:54 cmarzullo although that raises the level of complexity.
09:56 richardl I haven't used salt-mine before how do I push the key into it?
09:58 mortis richardl: put it in mine_functions in pillars
09:58 mortis richardl: https://docs.saltstack.com/en/latest/topics/mine/
10:09 Rumbles joined #salt
10:09 Brijesh2 joined #salt
10:25 jaybocc2 joined #salt
10:26 babilen richardl: There is https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.gpg.html that you can use for creating the keys
10:32 salato joined #salt
10:33 salato hi, when using jinja templates with separated file roots, how do I deal with things like the extend tag? what base path should I use?
10:33 AndreasLutro salato: pretend they're salt:// urls, but without the "salt://" bit
10:34 chrichip joined #salt
10:34 salato for example I get a not found when using a dir structure like /{base,prod,dev}/ and /base/nginx/templates/wpsite_server.tmpl , and this tag {% extends 'nginx/templates/wpsite_server.tmpl' %}    <======================
10:35 richardl Thank you all for the input I will examine the options and see what one works for my current project
10:36 salato AndreasLutro: I think I didn't understood what I did wrong in that case
10:38 keimlink joined #salt
10:38 AndreasLutro maybe it has to be part of the same environment? not sure. I don't use salt environments
10:39 Rumbles joined #salt
10:39 salato AndreasLutro: in this case is part of the same environment indeed
10:40 dariusjs joined #salt
10:41 jaybocc2 joined #salt
10:42 AndreasLutro dunno then. are you using salt-ssh?
10:45 rawzone joined #salt
10:48 salato AndreasLutro: yes
10:49 Taters_ joined #salt
10:50 AndreasLutro salato: oh, then you have to specify the templates you're extending in your Saltfile. try a google for "salt-ssh jinja extend saltfile"
10:51 keimlink joined #salt
10:51 chrichip joined #salt
10:52 Taters_ joined #salt
10:53 amcorreia joined #salt
10:54 fannet joined #salt
10:55 salato AndreasLutro: gotcha, thanks
10:57 chrichip joined #salt
10:59 keimlink joined #salt
10:59 dariusjs joined #salt
11:05 teryx510 joined #salt
11:06 keimlink joined #salt
11:10 Rumbles joined #salt
11:11 chrichip joined #salt
11:19 chrichip joined #salt
11:27 chrichip joined #salt
11:28 ashmckenzie joined #salt
11:29 ronnix joined #salt
11:41 ttrumm joined #salt
11:42 ttrumm joined #salt
11:45 chrichip joined #salt
12:00 chrichip joined #salt
12:06 babilen I just stumbled over https://docs.saltstack.com/en/develop/topics/targeting/#targeting-with-executions -- Any idea what happened to that?
12:10 phx what would that feature be exactly?
12:13 babilen phx: My understanding is that this targetter would run an arbitrary command/execution function on all minions and then target a subset of them based on the return value
12:14 phx that might be useful in some setups
12:14 jhauser joined #salt
12:14 babilen I haven't seen it in use anywhere and the documentation references 0.8.8 (ancient salt version). It might have never seen the light of day, but I'm not sure (hence my question)
12:16 phx gladly, i'm not affected by that :)
12:18 phx i'm thinking more about orchestration, most probably I will have to use that feature to set up AFS cells (~clusters), and i'm bothered a bit, because the highstate doesn't do orchestration, and to do orchestration i had to call the salt-runner, which is specific to those clients who require orchestration
12:19 phx and not all of my minions require orchestration, but i would like to initiate the salt calls uniformly across all minions
12:19 jaybocc2 joined #salt
12:20 XenophonF AFS!!!
12:20 babilen AFS???
12:20 XenophonF my favorite mid-90s networked file system!!!
12:22 XenophonF phx: orchestration kind of has to run from a central location
12:22 XenophonF it's kind of the point
12:22 XenophonF and it replaces? complements? highstate jobs, which are decentralized by definition
12:24 edrocks joined #salt
12:31 phx AFS still has its valid usecases
12:33 phx XenophonF, i know they are different. just when it comes to that, i would prefer not to special case the two types of setups when i had to call salt to do the configuration
12:34 Taters_ joined #salt
12:39 dariusjs joined #salt
12:41 gh34 joined #salt
12:48 ssplatt joined #salt
12:50 numkem joined #salt
12:54 nicksloan joined #salt
12:58 quasiben joined #salt
13:01 akhter joined #salt
13:01 racooper joined #salt
13:03 west575 joined #salt
13:07 akhter joined #salt
13:08 ttrumm joined #salt
13:10 ferbla joined #salt
13:12 west575_ joined #salt
13:19 akhter joined #salt
13:20 AndreasLutro I treat salt orchestration as just "run highstates in some particular order". in the end if you run them randomly enough times on every server they will all be configured correctly in the end regardless but it's nice if they do so the first time round
13:21 AndreasLutro your highstate should be somewhat context aware anway. for example, I stop my performance metrics collection daemon if I can't find a server to receive the metrics in the salt mine
13:23 phx i don't think that's a valid usecase for orchestration
13:23 phx in case of an AFS cell, various commands needs to be run across the member boxes in order
13:24 mapu joined #salt
13:24 phx like 1) do X 2) when all member servers in the cell with role A finished with X, do Y 3) ...
13:24 phx otherwise you can start over
13:30 akhter joined #salt
13:31 Taters_ joined #salt
13:33 hasues joined #salt
13:35 quasiben joined #salt
13:36 akhter_1 joined #salt
13:36 hasues left #salt
13:38 keimlink joined #salt
13:39 ronnix joined #salt
13:41 Reverend joined #salt
13:41 chrichip joined #salt
13:44 ttrumm joined #salt
13:45 scoates joined #salt
13:47 chrichip joined #salt
13:49 dyasny joined #salt
13:51 teryx510 joined #salt
13:51 fannet joined #salt
13:53 XenophonF isn't that exactly what salt orchestration's supposed to be able to do?
13:54 Tanta joined #salt
13:56 NV joined #salt
13:58 armonge joined #salt
14:03 chrichip joined #salt
14:03 jerredbell joined #salt
14:05 DEger joined #salt
14:05 akhter joined #salt
14:07 salato I can't find info on this error, http://paste.debian.net/798131/ any hint? I'm using salt-ssh
14:08 salato when using salt (non -ssh) it works with the same config.
14:10 AndreasLutro could be that salt-ssh's python doesn't have access to the python mysql module while regular salt does
14:10 AndreasLutro not sure what could cause that though
14:11 salato this is a lot of pain
14:11 toanju joined #salt
14:11 AndreasLutro get used to it :p
14:11 AndreasLutro salt-ssh is a second class citizen
14:12 salato also it seems that the mysql_grants configures users able to login without password, weird
14:12 Guest53962 joined #salt
14:14 AndreasLutro mysql_grants doesn't manage passwords, mysql_user does
14:16 salato yes that was a typo, I have http://paste.debian.net/798175/ and mysql -u dbuser , let me access the console...
14:17 AndreasLutro are you sure the dbpass variable isn't an empty string or something? use state.show_low_sls to see what the highstate data looks like
14:21 akhter joined #salt
14:21 GreatSnoopy joined #salt
14:21 salato AndreasLutro: could this be it? http://paste.debian.net/798196/
14:22 AndreasLutro looks correct
14:22 AndreasLutro don't know what could cause your thing then
14:23 AndreasLutro use mysql's `show grants` to check if there is a password set
14:27 salato I still need to learn the correct syntax... what a mess
14:27 salato how do I specify mysql_database and mysql_user when the db name and db user are the same?
14:27 salato http://paste.debian.net/798198/
14:30 badon joined #salt
14:30 AndreasLutro just add a : after mysql_database.present
14:30 akhter joined #salt
14:30 BattleChicken joined #salt
14:32 salato http://paste.debian.net/798198/
14:32 salato ops
14:32 beardedeagle joined #salt
14:33 jenastar joined #salt
14:33 mage_ are pillar data only merged in the top file?
14:34 gh34 joined #salt
14:35 richardl question, how does one store a file in a salt-mine via a saltstate?
14:36 mage_ in pgbouncer/production.sls I'm include: - pgbouncer (init.sls) but pillar data are *not* merged unless pgbouncer is also added to the top file .. is it expected?
14:38 keimlink joined #salt
14:38 beardedeagle possibly dumb question: Is it possible to exclude states in the top.sls rather than explicitly calling out each state to run in a formula?
14:39 hasues joined #salt
14:39 hasues left #salt
14:40 beardedeagle nevermind, was a dumb question. figured it out.
14:41 Reverend I have a mysteriously appearing "client" minion D:
14:41 Reverend haha
14:45 akhter joined #salt
14:47 cmarzullo richardl: you'll want to use the module.run state. calling mine.send
14:49 sp0097 joined #salt
14:50 Heartsbane joined #salt
14:50 StolenToast can I use the mount state to mount up the contents of fstab?  Or do I need to use a cmd?
14:51 richardl cmarzullo: do you have an example of the function in use?
14:53 sp0097 joined #salt
14:58 akhter joined #salt
14:59 pipps joined #salt
15:02 ttrumm joined #salt
15:03 Rumbles joined #salt
15:05 jenastar left #salt
15:06 Reverend what does salt-master normally spew out when you sync_grains to a minion?
15:06 Reverend I just get "minion-name:"
15:06 phx XenophonF, it is, exactly. it just need to be called differently than how you call a highstate, because it's done differently :)
15:09 jfindlay eightyeight: u know pull request? :-)
15:09 eightyeight pfft
15:09 jfindlay lol
15:10 eightyeight are the docs in git?
15:10 sp0097 joined #salt
15:10 jfindlay yes
15:10 eightyeight github, or saltstack.com?
15:11 jfindlay https://github.com/saltstack/salt/tree/2016.3/doc
15:11 jfindlay you can even make a pull request right on github.com if you have an account
15:11 eightyeight i know how pull requests work. :)
15:12 jfindlay I mean, you can edit files on the website and send a pull request
15:13 eightyeight yeah. easier to sed(1) thtrough the text files though, and do one big pull request, instead of many small ones.
15:13 jfindlay the tutorial docs are here: https://github.com/saltstack/salt-get-started
15:13 eightyeight thx
15:16 akhter joined #salt
15:21 akhter joined #salt
15:23 Elsmorian joined #salt
15:23 jschoolcraft joined #salt
15:23 Elsmorian Hi all - is there some bug in the spec of some of the Salt packages on the 12.04 apt repo?
15:24 Elsmorian apt-get install salt-minion=2016.3.2+ds-1  results in salt-minion depends on salt-common (= 2015.8.8+ds-2); however:
15:24 Elsmorian Version of salt-common on system is 2016.3.2+ds-1.
15:25 Elsmorian salt-minion 2016.3.2's requirements looks fixed to an old version?
15:26 _W_ joined #salt
15:29 cmarzullo richardl: http://pastebin.com/w3zDJNxM
15:29 wm-bot4 joined #salt
15:30 kshlm joined #salt
15:31 Elsmorian Hmm- an apt-get remove salt-minon and then install again seemed to have fixed it...
15:32 west575 joined #salt
15:33 sp0097 joined #salt
15:36 edrocks joined #salt
15:37 nonades joined #salt
15:38 _JZ_ joined #salt
15:38 keimlink joined #salt
15:40 jimklo joined #salt
15:43 akhter joined #salt
15:47 turnagwf joined #salt
15:55 akhter joined #salt
15:56 quasiben joined #salt
15:56 edrocks joined #salt
15:58 tpaul joined #salt
16:01 pppingme joined #salt
16:03 austinpapp_ joined #salt
16:03 austinpapp_ im looking for a way to read a file and use that file as arguments to a cmd.run ... possible?
16:05 catpig joined #salt
16:06 mpanetta joined #salt
16:11 akhter joined #salt
16:13 mpanetta joined #salt
16:16 ALLmightySPIFF joined #salt
16:17 chrichip joined #salt
16:17 ALLmight_ joined #salt
16:23 debian112 joined #salt
16:26 edrocks joined #salt
16:27 Reverend can one include a grain as part of the filepath to a sourced file?
16:28 Reverend I'm hoping to use it as salt://nginx/files/GRAIN/nginx.conf
16:29 woodtablet joined #salt
16:32 tiwula joined #salt
16:32 Reverend oh - i got it. turns out it's just python
16:32 Reverend mybad.
16:32 Reverend 'print' >_<
16:35 quasiben joined #salt
16:36 shaggy_surfer joined #salt
16:37 cmarzullo Reverend: probably should use jinja {{ grain['id'] }}
16:40 akhter joined #salt
16:41 cyborg-one joined #salt
16:44 amcorreia joined #salt
16:46 noob__ joined #salt
16:49 turnagwf I just updated my minions to 2016.3.2-1.el7 now salt commands on the master (2016.3.2) return "minion did not return [Not connected]" I see the job come in on the minion logs. thoughts?
16:51 onlyanegg joined #salt
16:51 Reverend if you do a test.ping, do you get two of the same box return?
16:51 Reverend or in salt-keys are there a bunch of unsigned keys?
16:52 * Reverend is clutching at straws here, but dealt with similar problems earlier >_<
16:53 edrocks joined #salt
16:53 turnagwf no unsigned guys, and test ping returns the same thing.
16:55 Reverend is salt-minion running on the boxes? :S
16:56 turnagwf deleting /var/cache/salt seems to fix it :D
16:56 pipps joined #salt
16:56 pipps joined #salt
16:57 Reverend win.
16:57 * Reverend cheers!
16:58 brotatochip joined #salt
17:02 akhter joined #salt
17:07 sjmh joined #salt
17:07 edrocks joined #salt
17:12 onlyanegg joined #salt
17:13 jnials joined #salt
17:14 jaybocc2 joined #salt
17:17 shaggy_surfer joined #salt
17:21 jnials So, how does one batch orchestrations?  I want to stop a bunch of services, upgrade them, and then restart them across a number of machines, but I only want to do 20% at a time.
17:22 akhter joined #salt
17:26 shaggy_surfer joined #salt
17:31 ttrumm joined #salt
17:31 heaje joined #salt
17:32 RedundancyD joined #salt
17:33 akhter joined #salt
17:33 fracklen joined #salt
17:34 whytewolf jnials: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.saltmod.html#salt.states.saltmod.state go down to where it discribes batch:
17:35 edrocks joined #salt
17:36 brotatochip joined #salt
17:36 whytewolf jnials: just a FYI saltmod is the orchestration state modules. all the state modules listed in it are the functions that you call from orchestrate.
17:37 karthyk joined #salt
17:37 karthyk left #salt
17:41 Vaelatern For the state pip.install, how do I specify which python version to use? Is env_bin required?
17:44 ttrumm joined #salt
17:44 mapu joined #salt
17:44 jnials whytewolf: Thanks. That's good information I didn't have. :)
17:45 flowstate joined #salt
17:45 flowstate greetings all
17:46 flowstate anyone ever seen an issue where a minion will happily ignore all targeting (despite being listed as up), and only reconnect after a salt-call test.ping?
17:46 flowstate or any salt-call
17:46 flowstate no error messages on either side
17:46 flowstate and it's sporadic
17:46 flowstate like the minion goes to sleep
17:47 whytewolf Vaelatern: I do believe so.
17:47 brotatochip joined #salt
17:47 flowstate this is on AWS if that helps. Newest stable salt on both ends
17:47 flowstate it just silently ignores all input from master
17:48 whytewolf flowstate: not in a long time. used to have that on older versions of 0mq
17:48 flowstate huh, I'm on the right major version
17:48 flowstate maybe it's an Amazon Linux thing
17:49 whytewolf could be. it shouldn't be silently ignored. the master should at least say it didn't respond
17:49 flowstate yeah, just silent,that's the thing I am confused by
17:50 flowstate my only idea is that I have acronjob that does manage.not_alived removekeys=True
17:50 flowstate to remove minions that no longer exist due to scaling events
17:50 tuxx joined #salt
17:50 whytewolf humm. do you also auto accept keys?
17:51 flowstate yep
17:51 flowstate and do a salt * test.ping every minute to try and force the keepalive
17:51 whytewolf that might be it. it gets removed. then when salt-called is ran on it it wakes up and gets readded
17:52 flowstate hmm, so I can trade that problem for the one of my killed minions slowing all my salt calls
17:52 flowstate unless there's a better way to get rid of slayed minions
17:52 whytewolf events
17:53 flowstate !!
17:53 whytewolf and reactors
17:53 flowstate ooooh
17:53 whytewolf mixed with autoscale working with salt-api
17:53 flowstate so when I kill the minion, send an event to master?
17:53 flowstate ahhhh, salt-api
17:53 flowstate k
17:53 whytewolf yeap
17:53 flowstate very interesting
17:53 flowstate tyvm
17:53 flowstate see
17:54 flowstate sry, new keyboard... sigh
17:54 whytewolf hehe no problem
17:54 flowstate I'll see if that cron was the root of the issue
17:54 t0m0 joined #salt
17:54 whytewolf https://github.com/saltstack-formulas/ec2-autoscale-reactor check that out and see if it helps once you find out if the cron is the issue
17:55 whytewolf I don't know how upto date it is though
17:55 flowstate awesome, ty again!
17:55 whytewolf no problem
17:57 raspado joined #salt
17:58 q1x joined #salt
17:58 fer_bla joined #salt
18:02 netcho joined #salt
18:03 numkem joined #salt
18:06 quasiben joined #salt
18:13 jimklo joined #salt
18:14 brotatochip joined #salt
18:14 Taters_ joined #salt
18:16 flowstate joined #salt
18:19 akhter joined #salt
18:19 cscf What's a clean way to insure that no files exist in a given dir except those provided by Salt?
18:20 cmarzullo It's a yuky problem. I've done it where every file that could be created is managed from pillar. and the default state is absent. I do this with the collectd plugins.
18:21 Tanta render the managed files, and then chattr +i /dir/name
18:22 fannet joined #salt
18:22 Tanta or, to ensure perfect cleanliness, delete recursively, create, render managed files, then set immutable
18:23 cmarzullo I like that.
18:23 cscf There should be a state for managing and dir & contents
18:23 Tanta you mean like https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.recurse
18:23 Tanta can also do file.directory with 'recurse': https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.directory
18:24 cscf Oh that might be what I need
18:24 cmarzullo there's a clean argument. but havn't used it
18:28 west575_ joined #salt
18:29 xbglowx_ joined #salt
18:35 brotatochip joined #salt
18:36 shaggy_surfer joined #salt
18:36 pipps joined #salt
18:47 pipps joined #salt
18:51 netcho hy guys, whats the best practice of pulling git changes from salt master? i wanna put all states an pillars in a repo
18:52 flowstate joined #salt
18:52 cmarzullo git.latest
18:52 drawsmcgraw netcho: I think you're looking for the GitFS backend and Git ext_pillar, respectively.
18:54 akhter joined #salt
18:58 akhter joined #salt
18:59 netcho drawsmcgraw: yeah loks like it.. i just want master to automatically pulls changes on commit
19:00 drawsmcgraw netcho: Well it depends on how impatient you are. GitFS polls Git every 60 seconds by default
19:00 drawsmcgraw If you insist on "pull on commit", my thought is to use salt-api + Reactor
19:00 drawsmcgraw Where you just have a single Reactor state that runs the runner fileserver.update
19:00 netcho sweet
19:00 drawsmcgraw i.e. when I'm impatient, I log onto the Salt master and 'salt-run fileserver.update'
19:00 liskl joined #salt
19:01 netcho i am thinking more of a cron job :D
19:01 drawsmcgraw But that's when I'm impatient. Otherwise, the 60-second poll interval suits me fine.
19:01 drawsmcgraw If you're thinking cronjob, I'd just change the poll interval for GitFS to a value you'd rather it be
19:02 drawsmcgraw netcho: Ah, here we are! https://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html#refreshing-gitfs-upon-push
19:03 netcho sweet, thanks
19:03 drawsmcgraw Just saw a big caveat: "provided that the git server is also a Salt minion."
19:03 drawsmcgraw So if you're using Github or some other 3rd party, you'll need that salt-api layer to get what you want.
19:03 drawsmcgraw Anyway, good luck!
19:04 netcho yeah github is in place
19:04 netcho ok
19:04 netcho will test it
19:06 akhter joined #salt
19:07 agentnoel joined #salt
19:11 DammitJim joined #salt
19:11 akhter joined #salt
19:12 akhter joined #salt
19:14 akhter joined #salt
19:15 marie1972 joined #salt
19:19 liskl joined #salt
19:21 armonge joined #salt
19:36 flowstate joined #salt
19:43 onlyanegg Is there a way to the get the key name in jinja?
19:44 onlyanegg something like pillar.my.key|name()
19:47 Tanta in what context
19:47 Tanta if it's a {% for k,v in salt['pillar.get
19:48 Tanta ']('key') %} where key is a dictionary, you can use {{ k }} within the loop
19:48 marie1972 left #salt
19:48 onlyanegg not in the context of a loop
19:49 onlyanegg hmmm, well maybe I can use a loop
19:49 Tanta how would you get the name of a key, value pair when you must explicitly state the key name to access the value
19:49 Tanta unless you're iterating through an unknown list of keys in a for loop
19:50 bluenemo joined #salt
19:51 onlyanegg yeah... maybe I didn't think this one through, lol
19:51 onlyanegg thx!
19:51 pipps joined #salt
19:53 dyasny joined #salt
19:55 brotatochip joined #salt
20:00 shaggy_surfer joined #salt
20:00 aisha joined #salt
20:00 ajw0100 joined #salt
20:01 brotatochip joined #salt
20:03 sp0097 joined #salt
20:03 aisha Hello! I tried reading through the entire installation and documentation as well. Did exactly the same. I don't understand  why it runs to a loop when I to call my minon as daemon.
20:04 aisha I don't understand these things, but I am willing to learn, cos I think this will help in schools and stuff.
20:04 aisha Can I get some help with that please?
20:04 aisha :(
20:06 Elsmorian joined #salt
20:07 brotatochip joined #salt
20:07 ayesha joined #salt
20:13 ayesha joined #salt
20:14 curious_girl joined #salt
20:14 pipps joined #salt
20:18 dyasny joined #salt
20:18 ajw0100 joined #salt
20:19 haam3r joined #salt
20:22 pipps joined #salt
20:23 curious_girl joined #salt
20:24 sjmh joined #salt
20:28 akhter joined #salt
20:32 akhter_1 joined #salt
20:34 tedski left #salt
20:36 onlyanegg aisha, what is your question?
20:42 haam3r joined #salt
20:47 pipps joined #salt
20:48 pipps99 joined #salt
20:54 Taters_ joined #salt
20:54 BattleChicken left #salt
20:55 ajw0100 joined #salt
20:55 Salander27 joined #salt
20:59 MeltedLux joined #salt
21:04 Cottser joined #salt
21:06 haam3r joined #salt
21:07 bluenemo joined #salt
21:07 toanju joined #salt
21:09 pipps joined #salt
21:17 fas3r joined #salt
21:17 fas3r hello
21:19 whytewolf Greetings Starfighter, you have been recrutied by the Star League to defend the frontier against Xur and the Ko-dan armada.
21:19 mpanetta Arent they supposedly remaking that movie?
21:20 whytewolf most likely they remake everything now days
21:21 whytewolf oh apperently not
21:21 whytewolf the rights holder won't give up the rights so that a remake can be made
21:26 jnials good.  I like it the way it is.  So many remakes not as good as the original.
21:28 whytewolf I agree. watched it not to long ago. the speciel effects are just starting to show their age. can tell things like green screen models were used and what not. and the computer graphics are laughable by todays standards. but Beta still holds up well.
21:30 whytewolf besides who could they get to fill the shoes of Robert Preston as Centauri.
21:31 jnials Bingo!
21:34 mpanetta haha
21:36 brotatochip joined #salt
21:36 jimklo joined #salt
21:38 jnials Now, if the took the existing one and just updated the CGI a bit, that wouldn't be so bad.  But they always want to fiddle.
21:40 ronnix joined #salt
21:40 izibi joined #salt
21:40 netcho joined #salt
21:41 ssplatt joined #salt
21:45 ssplatt joined #salt
21:46 jimklo joined #salt
21:48 flowstate joined #salt
21:52 xbglowx joined #salt
21:55 chrichip joined #salt
21:57 keimlink joined #salt
21:58 ssplatt joined #salt
21:58 flowstate joined #salt
22:00 ssplatt joined #salt
22:04 jimklo joined #salt
22:04 fredrick joined #salt
22:05 fredrick So I changed the ip of my salt master, using dns.  But the minions are still trying to talk to old ip??
22:05 fredrick is there a clear I can use?
22:06 pipps joined #salt
22:07 pipps joined #salt
22:07 quasiben joined #salt
22:07 whytewolf have you tried turning it off and on again?
22:10 justanotheruser joined #salt
22:10 west575 joined #salt
22:12 fredrick I have
22:12 jimklo joined #salt
22:12 wryfi i have a tough question about salt and test kitchen (at lesast, it's mystifying to me)
22:13 wryfi i am using kitchen-salt to copy over my whole state tree
22:13 wryfi inside of my state tree, i have a _grains folder
22:13 wryfi with a python grain in it
22:13 ajw0100 joined #salt
22:13 wryfi when i run 'kitchen converge', the state tree is copied over. but the highstate that is run as part of 'kitchen converge' never loads my python grain
22:14 wryfi if i then log in to the running kitchen test machine, and manually run a highstate (or ask for the grain) it is there
22:14 wryfi am i missing a sync step somewhere, or what?
22:16 whytewolf wryfi: you most likely are running into the issue described in the warning at the bottom of this https://docs.saltstack.com/en/latest/topics/grains/#writing-grains
22:16 whytewolf basicly "Custom grains will not be available in the top file until after the first highstate."
22:18 wryfi whytewolf: that's what i was suspecting
22:18 wryfi do you know if it's documented anywhere what sync_grains actually *does*?
22:18 pipps joined #salt
22:18 * wryfi has already forked kitchen-salt and goes to hack on some ruby
22:18 whytewolf you mean like "Sync grains modules from salt://_grains to the minion"
22:19 whytewolf https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.saltutil.html#salt.modules.saltutil.sync_grains
22:19 ssplatt joined #salt
22:19 wryfi whytewolf: wasn't looking for the function definition, but what it actually *does*
22:19 wryfi presumably copying a file from your state tree into somewhere on a python path?
22:20 wryfi probably need to read the code :(
22:20 wryfi but i think i can proceed without it
22:21 whytewolf it copies it from salt://_grains to /var/cache/salt/minion/extmods/grains
22:21 wryfi ahh
22:21 wryfi thanks
22:23 whytewolf it also clears the grains cache if grains cache is set
22:24 fannet joined #salt
22:28 brotatochip joined #salt
22:33 fredrick Test kitchen what is this?
22:33 fredrick like the one chef uses?
22:33 whytewolf yes
22:34 fredrick is this documented.
22:34 whytewolf it is a third party thing
22:34 whytewolf https://github.com/simonmcc/kitchen-salt
22:34 fredrick That is awesome.  Great news
22:37 onlyanegg joined #salt
22:40 wryfi it's better than nothing, but i've had to fork kitchen-salt and make a lot of mods to it to get it to work in my environment
22:41 wryfi (one day i will try to encapsulate them and file a PR upstream)
22:41 netcho joined #salt
22:43 pipps joined #salt
22:46 pipps joined #salt
22:47 shaggy_surfer joined #salt
22:48 Rumbles joined #salt
22:54 shaggy_surfer left #salt
22:55 xbglowx joined #salt
22:58 Deliants joined #salt
23:07 akhter joined #salt
23:10 west575 joined #salt
23:10 ssplatt joined #salt
23:14 Deliant joined #salt
23:14 brotatochip joined #salt
23:18 Vaelatern I'm having issues installing python 3.4 on my OpenBSD machine with a pkg.installed state. All I get is: "Result: False\n Comment: The following packages failed to install/update: python=3.4.4"
23:24 subsignal joined #salt
23:25 ajw0100 joined #salt
23:29 Rumbles joined #salt
23:32 debian112 joined #salt
23:35 ronrib joined #salt
23:35 Deliants joined #salt
23:36 evidence hmm.. anyone ever done a git.latest in a schedule?  for some reason it refuses to work properly, and even a schedule.run_job logs no errors
23:36 evidence nshttpd://pastebin.com/6KZftkqT
23:36 ssplatt joined #salt
23:37 chrichip joined #salt
23:40 ssplatt joined #salt
23:40 teryx510 joined #salt
23:43 chrichip joined #salt
23:47 west575 joined #salt
23:52 keimlink_ joined #salt

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