Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-07-08

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

All times shown according to UTC.

Time Nick Message
00:01 diegows joined #salt
00:08 mgw joined #salt
00:10 efixit joined #salt
00:11 jkleckner joined #salt
00:18 logix812 joined #salt
00:22 jdenning joined #salt
00:24 kevinastone left #salt
00:49 Jahkeup_ joined #salt
00:57 jdenning joined #salt
01:02 Gwayne joined #salt
01:02 Gwayne joined #salt
01:12 waldo323 joined #salt
01:21 Nexpro1 joined #salt
01:22 liuyq joined #salt
01:24 liuyq joined #salt
01:26 mgw joined #salt
01:35 zkurey joined #salt
01:37 mgw joined #salt
01:40 fragamus joined #salt
01:43 aat joined #salt
01:48 alazylearner joined #salt
01:54 Jahkeup_ joined #salt
01:58 bluemoon joined #salt
02:04 Furao joined #salt
02:11 dthom91 joined #salt
02:27 aat joined #salt
02:29 tomeff_ joined #salt
02:33 BRYANT__ joined #salt
02:41 alazylearner joined #salt
02:52 shiznit joined #salt
03:07 dthom91 joined #salt
03:11 jbunting joined #salt
03:15 aat joined #salt
03:18 berto- joined #salt
03:20 oz_akan_ joined #salt
03:20 Ivo joined #salt
03:27 chadhs joined #salt
03:29 chadhs looking for some help understanding how to specify config files to use with salt bootstrap script
03:37 UtahDave joined #salt
03:42 alazylearner joined #salt
03:43 ferene joined #salt
04:05 ferene joined #salt
04:06 bluemoon joined #salt
04:06 dthom91 joined #salt
04:12 jalbretsen joined #salt
04:18 aat joined #salt
04:43 bluemoon joined #salt
04:55 emocakes joined #salt
04:55 shiznit joined #salt
05:18 terminalmage joined #salt
05:27 jeddi joined #salt
05:32 linjan__ joined #salt
05:38 dthom91 joined #salt
05:38 emocakes joined #salt
05:44 zkurey joined #salt
05:51 bluemoon joined #salt
05:56 shiznit joined #salt
06:01 emocakes joined #salt
06:02 knightsamar joined #salt
06:07 qx joined #salt
06:14 dthom91 joined #salt
06:22 bluemoon joined #salt
06:38 bluemoon joined #salt
06:49 Lucas_- joined #salt
06:54 cxz joined #salt
06:56 balboah joined #salt
06:57 shiznit joined #salt
06:58 efixit joined #salt
07:02 fredvd joined #salt
07:05 drdran joined #salt
07:15 canci joined #salt
07:24 kiorky hi, i have trouble with a syndic, ive reported the issue here: http://goo.gl/eVAX3
07:24 kiorky but in the meanwhile, if someone had a clue ...
07:28 techdragon joined #salt
07:57 shiznit joined #salt
08:00 bluemoon joined #salt
08:05 techdragon joined #salt
08:08 jeddi joined #salt
08:14 bluemoon joined #salt
08:18 SpX joined #salt
08:19 felskrone joined #salt
08:19 felskrone hi
08:25 davidone joined #salt
08:27 felixhummel joined #salt
08:29 bluemoon joined #salt
08:31 azbarcea joined #salt
08:31 az87c joined #salt
08:34 krak3n` joined #salt
08:37 scott_w joined #salt
08:38 bemehow joined #salt
08:43 emocakes joined #salt
08:43 bemehow_ joined #salt
08:43 Jason-AVST joined #salt
08:53 davidone joined #salt
08:54 qx_ joined #salt
08:58 shiznit joined #salt
08:58 nickray joined #salt
08:58 nickray joined #salt
09:03 lyddonb joined #salt
09:04 jhauser joined #salt
09:07 Furao_ joined #salt
09:10 davidone_ joined #salt
09:11 kolaman joined #salt
09:12 kolaman hi all, I was thinking to use puppet/cf-engine for automation and a friend of mine told me about saltstack. Can saltstack be used for the same purpose (or in a better way) in the cloud
09:13 Furao cf-engine is like a coal powered train, puppet is on diesel, and salt is maglev
09:15 kolaman Furao: hmm, so you mean salt can be used in more effective way to get the work done by puppet/chef .
09:16 kolaman Furao: what is the learning curve for a system admin in case of salt ?
09:17 Furao impossible to tell, as everyone are different
09:17 Furao if you're comfortable with python, jinja2 and yaml, it's easier
09:18 tseNkiN joined #salt
09:19 mfournier kolaman: there's no silver bullet, imho. As long as the systems you manage have warts and bugs, any config-management system will make you feel them. Don't get blinded by the bells and whistles and start by picking a distro that works well for your need.
09:20 mfournier kolaman: what I mean is that you'll end up doing workarounds in your config mgmt system for whatever deficiencies your distro has, and it will be ugly and annoying to maintain whatever config mgmt tool you use.
09:22 Furao mfournier: you're talking about centos?
09:23 Furao 8 years old packages, can't upgrade major release without reinstall the OS, hybrid package manager, etc?
09:23 kolaman mfournier: in our case we mostly stick to ubuntu
09:28 mfournier Furao: nothing against centos/RHEL, it's a fine distro for stable stuff which doesn't move. But yeah, if your need bleeding edge technologies on machines you're going to throw away in < 1 year, then ubuntu would be my distro of choice.
09:29 Furao yes, doesn't move like can't upgrade :)
09:30 Furao from what I've seen ubuntu do have release supported for 5 years
09:30 Furao that's not < 1 y
09:30 Furao A new LTS version is released every 2 years. In previous releases, a Long Term Support (LTS) version had 3 years support on Ubuntu (Desktop) and 5 years on Ubuntu Server. Starting with Ubuntu 12.04 LTS, both versions will receive 5 years support.
09:31 mfournier Furao: sure, but guess what, after 5 years, you'll have 5 year-old packages on these systems ;-)
09:32 Furao http://wiki.centos.org/HowTos/MigrationGuide A fresh install is generally strongly preferred over an upgrade.
09:32 Furao at least there is a way to upgrade 12.04 to 14.04 without reinstall the server
09:33 Furao so, when it's centos, it's ok to have old package, but it's not when it's ubuntu?
09:34 mfournier Furao: I'm not saying any distro is better than another. I frankly don't care I can't upgrade an OS that's running on a machine hosting stuff that will be outdated before the OS itself.
09:36 mfournier and imho, a config mgmt good practice is to drop machines that are outdated, and reprovision new ones, possibly with a newer OS. dist-upgrading hosts is calling for problems, and is sign you don't really trust the code you've written in your config-mgmt tool ;)
09:37 nickray if you want to be always up to date, there's no way around Arch Linux :)
09:39 Furao last time I tried arch, upgrade firefox triggered a kernel upgrade that ends into non-bootable kernel. had to grub, boot older kernel from /usr/src/linux-$olderversion/arch/i386/boot/bzImage
09:40 Furao one of my employee is on arch, seem more stable than before
09:40 mfournier nickray: agree. But the point I'm tryingto make, is that you don't always want to be up to date. It really depends on what sort of solution you're building. This is why I avoid have strong opinions about which distro is "best". All have good & bad points, so just pick the one that fits the best.
09:40 Katafalkas joined #salt
09:41 viq Bunch of people say that the answer to the question whether to use chef or puppet or salt is a resounding YES
09:41 mfournier viq: +1 ;)
09:44 nickray speaking of which, is there a timeline for a 0.16.1 release of salt? there seem to be quite a few bugs in 0.16.0
09:44 viq If you can afford to do so, best idea is to come up with a scenario that reflects somewhat what you'll be dealing with in production, and try to achieve that scenario using each of the products you're considering (and maybe even some you don't), and see how you feel about them
09:44 felskrone nickray: what kind of bugs?
09:45 nickray felskrone: seems mostly Windows issues, but I was advised not to upgrade to 0.16.0 last time i was here.
09:45 felskrone hm ok, windows i dont really care about :-)
09:47 Furao if there was only windows bugs...
09:47 nickray Furao: what are the "worst" bugs you know of, currently?
09:48 Furao pip.install is broken
09:48 Furao and cmd.run break mess with file-descriptor that leave some process zombie
09:49 Furao my 400+ tests suite run without any errors on 0.15.3 and 90% fail in 0.16.0
09:49 nickray oh my... that does sound bad. how about integrating your test suite and running tests automatically from github commits?
09:50 Furao someday
09:50 nickray some fine day? :)
09:50 Furao but the cmd.run is a known bug
09:51 Furao I create new issues and fixed some with PR, but I couldn't spend days fixing bug like when 0.15.0 went out
09:53 Furao I changed bootstrap script + salt (api, cloud, master, minion) to use my own salt mirror and we don't use latest version anymore.
09:58 azbarcea joined #salt
09:58 shiznit joined #salt
10:02 mattmb joined #salt
10:06 ggoZ joined #salt
10:07 bemehow joined #salt
10:13 zooz joined #salt
10:18 giantlock joined #salt
10:28 davidone joined #salt
10:30 ruimarinho joined #salt
10:32 emocakes joined #salt
10:36 davidone joined #salt
10:41 Koma what state I've to use to edit the fstab ?
10:43 Koma I need to add an nfs share on all the machine
10:44 viq Koma: mount?
10:44 Koma yes but I want to set it in the fstab
10:45 Koma Comment:   State mount.set_fstab found in sls webserver is unavailable
10:45 viq Koma: http://docs.saltstack.com/ref/states/all/salt.states.mount.html#module-salt.states.mount makes me think it does modify fstab
10:45 Koma http://salt.readthedocs.org/en/v0.10.1/ref/modules/all/salt.modules.mount.html
10:46 Koma here says differently
10:47 viq Koma: and which version of salt are you using?
10:47 Koma latest
10:48 Koma root@WebAdmin:/srv/salt# salt --version
10:48 Koma salt 0.16.0
10:48 viq then why are you looknig at docs for 0.10.1 ?
10:48 Koma http://salt.readthedocs.org/en/latest/ref/modules/all/salt.modules.mount.html
10:48 Koma It's the same
10:49 jeddi joined #salt
10:49 viq to be honest, I am not sure anymore salt.readthedocs.org is updated anymore..
10:50 Koma Argh!
10:50 Koma http://docs.saltstack.com/ref/modules/all/salt.modules.mount.html#module-salt.modules.mount <- is there too
10:51 viq Ah, I know what threw me a bit off. You're asking about states, yet you're giving links to documentation of _execution_ modules
10:52 Koma states =/= execution modules?
10:52 viq Indeed they are different
10:53 viq state == how this machine should be configured. execution module == do this now.
10:53 Koma sooo there is no way to do that via state?
10:53 viq Yes, there is, and I linked you to it
10:53 viq At least how I understand what is written there
10:53 viq http://docs.saltstack.com/ref/states/all/salt.states.mount.html#module-salt.states.mount
10:53 Koma persist -> Set if the mount should be saved in the fstab, default to True
10:54 iMil joined #salt
10:54 iMil hi there
10:54 Koma Ok I need to eat something or I'm going to be completely dumb/numb in 5 minutes
10:54 Koma thank you viq
10:55 viq enjoy :)
10:56 iMil is there any kind of limitation with grains when it comes to "deeper" structures ?
10:56 iMil I mean, instead of just key: value
10:57 iMil having key: {k1: {k2: value}, {k3: value2}}
10:57 iMil when displaying grains with a grains.items call from the salt-master it shows up like a string
10:57 iMil when calling grains.items from the minion itself using salt-call, the output is well structued
10:59 shiznit joined #salt
10:59 iMil strictly put, can I do {% for foo in grains['foo']['bar'] %} ?
11:02 kmrhb joined #salt
11:14 Jahkeup_ joined #salt
11:15 Jahkeup__ joined #salt
11:30 emocakes joined #salt
11:30 vandermerwe joined #salt
11:34 diegows joined #salt
11:37 mikedawson joined #salt
11:38 uta joined #salt
11:39 kmrhb joined #salt
11:40 uta hi guys. quick question - can I select machines based on multiple grains? with 'and' and 'or' style operations
11:41 vandermerwe /mode vandermerwe +x
11:41 vandermerwe whhops
11:41 vandermerwe ;)
11:43 blee joined #salt
11:45 logix812 joined #salt
11:48 vandermerwe joined #salt
11:48 shiznit joined #salt
11:52 lbotti joined #salt
11:55 agend joined #salt
11:55 scott_w joined #salt
12:01 tomeff joined #salt
12:02 oz_akan_ joined #salt
12:08 kolaman joined #salt
12:10 kolaman hi all, I have just installed salt on an ubuntu machine in the cloud. now client shows connecting state at port 4505 to the sal server but when checked salt-key -L there are no keys .
12:10 kolaman what could be the problem
12:11 viq kolaman: verify on server that the connections are actually comming in (tcpdump)
12:11 viq Also, firewall?
12:11 flurick joined #salt
12:12 kolaman viq ports are opened in the firewall
12:15 viq kolaman: have you verified the packets are making their way to the server?
12:17 kolaman viq: got it, these instances are in the cloud and strange enough to see that adding security group to permit some port is not working so opened this for the glob :)
12:30 aat joined #salt
12:31 Nexpro1 joined #salt
12:31 jbunting joined #salt
12:36 drdran left #salt
12:38 kolaman hi viq sorry to bother you but I am again stuck in an issue with minion on client machine here is the pastebin of debug http://pastebin.ca/2421219
12:38 drdran joined #salt
12:39 viq I leave that to someone who actually knows something about salt :P
12:39 kolaman viq: :)
12:42 jslatts joined #salt
12:42 blee_ joined #salt
12:49 lemao joined #salt
12:53 shiznit joined #salt
12:54 blakearnold_ joined #salt
12:55 MTecknology agend: hi :)
12:56 agend MTecknology: hi :)
12:57 oz_akan_ joined #salt
13:02 anteaya joined #salt
13:04 Kholloway joined #salt
13:06 Gifflen joined #salt
13:08 Ivo joined #salt
13:09 juicer2 joined #salt
13:12 terminalmage joined #salt
13:15 KennethWilke joined #salt
13:18 iMil ok, replying to myself, deepness works out of the box in grains containing dicts
13:18 iMil this is awesome :)
13:19 teskew1 joined #salt
13:19 iMil {% for project in grains['projects'] %}
13:19 iMil {% for site in grains['projects'][project]['sites'] %}
13:19 iMil /tmp/{{ site }}:
13:19 iMil file.touch
13:19 iMil {% endfor %}
13:19 iMil {% endfor %}
13:19 iMil (for example)
13:19 iMil this works just as is :)
13:20 Nexpro1 joined #salt
13:22 jonconley joined #salt
13:26 whit joined #salt
13:27 diegows joined #salt
13:33 emocakes joined #salt
13:33 KennethWilke joined #salt
13:34 toastedpenguin joined #salt
13:38 shiznit joined #salt
13:39 emocakes joined #salt
13:41 racooper joined #salt
13:45 ageron joined #salt
13:46 jkleckner joined #salt
13:46 mgw joined #salt
13:46 Ivo joined #salt
13:47 brutasse iMil: you can directly go {% for project in grains['projects'].values() %} + {% for site in project['sites'] %}
13:48 ageron Hi everyone.  I read about the RSA exponent issue.  I installed '0.16.0-1precise', which is supposed to have the bug fixed, right?  And I ran salt '*' saltutil.regen_keys.  Is that all I need to do?  Shouldn't I also regenerate the server's key pair ?  Should I restart the minions?  Should I restart the master?  Thanks a lot.
13:53 iMil brutasse: oh, even better ! thanks :)
13:54 uta joined #salt
13:54 bemehow joined #salt
13:55 tpe11etier joined #salt
13:56 UForgotten joined #salt
13:57 capricorn_one joined #salt
13:57 uta joined #salt
13:57 pnl joined #salt
13:58 iMil pnl: \o/
13:58 iMil pnl: you there :)
13:59 bluemoon joined #salt
14:01 UForgotten_ joined #salt
14:08 pnl joined #salt
14:10 chadhs joined #salt
14:17 mgw joined #salt
14:18 kho joined #salt
14:18 isomorphic joined #salt
14:20 kho joined #salt
14:24 Jahkeup_ joined #salt
14:25 Jahkeup__ joined #salt
14:26 rbstewart joined #salt
14:30 teskew joined #salt
14:30 jspc joined #salt
14:32 jspc Can anybody point me to a good resource for what salt[] actually *does*? It looks like an array of coderefs (at least in perl aprlance) but I don't know if python has such a concept and I'm not familiar enough with the code base to find it
14:34 whit akoumjian: heyo, is salty-vagrant getting close to another release?
14:36 soukihei joined #salt
14:36 oz_akan_ joined #salt
14:38 akoumjian whit: Hi. We are waiting on Mitch to merge the provisioner into vagrant proper: https://github.com/mitchellh/vagrant/pull/1626
14:38 mgw jspc: Are you referring to the salt and __salt__ dicts that are available within the code?
14:38 jbunting joined #salt
14:38 akoumjian whit: Please feel free to bug him about it. :-)
14:38 whit akoumjian: oh cool :)
14:40 * whit adds a comment to that effect
14:40 noob2 joined #salt
14:40 shiznit joined #salt
14:40 JordanRinke What/where is the most complete/definitive salt stack tutorial that exists currently?
14:41 luminous JordanRinke: the walkthrough on docs.saltstack.com / salt.readthedocs.org
14:42 noob21 joined #salt
14:42 UtahDave joined #salt
14:42 Chocobo joined #salt
14:43 JordanRinke I will have to look at it again, when I looked at it before it just wasn't as guided, and complete as I would have liked (to recommend to people asking about it)
14:44 Asphyxiated|Dk joined #salt
14:44 Asphyxiated|Dk joined #salt
14:45 zooz joined #salt
14:45 jalbretsen joined #salt
14:46 jspc mgw: possibly... do you know off the top of your head *where* in the code it is?
14:46 jspc ...or how I can find it myself?
14:47 johntron joined #salt
14:49 Drekonus joined #salt
14:51 m_george|away joined #salt
14:52 m_george left #salt
14:52 mgw jspc: what is your goal?
14:53 mgw what part of the code are you working on?
14:53 cedwards joined #salt
14:54 mgw jspc: modules, for example, have the __salt__ dict which has references to all the other modules
14:56 mgw jspc: so, for example, in module a, you can do this: __salt__['b.fun']() to call the function 'fun' on module 'b'.
14:56 jbunting joined #salt
14:56 mgw UtahDave: good morning
14:56 StDiluted joined #salt
14:57 UtahDave mgw: morning!
14:57 Ivo joined #salt
14:58 mgw UtahDave: any thoughts on this: https://github.com/saltstack/salt/issues/5992
14:59 mgw madduck and I were discussing this Friday and got busy with it over the weekend.
14:59 Gifflen joined #salt
14:59 jspc mgw: I'm trying to understand what I'm reading in the docs more than anything- its more a case of 'why does this work'. By understanding what __salt__ is made of I hope to understand where to use it and why
14:59 mgw jspc: Which docs are you reading?
15:00 UtahDave Yeah, I did read those.  I think you have some great ideas.
15:00 mgw (where in the docs)
15:00 jspc https://salt.readthedocs.org/en/latest/topics/tutorials/states_pt3.html#advanced-sls-module-syntax
15:00 jspc Idle curiousity more than anything
15:00 UtahDave jspc: __salt__ is a dict that the Salt loader creates that contains all of the available Salt functions for you to use
15:00 Gifflen Hopefully this is a simple question. I'm deploying with salt-cloud and the infrastructure is running a bit slow on provisioning times. This is causing me to hit the 10 minute hard limit and destroying the VM. How would I go about extending the timeout when deploying?
15:02 UtahDave mgw: back in a few minutes. I have a conference call.
15:02 jspc UtahDave: when you say it contains functions: if the function is the key then what is the value? Is it a reference to where the code lives? Is it code (and so the brackets lambda-ise it [which is a verb I may have just invented] )
15:03 redbeard2 joined #salt
15:03 redbeard2 who was asking about salt-cloud?
15:03 mgw jspc: the value is the function itself
15:04 Gifflen me
15:04 redbeard2 hey Gifflen
15:04 Gifflen Hola!
15:04 redbeard2 Gifflen: i don't think we ever added a user option for timeout, but i can show you where it is in the code
15:05 Gifflen cool that works for me
15:05 mgw so you can do this (from the docs): {{ salt['file.group_to_gid'](usr) }}
15:05 jspc mgw: as it exists in memory? or the text of the function?
15:05 jspc mgw: I understand what it does; just not how it does it
15:05 isomorphic joined #salt
15:05 redbeard2 Gifflen: in fact, if you grep for timeout in saltcloud/utils/__init__.py, you'll see a couple of places to update it
15:05 Nexpro joined #salt
15:06 mgw jspc: in Python you can literally hold a reference to a function, so the value, essentially, is the function
15:06 mgw Are you wanting to define your own functions?
15:06 redbeard2 Gifflen: deploy_script() is the important function
15:06 Gifflen thanks redbeard2. I'll give that a go and see if that helps
15:06 Gifflen annnnnd.. things started deploying normally now hah
15:06 Gifflen go figure
15:07 Gifflen Good to know though.
15:07 Gifflen I still got a few more servers to deploy so I might need to update it anyway
15:07 bfrog so I'm a little confused by how to make salt secure
15:08 bfrog seems like if I do salt master/minion
15:08 bfrog should the master be comprimised my whole setup is comprimised
15:08 jspc mgw: nope, just honestly trying to understand what I'm reading. It does sound analogous to coderefs in other languages.
15:11 bfrog like I almost just want to have salt installed locally, do a one time salt-call high state then image and deploy
15:11 bfrog and never have a master
15:15 lazyguru joined #salt
15:16 toastedpenguin good morning
15:16 toastedpenguin is there anyway to do something like this "ln -sf /usr/share/zoneinfo/UTC /etc/localtime" on all hosts using salt state?
15:17 madduck mgw: I will be back over this probably tonight around 8pm CET+2 (in ca. 3 hours).
15:17 felskrone UtahDave: i sent thomas and also info@saltstack.com a mail regarding this: https://github.com/saltstack/salt/issues/5948
15:18 mgw madduck: ok
15:18 felskrone so if he wonders who wrotes this horribly long mail, that was me :-)
15:18 chrisgilmerproj joined #salt
15:22 chrisgilmerproj joined #salt
15:23 mattmb joined #salt
15:25 drdran left #salt
15:25 dthom91 joined #salt
15:26 aat joined #salt
15:27 jschadlick1 joined #salt
15:32 sciyoshi1 joined #salt
15:33 spork joined #salt
15:33 spork howdy
15:34 spork Could I bother you with something? How can I copy a file from the minion to the master? Salt-cp seems to work only one way... or I'm doing it wrong
15:34 spork I want to copy a .conf file and edit it... withoug using ssh, I don't know how
15:43 brianhicks joined #salt
15:43 spork anyone? :D
15:44 Odd_Bloke spork: Can you not just provision the file?
15:44 brianhicks spork: is there a reason file.managed doesn't work?
15:45 brianhicks spork: that is, what about your requirements makes it so you have to do minion -> master?
15:45 spork I want to install a package
15:45 spork and then change the source sonfig and provision it
15:45 spork but I need the original file first
15:46 spork let's say you install ntp. You might want to change /etc/ntp.conf later. Getting it to the salt:// directory on the master can come in handy
15:47 zkurey joined #salt
15:47 brianhicks sure. So you can't grab it with SCP even once?
15:47 spork of couse, I may be trying to do something kinda idiotic... I'm a salt noob :P
15:47 brianhicks otherwise, http://docs.saltstack.com/ref/states/all/salt.states.file.html#salt.states.file.sed may be useful for you
15:47 spork brianhicks: yes, I can. The question was, is that the standard way?
15:48 whit joined #salt
15:48 brianhicks I can't speak to the "standard" way but I'd copy the config file to master, make my edits/substitutions with a jinja template if needed, and just use state.managed
15:48 brianhicks that way everything is in once place.
15:48 spork since there's a salt-cp and a salt cp module, I though there could be a get and a put action
15:48 brianhicks it'd be more useful to edit in place, instead of making the round tirp
15:48 brianhicks that's what file.sed does
15:48 spork brianhicks: that's what I want to do, I was just wondering if I could do it withouh ssh, using salt alone
15:49 spork true, yet using file-managed is easier to read, specially in cases where you don't even have to template it (say, change the ntp server)
15:50 brianhicks spork: right, file.sed doesn't use ssh. So either copy it once and use file.managed or use file.sed to enforce the change despite other upstream config changes
15:50 spork also, thanks for the file.sed tip. I'm sure it'll come in handy later
15:50 spork brianhicks: yes, but to copy it, I can only use ssh, right?
15:51 brianhicks spork: the whole of salt.states.file is good - file.append might come in handy for NTP.
15:51 brianhicks spork: you definitely don't want to copy it *every* time, but to get it into your state tree to use file.managed, you would use SCP, yes. Or grab it from wherever it lives in source control.
15:51 Ryan_Lane joined #salt
15:52 spork yeah, I meant once
15:52 raccoon_ left #salt
15:52 brianhicks spork: you got it :)
15:52 spork I have a test machine, so I create a state to pkg.install something and then scp the .conf, edit it and file.manage it
15:53 spork I was just wandering If I could do something like salt-cp cp minion /etc/ntp.conf .
15:53 spork for example
15:53 spork still, ssh is good enough
15:53 zkurey joined #salt
15:54 spork thanks for all your help :D
15:55 brianhicks spork: you bet. Maybe look into vagrant though, it's super useful for test machines.
15:56 Katafalkas joined #salt
15:57 spork got a standard vbox setup (cloned machines, same base) for space reasons, but am going to convert some dev boxes to salt provisioning for sure (I vagrant at home)
15:57 spork but I need to learn how to do stuff with salt first
15:57 spork first impressions... way better tnah puppet :D
15:58 spork and the community is great. Thanks
16:02 rsimpkins In file.managed you can put a file_mode. Salt won't complain about it, but it also won't set the mode either. You have to use mode. Bug, or does salt not check for these types of things generally?
16:02 StDiluted morning
16:04 Gifflen joined #salt
16:04 UtahDave spork: you can use the cp.push function to copy a file from the minion to the master: http://docs.saltstack.com/ref/modules/all/salt.modules.cp.html#salt.modules.cp.push
16:05 UtahDave rsimpkins: The issue is if that the yaml gets compiled into python dicts and lists.  You can create arbitrary dict keys.
16:05 KyleG joined #salt
16:05 UtahDave StDiluted: morning!
16:06 UtahDave rsimpkins: so if you create a dict key/value that Salt doesn't care about, it doesn't do anything with it.  You can use that value in your templates, if you want
16:10 jpadilla joined #salt
16:10 koolhead17 joined #salt
16:11 pcarrier joined #salt
16:13 joehh joined #salt
16:14 kmrhb joined #salt
16:14 isomorphic joined #salt
16:16 spork UtahDave: Since this feature allows a minion to push a file up to the master server it is disabled by default for security purposes. - This part kinda worries me, mostly because the "on" feature seems to be all or nothing
16:17 UtahDave spork: how often do you plan on doing this?  Just for the initial setup?
16:17 spork can't just say "I want to receive files from just that minion". Also, is there any restriction as to the upload? Could I, for instance, overwrite a file with this?
16:17 spork yep
16:17 spork well, whenever I need to add a new config, for instance
16:17 spork I can live with ssh, no prob...
16:18 UtahDave Well, the uploaded file goes into the master's cache that it has for each minion. So each minion can only upload a file to it's cache directory.
16:18 spork ah, sweet
16:18 LucasCozy joined #salt
16:18 spork said that on the docs, but I wasn't sure how to use it
16:19 UtahDave spork: It's a fairly new feature, so I'm sure it could use some polishing.
16:19 spork the more I use salt, the more I like it
16:20 StDiluted When creating a user, and defining groups to have them added to the user, can you require that the group gets created first so that the user creation doesn't fail?
16:20 spork UtahDave: thatns, I'll check it out
16:20 zkurey Hey folks!  I'm running 15.3, and overstate keeps on plowing forward even if required stages have failures(results of False).  Just wondering since its a drastic change in behavior.  Haven't tried 16.0 since its not on epel(as of last night).
16:21 fxhp I stumbled on a quirk/bug in states/user.py module.   If a users home directory only set/created on the first highstate, if it is removed or changed it is not recreated or set during subsequent highstates.
16:22 fxhp %s/If /A/g
16:22 UtahDave StDiluted: yeah, just have your group creation states be required by the user creation states.  Also, there's an option to the user creation states that's something like "optional_groups"  so that the user creation continues even if a group in that list doesn't exist
16:23 StDiluted ok so require: - group: - whatever
16:23 UtahDave fxhp: I imagine that it's just passing in the option to the user creation function that creates the home directory. Sounds like it might be a bug
16:23 UtahDave StDiluted: Yeah, but you do have to have a state that's managing/creating that group
16:24 StDiluted can it be in the same state?
16:24 StDiluted like earlier in that same sls
16:24 UtahDave StDiluted: yep!
16:24 StDiluted whatever: group.present
16:24 StDiluted ok cool
16:24 UtahDave zkurey: can you pastebin your overstate?
16:27 dthom91 joined #salt
16:28 zkurey Sure.  http://pastebin.com/pYySCYfL
16:29 Chocobo joined #salt
16:31 UtahDave zkurey: OK, I think that looks good.  Are you getting any errors on your minions?
16:31 zkurey Not that I know of.  I downgraded back to 14.0, and things are happy again.  Actually only downgraded on the master.
16:32 fxhp UtahDave: I think that is what is happening, not sure about a decent solution.  I suppose the home directory could be managed via file.directory logic
16:32 zkurey Though even 14.0 will skip a few stages if one fails, and eventually starts executing them again.
16:32 UtahDave zkurey: any way you can test using 0.16.0? It should be in epel-testing
16:32 LucasCozy joined #salt
16:33 UtahDave fxhp: Why don't you open an issue on it so we can start a discussion on the proper way to handle that.
16:33 zkurey Yeah.  Will do later today.  If still present I'll file an issue.
16:33 UtahDave thanks, zkurey!
16:33 zkurey np.  thanks for all the salt.  = )
16:35 UtahDave :)
16:36 LucasCozy joined #salt
16:38 fxhp UtahDave: https://github.com/saltstack/salt/issues/6045
16:38 fxhp done
16:39 UtahDave thanks, man!
16:39 toastedpenguin when defining a symlink in a salt state, is there a way to force the symlink as with running ln -sf ?
16:40 kaptk2 joined #salt
16:41 toastedpenguin ran into an issue when trying to symlink /etc/localtime, got this error " File exists where the symlink /etc/localtime should be" but I can run ln -sf /usr/share/zoneinfo/UTC /etc/localtime manually
16:41 UtahDave toastedpenguin: have you tried  force: True      ?
16:42 ydavid joined #salt
16:43 toastedpenguin UtahDave:  didn't know there was that option....guess I need a "cheat" sheet of some sorts
16:43 toastedpenguin thanks!
16:43 LucasCozy joined #salt
16:44 LucasCozy joined #salt
16:45 StDiluted what does this error mean: Name /home/ubuntu/.emacs.d in sls emacs23-nox is not a dictionary
16:47 LucasCozy joined #salt
16:47 dzen StDiluted: your sls is not well formated
16:47 octarine joined #salt
16:48 UtahDave toastedpenguin: here's your cheatsheet!  :)  http://docs.saltstack.com/ref/states/all/salt.states.file.html#salt.states.file.symlink
16:54 noob2 joined #salt
16:55 cron0 joined #salt
16:56 teskew [ERROR   ] There was a query error: global name 'SaltCloudConfigError' is not defined
16:57 teskew getting this when trying to use a fresh install of salt-cloud 0.8.9 and fresh install of salt 0.16.0
16:58 teskew this is when trying to execute salt-cloud -m /path/to/a/mapfile
17:00 teskew https://gist.github.com/tateeskew/5950552   this is the command running and the warnings and exception
17:01 teskew this is with salt-cloud installed from PPA and also tested with install from PIP
17:02 UtahDave teskew: I'm summoning the salt-cloud dev
17:02 redbeard2 s0undt3ch: are you seeing this?
17:02 enduro joined #salt
17:03 jrgifford_ joined #salt
17:04 s0undt3ch redbeard2: looking
17:05 teskew i was getting ready to try the dev version from github, but i'll wait to see if s0undt3ch has they same issue
17:06 teskew i don't have a /etc/salt/cloud config. i'm using /etc/salt/cloud.profiles.d/variousfiles and /etc/salt/cloud.providers.d/variousfiles
17:08 jkleckner joined #salt
17:09 logix812 joined #salt
17:10 s0undt3ch teskew: there was a missing import, fixed on my local branch, though, it was trigered because you are either not defining 'private_key', the the path you've set to is is not valid
17:12 teskew okay, let me take a look. it's quite possible the path to the key is invalid
17:13 teskew since it's fresh install
17:13 dthom91 joined #salt
17:14 noob2 joined #salt
17:14 StDiluted UtahDave: re: my earlier group/user question, I need to  have a user and a group with the same name
17:14 s0undt3ch teskew: ok, redbeard2 just merged my change. If you use the latest from git, you should get a nice error
17:15 Vafoom joined #salt
17:15 s0undt3ch teskew: but you should be using the ec2 driver if there's nothing attaching you to the aws driver
17:15 StDiluted UtahDave: I have application: group.present
17:15 StDiluted but i also need application: user.present: - blah de blah
17:16 teskew s0undt3ch: there was a reason i was using the aws driver at some point. stuff changes so quickly that i'm sure i just stayed with the one that was original
17:16 Vafoom Just one quick question.  Can salt in standalone mode (no server) without use of ZeroMQ work on Python 2.4?
17:16 s0undt3ch teskew: yes, I'm sure. ec2 superseeds the aws driver in salt-cloud
17:16 Vafoom or is 2.6 absolutely minimum requirement?
17:16 s0undt3ch Vafoom: yep, 2.6 minimum
17:17 s0undt3ch Vafoom: ah, didn't read it all
17:17 UtahDave Vafoom: have you tried it yet?  It may work.
17:17 s0undt3ch Vafoom: you could test it, though, I'm unsure ;)
17:17 Vafoom i havent.  i have a need to run it on centos 5.x which comes with python 2.4.3.  Don't want to do any upgrade to run it standalone for some applications
17:19 atweiden joined #salt
17:19 felixhummel joined #salt
17:20 atweiden can anyone help? local arch linux box can't ping digital ocean, first time w/ salt
17:21 fxhp atweiden: hi
17:22 fxhp how do you mean cannot ping?
17:22 fxhp atweiden: ping ipaddress or salt 'minion-id' test.ping
17:23 atweiden fxhp: i'm running `sudo salt '*' test.ping`
17:24 bluemoon joined #salt
17:27 fxhp atweiden: salt-key -L
17:27 zkurey left #salt
17:27 fxhp atweiden: is your minion key approved?
17:27 atweiden Accepted Keys:
17:27 atweiden annakournikova.127.0.0.1
17:27 fxhp atweiden: is that the minion ID of your digital ocean server?
17:27 atweiden yes
17:28 fxhp (looks funny to me)
17:28 atweiden the IP?
17:28 fxhp yeah
17:28 atweiden change to digital ocean IP?
17:28 fxhp normally the minion ID is th hostname or FQDN of the minion
17:29 atweiden i didn't know the IP when setting it up
17:29 atweiden i do now though
17:30 atweiden but, have to check web browser gui
17:30 fxhp what uncommented settings are listed in your digital ocean minion config?
17:30 atweiden master: 127.0.0.1
17:30 atweiden that's all
17:30 fxhp is this a masterless minion?
17:30 atweiden oh, i'm sorry thought you said local box
17:30 atweiden i haven't connected to digital ocean yet
17:31 whit joined #salt
17:31 atweiden there's no minion config on that box
17:31 atweiden unless salt-cloud set it up for me
17:31 StDiluted Anyone have any idea how to get both a user and a group with the same name created in the sale .sls?
17:31 StDiluted same*
17:31 fxhp atweiden: hmmm
17:32 fxhp salt-cloud can setup the minion
17:32 fxhp atweiden: is annakournikova.127.0.0.1 your master?
17:32 fxhp or the minion in digital ocean?
17:32 atweiden AK is digital ocean minion
17:32 andrewclegg joined #salt
17:33 fxhp atweiden: I recently got digital ocean and salt-cloud/salt-master working together, check out my block, maybe you missed a step.
17:33 fxhp http://russell.ballestrini.net/create-your-own-fleet-of-servers-with-digital-ocean-and-salt-cloud/
17:34 fxhp StDiluted: yup
17:34 atweiden i followed your guide actually
17:34 fxhp atweiden: oh no! haha...
17:34 atweiden my /etc/salt/cloud is different
17:34 atweiden used master.127.0.0.1
17:34 StDiluted fxhp: lol, any hints? :)
17:34 fxhp Did you manually accept annakournikova.127.0.0.1 on your master?
17:35 atweiden no, salt-cloud did it automatically
17:35 whiteinge clone1018: did you get past that RuntimeError traceback in salt-api?
17:35 atweiden but what is purpose of master.foxhop.net?
17:35 fxhp atweiden: master.foxhop.net is a DNS record pointing at my salt master
17:36 atweiden does salt-master have to be a remote machine?
17:36 fxhp you could use the IP address of your salt master
17:36 clone1018 whiteinge: nope
17:36 atweiden ok
17:36 fxhp atweiden: salt-master can be configured to run from pretty much anywhere
17:36 atweiden i was trying to run it locally, but that's not strictly necessary
17:36 atweiden is there a way to run it from my local arch box?
17:37 fxhp atweiden: it is basically the "command center"
17:37 whiteinge clone1018: it's coming from a mismatch of salt & salt-api versions. what versions are your salt-master and salt-api?
17:37 UtahDave atweiden: that should probably be  master: 127.0.0.1
17:37 fxhp atweiden: I think you should start with an easier tutorial before jumping into salt-cloud
17:37 atweiden fxhp: heheh
17:37 clone1018 whiteinge: I'm not at home right now, it's running on a virtual box but they're both from the install bootstrap
17:37 atweiden but i prefer to dive in
17:38 fxhp atweiden: you learn the power of salt-cloud after learning the power of salt
17:38 atweiden there will be much salting then
17:38 atweiden :)
17:39 fxhp atweiden: I think you need a better foundation of how to setup a salt-master and a salt-minion first
17:39 fxhp atweiden: then move on to automating provisioning via salt-cloud
17:39 fxhp StDiluted: lets see
17:40 StDiluted fxhp: https://gist.github.com/dginther/5950843
17:41 StDiluted the user creation fails because the group is not there
17:41 StDiluted the deploy group gets created though
17:43 rlb Is startup_states the best way to configure a minion to a specific state when it first comes up (in particular when the minion might be started by something other than the master)?
17:43 toastedpenguin I am trying to setup salt to install/manage additional repos I need for different packages, is it possible to copy a file from the master to the minion as part of the requirement for the repo?  I need to get the pgp key for the repo onto the minions
17:43 whiteinge clone1018: double-check when you're back in front of that box. there are commits in salt-api's develop to use the new logging. it's looking to me like salt-api may need a new release to match the last salt release
17:44 alazylearner joined #salt
17:45 shiznit joined #salt
17:45 jslatts joined #salt
17:46 felixhummel joined #salt
17:47 jbunting joined #salt
17:50 teskew s0undt3ch and redbeard2 : i've got another. when trying to delete a map that contains one definition, i get this:  https://gist.github.com/tateeskew/5950919
17:51 fxhp StDiluted: just put this together but this is how I do it: http://russell.ballestrini.net/understanding-salt-stack-user-and-group-management/
17:52 StDiluted thanks fxhp
17:54 dthom91 joined #salt
17:56 fxhp StDiluted: welcome
17:57 StDiluted That worked. simple, but I was overlooking the proper syntax
17:58 Kholloway joined #salt
18:00 djn joined #salt
18:01 jacksontj joined #salt
18:01 thingles joined #salt
18:02 StDiluted how do i specify a null in jinja? like instead of None, I want a blank space
18:03 UtahDave ' '     like that?
18:03 djn hey, whats the status on an iptables state? there is an issue for it and its milestone is 0.17 which is due this month, but there is no code in git yet?
18:04 StDiluted perfect, thanks UtahDave
18:05 StDiluted I thought the tight be it but wasn't sure
18:05 neilf joined #salt
18:05 StDiluted that might*
18:05 munhitsu joined #salt
18:05 xrl joined #salt
18:06 UtahDave djn: I know redbeard2 was going to knock that one out soon. Not sure what he's done so far
18:06 ada__ joined #salt
18:06 xerxas joined #salt
18:07 UtahDave djn: you might ask on that thread to nudge him
18:08 redbeard2 djn: i've been trying to work on it these past several days, but i keep getting distracted by salt-cloud stuff. it hasn't been forgotten tho.
18:10 fxhp redbeard2: the salt-cloud docs need to be spanked into submission
18:10 fxhp : P
18:10 redbeard2 fxhp: agreed. and i was able to make some changes this morning.
18:10 redbeard2 too much to do, too little time.
18:12 djn redbeard2: thank you for your response, will it make the cut into 0.17? what do you think? also, ip6tables will be supported I guess? I'm looking forward to this
18:12 fxhp djn which bug are you talking about?
18:12 enduro joined #salt
18:12 StDiluted Any progress on VPC support in salt-cloud?
18:12 fxhp StDiluted: what is VPC?
18:13 redbeard2 djn: hopefully the iptables state will make it in... i'm only working on the ipv4 version right now, but i don't expect adding ip6tables will be too much of a pain when we add it
18:13 StDiluted Amazon Virtual Private containers
18:13 redbeard2 StDiluted: VPC was added by a community member, but not documented, so i keep forgetting about it. i can find you the relevant pull req if you'd like.
18:14 StDiluted redbeard2: ah, right on. I could really use it if it's working
18:14 djn fxhp: https://github.com/saltstack/salt/issues/3597 this one
18:14 stephen__ joined #salt
18:15 redbeard2 StDiluted: https://github.com/saltstack/salt-cloud/pull/585
18:15 redbeard2 there's really not much too it, and it's probably not complete, but there is something there
18:16 djn redbeard2: thanks for the prompt info, I appreciate it
18:16 loolglool joined #salt
18:16 redbeard2 djn: np
18:17 fxhp djn: ohh I see, yeah I messed around with the salt/modules/iptables.py you are looking for a salt/states/iptables.py implementation
18:17 StDiluted redbeard2: so that code is in the latest? (sorry, new to github, pull, etc)
18:18 redbeard2 StDiluted: yes, it is in 0.8.9, which is the latest
18:18 StDiluted ok great
18:18 redbeard2 it was added to develop just after 0.8.8, so you won't find it there
18:18 fxhp StDiluted: my blog post explains how to get the latest
18:19 koolhead17 joined #salt
18:19 koolhead17 joined #salt
18:19 fxhp StDiluted: because most os packages have not kept up with releases
18:19 StDiluted thanks fxhp
18:22 _dan__ left #salt
18:22 noob2 left #salt
18:22 DredTiger joined #salt
18:23 s0undt3ch teskew: is that still using aws?
18:23 cnelsonsic joined #salt
18:23 timoguin_work joined #salt
18:27 fxhp UtahDave: https://github.com/saltstack/salt/issues/6045#issuecomment-20625733
18:28 fxhp found the issue
18:28 fxhp not sure if salt can do anything to resolve it
18:28 fxhp in a systematic way
18:28 UtahDave Ah, interesting
18:30 bluemoon joined #salt
18:30 cnelsonsic left #salt
18:31 stevetodd joined #salt
18:32 djn joined #salt
18:33 fxhp UtahDave: yeah because I'm using a user for a service things could get hairy
18:33 fxhp I'm going to head to lunch and ponder a work around
18:34 fxhp (helps to walk away)
18:35 jslatts joined #salt
18:38 redbeard2 left #salt
18:38 g3cko joined #salt
18:45 Newt[cz] joined #salt
18:47 toguin_ joined #salt
18:48 cnelsonsic joined #salt
18:50 jacksontj joined #salt
18:53 cnelsonsic joined #salt
18:56 dthom91 joined #salt
19:03 N-Mi joined #salt
19:03 N-Mi joined #salt
19:06 teskew s0undt3ch: no, that's ec2
19:07 s0undt3ch teskew: hmm, could you file a bug reports with that info please? full logging output wouls also be cool, or a link to a gist containing that.
19:08 teskew s0undt3ch: also, i'm having this problem with a multivm map. https://github.com/saltstack/salt-cloud/issues/658
19:08 teskew which makes it pretty much unusable for me at the moment.
19:09 s0undt3ch teskew: ah, you're esacteksab?
19:09 teskew nope
19:09 s0undt3ch ah, same issue then
19:09 s0undt3ch :)
19:09 teskew but i'm having that same problem.
19:09 s0undt3ch well, I need to devote some time to fix the salt-cloud issues
19:10 s0undt3ch just haven't gotten to it
19:12 toastedpenguin if a file is specified in a state file on the master that doesnt exist on the minion, is it copied from the master to the minion?
19:14 toastedpenguin so far I have just been modifying existing files so I wasn't sure what the outcome is if the file doesnt exist
19:20 aranhoide joined #salt
19:20 dthom91 joined #salt
19:20 mgw toastedpenguin: if you're using file.managed, it will copy the file
19:22 eightyeight joined #salt
19:23 jacksontj joined #salt
19:24 jslatts joined #salt
19:27 diegows joined #salt
19:27 kaptk2 joined #salt
19:29 berto- joined #salt
19:29 spicyWith joined #salt
19:29 Newt[cz]1 joined #salt
19:30 codysoyland is there a way to invoke salt runners from the python api?
19:31 djn joined #salt
19:31 codysoyland for example, I need to write a script that first checks which nodes are down
19:31 codysoyland so I tried:
19:31 codysoyland from salt.runners.manage import down
19:31 codysoyland down()
19:31 codysoyland and it hits: NameError: global name '__opts__' is not defined
19:32 codysoyland indeed __opts__ is not defined because some poor design choice made most of salt impossible to import without doing dirty tricks
19:33 codysoyland so, can somebody enlighten me on this magic or otherwise tell me how to invoke a runner from a script that does not have __opts__ magically sprinkled in?
19:33 bfrog any thoughts on the best way to securely use salt?
19:33 bfrog totally isolated from the internet?
19:34 bfrog I mentioned my concerns yesterday, no one really mentioned what they do
19:35 toastedpenguin mgw: ok cool, didnt want to assume it did that, make life easier when pushing files out to the minions
19:35 eightyeight joined #salt
19:35 codysoyland bfrog: my understanding is that ZMQ is not safe to use over the internet without explicit firewall policies (whitelist your office IP for example), so most people including myself run salt only on an internal network and access the master via SSH
19:36 toastedpenguin what does using pkgrepo have over using file.managed for say yum.repos.d repo files?
19:37 lex joined #salt
19:40 StDiluted anyone written a salt state for the sumo logic collector?
19:45 koolhead11|away joined #salt
19:58 whiskybar joined #salt
20:09 whiteinge codysoyland: opts = config.client_config('/etc/salt/master'); runner_client = runner.Runner(opts)
20:11 codysoyland whiteinge: thanks
20:11 zwevans joined #salt
20:13 whiteinge codysoyland: (i'm looking at the runner client from the Python shell for the first time) ideally you should then be able to use the cmd() method to invoke the runner module (same as with salt's LocalClient)
20:14 codysoyland whiteinge: yeah, I was able to figure that out (runner.cmd('manage.status', [False]))
20:14 whiteinge codysoyland: ah, perfect. i was just about to complain that the interface to cmd() looks not user friendly :-/
20:15 druonysus joined #salt
20:15 druonysus joined #salt
20:15 codysoyland most of these APIs are fine. I'm just whiney about globals (__salt__, __opts__, etc) :)
20:15 dthom91 joined #salt
20:15 * whiteinge nods
20:16 StDiluted Is there a way to make Jinja match a glob or regex, such as {% if grains['node name'] == 'prod-*'
20:16 StDiluted stupid colloquy put a space in nodename
20:17 StDiluted since it's a huge hassle to get the EC2 tags from within an instance
20:18 nliadm StDiluted: they aren't in a grain?
20:18 StDiluted not the tags, no
20:19 nliadm could you write a grain? then you can do {% if 'tag' in grains['tags'] %}...
20:19 StDiluted in order to get that information, your AWS creeds have to be on the instance, and I would prefer that not be the case
20:20 nliadm could do it in the pillar
20:20 druonysus joined #salt
20:20 druonysus joined #salt
20:20 UtahDave StDiluted: how about: {% if grains['node name'].startswith('prod-')
20:20 StDiluted well, it's complicated by the fact that they have used comma separated lists for roles in the tags
20:21 StDiluted UtahDave: that's exactly what I needed. are there other '***with' functions, such as 'endswith', etc?
20:21 nliadm StDiluted: string.split(',')
20:22 UtahDave StDiluted: that's just a python builtin function on a string
20:22 nliadm http://jinja.pocoo.org/docs/templates/#list-of-builtin-filters
20:22 StDiluted nliadm: yes, I could do that, but the issue is that in my opinion, you shouldn't have multiple rioles assigned to a single machine
20:22 StDiluted ah. I'm not a python guy
20:22 StDiluted thanks
20:22 UtahDave you're welcome!
20:22 KennethWilke UtahDave: hey, i wanted to ask you about that salt sprint thingy, do you know who's doing salt sprint thing at rackspace
20:23 KennethWilke also that the address is wrong
20:23 StDiluted roles*
20:24 UtahDave oh, it is?
20:24 KennethWilke yeah, it's the old main address
20:24 UtahDave KennethWilke: JordanRinke has been helping coordinate the sprint. I know others are involved, but I'm not sure who
20:25 KennethWilke alrighty cool, thank you
20:25 UtahDave KennethWilke: you're welcome! I'll see about getting the correct address
20:25 UtahDave thanks for pointing that out
20:26 KennethWilke no problem
20:26 druonysus joined #salt
20:27 UtahDave KennethWilke:  5000 Walzem Rd correct?
20:28 zkurey joined #salt
20:29 KennethWilke yessir!
20:29 UtahDave thanks!
20:29 KennethWilke you come visit!
20:29 KennethWilke i know you have the address :)
20:30 toastedpenguin can you define the name of the nodegroups or are the predefined as group1, group2 etc.?
20:31 auser joined #salt
20:31 auser hey all
20:31 UtahDave yep!  be there on the 17th, KennethWilke
20:31 UtahDave toastedpenguin: you define the name to be whatever you want
20:31 UtahDave holla, auser!
20:31 bluemoon joined #salt
20:31 zkurey Hey UtahDave.  Trying to test the overstate problem I described earlier.  But having trouble getting the bits.  Know why 0.16.0 is not on epel-testing for cent6?
20:32 toastedpenguin hmm ok its telling me it can't find the nodegroups name I defined, thought maybe it was predefined
20:33 UtahDave zkurey: Ah, sorry. Our packager is behind on that. Hopefully he'll have it done soon.
20:33 UtahDave toastedpenguin: did you restart the master?
20:33 KennethWilke UtahDave: oh awesome, i may see you here
20:33 toastedpenguin yes
20:33 zkurey k.  just wanted to make sure I wasn't crazy.  Thanks.
20:33 UtahDave cool, KennethWilke!
20:33 auser how goes UtahDave!
20:33 UtahDave good, man!
20:34 shinta42 joined #salt
20:34 auser sweet
20:34 jbunting left #salt
20:35 jacksontj joined #salt
20:36 shinta42 left #salt
20:41 brianhicks joined #salt
20:41 bfrog left #salt
20:43 jhauser joined #salt
20:44 Xeago joined #salt
20:48 toastedpenguin UtahDave: the spacing in the master file for nodegroups was 2 spaces to many
20:49 toastedpenguin UtahDave: fixed that and it works....can you glob minion names in the nodegroups or do you need to list every minion individually?
20:52 bfrog joined #salt
20:52 bfrog seems like selinux.boolean doesn't work in fedora 19
20:55 spicyWith joined #salt
20:56 aboe joined #salt
20:58 bemehow joined #salt
20:58 zooz joined #salt
20:59 rigdon joined #salt
21:01 nrub joined #salt
21:02 rigdon Hopefully quick question. Using salt 0.15.3 on CentOS. Is there a way to specify a yum groupinstall inside an SLS file? I found the page on calling modules from states, but it's use is not entirely clear to me. Thanks in advance.
21:03 rigdon Basically the state equivalent of `salt "*" pkg.group_install "Development Tools"`
21:03 racooper bfrog,  what precisely is happening? errors? debug?
21:09 shiznit joined #salt
21:10 atweiden digital ocean is looking good
21:10 atweiden but i'm getting "Failed to authenticate,"
21:11 atweiden the cloud vm was successfully created and i'm sure the pub key is good
21:11 atweiden any ideas?
21:12 atweiden (im running it as root)
21:13 mr_chris joined #salt
21:13 mr_chris I see how to use salt.modules.git.clone from the command line but I am confused on how to use it within an SLS file.
21:14 UtahDave atweiden: I used digital ocean all the time. Have you specified your pub key in the profile?
21:14 atweiden UtahDave: yes
21:15 atweiden ssh_key_file: /etc/salt/keys/id_rsa
21:15 atweiden key name is good
21:15 giantlock joined #salt
21:15 atweiden during setup, salt-cloud successfully retrieved `date` as well
21:16 atweiden so idk what the issue is
21:17 UtahDave atweiden: can you pastebin a sanitized version of you salt-cloud configs?
21:17 jeffrubi` joined #salt
21:22 atweiden UtahDave: http://git.io/eiwsqQ
21:23 bfrog racooper: it just errors out with a python error
21:23 bfrog selinux.list_booleans
21:23 bfrog gives a python stack
21:23 bfrog lemme post it
21:23 atweiden UtahDave: 1 sec
21:23 bfrog https://gist.github.com/bfrog/5952625
21:23 bfrog racooper: above
21:24 redondos joined #salt
21:24 redondos joined #salt
21:24 racooper bfrog,  this might help narrow it down... http://docs.saltstack.com/topics/troubleshooting/index.html
21:24 atweiden UtahDave: http://git.io/VDp38w
21:24 UtahDave atweiden: OK, couple of things.  change it to   master: 173.255.198.27
21:25 UtahDave I think you only need the ssh key info in one place. probably just in cloud.providers.
21:25 UtahDave And it must match the key you uploaded in the digital ocean web gui
21:25 atweiden i will try that
21:26 redondos hi. can i tell pkg.install to install a version higher than a specific number? (i know version numbers can be difficult especially because of strings following digits)
21:26 UtahDave also, you need to run salt-cloud from your salt master to have it automatically set up the keys
21:27 racooper bfrog,  another thought: you may need semanage installed. It was missing in my (minimal) CentOS 6 install, from policycoreutils-python
21:29 UtahDave redondos: which OS?
21:30 redondos UtahDave: Linux
21:30 redondos Ubuntu and CentOS
21:30 UtahDave ok
21:30 bluemoon joined #salt
21:30 atweiden UtahDave: it's running from the master, unfortunately i get the same results with the config file change
21:31 UtahDave terminalmage: do you know if you can do what redondos is attempting? The docs don't indicate that it's possible.
21:31 atweiden it's retrieving `date` during setup tho
21:32 dthom91 joined #salt
21:32 terminalmage UtahDave: redondos: this depends on the support for this in the package provider
21:32 bfrog racooper: thanks
21:32 bfrog will do that
21:32 atweiden the only other oddity: [WARNING ] The function 'cloud_config()' defined in '/usr/lib/python2.7/site-packages/saltcloud/config.py' is not yet using the new 'default_path' argument to `salt.config.load_config()`. As such, the 'SALT_CLOUD_CONFIG' environment variable will be ignored
21:32 atweiden [WARNING ] The function 'cloud_providers_config()' defined in '/usr/lib/python2.7/site-packages/saltcloud/config.py' is not yet using the new 'default_path' argument to `salt.config.load_config()`. As such, the 'SALT_CLOUD_PROVIDERS_CONFIG' environment variable will be ignored
21:32 atweiden [WARNING ] The function 'vm_profiles_config()' defined in '/usr/lib/python2.7/site-packages/saltcloud/config.py' is not yet using the new 'default_path' argument to `salt.config.load_config()`. As such, the 'SALT_CLOUDVM_CONFIG' environment variable will be ignored
21:32 atweiden (apologiez)
21:33 terminalmage UtahDave: redondos: ebuild, pacman, and zypper support it
21:33 terminalmage this is noted in the documentation for the pkg.installed state
21:33 bhosmer joined #salt
21:33 UtahDave ah, thanks, terminalmage
21:33 redondos I missed that part of the docs, thank you terminalmage
21:34 UtahDave atweiden: in your cloud config the minion section needs to be indented on level.
21:35 atweiden 4 sw?
21:35 atweiden will see
21:35 terminalmage redondos: I guess that it is possible for us to ensure that a version is greater than a specified one
21:36 terminalmage but that support does not currently exist
21:36 terminalmage it presently just these operators where they are supported in the individualy provider
21:36 terminalmage s/just/just uses/
21:37 atweiden UtahDave: can you paste your cloud config?
21:37 atweiden I'm getting Error parsing configuration file: /etc/salt/cloud - mapping values are not allowed here
21:38 atweiden indented minion over by 4
21:38 tomeff joined #salt
21:38 bhosmer joined #salt
21:38 UtahDave atweiden: yeah, give me a minute
21:39 redondos terminalmage: i see. it's not always trivial, however, to tell when the version of a deb/rpm is higher than another. salt could support basic version numbering (2.5, 0.12.5) and it should just report if it can't determine it for sure (0.5-release vs 0.5-experimental: this is not uncommon, as a matter of fact I've seen worse)
21:40 dthom91 joined #salt
21:41 bhosmer_ joined #salt
21:42 bhosmer__ joined #salt
21:44 terminalmage redondos: yeah, some package providers have their own version comparison commands
21:44 terminalmage and we use them where possible
21:44 terminalmage ubuntu, for instance
21:44 terminalmage er, apt
21:45 terminalmage otherwise we use looseversion
21:45 Jahkeup_ joined #salt
21:46 terminalmage no solution will ever be perfect, but I think salt's is about as good as you can get
21:47 redondos so you're saying apt should support < and > for example?
21:47 emocakes joined #salt
21:47 terminalmage no
21:48 terminalmage we use the version comparison to check if the latest version is installed
21:48 terminalmage like I mentioned earlier, we're using the comparison operators directly as supported in the backend providers
21:48 terminalmage to apply it across the board would take some work
21:49 redondos ok, thanks again terminalmage (and UtahDave)
21:49 StDiluted hey there auser
21:49 terminalmage no prob. I'd have to think about how to apply this sort of sort across the board
21:49 auser hey StDiluted
21:50 StDiluted have a good weekend?
21:50 auser I'm about 1/2 the way through the post for you
21:50 auser :)
21:50 auser yeah, it was great
21:50 rlb Can salt commands race, for example can two simultaneous calls to "salt '*' hosts.set_host X Y" cause trouble with /etc/hosts, or is host.set_host careful to handle the updates atomically?
21:50 auser full of work, but great nonetheless
21:50 ckrough joined #salt
21:50 auser you?
21:50 StDiluted auser: no worries, no rush. My weekend was decent. Saw Mastodon, Five Finger Death Punch and Rob Zombie, and did absolutely nothing work related.
21:51 auser ahha, nice
21:51 auser lucky
21:51 StDiluted it's funny when your 13 year old daughter is the reason you go to a metal show
21:51 auser haha
21:55 talso joined #salt
21:56 AviMarcus joined #salt
21:56 cron0 joined #salt
21:57 aat joined #salt
21:58 jacksontj joined #salt
22:02 auser hey all
22:03 ninkotech joined #salt
22:05 Daviey joined #salt
22:06 jslatts joined #salt
22:07 jschadlick joined #salt
22:09 aat joined #salt
22:10 jeddi joined #salt
22:14 mr_chris How do you go about using the git modules in an sls file? http://docs.saltstack.com/ref/modules/all/salt.modules.git.html
22:15 mr_chris Could someone please point me in the right direction for learning how to convert the modules documentation into a work sls file is are sls files limited to installing packages and ensuring that services are running?
22:16 mr_chris *into a working, or are sls files limited...
22:18 mr_chris Nevermind. Figured it out. I'm looking for salt states, not salt modules. http://docs.saltstack.com/ref/states/all/salt.states.git.html
22:21 atweiden with digital ocean, i'm getting "No minions matched the target. No command was sent, no jid was assigned."
22:21 atweiden considering trying the git version
22:21 atweiden of salt-cloud
22:23 UtahDave mr_chris: yeah, you got it!
22:23 UtahDave atweiden: please pastebin the output of sudo salt-key -L      from your master
22:25 atweiden http://pastebin.com/trnVXysD
22:25 rlb can salt-key -A return before the key is actually accepted?  I thought I saw an (automated) "salt MINION cmd.run ..." fail when I ran it (automatically) immediately after a "salt-key -A MINION"
22:25 rlb ...and sleeping for a bit just after the "salt-key -A MINION" appeared to fix the problem
22:28 dthom91 joined #salt
22:31 mgw joined #salt
22:33 bemehow joined #salt
22:34 oz_akan_ joined #salt
22:35 techdragon joined #salt
22:37 fragamus joined #salt
22:40 UtahDave atweiden: so your minion config has   id: annakournikova.173.255.198.27      in it?
22:44 atweiden UtahDave: on the master server, /etc/salt/minion is 100% commented out
22:45 atweiden Is it necessary to adjust settings on the minion itself before running test.ping?
22:55 jacksontj for multi-master in 0.16.0 does the minion return the data for a given job to both masters? or do the masters replay the event bus to the other one?
22:55 berto- joined #salt
23:01 anteaya joined #salt
23:02 bluemoon joined #salt
23:05 UtahDave atweiden: I'm a bit confused.  Your minion config has to at least have master: <master hostname or ip>
23:05 UtahDave jacksontj: I believe the minions respond to requesting master. I'm not sure about the event bus. I'd guess the same, but I'm not sure.
23:07 jacksontj so the job cache won't be on both hosts then i'd imagine
23:07 bemehow joined #salt
23:14 nliadm UtahDave: does external_auth allow for multiple auth types? I can get it to work if I have just ldap OR pam, but not both
23:15 UtahDave nliadm: Yeah, I'm pretty sure you're supposed to be able to do that.
23:15 nliadm that's what I thought. I'll double-check my setup.
23:15 cxz joined #salt
23:16 nliadm I'd like to allow a few users to use pam, and then have ldap just auth against our AD server
23:19 UtahDave right.
23:19 druonysus joined #salt
23:19 druonysus joined #salt
23:21 zkurey left #salt
23:21 ydavid joined #salt
23:24 jaequery joined #salt
23:26 nliadm UtahDave: and '*' should work for a user?
23:27 UtahDave Yeah, all users.
23:28 nliadm doh, surrounding it with single quotes worked
23:29 Corey Yeah, wildcard escapes are fun.
23:31 tpe11etier joined #salt
23:34 jaequery joined #salt
23:38 ydavid joined #salt
23:40 druonysus joined #salt
23:40 druonysus joined #salt
23:44 david_a joined #salt
23:45 godber joined #salt
23:47 evax joined #salt
23:49 mgw joined #salt
23:52 whit joined #salt
23:59 jschadlick left #salt

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