Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2013-07-03

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

All times shown according to UTC.

Time Nick Message
00:01 Gifflen joined #salt
00:07 alazylearner joined #salt
00:07 pweo joined #salt
00:10 kenbolton joined #salt
00:10 bluemoon joined #salt
00:15 bhosmer joined #salt
00:17 dthom91 joined #salt
00:23 kenbolton joined #salt
00:30 kenbolton joined #salt
00:51 cxz joined #salt
00:53 toguin_ joined #salt
00:53 johntron joined #salt
00:54 jslatts joined #salt
00:54 Xeago_ joined #salt
00:55 Furao_ joined #salt
00:55 bhosmer joined #salt
00:55 sciyoshi2 joined #salt
00:57 alekibango joined #salt
00:58 ahammond any news about the 0.16 release? I'm all excited! :)
00:58 longdays_ joined #salt
00:59 tomeff joined #salt
01:00 tonthon_ joined #salt
01:00 zz_farra joined #salt
01:01 a1j joined #salt
01:01 cluther joined #salt
01:01 blakearnold_ joined #salt
01:01 chuffpdx_ joined #salt
01:01 KyleG1 joined #salt
01:01 dthom911 joined #salt
01:02 capricorn_1 unsalted newbie here. Trying to find how to manage KVM (ubuntu) from salt-master. right doc pages have yet to pop up. Any link? Appreciated
01:02 rfgarcia_ joined #salt
01:03 s0undt3ch joined #salt
01:03 bluemoon_ joined #salt
01:04 whiteinge capricorn_1: take a look at the virt module:
01:04 whiteinge http://docs.saltstack.com/ref/modules/all/salt.modules.virt.html
01:04 jefimenko1 joined #salt
01:04 chrism_ joined #salt
01:05 craig___ joined #salt
01:06 jafo joined #salt
01:06 whiteinge there is also two qemu modules that can work with vm images
01:06 whiteinge http://docs.saltstack.com/ref/modules/all/salt.modules.qemu_nbd.html
01:06 pmcg_ joined #salt
01:06 whiteinge http://docs.saltstack.com/ref/modules/all/salt.modules.qemu_img.html
01:06 tempspace_ joined #salt
01:06 capricorn_1 I tried a number of commands but I keep getting response like "virt.create" is not available or "hyper.virt_info" is not available. Seems I'm missing modules. Isn't that automagically installed with salt-master?
01:07 Valda joined #salt
01:07 koolhead11|away joined #salt
01:07 whiteinge ah, gotcha. no
01:07 whiteinge some salt modules have their own dependencies
01:08 whiteinge and those dependencies must be installed on the minion (in the case of execution modules, like the ones we're talking about now)
01:08 capricorn_1 whiteinge thanks. It seems I need to learn and play some more with basic salt stuff.
01:09 capricorn_1 is there a way to list the dependencies needed?
01:09 whiteinge if you look at the top of the virt module docs (little tough to see) it details what is required (if anything)
01:09 jpcw_ joined #salt
01:09 whiteinge not from the salt CLI. just from the docs
01:10 capricorn_1 I see what you are saying. I currently use virt-manager to create VMs but would like to do it from command line.
01:10 premera_t joined #salt
01:11 whiteinge if you aptitude install python-libvirt on your hypervisor those module functions should work in salt
01:12 Valdo joined #salt
01:12 whiteinge (you may need to restart the salt-minion to pick up the change)
01:12 jhujhiti joined #salt
01:12 goodwill joined #salt
01:13 jhujhiti joined #salt
01:13 joonas joined #salt
01:13 bawnzai joined #salt
01:13 jslatts joined #salt
01:14 capricorn_1 python-libvirt is already the newest version. Seems you are leading me to the water. I was able to create a virtual disk from example, qemu_img.make_image /tmp/image.raw 10240 raw That's a good start
01:14 hotbox joined #salt
01:14 viq joined #salt
01:14 viq joined #salt
01:14 oz_akan_ joined #salt
01:15 rhand joined #salt
01:16 whiteinge ah, nice. peculiar about libvirt though. do you have salt set up on a single machine or multiple machines?
01:16 akoumjian joined #salt
01:16 travisfischer joined #salt
01:16 mattikus` joined #salt
01:16 martineg_ joined #salt
01:17 svx joined #salt
01:17 swa joined #salt
01:18 baoboa joined #salt
01:18 capricorn_1 salt-master is ubuntu VM, and have a bunch ov centos etc. VMs on my workstation under VirtualBox. KVM server is another box with 2 manually created VMs but I want to manage them with salt.
01:18 s4muel joined #salt
01:18 ckrough joined #salt
01:19 jpcw joined #salt
01:19 Nexpro1 joined #salt
01:21 capricorn_1 have to run to do other things before I can play with nonproduction stuff. Great help whiteinge! Thanks.
01:21 whiteinge np. we'll be here :)
01:22 Jahkeup_ joined #salt
01:25 chadhs joined #salt
01:26 jhujhiti i've just got salt-master running from the freebsd port. i'm following the walkthrough and i'm at the "First SLS Formula" section. where do i put the sls files by default for this distribution? they're not being found in /srv/salt
01:26 jhujhiti running the master with debug logging, the only interesting thing i see is: loading module in ['/var/cache/salt/master/extmods/modules', but that looks wrong to me
01:29 aranhoide left #salt
01:30 jhujhiti ah, nevermind. it comes from the fileserver, so it's $PREFIX/etc/salt/states !
01:32 sciyoshi1 joined #salt
01:32 liuyq joined #salt
01:33 ajw0100 joined #salt
01:36 Jahkeup__ joined #salt
01:37 kenbolton joined #salt
01:39 alazylearner joined #salt
01:39 kmwhite joined #salt
01:40 mikedawson joined #salt
01:44 pweo joined #salt
01:51 dthom91 joined #salt
01:54 jaequery joined #salt
01:56 jalbretsen joined #salt
02:03 ipmb joined #salt
02:09 cxz how can i get a randomized mktmp()-style variable inside an SLS file?
02:23 alazylearner joined #salt
02:23 jefimenko joined #salt
02:23 Jahkeup_ joined #salt
02:31 jaequery joined #salt
02:32 james111 joined #salt
02:32 pweo joined #salt
02:33 chadhs joined #salt
02:34 fxhp http://russell.ballestrini.net/create-your-own-fleet-of-servers-with-digital-ocean-and-salt-cloud/
02:35 jensenja joined #salt
02:37 jensenja evening. I've been trying to search for a way to use salt to manage software that's built from source rather than via an OS' package management system
02:38 ipmb jensenja: I usually chain together a few states for that
02:39 dlawler left #salt
02:40 jensenja Started reading about states as a way to accomplish this (maybe I didn't read far enough) but I kept seeing references to a 'pkg' key
02:40 jensenja is this a requirement?
02:40 ipmb jensenja: here's an example https://dpaste.de/uTXNh/
02:40 jensenja or maybe I'm interpreting 'pkg' too literally
02:41 ipmb pkg is for your OS' package management system
02:41 ipmb jensenja: if you can build a package to distribute (even via Salt) you're probably better off though
02:42 ipmb dpkg, rpm, whatever
02:43 jensenja hum
02:46 jensenja well the packaging of something from source is definitely unfamiliar territory for me, but I suppose that is the easiest way to go about it
02:47 ipmb what OS are you using?
02:48 jensenja debian 7.1
02:48 dthom91 joined #salt
02:48 jensenja Going to have to start managing 16 route servers in the coming months - the build of quagga i'm using has to be compiled from source, but I believe BIRD does have deb packages available
02:51 ipmb jensenja: I think debhelper is your friend there
02:53 jensenja thanks - I'll have a look at that!
03:07 racooper joined #salt
03:09 Jahkeup_ joined #salt
03:14 bluemoon joined #salt
03:16 jacksontj joined #salt
03:19 Furao salt-cloud and digitalocean? :)
03:20 Furao I didn't saw a salt-cloud provider for it
03:20 Furao it's there but not in the doc?
03:21 Furao https://github.com/saltstack/salt-cloud/tree/master/saltcloud/clouds
03:21 Furao a lot more here https://github.com/saltstack/salt-cloud/tree/0.8.9/saltcloud/clouds
03:22 jbunting joined #salt
03:24 jacksontj_ joined #salt
03:28 pweo joined #salt
03:33 jaequery joined #salt
03:34 g3cko joined #salt
03:35 StDiluted joined #salt
03:45 jensenja left #salt
03:51 liuyq joined #salt
03:53 mchype joined #salt
03:53 redbeard2 joined #salt
03:57 rberger joined #salt
04:01 bluemoon joined #salt
04:07 Ryan_Lane joined #salt
04:13 oz_akan_ joined #salt
04:20 dthom91 joined #salt
04:28 cxz joined #salt
04:32 kleinishere joined #salt
04:46 scooby2 joined #salt
04:51 auser joined #salt
04:58 dthom91 joined #salt
05:01 liuyq joined #salt
05:02 liuyq joined #salt
05:09 rglauser joined #salt
05:19 x_or joined #salt
05:23 rberger joined #salt
05:27 Gifflen joined #salt
05:35 dthom91 joined #salt
05:37 linjan joined #salt
05:42 jkleckner joined #salt
05:45 alazylearner joined #salt
05:56 knightsamar joined #salt
06:06 jefimenko joined #salt
06:18 felixhummel joined #salt
06:34 rglauser joined #salt
06:50 vaxholm joined #salt
06:52 KyleG joined #salt
06:52 dthom91 joined #salt
06:53 ange how to update an install made using the bootstrap script ?
06:53 lahwran joined #salt
06:56 azbarcea joined #salt
06:56 Furao ange: install of what? the minion?
06:57 ange master and minion
06:57 Furao I have minion and master states
06:57 Furao so they upgrade themselves
06:57 carxwol_ joined #salt
06:57 ange run the script again could work I suppose
06:57 Furao but it can be tricky, in term of sequence. like you don't want to upgrade the master while minion run
06:58 hotbox joined #salt
06:58 ange I mean updating salt-master and salt-minion to 0.16 for example
06:58 travisfischer joined #salt
06:59 Furao apt-get update; apt-get upgrade
06:59 Furao apt-get install salt-minon
06:59 ange ..
07:00 ange 1. you know there is other things than apt based distro right ? 2. " an install made using the bootstrap script"
07:01 Furao I ignore others (especially centos), and even if you installed with bootstrap script, unless you specified you want it installed trough pip/git, it probably installed itself trough your local package manager
07:02 __gotcha joined #salt
07:02 __gotcha joined #salt
07:02 elbaschid joined #salt
07:03 ange Furao: yep my bad reading the script now, it adds a deb repo and install with it
07:04 jeddi joined #salt
07:07 ange arg have to wait
07:07 Furao .16 est pas encore packagé
07:09 ange why not stick to english ?
07:10 Furao many of those from france here speak a worst english than me :)
07:11 ange yep but many people here probably don't understand french
07:11 Furao at this time of the day it's very quiet anyway
07:13 schvin joined #salt
07:23 balboah joined #salt
07:24 bluemoon joined #salt
07:29 dthom91 joined #salt
07:34 ange Furao: thanks for the help
07:34 Newt[cz] joined #salt
07:34 krissaxton joined #salt
07:39 KyleG1 joined #salt
07:39 bluemoon joined #salt
07:40 isomorphic joined #salt
07:44 yumike joined #salt
07:46 krissaxton1 joined #salt
07:46 badmeischter joined #salt
07:56 auser joined #salt
08:08 bluemoon joined #salt
08:11 adotbrown joined #salt
08:14 p3rror joined #salt
08:28 krak3n` joined #salt
08:29 backjlack joined #salt
08:30 drdran joined #salt
08:36 __gotcha joined #salt
08:36 __gotcha joined #salt
08:41 Furao why pkg.list_pkgs return pkgs not installed?!?
08:42 Furao it return virtual pkgs
08:42 bluemoon joined #salt
08:44 krissaxton joined #salt
08:44 Jason-AVST joined #salt
08:53 basti_ joined #salt
09:00 mikedawson joined #salt
09:00 xerxas joined #salt
09:09 __gotcha joined #salt
09:11 carlos joined #salt
09:20 bluemoon joined #salt
09:33 oliv_mc joined #salt
09:34 dzen joined #salt
09:34 dzen moin'
09:44 JordanRinke Morning.
09:45 yota joined #salt
09:45 aleszoulek joined #salt
09:46 krissaxton joined #salt
09:48 hazzadous joined #salt
09:48 eduardoshanahan_ joined #salt
10:02 gzur joined #salt
10:13 oron joined #salt
10:14 oron I am a newbee in salt and wondering what's the best way to support multiple customers with it, we have several customers but want to deploy and orchestrate with one salt master, how can we seperate the sates to different repositories ?
10:17 oron ?
10:20 oron is there anyone here ?
10:28 Furao read the topic
10:29 Furao people are here 24/7 to wait for questions?
10:29 Furao salt master is not something that consume a lot of resource, maybe one per client is ok
10:29 Furao or you can have multiple environments
10:30 Nazca joined #salt
10:30 Nazca joined #salt
10:30 diegows joined #salt
10:30 fredvd joined #salt
10:30 ruimarinho joined #salt
10:31 ruimarinho hello.. is it possible to extend an sls file with a variable override?
10:31 ruimarinho sort of extend with { 'directory': /my/directory }
10:32 ruimarinho otherwise I have to extend and then iterate over each ID to override that property
10:33 Furao ruimarinho: pillars are there for that
10:34 Furao you can have a default directory and optional pillar to override it
10:34 Furao or you can include and extend
10:34 ruimarinho hmm, not exactly the same as far as I see it.. I'm probably not explaining it well enough
10:34 Furao but you won't be able to have the same .sls used multiple times
10:34 ruimarinho I have a cli.sls and a server.sls
10:35 ruimarinho both have their configuration file (config.cnf) but I want to apply the same set of sed rules to both
10:35 ruimarinho so I'm using a config.sls where I define those rules
10:35 ruimarinho and then I include config.sls on cli.sls and server.sls and extend the IDs
10:36 ruimarinho since the path is different -- /etc/mylib/cli/config.cnf and /etc/mylib/server/config.cnf
10:36 oron Fuaro
10:36 oron thx
10:36 ruimarinho so the path is variable, which is why I need to extend and then override each sed definition
10:37 ruimarinho is that necessary Furao?
10:37 Furao file.sed is a bad idea in first place. only file.managed is reliable.
10:37 Furao but you plan to be able to have both cli and server deployed at the same time?
10:37 Furao in a single state.highstate ?
10:37 ruimarinho yes, they are complementary and necessary
10:37 ruimarinho my init.sls includes both
10:37 Furao then you can't use include - extend
10:38 Furao because you'll end with a single definition of the config.sls
10:38 ruimarinho ah, it merges them at compile time
10:38 Furao kind of yes
10:38 Furao first it render jinja
10:38 Furao then resolve include
10:38 ruimarinho then my best chance is sharing a template?
10:38 Furao and create a big yaml
10:39 Furao yes that's the best, I do that all the time
10:39 Furao file.managed !
10:39 Furao sed == bad
10:39 ruimarinho I was already doing that way -- I just thought with 'sed' I would be able to mimick augeas' behaviour
10:39 Furao file.sed and file.comment is like doing bash over salt
10:39 ruimarinho right
10:39 Furao augeas ?
10:39 ruimarinho yes, salt supports it as a module, but not yet as a state
10:40 ruimarinho it's a configuration tool to replace bash-like tools such as awk, sed, etc
10:40 Furao ok
10:40 Furao sound horrible
10:40 ruimarinho it's built for this kind of setup
10:40 ruimarinho it isn't :)
10:40 Furao https://github.com/saltstack/salt/issues/4357
10:40 Furao once that will be fixed
10:40 Furao it will be so easy to create powerful extend of existing template or sls
10:41 ruimarinho yes, jinja is very powerful and it brings an extra juice to salt for sure
10:41 Furao or unreadable mess
10:42 ruimarinho the only issue I'm worried about is that managed templates are not future-proof
10:42 ruimarinho if a new release comes out with an updated configuration, you're out of luck
10:42 ruimarinho and if you only need to change one or two settings, file.managed is an unnecessary overhead
10:44 Furao I solved that by freezing version
10:44 Furao file.sed, file.comment and so on aren't future proof either
10:44 Furao what if new version switch from .ini style config file to XML?
10:44 Furao or file path change?
10:45 ruimarinho that is very unlikely in my opinion -- much more than a new setting being added to the configuration file
10:45 ruimarinho those are all breaking changes
10:45 Furao it's not true, what if you you upgrade FOSS 1.0 to 1.2
10:45 Furao you might ends with broken clustering
10:45 Furao because something change
10:46 Furao freezing version allowed me to also create a mirror  of all FOSS archives/deb/pip/whatever somewhere, installation are faster and survive to github/pip outage
10:46 Furao I have seen changes that broke upgrade for Elasticsearch, RabbitMQ
10:46 Furao and many others things I have to maintain
10:47 ruimarinho sure, there is always a risk, but as I see it, selectively changing one or two properties is less risky than completely managing a file when you really don't need it
10:47 Furao unplan upgrade are a nightmare
10:47 ruimarinho but of course, locking vendors is always the best solution if you don't want to run into upgrade troubles
10:48 Furao I spent weeks writing a testing tool for salt states and I was running each days, I found so many errors with new version of dependencies
10:48 Furao such as python-request that suddenly changed it's api
10:49 ruimarinho do you lock at the state level (pkg.version)?
10:50 Furao no, because repositories can't hold multiple version of the same package at the same time
10:50 Xeago joined #salt
10:50 Furao I use pkg.installed
10:50 Furao but that is for things that aren't in the distro official repositories
10:51 Furao that don't change except stability and  security fixes
10:51 Furao and for some repos I have complete mirrors
10:51 Furao mostly just PPA for PostgreSQL 9.2
10:51 ruimarinho alright, looks interesting
10:52 Furao and also salt itself :)
10:52 Furao after few disastrous new releases
10:52 Furao http://saltinwound.org/ubuntu/
10:52 Furao I should mirror 0.15.3
10:52 Furao before 0.16
10:53 adotbrown joined #salt
10:53 ruimarinho is 0.16 stable yet?
10:53 Furao not yet package
10:54 Furao d
10:54 ruimarinho the last release for wheezy is 0.15.90
10:54 ruimarinho alright
10:54 Jahkeup_ joined #salt
10:57 zooz joined #salt
11:00 krissaxton joined #salt
11:02 Furao here 0.15.3 is in mirror
11:05 jbunting joined #salt
11:06 adotbrown joined #salt
11:22 balboah joined #salt
11:23 waawal joined #salt
11:26 efixit joined #salt
11:32 waawal Hi, I'm trying to create a state for a application that uses a YAML-based configuration file that I would like to be able to manage with data from a pillar. What would be the smartest way to accomplish this?
11:32 adotbrown joined #salt
11:42 longdays joined #salt
11:46 blakearnold joined #salt
11:50 lothiraldan joined #salt
11:51 lothiraldan joined #salt
11:52 lothiraldan joined #salt
11:52 lothiraldan Hi
11:53 lothiraldan I think I've broken my salt-minion: https://novapaste.novapost.net/paste/1fb50272f1ca7383d95d1d4fc787eb859ef643f3#TmvKbSUKV6//TMG2PxxqiAfpH7sb03TbWxrKGQyFWqg=
11:55 lothiraldan joined #salt
11:57 lothiraldan_ joined #salt
11:58 lothiraldan_ Sorry, my client crashed
11:58 blakearnold_ joined #salt
11:58 lothiraldan_ I think I tried to run a state using an undefined pillar key and now I can't do anything from the master or the minion side to solve the problem
11:59 lothiraldan_ From the master: https://novapaste.novapost.net/paste/8425d50ef086e86a92b143d6ce5b2aab04a403e6#gVGV+XxwAIv1xCQxxJkMusnzRr0CILGkWW5oQwcRMV0=
12:01 lothiraldan_ I could not find a way to clean pillar data from the minion side, is anyone know how to do it?
12:04 cyp joined #salt
12:04 cyp hi
12:08 lothiraldan joined #salt
12:11 efixit joined #salt
12:13 linjan joined #salt
12:18 lemao joined #salt
12:18 kenbolton joined #salt
12:20 krissaxton joined #salt
12:25 erasmas joined #salt
12:26 lothiraldan I think I've found the bug
12:30 lothiraldan If you create an invalid pillar sls file, like "license_key = MY_LICENSE_KEY", salt-minion will generate exception
12:30 cron0 joined #salt
12:35 blee joined #salt
12:37 logix812 joined #salt
12:38 lothiraldan I've created an issue on github for describing the bug: https://github.com/saltstack/salt/issues/5910
12:38 lothiraldan By the way, salt is awesome, I'm deploying an elastic search cluster on rackspace in less than 24h
12:42 N-Mi joined #salt
12:43 brianhicks joined #salt
12:51 ipmb joined #salt
12:51 jbunting joined #salt
12:53 oz_akan_ joined #salt
12:55 mgw joined #salt
13:00 ninkotech joined #salt
13:02 Mrten joined #salt
13:04 juicer2 joined #salt
13:05 waawal lothiraldan: How do you render your pillars to elasticsearch.yml? Do you go by a jinja-template or have you been able to pull in the yaml directly from the pillar?
13:05 scott_w joined #salt
13:08 kermit joined #salt
13:08 Gifflen joined #salt
13:08 shiznit joined #salt
13:12 aat joined #salt
13:14 oz_akan_ joined #salt
13:16 alazylearner joined #salt
13:16 cwarner joined #salt
13:21 toto_ joined #salt
13:23 nickray joined #salt
13:24 Khollowa_ joined #salt
13:24 jslatts joined #salt
13:24 racooper joined #salt
13:28 shiznit joined #salt
13:29 redbeard2 joined #salt
13:32 jkleckner joined #salt
13:44 vaxholm joined #salt
13:49 kaptk2 joined #salt
13:49 racooper Trying to troubleshoot selinux state issue.  When running salt-call in debug I get the following output: [INFO    ] Executing command 'setsebool -P httpd_enable_homedirs None' in directory '/root'
13:50 racooper which obviously is an incorrect command.  The selinux.sls and output is here: http://pastebin.com/mP3cFGAk
14:03 Koma Hi all
14:04 rglauser joined #salt
14:04 rglauser left #salt
14:05 Koma what is the right way to check the dns/ntp configuration for a freebsd server with salt?
14:06 Koma all the information are stored on /etc/rc.conf
14:07 jbunting joined #salt
14:08 bhosmer joined #salt
14:11 vaxholm joined #salt
14:13 kho joined #salt
14:13 kho joined #salt
14:24 erasmas joined #salt
14:27 Koma what is the right way to check the dns/ntp configuration for a freebsd server with salt? all the information are stored on /etc/rc.conf
14:27 johntron joined #salt
14:27 scott_w joined #salt
14:28 Furao joined #salt
14:28 mgw joined #salt
14:30 johntron joined #salt
14:33 m_george|away joined #salt
14:33 m_george left #salt
14:36 hypyrdon joined #salt
14:37 bhosmer joined #salt
14:38 jacksontj joined #salt
14:39 lbotti joined #salt
14:46 StDiluted joined #salt
14:47 Johana joined #salt
14:49 mgw joined #salt
14:50 FreeSpencer joined #salt
14:55 whit joined #salt
14:55 krak3n` joined #salt
14:55 Ryan_Lane joined #salt
14:56 antsygeek joined #salt
14:56 salticus joined #salt
14:58 krak3n` joined #salt
14:59 rlb joined #salt
14:59 chrisgilmerproj joined #salt
15:03 rlb what's the correct way to install a package (providing a service), run a command after the pacakge is installed, and then restart the service?
15:03 Furao rlb: use service: - watch
15:03 Furao if something changed such as file, cmd.wait, or else
15:03 Furao it will restart the service for you
15:03 rlb I tried this:
15:03 rlb foo:
15:03 rlb pkg.installed:
15:03 rlb - fromrepo: sid
15:03 rlb some command:
15:03 rlb cmd:
15:03 rlb - run
15:04 rlb - require foo
15:04 rlb but I believe the syntax is wrong...
15:04 racooper rlb: pastebin might be easier
15:05 rlb racooper: ok, right -- and I got it wrong above anyway -- hang on.
15:08 rlb OK, here's my broken attempt: https://www.refheap.com/a4d1603c24d90cce8beac11ff
15:09 rlb Which causes the error 'The state "foo" in sls foo is not formed as a list'.
15:10 rlb I've just started looking at salt, so I'm almost certainly just "doing it wrong"...
15:11 rlb I'm wondering if it's a minor syntax issue, or if it's just a bad approach altogether.
15:11 rlb Furao: I'm not sure I want watch, since the command is a oneshot -- just needs to be run once after the initial package install to change the config.
15:12 Mrten cmd.run runs always
15:12 Mrten you want cmd.wait
15:12 bosszaru joined #salt
15:12 Furao rlb: then use cmd.wait: - watch: - foo: pkg
15:14 bosszaru how do I set a variable using a regexp against a grain in pillar I tried the following, but I don't seem to have the right idea  http://pastebin.com/52HMy51F
15:14 conan_the_destro joined #salt
15:14 rlb Furao: so more like this? https://www.refheap.com/a4d1603c24d90cce8beac11ff
15:15 racooper rlb, what about managing the config file from salt as well?
15:15 Furao line 4 is wrong
15:15 rlb racooper: it's not a config file -- the tool is the way to change the state
15:16 Furao rlb: check github.com/bclermont/states look around, checkout the repo and search for wait, watch, and require
15:16 Furao there is plenty of working examples there
15:18 backjlack joined #salt
15:18 rlb Furao: ok, I will, thanks.  What was wrong with line 4?
15:18 rlb (so I know)
15:18 Furao line 4 should be the value of -name: under line 5 statement
15:18 Furao and line 5 to the end should be unindented of 2 spaces each
15:19 koolhead17 joined #salt
15:20 LarsN Beyond state files and /etc/salt/* what other files on a salt master (also using salt-cloud) would be critical to recovering from a catastrophic failure of the master?
15:20 Furao check the git repo, you'll find a lot of cmd.wait example too
15:21 rlb Furao: ok, thanks -- I obviously need to learn the yaml syntax better.  I wasn't even sure if line 5 should exist, or if it should have just been cmd.wait:...
15:22 rlb i.e. does the command to run go before or after the "cmd.run", etc.  since "date: cmd.wait: -name: date" is a bit redundant (if that's even what you meant).  In any case, I'll go read a bit more.
15:23 Furao if -name isn't there salt take the state name as the - name argument
15:23 Furao but if you plan to - require: $modname: state-name
15:23 Furao keep it human readable
15:24 rlb Furao: ahh, ok, so I could have an arbitrary name for the state, and then put the actual command in -name -- if sp. that makes sense.
15:24 rlb s/sp./so/
15:24 Furao such as apache-server or foss-name instead of httpd-1.4.4
15:24 rlb (or vice versa)
15:24 conan_the_destro joined #salt
15:27 jschadlick1 joined #salt
15:28 _blakearnold joined #salt
15:30 Xeago_ joined #salt
15:33 chrisgilmerproj joined #salt
15:34 jschadlick1 so is 0.16.0 out?
15:35 dthom91 joined #salt
15:36 blakearnold joined #salt
15:37 zkrokovane left #salt
15:38 hypyrdon joined #salt
15:38 salticus jschadlick1: https://github.com/saltstack/salt/tree/v0.16.0
15:39 tomeff_ joined #salt
15:40 jschadlick1 right on, thanks :)
15:40 krissaxton joined #salt
15:40 hypyrdon joined #salt
15:41 hypyrdon left #salt
15:41 hypyrdon joined #salt
15:41 blakearnold_ joined #salt
15:41 conan_the_destro joined #salt
15:47 mlister2006 joined #salt
15:47 blakearnold joined #salt
15:48 mlister2006 salt gurus: I am trying to setup a pillar based on a subnet. https://gist.github.com/anonymous/5919594 (using mako here)
15:49 mlister2006 but looks like salt['network.in_subnet'] runs in a master context (i.e. checks salt master ip subnet and not a minion subnet).
15:50 mlister2006 probably intended that way, but is there another way to setup pillar value for minion based on its subnet association.
15:51 Furao mlister2006: pillar render in master
15:51 kermit joined #salt
15:52 rfgarcia joined #salt
15:54 Johana joined #salt
15:54 mlister2006 I guess I figured that out. (was confused with grains['id'] use in pillar files, but that is probably special case)
15:55 mlister2006 probably setting up grains value is a way to go I think?
15:58 alazylearner joined #salt
15:58 Furao why you don't juste salt['network.in_subnet'] in your state?
15:59 rfgarcia_ joined #salt
15:59 Furao instead of network.in_subnet -> grains -> state
15:59 Furao skip one step?
15:59 LarsN all this talk about Pillar, makes me think I'm doing it all wrong.
16:00 KyleG joined #salt
16:00 LarsN most of our magic is being done via grains, which we viewed as "metadata about instances"
16:01 EugeneKay The problem with grains is that they're only loaded at minion start time
16:01 EugeneKay And they're defined on the minion, not in a central place.
16:02 jdenning joined #salt
16:03 kenbolton joined #salt
16:07 mlister2006 Furao: pondering on using salt['network.in_subnet']  (and writing mako function to use in states for an ease of use), not a bad idea.
16:09 mlister2006 we don't want some minion to see all of our network information. (minion can pull any state file from salt server and see it all). so was thinking of using pillars(). if that is little safer to obfuscate all network level info
16:12 raulp left #salt
16:12 Johana joined #salt
16:13 pweo joined #salt
16:16 KyleG joined #salt
16:18 UtahDave joined #salt
16:18 mikedawson_ joined #salt
16:20 jacksontj joined #salt
16:22 racooper has anyone else seen issues with selinux states? I just entered this: https://github.com/saltstack/salt/issues/5912
16:25 fllr_ joined #salt
16:25 UtahDave racooper: I haven't used the selinux state at all.  Thanks for opening that issue!
16:25 fllr_ What is wrong with this sls file? https://gist.github.com/anonymous/5920071 I keep getting this error: The state "packages" in sls requirements is not formed as a list
16:25 erasmas joined #salt
16:27 UtahDave fllr_: try using - pkgs:   instead of names
16:28 UtahDave I commented on your gist, fllr_
16:28 racooper fllr_,   http://docs.saltstack.com/ref/states/all/salt.states.pkg.html has some examples of what you're trying to do.
16:29 carmony joined #salt
16:29 fllr_ s8#s8Now I'm getting this: Name packages in sls requirements is not a dictionary
16:32 fllr_ Nvm... I got it to work, it seems. :)
16:32 Johana left #salt
16:33 bhosmer joined #salt
16:33 fllr_ UtahDave: racooper: Thanks, guys! :D
16:34 carmony joined #salt
16:38 jefimenko joined #salt
16:39 jschadlick1 How should I go about getting 0.16.0 on debian wheezy? It doesn't seem to be in the debian repo yet.
16:41 Nazca joined #salt
16:41 Tuttle joined #salt
16:42 Tuttle hi. i'm new, just starting to learn whether salt can help me. and i'm optimistic. :)
16:42 UtahDave jschadlick1: Our main debian packager is out of town. I'll ping our backup packagers.
16:42 UtahDave welcome, Tuttle!
16:43 Tuttle 0.16 to /topic ?
16:44 Tuttle thanks
16:45 jschadlick1 UtahDave: thanks :)
16:45 joehh jschadlick1: doing it today - should be up in the next 24 hours
16:46 wifigi joined #salt
16:47 jschadlick1 joehh: thank you!
16:48 sciyoshi1 joined #salt
16:48 carmony joined #salt
16:48 wifigi Whenever I restart the salt-minion and salt-syndic, the one I restarted last will become the one seen by the root master
16:49 wifigi I'm trying to test out the salt-syndic functionality of Saltstack. Right now I have 3 nodes: a root master, a master, and a minion. The minion connects to the master, which connects to the root master. My problem is, I can only get the root master to see either the master or the minion (using test.ping to test), never both at once. The sub-master is also running a salt minion. It seems like the salt-minion and the salt-syndic are inter
16:49 chrisgilmerproj do you guys mind posting the debian build instructions so we can build in parallel?
16:49 wifigi (I have salt 15.3 on Ubuntu Server 12.04)
16:49 chrisgilmerproj I'd love to get going instead of waiting a couple hours for the next release
16:49 Topic for #salt is now Welcome to #salt - http://saltstack.org | 0.16.0 is the latest | Please be patient when asking questions as we are volunteers and may not have immediate answers - Channel logs are available at http://irclog.perlgeek.de/salt/
16:49 UtahDave thanks, Tuttle
16:49 UtahDave awesome, thanks, joehh!
16:49 Tuttle my first accepted pull request!
16:50 UtahDave congrats, Tuttle!
16:50 UtahDave wifigi: I think all the packaging stuff is in the repo.
16:51 chrisgilmerproj joehh: is it possible to run dpkg-buildpackage on the debian/ directory to get a valid deb file?
16:51 Tuttle i have a high-level question: is root access absolutely necassary for master and/or minion?
16:51 wifigi UtahDave: I think you meant someone else, my question wasn't about packaging
16:51 oz_akan__ joined #salt
16:52 teskew joined #salt
16:54 wifigi Does the salt-minion service interfere with the salt-syndic service on a master? And if so, is there any way to make a syndic master a minion as well?
16:54 aleszoulek Tuttle: Nope. It can run with dropped priviledges, but obviously you won't be able to do some of the actions :)
16:54 Tuttle cool
16:54 joehh chrisgilmerproj: yesish, the debian directory in the main git repo is used for the ubuntu packaging
16:55 chrisgilmerproj :)
16:55 chrisgilmerproj not confusing at all
16:55 chrisgilmerproj so i'm working with jschadlick1
16:55 Gifflen joined #salt
16:55 chrisgilmerproj we're hoping to get moving with the latest code
16:56 chrisgilmerproj i could just get the source package down from the repo and splice in the new code
16:56 joehh the debian packaging is maintained at http://wiki.debian.org/Teams/DebianSaltTeam
16:56 chrisgilmerproj but i'd rather follow some build procedure
16:56 joehh whoops - details of the packaging...
16:57 kenbolton joined #salt
16:57 Gifflen joined #salt
16:57 joehh if you don't have alioth ssh access, the repo is at http://anonscm.debian.org/git/pkg-salt/salt.git
16:57 chrisgilmerproj thanks
16:58 carmony joined #salt
16:59 joehh The work I'm doing before I upload is updating the init.d scripts - there are a couple of issues with these that need to get resolved
16:59 joehh the current ones work well enough, but are not perfect
17:01 chrisgilmerproj gotcha
17:02 backjlack joined #salt
17:02 chrisgilmerproj joehh:  in your opinion should we wait for that update or should we just get going on our own?
17:03 UtahDave wifigi: what version of Salt are you using?
17:03 joehh not sure where you are up to. If it is a "testing"/trial environment and you have skills/resources to manage versions of installed packages carefully then go for it now
17:03 joehh otherwise,wait a little
17:04 jacksontj joined #salt
17:05 Ryan_Lane joined #salt
17:06 chrisgilmerproj sounds good joehh, and thanks
17:06 chrisgilmerproj I think we'll wait till after lunch and see where things are
17:07 chrisgilmerproj but seriously, you've been super helpful
17:10 Ryan_Lane1 joined #salt
17:10 joehh chrisgilmerproj: not much will change here before your lunch - its 3am here - about to go to bed
17:10 Ryan_Lane joined #salt
17:10 chrisgilmerproj wow!
17:10 chrisgilmerproj 3am
17:10 chrisgilmerproj well thanks for staying up
17:10 chrisgilmerproj well thanks
17:10 chrisgilmerproj i appreciate the heads up
17:10 joehh chrisgilmerproj: no worries - up for other reasons :) and happened to notice this
17:11 joehh The packages for 0.16.0 as they are now are at http://jhh.no-ip.biz/salt/
17:12 joehh These have been built for unstable, but using the .dsc file should be easy to backport to wheezy
17:12 joehh If your comfortable with that then go for it, otherwise wait and they should be out overnight your time
17:12 Corey The PPA is also updated, for those Ubuntu flks.
17:14 jamiem joined #salt
17:18 joehh these aew "clean", no init.d changes
17:18 joehh s/aew/are/
17:18 jkleckner joined #salt
17:19 dave_den joined #salt
17:19 Tuttle left #salt
17:23 kenbolton joined #salt
17:24 efixit joined #salt
17:25 ruimarinho what's the best way to populate entire files via pillar data?
17:27 alazylearner joined #salt
17:31 UtahDave ruimarinho: use the - content variable in your file.managed state
17:32 jlund joined #salt
17:33 ruimarinho UtadDave, ok, I was using context and passing a variable ("content") for the template
17:34 dthom91 joined #salt
17:34 ruimarinho however, it seems that with "contents" salt has trouble reading multi-line data
17:34 wifigi UtahDave: I'm using Salt 15.3 - I said that in my original question (sorry for the delay, I went to lunch)
17:34 wifigi Repeat of question:I'm trying to test out the salt-syndic functionality of Saltstack. Right now I have 3 nodes: a root master, a master, and a minion. The minion connects to the master, which connects to the root master. My problem is, I can only get the root master to see either the master or the minion (using test.ping to test), never both at once. The sub-master is also running a salt minion. It seems like the salt-minion and the sa
17:35 whit joined #salt
17:36 ruimarinho UtahDave, here's a basic example of what I'd like to do: http://pastebin.com/NEhDZRg9
17:38 jalbretsen joined #salt
17:41 ruimarinho quoting the whole configuration works, but the output does not respect new lines
17:42 Furao joined #salt
17:43 jeddi Could someone pelase point me at a good example of just picking up an integer from pilllar for a given host, and then using that in a state file to loop with jinja?   I thought it'd be really easy, but the structure is throwing me.
17:45 TheSojourner joined #salt
17:45 TheSojourner joined #salt
17:45 herlo joined #salt
17:47 Gareth joined #salt
17:51 aranhoide joined #salt
17:51 jacksontj joined #salt
17:52 jefimenko joined #salt
17:58 TheRealBill jeddi: here is how to do the second half using range in Jinja: http://stackoverflow.com/questions/13897001/how-to-simulate-while-loop-in-jinja2
17:58 KennethWilke joined #salt
17:58 fxdgear joined #salt
17:58 TheRealBill the first half of your question should jsu tbe a standard pillar variable retrieval. In fact, I think I have something I can gist for you, gimme a moment to pull it up.
17:59 jeddi TheRealBill: thanks!  i think i'm possibly getting mucked around by poor understanding of scope.  and whether i can use a grains[] item as a key to a pillar_get
18:00 TheRealBill Here I am doing it off of grains but the structure should be the same. swap out the grains with pillar call and it should work: {% for port in range( grains['num_cpus']*4  ) %}
18:00 TheRealBill hmm that's a good question, I'm not sure if you can nest those either. UtahDave: can you use a grain in a pillat call?
18:01 azbarcea furao
18:01 KennethWilke TheRealBill: yar, you can
18:01 TheRealBill KennethWilke: nice
18:01 jeddi let me de-uglify the stuff i have here so it's relatively acceptable to push onto pastebin.
18:05 ruimarinho any idea how I can preserve newlines with jinja when passing file.managed contents as {{ variable }}?
18:06 KennethWilke ruimarinho: yeah, i know there's a doc in the jinja docs about that i can find for you
18:06 KennethWilke ruimarinho: http://jinja.pocoo.org/docs/templates/#whitespace-control
18:07 toastedpenguin joined #salt
18:07 ruimarinho not exactly that KennethWilke
18:07 ruimarinho because this is managed by salt itself
18:07 ruimarinho - contents: {{ project.configuration }}
18:07 ruimarinho project.configuration is a multiline string retrieved from pillar
18:08 ruimarinho yet salt/jinja renders the output without respecting newlines
18:08 berto- joined #salt
18:08 KennethWilke hmm, it may be a filtering thing then
18:09 KennethWilke but you may just need to quote the string
18:09 KennethWilke is the template rendering? or are the newlines causing errors?
18:10 ruimarinho the template renders fine, but without newlines.. the salt states correctly presents the diff with the file content I want, exception without newlines
18:10 ruimarinho +server { listen 80; listen 443 ssl;
18:10 ruimarinho already tried quoting the project.configuration multiline property
18:10 auser joined #salt
18:11 KennethWilke hmm, i'm not sure, typically in this situation i put the file in the state and reference it with salt://state/filename
18:12 ruimarinho me too..but since it's project-specific, I'd like to avoid mixing it with states
18:12 cron0 joined #salt
18:13 KennethWilke ah okay, someone else may know a good way to handle things that way, but i'm not familiar with that myself
18:13 ruimarinho I'll keep exploring, thanks for the help!
18:13 KennethWilke you're welcome, good luck!
18:16 UtahDave wifigi: There were some known deficiencies with the syndic in 0.15.x that have been fixed in 0.16.0.   Can you try upgrading and testing against that?
18:18 UtahDave ruimarinho: can you pastebin the part of your pillar where you set the contents?
18:18 UtahDave sorry, I just got back from a meeting and lunch
18:19 wifigi UtahDave: I was afraid of that...I will try it, but I can't do it quickly, as I have to talk our sysadmin into upgrading the local repository packages again
18:19 ruimarinho UtahDave: http://pastebin.com/85vVbqPd
18:19 wifigi UtahDave/anyone else: Where is the official place to get Ubuntu SaltStack builds? I see lots of different sites for it
18:20 UtahDave wifigi: Yeah, there were some subtle synchronous issues that were ironed out.
18:20 hazzadous joined #salt
18:20 UtahDave wifigi: there's an official ppa
18:20 UtahDave wifigi: sudo add-apt-repository ppa:saltstack/salt
18:20 rberger joined #salt
18:20 linjan_ joined #salt
18:20 wifigi Can't do that, no internet on the boxes
18:21 wifigi The only machines I have on the internet right now are Windows
18:21 ruimarinho UtahDave: file.managed part - http://pastebin.com/fAYXyGeK
18:24 ruimarinho I have to run, I'll check in with you later
18:24 UtahDave ruimarinho: try this: http://pastebin.com/zY6qqLKd
18:25 ruimarinho UtahDave, will try and let you know.. thanks for the feedback
18:25 erasmas_ joined #salt
18:25 UtahDave you're welcome. good luck, ruimarinho
18:26 mgw wifigi: you can download them from the ppa also
18:26 x_or joined #salt
18:27 mgw wifigi: https://launchpad.net/~saltstack/+archive/salt
18:29 Kamal_ I don't think I should run salt highstate on a cronjob
18:30 UtahDave Kamal_: Salt won't stop you.  :)
18:30 UtahDave Kamal_: are you having some issues with that?
18:30 Kamal_ Not at all. I just feel it's unnecessary
18:30 Kamal_ :]
18:32 JasonSwindle joined #salt
18:32 UtahDave I prefer running a highstate when I purposely need to.
18:32 Ryan_Lane joined #salt
18:32 Kamal_ Yeah, I had the cronjob set when I first started getting my hands dirty with saltstack
18:33 Kamal_ I believe I had it because my nginx state makes sure nginx is running
18:35 Newt[cz] joined #salt
18:36 bauser joined #salt
18:37 kermit joined #salt
18:38 hypyrdon_ joined #salt
18:38 dthom91 joined #salt
18:44 kleinishere joined #salt
18:45 bhosmer joined #salt
18:55 kenbolton joined #salt
18:57 blakearnold_ joined #salt
19:00 f4cl3y joined #salt
19:01 whit joined #salt
19:03 tethra joined #salt
19:04 tethra just set up >10 VPSs with salt after picking it up an hour or two ago. dear salt developers: jolly well done.
19:04 * tethra -> lurking mode
19:05 KyleG tis' nice, isn't it
19:05 tethra it really is
19:06 johntron joined #salt
19:06 tethra i'm going to try managing a riak cluster with it later i think
19:06 Gifflen joined #salt
19:06 tethra that should be fun, although i'm sure pretty much everyone i know with a pulse will write me off as a hipster if i mention it \o/
19:08 steveoliver I'm new to salt, infra management, monitoring, etc.  I need to setup a monitoring system and eventually build out infrastructure.  i've started studying nagios, just found opennms and now I've discovered salt.   I know salt will be at the center of it all — should I bother learning/configuring nagios or opennms, or stick with what monitoring functionality is within salt and its modules?
19:08 jeddi steveoliver: you still need something to monitor your systems - capacity, performance, etc.  salt doesn't do that.
19:08 steveoliver k
19:09 steveoliver looks like it's between opennms and nagios, is that about right?
19:09 jeddi steveoliver: also - most of the peeps around here recommend you look at shinken and/or icinga in preference to nagios.  not sure if that's just lots of personal preferences, but worth considerign.
19:09 steveoliver ok
19:09 steveoliver jeddi++
19:09 steveoliver thx
19:09 tethra yeah, icinga is nicer than nagios
19:09 steveoliver icinga, ok
19:09 jeddi steveoliver: ObDisclaimer - i used nagios for years, then moved to zabbix for a few years, and am probably about to crank up shinken on the next project.
19:09 jeddi or icinga. :)
19:10 steveoliver jeddi May I ask Why?
19:10 tethra i declare an interest here: i work with a different piece of monitoring software called Mauve - it isn't widely used but it does a cracking job and is much lighter weight and so on than others. IMO.
19:10 jeddi steveoliver: nagios used to make my toes curl.  and not in a good way.  but .. i'll have to evaluate all three before proceeding.   it's been about 8 years since i touched anything nagios-like.
19:10 kermit joined #salt
19:11 jeddi steveoliver: there *may* be some benefit in seeing what recipes / state files are already out there for plugging into monitoring systems with salt.  though i haven't seen much on this front.
19:11 steveoliver nagios sounds like it's been around a while and has some large community mass around it
19:11 tethra icinga = nagios but "better" (improved UI, can use the same checks, various other improvements) fyi :)
19:11 tethra 'tis a fork
19:12 jeddi steveoliver:  there's lots of this kind of propaganda out there -- http://www.shinken-monitoring.org/what-is-in-shinken-not-in-nagios-and-vice-versa/
19:12 jeddi naturally you really need to do a functionality assessment between the products that are there.
19:12 steveoliver functionality-wise I'm mainly dealing with web servers
19:13 steveoliver standard fare stuff, I'd imagine
19:13 * steveoliver has some homework to do.   heads in the direction of icinga first
19:13 jacksontj joined #salt
19:14 KyleG OMDistro
19:14 KyleG yummyness
19:14 KyleG http://omdistro.org/
19:14 KyleG has basically everything in one easy-to-install package
19:15 KyleG check_mk is awesome, and has been very good to us
19:15 kenbolton joined #salt
19:15 steveoliver authentication and control groups in icinga look winning
19:15 KyleG With check_mk+pnp4nagios which is built in, it's really cool to be able to get rid of cacti and have all my metrics in my monitoring tool, so when I pull up the firewall in check_mk I can also view the network interface graphs
19:16 johnsocp joined #salt
19:16 jeddi KyleG: that looks really quite neat .. if somewhat overkill :)
19:16 KyleG jeddi: I only use what I need with it :P
19:16 * steveoliver doesn't want overkill … wants to start small and stay granular
19:20 jacksontj joined #salt
19:26 tethra_ joined #salt
19:28 bhosmer joined #salt
19:28 Corey luminous: SHENANIGANS!
19:29 derelm joined #salt
19:30 bluemoon joined #salt
19:31 dthom91 joined #salt
19:33 canci_ is there a common best practice how one implements tests for custom state modules?
19:34 kleinishere joined #salt
19:36 madduck UtahDave: do you have a second? Do you know or could you ask Tom what this is for? https://github.com/saltstack/salt/blob/develop/salt/master.py#L818-L820
19:37 madduck UtahDave: the reason I ask is because self.tops seems to be loaded from opts['master_tops'] in loader.tops anyway, so checking for membership at each iteration seems a lost cause, a tautology. Or what are you trying to guard against? What could be in self.opts that wouldn't be in master_tops?
19:41 jeddi I was sure there's a way you can say (in a state file) 'if this grain doesn't exist for this host ... don't just crash' .. ?
19:42 jeddi i can see 'default' as a parameter to the modules.grains.get - but can't see how to flip that into a jinja if test.
19:42 rberger joined #salt
19:45 madduck jeddi: {{ grains.foobar | default 'Moo!' }}
19:45 madduck or default('Moo'), not entirely sure right now
19:45 madduck see jinja docs, list of defined filters, default
19:45 alazylearner joined #salt
19:46 wifigi joined #salt
19:46 kleinishere joined #salt
19:47 wifigi I'm back with the same problem I had earlier: I have a root master, a sub master running salt-syndic and salt-minion, and a minion connected to the sub master. When running test.ping from the root master, I can only get the sub master OR the minion to respond - never both at once. I am using salt 0.16 (upgrading from 0.15.3 didn't help)
19:48 wifigi Running the salt-syndic and salt-minion in debug shows that either one or the other doesn't receive the ping command
19:48 wifigi (which one gets it depends on which one was started most recently)
19:55 scottvdp joined #salt
19:57 kleinishere joined #salt
19:59 jeddi madduck: thanks so much!  taa.
20:02 kleinishere joined #salt
20:02 Jonathan_____ joined #salt
20:03 Jonathan_____ is there anyone out there?
20:04 racooper well I just found something fun and useful. is there any documentation that a custom state modules overrides a "default" module of the same name?
20:05 terminalmage racooper: I do not know
20:05 terminalmage I've never tested that
20:06 terminalmage did it override?
20:06 terminalmage or was it ignored?
20:06 racooper well, it appears to be the case that custom states modules do override defaults.  still testing but it looks that way.
20:06 terminalmage ahh
20:07 terminalmage don't you love it when people pop into IRC, ask if anyone is there, then leave?
20:07 rk___ joined #salt
20:07 terminalmage if you have a question, ask the question
20:08 terminalmage I don't get the need to have your presence acknowledged first
20:08 racooper there seems to be an expectation of instant gratification
20:08 wifigi Or some of us ask a question and then wait 20 minutes for an answer
20:08 wifigi Then ask I again, I guess
20:08 wifigi *it
20:09 terminalmage the channel topic says it all
20:09 EugeneKay Yes, I do love it.
20:09 berto- joined #salt
20:09 EugeneKay It usually means they'll be calling me up shortly, and that I can bill them for.
20:09 terminalmage if you have a question that is not being answered, the mailing list is your best bet
20:10 wifigi What if the mailing list sent me here?
20:10 racooper then you're caught in an infinite loop :P
20:10 terminalmage haha
20:10 wifigi So it would seem, haha
20:10 wifigi I will probably do both again just to be safe
20:10 kleinishere joined #salt
20:10 terminalmage the mailing list just has a persistence that IRC doesn't
20:11 terminalmage unless you go back and look at the logs
20:11 diegows joined #salt
20:11 EugeneKay Mailing lists have the unfortunate property of lag
20:11 terminalmage also, there are people that are rarely active in IRC, like myself
20:11 wifigi pros and cons
20:12 jschadlick joined #salt
20:12 terminalmage Instant gratification is what Salt Stack Enterprise is for ;)
20:12 EugeneKay See above re: phone calls
20:13 terminalmage :)
20:13 wifigi Yeah, I know. My use is mostly experimental though, and it wouldn't be very gratifying if I had to pay for it.
20:13 wifigi Plus I hate dealing with licenses
20:13 racooper is there a way to test if a selinux boolean is persistent?
20:14 terminalmage racooper: there's an selinux execution module
20:14 terminalmage you could probably get the information from that
20:15 terminalmage selinux.getsebool someboolean
20:15 terminalmage I don't have a machine running selinux to test unfortunately
20:15 racooper ah, getsebool does return the default status.  I had forgotten.
20:15 terminalmage ahh cool
20:15 racooper because running getsebool at command line only returns the current state; the salt module gives more info
20:16 EugeneKay What an unfortunately named command. o.O
20:16 racooper sounds like "gets evil" :p
20:16 terminalmage :)
20:17 EugeneKay I saw "goatse bowl", which I do not recommend googling.
20:17 racooper I've read slashdot long enough to know better...
20:20 spmurray joined #salt
20:20 akoumjian Is it possible to do a negative match in top matching? Something like 'not G@env:dev'
20:20 akoumjian nevermind, just saw it
20:23 spmurray When building custom modules, can the environment of the minion be identified in the module itself?
20:25 erasmas_ joined #salt
20:28 terminalmage spmurray: the env should always be available as __env__
20:29 spmurray ah great, thanks terminalmage
20:29 terminalmage I think...
20:29 terminalmage lemme check
20:29 spmurray about to test
20:29 terminalmage spmurray: it looks like states pass the env to modules in the kwargs
20:30 spmurray there a doc I can reference? having trouble finding any notes about
20:30 spmurray about it*
20:30 terminalmage yeah I don't know
20:30 spmurray hmm, ill keep hacking and see what I can find
20:31 terminalmage spmurray: I just recall fixing a bug with pkg states, where installing binary packages wasn't respecting the env
20:31 dthom91 joined #salt
20:31 terminalmage and the env was in the **kwargs
20:32 madduck terminalmage: #5926
20:32 terminalmage spmurray: https://github.com/saltstack/salt/blob/develop/salt/modules/pkg_resource.py#L263
20:33 spmurray awesome! thanks terminalmage
20:33 alekibango joined #salt
20:33 terminalmage spmurray: np
20:33 terminalmage thanks madduck
20:39 madduck terminalmage: thanks for alerting me so promptly. we are quits ;)
20:40 Drone[02] joined #salt
20:41 Bastion2202 joined #salt
20:42 toastedpenguin joined #salt
20:42 teskew joined #salt
20:42 conan_the_destro joined #salt
20:42 ipmb joined #salt
20:42 blee joined #salt
20:42 rizumu joined #salt
20:43 Corey madduck: Pardon the snark in my email just now. :-)
20:43 Corey I so rarely get to make a joke about the codebase.
20:43 rcg_re joined #salt
20:43 Bastion2202 hey guys, for ssh pub key. is adding the pub key file in a pseudo FS salt:// and get them using source is the way to go or hardcoding it in a pillar is better. remember I am only talking about the pub key.
20:44 Corey Bastion2202: Doesn't really matter either way.
20:44 terminalmage madduck: no prob, it was someone else that discovered the problem in the first place
20:44 Corey Bastion2202: I've stored my pub key in DNS txt records, on web servers, etc.
20:44 Corey Bastion2202: What's your github username?
20:44 rcg_re joined #salt
20:45 Bastion2202 Corey: bastion2202
20:46 Corey Bastion2202: You don't have ssh keys in your profile on github?
20:46 Corey https://github.com/bastion2202.keys comes up blank, is why I ask. :-)
20:46 Corey But yeah, if you add a pubkey to github, it becomes world readable.
20:47 carmony joined #salt
20:48 Bastion2202 Corey: tx I will use the source method. tx
20:48 Corey Bastion2202: No worries. Good luck. :-)
20:52 herlo joined #salt
20:52 mgw has anyone seen this?
20:52 mgw [CRITICAL] Failed to load grains defined in grain file opts.opts in function <function opts at 0x24d7398>, error:
20:52 mgw Traceback (most recent call last):…. AttributeError: 'str' object has no attribute 'get'
20:53 jschadlick joined #salt
20:53 isomorphic joined #salt
20:55 thingles joined #salt
20:55 thingles quick question, I'm diving into Salt for the first time. Does the salt-master run both master and minion? I assume it needs to have minion as well so you can manage the master itself?
20:56 * thingles is Salt n00b
20:57 racooper thingles,  have you gone through the tutorial yet?
20:57 Corey thingles: If you want to manage the master itself, it will need the minion, yes.
20:57 Corey Otherwise it will not;
20:57 thingles have gone through some writeups...
20:58 thingles Corey: thanks..
20:58 * madduck whacks Corey over the head with a large trout [http://stuff.madduck.net/pub/misc/fun/trout.jpg].
20:58 madduck (for msgid:<77B40B75-27C2-451A-BD04-F9485C5864E9@sequestered.net>)
20:58 madduck you don't deserve better.
20:58 madduck ;)
20:59 Corey madduck: Oh, I'm just having some casual fun [http://www.sequestered.net/~cquinn/casual.gif]
20:59 madduck AN ANIMATED GIF?
20:59 madduck honestly, I don't know whether I have enough punishment in my IRC client /alias list for that
20:59 Corey In 2013, you say?!
20:59 * madduck checks
21:00 luminous Corey: O.o
21:01 luminous what kinda shennanigans, eh?
21:01 madduck Corey: i am surprised that clients nowadays even still support that stuff, and <blink>
21:01 Corey luminous: "I'm certainly not ok with smtp, I don't believe any of us should be using it. Particularly after the disclosures of the last two months."
21:01 Corey madduck: Oh, my IRC client does not.
21:01 madduck but because i now have a new GIF to add to my "stuff": http://stuff.madduck.net/pub/misc/fun/1000000.swf
21:02 Corey It needs opening in a browser.
21:02 madduck i meant web clients.
21:02 luminous Corey: ...and?
21:03 Corey luminous: SMTP isn't the problem there.
21:03 luminous um... the protocol is pretty terrible, and outdated for todays needs
21:04 luminous it's too easily exploited if you have access to the pipesa
21:07 whit joined #salt
21:08 Corey luminous: STARTTLS offers some mitigation around that, particularly if you mandate it.
21:08 godog joined #salt
21:10 dthom91 joined #salt
21:11 Ryan_Lane joined #salt
21:13 akoumjian Actually, having some trouble with using the 'not' parameter in a compound match. If I'm trying to ping all the servers that do not have a value of 'stage' for the 'env' grain, how would I do this?
21:13 akoumjian This is what I've been trying: sudo salt -C 'not G@env:stage' test.ping
21:13 racooper I think you have to use '* and not....'
21:14 akoumjian racooper: Yep, you are right. That makes sense.
21:14 akoumjian racooper: thank you kindly
21:15 _dan__ joined #salt
21:16 racooper http://docs.saltstack.com/topics/targeting/compound.html for future reference :)
21:16 luminous Corey: I'll agree to disagree :)
21:16 ahammond looks like the "ret" issue is back for publish.publish.
21:20 scottvdp joined #salt
21:22 kleinishere joined #salt
21:23 f4cl3y joined #salt
21:26 ahammond UtahDave: so, this got fixed shortly after 15.1 got released, but has reappeared. I'll see if I can find the commit that fixed it.
21:26 UtahDave OK, I'm back from a long meeting.
21:29 ahammond UtahDave: so… looks like 16.0 fixed my long-standing publish.publish issue! Horray!!!
21:30 ahammond UtahDave: but may have re-introduced the "oops, 'ret' is in the returned values" bug from a while back.
21:31 ahammond (which is easy to work around, but… fugly)
21:31 ipmb how do I handle a situation where one state wants to install `cron.file` and another wants to do `cron.present`?
21:31 ipmb cron.file always seems to win and I don't see cron.present
21:31 efixit1 joined #salt
21:32 jacksontj joined #salt
21:37 UtahDave ahammond: can you document that regression?
21:37 ahammond UtahDave: is the return format for publish.publish supposed to be substantially different?
21:37 UtahDave ahammond: I'm not sure exactly. Are you seeing big changes?
21:38 ahammond UtahDave: yeah, instead of just the data I'd expect, I'm getting it layered pretty deeply
21:38 UtahDave ipmb: you can only have one function from a specific state under a single ID declaration
21:38 ipmb UtahDave: different IDs
21:38 UtahDave ipmb: if you need to use two different cron state functions, then you'll need to split them out to separate ID declarations
21:38 UtahDave ipmb: Hm. Could you pastebin what you have?
21:38 ahammond so, when I call sudo salt-call publish.publish foo grains.item datacenter, I'd expect foo: { datacenter:  bar }
21:39 ahammond instead, I'm getting foo: { out: grains, ret: { datacenter: bar } }
21:41 ipmb UtahDave: https://dpaste.de/DsvHa/
21:41 UtahDave ahammond: Hm. I'm not sure if that's expected or not. Go ahead and open an issue on the change and I'll track down whether or not that was expected
21:41 ipmb backup_databases runs, then root_crontab runs
21:41 ahammond UtahDave: will do.
21:41 ipmb root_crontab overwrites backup_databases (I assume)
21:42 UtahDave try having backup_databases require root_crontab.  You'll have to include state1.sls in state0.sls
21:42 UtahDave thanks, ahammond!
21:46 ipmb UtahDave: could I do a require_in instead?
21:46 UtahDave ipmb: sure, that's just coming from the other direction.
21:46 ipmb backup_databases is used on many servers, root_crontab on just one
21:48 ahammond UtahDave: https://github.com/saltstack/salt/issues/5928
21:49 UtahDave perfect, thanks, ahammond
21:49 bhosmer joined #salt
21:49 ahammond UtahDave: this breaks the majority of the stuff I've written that uses publish.publish, so… if it's the new way going forward, I'll update my code.
21:51 UtahDave I'm guessing that it was an inadvertent change, but I'm not 100% sure.
21:51 UtahDave I'll have to check with a dev when he gets off an airplane tonight
21:51 ahammond UtahDave: ok, thanks. :)
21:51 UtahDave you're welcome.
21:54 ruimarinho joined #salt
21:55 dthom91 joined #salt
21:58 jacksontj joined #salt
21:58 TheRealBill does salt have a python module named 'redis' by any chance?
21:59 ahammond TheRealBill: what do you want to do?
21:59 ahammond because… I've written a salt stat that will install redis for you.
22:00 ahammond TheRealBill: https://github.com/SmartReceipt/salt_redis/
22:00 jeddi pkg.installed redis? ;)
22:00 ruimarinho UtahDave: I wasn't able to run it like http://pastebin.com/zY6qqLKd
22:00 TheRealBill oh i've writen a neat one of those, ahammond. What I am running into is I am writing a redis module for gathering data, but in the module after importing redis I get an error on there being no Redis attribute in the module.
22:00 TheRealBill I'm writign a module to interface with redis on the minion
22:01 ruimarinho I had to change to http://pastebin.com/Dms4eeA6, but the indentation filter does not seem to have had any effect
22:01 ahammond TheRealBill: that sounds pretty cool!
22:02 TheRealBill ahammond: I am doing a *lot* of Redis work these days. And given the clusters I am working on I'm going to want^W need the interface with it in Salt. :)
22:02 ahammond TheRealBill: we have just a little redis here and I'd like to have more, so I'm interested.
22:04 ruimarinho UtahDave: found a way to make it work :) awesome.
22:04 TheRealBill but the pyredis module installs as redis ('import redis') and it *looks* like Salt has it's own python module somewhere in the path becuase the __dict__ doesn't match.
22:05 rlb I know I can write something, but is there a built in way to have the master delete keys for minions that have "died", for example, that you haven't been able to ping for N minutes or similar?
22:06 backjlack joined #salt
22:08 Corey TheRealBill, ahammond: I'm not such a fan of redis personally. Not that you care. :-)
22:08 Corey Redis + AWS = fail, generally.
22:09 carmony :O
22:09 * carmony hugs his redis.
22:09 carmony though I haven't ran it on AWS before
22:10 TheRealBill Corey: there is a particular problem in that formula: AWS. ;)
22:10 Corey TheRealBill: Technically, "Xen" was the problematic part.
22:10 TheRealBill yeah probably. But Redis in a VM is generally much less nice than on a physical machine.
22:11 EugeneKay What's the particular problem with Xen+Redis? It works fine for me on Linode.
22:12 TheRealBill EugeneKay: how large is your dataset?
22:12 EugeneKay We're just using it for in-memory caching, ~5GB right now.
22:13 TheRealBill so you'd probably be fine, overall. ;)
22:13 Corey EugeneKay: Disk persistence calls fork.
22:13 mgw joined #salt
22:13 Corey EugeneKay: Fork on Xen is 1-2 orders of magnitude slower than on other virt platforms, or bare metal.
22:13 TheRealBill with large datasets and disk persistence you can see serious suckage on VMs
22:13 EugeneKay Ah, well we don't have that, at all.
22:13 EugeneKay In-memory yay :-p
22:13 Corey http://railsmachine.com/articles/2012/10/22/red-is-alert <-- Explains it better
22:14 TheRealBill EugeneKay: it is what Redis is primarily designed for. ;)
22:14 EugeneKay I believe it, I was just curious.
22:14 EugeneKay I won't worry about hitting that ceiling
22:15 necronian joined #salt
22:16 KennethWilke joined #salt
22:17 necronian joined #salt
22:18 oz_akan_ joined #salt
22:20 jkleckner joined #salt
22:27 Gifflen joined #salt
22:27 TheRealBill curious. I don't see the problem when using salt-call on the minion, only when running via the master.
22:33 mgw joined #salt
22:35 mgw1 joined #salt
22:37 redbeard2 joined #salt
22:41 KennethWilke joined #salt
22:41 adotbrown joined #salt
22:43 ajw0100 joined #salt
22:47 mgw joined #salt
22:49 kermit joined #salt
23:00 spmurray does the salttesting module exist in the git repo?
23:00 jacksontj joined #salt
23:08 spmurray nvm, just found the other repo (https://github.com/saltstack/salt-testing)
23:08 jschadlick left #salt
23:19 mgw joined #salt
23:19 StDiluted joined #salt
23:20 adotbrown joined #salt
23:23 copec joined #salt
23:24 copec joined #salt
23:25 copec joined #salt
23:26 copec joined #salt
23:26 copec joined #salt
23:28 copec joined #salt
23:28 copec joined #salt
23:29 copec joined #salt
23:39 dthom91 joined #salt
23:39 stevejohnson joined #salt
23:40 stevejohnson is there a way to deploy a git branch other than master? (I didn't set up this deploy, wondering if there's a command line arg to state.highstate or something)
23:40 stevejohnson (*didn't set up this config)
23:41 UtahDave stevejohnson: yeah, there's an option to specify the branch or tag you want
23:42 cxz joined #salt
23:43 stevejohnson I'm having a tough time finding anything useful on google, UtahDave
23:44 UtahDave stevejohnson: http://docs.saltstack.com/ref/states/all/salt.states.git.html#salt.states.git.latest      "rev" is the option you want
23:45 stevejohnson looks like I can just pass that on the command line with 'salt.call state.highstate rev=blah'?
23:45 martineg_ joined #salt
23:46 basepi joined #salt
23:46 stevejohnson ...nope
23:46 UtahDave stevejohnson: no, it needs to be in your state where you define it
23:46 Micromus_ joined #salt
23:48 xt joined #salt
23:52 jalbretsen joined #salt
23:55 jalbretsen *SIGH*
23:56 jalbretsen opps, wrong window :)

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