Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-07-19

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

All times shown according to UTC.

Time Nick Message
00:02 pcdummy pwhack: your current state is that it works with nginx but not with the java repo?
00:03 pwhack @pcdummy i'm afraid the nginx repo is superfluous and might cause confusion in this scenario. at the moment i'm only trying to use the sun-java formula and git repo
00:04 pcdummy jdp99898: it should work
00:05 pcdummy jdp99898: found something: http://chwilliamson.me.uk/article/SaltStack-Masterless-Beginnings
00:06 pcdummy pwhack: did you try that mount-point thing?
00:06 pcdummy pwhack: i think you need to have a "sun-java/init.sls" folder right in the repo, you have that?
00:10 rem5 joined #salt
00:13 teryx510 joined #salt
00:15 woodtablet left #salt
00:16 teryx510 joined #salt
00:16 barmaley joined #salt
00:25 pwhack @pcdummy sorry, more interruptions. ok, yes, the master config does contain mountpoint: salt://sun-java  (http://pastebin.com/38ED33ie)    and 'sun-java' folder exists at the root of the repo so 'sun-java/init.sls' should be valid and accessible.
00:26 pwhack @pcdummy ahhhhhhh. i didn't bother reading one of the outputs...
00:26 racooper_ joined #salt
00:27 pwhack @pcdummy: one of the outputs i sent @whytewolf ('salt-run fileserver.file_list backend=git saltenv=development') (http://pastebin.com/WmpD8TrN)  shows '- sun-java/sun-java/init.sls'
00:29 gableroux_ joined #salt
00:29 gableroux_ left #salt
00:30 justanotheruser joined #salt
00:30 pwhack @pcdummy @whytewolf : at some point i had commented out '- root: sun-java' in my master config. that caused the double sun-java name. uncommented, restarted master service, now 'salt-run fileserver.file_list backend=git saltenv=development' shows correct output. now minion is able to highstate!    i don't recall how long ago today i commented out root for the gitfs_remotes.
00:32 MTecknology heh... is it possible to make a yaml file that loads other bits of the same thing? like, say.... http://dpaste.com/1VZK4C1
00:32 MTecknology which is totally silly and would never work, but at least it shows off what I'm trying to do..
00:33 infrmnt joined #salt
00:36 hemebond MTecknology: Yes
00:37 hemebond https://gist.github.com/bowsersenior/979804
00:37 hemebond Assuming my fix is in the version you're running.
00:37 hemebond https://github.com/saltstack/salt/issues/14550
00:37 saltstackbot [#14550][MERGED] Using YAML anchors/references in Pillars causes conflicting IDs | How to reproduce:...
00:39 flowstate joined #salt
00:40 gableroux @whytewolf I found it, I don't know how I managed to write this, but repo url had ssh:// in front of it, that was wrong
00:41 rem5 joined #salt
00:43 kevinquinnyo1 joined #salt
00:50 netcho joined #salt
00:57 MTecknology hemebond: 1) neat 2) heh, interesting 3) Thanks!
01:00 etangle joined #salt
01:00 etangle can salt-cloud provision rackspace cloud db instance ?
01:03 rem5 joined #salt
01:06 brotatochip joined #salt
01:09 etangle can salt-cloud be used for openstack trove database
01:15 rem5 joined #salt
01:17 catpigger joined #salt
01:17 k_sze[work] joined #salt
01:18 DEger joined #salt
01:20 Nahual joined #salt
01:22 Brijesh1 joined #salt
01:29 bilal80 left #salt
01:29 iceyao joined #salt
01:31 MeltingFiction joined #salt
01:40 flowstate joined #salt
01:41 Brijesh1 joined #salt
01:48 ilbot3 joined #salt
01:48 Topic for #salt is now Welcome to #salt! | Latest Versions: 2015.5.10, 2015.8.10, 2016.3.1 | 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 pwhack @pcdummy @whytewolf: it turns out the 'gitfs_base' statement was the cause of the problems (after i uncommented the root statement). thanks for all your help!
01:50 Rikil joined #salt
01:55 MeltingFiction joined #salt
02:01 flowstate joined #salt
02:13 brotatochip joined #salt
02:15 Rikil joined #salt
02:27 writtenoff joined #salt
02:28 Rikil joined #salt
02:36 |_[O_O]_| joined #salt
02:40 Brijesh1 joined #salt
02:42 bastiandg joined #salt
02:51 netcho joined #salt
02:57 sabo joined #salt
02:57 rem5 joined #salt
03:06 RickLee joined #salt
03:07 RickLee joined #salt
03:07 flowstate joined #salt
03:12 evle joined #salt
03:23 treaki__ joined #salt
03:46 DEger joined #salt
04:04 FreeSpencer joined #salt
04:04 FreeSpencer joined #salt
04:14 ivanjaros joined #salt
04:15 rem5_ joined #salt
04:39 flowstate joined #salt
04:41 POJO joined #salt
04:41 Bryson joined #salt
04:52 netcho joined #salt
04:57 lompik joined #salt
05:06 felskrone joined #salt
05:13 armyriad joined #salt
05:25 nidr0x joined #salt
05:32 jonky joined #salt
05:32 jonky hi
05:33 jonky are there any recommended IDE's and/or plugins that aid salt development?
05:33 jonky specifically im looking to navigate to definitions and locating usages
05:37 flowstate joined #salt
05:40 hemebond jonky: Sublime Text?
05:40 hemebond Any Python IDE should help out some.
05:41 jonky i have sublime text with the saltstack plugin installed, but I don't see any "navigate to.." options anywhere
05:41 hemebond Go to definition
05:41 hemebond Works with most languages I think.
05:42 hemebond There's also CTRL+R
05:42 hemebond And CTRL+P
05:43 jonky im looking for something more powerful like found in the jetbrains IDEs
05:44 hemebond Doesn't Jetbrains have a Python IDE?
05:44 jonky yes, but there's no support for saltstack
05:44 hemebond PyCharm
05:44 hemebond Well, Salt is just Python.
05:45 jonky im talking about for sls files
05:45 hemebond Oh, well, I mean, they're just Jinja and YAML.
05:47 jonky that doesn't help if there's no salt context to tell the IDE what each line means
05:47 jonky maybe im not asking my question right
05:47 hemebond Oh I see what you're after.
05:47 jonky let me find an exanoke
05:47 jonky example
05:47 hemebond I thought you meant Salt itself.
05:47 hemebond Not something to help you write states.
05:48 jonky ah, yea
05:48 hemebond I know the Sublime Text addon for Salt is always trying to insert things as I type.
05:48 hemebond But probably not as clever as what you're after.
05:48 jonky well, i dont necessarily need anything to help me write a salt state
05:48 jonky just to help with navigate
05:48 hemebond To... the docs?
05:49 jonky our salt state at work has 1957 files, and it'd be nice to navigate between references easier
05:49 netcho joined #salt
05:49 hemebond The state IDs?
05:50 jonky what do you mean?
05:50 hemebond "navigate between references"
05:50 hemebond Trying to understand what "references" means in the context of a Salt state file.
05:50 jtang joined #salt
05:50 hemebond I assumed state IDs.
05:50 garphy joined #salt
05:52 DEger joined #salt
05:54 jonky for example, https://dpaste.de/13Nb#L
05:54 jonky I would like a way to quickly navigate to whatever baseline, tool, and system,user.someuser are
05:54 hemebond Ah
05:54 jonky and then navigate back
05:54 hemebond Well that's where I'd probably already use CTRL+P
05:55 hemebond But I see now what you're after.
05:55 hemebond I don't know of anything that would do that for you. Perhaps someone else does.
05:55 SaganMan joined #salt
05:55 jonky i haven't found anything yet :)
05:55 jonky i think i'll have to write a plugin
05:55 hemebond Yeah, it's an odd one. I mean, they're just file references.
05:56 hemebond I thought you meant within a state file.
05:56 jonky they're file references, but dotted like python paths, so it's a little less straight forward
05:57 rdas joined #salt
05:57 jonky less straight-forward for a plugin i mean
05:58 jonky thanks for your input all the same
05:58 jonky what is ctrl-p?
05:58 jonky im not seeing anything useful
05:58 hemebond Sublime Text goto anything doesn't seem to take directories into account.
05:58 hemebond CTRL+P is Goto Anything.
05:58 jonky ah
05:59 hemebond Doesn't seem to be working for me though.
05:59 jonky yea, doesn't work with dotted paths
06:00 hemebond no but I thought it picked up directory names.
06:00 hemebond Oh wait, the file doesn't exist :-P
06:01 hemebond Okay, it works well.
06:01 hemebond Just put spaces instead of dots.
06:01 SaganMan left #salt
06:02 impi joined #salt
06:02 hemebond e.g., typing "system user someuser" would work if I had that file.
06:02 jonky yea, i follow
06:03 jonky i guess im just spoiled and dont want to keep typing :)
06:05 iceyao joined #salt
06:06 hemebond :-)
06:09 aw110f joined #salt
06:12 aw110f__ joined #salt
06:14 jtang joined #salt
06:28 iceyao joined #salt
06:37 iceyao_ joined #salt
06:39 flowstate joined #salt
06:43 goldielox joined #salt
06:46 ninjada joined #salt
06:53 garphy joined #salt
06:58 ribx joined #salt
07:02 watersoul joined #salt
07:03 fracklen joined #salt
07:03 sarlalian joined #salt
07:06 fracklen joined #salt
07:09 AirOnSkin joined #salt
07:16 ninjada_ joined #salt
07:18 rubendv joined #salt
07:18 rubendv joined #salt
07:19 Laidback joined #salt
07:24 msn joined #salt
07:25 msn the saltstack-formula for php is missing some parts. it mentions php.dotdeb but no such file and again it check for dotdeb frm pillar or the php:version but no such variable exists
07:25 msn is it intentional
07:26 ajw0100 joined #salt
07:26 kawa2014 joined #salt
07:26 babilen msn: Sounds like a bug in the formula -- https://github.com/saltstack-formulas/php-formula/issues/99
07:26 saltstackbot [#99][OPEN] php state mention unexistent state | While updating my internal php-formula just mentioned ``php/init.sls`` includes ``php.dotdeb`` which is not existent here....
07:31 impi joined #salt
07:32 babilen msn: That should only be a problem on Jessie and if you try to install PHP 7.0 though
07:33 msn that's exactly what i am doing
07:34 ninjada joined #salt
07:35 babilen I guess you'll have to implement php.dotdeb yourself then. Presumably that contains a pkgrepo.managed state that configured dotdeb repositories, but the person who submitted that PR (ages ago) never contributed that state, so we can only guess.
07:35 msn np
07:35 msn i was about to do that
07:35 msn was just making sure i didn't miss anything
07:36 babilen You didn't. I'd happily merge a PR once you have your php.dotdeb state
07:37 babilen I guess a simple pkgrepo.managed state for "deb http://packages.dotdeb.org jessie all" is all you need.
07:38 msn yup
07:38 babilen Or make that "deb http://packages.dotdeb.org {{ grains['oscodename'] }} all" :)
07:38 flowstate joined #salt
07:40 msn yeah I was thinking more of instead of dotdeb make it php7 repo so redhat can have remi repos and deb and have dotdeb
07:40 babilen Ah, and the code is broken in more than one way as oscodename is "jessie" not "Jessie"
07:40 ravenx joined #salt
07:40 babilen msn: Something like that.
07:41 babilen God, what a broken PR
07:41 msn guess I would be fixing it slowly
07:42 msn and it got merged
07:43 babilen You really have to wonder if the submitter even tried it once
07:43 babilen Anyway, it is relatively obvious what needs to be done.
07:44 babilen Ping me if you submit a PR, I'll happily merge it
07:44 babilen (maybe just sort out the "Jessie" → "jessie" rename and the pkgrepo.managed state for now)
07:44 ivanjaros joined #salt
07:48 msn that's not the only thing broken
07:48 msn the init is cehcking for php:version which doesnt exist in pillar
07:48 garphy joined #salt
07:49 msn i don't think someone tried using it yet
07:49 keimlink joined #salt
07:51 netcho joined #salt
07:55 krymzon joined #salt
07:56 ninjada joined #salt
08:00 manji joined #salt
08:00 JohnnyRun joined #salt
08:01 TyrfingMjolnir joined #salt
08:01 ronnix joined #salt
08:06 armyriad joined #salt
08:06 Rumbles joined #salt
08:08 iceyao joined #salt
08:10 iceyao_ joined #salt
08:12 badon joined #salt
08:14 toanju joined #salt
08:23 GreatSnoopy joined #salt
08:25 ravenx joined #salt
08:37 flowstate joined #salt
08:39 armyriad joined #salt
08:43 impi joined #salt
08:46 s_kunk joined #salt
08:49 ronnix joined #salt
08:53 huyby joined #salt
08:58 zer0def joined #salt
09:03 hereiam_ joined #salt
09:04 hereiam_ just curious: the order in which the terminal print out appears when running salt '*' state.highstate, is that the order of execution on the node?
09:05 hemebond hereiam_: I think it is.
09:06 hemebond I probably shouldn't have answered really as I'm not sure.
09:07 hereiam_ hemebond: Not a problem, because I noticed odd occurrences of unpredictable ordering of terminal printouts after state.highstate. I have lots of require and require_in statements and just wish to know that they are actually executed in the correct order.
09:08 hemebond I would assume they are since states are executed sequentially.
09:08 hemebond The other might change where explicit order is not enforced.
09:08 hemebond Or where Salt has to move a state to a different place to enforce order.
09:09 lero joined #salt
09:10 AndreasLutro salt's state ordering can be kinda random at times, but require/require_in is always respected in my experience
09:12 ozux joined #salt
09:14 hereiam_ AndreasLutro: I shall implement more require and require_in since the states are executed in different order at different times.
09:16 fredvd joined #salt
09:17 hemebond Interpolation (I think) http://paste.debian.net/783054/ :-)
09:18 hemebond Works in Salt itself too.
09:24 JohnnyRun joined #salt
09:30 Harris joined #salt
09:30 Harris How can you pass pillarenv to a 'salt.state' of orchestrate ?
09:33 tho joined #salt
09:35 babilen hereiam_: Well, blocks of states might be executed at different times, but the dependencies between individual states should still be the same (state A always after state B)
09:35 babilen Questions like Harris' make me happy that I don't use environments
09:36 ronnix joined #salt
09:36 ninjada joined #salt
09:37 hereiam_ babilen: Thanks a lot for this info. I figured out a way to separate my states so they always run in the order I want them to except when it is necessary to be flexible. I guess salt can flexibly change ordering of state execution depending on the current state of the system right, in order to uphold dependencies?
09:38 flowstate joined #salt
09:39 babilen hereiam_: Well, either there is a requirement to run state A after state B or there isn't. I'd only specify actual requirements and then there would also be no need "to be flexible"
09:40 babilen You are essentially saying "Just ensure that this states executes later than this other state" and salt comes up with a suitable order.
09:41 ozux What is the diff between state.highstate and state.apply? (In official docs it says use state.apply but in many books it's state.highstate )
09:42 hemebond ozux: state.apply applies a single state.
09:42 hemebond state,highstate applies every state targeted at the minion from the top.sls
09:43 ozux @hemebond exactly that's my impression, but https://docs.saltstack.com/en/latest/ref/states/layers.html#highstate
09:43 ozux My question is if it's internally makes difference if I run "salt '*' state.apply"  or "salt '*' state.highstate" ?
09:44 ozux or does it effect how I create the tops.sls
09:44 hemebond I don't believe there's a difference internally.
09:44 ozux @hemebond Thanks :)
09:44 hemebond top,sls is what you want highstate to apply.
09:46 babilen ozux: state.apply was developed later and subsumes the functionality of both state.highstate (if called without an argument) and state.sls (if called with the name of a state)
09:46 babilen Which is why you find state.apply in current documentation, while a lot of people and books still use the "old" state.highstate or state.sls
09:47 hemebond state.apply reads top.sls?
09:47 hemebond Oh wow.
09:47 babilen It does
09:47 babilen It is "state.highstate" if called without arguments and "state.sls" if called with an argument
09:47 hemebond Learned something new today :-)
09:47 ozux @babilen Aha, it explains a lot, yeah the book we got is "Mastering SaltStack 2015"
09:47 hemebond I'll probably forget it though, since highstate is engrained now.
09:48 babilen It was probably meant to simplify the way states are called, but the sitaution right now is that there are four concurrent ways
09:48 ozux And what about if I want to list all my hosts which are in test,dev,prod environments?  Without looking at top.sls
09:48 ozux Something like salt \* test.ping  saltenv=prod  but test,ping fucntion does not suppport saltenv
09:48 babilen Unfortunately state.apply does not (yet?) support state.sls_id which isn't very user friendly
09:49 babilen Either there is a single way to call all sorts of states or there isn't
09:49 babilen ozux: I really wouldn't recommend to use environments
09:49 ozux babilen: And what is the alternative for it?
09:50 ozux babilen: Or better way to do it
09:50 babilen We use different masters
09:50 notnotpeter joined #salt
09:50 babilen Found environments to be really pesky, broken and annoying and .. well .. just couldn't be bothered.
09:50 ozux Different masters on same server? or masters on different instances ?
09:51 babilen Also the fact that git branches automatically become environments in GitFS is annoying as fuck
09:51 ozux yes exactly
09:51 babilen ozux: Different instances
09:51 fracklen babilen: Totally agree
09:51 ozux Aha
09:51 ozux And u do master of masters, or just master?
09:51 babilen fracklen: Let me check if you can disable that
09:51 ozux we have buch of masters for different zones and networks internally, which is a pain already :P
09:51 garphy joined #salt
09:52 babilen ozux: No syndic, separate environments completely
09:52 babilen (but note, that is just one approach)
09:52 babilen I feel your pain
09:52 babilen Shouldn't be too horrible with syndic though or is it?
09:52 ozux And if I stuck with thousands of nodes and already setup Master with environments, is there any way I look for which instance is on which environment?
09:53 babilen Can't they be in more than one?
09:53 hemebond I use fqdn as minion IDs to help with environments.
09:54 fracklen babilen: Coming from Chef, environments in Saltstack just doesn't seem as powerful a concept. The GitFS trouble just made it worse :)
09:54 hemebond Salt environments don't isolate minion the way you'd expect them to.
09:54 babilen fracklen: It is a complete nightmare and I really don't understand why they ever thought that implementing environments like this would be a good idea
09:55 hemebond Setting the environment in the minion config helps.
09:55 babilen Exactly!
09:55 Rumbles hmmm I wanted to do a state.apply on a load of hosts, they gave an error saying tate.apply wasn't available, so I did a refresh_pillar, a number of hosts returned true and now those hosts will apply the state
09:55 Rumbles however a load of hsots returned None to the refrsh_pillar and still won't state.apply
09:55 babilen Yeah, but then you are constantly playing the "which environment is it really?" game and get into hell as soon as you want environments to share certain "base" states
09:56 hemebond Rumbles: Possibly an error in the pillar compilation.
09:56 babilen Rumbles: I've never seen that
09:56 babilen Rumbles: Could you provide more information on a pastebin maybe?
09:56 hemebond False or None means the refresh didn't work.
09:56 Rumbles okay, not sure what information would be useful at this stage
09:57 Rumbles hemebond, any way to get some diagnostic info about why it failed?
09:57 N-Mi joined #salt
09:57 babilen fracklen: https://docs.saltstack.com/en/latest/ref/configuration/master.html#gitfs-env-whitelist might help
09:57 fracklen babilen: Thanks a lot!
09:57 hemebond Rumbles: Try a pillar.items for a failing minion.
09:58 babilen fracklen: All I wish for is a "gitfs_no_env_mapping: True" setting
09:58 hemebond The master log will contain errors. Might need debug logging enabled.
09:58 fracklen Yes - exactly
09:58 babilen fracklen: I loved it when we had problems because somebody pushed a branch to the git repo and it fucked up everything because salt immediately used it as environment
09:59 hemebond babilen: How did it break things?
09:59 hemebond Oh wait. I guess it had a top.sls in it.
10:01 babilen hemebond: It's been a while, but it was something like that, yeah
10:01 babilen hemebond: The minion was suddenly in a different environment and not all formulas were available (as they only have one branch)
10:01 hemebond That sounds odd.
10:02 hemebond Oh wait, top.sls can do that.
10:02 babilen It's been a while and I can't recount the exact circumstances ..
10:03 babilen It was a "Why on earth is this not working" -- "WTF, environments!" -- "git push :some-branch-we-wanted-to-collaborate-on" moment
10:03 babilen https://github.com/saltstack/salt/issues/34775
10:03 saltstackbot [#34775][OPEN] Please allow users to disable branch environment mapping in GitFS | Description of Issue/Question...
10:03 hemebond Yeah. It's the reason my minion IDs are like fqdn and each top.sls applies only to a single "domain".
10:04 babilen If I could change two things in salt I'd completely rework the environment handling and switch mako for jinja
10:04 hemebond Switch the default to mako? Hmm.
10:04 hemebond I haven't used Mako at all.
10:05 cyborg-one joined #salt
10:05 fracklen babilen: We've opted to disable GitFS and have the master highstate update from git. A bit cumbersome - bug debuggable and predictable :)
10:05 k_sze[work] when using file.recurse, does the target directory need to exist already/
10:06 babilen hemebond: One thing that makes mako infinitesimaly more useful than jinja is the fact that you can include literal Python blocks in which you have access to the entire stdlib. That allows you to do some "heavy lifting" in the states without having to go "full Python".
10:07 mikecmpbll joined #salt
10:07 kbaikov joined #salt
10:07 babilen hemebond: mako was essentially designed for rendering websites where *all* data anlysis and logic was in the background ... The fact that salt doesn't allow users to easily extend jinja filters doesn't make it better
10:07 babilen But it's way too late for that now
10:07 hemebond Have you changed to Mako in your setup?
10:08 babilen No
10:08 hemebond Ah...
10:08 hemebond I suppose it would require editing all the formulas.
10:08 hemebond Oh, but you could use Mako in your states.
10:09 babilen I would have loved to, but I can't even set "default_renderer" as salt doesn't force you to set the renderer in the shebang in every SLS .. there just is too much code out there that relies on the fact that #!jinja|yaml is the default
10:09 babilen And some colleagues already have problems accepting two renderers (we shell out to #!py when necessary)
10:10 babilen Adding another one into the mix is just increasing the learning curve
10:10 babilen Maybe I should have forced us to use mako (or another more powerful renderer) right from the beginning, but at that point I didn't realise how limited jinja is
10:13 hemebond Isn't it easier to just use !py?
10:14 babilen Easier than what?
10:14 babilen mako?
10:15 hemebond Using python inside a templating language
10:15 hemebond Makes me think of PHP :-D
10:15 babilen It's the little things .. I'd love to be able to easily split data with regular expressions and use some itertools functionality (zip for example) in templates
10:16 babilen Sometimes you don't need "much more", but just that one step more
10:16 hemebond regex is a big one. It is a shame it's not easy to register new filters.
10:16 babilen In jinja you are now forced to *always* implement that functionality in your own execution module
10:17 babilen hemebond: I have planned for a long time to implement support for easier custom jinja filters .. it actually isn't that hard to do, but I haven't found the time
10:17 babilen https://github.com/saltstack/salt/issues/28236
10:17 saltstackbot [#28236][OPEN] Feature: Allow users to define custom jinja filters in _filters | It would be awesome to be able to easily extend the jinja renderer ourselves as detailed in http://jinja.pocoo.org/docs/dev/api/#custom-filters...
10:17 hemebond We could at least lift the regex stuff from Ansible and merge it into Salt :-)
10:18 babilen hemebond: You can't do that as the licenses are incompatible
10:19 hemebond Nuts.
10:20 notnotpe_ joined #salt
10:22 jhauser joined #salt
10:29 irctc417 joined #salt
10:29 irctc417 Is it possible to set a CORS header using just Salt-API Cherry, or do I need to put things through NGINX?
10:33 goudale joined #salt
10:38 whaity_ joined #salt
10:39 flowstate joined #salt
10:41 DEger joined #salt
10:41 hereiam_ babilen: Do you think that I should default to imperative states and declare requirements only if absolutely needed?
10:42 babilen hereiam_: What do you mean by "imperative states" ?
10:42 hemebond Implied?
10:42 hemebond implied order?
10:43 hereiam_ babilen: like making sure that I write the state A before state B which is parsed one after the other. Hence the order will always be A, then B. This apparently is imperative according to the documentation.
10:43 babilen "implied" is the word, yes
10:44 babilen Well, either there is a dependency between those state or there isn't. Why do you want "state A" to run before "state V"
10:44 babilen s/V/B
10:46 hereiam_ Should I put imports from jinja at the very top of a file? If so should i also put it before or after include statement? Example: {% from "jenkins/map.jinja" import jenkins with context %}
10:46 ninjada joined #salt
10:52 badon joined #salt
10:54 teryx510 joined #salt
11:02 amcorreia joined #salt
11:05 fracklen joined #salt
11:06 fracklen joined #salt
11:07 fracklen joined #salt
11:09 fracklen joined #salt
11:10 fracklen joined #salt
11:22 whaity__ joined #salt
11:23 impi joined #salt
11:29 ribx joined #salt
11:31 XenophonF hereiam_: yes, because everyone else does it that way
11:31 XenophonF jinja imports/loads should be at the very top of the file
11:32 XenophonF https://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html
11:32 hereiam_ XenophonF: inspecting the salt-formula for jenkins: https://github.com/saltstack-formulas/jenkins-formula/blob/master/jenkins/plugins.sls I found that they actually put the jinja import after include. Is this optional or required? I will try it out now.
11:34 Roelt joined #salt
11:37 flowstate joined #salt
11:39 fredvd joined #salt
11:48 impi joined #salt
11:52 emaninpa joined #salt
11:54 badon joined #salt
12:02 cliffstah joined #salt
12:04 XenophonF that's kind of confusing IMO
12:08 TooLmaN joined #salt
12:14 calve joined #salt
12:15 rem5 joined #salt
12:15 ALLmightySPIFF joined #salt
12:16 ALLmight_ joined #salt
12:19 ribx joined #salt
12:21 iceyao joined #salt
12:23 hemebond Can anyone confirm for me that salt['mine.get'] works in Jinja?
12:23 hemebond Anyone successfully using it?
12:25 calve afair I had trouble doing this
12:25 calve but this is just a feedback from a stranger on the internet, try it yourself
12:26 hemebond Thanks, I am trying. It's not working for me.
12:26 hemebond Still trying to find explicit examples in the docs.
12:28 hemebond Okay, I'm trying to use it in a Pillar. That might not be supported.
12:30 fracklen joined #salt
12:30 hemebond Which I suppose makes sense when you consider where the mine.get would normally be run.
12:30 hemebond i.e., the minion, not the master.
12:31 hemebond https://github.com/saltstack/salt/issues/11509
12:31 saltstackbot [#11509][MERGED] Exception when using Salt mine from pillar | ```...
12:36 fracklen joined #salt
12:38 flowstate joined #salt
12:39 gableroux joined #salt
12:42 DEger joined #salt
13:05 bastiandg joined #salt
13:05 gh34 joined #salt
13:07 brd joined #salt
13:08 garphy joined #salt
13:11 numkem joined #salt
13:12 catpig joined #salt
13:15 subsigna_ joined #salt
13:16 jhauser joined #salt
13:19 CIAguy joined #salt
13:21 bastiandg joined #salt
13:21 Rumbles joined #salt
13:29 mpanetta joined #salt
13:30 CIAguy left #salt
13:31 mpanetta joined #salt
13:31 CIAguy joined #salt
13:31 protoz joined #salt
13:31 CIAguy left #salt
13:38 flowstate joined #salt
13:43 XenophonF joined #salt
13:55 babilen hemebond: https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.mine.html#salt.modules.mine.get has documentation on how to use it in the pillar
13:55 ribx joined #salt
13:56 skinnejo joined #salt
13:58 infrmnt joined #salt
14:03 Tanta joined #salt
14:06 kawa2014 joined #salt
14:07 scoates joined #salt
14:09 infrmnt joined #salt
14:09 ninjada joined #salt
14:13 bowhunter joined #salt
14:14 kshlm joined #salt
14:18 hasues joined #salt
14:18 hasues left #salt
14:31 darvon joined #salt
14:31 pfallenop joined #salt
14:32 edrocks joined #salt
14:33 perfectsine joined #salt
14:34 infrmnt joined #salt
14:35 kaushal_ joined #salt
14:36 sfxandy joined #salt
14:36 sfxandy hi everyone
14:36 darvon joined #salt
14:36 pfallenop joined #salt
14:41 Rumbles joined #salt
14:42 ALLmightySPIFF joined #salt
14:43 Brew joined #salt
14:43 stotch joined #salt
14:43 DEger joined #salt
14:45 KingJ joined #salt
14:51 tapoxi joined #salt
14:52 dfinn joined #salt
14:52 tapoxi anyone using salt for monitoring?
14:57 kawa2014 joined #salt
15:01 sfxandy go on tapoxi ...
15:01 tapoxi hah, I'm just curious about experiences with monitoring with salt as opposed to sensu etc
15:02 Tanta I use Salt to manage cron jobs that collect monitoring metrics and feed them into cloud watch
15:03 Tanta not sure that using Salt bare is a good idea since you will have to build a monitoring and alerting framework around it
15:04 sfxandy i use beacons and reactors to alert when certain thigns have changed and to take remedial action
15:05 flowstate joined #salt
15:05 tapoxi sfxandy are you monitoring file changes and the like or system info?
15:05 flowstate joined #salt
15:06 sfxandy using inotify beacons to detect config file changes
15:07 dfinn joined #salt
15:08 anotherZero joined #salt
15:09 ekristen joined #salt
15:09 mapu joined #salt
15:11 Brijesh1 joined #salt
15:15 autofsckk joined #salt
15:16 coval3nce joined #salt
15:16 ronnix joined #salt
15:21 PeterO joined #salt
15:26 PeterO_ joined #salt
15:29 morissette joined #salt
15:29 brotatochip joined #salt
15:30 kaptk2 joined #salt
15:31 corichar joined #salt
15:34 Garo_ joined #salt
15:40 manji joined #salt
15:43 scooby2 joined #salt
15:44 kawa2014 joined #salt
15:44 kshlm joined #salt
15:47 spuder joined #salt
15:50 tuxx joined #salt
15:50 tuxx hey guys.. when i try to highstate a host, i get a "conflicting id" error... can someone tell me how to resolve which id exactly is conflicting?
15:50 tuxx i really think that it wld be super nice of salt to tell you what exactly is conflicting rather than leaving it for you to guess
15:51 gtmanfred it should give you that in the error message
15:51 flowstate joined #salt
15:51 tuxx Rendering SLS 'base:p.host1' failed: Conflicting ID 'Directory'
15:52 tuxx thats all i get
15:52 gtmanfred Directory is the name of the state that is conflicting
15:52 gtmanfred and it is in your p.host1 state file
15:52 tuxx gtmanfred: oh :D
15:52 gtmanfred local:
15:52 gtmanfred - Rendering SLS 'base:this' failed: Conflicting ID 'test'
15:52 gtmanfred which is /srv/salt/this.sls
15:52 gtmanfred and has two test ids
15:52 tuxx sorry then .. my fault
15:53 gtmanfred no worries :)
15:55 SpX joined #salt
16:04 lero joined #salt
16:04 tuxx left #salt
16:10 sabo joined #salt
16:10 DammitJim joined #salt
16:13 brent_ joined #salt
16:14 flowstate joined #salt
16:16 brotatochip joined #salt
16:18 writtenoff joined #salt
16:25 edrocks joined #salt
16:25 egor joined #salt
16:26 impi joined #salt
16:33 onlyanegg joined #salt
16:36 ronnix joined #salt
16:39 Brijesh1 i am new to salt , is there any book or video from where i can start from beginning to advance
16:40 woodtablet joined #salt
16:40 riftman joined #salt
16:41 mpanetta joined #salt
16:41 gtmanfred I have heard that coltons book is pretty good, and he just finished the sconed edition https://www.amazon.com/dp/1785881906
16:42 mpanetta joined #salt
16:42 Edgan joined #salt
16:45 Brijesh1 Thanks gtmanfred
16:49 berto- joined #salt
16:50 XenophonF Brijesh1: feel free to take a look at my public salt-states and pillar data repos
16:51 XenophonF Brijesh1: https://github.com/irtnog/salt-states, https://github.com/irtnog/salt-pillar-example, and a variety of formulas in various states of decay, to allude to the Classic Who serial
16:51 Brijesh1 sure, Thanks a lot XenophonF
16:52 aw110f joined #salt
16:52 XenophonF i strongly recommend reading through https://github.com/saltstack-formulas, too
16:53 XenophonF starting out, stick to simple states like pushing a file to a server or running a command (but only running it once or only running it when necessary)
16:53 ivanjaros joined #salt
16:53 sfxandy idempotence XenophonF
16:54 sfxandy :)
16:54 XenophonF exactly
16:54 brd XenophonF: yay poudriere :)
16:54 XenophonF haha i'm a big freebsd geek
16:55 brd XenophonF: I am a FreeBSD committer :)
16:55 * XenophonF is not worthy to be in the presence of someone with commit bits.
16:56 XenophonF i need to revisit the poudriere states
16:56 brd XenophonF: pfft, just send patches and you can have your very own :)
16:57 brd XenophonF: https://github.com/irtnog/salt-states/blob/master/top.sls references a bunch of other sls files, are those online somewhere?
16:57 XenophonF brd: yes, other branches of the same repo
16:58 brd ohh, cool
16:58 XenophonF and if not there, then the states come from the saltstack-formulas organization
16:58 brd XenophonF: I really need to play with salt's integration with git
16:58 XenophonF which i tend to fork into my own account
16:59 brd gotcha
17:00 brd XenophonF: thanks! :)
17:01 XenophonF you're welcome!
17:02 brd I am trying to learn enough Salt that I can justify replacing an existing Puppet setup at a contract I just obtained
17:03 sfxandy you'll learn plenty in here brd, i have!
17:04 brd sfxandy: yeah! that is why I try to grab links like those when they are posted, so I can go learn :)
17:04 sfxandy indeed.
17:04 spuder_ joined #salt
17:05 emaninpa joined #salt
17:05 brotatochip joined #salt
17:10 ninjada joined #salt
17:11 brent_ joined #salt
17:16 mapu joined #salt
17:17 artemz joined #salt
17:18 ronnix joined #salt
17:19 fracklen joined #salt
17:22 protoz joined #salt
17:22 manji joined #salt
17:23 ronnix joined #salt
17:24 WKNiGHT joined #salt
17:26 bowhunter joined #salt
17:27 Brijesh1 joined #salt
17:28 egor I'm working on getting a jinja template to work for me.  I have pillar data which the target host can view, but something isn't right in my jinja template.
17:28 egor This may be useful : https://gist.github.com/anonymous/ff9517464cb8a8c47c5dd27c10f0079d
17:29 manji egor, you can't have {{}} within {{}}
17:29 egor as I go through a for loop, I want the 'topID' to be expanded in the jinja template.  The pillar data is visible to the host in question.
17:29 egor well.. that is my problem ;P
17:29 manji what is topID? a variable?
17:29 manji hmm
17:29 manji try
17:30 manji ('%s:keyvalue' %s topID, 'keynotfounf')
17:30 manji erm sorry
17:30 manji ('%s:keyvalue' % topID, 'keynotfounf')
17:31 egor I'll give it a go.  My two questions were - how do I get {{topID}} to expand (which.. I can't) and - should I be doing it differently - which sounds like I should.
17:32 spuder joined #salt
17:33 manji another way would be
17:33 manji ('{0}'.format(topID), 'keynotfound')
17:34 manji try that in your jinja template and see how it goes
17:34 gtmanfred '%s:keyvalue'|format(topID)
17:34 manji instead of {{topID}}
17:35 gtmanfred {{ salt['pillar.get']('%s:keyvalue'|format(topID),'keynotfound') }}
17:36 manji that is more jinja-ish indeed:p
17:36 manji the other is more python-ish :p
17:36 gtmanfred yar
17:37 flowstate joined #salt
17:38 keimlink joined #salt
17:41 tapoxi joined #salt
17:41 egor I may have a different problem - Unable to manage file: Jinja variable 'topID' is undefined.  let me dig a bit further.. thanks for getting me closer to the track
17:47 egor woot!  found it.  I'll share shortly.  it'll probably be obvious, but some benefit to others I'm sure
17:48 s_kunk joined #salt
17:54 flowstate joined #salt
17:55 egor So after updating my jinja template to what @gtmanfred suggested, the template wasn't getting the `topID`.  This was the magic sauce that solved it :
17:55 egor https://gist.github.com/anonymous/213a9cb6e354c4acb305baba7c419b88
17:56 gtmanfred cool
17:56 egor needed to use app_name in the jinja template
17:56 egor thanks for the help manji and gtmanfred
17:56 gtmanfred :)
17:56 egor made my morning less of a grind
17:57 garphy joined #salt
17:57 MTecknology hemebond: figuring out this anchor stuff is tricky..
18:09 jwon joined #salt
18:11 ajw0100 joined #salt
18:12 mark25987 joined #salt
18:12 sagerdearia joined #salt
18:13 Brew joined #salt
18:16 teryx510 joined #salt
18:18 GreatSnoopy joined #salt
18:19 c4t3l hello all. I have a question regarding yum repo management in salt.  Is it better to use a templated file with jinja (ie epel.repo) or the pkg.repo state definitions for setting up repos on hosts?
18:21 Sketch you can require that the repo exists before installing certain packages with pkg.repo, not sure about with a templated file
18:23 c4t3l I've used the require call in states with the templated file.  I'm just wondering if that is optimal
18:23 ageorgop joined #salt
18:24 c4t3l let's say I have a repo that I need to activate first, then deactivate after my package has been installed/upated.  Does pkg.repo support this kind of thing?
18:24 impi joined #salt
18:24 c4t3l or would that be modrepo?
18:25 pcdummy c4t3l: you could write an activate state, an install state and finaly a removed state
18:25 pcdummy c4t3l: but every time you run this you will activate/deactivate
18:25 pcdummy c4t3l: i'm sure you don't want that kind of thing.
18:26 c4t3l hmm
18:27 subsignal joined #salt
18:28 macheck joined #salt
18:29 CeBe joined #salt
18:32 hasues joined #salt
18:36 edrocks joined #salt
18:37 hasues left #salt
18:39 Rumbles joined #salt
18:48 jrgochan pcdummy: it seems to be working great. thanks!
18:51 edrocks joined #salt
18:52 aw110f joined #salt
18:55 MTecknology I'm absolutely shocked with how dead simple it is to use anchors in yaml. That's sexy stuff!
18:55 pcdummy jrgochan: np, have fun mate :)
18:57 pcdummy MTecknology: make stuff even more complicated, but its sexy yes.
18:57 MTecknology In this case, it's way less complicated
18:58 pwhack joined #salt
18:59 tapoxi not familiar with anchors MTecknology how are you using them?
19:00 MTecknology I'm excited about it .. gimme a sec
19:01 sud0x3 joined #salt
19:02 aw110f joined #salt
19:04 MTecknology tapoxi: pcdummy: Here's an example of what I'm doing with it - http://dpaste.com/0Q2G016
19:05 MTecknology I can't even picture what a more elegant solution would look like
19:06 pcdummy hard to read
19:07 MTecknology That is?!
19:08 pcdummy MTecknology: after a while its fine, but at first its confusing
19:09 POJO joined #salt
19:10 kossy_ joined #salt
19:11 MTecknology I feel like it's immediately obvious what & and * do in that context, but I'm also familiar with * meaning pointer.
19:11 c4t3l MTecknology: what do the anhors provide?  is it human readability or something else?
19:11 MTecknology When I first saw the example mentioned yesterday, I already thought it was neat as crap, then I realized they're trying to merge dictionaries and what I actually need is way prettier
19:12 brotatochip joined #salt
19:12 MTecknology c4t3l: Imagine that file being much larger where you need to sometimes tell servers in some countries (or localities within the country) to use a different NTP server as quickly and easily as possible.
19:13 ninjada joined #salt
19:13 MTecknology It helps with that. It also prevents having to duplicate everything.
19:13 c4t3l ahh I see it now
19:14 pcdummy a good example is here: https://learnxinyminutes.com/docs/yaml/
19:15 MTecknology In the repo, the zones section is *MUCH* larger, over half filled with comments about getting approval for that stratum 1 server and whatever else. I always try to keep good documentation about talking to external NTP S1 servers.
19:16 MTecknology It's almost painful to look through because it's so heavily documented in that section.
19:17 c4t3l I'm bookmarking that yaml site ;)
19:17 MTecknology bookmark this too if you've never seen it - http://yaml-online-parser.appspot.com/
19:17 c4t3l oh yes thats a good one too
19:18 MTecknology pcdummy: heh, I was confused when I opened that.. turns out it was open in another tab
19:19 rem5 joined #salt
19:22 pcdummy i love yamltojson.com :)
19:23 kossy_ joined #salt
19:26 MTecknology I like anything that isn't javascript, but json... I don't mind json
19:27 MTecknology too many ads on that one
19:30 MTecknology and it requires clicking a button
19:30 Salander27 joined #salt
19:31 brotatochip joined #salt
19:38 c4t3l is there a sane way to copy a file from one minion to another that isnt a huge security risk?
19:39 Sketch not that i know of
19:39 MTecknology I can't think of anything...
19:39 MTecknology minion->minion is tough
19:40 rem5 joined #salt
19:42 kossy_ joined #salt
19:44 pcdummy same here can't think of
19:44 pcdummy c4t3l: minion->master->minion should work from what i know
19:45 teryx510 joined #salt
19:46 Sketch but even then, there's no direct way to do that from a single state
19:46 keimlink joined #salt
19:47 Sketch maybe you could write a module to copy a file from a host to the master, which you call before pushing the file out
19:49 c4t3l that sounds like the right kind of direction. I need to manage a file across a pair of salt masters for two-factor auth.  This is a tough one
19:50 c4t3l can you call a local module from a state? is that right
19:50 kossy_ joined #salt
19:51 hoonetorg joined #salt
19:52 Sketch i assume so, but i've never tried
19:53 Sketch but i guess you can't call a module on a different host
19:53 Sketch since salt only operates on one at a time
19:53 Sketch so maybe that wouldn't work
19:54 c4t3l yeah... I honeslty think the 2FAC should happen a layer removed from the hosts involved
19:55 c4t3l but I dont have any kind of workaround.  I'm stuck with the solution i have
19:56 c4t3l I have a small set of users, but they all need to have a config generated and then copied over to the standby node in case of outage
19:57 c4t3l at first I was thinking of using some kind or reactor, but it doesnt solve the problem of getting the config over to the other minion
19:57 kossy_ joined #salt
19:59 TyrfingMjolnir joined #salt
20:00 daishan joined #salt
20:03 ageorgop joined #salt
20:04 flowstate joined #salt
20:06 kossy_ joined #salt
20:07 pcdummy c4t3l: what about configuring a user with ssh keys and copy over that one?
20:07 Tanta shared network drive (read-only), TFTP server, SFTP server, etc etc
20:07 rem5 joined #salt
20:07 Tanta you can even use version control for something like that
20:08 pcdummy yep
20:08 pcdummy last sounds best
20:08 c4t3l pcdummy: that is what I'm doing for minion keys... It gets messy after that tho.  I would have to figure out how to reset permissions on the file and get it copied to the right place per user home dir
20:08 Tanta or just have the standby node generate the same template using the same pillars/Jinja
20:09 Linuturk joined #salt
20:09 ronnix joined #salt
20:10 Linuturk There are two Multi Master tutorials on the documentation site. One says to copy your master.pem|pub to each master, and the other says to not share this file.
20:11 Sketch heh
20:11 subsigna_ joined #salt
20:12 c4t3l Linuturk: I've found that the security requirements of your site will dictate which Multi Master setup you choose
20:13 c4t3l if you are in a trusted network I dont see the benifit of MultiMaster PKI
20:13 c4t3l of you are not  (ie cloud based hosts) then PKI makes more sense to me
20:13 Linuturk pki seems a bit more fragile in terms of recovery
20:14 Linuturk ie, some of my minions don't like a replacement master
20:16 c4t3l true... minions can get in a stuck state.  The 2016.3 release provides the failback mechanism for minions.  This was the single biggest reason for its quick adoption in my environment
20:16 mikecmpbll joined #salt
20:17 Tanta for ultimate security, go masterless
20:18 c4t3l Tanta: would you say that masterless is a better setup for DMZs?
20:18 Tanta it's a better setup for any non-trivial network
20:18 Tanta if you have one VPC (or VLAN), then it's convenient, but it seems overly complex for a network with multiple segments
20:19 pcdummy What is with shared enviornments where users have root on theier "managed server" ?
20:19 Linuturk tell me more about that failback mechanism c4t3l ? is that the failover method?
20:20 Linuturk and I've got the master_sign_pubkey set
20:20 Linuturk but the master isn't sending it for some reason
20:22 c4t3l Linuturk: In a nutshell... the minions send a test.ping to the masters listed in the minion config.  First in the list is "primary".  If the minion cant reach it for specified timeout, the minion will fail over to the second master in the list.  The minion will still ping all masters in the config.  If original primary comes back and responds to test.ping, then the minion will "failback" to the original master
20:22 c4t3l All that ^^ assumes no master shuffling settings
20:23 Linuturk are all masters considered "hot" in that scenario or just the most recent one to respond to the test.ping?
20:23 c4t3l only one master is active in that scenario
20:24 Linuturk what's weird here is, the minions start working right away if I stop the service, and launch with salt-minion -l debug
20:24 Linuturk if I try a minion restart using the init.d scripts, it doesn't actually reconnect right
20:27 Linuturk weird
20:28 Linuturk maybe I should just rip out all the pki stuff and see if that's more stable
20:28 Linuturk signing*
20:32 nidr0x joined #salt
20:34 nidr0x joined #salt
20:42 kevinquinnyo1 joined #salt
20:43 cyborg-one joined #salt
20:47 kossy_ joined #salt
20:48 c4t3l Here's an idea... could a cmd.script call return an abritrary string of data than can be used in another state to populate a file?
20:50 amcorreia joined #salt
20:50 tapoxi c4t3l I've done that with the python api
20:50 tapoxi using a runner
20:50 tapoxi not sure about only doing it in states
20:50 tapoxi maybe if you wrote the state in python instead of yaml
20:52 Slimmons joined #salt
20:52 kossy_ joined #salt
21:03 Rumbles joined #salt
21:04 linovia mmm, I've facing an unusual issue with salt. I'm starting a state.highstate and the master returns  "Minion did not return. [No response]" but I don't have any log that says things went south
21:04 linovia note that test.ping does work for that minion though
21:05 tapoxi linovia do you notice anything when using salt-call on the minion?
21:05 linovia should it be the same as calling salt but starting it on the minion ?
21:05 tapoxi yes
21:06 linovia ran fine
21:07 tapoxi how long did it take?
21:07 hemebond MTecknology: Glad you're finding them useful :-)
21:08 linovia tapoxi: a few seconds
21:08 flowstate joined #salt
21:09 tapoxi hmm, not sure linovia. check the job history on the master
21:09 tapoxi see if it just timed out
21:09 linovia with -l all, I get tons of "[TRACE   ] _get_event() waited 0 seconds and received nothing"
21:09 linovia while with test.ping I get none of those
21:09 linovia well, will dig
21:09 linovia thanks
21:11 linovia weird, seems it now works
21:11 linovia seems I wasn't the only one: http://stackoverflow.com/questions/37732774/targeting-nested-nodegroups-fails-with-minion-did-not-return-no-response-d
21:12 linovia and https://github.com/saltstack/salt/issues/33950
21:12 saltstackbot [#33950][OPEN] Minions are not responsive when targeted with nested nodegroups | Description of issue...
21:13 ninjada joined #salt
21:15 subsignal joined #salt
21:16 aw110f joined #salt
21:22 Slimmons joined #salt
21:23 Slimmons When using the reactor, is it possible to either pass postdata from data.get() to the state file, or to save it in pillar or grain?  Here's an example of what I have. https://gist.github.com/Slimmons/b52d768f52033c86890666759d4836e0
21:24 Slimmons All of that works, I just wanted to add more data than just tgt it, but it's stuff that the init.sls file would need
21:25 Slimmons or, for example, wanting data for the file being managed by init
21:38 ronnix joined #salt
21:38 nidr0x joined #salt
21:38 flowstate joined #salt
21:42 brotatochip joined #salt
21:55 DEger joined #salt
21:55 KajiMaster joined #salt
21:56 rem5 joined #salt
22:01 ribx joined #salt
22:02 nickg joined #salt
22:02 nickg I used file.append to add a line, is there an opposite to remove that line?
22:08 edrocks joined #salt
22:08 manji joined #salt
22:09 lero joined #salt
22:09 writtenoff joined #salt
22:14 djgerm joined #salt
22:15 djgerm I am seeing, very regularly, my pillar not getting updated due to a git lock and the master log file telling me to run "salt-run cache.clear_git_lock git_pillar type=update" to fix it…. which generally does but: why does it keep happening?
22:51 ninjada joined #salt
22:58 raspy_ joined #salt
23:00 raspy_ is there a way to call line 2 and have it populate line 11 and line 12 as such http://pastebin.com/E1pmPsBV
23:02 subsignal joined #salt
23:04 subsigna_ joined #salt
23:06 debian112 joined #salt
23:06 ninjada joined #salt
23:11 subsignal joined #salt
23:12 brotatochip joined #salt
23:15 nickg left #salt
23:16 tawm04 joined #salt
23:17 subsigna_ joined #salt
23:18 kevinquinnyo1 joined #salt
23:18 TyrfingMjolnir joined #salt
23:29 cableninja_ joined #salt
23:34 ajw0100 joined #salt
23:42 mapu joined #salt
23:47 PeterO joined #salt
23:56 keimlink_ joined #salt

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