Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-07-04

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

All times shown according to UTC.

Time Nick Message
00:00 joehh I'm also doing debian so the debian ones will be hosted at debian.saltstack.com
00:00 Ryan_Lane the only downside to putting the RC into the nightly branch is that people will switch to the nightly branch temporarily, then will stay there and will accidentally be running dangerous code
00:00 joehh I may host the ubuntu ones there as well so that they don't disappear as soon as a new build is uploaded
00:00 Ryan_Lane I guess with a RC PPA they'll be stuck with old code
00:01 Ryan_Lane it would really be nice to have a PPA per stable branch
00:01 Ryan_Lane so, 2014.1 would have its own ppa and 2014.7 would have one too
00:01 joehh Ryan_Lane: that is where I think I am heading
00:01 Ryan_Lane the RCs could go into 2014.7
00:01 * Ryan_Lane nods
00:02 joehh nice idea, and put the nightlies in a dev branch
00:02 Ryan_Lane that also makes it possible to stick with a stable PPA without getting a major update accidentally
00:02 mgw joined #salt
00:03 joehh I'm a cautious with any update, but yes
00:04 Ryan_Lane well, people using a PPA and using pkg.latest will always get it since it's newer
00:04 Ryan_Lane assuming the major update is in the same PPA
00:06 joehh yes
00:08 troyready joined #salt
00:10 jnials joined #salt
00:12 ipalreadytaken joined #salt
00:14 pfallenop joined #salt
00:15 quickdry21 joined #salt
00:18 aw110f joined #salt
00:20 ericsysmin joined #salt
00:23 azylman joined #salt
00:24 shaggy_surfer joined #salt
00:25 mateoconfeugo joined #salt
00:26 pssblts joined #salt
00:28 ajolo joined #salt
00:32 mosen joined #salt
00:34 dude051 joined #salt
00:37 dude051 joined #salt
00:43 Ryan_Lane joined #salt
00:44 ramishra joined #salt
00:49 mgw joined #salt
01:00 tkharju3 joined #salt
01:10 Ryan_Lane whiteinge, basepi, manfred: anyone seen this post yet? https://twitter.com/imarshut/status/484787934134956033
01:10 whiteinge Ryan_Lane: yeah, thank you
01:11 whiteinge i'm working on getting that added to the docs right now
01:11 whiteinge i'll reply there too
01:11 Ryan_Lane (someone should reply to him on twitter)
01:11 Ryan_Lane ah cool
01:11 Ryan_Lane bad to have posts like that unanswered ;)
01:12 basepi Ryan_Lane:  whiteinge: cachedout also emailed the guy directly.
01:12 basepi So we're pretty well handled.
01:12 * Ryan_Lane nods
01:12 basepi Thanks for the heads up. =)
01:13 Ryan_Lane I meant publically, though, so people can see the reply on twitter
01:14 basepi Will do
01:15 basepi Ah whiteinge got it.
01:15 Ryan_Lane cool
01:15 whiteinge thanks
01:15 bhosmer joined #salt
01:18 rjc joined #salt
01:24 krow joined #salt
01:27 rjc joined #salt
01:27 TyrfingMjolnir joined #salt
01:38 ajolo joined #salt
01:42 yomilk joined #salt
01:45 ramishra joined #salt
01:47 alekibango_ joined #salt
01:51 jslatts joined #salt
01:56 ajolo joined #salt
01:57 dalexander joined #salt
02:00 N-Mi joined #salt
02:04 troyready joined #salt
02:06 schimmy joined #salt
02:11 gzcwnk I am tring to set up a ssh.sls but get an error, http://dpaste.com/1JAXQ72  any idea why pls?
02:12 ajolo joined #salt
02:13 mgw joined #salt
02:17 possibilities joined #salt
02:18 gzcwnk i guess I need to do multiple things to the same file but need syntax
02:21 TaiSHi Well
02:21 TaiSHi Congrats to me
02:21 TaiSHi For (at least) the next 8 months I'll be working with my city govt
02:21 TaiSHi And I'll be using virtualization on mainframe
02:22 gzcwnk mainframe?  hmmm
02:22 gzcwnk why do they virtualiseona mainframe?
02:22 ajolo joined #salt
02:23 TaiSHi It's the govt
02:23 TaiSHi They need someone to blame if something doesn't work
02:23 joehh gzcwnk: if that is really what you want, then do something like http://dpaste.com/0BVHG6W
02:23 TaiSHi They're using Suse............................................................................
02:23 gzcwnk ah, so that's you then
02:23 TaiSHi I am
02:23 TaiSHi Not
02:23 kossy joined #salt
02:23 TaiSHi I work for a company that the govt hired
02:23 joehh but if you have file.managed, couldn't you just put the permitrootlogin in the file on the master?
02:24 gzcwnk contractors are always the sacrifical lamb
02:24 TaiSHi Indeed, but at least I'll be working with ze new toys
02:25 TaiSHi Can you not use profiles in salt-cloud? I mean, I want to just start a machine called xx-yy and it should "know" which profile to use
02:26 platforms joined #salt
02:26 gzcwnk I'd have to construct a file on the master and make it exportable..
02:26 gzcwnk and I have different linux versions, so a simple append seems the best way
02:27 gzcwnk that didnt work either
02:27 joehh http://dpaste.com/3GXJG4X
02:29 gzcwnk http://dpaste.com/03MSEP0
02:29 m1crofarmer joined #salt
02:30 joehh we often do something like: http://dpaste.com/20TX2AC
02:30 joehh where a os specific one (if it exists) will override the default
02:30 joehh I think the issue is with the spacing of your permitrootlogin
02:30 joehh I would try and avoid append if you can
02:32 gzcwnk it was working fine,
02:32 joehh My copy/paste may have messed up spacing
02:36 gzcwnk hmm, k
02:36 gzcwnk the two parst work fine just not combined
02:36 gzcwnk wierd
02:38 bhosmer joined #salt
02:39 ajolo_ joined #salt
02:41 ramishra joined #salt
02:49 johngrasty terminalmage: No problem. I missed that too. When will the helium release be?
02:50 jnials_laptop joined #salt
02:56 gzcwnk is there no way to combine multiple actions like file.managed and file.append on teh same file?
03:00 twiedenbein joined #salt
03:07 Aletheuo left #salt
03:09 possibilities joined #salt
03:12 ramishra joined #salt
03:16 TyrfingMjolnir joined #salt
03:16 bmatt sure there is
03:17 bmatt they just have to have unique state IDs
03:18 bmatt multiple states can share a name argument, but their ID must be unique
03:19 gzcwnk ok, where whould I find examples of file.managed and file.append sharing a unique ID?
03:20 gzcwnk I assume one would be under the other, but there are so few examples I am unable to guess the file structure needed
03:21 bmatt https://gist.github.com/thenewwazoo/552d50c8cb6f252159b8
03:21 tkharju4 joined #salt
03:22 bmatt the topmost declaration is the state ID
03:22 gzcwnk I ahve this,
03:22 gzcwnk http://dpaste.com/3TAC0XC
03:22 gzcwnk ah ok
03:22 bmatt if the name argument isn't otherwise specified, name defaults to the ID
03:23 bmatt but that's very often a bad idea
03:23 bmatt (and, in fact, if I were king for a day, I'd undo that little 'feature')
03:24 tkharju joined #salt
03:24 gzcwnk yeah that worked fine thanks...
03:26 bmatt np
03:27 ekristen joined #salt
03:29 gzcwnk :D
03:34 catpigger joined #salt
03:48 mosen joined #salt
03:51 econnell joined #salt
03:52 dvogt joined #salt
03:52 logix812 joined #salt
04:05 Ryan_Lane joined #salt
04:07 ipalreadytaken joined #salt
04:08 TyrfingMjolnir_ joined #salt
04:18 johngrasty Hey. I'm trying to get the bootstrap script to work on SmartOS. Most of the files are making it to the right place (/opt/local/foo), but the config files are going to /etc/salt instead of /opt/local/etc/salt. Any ideas?
04:18 techdragon joined #salt
04:23 possibilities joined #salt
04:25 mateoconfeugo joined #salt
04:31 kossy joined #salt
04:39 ocdmw joined #salt
04:40 ocdmw joined #salt
04:41 troyready joined #salt
04:41 Outlander left #salt
04:43 Shenril joined #salt
04:51 bhosmer joined #salt
04:52 thayne_ joined #salt
04:53 AviMarcus joined #salt
04:57 krow joined #salt
05:08 malinoff joined #salt
05:10 taterbase joined #salt
05:16 Nazca joined #salt
05:16 twoflowers joined #salt
05:17 ramteid joined #salt
05:22 luminous johngrasty: you'll likely need to dig into the bootstrap functions for SmartOS
05:23 johngrasty luminous: Thanks. I just found what I needed. BS_SALT_ETC_DIR
05:23 luminous :)
05:24 luminous https://github.com/saltstack-formulas/salt-formula/blob/master/salt/files/minion#L268 <<< where is the isinstance() jinja macro defined?
05:24 luminous I can't seem to find this noted anywhere..
05:24 luminous not in jinja itself, salt docs, etc
05:40 ramishra_ joined #salt
05:40 tinuva joined #salt
05:48 ramishra joined #salt
05:56 jalaziz joined #salt
06:00 thayne_ joined #salt
06:05 ramishra joined #salt
06:08 Shenril joined #salt
06:13 bmatt https://docs.python.org/2/library/functions.html#isinstance
06:14 malinoff bmatt, the problem is you can't call arbitrary python functions within jinja without injecting them to template renderer
06:14 bmatt then I have a sneaking suspicion that jinja2 injects builtins by default
06:14 malinoff it's not
06:15 malinoff https://groups.google.com/forum/#!topic/pocoo-libs/99YXzP8RpFw
06:15 bmatt hm. then how does the salt formula work?
06:16 malinoff bmatt, this is the question :)
06:17 malinoff bmatt, also, in py2 there is `apply` function in builtins, which can call any other function. So if you allow builtins on py2, you allow everything
06:18 bmatt hm
06:19 malinoff actually, you can get access to builtins, not with jinja but with yaml
06:19 malinoff !!python/object/apply http://pyyaml.org/wiki/PyYAMLDocumentation#YAMLtagsandPythontypes
06:20 malinoff (which works only in py2 because of `apply` in builtins)
06:22 techdragon joined #salt
06:25 krow joined #salt
06:26 krow1 joined #salt
06:27 Hell_Fire joined #salt
06:28 happytux_ joined #salt
06:32 johngrasty Hey. I've tried googling, but I've not had any luck. Is helium going to be the next release?
06:39 ipalreadytaken joined #salt
06:39 bhosmer joined #salt
06:43 ramishra_ joined #salt
06:48 keyvan joined #salt
06:48 ramishra joined #salt
06:54 krow joined #salt
06:58 babilen johngrasty: It is
06:59 ramishra joined #salt
07:04 ml_1 joined #salt
07:08 ndrei joined #salt
07:12 jhauser joined #salt
07:13 jdmf joined #salt
07:13 ndrei_ joined #salt
07:15 Kenzor joined #salt
07:23 alanpearce joined #salt
07:34 alekibango joined #salt
07:38 chiui joined #salt
07:39 babilen AFAICT there are two ways to raise my own events: 1. Use cmd.run with "salt-call event.fire {...}" or 2. Write my own state module and use code such as that detailed on http://docs.saltstack.com/en/latest/topics/event/index.html and "call" that from an SLS file or from the reactor. Is that correct or are there other, more common, approaches?
07:45 CeBe joined #salt
07:48 darkelda joined #salt
07:53 ramishra joined #salt
08:03 slav0nic joined #salt
08:03 tinuva joined #salt
08:10 jhauser joined #salt
08:15 Lomithrani joined #salt
08:15 dzen joined #salt
08:16 dzen hello
08:17 ramishra joined #salt
08:27 Booof joined #salt
08:27 bhosmer joined #salt
08:28 Booof Hello. Is there any way to use jinja to see if a grain is in a specific subnet? I want to customise a template using something like if grains['fqdn_ip4'] is in <prod netrange> then; else;
08:28 Booof It's a big ask - is breaking out to full python the best option in the template at this point?
08:29 malinoff Booof, {% if grains['fqdn_ip4'] in [ip1, ip2, ip3] %}
08:30 ipalreadytaken joined #salt
08:31 babilen Booof: I would write that in Python and use IPy
08:32 babilen It's just bound to get ugly in jinja, but it really depends on what you want to do. I mean if all you want to check is if a given IP starts with 127 or so then writing that in Python would certainly be overkill.
08:32 gmoro joined #salt
08:34 gope joined #salt
08:34 gope Hi!
08:34 robertapi joined #salt
08:34 gope I have a question...
08:34 babilen *drumroll*
08:36 gope I need to deploy a script to all minions, including the ones that are offline, what I mean is I need the master to keep track of all minions state deploy and if they are offline/shutdown wait until they are up
08:37 gope how can I do this? and yes I'm new to saltstack
08:37 babilen gope: Run a highstate whenever a minion comes online. I'd tie that into presen(s|c)e events with the reactor system.
08:38 babilen gope: http://docs.saltstack.com/en/latest/topics/reactor/index.html details the reactor system and you can enable presence events by setting "presence_events: True" in your master conf
08:39 gope ok thank you :)
08:40 babilen That gives you events whenever the "presence" state of a minion changes and you can then trigger a highstate run on the minion (or just call that particular state that you want to enforce). Please note that the versions of saltstack spell "presence" as "presense" to you will have to write reactor configuration that takes that into account (and that will break once the new salt version is being released)
08:42 alanpearce joined #salt
08:43 gope ok, I guess.. How can I check the reactor progress?
08:43 babilen gope: So you get events such as http://paste.debian.net/108087/ (output of the eventlisten.py script (you need the version from the salt version you run!!))
08:43 babilen reactor progress?
08:46 gope nevermind, I wanted to keep track of progress
08:46 malinoff gope, salt can't track progress of a single state
08:47 dzen is there a command form salt, e.g. salt 'machine' <cmd> to rename a minion ?
08:48 babilen dzen: You mean: Change it's minion id?
08:48 babilen (or change its hostname, or both, ot what?)
08:48 dzen yes changing it's id
08:48 babilen *its
08:48 dzen yes sorry, its
08:48 babilen dzen: Manage its minion configu and set the id in there.
08:48 babilen dzen: Well, I was correcting *my* spelling not yours, but consider both to be corrected now :)
08:49 malinoff dzen, you can use file.replace on /etc/salt/minion and change its id, but you will have to re-authenticate your minion with salt-key
08:49 malinoff I've never tried that by myself, but I think that should work
08:49 dzen I'll put an id in "/etc/salt/minion.d/id.conf"
08:49 babilen Or just manage that file to begin with, use watch_in on the salt-minion service and populate it from pillar
08:50 babilen You could even use the reactor system to authenticate this minion automagically
08:50 dzen my machines are bootstraped via PXE, and their id are like: 00:50:db:00:b2:3a.temp.$FQDN
08:50 babilen mmmhh, lovely.
08:51 dzen :p
08:51 * babilen pats debootstrap and sensible preseeding
08:51 dzen yes :)
08:51 babilen Wait, you are using Debian?
08:51 dzen Yes, I'm
08:52 dzen when I install machines, I won't know their usage or hostanme
08:52 dzen (well, they're linked)
08:52 babilen Oh, in that case: Why don't you preseed the actual hostname in the preseed file? https://www.debian.org/releases/wheezy/example-preseed.txt
08:52 babilen Ah, okay ... when do you know their usage?
08:53 dzen babilen: I prepare a pool of machines, to be sent to anuwhere in the world (hu, I've got a few machine in angkor, yaounde, abidjan …)
08:53 dzen and then I remotely configure them
08:54 babilen I can understand where you come from, but we essentially know what a machine will be used for when we install it and then set values in the preseed file accordingly.
08:54 babilen (before the salt provisioner does the rest)
08:54 dzen yup
08:55 babilen It strikes me as wasteful to just install a number of boxes without purpose and let them linger in some weird childhood state before you figure out what you will use them for :)
08:56 babilen Either way: Manage /etc/salt/minion or a file in /etc/salt/minion.d/, define a watch_in: salt-minion-service (and the service!) for that file and accept the new name on the master (either manually or automatically via reactors)
08:56 dzen It's a temporary process, waiting for our saltmaster to contact or stock information system
08:56 dzen to guess what will be it's name|id
08:59 Booof malinoff / babilen - thanks. If there's nothing 'native' already in saltstack for netrange matching like that I might just define a grain on the minions. Probably more sensible in the long term as I can key off it's netrange / vlan for other things in the same fashion.
08:59 briner joined #salt
08:59 malinoff Booof, if this information is sensible, you should store it in pillars
09:00 babilen Booof: I custom grain would certainly make sense in that case and is quite easy to write.
09:01 Booof :) well looks like I have a choice to make :P
09:01 Booof on a side note - does anyone know how support holds up for RHEL7? (and derivatives)
09:01 babilen I would argue that this is data you want as a grain as it is more or less static about the minion itself.
09:01 babilen (much like the IP address itself)
09:02 linjan joined #salt
09:02 Booof babilen - yes, it's just to have some way to know which of our networks / vlans a minion is in for salt. So I can then template config differences on each minion based on that. It would be unlikely to ever change (or very rarely in any rate)
09:03 Booof babilen - and yes, it would of course be tied heavily to the IP which is also static as you've suggested.
09:03 babilen We do something similar for lacp and target by that
09:03 Booof babilen - at the moment I'm trying to resist putting too much custom config on the salt-minion install as I then have to write other scripts in other tools to figure that out for deployment :)
09:04 babilen It works beautifully and the external grain is not complex to write.
09:05 giantlock joined #salt
09:05 babilen Take a look at the sync_grains reactor discussed on http://docs.saltstack.com/en/latest/topics/reactor/index.html
09:07 Booof babilen - hmm thanks. That's interesting. Though I think it would leave me in the same spot I'm in now, having to decide what network a minion is in programatically within salt.
09:11 babilen Booof: Oh, and distant memories of salt and its documentation made me double-check http://docs.saltstack.com/en/latest/topics/targeting/compound.html
09:11 babilen Booof: Take a look at: steveoliver Subnet/IP addressS@192.168.1.0/24 or S@192.168.1.100
09:11 babilen steveoliver?
09:12 babilen Should have checked that first :-/ -- Sorry for that.
09:13 Booof babilen - ooooh - that looks like exactly what I need. Presuming I can use that syntax in a pillar when matching a grain. Fantastic! Thank you.
09:15 babilen You are welcome. And evidence that I should read the documentation again once more :)
09:16 dRiN joined #salt
09:17 xmj daily nagging time:
09:17 xmj 2014.1.6?
09:18 babilen "not today"
09:18 Sp00n "soon"
09:19 Booof babilen - in your defence there is an awful lot of (good) documentation. It's a lot to take in! You've ingested more of it than I've managed..clearly.. :)
09:22 babilen It's time for a good O'Reilly book IMHO
09:23 malinoff babilen, for?
09:23 babilen salt
09:24 malinoff I guess nobody can write a book about salt, due to "its rolling nature". How can you write about something that can change in a week? :)
09:24 babilen + "Cooking with salt" (aka. "The Salt Cookbook")
09:24 Booof I'm sure I saw a book someone was writing due out at the end of the year. Not O'Reilly though - self published I think
09:24 xmj hah
09:24 xmj malinoff: it's simple
09:25 xmj malinoff: just make it an ebook with rolling revisions.
09:25 babilen malinoff: Reasonable argument. But the time the book gets published the content is already so old that it is useless
09:25 TheThing joined #salt
09:25 malinoff xmj, such ebook is called "docs"
09:25 xmj malinoff: charge a lot for the initial ebook and have an upgrading license (paid for, monthly)
09:25 Sp00n salt essentials is supposed to be due in dec
09:25 babilen Booof: I just like the style of most O'Reilly books and would love to read something along those lines for salt.
09:26 greyhatpython joined #salt
09:26 CeBe joined #salt
09:27 babilen But a cookbook (like O'Reilly's Python Cookbook) would come in handy too. I love to read those little snippets and am always happy when I can incorporate some of them into my code.
09:27 CeBe joined #salt
09:30 CeBe joined #salt
09:33 xmj malinoff: doesn't get the idea of "passive income" :-P
09:34 babilen If I manage /etc/salt/master from salt can watch that file in the salt-master service and will the master service be reloaded without problems?
09:36 malinoff xmj, i don't think this income is passive, salt changes very often and there should be a dedicated person just to make sure such ebook is always correct
09:36 malinoff Or salt may think about backwards compatibility
09:36 malinoff but...
09:40 linjan_ joined #salt
09:47 xmj malinoff: no income is ever passive
09:47 xmj and that is how you can milk people, by continuously upselling them on latest revisions of your ebook :-P
09:48 Outlander joined #salt
09:50 TheThing joined #salt
09:51 bhosmer joined #salt
09:56 CeBe joined #salt
09:59 happytux joined #salt
10:01 linjan_ joined #salt
10:02 linjan joined #salt
10:05 CeBe joined #salt
10:09 ramishra joined #salt
10:15 darkelda joined #salt
10:16 bhosmer joined #salt
10:22 Hell_Fire joined #salt
10:32 analogbyte joined #salt
10:34 TheThing_ joined #salt
10:50 robertapi joined #salt
11:11 davidone joined #salt
11:16 tinuva joined #salt
11:21 tinuva joined #salt
11:33 bhosmer joined #salt
11:33 Outlander joined #salt
11:38 ramishra joined #salt
11:42 jhauser joined #salt
11:43 viq Hm, 2014.1.6 still not available
11:49 CeBe joined #salt
11:57 tinuva joined #salt
11:57 babilen heh
12:04 bhosmer_ joined #salt
12:05 Lomithrani joined #salt
12:10 Outlander joined #salt
12:12 Lomithrani in a state reactor where does that data array come from ? {{ data['id'] }}
12:12 Lomithrani in the example they always use this but I don't see them declaring it
12:13 Lomithrani seems a bit like grains
12:29 babilen It is being handed over in reactors (much like grains['...'])
12:31 alanpearce joined #salt
12:34 Walle_ joined #salt
12:36 jaimed joined #salt
12:39 ramishra joined #salt
12:43 ramishra joined #salt
12:49 ekristen joined #salt
12:53 diegows joined #salt
12:55 elfixit joined #salt
12:59 alanpearce joined #salt
13:11 mgw joined #salt
13:34 JoeHazzers how do you guys manage your firewall rules (specifically plain iptables)?
13:37 babilen JoeHazzers: The last things I heard were that somebody was working implementing this properly in salt, but wasn't done yet. Not sure if I've seen it in here or on the mailing list.
13:37 Lomithrani joined #salt
13:37 JoeHazzers alright
13:38 JoeHazzers babilen, thanks
13:38 babilen There is http://docs.saltstack.com/en/latest/ref/states/all/salt.states.iptables.html, but you will probably go nuts
13:39 babilen https://github.com/saltstack-formulas/iptables-formula might be what I was thinking of
13:39 ggoZ joined #salt
13:45 aquinas joined #salt
13:48 bhosmer joined #salt
13:52 bhosmer_ joined #salt
14:04 logix812 joined #salt
14:20 yidhra joined #salt
14:25 alanpearce joined #salt
14:25 robawt joined #salt
14:25 Miguel_london joined #salt
14:26 Miguel_london can some one point me to a documentation oon how  push  service config files to minions
14:26 Miguel_london ?
14:26 bhosmer joined #salt
14:29 babilen Miguel_london: The easiest way is to use file.managed and use a suitable source: in there. You can then also populate that file with data from pillars and render it with "template: jinja"
14:34 Miguel_london any documentation
14:34 Miguel_london ?
14:34 m____s joined #salt
14:34 TaiSHi Miguel_london: which service?
14:34 mgw joined #salt
14:36 Miguel_london xinetd
14:37 mateoconfeugo joined #salt
14:37 TaiSHi Have you checked out formulas?
14:38 bluenemo joined #salt
14:38 yomilk joined #salt
14:38 bluenemo hi guys. Can I buy a saltstack t-shirt somewhere?
14:38 babilen Miguel_london: There is a *lot* of documentation. http://docs.saltstack.com/en/latest/ is the top-level link and I was specifically referring to http://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html
14:39 TaiSHi Exactly and differentiating by pillars if information is sensitive
14:39 Miguel_london babilen thanks
14:41 babilen Miguel_london: But there are lots of different approaches .. I mean it is essentially what salt is about. The "most idiomatic" way is probably to write (or use) a formula. The design of those is detailed in http://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html and you find existing ones at https://github.com/saltstack-formulas/
14:44 ajolo_ joined #salt
14:46 Miguel_london also when i run   state.hightstate i recieve   'state.hightstate' is not available.
14:47 Shish highstate, not hightstate
14:47 babilen picky salt!
14:48 acabrera joined #salt
14:48 tinuva joined #salt
14:49 taterbase joined #salt
14:51 TaiSHi I didn't catch the error at first glance either :P
14:54 johngrasty babilen: Thanks for the info.
14:57 quickdry21 joined #salt
15:04 JoeHazzers [INFO    ] Fetching file from saltenv 'base', ** skipped ** latest already in cache 'salt://openstack/neutron/controller.sls'
15:04 JoeHazzers followed by
15:04 JoeHazzers No matching sls found for 'openstack.neutron.controller' in env 'base'
15:04 JoeHazzers wat.
15:05 tinuva joined #salt
15:09 ipmb joined #salt
15:10 ramishra joined #salt
15:11 mgw joined #salt
15:13 thayne_ joined #salt
15:17 felskrone joined #salt
15:17 xmj state-p 2014.1.6 ?
15:17 ccase joined #salt
15:20 bhosmer joined #salt
15:30 tinuva joined #salt
15:32 krow joined #salt
15:52 bhosmer joined #salt
15:54 toastedpenguin joined #salt
16:06 jforest joined #salt
16:11 ramishra joined #salt
16:23 gildegoma joined #salt
16:23 mgw joined #salt
16:24 bhosmer joined #salt
16:28 luminous anyone using salt with the logstash zmq logger?
16:45 borgstrom joined #salt
17:00 ml_1 joined #salt
17:09 krow joined #salt
17:10 thayne_ joined #salt
17:13 thedodd joined #salt
17:14 ndrei joined #salt
17:14 ndrei_ joined #salt
17:17 jnials joined #salt
17:25 mgw joined #salt
17:30 mgw joined #salt
17:31 Tween joined #salt
17:35 bhosmer joined #salt
17:49 johngrasty Hey. I did an esky build of the development branch of salt to test somethings on SmartOS. I have run into this problem though. http://pastebin.com/UnW0c4Kw This error is on the master.
17:49 johngrasty Any help would be appreciated.
17:50 acabrera joined #salt
17:51 dzen luminous: what's your idea behind it
17:51 dzen ?
17:51 timwillis joined #salt
17:54 ipalreadytaken joined #salt
17:54 luminous dzen: I'm not sure how to confirm whether it's working on the salt side.. or if this replaces the regular log or just in addition to it..
17:55 luminous I've set it up, but I'm not seeing logs
17:55 luminous (in ES/kibana/LS)
18:08 thayne_ joined #salt
18:17 TheThing joined #salt
18:18 krow joined #salt
18:25 diegows joined #salt
18:26 dvogt joined #salt
18:27 ckao joined #salt
18:27 Tween joined #salt
18:29 dude051 joined #salt
18:38 dude051 joined #salt
18:42 schimmy joined #salt
18:42 aberdine joined #salt
18:50 schimmy joined #salt
19:10 demos_ joined #salt
19:13 krow joined #salt
19:14 ramishra joined #salt
19:15 diegows joined #salt
19:20 ajolo joined #salt
19:23 yomilk joined #salt
19:23 bhosmer joined #salt
19:26 jalaziz joined #salt
19:29 ipalreadytaken joined #salt
19:30 ajolo joined #salt
19:36 mgw joined #salt
19:36 xzarth joined #salt
19:53 jslatts joined #salt
20:08 NV joined #salt
20:12 micko joined #salt
20:15 ramishra joined #salt
20:30 ipalreadytaken joined #salt
20:47 TaiSHi Mornin'
20:49 TaiSHi Anyone using an upstart/service formula that could share ?
20:50 babilen Are upstart services not supported by default?
20:51 kaiserpathos joined #salt
20:53 TaiSHi I mean for the conf file :P I'm lazy today
20:53 TaiSHi Quitting my job makes me lazy
20:54 babilen Can't be that hard to write one :)
20:54 babilen But check saltstack-formulas on GH
20:54 TaiSHi I did, found one from another user I might use
20:55 TaiSHi Or I might write mine because I'm like an OCD kind of person
20:55 TaiSHi :P
20:55 TaiSHi (Except when I'm lazy)
20:56 babilen Well, do whatever you think is right.
20:57 TaiSHi I shall, just wanted to come by and annoy everyone with stupid questions
21:11 bhosmer joined #salt
21:20 ajw0100 joined #salt
21:43 acabrera joined #salt
21:44 Hell_Fire_ joined #salt
21:49 zain_ joined #salt
21:52 krow joined #salt
21:53 rjc joined #salt
22:15 alainv Anyone here have a clean setup for a multi-machine vagrant dev environment? Roles being defined in a grain seems very standard, but the vagrant provisioner only supports cleanly modifying pillar data. A separate minion file per node seems excessive?
22:21 ajolo joined #salt
22:41 yomilk joined #salt
22:46 fllr joined #salt
22:59 bhosmer joined #salt
23:00 logix812 joined #salt
23:11 mateoconfeugo joined #salt
23:13 mateoconfeugo joined #salt
23:14 mateocon_ joined #salt
23:17 ramishra joined #salt
23:23 alekibango joined #salt
23:30 aquinas joined #salt
23:41 krow joined #salt

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