Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-03-07

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

All times shown according to UTC.

Time Nick Message
00:01 meteorfox joined #salt
00:06 rojem joined #salt
00:12 Ryan_Lane will autoscale groups be supported by salt-cloud at any point?
00:13 Ryan_Lane also, is it possible to put salt-cloud config info into pillars, rather than making files?
00:13 faldridge joined #salt
00:14 Ryan_Lane and is it possible to call salt-cloud from salt modules?
00:15 ndrei joined #salt
00:16 rojem joined #salt
00:17 rojem joined #salt
00:18 krow joined #salt
00:27 dyim joined #salt
00:28 manfred Ryan_Lane: the cloud modules calls the salt-cloud client
00:28 manfred https://github.com/saltstack/salt/blob/develop/salt/modules/cloud.py#L35
00:28 Ryan_Lane yeah, i don't want to use salt-cloud client
00:29 Ryan_Lane ah
00:29 manfred no, it calls the salt.cloud.CloudClient() similar to how you would call salt.client.LocalClient()
00:29 Ryan_Lane it's a python api
00:29 Ryan_Lane I see
00:29 themadcanudist left #salt
00:29 manfred so the plan is
00:29 manfred you setup your providers and profiles
00:30 manfred then you can use the cloud state, and it will call the cloud modules, and then you are portable across multiple providers
00:30 Ryan_Lane I really don't want to manage the providers and profiles via the config files. it would be ideal to use pillars for that
00:30 Ryan_Lane I have a very strong use case for that
00:31 joehoyle joined #salt
00:31 manfred once it is in the cloud state, you could manage it from there, using cloud.present?  well you cold manage the profile there, you still need something for the provider
00:31 manfred (expect the nova one manages them in the keystone.<w/e> pillar data)
00:31 lionel joined #salt
00:32 manfred so, it might be coming to the other ones
00:33 manfred I am actually working on stripping apart the salt/cloud/clouds/nova.py right now, in hopes to tie it all together with a specific library to add volume_create and volume_attach to the cloud state right now.
00:33 Ryan_Lane heh. I actually need this for ec2 right now :)
00:33 manfred and at some point i would like to incorperate openstack autoscale groups once heat becomes stable.
00:33 manfred sure sure :)
00:34 Ryan_Lane hm. yeah, nova seems to use pillars as well
00:34 manfred yar
00:34 Ryan_Lane does the ec2 one not?
00:34 manfred no idea
00:34 manfred i have never looked at it
00:34 Ryan_Lane hm. I'd imagine they're all called the same
00:39 krow joined #salt
00:44 Ryan_Lane hm. if profiles can come from pillars I think I'mg ood
00:50 Ryan_Lane ah. damn. in nova pillars are only used for the keystone info
00:50 Ryan_Lane because it uses the nova modules
00:50 Ryan_Lane providers and profiles are still in config files
00:51 * Ryan_Lane opens a new issue
00:51 krow joined #salt
00:55 zain_ joined #salt
00:56 justlooks joined #salt
01:00 manicouman joined #salt
01:01 meteorfo_ joined #salt
01:09 wkf joined #salt
01:09 malinoff joined #salt
01:14 estjang joined #salt
01:14 estjang hi, I am trying to call jobs.job_list() function from a python program.
01:15 estjang Is there a good way to do this?
01:15 estjang I mean in salt/runners/jobs.py
01:15 estjang It expects __opts__ to be set
01:16 manfred __opts__ gets injected in the salt/loader.py gen_modules() function
01:18 [diecast] joined #salt
01:19 estjang Ah ok.
01:19 estjang would you use raw_mod() in loader.py to load a module, and use it?
01:19 manfred have no idea
01:20 estjang OK... I will try using loader.py. Thanks for pointing that out.
01:21 schimmy joined #salt
01:23 snuffeluffegus joined #salt
01:24 bhosmer_ joined #salt
01:25 faldridge joined #salt
01:29 rojem joined #salt
01:30 ekristen joined #salt
01:31 nicksloan joined #salt
01:33 CeBe joined #salt
01:35 stlouistechy joined #salt
01:35 stlouistechy hello, is this a good spot to look for saltstack support?
01:37 malinoff stlouistechy, yes. Also, salt-users mailing list is useful
01:37 stlouistechy great! we are having some issues with our salt minion/master keys
01:38 stlouistechy we have to image and deploy debian wheezy systems with salt pre-installed, and each time they attempt to register with the master, they find a cached key with the old hostname
01:38 stlouistechy we have tried multiple ways to clear these keys out, delete all keys on Master/Minion, delete the var/cache/salt files etc
01:39 malinoff stlouistechy, before creating an image, delete contents of /etc/salt/pki directory
01:39 stlouistechy hmm, we have actually tried that as well
01:39 malinoff stlouistechy, that should do the job
01:39 stlouistechy in the minion logs, it states an error: the salt key is cached on the master
01:39 malinoff stlouistechy, ah
01:39 stlouistechy full error:
01:40 stlouistechy 2014-03-07 00:52:44,601 [salt.crypt                               ][ERROR   ] The Salt Master has cached the public key for this node, this salt minion will wait for 10 seconds before attempting to re-authenticate
01:40 malinoff Did you delete this minion from the master?
01:40 stlouistechy yes
01:40 malinoff Hm
01:40 stlouistechy yeah, its got us pretty stumped here too
01:40 malinoff Could you post your question on salt-users?
01:40 stlouistechy sure, URL?
01:40 malinoff https://groups.google.com/forum/#!forum/salt-users
01:41 stlouistechy diving in now, thanks malinoff!
01:41 malinoff stlouistechy, np
01:41 malinoff Well, deleting /etc/salt/pki, /var/cache/salt and so forth had helped me so far
01:41 malinoff So I don't really know what's going on :)
01:41 malinoff Btw, what version do you use?
01:42 Xe joined #salt
01:43 Ryan_Lane joined #salt
01:44 jaimed joined #salt
01:46 stlouistechy just updated both the master and minion to the latest releases
01:46 stlouistechy I also just posted a fresh topic on the salt-users group for ya
01:47 stlouistechy and I wouldn't be against purchasing a support pkg here, this is for a production application we are currently developing and support is a pretty high priority for us
01:47 akoumjian joined #salt
01:47 sporkd2 your just giving the same key to all minions right?
01:47 malinoff stlouistechy, I'm not a salt core guy :)
01:47 thayne joined #salt
01:48 Ryan_Lane joined #salt
01:48 stlouistechy gotcha, probably still got a bit of a leg up on me I bet. 4 month novice user here ;-)
01:48 sporkd2 stlouistechy: your preseeding the images with the same master / minion keys?
01:48 malinoff stlouistechy, you should also delete /etc/salt/minion_id
01:49 stlouistechy I am yes, I'll try to delete the /etc/salt/minion_id real quick here
01:49 stlouistechy see if that helps
01:49 bhosmer joined #salt
01:50 stlouistechy have deleted everything in the /etc/salt/pki dir
01:50 stlouistechy didnt help any
01:50 sporkd2 are there any keys waiting to be accepted on the master?
01:51 stlouistechy yes if I don't accept it. It boots and attempts to register with the master using the original hostname although the hostname has been updated
01:52 stlouistechy after accepting the key with the incorrect hostname, test.ping seems to return OK. We just need to be sure that all our images are registering with the proper names
01:52 sporkd2 are you deploying these to a provider?
01:52 stlouistechy not sure what you mean by provider
01:53 stlouistechy AHH YEAH! Deleting the /etc/salt/minion_id seems to have done the trick!
01:53 sporkd2 nice
01:53 stlouistechy after a quick reboot, the minion comes back online and registers with the master using the new hostname!
01:53 stlouistechy Big props sporkd2! :-D
01:53 sporkd2 right because you didn't specify ID
01:53 sporkd2 no that was malinoff
01:54 sporkd2 lol
01:54 malinoff :D
01:54 stlouistechy Ha! you too bud!
01:54 oz_akan_ joined #salt
01:54 stlouistechy I just deleted the wrong stuff on the minions. You just saved me a good couple more hours there big guy
01:56 oz_akan_ joined #salt
01:58 schimmy1 joined #salt
02:06 ilbot3 joined #salt
02:06 Topic for #salt is now Welcome to #salt | Thanks to everyone who made SaltConf 2014 amazing! | 2014.1.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/
02:06 oc joined #salt
02:06 lpn joined #salt
02:06 ashb joined #salt
02:06 jacksontj joined #salt
02:06 patrek_ joined #salt
02:06 ferai joined #salt
02:07 eofs joined #salt
02:07 rager joined #salt
02:07 keekz joined #salt
02:07 justBob joined #salt
02:07 borgstrom joined #salt
02:08 bhosmer joined #salt
02:13 bemehow_ joined #salt
02:16 favadi joined #salt
02:17 rojem joined #salt
02:18 zain__ joined #salt
02:18 rojem joined #salt
02:19 elsmorian joined #salt
02:19 rojem joined #salt
02:19 longdays_ joined #salt
02:19 rgbkrk_ joined #salt
02:20 TheSojourner joined #salt
02:20 TheSojourner joined #salt
02:20 Kraln- joined #salt
02:20 cyrusdav- joined #salt
02:21 rojem joined #salt
02:21 d10n_ joined #salt
02:21 fr0 joined #salt
02:21 carmony_ joined #salt
02:21 copelco_____ joined #salt
02:22 kossy joined #salt
02:22 thayne_ joined #salt
02:24 nicksloan_ joined #salt
02:24 Kyle- joined #salt
02:24 dopp_ joined #salt
02:25 Heartbane joined #salt
02:25 nlb_ joined #salt
02:25 scalability-junk joined #salt
02:25 scalability-junk joined #salt
02:25 insatsu_ joined #salt
02:25 scurry joined #salt
02:25 [vaelen] joined #salt
02:25 codekoala joined #salt
02:25 N-Mi joined #salt
02:25 N-Mi joined #salt
02:25 manicouman joined #salt
02:25 berto- joined #salt
02:25 baoboa joined #salt
02:26 gldnspud__ joined #salt
02:26 herzi_ joined #salt
02:26 alunduil joined #salt
02:26 goodwill joined #salt
02:27 gmoro joined #salt
02:27 dyim joined #salt
02:27 dave_den1 joined #salt
02:27 crane joined #salt
02:27 rgbkrk joined #salt
02:27 fxhp joined #salt
02:28 danielbachhuber- joined #salt
02:28 raizyr_ joined #salt
02:28 seb` joined #salt
02:30 btorch_ joined #salt
02:30 feth joined #salt
02:32 longdays joined #salt
02:33 [diecast] joined #salt
02:37 cewood joined #salt
02:37 lahwran joined #salt
02:38 krow joined #salt
02:39 oz_akan_ joined #salt
02:42 torrancew joined #salt
02:44 kermit joined #salt
02:50 ajw0100 joined #salt
02:52 AdamSewell joined #salt
02:58 vejdmn joined #salt
02:58 cheus joined #salt
03:00 schimmy joined #salt
03:01 twobitsp1ite joined #salt
03:06 xl1 joined #salt
03:06 bwq joined #salt
03:07 bt joined #salt
03:07 goki joined #salt
03:07 googolhash joined #salt
03:08 gldnspud__ joined #salt
03:08 bwq joined #salt
03:08 cb joined #salt
03:08 googolhash joined #salt
03:08 Zuru joined #salt
03:08 crane_ joined #salt
03:09 wrigley joined #salt
03:09 vipul joined #salt
03:09 qybl hey, is anyone familiar with the logstash log handler? we have the following configuration in our minion and master config https://paste.selfnet.de/ZAG4/ and it sends the following json to our logstash instance https://paste.selfnet.de/g0G/ salt-version is 2014.1.0+ds-1~bpo70+1 on debian stable
03:11 nmistry joined #salt
03:11 qybl my problem is that that's not the version 1 json format logstash uses, I know that with https://github.com/saltstack/salt/pull/9539 v1 should be supported, so I'm wondering why my minions/master set version to 1 but send the json formatted with v0
03:11 lynxman joined #salt
03:11 googolhash joined #salt
03:11 dancat joined #salt
03:12 googolhash joined #salt
03:15 qybl ah, logstash input looks like this https://paste.selfnet.de/QjcM/ (so except for the port what salt suggests in the documentation)
03:16 mfournier1 joined #salt
03:17 Zuru_ joined #salt
03:18 phyde_ joined #salt
03:19 googolhash joined #salt
03:21 ajw0100 joined #salt
03:21 pt|Zool_ joined #salt
03:23 tvle joined #salt
03:23 bashcode` joined #salt
03:24 jY- joined #salt
03:25 tamentis joined #salt
03:25 synfin joined #salt
03:25 andr386 joined #salt
03:26 darrend joined #salt
03:26 ClausA joined #salt
03:29 Teknix joined #salt
03:29 fr0 joined #salt
03:30 errr joined #salt
03:30 pexio joined #salt
03:31 akl joined #salt
03:32 tzero joined #salt
03:32 zartoosh joined #salt
03:41 manicouman joined #salt
03:51 ravibhure joined #salt
03:53 snuffeluffegus joined #salt
04:03 tvle joined #salt
04:27 elsmorian joined #salt
04:29 frasergraham joined #salt
04:29 budrose joined #salt
04:30 budrose I'm attempting to get a masterless set-up working with Vagrant, but the process keeps hanging at "Calling state.highstate..." without any debug information. Any ideas on what could be causing this?
04:38 testtest234 joined #salt
04:39 testtest234 just upgraded my server and client on CentOS 6.5 (epel) to 2014.1.0
04:40 testtest234 im not getting "No Top file or external nodes data matches found"
04:43 testtest234 https://gist.github.com/jeteokeeffe/9405371
04:51 d3vz3r0 joined #salt
04:56 manfred your master is not 2014.1.0 yet
04:57 manfred 2014.1.0 minion can't talk to a 0.17.5 master
04:57 testtest234 both are 2014.1.0
04:57 manfred and restarted?
04:57 testtest234 yes, running it in the foreground now (salt-master -l debug)
04:58 testtest234 could this be cache related?
04:58 manfred that may be possible...
04:58 manfred i don't know
05:00 frasergraham joined #salt
05:06 ravibhure left #salt
05:12 baniir joined #salt
05:14 thayne_ joined #salt
05:28 krow joined #salt
05:28 d3vz3r0 joined #salt
05:33 giantlock joined #salt
05:36 budrose when I call "salt-call state.highstate --local" on my server directly, everything works as planned, but when I run salt through Vagrant provisioning, it hangs on "Calling state.highstate... (this may take a while)" ... any ideas why?
05:47 d3vz3r0 joined #salt
05:54 andr386 joined #salt
06:01 dren_ joined #salt
06:06 lionel joined #salt
06:11 jeffro joined #salt
06:18 krow joined #salt
06:28 elsmorian joined #salt
06:53 Sypher joined #salt
07:26 ndrei joined #salt
07:34 mike25ro joined #salt
07:44 Iwirada joined #salt
07:49 krow joined #salt
07:49 Shenril joined #salt
07:53 jeffro joined #salt
07:53 roolo joined #salt
07:53 kadel joined #salt
07:53 nebuchadnezzar joined #salt
07:53 hartym joined #salt
07:53 skynet joined #salt
07:53 zain_ joined #salt
07:53 gammalget joined #salt
07:53 davet joined #salt
07:53 d3vz3r0 joined #salt
07:53 n0c joined #salt
07:53 dimeshake joined #salt
07:53 torrancew joined #salt
07:53 renoirb joined #salt
07:53 jnials joined #salt
07:53 HeadAIX joined #salt
07:53 Ryan_Lane joined #salt
07:53 openxmark joined #salt
07:53 Kyle joined #salt
07:53 tharkun joined #salt
07:53 jmccree joined #salt
07:53 EntropyWorks joined #salt
07:53 jeff joined #salt
07:53 bwq joined #salt
07:53 xl1 joined #salt
07:53 zdong joined #salt
07:53 64MAAETTT joined #salt
07:53 kedo40 joined #salt
07:53 zz_Cidan joined #salt
07:53 tmwsiy_ joined #salt
07:53 blabla_ joined #salt
07:53 funzo joined #salt
07:53 dopp_ joined #salt
07:53 alunduil joined #salt
07:53 cb joined #salt
07:53 Hipikat joined #salt
07:53 SEJeff_work joined #salt
07:53 paramah joined #salt
07:53 bigmstone joined #salt
07:53 ckao joined #salt
07:53 vlcn_ joined #salt
07:53 symroe joined #salt
07:53 ze- joined #salt
07:53 Schmidt joined #salt
07:53 svs joined #salt
07:53 honestly joined #salt
07:53 terminalmage joined #salt
07:53 patrek joined #salt
07:53 gldnspud__ joined #salt
07:53 razor joined #salt
07:53 babilen joined #salt
07:53 jbub joined #salt
07:53 sinh joined #salt
07:53 svx joined #salt
07:53 SaveTheRbtz joined #salt
07:53 msciciel joined #salt
07:53 magenbrot joined #salt
07:53 scarcry joined #salt
07:53 andrej joined #salt
07:53 sashka_ua joined #salt
07:53 balltongu joined #salt
07:53 Tinuva joined #salt
07:53 kaictl joined #salt
07:53 alienresidents joined #salt
07:53 runnyspot joined #salt
07:53 shadowsu1 joined #salt
07:53 pnl joined #salt
07:53 dpacz joined #salt
07:53 gamingrobot joined #salt
07:53 modafinil_ joined #salt
07:53 rcsheets joined #salt
07:53 rogst joined #salt
07:53 delkins_ joined #salt
07:53 bretep` joined #salt
07:53 abele joined #salt
07:53 JordanRinke joined #salt
07:53 xt joined #salt
07:53 sporkd2 joined #salt
07:53 puppet joined #salt
07:53 jero joined #salt
07:53 hotbox joined #salt
07:53 DaveQB joined #salt
07:53 chuffpdx joined #salt
07:53 naiyte_ joined #salt
07:53 TheSojourner joined #salt
07:53 cyrusdavid joined #salt
07:53 carmony joined #salt
07:53 kossy joined #salt
07:53 nicksloan_ joined #salt
07:53 kevinbrolly_ joined #salt
07:53 bejer joined #salt
07:53 sroegner_ joined #salt
07:53 rhand joined #salt
07:53 fejjerai joined #salt
07:53 steveoliver joined #salt
07:53 dcmorton joined #salt
07:53 backjlack joined #salt
07:53 juice joined #salt
07:53 ahammond joined #salt
07:53 jforest joined #salt
07:53 MTecknology joined #salt
07:53 malinoff joined #salt
07:53 cornmander joined #salt
07:53 luminous joined #salt
07:53 repl1cant joined #salt
07:53 monokrome joined #salt
07:53 twiedenbein joined #salt
07:53 zach_ joined #salt
07:53 Psi-Jack joined #salt
07:53 JaredRo joined #salt
07:53 gcbirzan joined #salt
07:53 nliadm joined #salt
07:53 seanz joined #salt
07:53 berto- joined #salt
07:53 codekoala joined #salt
07:53 scurry joined #salt
07:53 rager joined #salt
07:53 jasonrm joined #salt
07:53 hillna joined #salt
07:53 hvn joined #salt
07:53 codekoala joined #salt
07:53 jeffro joined #salt
07:54 echos joined #salt
07:54 joehoyle joined #salt
07:57 herzi_ joined #salt
07:57 mrchrisadams joined #salt
07:58 goki joined #salt
07:58 unicoletti joined #salt
07:59 jab416171 joined #salt
08:00 gammalget joined #salt
08:00 topochan joined #salt
08:03 munhitsu_ joined #salt
08:03 Kenzor joined #salt
08:03 blast_hardcheese joined #salt
08:05 copelco_____ joined #salt
08:06 linjan_ joined #salt
08:08 harobed_ joined #salt
08:09 octarine joined #salt
08:09 harobed_ joined #salt
08:11 elsmorian joined #salt
08:18 think-free_ joined #salt
08:21 krow joined #salt
08:24 joehoyle joined #salt
08:25 slav0nic joined #salt
08:25 slav0nic joined #salt
08:26 CeBe joined #salt
08:27 krow joined #salt
08:32 krow joined #salt
08:35 giantlock_ joined #salt
08:37 sfello joined #salt
08:38 krow joined #salt
08:40 brian linda
08:43 krow joined #salt
08:45 rjc joined #salt
08:47 krow1 joined #salt
08:50 rgbkrk joined #salt
08:51 brian left #salt
08:52 krow joined #salt
08:54 babilen Hi all - Are you aware of pretty large salt configurations that might be available for reading online? I need some inspiration for organising my state namespace and how to deal with dependencies and thought that it is a good idea to learn from larg(ish) setups.
08:56 babilen I am developing in a style in which I configure "services" in the sense of "Run www.example.com" and target that to minions, but that ends up with dependencies all over the place. Also not sure how to structure my top-level directories in a sensible way .. (e.g. do you have pkgs.foo.server ? or rather foo.server? or customer1.web.www.example.com or ... ?
08:58 krow joined #salt
09:02 lessismore I just found out that salt-ssh complies with the top.sls of the pillar, nice!
09:02 bezaban I would be interested in that too
09:02 andr386 @babilen: Hi, you can see some examples at http://saltstarters.org/ and https://github.com/saltstack/salt-states.  I am myself a newbie and found out that it was easier to have a bottom up approach. I am moving from the existing infrastructure to a salt infrastructure by salting it step by step. Also services don't live in a void, they need a base (your dependencies) and you must handle that first
09:03 bezaban good timing, thanks andr386
09:03 babilen andr386: Could you elaborate on the "bottom up" appraoch a little?
09:03 babilen *approach
09:03 krow joined #salt
09:05 babilen My mindset is simply "I want foo-host to provide bar-service" and I want to express *that* in salt (and want it to sort out the details). I, naturally, need basic building blocks (e.g. install package foo, use apache-formula, ...) and I make ample use of saltstack-formulas, but I just want to see some good (larger) examples to get a feeling for what can be done.
09:06 andr386 @babilen:With salt I can see how many servers I have that use 'apache' or 'opensshserver'. Then I try to write a state that match for one of them. Then for a few of them. Then I write a pillar that holds the configuration for that services on all of them.
09:06 [j4jackj] joined #salt
09:07 [j4jackj] left #salt
09:08 krow1 joined #salt
09:08 babilen andr386: So you would use "'foo': - apache - php - postgresql" (which in their entirety constitute what is needed for www.example.com) rather than "'foo': - example.com" with example.com being "include: - apache - php - postgresql" ?
09:08 andr386 Yes, in a first time
09:09 andr386 It's a good beginning
09:10 MTecknology joined #salt
09:10 andr386 apache - php -postgresql are only the top layer, below that you have network, firewall, virtualization, ntp, user management ....
09:11 andr386 You can't know beforehand what you will want to abstract
09:12 andr386 or if you know, you're going to miss on what is really happening
09:13 babilen Sure, but I know that I want "www.example.com" now and am not sure how to structure my top layer. There simply isn't a "layer hierarchy standard" for salt and I have to invent my own ... thought that there might be proven schemes already. (e.g. have "service.$FOO (.apache,.postgresql, ...), pkgs.$BAR (.vim, .emacs, ...), ...)
09:13 scott_w joined #salt
09:13 krow joined #salt
09:14 bhosmer joined #salt
09:14 babilen andr386: Thanks for the two links, they are brilliant :)
09:16 bezaban I'm having somewhat similar problems wrt structure.  Although I'm still reconsidering my targeting schemes.  Salt made me realize that the servers are much less uniform than I thought
09:16 bezaban I'll poke the links
09:16 bhosmer_ joined #salt
09:18 rdorgueil joined #salt
09:18 rdorgueil joined #salt
09:19 krow joined #salt
09:23 andr386 @bezaban: good luck
09:25 krow joined #salt
09:26 bezaban thanks :).  I've been trying to find common denominators for machines to be able to be able to target as many at once using nodegroups, but I think that may be the wrong approach and instead of striving for the smallest possible statefiles I should define every machine explicitly
09:27 bhosmer joined #salt
09:27 elsmorian andr386: Don't suppose you have any ideas on my SO question- http://stackoverflow.com/questions/22232110/salts-mine-get-command-works-on-cli-but-not-in-a-jinja-template
09:29 andr386 @elsmorian: Sorry, I am not using salt-mine yet, and I am also struggling with jinja ;-)
09:30 krow joined #salt
09:33 carlos joined #salt
09:35 vmdsch joined #salt
09:35 vmdsch left #salt
09:36 krow joined #salt
09:37 elsmorian andr386: ah, shame!
09:41 babilen What are your thoughts regarding "pkg: - installed" or "pkg: - latest" ? I tend to favour the latter, but see "- installed" to be used more frequently in other recipes (states?)
09:48 andr386 'installed' you know what version you have, and if that version doesn't break it dependencies you are golden
09:49 andr386 'latest' you never know if a new version will break compatibility, latest could be a good idea on a test server maybe
09:49 babilen How would I ensure that I have the latest version of those packages in that case?
09:50 babilen andr386: Yeah, but we are deploying on Debian stable and test deployments in a/another virtual environment before taking them into production.
09:50 babilen I see how "- installed" is the "never change a running system" approach :)
09:51 andr386 You can define manually the 'version' with installed, if that version is available
09:52 sgflt joined #salt
09:52 andr386 I try to keep all my packages debian stable standards. Exceptions are installed from git.
09:52 elfixit joined #salt
09:52 fnbar joined #salt
09:54 fnbar hi guys
09:54 fnbar Currently trying to takle down a possible bug... Something I need to know from you: Installing Salt on debian using the SaltStack repos: Why does salt install on both python2.6 AND python2.7? :-)
09:55 krow joined #salt
09:58 honestly joined #salt
09:59 mike25ro left #salt
10:04 fnbar Somehow my salt minion still tries to contact my DNS, altough i disabled it
10:06 mike25ro joined #salt
10:13 viod joined #salt
10:23 johtso joined #salt
10:25 oznt hi everyone, is there anyone here who uses salt on windows?
10:25 babilen I'm using pkrepo.managed to add a local Debian repository, but the GPG key used for signing is not available on a keyserver and "gpgkey: file:///...." looks as if it is specific to yum. How would I deal with this? (cf. http://docs.saltstack.com/ref/states/all/salt.states.pkgrepo.html (
10:26 babilen ))
10:29 babilen Hmm, I wonder if pkgrepo.managed.key_url is actually pkgrepo.managed.key_uri ... lets try that
10:31 manicouman joined #salt
10:32 babilen Hmm, it does quite specifically say "A web URL to retrieve the GPG key from." which implies that URIs are not accepted :-/ -- Well, I guess that I have to try it and file a bug if URIs such as file:// work.
10:33 Furao joined #salt
10:35 helderco joined #salt
10:39 helderco joined #salt
10:41 manicouman joined #salt
10:49 MrTango joined #salt
11:03 robinsmidsrod joined #salt
11:04 DenkBrettl joined #salt
11:04 bhosmer joined #salt
11:05 tr_h joined #salt
11:08 lessismore anybody got salt-cloud working on debian wheezy? it seems that the requirement of salt-cloud are not enforced in the package, and this gives error at runtime: ImportError: Your version of libcloud is 0.5.0. salt-cloud requires >= libcloud 0.13.2. Please upgrade.
11:08 lessismore and it seems that there is no debian package of libcloud 0.13.2
11:11 manicouman joined #salt
11:11 ggoZ joined #salt
11:13 justBob joined #salt
11:16 oznt can i run file.copy  from withing a state?
11:18 davidone good morning
11:18 davidone is therey a way (state/module) to manage /etc/crontab?
11:19 bhosmer joined #salt
11:19 topochan joined #salt
11:20 honestly yes.
11:21 honestly you can use file.append, or you can use http://docs.saltstack.com/ref/states/all/salt.states.cron.html
11:23 davidone all salt states in that page refers to a specific user (default=root)
11:24 davidone the best (manageable, quick) way seems to be a file.managed and a jinja template
11:24 davidone (probably)
11:29 honestly it defaults to root
11:29 honestly but you can change that...
11:31 bhosmer joined #salt
11:31 manicouman joined #salt
11:32 davidone yes, but /etc/crontab is not the crontab of a specific user
11:32 honestly ...
11:33 honestly pretty sure that state will write /etc/crontab
11:33 bhosmer_ joined #salt
11:35 honestly users don't have specific crontabs, the user is specified as a field in /etc/crontab
11:35 fnbar joined #salt
11:36 fnbar Hi guys. Is it possible to disable single grains (of the included core-grains?)
11:42 davidone honestly: http://pastebin.com/mmNZYHsH
11:47 viq honestly: I'm afraid users _do_ have specific crontabs
11:48 bitmand davidone: afaik, file.manged is the only way for the system crontab
11:48 bitmand file.managed :)
11:50 davidone bitmand: me too :)
11:54 Furao joined #salt
11:54 bitmand davidone: I ended up moving my root cronjobs to the root users crontab, so I could use the cron state. No difference in my case :)
11:55 davidone it makes sense
11:55 krow joined #salt
11:55 davidone I don't give this level of freedom to users :)
11:55 bhosmer joined #salt
12:01 bitmand davidone: true .. users should never have freedom ;)
12:03 rojem joined #salt
12:03 davidone bitmand: :)
12:03 N-Mi joined #salt
12:07 bhosmer joined #salt
12:11 mailo joined #salt
12:12 bhosmer joined #salt
12:13 bhosmer joined #salt
12:17 favadi joined #salt
12:22 babilen How can I disable the installation of Recommends with pkg.installed on Debian systems?
12:26 kalleh joined #salt
12:30 ndrei joined #salt
12:30 AdamSewell joined #salt
12:46 higgs001 joined #salt
12:47 jslatts joined #salt
12:48 kalleh Hey guys, I've been looking at Saltstack briefly but I am a bit confused regarding bare metal deployment. How would one do this the best way with SaltStack? Does SaltStack have integrated tools to do this in itself or would you use Puppet razor and then jump to saltstack?
12:48 gnugnu8 joined #salt
12:54 joehoyle joined #salt
12:54 babilen "Rendering SLS "base:apache.debian_full" failed: Conflicting ID "extend"" huh?! Really?
12:54 babilen https://github.com/saltstack-formulas/apache-formula/blob/master/apache/debian_full.sls
12:54 linjan joined #salt
12:55 manicouman joined #salt
12:55 vejdmn joined #salt
13:01 backjlack joined #salt
13:03 ajprog_laptop joined #salt
13:04 bhosmer joined #salt
13:04 babilen All I do is to include it in another state .. what can I do about this?
13:07 krow joined #salt
13:14 rojem joined #salt
13:15 jforest joined #salt
13:16 krow joined #salt
13:18 patrek_ joined #salt
13:24 zooz joined #salt
13:26 gnugnu8 joined #salt
13:31 viq kalleh: saltstack itself does not have any facilities for bare metal provisioning - it does have some for cloud/virtualization though. And yeah, you could use something like razor/foreman/cobbler and have it install salt so it would connect to your controller
13:32 vardelean joined #salt
13:33 kadel joined #salt
13:33 oz_akan_ joined #salt
13:35 oz_akan_ joined #salt
13:41 manicouman joined #salt
13:43 wkf joined #salt
13:44 kalleh viq: Ok great, thanks for the information. Always good to get a clarification. :)
13:45 viod joined #salt
13:47 AdamSewell joined #salt
13:49 corm joined #salt
13:50 corm Can someone tell me how to view attributes loaded into the "mine"?
13:53 viq corm: I think mine.get from http://docs.saltstack.com/ref/modules/all/salt.modules.mine.html
13:53 EzeQL joined #salt
13:54 akoumjian joined #salt
13:55 viq corm: also http://docs.saltstack.com/ref/runners/all/salt.runners.cache.html?highlight=mine#salt.runners.cache.mine
13:55 jaimed joined #salt
13:57 x5257 joined #salt
13:57 dyim joined #salt
13:58 rgbkrk joined #salt
14:00 corm viq: i've seen those docs thanks. "salt-run cache.mine" returns "Function 'cache.mine' is unavailable". Regarding mine.get i find this confusing, If i run the example command i get results even on minions i havaent configured the mine data for. What I'm expecing is that the mine data is "send" and stored somewhere. From reading the documentation i expected it to be available in the master pillar data.
14:01 ndrei joined #salt
14:02 colinbits joined #salt
14:03 EzeQL left #salt
14:04 corm Specifically this part of the documentation "The functions to be executed are merged from the master config, pillar and minion config under the option "function_cache":".  I dont know what the "function_cache" is though. Perhaps "cache.mine" which i'm failign to run?
14:06 babilen How would I extend https://github.com/saltstack-formulas/apache-formula/blob/master/apache/debian_full.sls ? Whenever I try to include it I get: "Rendering SLS "base:apache.debian_full" failed: Conflicting ID "extend"" unfortunately
14:07 dyim joined #salt
14:07 babilen And is there any way to prevent the installation of recommended packages on Debian systems?
14:07 timoguin joined #salt
14:10 R_Shackleford joined #salt
14:10 viq skip_suggestions ?
14:11 vardelean_ joined #salt
14:11 babilen viq: No, that is not what I am looking for (or I don't understand what it does)
14:12 Gifflen joined #salt
14:12 Gifflen joined #salt
14:13 babilen viq: Recommended packages (a lighter form of package dependency) are installed by default on Debian. I don't want to do that for a small number of packages and salt's salt.states.pkg.installed doesn't seem to support that. I am therefore wondering how people solved it (short of just running "apt-get --no-install-recommend install ..." through salt)
14:13 Guest30779 joined #salt
14:13 cym3try joined #salt
14:13 cym3try i am a bit stuck with trying to make the mysql module to work
14:14 cym3try i am getting the error State mysql_user.present found in sls mysql is unavailable
14:14 faldridge joined #salt
14:15 bhosmer cym3try: Do you have python-mysql installed?
14:16 cym3try yes
14:16 cym3try wait..i only installed it on the master
14:16 Ponycorn joined #salt
14:16 cym3try let me install it on the minion too
14:16 bhosmer Yeah, that might do it for you.
14:17 cym3try yep that was the issue
14:17 bhosmer Sweet!
14:18 juicer2 joined #salt
14:18 faldridge joined #salt
14:20 Ponycorn Hey guys, i trying to use a state to create users on my minions. I'd like to create a user, set a default password and make user change it when they first log in.
14:21 Ponycorn so i my state i have user: - password: 'hash of default pass' - date: 0
14:21 Ponycorn (among other settings)
14:21 topochan joined #salt
14:21 Ponycorn default password works great, but the date doesn't
14:22 bhosmer I've got a state that does exactly what you are trying to do, let me find it...
14:22 Ponycorn i have to apply shadow.set_date user 0 after to force the password change
14:22 mpanetta joined #salt
14:23 che-arne joined #salt
14:23 rgbkrk joined #salt
14:23 unicoletti left #salt
14:24 yomilk joined #salt
14:24 bhosmer http://pastebin.com/xriabeFz is what I wound up doing
14:25 bhosmer Ponycorn: If I remember right, something wasn't quite working with the shadow and expiring the passwords.
14:26 sfello joined #salt
14:27 Ponycorn bhosmer: okay, i'll use your work around waiting for an update ! thanks mate
14:27 bhosmer I think I was going to take a look at the shadow and see why it wasn't working, but I just worked around it instead. Lazy, I know. I should actually fix it.
14:29 Ponycorn well if you use the shadow module, it works. But not in the user's state..
14:29 kermit joined #salt
14:29 pdayton joined #salt
14:30 sporkd2 joined #salt
14:32 timoguin Ponycorn, what if you call the shadow module directly in the sls with module.run?
14:36 Ponycorn timoguin: i'm trying this way, i'll tell you
14:39 oraqol joined #salt
14:39 bhosmer joined #salt
14:40 oraqol Ok so I have a weird question:  is there a way for salt to scan a directory on all minions, then delete a file if it exists on the minion?  Like if a tarball exists in root directory, rm it?
14:40 Gifflen joined #salt
14:41 oraqol I was thinking place a script to do this in a .sls
14:41 oraqol I guess I could just have the minion state add a script that does that to cron...
14:42 Networkn3rd joined #salt
14:42 oraqol I'll think about this some more and come back
14:44 btorch_ does salt keep a cache or ordering ?
14:44 btorch_ on
14:44 pdayton1 joined #salt
14:47 racooper joined #salt
14:51 elfixit joined #salt
14:54 gammalget joined #salt
14:58 Ponycorn timoguin; the module.run does work on a state
14:58 Ponycorn so it's only the 'date' argument in the user module that is not working
14:58 bhosmer joined #salt
15:00 cym3try btw what is the best way to run commands only the first time, so everytime i run highstate these are ignored?
15:01 cym3try for instance, i want to compile some packages when i spin new boxes, but everytime i run highstate, i dont want them to be recompiled each time
15:02 Shish assuming you're using cmd.run to literally run a command line, I'd think the solution would be to add "- unless: <command line which returns true if the binary already exists>"
15:02 vejdmn joined #salt
15:03 mgw joined #salt
15:03 GradysGhost joined #salt
15:03 HeadAIX joined #salt
15:03 cym3try yes indeed i use cmd.run
15:05 liwen joined #salt
15:06 Ahlee anybody had luck running minions within supervisord? and/or know a trick for keeping minions up/responding?
15:07 seapasulli joined #salt
15:08 Ahlee i'm running the master, minion, and api inside a single supervisord right now, and it still managed to get into a bad state
15:10 zain_ joined #salt
15:14 tharkun joined #salt
15:16 thayne_ joined #salt
15:16 bhosmer joined #salt
15:17 sporkd2 has anyone gotten the start_action to work on salt cloud?
15:21 rgbkrk joined #salt
15:22 forrest joined #salt
15:22 GradysGhost joined #salt
15:23 rostam joined #salt
15:23 mgw joined #salt
15:24 liwen joined #salt
15:29 replicant1 joined #salt
15:30 danielbachhuber joined #salt
15:31 bhosmer joined #salt
15:33 akoumjian joined #salt
15:33 mr_chris joined #salt
15:34 ndrei joined #salt
15:34 tvle joined #salt
15:35 manicouman joined #salt
15:36 alunduil joined #salt
15:37 Zuru joined #salt
15:37 oraqol left #salt
15:39 krow joined #salt
15:40 btorch_ hmm pkg.installed is not supposed to update a pkg is it ?
15:41 liwen joined #salt
15:42 forrest btorch_, no
15:42 forrest btorch_, that's pkg.latest
15:42 forrest or via a specified version in pkg.installed
15:43 bt joined #salt
15:44 btorch_ forrest: thought so, about the ordering of yesterday .. I had to end up adding order: 10000[0-5] in order to make the state last
15:45 bhosmer joined #salt
15:48 frasergraham joined #salt
15:48 hhenkel joined #salt
15:49 hhenkel Hi all, anyone using gitfs for environments?
15:49 conan_the_destro joined #salt
15:49 hhenkel I'm currently playing around a bit and facing this error: The conflicting ID is "/tmp/motd" and is found in SLS "base:common" and SLS "dev:common"
15:50 hhenkel I'm aware of the fact that master is mapped into base but how am I supposed to work with different envs then?
15:52 luminous_ joined #salt
15:52 ze-_ joined #salt
15:53 krow joined #salt
15:56 bhosmer_ joined #salt
15:57 higgs001 joined #salt
15:57 Zuru joined #salt
15:57 gammalget_ joined #salt
15:58 luminous joined #salt
15:59 ndrei_ joined #salt
16:02 lessismore left #salt
16:03 ipalreadytaken joined #salt
16:04 debian112 joined #salt
16:06 forrest btorch_, weird
16:06 forrest is your service in the same state as all of the configuration it depends on?
16:06 kaptk2 joined #salt
16:06 openxmar1 joined #salt
16:06 cornmand1r joined #salt
16:06 vlcn joined #salt
16:07 debian112 does anyone have an good example on how to connect salt to GITFS with multi-evironments? I am looking to allow only members in those environments to checkout and push back to their repo, where that will have their own top.sls file.
16:07 higgs001 joined #salt
16:07 krow joined #salt
16:08 btorch_ forrest:  do you mean same state file ? or do you mean like mystate: pkg, file, services ?
16:08 malinoff_ joined #salt
16:09 btorch_ forrest: but yeah everything is on the same state file so .. swift_object/init.sls has everything in there
16:09 danielbachhuber- joined #salt
16:09 jmccree_ joined #salt
16:09 Ryan_Lane joined #salt
16:09 johtso joined #salt
16:09 forrest btorch_, I see
16:09 forrest can you pastebin it?
16:09 gnugnu8 joined #salt
16:09 forrest after cleaning sensitive data of course
16:09 Zuru joined #salt
16:10 ahammond joined #salt
16:10 btorch_ forrest: give me a few momements
16:10 jeremyfelt joined #salt
16:11 frumpel joined #salt
16:12 frumpel Hi All! Is there a way to configure a syndic as if it were a regular minion? If I run salt-run manage.status the syndic always shows as down ...
16:13 jforest joined #salt
16:13 MTecknology joined #salt
16:13 forrest frumpel, the syncid should be treated like a normal minion from the master above it, there was a bug on this: https://github.com/saltstack/salt/issues/8701
16:14 quantumriff joined #salt
16:15 Zuru joined #salt
16:15 FarrisG It looks like the IAM role is defined in the provider config for salt-cloud. How can we dynamically define different roles based on certain criteria for individual nodes deployed via salt-cloud? I don't see any IAM parameters in the profile config.
16:16 xmltok joined #salt
16:18 baniir joined #salt
16:18 mattmtl trying to set up a schedule job using states. I did sync the states on minion but the scheduled job is never been executed
16:19 jalbretsen joined #salt
16:20 mattmtl the job gets executed when I copy/paste the content of the state file into the minion conf file and restart the minion
16:21 pdo1013 joined #salt
16:21 pdo1013 I'm seeing some odd behavior, and I was wondering if anyone else has
16:22 pdo1013 running 2014.1.0
16:22 pdo1013 my salt-master is getting authentication requests from machines that have their salt-minions shut off
16:22 pdo1013 like so:
16:22 pdo1013 2014-03-07 16:21:16,985 [salt.master      ][INFO    ] Clear payload received with command _auth
16:22 pdo1013 2014-03-07 16:21:16,986 [salt.master      ][INFO    ] Authentication request from digitalocean-proxy-1238
16:22 pdo1013 2014-03-07 16:21:16,988 [salt.master      ][INFO    ] Authentication accepted from digitalocean-proxy-1238
16:24 vlcn anyone have any suggestions on what would be causing rendering to fail on this? https://gist.github.com/kelchm/30439a82d70b7ea29c71
16:24 ndrei joined #salt
16:24 tl-ml joined #salt
16:25 pdo1013 ah crap, just answered my own question
16:25 pdo1013 the Upstart script is reporting they're down, but there are stray salt-minions still running
16:25 yomilk joined #salt
16:26 FarrisG Can you put the "iam_profile" in the salt-cloud profile definition rather than the provider? It seems to defeat the purpose of IAM roles to have *all* nodes from the same provider use the same profile/role.
16:27 Zuru joined #salt
16:29 seapasulli joined #salt
16:29 higgs001 joined #salt
16:30 pdayton joined #salt
16:31 krow joined #salt
16:31 cym3try joined #salt
16:33 tvle joined #salt
16:36 sporkd2 is there somewhere that lists all event tags to match your reactor on?
16:37 Zuru joined #salt
16:37 ndrei joined #salt
16:39 backjlack joined #salt
16:39 krow joined #salt
16:43 rgbkrk joined #salt
16:44 bhosmer joined #salt
16:47 jeremyBass1 joined #salt
16:50 higgs001 joined #salt
16:50 krow joined #salt
16:50 hunter joined #salt
16:51 circ-user-dYxXc joined #salt
16:51 circ-user-dYxXc Hey guys is it possible to include a file with all variables ?
16:51 forrest circ-user-dYxXc, what do you mean?
16:52 circ-user-dYxXc I have multiple sls file and they all need to access the same variables
16:53 jeremyBass1 joined #salt
16:54 colinbits joined #salt
16:54 scoates joined #salt
16:54 elsmorian circ-user-dYxXc: that is i think what the pillar is for
16:54 forrest circ-user-dYxXc, ok, so those variables could either live within a state if they don't need to be secure, or they could live in pillar.
16:55 elsmorian yeah
16:55 forrest pillar is usually better all around.
16:55 forrest a bit slower, but easier to keep stuff there if it isn't OS related.
16:55 forrest some guys have been messing with a secondary state just for associated values though.
16:56 krow joined #salt
16:56 naiyte joined #salt
16:56 KyleG joined #salt
16:56 KyleG joined #salt
16:56 thingsnstuff joined #salt
16:57 Iwirada left #salt
16:57 TheRealBill_here joined #salt
16:59 Zuru joined #salt
16:59 meteorfox joined #salt
17:03 matt_debug joined #salt
17:06 Zuru joined #salt
17:09 krow joined #salt
17:10 vlcn https://gist.github.com/kelchm/30439a82d70b7ea29c71
17:10 vlcn what do I need to do to get the actual values out of each of these arrays?
17:11 thayne_ joined #salt
17:13 smcquay joined #salt
17:15 xmltok joined #salt
17:15 rsimpkins What are some possible reasons that minions wouldn't copy down new files from the master? I can see the newer file in files_root on the master, but in /var/cache/salt on the minion I have the old version. There are no errors in the minion's log that indicate what could cause the issue.
17:16 vejdmn joined #salt
17:17 Zuru joined #salt
17:17 darrend joined #salt
17:18 ashb If i change the grains for a box in a cloud.map file that already exists, do those every make it out to updated grains on the box?
17:18 Heartbane basepi: if I am ready to deploy on Centos 5 hosts, Is the repo to patch zeromq to new versions located here: http://docs.saltstack.com/downloads/cent5/
17:19 basepi Heartbane: yes.
17:19 Heartbane basepi: do I need to deploy a newer version of python too?
17:19 bemehow joined #salt
17:20 forrest Heartbane, you need python 2.6
17:22 basepi Yep, what forrest said.  =P  Should be good on Python version.
17:22 vejdmn joined #salt
17:23 Heartbane basepi: forrest: ya I already checked that
17:23 Heartbane Thanks Colt
17:23 forrest cool
17:24 sfello joined #salt
17:25 vlcn can anyone help me with this jinja for loop? https://gist.github.com/kelchm/30439a82d70b7ea29c71
17:25 vlcn going completely nuts here
17:26 fxhp Heartbane !!  : )
17:26 vlcn how can I actually get the value rather than the key?  Specifying key, value in the loop causes rendering to fail
17:27 krow joined #salt
17:27 fxhp vlcn: looking
17:28 fxhp vlcn: do you know python?
17:28 vlcn fxhp: not really.  I'm working on getting more comfortable with it though.
17:28 Heartbane fxhp: ?
17:29 fxhp Heartbane: morning : )
17:29 budrose joined #salt
17:30 fxhp vlcn - well so Jinja is like a subset of python (templating lang) which allows python like data flow and access inside of other markups (in this case yaml)
17:30 fxhp pillar is a python dictionary
17:30 fxhp so the same rules for python dictionaries apply for accessing data in pillar
17:31 higgs001_ joined #salt
17:31 fxhp vlcn: that said I have not had a need to use the reactor system yes
17:32 krow joined #salt
17:32 tvle joined #salt
17:32 fxhp vlcn: data['data']['node'] does this exist?  what happens if you just print that?
17:32 vlcn fxhp, yes it exists.  Take a look at the output
17:33 vlcn the issue is that I can't get the actual values without doing a second for loop
17:33 Zuru joined #salt
17:33 vlcn and using for key, value in data['data']['node'] causes the rendering to fail
17:33 fxhp vlcn: so you can getting key instead of real value?
17:33 fxhp data['data']['node'].items()
17:33 vlcn fxhp: if you look at 'output' thats what the rendered sls actually looks like
17:34 naiyte vlcn: Iterating over a python dict gives you the value by default. Using .values() will give you a list of values to iterate over instead.
17:34 fxhp for key, value in data['data']['node'].items()
17:34 kballou joined #salt
17:34 naiyte ^ - that's even nicer. items() gives you a tuple of the key and the value.
17:35 faldridg_ joined #salt
17:35 fxhp the items() method of a dict will yeild a tuple of (key,value) pairs
17:35 pdayton1 joined #salt
17:35 vlcn sure enough, that worked perfectly naiyte
17:36 vlcn er, fxhp
17:36 vlcn so basically, I just need to spend this weekend learning Python ;)
17:36 fxhp : )
17:36 fxhp vlcn: that would help, python is my favorite programming lang
17:37 vlcn I'm having a reallllly hard time not hating it
17:37 fxhp vlcn: what are you using the reactor system for?
17:37 vlcn fxhp: it's for adding new solusvz slaves to the solusvm master
17:37 vlcn http://www.solusvm.com/
17:37 krow joined #salt
17:38 naiyte vlcn: out of curiosity, what do you hate about Python?
17:38 fxhp So basically auto-accpeting the new minions key ?
17:39 schimmy joined #salt
17:39 vlcn fxhp, thats another part of it.  My reasoning for using the reactor system here is that I don't need to user peer communication, everything goes directly through the master
17:40 smcquay joined #salt
17:40 vlcn naiyte: the indentation and seeming lack of structure
17:42 vlcn fxhp, this is an older version of what I was working on today, but it might give you a more complete idea of what is going on: https://gist.github.com/kelchm/9239311
17:43 Ryan_Lane1 joined #salt
17:45 krow joined #salt
17:47 themilnet joined #salt
17:48 bhosmer joined #salt
17:53 bhosmer joined #salt
17:56 raizyr joined #salt
17:56 krow joined #salt
17:56 tvle joined #salt
17:57 hunter joined #salt
17:58 hunter joined #salt
17:59 cym3try joined #salt
18:00 amckinley joined #salt
18:00 crazysim joined #salt
18:02 tvle joined #salt
18:04 pdayton joined #salt
18:05 akoumjian joined #salt
18:07 krow joined #salt
18:09 hunter joined #salt
18:09 rojem joined #salt
18:10 mattbarto joined #salt
18:17 diegows joined #salt
18:17 Gareth morning
18:18 elfixit joined #salt
18:18 diegows a grain listing all the mounted filesystem would be great :)
18:18 CeBe1 joined #salt
18:20 sporkd2 diegows: i agree write it up :)
18:20 Gareth diegows: file an issue/feature request.
18:21 diegows yes
18:21 diegows I'll do... and I'll write it if I have some time next week
18:22 diegows filed
18:22 diegows https://github.com/saltstack/salt/issues/11043
18:24 krow joined #salt
18:27 m87carlson joined #salt
18:30 krow joined #salt
18:31 rdorgueil joined #salt
18:37 d3vz3r0 joined #salt
18:39 Ahlee diegows: i don't think grains are the right place for that info, mounts can change quite frequently.  It'd be better as an external pillar
18:40 [vaelen] joined #salt
18:40 kula it won't work as an external pillar --- external pillars run on the master, not on the minions. but i agree, it's not a grains thing.
18:41 allanparsons joined #salt
18:42 mgw joined #salt
18:42 krow joined #salt
18:49 diegows kula, Ahlee well... the ticket is right place for the debate about this :)
18:49 Ahlee kula: good call.
18:52 allanparsons is there a way to use git over port 443?
18:53 hunter joined #salt
18:53 joehoyle joined #salt
18:54 joehoyle joined #salt
18:54 Ahlee the concept of a dynamic 'grain' is interesting to me though.  Items like active NIC in a bonded interface
18:58 cpenner461 joined #salt
18:59 dave_den allanparsons: just use https://blah.com/foo.git
18:59 allanparsons what about if its a private repo?
18:59 allanparsons via cmd prompt, i use:  git+ssh and then add this to my ~/.ssh/config:  https://help.github.com/articles/using-ssh-over-the-https-port
19:00 allanparsons but i was wondering if there was a way to do git+ssh  for git.latest:
19:02 dave_den yes, you can use git+ssh for git.latest
19:02 dave_den and you can specify an alternate ssh pubkey using 'identity' for git.latest
19:04 themadcanudist joined #salt
19:04 themadcanudist hey guys, in a reactor .sls, can I execute a salt.module  within the template so that I can gather some data to pass inline to pillar in the mapped call?
19:07 fridiculous joined #salt
19:08 fridiculous hey, does anyone have experience launching elasticsearch with salt / salt-cloud here?
19:08 fridiculous i'm trying to figure out what's the best way to manage replicas and discovery
19:11 jperras fridiculous: what do you mean? ES should do multicast-like discovery using the AWS EC2 apis
19:12 jperras you should only need to have salt configure new ES nodes with the right cluster names & discovery protocol, and have the instance booted with the right security group(s)
19:13 higgs001 joined #salt
19:13 fridiculous jperras i see
19:14 fridiculous do you know if there is a difference between using VPC and EC2 with salt?
19:14 fridiculous i mean with elasticsearch's interface to AWS's api
19:14 jperras unsure. you could probably use real multicast with VPC
19:16 krow joined #salt
19:18 faldridge joined #salt
19:20 rsimpkins left #salt
19:21 jslatts joined #salt
19:24 schimmy joined #salt
19:25 dansalmo joined #salt
19:25 dansalmo I am having trouble in 3.3.3. States tutorial, part 2:  Even though salt reports "Package apache2 is already installed", when it tries start the service it reports  "The following requisites were not found:     require:  pgk: apache2
19:27 dansalmo I am using Ubuntu 12.04
19:27 dave_den dansalmo: did you spell 'pkg' correctly?
19:27 fridiculous dansalmo can you show your state files in pastebin?
19:33 dansalmo dave_den: thanks!
19:33 ajw0100 joined #salt
19:33 rojem joined #salt
19:34 dave_den fixed?
19:34 dansalmo yes
19:38 higgs001 joined #salt
19:41 carnedepassaro joined #salt
19:44 ajw0100 joined #salt
19:47 BrendanGilmore joined #salt
19:48 fullung joined #salt
19:49 bemehow joined #salt
19:50 fullung i'm testing some changes to states and pillars directly on a minion with salt-call --local --file-root=... --pillar-root=... . we have some custom grains in states/_grains. is there a way to get these to work when i do salt-call --local -g without involving a server?
19:53 budrose joined #salt
19:53 juicer21 joined #salt
19:53 jperras fullung: http://docs.saltstack.com/ref/modules/all/salt.modules.saltutil.html#salt.modules.saltutil.sync_grains ?
19:54 vejdmn joined #salt
19:57 fullung jperras: i (preferably) don't want to do anything on the server that's handling machines in production. i want to work on everything locally on a mini[1;5Don that's not in production until i have everything working. i can do this with states and pillars, just not grains it seems?
19:58 helderco joined #salt
20:00 hunter joined #salt
20:00 jperras fullung: you want to match on a grain with salt-call, or you want to assign your minion specific grains?
20:02 gkze joined #salt
20:02 gkze how can I define a list in pillar to iterate over in a state, in the most simple way?
20:02 gkze I've only defined dicts in pillar before
20:03 Ryan_Lane1 fullung: depending on what you're doing, grains could be broken on the local node. also, I'm pretty sure you need to use file_roots for grains.
20:03 fullung jperras: i want minion-specific grains on the minion i'm testing on to be assigned by a custom script in a local _grains directory (let me know if this doesn't make sense. new to salt)
20:03 Ryan_Lane1 I couldn't figure out how to make grains work without file_roots and saltutil.sync_grains
20:03 Ryan_Lane1 the configuration for this kind of stuff is a giant mess and really badly documented
20:04 fullung Ryan_Lane1: i'm setting file_root on the command line for salt-call. are you saying that i should do that and sync_grains?
20:04 Ryan_Lane1 yep
20:04 fullung okay, thanks, let me try that
20:04 jperras fullung: have you tried setting your grains in the minion config? E.g. in /etc/salt/minion (a yaml file), under the grains: key
20:04 Ryan_Lane1 which is kind of silly, since it means your grains will get cached between runs
20:05 jperras unsure if that would work for you
20:05 ndrei joined #salt
20:05 fullung thanks, that did the trick
20:06 jperras which one? :)
20:06 Ryan_Lane1 I was assuming that fullung had custom python grains
20:06 fullung well, your first suggestion and ryan's. i didn't realise that sync_grains would do something useful for salt-call --local
20:06 jperras ah
20:07 jperras cool, as long as it works :). Wasn't sure why saltutil.sync_grains wouldn't work, but I don't use salt-call much.
20:07 Ryan_Lane1 I think it's absurd that sync_* is necessary at all when using masterless
20:07 bhosmer joined #salt
20:07 fullung agreed
20:07 ipalreadytaken joined #salt
20:07 Ryan_Lane1 for modules and pillars it isn't
20:08 ajw0100 joined #salt
20:10 wendall911 joined #salt
20:11 jaimed joined #salt
20:11 ndrei joined #salt
20:13 tvle joined #salt
20:13 DaveQB joined #salt
20:18 kickerdog joined #salt
20:20 kickerdog left #salt
20:21 Voziv Where does salt checkout git when being used as a backend?
20:23 dave_den Voziv: /var/cache/salt/gitfs or similar
20:23 dave_den i cant recall exactly
20:23 hunter joined #salt
20:23 Voziv yeah that's it (or close enough, found it). Thanks
20:24 dave_den np
20:25 viod joined #salt
20:25 AdamSewell joined #salt
20:26 Voziv Is there a reason why it would be checking out an empty directory? The ssh key hasn't changed (and I can clone the repo without a problem)
20:26 xmltok joined #salt
20:27 Voziv It was also using the git backend before without a problem
20:27 raizyr joined #salt
20:27 akoumjian joined #salt
20:28 abe_music joined #salt
20:29 dansalmo how would use salt states to integrate a script with startup/shutdown, such as: sudo update-rc.d new-script defaults
20:29 dansalmo do I just run it as a command or is there a better way?
20:29 jaimed joined #salt
20:30 timoguin Voziv, I don't think the master actually does a 'git checkout' by default
20:31 kermit joined #salt
20:31 timoguin but just grabs the metadata. a 'git log --all' should confirm
20:31 timoguin and you can do a manual 'git checkout' to look at everything
20:31 Voziv timoguin: right you are. Thanks
20:33 hunter Is there a migration document for those of us on 0.17.5 to 2014.1.0 ?
20:34 norokh joined #salt
20:34 Voziv Since that is the case: Do you know why I get 'No Top file or external nodes data matches found' when I try to run "salt 'mpstoolbox*' state.highstate" even though in my top.sls I have a section defined for it?
20:34 frasergraham if I assign a pillar value to all hosts that match a specific pattern e.g. "builder-*" and then later want to override that value for just one of those machines will that work?
20:35 pdayton1 joined #salt
20:35 Voziv My salt-master is on veryion 0.17.5
20:35 Voziv version*
20:37 ajprog_laptop1 joined #salt
20:37 hunter frasergraham: it might, _but_ I found other limitations that drove me to reclass
20:39 rjc joined #salt
20:39 frasergraham so, i'm just learning how to use Salt and I feel like i'm using it wrong. What is the preferred way to divide up a pool of 30 minions into 90%/10% dev prod mix and deploy different code to them? I often need to adjust that 90/10 mix based on testing needs so I want to be able to drive that from the master
20:40 hunter That I can't answer
20:40 ajw0100 joined #salt
20:40 hunter (becuase we don't do that, not yet at least).
20:41 hunter frasergraham: I'd look at a variable in pillar (or a grain) that says dev/prod and then drive what formulas/states go to a machine based on that.
20:41 frasergraham ok, so that's what i'm doing - but i dont want to list out each of the 30 machines individually with a dev or prod variable. I'd like to say "all these are prod, except those two"
20:42 gkze How can I properly write a list in pillar of packages I want to iterate over and install?
20:42 forrest frasergraham, is there any sort of rhyme or reasons?
20:43 forrest frasergraham, in the naming scheme? If not you should use: http://docs.saltstack.com/topics/targeting/nodegroups.html
20:43 forrest if you can't base it off grain data that is.
20:44 frasergraham all the machines are identical and have hostnames of "builder-001" - "builder-010". Sometimes I want to pull a specific one into the dev pool to debug something
20:44 frasergraham nodegroups sounds like exactly what I want
20:45 frasergraham do nodegroups have to be specified in the master config?
20:45 forrest frasergraham, yep!
20:45 frasergraham which means a restart of the salt-master service to change them?
20:46 forrest correct :(
20:46 hunter yes
20:46 djaime joined #salt
20:46 forrest frasergraham, hmm, are your machines in different subnets or anything?
20:46 forrest so you have a dev/test/prod subnet?
20:46 forrest or dev/prod in your case.
20:47 faldridge joined #salt
20:48 frasergraham yes, but it may expand to dev/test/prod soon
20:48 forrest so could you match on subnet?
20:48 frasergraham all on the same subnet
20:48 forrest oh bummer
20:48 snuffeluffegus joined #salt
20:48 forrest I'm struggling with this right now as well, but I can't use node groups, not realistic due to the number of machines. I've been considering writing a custom grain :\
20:48 corm joined #salt
20:49 forrest frasergraham, are you out on a public cloud?
20:49 forrest someone wrote ec2 grain stuff: https://github.com/saltstack/salt-contrib/tree/master/grains
20:49 frasergraham no, internal machines
20:49 forrest bummer
20:49 druonysus joined #salt
20:49 druonysus joined #salt
20:49 kballou joined #salt
20:50 frasergraham i have this pattern in a few different systems too, this is the smallest of them. I wanted to figure out the best way then apply it to the pool of 600 minions
20:50 frasergraham with the same 90/10 prod/dev split
20:50 frasergraham how would a custom grain help solve this?
20:50 frasergraham would that not require setting the dev/prod value on the minion? I'm trying to avoid ever having to login to a minion
20:51 Ryan_Lane1 joined #salt
20:51 forrest frasergraham, well, my plan was to create a grain that was super ghetto, and read from a static file that was dropped in by our provisioning system
20:52 forrest because I have ZERO data to base anything off of.
20:52 blee joined #salt
20:52 forrest my 'solution' if you can call it that totally sucks, but when every grain has identical grain information, and what unique info it has is utterly useless, I don't know what else to do, or how people are handling that in large environments.
20:52 forrest no way am I creating node groups for 800+ machines :P
20:53 frasergraham yeah, and similarly i dont want to list out all of my machines individually in a pillar file
20:53 forrest exactly
20:53 forrest I need to match grains, but there are no unique grains
20:53 forrest thus the custom :\
20:54 frasergraham i would have expected the matching rules to have some kind of precedence. If I set a key for all minions and then further down the pillar/top.sls set that same key for just a few minions I would expect it to overwrite the old one.
20:54 frasergraham but it doesn't appear to do that
20:55 forrest frasergraham, there's actually an issue on that I believe.
20:55 frasergraham oh really?
20:55 vejdmn joined #salt
20:55 forrest frasergraham, yea it's a few months old, I don't know if I have it handy...
20:55 hunter That bug is the one that drove me to reclass - yes, its a known issue in 0.17 at least.
20:56 frasergraham https://github.com/saltstack/salt/issues/1432
20:56 philipsd6 dunno if this would work for you frasergraham, but for temporarily pulling a machine into dev mode, how about something like this: salt -L 'builder-010,builder-021' grains.append role dev
20:56 forrest frasergraham, there was a newer one
20:57 schimmy joined #salt
20:57 forrest philipsd6, are you assigning the role grain on server build though?
20:57 forrest or when it's added to the salt master?
20:57 forrest doing that manually seems painful
20:57 frasergraham that one seems to imply I can set an order for sls rendering
20:58 Gifflen_ joined #salt
20:58 harobed joined #salt
20:58 frasergraham grains.append wouldn't survive a reboot, right?
20:58 Voziv What would stop files from being copied to a minion? I did salt '*' cp.list_master and I have a minion who has copied the data and a minion who hasn't
20:59 philipsd6 forrest: well if you don't have any way to use existing grains to target, and all you have is an arbitrary list of servers, then isn't that the only sane way of doing it?
20:59 vejdmn joined #salt
20:59 forrest philipsd6, pretty much, but I need it to survive reboots, and be able to handle a lot of machines being added daily
20:59 forrest no way I want to do that manually :P
21:00 schimmy1 joined #salt
21:00 philipsd6 I see. ok.
21:00 forrest philipsd6, yea it sucks
21:00 frasergraham specifying the order in the sls file seems to work for me
21:01 frasergraham if I set all machines to prod and then name the dev ones. Then i'm only specifying names for 10% of the pool instead of all of it
21:01 frasergraham better than nothing
21:02 dave_den the tops files are evaluated in order and the last one should have precedence, however if you are setting dict keys, the pillar data is merged with dict.update()
21:02 Gifflen joined #salt
21:03 Ryan_Lane1 joined #salt
21:04 dave_den this means if you have pillar={"foo": {"bar": "baz"}} for prod, and then pillar={"foo": {"quux": "zed"}}, your end pillar would be {"foo": {"bar": baz, "quux": "zed"}}
21:04 tvle joined #salt
21:04 dave_den only dicts are merged, so lists and string will overwrite the previous entry.
21:04 hunter dave_den: there's a bug (or two) on that that prevents myself and i believe frasergraham from using it in this case
21:05 dave_den oh, i'm not aware of the bug. but that's how it's *supposed*' to work :)
21:06 hunter let me find the bug number.
21:08 hunter dave_den: I personally suspect its related to 10900, but thats NOT the bug I had in mind.
21:09 hunter there's also 10553 but thats NOT the ticket I had in mind EITHER.
21:09 dave_den heh
21:09 hunter dave_den: damnit, I can't find it.
21:10 andr386 joined #salt
21:11 hunter dave_den: 3991 ? Maybe
21:11 hunter 9321
21:11 hunter 6126
21:12 rojem joined #salt
21:12 oraqol joined #salt
21:12 hunter 9184
21:12 dave_den now you're just typing random numbers
21:12 dave_den :D
21:12 hunter dave_den: how about we go with .... look - A WOOKIE!
21:12 oraqol So I'm getting some strange behavior from salt.
21:13 oraqol when I run salt '*' highstate, pretty much all minions get their state updates
21:13 hunter I was actaully looking at all the pillar related issues on github and trying to match up with the problem I was having.
21:13 oraqol but when I run it in batch mode, a large chunk of them don't.
21:13 oraqol Shouldn't this behavior be the inverse?
21:14 oraqol Any idea why this is happening?
21:19 pdayton joined #salt
21:20 manicouman joined #salt
21:24 nliadm Is it possible to have the master run a command to make a file if to doesn't exist in the salt state tree?
21:24 rainmanjam joined #salt
21:25 bhosmer joined #salt
21:27 aaroneous joined #salt
21:29 kickerdog joined #salt
21:30 ipalreadytaken joined #salt
21:32 CC0422 joined #salt
21:39 hunter joined #salt
21:39 tr_h joined #salt
21:40 hunter_ joined #salt
21:42 budrose joined #salt
21:43 budrose having some issue installing docker with saltstack...here is docker's init.sls file: https://gist.github.com/JulianGindi/1ff27d5c57c3e37741ac. Any help would be greatly appreciated
21:43 budrose ps. the error I am getting is, "The following packages failed to install/update: lxc-docker."
21:46 tr_h joined #salt
21:48 sroegner_ budrose: what are you trying to install it on?
21:48 faldridge joined #salt
21:48 budrose sroegner_: Ubuntu 13.04
21:50 tvle joined #salt
21:51 tvle joined #salt
21:51 oraqol left #salt
21:51 sroegner_ budrose: looks like you're missing the docker repo?
21:52 budrose sroegner_: Yeah, I think that is the case. How do I include it using salt states?
21:53 sroegner_ sth like this I'd say: http://docs.saltstack.com/ref/states/all/salt.states.pkgrepo.html#module-salt.states.pkgrepo
21:54 kickerdog joined #salt
21:56 Tekni joined #salt
21:56 nextdoorwarren joined #salt
21:58 meteorfox joined #salt
21:59 pdayton joined #salt
22:01 oz_akan_ joined #salt
22:02 krow joined #salt
22:16 ajw0100 joined #salt
22:18 rojem joined #salt
22:21 Gifflen joined #salt
22:28 pdayton joined #salt
22:31 joehoyle joined #salt
22:32 alunduil joined #salt
22:36 oznt joined #salt
22:38 rojem joined #salt
22:40 vbabiy_ joined #salt
22:44 renoirb Question about the salt command
22:45 renoirb Does it return a nonzero value if it had failures?
22:49 greg__ joined #salt
22:49 ahammond I want to iterate over the keys of a dict in a jinja file in a repeatable way. {% for dbname in sorted(databases.keys()) -%} doesn't work. What does?
22:49 Gifflen_ joined #salt
22:50 gtmacdonald joined #salt
22:50 ahammond ah, dictsort(). Ok.
22:56 frumpel I am confused. I would like to use a jinja template an insert data about the MASTER (specifically its IP) ... is there a way to do that or can you only access minion information in jinja. Probably RTFM so if anyone could point me at the right manual that would be much appreciated
22:57 rjc joined #salt
23:00 rojem joined #salt
23:00 seanz joined #salt
23:11 kermit joined #salt
23:13 ahammond any good examples of using dictsort?
23:14 ahammond google has failed me and the jinja docs are, well, kinda lacking.
23:14 FarrisG Re: salt-cloud, are there any hooks available to run some custom scripts after deploying hosts? For instance, we need to update internal DNS when a new host is deployed.
23:15 hunter FarrisG: I have no idea but what are you targetting salt-cloud against? I need to play with it
23:15 hunter I guess I could use a couple free EC2 instances
23:16 FarrisG hunter: Using ec2. After we deploy ec2 (vpc) instances, we need to run a script to update our internal DNS and change the hostname on the ec2 host.
23:16 hunter vpc?
23:16 nkuttler hunter: free ec2, digital ocean codes, etc
23:16 hunter nkuttler: eh? digital ocean has free instances?
23:16 FarrisG Virtual Private Cloud
23:17 hunter oh
23:17 hunter a whole new world to learn
23:17 nkuttler hunter: no, but there are plenty of promo codes around
23:17 nkuttler hunter: at least i found a $20 one a few weeks ago..
23:17 hunter oh. I could look. But my real target is our internal openstack cloud
23:17 nkuttler ah, even better :)
23:17 hunter But its not ready yet and I figured I could learn with EC2
23:18 nkuttler sure, ec2 will also work
23:18 nkuttler (once it's configured)
23:18 FarrisG Can someone point me toward a doc that tells me exactly how to use salt-cloud to deploy to a specific VPC subnet?
23:24 oz_akan_ joined #salt
23:24 AdamSewell joined #salt
23:24 frasergr_ joined #salt
23:30 themadcanudist joined #salt
23:31 ajw0100 joined #salt
23:39 joehoyle joined #salt
23:44 forrest joined #salt
23:48 cfqxdc joined #salt
23:48 krow joined #salt
23:50 dansalmo I created a new user with .sls  and it worked on minion, but what is the password?
23:50 themadcanudist left #salt
23:50 forrest dansalmo, what does it say in /etc/shadow?
23:51 Gordonz joined #salt
23:51 dansalmo on master or minion?
23:51 forrest on the minion
23:51 forrest if you didn't set a password, it shouldn't have one
23:51 forrest take a look at this: https://gist.github.com/UtahDave/3785738
23:52 dansalmo /etc/shodow is empty
23:53 forrest the user isn't in there?
23:53 forrest what OS is this
23:53 dansalmo Lubuntu 13.xxx
23:53 dansalmo The user did get added, I can try to log in
23:54 forrest well, I imagine there is a ! for the password
23:54 forrest you have to set one
23:54 forrest that's why I linked that gist, it shows users being stored in pillar for security
23:54 joehoyle joined #salt
23:56 dansalmo ! for password did not work
23:56 dansalmo OK, thanks
23:56 forrest no no
23:56 forrest ! = no password set
23:57 Ryan_Lane1 joined #salt
23:57 dansalmo When I do not enter anything for password, it does not work either
23:57 forrest right
23:57 forrest because ! = account locked
23:58 forrest unless I'm mistaken, I didn't double check it
23:59 ajw0100 joined #salt
23:59 Steve____ joined #salt

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